<?xml version='1.0' encoding='utf-8'?>
<graphml xmlns="http://graphml.graphdrawing.org/xmlns"><key id="node_entity_id" for="node" attr.name="entity_id" attr.type="string" /><key id="node_entity_type" for="node" attr.name="entity_type" attr.type="string" /><key id="node_canonical_name" for="node" attr.name="canonical_name" attr.type="string" /><key id="node_acronym" for="node" attr.name="acronym" attr.type="string" /><key id="node_domain" for="node" attr.name="domain" attr.type="string" /><key id="node_description" for="node" attr.name="description" attr.type="string" /><key id="node_observed_status" for="node" attr.name="observed_status" attr.type="string" /><key id="node_observed_as_of" for="node" attr.name="observed_as_of" attr.type="string" /><key id="node_confidence" for="node" attr.name="confidence" attr.type="string" /><key id="node_notes" for="node" attr.name="notes" attr.type="string" /><key id="edge_relationship_id" for="edge" attr.name="relationship_id" attr.type="string" /><key id="edge_source_entity_id" for="edge" attr.name="source_entity_id" attr.type="string" /><key id="edge_relationship_type" for="edge" attr.name="relationship_type" attr.type="string" /><key id="edge_target_entity_id" for="edge" attr.name="target_entity_id" attr.type="string" /><key id="edge_operational_context" for="edge" attr.name="operational_context" attr.type="string" /><key id="edge_observed_as_of" for="edge" attr.name="observed_as_of" attr.type="string" /><key id="edge_confidence" for="edge" attr.name="confidence" attr.type="string" /><key id="edge_notes" for="edge" attr.name="notes" attr.type="string" /><graph id="Atlas" edgedefault="directed"><node id="ALERT_CONTINGENT_LIABLE_OVERPAYMENT"><data key="node_entity_id">ALERT_CONTINGENT_LIABLE_OVERPAYMENT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Contingently Liable Overpayment Alert</data><data key="node_domain">Debt &amp; Overpayments / Work Control</data><data key="node_description">Annual SSA alert that notifies employees when a contingently liable individual in the same household is receiving benefits on the overpaid record that should be adjusted for recovery.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">OIG documents current use; the public report does not disclose the alert-generation implementation.</data></node><node id="ALERT_ECO_AWG_UNDELIV"><data key="node_entity_id">ALERT_ECO_AWG_UNDELIV</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">ECO-AWG Undeliverable Alerts</data><data key="node_acronym">Alerts E/F/G/H</data><data key="node_domain">Debt &amp; External Collections / AWG</data><data key="node_description">PCACS alert family generated by ECO when returned AWG employer mail cannot be automatically resent or otherwise resolved from available employer information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2022-08-22</data><data key="node_confidence">5</data><data key="node_notes">Includes documented Alert H for undeliverable AWG package and Alerts E/F/G for returned change/resume/stop garnishment notices.</data></node><node id="ALERT_PREPARE1184_REACT"><data key="node_entity_id">ALERT_PREPARE1184_REACT</data><data key="node_entity_type">work_control_artifact</data><data key="node_canonical_name">PREPARE 1184 REACT Alert</data><data key="node_acronym">PREPARE 1184</data><data key="node_domain">Title II / Payments / Work Control</data><data key="node_description">REACT work-control alert received by a Program Service Center when a manual F-stop is needed on a courtesy replacement check.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public POMS identifies the alert and triggering workflow but does not disclose its physical queue or persistence implementation.</data></node><node id="ALERT_REENTITLED_OVERPAYMENT"><data key="node_entity_id">ALERT_REENTITLED_OVERPAYMENT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Re-entitled Overpayment Alert</data><data key="node_domain">Debt &amp; Overpayments / Work Control</data><data key="node_description">Annual SSA alert that notifies employees when an overpaid individual is receiving OASDI benefits on a separate benefit record and those benefits should be adjusted to recover the overpayment.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">OIG documents current use and also identifies cases in which employees did not act on alerts.</data></node><node id="ALERT_RETAP_STUDENT_AGE18"><data key="node_entity_id">ALERT_RETAP_STUDENT_AGE18</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Regular Transcript Attainment and Selection Pass Student Age-18 Alert</data><data key="node_acronym">RETAP Student Alert</data><data key="node_domain">Title II / Student Benefits / Work Control</data><data key="node_description">Planned alert to identify cases where a child's benefits were terminated at age 18 even though the benefit record indicates full-time student status.</data><data key="node_observed_status">planned_fy2026</data><data key="node_observed_as_of">2026-02-25</data><data key="node_confidence">5</data><data key="node_notes">SSA states the solution will use Regular Transcript Attainment and Selection Pass Alerts in the Title II Redesign environment.</data></node><node id="ALERT_SSI_SAVINGS_SECURITY"><data key="node_entity_id">ALERT_SSI_SAVINGS_SECURITY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Savings Security Interface Alert</data><data key="node_acronym">SB alert</data><data key="node_domain">Title XVI / Program Integrity / Resources</data><data key="node_description">Work-control alert generated from the Fiscal Service savings-security match when qualifying ownership/value conditions are met.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says the alert posts to SSR and is controlled by PE ODS.</data></node><node id="API_EARQ"><data key="node_entity_id">API_EARQ</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Earnings Alert Query API</data><data key="node_acronym">EARQ API</data><data key="node_domain">Earnings / Integration</data><data key="node_description">API introduced for retirement iClaim straight-through processing to flag CCE claims that have earnings alerts requiring technician development.</data><data key="node_observed_status">production</data><data key="node_observed_as_of">2026-07-14</data><data key="node_confidence">5</data><data key="node_notes">SSA states the API went into production in late April 2026; exact production date is not stated.</data></node><node id="API_STATEMENT"><data key="node_entity_id">API_STATEMENT</data><data key="node_entity_type">system_interface</data><data key="node_canonical_name">Social Security Statement API</data><data key="node_acronym">Statement API</data><data key="node_domain">Digital Service / Social Security Statement</data><data key="node_description">Modern SSA Statement service described as using back-end systems to generate the online Social Security Statement PDF through Customer Communications Management.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Backend source systems, hosting, protocol, and API implementation are not publicly specified in the cited policy.</data></node><node id="APP_800_CLAIMS"><data key="node_entity_id">APP_800_CLAIMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">National 800 Number Claims Status</data><data key="node_domain">Customer Service / Telephone</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2008-02-15.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2008-02-15</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_800_EMPVER"><data key="node_entity_id">APP_800_EMPVER</data><data key="node_entity_type">application</data><data key="node_canonical_name">National 800 Number Employer Verification Automated Telephone Application</data><data key="node_domain">Customer Service / Employer</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2025-02-11.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_800_QA_BOT"><data key="node_entity_id">APP_800_QA_BOT</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSA 800 Number Public Question and Answer Bot and OIG Hotline Automation</data><data key="node_domain">Customer Service / AI</data><data key="node_description">Generative-AI/NLU automation that answers approved SSA.gov FAQ questions in English and Spanish and supports structured fraud, waste, and abuse intake.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2023-06-05</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_800_VOICE"><data key="node_entity_id">APP_800_VOICE</data><data key="node_entity_type">application</data><data key="node_canonical_name">National 800 Number Network Transfer of Voice Data Collection System</data><data key="node_domain">Customer Service / Telephone</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2008-10-11.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2008-10-11</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_AARPS_PORTAL"><data key="node_entity_id">APP_AARPS_PORTAL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Appeals and Appointed Representative Processing Services Portal</data><data key="node_acronym">AARPS</data><data key="node_domain">Representation / Digital Services</data><data key="node_description">Current portal for registered representatives to view registration and business information, client lists, and past fee-payment information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Public sources establish the portal and capabilities but do not disclose its backend data-store or interface topology; no RASR integration is inferred.</data></node><node id="APP_ACCSTATS"><data key="node_entity_id">APP_ACCSTATS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Statistics System</data><data key="node_acronym">ACCSTATS</data><data key="node_domain">Title XVI / Accounting</data><data key="node_description">Reports/accounts for daily and monthly SSI payments posted to the SSR for payment certification.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_ACCUWAGE"><data key="node_entity_id">APP_ACCUWAGE</data><data key="node_entity_type">application</data><data key="node_canonical_name">AccuWage Online</data><data key="node_acronym">AccuWage</data><data key="node_domain">Earnings / Employer</data><data key="node_description">BSO application for testing EFW2 and EFW2C formatted wage files for correctness before submission.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_ACDV"><data key="node_entity_id">APP_ACDV</data><data key="node_entity_type">application</data><data key="node_canonical_name">Automated Consumer Dispute Verification System</data><data key="node_acronym">ACDV</data><data key="node_domain">Debt &amp; Overpayments / Credit Reporting</data><data key="node_description">Online system linking credit bureaus and SSA for consumer disputes of SSA-reported overpayment debt.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-05-08</data><data key="node_confidence">5</data><data key="node_notes">Current Title II and Title XVI POMS identify ACDV. Operational processing is handled by NEPSC.</data></node><node id="APP_ACT"><data key="node_entity_id">APP_ACT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Assignment and Correspondence Tracking</data><data key="node_acronym">ACT</data><data key="node_domain">Enterprise Workflow / Correspondence</data><data key="node_description">SSA application/data asset that automates assigning correspondence, processing work electronically, and tracking assignment status.</data><data key="node_observed_status">observed_current_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-219. Current catalog listing does not establish physical relationship to EMAC.</data></node><node id="APP_ADRP"><data key="node_entity_id">APP_ADRP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Advance Designation of Representative Payee System</data><data key="node_acronym">ADRP</data><data key="node_domain">Representative Payee / Advance Designation</data><data key="node_description">System recording advance-designation information and contact history for individuals a beneficiary or claimant wants SSA to consider first if a payee is later needed.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Public advance designation service remains current; POMS documents system and access paths.</data></node><node id="APP_AFES"><data key="node_entity_id">APP_AFES</data><data key="node_entity_type">application</data><data key="node_canonical_name">Anti-Fraud Enterprise Solution</data><data key="node_acronym">AFES</data><data key="node_domain">Fraud / Analytics</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2018-04-18.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Active CMA 1094 explicitly retains CMS response data in AFES under SORN 60-0388 for fraud analytics or investigation leads.</data></node><node id="APP_AFII"><data key="node_entity_id">APP_AFII</data><data key="node_entity_type">application</data><data key="node_canonical_name">Access to Financial Institution Information</data><data key="node_acronym">AFII</data><data key="node_domain">SSI / Financial Data</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2005-09-08.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2005-09-08</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_AGENCY_SUPPORT_COMPANION"><data key="node_entity_id">APP_AGENCY_SUPPORT_COMPANION</data><data key="node_entity_type">application</data><data key="node_canonical_name">Agency Support Companion</data><data key="node_acronym">ASC</data><data key="node_domain">Enterprise AI / Employee Support</data><data key="node_description">Generative-AI assistant for agency staff supporting content generation, summarization, analysis, refinement, and research.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2025-04-16</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_AIRS"><data key="node_entity_id">APP_AIRS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Automated Incident Reporting System</data><data key="node_acronym">AIRS</data><data key="node_domain">Physical Security</data><data key="node_description">SAFE module documented for reporting security incidents at the user location.</data><data key="node_observed_status">observed_current_source_system</data><data key="node_observed_as_of">2025-08-20</data><data key="node_confidence">3</data><data key="node_notes">Historically documented as a SAFE module. The 2025 60-0350 SORN independently confirms AIRS remains a source of reports used for High Risk customer-service alerts; current internal module/platform implementation remains unconfirmed.</data></node><node id="APP_AI_COMMENT_ANALYSIS"><data key="node_entity_id">APP_AI_COMMENT_ANALYSIS</data><data key="node_entity_type">application</data><data key="node_canonical_name">AI Comment Analysis</data><data key="node_domain">Rulemaking / Public Comments</data><data key="node_description">Pilot generative-AI system that preliminarily flags public-comment content such as PII, offensive content, and other staff-defined categories for human review.</data><data key="node_observed_status">pilot</data><data key="node_observed_as_of">2025-09-21</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_AI_DIP"><data key="node_entity_id">APP_AI_DIP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Duplicate Identification Process</data><data key="node_acronym">DIP</data><data key="node_domain">Hearings &amp; Appeals / AI</data><data key="node_description">Machine-learning use case that identifies and flags duplicate cases for hearings.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2019-09-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_ALJ_MISCONDUCT"><data key="node_entity_id">APP_ALJ_MISCONDUCT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Administrative Law Judge/Public Alleged Misconduct Complaints System</data><data key="node_domain">Hearings / Oversight</data><data key="node_description">Electronic ALJ/PAMC complaint-management system that collects and maintains complaint-derived case, claimant, representative/filer, ALJ and review/investigation information.</data><data key="node_observed_status">observed_current_pia_architecture</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Direct 2025 PIA documents electronic housing and complaint-derived information. Underlying hosting, database product, and transport remain unspecified.</data></node><node id="APP_AMP"><data key="node_entity_id">APP_AMP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Automated Medicare Processing</data><data key="node_acronym">AMP</data><data key="node_domain">Title II / Medicare Claims</data><data key="node_description">Application previously used to process Medicare-only iClaims before the TAA path was released; some claims were also routed to MCS technicians.</data><data key="node_observed_status">documented_predecessor_path</data><data key="node_observed_as_of">2025-12-13</data><data key="node_confidence">5</data><data key="node_notes">A January 2026 EM says Medicare-only iClaims were previously processed via AMP. It does not state that AMP was fully retired.</data></node><node id="APP_APINET"><data key="node_entity_id">APP_APINET</data><data key="node_entity_type">application</data><data key="node_canonical_name">Administration Payments Information Network</data><data key="node_acronym">APINET</data><data key="node_domain">Finance / Accounting</data><data key="node_description">Intranet application documented as providing status access to administrative payment information processed through SSOARS.</data><data key="node_observed_status">documented_2020_current_status_unconfirmed</data><data key="node_observed_as_of">2020-05-19</data><data key="node_confidence">5</data><data key="node_notes">2020 SSOARS PIA; no later first-party source found in this run confirming current APINET status.</data></node><node id="APP_APPOINTED_REP"><data key="node_entity_id">APP_APPOINTED_REP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Appointed Representatives</data><data key="node_domain">Representation</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2010-02-04.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_APP_OBSERVABILITY_AI"><data key="node_entity_id">APP_APP_OBSERVABILITY_AI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Application Observability Support</data><data key="node_acronym">ACI</data><data key="node_domain">Infrastructure / Observability</data><data key="node_description">Machine-learning observability capability that establishes performance baselines and alerts on significant deviations for critical on-premises and cloud applications.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2025-04-03</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_APRS_SSOARS"><data key="node_entity_id">APP_APRS_SSOARS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Acquisition Planning and Reporting System</data><data key="node_acronym">APRS</data><data key="node_domain">Finance / Acquisition Planning</data><data key="node_description">SSOARS subsystem documented as tracking the Information Technology Systems budget; formerly called the Automated Procurement Requisition System.</data><data key="node_observed_status">documented_2020_current_status_unconfirmed</data><data key="node_observed_as_of">2020-05-19</data><data key="node_confidence">5</data><data key="node_notes">Do not confuse with Appeals Review Processing System (ARPS).</data></node><node id="APP_ARIS"><data key="node_entity_id">APP_ARIS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Allegation Referral Intake System</data><data key="node_acronym">ARIS</data><data key="node_domain">Program Integrity / Fraud Referrals</data><data key="node_description">SSA application through which employees and DDS personnel submit suspected program violations and criminal allegations to SSA OIG.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-06-24</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS requires ARIS referrals.</data></node><node id="APP_ARPS"><data key="node_entity_id">APP_ARPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Appeals Review Processing System</data><data key="node_acronym">ARPS</data><data key="node_domain">Appeals</data><data key="node_description">Appeals-processing system named in current field-office adjudication instructions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">EM-25061 identifies ARPS as the post-CPMS query for Appeals Council and Federal Court pending/closed cases.</data></node><node id="APP_ARS"><data key="node_entity_id">APP_ARS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Appointed Representative Services</data><data key="node_acronym">ARS</data><data key="node_domain">Representation / Electronic Records</data><data key="node_description">Current SSA application for appointed representatives to view and download electronic-folder contents, upload medical evidence and other documents, and obtain case status information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA pages also call this Electronic Records Express Appointed Representative Services (ERE ARS). Kept separate from the broader 2010 Appointed Representatives project/PIA object.</data></node><node id="APP_ARS2"><data key="node_entity_id">APP_ARS2</data><data key="node_entity_type">application</data><data key="node_canonical_name">Accounts Receivable System II</data><data key="node_acronym">ARS II</data><data key="node_domain">Debt &amp; Overpayments</data><data key="node_description">DMS subsystem that tracks and monitors Title II funds due from Treasury for inclusion in SSA general-ledger accounts receivable.</data><data key="node_observed_status">documented_current_dms_architecture</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Named in the 2018 DMS PIA still listed in SSA current PIA catalog; no separate 2026 operating instruction found in this run.</data></node><node id="APP_ASC"><data key="node_entity_id">APP_ASC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Appointment Scheduling Calendar</data><data key="node_acronym">ASC</data><data key="node_domain">Customer Service / Scheduling</data><data key="node_description">Web-based SSA appointment system used by customers and technicians to schedule, reschedule, modify and cancel initial-claim telephone appointments.</data><data key="node_observed_status">observed_limited_rollout</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes">Current SSA emergency message documents expanded production rollout; FY2027 budget calls the initiative National Appointment Scheduling Calendar.</data></node><node id="APP_AS_TOOL"><data key="node_entity_id">APP_AS_TOOL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Administrative Sanctions Tool</data><data key="node_acronym">AS Tool</data><data key="node_domain">Program Integrity / Administrative Sanctions</data><data key="node_description">SSA tool displaying administrative sanction periods and supporting sanction processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS references the tool; public implementation details are not published.</data></node><node id="APP_ATS"><data key="node_entity_id">APP_ATS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Audit Trail System</data><data key="node_acronym">ATS</data><data key="node_domain">Security / Audit</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2017-12-20.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2017-12-20</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_AURORA"><data key="node_entity_id">APP_AURORA</data><data key="node_entity_type">notice_processing_system</data><data key="node_canonical_name">Aurora</data><data key="node_acronym">Aurora</data><data key="node_domain">Notices / Processing Center</data><data key="node_description">Processing-center notice system; current POMS states Aurora notices automatically post to ORS.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2025-03-25</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_AWS_WLM_ATTEMPT"><data key="node_entity_id">APP_AWS_WLM_ATTEMPT</data><data key="node_entity_type">cloud_service</data><data key="node_canonical_name">AWS Workload Management Solution</data><data key="node_domain">Telephone / Workforce Management</data><data key="node_description">AWS workforce-management capability SSA attempted to use with AWS Connect for scheduling, forecasting, performance management, agent tracking, and reporting.</data><data key="node_observed_status">failed_and_replaced_2025</data><data key="node_observed_as_of">2025-07-31</data><data key="node_confidence">5</data><data key="node_notes">OIG reports scheduling/forecasting did not meet SSA needs and contractor compensation was provided.</data></node><node id="APP_BDCS"><data key="node_entity_id">APP_BDCS</data><data key="node_entity_type">application</data><data key="node_canonical_name">BOND Data Collection System</data><data key="node_acronym">BDCS</data><data key="node_domain">Disability Demonstrations / BOND</data><data key="node_description">BOND application used by contractor personnel to collect information on BOND participants.</data><data key="node_observed_status">historical_bond_project</data><data key="node_observed_as_of">2017-02-13</data><data key="node_confidence">4</data><data key="node_notes">Historical BOND architecture; current operation is not inferred.</data></node><node id="APP_BODS"><data key="node_entity_id">APP_BODS</data><data key="node_entity_type">application</data><data key="node_canonical_name">BOND Operations Data System</data><data key="node_acronym">BODS</data><data key="node_domain">Disability Demonstrations / BOND</data><data key="node_description">BOND standalone operations data system used to store/manage study information and send earnings-calculation data through BWS to BSAS.</data><data key="node_observed_status">historical_bond_project</data><data key="node_observed_as_of">2017-02-13</data><data key="node_confidence">5</data><data key="node_notes">2011 PIA says BODS was externally hosted outside SSA firewalls; 2017 IDMS PIA also describes its relationship with BSAS/BWS. BOND project later ended.</data></node><node id="APP_BOND"><data key="node_entity_id">APP_BOND</data><data key="node_entity_type">application</data><data key="node_canonical_name">Benefit Offset National Demonstration</data><data key="node_acronym">BOND</data><data key="node_domain">Disability Demonstration</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2011-01-19.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2011-01-19</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_BPS"><data key="node_entity_id">APP_BPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">BOND Project System</data><data key="node_acronym">BPS</data><data key="node_domain">Disability Demonstrations / BOND</data><data key="node_description">BOND analysis system used to analyze SSA, Rehabilitation Services Administration, and Department of Labor information on BOND participants.</data><data key="node_observed_status">historical_bond_project</data><data key="node_observed_as_of">2017-02-13</data><data key="node_confidence">4</data><data key="node_notes">Historical BOND architecture; current operation is not inferred.</data></node><node id="APP_BSAS"><data key="node_entity_id">APP_BSAS</data><data key="node_entity_type">application</data><data key="node_canonical_name">BOND Stand-Alone System</data><data key="node_acronym">BSAS</data><data key="node_domain">Disability Demonstrations / BOND</data><data key="node_description">SSA-side BOND application that accepted BODS files, stored beneficiary earnings/work-incentive estimates, and supported benefit-offset adjustment processing.</data><data key="node_observed_status">retired_obsolete</data><data key="node_observed_as_of">2024-07-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS marks the procedure obsolete and states the BOND project is over.</data></node><node id="APP_BUCS"><data key="node_entity_id">APP_BUCS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Bounty Update Control System</data><data key="node_acronym">BUCS</data><data key="node_domain">Program Integrity / Prisoner Payments</data><data key="node_description">System performing monthly sweeps of PUPS records with unpaid prisoner incentive amounts and passing payment records for EFT disbursement.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data></node><node id="APP_CAL_SELECTION"><data key="node_entity_id">APP_CAL_SELECTION</data><data key="node_entity_type">application</data><data key="node_canonical_name">Compassionate Allowances Selection Software</data><data key="node_acronym">CAL Selection Software</data><data key="node_domain">Disability / Fast Track</data><data key="node_description">Software that identifies Compassionate Allowances candidates from alleged impairments in disability reports and EDCS processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current CAL/QDD POMS identifies this software separately from the QDD predictive model.</data></node><node id="APP_CARS_SECURITY"><data key="node_entity_id">APP_CARS_SECURITY</data><data key="node_entity_type">application</data><data key="node_canonical_name">Compliance and Risk Survey System</data><data key="node_acronym">CARS</data><data key="node_domain">Physical Security</data><data key="node_description">SAFE module documented for performing physical-security compliance and risk assessments for SSA sites.</data><data key="node_observed_status">historically_documented_safe_module; current_implementation_unconfirmed</data><data key="node_observed_as_of">2013-09-30</data><data key="node_confidence">3</data><data key="node_notes">Named CARS is scoped here to the SMACS/SAFE physical-security module.</data></node><node id="APP_CATS"><data key="node_entity_id">APP_CATS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Civil Action Tracking System</data><data key="node_acronym">CATS</data><data key="node_domain">Legal / Class Actions</data><data key="node_description">System used to support implementation of class-action court orders, settlement agreements and Acquiescence Ruling notices.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA SORN catalog lists SORN 60-0186 and 2024 POMS still directs CATS queries.</data></node><node id="APP_CBSV"><data key="node_entity_id">APP_CBSV</data><data key="node_entity_type">application</data><data key="node_canonical_name">Consent Based Social Security Number Verification System</data><data key="node_acronym">CBSV</data><data key="node_domain">Identity Verification</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2008-11-05.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_CCE"><data key="node_entity_id">APP_CCE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Consolidated Claims Experience</data><data key="node_acronym">CCE</data><data key="node_domain">Title XVI Claims</data><data key="node_description">Current Title XVI claims experience used in 2026 operational instructions.</data><data key="node_observed_status">observed_current_under_modernization</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2027 Congressional Justification continues funding CCE modernization and describes further migration from legacy COBOL to modern cloud-native applications and APIs.</data></node><node id="APP_CCM"><data key="node_entity_id">APP_CCM</data><data key="node_entity_type">application</data><data key="node_canonical_name">Customer Communications Management</data><data key="node_acronym">CCM</data><data key="node_domain">Notices / Communications</data><data key="node_description">System/data asset used to develop and store notices and version information and identify notice recipients.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_CDREO"><data key="node_entity_id">APP_CDREO</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Continuing Disability Review Enforcement Operation</data><data key="node_acronym">CDREO</data><data key="node_domain">Title II Disability / Work CDR</data><data key="node_description">Automated earnings-enforcement operation that identifies Title II/concurrent disability beneficiaries with potentially uninvestigated substantial earnings and generates work CDR alerts.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS batch through 2026 describes CDREO operations and alert criteria.</data></node><node id="APP_CDR_MODEL"><data key="node_entity_id">APP_CDR_MODEL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Continuing Disability Review Model</data><data key="node_acronym">CDR Model</data><data key="node_domain">Disability / Program Integrity</data><data key="node_description">High-impact model that scores disability cases by likelihood of medical improvement for CDR prioritization.</data><data key="node_observed_status">deployed_high_impact</data><data key="node_observed_as_of">2023-09-30</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_CENTRAL_DATA_EXCHANGE_UNNAMED"><data key="node_entity_id">APP_CENTRAL_DATA_EXCHANGE_UNNAMED</data><data key="node_entity_type">application</data><data key="node_canonical_name">Unnamed Centralized Data Exchange Application</data><data key="node_domain">External Data Exchange / Identity Verification</data><data key="node_description">Centralized application into which SSA combined several data-exchange systems in FY2026; SSA plans to incorporate some Numident-verification systems into it.</data><data key="node_observed_status">observed_current_with_planned_expansion</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">OIG does not name the application, identify the consolidated systems, hosting, database, vendor, or interface technology. Do not equate it with DEVO without further evidence.</data></node><node id="APP_CET_SUITE_2016"><data key="node_entity_id">APP_CET_SUITE_2016</data><data key="node_entity_type">application_suite</data><data key="node_canonical_name">Customer Engagement Tools Application Suite</data><data key="node_acronym">CET</data><data key="node_domain">Customer Service / Digital Engagement</data><data key="node_description">Historical Customer Engagement Tools application suite identified as a planned key consumer of BORG person-centered data.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Kept separate from the CET Record System SORN/data-store entity. The source establishes application-suite consumer intent, not a physical record-store identity.</data></node><node id="APP_CFRMS"><data key="node_entity_id">APP_CFRMS</data><data key="node_entity_type">records_management_system</data><data key="node_canonical_name">Claims File Records Management System</data><data key="node_acronym">CFRMS</data><data key="node_domain">Claims / Records Management</data><data key="node_description">System supporting access, disclosure, retention and destruction of electronically stored information in the CFRMS claims folder.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_CFUI"><data key="node_entity_id">APP_CFUI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Claims File User Interface</data><data key="node_acronym">CFUI</data><data key="node_domain">Claims / Evidence</data><data key="node_description">Claims-file interface named in current field-office adjudication instructions.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_CHIP"><data key="node_entity_id">APP_CHIP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Customer Help and Information Program</data><data key="node_acronym">CHIP</data><data key="node_domain">Notices / Communications</data><data key="node_description">SSA application that can prepare cover notices and select forms/publications for Special Notice Option alternate-format fulfillment.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS supports the SNO workflow; internal technology and vendor details are not public in the cited source.</data></node><node id="APP_CICS_CUSTOMER_INFO"><data key="node_entity_id">APP_CICS_CUSTOMER_INFO</data><data key="node_entity_type">application</data><data key="node_canonical_name">Customer Information Control System</data><data key="node_acronym">CICS</data><data key="node_domain">Customer Service</data><data key="node_description">SSA customer information system named in current VAPT POMS as a surface where the CSRQ VAPT alert appears.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Kept separate from TECH_CICS (IBM CICS technology). Public POMS establishes the application name but not its physical implementation.</data></node><node id="APP_CIP"><data key="node_entity_id">APP_CIP</data><data key="node_entity_type">web_application</data><data key="node_canonical_name">Change in PIA</data><data key="node_acronym">CIP</data><data key="node_domain">Title II / Post-entitlement / PIA</data><data key="node_description">Web-based SSA application used in current POMS to process Primary Insurance Amount recomputations for specified post-entitlement pension/WEP cases.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current cited procedure applies to post-entitlement development for months of entitlement before January 2024. Broader current CIP scope is not inferred.</data></node><node id="APP_CIRP"><data key="node_entity_id">APP_CIRP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Comprehensive Integrity Review Process</data><data key="node_acronym">CIRP</data><data key="node_domain">Program Integrity</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2007-09-27.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">Current Data.gov inventory and March 2026 POMS independently corroborate CIRP operation.</data></node><node id="APP_CODE_MOD_AI"><data key="node_entity_id">APP_CODE_MOD_AI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Intelligent Generation of Modernized Code</data><data key="node_domain">Application Development / Modernization</data><data key="node_description">AI-assisted legacy modernization that analyzes legacy code and generates modernized code plus business and technical requirements.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2024-10-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_CODING_ASSIST"><data key="node_entity_id">APP_CODING_ASSIST</data><data key="node_entity_type">application</data><data key="node_canonical_name">Coding Assistance</data><data key="node_domain">Application Development / AI</data><data key="node_description">Pre-deployment agentic-AI coding assistant intended to improve developer efficiency and code quality.</data><data key="node_observed_status">pre_deployment</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_COGS"><data key="node_entity_id">APP_COGS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Court Ordered Garnishment System</data><data key="node_acronym">COGS</data><data key="node_domain">Title II / Garnishment</data><data key="node_description">SSA system that processes garnishment orders, including electronically submitted income-withholding orders, and supports garnishment case queries and actions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="APP_COMMUNICATIONS_CENTRAL"><data key="node_entity_id">APP_COMMUNICATIONS_CENTRAL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Communications Central</data><data key="node_domain">Operations / Communications</data><data key="node_description">SSA communications application/service through which specific mass-loss information is posted to SSAlerts.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named by current POMS; no physical platform or vendor is inferred.</data></node><node id="APP_CONTACT_CENTER_WFM"><data key="node_entity_id">APP_CONTACT_CENTER_WFM</data><data key="node_entity_type">cloud_service</data><data key="node_canonical_name">Cloud-Based Contact Center Workforce Management Software (Product Name Not Publicly Identified)</data><data key="node_domain">Telephone / Workforce Management</data><data key="node_description">Replacement cloud workforce-management software SSA purchased in July 2025 for workforce optimization, scheduling, forecasting, monitoring, and reporting.</data><data key="node_observed_status">observed_in_use_2026</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">OIG reports the product met SSA needs but does not identify the product name; no API/interface to Amazon Connect is inferred.</data></node><node id="APP_CPMS"><data key="node_entity_id">APP_CPMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Case Processing &amp; Management System</data><data key="node_acronym">CPMS</data><data key="node_domain">Hearings &amp; Appeals</data><data key="node_description">Retired hearings/appeals case-processing website that no longer receives new hearing-level appeals or decisions; historical data remains queryable.</data><data key="node_observed_status">retired_2025-09-26_historical_query_available</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">EM-25061 states CPMS website retired September 26, 2025. No new hearings-level appeals/decisions are added after retirement; historical data remains available to query. Earlier coexistence-with-HACPS status is superseded.</data></node><node id="APP_CPS"><data key="node_entity_id">APP_CPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Critical Payment System</data><data key="node_acronym">CPS</data><data key="node_domain">Title II / Critical Payments</data><data key="node_description">System used to establish, approve, transmit and record Title II critical/immediate payments.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-18</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_CSRQ"><data key="node_entity_id">APP_CSRQ</data><data key="node_entity_type">application</data><data key="node_canonical_name">Customer Service Record Query</data><data key="node_acronym">CSRQ</data><data key="node_domain">Customer Service / Identity Query</data><data key="node_description">SSA online application named by the current GUNSCHIP/GUNPUC03 inventory as a consumer of Numident-retrieval utilities.</data><data key="node_observed_status">current_open_data_inventory_reference</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">4</data><data key="node_notes">The current inventory names CSRQ but does not document its broader architecture, hosting, or complete data dependencies.</data></node><node id="APP_CWOSS"><data key="node_entity_id">APP_CWOSS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Comprehensive Work Opportunities Support System</data><data key="node_acronym">CWOSS</data><data key="node_domain">Ticket to Work / Work Incentives</data><data key="node_description">System capturing workload case-management, contract, and payment information to support Ticket to Work.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Catalog also uses the shortened title 'Comprehensive Work Opp Support System'.</data></node><node id="APP_CXFT"><data key="node_entity_id">APP_CXFT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Customer Feedback Tool</data><data key="node_acronym">CXFT</data><data key="node_domain">Customer Experience / Analytics</data><data key="node_description">Survey and text-analytics capability that produces sentiment, category, suggested-action, customer-effort, and translation outputs.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2021-08-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_CYBER_RISK_MGMT_TOOL"><data key="node_entity_id">APP_CYBER_RISK_MGMT_TOOL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Centralized Cybersecurity Risk Management Tool</data><data key="node_domain">Cybersecurity / Risk Management</data><data key="node_description">Centralized risk-management tool launched in FY2026 to align previously siloed cybersecurity risk processes; migration and refinement remained ongoing during the FY2026 FISMA assessment.</data><data key="node_observed_status">launched_fy2026_migration_ongoing</data><data key="node_observed_as_of">2026-09-24</data><data key="node_confidence">5</data><data key="node_notes">OIG does not publicly identify the product name or hosting architecture.</data></node><node id="APP_DABA"><data key="node_entity_id">APP_DABA</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Database Extraction/Selection System</data><data key="node_acronym">DABA</data><data key="node_domain">Title XVI / Data</data><data key="node_description">Selects SSRs using criteria supplied by process owners, external agencies and SSI subsystems.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_DACUS"><data key="node_entity_id">APP_DACUS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Death Alert Control and Update System</data><data key="node_acronym">DACUS</data><data key="node_domain">Death / Program Integrity</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2007-09-28.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_DAILY_FAX"><data key="node_entity_id">APP_DAILY_FAX</data><data key="node_entity_type">application</data><data key="node_canonical_name">Daily/Monthly Financial Accounting Exchange</data><data key="node_acronym">Daily/Monthly FAX</data><data key="node_domain">Title XVI / Accounting</data><data key="node_description">Tracks and controls payment/accounting transactions posted to the SSR.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_DALLAS_APPEALS"><data key="node_entity_id">APP_DALLAS_APPEALS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Dallas Appeals Application</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Application, commonly called Banana, used for SSI non-medical post-eligibility reconsideration requests and related Goldberg-Kelly payment-continuation/overpayment-recovery actions.</data><data key="node_observed_status">mandatory_use_as_of_source</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Emergency message says use remains mandatory until further notice due to the Amin settlement; retention date is 2026-10-03.</data></node><node id="APP_DATS"><data key="node_entity_id">APP_DATS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Death Alerts Tracking System</data><data key="node_acronym">DATS</data><data key="node_domain">Death / Program Integrity</data><data key="node_description">System used to display, document and clear death alerts arising from DIPS and Numident/payment-record discrepancies.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS revised September 15, 2026.</data></node><node id="APP_DCE"><data key="node_entity_id">APP_DCE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Document Conversion Engine</data><data key="node_acronym">DCE</data><data key="node_domain">Document Management / Conversion</data><data key="node_description">SSA Document Conversion Engine supported by the Apryse PDFTron PDFNet SDK according to a 2026 software-renewal solicitation.</data><data key="node_observed_status">observed_operational_support_target</data><data key="node_observed_as_of">2026-04-29</data><data key="node_confidence">5</data><data key="node_notes">The public notice validates DCE as a supported SSA component but does not disclose its broader architecture.</data></node><node id="APP_DCFS"><data key="node_entity_id">APP_DCFS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Disability Control File System</data><data key="node_acronym">DCFS</data><data key="node_domain">Disability / Post-entitlement</data><data key="node_description">IDMS subsystem/system wrapper around Disability Control File functions for disability adjudication history, earnings verification, CDR, Ticket to Work, and related controls.</data><data key="node_observed_status">historically_documented_2017_current_parent_pia_listed</data><data key="node_observed_as_of">2017-02-13</data><data key="node_confidence">4</data><data key="node_notes">The 2017 PIA identifies DCFS as an IDMS subsystem and DCF as the master file. Current PIA catalog still lists IDMS; current DCFS component boundaries are not independently verified.</data></node><node id="APP_DCPS"><data key="node_entity_id">APP_DCPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Disability Case Processing System</data><data key="node_acronym">DCPS</data><data key="node_domain">DDS Disability Processing</data><data key="node_description">DDS disability case-processing system used for development, adjudication and case notes.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_DCS_BUDGET"><data key="node_entity_id">APP_DCS_BUDGET</data><data key="node_entity_type">application</data><data key="node_canonical_name">DCS Budget Tracking System</data><data key="node_domain">IT Governance / Budget</data><data key="node_description">SSA budget tracking system whose database contains Information Technology and Other Objects budget allocation and expenditure data for monitoring and tracking.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current Data.gov metadata confirms the system/database function; application stack and interfaces are not disclosed.</data></node><node id="APP_DDSQ"><data key="node_entity_id">APP_DDSQ</data><data key="node_entity_type">application</data><data key="node_canonical_name">Disability Determination Services Query</data><data key="node_acronym">DDSQ</data><data key="node_domain">DDS / Queries</data><data key="node_description">DDS query source named in current field-office adjudication instructions.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_DEVO"><data key="node_entity_id">APP_DEVO</data><data key="node_entity_type">application</data><data key="node_canonical_name">Data Exchanges and Verifications Online</data><data key="node_acronym">DEVO</data><data key="node_domain">External Data Exchange</data><data key="node_description">Parameter-driven back-end for batch and real-time SSN verification and data-exchange processing.</data><data key="node_observed_status">observed_current_numident_verification_system</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">August 20, 2026 OIG audit treats DEVO as one of five Numident verification systems and reports FY2021-25 management data for it. Do not assume DEVO is the unnamed FY2026 centralized data-exchange application; the audit does not make that identification.</data></node><node id="APP_DGP"><data key="node_entity_id">APP_DGP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Data Governance Product</data><data key="node_acronym">DGP</data><data key="node_domain">Enterprise Data / Governance</data><data key="node_description">AI-enabled data-governance capability for discovery, classification, curation, predictive analysis, and data-quality rule creation.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2014-11-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_DGS"><data key="node_entity_id">APP_DGS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Document Generation System</data><data key="node_acronym">DGS</data><data key="node_domain">Hearings &amp; Appeals / Notices</data><data key="node_description">Document-generation application used by OHO for notices, decisions, dismissals and other correspondence.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current HALLEX identifies DGS alongside HACPS for document generation.</data></node><node id="APP_DHS_SELF_CHECK"><data key="node_entity_id">APP_DHS_SELF_CHECK</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">DHS Self Check</data><data key="node_acronym">Self Check</data><data key="node_domain">Identity / Employment Verification</data><data key="node_description">DHS-owned E-Verify subsystem that lets individuals check employment-eligibility information and may surface mismatches with SSA records.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA treats Self Check mismatches through normal SSN-record correction procedures; SSA staff do not use EV-STAR for Self Check cases.</data></node><node id="APP_DICARS_LEGACY"><data key="node_entity_id">APP_DICARS_LEGACY</data><data key="node_entity_type">application</data><data key="node_canonical_name">Disability Case Adjudication and Review</data><data key="node_acronym">DICARS</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">Legacy disability quality-review case-processing system. SSA FY2025 budget evidence says QRCPS replaced DICARS and DQR by September 2023, while May 2026 Federal Data Catalog metadata still describes DICARS as a legacy system supporting DQB quality-review workflows.</data><data key="node_observed_status">status_conflict_replacement_vs_2026_catalog_metadata</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">Do not treat the 2026 catalog description as proof that DICARS was reactivated. Current September 2026 POMS explicitly uses QRCPS in DQR workflows. Preserve both sources as a status conflict/stale-metadata issue pending an authoritative inventory retirement clarification.</data></node><node id="APP_DIGITAL_ID_AI"><data key="node_entity_id">APP_DIGITAL_ID_AI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Digital Identity Verification Services</data><data key="node_domain">Identity / Cybersecurity</data><data key="node_description">High-impact computer-vision AI used for online identity verification, risk indicators, fraud alerts, authentication logs, and compliance outputs.</data><data key="node_observed_status">deployed_high_impact</data><data key="node_observed_as_of">2020-06-05</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_DIGITAL_SERVICES_CONTROL"><data key="node_entity_id">APP_DIGITAL_SERVICES_CONTROL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Digital Services Control System</data><data key="node_acronym">Digital Services Control System</data><data key="node_domain">Notices / Digital Services</data><data key="node_description">Internal request system documented for notice-project teams to request QR codes/links from Digital Services.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No database, hosting platform, QR generator product, or transport is inferred beyond the documented internal request/control system.</data></node><node id="APP_DIPS"><data key="node_entity_id">APP_DIPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Death Information Processing System</data><data key="node_acronym">DIPS</data><data key="node_domain">Death / Program Integrity</data><data key="node_description">System used to add, change or remove death information on Numident and, in most cases, post death information to payment records.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS requires DIPS for death updates involving SSNs.</data></node><node id="APP_DMS"><data key="node_entity_id">APP_DMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Debt Management System</data><data key="node_acronym">DMS</data><data key="node_domain">Debt &amp; Overpayments</data><data key="node_description">Major SSA debt-management system controlling debt recovery, billing, external collection, remittances and debt-related due-process data through multiple subsystems.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS and the current PIA catalog corroborate continued operation; DMP is no longer being pursued and CRS implementation is a separate modernization path.</data></node><node id="APP_DMS_REMITTANCE"><data key="node_entity_id">APP_DMS_REMITTANCE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Debt Management System Remittance Process</data><data key="node_acronym">DMS Remittance</data><data key="node_domain">Debt &amp; Remittances</data><data key="node_description">DMS subsystem for recording, maintaining and tracking remittance data from beneficiaries and other remitters.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-10</data><data key="node_confidence">5</data><data key="node_notes">Current FO remittance instructions identify DMS remittance input and receipt functions.</data></node><node id="APP_DMT_DM_TRACKING"><data key="node_entity_id">APP_DMT_DM_TRACKING</data><data key="node_entity_type">application</data><data key="node_canonical_name">Administrative Debt Management Team DM Tracking System</data><data key="node_acronym">DM system</data><data key="node_domain">Finance / Administrative Debt</data><data key="node_description">Internal Debt Management Team system used to track return of incorrectly paid prisoner incentive payments and follow-up actions.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">4</data><data key="node_notes">POMS calls this the “Debt Management (DM) system” but does not establish whether it is the same physical application as SSA Debt Management System (DMS).</data></node><node id="APP_DM_CONVERSION"><data key="node_entity_id">APP_DM_CONVERSION</data><data key="node_entity_type">application</data><data key="node_canonical_name">Debt Management Conversion</data><data key="node_acronym">DM Conversion</data><data key="node_domain">Debt &amp; Overpayments</data><data key="node_description">DMS subsystem that prepares online Title II debt-management transactions for ROAR, RECOOP, Remittance Process and ECO.</data><data key="node_observed_status">documented_current_dms_architecture</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Current cataloged DMS PIA architecture; no separate fresh operating source found.</data></node><node id="APP_DOORS"><data key="node_entity_id">APP_DOORS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Detailed Office/Organization Resource System</data><data key="node_acronym">DOORS</data><data key="node_domain">SSA Internal Operations / Routing</data><data key="node_description">SSA resource used to obtain office or organization address, telephone, and email information, including WSU contact information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS batch references DOORS; substantive section revision is 2022, so current implementation detail beyond documented use is not inferred.</data></node><node id="APP_DPS"><data key="node_entity_id">APP_DPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Document Processing System</data><data key="node_acronym">DPS</data><data key="node_domain">Notices / Communications</data><data key="node_description">SSA notice-generation system used for manual due-process/final notices, representative-appointment notices when automated delivery fails, wage-report receipts, and Special Notice Option workflows.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS supports operational use; runtime platform and vendor are not inferred.</data></node><node id="APP_DQR_LEGACY"><data key="node_entity_id">APP_DQR_LEGACY</data><data key="node_entity_type">application</data><data key="node_canonical_name">Disability Quality Review Legacy System</data><data key="node_acronym">DQR</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">Legacy DQR system named by SSA as replaced by QRCPS; distinct from the continuing DQR business function.</data><data key="node_observed_status">replaced_legacy_by_2023_09</data><data key="node_observed_as_of">2023-09</data><data key="node_confidence">5</data><data key="node_notes">Do not conflate this legacy system entity with the current Disability Quality Review process.</data></node><node id="APP_DRAMS"><data key="node_entity_id">APP_DRAMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Disability, Railroad, Alien and Military Service Query</data><data key="node_acronym">DRAMS</data><data key="node_domain">Queries / Eligibility</data><data key="node_description">Query named in current POMS as a source of acceptable proof.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-06-15</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_DRAP"><data key="node_entity_id">APP_DRAP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Digital Recording Acquisition Project</data><data key="node_acronym">DRAP</data><data key="node_domain">Hearings &amp; Appeals / Recording</data><data key="node_description">Legacy hearing-recording system/project that replaced analog recording with digital audio and was later identified by SSA as the legacy system being replaced by HeaRT.</data><data key="node_observed_status">legacy_superseded_in_hearing_recording_workflow</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA confirms HeaRT migration from legacy DRAP. Public sources do not prove every historical DRAP component or stored recording has been physically decommissioned.</data></node><node id="APP_DVW"><data key="node_entity_id">APP_DVW</data><data key="node_entity_type">reference_portal</data><data key="node_canonical_name">Document Verification Website</data><data key="node_acronym">DVW</data><data key="node_domain">Identity / Enumeration / Document Authentication</data><data key="node_description">SSA document-verification reference portal that provides access to identity-document visual standards and resources including Docutector and other verification material.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Public POMS describes DVW as the access point for document-verification resources; internal hosting and authentication architecture are not public.</data></node><node id="APP_DXQM"><data key="node_entity_id">APP_DXQM</data><data key="node_entity_type">query_platform</data><data key="node_canonical_name">DXQM</data><data key="node_acronym">DXQM</data><data key="node_domain">Payments / Query Infrastructure</data><data key="node_description">SSA query platform/location on which the Treasury Check Verification Query is available to field offices.</data><data key="node_observed_status">current_federal_data_catalog_reference</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">4</data><data key="node_notes">Only the TCVQ catalog entry establishes DXQM here. Expansion, hosting, database technology, and other functions remain unresolved.</data></node><node id="APP_E4641"><data key="node_entity_id">APP_E4641</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic SSA-4641</data><data key="node_acronym">e4641</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">Web-based electronic component used with eAFI to request financial-institution account information and historical balances.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes">POMS calls this the e4641 website; no inference is made about hosting, implementation, or vendor.</data></node><node id="APP_E562"><data key="node_entity_id">APP_E562</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic E562 Request for Assistance</data><data key="node_acronym">e562</data><data key="node_domain">SSA Internal Communications</data><data key="node_description">Electronic request-for-assistance mechanism available across SSA regions and foreign service posts for interoffice development requests.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS describes availability and use; public material does not expose implementation details.</data></node><node id="APP_EAFI"><data key="node_entity_id">APP_EAFI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Access to Financial Institutions</data><data key="node_acronym">eAFI</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">Electronic AFI subsystem used to request and view financial-institution account balance data for SSI resource verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes">POMS identifies eAFI as one of the two main AFI components; protocol and current vendor are not publicly identified in this source.</data></node><node id="APP_EAUTH"><data key="node_entity_id">APP_EAUTH</data><data key="node_entity_type">application</data><data key="node_canonical_name">e-Authentication</data><data key="node_acronym">eAuth</data><data key="node_domain">Identity / Digital Access</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2011-05-31.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2011-05-31</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_EAUTH827"><data key="node_entity_id">APP_EAUTH827</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Authorization</data><data key="node_acronym">eAuthorization</data><data key="node_domain">Disability / Evidence Authorization</data><data key="node_description">Current SSA eAuthorization screen/process used in EDCS and eView to attest, submit, and create an electronically signed SSA-827 that the system adds to the electronic folder.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directly documents the SSA-827 eAuthorization screen in EDCS/eView and automatic addition of the signed form to the electronic folder.</data></node><node id="APP_EBB"><data key="node_entity_id">APP_EBB</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Bench Book</data><data key="node_acronym">eBB</data><data key="node_domain">Hearings / Adjudication Support</data><data key="node_description">Electronic bench-book application linked from eView for qualifying hearing-office-level or higher cases.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-25</data><data key="node_confidence">4</data><data key="node_notes">The operative POMS text is older but the page batch ran in September 2026; detailed current feature set requires further validation.</data></node><node id="APP_ECAT"><data key="node_entity_id">APP_ECAT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Claims Analysis Tool</data><data key="node_acronym">eCAT</data><data key="node_domain">Disability / Adjudication</data><data key="node_description">Electronic disability analysis/documentation tool based on sequential evaluation.</data><data key="node_observed_status">partially_active_or_transitioning</data><data key="node_observed_as_of">2026-07-13</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS still uses eCAT in some workflows while other 2025/2026 guidance explicitly removes eCAT references in favor of DCPS.</data></node><node id="APP_ECBSV"><data key="node_entity_id">APP_ECBSV</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Consent Based Social Security Number Verification System</data><data key="node_acronym">eCBSV</data><data key="node_domain">Identity Verification</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2020-07-15.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2020-07-15</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_ECC"><data key="node_entity_id">APP_ECC</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Enterprise Contact Center</data><data key="node_acronym">ECC</data><data key="node_domain">Customer Service / Contact Center</data><data key="node_description">SSA cloud-based enterprise contact-center solution described in FY2027 modernization plans.</data><data key="node_observed_status">observed_current_modernization</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">FY2027 budget identifies it as the agency's cloud-based contact-center solution; exact provider/component topology is not inferred here.</data></node><node id="APP_ECMS"><data key="node_entity_id">APP_ECMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Earnings Case Management System</data><data key="node_acronym">ECMS</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">System containing the electronic REAP Form SSA-4130 used for some earnings adjustments.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Detailed POMS evidence is from 2019.</data></node><node id="APP_ECO"><data key="node_entity_id">APP_ECO</data><data key="node_entity_type">application</data><data key="node_canonical_name">External Collection Operation</data><data key="node_acronym">ECO</data><data key="node_domain">Debt &amp; External Collections</data><data key="node_description">DMS external-collection subsystem that selects delinquent debts for TOP/TRO, administrative offset, AWG, FSO and credit-bureau reporting.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS states ECO selects and maintains debts sent to TOP and performs automated external-collection selection.</data></node><node id="APP_ECOMPS"><data key="node_entity_id">APP_ECOMPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI eComputations</data><data key="node_acronym">eComps</data><data key="node_domain">Title XVI / Computations</data><data key="node_description">SSA computation application used for manual Title II/Title XVI windfall offset calculations and other SSI benefit calculations.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS still instructs staff to use eComps. Physical implementation and persistence are not published.</data></node><node id="APP_EDCS"><data key="node_entity_id">APP_EDCS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Disability Collect System</data><data key="node_acronym">EDCS</data><data key="node_domain">Disability Intake</data><data key="node_description">Electronic disability intake/collection system receiving data from multiple SSA mainframe sources.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-01</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_EEO"><data key="node_entity_id">APP_EEO</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Earnings Enforcement Operation</data><data key="node_acronym">EEO</data><data key="node_domain">Title II / Earnings Test</data><data key="node_description">Automated Title II earnings-test enforcement system that compares MEF earnings with MBR-reported earnings to identify potential overpayments, underpayments and cases requiring review.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS describes the EEO as an automated system and current enforcement process.</data></node><node id="APP_EFI"><data key="node_entity_id">APP_EFI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Folder Interface</data><data key="node_acronym">EFI</data><data key="node_domain">Disability / Integration</data><data key="node_description">Messaging hub documented within eDIB for transmitting messages among systems involved in electronic disability case processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current EDCS Actions procedures explicitly describe active AR transaction processing through EFI. Detailed internal topology remains based on older eDIB documentation and is not promoted beyond what current POMS supports. 2018 eDIB PIA also referred to the Electronic Folder Interface Test and described it as the electronic disability messaging hub.</data></node><node id="APP_EFORMS"><data key="node_entity_id">APP_EFORMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">eForms</data><data key="node_acronym">eForms</data><data key="node_domain">Disability / Evidence Forms</data><data key="node_description">Electronic forms program linked from EDCS for disability-case forms not otherwise available directly in EDCS.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-01</data><data key="node_confidence">5</data><data key="node_notes">Current EDCS TOC retains eForms. Detailed behavior comes from older POMS instructions and is modeled only where explicitly documented.</data></node><node id="APP_EIAR"><data key="node_entity_id">APP_EIAR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Interim Assistance Reimbursement</data><data key="node_acronym">eIAR</data><data key="node_domain">Title XVI / SSI</data><data key="node_description">Automates Interim Assistance Reimbursement between SSA and participating IAR states.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Component described in 2021 SSIRMS PIA still linked in current PIA catalog; current POMS separately corroborates eIAR workflow.</data></node><node id="APP_ELAS"><data key="node_entity_id">APP_ELAS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Database and Enhanced Leads and Appointment Systems</data><data key="node_acronym">eLAS</data><data key="node_domain">Customer / Appointments</data><data key="node_description">Leads/appointment system named in current field-office adjudication instructions.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_EMAC"><data key="node_entity_id">APP_EMAC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Management of Assignments and Correspondence</data><data key="node_acronym">EMAC</data><data key="node_domain">Enterprise Workflow / Correspondence</data><data key="node_description">Internal web-based system for authorized employees to access, create, assign, track, and process internal and external correspondence through completed response.</data><data key="node_observed_status">reengineering_reported</data><data key="node_observed_as_of">2025-07-14</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data says EMAC is in the process of being re-engineered; no public completion date or replacement architecture is stated.</data></node><node id="APP_ENM"><data key="node_entity_id">APP_ENM</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Non-Medical</data><data key="node_acronym">ENM</data><data key="node_domain">Hearings &amp; Appeals</data><data key="node_description">OHO/OAO electronic non-medical system referenced in current operational instructions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">EM-25061 directs technicians to ENM queries for non-medical hearing information after CPMS retirement.</data></node><node id="APP_EP"><data key="node_entity_id">APP_EP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Evidence Portal</data><data key="node_acronym">EP</data><data key="node_domain">Evidence &amp; Documents</data><data key="node_description">Application used to search/store evidence in SSA electronic repositories and disability folders.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_EPECS"><data key="node_entity_id">APP_EPECS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Personal Enrollment Credential System</data><data key="node_acronym">EPECS</data><data key="node_domain">Identity / Physical Security</data><data key="node_description">Primary enrollment entry point documented under SMACS for SSA employees, contractors, and other personnel; creates credential records and supports identity proofing/background-investigation workflows.</data><data key="node_observed_status">documented_component_of_currently_listed_parent; current_implementation_unconfirmed</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">SMACS remains in SSA current PIA catalog, but the detailed EPECS implementation evidence comes from the 2013 SMACS PIA.</data></node><node id="APP_EQA"><data key="node_entity_id">APP_EQA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Quality Assurance</data><data key="node_acronym">eQA</data><data key="node_domain">Quality / Oversight</data><data key="node_description">Web-enabled SSA intranet application documented in 2018 for quality performance studies and reviews across enumeration, Title II, Title XVI, Medicare Part D subsidy, and hearing-level samples; supports study definition, sample selection, findings, reporting, BPM, support materials, and EFI communication.</data><data key="node_observed_status">documented_2018_current_status_unconfirmed</data><data key="node_observed_as_of">2018-12-18</data><data key="node_confidence">5</data><data key="node_notes">QAS PIA remains published/current-listed at parent level, but eQA production status after 2018 is not independently established.</data></node><node id="APP_EQS"><data key="node_entity_id">APP_EQS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Earnings Query System</data><data key="node_acronym">EQS</data><data key="node_domain">Earnings / Queries</data><data key="node_description">Web application identified by SSA in 2026 instructions for displaying earnings alerts; its alert logic was stricter than the legacy PCOM EARQ logic when first deployed.</data><data key="node_observed_status">observed_current_with_interim_legacy_fallback</data><data key="node_observed_as_of">2026-07-14</data><data key="node_confidence">5</data><data key="node_notes">SSA instructed technicians to continue using the legacy PCOM application until EQS logic was aligned. Do not infer later remediation completion.</data></node><node id="APP_ERE"><data key="node_entity_id">APP_ERE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Records Express</data><data key="node_acronym">ERE</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Secure electronic service for submitting medical, vocational and other disability evidence and associating it with a claimant's electronic folder.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA ERE service remains available.</data></node><node id="APP_ERE_EXPERTS"><data key="node_entity_id">APP_ERE_EXPERTS</data><data key="node_entity_type">web_application</data><data key="node_canonical_name">Electronic Records Express for Experts</data><data key="node_acronym">ERE for Experts</data><data key="node_domain">Hearings / Evidence / External Access</data><data key="node_description">SSA web service enabling authorized medical and vocational experts to access assigned electronic case material, receive status reports, and upload specified documents.</data><data key="node_observed_status">observed_current_public_service</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA page remains live and provides release history from 2016 onward.</data></node><node id="APP_ERMS"><data key="node_entity_id">APP_ERMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Earnings Record Maintenance System</data><data key="node_acronym">ERMS</data><data key="node_domain">Earnings</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2007-09-27.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_ERPA"><data key="node_entity_id">APP_ERPA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Representative Payee Accounting</data><data key="node_acronym">eRPA</data><data key="node_domain">Representative Payee / Accounting</data><data key="node_description">Electronic accounting component used to control and process representative-payee accounting workloads.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current Data.gov asset US-GOV-SSA-149; POMS identifies eRPA within eRPS.</data></node><node id="APP_ERPC"><data key="node_entity_id">APP_ERPC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Request for Program Consultation Web-Based Tool</data><data key="node_acronym">eRPC</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">SSA web-based tool that manages Request for Program Consultation submissions, workload, notifications, scheduling, data searches and dashboards.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-18</data><data key="node_confidence">5</data><data key="node_notes">Public POMS also calls it the RPC tool.</data></node><node id="APP_ERPS"><data key="node_entity_id">APP_ERPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Representative Payee System</data><data key="node_acronym">eRPS</data><data key="node_domain">Representative Payee</data><data key="node_description">Primary representative-payee application and data system for applications, selection, suitability, payee-related information, misuse processing, and synchronization/control workflows with benefit payment records.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-16</data><data key="node_confidence">5</data><data key="node_notes">Current POMS and September 2026 Open Data inventory corroborate active use. Some MBR/SSR payment-record updates remain manual or workflow-dependent; rare no-SSN payee cases bypass eRPS.</data></node><node id="APP_ESCORR"><data key="node_entity_id">APP_ESCORR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Enumeration System Correspondence</data><data key="node_acronym">ESCORR</data><data key="node_domain">enumeration and identity</data><data key="node_description">SSA application used in the Form 4029 return workflow to key required information affecting the Numident.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS RM 04906.001; backend/technology not inferred.</data></node><node id="APP_ESD_MI"><data key="node_entity_id">APP_ESD_MI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Service Delivery Management Information</data><data key="node_acronym">ESD MI</data><data key="node_domain">Digital Service / Analytics</data><data key="node_description">Automated application that produces electronic-service-delivery management information.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">The public catalog does not publish implementation technology or interfaces.</data></node><node id="APP_ESPF"><data key="node_entity_id">APP_ESPF</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">electronic SSA Protective Filing Tool</data><data key="node_acronym">eSPF</data><data key="node_domain">Customer Service / Protective Filing</data><data key="node_description">Historical public-facing web tool that let individuals request an appointment to file for benefits and establish a protective filing date for themselves or another person.</data><data key="node_observed_status">decommissioned</data><data key="node_observed_as_of">2024-11-21</data><data key="node_confidence">5</data><data key="node_notes">Released 2022-03-19 and decommissioned 2024-11-21. Pending requests continued to be worked in eLAS after retirement.</data></node><node id="APP_ESS"><data key="node_entity_id">APP_ESS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Enterprise Scheduling System</data><data key="node_acronym">ESS</data><data key="node_domain">Customer Service / Scheduling</data><data key="node_description">SSA scheduling system used for enumeration and post-entitlement appointments, including employee scheduling and customer self-scheduling capabilities.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes">Current POMS preserves eLAS for initial claims while ESS handles PE and enumeration scheduling.</data></node><node id="APP_ETO"><data key="node_entity_id">APP_ETO</data><data key="node_entity_type">application</data><data key="node_canonical_name">Efforts to Outcomes</data><data key="node_acronym">ETO</data><data key="node_domain">Ticket to Work / Case Management</data><data key="node_description">Commercial off-the-shelf web case-management application described as supporting Ticket to Work client recruitment, demographics, assessments, and outcomes.</data><data key="node_observed_status">historically_documented_2017</data><data key="node_observed_as_of">2017-02-13</data><data key="node_confidence">4</data><data key="node_notes">2017 IDMS PIA evidence only; current use is unverified.</data></node><node id="APP_ETS"><data key="node_entity_id">APP_ETS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Enterprise Ticketing System</data><data key="node_acronym">ETS</data><data key="node_domain">IT Service Management</data><data key="node_description">AI-enabled ServiceNow capability that consolidates searches across applications and portals to help employees locate the correct request form.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2025-09-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_EVID"><data key="node_entity_id">APP_EVID</data><data key="node_entity_type">application</data><data key="node_canonical_name">Evidence Screens</data><data key="node_acronym">EVID</data><data key="node_domain">Evidence</data><data key="node_description">Evidence screens in SSA's Shared Process Menu used as acceptable proof and operational evidence.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_EVIEW"><data key="node_entity_id">APP_EVIEW</data><data key="node_entity_type">application</data><data key="node_canonical_name">eView</data><data key="node_acronym">eView</data><data key="node_domain">Disability Evidence</data><data key="node_description">Web application for viewing and acting on disability information in the electronic folder.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_EVITAL"><data key="node_entity_id">APP_EVITAL</data><data key="node_entity_type">application</data><data key="node_canonical_name">eVital / Electronic Death Registration</data><data key="node_acronym">eVital</data><data key="node_domain">Death / Vital Records</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2005-09-08.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2005-09-08</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_EVS"><data key="node_entity_id">APP_EVS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Enumeration Verification System</data><data key="node_acronym">EVS</data><data key="node_domain">Identity Verification</data><data key="node_description">Batch SSN verification application serving government agencies, private companies and internal SSA users.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">Current metadata says future replacement by DEVO.</data></node><node id="APP_EV_STAR"><data key="node_entity_id">APP_EV_STAR</data><data key="node_entity_type">application</data><data key="node_canonical_name">EV-STAR</data><data key="node_acronym">EV-STAR</data><data key="node_domain">Identity / Employment Verification</data><data key="node_description">Application SSA field offices and card centers use to record resolution of E-Verify cases.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current Self Check/E-Verify POMS differentiates EV-STAR case handling from Self Check.</data></node><node id="APP_EWORK"><data key="node_entity_id">APP_EWORK</data><data key="node_entity_type">application</data><data key="node_canonical_name">eWork</data><data key="node_acronym">eWork</data><data key="node_domain">Work CDR / Earnings</data><data key="node_description">Application used to develop and effectuate work continuing-disability reviews.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-05-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_EWR"><data key="node_entity_id">APP_EWR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Electronic Wage Reporting System</data><data key="node_acronym">EWR</data><data key="node_domain">Earnings / Employer</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2012-01-20.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2012-01-20</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_FACTS"><data key="node_entity_id">APP_FACTS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Fee Action Tracking System</data><data key="node_acronym">FAcTS</data><data key="node_domain">Representation / Hearings</data><data key="node_description">OHO tracking and notice-generation system used for representative fee administrative review.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_FALCON"><data key="node_entity_id">APP_FALCON</data><data key="node_entity_type">application</data><data key="node_canonical_name">Falcon Data Entry System</data><data key="node_acronym">Falcon</data><data key="node_domain">Data Entry</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2007-09-27.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_FAS"><data key="node_entity_id">APP_FAS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSA Functional Assessment Study System</data><data key="node_domain">Disability / Research</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2025-02-11.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_FAS_QDS"><data key="node_entity_id">APP_FAS_QDS</data><data key="node_entity_type">application_module</data><data key="node_canonical_name">Questionnaire Delivery System</data><data key="node_acronym">QDS</data><data key="node_domain">Disability / Research / Functional Assessment</data><data key="node_description">Module of the Calibration Study Management System that delivers study questionnaires through Westat interviewers or directly to participants through a web application.</data><data key="node_observed_status">documented_current_pia_architecture</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Documented as one of two discrete SMS modules in the current FAS PIA.</data></node><node id="APP_FAS_SMS"><data key="node_entity_id">APP_FAS_SMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Calibration Study Management System</data><data key="node_acronym">SMS</data><data key="node_domain">Disability / Research / Functional Assessment</data><data key="node_description">Web-based Functional Assessment Study system built and hosted by Westat to prescreen, enroll and track participants, protect data, and administer study questionnaires.</data><data key="node_observed_status">documented_current_pia_architecture</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The current FAS PIA documents the architecture but uses study/project language; this does not prove continuous production use throughout 2026.</data></node><node id="APP_FECS"><data key="node_entity_id">APP_FECS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Front End Capture System</data><data key="node_acronym">FECS</data><data key="node_domain">Disability / Evidence Intake</data><data key="node_description">Capture servers deployed in DDS/OHO that are counted in current ERE management-information reporting.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-05-22</data><data key="node_confidence">5</data><data key="node_notes">Current ERE MI asset explicitly reports volumes at each FECS.</data></node><node id="APP_FEEBAYNET"><data key="node_entity_id">APP_FEEBAYNET</data><data key="node_entity_type">application</data><data key="node_canonical_name">FeeBayNet Non-Programmatic Fee Invoicing</data><data key="node_acronym">FeeBayNet</data><data key="node_domain">Finance / Payments</data><data key="node_description">Named SSA fee-invoicing application; not used to process the standard administrative fee payments handled by SERS.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_FFAP"><data key="node_entity_id">APP_FFAP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Fugitive Felon Automated Process</data><data key="node_acronym">FFAP</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">Fugitive Felon Automated Process used to automate SSI fugitive-felon suspension actions and notices for most cases; weekly cases can post N25 status to SSR and make notices available in ORS, with exception cases routed for field-office action.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS explicitly calls FFAP the Title XVI warrant system.</data></node><node id="APP_FFSCF"><data key="node_entity_id">APP_FFSCF</data><data key="node_entity_type">application</data><data key="node_canonical_name">Fugitive Felon SSA Control File</data><data key="node_acronym">FFSCF</data><data key="node_domain">Program Integrity / Fugitive Felon</data><data key="node_description">Warrant-control database and processing application used to record, match, monitor, route, and disposition fugitive-felon and probation/parole warrant information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS continues to document FFSCF functions; no hosting or platform inference is made.</data></node><node id="APP_FIS"><data key="node_entity_id">APP_FIS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Federated Identity System</data><data key="node_acronym">FIS</data><data key="node_domain">Identity / Authentication</data><data key="node_description">SSA identity system identified in FY2026 modernization plans as the target of identity-assurance modernization across service channels.</data><data key="node_observed_status">observed_modernization_target</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">FY2026 budget confirms the system and modernization target but does not establish detailed current production topology.</data></node><node id="APP_FIVR"><data key="node_entity_id">APP_FIVR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Financial Interactive Voice Response System</data><data key="node_acronym">FIVR</data><data key="node_domain">Finance / Administrative Payments / Vendor Services</data><data key="node_description">Automated self-service telephone system providing vendors direct electronic access to administrative payment information and current payment-processing activity.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA says FIVR is available 24 hours a day. Public sources do not identify its backend database or application stack.</data></node><node id="APP_FOIAONLINE"><data key="node_entity_id">APP_FOIAONLINE</data><data key="node_entity_type">application</data><data key="node_canonical_name">FOIAonline</data><data key="node_acronym">FOIAonline</data><data key="node_domain">FOIA / Privacy / Public Records</data><data key="node_description">Browser-based FOIA processing application that SSA's current FOIA About page says the agency transitioned to in 2017 and uses to capture and process FOIA requests.</data><data key="node_observed_status">current_documentation_conflict</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Current SSA Request/Reports pages identify FOIAXpress/PAL and 2023-2025 raw data as FOIAXpress, while the current About page still says FOIAonline processes all requests. Atlas preserves the conflict and does not infer whether FOIAonline remains an internal layer or the About page is stale.</data></node><node id="APP_FOIAXPRESS_PAL"><data key="node_entity_id">APP_FOIAXPRESS_PAL</data><data key="node_entity_type">public_portal</data><data key="node_canonical_name">FOIAXpress Public Access Link</data><data key="node_acronym">PAL</data><data key="node_domain">FOIA / Privacy / Public Records</data><data key="node_description">SSA public online portal for submitting and tracking Freedom of Information Act requests, including requests for deceased individuals' SS-5 and Numident records.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA FOIA pages direct requesters to securefoia.ssa.gov. Current PAL supports Login.gov and ID.me sign-in and also displays a legacy ROME option; no underlying vendor or processing database is inferred.</data></node><node id="APP_FONS"><data key="node_entity_id">APP_FONS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Field Office Notice Software</data><data key="node_acronym">FONS</data><data key="node_domain">Notices / Customer Communications</data><data key="node_description">SSA software used to prepare manual notices, including Title VIII SVB notices.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Retained in current POMS references; exact platform lifecycle not independently verified.</data></node><node id="APP_FORM_DATA_EXTRACTION"><data key="node_entity_id">APP_FORM_DATA_EXTRACTION</data><data key="node_entity_type">application</data><data key="node_canonical_name">Intelligent Document Processing - Forms Classification and Data Extraction</data><data key="node_acronym">Form Data Extraction</data><data key="node_domain">Evidence &amp; Documents / AI</data><data key="node_description">Computer-vision capability that classifies forms and extracts printed and handwritten fields; extracted fields are exposed in JSON to downstream systems through APIs or queues.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2021-01-02</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_FRATS"><data key="node_entity_id">APP_FRATS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Fugitive Felon Reporting and Tracking System</data><data key="node_acronym">FRATS</data><data key="node_domain">Program Integrity / Fugitive Felon</data><data key="node_description">Reporting and tracking system that houses fugitive data submitted by reporters and warrant agencies, controls agreement expiration dates, and maintains address/contact data for reporter and warrant-agency identifiers.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-662. Address/contact data described by the catalog are for RIDs/WAIDs, not evidence of beneficiary residence.</data></node><node id="APP_FTD"><data key="node_entity_id">APP_FTD</data><data key="node_entity_type">application</data><data key="node_canonical_name">Foreign Travel Data Application</data><data key="node_acronym">FTD</data><data key="node_domain">Title XVI / Program Integrity / External Travel Data</data><data key="node_description">SSA application that provides direct query access to DHS Arrival and Departure Information System travel data for specified SSI workloads.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS states FTD is available from the SSI Claims Actions page in CCE. As of the current POMS, FTD is not yet available for RSDI claims.</data></node><node id="APP_GARNISH_NOTICE"><data key="node_entity_id">APP_GARNISH_NOTICE</data><data key="node_entity_type">notice_processing_system</data><data key="node_canonical_name">Garnishment Notice System</data><data key="node_domain">Notices / Garnishment</data><data key="node_description">Automated notice system that uses Garnishment DB2 and MBR data and passes notice information to Customer Communications Management.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Source documents architecture beginning in 2020; current garnishment POMS continues to reference automated notices.</data></node><node id="APP_GENAI_ANALYTICS"><data key="node_entity_id">APP_GENAI_ANALYTICS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Generative AI for Analytic Insights</data><data key="node_domain">Customer Service / Analytics</data><data key="node_description">Generative-AI use case analyzing National 800 Number and field-office call transcripts plus IVR logs for caller intent, resolution, and topic insights.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2023-09-30</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_GENERAL_USE_CHATBOT"><data key="node_entity_id">APP_GENERAL_USE_CHATBOT</data><data key="node_entity_type">application</data><data key="node_canonical_name">General Use Chatbot</data><data key="node_domain">Enterprise AI / Productivity</data><data key="node_description">Pilot Microsoft M365 Copilot Chat capability for routine content, analysis, suggestions, and image generation.</data><data key="node_observed_status">pilot</data><data key="node_observed_as_of">2025-08-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_GSO"><data key="node_entity_id">APP_GSO</data><data key="node_entity_type">application</data><data key="node_canonical_name">Government to Government Services Online</data><data key="node_acronym">GSO</data><data key="node_domain">External Data Exchange / Government Reporting</data><data key="node_description">SSA online portal allowing approved government organizations to report and share data with SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current services include vital records, prison/fugitive, federal, sheltered-workshop and foreign-death reporting.</data></node><node id="APP_HACPS"><data key="node_entity_id">APP_HACPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Hearings and Appeals Case Processing System</data><data key="node_acronym">HACPS</data><data key="node_domain">Hearings &amp; Appeals</data><data key="node_description">National hearings case-processing application used for hearing case management, receipt, workup, scheduling, fiscal actions and case closure.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">GAO and current HALLEX confirm active use; legacy CPMS still coexists for some workloads.</data></node><node id="APP_HACPS_INVOICE"><data key="node_entity_id">APP_HACPS_INVOICE</data><data key="node_entity_type">application</data><data key="node_canonical_name">HACPS Invoice Portal</data><data key="node_domain">Hearings / Expert Invoicing</data><data key="node_description">Portal for medical experts, vocational experts and verbatim hearing reporters to view call orders and submit invoices electronically.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_HDOP_POWERAPP"><data key="node_entity_id">APP_HDOP_POWERAPP</data><data key="node_entity_type">application</data><data key="node_canonical_name">High Dollar Overpayment Application</data><data key="node_acronym">HDOP Power App</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">HDOP Power App used to provide RQ/GAP reviewers the signed SSA-635 form during proposed high-dollar waiver approval review; platform, database and retention unspecified.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_HEART"><data key="node_entity_id">APP_HEART</data><data key="node_entity_type">application</data><data key="node_canonical_name">Hearing Recording and Transcriptions</data><data key="node_acronym">HeaRT</data><data key="node_domain">Hearings / Recording</data><data key="node_description">Software-only hearing recording and transcription system announced for nationwide rollout in 2025.</data><data key="node_observed_status">nationwide_rollout_announced</data><data key="node_observed_as_of">2025-03-17</data><data key="node_confidence">5</data><data key="node_notes">SSA announced expected nationwide completion by March 17, 2025; no later first-party status page was located in this pass.</data></node><node id="APP_HRS"><data key="node_entity_id">APP_HRS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Human Resources System</data><data key="node_acronym">HRS</data><data key="node_domain">Administrative / HR</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2017-09-15.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2017-09-15</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_HR_CHATBOT"><data key="node_entity_id">APP_HR_CHATBOT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Human Resource Chatbot</data><data key="node_acronym">HR Chatbot</data><data key="node_domain">Human Resources / Policy</data><data key="node_description">Generative-AI chatbot grounded in SSA personnel policy and related HR documents for HR staff policy research and response support.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2025-04-30</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_I3368"><data key="node_entity_id">APP_I3368</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Adult Disability Report</data><data key="node_acronym">i3368</data><data key="node_domain">Disability / Internet Intake</data><data key="node_description">Online adult disability report used with initial adult disability claims.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current IDR table of contents includes i3368; no hosting stack inferred.</data></node><node id="APP_I3368PRO"><data key="node_entity_id">APP_I3368PRO</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Adult Disability and Work History Report - Professional</data><data key="node_acronym">i3368PRO</data><data key="node_domain">Disability / Internet Intake</data><data key="node_description">Professional-user version of the Internet Adult Disability and Work History Report for disability representatives and community organizations assisting adult disability claimants.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA Developers Support currently lists i-3368PRO as available. Current POMS documents its February 2005 production launch.</data></node><node id="APP_I3441"><data key="node_entity_id">APP_I3441</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Disability Report - Appeal</data><data key="node_acronym">i3441</data><data key="node_domain">Disability / Appeals Intake</data><data key="node_description">Online disability appeal report used with iAppeals.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current IDR and iAppeals POMS continue to reference i3441.</data></node><node id="APP_I3820"><data key="node_entity_id">APP_I3820</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Child Disability Report</data><data key="node_acronym">i3820</data><data key="node_domain">Disability / Internet Intake</data><data key="node_description">Standalone online child disability report for Title XVI child disability claims.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current IDR table of contents includes i3820.</data></node><node id="APP_I454"><data key="node_entity_id">APP_I454</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Continuing Disability Review Report</data><data key="node_acronym">i454</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">Online medical CDR application for eligible adult Title II, Title XVI, and concurrent beneficiaries/recipients without a representative payee; accessed behind my Social Security.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current live POMS names the application i454. The public Forms catalog separately routes SSA-454-BK online submission through Upload Documents; the Atlas does not merge those two channels.</data></node><node id="APP_IACCOMMODATE"><data key="node_entity_id">APP_IACCOMMODATE</data><data key="node_entity_type">application</data><data key="node_canonical_name">iAccommodate</data><data key="node_acronym">iAccommodate</data><data key="node_domain">Accessibility / Customer Service</data><data key="node_description">Application used to record and refer non-standard accommodation requests to Reasonable Accommodation staff in Human Resources.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says it is found on IMAIN under Person Information (Identity, Contact, Accommodation). POMS revised 2026-10-01 also says the application must not be used to record accommodations for individuals without SSNs or individuals with a date of death on Numident; this limitation is specific to the iAccommodate recording workflow.</data></node><node id="APP_IAPPEALS"><data key="node_entity_id">APP_IAPPEALS</data><data key="node_entity_type">application</data><data key="node_canonical_name">iAppeals</data><data key="node_acronym">iAppeals</data><data key="node_domain">Appeals</data><data key="node_description">SSA online appeals service for electronically filing disability reconsideration and hearing requests, with i561/i501/i3441 components and i520 for Appeals Council review; current POMS documents downstream WMI, MCS/MSSICS, EDCS, and ORS processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA appeals guidance identifies iAppeals i520 as the preferred Appeals Council request-for-review method.</data></node><node id="APP_IAPPT"><data key="node_entity_id">APP_IAPPT</data><data key="node_entity_type">application</data><data key="node_canonical_name">iAppointment</data><data key="node_acronym">iAppt</data><data key="node_domain">Customer Service / Appointments</data><data key="node_description">Online appointment-scheduling tool reached from iClaim after specified verification failures; schedules telephone or in-office field-office appointments through eLAS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS states iClaim is the only entry point. iAppt data creates an unverified eLAS appointment/protective filing and does not itself update CLIENT or correct the Numident before verification.</data></node><node id="APP_ICER"><data key="node_entity_id">APP_ICER</data><data key="node_entity_type">application</data><data key="node_canonical_name">Informational/Certified Earnings Record</data><data key="node_acronym">ICER</data><data key="node_domain">Earnings</data><data key="node_description">Earnings-record query/source named in current field-office adjudication instructions.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_ICERS"><data key="node_entity_id">APP_ICERS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Informational/Certified Earnings Record System</data><data key="node_acronym">ICERS</data><data key="node_domain">Earnings / Railroad / Disability</data><data key="node_description">SSA system referenced by current railroad-disability policy for reviewing railroad earnings and determining whether RRB medical evidence is available.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public policy does not disclose physical database technology or persistence beyond the documented system/work-control references.</data></node><node id="APP_ICF_T16"><data key="node_entity_id">APP_ICF_T16</data><data key="node_entity_type">application</data><data key="node_canonical_name">Title XVI Interactive Computation Facility</data><data key="node_acronym">ICF</data><data key="node_domain">Title XVI / Computations</data><data key="node_description">Interactive computation facility for Title XVI eligibility and payment calculations, referenced through current POMS and SSA main-menu procedures.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">4</data><data key="node_notes">Current POMS batch still references the Title XVI facility, but much detailed screen documentation is old; distinguish from Title II ICF.</data></node><node id="APP_ICF_T2"><data key="node_entity_id">APP_ICF_T2</data><data key="node_entity_type">application</data><data key="node_canonical_name">Title II Interactive Computations Facility</data><data key="node_acronym">ICF</data><data key="node_domain">Title II / WC-PDB Offset</data><data key="node_description">Interactive computation facility for workers' compensation/public disability benefit offset computations and notices.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2025-03-25</data><data key="node_confidence">5</data><data key="node_notes">Distinguish from any other ICF acronym uses.</data></node><node id="APP_ICLAIM"><data key="node_entity_id">APP_ICLAIM</data><data key="node_entity_type">application</data><data key="node_canonical_name">iClaim</data><data key="node_acronym">iClaim</data><data key="node_domain">Title II / Internet Claims</data><data key="node_description">SSA Internet benefit-application service that precedes the Internet Adult Disability Report path.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current disability POMS requires an iClaim before an i3368; only the disability-path role is asserted here.</data></node><node id="APP_ICOR"><data key="node_entity_id">APP_ICOR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Item Correction</data><data key="node_acronym">ICOR</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">Earnings correction application/process used to correct an individual number holder Master Earnings File record.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS describes Item Correction (ICOR) as an Earnings Modernization system used to correct MEF records; EMOD ICOR terminology appears in current earnings-correction instructions.</data></node><node id="APP_ICP"><data key="node_entity_id">APP_ICP</data><data key="node_entity_type">notice_processing_system</data><data key="node_canonical_name">Interactive Communication Processing</data><data key="node_acronym">ICP</data><data key="node_domain">Notices / Manual Processing</data><data key="node_description">SSA tool used by processing-center staff to manually prepare notices when an automated notice cannot be generated.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS explicitly directs manual Garnishment notices to ICP and states there is no ICP interface for Garnishment system notices.</data></node><node id="APP_IDMS_DIS"><data key="node_entity_id">APP_IDMS_DIS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Integrated Disability Management System</data><data key="node_acronym">IDMS</data><data key="node_domain">Disability</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2017-02-13.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_IMAGEN"><data key="node_entity_id">APP_IMAGEN</data><data key="node_entity_type">application</data><data key="node_canonical_name">Intelligent Medical-Language Analysis Generation</data><data key="node_acronym">IMAGEN</data><data key="node_domain">Disability / Decision Support</data><data key="node_description">Machine-learning/predictive-analytics decision-support tool helping examiners review medical evidence against SSA disability policy.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2025-06-26</data><data key="node_confidence">5</data><data key="node_notes">GAO reports it helped resolve about 265,000 disability cases in FY2024.</data></node><node id="APP_IMAIN"><data key="node_entity_id">APP_IMAIN</data><data key="node_entity_type">application</data><data key="node_canonical_name">I-Main</data><data key="node_acronym">I-Main</data><data key="node_domain">Claims / Immigration Verification</data><data key="node_description">SSA access route identified in POMS for claims personnel to access SAVE.</data><data key="node_observed_status">observed_current_access_path</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Public POMS does not expose protocol, implementation stack, or ownership boundary.</data></node><node id="APP_IMRC"><data key="node_entity_id">APP_IMRC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Medicare Replacement Card</data><data key="node_domain">Medicare / Digital Service</data><data key="node_description">Online application through which Medicare beneficiaries can request a replacement Medicare card.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA Open Data updated 2026-04-10 describes current Internet/Online Medicare Replacement Card processing and data collection.</data></node><node id="APP_INFORM"><data key="node_entity_id">APP_INFORM</data><data key="node_entity_type">application</data><data key="node_canonical_name">inForm</data><data key="node_acronym">inForm</data><data key="node_domain">Enterprise Forms / Internal Service</data><data key="node_description">SSA internal electronic forms application/library used by technicians to open and complete forms such as SSA-632-BK and SSA-8102.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS uses both “Inform” and “inForm” wording. No backend, vendor, or hosting architecture is inferred.</data></node><node id="APP_INSIGHT"><data key="node_entity_id">APP_INSIGHT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Insight</data><data key="node_domain">Hearings &amp; Appeals / Decision Support</data><data key="node_description">Machine-learning decision-support web application for hearings and appeals adjudicators that analyzes disability decisions and case data and raises quality flags.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2017-10-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_IQF"><data key="node_entity_id">APP_IQF</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Internet Query Facility</data><data key="node_acronym">IQF</data><data key="node_domain">Disability / Internet Intake</data><data key="node_description">Set of field-office mainframe queries used to inspect and control Internet Disability Reports in the Internet Report Database.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Procedure is older but remains in the current 2026 IDR subchapter table of contents.</data></node><node id="APP_IRCS"><data key="node_entity_id">APP_IRCS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Incarceration Reporting and Control System</data><data key="node_acronym">IRCS</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">Automated screens, queries, and database maintaining correctional/mental institution, reporter, agreement, report, alert, and incentive-payment information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data></node><node id="APP_IRES"><data key="node_entity_id">APP_IRES</data><data key="node_entity_type">application</data><data key="node_canonical_name">Integrated Registration Services</data><data key="node_acronym">IRES</data><data key="node_domain">Identity / Employer Services</data><data key="node_description">SSA Internet registration/access-control application historically supporting BSO and external service roles; current EWRWS Terms of Service still requires an IRES account holder credential for existing EWRWS users.</data><data key="node_observed_status">observed_residual_current_for_ewrws</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA's FY2025 Congressional Justification said SSA intended to retire IRES and migrate services to a modern identity framework. Current 2026-linked EWRWS terms still reference IRES, indicating at least a residual dependency for EWRWS. Do not generalize this to all BSO services, which now use Login.gov/ID.me.</data></node><node id="APP_IRMAA"><data key="node_entity_id">APP_IRMAA</data><data key="node_entity_type">application</data><data key="node_canonical_name">IRMAA Processing System</data><data key="node_acronym">IRMAA</data><data key="node_domain">Medicare / IRMAA</data><data key="node_description">SSA processing environment referenced in current policy as the IRMAA system and IRMAA screens for income-related monthly adjustment amount determinations.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public policy establishes the processing system/screens but not database technology, hosting, or system boundary below the user-interface level.</data></node><node id="APP_IRON"><data key="node_entity_id">APP_IRON</data><data key="node_entity_type">application</data><data key="node_canonical_name">Image Retrieval Online</data><data key="node_acronym">IRON</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">System used to retrieve paper SS-5 applications and SS-5 microprints for Numident correction review.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies IRON as a source for prior SS-5 records.</data></node><node id="APP_IRPA"><data key="node_entity_id">APP_IRPA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Representative Payee Accounting</data><data key="node_acronym">iRPA</data><data key="node_domain">Representative Payee / Digital Service</data><data key="node_description">Internet facility allowing eligible representative payees with a current accounting request to submit the accounting report online.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-04-18</data><data key="node_confidence">5</data><data key="node_notes">Current POMS continues to identify iRPA as an online accounting channel.</data></node><node id="APP_IRPP"><data key="node_entity_id">APP_IRPP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Representative Payee Portal</data><data key="node_acronym">iRPP</data><data key="node_domain">Representative Payee / Digital Service</data><data key="node_description">Central my Social Security gateway for individual representative payees to manage beneficiary business including annual accounting and wage reporting.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_ISNO"><data key="node_entity_id">APP_ISNO</data><data key="node_entity_type">application</data><data key="node_canonical_name">Intranet Special Notice Option Application</data><data key="node_acronym">iSNO</data><data key="node_domain">Notices / Accessibility</data><data key="node_description">Application used to record and query requested Special Notice Options and related contact information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents mini-path access from MCS, MSSICS and RPS plus access from ARPS and CHIP.</data></node><node id="APP_ISSNRC"><data key="node_entity_id">APP_ISSNRC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Social Security Number Replacement Card</data><data key="node_acronym">iSSNRC</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Current logical/public online replacement-card service family. SSA Open Data continues to report iSSNRC front-end activity while prior SSA evidence shows authenticated replacement-card functionality integrated into oSSNAP effective January 31, 2026.</data><data key="node_observed_status">observed_current_logical_service_integrated_into_oSSNAP</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Public-facing iSSNRC screens were removed and functionality integrated into oSSNAP. Run 35 preserves both facts: current SSA Open Data continues the iSSNRC logical/reporting label, while previously validated evidence shows functionality integrated into oSSNAP. This does not prove a separate current backend.</data></node><node id="APP_ITOPSS"><data key="node_entity_id">APP_ITOPSS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Ticket Operation Provider Support System</data><data key="node_acronym">iTOPSS</data><data key="node_domain">Ticket to Work / Work Incentives</data><data key="node_description">SSA management information system used to facilitate and record Ticket to Work business functions, including assignments, provider payments and timely-progress reviews.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_IT_INVESTMENT_MGMT_TOOL"><data key="node_entity_id">APP_IT_INVESTMENT_MGMT_TOOL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Investment Management Tool</data><data key="node_domain">Enterprise IT Governance / Portfolio Management</data><data key="node_description">SSA tool used to track IT investments, risks, contingency and mitigation plans, resolutions, and investment-management data.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">OIG names the tool but does not disclose product/vendor, hosting, database, or implementation architecture.</data></node><node id="APP_IWMI"><data key="node_entity_id">APP_IWMI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Workload Management Information</data><data key="node_acronym">iWMI</data><data key="node_domain">Disability / Workload Management</data><data key="node_description">Workload-list system that notifies field offices of submitted Internet Disability Reports requiring action.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current IDR subchapter retains iWMI and 2026 batch instructions continue to reference it.</data></node><node id="APP_LAWS"><data key="node_entity_id">APP_LAWS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Legal Automated Workflow System</data><data key="node_acronym">LAWS</data><data key="node_domain">Legal / Workload Management</data><data key="node_description">eDIB subsystem described as managing workloads in the Office of the General Counsel.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">No claim of current production status beyond the 2018 PIA.</data></node><node id="APP_LOSS_REPORTING_TOOL"><data key="node_entity_id">APP_LOSS_REPORTING_TOOL</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSA Loss Reporting Tool</data><data key="node_acronym">LRT</data><data key="node_domain">Privacy / IRS Data</data><data key="node_description">SSA internal tool for managers to report suspected or confirmed federal tax information loss or improper disclosure under incident response procedure.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Only a named internal reporting tool is documented; software product, transport, storage and retention unknown.</data></node><node id="APP_LSAS"><data key="node_entity_id">APP_LSAS</data><data key="node_entity_type">application</data><data key="node_canonical_name">LENEL Security Access System</data><data key="node_acronym">LSAS</data><data key="node_domain">Physical Security</data><data key="node_description">Access-control implementation documented under PACS for many SSA sites; validates credential/PIN authorization and records or alarms unauthorized access.</data><data key="node_observed_status">historically_documented_smacs_component; current_implementation_unconfirmed</data><data key="node_observed_as_of">2013-09-30</data><data key="node_confidence">3</data><data key="node_notes">No inference is made about the current Lenel product version, hosting, or footprint.</data></node><node id="APP_M2M"><data key="node_entity_id">APP_M2M</data><data key="node_entity_type">application</data><data key="node_canonical_name">Manager-to-Manager Web Application</data><data key="node_acronym">M2M</data><data key="node_domain">SSA Internal Communications</data><data key="node_description">Two-way web application used by managers to initiate and manage priority interoffice inquiries on critical beneficiary cases.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">OIG audited M2M controls and usage; no hosting or data-store details are inferred.</data></node><node id="APP_MACADE"><data key="node_entity_id">APP_MACADE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Manual Adjustment Credit and Award Data Entry</data><data key="node_acronym">MACADE</data><data key="node_domain">Title II / Claims &amp; Post-entitlement</data><data key="node_description">Manual data-entry system used for Title II denials and other actions when normal systems processing is unavailable.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-04-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_MADCAP"><data key="node_entity_id">APP_MADCAP</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Manual Adjustment, Credit and Award Process</data><data key="node_acronym">MADCAP</data><data key="node_domain">Title II / Claims &amp; Post-entitlement</data><data key="node_description">Title II manual adjustment/credit/award processing and notice function.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-07-28</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_MADCAP_NOTICE_PRINT"><data key="node_entity_id">APP_MADCAP_NOTICE_PRINT</data><data key="node_entity_type">notice_processing_system</data><data key="node_canonical_name">MADCAP Beneficiary Notice Print Program</data><data key="node_acronym">MADCAP</data><data key="node_domain">Title II / Notices</data><data key="node_description">Beneficiary notice print program documented in the current POMS subchapter for Manual Adjustment, Credit and Award Process notices.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Logical notice-print capability is validated. No separate runtime, hosting, database, or deployment boundary is inferred beyond the POMS-described program.</data></node><node id="APP_MAINFRAME_CODE_ASSIST"><data key="node_entity_id">APP_MAINFRAME_CODE_ASSIST</data><data key="node_entity_type">application</data><data key="node_canonical_name">Mainframe Code Modernization Assistant</data><data key="node_domain">Mainframe / Modernization</data><data key="node_description">Pre-deployment generative-AI coding assistant for mainframe modernization; SSA lists IBM watsonx Code Assistant and Broadcom Code for Z.</data><data key="node_observed_status">pre_deployment</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_MAMPSC_SSA4510"><data key="node_entity_id">APP_MAMPSC_SSA4510</data><data key="node_entity_type">application</data><data key="node_canonical_name">MAMPSC Data Input Web Application</data><data key="node_acronym">SSA-4510</data><data key="node_domain">Title II / Payments / Stop Payment</data><data key="node_description">Mid-America Program Service Center Data Input Web application used by processing centers to input Title II F-stop actions; current POMS also calls its stop-payment screen the SSA-4510 Stop Payment Request Input Form.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Application/runtime technology, hosting, persistence, and transport to Treasury are not disclosed in public POMS.</data></node><node id="APP_MAPS"><data key="node_entity_id">APP_MAPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Medicare Application Processing System</data><data key="node_acronym">MAPS</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">SSA application for Medicare Part D Extra Help applications, verification, determinations, changes, and workload processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_MBR_SELECTIONS_GROUP"><data key="node_entity_id">APP_MBR_SELECTIONS_GROUP</data><data key="node_entity_type">subsystem</data><data key="node_canonical_name">MBR Selections Group</data><data key="node_acronym">MBR Selections</data><data key="node_domain">Title II / MBR Processing</data><data key="node_description">Subsystem group documented as updating specific data based on cost-of-living calculations, adjustments, and special-format run requests.</data><data key="node_observed_status">documented_2017_current_status_unconfirmed</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes">PIA says Master Beneficiary Rate, but context is MBR; canonical name normalized to common MBR acronym without changing source wording in evidence.</data></node><node id="APP_MBR_UPDATE_GROUP"><data key="node_entity_id">APP_MBR_UPDATE_GROUP</data><data key="node_entity_type">subsystem</data><data key="node_canonical_name">MBR Update Group</data><data key="node_acronym">MBR Update</data><data key="node_domain">Title II / MBR Processing</data><data key="node_description">2017 subsystem documented as containing Title II beneficiary payment history since 1984, validating claims/post-entitlement actions, maintaining data, and transmitting records to Treasury.</data><data key="node_observed_status">documented_2017_current_status_unconfirmed</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes">Historical subsystem-group architecture; do not infer a single current physical database distinct from MBR.</data></node><node id="APP_MCAS_COST"><data key="node_entity_id">APP_MCAS_COST</data><data key="node_entity_type">application</data><data key="node_canonical_name">Managerial Cost Analysis System</data><data key="node_acronym">MCAS</data><data key="node_domain">Enterprise Data / Cost Accounting</data><data key="node_description">Current SUMS/MCAS cost-accounting application/data asset used for essential SSA cost accounting.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">Data.gov title says Managerial Cost Analysis System while the umbrella PIA/SORN says Managerial Cost Accountability System; naming variance is preserved.</data></node><node id="APP_MCS"><data key="node_entity_id">APP_MCS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Modernized Claims System</data><data key="node_acronym">MCS</data><data key="node_domain">Title II Claims</data><data key="node_description">Title II claims-processing application.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_MDW_AI"><data key="node_entity_id">APP_MDW_AI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Modernized Development Worksheet</data><data key="node_acronym">MDW</data><data key="node_domain">Processing Center / AI</data><data key="node_description">Machine-learning/NLP capability that labels and categorizes case-development requests to reduce manual categorization workload.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2023-12-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_MEGAHIT"><data key="node_entity_id">APP_MEGAHIT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Medical Evidence Gathering and Analysis through Health Information Technology</data><data key="node_acronym">MEGAHIT</data><data key="node_domain">Disability / Health IT</data><data key="node_description">Automates requesting and receiving electronic medical evidence from Health IT partners and prepares evidence for disability examiners.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data asset plus current POMS corroborate ongoing HIT evidence-request processing.</data></node><node id="APP_MENS"><data key="node_entity_id">APP_MENS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Mass Emergency Notification System</data><data key="node_acronym">MENS</data><data key="node_domain">Administrative / Emergency</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2021-09-22.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2021-09-22</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_MFQM"><data key="node_entity_id">APP_MFQM</data><data key="node_entity_type">application</data><data key="node_canonical_name">Master File Query Menu</data><data key="node_acronym">MFQM</data><data key="node_domain">Enterprise Queries</data><data key="node_description">SSA menu layer used to access master-file and specialized query functions, including DEQY and other inquiry paths.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a query-navigation application/menu, not as a source database.</data></node><node id="APP_MICES"><data key="node_entity_id">APP_MICES</data><data key="node_entity_type">application</data><data key="node_canonical_name">Management Information Control for Earnings System</data><data key="node_acronym">MICES</data><data key="node_domain">Earnings / Workload Control</data><data key="node_description">System used to control earnings correspondence and provide earnings inquiry/quality-review management information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-07</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data inventory corroborates POMS naming and function.</data></node><node id="APP_MIDAS"><data key="node_entity_id">APP_MIDAS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Modernized Integrated Disability Adjudicative System</data><data key="node_acronym">MIDAS</data><data key="node_domain">Disability / Adjudication</data><data key="node_description">Disability case-processing system described for State DDSs and federal disability-processing components.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">No inference that this remains the current DDS platform everywhere.</data></node><node id="APP_MNUP_WEBSITE"><data key="node_entity_id">APP_MNUP_WEBSITE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Medicare Non-Utilization Project Website</data><data key="node_acronym">MNUP Website</data><data key="node_domain">Title II / Program Integrity / Work Control</data><data key="node_description">SSA intranet work-control site used to document MNUP appointment/interview activity and case status.</data><data key="node_observed_status">observed_current_policy_reference_with_older_architecture_detail</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Current 2026 POMS requires use; older still-active policy supplies historical-summary persistence detail. Hosting/database technology is not identified.</data></node><node id="APP_MONET"><data key="node_entity_id">APP_MONET</data><data key="node_entity_type">application</data><data key="node_canonical_name">Miscellaneous Online Edited Transaction System</data><data key="node_acronym">MONET</data><data key="node_domain">Title II / Post-entitlement</data><data key="node_description">Online transaction system used in current POMS to post Special Message Data to the MBR.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-01-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_MOURS"><data key="node_entity_id">APP_MOURS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Modernized Overpayment Underpayment Report System</data><data key="node_acronym">MOURS</data><data key="node_domain">Title XVI / Debt</data><data key="node_description">Tracks SSI underpayment/overpayment data and prepares aging reports for SSI program debt.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Current production status needs direct operational corroboration beyond the cataloged 2021 PIA.</data></node><node id="APP_MSSICS"><data key="node_entity_id">APP_MSSICS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Modernized Supplemental Security Income Claims System</data><data key="node_acronym">MSSICS</data><data key="node_domain">Title XVI Claims</data><data key="node_description">Legacy/modernized SSI claims-processing application still referenced in current workflows.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes">CCE also appears in current Title XVI workflows; transition mapping is a research priority.</data></node><node id="APP_MYCOA"><data key="node_entity_id">APP_MYCOA</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">my Social Security Change of Address</data><data key="node_acronym">myCOA</data><data key="node_domain">Digital Service / Title II</data><data key="node_description">Online my Social Security service for permitted address and telephone changes, with Title II processing through T2R and limited Title XVI telephone-update scope.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current policy allows Title II address/phone changes and specified Title XVI/concurrent phone changes; it does not enable Title XVI address changes through myCOA.</data></node><node id="APP_MYDD"><data key="node_entity_id">APP_MYDD</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">my Social Security Direct Deposit</data><data key="node_domain">Title II / Digital Service</data><data key="node_description">Online my Social Security service used by Social Security beneficiaries to establish or change direct-deposit information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data; not available for SSI or people without a U.S. mailing address.</data></node><node id="APP_MYRPA"><data key="node_entity_id">APP_MYRPA</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">My Representative Payee Accounting</data><data key="node_acronym">myRPA</data><data key="node_domain">Representative Payee</data><data key="node_description">Online representative-payee accounting service SSA identifies as an electronic filing option for individual payees.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS uses myRPA; 2020 SSA report provides the expansion. No equivalence with iRPA or the Representative Payee Portal is inferred.</data></node><node id="APP_MYSSA"><data key="node_entity_id">APP_MYSSA</data><data key="node_entity_type">application</data><data key="node_canonical_name">My Social Security</data><data key="node_acronym">mySSA</data><data key="node_domain">Digital Service</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2005-09-08.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-21</data><data key="node_confidence">5</data><data key="node_notes">Current SSA release documents new hearing/appeal status, forms, proffer-letter and notice functionality in my Social Security.</data></node><node id="APP_MYWR"><data key="node_entity_id">APP_MYWR</data><data key="node_entity_type">application</data><data key="node_canonical_name">myWageReport</data><data key="node_acronym">myWR</data><data key="node_domain">Earnings / Digital Service</data><data key="node_description">Online wage-reporting tool used by eligible SSI recipients and other supported users.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_NAPA"><data key="node_entity_id">APP_NAPA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Native American Precedent Application Website</data><data key="node_acronym">NAPA</data><data key="node_domain">Title XVI / Native American Income and Resources</data><data key="node_description">Former SSA repository/application for Tribal benefit precedents that was replaced by NAPR.</data><data key="node_observed_status">decommissioned_2023</data><data key="node_observed_as_of">2023-01</data><data key="node_confidence">5</data><data key="node_notes">POMS states NAPA was decommissioned as of January 2023 and its precedents were transferred to NAPR.</data></node><node id="APP_NAPR"><data key="node_entity_id">APP_NAPR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Native American Precedent and Resource Center Website</data><data key="node_acronym">NAPR</data><data key="node_domain">Title XVI / Native American Income and Resources</data><data key="node_description">SSA website used to store, search, create, approve, and publish Tribal income/resource precedents, references, and decision trees.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS links the internal NAPR site through an SSA SharePoint domain.</data></node><node id="APP_NAR"><data key="node_entity_id">APP_NAR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Nuance Application Reporting</data><data key="node_acronym">NAR</data><data key="node_domain">Customer Service / Contact Center Analytics</data><data key="node_description">Temporary Care 2020 management-information tool for customer interactions with the Nuance IVR system.</data><data key="node_observed_status">temporary_tool_current_inventory</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Catalog calls NAR temporary; current inventory presence does not establish a retirement date.</data></node><node id="APP_NCPS"><data key="node_entity_id">APP_NCPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">National Case Processing System</data><data key="node_acronym">NCPS</data><data key="node_domain">Disability / Appeals</data><data key="node_description">Current case-processing system used in DQR workflows; SSA also plans broader consolidation and appeals-level workload capabilities around NCPS.</data><data key="node_observed_status">observed_current_and_modernizing</data><data key="node_observed_as_of">2026-03-27</data><data key="node_confidence">5</data><data key="node_notes">Current operation is proven by POMS; FY2027 broader consolidation remains planned.</data></node><node id="APP_NDDSS"><data key="node_entity_id">APP_NDDSS</data><data key="node_entity_type">application</data><data key="node_canonical_name">National Disability Determination Services System</data><data key="node_acronym">NDDSS</data><data key="node_domain">DDS Disability Processing</data><data key="node_description">National DDS system referenced in current eCDR case closure/routing instructions.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_NED"><data key="node_entity_id">APP_NED</data><data key="node_entity_type">application</data><data key="node_canonical_name">Non-Entitled Debtor</data><data key="node_acronym">NED</data><data key="node_domain">Debt &amp; Overpayments</data><data key="node_description">DMS capability for debts owed by persons or entities without their own MBR/SSR entitlement record, including qualifying representative-payee debts.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Operational policy remains published; detailed scope text is older and should be revalidated if expanded releases occurred.</data></node><node id="APP_NHRP"><data key="node_entity_id">APP_NHRP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Non-Home Real Property</data><data key="node_acronym">NHRP</data><data key="node_domain">Title XVI / Resources</data><data key="node_description">Electronic non-home real property search process integrated in the SSI Claims system and using LexisNexis|Accurint to generate potential property-ownership/value leads for development.</data><data key="node_observed_status">observed_current_integrated_process</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says NHRP is integrated in the SSI Claims system (MSSICS/SSI claim) and uses LexisNexis|Accurint. Accurint output is a third-party lead that may be inaccurate or incomplete and generally requires independent verification before adverse action.</data></node><node id="APP_NOVU"><data key="node_entity_id">APP_NOVU</data><data key="node_entity_type">application</data><data key="node_canonical_name">Numident Online Verification Utility</data><data key="node_acronym">NOVU</data><data key="node_domain">Identity Verification</data><data key="node_description">Mainframe application that accesses Numident for real-time SSN verification and returns verification codes.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">Underlying description is 2016, but current VAMS metadata says NOVU requests are currently checked in VAMS.</data></node><node id="APP_NVF_FEEDS"><data key="node_entity_id">APP_NVF_FEEDS</data><data key="node_entity_type">application</data><data key="node_canonical_name">National Vendor File Data Feeds</data><data key="node_acronym">NVF Data Feeds</data><data key="node_domain">Disability / Integration</data><data key="node_description">Integration application documented as moving legacy DDS vendor data through EFI into NVF.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">2018 PIA architecture; legacy-feed relevance may have changed after national DCPS rollout.</data></node><node id="APP_NVF_MGMT"><data key="node_entity_id">APP_NVF_MGMT</data><data key="node_entity_type">application</data><data key="node_canonical_name">National Vendor File Management Application</data><data key="node_acronym">NVF Management</data><data key="node_domain">Disability / Vendor Data</data><data key="node_description">Intranet application documented as consolidating disability vendor repositories and supporting provider search.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">2018 eDIB PIA architecture; current NVF repository itself is independently corroborated.</data></node><node id="APP_OAOCPS"><data key="node_entity_id">APP_OAOCPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Office of Appellate Operations Case Processing System</data><data key="node_acronym">OAOCPS</data><data key="node_domain">Appeals Council</data><data key="node_description">Current Appeals Council/OAO case-processing application used alongside remaining ARPS workloads.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current HALLEX names OAOCPS repeatedly and documents automatic propagation from RASR.</data></node><node id="APP_OIG_ICMS"><data key="node_entity_id">APP_OIG_ICMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Investigative Case Management System</data><data key="node_acronym">ICMS</data><data key="node_domain">OIG / Investigations</data><data key="node_description">SSA OIG case-management application supporting investigative workloads; enhanced for NIBRS data and being transitioned toward cloud-hosted architecture.</data><data key="node_observed_status">observed_current_cloud_transition_underway</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes">OIG testimony uses 'Investigative Case Management System'; exact continuity with the inventoried 'National Investigative Case Management System' is modeled with a caveat. Run 21 OIG FY2027 testimony reports continuing architectural improvements to transition ICMS and line-of-business support applications to a cloud-hosted environment.</data></node><node id="APP_OPEN_GOV"><data key="node_entity_id">APP_OPEN_GOV</data><data key="node_entity_type">application</data><data key="node_canonical_name">Open Government Citizen Engagement Tool</data><data key="node_domain">Digital Engagement</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2010-04-05.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2010-04-05</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_OPICS"><data key="node_entity_id">APP_OPICS</data><data key="node_entity_type">application</data><data key="node_canonical_name">OPICS Record System</data><data key="node_acronym">OPICS</data><data key="node_domain">Public Inquiries / Correspondence</data><data key="node_description">Record system used as the entry point for measuring public-inquiry processing time through completion.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2025-07-14</data><data key="node_confidence">4</data><data key="node_notes">SSA Open Data names the OPICS record system but does not expand the acronym or publish architecture details.</data></node><node id="APP_OPTS"><data key="node_entity_id">APP_OPTS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Online Processing and Tracking System</data><data key="node_acronym">OPTS</data><data key="node_domain">Enterprise Workflow / Tracking</data><data key="node_description">SSA Online Processing and Tracking System supported through an active BPA for software and support services.</data><data key="node_observed_status">observed_current_procurement</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current USAspending BPA identifies OPTS and Salesforce license renewal/services.</data></node><node id="APP_OPWIZ"><data key="node_entity_id">APP_OPWIZ</data><data key="node_entity_type">application</data><data key="node_canonical_name">Overpayment Wizard</data><data key="node_acronym">OPWIZ</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Decision-support application referenced by current POMS for preparing explanations of Title II overpayments; available on the PCOM OQA toolbar.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS establishes operational use but not the underlying hosting or database architecture.</data></node><node id="APP_ORS"><data key="node_entity_id">APP_ORS</data><data key="node_entity_type">application</data><data key="node_canonical_name">On-line Retrieval System</data><data key="node_acronym">ORS</data><data key="node_domain">Retrieval / Queries</data><data key="node_description">Current SSA cataloged system containing data that supports retrieval and storage of documents sent to individuals on behalf of SSA.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_OSSNAP"><data key="node_entity_id">APP_OSSNAP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Online Social Security Number Application Process</data><data key="node_acronym">oSSNAP</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Public online SSN application flow supporting partially and fully automated card processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Effective Jan. 31, 2026, former iSSNRC functionality is incorporated into oSSNAP.</data></node><node id="APP_PACS"><data key="node_entity_id">APP_PACS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Physical Access Control System</data><data key="node_acronym">PACS</data><data key="node_domain">Physical Security</data><data key="node_description">SMACS subsystem documented as controlling physical access to SSA facilities through authorized credentials.</data><data key="node_observed_status">documented_component_of_currently_listed_parent; current_implementation_unconfirmed</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Detailed implementation evidence is from the 2013 PIA.</data></node><node id="APP_PAM_PHYSICAL"><data key="node_entity_id">APP_PAM_PHYSICAL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Physical Access Management</data><data key="node_acronym">PAM</data><data key="node_domain">Physical Security</data><data key="node_description">SAFE module documented for granting physical access to buildings, rooms, or access levels.</data><data key="node_observed_status">historically_documented_safe_module; current_implementation_unconfirmed</data><data key="node_observed_as_of">2013-09-30</data><data key="node_confidence">3</data><data key="node_notes">Named PAM is scoped here to SMACS/SAFE physical access.</data></node><node id="APP_PAPERLESS_PSC"><data key="node_entity_id">APP_PAPERLESS_PSC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Paperless PSC</data><data key="node_domain">Program Service Center</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2007-09-28.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_PASS_CIS"><data key="node_entity_id">APP_PASS_CIS</data><data key="node_entity_type">application</data><data key="node_canonical_name">PASS Control and Information System</data><data key="node_acronym">PASS CIS</data><data key="node_domain">Title XVI / Work Incentives</data><data key="node_description">Application PASS specialists use to initiate, develop, adjudicate, monitor, and track PASS cases.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current 2025/2026-batch POMS requires use of CIS. Exact relationship to SORN 60-0255 PASS MIS is not proven and is intentionally left unresolved.</data></node><node id="APP_PAT"><data key="node_entity_id">APP_PAT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Policy Assistance Tool</data><data key="node_acronym">PAT</data><data key="node_domain">Policy / Knowledge Management</data><data key="node_description">High-impact generative-AI pilot grounded in SSA policy data; responses provide references and links to source policy documents.</data><data key="node_observed_status">pilot_high_impact</data><data key="node_observed_as_of">2025-09-16</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_PATH"><data key="node_entity_id">APP_PATH</data><data key="node_entity_type">application</data><data key="node_canonical_name">Proactive Triage and Analysis of Hearings</data><data key="node_acronym">PATH</data><data key="node_domain">Hearings &amp; Appeals / AI</data><data key="node_description">High-impact model that flags claims with high likelihood of a favorable decision for human review and possible on-the-record hearing decisions.</data><data key="node_observed_status">deployed_high_impact</data><data key="node_observed_as_of">2024-11-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_PAYMT"><data key="node_entity_id">APP_PAYMT</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Payment System</data><data key="node_acronym">PAYMT</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Produces daily/monthly SSI payment files for Treasury and payment-certification reports.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_PCACS"><data key="node_entity_id">APP_PCACS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Processing Center Action Control System</data><data key="node_acronym">PCACS</data><data key="node_domain">Processing Center / Workload Control</data><data key="node_description">Payment-center workload-control system used for action controls, diaries, requests and folder-location work.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-07-28</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_PCS"><data key="node_entity_id">APP_PCS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Preliminary Claims System</data><data key="node_acronym">PCS</data><data key="node_domain">Benefits / Claims Intake</data><data key="node_description">Historical pre-interview application developed to help SSA employees identify potential retirement, disability, SSI, and Medicare eligibility and share collected information with claims systems.</data><data key="node_observed_status">retired_integrated_into_cce_2020</data><data key="node_observed_as_of">2022-08</data><data key="node_confidence">5</data><data key="node_notes">Development began in March 2018. Beta reached 8 field offices in July 2019 and 40 additional offices in November 2019. Beta testing ended March 2020; SSA stopped PCS development and began integrating PCS programming/functionality into CCE in September 2020.</data></node><node id="APP_PEBES"><data key="node_entity_id">APP_PEBES</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Personal Earnings and Benefits Statement Processing System</data><data key="node_acronym">PEBES</data><data key="node_domain">Social Security Statement / Earnings</data><data key="node_description">SSA processing system that selects automatic Statement recipients, procures addresses from IRS, combines MEF/requester or selection information, computes Statement data, and passes compiled output into the communications/print pipeline.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">PEBES remains SSA internal terminology for the processing system even though SSA says the public-facing form should be called the Social Security Statement.</data></node><node id="APP_PEBES_ONLINE"><data key="node_entity_id">APP_PEBES_ONLINE</data><data key="node_entity_type">application</data><data key="node_canonical_name">PEBES Online</data><data key="node_acronym">PEBES Online</data><data key="node_domain">Social Security Statement / Internal Query</data><data key="node_description">SSA query system used by field office and teleservice personnel to view benefit estimates.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS validates the query capability but does not expose its technical implementation.</data></node><node id="APP_PERSON_INFO"><data key="node_entity_id">APP_PERSON_INFO</data><data key="node_entity_type">application</data><data key="node_canonical_name">Person Information</data><data key="node_acronym">PI</data><data key="node_domain">Identity / Shared Person Data</data><data key="node_description">Web-based SSA Person Information (PI/PERSON) application that supports viewing/updating identity, death, citizenship, contact, marriage, and accommodation information and is positioned by SSA as its Customer Record database and enterprise-level authoritative customer-data source.</data><data key="node_observed_status">observed_current_customer_record_database</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current October 2026 POMS still exposes Person Information through IMAIN/iAccommodate and other workflows. FY2025 budget material calls PI the Customer Record database and enterprise authoritative customer-data source. This does not imply all program, entitlement, earnings, disability, debt, or address data is physically stored in PI; underlying database technology/hosting are not established.</data></node><node id="APP_PER_TDR_MODELS"><data key="node_entity_id">APP_PER_TDR_MODELS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Pre-Effectuation Review / Targeted Denial Review Models</data><data key="node_acronym">PER/TDR</data><data key="node_domain">Disability / Program Integrity</data><data key="node_description">High-impact models that identify claims with high likelihood of error and refer them for review; outputs probability scores through an inline mainframe process.</data><data key="node_observed_status">deployed_high_impact</data><data key="node_observed_as_of">2003-12-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_PIV"><data key="node_entity_id">APP_PIV</data><data key="node_entity_type">application</data><data key="node_canonical_name">Personal Identity Verification / HSPD-12</data><data key="node_acronym">PIV</data><data key="node_domain">Security / Identity</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2012-08-01.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status. Run 21 revalidated Personal Identity Verification/HSPD-12 in SSA current PIA catalog. Run 26: July 2026 SSA procurement for HSPD-12 PIV cardstock replacement and personalization services independently corroborates active PIV support.</data></node><node id="APP_PIV_CMS"><data key="node_entity_id">APP_PIV_CMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">PIV Card Management System</data><data key="node_acronym">CMS</data><data key="node_domain">Identity / Physical Security</data><data key="node_description">SMACS subsystem documented as managing PIV credential issuance, card production, and public key infrastructure.</data><data key="node_observed_status">documented_component_of_currently_listed_parent; current_implementation_unconfirmed</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Do not confuse this CMS acronym with Centers for Medicare &amp; Medicaid Services.</data></node><node id="APP_POLICYNET_21C"><data key="node_entity_id">APP_POLICYNET_21C</data><data key="node_entity_type">application</data><data key="node_canonical_name">21st Century PolicyNet</data><data key="node_domain">Policy / Knowledge Management</data><data key="node_description">Policy search platform whose plain-language search use case uses Apache Solr and learning-to-rank features.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2024-09-21</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_POS"><data key="node_entity_id">APP_POS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Postentitlement Online System</data><data key="node_acronym">POS</data><data key="node_domain">Title II / Post-entitlement</data><data key="node_description">Online post-entitlement system used for Title II changes, including specified entitlement conversions.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-04-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_PPC"><data key="node_entity_id">APP_PPC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Paperless Processing Center System</data><data key="node_acronym">PPC</data><data key="node_domain">Processing Center / Document Management</data><data key="node_description">Electronic imaging and work-management system used in SSA payment/processing centers to manage work and scanned program documents.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Often referred to simply as Paperless. Public sources do not establish its current hosting stack or repository technology.</data></node><node id="APP_PTMI"><data key="node_entity_id">APP_PTMI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Prisoner Tracking Management Information System</data><data key="node_acronym">PTMI</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">Management information system used to monitor PUPS pending workloads and produce field-office pending-record listings.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="APP_PUPS"><data key="node_entity_id">APP_PUPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Prisoner Update Processing System</data><data key="node_acronym">PUPS</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">System supporting prisoner reporting, suspensions and incentive-payment processing.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_QAS"><data key="node_entity_id">APP_QAS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Quality Assurance System</data><data key="node_acronym">QAS</data><data key="node_domain">Quality / Oversight</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2018-12-17.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2018-12-17</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_QCHECK"><data key="node_entity_id">APP_QCHECK</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Query Check</data><data key="node_acronym">QCHECK</data><data key="node_domain">Hearings / Query Aggregation</data><data key="node_description">OHO-referenced query utility that includes access to MDW, FACT, SSID and Customer Service Record information.</data><data key="node_observed_status">observed_current_hallex_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">HALLEX page remains available and names QCHECK. Because the same page also names retired CPMS, QCHECK is retained as a current policy reference while exact runtime status/implementation remains to be independently confirmed.</data></node><node id="APP_QDD_MODEL"><data key="node_entity_id">APP_QDD_MODEL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Quick Disability Determinations Model</data><data key="node_acronym">QDD Model</data><data key="node_domain">Disability / Triage</data><data key="node_description">High-impact predictive model that scores initial disability applications for likely favorable outcomes and medical-evidence availability to support expedited DDS processing.</data><data key="node_observed_status">deployed_high_impact</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary. Current SSA QDD materials observed 2026-10-03 say SSA continues to use QDD nationally and refine the predictive model; POMS continues to identify QDD cases via the predictive model in EDCS.</data></node><node id="APP_QRCPS"><data key="node_entity_id">APP_QRCPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Quality Review Case Processing System</data><data key="node_acronym">QRCPS</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">SSA quality-review case processing system used by Office of Quality Review field sites and supporting current DQR/MAQR workflows.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes">FY2025 budget states it replaced legacy DICARS and DQR systems by September 2023.</data></node><node id="APP_R105_LONGEVITY_VISUALIZER"><data key="node_entity_id">APP_R105_LONGEVITY_VISUALIZER</data><data key="node_entity_type">public_analysis_software</data><data key="node_canonical_name">SSA Longevity Visualizer Software</data><data key="node_domain">Actuarial &amp; Statistical Data</data><data key="node_description">Publicly distributed Windows-only standalone visualizer released May 2016, revised May 13, 2016; operates on OACT cohort mortality/life tables for single/cohort/joint survival analysis.</data><data key="node_observed_status">historical_public_software_listing</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA still lists 2016 installer on website; not proof of modern maintenance or live server.</data></node><node id="APP_RACEETH"><data key="node_entity_id">APP_RACEETH</data><data key="node_entity_type">application</data><data key="node_canonical_name">Race Ethnicity Collection System</data><data key="node_domain">Customer Data</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2009-11-18.</data><data key="node_observed_status">observed_current_sorn_2025</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN 60-0104 confirms an electronic RECS holding SSN, race/ethnicity and data-source indicator records. SORN says information is also located in additional cloud-based locations for business-continuity purposes; this does not establish primary production hosting.</data></node><node id="APP_RASR"><data key="node_entity_id">APP_RASR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Registration, Appointment, and Services for Representatives</data><data key="node_acronym">RASR</data><data key="node_domain">Representation</data><data key="node_description">Application for representative appointments and related information; current hearing/appeals systems receive propagated updates from RASR.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_RCOR"><data key="node_entity_id">APP_RCOR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Report Correction</data><data key="node_acronym">RCOR</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">Automated employer-report adjustment process for MEF and the Suspense File.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Detailed POMS description is from 2019; no claim that implementation is unchanged.</data></node><node id="APP_RCS"><data key="node_entity_id">APP_RCS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Registration and Customer Support</data><data key="node_acronym">RCS</data><data key="node_domain">Identity / Digital Customer Support</data><data key="node_description">SSA application documented for managing customer registration/support and standard eServices access blocks.</data><data key="node_observed_status">documented_2021_standard_block_management_current_status_unconfirmed</data><data key="node_observed_as_of">2021-05-05</data><data key="node_confidence">4</data><data key="node_notes">2021 instructions explicitly reference existing RCS policy for standard block/unblock actions. Current 2026 electronic blocks remain documented, but the current application name/platform has not been independently revalidated.</data></node><node id="APP_REACT"><data key="node_entity_id">APP_REACT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Returned Check Action Program</data><data key="node_acronym">REACT</data><data key="node_domain">Payments / Returned Checks</data><data key="node_description">SSA program/system used to process returned benefit checks and limited-payability credits and corrections.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-16</data><data key="node_confidence">5</data></node><node id="APP_RECOOP"><data key="node_entity_id">APP_RECOOP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Recovery and Collection of Overpayments Process</data><data key="node_acronym">RECOOP</data><data key="node_domain">Debt &amp; Collections</data><data key="node_description">DMS billing and follow-up subsystem controlling Title II and Title XVI debts not recoverable through current benefit offset.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS repeatedly identifies RECOOP as active billing/follow-up system and automated CPR selector.</data></node><node id="APP_REP_AVAIL_PORTAL"><data key="node_entity_id">APP_REP_AVAIL_PORTAL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Representative Availability Portal</data><data key="node_acronym">RAP</data><data key="node_domain">Hearings / Scheduling</data><data key="node_description">Web portal for representatives to submit hearing availability under the Enhanced Representative Availability Process.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Reached through my Social Security credentialing; portal moved to national availability for January 2026 target scheduling month.</data></node><node id="APP_REP_CONDUCT_CLAIMS"><data key="node_entity_id">APP_REP_CONDUCT_CLAIMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Representative Conduct Claims</data><data key="node_domain">Representation / Program Integrity</data><data key="node_description">Application named by SSA as a repository for information concerning disqualified and suspended representatives and non-recognized persons.</data><data key="node_observed_status">listed_in_current_pia_catalog; implementation_detail_from_2021_pia</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">The project remains in SSA's current PIA catalog; the application/repository detail is explicitly documented in the 2021 PIA.</data></node><node id="APP_RET_EST"><data key="node_entity_id">APP_RET_EST</data><data key="node_entity_type">application</data><data key="node_canonical_name">Retirement Estimator</data><data key="node_domain">Digital Service / Retirement</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2007-02-28.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2007-02-28</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_ROAR"><data key="node_entity_id">APP_ROAR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Recovery of Overpayments, Accounting and Reporting</data><data key="node_acronym">ROAR</data><data key="node_domain">Debt &amp; Overpayments</data><data key="node_description">Title II overpayment establishment, recovery and accounting subsystem within SSA debt management architecture.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">Current POMS uses ROAR for Title II debt selection, installment updates, SERS debt display and cross-program recovery.</data></node><node id="APP_ROQS"><data key="node_entity_id">APP_ROQS</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Paperless Read Only Query System</data><data key="node_acronym">ROQS</data><data key="node_domain">Processing Center / Paperless</data><data key="node_description">Read-only paperless query source referenced in current processing-center workflows.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-05-13</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_RPMA"><data key="node_entity_id">APP_RPMA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Representative Payee Monitoring Application</data><data key="node_acronym">RPMA</data><data key="node_domain">Representative Payee / Oversight</data><data key="node_description">Application used to annotate and track representative payees subject to expanded monitoring.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2025-03-25</data><data key="node_confidence">4</data><data key="node_notes">Current POMS refers to RPMA when terminating a payee subject to expanded monitoring.</data></node><node id="APP_RPMT"><data key="node_entity_id">APP_RPMT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Representative Payee Monitoring Tool</data><data key="node_acronym">RPMT</data><data key="node_domain">Representative Payee / Oversight</data><data key="node_description">Monitoring tool that automatically identifies fee-for-service payees due for periodic three-year representative-payee review.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">POMS description is from 2023; current P&amp;A review program independently remains active.</data></node><node id="APP_RPS"><data key="node_entity_id">APP_RPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Representative Payee System</data><data key="node_acronym">RPS</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">Representative-payee system referenced by current FFSCF POMS as a warrant-matching target and recipient of actionable warrant files.</data><data key="node_observed_status">documented_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Kept separate from eRPS because the public source does not establish whether RPS and eRPS are the same technical component.</data></node><node id="APP_RSDI_ACCT"><data key="node_entity_id">APP_RSDI_ACCT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Retirement, Survivors, Disability Insurance Accounting System</data><data key="node_domain">Title II / Accounting</data><data key="node_description">SSA accounting application that accumulates accounting-control, payment-certification, trust-fund, and statistical totals for Title II benefit payment processing.</data><data key="node_observed_status">listed_in_current_pia_catalog_architecture_documented_2007</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status. Detailed payment/accounting architecture is documented in the 2007 PIA; current physical implementation and interfaces are not inferred unchanged.</data></node><node id="APP_RZWIZ"><data key="node_entity_id">APP_RZWIZ</data><data key="node_entity_type">application</data><data key="node_canonical_name">Redetermination Wizard</data><data key="node_acronym">RZwiz</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">Interview-support tool that retrieves and consolidates SSI, earnings and new-hire queries for redeterminations, limited issues and wage-related diary interviews.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">TN 105 (09-26) requires RZwiz in current SSI redetermination workflows.</data></node><node id="APP_SAFE"><data key="node_entity_id">APP_SAFE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Security Automated Features and Enhancements</data><data key="node_acronym">SAFE</data><data key="node_domain">Physical Security</data><data key="node_description">SMACS web-tool suite supporting compliance/risk assessments, passes, physical access, parking, incident reporting, and related physical-security workflows.</data><data key="node_observed_status">documented_component_of_currently_listed_parent; current_implementation_unconfirmed</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Detailed implementation evidence is from the 2013 PIA.</data></node><node id="APP_SERS"><data key="node_entity_id">APP_SERS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Social Security Electronic Remittance System</data><data key="node_acronym">SERS</data><data key="node_domain">Debt &amp; Remittances</data><data key="node_description">FO electronic payment solution using check scanners to process checks and money orders for certain programmatic debts, conserved funds, misused funds and fees.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_SEXTANT"><data key="node_entity_id">APP_SEXTANT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Sextant Contact Center Analytics</data><data key="node_acronym">Sextant</data><data key="node_domain">Customer Service / Contact Center Analytics</data><data key="node_description">Care 2020 reporting system providing real-time and historical N8NN management information about customer and agent interactions.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data inventory directly identifies Sextant as an N8NN reporting system.</data></node><node id="APP_SMACS"><data key="node_entity_id">APP_SMACS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Security Management Access Control System</data><data key="node_acronym">SMACS</data><data key="node_domain">Security / Access</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2013-09-30.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status. Run 21 revalidated SMACS in SSA current PIA catalog; component implementation details remain bounded by the 2013 PIA.</data></node><node id="APP_SOCIALMEDIA"><data key="node_entity_id">APP_SOCIALMEDIA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Social Media Third-Party Websites and Applications System</data><data key="node_domain">Communications</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2011-09-13.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2011-09-13</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_SOLQ"><data key="node_entity_id">APP_SOLQ</data><data key="node_entity_type">application</data><data key="node_canonical_name">State Online Query</data><data key="node_acronym">SOLQ</data><data key="node_domain">External Data Exchange / State Services</data><data key="node_description">Real-time online State data-exchange implementation that provides SSN verification and Title II/Title XVI benefit data; current POMS distinguishes SOLQ as typically mainframe-based from the web-based SOLQ-I application.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Modeled separately from the pre-existing combined SOLQ/SOLQ-I exchange-product record to expose the documented mainframe-oriented implementation. No underlying host, transaction manager, database, or network protocol is inferred.</data></node><node id="APP_SOLQI"><data key="node_entity_id">APP_SOLQI</data><data key="node_entity_type">application</data><data key="node_canonical_name">State Online Query Internet</data><data key="node_acronym">SOLQ-I</data><data key="node_domain">External Data Exchange / State Services</data><data key="node_description">Internet application allowing authorized state agencies real-time SSN verification and, when permitted, Title II and Title XVI retrieval.</data><data key="node_observed_status">observed_current_service</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Current SSA support pages still expose SOLQ-I; detailed developer page was last modified in 2013.</data></node><node id="APP_SPS"><data key="node_entity_id">APP_SPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Single Payment System</data><data key="node_acronym">SPS</data><data key="node_domain">Title II / Payments</data><data key="node_description">System used for appointed-representative fee payments and other Title II payments that cannot be made through the current Title II System.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_SRDBAR"><data key="node_entity_id">APP_SRDBAR</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Suspense Reinstate Daily Batch Adjustment and Reinstate System</data><data key="node_acronym">SRDBAR</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">Batch adjustment/reinstatement system involved in processing Item Correction earnings adjustments and generating rejects requiring manual correction.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS revised 2025 documents SRDBAR rejects and downstream control.</data></node><node id="APP_SS5_REPRINTS"><data key="node_entity_id">APP_SS5_REPRINTS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SS-5 Reprints</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Program used to retrieve prior SS-5 records for enumeration correction work.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Links are available in SSNAP according to current POMS.</data></node><node id="APP_SSA93_QR_WEB"><data key="node_entity_id">APP_SSA93_QR_WEB</data><data key="node_entity_type">web_application</data><data key="node_canonical_name">SSA-93 Quality Review Website</data><data key="node_acronym">SSA-93 website</data><data key="node_domain">SSI / Quality Review / Work Control</data><data key="node_description">Internal quality-review website used to make SSA-93 feedback available, capture field-office responses/comments, signal completion and support regional monitoring.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2025-08-11</data><data key="node_confidence">5</data><data key="node_notes">Public policy does not establish whether this website is a module of QRCPS or a separate physical platform.</data></node><node id="APP_SSALERTS"><data key="node_entity_id">APP_SSALERTS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSAlerts</data><data key="node_acronym">SSAlerts</data><data key="node_domain">Operations / Alerts / Payments</data><data key="node_description">SSA alert surface used by field, regional, teleservice, and processing-center staff to view mass-loss information after a determination is posted.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy establishes use for mass-loss communications; hosting and implementation technology are not identified.</data></node><node id="APP_SSAMWR"><data key="node_entity_id">APP_SSAMWR</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSA Mobile Wage Reporting</data><data key="node_acronym">SSAMWR</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">Mobile application for reporting prior-month wages to SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_SSASY"><data key="node_entity_id">APP_SSASY</data><data key="node_entity_type">application</data><data key="node_canonical_name">Social Security Streamlined Acquisition System</data><data key="node_acronym">SSASy</data><data key="node_domain">Procurement / Acquisition Management</data><data key="node_description">SSA acquisition system that the Office of Acquisition and Grants currently states it operates.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Public source establishes current operation but does not disclose product, hosting, database, interfaces, or implementation stack.</data></node><node id="APP_SSBS_PHONE"><data key="node_entity_id">APP_SSBS_PHONE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Replacement Social Security Benefit Statement (SSA-1099/1042S) Automated Telephone Application</data><data key="node_acronym">SSBS Automated Telephone</data><data key="node_domain">Telephone / Tax Statements</data><data key="node_description">Automated National 800 Number application for eligible beneficiaries to request replacement SSA-1099/SSA-1042S statements using automated phone service.</data><data key="node_observed_status">observed_current_service</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current 2025 SSA public guidance confirms the automated-phone replacement service remains available; detailed authentication design comes from the PIA.</data></node><node id="APP_SSIMWV"><data key="node_entity_id">APP_SSIMWV</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Monthly Wage Verification</data><data key="node_acronym">SSIMWV</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">Intranet wage-verification application used by employees to process pay-stub wage reports.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directs staff to use SSIMWV whenever possible.</data></node><node id="APP_SSIRM"><data key="node_entity_id">APP_SSIRM</data><data key="node_entity_type">application</data><data key="node_canonical_name">Supplemental Security Income Record Maintenance System</data><data key="node_domain">Title XVI / SSI</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2021-03-25.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_SSITMS"><data key="node_entity_id">APP_SSITMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Supplemental Security Income Trust Monitoring System</data><data key="node_acronym">SSITMS</data><data key="node_domain">Title XVI / Resources / Trusts</data><data key="node_description">Internal SSA website used to submit, review, track, and communicate SSI trust resource determinations and related review decisions.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents active SSITMS workflows; hosting/runtime/database technology is not publicly established.</data></node><node id="APP_SSITWR"><data key="node_entity_id">APP_SSITWR</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Telephone Wage Reporting</data><data key="node_acronym">SSITWR</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">Automated telephone wage-reporting channel that updates SSI wage information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_SSI_CLAIMS_LOGICAL"><data key="node_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="node_entity_type">application_family</data><data key="node_canonical_name">SSI Claims System</data><data key="node_domain">Title XVI Claims</data><data key="node_description">Logical Title XVI claims-system boundary named in current POMS, including a Vehicle page that links employees to J.D. Power Values Online.</data><data key="node_observed_status">observed_current_logical_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">4</data><data key="node_notes">Do not infer that this POMS label is a physically separate application from MSSICS, CCE, or other Title XVI components; the public source does not establish that mapping.</data></node><node id="APP_SSI_CMS_NH_INTERFACE"><data key="node_entity_id">APP_SSI_CMS_NH_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/CMS Nursing Home Admissions Interface System</data><data key="node_acronym">CMS Nursing Home Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Compares CMS records with SSI records to identify unreported nursing home admissions.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_CODO"><data key="node_entity_id">APP_SSI_CODO</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Central Office/District Office Communications</data><data key="node_acronym">SSI CO/DO</data><data key="node_domain">Title XVI / Operations</data><data key="node_description">Transmits formatted SSI alerts, rejections, exceptions, diaries, query responses and follow-up listings.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_COMPUTE"><data key="node_entity_id">APP_SSI_COMPUTE</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Computations Subsystem</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Calculates monthly SSI/SVB payment amounts and balances overpayment/underpayment errors.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_DAILY_EDITS"><data key="node_entity_id">APP_SSI_DAILY_EDITS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Daily Edits (IC/PE)</data><data key="node_acronym">IC/PE</data><data key="node_domain">Title XVI / Processing</data><data key="node_description">Edits/formats internal and external data into SSR update transactions and routes rejected transactions for resolution.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_DHS_ICE_INTERFACE"><data key="node_entity_id">APP_SSI_DHS_ICE_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/DHS Immigration and Customs Enforcement and Deportation Interface System</data><data key="node_acronym">SSI/DHS ICE Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Compares DHS records with SSI records to identify individuals potentially ineligible because of immigration status.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_DOD_INTERFACE"><data key="node_entity_id">APP_SSI_DOD_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/Department of Defense Interface System</data><data key="node_acronym">SSI/DOD Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Sends finder files to DOD, receives military payment data, and formats the data into alerts.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_DOL_BLB_INTERFACE"><data key="node_entity_id">APP_SSI_DOL_BLB_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/Department of Labor Black Lung Part B Interface System</data><data key="node_acronym">SSI/DOL Black Lung Part B Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Inputs Black Lung data and builds income transactions used to post Black Lung income to SSR and MSSICS.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_EPATH"><data key="node_entity_id">APP_SSI_EPATH</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI ePath</data><data key="node_acronym">SSI ePath</data><data key="node_domain">Title XVI / Field Operations</data><data key="node_description">Intranet application that guides employees through collection of SSI changes.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_EXCEPTION"><data key="node_entity_id">APP_SSI_EXCEPTION</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Exception Control System</data><data key="node_domain">Title XVI / Processing</data><data key="node_description">Processes exceptions from initial-claim update transactions and tracks IC data until adjudication.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_FINVERIFY"><data key="node_entity_id">APP_SSI_FINVERIFY</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Financial Verification System</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Processes Treasury input, creates SSI update transactions and exception reports for certification analysts.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_FOLDERCTRL"><data key="node_entity_id">APP_SSI_FOLDERCTRL</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Folder Control System</data><data key="node_domain">Title XVI / Records</data><data key="node_description">Tracks physical SSI claim-folder location, inactivation, destruction and referral.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_GROUPTOTALS"><data key="node_entity_id">APP_SSI_GROUPTOTALS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Group Totals</data><data key="node_domain">Title XVI / Accounting</data><data key="node_description">Tracks and controls accounting and payment information posted to the SSR.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_HOME"><data key="node_entity_id">APP_SSI_HOME</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Home</data><data key="node_domain">Title XVI / Field Operations</data><data key="node_description">Intranet portal providing links to SSI intranet applications.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_IC_UPDATE"><data key="node_entity_id">APP_SSI_IC_UPDATE</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Initial Claim Update System</data><data key="node_acronym">SSI IC Update</data><data key="node_domain">Title XVI / Initial Claims</data><data key="node_description">Processes initial-claim update transactions to establish SSRs for new claims.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_INDEX"><data key="node_entity_id">APP_SSI_INDEX</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Index System</data><data key="node_domain">Title XVI / Data</data><data key="node_description">Creates index records for SSNs and Claim Account Numbers on the SSR.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_IRS_P1099_INTERFACE"><data key="node_entity_id">APP_SSI_IRS_P1099_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/IRS Pension and 1099 Interface System</data><data key="node_acronym">SSI/IRS Pension &amp; 1099 Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Receives pension and Form 1099 data from IRS.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_MBR_INTERFACE"><data key="node_entity_id">APP_SSI_MBR_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/Master Beneficiary Record Interface System</data><data key="node_acronym">SSI/MBR Interface</data><data key="node_domain">Title XVI / Title II Integration</data><data key="node_description">Inputs, edits, and posts Title II income and Title XVIII entitlement to SSR and MSSICS.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_MEF_INTERFACE"><data key="node_entity_id">APP_SSI_MEF_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/Master Earnings File Interface System</data><data key="node_acronym">SSI/MEF Interface</data><data key="node_domain">Title XVI / Earnings Integration</data><data key="node_description">Inputs MEF data and builds transactions used to post alerts to SSR.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_NOTICES"><data key="node_entity_id">APP_SSI_NOTICES</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Notices</data><data key="node_domain">Title XVI / Notices</data><data key="node_description">Creates files for SSI notices and alternative-format outputs; also supports telephone-call processing.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_OCSE_INTERFACE"><data key="node_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/Office of Child Support Enforcement Interface System</data><data key="node_acronym">SSI/OCSE Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Inputs wage and unemployment data and builds transactions used to post alerts to SSR.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_OPM_INTERFACE"><data key="node_entity_id">APP_SSI_OPM_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/Office of Personnel Management Interface System</data><data key="node_acronym">SSI/OPM Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Inputs civil service data and builds income transactions used to post civil service income to SSR and MSSICS.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_PAYHIST_CORR"><data key="node_entity_id">APP_SSI_PAYHIST_CORR</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Payment History Corrections</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Online application for correcting Treasury items that failed to post to the SSR; sends items to SSI Financial Verification nightly.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_PE_UPDATE"><data key="node_entity_id">APP_SSI_PE_UPDATE</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Post Eligibility Update System</data><data key="node_acronym">SSI PE Update</data><data key="node_domain">Title XVI / Post-Eligibility</data><data key="node_description">Updates and validates SSRs using post-eligibility transactions from SSI subsystems.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_PREPOST"><data key="node_entity_id">APP_SSI_PREPOST</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Pre/Post Update Operations System</data><data key="node_domain">Title XVI / Processing</data><data key="node_description">Creates files for initial-claim and post-eligibility update subsystems to update SSRs.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_REDET"><data key="node_entity_id">APP_SSI_REDET</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Redeterminations</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">Selects a subset of SSI recipients for periodic eligibility/payment review.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Current redetermination processing is independently corroborated by 2026 POMS.</data></node><node id="APP_SSI_RMA"><data key="node_entity_id">APP_SSI_RMA</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Retrospective Monthly Program</data><data key="node_acronym">RMA</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Program identified by current POMS as an option for computing an Emergency Advance Payment amount before the payment is established in MSSICS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS names the SSI Retrospective Monthly (RMA) program but does not disclose its runtime platform or interfaces.</data></node><node id="APP_SSI_RRB_INTERFACE"><data key="node_entity_id">APP_SSI_RRB_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/Railroad Retirement Board Interface System</data><data key="node_acronym">SSI/RRB Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Inputs RRB data and builds income transactions used to post RRB income to SSR and MSSICS.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_RZ_MODEL"><data key="node_entity_id">APP_SSI_RZ_MODEL</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Redetermination Model</data><data key="node_acronym">SSIRZ</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">High-impact model that prioritizes SSI redetermination cases based on expected overpayment likelihood and amount.</data><data key="node_observed_status">deployed_high_impact</data><data key="node_observed_as_of">1999-01-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_SSI_SDX_SYSTEM"><data key="node_entity_id">APP_SSI_SDX_SYSTEM</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI State Data Exchange System</data><data key="node_acronym">SSI SDX System</data><data key="node_domain">Title XVI / State Exchange</data><data key="node_description">Provides States with SSI eligibility, payment, and demographic data about claimants and recipients.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSI_TREASURY"><data key="node_entity_id">APP_SSI_TREASURY</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Treasury System</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Reads the monthly SSR Master and distributes payment-related change records to SDX and Daily/Monthly FAX.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="APP_SSI_VA_INTERFACE"><data key="node_entity_id">APP_SSI_VA_INTERFACE</data><data key="node_entity_type">interface_system</data><data key="node_canonical_name">SSI/Veterans Administration Interface System</data><data key="node_acronym">SSI/VA Interface</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">Inputs veterans data and builds income transactions used to post veterans income to SSR and MSSICS.</data><data key="node_observed_status">documented_2021_current_status_unconfirmed</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Named SSIRMS subsystem in 2021 PIA. Existing current exchange products are linked separately where authoritative evidence supports the functional continuity.</data></node><node id="APP_SSNAP"><data key="node_entity_id">APP_SSNAP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Social Security Number Application Process</data><data key="node_acronym">SSNAP</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">SSA application/process used to take, pend, complete and correct SSN card applications.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS repeatedly directs technicians to SSNAP.</data></node><node id="APP_SSNEC"><data key="node_entity_id">APP_SSNEC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Social Security Number Establishment and Correction System</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2007-09-27.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Current SSA PIA catalog still lists SSNEC among Systems, Applications, and Projects. The detailed architecture PIA is dated 2007; current component boundaries are therefore not inferred. SORN 60-0058 continues to govern the enumeration/SSN application record environment.</data></node><node id="APP_SSNVS"><data key="node_entity_id">APP_SSNVS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Social Security Number Verification Service</data><data key="node_acronym">SSNVS</data><data key="node_domain">Employer / Earnings</data><data key="node_description">Employer service for verifying current or former employee names and SSNs for wage-reporting purposes, with immediate screen verification and large batch-file processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA public service; online and file-upload modes.</data></node><node id="APP_SSN_NAME_VALID"><data key="node_entity_id">APP_SSN_NAME_VALID</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Social Security Number Name Validation System</data><data key="node_domain">Earnings / Identity Verification</data><data key="node_description">SSA Numident verification system that validates wage and self-employment reports, routes unmatched wage information to the Earnings Suspense File, and later reprocesses suspended wage reports.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">OIG also calls this the SSN Name Validation System. Do not confuse it with the employer-facing Social Security Number Verification Service (SSNVS).</data></node><node id="APP_SSOARS"><data key="node_entity_id">APP_SSOARS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Social Security Online Accounting and Reporting System</data><data key="node_acronym">SSOARS</data><data key="node_domain">Finance / Accounting</data><data key="node_description">SSA official book-of-record accounting system; records agency financial transactions and processes administrative payments and collections.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status. Current 2026 Open Data inventory independently confirms present SSOARS function; an in-progress USAspending task order provides current database/OS support evidence.</data></node><node id="APP_SSOARS_FIS"><data key="node_entity_id">APP_SSOARS_FIS</data><data key="node_entity_type">subsystem</data><data key="node_canonical_name">SSOARS Financial Information System</data><data key="node_acronym">SSOARS FIS</data><data key="node_domain">Finance / Accounting</data><data key="node_description">Financial Information System component named within SSOARS in the 2020 PIA.</data><data key="node_observed_status">documented_2020_current_status_unconfirmed</data><data key="node_observed_as_of">2020-05-19</data><data key="node_confidence">5</data><data key="node_notes">Component name documented; detailed current function/technology not separately described.</data></node><node id="APP_SSOARS_SOA"><data key="node_entity_id">APP_SSOARS_SOA</data><data key="node_entity_type">subsystem</data><data key="node_canonical_name">SSOARS Service-Oriented Architecture</data><data key="node_acronym">SSOARS SOA</data><data key="node_domain">Finance / Integration</data><data key="node_description">Web-services/service-oriented architecture component named within SSOARS in the 2020 PIA.</data><data key="node_observed_status">documented_2020_current_status_unconfirmed</data><data key="node_observed_as_of">2020-05-19</data><data key="node_confidence">5</data><data key="node_notes">2025 AFR still identifies Service Oriented Architecture Suite as a SSOARS component, corroborating current SOA capability but not exact 2020 component boundary.</data></node><node id="APP_SSTNG"><data key="node_entity_id">APP_SSTNG</data><data key="node_entity_type">application</data><data key="node_canonical_name">StaRZ &amp; Stripes</data><data key="node_acronym">SSTNG</data><data key="node_domain">Title XVI / Workload Management</data><data key="node_description">Field-office post-eligibility tracking application for redeterminations and limited issues.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data inventory explicitly says PEODS includes Starz &amp; Stripes data.</data></node><node id="APP_STATUTORY_BENEFIT_CONT"><data key="node_entity_id">APP_STATUTORY_BENEFIT_CONT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Statutory Benefit Continuation Software</data><data key="node_domain">Title XVI / Appeals and Payment Continuation</data><data key="node_description">SSA software used to control many payment-continuation cases formerly paid manually under Goldberg/Kelly procedures.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-07</data><data key="node_confidence">4</data><data key="node_notes">Current POMS says many N07/N08 cases previously paid manually via the GK process are controlled via this software and are in payment status C01. Technical implementation is not disclosed.</data></node><node id="APP_SUMS_TAS"><data key="node_entity_id">APP_SUMS_TAS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SUMS/MCAS Time Allocation System</data><data key="node_acronym">TAS</data><data key="node_domain">Enterprise Data / Time Allocation</data><data key="node_description">Current SUMS/MCAS application/data asset supporting time-allocation management information and consistency of MI.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-57.</data></node><node id="APP_SVS"><data key="node_entity_id">APP_SVS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Standard Verification System</data><data key="node_acronym">SVS</data><data key="node_domain">Identity Verification</data><data key="node_description">Mainframe program used by internal SSA applications to verify SSNs against Numident; includes real-time online processing.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_SVS_LITE"><data key="node_entity_id">APP_SVS_LITE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Standard Verification System Lite</data><data key="node_acronym">SVS Lite</data><data key="node_domain">Identity Verification</data><data key="node_description">Mainframe batch SSN verification variant used exclusively by OCSE with a reduced response set.</data><data key="node_observed_status">cataloged_operational_metadata</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Dataset metadata last updated in 2025; retained with lower status confidence.</data></node><node id="APP_SW_LICENSE_TRACKER"><data key="node_entity_id">APP_SW_LICENSE_TRACKER</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSA Software License Usage Tracking Application</data><data key="node_domain">IT Asset Management / Software Licensing</data><data key="node_description">SSA application reported to GAO as being developed to track software-license usage and compare licenses in use against purchase records.</data><data key="node_observed_status">development_reported_completion_unconfirmed</data><data key="node_observed_as_of">2026-02</data><data key="node_confidence">4</data><data key="node_notes">GAO says SSA expected availability by the end of FY2026, but as of the latest public GAO update cited here SSA had provided no further information. The Atlas does not infer completion or deployment.</data></node><node id="APP_T2R"><data key="node_entity_id">APP_T2R</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Title II Redesign Transaction Processing</data><data key="node_acronym">T2R</data><data key="node_domain">Title II / Post-entitlement</data><data key="node_description">Current POMS transaction-processing function for selected Title II actions, including prisoner suspension actions.</data><data key="node_observed_status">current_operational_reference_pia_boundary_retired</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes">The older Title II Redesign PIA is retired; current POMS still explicitly references T2R processing. Exact system boundary requires later validation. Current POMS still uses Title II Redesign as an operational processing label, but SSA current PIA catalog lists the historical Title II Redesign PIA as Retired / Obsolete. The Atlas therefore preserves T2R as a current logical/processing reference with physical application boundary uncertain.</data></node><node id="APP_T2_BATCH_SUBSYS"><data key="node_entity_id">APP_T2_BATCH_SUBSYS</data><data key="node_entity_type">subsystem</data><data key="node_canonical_name">Title II Batch Subsystem</data><data key="node_acronym">T2 Batch</data><data key="node_domain">Title II / Batch</data><data key="node_description">Title II subsystem documented as annotating the MBR or System Interface Records and computing benefit changes.</data><data key="node_observed_status">documented_2017_current_status_unconfirmed</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes">Historical architecture within 10-year window; current physical implementation not independently established.</data></node><node id="APP_T2_DATA_EXCHANGE_GROUP"><data key="node_entity_id">APP_T2_DATA_EXCHANGE_GROUP</data><data key="node_entity_type">subsystem</data><data key="node_canonical_name">Title II Data Exchange Subsystem</data><data key="node_acronym">T2 Data Exchange</data><data key="node_domain">Title II / External Exchange</data><data key="node_description">2017 Title II subsystem group whose applications provide data to institutions, agencies, and organizations under sharing agreements and matching programs.</data><data key="node_observed_status">documented_2017_current_status_unconfirmed</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes">Subsystem grouping, not one exchange mechanism or database.</data></node><node id="APP_T2_INFRA_SUBSYS"><data key="node_entity_id">APP_T2_INFRA_SUBSYS</data><data key="node_entity_type">subsystem</data><data key="node_canonical_name">Title II Redesign Infrastructure</data><data key="node_acronym">T2 Infrastructure</data><data key="node_domain">Title II / Claims and Post-Entitlement</data><data key="node_description">Subsystem documented in 2017 for initial claims and post-entitlement actions and for calculating transactions including debits, credits, payments, and overpayments in coordination with Treasury.</data><data key="node_observed_status">documented_2017_current_status_unconfirmed</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes">Do not equate automatically with the current logical T2R transaction-processing label; exact lineage is unresolved.</data></node><node id="APP_T2_PC_WORKLOADS"><data key="node_entity_id">APP_T2_PC_WORKLOADS</data><data key="node_entity_type">subsystem</data><data key="node_canonical_name">Title II Payment Center Workloads</data><data key="node_acronym">PC Workloads</data><data key="node_domain">Title II / Payment Centers</data><data key="node_description">Tracking, routing, and updating subsystem documented for Payment Center records.</data><data key="node_observed_status">documented_2017_current_status_unconfirmed</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes">Historical subsystem-group evidence; no current hosting or technology inferred.</data></node><node id="APP_TATTER"><data key="node_entity_id">APP_TATTER</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Terminations, Attainments, Transfers and Terminations</data><data key="node_acronym">TATTER</data><data key="node_domain">Title II / Post-entitlement</data><data key="node_description">Title II post-entitlement processing program that handles specified terminations/conversions and generates exception alerts when certain POS inputs do not process.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-05-08</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS documents TATTER exception processing.</data></node><node id="APP_TAX_LEVY_NOTICE"><data key="node_entity_id">APP_TAX_LEVY_NOTICE</data><data key="node_entity_type">notice_processing_system</data><data key="node_canonical_name">Tax Levy Notice System</data><data key="node_domain">Notices / Tax Levy</data><data key="node_description">Automated notice system documented by SSA as using Tax Levy DB2 and MBR data to notify beneficiaries and the IRS about federal tax-levy withholding.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The POMS subchapter remains current in 2025. Specific database/interface architecture is documented in a 2006 description, so current implementation details are not assumed.</data></node><node id="APP_TCVQ"><data key="node_entity_id">APP_TCVQ</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Treasury Check Verification Query</data><data key="node_acronym">TCVQ</data><data key="node_domain">Payments / Check Resolution</data><data key="node_description">SSA query system used by field offices to determine the SSN associated with an SSA check returned to a local field office after SSNs were removed from checks.</data><data key="node_observed_status">current_federal_data_catalog</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-656. Internal data source and lookup mechanics are not disclosed.</data></node><node id="APP_TDCP"><data key="node_entity_id">APP_TDCP</data><data key="node_entity_type">application</data><data key="node_canonical_name">Totalization Data Collection Program</data><data key="node_acronym">TDCP</data><data key="node_domain">Title II / International / Totalization</data><data key="node_description">SSA application used to establish and manage records for Totalization claims and foreign-agency assistance requests and to produce management information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 Romania instructions explicitly require use of TDCP; physical hosting and technology stack are not publicly established.</data></node><node id="APP_TEAMMATE_OIG"><data key="node_entity_id">APP_TEAMMATE_OIG</data><data key="node_entity_type">application</data><data key="node_canonical_name">Automated Working Papers System (TeamMate)</data><data key="node_acronym">TeamMate</data><data key="node_domain">OIG Audit Management</data><data key="node_description">Distributed OIG system for electronic audit/review planning, working-paper preparation, review, storage, and retention using commercial TeamMate software.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current catalog placement supports present listing; PIA architecture detail dates to 2005.</data></node><node id="APP_TED"><data key="node_entity_id">APP_TED</data><data key="node_entity_type">application</data><data key="node_canonical_name">Technician Experience Dashboard</data><data key="node_acronym">TED</data><data key="node_domain">Employee Experience / Customer Service</data><data key="node_description">SSA technician-facing dashboard used in customer-service workflows, including WLM access, ASC access/history and task initiation.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes">Current SSA emergency messages and POMS corroborate use.</data></node><node id="APP_THERAPY_CHATBOT"><data key="node_entity_id">APP_THERAPY_CHATBOT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Therapy Chatbot - Text-Based Mental Health Support</data><data key="node_domain">Human Resources / Employee Support</data><data key="node_description">Employee-facing AI chatbot providing confidential text-based mental-health support and escalation to live counselors when needed.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2023-09-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_TICKET_PORTAL"><data key="node_entity_id">APP_TICKET_PORTAL</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Ticket Portal</data><data key="node_acronym">Ticket Portal</data><data key="node_domain">Ticket to Work / External Provider Services</data><data key="node_description">SSA secure online system used by Employment Networks and State VR agencies to perform Ticket to Work transactions in real time.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled separately from the older APP_TTW_PORTAL because public sources reviewed do not explicitly prove object identity.</data></node><node id="APP_TIME_REFERENCE_MI"><data key="node_entity_id">APP_TIME_REFERENCE_MI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Time Reference for Management Information</data><data key="node_acronym">Time Reference MI</data><data key="node_domain">Enterprise Data / Reference Data</data><data key="node_description">Application maintaining fiscal-year and processing-year reference tables located on mainframe and data-warehouse servers.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Source identifies server classes but not specific database products or warehouse names.</data></node><node id="APP_TITLE2_PIA"><data key="node_entity_id">APP_TITLE2_PIA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Title II System</data><data key="node_domain">Title II / Entitlement</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2017-07-20.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_TITLEII_MAJOR"><data key="node_entity_id">APP_TITLEII_MAJOR</data><data key="node_entity_type">major_application</data><data key="node_canonical_name">Title II Major Application</data><data key="node_acronym">Title II</data><data key="node_domain">Title II / Enterprise Boundary</data><data key="node_description">2017 SSA PIA system boundary encompassing subsystems and applications for receiving, adjudicating, processing, paying, and servicing Title II claims and post-entitlement actions.</data><data key="node_observed_status">documented_2017_system_boundary_current_status_unconfirmed</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes">Time-scoped architecture from 2017 PIA. Current individual Title II systems are corroborated elsewhere; do not assume the full 2017 security boundary is unchanged.</data></node><node id="APP_TPIBA"><data key="node_entity_id">APP_TPIBA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Third Party Internet Social Security Benefits Application</data><data key="node_domain">Digital Service / Claims</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2008-09-08.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2008-09-08</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_TPPS"><data key="node_entity_id">APP_TPPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Third Party Payment System</data><data key="node_acronym">TPPS</data><data key="node_domain">Payments / Field Office</data><data key="node_description">System used in field offices to issue immediate payments via U.S. Debit Card after CPS transmission.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-18</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_TPS_BUYIN"><data key="node_entity_id">APP_TPS_BUYIN</data><data key="node_entity_type">application</data><data key="node_canonical_name">Third-Party System</data><data key="node_acronym">TPS</data><data key="node_domain">Medicare / State Buy-In</data><data key="node_description">SSA system identified in current POMS as receiving state buy-in status updates and subsequently updating the MBR Third-Party line.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS establishes the system role and timing but does not disclose hosting, database technology, or transport.</data></node><node id="APP_TP_RISK_MGMT"><data key="node_entity_id">APP_TP_RISK_MGMT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Third-Party Risk Management System</data><data key="node_domain">Cybersecurity / Third-Party Risk</data><data key="node_description">SSA system used to review and track third-party relationships through onboarding, contract performance, and completion.</data><data key="node_observed_status">observed_current_product_unspecified</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG page names the system but does not disclose product, vendor, hosting, database, or integrations.</data></node><node id="APP_TRAINING_MEDIA_AI"><data key="node_entity_id">APP_TRAINING_MEDIA_AI</data><data key="node_entity_type">application</data><data key="node_canonical_name">Training Audio and Video Generation</data><data key="node_domain">Human Resources / Training</data><data key="node_description">Pilot use of commercial generative-AI tools to create custom audio, video, and image content for SSA training products.</data><data key="node_observed_status">pilot</data><data key="node_observed_as_of">2025-09-08</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_TRAINING_SIMULATOR"><data key="node_entity_id">APP_TRAINING_SIMULATOR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Training Interaction Simulator</data><data key="node_domain">Human Resources / Training</data><data key="node_description">Generative-AI training tool that simulates client/coworker interactions and provides coaching feedback.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2025-06-03</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_TTW_PORTAL"><data key="node_entity_id">APP_TTW_PORTAL</data><data key="node_entity_type">application</data><data key="node_canonical_name">Ticket to Work Secure Provider Portal System</data><data key="node_domain">Ticket to Work</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2010-07-20.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2010-07-20</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="APP_UBA"><data key="node_entity_id">APP_UBA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Universal Benefit Application</data><data key="node_acronym">UBA</data><data key="node_domain">Claims / Digital Service</data><data key="node_description">SSA internet benefit application recognized in current POMS and 2026 field guidance; it is also a current modernization focus for streamlining and expanding online claims processing.</data><data key="node_observed_status">observed_current_modernization</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Do not treat UBA as having already replaced iClaim or as currently supporting every SSA program. GAO reports broader all-program coverage as SSA modernization direction, while current field guidance lists UBA alongside iClaim.</data></node><node id="APP_UIPATH_ASSISTANT_PC"><data key="node_entity_id">APP_UIPATH_ASSISTANT_PC</data><data key="node_entity_type">application</data><data key="node_canonical_name">UiPath Assistant for SSA Processing Centers</data><data key="node_domain">Infrastructure / Operations Automation</data><data key="node_description">SSA says UiPath Assistant was rolled out to processing-center users in August 2025 after final testing.</data><data key="node_observed_status">documented_deployed_2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_UMCCC"><data key="node_entity_id">APP_UMCCC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Uneffectuated Medical Cessations Clearance Control</data><data key="node_acronym">UMCCC</data><data key="node_domain">Disability / Work Control</data><data key="node_description">New York Regional website work-control application used to track administrative actions for the identified legacy UMC workload until all actions are completed and recorded to SSA systems.</data><data key="node_observed_status">observed_current_legacy_workload_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS still directs FO use; DDS lacks access. Product, hosting stack, and database are not identified.</data></node><node id="APP_UMS_MCAS"><data key="node_entity_id">APP_UMS_MCAS</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSA Unified Measurement System / Managerial Cost Accountability System</data><data key="node_acronym">UMS/MCAS</data><data key="node_domain">Performance / Cost</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2008-01-16.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 Data.gov assets explicitly use the SUMS/MCAS name for cost accounting and time allocation, while SSA still lists the umbrella PIA in its current catalog.</data></node><node id="APP_UNIFORMS"><data key="node_entity_id">APP_UNIFORMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">UniForms</data><data key="node_acronym">UniForms</data><data key="node_domain">Forms</data><data key="node_description">Web application and internal service for federal forms used by SSA; accessible through DCPS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_UPLOAD_DOCUMENTS"><data key="node_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Upload Documents</data><data key="node_acronym">Upload Documents</data><data key="node_domain">Evidence / Digital Service</data><data key="node_description">SSA digital intake service supporting technician-initiated and customer-initiated electronic submission of selected forms and evidence, including webform completion and PDF/file upload.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms links across multiple program domains route through the shared /eSubmit/upload-documents-ui/start path. FY2024 performance reporting states Upload Documents was formerly eSubmit.</data></node><node id="APP_UPS"><data key="node_entity_id">APP_UPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Unverified Prisoner System</data><data key="node_acronym">UPS</data><data key="node_domain">Program Integrity / Prisoner Identity</data><data key="node_description">System that supports manual SSN verification for inmate reports that fail automated EVS verification and can feed corrected identity information back into matching.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="APP_UPTQ"><data key="node_entity_id">APP_UPTQ</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Treasury Status Query</data><data key="node_acronym">UPTQ</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">SSA Treasury-status query used in Title XVI returned-payment and nonreceipt processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Public POMS identifies the query function but does not disclose its underlying implementation or interface to Treasury.</data></node><node id="APP_VAAT"><data key="node_entity_id">APP_VAAT</data><data key="node_entity_type">application</data><data key="node_canonical_name">Vocational Assessment Assistant Tool</data><data key="node_acronym">VAAT</data><data key="node_domain">Disability / Decision Support</data><data key="node_description">High-impact generative-AI assistant for job-code research and transferable-skills analysis, producing recommendations and structured explanations.</data><data key="node_observed_status">deployed_high_impact</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="APP_VAMS"><data key="node_entity_id">APP_VAMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Verification Account Management System</data><data key="node_acronym">VAMS</data><data key="node_domain">External Data Exchange</data><data key="node_description">Central account-management application for SSA verification and data-exchange accounts and Verification Account Numbers.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_VERINT_IMPACT360"><data key="node_entity_id">APP_VERINT_IMPACT360</data><data key="node_entity_type">application</data><data key="node_canonical_name">Verint/Impact 360</data><data key="node_acronym">Impact 360</data><data key="node_domain">Customer Service / Workforce Management</data><data key="node_description">Historical CARE 2020 workforce-optimization system storing agent activity, service observations, KPIs, and work schedules.</data><data key="node_observed_status">historical_architecture_current_operation_unverified</data><data key="node_observed_as_of">2017-12-20</data><data key="node_confidence">3</data><data key="node_notes">Official SSA Open Data record remains cataloged in 2026 but its substantive metadata was last modified in 2017. Current operation is not established.</data></node><node id="APP_VIPR"><data key="node_entity_id">APP_VIPR</data><data key="node_entity_type">application</data><data key="node_canonical_name">Visitor Intake Process Re-write</data><data key="node_acronym">VIPr</data><data key="node_domain">Field Office / Customer Service</data><data key="node_description">SSA application/data asset used to manage field-office contacts with the public and, under documented operating instructions, to display and add selected field-office appointments.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-176. Separate from the existing VIPr management-information data store.</data></node><node id="APP_VIT"><data key="node_entity_id">APP_VIT</data><data key="node_entity_type">web_application</data><data key="node_canonical_name">Vocational Information Tool</data><data key="node_acronym">VIT</data><data key="node_domain">Disability / Vocational Evidence</data><data key="node_description">Web-based information technology platform being developed to combine ORS with other reliable occupational-information sources and to house, expose, and operationalize the OIS.</data><data key="node_observed_status">in_development</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SSA states completion of VIT is required before OIS can be used in the disability program.</data></node><node id="APP_VOIP_STATION_MANAGER"><data key="node_entity_id">APP_VOIP_STATION_MANAGER</data><data key="node_entity_type">application</data><data key="node_canonical_name">VoIP Station Manager</data><data key="node_domain">Infrastructure / Telephony</data><data key="node_description">Station-management application named by the TSMI catalog record; TSMI supports its configuration, management, maintenance, and voice-message reporting.</data><data key="node_observed_status">documented_2018_currentity_unconfirmed</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">4</data><data key="node_notes">Named in an SSA catalog asset last updated in 2018. Do not infer that it survived later NGTP/Amazon Connect telephony changes.</data></node><node id="APP_VRRMS"><data key="node_entity_id">APP_VRRMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Vocational Rehabilitation Reimbursement Management System</data><data key="node_acronym">VRRMS</data><data key="node_domain">Vocational Rehabilitation / Reimbursement</data><data key="node_description">SSA management information system used to facilitate cost reimbursement payments to State VR agencies.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_W2_ONLINE_2026"><data key="node_entity_id">APP_W2_ONLINE_2026</data><data key="node_entity_type">application</data><data key="node_canonical_name">Modernized W-2/W-2C Online</data><data key="node_acronym">W-2/W-2C Online</data><data key="node_domain">Earnings / Employer</data><data key="node_description">Current BSO application for manual electronic W-2 and W-2C filing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Currently supports U.S. domestic wage reporting; territory support planned for early December 2026.</data></node><node id="APP_W2_ONLINE_PREV"><data key="node_entity_id">APP_W2_ONLINE_PREV</data><data key="node_entity_type">application</data><data key="node_canonical_name">Previous W-2/W-2c Online Application</data><data key="node_domain">Earnings / Employer</data><data key="node_description">Pre-modernization browser-based electronic W-2/W-2c filing application.</data><data key="node_observed_status">decommissioned</data><data key="node_observed_as_of">2026-09-19</data><data key="node_confidence">5</data><data key="node_notes">SSA states it was decommissioned September 19, 2026.</data></node><node id="APP_WAC"><data key="node_entity_id">APP_WAC</data><data key="node_entity_type">application</data><data key="node_canonical_name">Workload Action Center</data><data key="node_acronym">WAC</data><data key="node_domain">Representative Payee / Workload Control</data><data key="node_description">Program documented by OIG as storing and controlling Stuck Sweeper and eRPS development alerts and listing pending alerts for field offices.</data><data key="node_observed_status">observed_active_2026</data><data key="node_observed_as_of">2026-01-30</data><data key="node_confidence">5</data><data key="node_notes">January 2026 SSA instructions document WAC as an operational work queue for TAA exception claims.</data></node><node id="APP_WAIVER_DECISION_TREE"><data key="node_entity_id">APP_WAIVER_DECISION_TREE</data><data key="node_entity_type">application</data><data key="node_canonical_name">Waiver Decision Tree - Title II &amp; Title XVI</data><data key="node_domain">Debt &amp; Overpayments / Decision Support</data><data key="node_description">Interactive decision-support application referenced by SSA for selecting waiver provisions and processing steps for Title II and Title XVI overpayment waivers.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA separately publishes a PDF version; this entity represents the explicitly named Interactive Application only.</data></node><node id="APP_WEBAFS"><data key="node_entity_id">APP_WEBAFS</data><data key="node_entity_type">application</data><data key="node_canonical_name">web Attorney Fee System</data><data key="node_acronym">webAFS</data><data key="node_domain">Representation / Appeals</data><data key="node_description">OAO tracking system used for representative fee administrative review.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_WEBALJ"><data key="node_entity_id">APP_WEBALJ</data><data key="node_entity_type">application</data><data key="node_canonical_name">WebALJ</data><data key="node_acronym">WebALJ</data><data key="node_domain">Hearings &amp; Appeals / Workload Control</data><data key="node_description">Legacy/regional hearing workload mechanism used for SSI ALJ reversals whose new-case updates stopped when CPMS retired.</data><data key="node_observed_status">new_case_feed_interrupted_post_cpms_retirement</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current EM says WebALJ cannot receive new cases until a replacement data path is identified and must not be used as the controlling mechanism in the interim.</data></node><node id="APP_WEIA"><data key="node_entity_id">APP_WEIA</data><data key="node_entity_type">application</data><data key="node_canonical_name">Wage and Employment Information Authorization Application</data><data key="node_acronym">WEIA</data><data key="node_domain">Earnings / Authorization</data><data key="node_description">Application used to obtain, record and query authorization for SSA to obtain wage/employment information from payroll data providers.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="APP_WLM"><data key="node_entity_id">APP_WLM</data><data key="node_entity_type">application</data><data key="node_canonical_name">Workload Management</data><data key="node_acronym">WLM</data><data key="node_domain">Enterprise Work Management</data><data key="node_description">SSA workload-management application that places eligible appointments/work into a national queue and assigns work using technician skill and availability.</data><data key="node_observed_status">observed_limited_rollout</data><data key="node_observed_as_of">2026-08-29</data><data key="node_confidence">5</data><data key="node_notes">Current SSA emergency message documents expanded production rollout. FY2026/FY2027 budget documents use National Workload Management / National Workload Management System terminology.</data></node><node id="APP_WMS"><data key="node_entity_id">APP_WMS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Workload Management System</data><data key="node_acronym">WMS</data><data key="node_domain">Title II / Workload Control</data><data key="node_description">SSA workload-control system that provides information about Title II benefit claims currently in process and is queried for workload or diary-origin routing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS uses the full name Workload Management System and acronym WMS. It is kept separate from the newer Workload Management (WLM) product because authoritative public evidence does not establish equivalence, succession, or shared implementation.</data></node><node id="APP_WORKSMART"><data key="node_entity_id">APP_WORKSMART</data><data key="node_entity_type">application</data><data key="node_canonical_name">WorkSmart Earnings Risk Identification Tool</data><data key="node_domain">Disability / Program Integrity</data><data key="node_description">SSA tool that alerts DI cases for work continuing-disability review based on available earnings data; possible PIE data use is subject to authorization.</data><data key="node_observed_status">documented_active_fy2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">PIE utilization described conditionally in AFR; do not assert universal live data feed.</data></node><node id="APP_WORKTRACK"><data key="node_entity_id">APP_WORKTRACK</data><data key="node_entity_type">application</data><data key="node_canonical_name">WorkTrack</data><data key="node_acronym">WorkTrack</data><data key="node_domain">Evidence / Work Management</data><data key="node_description">SSA field-office work-management application receiving document work items from multiple intake channels for staff review and downstream handling.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current waiver POMS explicitly calls the application WorkTrack 2.0 and directs staff to use its “Upload a Batch” process. Modeled as work management, not a document repository.</data></node><node id="APP_WRPS"><data key="node_entity_id">APP_WRPS</data><data key="node_entity_type">application</data><data key="node_canonical_name">National Wage Reporting Processing System</data><data key="node_acronym">WRPS</data><data key="node_domain">Earnings / Employer Reporting</data><data key="node_description">System through which field offices may refer employer wage-reporting problems for processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current 2024 POMS explicitly names the system; downstream processing topology is not published in the source.</data></node><node id="APP_ZIP4_SOFTWARE"><data key="node_entity_id">APP_ZIP4_SOFTWARE</data><data key="node_entity_type">application</data><data key="node_canonical_name">ZIP +4 Software</data><data key="node_acronym">ZIP +4</data><data key="node_domain">Address / Postal Standardization</data><data key="node_description">SSA-referenced ZIP +4 software used to verify ZIP information and derive ZIP+4 and delivery-point data for address maintenance.</data><data key="node_observed_status">observed_current_policy_reference_implementation_unconfirmed</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Detailed POMS implementation description is substantively dated 2011; current product/vendor identity and runtime are not established.</data></node><node id="ARCH_BI"><data key="node_entity_id">ARCH_BI</data><data key="node_entity_type">architecture</data><data key="node_canonical_name">Business Intelligence Architecture</data><data key="node_acronym">BI Architecture</data><data key="node_domain">Enterprise Data / Business Intelligence</data><data key="node_description">SSA business-intelligence architecture explicitly referenced by the current MSHARE data asset.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">No specific vendor or physical topology is inferred.</data></node><node id="ARCH_BI_ODS_2016"><data key="node_entity_id">ARCH_BI_ODS_2016</data><data key="node_entity_type">architecture</data><data key="node_canonical_name">Business Intelligence Operational Data Stores Layer (2016)</data><data key="node_acronym">BI ODS Layer</data><data key="node_domain">Enterprise Data / Analytics</data><data key="node_description">Historical BI architecture layer in which detailed operational data was primarily stored in DB2 for tactical, operational, query, and reporting needs.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Represents an architecture layer/group of ODS assets, not a claim that SSA had one single physical ODS database.</data></node><node id="ARCH_CLOUD"><data key="node_entity_id">ARCH_CLOUD</data><data key="node_entity_type">architecture</data><data key="node_canonical_name">Cloud-Based Application Architecture</data><data key="node_acronym">Cloud</data><data key="node_domain">Technology / Architecture</data><data key="node_description">Cloud architecture explicitly documented by GAO for SSA's national DCPS2.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2026 SSA infrastructure planning explicitly describes current hybrid-cloud operations; existing system-specific cloud evidence remains separate.</data></node><node id="ARCH_HYBRID_CLOUD"><data key="node_entity_id">ARCH_HYBRID_CLOUD</data><data key="node_entity_type">architecture</data><data key="node_canonical_name">SSA Hybrid Cloud Ecosystem</data><data key="node_acronym">Hybrid Cloud</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">Current SSA infrastructure architecture in which IT Operations Management capabilities span a hybrid cloud ecosystem.</data><data key="node_observed_status">observed_current_fy2026</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2026 budget explicitly uses 'hybrid cloud ecosystem.' It does not publish a complete provider inventory or on-premises/cloud allocation.</data></node><node id="ARCH_IWS_LAN"><data key="node_entity_id">ARCH_IWS_LAN</data><data key="node_entity_type">architecture</data><data key="node_canonical_name">Intelligent Workstation / Local Area Network Architecture</data><data key="node_acronym">IWS/LAN</data><data key="node_domain">Infrastructure / Distributed Computing</data><data key="node_description">SSA distributed-computing architecture intended to replace dumb terminals with networked personal computers while retaining centralized backend databases and mainframe roles.</data><data key="node_observed_status">historical_pilot_and_deployment_1990s</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">System Zero experimentation began after 1990 design selection; 10 pilot field offices had operated IWS/LAN in day-to-day work since mid-1992.</data></node><node id="ARCH_PROGRAM_SILO_1994"><data key="node_entity_id">ARCH_PROGRAM_SILO_1994</data><data key="node_entity_type">architecture</data><data key="node_canonical_name">SSA Program-Silo Database Architecture (1994)</data><data key="node_acronym">Program-Silo DB Architecture</data><data key="node_domain">Enterprise Data / Historical</data><data key="node_description">Historical architecture in which SSA maintained separate databases for its programs, preventing employees from obtaining a whole-person view of clients.</data><data key="node_observed_status">historically_documented_1994</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">Represents an architectural condition documented by OTA, not a single physical database.</data></node><node id="ARCH_SUMS"><data key="node_entity_id">ARCH_SUMS</data><data key="node_entity_type">architecture</data><data key="node_canonical_name">SSA Unified Measurement System Standards and Architecture</data><data key="node_acronym">SUMS</data><data key="node_domain">Enterprise Data / Analytics</data><data key="node_description">Standards/architecture explicitly cited for the SSNAP management-information ODS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ARCH_ZERO_TRUST"><data key="node_entity_id">ARCH_ZERO_TRUST</data><data key="node_entity_type">architecture</data><data key="node_canonical_name">Zero Trust Architecture</data><data key="node_acronym">ZTA</data><data key="node_domain">Cybersecurity / Architecture</data><data key="node_description">Cybersecurity architecture SSA states it is expanding, with focus on High Value Assets and federal zero-trust principles.</data><data key="node_observed_status">expansion_in_progress_fy2026</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="AUTH_SAP"><data key="node_entity_id">AUTH_SAP</data><data key="node_entity_type">security_control</data><data key="node_canonical_name">Security Authentication PIN</data><data key="node_acronym">SAP</data><data key="node_domain">Identity / Telephone Authentication</data><data key="node_description">Optional PIN feature for my Social Security accountholders used to authenticate identity more quickly and securely when calling SSA; FY2027 budget states SAP is now required for certain telephone transactions including direct-deposit changes unless handled in person.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">Introduced beginning August 2025; do not infer underlying credential storage or cryptographic implementation.</data></node><node id="CAP_APP_DEV_INFRA"><data key="node_entity_id">CAP_APP_DEV_INFRA</data><data key="node_entity_type">service</data><data key="node_canonical_name">Application Development Infrastructure</data><data key="node_domain">Application Development / Infrastructure</data><data key="node_description">Enterprise-wide analysis, design, development, coding, testing, and release services supporting application development.</data><data key="node_observed_status">funded_fy2026</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Public budget describes the capability but does not publish the full toolchain, platform products, or hosting boundaries.</data></node><node id="CAP_CLICK_SIGN"><data key="node_entity_id">CAP_CLICK_SIGN</data><data key="node_entity_type">signature_capability</data><data key="node_canonical_name">Click-and-Sign Electronic Signature</data><data key="node_acronym">Click-and-Sign</data><data key="node_domain">Digital Intake / Signatures</data><data key="node_description">SSA electronic-signature capability used by claimants to sign eligible iClaim applications and selected associated forms.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes">Current POMS describes first-party mySSA authentication, the iClaim checkbox/submission action, MCS/DW01 signature documentation, and ORS storage of submitted summaries.</data></node><node id="CAP_ENTERPRISE_LOGGING"><data key="node_entity_id">CAP_ENTERPRISE_LOGGING</data><data key="node_entity_type">service</data><data key="node_canonical_name">Enterprise Logging Capabilities</data><data key="node_domain">Cybersecurity / Logging</data><data key="node_description">Agency-wide logging capability SSA states it is enhancing to support investigation and remediation of cybersecurity incidents.</data><data key="node_observed_status">enhancement_in_progress_fy2026</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Public source does not name the underlying logging/SIEM product or vendor.</data></node><node id="CAP_UPLOAD_CONVERSATIONAL"><data key="node_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">Upload Documents Conversational Forms</data><data key="node_acronym">Conversational Forms</data><data key="node_domain">Evidence / Digital Service</data><data key="node_description">Upload Documents webform mode in which standardized questions appear conditionally based on customer responses and produce the same final PDF as the corresponding paper/fillable form.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA announced first production batch for July 25, 2026. This is modeled as a feature/mode of Upload Documents, not a separate backend application.</data></node><node id="CAP_UPLOAD_EVIDENCE_MODE"><data key="node_entity_id">CAP_UPLOAD_EVIDENCE_MODE</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">Upload Documents Evidence Submission Mode</data><data key="node_domain">Evidence / Digital Intake</data><data key="node_description">Customer-initiated Upload Documents capability for selected non-original/non-certified evidence types, including disability-related evidence classifications.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Introduced June 28, 2025; original or certified evidence remains outside this electronic channel.</data></node><node id="CAP_UPLOAD_WEBFORM_MODE"><data key="node_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">Upload Documents Webform Mode</data><data key="node_domain">Digital Forms / Web Intake</data><data key="node_description">Upload Documents capability allowing selected forms to be completed as webforms rather than uploaded only as completed PDFs.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current Forms links use type=completeOnline; EM-25024 calls this the Complete Online webform option and documents static webforms.</data></node><node id="CODE_EDCS_EXR_INITIAL"><data key="node_entity_id">CODE_EDCS_EXR_INITIAL</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">EDCS Expedited Reinstatement Initial Case Level</data><data key="node_acronym">EXR Initial</data><data key="node_domain">Disability / EXR</data><data key="node_description">EDCS/eView case level identifying an initial Expedited Reinstatement case transferred to DDS.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="CODE_EDCS_EXR_RECON"><data key="node_entity_id">CODE_EDCS_EXR_RECON</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">EDCS Expedited Reinstatement Reconsideration Case Level</data><data key="node_acronym">EXR Recon</data><data key="node_domain">Disability / EXR</data><data key="node_description">EDCS/eView case level identifying an Expedited Reinstatement reconsideration case.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="CODE_EDCS_SPECIAL_A"><data key="node_entity_id">CODE_EDCS_SPECIAL_A</data><data key="node_entity_type">case_flag_type</data><data key="node_canonical_name">EDCS Special-A Flag</data><data key="node_acronym">Special-A</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">CEF/EDCS special-handling flag type used for AIDS cases.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="CODE_EDCS_SPECIAL_F"><data key="node_entity_id">CODE_EDCS_SPECIAL_F</data><data key="node_entity_type">case_flag_type</data><data key="node_canonical_name">EDCS Special-F Flag</data><data key="node_acronym">Special-F</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">CEF/EDCS special-handling flag type used for possible fraud or similar-fault cases.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="CODE_EDCS_SPECIAL_H"><data key="node_entity_id">CODE_EDCS_SPECIAL_H</data><data key="node_entity_type">case_flag_type</data><data key="node_canonical_name">EDCS Special-H Flag</data><data key="node_acronym">Special-H</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">CEF/EDCS special-handling flag type used for homicidal or potentially violent claimant cases.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="CODE_EDCS_SPECIAL_S"><data key="node_entity_id">CODE_EDCS_SPECIAL_S</data><data key="node_entity_type">case_flag_type</data><data key="node_canonical_name">EDCS Special-S Flag</data><data key="node_acronym">Special-S</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">CEF/EDCS special-handling flag type used for suicide-threat cases.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="CODE_NDDSS_CDT5"><data key="node_entity_id">CODE_NDDSS_CDT5</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">NDDSS Continuing Disability Type 5</data><data key="node_acronym">CDT=5</data><data key="node_domain">Disability / EXR</data><data key="node_description">NDDSS continuing-disability-type code that distinguishes Expedited Reinstatement from a medical CDR.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="CODE_NDDSS_TYP_CD"><data key="node_entity_id">CODE_NDDSS_TYP_CD</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">NDDSS Case Type CD</data><data key="node_acronym">TYP=CD</data><data key="node_domain">Disability / EXR</data><data key="node_description">NDDSS case-type code used when DDS receipts an Expedited Reinstatement case as a continuing-disability-review type.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="COMP_CDR_DEV_TOOLBOX"><data key="node_entity_id">COMP_CDR_DEV_TOOLBOX</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">CDR Development Toolbox</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">WAC workflow feature used by field offices when initiating a medical continuing disability review.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current live POMS names the CDR Development Toolbox within the WAC initiation workflow; hosting or implementation beyond WAC is not inferred.</data></node><node id="COMP_DIFSLA_ALERT_PROFILER"><data key="node_entity_id">COMP_DIFSLA_ALERT_PROFILER</data><data key="node_entity_type">processing_component</data><data key="node_canonical_name">DIFSLA IRS Alert Profiling Module</data><data key="node_acronym">DIFSLA Profiling Module</data><data key="node_domain">Title XVI / IRS Match / Program Integrity</data><data key="node_description">Profiling component applied after DIFSLA tolerance and exclusion screening to reduce the IRS-match alerts released to field offices for development.</data><data key="node_observed_status">observed_in_current_cma_attachment</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">The current CMA cost-benefit attachment says the module was developed by OQI and describes FY2023 operations. Public evidence does not identify implementation technology or hosting.</data></node><node id="COMP_DMA"><data key="node_entity_id">COMP_DMA</data><data key="node_entity_type">platform_component</data><data key="node_canonical_name">Document Management Architecture</data><data key="node_acronym">DMA</data><data key="node_domain">Evidence &amp; Documents</data><data key="node_description">Barcode/indexing architecture used to associate scanned/faxed documents with CEF cases and repositories.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="COMP_ERPS_WM"><data key="node_entity_id">COMP_ERPS_WM</data><data key="node_entity_type">platform_component</data><data key="node_canonical_name">eRPS Workload Management</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">eRPS workload-management capability where field offices receive specified criminal-information work issues.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current live POMS documents the function; physical deployment boundaries within eRPS are not published.</data></node><node id="COMP_STC"><data key="node_entity_id">COMP_STC</data><data key="node_entity_type">platform_component</data><data key="node_canonical_name">State Transmission/Transfer Component</data><data key="node_acronym">STC</data><data key="node_domain">External Data Exchange / State Services</data><data key="node_description">State-side transfer component used when an approved state agency cannot receive SSA data directly.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA State Agreements page requires an STC Agreement documenting data flow and safeguards.</data></node><node id="CONTRACT_KIOWARE_2026"><data key="node_entity_id">CONTRACT_KIOWARE_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA KioWare Maintenance Purchase Order 28321326P00050062</data><data key="node_acronym">28321326P00050062</data><data key="node_domain">Procurement / Field Office Technology</data><data key="node_description">FY2026 SSA purchase order for KioWare maintenance supporting the Visitor Intake Process Rewrite kiosk project.</data><data key="node_observed_status">awarded</data><data key="node_observed_as_of">2026-09-09</data><data key="node_confidence">4</data><data key="node_notes">Reported obligation $63,342 and seven offers; mirror-derived procurement evidence is intentionally lower confidence than directly retrieved SAM.gov/USAspending records.</data></node><node id="CONTRACT_SEWP_NNG15SC19B"><data key="node_entity_id">CONTRACT_SEWP_NNG15SC19B</data><data key="node_entity_type">contract_vehicle</data><data key="node_canonical_name">NASA SEWP V Contract NNG15SC19B</data><data key="node_acronym">NNG15SC19B</data><data key="node_domain">Technology Procurement</data><data key="node_description">NASA SEWP V government-wide acquisition contract used for SSA delivery orders for IBM infrastructure.</data><data key="node_observed_status">open_ordering_vehicle</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">USAspending lists ordering-period end date 2027-01-31.</data></node><node id="CONTRACT_SEWP_NNG15SC20B"><data key="node_entity_id">CONTRACT_SEWP_NNG15SC20B</data><data key="node_entity_type">contract_vehicle</data><data key="node_canonical_name">NASA SEWP V Contract NNG15SC20B</data><data key="node_acronym">NNG15SC20B</data><data key="node_domain">Procurement / Infrastructure</data><data key="node_description">NASA Solutions for Enterprise-Wide Procurement V indefinite-delivery vehicle held by Sterling Computers Corporation and used for SSA order 28321326FDX030037.</data><data key="node_observed_status">observed_current_vehicle</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Added separately from existing NNG15SC19B vehicle because this is a different SEWP V IDV.</data></node><node id="CONTRACT_SSA_28321324FDX030088"><data key="node_entity_id">CONTRACT_SSA_28321324FDX030088</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Delivery Order 28321324FDX030088</data><data key="node_acronym">28321324FDX030088</data><data key="node_domain">Infrastructure Procurement</data><data key="node_description">SSA delivery order under NASA SEWP V to procure IBM Power10 at the Second Support Center to upgrade existing IBM Power8.</data><data key="node_observed_status">completed_order</data><data key="node_observed_as_of">2024-05-11</data><data key="node_confidence">5</data><data key="node_notes">USAspending lists $248,955 obligated, start 2024-04-11, end 2024-05-11.</data></node><node id="CONTRACT_SSA_28321326FDX030016"><data key="node_entity_id">CONTRACT_SSA_28321326FDX030016</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Delivery Order 28321326FDX030016</data><data key="node_acronym">28321326FDX030016</data><data key="node_domain">Infrastructure Procurement</data><data key="node_description">SSA delivery order under NASA SEWP V for IBM Super Server appliances supporting the Second Support Center and National Support Center.</data><data key="node_observed_status">completed_order</data><data key="node_observed_as_of">2026-03-11</data><data key="node_confidence">5</data><data key="node_notes">USAspending lists $713,738 obligated, start 2026-02-09, end 2026-03-11.</data></node><node id="CON_AWS_CONNECT_2024"><data key="node_entity_id">CON_AWS_CONNECT_2024</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Amazon Connect CCaaS Task Order 28321324FA0010214</data><data key="node_acronym">28321324FA0010214</data><data key="node_domain">Procurement / Contact Center</data><data key="node_description">Task order issued under the Four Points BPA for Contact Center as a Service, Amazon Web Services Connect.</data><data key="node_observed_status">documented_in_2025_gao_record</data><data key="node_observed_as_of">2025-06-30</data><data key="node_confidence">5</data><data key="node_notes">Issued 2024-08-01 with a one-year base and one-year option according to GAO. This run does not assert whether the option was exercised or what replaced/extended it after the documented period.</data></node><node id="CON_CALL_BRANDING_2026"><data key="node_entity_id">CON_CALL_BRANDING_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Outbound Call Spoof-Proofing and Call Branding BPA Call 28321326FA0010070</data><data key="node_acronym">28321326FA0010070</data><data key="node_domain">Procurement / Telephony / Fraud Prevention</data><data key="node_description">SSA BPA call order to procure TransUnion outbound-call spoof-proofing and call-branding services under Commercial Cloud Services BPA 28321321A00040003.</data><data key="node_observed_status">observed_award_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Federal-award data mirrors report initial June 12, 2026 obligation of about $3.03M. HigherGov reports a potential value up to about $16.6M. Deployment status is not inferred.</data></node><node id="CON_CLOUD_BPA_FOUR_POINTS"><data key="node_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Commercial Cloud Services BPA 28321321A00040003</data><data key="node_acronym">28321321A00040003</data><data key="node_domain">Procurement / Cloud</data><data key="node_description">SSA blanket purchase agreement established with Four Points to provide access to commercial cloud service providers supporting public and technician-facing business services.</data><data key="node_observed_status">observed_active_during_oig_review_2026</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">Established 2020-12-22. Current October 2026 period/status is not inferred. Run 21 OIG audit states the BPA was active during the audit and documents eight call orders as of June 2026. OIG September 2026 found insufficient annual BPA best-value reviews, a scope modification beyond the originally established term, inconsistent contractor-performance monitoring, and limited quality/performance incentives; SSA agreed to five recommendations.</data></node><node id="CON_CLOUD_CO1_2021"><data key="node_entity_id">CON_CLOUD_CO1_2021</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Cloud BPA Call Order 28321321FA0010133</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">Call Order 1 under SSA Commercial Cloud Services BPA 28321321A00040003; funded the base year of the Cloud BPA.</data><data key="node_observed_status">documented_historical_call_order</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">OIG September 2026 audit documents the order and effective date 2021-04-14.</data></node><node id="CON_CLOUD_CO2_2022"><data key="node_entity_id">CON_CLOUD_CO2_2022</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Cloud BPA Call Order 28321322FA0010168</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">Call Order 2 under SSA Commercial Cloud Services BPA; funded Option Year 1.</data><data key="node_observed_status">documented_historical_call_order</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">OIG audit documents effective date 2022-04-25.</data></node><node id="CON_CLOUD_CO3_2023"><data key="node_entity_id">CON_CLOUD_CO3_2023</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Cloud BPA Call Order 28321323FA0010120</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">Call Order 3 under SSA Commercial Cloud Services BPA; funded Option Year 2.</data><data key="node_observed_status">documented_historical_call_order</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">OIG audit documents effective date 2023-04-17.</data></node><node id="CON_CLOUD_CO4_2024"><data key="node_entity_id">CON_CLOUD_CO4_2024</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Cloud BPA Call Order 28321324FA0010089</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">Call Order 4 under SSA Commercial Cloud Services BPA; funded Option Year 3 cloud services and additional software.</data><data key="node_observed_status">documented_historical_call_order</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">Public audit does not identify the additional software product.</data></node><node id="CON_CLOUD_CO6_2025"><data key="node_entity_id">CON_CLOUD_CO6_2025</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Cloud BPA Call Order 28321325FA0010110</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">Call Order 6 under SSA Commercial Cloud Services BPA; funded Option Year 4.</data><data key="node_observed_status">documented_call_order</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">OIG audit documents effective date 2025-04-21.</data></node><node id="CON_CLOUD_CO7_2026"><data key="node_entity_id">CON_CLOUD_CO7_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Cloud BPA Call Order 28321326FA0010007</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">Call Order 7 under SSA Commercial Cloud Services BPA; procured additional software.</data><data key="node_observed_status">documented_2026_call_order</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">The public audit does not identify the additional software product.</data></node><node id="CON_CLOUD_CO8_2026"><data key="node_entity_id">CON_CLOUD_CO8_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Cloud BPA Call Order 28321326FA0010026</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">Call Order 8 under SSA Commercial Cloud Services BPA; procured a data-warehouse management product capable of processing and analyzing data.</data><data key="node_observed_status">documented_2026_call_order</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">The public OIG report does not identify the product or vendor beyond the BPA contractor.</data></node><node id="CON_CREOAL_SSOARS_SERS"><data key="node_entity_id">CON_CREOAL_SSOARS_SERS</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSOARS/SERS Application Database Administration and Operating System Services Task Order 28321323FDX030012</data><data key="node_acronym">28321323FDX030012</data><data key="node_domain">Procurement / Finance Systems</data><data key="node_description">SSA delivery order for application database administration and operating system services for SSOARS and SERS.</data><data key="node_observed_status">in_progress_award</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">USAspending reports start 2022-11-15, current end 2026-11-01, potential end 2028-05-01, obligated/current award amount $10,983,335.16 and potential award amount $15,351,640.92.</data></node><node id="CON_DCPS_LEIDOS_2018"><data key="node_entity_id">CON_DCPS_LEIDOS_2018</data><data key="node_entity_type">contract</data><data key="node_canonical_name">DCPS Support Delivery Order 28321318FDS030231</data><data key="node_acronym">28321318FDS030231</data><data key="node_domain">Procurement</data><data key="node_description">Completed delivery order for contractor expertise, technical knowledge, IT support personnel and related resources for the SSA Disability Case Processing System program.</data><data key="node_observed_status">completed_award</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">USAspending reports start 2018-06-26, potential end 2022-09-28, current award about $11.2M and potential award about $142.9M.</data></node><node id="CON_DIGITAL_EVIDENCE_NOI_2026"><data key="node_entity_id">CON_DIGITAL_EVIDENCE_NOI_2026</data><data key="node_entity_type">procurement_notice</data><data key="node_canonical_name">Digital Evidence Management Notice of Intent 28321326RNOI00018</data><data key="node_acronym">28321326RNOI00018</data><data key="node_domain">Procurement / Digital Evidence</data><data key="node_description">SSA special notice announcing intent to sole-source a digital evidence management requirement.</data><data key="node_observed_status">inactive_preaward_notice</data><data key="node_observed_as_of">2026-09-25</data><data key="node_confidence">5</data><data key="node_notes">Visible SAM.gov notice does not identify the vendor/product in its description; no award is inferred.</data></node><node id="CON_DRN_2026"><data key="node_entity_id">CON_DRN_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Data Replication Network Delivery Order 28321326FDX030037</data><data key="node_acronym">28321326FDX030037</data><data key="node_domain">Procurement / Infrastructure / Disaster Recovery</data><data key="node_description">SSA delivery order under NASA SEWP V for Data Replication Network support for resilient real-time mainframe-data replication and disaster recovery.</data><data key="node_observed_status">active_award</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">USAspending shows $349,884; start 2026-06-15; end 2027-06-14.</data></node><node id="CON_FIRSTNET_BACKUP_2026"><data key="node_entity_id">CON_FIRSTNET_BACKUP_2026</data><data key="node_entity_type">procurement_notice</data><data key="node_canonical_name">Emergency Backup FirstNet Equipment Solicitation 28321326Q00000309</data><data key="node_acronym">28321326Q00000309</data><data key="node_domain">Infrastructure / Resilience</data><data key="node_description">SSA solicitation for emergency satellite-backup equipment supporting FirstNet communications at critical facilities.</data><data key="node_observed_status">solicitation_closed_no_award_observed</data><data key="node_observed_as_of">2026-09-23</data><data key="node_confidence">5</data><data key="node_notes">Pre-award procurement evidence only; no awardee is inferred.</data></node><node id="CON_GRAND_SLLAM"><data key="node_entity_id">CON_GRAND_SLLAM</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Grand SLLAM Task Order 28321320FDX030010</data><data key="node_acronym">28321320FDX030010</data><data key="node_domain">Procurement / Telecommunications</data><data key="node_description">SSA Local and Long Distance Access Management task order consolidating telephony services and locally purchased services under GSA EIS.</data><data key="node_observed_status">documented_in_2025_gao_record</data><data key="node_observed_as_of">2025-06-30</data><data key="node_confidence">5</data><data key="node_notes">Issued 2020-02-04. GAO said the most recent option year then in the record was set to end 2026-02-03; no October 2026 continuation is inferred.</data></node><node id="CON_HV_PRINTER_RFI_2026"><data key="node_entity_id">CON_HV_PRINTER_RFI_2026</data><data key="node_entity_type">procurement_notice</data><data key="node_canonical_name">High Volume Production Printers RFI 28321326RI0000036</data><data key="node_acronym">28321326RI0000036</data><data key="node_domain">Procurement / Printing Infrastructure</data><data key="node_description">SSA RFI for high-volume production printers for nationwide SSA offices, including DDS service improvement.</data><data key="node_observed_status">inactive_rfi_no_award_observed</data><data key="node_observed_as_of">2026-08-07</data><data key="node_confidence">5</data><data key="node_notes">SAM.gov notice was published 2026-07-09 and became inactive 2026-08-07; no award or selected product inferred.</data></node><node id="CON_MITRE_NETWORK_ASSESS_2026"><data key="node_entity_id">CON_MITRE_NETWORK_ASSESS_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Network Infrastructure Assessment Delivery Order 28321326FDX030085</data><data key="node_acronym">28321326FDX030085</data><data key="node_domain">Procurement / Infrastructure / Network</data><data key="node_description">SSA delivery order awarded to MITRE for an independent third-party assessment of network infrastructure and future-state recommendations.</data><data key="node_observed_status">observed_award_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Award mirror reports $725,000, period 2026-06-01 through 2027-05-31.</data></node><node id="CON_MONGODB_2026"><data key="node_entity_id">CON_MONGODB_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">MongoDB Cloud BPA Call Order 28321326FA0010219</data><data key="node_acronym">28321326FA0010219</data><data key="node_domain">Procurement / Cloud / Data Platform</data><data key="node_description">SSA BPA call order for MongoDB under Commercial Cloud Services BPA 28321321A00040003.</data><data key="node_observed_status">observed_award_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Secondary federal-award data mirrors report award date 2026-09-24, about $2.989M obligated/current award and up to about $8.94M potential value. Primary USAspending detail page was not machine-readable in this run.</data></node><node id="CON_NGTP_VERIZON"><data key="node_entity_id">CON_NGTP_VERIZON</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Next Generation Telephony Project Contract</data><data key="node_domain">Procurement / Telecommunications</data><data key="node_description">SSA contract with Verizon supporting design, implementation, testing, transition, training, operations and maintenance of NGTP.</data><data key="node_observed_status">ended_2025-03-08</data><data key="node_observed_as_of">2025-04-23</data><data key="node_confidence">5</data><data key="node_notes">OIG reports SSA paid over $160M for NGTP platform deliverables/O&amp;M/help desk and that the final option year ended 2025-03-08 with no further options exercised.</data></node><node id="CON_OPTS_ACCENTURE_BPA"><data key="node_entity_id">CON_OPTS_ACCENTURE_BPA</data><data key="node_entity_type">contract</data><data key="node_canonical_name">BPA 28321321A00040017 - OPTS Software and Support</data><data key="node_acronym">28321321A00040017</data><data key="node_domain">Procurement</data><data key="node_description">SSA blanket purchase agreement for software and support services for the Online Processing and Tracking System.</data><data key="node_observed_status">observed_open</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">USAspending shows ordering through October 31, 2026.</data></node><node id="CON_ORACLE_MAINT_2026"><data key="node_entity_id">CON_ORACLE_MAINT_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Oracle, SERS, and SSOARS Software Maintenance Delivery Order 28321326FDX030114</data><data key="node_acronym">28321326FDX030114</data><data key="node_domain">Procurement / Software Maintenance</data><data key="node_description">SSA delivery order covering Oracle database/middleware/learning and SERS/SSOARS software maintenance, awarded to Emergent, LLC.</data><data key="node_observed_status">observed_award_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Award mirror reports $3.907M, period 2026-08-18 through 2027-02-28. The bundled description does not prove that SERS or SSOARS use Oracle Database or Oracle Middleware.</data></node><node id="CON_OSEP_GIS_2025"><data key="node_entity_id">CON_OSEP_GIS_2025</data><data key="node_entity_type">contract</data><data key="node_canonical_name">OSEP GIS Development and Support Services BPA Call 28321325FA0010051</data><data key="node_acronym">28321325FA0010051</data><data key="node_domain">Procurement / Security &amp; Emergency Preparedness</data><data key="node_description">SSA BPA call for geographic information system development and support services for the Office of Security and Emergency Preparedness.</data><data key="node_observed_status">completed_award</data><data key="node_observed_as_of">2026-06-18</data><data key="node_confidence">5</data><data key="node_notes">USAspending shows start 2024-12-19, current end 2026-06-18, $1,563,373.66 obligated/current award. No specific GIS product, hosting platform, or cloud architecture is inferred.</data></node><node id="CON_PEGA_2026"><data key="node_entity_id">CON_PEGA_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Pega Re-Compete Award 28321326FDX030072</data><data key="node_acronym">28321326FDX030072</data><data key="node_domain">Procurement</data><data key="node_description">SSA award for Pega software modules, software maintenance and SaaS platform, with base period and two one-year options.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">USAspending shows $14.1525M current award amount and $50.1867M potential award amount; current end October 27, 2026 and potential end October 27, 2028.</data></node><node id="CON_PIE_IDIQ_2024"><data key="node_entity_id">CON_PIE_IDIQ_2024</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Electronic Payroll Information Exchange Contract 28321324D00060023</data><data key="node_acronym">28321324D00060023</data><data key="node_domain">Procurement</data><data key="node_description">Indefinite-delivery contract for Electronic Payroll Information Exchange services awarded to Equifax Workforce Solutions.</data><data key="node_observed_status">observed_award</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Award identity/vendor corroborated through FPDS-derived public procurement records; values should be validated against first-party award data before financial reporting.</data></node><node id="CON_PIE_TASK_2026"><data key="node_entity_id">CON_PIE_TASK_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">PIE Matched Hits Task Order 28321326FDS030081</data><data key="node_acronym">28321326FDS030081</data><data key="node_domain">Procurement</data><data key="node_description">2026-2027 delivery order for matched hits supporting Payroll Information Exchange.</data><data key="node_observed_status">observed_award</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">FPDS-derived public record reports approximately $55M and period June 1, 2026-May 31, 2027; validate directly before using financial totals.</data></node><node id="CON_SERVICENOW_BPA_2019"><data key="node_entity_id">CON_SERVICENOW_BPA_2019</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA ServiceNow Software BPA 28321319A00040024</data><data key="node_acronym">28321319A00040024</data><data key="node_domain">Procurement / IT Service Management</data><data key="node_description">Prior SSA ServiceNow software BPA referenced as the predecessor to BPA 28321325A00040016.</data><data key="node_observed_status">historical_predecessor_reference</data><data key="node_observed_as_of">2026-02-11</data><data key="node_confidence">4</data><data key="node_notes">Only the predecessor PIID and relationship are established from the current FPDS record; awardee, dates, ceiling, and detailed scope are not inferred.</data></node><node id="CON_SERVICENOW_BPA_2025"><data key="node_entity_id">CON_SERVICENOW_BPA_2025</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA ServiceNow Software FSS BPA 28321325A00040016</data><data key="node_acronym">28321325A00040016</data><data key="node_domain">Procurement / IT Service Management</data><data key="node_description">SSA single-award FSS blanket purchase agreement for ServiceNow software.</data><data key="node_observed_status">observed_active_ordering_vehicle</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">FPDS record states last date to order 2029-03-29, ceiling $97,786,140.39, and $20,665,339 obligated on orders in the cited February 2026 snapshot. Amounts are snapshot values, not asserted as October 2026 totals.</data></node><node id="CON_SONATYPE_NEXUS_2026"><data key="node_entity_id">CON_SONATYPE_NEXUS_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Sonatype Nexus Repository Renewal Delivery Order 28321326FDX030022</data><data key="node_acronym">28321326FDX030022</data><data key="node_domain">Procurement / Application Development Infrastructure</data><data key="node_description">SSA delivery order for annual renewal of Sonatype Nexus Repository software, awarded to AccessAgility LLC.</data><data key="node_observed_status">observed_award_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Award mirror reports $195,000, period 2026-04-03 through 2027-04-03, and identifies prior order 28321325FDX030060.</data></node><node id="CON_VIN_RFI_2026"><data key="node_entity_id">CON_VIN_RFI_2026</data><data key="node_entity_type">procurement_notice</data><data key="node_canonical_name">Video Integration Network RFI 28321326RI0000021</data><data key="node_acronym">28321326RI0000021</data><data key="node_domain">Procurement / Video Integration Network</data><data key="node_description">SSA request for information for a Video Integration Network requirement.</data><data key="node_observed_status">inactive_rfi_no_award_observed</data><data key="node_observed_as_of">2026-05-28</data><data key="node_confidence">5</data><data key="node_notes">Public notice supplies no architecture, product selection, awardee or contract value; none is inferred.</data></node><node id="CTRL_CDRW"><data key="node_entity_id">CTRL_CDRW</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">CDR Development Worksheet Five-Day Tickle</data><data key="node_acronym">CDRW</data><data key="node_domain">Disability / CDR / Work Control</data><data key="node_description">Five-day control placed on the CDR Development Worksheet in DCF to ensure expected MBR and/or SSR updates have posted after a CDR appeal determination.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-08-12</data><data key="node_confidence">5</data><data key="node_notes">Title II and concurrent cases can control both MBR and SSR; Title XVI controls the SSR. This is a control, not the update mechanism itself.</data></node><node id="CTRL_DECEFFECT"><data key="node_entity_id">CTRL_DECEFFECT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eWork Decision Effectuation Issue</data><data key="node_acronym">DECEFFECT</data><data key="node_domain">Disability / Work CDR / Effectuation</data><data key="node_description">eWork Development Worksheet issue used when a work-CDR decision cannot automatically update/effectuate the required Title II record action.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-14</data><data key="node_confidence">5</data><data key="node_notes">Current POMS and EM-24037 document DECEFFECT exception routing, PCACS follow-up, and MBR verification.</data></node><node id="CTRL_DIBCESS_PCACS"><data key="node_entity_id">CTRL_DIBCESS_PCACS</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DIBCESS PCACS Issue</data><data key="node_acronym">DIBCESS</data><data key="node_domain">Disability / CDR / Processing Center</data><data key="node_description">PCACS issue that field offices verify is pending when a Title II MBR CDR-appeal update does not automatically post within five days.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-08-12</data><data key="node_confidence">5</data><data key="node_notes">Public POMS identifies the issue and PCACS but does not expose the underlying background-program implementation for the issue.</data></node><node id="CTRL_ESERVICES_BLOCK"><data key="node_entity_id">CTRL_ESERVICES_BLOCK</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Electronic Services Access Block</data><data key="node_acronym">eServices Block</data><data key="node_domain">Identity / Digital Access Control</data><data key="node_description">Control that blocks a customer’s electronic access to personal information; current SSA online text says a block can prevent online and automated telephone access.</data><data key="node_observed_status">observed_current_control</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Standard block management is distinct from the temporary COVID-era elevated-block telephone removal process.</data></node><node id="CTRL_G845_DW01"><data key="node_entity_id">CTRL_G845_DW01</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">G845 DW01 Follow-Up Issue</data><data key="node_acronym">G845 DW01</data><data key="node_domain">Title II / Development Control</data><data key="node_description">MCS DW01 development issue used to control a G-845 request with a 20-federal-working-day follow-up period.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">POMS specifies the issue label G845 and a 20-day follow-up. This is a work-control artifact, not a person record.</data></node><node id="DASH_ERPC_MI"><data key="node_entity_id">DASH_ERPC_MI</data><data key="node_entity_type">dashboard</data><data key="node_canonical_name">eRPC Management Information Dashboards</data><data key="node_acronym">RPC MI Dashboards</data><data key="node_domain">Disability / Program Consultation Analytics</data><data key="node_description">Dashboards in the RPC tool used to identify trends, track counts and rates, measure activities, and monitor issues.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="DASH_PIR_SUMMARY"><data key="node_entity_id">DASH_PIR_SUMMARY</data><data key="node_entity_type">dashboard</data><data key="node_canonical_name">PIR Summary Metrics Dashboard</data><data key="node_acronym">PIR Dashboard</data><data key="node_domain">IT Governance / Investment Management</data><data key="node_description">Unnamed Agency dashboard containing summary metrics for Post-Implementation Reviews.</data><data key="node_observed_status">documented_historical_current_through_2026_audit</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">OIG states dashboard data were separate from PIR report files on the shared site; technology is not identified.</data></node><node id="DATA_AC_RR_PUBLIC"><data key="node_entity_id">DATA_AC_RR_PUBLIC</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Appeals Council Requests for Review Data Collection</data><data key="node_domain">Appeals Council / Public Data</data><data key="node_description">Public dataset reporting Appeals Council requests-for-review receipts, dispositions and pending workloads.</data><data key="node_observed_status">cataloged_public_data</data><data key="node_observed_as_of">2026-09-08</data><data key="node_confidence">5</data><data key="node_notes">Underlying dataset last updated 2024; catalog remained current in September 2026.</data></node><node id="DATA_ADRP_CONTACT_HISTORY"><data key="node_entity_id">DATA_ADRP_CONTACT_HISTORY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">ADRP Contact History Table</data><data key="node_domain">Payee / Person Identity</data><data key="node_description">Application-described Contact History table recording contact results and comments including date, time and SSA employee entry; physical DBMS and separate storage unknown.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS explicitly calls this a table. This does not establish a standalone enterprise database.</data></node><node id="DATA_ADRP_DESIGNEE_INFO"><data key="node_entity_id">DATA_ADRP_DESIGNEE_INFO</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ADRP Advance Designee Profile Attributes</data><data key="node_domain">Payee / Person Identity</data><data key="node_description">Designee name, telephone, optional relationship, ordered priority and update date; SSA says designee SSN is not collected.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_ADRP_OR_RECEIPT"><data key="node_entity_id">DATA_ADRP_OR_RECEIPT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">ADRP Designation Transaction Receipt in ORS</data><data key="node_domain">Payee / Communications</data><data key="node_description">Receipt copy preserved in Online Retrieval System after printed transaction receipts ceased being mailed effective July 1 2025.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_ALJ_CASE_REVIEW_HIST"><data key="node_entity_id">DATA_ALJ_CASE_REVIEW_HIST</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Disability Case Review of ALJ Hearing Decisions Data, FY2009-2015</data><data key="node_acronym">ALJ Case Review Data</data><data key="node_domain">Hearings / Appeals / Quality / Open Data</data><data key="node_description">Historical public dataset of post-effectuation quality-review agreement rates for favorable and unfavorable ALJ disability hearing decisions.</data><data key="node_observed_status">historical_review_discontinued</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1547; SSA states it no longer conducts this review as of 2019.</data></node><node id="DATA_ALJ_PAMC_ADDRESS"><data key="node_entity_id">DATA_ALJ_PAMC_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ALJ/PAMC Complaint-Derived Claimant Address</data><data key="node_acronym">ALJ/PAMC Claimant Address</data><data key="node_domain">Hearings / Oversight / Address Provenance</data><data key="node_description">Claimant address maintained when supplied in an ALJ bias/misconduct complaint and relevant to the complaint.</data><data key="node_observed_status">documented_current_pia_attribute</data><data key="node_observed_as_of">2025-02-11</data><data key="node_confidence">5</data><data key="node_notes">Complaint-derived application attribute; PIA does not establish any update to PI/PERSON, Numident, MBR, SSR, or another authoritative program address.</data></node><node id="DATA_ARPS_VPAT"><data key="node_entity_id">DATA_ARPS_VPAT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ARPS VPAT Case Characteristic</data><data key="node_acronym">VPAT</data><data key="node_domain">Appeals / Disability / Priority</data><data key="node_description">VAPT priority case characteristic added in Appeals Review Processing System.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies ARPS VPAT for matched VAPT cases.</data></node><node id="DATA_AVC_DEBTOR_ADDR"><data key="node_entity_id">DATA_AVC_DEBTOR_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">AVC Verified Debtor Address</data><data key="node_acronym">AVC verified address</data><data key="node_domain">Address Provenance / Debt Collection</data><data key="node_description">Verified debtor address returned by the Address Verification Contractor for ECO pre-offset notice mailing.</data><data key="node_observed_status">observed_current_lookup_attribute</data><data key="node_observed_as_of">2025-05-08</data><data key="node_confidence">5</data><data key="node_notes">If AVC does not provide a good address, ECO may use a recently updated MBR/SSR address; no source establishes that the AVC address overwrites MBR, SSR, Numident, or PI/PERSON.</data></node><node id="DATA_AWARD_TERMINATION_TRANSACTION"><data key="node_entity_id">DATA_AWARD_TERMINATION_TRANSACTION</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Annual Award and Termination Transaction File</data><data key="node_domain">Title II / Statistical Production / Historical</data><data key="node_description">Historical SSA statistical transaction file used as a source for disability award and termination statistics during portions of 2000 through 2011.</data><data key="node_observed_status">historical_statistical_source_2000_2011</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">2024 disability statistical report documents a 1-percent sample for 2000-2001 and 100-percent award data for 2002-2011; some termination tables use the file for 2004-2011.</data></node><node id="DATA_AWI_RAW_WAGE"><data key="node_entity_id">DATA_AWI_RAW_WAGE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA Raw Average Wage Data</data><data key="node_acronym">Raw Average Wage Data</data><data key="node_domain">Actuarial / Earnings Statistics</data><data key="node_description">OACT published series of average wages per worker with underlying worker counts and aggregate wage amounts used to develop the national Average Wage Index.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OACT page publishes raw average wage data and explicitly distinguishes average per worker from average per job.</data></node><node id="DATA_AWI_SERIES"><data key="node_entity_id">DATA_AWI_SERIES</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">National Average Wage Index Series</data><data key="node_acronym">AWI</data><data key="node_domain">Actuarial / Earnings Statistics</data><data key="node_description">SSA national Average Wage Index time series used in Social Security program indexing and automatic determinations.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">OACT currently publishes the series through 2024, with 2024 AWI 69,846.57. The Atlas stores lineage, not individual annual values.</data></node><node id="DATA_BENDATA"><data key="node_entity_id">DATA_BENDATA</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">State Beneficiary Data File</data><data key="node_acronym">BENDATA</data><data key="node_domain">External Data Exchange / State Services</data><data key="node_description">File sent by a state to SSA to request SSA data for BENDEX processing.</data><data key="node_observed_status">observed_current_documentation</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Data Exchange glossary defines the file and processing cutoff.</data></node><node id="DATA_BENDEX_CITIZENSHIP"><data key="node_entity_id">DATA_BENDEX_CITIZENSHIP</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">BENDEX Citizenship Occurrence Data</data><data key="node_domain">person identity</data><data key="node_description">BENDEX citizenship occurrence data, including occurrence start/stop dates, country, and U.S.-proof information where present.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Exchange field set; no inference about upstream physical storage.</data></node><node id="DATA_BENDEX_PAYEE_ADDR"><data key="node_entity_id">DATA_BENDEX_PAYEE_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">BENDEX Payee Mailing Address</data><data key="node_domain">address provenance</data><data key="node_description">Payee name and mailing-address fields transmitted in the BENDEX response record, including street, city, State, and ZIP data.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Exchange representation; not modeled as a separate authoritative address master.</data></node><node id="DATA_BENDEX_RESPONSE"><data key="node_entity_id">DATA_BENDEX_RESPONSE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">BENDEX Response Record</data><data key="node_domain">external exchanges</data><data key="node_description">Structured BENDEX record returned by SSA to participating State partners with Title II beneficiary, payment, entitlement, identity, address, and related fields documented in the BENDEX record layout.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Record-layout object; does not imply a distinct physical database.</data></node><node id="DATA_BENDEX_RES_SCC"><data key="node_entity_id">DATA_BENDEX_RES_SCC</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">BENDEX State and County Code of Residence</data><data key="node_domain">address provenance</data><data key="node_description">Five-position State and county code in the BENDEX response reflecting the beneficiary's residence geography.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Residence-geography attribute, not a complete street address.</data></node><node id="DATA_BENDEX_VERIFIED_BOAN"><data key="node_entity_id">DATA_BENDEX_VERIFIED_BOAN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">BENDEX Verified Beneficiary Own Account Number</data><data key="node_domain">person identity</data><data key="node_description">Verified beneficiary own-account-number indicator/value carried in the BENDEX response layout.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Identity-related exchange field.</data></node><node id="DATA_BENEF_ABROAD_ACTUAL_RESIDENCE"><data key="node_entity_id">DATA_BENEF_ABROAD_ACTUAL_RESIDENCE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Beneficiary Abroad Actual Residence Address</data><data key="node_acronym">Actual Residence Abroad</data><data key="node_domain">Title II / International / Address Provenance</data><data key="node_description">Actual residence address that a beneficiary abroad must keep SSA advised of even when using a U.S. mailing address.</data><data key="node_observed_status">observed_current_policy_attribute</data><data key="node_observed_as_of">2024-02-07</data><data key="node_confidence">5</data><data key="node_notes">Physical persistence location is not established by this source.</data></node><node id="DATA_BEPUF2020_BENEFITS"><data key="node_entity_id">DATA_BEPUF2020_BENEFITS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">BEPUF 2020 Benefits Subfile</data><data key="node_acronym">Benefits Subfile</data><data key="node_domain">Research / Public-Use Microdata</data><data key="node_description">Fully synthetic Benefits Subfile in BEPUF 2020 containing benefit-related variables and linked at record level to the Earnings Subfile by synthetic beneficiary identifier.</data><data key="node_observed_status">current_publication</data><data key="node_observed_as_of">2026-04</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-3267. April 24, 2026 errata removed AIME, PIA, and nEarns from this subfile after calculation errors were identified.</data></node><node id="DATA_BEPUF2020_EARNINGS"><data key="node_entity_id">DATA_BEPUF2020_EARNINGS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">BEPUF 2020 Earnings Subfile</data><data key="node_acronym">Earnings Subfile</data><data key="node_domain">Research / Public-Use Microdata</data><data key="node_description">Fully synthetic Earnings Subfile in BEPUF 2020 containing taxable earnings histories and linked at record level to the Benefits Subfile by synthetic beneficiary identifier.</data><data key="node_observed_status">current_publication</data><data key="node_observed_as_of">2026-04</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-3268. SSA cautions that the synthetic earnings history and monthly benefit relationship is statistically modeled rather than computed under program rules.</data></node><node id="DATA_BEPUF_2020"><data key="node_entity_id">DATA_BEPUF_2020</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Benefits and Earnings Public-Use File, 2020</data><data key="node_acronym">BEPUF 2020</data><data key="node_domain">Research / Public-Use Microdata</data><data key="node_description">Fully synthetic microdata product statistically representing a self-weighted 10 percent sample of the current adult OASDI beneficiary population as of December 2020.</data><data key="node_observed_status">current_publication</data><data key="node_observed_as_of">2026-04</data><data key="node_confidence">5</data><data key="node_notes">Released May 2025 and updated April 2026. SSA states no released record can be matched to a real beneficiary; synthetic values are modeled statistically.</data></node><node id="DATA_BE_PUF"><data key="node_entity_id">DATA_BE_PUF</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Benefit and Earnings Public Use File</data><data key="node_domain">Research Data / Privacy</data><data key="node_description">Synthetic public-use microdata generated with machine-learning methods to support benefits and earnings research while protecting privacy.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2025-05-01</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="DATA_BLS_CPIW"><data key="node_entity_id">DATA_BLS_CPIW</data><data key="node_entity_type">external_data_product</data><data key="node_canonical_name">Consumer Price Index for Urban Wage Earners and Clerical Workers</data><data key="node_acronym">CPI-W</data><data key="node_domain">External Statistical Input / Actuarial</data><data key="node_description">Monthly Bureau of Labor Statistics consumer-price index used by SSA in statutory cost-of-living adjustment calculations.</data><data key="node_observed_status">observed_current_series</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">OACT republishes the national CPI-W series and states BLS calculates it monthly.</data></node><node id="DATA_BSO_ACTIVATION_CODE"><data key="node_entity_id">DATA_BSO_ACTIVATION_CODE</data><data key="node_entity_type">access_control_artifact</data><data key="node_canonical_name">BSO Employer Service Activation Code</data><data key="node_acronym">BSO Activation Code</data><data key="node_domain">Employer Services / Identity &amp; Access</data><data key="node_description">Time-sensitive activation code mailed to an employer after a BSO user requests employer services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA guidance states the code is mailed to the employer address on file with IRS and then entered in BSO.</data></node><node id="DATA_BSO_IRS_EMPLOYER_ADDRESS"><data key="node_entity_id">DATA_BSO_IRS_EMPLOYER_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">IRS-Registered Employer Address Used for BSO Activation</data><data key="node_acronym">IRS Employer Address</data><data key="node_domain">Employer Services / Address Provenance</data><data key="node_description">Employer address on file with IRS used by SSA to mail a Business Services Online employer-suite activation code.</data><data key="node_observed_status">observed_current_controlled_use</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Use is documented for BSO activation/authorization mailing. Do not infer that this value becomes an SSA person, employer master, Numident, MBR, or SSR address.</data></node><node id="DATA_CAR"><data key="node_entity_id">DATA_CAR</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Certified Administrative Record</data><data key="node_acronym">CAR</data><data key="node_domain">Appeals / Federal Court</data><data key="node_description">Certified administrative record prepared for Social Security federal-court litigation and made available electronically for routing/filing.</data><data key="node_observed_status">observed_current_hallex</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">HALLEX documents an electronic route through eView and USAfx; some jurisdictions still require paper copies.</data></node><node id="DATA_CAWR_EIN_TAXYEAR_KEY"><data key="node_entity_id">DATA_CAWR_EIN_TAXYEAR_KEY</data><data key="node_entity_type">logical_data_element</data><data key="node_canonical_name">CAWR Employer EIN and Tax-Year Matching Keys</data><data key="node_acronym">EIN/TY</data><data key="node_domain">Earnings / IRS</data><data key="node_description">EIN and tax year are explicitly used to reconcile SSA employer W-2 totals with corresponding IRS employer tax filings; not an individual mailing-address matching key.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_CEF_FLAG"><data key="node_entity_id">DATA_CEF_FLAG</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Certified Electronic Folder Flag</data><data key="node_acronym">CEF Flag</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">User-created CEF flag identifying special case-handling situations, with a flag type, optional text, and system metadata.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes">Only one flag of each type can exist for a folder. Flags persist for the life of the case, including appeals, unless manually deleted; closure does not automatically delete them.</data></node><node id="DATA_CEF_MESSAGE"><data key="node_entity_id">DATA_CEF_MESSAGE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Certified Electronic Folder Message</data><data key="node_acronym">CEF Message</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">User-created CEF case-handling message created in EDCS or eView with message text and optional expiration.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes">Messages are not official documentation of case-processing actions. They persist until expiration or manual deletion.</data></node><node id="DATA_CE_PROVIDER_ADDR"><data key="node_entity_id">DATA_CE_PROVIDER_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">DDS CE Provider Address</data><data key="node_domain">Disability / Consultative Examinations / Address Provenance</data><data key="node_description">Address maintained for an individual who performs consultative examinations for a State DDS.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Business/provider address, not a claimant or beneficiary program address.</data></node><node id="DATA_CE_PROVIDER_CREDENTIAL"><data key="node_entity_id">DATA_CE_PROVIDER_CREDENTIAL</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">DDS CE Provider Credential Record</data><data key="node_domain">Disability / Consultative Examinations / Provider Identity</data><data key="node_description">CE provider medical-license and credential information, including license number and expiration date.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Maintained in CE Provider File; source does not establish a separate credential database.</data></node><node id="DATA_CE_PROVIDER_OVERSIGHT"><data key="node_entity_id">DATA_CE_PROVIDER_OVERSIGHT</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">DDS CE Provider Oversight Record</data><data key="node_domain">Disability / Consultative Examinations / Program Integrity</data><data key="node_description">CE provider record of report timeliness and quality, fees, site visits, agency oversight, exclusion information, scheduling preferences, and investigations.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical record grouping based on the current SORN; no separate physical repository is inferred.</data></node><node id="DATA_CE_PROVIDER_PHOTO_ID"><data key="node_entity_id">DATA_CE_PROVIDER_PHOTO_ID</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DDS CE Provider Photo Identification Image</data><data key="node_domain">Disability / Consultative Examinations / Provider Identity</data><data key="node_description">Image of a CE provider photo identification card maintained in the CE Provider File.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SORN explicitly lists photo-ID images among record categories.</data></node><node id="DATA_CLIENT_LANGUAGE_PREF"><data key="node_entity_id">DATA_CLIENT_LANGUAGE_PREF</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Language Preferences for Written and Spoken Communications</data><data key="node_acronym">Client Language Preferences</data><data key="node_domain">Shared Client Data / Language</data><data key="node_description">Non-public SSA client-data asset containing written and spoken language preference when the preference is other than English.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-568; catalog tags include CLIENT, T2, and T16. Current physical extraction/storage topology is not stated.</data></node><node id="DATA_CMA1045_EMPLOYER_ADDR"><data key="node_entity_id">DATA_CMA1045_EMPLOYER_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CMA 1045 Employer Address</data><data key="node_domain">Earnings / External Exchange / Address Provenance</data><data key="node_description">Employer address information SSA is scheduled to disclose to OPM with matched wage and self-employment data under CMA 1045.</data><data key="node_observed_status">scheduled_exchange_field</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">This is an employer/business address originating from SSA earnings records, not a beneficiary mailing address.</data></node><node id="DATA_CMA1071_SVES_IND"><data key="node_entity_id">DATA_CMA1071_SVES_IND</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CMA 1071 SVES Indicator</data><data key="node_acronym">SVES Indicator</data><data key="node_domain">External Exchange / Title II / Request Routing</data><data key="node_description">Indicator OPM submits under CMA 1071 to request Title II benefit information from the Master Beneficiary Record through SVES.</data><data key="node_observed_status">scheduled_exchange_field</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Federal Register notice explicitly identifies the SVES indicator as part of OPM input.</data></node><node id="DATA_CMS1957"><data key="node_entity_id">DATA_CMS1957</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">CMS-1957 State Buy-In Problem Report</data><data key="node_acronym">CMS-1957</data><data key="node_domain">Medicare / State Coordination</data><data key="node_description">Former physical report used to escalate State buy-in problems to CMS Premium Module staff.</data><data key="node_observed_status">retired_2026_04_01</data><data key="node_observed_as_of">2026-04-01</data><data key="node_confidence">5</data><data key="node_notes">CMS stopped using the physical form April 1, 2026; issue submission moved to email.</data></node><node id="DATA_CMS_EDB"><data key="node_entity_id">DATA_CMS_EDB</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">CMS Enrollment Database</data><data key="node_acronym">EDB</data><data key="node_domain">External Data / Medicare</data><data key="node_description">CMS source system used in CMA 1094 to provide Medicare enrollment information.</data><data key="node_observed_status">documented_current_exchange_source</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">CMS SOR 09-70-0502.</data></node><node id="DATA_CMS_HIX"><data key="node_entity_id">DATA_CMS_HIX</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">CMS Health Insurance Exchange System</data><data key="node_acronym">HIX</data><data key="node_domain">External Data / CMS</data><data key="node_description">CMS system of records supporting ACA marketplace requests and match results for the SSA-CMS matching program.</data><data key="node_observed_status">observed_current_exchange_source</data><data key="node_observed_as_of">2026-03-09</data><data key="node_confidence">5</data><data key="node_notes">CMS SORN 09-70-0560.</data></node><node id="DATA_CMS_LTC_MDS"><data key="node_entity_id">DATA_CMS_LTC_MDS</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">CMS Long-Term Care Minimum Data Set</data><data key="node_acronym">LTC/MDS</data><data key="node_domain">External Data / Medicare</data><data key="node_description">CMS source system used in CMA 1094 to identify nursing-facility residence and related status information.</data><data key="node_observed_status">documented_current_exchange_source</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">CMS SOR 90-70-0528.</data></node><node id="DATA_CMS_NCH"><data key="node_entity_id">DATA_CMS_NCH</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">CMS National Claims History</data><data key="node_acronym">NCH</data><data key="node_domain">External Data / Medicare</data><data key="node_description">CMS source system used in CMA 1094 to provide Medicare claims-history information for non-utilization matching.</data><data key="node_observed_status">documented_current_exchange_source</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">CMS SOR 09-70-0558.</data></node><node id="DATA_COA_INET"><data key="node_entity_id">DATA_COA_INET</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Internet Change of Address Applications - Monthly Volume</data><data key="node_acronym">Internet COA Volume</data><data key="node_domain">Title II / Digital Service Analytics</data><data key="node_description">Public monthly national counts of Internet Change of Address transactions.</data><data key="node_observed_status">current_public_data_product</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1404.</data></node><node id="DATA_COMBINED_DISABILITY_APT"><data key="node_entity_id">DATA_COMBINED_DISABILITY_APT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Combined Title II Disability and Title XVI Blind and Disabled Average Processing Time</data><data key="node_acronym">Combined Disability APT</data><data key="node_domain">disability and public data</data><data key="node_description">Monthly public dataset measuring overall cumulative elapsed days from filing through payment or denial for initial Title II disability and Title XVI blind/disabled claims requiring a medical determination, excluding technical denials.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1406; updated July 10, 2026.</data></node><node id="DATA_CONGRESSIONAL_STATS_2025"><data key="node_entity_id">DATA_CONGRESSIONAL_STATS_2025</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Congressional Statistics, 2025</data><data key="node_acronym">Congressional Statistics 2025</data><data key="node_domain">Statistics / Publications / Congressional Districts</data><data key="node_description">State and Congressional-district OASDI and SSI fact sheets using data as of December 2025 for the 119th Congress.</data><data key="node_observed_status">current_publication_2026</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog ID US-GOV-SSA-3372. Source page does not establish the physical production system.</data></node><node id="DATA_CONG_OASDI_2025"><data key="node_entity_id">DATA_CONG_OASDI_2025</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2025 Congressional Statistics OASDI District Table</data><data key="node_domain">Statistical / Congressional</data><data key="node_description">Congressional district counts and monthly amounts for OASDI beneficiaries, derived from MBR 100-percent data with USPS congressional geographic data.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_CONG_SSI_2025"><data key="node_entity_id">DATA_CONG_SSI_2025</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2025 Congressional Statistics SSI District Table</data><data key="node_domain">Statistical / Congressional</data><data key="node_description">Congressional district counts and monthly amounts for SSI recipients, derived from SSR 100-percent data with USPS congressional geographic data.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_CORE_DAILY_DEATH_FILE"><data key="node_entity_id">DATA_CORE_DAILY_DEATH_FILE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Fiscal Service CORE Daily Death File</data><data key="node_acronym">CORE Daily Death File</data><data key="node_domain">External / Treasury / Death / Payment Control</data><data key="node_description">Daily file sent by the Bureau of the Fiscal Service to the Federal Reserve Bank handling CORE after SSA reports a payee death and related stop-payment information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">File transport, format, retention, and field layout are not disclosed by the cited public POMS.</data></node><node id="DATA_CPMS_VPAT"><data key="node_entity_id">DATA_CPMS_VPAT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CPMS VPAT Case Characteristic</data><data key="node_acronym">VPAT</data><data key="node_domain">Hearings / Disability / Priority</data><data key="node_description">VAPT priority case characteristic historically added in CPMS.</data><data key="node_observed_status">historical_parent_retired_current_poms_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Current POMS still describes CPMS VPAT, but Atlas evidence records CPMS retired 2025-09-26; do not infer current CPMS production use.</data></node><node id="DATA_CSCRA_QUESTIONNAIRE"><data key="node_entity_id">DATA_CSCRA_QUESTIONNAIRE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">CSCRA Questionnaire</data><data key="node_acronym">CSCRA Questionnaire</data><data key="node_domain">Cybersecurity / Third-Party Risk</data><data key="node_description">Questionnaire used to collect third-party supply-chain and cybersecurity risk information before SSA contract award.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">OAG lists high-level questionnaire categories including foreign ownership/control, non-U.S. labor, incident history, economic status, and executive background.</data></node><node id="DATA_CSRQ_VAPT_ALERT"><data key="node_entity_id">DATA_CSRQ_VAPT_ALERT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Customer Service Record Query VAPT Expedited Procedures Alert</data><data key="node_acronym">VAPT CSRQ Alert</data><data key="node_domain">Disability / Customer Service</data><data key="node_description">Customer Service Record Query alert stating VA 100% P&amp;T - Use Expedited Procedures, displayed in VIPr and the Customer Information Control System.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS writes the acronym as CSQR while the Federal Data Catalog entity in the Atlas is CSRQ; alias/conflict retained.</data></node><node id="DATA_CSR_HIGH_RISK_ALERT"><data key="node_entity_id">DATA_CSR_HIGH_RISK_ALERT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Customer Service High Risk Alert</data><data key="node_acronym">High Risk Alert</data><data key="node_domain">Customer Service / Physical Security</data><data key="node_description">Alert information about persons SSA reasonably believes may pose a security risk when contacting an SSA facility.</data><data key="node_observed_status">observed_current_sorn_attribute</data><data key="node_observed_as_of">2025-08-20</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0350 identifies source of report from AIRS. No backend or synchronization mechanism is inferred.</data></node><node id="DATA_CSR_VISITOR_MAILING_ADDRESS"><data key="node_entity_id">DATA_CSR_VISITOR_MAILING_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Customer Service Visitor Mailing Address</data><data key="node_domain">Customer Service / Address Provenance</data><data key="node_description">Mailing-address attribute maintained within visitor/customer-service records under SORN 60-0350.</data><data key="node_observed_status">observed_current_sorn_attribute</data><data key="node_observed_as_of">2025-08-20</data><data key="node_confidence">5</data><data key="node_notes">Source categories are broad; do not infer that this mailing address comes from or updates MBR, SSR, Numident, or PI/PERSON.</data></node><node id="DATA_CWHS"><data key="node_entity_id">DATA_CWHS</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Continuous Work History Sample</data><data key="node_acronym">CWHS</data><data key="node_domain">Earnings / Actuarial / Research</data><data key="node_description">Recurring 1-percent SSA work-history sample used in current statistical and actuarial work, including covered-worker and insured-status estimates.</data><data key="node_observed_status">observed_current_data_asset</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 actuarial/statistical sources confirm continued use. Historical SSA documentation describes lineage from MEF, Numident, and MBR; that lineage is retained with historical observation dates rather than assumed unchanged in implementation detail.</data></node><node id="DATA_CYBER_RISK_REGISTER"><data key="node_entity_id">DATA_CYBER_RISK_REGISTER</data><data key="node_entity_type">governance_data_artifact</data><data key="node_canonical_name">Cybersecurity Risk Register</data><data key="node_domain">Enterprise Security / Risk Management</data><data key="node_description">SSA cybersecurity risk register used in the agency risk-management program.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-09-24</data><data key="node_confidence">5</data><data key="node_notes">FY2026 OIG evidence says SSA needed to improve the Cybersecurity Risk Register. Storage technology, schema, workflow tooling, and system of record are not public.</data></node><node id="DATA_DAF"><data key="node_entity_id">DATA_DAF</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Disability Analysis File</data><data key="node_acronym">DAF</data><data key="node_domain">Disability / Research Analytics</data><data key="node_description">Annual research database assembled from multiple SSA administrative files to support disability/work research and evaluation.</data><data key="node_observed_status">production_discontinued_after_2023_partial</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2026 budget says the FY2022 continuation contract ended in FY2025; DAF 2023 was mostly complete and DAF 2024-2026 are no longer planned.</data></node><node id="DATA_DCF_PROBLEM_REPORT"><data key="node_entity_id">DATA_DCF_PROBLEM_REPORT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DCF Problem Report</data><data key="node_acronym">DCF Problem Report</data><data key="node_domain">Disability / CDR / Exception Handling</data><data key="node_description">Problem report submitted through usual channels when specified CDR update controls do not explain a missing Title II update.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-08-12</data><data key="node_confidence">5</data><data key="node_notes">Public POMS establishes the report trigger but not the submission platform, persistence store, or routing mechanism.</data></node><node id="DATA_DCR_LOCATION_V32"><data key="node_entity_id">DATA_DCR_LOCATION_V32</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Disability Case Review Location Code V32</data><data key="node_acronym">V32</data><data key="node_domain">Disability / Work Routing</data><data key="node_description">SSA location code identifying Disability Case Review for routing specified disability claims.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-04-16</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly identifies DCR location code V32.</data></node><node id="DATA_DDFP_BLOCK"><data key="node_entity_id">DATA_DDFP_BLOCK</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Direct Deposit Fraud Prevention Block</data><data key="node_acronym">DDFP Block</data><data key="node_domain">Payments / Fraud Prevention</data><data key="node_description">Record-level control that can require a beneficiary, recipient, or representative payee to make direct-deposit changes in person.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="DATA_DDS_ACCURACY"><data key="node_entity_id">DATA_DDS_ACCURACY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Disability Determination Services Accuracy Data</data><data key="node_acronym">DDS Accuracy Data</data><data key="node_domain">Disability / Quality / Open Data</data><data key="node_description">Public state and national accuracy-rate dataset for SSA reviews of DDS disability medical determinations, covering fiscal year 2007 and later.</data><data key="node_observed_status">observed_current_dataset</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-344.</data></node><node id="DATA_DDS_CE_MER_FEE_SCHEDULE"><data key="node_entity_id">DATA_DDS_CE_MER_FEE_SCHEDULE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DDS CE and MER Fee Schedule</data><data key="node_acronym">CE/MER Fee Schedule</data><data key="node_domain">Disability / Consultative Examinations</data><data key="node_description">Current consultative-examination and medical-evidence-of-record fee schedules uploaded annually by DDS components.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_DDS_CE_OVERSIGHT_REPORT"><data key="node_entity_id">DATA_DDS_CE_OVERSIGHT_REPORT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DDS Annual Consultative Examination Oversight Report</data><data key="node_acronym">CE Oversight Report</data><data key="node_domain">Disability / Consultative Examinations</data><data key="node_description">Annual DDS report covering CE oversight and medical/professional-relations activity for the preceding fiscal year.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_DDS_CE_PROVIDER_LIST"><data key="node_entity_id">DATA_DDS_CE_PROVIDER_LIST</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DDS Consultative Examination Provider List</data><data key="node_acronym">CE Provider List</data><data key="node_domain">Disability / Consultative Examinations</data><data key="node_description">Annual list of CE providers, including key/volume providers and provider-removal/onsite-review information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_DDS_STATE_MONTHLY_WORKLOAD"><data key="node_entity_id">DATA_DDS_STATE_MONTHLY_WORKLOAD</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA State Agency Monthly Workload Data</data><data key="node_acronym">State Agency Monthly Workload</data><data key="node_domain">Disability / DDS / Public Data</data><data key="node_description">Public monthly disability workload dataset containing historical and current information on claims referred to state Disability Determination Services and similarly involved federal components.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Monthly data begin October 2000. Current documentation describes DIODS as the definitive workload-management store and explains that published summaries derive from row-level disability case data.</data></node><node id="DATA_DD_INET"><data key="node_entity_id">DATA_DD_INET</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Internet Direct Deposit Applications - Monthly Volume</data><data key="node_acronym">Internet DD Volume</data><data key="node_domain">Title II / Digital Service Analytics</data><data key="node_description">Public monthly national counts of Internet Direct Deposit applications.</data><data key="node_observed_status">current_public_data_product</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1405.</data></node><node id="DATA_DD_NATIONAL_TRENDS"><data key="node_entity_id">DATA_DD_NATIONAL_TRENDS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">National Trends in Direct Deposit Participation</data><data key="node_acronym">Direct Deposit Trends</data><data key="node_domain">Public Data / Payments</data><data key="node_description">SSA public historical series reporting the percentage of Social Security and SSI payments made by direct deposit across fiscal years.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Page reports September 2026 participation values and a long historical series; internal production lineage is not disclosed.</data></node><node id="DATA_DECOR_IRS_SE_ADDRESS"><data key="node_entity_id">DATA_DECOR_IRS_SE_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">IRS-Derived Self-Employed Worker Address for DECOR</data><data key="node_acronym">DECOR IRS Address</data><data key="node_domain">Address Provenance / IRS / Earnings</data><data key="node_description">Address derived from IRS-provided data and historically used by SSA to mail SSA-L2765-C1 to a self-employed worker.</data><data key="node_observed_status">historical_documented_use</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">This is explicit evidence of IRS-derived address use for correspondence, not evidence of an automatic update to Numident, MBR, SSR, or PI/PERSON.</data></node><node id="DATA_DECOR_W2_EMPLOYEE_ADDRESS"><data key="node_entity_id">DATA_DECOR_W2_EMPLOYEE_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">W-2-Derived Employee Address for DECOR</data><data key="node_acronym">DECOR W-2 Address</data><data key="node_domain">Address Provenance / Earnings</data><data key="node_description">Employee address derived from Form W-2 and historically used to mail SSA-L3365-C1.</data><data key="node_observed_status">historical_documented_use</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Correspondence-use provenance only; no master-record update path established.</data></node><node id="DATA_DHS_ADMISSION_NUMBER"><data key="node_entity_id">DATA_DHS_ADMISSION_NUMBER</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">DHS Admission Number</data><data key="node_acronym">Admission Number</data><data key="node_domain">Identity / Immigration Verification</data><data key="node_description">DHS immigration-document identifier that SSA can use, like an A-Number, to query SAVE.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current lawful-presence policy says an A-Number or Admission Number is required for the online SAVE query in the documented workflow.</data></node><node id="DATA_DIB_INTERNET_APPS_2247"><data key="node_entity_id">DATA_DIB_INTERNET_APPS_2247</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Initial Disability Insurance Applications Filed via the Internet Data Collection</data><data key="node_acronym">US-GOV-SSA-2247</data><data key="node_domain">Title II Disability / Public Data</data><data key="node_description">Monthly national data for initial SSDI applications filed via the Internet and comparable non-Internet channels, excluding online SSI disability applications.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog collection identifier US-GOV-SSA-2247; CSV publication for fiscal years 2012 and later.</data></node><node id="DATA_DIFSLA_FINDER"><data key="node_entity_id">DATA_DIFSLA_FINDER</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">SSA DIFSLA Finder File</data><data key="node_acronym">DIFSLA Finder File</data><data key="node_domain">Title XVI / IRS Match / Exchange Data</data><data key="node_description">SSA input/tickler file for CMA 1016 containing SSN and four-character surname name control for individuals for whom SSI unearned-income information is requested.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">CMA 1016 expects roughly 18 million finder records per fiscal year. IRS retains the input/tickler file approximately 90 days and treats it as transitory intermediate input.</data></node><node id="DATA_DIFSLA_FO_ALERT"><data key="node_entity_id">DATA_DIFSLA_FO_ALERT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DIFSLA IRS Field Office Development Alert</data><data key="node_acronym">DIFSLA IRS Alert</data><data key="node_domain">Title XVI / IRS Match / Work Control</data><data key="node_description">Work alert released to SSA field offices for development after IRS-match records pass screening and profiling.</data><data key="node_observed_status">observed_in_current_cma_attachment</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">CMA attachment reports 86,987 alerts completed by field offices in FY2023; exact mapping between this alert and the 5B diary is not asserted here.</data></node><node id="DATA_DIFSLA_PAYEE_ADDRESS"><data key="node_entity_id">DATA_DIFSLA_PAYEE_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">IRS DIFSLA Payee Mailing Address</data><data key="node_acronym">DIFSLA Payee Address</data><data key="node_domain">Title XVI / IRS Match / Address Provenance</data><data key="node_description">Payee name and mailing-address element returned by IRS in a CMA 1016 DIFSLA match response.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal tax information restricted to SSI eligibility/payment verification. The agreement does not establish automatic overwrite of SSR, Person, Numident, MBR, or any SSA master address.</data></node><node id="DATA_DIFSLA_PAYER_ADDRESS"><data key="node_entity_id">DATA_DIFSLA_PAYER_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">IRS DIFSLA Payer Address</data><data key="node_acronym">DIFSLA Payer Address</data><data key="node_domain">Title XVI / IRS Match / Third-Party Provenance</data><data key="node_description">Payer name and address element returned by IRS in a CMA 1016 DIFSLA match response.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">This is a third-party payer address, not a claimant residence/mailing address. Use is constrained by the CMA and IRC 6103.</data></node><node id="DATA_DIFSLA_RESPONSE"><data key="node_entity_id">DATA_DIFSLA_RESPONSE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">IRS DIFSLA Response Record</data><data key="node_acronym">DIFSLA Response</data><data key="node_domain">Title XVI / IRS Match / Exchange Data</data><data key="node_description">IRS response record produced for individuals identified by SSA in CMA 1016, carrying matched unearned-income information from IRMF.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">CMA 1016 states IRS provides a response record for each individual identified by SSA; one individual may yield multiple response records. Current CMA also requires SSA to destroy the matching file after the match purpose is served and applicable legal retention requirements are met; no permanent separate DIFSLA person repository is inferred.</data></node><node id="DATA_DIGID_ACCESS_LOG"><data key="node_entity_id">DATA_DIGID_ACCESS_LOG</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Digital Identity Access Activity Log</data><data key="node_acronym">Digital Access Log</data><data key="node_domain">identity and access management</data><data key="node_description">Date/time, activity logs, IP address, internet activity and related access records for SSA computers, networks, online programs and applications.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN 60-0373.</data></node><node id="DATA_DIGID_DEVICE_FINGERPRINT"><data key="node_entity_id">DATA_DIGID_DEVICE_FINGERPRINT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Digital Identity Device Fingerprint</data><data key="node_acronym">Device Fingerprint</data><data key="node_domain">identity and access management</data><data key="node_description">Browser/device information collected from a device used to access SSA IT services, including a device fingerprint.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN 60-0373.</data></node><node id="DATA_DIGID_EVIDENCE_IMAGE"><data key="node_entity_id">DATA_DIGID_EVIDENCE_IMAGE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Digital Identity Evidence Image</data><data key="node_acronym">Identity Evidence Image</data><data key="node_domain">identity and access management</data><data key="node_description">Image of identity evidence such as a driver license maintained as part of digital identity processing where applicable.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN 60-0373.</data></node><node id="DATA_DIGID_POSTAL_ADDRESS"><data key="node_entity_id">DATA_DIGID_POSTAL_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Digital Identity File Postal Address Attributes</data><data key="node_acronym">Digital Identity Postal Address</data><data key="node_domain">Identity / Address Provenance</data><data key="node_description">Postal address information stored as an attribute within the Digital Identity File Record System.</data><data key="node_observed_status">observed_current_sorn_attribute</data><data key="node_observed_as_of">2025-08-20</data><data key="node_confidence">5</data><data key="node_notes">Address is held for digital identity processes. No authoritative evidence found that this attribute updates PI/PERSON, Numident, MBR, or SSR.</data></node><node id="DATA_DIGID_PROOF_RESULT"><data key="node_entity_id">DATA_DIGID_PROOF_RESULT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Digital Identity Proofing Result</data><data key="node_acronym">Proofing Result</data><data key="node_domain">identity and access management</data><data key="node_description">Pass/fail indicator and related transaction outcome information maintained for digital identity proofing or authentication.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN 60-0373.</data></node><node id="DATA_DIGID_RISK_CONFIDENCE"><data key="node_entity_id">DATA_DIGID_RISK_CONFIDENCE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Digital Identity Confidence and Risk Indicator</data><data key="node_acronym">Identity Confidence/Risk</data><data key="node_domain">identity and access management</data><data key="node_description">Level of confidence in provided identity/attributes and indicators of potential risk factors.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN 60-0373.</data></node><node id="DATA_DIGID_TRANSACTION_RECORD"><data key="node_entity_id">DATA_DIGID_TRANSACTION_RECORD</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Digital Identity Transaction Record</data><data key="node_acronym">Digital Identity Transaction</data><data key="node_domain">identity and access management</data><data key="node_description">Archived and historical digital-identity transaction data including transaction identifiers, timing, codes, and related credential/proofing attributes.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN 60-0373; logical record grouping, not a claim of a separate database.</data></node><node id="DATA_DIGID_W2SE_ADDRESS"><data key="node_entity_id">DATA_DIGID_W2SE_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">W-2 and Schedule-SE Address Attributes in Digital Identity File</data><data key="node_acronym">W-2/Schedule-SE Address</data><data key="node_domain">Identity / Address Provenance</data><data key="node_description">Address attributes from W-2 and Schedule-SE forms included among records maintained in the Digital Identity File Record System.</data><data key="node_observed_status">observed_current_sorn_attribute</data><data key="node_observed_as_of">2025-08-20</data><data key="node_confidence">5</data><data key="node_notes">The SORN lists these address attributes but does not establish the precise upstream source path or any program-master update path.</data></node><node id="DATA_DIRECT_DEPOSIT_NOC"><data key="node_entity_id">DATA_DIRECT_DEPOSIT_NOC</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Direct Deposit Notification of Change</data><data key="node_acronym">NOC</data><data key="node_domain">Payments / Direct Deposit / Financial Institution Exchange</data><data key="node_description">Electronic financial-institution change message used to notify SSA of routing transit number, depositor account number, or account-type corrections that do not require a different account.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS states NOCs are transmitted electronically to SSA through ACH and resulting information appears on the Title II or Title XVI record.</data></node><node id="DATA_DIRECT_DEPOSIT_PRENOTE"><data key="node_entity_id">DATA_DIRECT_DEPOSIT_PRENOTE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Direct Deposit Prenotification</data><data key="node_acronym">Prenote</data><data key="node_domain">Payments / Direct Deposit / Financial Institution Exchange</data><data key="node_description">Prenotification message indicating that SSA will soon begin sending payments to a specified account.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Defined in active POMS. Public policy reviewed in this run does not establish the internal generating system or persistence mechanism.</data></node><node id="DATA_DISABILITY_DENIAL_REVIEWS"><data key="node_entity_id">DATA_DISABILITY_DENIAL_REVIEWS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Disability Denial Reviews Data</data><data key="node_acronym">Denial Review Data</data><data key="node_domain">Disability / Quality / Open Data</data><data key="node_description">Public annual national dataset showing reviewed DDS denials, returned cases, reversals, return rates and reversal rates for fiscal year 2013 and later.</data><data key="node_observed_status">observed_current_dataset</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1495.</data></node><node id="DATA_DISABILITY_RECON_APT"><data key="node_entity_id">DATA_DISABILITY_RECON_APT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Disability Reconsideration Average Processing Time Data</data><data key="node_acronym">Reconsideration APT</data><data key="node_domain">Disability / Appeals / Open Data</data><data key="node_description">Public dataset of cumulative elapsed processing time for disability reconsideration claims requiring a medical determination, fiscal year 2014 and later.</data><data key="node_observed_status">observed_current_dataset</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1768. SSA says elapsed days are electronically collected for every processed disability reconsideration case and presented using business-intelligence capabilities; no specific repository is inferred.</data></node><node id="DATA_DISABILITY_RESEARCH_FILE"><data key="node_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disability Research File</data><data key="node_domain">Disability / Research Analytics</data><data key="node_description">SSA research file updated annually with disability-application information used to determine and publish application outcomes through the conclusion of the administrative appeals process.</data><data key="node_observed_status">observed_current_statistical_source</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Public statistical methodology establishes annual update and publication use, but does not disclose physical platform, schema, or detailed source-extract process.</data></node><node id="DATA_DISALLOWED_APP_FILE"><data key="node_entity_id">DATA_DISALLOWED_APP_FILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disallowed Application File</data><data key="node_domain">Identity / Enumeration / Program Integrity</data><data key="node_description">SSA file referenced during identity-evidence assessment; the presence of an applicant record is an indicator that the applicant may not be who they claim to be.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS establishes the file as a risk indicator but does not disclose physical platform, population criteria, retention, or whether lookup is automated within SSNAP.</data></node><node id="DATA_DMF"><data key="node_entity_id">DATA_DMF</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Death Master File / SSA Death Information Files</data><data key="node_acronym">DMF</data><data key="node_domain">Death / Data Exchange</data><data key="node_description">Files of death information compiled from SSA's Enumeration System/SSN-holder master records; public limited file is distributed through NTIS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Full file and public/limited-access file have different statutory access rules.</data></node><node id="DATA_DMS_AUTOMATED_RECEIPT"><data key="node_entity_id">DATA_DMS_AUTOMATED_RECEIPT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DMS Automated Remittance Receipt</data><data key="node_acronym">Automated Receipt</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">DMS-generated receipt that serves as the remitter's record of payment to SSA in field-office remittance processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Distinct from the associated payment coupon already mapped in the Atlas.</data></node><node id="DATA_DMS_EXPLANATION_PROTEST_REASON"><data key="node_entity_id">DATA_DMS_EXPLANATION_PROTEST_REASON</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">DMS Explanation Protest Reason</data><data key="node_acronym">Explanation Protest Reason</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Debt Management System protest/stop-recovery reason used to classify a request for an explanation of a Title II overpayment and suspend recovery while it is resolved.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS instructs FO/PSC staff to use the explanation protest reason; OIG reported processing errors involving system indicators.</data></node><node id="DATA_DMS_FO_COUPON"><data key="node_entity_id">DATA_DMS_FO_COUPON</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DMS Field Office Payment Coupon</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">DMS-generated payment coupon containing receipt and scan-line information used by MATPSC to credit remittance accounts.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS states MATPSC scanner relies on the coupon scan line.</data></node><node id="DATA_DNE"><data key="node_entity_id">DATA_DNE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Death Notification Entry</data><data key="node_acronym">DNE</data><data key="node_domain">Payments / Death / Direct Deposit</data><data key="node_description">Electronic non-monetary death notification sent by SSA to the direct-deposit financial institution with payment identifiers and date-of-death information.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">DNE is generated after verified death is posted to the Title II or Title XVI record and is part of the automated EFT reclamation sequence.</data></node><node id="DATA_DOD_SSI_ADDRESS"><data key="node_entity_id">DATA_DOD_SSI_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">DoD/SSI Interface Beneficiary Address</data><data key="node_acronym">DoD SSI Address</data><data key="node_domain">Title XVI / External Exchange / Address Provenance</data><data key="node_description">Beneficiary address and ZIP code carried in the Department of Defense extract used by the SSI/DOD interface.</data><data key="node_observed_status">current_documented_interface_attribute</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS legend explicitly identifies DOD as the source for beneficiary address and ZIP. No master-address update path is documented.</data></node><node id="DATA_DOL_BLC_MONTHLY_FILE"><data key="node_entity_id">DATA_DOL_BLC_MONTHLY_FILE</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">DOL Black Lung Part C Monthly Payment File</data><data key="node_acronym">DOL BL Part C file</data><data key="node_domain">External Data / Black Lung</data><data key="node_description">Monthly DOL file containing live miners entitled to Part C Black Lung benefits used for SSA offset processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Detailed POMS is older; active CMA and current POMS references support continued exchange context.</data></node><node id="DATA_DOT"><data key="node_entity_id">DATA_DOT</data><data key="node_entity_type">external_data_reference</data><data key="node_canonical_name">Dictionary of Occupational Titles</data><data key="node_acronym">DOT</data><data key="node_domain">Disability / Occupational Data</data><data key="node_description">Legacy Department of Labor occupational reference that remains SSA's main occupational information source pending OIS replacement; DOL stopped updating it in 1991.</data><data key="node_observed_status">legacy_primary_reference_pending_ois</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The Atlas records current SSA reliance and planned replacement, not a claim that DOT itself is an SSA-operated system.</data></node><node id="DATA_DOWR"><data key="node_entity_id">DATA_DOWR</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">District Office Workload Report</data><data key="node_acronym">DOWR</data><data key="node_domain">Enterprise Data / Work Measurement</data><data key="node_description">SSA work-measurement data used for weekly and monthly mission workload volume counts and receipt-date reporting.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data></node><node id="DATA_DSI_EOL_QA"><data key="node_entity_id">DATA_DSI_EOL_QA</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disability Service Improvement End-Of-Line Quality Assurance</data><data key="node_acronym">DSI EOL QA</data><data key="node_domain">Disability / Quality Assurance</data><data key="node_description">Non-public SSA dataset containing sampled disability cases to support end-of-line quality assurance reviews.</data><data key="node_observed_status">current_federal_data_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-84; catalog modified 2026-09-08 and inventoried 2016-06-24.</data></node><node id="DATA_DX_SOFTWARE_LICENSE_GRANT"><data key="node_entity_id">DATA_DX_SOFTWARE_LICENSE_GRANT</data><data key="node_entity_type">access_control_artifact</data><data key="node_canonical_name">Data Exchange Software License Grant</data><data key="node_acronym">Data Exchange Software License</data><data key="node_domain">External Data Exchange / Security</data><data key="node_description">SSA-issued software-license grant, generally providing test and production licenses, for an external entity to communicate with SSA where required and contractually permitted.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current policy states the licenses are for the sole purpose of communication with SSA and external hosting/outsourcing remains subject to security requirements.</data></node><node id="DATA_E2960"><data key="node_entity_id">DATA_E2960</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Electronic SSA-2960 Totalization Transmittal/Request/Certification Form Family</data><data key="node_acronym">e2960</data><data key="node_domain">Title II / International / Totalization</data><data key="node_description">Country-specific electronic liaison-form family generated through TDCP for Totalization claims, requests and certifications.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Country-specific variants exist; Run 35 directly validates the USA/RO 3 Romania variant.</data></node><node id="DATA_E4962"><data key="node_entity_id">DATA_E4962</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Electronic Totalization Data Collection Form</data><data key="node_acronym">e4962</data><data key="node_domain">Title II / International / Totalization</data><data key="node_description">Electronic form used in TDCP to establish, update and clear Totalization claim and foreign-assistance-request records.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Replaces paper SSA-4962-U2.</data></node><node id="DATA_EAB_BCN"><data key="node_entity_id">DATA_EAB_BCN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Enumeration at Birth Birth Certificate Number</data><data key="node_acronym">BCN</data><data key="node_domain">Identity &amp; Enumeration / Vital Records</data><data key="node_description">State-assigned birth certificate number transmitted to SSA in the EAB request and represented on EAB Numident records.</data><data key="node_observed_status">current_documented_data_element</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">State vital statistics assigns the BCN. No inference is made that SSA creates or modifies the state value.</data></node><node id="DATA_EAB_MOTHER_ADDRESS"><data key="node_entity_id">DATA_EAB_MOTHER_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Enumeration at Birth Mother Address</data><data key="node_acronym">EAB Mother Address</data><data key="node_domain">Identity &amp; Enumeration / Address Provenance</data><data key="node_description">Address of the mother transmitted by a state vital statistics office with a newborn EAB request.</data><data key="node_observed_status">current_documented_transmitted_attribute</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Transmission to SSA is authoritative. Public evidence does not establish persistence as an SSA mailing/residence master address or an update to PI/PERSON, MBR, SSR, or another program master.</data></node><node id="DATA_EAE_DHS_DOS_MAILING_ADDRESS"><data key="node_entity_id">DATA_EAE_DHS_DOS_MAILING_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EAE DHS/DoS SSN Card Mailing Address</data><data key="node_acronym">EAE Card Mailing Address</data><data key="node_domain">Identity &amp; Enumeration / Address Provenance</data><data key="node_description">Mailing address collected in the immigrant visa/admission process and carried through Enumeration at Entry for SSA to mail an original or replacement Social Security card.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Card-delivery address; no automatic propagation to PI/PERSON, MBR, SSR, or another program master address is established.</data></node><node id="DATA_EBE_USCIS_MAILING_ADDRESS"><data key="node_entity_id">DATA_EBE_USCIS_MAILING_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">USCIS-Provided EBE SSN Card Mailing Address</data><data key="node_acronym">EBE Card Mailing Address</data><data key="node_domain">Identity &amp; Enumeration / Address Provenance</data><data key="node_description">Mailing address supplied by an applicant on a USCIS application and transmitted in the Enumeration Beyond Entry process for SSA to mail an original or replacement SSN card.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The address supports card delivery. Current POMS does not establish automatic propagation from this EBE address to MBR, SSR, Person, or another program master record.</data></node><node id="DATA_ECO_MASTER_RECORD"><data key="node_entity_id">DATA_ECO_MASTER_RECORD</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">ECO Master Record</data><data key="node_acronym">ECO Master</data><data key="node_domain">Debt &amp; External Collections</data><data key="node_description">Logical ECO record structure on which undeliverable pre-offset notices and AWG status/address information are recorded and queried.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Public policy calls this ECO Master or ECO Master File. Exact physical identity or containment relationship with the separately cataloged External Collection Operation Data File is unresolved.</data></node><node id="DATA_EDCS_FOLDER_NUMBER"><data key="node_entity_id">DATA_EDCS_FOLDER_NUMBER</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EDCS Folder Number</data><data key="node_acronym">EDCS Folder Number</data><data key="node_domain">Disability / Case Identity</data><data key="node_description">Unique identifying number assigned to an electronic disability case when the Field Office creates the case in EDCS.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS says the number is unique to the case and appears on the EDCS routing form.</data></node><node id="DATA_EDCS_UAT_ALERT"><data key="node_entity_id">DATA_EDCS_UAT_ALERT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">EDCS Update-After-Transfer Alert</data><data key="node_acronym">UAT Alert</data><data key="node_domain">Disability / Workflow</data><data key="node_description">EDCS alert used to notify the DDS or other office holding jurisdiction of a post-transfer change, including claimant address changes.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current disability policy explicitly calls the address-change notification a UAT Alert; no transport/protocol is inferred.</data></node><node id="DATA_EDIB_ADDR_CHANGE_REPORT"><data key="node_entity_id">DATA_EDIB_ADDR_CHANGE_REPORT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">eDIB Post-Adjudicative Address Change Report</data><data key="node_domain">Disability / Address Provenance / Electronic Case Records</data><data key="node_description">Post-adjudicative report of a claimant or beneficiary change of address maintained within the Electronic Disability Claim File record set.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0320 explicitly lists reports of changes of address among post-adjudicative actions entered into computer processes. This record is not treated as proof of an automatic MBR, SSR, Numident, or PI/PERSON update.</data></node><node id="DATA_EDIB_EMSG_SELECTION"><data key="node_entity_id">DATA_EDIB_EMSG_SELECTION</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eDIB Electronic Messaging Selection</data><data key="node_domain">Disability / Customer Communications</data><data key="node_description">Opt-in or opt-out selection for electronic messaging maintained in the eDIB Claim File.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Added to the 2026 modified SORN; implementation/user-interface details are not public.</data></node><node id="DATA_EDIB_PROVIDER_CREDENTIAL"><data key="node_entity_id">DATA_EDIB_PROVIDER_CREDENTIAL</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">eDIB Medical Provider Credential Record</data><data key="node_domain">Disability / Medical Evidence / Provider Identity</data><data key="node_description">Medical examiner/provider identifying and credential information maintained in eDIB, including address, TIN, medical license number and license expiration date.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The SORN establishes record content, not the physical provider-master database or synchronization mechanism.</data></node><node id="DATA_EFI_DOWNLOAD"><data key="node_entity_id">DATA_EFI_DOWNLOAD</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Electronic Folder Interface Download</data><data key="node_acronym">EFI Download</data><data key="node_domain">Disability / Integration</data><data key="node_description">Per-claim electronic download created by EDCS containing basic claimant/claim data and detailed disability-report data for DDS receipt processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Current DDS TOC retains EFI Download. Detailed field/payload description comes from older base instructions; no protocol is inferred.</data></node><node id="DATA_EFW2_EMPLOYER_DELIVERY_ADDRESS"><data key="node_entity_id">DATA_EFW2_EMPLOYER_DELIVERY_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EFW2 RE Employer Delivery Address</data><data key="node_acronym">Employer Delivery Address</data><data key="node_domain">Earnings / Employer / Address Provenance</data><data key="node_description">Employer delivery address in the EFW2 RE Employer record; SSA states it is required for electronic submissions starting with tax year 2025.</data><data key="node_observed_status">observed_current_required_field</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">Submissions are returned when required RE employer information is blank.</data></node><node id="DATA_EMPLOYER_SIGNATURE_PIN"><data key="node_entity_id">DATA_EMPLOYER_SIGNATURE_PIN</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Employer Signature PIN</data><data key="node_acronym">Employer Signature PIN</data><data key="node_domain">Earnings / Employer / Identity and Access</data><data key="node_description">Planned annually issued PIN that organizations may use to electronically authorize wage submissions through BSO.</data><data key="node_observed_status">planned_december_2026</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Opt-in for employers in 2026 per current SSA employer guidance; not modeled as currently active.</data></node><node id="DATA_ENUM_ACCURACY"><data key="node_entity_id">DATA_ENUM_ACCURACY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Data for Enumeration Accuracy</data><data key="node_acronym">Enumeration Accuracy</data><data key="node_domain">Enumeration / Quality / Open Data</data><data key="node_description">Public SSA dataset reporting accuracy rates from sampled completed enumeration actions, covering EAB, in-person/local-office or card-center applications, and EAE.</data><data key="node_observed_status">observed_public_historical_series</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-325. Published/open-data series currently contains historical enumeration-quality results; page states new studies will be added if conducted.</data></node><node id="DATA_ENUM_FEEDBACK_EM"><data key="node_entity_id">DATA_ENUM_FEEDBACK_EM</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Enumeration Feedback Message</data><data key="node_acronym">EM</data><data key="node_domain">Identity &amp; Enumeration / Exceptions</data><data key="node_description">Enumeration exception message generated for certain EAE applications placed in Investigate status.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">EAE POMS says these messages are not listed on the Enumeration MI listing.</data></node><node id="DATA_ENUM_FEEDBACK_EM3"><data key="node_entity_id">DATA_ENUM_FEEDBACK_EM3</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Enumeration Feedback Message 3</data><data key="node_acronym">EM3</data><data key="node_domain">Identity &amp; Enumeration / Exceptions</data><data key="node_description">Enumeration exception message generated for certain EBE applications placed in Investigate status.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">EBE POMS explicitly calls this EM3 and says it is listed on the Enumeration MI listing.</data></node><node id="DATA_ENUM_PROCESSING_TIME"><data key="node_entity_id">DATA_ENUM_PROCESSING_TIME</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Enumeration Processing Time</data><data key="node_acronym">Enumeration Processing Time</data><data key="node_domain">Identity &amp; Enumeration / Public Data</data><data key="node_description">Quarterly national processing-time dataset for SSA-handled original/replacement SSN cards and the non-SSA portion of Enumeration at Birth.</data><data key="node_observed_status">historical_public_data_product_no_longer_updated</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-436. Data cover FY2014-2016; SSA stopped adding data because internet SSN replacement applications were excluded from the measure.</data></node><node id="DATA_EQA_DYNAMIC_REPORTING"><data key="node_entity_id">DATA_EQA_DYNAMIC_REPORTING</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">eQA Dynamic Reporting Dataset</data><data key="node_acronym">eQA Dynamic Reporting</data><data key="node_domain">quality assurance</data><data key="node_description">Dataset used by Electronic Quality Assurance for analytical reporting within the Quality Assurance System.</data><data key="node_observed_status">documented_2018_current_status_unconfirmed</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">2018 QAS PIA explicitly names analytical reporting from the dynamic reporting dataset; current physical implementation not independently established.</data></node><node id="DATA_ERE_EXPERT_AUTH_SSN"><data key="node_entity_id">DATA_ERE_EXPERT_AUTH_SSN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ERE for Experts Expert Authorization SSN</data><data key="node_acronym">Expert Authorization SSN</data><data key="node_domain">Hearings / Identity / Authorization</data><data key="node_description">Expert SSN used to verify that an expert is authorized to access an assigned claimant eFolder.</data><data key="node_observed_status">documented_current_page</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current page says the SSN is used strictly for authentication/authorization and housed only in the restricted Admin Table.</data></node><node id="DATA_ERE_EXPERT_RESUME"><data key="node_entity_id">DATA_ERE_EXPERT_RESUME</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">ERE for Experts Resume Upload</data><data key="node_acronym">Expert Resume Upload</data><data key="node_domain">Hearings / Evidence / Experts</data><data key="node_description">Curriculum vitae/resume document uploaded by an authorized expert through ERE for Experts into an assigned electronic folder.</data><data key="node_observed_status">documented_release_capability</data><data key="node_observed_as_of">2016-12-09</data><data key="node_confidence">5</data><data key="node_notes">Does not establish that the upload is the same physical repository as SORN 60-0014; no such linkage is inferred.</data></node><node id="DATA_ERE_EXPERT_STATUS_REPORT"><data key="node_entity_id">DATA_ERE_EXPERT_STATUS_REPORT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">ERE for Experts Status Report</data><data key="node_acronym">Expert Status Report</data><data key="node_domain">Hearings / Experts / Work Control</data><data key="node_description">Expert-facing status report for assigned cases; documented fields include full claimant SSN and scheduling or service-order information, with later support for both Hearing Office and Appeals Council cases.</data><data key="node_observed_status">observed_current_service_documentation_with_historical_release_lineage</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current service page preserves release descriptions; exact current backing query after CPMS retirement is unresolved.</data></node><node id="DATA_ERPS_ABLE_TITLE_NOTE"><data key="node_entity_id">DATA_ERPS_ABLE_TITLE_NOTE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eRPS ABLE Account Titling Note</data><data key="node_domain">Representative Payee / Financial Management</data><data key="node_description">Account-titling and payee signature-authority details documented in eRPS Relationship Details when payee manages SSA benefits via ABLE account.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_ERPS_BENE_CAPABILITY_NOTE"><data key="node_entity_id">DATA_ERPS_BENE_CAPABILITY_NOTE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">eRPS Bene Capability Determination Note</data><data key="node_acronym">Bene Capability Determination</data><data key="node_domain">Representative Payee / Capability</data><data key="node_description">Named eRPS note type used to record the facts, evidence, and reasoning supporting an adult beneficiary capability determination.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="DATA_ERPS_CONTACT_ADDRESS"><data key="node_entity_id">DATA_ERPS_CONTACT_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eRPS Payee Contact Address</data><data key="node_acronym">Payee Contact Address</data><data key="node_domain">Representative Payee / Address Provenance</data><data key="node_description">Address/contact information recorded for a representative-payee applicant or payee in eRPS; published policy allows an organization address or P.O. Box to substitute in specified privacy circumstances.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Do not interpret this field as necessarily proving the payee’s personal residence or physical location; published eRPS procedure permits substitute contact addresses in specified cases.</data></node><node id="DATA_ERPS_CRIM_WORK"><data key="node_entity_id">DATA_ERPS_CRIM_WORK</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">eRPS Criminal Background Check Work Issues</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">Representative-payee criminal-information work issues documented in eRPS Workload Management and WAC, including VRFCRM, FELONY, CRM202, and PYE202 issue types.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Issue types are preserved as aliases/codes; no database or transport mechanism is inferred.</data></node><node id="DATA_ERPS_EINVER_ISSUE"><data key="node_entity_id">DATA_ERPS_EINVER_ISSUE</data><data key="node_entity_type">work_control_artifact</data><data key="node_canonical_name">eRPS EINVER Issue</data><data key="node_acronym">EINVER</data><data key="node_domain">Representative Payee / Employer Identity</data><data key="node_description">eRPS work issue created when an EIN match is rejected or verification cannot be completed, with a documented five-day tickle in specified cases.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2023-05-23</data><data key="node_confidence">5</data><data key="node_notes">Issue persistence implementation is not publicly identified.</data></node><node id="DATA_ERPS_INDIVIDUAL_ID"><data key="node_entity_id">DATA_ERPS_INDIVIDUAL_ID</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eRPS Individual Payee Identifier</data><data key="node_acronym">Individual Payee SSN</data><data key="node_domain">Representative Payee / Identity</data><data key="node_description">The verified Social Security Number used by eRPS as the unique numeric identifier for an individual representative-payee applicant or payee.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-17</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly states eRPS verifies the applicant SSN before using it as the individual identifier.</data></node><node id="DATA_ERPS_ORG_ID"><data key="node_entity_id">DATA_ERPS_ORG_ID</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">eRPS Organization ID</data><data key="node_domain">Representative Payee / Identity</data><data key="node_description">Unique eRPS identifier for an organizational representative payee, created from the organization physical-location ZIP Code plus a sequence number.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-17</data><data key="node_confidence">5</data><data key="node_notes">The Organization ID is separate from the organization EIN; current POMS requires EIN recording and verification.</data></node><node id="DATA_ERPS_ORG_PHYS_ZIP"><data key="node_entity_id">DATA_ERPS_ORG_PHYS_ZIP</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eRPS Organization Physical Location ZIP Code</data><data key="node_acronym">Organization location ZIP</data><data key="node_domain">Representative Payee / Address Provenance</data><data key="node_description">ZIP Code of an organization’s physical location used by eRPS as an input to the generated Organization ID.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-17</data><data key="node_confidence">5</data><data key="node_notes">This address-derived element functions as an organization-identifier input. It should not be conflated with beneficiary residence, beneficiary mailing address, or necessarily the organization correspondence address.</data></node><node id="DATA_ERPS_PAYEE_ORG_ADDRESS"><data key="node_entity_id">DATA_ERPS_PAYEE_ORG_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eRPS Organizational Payee Address Attribute</data><data key="node_domain">Representative Payee / Address Provenance</data><data key="node_description">Organization address changes may require organization/legend updates without replacing representative payee, depending on ownership and EIN continuity.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_ERPS_REP_PAYEE_APPLICANT_NOTE"><data key="node_entity_id">DATA_ERPS_REP_PAYEE_APPLICANT_NOTE</data><data key="node_entity_type">case_note_type</data><data key="node_canonical_name">eRPS Rep Payee Applicant Note Type</data><data key="node_acronym">Rep Payee Applicant</data><data key="node_domain">Representative Payee / Case Documentation</data><data key="node_description">eRPS note type used through the Make Note screen to document representative-payee applicant interview circumstances, suitability observations, and criminal-history-related notes.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Directly identified in current representative-payee interview policy already retained in the Atlas.</data></node><node id="DATA_ESTOP_SF1184"><data key="node_entity_id">DATA_ESTOP_SF1184</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">E-stop (SF-1184) EFT Reclamation Request</data><data key="node_acronym">SF-1184</data><data key="node_domain">Payments / Treasury Exchange</data><data key="node_description">Automated reclamation request sent by SSA to Treasury for unrecovered direct-deposit payments issued after death.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS describes the E-stop as showing date of death and outstanding post-death payments; Title II E-stop information is displayed in PHUS.</data></node><node id="DATA_EVIEW_CASE_DATA"><data key="node_entity_id">DATA_EVIEW_CASE_DATA</data><data key="node_entity_type">data_view</data><data key="node_canonical_name">eView Case Data Tab</data><data key="node_acronym">Case Data</data><data key="node_domain">Disability / Evidence / Case Data</data><data key="node_description">eView case-data view where limited post-transfer MCS/MSSICS data repropagated by EDCS UAT, including claimant address, is displayed.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS distinguishes Case Data from disability reports: UAT changes appear under Case Data and do not update the disability reports themselves.</data></node><node id="DATA_EVIEW_CASE_STATUS"><data key="node_entity_id">DATA_EVIEW_CASE_STATUS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eView Electronic-Folder Case Status</data><data key="node_acronym">eView Case Status</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">Displayed electronic-folder processing status such as Closed, Pending, Transferred, or Manually Cleared.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS documents status semantics; no separate status repository is inferred.</data></node><node id="DATA_EVIEW_CEF_INDICATOR"><data key="node_entity_id">DATA_EVIEW_CEF_INDICATOR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eView CEF Indicator</data><data key="node_acronym">CEF Indicator</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">Case-selection indicator showing whether the electronic folder is the certified official folder (Y) or whether a paper folder remains official (N).</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical display field; no physical persistence technology inferred.</data></node><node id="DATA_EVIEW_CLIENT_DATES"><data key="node_entity_id">DATA_EVIEW_CLIENT_DATES</data><data key="node_entity_type">data_view</data><data key="node_canonical_name">eView Client Dates</data><data key="node_acronym">Client Dates</data><data key="node_domain">Disability / eFolder</data><data key="node_description">eView Case Information view that shows Internet disability-report submission/propagation status, including dates, form type, and reason when a form did not propagate.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-03-17</data><data key="node_confidence">5</data><data key="node_notes">Presentation/view artifact; physical storage location is not established.</data></node><node id="DATA_EVVE_DEATH_INDICATION"><data key="node_entity_id">DATA_EVVE_DEATH_INDICATION</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EVVE Death Indication</data><data key="node_domain">Identity / Enumeration / Death</data><data key="node_description">EVVE output indicating that a number holder may be deceased, used with allegations and SSA records to resolve evidence or erroneous death data.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">An EVVE indication alone is not modeled as an automatic death update. Current POMS requires comparison and development.</data></node><node id="DATA_EVVE_STATE_FILE_NUMBER"><data key="node_entity_id">DATA_EVVE_STATE_FILE_NUMBER</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EVVE State File Number</data><data key="node_domain">Identity / Enumeration / Vital Records</data><data key="node_description">State file number returned by EVVE and documented in the MCS DW01 remarks when EVVE verifies birth information for a claim.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Returned verification output. It is not modeled as an SSA authoritative vital-record identifier beyond the documented workflow.</data></node><node id="DATA_EVVE_VERIFICATION_RESULT"><data key="node_entity_id">DATA_EVVE_VERIFICATION_RESULT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EVVE Verification Result</data><data key="node_domain">Identity / Enumeration / Vital Records</data><data key="node_description">EVVE result indicating whether submitted birth-certificate data matches a participating state vital-record system.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">EVVE is a verification service, not a certification service. Match/no-match results are documented in SSA claims or enumeration workflows.</data></node><node id="DATA_FDC_3465"><data key="node_entity_id">DATA_FDC_3465</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Hearing Office Average Processing Time Ranking Report - March 2026</data><data key="node_acronym">US-GOV-SSA-3465</data><data key="node_domain">Hearings &amp; Appeals / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3465.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3466"><data key="node_entity_id">DATA_FDC_3466</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Hearing Office Average Processing Time Ranking Report - April 2026</data><data key="node_acronym">US-GOV-SSA-3466</data><data key="node_domain">Hearings &amp; Appeals / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3466.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3467"><data key="node_entity_id">DATA_FDC_3467</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Hearing Office Average Processing Time Ranking Report - May 2026</data><data key="node_acronym">US-GOV-SSA-3467</data><data key="node_domain">Hearings &amp; Appeals / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3467.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3468"><data key="node_entity_id">DATA_FDC_3468</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Hearing Office Average Processing Time Ranking Report - June 2026</data><data key="node_acronym">US-GOV-SSA-3468</data><data key="node_domain">Hearings &amp; Appeals / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3468.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3469"><data key="node_entity_id">DATA_FDC_3469</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Appeals Council Requests for Review - FY 2024</data><data key="node_acronym">US-GOV-SSA-3469</data><data key="node_domain">Appeals Council / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3469.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3470"><data key="node_entity_id">DATA_FDC_3470</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Appeals Council Requests for Review - FY 2025</data><data key="node_acronym">US-GOV-SSA-3470</data><data key="node_domain">Appeals Council / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3470.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3471"><data key="node_entity_id">DATA_FDC_3471</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">National Court Remands - FY 2024</data><data key="node_acronym">US-GOV-SSA-3471</data><data key="node_domain">Litigation / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3471.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3472"><data key="node_entity_id">DATA_FDC_3472</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">National Court Remands - FY 2025</data><data key="node_acronym">US-GOV-SSA-3472</data><data key="node_domain">Litigation / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3472.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3473"><data key="node_entity_id">DATA_FDC_3473</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">National New Court Cases - FY 2024</data><data key="node_acronym">US-GOV-SSA-3473</data><data key="node_domain">Litigation / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3473.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FDC_3474"><data key="node_entity_id">DATA_FDC_3474</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">National New Court Cases - FY 2025</data><data key="node_acronym">US-GOV-SSA-3474</data><data key="node_domain">Litigation / Public Data</data><data key="node_description">Recently cataloged SSA public data asset identified by Federal Data Catalog identifier US-GOV-SSA-3474.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data page lists this asset among recently cataloged data assets; internal production pipeline not inferred.</data></node><node id="DATA_FI_BALANCE_HISTORY"><data key="node_entity_id">DATA_FI_BALANCE_HISTORY</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Financial Institution Historical Account Balance Data</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">Historical account balances and related account-verification information returned through AFI for SSI eligibility and waiver determinations.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data></node><node id="DATA_FI_BANK_STATEMENT_EVIDENCE"><data key="node_entity_id">DATA_FI_BANK_STATEMENT_EVIDENCE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Financial Institution Bank Statement Evidence</data><data key="node_acronym">Bank Statement Evidence</data><data key="node_domain">Title XVI / Financial Verification / Evidence</data><data key="node_description">Bank statements or other qualifying financial-institution records accepted as evidence for SSI financial-resource development under specified conditions.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS permits complete and unaltered bank statements, including files/images submitted electronically through Upload Documents. Alternative evidence does not necessarily eliminate AFI negative searches or later AFI responses.</data></node><node id="DATA_FI_BENEFICIARY_ADDRESS"><data key="node_entity_id">DATA_FI_BENEFICIARY_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Financial-Institution-Furnished Beneficiary Mailing Address</data><data key="node_acronym">FI Mailing Address</data><data key="node_domain">Title II / Address Provenance</data><data key="node_description">Current beneficiary mailing address furnished by a financial institution in response to E3759 or an equivalent locate request.</data><data key="node_observed_status">observed_current_policy_data</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Controlled address-development input. Receipt does not itself imply an automatic master-record update; current policy routes developed address action through authorized post-entitlement processing.</data></node><node id="DATA_FI_LOCATE_MAIL_ADDR"><data key="node_entity_id">DATA_FI_LOCATE_MAIL_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Financial Institution-Supplied Beneficiary Mailing Address</data><data key="node_acronym">FI Locate Address</data><data key="node_domain">Title II / address provenance</data><data key="node_description">Current beneficiary mailing address supplied by the beneficiary financial institution during whereabouts-unknown or undeliverable-mail development.</data><data key="node_observed_status">observed_current_policy_input</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">External address lead that may become a program address after development; not automatic source-to-MBR synchronization.</data></node><node id="DATA_FOREIGN_CARE_OF_MAILING_ADDR"><data key="node_entity_id">DATA_FOREIGN_CARE_OF_MAILING_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Foreign In-Care-Of Beneficiary Mailing Address</data><data key="node_acronym">Foreign C/O Mailing Address</data><data key="node_domain">Title II / International / Address Provenance</data><data key="node_description">Foreign mailing address used in care of a relative or friend when policy conditions are met.</data><data key="node_observed_status">observed_current_policy_attribute</data><data key="node_observed_as_of">2023-12</data><data key="node_confidence">5</data><data key="node_notes">Separate from the beneficiary actual residence address.</data></node><node id="DATA_FO_CONTACT"><data key="node_entity_id">DATA_FO_CONTACT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Field Office Contact Information</data><data key="node_domain">Operations / Office Data</data><data key="node_description">Public quarterly machine-readable field-office locations, contact information, and hours.</data><data key="node_observed_status">current_public_data_product</data><data key="node_observed_as_of">2026-03-09</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1733.</data></node><node id="DATA_FO_VISITORS_AVG"><data key="node_entity_id">DATA_FO_VISITORS_AVG</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Field Office Visitors Daily Average</data><data key="node_acronym">FO Visitors Daily Average</data><data key="node_domain">Customer Service / Public Data</data><data key="node_description">Annual national average daily field-office visitor counts derived from SSA field-office intake activity.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA Open Data covers FY2006 and later. The current documentation says CSR ODS has been used since FY2009; person identifiers enter the intake workflow but the published product is aggregate.</data></node><node id="DATA_FPLP_BYPASS_CODE"><data key="node_entity_id">DATA_FPLP_BYPASS_CODE</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">FPLP Bypass Code</data><data key="node_domain">Payments / Tax Levy</data><data key="node_description">System-generated code placed on the FPLP payment record to tell Fiscal Service not to levy payments that meet exclusion criteria.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="DATA_FPLP_PAYMENT_RECORD"><data key="node_entity_id">DATA_FPLP_PAYMENT_RECORD</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SSA System-Generated FPLP Payment Record</data><data key="node_domain">Payments / Tax Levy</data><data key="node_description">SSA-generated payment record sent to Fiscal Service for Title II disbursement and tax-levy processing; POMS explicitly distinguishes it from the MBR.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="DATA_FPLP_WEEKLY_OFFSET_FILE"><data key="node_entity_id">DATA_FPLP_WEEKLY_OFFSET_FILE</data><data key="node_entity_type">exchange_data</data><data key="node_canonical_name">Fiscal Service Weekly FPLP Offset File to SSA</data><data key="node_domain">External Exchanges / Treasury</data><data key="node_description">Weekly Fiscal Service offset event file sent to SSA central office; SSA posts event information to Payment History Update System; file format and staging unknown.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_FUGFEL"><data key="node_entity_id">DATA_FUGFEL</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Fugitive Felon (FUGFEL)</data><data key="node_acronym">FUGFEL</data><data key="node_domain">Program Integrity / Fugitive Felon</data><data key="node_description">Current cataloged SSA data asset that supports fugitive felon adjudication.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-131. Asset type/topology beyond the catalog description is not inferred.</data></node><node id="DATA_HALE_SECURE_MAIL_ADDR"><data key="node_entity_id">DATA_HALE_SECURE_MAIL_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">HALE Secure Disability-Claim Mailing Address</data><data key="node_acronym">HALE Secure Mailing Address</data><data key="node_domain">Address Provenance / Disability / Privacy</data><data key="node_description">Claimant-provided mailing address that field-office staff verify is secure for disability-claim notices in HALE cases.</data><data key="node_observed_status">observed_current_transaction_attribute</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS requires verification of a secure mailing address but does not establish persistence or automatic propagation to PI, Numident, MBR, or SSR.</data></node><node id="DATA_HAVV_TXN_STATE"><data key="node_entity_id">DATA_HAVV_TXN_STATE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">HAVV Transactions by State Data Collection</data><data key="node_acronym">HAVV Transactions by State</data><data key="node_domain">Identity Verification / Open Data</data><data key="node_description">Public weekly and monthly aggregate data product reporting state Help America Vote Verification transaction results.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-2439; public data cover 2011 forward. Submitted person-level HAVV information is restricted to voter-registration use.</data></node><node id="DATA_HA_APPEALS_ISSUE_TYPE"><data key="node_entity_id">DATA_HA_APPEALS_ISSUE_TYPE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Appeals Issue Type</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Appeals issue type, including disability, non-disability, overpayment, and continuing disability review categories.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HA_ASSIGNED_ALJ"><data key="node_entity_id">DATA_HA_ASSIGNED_ALJ</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Assigned Administrative Law Judge</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Information about the Administrative Law Judge assigned to a case.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HA_ASSIGNED_APPEALS_REVIEWER"><data key="node_entity_id">DATA_HA_ASSIGNED_APPEALS_REVIEWER</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Assigned Appeals Reviewer</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Information about the Administrative Appeals Judge and/or Appeals Officer assigned to the case.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HA_CASE_LOCATION_STAGE"><data key="node_entity_id">DATA_HA_CASE_LOCATION_STAGE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Case Location Stage</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Case location or stage such as pre-hearing, scheduling, hearing, post-hearing, disposition, routing, or transfer.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HA_FILING_DATE"><data key="node_entity_id">DATA_HA_FILING_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Case Filing Date</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Date of filing maintained within the hearings and appeals case-control record boundary.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HA_HEARING_REQUEST_RECEIPT"><data key="node_entity_id">DATA_HA_HEARING_REQUEST_RECEIPT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Case Hearing Request Receipt Date</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Date a request for hearing is received, maintained within the 60-0009 case-control record boundary.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HA_LAST_ACTION_DATE"><data key="node_entity_id">DATA_HA_LAST_ACTION_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Case Last Action and Action Date</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Last action taken on a case and the date of that action within the 60-0009 case-control record boundary.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HA_REQUEST_REVIEW_DATE"><data key="node_entity_id">DATA_HA_REQUEST_REVIEW_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Request-for-Review Date</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Date a request for review is made in the Appeals Council portion of the case-control record.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HA_SCHEDULED_HEARING_DATE"><data key="node_entity_id">DATA_HA_SCHEDULED_HEARING_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Hearings Scheduled Hearing Date</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Scheduled hearing date maintained within the 60-0009 case-control record boundary.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical category of record in SORN 60-0009. Do not infer one-to-one physical storage in HACPS, OAOCPS, ARPS, or another application.</data></node><node id="DATA_HEARING_RECEIPTS_PENDING_HIST"><data key="node_entity_id">DATA_HEARING_RECEIPTS_PENDING_HIST</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">National Hearing Receipts and Closing Pending Data, FY1985-2009</data><data key="node_acronym">Historical Hearing Receipts/Pending</data><data key="node_domain">Hearings / Appeals / Open Data</data><data key="node_description">Historical national dataset of hearing receipts and closing pending for SSA program cases from fiscal years 1985 through 2009.</data><data key="node_observed_status">historical_public_dataset</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1550. SSA says later data are available through OHO beginning FY2010; source notes multiple tools and data warehouses were used during 1985-2009.</data></node><node id="DATA_HEARING_RECORDING"><data key="node_entity_id">DATA_HEARING_RECORDING</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Official Hearing Recording</data><data key="node_domain">Hearings / Record</data><data key="node_description">Verbatim audio recording that constitutes the official record of hearing testimony.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current HALLEX says even video hearings are recorded in audio only.</data></node><node id="DATA_HEARING_REPRESENTATION_HIST"><data key="node_entity_id">DATA_HEARING_REPRESENTATION_HIST</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Representation at Social Security Hearings Data, FY1979-2015</data><data key="node_acronym">Hearing Representation Data</data><data key="node_domain">Hearings / Appeals / Open Data</data><data key="node_description">Historical national dataset showing percentages of OHO hearing claimants represented by attorneys and non-attorney representatives.</data><data key="node_observed_status">historical_public_dataset</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1553; data period FY1979-2015.</data></node><node id="DATA_HEARING_TRANSCRIPT"><data key="node_entity_id">DATA_HEARING_TRANSCRIPT</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Hearing Transcript</data><data key="node_domain">Hearings / Record</data><data key="node_description">Transcript produced from hearing recordings for case-processing and review purposes.</data><data key="node_observed_status">documented_current_capability</data><data key="node_observed_as_of">2025-03-13</data><data key="node_confidence">5</data><data key="node_notes">HeaRT is documented as producing transcripts; transcript creation requirements vary by workload.</data></node><node id="DATA_HIT_ADJUDICATION_REQUEST_WINDOW"><data key="node_entity_id">DATA_HIT_ADJUDICATION_REQUEST_WINDOW</data><data key="node_entity_type">logical_data_element</data><data key="node_canonical_name">HIT Automated Medical Evidence Coverage Window</data><data key="node_domain">Disability / Health IT</data><data key="node_description">Request interval calculated using alleged onset or protective filing for initial claim, prior request date on reconsideration, or 12 months for CDR; periods depend on benefit type.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_HIT_MER"><data key="node_entity_id">DATA_HIT_MER</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">HIT Medical Evidence Record Document</data><data key="node_acronym">HIT MER</data><data key="node_domain">Disability / Medical Evidence</data><data key="node_description">Imaged medical-evidence document produced by MEGAHIT when health-IT medical records are received.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Stored in the electronic folder.</data></node><node id="DATA_HIT_REQUEST"><data key="node_entity_id">DATA_HIT_REQUEST</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">HIT Request Document</data><data key="node_acronym">HIT Request</data><data key="node_domain">Disability / Medical Evidence</data><data key="node_description">Electronic-folder artifact created when MEGAHIT sends a health-IT evidence request.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Contains requested-source/HIE/date-range/request-date information when available.</data></node><node id="DATA_HIT_REQUEST_LIMIT"><data key="node_entity_id">DATA_HIT_REQUEST_LIMIT</data><data key="node_entity_type">logical_control</data><data key="node_canonical_name">HIT User-Triggered Request Limit</data><data key="node_domain">Disability / Health IT</data><data key="node_description">Policy limits user-triggered requests to ten per HIT partner at each adjudication level; physical enforcement mechanism undocumented.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_HIT_RESPONSE"><data key="node_entity_id">DATA_HIT_RESPONSE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">HIT Response Document</data><data key="node_acronym">HIT Response</data><data key="node_domain">Disability / Medical Evidence</data><data key="node_description">Electronic-folder artifact MEGAHIT creates when the HIE returns no response or no medical-record data.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">POMS states MEGAHIT does not generate another request after this outcome.</data></node><node id="DATA_HRS_CONSENT_HISTORY"><data key="node_entity_id">DATA_HRS_CONSENT_HISTORY</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">HRS Cross-Wave Permissions Consent History</data><data key="node_domain">Research / Consent and Administrative Linkage</data><data key="node_description">HRS-derived file tracking whether respondents were asked for SSA linkage consent, granted permission, whether completed consent was sent to SSA, and whether respondents ultimately matched to SSA administrative earnings and/or benefits files.</data><data key="node_observed_status">documented_hrs_derived_data_product</data><data key="node_observed_as_of">2024-05-24</data><data key="node_confidence">5</data><data key="node_notes">University of Michigan HRS user guide documents this file. It records consent and match status; it is not itself an SSA operational database.</data></node><node id="DATA_HRS_CYBF"><data key="node_entity_id">DATA_HRS_CYBF</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">HRS Respondent Cross-Year Benefits File</data><data key="node_acronym">CYBF</data><data key="node_domain">Title II / Research Extract</data><data key="node_description">Restricted HRS SSA-linked benefit file derived from the Master Beneficiary Record and Payment History Update System.</data><data key="node_observed_status">current_restricted_research_product_april_2026</data><data key="node_observed_as_of">2026-04-01</data><data key="node_confidence">5</data><data key="node_notes">HRS guide says MBR supplies benefit information and PHUS supplies payment information; no physical extraction mechanism is inferred. April 2026 HRS release covers MBR-derived cross-year benefits through 2024 and supersedes prior Respondent Benefits releases.</data></node><node id="DATA_HRS_DER"><data key="node_entity_id">DATA_HRS_DER</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">HRS Detailed Earnings Records</data><data key="node_acronym">DER</data><data key="node_domain">Earnings / Research Extract</data><data key="node_description">Restricted HRS SSA-linked extract derived from the Master Earnings File with respondent-employer-year earnings back to 1978.</data><data key="node_observed_status">current_restricted_research_product_april_2026</data><data key="node_observed_as_of">2026-04-01</data><data key="node_confidence">5</data><data key="node_notes">HRS guide states the DER is a long file and is not top-coded, subject to HRS disclosure masking. It is modeled as an extract, not a separate SSA operational system. Run 83: current official product title is Respondent Cross-Year Detail Earnings; 25,179 consenting respondents, 869,743 respondent/year/employer records, MEF years 1978-2023; April 2026 release.</data></node><node id="DATA_HRS_FORM831"><data key="node_entity_id">DATA_HRS_FORM831</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">HRS SSA Form 831 Respondent Records</data><data key="node_acronym">Form 831</data><data key="node_domain">Disability / Research Extract</data><data key="node_description">Restricted HRS SSA-linked file documenting medically reviewed SSDI and SSI disability applications and initial/reconsideration determinations.</data><data key="node_observed_status">current_restricted_research_product_april_2026</data><data key="node_observed_as_of">2026-04-01</data><data key="node_confidence">5</data><data key="node_notes">HRS and SSA sources document coverage beginning with applications from 1988 onward and note that technical denials and later appeal outcomes are not fully represented. Run 83: current release contains 14,500 records for 4,576 respondents, covering January 1974 through December 2024.</data></node><node id="DATA_HRS_IMPUTED_LIFETIME_EARNINGS"><data key="node_entity_id">DATA_HRS_IMPUTED_LIFETIME_EARNINGS</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">HRS Imputation of Lifetime Earnings Records</data><data key="node_acronym">Imputed Lifetime Earnings</data><data key="node_domain">research / linked administrative data</data><data key="node_description">Restricted HRS respondent-level product containing cumulative lifetime earnings through selected ages using matched SSA earnings where available and imputation/projection otherwise.</data><data key="node_observed_status">current_restricted_research_product_april_2026</data><data key="node_observed_as_of">2026-04-01</data><data key="node_confidence">5</data><data key="node_notes">Latest release April 2026 (Version 2022); derived research product, not an SSA operational master record.</data></node><node id="DATA_HRS_SER"><data key="node_entity_id">DATA_HRS_SER</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">HRS Summary Earnings Records</data><data key="node_acronym">SER</data><data key="node_domain">Earnings / Research Extract</data><data key="node_description">Restricted HRS SSA-linked extract derived from the Master Earnings File with respondent-level annual covered earnings back to 1951.</data><data key="node_observed_status">current_restricted_research_product_april_2026</data><data key="node_observed_as_of">2026-04-01</data><data key="node_confidence">5</data><data key="node_notes">HRS guide states the file is a respondent-level wide file and earnings are top-coded at the OASDI taxable maximum. It is modeled as an extract, not a separate SSA operational system. Run 83: current official product title is Respondent Cross-Year Summary Earnings; 30,531 respondents, MEF years 1951-2023; April 2026 release.</data></node><node id="DATA_HRS_SSI"><data key="node_entity_id">DATA_HRS_SSI</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">HRS Supplemental Security Income File</data><data key="node_acronym">HRS SSI</data><data key="node_domain">Title XVI / Research Extract</data><data key="node_description">Restricted HRS SSA-linked file derived from the Supplemental Security Record containing SSI eligibility periods and monthly benefit information.</data><data key="node_observed_status">current_restricted_research_product_april_2026</data><data key="node_observed_as_of">2026-04-01</data><data key="node_confidence">5</data><data key="node_notes">HRS guide documents SSI information beginning in 1974. It is modeled as a research extract, not as the operational SSR itself. April 2026 HRS release covers SSI benefit information for 4,700 respondents through December 2024.</data></node><node id="DATA_HRS_SS_WEIGHTS"><data key="node_entity_id">DATA_HRS_SS_WEIGHTS</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">HRS Cross-Wave Social Security Weights</data><data key="node_acronym">Social Security Weights</data><data key="node_domain">research / linked administrative data</data><data key="node_description">Restricted HRS cross-wave weights product supporting analysis of respondents with linked SSA administrative records.</data><data key="node_observed_status">current_restricted_research_product_february_2024</data><data key="node_observed_as_of">2024-02-28</data><data key="node_confidence">5</data><data key="node_notes">Replaces earlier Social Security weights products and is distributed with benefits, summary earnings, and detail earnings respondent datasets.</data></node><node id="DATA_IAA_PACKAGE"><data key="node_entity_id">DATA_IAA_PACKAGE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Interagency Agreement Package</data><data key="node_acronym">IAA Package</data><data key="node_domain">Data Exchange / Governance / Interagency</data><data key="node_description">SSA-defined package used when a Federal agency agrees to perform reimbursable work for SSA; the package includes Form SSA-429, an administrative agreement, and an Office of the General Counsel clearance memorandum.</data><data key="node_observed_status">observed_current_glossary</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Package composition is defined by SSA Data Exchange glossary; no workflow system or repository is inferred.</data></node><node id="DATA_IAPPEALS_CLAIMANT_MAILING_ZIP"><data key="node_entity_id">DATA_IAPPEALS_CLAIMANT_MAILING_ZIP</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">iAppeals Claimant Mailing ZIP or Postal Code</data><data key="node_acronym">Mailing ZIP</data><data key="node_domain">Hearings &amp; Appeals / Digital Intake / Address Provenance</data><data key="node_description">Claimant mailing ZIP/postal-code input used by iAppeals for field-office routing and coversheet office selection for applicable appeals.</data><data key="node_observed_status">observed_current_routing_attribute</data><data key="node_observed_as_of">2025-12-02</data><data key="node_confidence">5</data><data key="node_notes">Treated as transaction/routing data; no automatic MBR/SSR update path is established.</data></node><node id="DATA_IAPPEALS_COVERSHEET_PAGE"><data key="node_entity_id">DATA_IAPPEALS_COVERSHEET_PAGE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">iAppeals Coversheet Page</data><data key="node_acronym">Coversheet</data><data key="node_domain">Hearings &amp; Appeals / Digital Intake / Address</data><data key="node_description">Post-submission coversheet containing the BNC, claimant and Internet-user contact information, and a local field-office address derived from the claimant mailing ZIP code.</data><data key="node_observed_status">observed_current_transaction_artifact</data><data key="node_observed_as_of">2025-12-02</data><data key="node_confidence">5</data><data key="node_notes">The local FO address is routing/output data, not a claimant master address.</data></node><node id="DATA_IAPPEALS_RECEIPT_PAGE"><data key="node_entity_id">DATA_IAPPEALS_RECEIPT_PAGE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">iAppeals Receipt Page</data><data key="node_acronym">Receipt Page</data><data key="node_domain">Hearings &amp; Appeals / Digital Intake</data><data key="node_description">Post-submission receipt containing submission date, time, and a summary of information supplied on the appeal forms.</data><data key="node_observed_status">observed_current_transaction_artifact</data><data key="node_observed_as_of">2025-12-02</data><data key="node_confidence">5</data><data key="node_notes">User prints or saves the receipt; backend storage is not asserted.</data></node><node id="DATA_IAPPEALS_REENTRY_NUMBER"><data key="node_entity_id">DATA_IAPPEALS_REENTRY_NUMBER</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">iAppeals Reentry Number</data><data key="node_acronym">Reentry Number</data><data key="node_domain">Hearings &amp; Appeals / Digital Intake</data><data key="node_description">Reentry token issued by iAppeals so an Internet user can resume an unfinished appeal submission; the user must restart if not submitted within 65 days of issuance.</data><data key="node_observed_status">observed_current_transaction_artifact</data><data key="node_observed_as_of">2025-12-02</data><data key="node_confidence">5</data><data key="node_notes">Persistence implementation is not stated publicly.</data></node><node id="DATA_IAPPT_MAILING_ADDRESS"><data key="node_entity_id">DATA_IAPPT_MAILING_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">iAppointment Mailing Address</data><data key="node_acronym">iAppt Mailing Address</data><data key="node_domain">Address Provenance / Appointment Scheduling</data><data key="node_description">Mailing address supplied in iAppointment as required appointment-intake information.</data><data key="node_observed_status">observed_current_unverified_intake_attribute</data><data key="node_observed_as_of">2026-06-26</data><data key="node_confidence">5</data><data key="node_notes">Current policy identifies this as claimant-provided iAppt data. Existing policy states unverified iAppt data does not automatically correct Person Information or Numident.</data></node><node id="DATA_IMRC_APPLICATION_VOLUMES"><data key="node_entity_id">DATA_IMRC_APPLICATION_VOLUMES</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Internet Medicare Replacement Card Application Volumes</data><data key="node_acronym">IMRC Application Volumes</data><data key="node_domain">Medicare / Digital Service / Public Data</data><data key="node_description">Monthly national volume dataset for Internet Medicare Replacement Card transactions.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA Open Data covers FY2008 and later. Front-end counts are stored nightly in Electronic Services ODS, then moved the next day to an unnamed Data Warehouse.</data></node><node id="DATA_IRMAA_PROOF_STATUS"><data key="node_entity_id">DATA_IRMAA_PROOF_STATUS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">IRMAA Proof Status</data><data key="node_acronym">Proof Status</data><data key="node_domain">Medicare / IRMAA / Evidence</data><data key="node_description">IRMAA proof-status value used in current policy, including PENDING, PROVEN, and NOT PROVEN states.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_IRS_ACCOUNT_TRANSCRIPT"><data key="node_entity_id">DATA_IRS_ACCOUNT_TRANSCRIPT</data><data key="node_entity_type">external_data_product</data><data key="node_canonical_name">IRS Account Transcript for SSA</data><data key="node_acronym">Account Transcript</data><data key="node_domain">Earnings / IRS / External Evidence</data><data key="node_description">IRS transcript that provides account financial status, filing/assessment transaction information, and related dates for SSA tax-information development.</data><data key="node_observed_status">observed_current_external_evidence</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says applicable transcripts are generally available for the current and prior three years.</data></node><node id="DATA_IRS_RETURN_TRANSCRIPT"><data key="node_entity_id">DATA_IRS_RETURN_TRANSCRIPT</data><data key="node_entity_type">external_data_product</data><data key="node_canonical_name">IRS Return Transcript for SSA</data><data key="node_acronym">Return Transcript</data><data key="node_domain">Earnings / IRS / External Evidence</data><data key="node_description">IRS transcript containing most line items from a filed tax return, used in response to SSA written tax-information requests when appropriate.</data><data key="node_observed_status">observed_current_external_evidence</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Current POMS notes that filing date is not shown on the Return Transcript.</data></node><node id="DATA_IRS_STATEMENT_MAIL_ADDR"><data key="node_entity_id">DATA_IRS_STATEMENT_MAIL_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">IRS-Sourced Social Security Statement Mailing Address</data><data key="node_acronym">IRS Statement Address</data><data key="node_domain">Address Provenance / Social Security Statement</data><data key="node_description">Taxpayer mailing address obtained from the IRS Individual Master File for automatic Social Security Statement issuance.</data><data key="node_observed_status">observed_current_controlled_use</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Authorized for Statement mailing under 26 U.S.C. 6103(m)(7). Current SSA policy documents PEBES procurement/use but no automatic update from this address into Person, Numident, MBR, or SSR.</data></node><node id="DATA_IRS_TAX_REQUEST_TEMPLATE"><data key="node_entity_id">DATA_IRS_TAX_REQUEST_TEMPLATE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA IRS Tax Information Request Template</data><data key="node_acronym">IRS Request Template</data><data key="node_domain">Earnings / IRS / External Exchange</data><data key="node_description">Two-part SSA written request consisting of a cover letter and request-template page used to request specified IRS forms, schedules, or tax information.</data><data key="node_observed_status">observed_current_form_artifact</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">POMS requires SSA letterhead/signature and specified taxpayer/request details.</data></node><node id="DATA_IRS_TAX_REQUEST_TP_ADDRESS"><data key="node_entity_id">DATA_IRS_TAX_REQUEST_TP_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">IRS Tax Request Taxpayer Address</data><data key="node_acronym">Taxpayer Address on IRS Request</data><data key="node_domain">Earnings / IRS / Address Provenance</data><data key="node_description">Taxpayer address included by SSA on the written IRS tax-information request template when available.</data><data key="node_observed_status">observed_current_outbound_attribute</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">This is SSA-to-IRS request data and is not evidence of an IRS-derived address updating SSA master records.</data></node><node id="DATA_IRS_TOP_WEEKLY_TAX_DEBT_FILE"><data key="node_entity_id">DATA_IRS_TOP_WEEKLY_TAX_DEBT_FILE</data><data key="node_entity_type">exchange_data</data><data key="node_canonical_name">IRS Weekly Delinquent Tax Debt Submission to Treasury TOP</data><data key="node_domain">External Exchanges / Treasury</data><data key="node_description">Weekly IRS tax debt file submitted to Fiscal Service for TOP matching and updates to debtor database; carries tax-debt identifier and status, format and transport undisclosed.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_ISSNRC_APP_VOLUMES"><data key="node_entity_id">DATA_ISSNRC_APP_VOLUMES</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Internet SSN Replacement Card Application Volumes</data><data key="node_acronym">iSSNRC Application Volumes</data><data key="node_domain">Enumeration; Open Data</data><data key="node_description">Monthly national public dataset reporting internet and total Social Security number replacement-card application volumes from fiscal year 2016 forward.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1735; public data updated 2026-04-10.</data></node><node id="DATA_ITS_BANK_ADDRESS"><data key="node_entity_id">DATA_ITS_BANK_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ITS.gov Bank Address</data><data key="node_acronym">ITS Bank Address</data><data key="node_domain">Payments / International Direct Deposit / Financial Institution</data><data key="node_description">Financial-institution address entered into Treasury ITS.gov as part of documented international direct-deposit processing.</data><data key="node_observed_status">observed_current_policy_attribute</data><data key="node_observed_as_of">2026-07-20</data><data key="node_confidence">5</data><data key="node_notes">Institution address, not beneficiary residence. Public policy does not identify persistence duration or physical ITS.gov storage schema.</data></node><node id="DATA_ITS_BENEFICIARY_ADDRESS"><data key="node_entity_id">DATA_ITS_BENEFICIARY_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ITS.gov Beneficiary Address</data><data key="node_acronym">ITS Beneficiary Address</data><data key="node_domain">Payments / International Direct Deposit / Address Provenance</data><data key="node_description">Beneficiary address entered into Treasury ITS.gov as part of international direct-deposit enrollment or update processing.</data><data key="node_observed_status">observed_current_policy_attribute</data><data key="node_observed_as_of">2026-07-20</data><data key="node_confidence">5</data><data key="node_notes">Country-specific POMS documents this as required ITS.gov data. No source establishes that the ITS.gov beneficiary address itself overwrites the MBR address.</data></node><node id="DATA_LAWFUL_PRESENCE_PROOF"><data key="node_entity_id">DATA_LAWFUL_PRESENCE_PROOF</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSA Lawful Presence Proof and Evidence Coding</data><data key="node_acronym">Lawful Presence Proof</data><data key="node_domain">Person / Claims / Immigration</data><data key="node_description">Claims-record evidence/proof coding used to establish U.S. lawful presence for benefit payment when policy conditions are satisfied.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current policy accepts qualifying MBR/SSR/cleared MCS/MSSICS evidence; Numident coding alone is expressly not acceptable proof.</data></node><node id="DATA_LOCKBOX_IRN"><data key="node_entity_id">DATA_LOCKBOX_IRN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Lockbox Individual Reference Number</data><data key="node_acronym">IRN</data><data key="node_domain">Payments / Debt / Treasury Lockbox</data><data key="node_description">Unique lockbox remittance reference generated by U.S. Bank and sent to Treasury CIR; the final eight digits appear with an LCK prefix in SSA lockbox detail and DMS receipt-number fields.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">This is a transaction identifier, not a person identifier.</data></node><node id="DATA_MANUAL_DEEMING_LIST"><data key="node_entity_id">DATA_MANUAL_DEEMING_LIST</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Manual Deeming List</data><data key="node_domain">Title XVI / Deeming</data><data key="node_description">Annual read-only list of SSI records requiring manual deemed-income computation by field offices.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07</data><data key="node_confidence">5</data><data key="node_notes">POMS says the list is produced in October, placed on the Deeming Listings Page, updated annually, and is not controlled by SUMS/MCAS MI Central; no SSR diary identifies these cases.</data></node><node id="DATA_MAPS_IRS_AGENCY_DATA"><data key="node_entity_id">DATA_MAPS_IRS_AGENCY_DATA</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">MAPS IRS Agency Data</data><data key="node_acronym">IRS agency data</data><data key="node_domain">Medicare / Extra Help / IRS</data><data key="node_description">IRS-derived agency information used by MAPS to develop Extra Help income and resource issues from information-return reporting.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">IRS is the reporting conduit, not necessarily the originator of the underlying payment; payer/source verification may be required.</data></node><node id="DATA_MAPS_MAILING_ADDRESS"><data key="node_entity_id">DATA_MAPS_MAILING_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Extra Help Application Mailing Address in MAPS</data><data key="node_acronym">MAPS Mailing Address</data><data key="node_domain">Medicare / Extra Help / Address</data><data key="node_description">Claimant mailing address collected in MAPS for Extra Help correspondence and change-of-address development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy establishes conditional downstream MBR/SSR update procedures, not an automatic MAPS master-address synchronization.</data></node><node id="DATA_MASS_LOSS_SPECIAL_NONRECEIPT_FILE"><data key="node_entity_id">DATA_MASS_LOSS_SPECIAL_NONRECEIPT_FILE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Mass Loss Special Nonreceipt Payment File</data><data key="node_domain">Payments / Treasury / Nonreceipt</data><data key="node_description">Special nonreceipt payment file used in central-office mass-loss processing so Treasury can issue replacement checks to affected individuals without separate field input.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source establishes the file role but not its physical format, transport, or persistence.</data></node><node id="DATA_MA_ADDRESS_VERIFY_FORM"><data key="node_entity_id">DATA_MA_ADDRESS_VERIFY_FORM</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Medicare Advantage Address Verification Form (POMS Exhibit)</data><data key="node_acronym">MA Address Verification Form</data><data key="node_domain">Title II; Medicare; Address</data><data key="node_description">POMS exhibit used to capture mailing address, permanent residence address, county of residence, phone number, and reason mailing and residence addresses differ.</data><data key="node_observed_status">observed_current_policy_exhibit</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The exhibit is not assigned a formal SSA form number in the cited POMS.</data></node><node id="DATA_MBR_ADDR_UPDATED"><data key="node_entity_id">DATA_MBR_ADDR_UPDATED</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Address Updated Date</data><data key="node_acronym">ADDR Updated</data><data key="node_domain">Title II / Address / Record Control</data><data key="node_description">Date/control value on the Master Beneficiary Record indicating when the MBR address was updated, used to compare address recency with the SSR.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS uses the label ADDR Updated when comparing MBR address recency with the SSR ACD. No physical field implementation is inferred.</data></node><node id="DATA_MBR_DD_INDICATOR"><data key="node_entity_id">DATA_MBR_DD_INDICATOR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Direct Deposit Indicator</data><data key="node_acronym">Direct Deposit Indicator</data><data key="node_domain">Title II / Payments / Resource Development</data><data key="node_description">Master Beneficiary Record indicator whose presence is a lead to develop a financial account during an SSI redetermination.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS documents the indicator as a development lead; internal field code is not identified.</data></node><node id="DATA_MBR_FUT_PENSION_ENT"><data key="node_entity_id">DATA_MBR_FUT_PENSION_ENT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Future Pension Entitlement Date</data><data key="node_domain">Title II / Historical GPO</data><data key="node_description">MBR date used by RETAP to generate an alert a month before expected noncovered pension entitlement; retained legacy rule for pre-2024 months.</data><data key="node_observed_status">legacy_pre_2024_processing</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_MBR_LAW_PRS"><data key="node_entity_id">DATA_MBR_LAW_PRS</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">MBR Lawful Presence Data Line</data><data key="node_acronym">LAW PRS</data><data key="node_domain">Title II / Person / Immigration</data><data key="node_description">Master Beneficiary Record data line containing lawful-presence proof/status information used under current policy to establish previously proven lawful presence when specified criteria are met.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Physical field/table implementation is not disclosed.</data></node><node id="DATA_MBR_MAILING_ADDRESS"><data key="node_entity_id">DATA_MBR_MAILING_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Master Beneficiary Record Mailing Address</data><data key="node_acronym">MBR Mailing Address</data><data key="node_domain">Title II; Address</data><data key="node_description">Mailing-address attribute maintained on the Master Beneficiary Record and used for Title II correspondence and post-entitlement address processing.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Distinguished from residence geography such as SCC; an MBR mailing address may differ from actual residence.</data></node><node id="DATA_MBR_MNUP_SPECIAL_MESSAGE"><data key="node_entity_id">DATA_MBR_MNUP_SPECIAL_MESSAGE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR MNUP Foreign Change-of-Address Special Message</data><data key="node_acronym">MNUP COA Special Message</data><data key="node_domain">Title II / Address Provenance</data><data key="node_description">Special message posted to the MBR documenting an MNUP foreign change-of-address case and the handling OEIO/FO identifiers.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">The message is explicit; it is not modeled as the address field itself.</data></node><node id="DATA_MBR_MONTHLY_AWARD_ACTION_FILE"><data key="node_entity_id">DATA_MBR_MONTHLY_AWARD_ACTION_FILE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">MBR Monthly Award Action File</data><data key="node_acronym">MBR Monthly Award File</data><data key="node_domain">Actuarial / Statistical Production</data><data key="node_description">Monthly file of OASDI award actions created when the Master Beneficiary Record is updated.</data><data key="node_observed_status">documented_statistical_pipeline_2025</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes">SSA Appendix B methodology states a record of award actions is created each month when MBR is updated.</data></node><node id="DATA_MBR_RESIDENCE_SCC"><data key="node_entity_id">DATA_MBR_RESIDENCE_SCC</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR State and County Code of Residence</data><data key="node_acronym">SCC</data><data key="node_domain">Title II; Address; Medicare</data><data key="node_description">State and county code maintained on the MBR to represent the beneficiary residence jurisdiction when residence differs from mailing address.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">CMS uses the SCC to verify Medicare Advantage service-area residence; do not treat SCC as a full residence-address field.</data></node><node id="DATA_MBR_SID_LINE"><data key="node_entity_id">DATA_MBR_SID_LINE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR State Identification Code Line</data><data key="node_acronym">SID line</data><data key="node_domain">Medicare / State Buy-In / MBR</data><data key="node_description">Master Beneficiary Record line containing state buy-in status information used in the SSR-MBR state buy-in interface.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS names the SID line and SISC values; modeled as an MBR data element, not a separate repository.</data></node><node id="DATA_MBR_SPA_LINE"><data key="node_entity_id">DATA_MBR_SPA_LINE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Special Payment Amount Line</data><data key="node_acronym">SPA</data><data key="node_domain">Title II / Payments / Master Record</data><data key="node_description">Master Beneficiary Record line on which certain returned-check amounts issued after death can be placed when benefits are suspended.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a logical MBR data element; physical record layout is not inferred.</data></node><node id="DATA_MBR_STUDENT_ENTITLEMENT"><data key="node_entity_id">DATA_MBR_STUDENT_ENTITLEMENT</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">MBR Student Entitlement Data</data><data key="node_acronym">Student Data</data><data key="node_domain">Title II / Student Benefits / MBR</data><data key="node_description">Logical student-benefit data posted to the Master Beneficiary Record to support continuation or termination of Title II child benefits after age 18.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS explicitly says student data must be posted to MBR; this logical structure does not assert an undocumented physical segment name.</data></node><node id="DATA_MBR_THIRD_PARTY_LINE"><data key="node_entity_id">DATA_MBR_THIRD_PARTY_LINE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Third-Party Line</data><data key="node_acronym">Third-Party line</data><data key="node_domain">Medicare / State Buy-In / MBR</data><data key="node_description">Master Beneficiary Record line updated through the Third-Party System to reflect state Medicare buy-in/premium-payment status.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents delayed TPS-to-MBR updating after correction of the SID line.</data></node><node id="DATA_MBR_TOTALIZATION_CODES"><data key="node_entity_id">DATA_MBR_TOTALIZATION_CODES</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">MBR Totalization Codes</data><data key="node_acronym">Totalization Codes</data><data key="node_domain">Title II / International / MBR</data><data key="node_description">Systems-generated Title II codes posted to the Master Beneficiary Record from MCS entries for U.S. Totalization claims.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Physical field layout is not disclosed in public POMS.</data></node><node id="DATA_MCS_IAPPEALS_CONTACT_ALERT"><data key="node_entity_id">DATA_MCS_IAPPEALS_CONTACT_ALERT</data><data key="node_entity_type">work_control_artifact</data><data key="node_canonical_name">MCS iAppeals Contact-Information Discrepancy Alert</data><data key="node_acronym">Contact Discrepancy Alert</data><data key="node_domain">Title II / Appeals / Work Control / Address Provenance</data><data key="node_description">MCS alert shown to a technician when contact information imported from iAppeals differs from contact information already in MCS.</data><data key="node_observed_status">observed_current_work_control</data><data key="node_observed_as_of">2025-12-02</data><data key="node_confidence">5</data><data key="node_notes">This is a discrepancy alert, not evidence of automatic overwrite of MCS contact data.</data></node><node id="DATA_MGD"><data key="node_entity_id">DATA_MGD</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Master Geographic and Demographic Data File</data><data key="node_acronym">MGD</data><data key="node_domain">Research / Statistics / Earnings</data><data key="node_description">Annual worker-level geographic/demographic data files containing state of residence, year of birth, and sex for nearly all workers whose earnings records were filed with IRS for the tax year.</data><data key="node_observed_status">research_data_files_2014_2021</data><data key="node_observed_as_of">2024-12</data><data key="node_confidence">5</data><data key="node_notes">ORES had assembled files for tax years 2014-2021. The files do not contain earnings type or amount; the address information is the only data extracted from tax records for geographic assignment.</data></node><node id="DATA_MMCR"><data key="node_entity_id">DATA_MMCR</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Miscellaneous Money Control Record</data><data key="node_acronym">MMCR</data><data key="node_domain">Payments / Field Office / Records Control</data><data key="node_description">Separate control record used for each benefit check mailed to a field office when the field-office address serves as a claimant mailing address.</data><data key="node_observed_status">observed_current_policy_artifact</data><data key="node_observed_as_of">2026-09-18</data><data key="node_confidence">5</data><data key="node_notes">POMS also uses MMRC once in the text; the recurring acronym is MMCR. Control records can be retained in NDRed or a secure office holding file for 3 years after distribution.</data></node><node id="DATA_MNUP_HIST_SUMMARY"><data key="node_entity_id">DATA_MNUP_HIST_SUMMARY</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">MNUP Historical Summary-Level Data</data><data key="node_acronym">MNUP Historical Summary</data><data key="node_domain">Title II / Program Integrity</data><data key="node_description">Historical summary-level data maintained by the MNUP website after interview information is entered; completed cases remain listed as complete under older still-active website guidance.</data><data key="node_observed_status">current_workflow_with_older_active_policy_detail</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Persistence is documented, but retention duration and physical store are not.</data></node><node id="DATA_MNUP_ONLINE_WORKSHEET"><data key="node_entity_id">DATA_MNUP_ONLINE_WORKSHEET</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">MNUP Online Interview Worksheet</data><data key="node_acronym">MNUP Online Worksheet</data><data key="node_domain">Title II / Program Integrity</data><data key="node_description">Online worksheet on the MNUP website into which staff transcribe interview information and document case findings.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Physical storage and retention schedule are not published.</data></node><node id="DATA_MNUP_RESIDENCE_ADDRESS"><data key="node_entity_id">DATA_MNUP_RESIDENCE_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MNUP Developed Residence Address</data><data key="node_acronym">MNUP Residence Address</data><data key="node_domain">Title II / Address Provenance</data><data key="node_description">Residence address developed during MNUP when SSA initially has only a mailing address or learns the beneficiary resides at another location.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Address can be documented on MNUP worksheet; no automatic MBR write is inferred for domestic development.</data></node><node id="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="node_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot Flattened Time Series</data><data key="node_acronym">MSS Flattened Time Series</data><data key="node_domain">Statistics / Publications / Open Data</data><data key="node_description">Beta JSON and CSV time-series files concatenating every Monthly Statistical Snapshot table from December 2012 through the latest edition.</data><data key="node_observed_status">current_beta_public_data_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SSA regenerates files monthly from the full archive, incorporating post-release corrections; FDC ID US-GOV-SSA-3413.</data></node><node id="DATA_MONTHLY_STAT_SNAPSHOT"><data key="node_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot</data><data key="node_domain">Statistics / Publications</data><data key="node_description">Monthly SSA statistical publication covering Social Security and SSI beneficiary counts, benefits, and payments.</data><data key="node_observed_status">current_public_data_product</data><data key="node_observed_as_of">2026-09</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-3413; August 2026 edition released September 2026.</data></node><node id="DATA_MRPF_ADDRESS"><data key="node_entity_id">DATA_MRPF_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Master Representative Payee File Address Attributes</data><data key="node_acronym">MRPF Address</data><data key="node_domain">Address Provenance / Representative Payee</data><data key="node_description">Addresses maintained in the Master Representative Payee File for representative payees, payee applicants, beneficiaries or recipients, and certain organizations.</data><data key="node_observed_status">observed_current_record_category</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0222 lists address among record categories and permits use of residence stability/contact information in payee suitability and program administration. No automatic write-back to MBR, SSR, Numident, or PI/PERSON is documented.</data></node><node id="DATA_MSP_L447_MAILINGS"><data key="node_entity_id">DATA_MSP_L447_MAILINGS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">L447 Notice Mailings by ZIP Code</data><data key="node_acronym">L447 Mailings</data><data key="node_domain">Medicare / Open Data / Outreach</data><data key="node_description">Annual ZIP-code-level counts of L447 notices mailed by SSA.</data><data key="node_observed_status">current_public_data_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">FY2017 onward; ZIP codes with 10 or fewer mailings are suppressed with an asterisk; FDC ID US-GOV-SSA-1848.</data></node><node id="DATA_MSP_L448_MAILINGS"><data key="node_entity_id">DATA_MSP_L448_MAILINGS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">L448 Notice Mailings by ZIP Code</data><data key="node_acronym">L448 Mailings</data><data key="node_domain">Medicare / Open Data / Outreach</data><data key="node_description">Annual ZIP-code-level counts of L448 notices mailed by SSA.</data><data key="node_observed_status">current_public_data_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">FY2017 onward; ZIP codes with 10 or fewer mailings are suppressed with an asterisk; FDC ID US-GOV-SSA-1849.</data></node><node id="DATA_MSP_OUTREACH_FILE"><data key="node_entity_id">DATA_MSP_OUTREACH_FILE</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Medicare Savings Program Outreach Candidate File</data><data key="node_acronym">MSP Outreach File</data><data key="node_domain">Medicare / Low-Income Assistance</data><data key="node_description">System-generated file of Medicare beneficiaries who appear to meet criteria for MSP or Extra Help outreach letters.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Built using MBR, SSR, MAPS, and files from other Federal agencies; physical implementation not published.</data></node><node id="DATA_MYCOA_PENDING_FUTURE_ADDRESS"><data key="node_entity_id">DATA_MYCOA_PENDING_FUTURE_ADDRESS</data><data key="node_entity_type">work_control_artifact</data><data key="node_canonical_name">myCOA Future-Effective Address Change</data><data key="node_acronym">Pending Future COA</data><data key="node_domain">Title II / Address Provenance</data><data key="node_description">A Title II mailing-address change submitted through myCOA with an effective date up to 90 days in the future that remains pending until the appropriate month.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">POMS establishes pending state but does not identify the physical queue/table holding the pending transaction.</data></node><node id="DATA_N8NN_CALL_VOLUME_BUSY"><data key="node_entity_id">DATA_N8NN_CALL_VOLUME_BUSY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">National 800 Number Call Volume and CSR Busy Rate Data</data><data key="node_acronym">N8NN Call Volume / Busy Rate</data><data key="node_domain">Customer Service / Public Data</data><data key="node_description">Monthly national data on National 800 Number calls offered to CSRs, busy calls, and CSR busy rate.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog US-GOV-SSA-324; data file updated 2026-04-17 and covers FY2009 onward.</data></node><node id="DATA_NAPR_PRECEDENTS"><data key="node_entity_id">DATA_NAPR_PRECEDENTS</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Native American Tribal Income and Resource Precedents</data><data key="node_acronym">NAPR Precedents</data><data key="node_domain">Title XVI / Native American Income and Resources</data><data key="node_description">Tribal-program income and resource determinations maintained as precedents and used as guidance for similar SSI cases.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">New precedents and resources have been established and stored in NAPR since August 1, 2022.</data></node><node id="DATA_NBDS"><data key="node_entity_id">DATA_NBDS</data><data key="node_entity_type">research_dataset</data><data key="node_canonical_name">New Beneficiary Data System</data><data key="node_acronym">NBDS</data><data key="node_domain">Research / Administrative Data / Longitudinal</data><data key="node_description">Longitudinal SSA research dataset combining the 1982 New Beneficiary Survey, later administrative records, and the 1991 New Beneficiary Follow-up to study changing circumstances of aged and disabled beneficiaries.</data><data key="node_observed_status">historical_public_use_dataset</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Released as public-use components in 1997; current Federal Data Catalog metadata was inventoried in 2026. Do not infer the operational source systems for administrative fields unless separately documented.</data></node><node id="DATA_NBDS_ADMIN_PUF"><data key="node_entity_id">DATA_NBDS_ADMIN_PUF</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">NBDS Public-Use Administrative Data</data><data key="node_domain">Research / Administrative Data / Public Use</data><data key="node_description">Public-use administrative data for NBDS respondents and spouses, distributed in beneficiary-group files with later update data.</data><data key="node_observed_status">historical_public_use</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA notes an update file covering benefits in December 2000 and earnings in 1991-1999. Federal catalog description also identifies covered earnings, Medicare expenditures, SSI application/payment status, and death dates as NBDS longitudinal measures.</data></node><node id="DATA_NBDS_PUF"><data key="node_entity_id">DATA_NBDS_PUF</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">New Beneficiary Data System Public-Use Files</data><data key="node_domain">Research / Public Use Data</data><data key="node_description">Public-use files released from the New Beneficiary Data System, including NBS, NBF, and administrative-data components.</data><data key="node_observed_status">current_catalog_historical_release</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-3418; dataset modified 1997-03-15 and inventoried 2026-08-26.</data></node><node id="DATA_NBS"><data key="node_entity_id">DATA_NBS</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">National Beneficiary Survey</data><data key="node_acronym">NBS</data><data key="node_domain">Disability / Research Analytics</data><data key="node_description">Survey dataset covering disability beneficiaries and recipients, including work, health and service-use information not available in administrative records.</data><data key="node_observed_status">2023_survey_received_fy2025</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2026 budget says the 2023 NBS survey and restricted-use data file were received in FY2025.</data></node><node id="DATA_NDDSS_DEC"><data key="node_entity_id">DATA_NDDSS_DEC</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">NDDSS Decision Code Field</data><data key="node_acronym">DEC</data><data key="node_domain">DDS Disability Processing</data><data key="node_description">NDDSS/DDSQ field used to expose the disability decision code in the full query response.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_NDDSS_DST"><data key="node_entity_id">DATA_NDDSS_DST</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">NDDSS Clearance Destination Field</data><data key="node_acronym">DST</data><data key="node_domain">DDS Disability Processing</data><data key="node_description">NDDSS/DDSQ field showing clearance destination; an R-prefixed location can indicate Office of Quality Performance review.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_NDDSS_SO"><data key="node_entity_id">DATA_NDDSS_SO</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">NDDSS System Override Field</data><data key="node_acronym">SO</data><data key="node_domain">DDS Disability Processing</data><data key="node_description">NDDSS/DDSQ field controlling transmission of case-movement and decisional data to SSA systems, with documented N, C, D, and Y states.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_NED_DOMESTIC_ADDRESS"><data key="node_entity_id">DATA_NED_DOMESTIC_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">NED Domestic Debtor Address</data><data key="node_acronym">NED Address</data><data key="node_domain">Address Provenance / Debt Collection</data><data key="node_description">Domestic address maintained for a non-entitled debtor in the NED database and made available to ECO through ECO extraction from NED.</data><data key="node_observed_status">observed_current_policy_attribute</data><data key="node_observed_as_of">2017-10-31</data><data key="node_confidence">5</data><data key="node_notes">POMS expressly states that changing this NED address does not interface with or update the MBR.</data></node><node id="DATA_NOTICE_QR_CODE"><data key="node_entity_id">DATA_NOTICE_QR_CODE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Agency Notice Quick Response Code</data><data key="node_acronym">QR Code</data><data key="node_domain">Notices / Digital Content</data><data key="node_description">QR-code artifact embedded in agency notices to connect recipients to online versions of paper enclosures or other approved content.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No database, hosting platform, QR generator product, or transport is inferred beyond the documented internal request/control system.</data></node><node id="DATA_NUMIDENT_ALIEN_REG_NUM"><data key="node_entity_id">DATA_NUMIDENT_ALIEN_REG_NUM</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Alien Registration Number Attribute</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Alien registration number information received on or during processing of an SSN request and maintained in the 60-0058 record environment.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Identity/application attribute. This does not establish an SSA immigration-status master separate from Numident.</data></node><node id="DATA_NUMIDENT_BENEFIT_CLAIM_IND"><data key="node_entity_id">DATA_NUMIDENT_BENEFIT_CLAIM_IND</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Benefit Claim Indicator</data><data key="node_domain">Identity &amp; Enumeration / Claims</data><data key="node_description">Indicator that a person has filed a benefit claim under a particular SSN.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The SORN establishes the indicator, but not which claims application writes it or how it is physically stored.</data></node><node id="DATA_NUMIDENT_CITIZENSHIP_CODE"><data key="node_entity_id">DATA_NUMIDENT_CITIZENSHIP_CODE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Citizenship Code</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Code identifying an SSN holder as a U.S. citizen or identifying the work authorization of a non-citizen.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN category of record. Field encoding and update implementation are not stated.</data></node><node id="DATA_NUMIDENT_DEATH_COMMENTS"><data key="node_entity_id">DATA_NUMIDENT_DEATH_COMMENTS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Death Comments</data><data key="node_acronym">Death Comments</data><data key="node_domain">Identity; Numident; Death</data><data key="node_description">Comments field in the Death Data Numident response used as part of the proof test for verified EDR deaths.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies the text EDR Death Report as part of the verified-EDR combination.</data></node><node id="DATA_NUMIDENT_DNP_MATCH_RESPONSE"><data key="node_entity_id">DATA_NUMIDENT_DNP_MATCH_RESPONSE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Do Not Pay Match Response Code</data><data key="node_domain">Identity / External Verification / Payment Integrity</data><data key="node_description">Numerical match or non-match response concept documented for the Numident-to-Do Not Pay identity-verification design covering submitted name, SSN, and optional date of birth.</data><data key="node_observed_status">final_numident_designation_effective_response_design_from_proposal</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Run 84 incorrectly stated that no final designation notice had been located. Treasury published the final designation April 10, 2026, effective immediately. The numerical response-code mechanics remain sourced to the February proposal; current Treasury product availability is tracked separately.</data></node><node id="DATA_NUMIDENT_EAB_PARENTAGE"><data key="node_entity_id">DATA_NUMIDENT_EAB_PARENTAGE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">EAB Numident Parentage Fields</data><data key="node_domain">Identity / Enumeration / Person Data</data><data key="node_description">EAB-specific Numident iteration indicators and parent-name-at-birth fields, including FMC value 6 and the MNA/FNA fields populated from state vital-statistics birth registration data.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS permits specified EAB Numident data to support certain Title II parent-child determinations. This does not imply automatic propagation of parent attributes to MBR, SSR, eRPS, or other person records.</data></node><node id="DATA_NUMIDENT_EAE_FMC_A"><data key="node_entity_id">DATA_NUMIDENT_EAE_FMC_A</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident EAE Form Code A</data><data key="node_acronym">FMC A</data><data key="node_domain">Identity &amp; Enumeration / Numident</data><data key="node_description">Numident form-code value A indicating that the Numident record was established through Enumeration at Entry.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS says no microfilm/electronic SS-5 exists for fully processed EAE and FMC A appears on Numident.</data></node><node id="DATA_NUMIDENT_EDR_FIELD"><data key="node_entity_id">DATA_NUMIDENT_EDR_FIELD</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Electronic Death Registration Indicator</data><data key="node_acronym">EDR</data><data key="node_domain">Identity; Numident; Death</data><data key="node_description">Numident field indicating Electronic Death Registration status; current POMS uses Y, and treats O as a proven EDR death, in conjunction with other death-proof fields.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">EDR is a provenance/proof indicator on the death-data Numident response, not the I-EDR exchange itself.</data></node><node id="DATA_NUMIDENT_FORM_CODE"><data key="node_entity_id">DATA_NUMIDENT_FORM_CODE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Form Code</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Code identifying the application path associated with SSN issuance or later identifying-information changes, including original issuance and Enumeration at Birth examples.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Generic current SORN field concept. Existing Form Code A for Enumeration at Entry remains separately modeled as a documented code value.</data></node><node id="DATA_NUMIDENT_FRAUD_APP_MAIL_ADDR"><data key="node_entity_id">DATA_NUMIDENT_FRAUD_APP_MAIL_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Suspect/Fraud Application Mailing Address</data><data key="node_domain">Identity &amp; Enumeration / Address Provenance / Program Integrity</data><data key="node_description">Mailing address of a person who filed an SSN application supported by evidence SSA suspects or determines to be fraudulent.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN 60-0058 explicitly limits this mailing-address language to suspect/fraud application records. It is not evidence that Numident is a universal current-residence or benefit-mailing-address master.</data></node><node id="DATA_NUMIDENT_IDN_H"><data key="node_entity_id">DATA_NUMIDENT_IDN_H</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident IDN Code H</data><data key="node_acronym">IDN H</data><data key="node_domain">Identity / Immigration</data><data key="node_description">Numident identity coding referenced in current lawful-presence policy.</data><data key="node_observed_status">observed_current_not_acceptable_lawful_presence_proof</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly says Numident coding is not acceptable evidence of lawful presence for this determination.</data></node><node id="DATA_NUMIDENT_INTERNAL_PROC_REF"><data key="node_entity_id">DATA_NUMIDENT_INTERNAL_PROC_REF</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Internal Processing Reference Number</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Agency internal processing reference number maintained within the 60-0058 record environment and identified as a retrieval key.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical SORN field/identifier. The public notice does not identify a physical column, table, or database technology.</data></node><node id="DATA_NUMIDENT_ITERATION"><data key="node_entity_id">DATA_NUMIDENT_ITERATION</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Numident Record Iteration</data><data key="node_acronym">Numident Iteration</data><data key="node_domain">Identity &amp; Enumeration / Person Record History</data><data key="node_description">A versioned iteration of a number holder record within Numident. Ordinary supported updates create a new iteration appended to the prior iteration; documented keying-error corrections through NCP do not add an iteration.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical record-history structure documented by current POMS; physical storage implementation is not inferred.</data></node><node id="DATA_NUMIDENT_MULTI_SSN_XREF_ATTR"><data key="node_entity_id">DATA_NUMIDENT_MULTI_SSN_XREF_ATTR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Multiple-SSN Cross-Reference Attribute</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Current 60-0058 logical cross-reference information maintained when multiple SSNs have been issued to the same person.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Do not equate this current SORN attribute with the legacy Multiple Social Security Number Cross Reference File unless a source establishes physical continuity.</data></node><node id="DATA_NUMIDENT_PARENT_NAME"><data key="node_entity_id">DATA_NUMIDENT_PARENT_NAME</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Parent Name Field</data><data key="node_acronym">Parent Name</data><data key="node_domain">Identity &amp; Enumeration / Person Relationships</data><data key="node_description">Parent-name attribute maintained on a child number holder’s Numident record.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">When changed, current POMS directs staff to review relevant MBR, SSR, and RPS records and initiate necessary actions.</data></node><node id="DATA_NUMIDENT_POD"><data key="node_entity_id">DATA_NUMIDENT_POD</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Proof of Death</data><data key="node_acronym">POD</data><data key="node_domain">Identity; Numident; Death</data><data key="node_description">Numident proof-of-death field used with SSD, EDR and comments to determine whether death data can serve as preferred proof.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies code P as proven/preferred proof in specified combinations.</data></node><node id="DATA_NUMIDENT_SEX_CODE"><data key="node_entity_id">DATA_NUMIDENT_SEX_CODE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Sex Code</data><data key="node_acronym">Sex Code</data><data key="node_domain">Identity &amp; Enumeration / Person Attributes</data><data key="node_description">Sex-at-birth code maintained on the Numident record and subject to evidence-based correction or update.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directs associated SSA records to be updated when this Numident field is changed; the mechanism is not described as automatic.</data></node><node id="DATA_NUMIDENT_SPECIAL_INDICATOR_CODE"><data key="node_entity_id">DATA_NUMIDENT_SPECIAL_INDICATOR_CODE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Special Indicator Code</data><data key="node_domain">Identity &amp; Enumeration / Program Integrity</data><data key="node_description">Special indicator code identifying questionable data or special circumstances concerning an SSN application, with examples including false identity, illegal alien, and scrambled earnings.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Generic current SORN field concept. Individual code values may be separately modeled only when authoritative policy identifies them.</data></node><node id="DATA_NUMIDENT_SPIN6"><data key="node_entity_id">DATA_NUMIDENT_SPIN6</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident HALE Special Indicator 6</data><data key="node_acronym">SPIN 6</data><data key="node_domain">Identity &amp; Enumeration / Privacy</data><data key="node_description">Numident special indicator code identifying an SSN issued under harassment, abuse, or life-endangerment criteria.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current disability POMS explicitly states HALE-issued SSNs have SPIN 6 on the Numident record.</data></node><node id="DATA_NUMIDENT_SSD"><data key="node_entity_id">DATA_NUMIDENT_SSD</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Source of Death</data><data key="node_acronym">SSD</data><data key="node_domain">Identity; Numident; Death</data><data key="node_description">Numident death-provenance field identifying the source of SSA death information; codes 01-65 identify a State source, and code 97 is treated as State Death Match data in current proof-of-death policy.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Source values carry legal disclosure consequences under Social Security Act section 205(r).</data></node><node id="DATA_NUMI_BIRTH_CERTIFICATE_NUMBER"><data key="node_entity_id">DATA_NUMI_BIRTH_CERTIFICATE_NUMBER</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Birth Certificate Number Field</data><data key="node_acronym">BCN</data><data key="node_domain">Enumeration / Identity Proofing</data><data key="node_description">POMS expressly identifies Numident BCN field and differing display conventions for state birth certificate numbers; not a postal address attribute.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_OACT_ACTUARIAL_LIFE_TABLE"><data key="node_entity_id">DATA_OACT_ACTUARIAL_LIFE_TABLE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Actuarial Life Table</data><data key="node_acronym">Actuarial Life Table</data><data key="node_domain">actuarial / mortality</data><data key="node_description">Public OACT period life table view showing death probability, number of lives, and life expectancy by exact age and sex.</data><data key="node_observed_status">observed_current_public_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current page presents the 2023 period life table as used in the 2026 Trustees Report and allows other years.</data></node><node id="DATA_OACT_AS_4A1_OASI_TF"><data key="node_entity_id">DATA_OACT_AS_4A1_OASI_TF</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Actuarial Services Table 4.A1 - Old-Age and Survivors Insurance Trust Fund</data><data key="node_acronym">4.A1</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">Public Actuarial Services time series for OASI Trust Fund income, cost, reserves, and related components.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current table includes historical data through 2025 and replaces the corresponding discontinued Annual Statistical Supplement section table.</data></node><node id="DATA_OACT_AS_4A2_DI_TF"><data key="node_entity_id">DATA_OACT_AS_4A2_DI_TF</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Actuarial Services Table 4.A2 - Disability Insurance Trust Fund</data><data key="node_acronym">4.A2</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">Public Actuarial Services time series for DI Trust Fund income, cost, reserves, and related components.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current table includes historical data through 2025.</data></node><node id="DATA_OACT_AS_4A3_OASDI_TF"><data key="node_entity_id">DATA_OACT_AS_4A3_OASDI_TF</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Actuarial Services Table 4.A3 - OASI and DI Trust Funds</data><data key="node_acronym">4.A3</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">Public Actuarial Services combined OASDI trust-fund historical financial data.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current table includes historical data through 2025.</data></node><node id="DATA_OACT_AS_4A4_TOTAL_BENEFITS"><data key="node_entity_id">DATA_OACT_AS_4A4_TOTAL_BENEFITS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Actuarial Services Table 4.A4 - Total Annual Benefits by Type and Trust Fund</data><data key="node_acronym">4.A4</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">Public Actuarial Services series for total annual Social Security and Medicare benefits by type of benefit and trust fund.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current table includes historical data through 2025.</data></node><node id="DATA_OACT_AS_4A5_OASI_BENEFITS"><data key="node_entity_id">DATA_OACT_AS_4A5_OASI_BENEFITS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Actuarial Services Table 4.A5 - OASI Benefits by Type</data><data key="node_acronym">4.A5</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">Public Actuarial Services series for annual benefits paid from the OASI Trust Fund by type of benefit.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current table includes historical data through 2025.</data></node><node id="DATA_OACT_AS_4A6_DI_BENEFITS"><data key="node_entity_id">DATA_OACT_AS_4A6_DI_BENEFITS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Actuarial Services Table 4.A6 - DI Benefits by Type</data><data key="node_acronym">4.A6</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">Public Actuarial Services series for annual benefits paid from the DI Trust Fund by type of benefit.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current table includes historical data through 2025.</data></node><node id="DATA_OACT_AUTO_DETERMINATIONS"><data key="node_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Automatic Determinations in Recent Years</data><data key="node_domain">Actuarial / Statistical Data Products</data><data key="node_description">OACT consolidated public table of Social Security program amounts automatically adjusted under statutory formulas.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Includes 2016-2026 values within the Atlas research horizon across COLA, AWI, taxable maximum, earnings test, bend points, coverage, SGA and related amounts.</data></node><node id="DATA_OACT_BEND_POINTS"><data key="node_entity_id">DATA_OACT_BEND_POINTS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Benefit Formula Bend Points</data><data key="node_acronym">PIA Bend Points</data><data key="node_domain">Actuarial / Benefit Formula / Public Data</data><data key="node_description">OACT public series of annual Primary Insurance Amount and maximum-family-benefit formula bend points.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current series includes 2026 PIA bend points of $1,286 and $7,749 and maximum-family-benefit bend points of $1,643, $2,371, and $3,093.</data></node><node id="DATA_OACT_BENEFICIARY"><data key="node_entity_id">DATA_OACT_BENEFICIARY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Social Security Beneficiary Data</data><data key="node_acronym">OACT Beneficiary Data</data><data key="node_domain">Actuarial / Statistical Data</data><data key="node_description">Current OCACT public beneficiary-data service providing tables and queryable statistics on currently paid Social Security beneficiaries, distributions, awards, and related measures.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public statistical product; underlying physical production store is not identified by the cited page.</data></node><node id="DATA_OACT_BEN_BY_AGE"><data key="node_entity_id">DATA_OACT_BEN_BY_AGE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Social Security Beneficiaries by Age</data><data key="node_domain">Actuarial / Beneficiary Statistics</data><data key="node_description">OACT public product presenting numbers of currently paid Social Security beneficiaries by age and beneficiary type, with privacy suppression for cells containing one or two beneficiaries.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Page observed October 7, 2026; displayed aggregate section is end of December 2025. Internal source repository and publication stack are not stated.</data></node><node id="DATA_OACT_BEN_BY_BENEFIT_LEVEL"><data key="node_entity_id">DATA_OACT_BEN_BY_BENEFIT_LEVEL</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Social Security Beneficiaries by Benefit Level</data><data key="node_acronym">Beneficiaries by Benefit Level</data><data key="node_domain">Actuarial / Statistical Publications</data><data key="node_description">OACT data product reporting Social Security beneficiaries in current-payment status by monthly benefit level; the current page reports data at the end of December 2025.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public page does not identify the internal source database, ETL process, scheduler, or publication engine.</data></node><node id="DATA_OACT_BEN_TYPE_ICP"><data key="node_entity_id">DATA_OACT_BEN_TYPE_ICP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Benefits Paid by Type of Beneficiary - Current Payment Status</data><data key="node_domain">Actuarial / Beneficiary Statistics</data><data key="node_description">Interactive OACT public data product reporting beneficiary counts and average benefits by beneficiary type for selected months or time series, with data available from 1967 onward.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">The page cautions current-payment amounts are not total trust-fund benefits paid and does not expose its internal production pipeline.</data></node><node id="DATA_OACT_CBB"><data key="node_entity_id">DATA_OACT_CBB</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Contribution and Benefit Base Determination</data><data key="node_acronym">CBB</data><data key="node_domain">Actuarial / Automatic Determinations / Earnings</data><data key="node_description">OACT annual determination of the OASDI contribution and benefit base using the statutory AWI-indexed formula.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 base is $184,500; internal calculation software is not identified publicly.</data></node><node id="DATA_OACT_COHORT_LIFE_2026"><data key="node_entity_id">DATA_OACT_COHORT_LIFE_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Report Cohort Life Tables</data><data key="node_acronym">Cohort Life Tables</data><data key="node_domain">actuarial / mortality</data><data key="node_description">Historical and projected cohort life tables by single year of age, sex, and birth year for the 2026 Trustees Report.</data><data key="node_observed_status">observed_current_public_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Birth cohorts 1900-2100 under alternatives I, II, III.</data></node><node id="DATA_OACT_COVERAGE_THRESH"><data key="node_entity_id">DATA_OACT_COVERAGE_THRESH</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Employment Coverage Threshold Determinations</data><data key="node_domain">Actuarial / Automatic Determinations / Coverage</data><data key="node_description">OACT annual domestic-employee and election-worker coverage threshold determinations.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 thresholds are $3,000 for domestic employees and $2,500 for election workers.</data></node><node id="DATA_OACT_CURRENT_PAYMENT_QUARTERLY"><data key="node_entity_id">DATA_OACT_CURRENT_PAYMENT_QUARTERLY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Benefits in Current Payment Status Quarterly Series</data><data key="node_domain">Actuarial / Beneficiary Statistics</data><data key="node_description">OACT historical quarterly series showing counts of people receiving Social Security benefits at calendar-quarter end, beginning March 1970, by major beneficiary class.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Page observed October 7, 2026 displays end-of-December 2025 values; internal source and ETL stack are not stated.</data></node><node id="DATA_OACT_DEATH_PROB_2026"><data key="node_entity_id">DATA_OACT_DEATH_PROB_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Report Death Probabilities Tables</data><data key="node_acronym">Death Probabilities</data><data key="node_domain">actuarial / mortality</data><data key="node_description">Historical and projected probabilities of death by single year of age, sex, and year for the 2026 Trustees Report.</data><data key="node_observed_status">observed_current_public_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Historical 1900-2023; projected 2024-2100 under alternatives I, II, III.</data></node><node id="DATA_OACT_DISABILITY_INSURED_WORKERS"><data key="node_entity_id">DATA_OACT_DISABILITY_INSURED_WORKERS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Disability Insured Workers by Age and Sex</data><data key="node_acronym">Disability Insured Workers</data><data key="node_domain">actuarial and statistics</data><data key="node_description">Estimated number of workers insured in the event of disability by age group and sex, with annual series through 2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">OACT statistical table 4.C2 disability insured.</data></node><node id="DATA_OACT_DISABLED_AGE_SEX_202606"><data key="node_entity_id">DATA_OACT_DISABLED_AGE_SEX_202606</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Disabled Worker Beneficiaries by Age and Sex - June 2026</data><data key="node_domain">Actuarial / Beneficiary Statistics</data><data key="node_description">Detailed table of disabled worker beneficiaries in current-payment status at the end of June 2026, distributed by age and sex with average benefit amounts.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public page does not identify internal extraction, source database, ETL, or publication technology.</data></node><node id="DATA_OACT_DI_INCIDENCE_2026"><data key="node_entity_id">DATA_OACT_DI_INCIDENCE_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 DI Disability Incidence Rate Series</data><data key="node_domain">Actuarial / Disability Insurance / Public Data</data><data key="node_description">Public plot-point series for Figure V.C3 of the 2026 Trustees Report, covering historical and projected disabled-worker incidence rates.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public data product; internal production pipeline is not identified.</data></node><node id="DATA_OACT_DI_TERMINATION_2026"><data key="node_entity_id">DATA_OACT_DI_TERMINATION_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 DI Disability Termination Rate Series</data><data key="node_domain">Actuarial / Disability Insurance / Public Data</data><data key="node_description">Public plot-point series for Figure V.C4 of the 2026 Trustees Report, covering historical and projected disabled-worker termination rates.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public data product; internal production pipeline is not identified.</data></node><node id="DATA_OACT_FACT_SHEET_20260630"><data key="node_entity_id">DATA_OACT_FACT_SHEET_20260630</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">June 30, 2026 Fact Sheet on Social Security</data><data key="node_acronym">OACT Fact Sheet 2026</data><data key="node_domain">Actuarial / Statistical Publications</data><data key="node_description">OACT public fact sheet summarizing current OASDI coverage, beneficiary protection, trust-fund operations, and related program statistics as of June 30, 2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public OACT product; the page does not identify an internal database, ETL engine, or publication scheduler.</data></node><node id="DATA_OACT_FULLY_INSURED_WORKERS"><data key="node_entity_id">DATA_OACT_FULLY_INSURED_WORKERS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Fully Insured Workers by Age and Sex</data><data key="node_acronym">Fully Insured Workers</data><data key="node_domain">actuarial and statistics</data><data key="node_description">Estimated number of fully insured workers by age group and sex, with annual series through 2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">OACT statistical table 4.C2 fully insured.</data></node><node id="DATA_OACT_INSURED_WORKERS_STATUS"><data key="node_entity_id">DATA_OACT_INSURED_WORKERS_STATUS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Insured Workers by Insured Status</data><data key="node_acronym">Insured Workers by Status</data><data key="node_domain">actuarial and statistics</data><data key="node_description">Estimated number of insured workers by insured status, with annual series through 2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">OACT statistical table 4.C1.</data></node><node id="DATA_OACT_OASDI_BEN_STATS"><data key="node_entity_id">DATA_OACT_OASDI_BEN_STATS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Social Security Beneficiary Statistics</data><data key="node_acronym">OASDI Beneficiary Statistics</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">OACT beneficiary-count data product providing annual OASI/DI beneficiary counts and described by SSA as unedited data from the Master Beneficiary Record.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current page contains data through December 31, 2025 and points to more detailed beneficiary tables.</data></node><node id="DATA_OACT_OLDLAW_CBB"><data key="node_entity_id">DATA_OACT_OLDLAW_CBB</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Old-Law Contribution and Benefit Base Determination</data><data key="node_acronym">Old-law CBB</data><data key="node_domain">Actuarial / Automatic Determinations / Earnings</data><data key="node_description">OACT annual old-law contribution and benefit base determination used for specified Social Security, Railroad Retirement, and ERISA purposes.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 amount is $137,100.</data></node><node id="DATA_OACT_PERIOD_LIFE_2026"><data key="node_entity_id">DATA_OACT_PERIOD_LIFE_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Report Period Life Tables</data><data key="node_acronym">Period Life Tables</data><data key="node_domain">actuarial / mortality</data><data key="node_description">Historical and projected period life tables by single year of age, sex, and calendar year for the 2026 Trustees Report.</data><data key="node_observed_status">observed_current_public_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Historical 1900-2023; projected 2024-2100 under alternatives I, II, III.</data></node><node id="DATA_OACT_PRIMARY_BEN_AGE_SEX_2026"><data key="node_entity_id">DATA_OACT_PRIMARY_BEN_AGE_SEX_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Primary Beneficiaries by Age and Sex - June 2026</data><data key="node_domain">Actuarial / Beneficiary Statistics</data><data key="node_description">OACT data product showing retired-worker and disabled-worker primary beneficiaries by age and sex as of June 30, 2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">Public page exposes underlying graph data but does not identify the administrative source store or production pipeline.</data></node><node id="DATA_OACT_PRINC_ECON_2026"><data key="node_entity_id">DATA_OACT_PRINC_ECON_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Principal Economic Assumptions Table V.B1</data><data key="node_acronym">Table V.B1</data><data key="node_domain">Actuarial / Economic Projections</data><data key="node_description">Public table of historical and projected principal economic assumptions for calendar years 1960 through 2100 under Trustees Report alternatives.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-06-09</data><data key="node_confidence">5</data><data key="node_notes">Public data product tied to 2026 Trustees Report; no internal model implementation inferred.</data></node><node id="DATA_OACT_QC_AMOUNT"><data key="node_entity_id">DATA_OACT_QC_AMOUNT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Quarter of Coverage Earnings Amount</data><data key="node_acronym">QC Amount</data><data key="node_domain">Actuarial / Automatic Determinations / Insured Status</data><data key="node_description">Annual amount of earnings needed to earn a Social Security quarter of coverage, published within OACT automatic determinations.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 amount is $1,890. This is a published program parameter, not a claimant-level earnings record.</data></node><node id="DATA_OACT_RETIRED_AGE_SEX_202606"><data key="node_entity_id">DATA_OACT_RETIRED_AGE_SEX_202606</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Retired Worker Beneficiaries by Age and Sex - June 2026</data><data key="node_domain">Actuarial / Beneficiary Statistics</data><data key="node_description">OACT table of retired worker beneficiaries in current payment status at the end of June 2026 by single year of age and sex, with average benefit amounts and dual-entitlement breakouts.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">Public table does not identify the internal data-extraction or publication technology.</data></node><node id="DATA_OACT_RET_TEST_EXEMPT"><data key="node_entity_id">DATA_OACT_RET_TEST_EXEMPT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Retirement Earnings Test Exempt Amount Determination</data><data key="node_domain">Actuarial / Automatic Determinations / Title II</data><data key="node_description">OACT annual lower and higher retirement earnings-test exempt amounts determined under statutory wage-indexed formulas.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">For 2026, annual amounts are $24,480 and $65,160.</data></node><node id="DATA_OACT_SGA"><data key="node_entity_id">DATA_OACT_SGA</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Substantial Gainful Activity Amount Determination</data><data key="node_acronym">SGA</data><data key="node_domain">Actuarial / Automatic Determinations / Disability</data><data key="node_description">OACT annual SGA amount determination for blind and non-blind disability cases.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 monthly amounts are $2,830 for statutory blindness and $1,690 for other disabilities.</data></node><node id="DATA_OACT_SOCSEC_AREA_INSURED"><data key="node_entity_id">DATA_OACT_SOCSEC_AREA_INSURED</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Social Security Area Population and Fully Insured Percent</data><data key="node_acronym">Social Security Area Insured Population</data><data key="node_domain">actuarial and statistics</data><data key="node_description">Population in the Social Security area with estimated number and percent fully insured by age and sex for 2022-2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">OACT statistical table 4.C5.</data></node><node id="DATA_OACT_SOCSEC_POP_DOWNLOAD_2026"><data key="node_entity_id">DATA_OACT_SOCSEC_POP_DOWNLOAD_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Report Social Security Area Population Tables</data><data key="node_acronym">Social Security Area Population Tables</data><data key="node_domain">actuarial / population</data><data key="node_description">Historical and projected Social Security area population tables by single year of age, sex, marital status, and year.</data><data key="node_observed_status">observed_current_public_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Beginning-, mid-, and end-of-year series with projections through 2100/2101 depending on measure.</data></node><node id="DATA_OACT_SOLVENCY_PROVISIONS"><data key="node_entity_id">DATA_OACT_SOLVENCY_PROVISIONS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Long Range Solvency Provisions Collection</data><data key="node_acronym">Long Range Solvency Provisions</data><data key="node_domain">Actuarial / Policy Options</data><data key="node_description">Public OACT collection of estimated Social Security program-change provisions and solvency effects.</data><data key="node_observed_status">taxation_category_2026_basis_confirmed_other_categories_unverified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Current OACT summary page states that estimates are based on the intermediate assumptions of the 2026 Trustees Report. Earlier transition observations remain preserved in prior-version history. Run114: taxation-of-benefits category specifically states 2026 Trustees intermediate assumptions as basis; do not generalize to every other OACT solvency category.</data></node><node id="DATA_OACT_TR2026_COLA_AWI_EST"><data key="node_entity_id">DATA_OACT_TR2026_COLA_AWI_EST</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT 2026 Trustees Report COLA and AWI Estimates</data><data key="node_domain">Actuarial / Economic Assumptions</data><data key="node_description">OACT table of estimated future cost-of-living adjustments and national average wage index increases derived from the intermediate assumptions of the 2026 Trustees Report.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public product identifies the report assumption basis but not the internal actuarial calculation or publication stack.</data></node><node id="DATA_OACT_TR2026_SINGLE_YEAR"><data key="node_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 OASDI Trustees Report Single-Year Tables</data><data key="node_domain">actuarial and statistical</data><data key="node_description">OACT set of historical and projected single-year tables consistent with the 2026 OASDI Trustees Report, with downloadable spreadsheet data.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public actuarial/statistical publication layer; internal calculation platform not inferred.</data></node><node id="DATA_OACT_TRUST_FUND_FINANCIAL"><data key="node_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">OACT Social Security Trust Fund Financial Data</data><data key="node_acronym">Trust Fund Financial Data</data><data key="node_domain">Actuarial; Trust Funds; Finance</data><data key="node_description">OACT public financial-data family for OASI and DI trust-fund income, cost, reserves, and related financial operations by selectable periods and frequencies.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Treasury supplies SSA monthly financial-operations data; OACT publishes selectable financial views.</data></node><node id="DATA_OACT_TRUST_FUND_HOLDINGS"><data key="node_entity_id">DATA_OACT_TRUST_FUND_HOLDINGS</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">OACT Trust Fund Investment Holdings</data><data key="node_acronym">Trust Fund Investment Holdings</data><data key="node_domain">Actuarial; Trust Funds; Finance</data><data key="node_description">OACT public investment-holdings data showing amounts held by security type, interest rate, maturity date, and trust fund, based on monthly Bureau of the Fiscal Service reports.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public data available for 1990 and later.</data></node><node id="DATA_OACT_TRUST_FUND_TIME_SERIES"><data key="node_entity_id">DATA_OACT_TRUST_FUND_TIME_SERIES</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">OACT Trust Fund Financial Time Series</data><data key="node_acronym">Trust Fund Financial Time Series</data><data key="node_domain">Actuarial; Trust Funds; Finance</data><data key="node_description">OACT selectable time-series product for OASI, DI, or combined trust-fund financial items at monthly, quarterly, calendar-year, or fiscal-year frequencies.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The public page exposes time series for data after 1986; physical publication tooling is not identified.</data></node><node id="DATA_OACT_TRUST_FUND_TRANSACTIONS"><data key="node_entity_id">DATA_OACT_TRUST_FUND_TRANSACTIONS</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">OACT Trust Fund Investment Transactions</data><data key="node_acronym">Trust Fund Investment Transactions</data><data key="node_domain">Actuarial; Trust Funds; Finance</data><data key="node_description">OACT public data product summarizing Social Security trust-fund investment acquisitions and redemptions, including monthly and time-series views.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Based on Treasury/Bureau of the Fiscal Service monthly reporting.</data></node><node id="DATA_OACT_TRUST_RATIO_TABLE"><data key="node_entity_id">DATA_OACT_TRUST_RATIO_TABLE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table IV.B5 Trust Fund Ratios</data><data key="node_domain">actuarial and statistical</data><data key="node_description">Single-year historical and projected OASI, DI, and combined trust-fund ratio table consistent with the 2026 OASDI Trustees Report.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published OACT data table.</data></node><node id="DATA_OACT_TR_IVB1_RATES"><data key="node_entity_id">DATA_OACT_TR_IVB1_RATES</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table IV.B1 Annual Income Rates, Cost Rates, and Balances</data><data key="node_acronym">TR IV.B1</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Single-year historical and projected OASDI annual income rates, cost rates, and balances for calendar years 1970-2100 under Trustees assumptions.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as HTML and Excel through OACT supplemental single-year tables. Internal production database/model technology is not inferred.</data></node><node id="DATA_OACT_TR_IVB2_COMPONENTS"><data key="node_entity_id">DATA_OACT_TR_IVB2_COMPONENTS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table IV.B2 Components of Annual Income Rates</data><data key="node_acronym">TR IV.B2</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Single-year OASDI components of annual income rates for calendar years 1970-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as HTML and Excel through OACT supplemental single-year tables. Internal production database/model technology is not inferred.</data></node><node id="DATA_OACT_TR_IVB3_GDP"><data key="node_entity_id">DATA_OACT_TR_IVB3_GDP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table IV.B3 Income Rates, Cost Rates, and Balances as Percent of GDP</data><data key="node_acronym">TR IV.B3</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Single-year OASDI income rates, cost rates, and balances expressed as a percentage of GDP for calendar years 1970-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as HTML and Excel through OACT supplemental single-year tables. Internal production database/model technology is not inferred.</data></node><node id="DATA_OACT_TR_VA1_FERT_MORT"><data key="node_entity_id">DATA_OACT_TR_VA1_FERT_MORT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.A1 Fertility and Mortality Assumptions</data><data key="node_acronym">TR V.A1</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Single-year fertility and mortality assumption series for calendar years 1940-2100 consistent with the 2026 OASDI Trustees Report.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as HTML and Excel through OACT supplemental single-year tables. Internal production database/model technology is not inferred.</data></node><node id="DATA_OACT_TR_VA2_IMMIGRATION"><data key="node_entity_id">DATA_OACT_TR_VA2_IMMIGRATION</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.A2 Immigration Assumptions</data><data key="node_acronym">V.A2</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Immigration assumptions, calendar years 1940-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VA3_POP_DEP"><data key="node_entity_id">DATA_OACT_TR_VA3_POP_DEP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.A3 Social Security Area Population and Dependency Ratios</data><data key="node_acronym">V.A3</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Social Security area population on July 1 and dependency ratios, calendar years 1941-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VA4_PERIOD_LE"><data key="node_entity_id">DATA_OACT_TR_VA4_PERIOD_LE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.A4 Period Life Expectancy</data><data key="node_acronym">V.A4</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Period life expectancy supplemental single-year table.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VA5_COHORT_LE"><data key="node_entity_id">DATA_OACT_TR_VA5_COHORT_LE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.A5 Cohort Life Expectancy</data><data key="node_acronym">V.A5</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Cohort life expectancy supplemental single-year table.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VB2_ECON"><data key="node_entity_id">DATA_OACT_TR_VB2_ECON</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.B2 Additional Economic Factors</data><data key="node_acronym">V.B2</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Additional economic factors, calendar years 1960-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VC4_OASI_BEN"><data key="node_entity_id">DATA_OACT_TR_VC4_OASI_BEN</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.C4 OASI Beneficiaries in Current-Payment Status</data><data key="node_acronym">V.C4</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">OASI beneficiaries with benefits in current-payment status at year end, 1975-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VC5_DI_BEN"><data key="node_entity_id">DATA_OACT_TR_VC5_DI_BEN</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.C5 DI Beneficiaries in Current-Payment Status</data><data key="node_acronym">V.C5</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">DI beneficiaries with benefits in current-payment status at year end, 1975-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VC7_SCHED_BEN"><data key="node_entity_id">DATA_OACT_TR_VC7_SCHED_BEN</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table V.C7 Scheduled Benefit Amounts by Pre-Retirement Earnings Pattern</data><data key="node_acronym">V.C7</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Annual scheduled benefit amounts for retired workers with various pre-retirement earnings patterns, 1940-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VIG1_ECON_VARS"><data key="node_entity_id">DATA_OACT_TR_VIG1_ECON_VARS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table VI.G1 Selected Economic Variables</data><data key="node_acronym">VI.G1</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Selected economic variables, calendar years 1970-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VIG2_TRUST_OPS_CUR"><data key="node_entity_id">DATA_OACT_TR_VIG2_TRUST_OPS_CUR</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table VI.G2 Combined OASI and DI Trust Fund Operations in Current Dollars</data><data key="node_acronym">VI.G2</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Operations of combined OASI and DI trust funds in current dollars from 1970 through reserve depletion.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VIG3_NONINT_CUR"><data key="node_entity_id">DATA_OACT_TR_VIG3_NONINT_CUR</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table VI.G3 Annual Non-Interest Income, Cost, and Balance in Current Dollars</data><data key="node_acronym">VI.G3</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Annual non-interest income, cost, and balance in current dollars, 1970-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VIG4_TRUST_OPS_CPI"><data key="node_entity_id">DATA_OACT_TR_VIG4_TRUST_OPS_CPI</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table VI.G4 Combined OASI and DI Trust Fund Operations in CPI-Indexed 2026 Dollars</data><data key="node_acronym">VI.G4</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Operations of combined OASI and DI trust funds in CPI-indexed 2026 dollars from 1970 through reserve depletion.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TR_VIG5_NONINT_CPI"><data key="node_entity_id">DATA_OACT_TR_VIG5_NONINT_CPI</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table VI.G5 Annual Non-Interest Income, Cost, and Balance in CPI-Indexed 2026 Dollars</data><data key="node_acronym">VI.G5</data><data key="node_domain">Actuarial / OASDI / Publication Data</data><data key="node_description">Annual non-interest income, cost, and balance in CPI-indexed 2026 dollars, 1970-2100.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_OACT_TWP"><data key="node_entity_id">DATA_OACT_TWP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Trial Work Period Earnings Trigger Determination</data><data key="node_acronym">TWP Trigger</data><data key="node_domain">Actuarial / Automatic Determinations / Disability Work Incentives</data><data key="node_description">OACT annual monthly earnings amount used to determine whether a month counts as a trial work period service month.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 monthly amount is $1,210.</data></node><node id="DATA_OACT_WORKERS_BEN_TABLE"><data key="node_entity_id">DATA_OACT_WORKERS_BEN_TABLE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Trustees Table IV.B4 Covered Workers and Beneficiaries</data><data key="node_domain">actuarial and statistical</data><data key="node_description">Single-year historical and projected table of covered workers and beneficiaries consistent with the 2026 OASDI Trustees Report.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published OACT data table.</data></node><node id="DATA_OAG_HQ_AWARDS"><data key="node_entity_id">DATA_OAG_HQ_AWARDS</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Recent SSA Headquarters Contracting History Dataset</data><data key="node_domain">Procurement / Public Data</data><data key="node_description">Downloadable OAG headquarters award listing available in HTML, CSV, XML, and JSON formats.</data><data key="node_observed_status">published_snapshot_stale_2023</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Live OAG page displays a listing date of November 2, 2023 and excludes modifications and BPA call orders; it is not treated as current comprehensive procurement data.</data></node><node id="DATA_OASDI_ANNUAL_AWARD_FILE"><data key="node_entity_id">DATA_OASDI_ANNUAL_AWARD_FILE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OASDI Annual 100-Percent Award File</data><data key="node_acronym">Annual Award File</data><data key="node_domain">Actuarial / Statistical Production</data><data key="node_description">Annual OASDI benefit-award file formed by combining 12 monthly MBR award-action files and used to prepare 100-percent award statistics.</data><data key="node_observed_status">documented_statistical_pipeline_2025</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes">Methodology documented for the 2025 Annual Statistical Supplement, completed in 2026; no unpublished ETL technology is inferred.</data></node><node id="DATA_OASDI_PUF_2001"><data key="node_entity_id">DATA_OASDI_PUF_2001</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OASDI Public-Use Microdata File, 2001</data><data key="node_acronym">OASDI PUF 2001</data><data key="node_domain">Research / Public-Use Microdata</data><data key="node_description">Deidentified public-use extract from the Master Beneficiary Record for persons entitled to OASDI benefits in December 2001; 1 percent representative sample, about 460,000 records and 16 fields.</data><data key="node_observed_status">historical_public_use_currently_available</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Released October 2003; SAS and CSV distributions. Sampling, top/bottom coding, grouping and rounding support disclosure protection.</data></node><node id="DATA_OASDI_STATE_COUNTY_2025"><data key="node_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OASDI Beneficiaries by State and County, 2025</data><data key="node_acronym">OASDI State and County 2025</data><data key="node_domain">Title II / Statistical Publication / Geography</data><data key="node_description">Annual state- and county-level OASDI beneficiary and payment statistics for December 2025.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Released August 2026; Federal Data Catalog identifier US-GOV-SSA-3415. Publication notes establish MBR and USPS ZIP+4 lineage.</data></node><node id="DATA_OASDI_ZIP_2024"><data key="node_entity_id">DATA_OASDI_ZIP_2024</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OASDI Beneficiaries by State and ZIP Code, 2024</data><data key="node_acronym">OASDI ZIP 2024</data><data key="node_domain">Statistical Publication / Geographic</data><data key="node_description">Annual publication reporting OASDI beneficiary counts and benefit amounts by state, SSA field office, and ZIP Code for December 2024.</data><data key="node_observed_status">current_publication</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes">SSA says statistics derive from MBR; DOORS associates field-office data with ZIP Codes; USPS geographic data is used. For beneficiaries with representative payees, state/field-office designations are those of the payees, not necessarily beneficiaries.</data></node><node id="DATA_OHO_AVG_WAIT_HIST"><data key="node_entity_id">DATA_OHO_AVG_WAIT_HIST</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Data for Average Processing Time Until Hearing Held</data><data key="node_domain">Hearings &amp; Appeals / Public Data</data><data key="node_description">Historical national annual hearing-held processing-time dataset covering FY1989 through FY2009.</data><data key="node_observed_status">historical_open_data</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1551. SSA directs users to the separate monthly office series for more recent data beginning September 2010.</data></node><node id="DATA_OHO_AVG_WAIT_MONTHLY"><data key="node_entity_id">DATA_OHO_AVG_WAIT_MONTHLY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Average Wait Time Until Hearing Held Report</data><data key="node_domain">Hearings &amp; Appeals / Public Data</data><data key="node_description">Monthly office-level public report of average months from hearing request date until hearing held for closed cases where a hearing occurred.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current page is August 2026; archived monthly reports were previously called NETSTATS reports. Do not infer the production data store from the publication alone.</data></node><node id="DATA_OHO_EXPERT_BUS_ADDRESS"><data key="node_entity_id">DATA_OHO_EXPERT_BUS_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">OHO Expert and Reporter Business Address</data><data key="node_acronym">Expert Business Address</data><data key="node_domain">Hearings / Experts / Address Provenance</data><data key="node_description">Business address information maintained for vocational experts, medical experts, other covered experts, and verbatim hearing reporters under BPA.</data><data key="node_observed_status">documented_persistent_contract_contact_attribute</data><data key="node_observed_as_of">2018-11-01</data><data key="node_confidence">5</data><data key="node_notes">Contractor/business contact address, not a claimant or beneficiary address. 60-0012 retains records for two years after contract expiration.</data></node><node id="DATA_OHO_LOCATION"><data key="node_entity_id">DATA_OHO_LOCATION</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Social Security Hearing Office Location Information</data><data key="node_acronym">OHO Hearing Office Location Data</data><data key="node_domain">Hearings &amp; Appeals / Geographic Data</data><data key="node_description">Public dataset containing address and telephone information for Social Security hearing offices, distributed as HTML and XML.</data><data key="node_observed_status">observed_current_public_data</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1729.</data></node><node id="DATA_OHO_WORKLOAD_PUBLIC"><data key="node_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">OHO Hearing Office Workload Data FY 2026</data><data key="node_domain">Hearings &amp; Appeals / Public Data</data><data key="node_description">Public hearing-office-level dataset with receipts, dispositions, pending cases and average processing time.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-28</data><data key="node_confidence">5</data><data key="node_notes">Useful for future geographic/district display layers.</data></node><node id="DATA_OIG_WARRANT_DISP"><data key="node_entity_id">DATA_OIG_WARRANT_DISP</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">OIG Warrant Disposition File</data><data key="node_domain">Program Integrity / Fugitive Felon</data><data key="node_description">File created after OIG warrant validation and law-enforcement follow-up and returned for FFSCF disposition processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="DATA_ORS"><data key="node_entity_id">DATA_ORS</data><data key="node_entity_type">survey</data><data key="node_canonical_name">Occupational Requirements Survey</data><data key="node_acronym">ORS</data><data key="node_domain">Disability / Occupational Data</data><data key="node_description">BLS occupational survey developed using National Compensation Survey infrastructure; ORS work-requirement data are designated as the primary data source for OIS.</data><data key="node_observed_status">wave3_collection_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Wave 2 five-year production data were published in February 2024; BLS is collecting Wave 3.</data></node><node id="DATA_PACOMM_2016"><data key="node_entity_id">DATA_PACOMM_2016</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">iAccommodate (PACOMM) BORG Source Dataset</data><data key="node_acronym">PACOMM</data><data key="node_domain">Accessibility / Person Data / Historical</data><data key="node_description">iAccommodate dataset identified as a source for the BORG Person subject area.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Dataset/application relationship is documented by the source naming; exact schema, extract path, and retention are not public.</data></node><node id="DATA_PAYMENT_CALC_BASES"><data key="node_entity_id">DATA_PAYMENT_CALC_BASES</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Payment Calculation Bases</data><data key="node_acronym">Payment Calculation Bases</data><data key="node_domain">Actuarial / Work Incentives / Provider Payments</data><data key="node_description">OACT annual Title II and Title XVI values used to calculate certain payments to rehabilitation service providers.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">Public series includes annual values through 2026 and historical years; internal calculation software and data pipeline are not identified.</data></node><node id="DATA_PCACS_ECR"><data key="node_entity_id">DATA_PCACS_ECR</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Electronic Control Record</data><data key="node_acronym">ECR</data><data key="node_domain">Processing Center / Workload Control</data><data key="node_description">PCACS placeholder/control record created when a listing is received with no paper associated with it.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Public policy describes it as a placeholder in PCACS.</data></node><node id="DATA_PCLNT_2016"><data key="node_entity_id">DATA_PCLNT_2016</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Client (PCLNT) BORG Source Dataset</data><data key="node_acronym">PCLNT</data><data key="node_domain">Shared Client Data / Historical</data><data key="node_description">Client dataset identified as one of the source datasets loaded into the BORG Person subject area.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Do not equate PCLNT automatically with the current Integrated Client Database physical store; the strategic plan names Client (PCLNT) but does not publish the underlying physical source topology.</data></node><node id="DATA_PC_INITIAL_DISABILITY_APT"><data key="node_entity_id">DATA_PC_INITIAL_DISABILITY_APT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Processing Center Initial Disability Average Processing Time Data</data><data key="node_acronym">PC Initial Disability APT</data><data key="node_domain">Disability / Processing Centers / Public Data</data><data key="node_description">Annual public data for processing-center and total-agency elapsed processing time and counts for initial disability cases involving a medical determination.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog US-GOV-SSA-1384; dataset covers FY2012 onward.</data></node><node id="DATA_PERSON_VAPT_SEGMENT"><data key="node_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">PERSON VAPT Segment</data><data key="node_acronym">VAPT Segment</data><data key="node_domain">Person / Identity / Disability</data><data key="node_description">PERSON/ICDB segment that holds the SSN of VA 100 percent permanent and total disability compensation recipients after SSA verifies supplied identity data against Numident.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS calls PERSON the SSA Integrated Client Data Base in this workflow. Only the verified SSN storage is established; no broader VA payload persistence is inferred.</data></node><node id="DATA_PER_REVIEW_2012_2016"><data key="node_entity_id">DATA_PER_REVIEW_2012_2016</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Pre-effectuation Review of Disability Determinations Data, FY2012-2016</data><data key="node_acronym">PER Data</data><data key="node_domain">Disability / Quality / Open Data</data><data key="node_description">Public national-level annual results from SSA Pre-effectuation Review of disability determinations for fiscal years 2012 through 2016.</data><data key="node_observed_status">historical_public_dataset</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1492; page remains publicly available although the dataset time period ends in 2016.</data></node><node id="DATA_PHUS_EVENT070"><data key="node_entity_id">DATA_PHUS_EVENT070</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">PHUS Event Code 070</data><data key="node_acronym">EVENT 070</data><data key="node_domain">Title II / Payments / Payment History</data><data key="node_description">PHUS event code used in the current CORE erroneous-death workflow to confirm that Treasury returned a credit after the presenting financial institution was denied payment.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS also references CDAMT and TDSC-32 in the same event; these subfields are not separately modeled in this run.</data></node><node id="DATA_PI_ACCOMMODATION_INFO"><data key="node_entity_id">DATA_PI_ACCOMMODATION_INFO</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Person Information Accommodation Information</data><data key="node_acronym">PI Accommodation</data><data key="node_domain">Identity / Shared Person Data / Accessibility</data><data key="node_description">Accommodation information documented through iAccommodate within the Person Information (Identity, Contact, Accommodation) environment.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS establishes the application context and recording workflow. This entity models the data domain, not a claim that every accommodation or all supporting medical material resides in the Person data store.</data></node><node id="DATA_PI_ARN"><data key="node_entity_id">DATA_PI_ARN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Person Information Alien Registration Number</data><data key="node_acronym">ARN / A-Number</data><data key="node_domain">Identity / Immigration</data><data key="node_description">Alien Registration Number recorded in Person Information when available on immigration evidence and used by SSA in SAVE verification workflows.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The A-Number is a DHS identifier. Current POMS directs staff to enter it in Person Information; this does not make PI the DHS source of the identifier.</data></node><node id="DATA_PI_DEATH_SOURCE_NOTIFICATION"><data key="node_entity_id">DATA_PI_DEATH_SOURCE_NOTIFICATION</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Person Information Death Source of Notification</data><data key="node_acronym">Source of Notification</data><data key="node_domain">Identity / Death / Provenance</data><data key="node_description">Person Information death-data provenance field whose documented values can identify MBR or Treasury as the source of death notification.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents values 3=MBR and 4=Treasury for sufficient death documentation. Other possible values are not exhaustively mapped in this run.</data></node><node id="DATA_POPULAR_BABY_NAMES"><data key="node_entity_id">DATA_POPULAR_BABY_NAMES</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Popular Baby Names Data</data><data key="node_acronym">Popular Baby Names</data><data key="node_domain">Actuarial / Enumeration Statistics</data><data key="node_description">SSA/OCACT public baby-name statistics derived from Social Security card application records; current background states the data use a 100-percent sample of application records as of March 2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes">Statistical product from enumeration application records. The source page does not state that the publication is generated directly from Numident, SSNAP transaction databases, or another specific physical store.</data></node><node id="DATA_PPC_ACR"><data key="node_entity_id">DATA_PPC_ACR</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Action Control Record</data><data key="node_acronym">ACR</data><data key="node_domain">Processing Center / Workflow Control</data><data key="node_description">Paperless work-control record that carries event metadata, document history, user identity and audit-trail information for processing-center actions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a workflow/control record, not a standalone application.</data></node><node id="DATA_PUPS_FACILITY_ADDR"><data key="node_entity_id">DATA_PUPS_FACILITY_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">PUPS Prison or Facility Address</data><data key="node_domain">address provenance</data><data key="node_description">Prison or facility address, city, State, ZIP, and related contact fields in the prisoner response record layout.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">Institution/facility address, not a beneficiary residence or mailing address.</data></node><node id="DATA_PUPS_FACILITY_ID"><data key="node_entity_id">DATA_PUPS_FACILITY_ID</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">PUPS Prisoner Facility Identification Code</data><data key="node_acronym">FID</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">Six-position facility identification code used to identify the correctional or mental health institution associated with prisoner incentive-payment processing.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes">Facility/institution identifier, not a person identifier.</data></node><node id="DATA_PUPS_INCENTIVE_PAYEE_ADDRESS"><data key="node_entity_id">DATA_PUPS_INCENTIVE_PAYEE_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Prisoner Incentive Payee Facility Mailing Address</data><data key="node_acronym">Incentive Payee Address</data><data key="node_domain">Program Integrity / Prisoner / Address Provenance</data><data key="node_description">Correctional or mental health institution mailing address used for prisoner incentive-payment notices and displayed in QPID/IPID workflows.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes">Institution/business address, not a beneficiary mailing or residence address.</data></node><node id="DATA_PUPS_RESPONSE"><data key="node_entity_id">DATA_PUPS_RESPONSE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">PUPS Prisoner Response Record</data><data key="node_domain">external exchanges</data><data key="node_description">Abridged response-record structure associated with SSA prisoner data exchange and PUPS processing.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">Underlying layout is dated April 2013 but remains linked from the current SSA Data Exchange Applications catalog.</data></node><node id="DATA_QR_REVDOC93"><data key="node_entity_id">DATA_QR_REVDOC93</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">REVDOC 93 Quality Review Evidence Label</data><data key="node_acronym">REVDOC 93</data><data key="node_domain">Evidence / SSI Quality Review</data><data key="node_description">Document naming/label convention applied by Quality Review to supporting evidence scanned into NDRed so QR material can be distinguished from field-office documents.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2025-08-11</data><data key="node_confidence">5</data><data key="node_notes">Represents a document label/artifact, not a separate repository.</data></node><node id="DATA_R105_ECBSV_CERT"><data key="node_entity_id">DATA_R105_ECBSV_CERT</data><data key="node_entity_type">governance_document</data><data key="node_canonical_name">eCBSV Permitted Entity Biennial Certification</data><data key="node_domain">External Exchanges &amp; Identity</data><data key="node_description">eCBSV permitted entities submit signed certification at least biennially covering user eligibility, Banking Bill compliance, privacy safeguards and retention of compliance records for at least two years.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R105_ECBSV_CONSENT"><data key="node_entity_id">DATA_R105_ECBSV_CONSENT</data><data key="node_entity_type">consent_artifact</data><data key="node_canonical_name">eCBSV Number Holder Written Verification Consent</data><data key="node_domain">External Exchanges &amp; Identity</data><data key="node_description">eCBSV requires number holder written wet or electronic signature authorizing name/date-of-birth/SSN verification and permitted disclosure.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R105_ISNO_ACCOM_ADDR"><data key="node_entity_id">DATA_R105_ISNO_ACCOM_ADDR</data><data key="node_entity_type">logical_address_attribute</data><data key="node_canonical_name">iSNO Accommodation Decision Mailing Address</data><data key="node_domain">Person &amp; Address Provenance</data><data key="node_description">Applicant/recipient provides mailing address for written decision on special notice accommodation; source is user-provided and use is correspondence-scoped.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Not proof of MBR, SSR, or Numident address update. Retention unspecified.</data></node><node id="DATA_R105_ISNO_HISTORY"><data key="node_entity_id">DATA_R105_ISNO_HISTORY</data><data key="node_entity_type">logical_data_object</data><data key="node_canonical_name">iSNO Client Special Notice Option History</data><data key="node_domain">Notices &amp; Customer Service</data><data key="node_description">iSNO Client History box displays ten most recent selections and optionally accommodation counts, all request history and pending accommodation alerts; no physical table/retention interval identified.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Display semantics only; full record count and persistence unspecified.</data></node><node id="DATA_R105_LV_JOINT"><data key="node_entity_id">DATA_R105_LV_JOINT</data><data key="node_entity_type">derived_public_analytic_data</data><data key="node_canonical_name">Longevity Visualizer Joint Survivability Outputs</data><data key="node_domain">Actuarial &amp; Statistical Data</data><data key="node_description">Visualizer combines individual life-table survival functions to estimate two-person outcomes: both alive, both dead, one survivor.</data><data key="node_observed_status">documented_2016_method</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R105_LV_SURVIVAL"><data key="node_entity_id">DATA_R105_LV_SURVIVAL</data><data key="node_entity_type">derived_public_analytic_data</data><data key="node_canonical_name">Longevity Visualizer Survival and Death Distributions</data><data key="node_domain">Actuarial &amp; Statistical Data</data><data key="node_description">Visualizer computes monthly survival functions and death-age probability distributions from OACT cohort life-table annual mortality inputs (2016 method).</data><data key="node_observed_status">documented_2016_method</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R105_OACT_COHORT_TABLE_FAMILY"><data key="node_entity_id">DATA_R105_OACT_COHORT_TABLE_FAMILY</data><data key="node_entity_type">statistical_data_product_family</data><data key="node_canonical_name">OACT Cohort Mortality Life Table Product Family</data><data key="node_acronym">OACT Cohort Life Tables</data><data key="node_domain">Actuarial &amp; Statistical Data</data><data key="node_description">OACT cohort mortality life tables supply probability-of-death and survival inputs for SSA Longevity Visualizer as documented in 2016; no current published version or executable refresh inferred.</data><data key="node_observed_status">historical_2016_documented_product</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Separate from the 2026 Trustees cohort life tables; 2016 executable dataset/version cannot be assumed current.</data></node><node id="DATA_R194_EAB_ORIGINAL"><data key="node_entity_id">DATA_R194_EAB_ORIGINAL</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">EAB State Vital Records Original Infant Enumeration Transmission</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Hospitals submit parent-authorized EAB birth-registration SSN request to State vital records agency, which electronically sends the original infant enumeration request to SSA NCC.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2010-01-15</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R194_SAMOA_BANK_ADDR"><data key="node_entity_id">DATA_R194_SAMOA_BANK_ADDR</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">ITS.gov Samoa Financial Institution Address</data><data key="node_domain">Address Provenance</data><data key="node_description">Treasury ITS.gov Samoa enrollment includes a bank-address field formatted using WS/Town/Name; this is not a beneficiary residence address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R194_SAMOA_BENE_ADDR"><data key="node_entity_id">DATA_R194_SAMOA_BENE_ADDR</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">ITS.gov Samoa Beneficiary Address</data><data key="node_domain">Address Provenance</data><data key="node_description">Treasury ITS.gov Samoa enrollment separately includes beneficiary address formatted WS/Town/Name; not shown to update MBR.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R194_SM_SWIFT"><data key="node_entity_id">DATA_R194_SM_SWIFT</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">San Marino IDD Bank SWIFT-BIC Identifier</data><data key="node_domain">Title II Payments</data><data key="node_description">San Marino IDD enrolment in ITS.gov requires bank SWIFT-BIC in addition to IBAN; not a person or address identifier.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-01-16</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R194_STAT2020_T2A17_COR"><data key="node_entity_id">DATA_R194_STAT2020_T2A17_COR</data><data key="node_entity_type">publication_revision</data><data key="node_canonical_name">2020 Statistical Supplement Table 2.A17 PIA Corrections</data><data key="node_domain">Data Products &amp; Publication</data><data key="node_description">March 6 2026 corrections to minimum PIAs (2013-19) and family maximum formulas.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R194_STAT2020_T2A26_COR"><data key="node_entity_id">DATA_R194_STAT2020_T2A26_COR</data><data key="node_entity_type">publication_revision</data><data key="node_canonical_name">2020 Statistical Supplement Table 2.A26 Family Benefit Corrections</data><data key="node_domain">Data Products &amp; Publication</data><data key="node_description">April 21 2026 correction to family amounts and survivor-family minimum-wage PIA.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-04-21</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_R194_STAT2020_T4A2_COR"><data key="node_entity_id">DATA_R194_STAT2020_T4A2_COR</data><data key="node_entity_type">publication_revision</data><data key="node_canonical_name">2020 Statistical Supplement Table 4.A2 Railroad Transfer Correction</data><data key="node_domain">Data Products &amp; Publication</data><data key="node_description">December 5 2025 correction to 1977 Railroad Retirement transfer amount representation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-12-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_RECS_SOURCE_INDICATOR"><data key="node_entity_id">DATA_RECS_SOURCE_INDICATOR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">RECS Race/Ethnicity Data Source Indicator</data><data key="node_acronym">RECS Source Indicator</data><data key="node_domain">Identity &amp; Enumeration / Race and Ethnicity</data><data key="node_description">Indicator code in the Race and Ethnicity Collection System identifying the source of race/ethnicity data, such as the SSN application process or Enumeration at Birth.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2025 SORN explicitly identifies this field and examples.</data></node><node id="DATA_REP_PAYEE_LAY_CAP_EVIDENCE"><data key="node_entity_id">DATA_REP_PAYEE_LAY_CAP_EVIDENCE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Representative Payee Lay Capability Evidence</data><data key="node_acronym">Lay Capability Evidence</data><data key="node_domain">representative payee / evidence</data><data key="node_description">Third-party lay evidence describing how the beneficiary manages finances to meet basic needs.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SSA-788 is required when SSA contacts a custodian different from the payee applicant.</data></node><node id="DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE"><data key="node_entity_id">DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Representative Payee Legal Incompetence Evidence</data><data key="node_acronym">Legal Incompetence Evidence</data><data key="node_domain">representative payee / evidence</data><data key="node_description">Certified court-order evidence establishing or addressing legal incompetence for representative-payee capability determinations.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Stored in NDRed or eView and legal-incompetence details are documented in eRPS when applicable.</data></node><node id="DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE"><data key="node_entity_id">DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Representative Payee Medical Capability Evidence</data><data key="node_acronym">Medical Capability Evidence</data><data key="node_domain">representative payee / evidence</data><data key="node_description">Medical evidence used to assess a beneficiary ability to manage or direct management of benefits.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SSA-787 is the preferred vehicle, but qualifying other medical-source statements may also be used.</data></node><node id="DATA_REP_PAYEE_TYPE"><data key="node_entity_id">DATA_REP_PAYEE_TYPE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Representative Payee Type</data><data key="node_acronym">Rep Payee Type</data><data key="node_domain">Representative Payee / Person and Organization Identity</data><data key="node_description">Indicator identifying a representative payee as an individual or organization; current policy says it is recorded in eRPS, MBR, and SSR.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-17</data><data key="node_confidence">5</data><data key="node_notes">This is a program/payee classification attribute maintained across separate records, not evidence of a single enterprise person repository.</data></node><node id="DATA_RIB_INTERNET_APPS_2246"><data key="node_entity_id">DATA_RIB_INTERNET_APPS_2246</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Retirement Insurance Applications Filed via the Internet Data Collection</data><data key="node_acronym">US-GOV-SSA-2246</data><data key="node_domain">Title II / Public Data</data><data key="node_description">Monthly national data for retirement insurance applications filed via the Internet and comparable applications filed through other channels, fiscal years 2012 and later.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog collection identifier US-GOV-SSA-2246; CSV publication.</data></node><node id="DATA_ROC"><data key="node_entity_id">DATA_ROC</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Record of Change</data><data key="node_acronym">ROC</data><data key="node_domain">Disability / Audit Trail</data><data key="node_description">Electronic-folder audit/change artifact produced for specified EDCS post-transfer changes and viewable through electronic-folder case data/history.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">UAT POMS explicitly states EDCS produces a Record of Change for the first UAT action. No physical storage table or file format is inferred.</data></node><node id="DATA_RR37_TD_SM"><data key="node_entity_id">DATA_RR37_TD_SM</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Railroad 1937-to-Date Service Months</data><data key="node_acronym">RR 37 TD Service Months</data><data key="node_domain">Title II / Railroad / Earnings</data><data key="node_description">Railroad service-month value on DRRE; 120 or more months can establish career railroad jurisdiction under current policy.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical screen data element only.</data></node><node id="DATA_RR96_TD_SM"><data key="node_entity_id">DATA_RR96_TD_SM</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Railroad 1996-to-Date Service Months</data><data key="node_acronym">RR 96 TD Service Months</data><data key="node_domain">Title II / Railroad / Earnings</data><data key="node_description">Railroad service-month value on DRRE; 60 or more months can establish career railroad jurisdiction under current policy.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical screen data element only.</data></node><node id="DATA_RRB_MEDICAL_EVIDENCE"><data key="node_entity_id">DATA_RRB_MEDICAL_EVIDENCE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Railroad Retirement Board Medical Evidence</data><data key="node_acronym">RRB Medical Evidence</data><data key="node_domain">Disability / External Evidence</data><data key="node_description">Medical evidence maintained by the Railroad Retirement Board and furnished to SSA on request to avoid duplicate development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public policy does not disclose physical database technology or persistence beyond the documented system/work-control references.</data></node><node id="DATA_RRB_SSI_ADDRESS"><data key="node_entity_id">DATA_RRB_SSI_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">RRB/SSI Interface Address and ZIP</data><data key="node_acronym">RRB SSI Address</data><data key="node_domain">Title XVI / External Exchange / Address Provenance</data><data key="node_description">Address and ZIP fields displayed in the Railroad Retirement Board record format used by the SSI/RRB interface.</data><data key="node_observed_status">current_documented_interface_attribute</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">The extract identity establishes RRB context, but the displayed excerpt does not separately label the address field source. No master-address update path is documented.</data></node><node id="DATA_RSDI_ACCOUNTING_TOTALS"><data key="node_entity_id">DATA_RSDI_ACCOUNTING_TOTALS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">RSDI Accounting Control and Trust Fund Totals</data><data key="node_acronym">RSDI Accounting Totals</data><data key="node_domain">Title II / Payments &amp; Accounting</data><data key="node_description">Accounting, payment-certification, trust-fund, Medicare-premium, and statistical totals accumulated by RSDI-ACCT and used to validate Title II payment/MBR integrity and support financial/trust-fund reporting.</data><data key="node_observed_status">historically_documented_current_catalog_parent</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">4</data><data key="node_notes">The PIA documents this data function in 2007; current catalog listing supports parent-system continuity but not unchanged physical implementation.</data></node><node id="DATA_RSI_APPLICATION_VOLUMES"><data key="node_entity_id">DATA_RSI_APPLICATION_VOLUMES</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Retirement and Survivor Insurance Application Volumes</data><data key="node_acronym">RSI Application Volumes</data><data key="node_domain">Title II / Public Data</data><data key="node_description">Monthly national volumes of Retirement and Survivors Insurance applications and initial Medicare claims, including receipt and completion counts.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA Open Data covers FY2009 and later and documents nightly MCS-to-Title II ODS collection plus DOWR reporting dates.</data></node><node id="DATA_RS_CONTACT"><data key="node_entity_id">DATA_RS_CONTACT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Resident Station Contact Information</data><data key="node_domain">Operations / Office Data</data><data key="node_description">Public machine-readable resident-station information distributed with SSA office-location data.</data><data key="node_observed_status">current_public_data_product</data><data key="node_observed_as_of">2026-03-09</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1734.</data></node><node id="DATA_SAVE_CLASS_OF_ADMISSION"><data key="node_entity_id">DATA_SAVE_CLASS_OF_ADMISSION</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SAVE Class of Admission Code</data><data key="node_acronym">Class of Admission</data><data key="node_domain">Identity / Immigration Attribute</data><data key="node_description">Class-of-Admission or immigration-status code displayed in the online SAVE response and interpreted with the eligibility statement and submitted documentation.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">The code does not by itself establish the statutory basis for lawful presence.</data></node><node id="DATA_SAVE_COUNTRY_OF_BIRTH"><data key="node_entity_id">DATA_SAVE_COUNTRY_OF_BIRTH</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SAVE Country of Birth</data><data key="node_acronym">SAVE COB</data><data key="node_domain">Identity / Person Attribute</data><data key="node_description">Country of birth returned in applicable online SAVE query responses.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Country of birth is not necessarily nationality/citizenship; current POMS says it is shown when an A-Number is used.</data></node><node id="DATA_SAVE_DATE_ADMITTED_TO"><data key="node_entity_id">DATA_SAVE_DATE_ADMITTED_TO</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SAVE Date Admitted To</data><data key="node_acronym">Date Admitted To</data><data key="node_domain">Identity / Immigration Attribute</data><data key="node_description">Date-admitted-to value returned in the online SAVE response.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Response attribute; no independent storage or master-record update is inferred.</data></node><node id="DATA_SAVE_DATE_OF_ENTRY"><data key="node_entity_id">DATA_SAVE_DATE_OF_ENTRY</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SAVE Date of Entry</data><data key="node_acronym">SAVE Date of Entry</data><data key="node_domain">Identity / Immigration Attribute</data><data key="node_description">Date of entry returned in the online SAVE response.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Response attribute used with immigration evidence; no SSA master-record write is inferred.</data></node><node id="DATA_SAVE_DHS_SSN"><data key="node_entity_id">DATA_SAVE_DHS_SSN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">DHS-Record SSN in SAVE Response</data><data key="node_acronym">SAVE DHS SSN</data><data key="node_domain">Identity / Person Attribute</data><data key="node_description">SSN value shown from the DHS record in an applicable SAVE query response.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">POMS warns this SSN was usually supplied to DHS by the alien and may be inaccurate; SSA is told not to verify it or request DHS correction if incorrect.</data></node><node id="DATA_SAVE_DOB"><data key="node_entity_id">DATA_SAVE_DOB</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SAVE Date of Birth</data><data key="node_acronym">SAVE DOB</data><data key="node_domain">Identity / Person Attribute</data><data key="node_description">Date of birth returned from the DHS record in an online SAVE query response.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Response attribute; not modeled as authoritative SSA master data.</data></node><node id="DATA_SAVE_ELIGIBILITY_STATEMENT"><data key="node_entity_id">DATA_SAVE_ELIGIBILITY_STATEMENT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SAVE Eligibility Statement</data><data key="node_acronym">Eligibility Statement</data><data key="node_domain">Identity / Immigration Verification</data><data key="node_description">Eligibility Statement value returned on SSA SAVE query responses as part of DHS immigration-status verification.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Certain Eligibility Statement messages require additional verification and cannot alone establish status.</data></node><node id="DATA_SAVE_QUERY_RESPONSE"><data key="node_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SAVE Query Response</data><data key="node_acronym">SAVE Response</data><data key="node_domain">Identity / Immigration Verification</data><data key="node_description">Online response propagated from DHS records to SSA for a SAVE query using an A-Number or admission number; includes identity and immigration-status attributes.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Treat as a query-response artifact. Current policy requires comparison to submitted immigration evidence and does not establish a standalone SSA response database.</data></node><node id="DATA_SAVE_VERIFICATION_NUMBER"><data key="node_entity_id">DATA_SAVE_VERIFICATION_NUMBER</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SAVE Verification Number</data><data key="node_acronym">SAVE Verification No.</data><data key="node_domain">Identity / Immigration Verification</data><data key="node_description">Verification number returned by online SAVE.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Transaction/verification attribute; persistence beyond the documented response/evidence workflow is not established.</data></node><node id="DATA_SDX_CURRENT_REC_IND"><data key="node_entity_id">DATA_SDX_CURRENT_REC_IND</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SDX Current Records Indicator</data><data key="node_domain">external exchanges</data><data key="node_description">Indicator used in SDX to identify the most current record on file when multiple transactions generate more than one SDX record.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Exchange sequencing/current-record field.</data></node><node id="DATA_SDX_PAYMENT_STATUS"><data key="node_entity_id">DATA_SDX_PAYMENT_STATUS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SDX SSI Payment Status and Ineligibility Reason</data><data key="node_domain">Title XVI / State Data Exchange</data><data key="node_description">SDX includes SSI payment-status code allowing States to determine reason for SSI nonpayment and related Medicaid continuation obligations.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_SDX_REP_PAYEE_ADDR"><data key="node_entity_id">DATA_SDX_REP_PAYEE_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SDX Representative Payee Address</data><data key="node_domain">address provenance</data><data key="node_description">Representative payee address fields carried in SDX, including address lines, city, State, ZIP, and ZIP+4 where available.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Payee contact/address representation in the exchange.</data></node><node id="DATA_SDX_RESIDENCY_BEGIN"><data key="node_entity_id">DATA_SDX_RESIDENCY_BEGIN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SDX Date Residency Began</data><data key="node_domain">address provenance</data><data key="node_description">SDX date indicating when residence in the reported State/county jurisdiction began; documentation says it is updated by interstate or intrastate moves.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Jurisdiction/residency provenance field.</data></node><node id="DATA_SDX_RESPONSE"><data key="node_entity_id">DATA_SDX_RESPONSE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SDX Response Record</data><data key="node_domain">external exchanges</data><data key="node_description">Structured State Data Exchange record carrying SSI eligibility/payment, identity, address, jurisdiction, representative-payee, and other recipient information.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Record-layout object; no distinct physical repository inferred.</data></node><node id="DATA_SERS_FEE_RECEIPT"><data key="node_entity_id">DATA_SERS_FEE_RECEIPT</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SERS Non-Programmatic Fee Receipt</data><data key="node_domain">Finance / Payments</data><data key="node_description">Receipt printed for customer after successful SERS payment transaction; storage of receipt copy not established.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_SERS_REFUND_REQUEST"><data key="node_entity_id">DATA_SERS_REFUND_REQUEST</data><data key="node_entity_type">logical_data_element</data><data key="node_canonical_name">SERS Non-Programmatic Refund Request Data</data><data key="node_domain">Finance / Address Provenance</data><data key="node_description">FO-submitted refund request carries SERS order number, customer name, taxpayer ID/SSN, refund mailing address and amount; not an SSA program address master.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Address arises from a refund request and is used for payment correspondence. No evidence of MBR, SSR or Numident update.</data></node><node id="DATA_SIPP"><data key="node_entity_id">DATA_SIPP</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Survey of Income and Program Participation</data><data key="node_acronym">SIPP</data><data key="node_domain">External Data / Census / Research</data><data key="node_description">U.S. Census Bureau survey data used by SSA as an input to the MINT8 microsimulation model when matched to SSA administrative records.</data><data key="node_observed_status">observed_current_external_input</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled as an external data asset; Atlas does not imply SSA owns the source survey.</data></node><node id="DATA_SOLQ_ID_DISCREP"><data key="node_entity_id">DATA_SOLQ_ID_DISCREP</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SOLQ Identity Discrepancy Code</data><data key="node_domain">person identity</data><data key="node_description">Identity discrepancy code returned in the SOLQ Type 1 response.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Exchange verification result.</data></node><node id="DATA_SOLQ_MULTI_SSN"><data key="node_entity_id">DATA_SOLQ_MULTI_SSN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SOLQ Multiple SSN Indicator and List</data><data key="node_domain">person identity</data><data key="node_description">Multiple-SSN indicator and related SSN list fields documented in the SOLQ/SOLQ-I response record.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Exchange identity data; no separate repository inferred.</data></node><node id="DATA_SOLQ_T16_RESPONSE"><data key="node_entity_id">DATA_SOLQ_T16_RESPONSE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SOLQ/SOLQ-I Type 3 Title XVI Response</data><data key="node_acronym">SOLQ Type 3</data><data key="node_domain">External Data Exchange / Title XVI</data><data key="node_description">Title XVI response structure appended to the SOLQ/SOLQ-I Type 1 identity response, including SSI status, income, payee, mailing address, residence address, multiple-SSN and payment fields.</data><data key="node_observed_status">observed_current_record_layout</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The record layout ties address ZIP+4 fields to the SSR/SSI master file and describes multiple other SSI record elements. Read-only exchange output is not an SSA address-update path.</data></node><node id="DATA_SOLQ_T1_RESPONSE"><data key="node_entity_id">DATA_SOLQ_T1_RESPONSE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SOLQ Type 1 Response</data><data key="node_domain">external exchanges</data><data key="node_description">SOLQ/SOLQ-I Type 1 response structure containing identity-verification inputs and response fields such as SSN, name, date of birth, sex, discrepancy, and verification information.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Real-time exchange response structure.</data></node><node id="DATA_SOLQ_T2_RESPONSE"><data key="node_entity_id">DATA_SOLQ_T2_RESPONSE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SOLQ/SOLQ-I Type 2 Title II Response</data><data key="node_acronym">SOLQ Type 2</data><data key="node_domain">External Data Exchange / Title II</data><data key="node_description">Title II response structure appended to the SOLQ/SOLQ-I Type 1 identity response, including benefit, payment, address, entitlement, death and Medicare-related fields.</data><data key="node_observed_status">observed_current_record_layout</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The record layout explicitly identifies several fields as reflecting Master Beneficiary Record data. It does not establish that every Type 2 field is sourced exclusively from MBR.</data></node><node id="DATA_SOLQ_VERIFY_CODE"><data key="node_entity_id">DATA_SOLQ_VERIFY_CODE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SOLQ Verification Code</data><data key="node_domain">person identity</data><data key="node_description">Verification code returned in the SOLQ Type 1 response with SSN verification data.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Exchange verification result.</data></node><node id="DATA_SSA1020_OCR"><data key="node_entity_id">DATA_SSA1020_OCR</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA-1020-OCR Extra Help Application</data><data key="node_acronym">SSA-1020-OCR</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">Scannable paper application for Medicare Part D Extra Help.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_SSA455"><data key="node_entity_id">DATA_SSA455</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA-455 Disability Update Report</data><data key="node_acronym">SSA-455</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">CDR mailer form used to collect updates on medical condition, treatment, training, and work activity; current SSA Forms catalog offers electronic completion and PDF upload.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA also names SSA-455-OCR-SM and SSA-455-APP variants. They are recorded as variants/aliases here only at the form-family level; the Atlas does not assert that all variants are technically identical.</data></node><node id="DATA_SSA545"><data key="node_entity_id">DATA_SSA545</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA-545-BK Plan to Achieve Self-Support Application</data><data key="node_acronym">SSA-545-BK</data><data key="node_domain">Title XVI / Work Incentives</data><data key="node_description">PASS application form and retained evidentiary artifact.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_SSA552"><data key="node_entity_id">DATA_SSA552</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA-552 Dedicated Account Use of Funds Statement</data><data key="node_acronym">SSA-552</data><data key="node_domain">Representative Payee / SSI</data><data key="node_description">Dedicated-account use statement signed by a representative payee acknowledging permitted-use restrictions and reporting responsibilities.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents electronic completion via Upload Documents, TED initiation, WorkTrack routing and NDRed storage through Evidence Portal.</data></node><node id="DATA_SSA721_SURVIVOR_ADDRESS"><data key="node_entity_id">DATA_SSA721_SURVIVOR_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSA-721 Survivor Address</data><data key="node_domain">Death / Survivor Leads / Address Provenance</data><data key="node_description">Address of a surviving spouse or minor/disabled adult child when supplied on SSA-721.</data><data key="node_observed_status">observed_current_form_attribute</data><data key="node_observed_as_of">2026-05-29</data><data key="node_confidence">5</data><data key="node_notes">POMS documents use to send a Survivor letter in DPS. It is a lead/contact attribute; no master-address update is established.</data></node><node id="DATA_SSA8102"><data key="node_entity_id">DATA_SSA8102</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA-8102 Advance Payment or Immediate Payment Receipt and Notice</data><data key="node_acronym">SSA-8102</data><data key="node_domain">Payments / Field Office / Evidence</data><data key="node_description">Receipt-and-notice form used for emergency advance and immediate payments and retained in SSA electronic evidence after payment release.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current September 2026 POMS places the form in the inForm Library and directs technicians to upload the file copy through Evidence Portal after payment release.</data></node><node id="DATA_SSA8240"><data key="node_entity_id">DATA_SSA8240</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA-8240 Wage and Employment Information Authorization</data><data key="node_acronym">SSA-8240</data><data key="node_domain">Earnings / Authorization</data><data key="node_description">Authorization used to obtain wage and employment information from payroll data providers for SSDI and SSI, including PIE use.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS states SSA-8240 or WEIA application pages are the authorized means for WEIA. Current Forms catalog routes electronic completion through Upload Documents.</data></node><node id="DATA_SSA_COMPREHENSIVE_LISTING"><data key="node_entity_id">DATA_SSA_COMPREHENSIVE_LISTING</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA Comprehensive Data Listing</data><data key="node_acronym">Comprehensive Data Listing</data><data key="node_domain">Enterprise Data / Open Data</data><data key="node_description">SSA inventory of authoritative primary/originating data assets and associated public endpoints, available through the Federal Data Catalog and downloadable in structured formats.</data><data key="node_observed_status">observed_current_inventory</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">SSA Open Data page states the inventory was last updated August 24, 2026.</data></node><node id="DATA_SSA_DISABILITY_CLAIM_DATA"><data key="node_entity_id">DATA_SSA_DISABILITY_CLAIM_DATA</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSA Fiscal Year Disability Claim Data</data><data key="node_domain">Disability / DDS / Public Data</data><data key="node_description">Public SSA dataset reporting state-agency disability claim receipts, determinations, and favorable determinations by fiscal year.</data><data key="node_observed_status">observed_current_public_data_product</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA documentation states these workload measures come entirely from DIODS and exclude claims never referred to a state agency or adjudicative federal component.</data></node><node id="DATA_SSA_INCARCERATION_DNP"><data key="node_entity_id">DATA_SSA_INCARCERATION_DNP</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">SSA Incarceration Data (Do Not Pay source)</data><data key="node_domain">Program Integrity / Incarceration / External Exchange</data><data key="node_description">SSA-owned data source described by Treasury as containing 2025-2026 information on individuals incarcerated in local, state, county, and non-federal facilities as reported to SSA.</data><data key="node_observed_status">planned_dnp_availability</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Treasury lists federal and state usage as coming soon and product availability through Do Not Pay Connect; no current consuming program or transport is inferred.</data></node><node id="DATA_SSA_WEB_INCIDENT_HISTORY"><data key="node_entity_id">DATA_SSA_WEB_INCIDENT_HISTORY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA Web Services Incident History</data><data key="node_acronym">SSA Status History</data><data key="node_domain">Infrastructure / Availability / Publication Data</data><data key="node_description">Public historical incident and scheduled-maintenance record exposed by SSA Web Services Status, including my Social Security network disruptions and maintenance windows.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Operational history only; root cause beyond the public incident narrative is not inferred.</data></node><node id="DATA_SSIDPP_CASE_CONTROL"><data key="node_entity_id">DATA_SSIDPP_CASE_CONTROL</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSIDPP Case Control Sheet</data><data key="node_acronym">SSIDPP Case Control</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">Case-control artifact prepared for each SSN affected by an SSI duplicate-record case.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Used together with Numident and SSID data in the SSI Duplicate Payment Project.</data></node><node id="DATA_SSID_CRZD_SEGMENT"><data key="node_entity_id">DATA_SSID_CRZD_SEGMENT</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SSID CRZD Segment</data><data key="node_acronym">CRZD</data><data key="node_domain">Title XVI / SSI Query / Selection Control</data><data key="node_description">SSID segment carrying redetermination and limited-issue selection indicators and profile-related workload information.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS uses CRZD selection indicators to identify multiple RZ/LI case types.</data></node><node id="DATA_SSID_DIAR_SEGMENT"><data key="node_entity_id">DATA_SSID_DIAR_SEGMENT</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SSID DIAR Segment</data><data key="node_acronym">DIAR</data><data key="node_domain">Title XVI / SSI Query / Work Control</data><data key="node_description">SSID segment that carries diary maturity information, including dedicated-account monitoring DI diary maturity dates.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies the logical segment; physical database layout is not inferred.</data></node><node id="DATA_SSID_REPY_SEGMENT"><data key="node_entity_id">DATA_SSID_REPY_SEGMENT</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SSID REPY Segment</data><data key="node_acronym">REPY</data><data key="node_domain">Title XVI / Representative Payee / SSI Query</data><data key="node_description">SSID representative-payee segment used before redetermination to expose payee/custody information and accounting-control indicators.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS references Type of Payee, Custody, conserved-funds and PA-code information in REPY.</data></node><node id="DATA_SSITMS_TRUST_CASE"><data key="node_entity_id">DATA_SSITMS_TRUST_CASE</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">SSITMS Trust Review Case Record</data><data key="node_acronym">SSITMS Trust Case</data><data key="node_domain">Title XVI / Resources / Trusts / Person Data</data><data key="node_description">Case-level trust review information entered into SSITMS, including claimant or recipient name, representative payee name when applicable, SSN, trust type, remarks, review status, and results.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Field-level set is limited to items explicitly named in POMS; persistence and physical schema are not inferred.</data></node><node id="DATA_SSI_ABLE_ACCOUNT"><data key="node_entity_id">DATA_SSI_ABLE_ACCOUNT</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">SSI ABLE Account Information</data><data key="node_acronym">ABLE Account Data</data><data key="node_domain">Title XVI / Resources</data><data key="node_description">ABLE account information maintained for SSI resource treatment, including State/account identifiers, ownership/signature-authority attributes, dates, and balances; current POMS documents use of the SSI Claims System.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 POMS confirms current SSI Claims System handling and State exchange. Earlier 2021 PIA evidence that ABLE information was stored in the MSSICS database is retained as historical architecture; no physical migration is inferred.</data></node><node id="DATA_SSI_ABLE_BALANCE"><data key="node_entity_id">DATA_SSI_ABLE_BALANCE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI ABLE Account Balance Information</data><data key="node_acronym">ABLE Balance</data><data key="node_domain">Title XVI / Resources / External Data</data><data key="node_description">ABLE account balance month/year and balance amount maintained in the SSI Claims System.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">After the account is documented, subsequent matching State reports can automatically update balance information.</data></node><node id="DATA_SSI_ABLE_DISTRIBUTION"><data key="node_entity_id">DATA_SSI_ABLE_DISTRIBUTION</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">State-Reported ABLE Distribution Data in SSI Claims System</data><data key="node_acronym">ABLE Distribution Data</data><data key="node_domain">Title XVI / Resources / External Data</data><data key="node_description">ABLE distribution information obtained from State data exchange and present in the SSI Claims System.</data><data key="node_observed_status">present_but_currently_not_user_accessible</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says staff cannot access State-exchange distribution data until additional system enhancements are completed.</data></node><node id="DATA_SSI_ABLE_PREPAID_CARD"><data key="node_entity_id">DATA_SSI_ABLE_PREPAID_CARD</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI ABLE Prepaid Debit Card Resource Record</data><data key="node_acronym">ABLE Prepaid Debit Card</data><data key="node_domain">Title XVI / Resources</data><data key="node_description">SSI resource record for an ABLE prepaid debit card, including program State, ABLE account number, intended use, alleged value, and excluded amount.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directs use of the Other Resource page and a dedicated exclusion reason.</data></node><node id="DATA_SSI_ALIEN_STATUS_CODE"><data key="node_entity_id">DATA_SSI_ALIEN_STATUS_CODE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Alien Status Code</data><data key="node_acronym">Alien Status</data><data key="node_domain">Title XVI / Identity / Immigration</data><data key="node_description">SSI Alien Status page code used in lawful-presence evidence, including K, S, Y, and 3 in the current policy example.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Program-claim evidence code; Numident coding alone is explicitly insufficient proof of lawful presence.</data></node><node id="DATA_SSI_ALIEN_STATUS_VERIFIED"><data key="node_entity_id">DATA_SSI_ALIEN_STATUS_VERIFIED</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Alien Status Verified Indicator</data><data key="node_acronym">Alien Status Verified</data><data key="node_domain">Title XVI / Identity / Immigration</data><data key="node_description">Yes/no verification indicator on the SSI Alien Status page used when prior SSI records establish acceptable lawful-presence evidence.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Evidence-status attribute.</data></node><node id="DATA_SSI_AR_IVA1_POP"><data key="node_entity_id">DATA_SSI_AR_IVA1_POP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.A1 Social Security Area Population</data><data key="node_acronym">IV.A1</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Historical and projected Social Security area population under intermediate assumptions, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVA2_FBR"><data key="node_entity_id">DATA_SSI_AR_IVA2_FBR</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.A2 Federal Benefit Rate Increases and Levels</data><data key="node_acronym">IV.A2</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Historical and projected SSI federal benefit rate increases and levels, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVB1_APPLICATIONS"><data key="node_entity_id">DATA_SSI_AR_IVB1_APPLICATIONS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B1 Federally Administered Applications</data><data key="node_acronym">SSI IV.B1</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Historical and projected SSI federally administered applications by calendar year through 2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as part of OACT 2026 SSI supplemental single-year tables. Internal production system and ETL implementation are not inferred.</data></node><node id="DATA_SSI_AR_IVB2_NEW_RECIPIENTS"><data key="node_entity_id">DATA_SSI_AR_IVB2_NEW_RECIPIENTS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B2 New Recipients</data><data key="node_acronym">SSI IV.B2</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Historical and projected new recipients resulting from SSI applications by calendar year through 2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as part of OACT 2026 SSI supplemental single-year tables. Internal production system and ETL implementation are not inferred.</data></node><node id="DATA_SSI_AR_IVB3_DEATH_TERMS"><data key="node_entity_id">DATA_SSI_AR_IVB3_DEATH_TERMS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B3 Terminations Due to Death</data><data key="node_acronym">SSI IV.B3</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Historical and projected SSI federally administered terminations due to death by calendar year through 2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as part of OACT 2026 SSI supplemental single-year tables. Internal production system and ETL implementation are not inferred.</data></node><node id="DATA_SSI_AR_IVB4_NONDEATH_TERMS"><data key="node_entity_id">DATA_SSI_AR_IVB4_NONDEATH_TERMS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B4 Terminations Other Than Death</data><data key="node_acronym">IV.B4</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">SSI federally administered terminations due to reasons other than death, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVB5_ALL_TERMS"><data key="node_entity_id">DATA_SSI_AR_IVB5_ALL_TERMS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B5 Terminations for All Reasons</data><data key="node_acronym">IV.B5</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">SSI federally administered terminations for all reasons, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVB6_FED_CP"><data key="node_entity_id">DATA_SSI_AR_IVB6_FED_CP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B6 Recipients With Federal Payments in Current-Payment Status</data><data key="node_acronym">IV.B6</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">SSI recipients with federal payments in current-payment status as of December, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVB7_PREVALENCE"><data key="node_entity_id">DATA_SSI_AR_IVB7_PREVALENCE</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B7 Federal SSI Prevalence Rates</data><data key="node_acronym">IV.B7</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Federal SSI prevalence rates as of December, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVB8_STATE_ONLY_CP"><data key="node_entity_id">DATA_SSI_AR_IVB8_STATE_ONLY_CP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B8 State Supplementation-Only Recipients in Current-Payment Status</data><data key="node_acronym">IV.B8</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Recipients with federally administered State supplementation payments only in current-payment status, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVB9_ALL_ADMIN_CP"><data key="node_entity_id">DATA_SSI_AR_IVB9_ALL_ADMIN_CP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.B9 Federally Administered Payment Recipients in Current-Payment Status</data><data key="node_acronym">IV.B9</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Recipients with federally administered payments in current-payment status, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVC1_FED_PAYMENTS"><data key="node_entity_id">DATA_SSI_AR_IVC1_FED_PAYMENTS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.C1 Federal Payments</data><data key="node_acronym">SSI IV.C1</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">SSI Federal payments in current dollars by calendar year, published as a supplemental single-year series.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as part of OACT 2026 SSI supplemental single-year tables. Internal production system and ETL implementation are not inferred.</data></node><node id="DATA_SSI_AR_IVC2_FY_FED_PAY"><data key="node_entity_id">DATA_SSI_AR_IVC2_FY_FED_PAY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.C2 Federal Payments by Fiscal Year</data><data key="node_acronym">IV.C2</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">SSI federal payments in current dollars, fiscal years 1978-2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVC3_CPI_FED_PAY"><data key="node_entity_id">DATA_SSI_AR_IVC3_CPI_FED_PAY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.C3 Federal Payments in CPI-Indexed 2026 Dollars</data><data key="node_acronym">IV.C3</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">SSI federal payments in CPI-indexed 2026 dollars, calendar years 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVC4_STATE_SUPP_PAY"><data key="node_entity_id">DATA_SSI_AR_IVC4_STATE_SUPP_PAY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.C4 Federally Administered State Supplementation Payments</data><data key="node_acronym">IV.C4</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Federally administered State supplementation payments in current dollars, 1974-2025.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVD1_GDP"><data key="node_entity_id">DATA_SSI_AR_IVD1_GDP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.D1 Federal Payments as a Percentage of GDP</data><data key="node_acronym">IV.D1</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">SSI federal payments as a percentage of GDP, 1974-2050.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_IVE1_COSTS"><data key="node_entity_id">DATA_SSI_AR_IVE1_COSTS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.E1 Selected SSI Costs</data><data key="node_acronym">IV.E1</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Selected SSI costs, fiscal years 1978-2026.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published by OACT as a 2026 SSI Annual Report supplemental single-year table in HTML and Excel; internal production stack not inferred.</data></node><node id="DATA_SSI_AR_VC1_ADULT_DISP"><data key="node_entity_id">DATA_SSI_AR_VC1_ADULT_DISP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table V.C1 Disabled Adult Claim Dispositions</data><data key="node_acronym">SSI V.C1</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Disposition of adult SSI disability applications by year of filing and level of decision.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as part of OACT 2026 SSI supplemental single-year tables. Internal production system and ETL implementation are not inferred.</data></node><node id="DATA_SSI_AR_VC2_CHILD_DISP"><data key="node_entity_id">DATA_SSI_AR_VC2_CHILD_DISP</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table V.C2 Disabled Child Claim Dispositions</data><data key="node_acronym">SSI V.C2</data><data key="node_domain">Actuarial / SSI / Publication Data</data><data key="node_description">Disposition of child SSI disability applications by year of filing and level of decision.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Published as part of OACT 2026 SSI supplemental single-year tables. Internal production system and ETL implementation are not inferred.</data></node><node id="DATA_SSI_CMRV"><data key="node_entity_id">DATA_SSI_CMRV</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Current Market Rental Value</data><data key="node_acronym">CMRV</data><data key="node_domain">Title XVI / Living Arrangements</data><data key="node_description">Current market rental value used with rental amount in SSI rental-subsidy determinations.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS requires verifying/updating CMRV when processing the E2 diary.</data></node><node id="DATA_SSI_DTAC"><data key="node_entity_id">DATA_SSI_DTAC</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI D-TAC</data><data key="node_acronym">D-TAC</data><data key="node_domain">Title XVI / Payments / Accounting</data><data key="node_description">SSI transaction/accounting control used in a CORE erroneous-death correction scenario to prevent an underpayment from being released.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS names D-TAC operationally but does not expand the acronym or disclose implementation details.</data></node><node id="DATA_SSI_IRS_CONTROLLED_ALERT"><data key="node_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI/IRS Controlled Alert</data><data key="node_acronym">Controlled IRS Alert</data><data key="node_domain">Title XVI / IRS interface</data><data key="node_description">IRS interface alert for SSI records exceeding specified tolerances; associated cases receive a 5B diary on the SSR.</data><data key="node_observed_status">observed_current_poms</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Alert is described as a printout from the IRS database; distinguish from the SSR 5B diary itself.</data></node><node id="DATA_SSI_IRS_INFORMATIONAL_ALERT"><data key="node_entity_id">DATA_SSI_IRS_INFORMATIONAL_ALERT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI/IRS Informational Alert</data><data key="node_acronym">Informational IRS Alert</data><data key="node_domain">Title XVI / IRS interface</data><data key="node_description">Informational IRS interface alert for specified high-error-profile redeterminations with resource indicators below controlled-alert tolerance.</data><data key="node_observed_status">observed_current_poms</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Available through MI Central; SSTNG availability documented for high-error-profile RZ cases; disclosure/destruction rules apply.</data></node><node id="DATA_SSI_IRS_NONWAGE"><data key="node_entity_id">DATA_SSI_IRS_NONWAGE</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">SSI IRS Non-Wage Income and Resource Data</data><data key="node_acronym">SSI IRS Non-Wage Data</data><data key="node_domain">Title XVI / IRS Match / Program Integrity</data><data key="node_description">IRS-derived non-wage income/resource information from Form 1099 and similar financial-transaction reports used in the SSI IRS interface and 5B alert process.</data><data key="node_observed_status">observed_current_interface_data</data><data key="node_observed_as_of">2026-02-25</data><data key="node_confidence">5</data><data key="node_notes">Treat as restricted interface/match data. It is not a verified SSI fact or an address-master update merely because it appears in the interface.</data></node><node id="DATA_SSI_MONTHLY_STATS"><data key="node_entity_id">DATA_SSI_MONTHLY_STATS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Monthly Statistics</data><data key="node_acronym">SSI Monthly Statistics</data><data key="node_domain">Title XVI / Statistics</data><data key="node_description">Recurring SSA statistical publication reporting SSI recipient and payment measures; July 2026 tables identify the Supplemental Security Record as the source using 100 percent data.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-07</data><data key="node_confidence">5</data><data key="node_notes">Publication/data-product lineage only. This record does not imply a particular ETL, warehouse, database engine, or publication-generation platform.</data></node><node id="DATA_SSI_PAYMENT_FILES"><data key="node_entity_id">DATA_SSI_PAYMENT_FILES</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">SSI Payment Files</data><data key="node_acronym">SSI Payment Files</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Non-public SSA payment files sent to the Department of the Treasury to pay SSI recipients.</data><data key="node_observed_status">current_federal_data_catalog</data><data key="node_observed_as_of">2026-08-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-588. The catalog does not specify file format, transport, cadence, or internal staging.</data></node><node id="DATA_SSI_PROTECTIVE_FILING_DATE"><data key="node_entity_id">DATA_SSI_PROTECTIVE_FILING_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Protective Filing Date</data><data key="node_acronym">Protective Filing Date</data><data key="node_domain">Title XVI / Intake / Filing</data><data key="node_description">Date protected by an SSI oral inquiry when policy criteria are satisfied; current POMS examples show technicians documenting this date in eLAS and later using it as the application filing date when applicable.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical business data element; physical field name and storage schema are not disclosed.</data></node><node id="DATA_SSI_PS_T20"><data key="node_entity_id">DATA_SSI_PS_T20</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">SSI Payment Status T20</data><data key="node_acronym">T20</data><data key="node_domain">Title XVI / Payment Status</data><data key="node_description">SSI payment status used to terminate an incorrect duplicate record when duplicate payment was made.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="DATA_SSI_PS_T50"><data key="node_entity_id">DATA_SSI_PS_T50</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">SSI Payment Status T50</data><data key="node_acronym">T50</data><data key="node_domain">Title XVI / Payment Status</data><data key="node_description">SSI payment status used to terminate an incorrect duplicate record when no payment was made, preventing duplicate issuance.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="DATA_SSI_PTAC"><data key="node_entity_id">DATA_SSI_PTAC</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI P-TAC</data><data key="node_acronym">P-TAC</data><data key="node_domain">Title XVI / Payments / Accounting</data><data key="node_description">SSI transaction/accounting control used in a CORE erroneous-death correction scenario to establish an overpayment equal to the affected payment.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS names P-TAC operationally but does not expand the acronym or disclose implementation details.</data></node><node id="DATA_SSI_PUF_2001"><data key="node_entity_id">DATA_SSI_PUF_2001</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Public-Use Microdata File, 2001</data><data key="node_acronym">SSI PUF 2001</data><data key="node_domain">Research / Public-Use Microdata</data><data key="node_description">Deidentified public-use extract from the Supplemental Security Record for persons receiving federal SSI in December 2001; 5 percent representative sample, about 320,000 records and 13 fields.</data><data key="node_observed_status">historical_public_use_currently_available</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Released October 2003; SAS and CSV distributions. Direct identifiers are removed and disclosure-avoidance transformations are applied.</data></node><node id="DATA_SSI_RENTAL_SUBSIDY_AMOUNT"><data key="node_entity_id">DATA_SSI_RENTAL_SUBSIDY_AMOUNT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Rental Subsidy Amount</data><data key="node_acronym">Rental Subsidy Amount</data><data key="node_domain">Title XVI / Living Arrangements</data><data key="node_description">Rental-subsidy value used in SSI living-arrangement processing and the E2 diary workflow.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS requires review/update during E2 diary processing.</data></node><node id="DATA_SSI_RES_STATE_COUNTY"><data key="node_entity_id">DATA_SSI_RES_STATE_COUNTY</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI State and County of Residence Code</data><data key="node_acronym">SSI Residence State/County</data><data key="node_domain">Title XVI / Address / Residency</data><data key="node_description">State and county residence coding maintained on the SSR for SSI and state-supplement administration.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">MSSICS/LRES may prefill codes from alleged residence/ZIP; policy requires correction when the prefill is wrong.</data></node><node id="DATA_SSI_SINGLE_YEAR_2026"><data key="node_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 SSI Annual Report Supplemental Single-Year Tables</data><data key="node_acronym">SSI 2026 Single-Year Tables</data><data key="node_domain">Actuarial / SSI / Statistical Publications</data><data key="node_description">Supplemental historical and projected single-year tables consistent with the 2026 SSI Annual Report, published in HTML and Microsoft Excel.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Tables extend single-year detail beyond what the bound annual report can show; report context governs interpretation.</data></node><node id="DATA_SSI_STATE_COUNTY_2025"><data key="node_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Recipients by State and County, 2025</data><data key="node_acronym">SSI State and County 2025</data><data key="node_domain">Title XVI / Statistical Publication / Geography</data><data key="node_description">Annual state- and county-level SSI recipient and payment statistics for December 2025.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Released August 2026; Federal Data Catalog identifier US-GOV-SSA-3416. Publication identifies SSR as principal administrative data source.</data></node><node id="DATA_SSI_UNDERPAY_CTRL_LOG"><data key="node_entity_id">DATA_SSI_UNDERPAY_CTRL_LOG</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Underpayment Control Log</data><data key="node_domain">Title XVI / Payments / Work Control</data><data key="node_description">Manual control log used by SSA employees to track large SSI underpayments that require pre-payment review.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">OIG explicitly describes manual tracking. The public source does not disclose whether the log is a spreadsheet, database, shared list, or another implementation.</data></node><node id="DATA_SSI_US_ADMISSION_DATE"><data key="node_entity_id">DATA_SSI_US_ADMISSION_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI U.S. Admission Date</data><data key="node_acronym">U.S. Admission Date</data><data key="node_domain">Title XVI / Identity / Immigration</data><data key="node_description">Admission-date attribute documented on the SSI Alien Status page for previously established lawful-presence evidence.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Claim evidence attribute, not a Numident authority.</data></node><node id="DATA_SSI_U_TAC"><data key="node_entity_id">DATA_SSI_U_TAC</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI U TAC Manual-Netting Code</data><data key="node_acronym">U TAC</data><data key="node_domain">Title XVI / Earnings / Payment Adjustment</data><data key="node_description">Transaction/action code staff input when manual netting is required after automated SSI redetermination processing cannot complete.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">The public source identifies the code but does not independently document its physical storage.</data></node><node id="DATA_SSI_YTED_CG"><data key="node_entity_id">DATA_SSI_YTED_CG</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Youth Transition Exploration Demonstration Case Characteristics Code</data><data key="node_acronym">YTED CG</data><data key="node_domain">Title XVI / Demonstration / SSR</data><data key="node_description">Case Characteristics code on the SSR Special Message page carrying YTED plus the MMYY demonstration enrollment start month.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-02-06</data><data key="node_confidence">5</data><data key="node_notes">POMS cautions that the code should not be overlaid because it supports demonstration research.</data></node><node id="DATA_SSNAP_REPLACEMENT_CARD_COUNT"><data key="node_entity_id">DATA_SSNAP_REPLACEMENT_CARD_COUNT</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSNAP Replacement Card Count</data><data key="node_acronym">Replacement Card Count</data><data key="node_domain">Identity &amp; Enumeration / SSN Card Controls</data><data key="node_description">Enumeration-system count of replacement SSN cards used to enforce statutory annual and lifetime card limits and displayed on the SSNAP Additional Info screen.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS warns staff not to rely on visual Numident inspection for this count.</data></node><node id="DATA_SSNEC_APP_MAIL_ADDR"><data key="node_entity_id">DATA_SSNEC_APP_MAIL_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSN Application Mailing Address</data><data key="node_acronym">SSN application mailing address</data><data key="node_domain">Identity &amp; Enumeration / Address</data><data key="node_description">Mailing-address information associated with Social Security number applications in the SSNEC/60-0058 record environment.</data><data key="node_observed_status">documented_scope_evolved</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">The 2007 SSNEC PIA describes mailing addresses of individuals filing SSN applications broadly. The 2025 republished 60-0058 SORN explicitly lists mailing addresses in the fraud/suspect-application category. This is application provenance, not an enterprise current-residence master.</data></node><node id="DATA_SSN_CARD_PRINT_FILE"><data key="node_entity_id">DATA_SSN_CARD_PRINT_FILE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSN Card Printing File</data><data key="node_acronym">SSN Card Print File</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">File established by the SSNEC environment from which Social Security cards are printed.</data><data key="node_observed_status">historically_documented_component</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">4</data><data key="node_notes">Detailed component architecture is documented in the 2007 PIA. Current PIA catalog still lists SSNEC, but current physical implementation of this print file is not independently verified.</data></node><node id="DATA_SSN_RETIREMENT_DESIG"><data key="node_entity_id">DATA_SSN_RETIREMENT_DESIG</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Additional SSN Retirement Designation</data><data key="node_acronym">Retired SSN Designation</data><data key="node_domain">Identity &amp; Enumeration / Numident Integrity</data><data key="node_description">Designation that an additional SSN assigned to the same individual is retired, described by SSA OIG as a remediation control for duplicate SSN assignment.</data><data key="node_observed_status">remediation_control_documented_2026</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">OIG documents the control outcome but does not identify the physical field, application, or repository in which retirement status is stored.</data></node><node id="DATA_SSN_SEX_VERIFY_IND"><data key="node_entity_id">DATA_SSN_SEX_VERIFY_IND</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSN Sex Field Verification Indicator</data><data key="node_acronym">Sex Field Verification Indicator</data><data key="node_domain">Identity / Data Exchange</data><data key="node_description">Response data element that SSA may include in an SSN verification exchange only when the requesting entity provides sufficient program need justification and SSA approves disclosure.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Removed from SSNVS employer service in September 2011; for covered data exchanges since 2013 it requires business-need justification.</data></node><node id="DATA_SSR_ACD"><data key="node_entity_id">DATA_SSR_ACD</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Address Change Date</data><data key="node_acronym">ACD</data><data key="node_domain">Title XVI / Address / Record Control</data><data key="node_description">Address change date field on the Supplemental Security Record used to determine the recency of the SSI address during cross-program address development.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Title II undeliverable-mail policy directs staff to compare the SSR ACD with the MBR ADDR Updated value. The field is a recency/control attribute, not a separate address source.</data></node><node id="DATA_SSR_AD"><data key="node_entity_id">DATA_SSR_AD</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Supplemental Security Record Address Field</data><data key="node_acronym">AD</data><data key="node_domain">Title XVI / Address</data><data key="node_description">SSR address field used for the mailing address for notices and, where applicable, checks; with a representative payee it reflects the payee mailing address.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">AD is not necessarily the recipient residence address and is not affected by direct-deposit bank-address data.</data></node><node id="DATA_SSR_CMPH_SEGMENT"><data key="node_entity_id">DATA_SSR_CMPH_SEGMENT</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SSR CMPH Case Characteristics Segment</data><data key="node_acronym">CMPH</data><data key="node_domain">Title XVI / Supplemental Security Record / Address</data><data key="node_description">SSR segment that current interstate COA policy says should be updated with correct residence information after new residence and living-arrangement development.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-08-07</data><data key="node_confidence">5</data><data key="node_notes">Physical record layout is not inferred beyond the named SSR segment.</data></node><node id="DATA_SSR_DD_INDICATOR"><data key="node_entity_id">DATA_SSR_DD_INDICATOR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Direct Deposit Indicator</data><data key="node_acronym">Direct Deposit Indicator</data><data key="node_domain">Title XVI / Payments / Resource Development</data><data key="node_description">Supplemental Security Record indicator whose presence is a lead to develop a financial account during an SSI redetermination.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS documents the indicator as a development lead; internal field code is not identified.</data></node><node id="DATA_SSR_GRC"><data key="node_entity_id">DATA_SSR_GRC</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Pending Grant Reimbursement Code</data><data key="node_acronym">GRC</data><data key="node_domain">Title XVI / Interim Assistance / SSR</data><data key="node_description">Pending grant reimbursement code placed on the Supplemental Security Record when interim assistance reimbursement is pending.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says the code can be added by an FO or an automated interface; source does not identify a single upstream interface.</data></node><node id="DATA_SSR_M1"><data key="node_entity_id">DATA_SSR_M1</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Multiple Social Security Number Field M1</data><data key="node_acronym">M1</data><data key="node_domain">Title XVI / Identity Cross-Reference</data><data key="node_description">Supplemental Security Record field used to cross-reference another SSN associated with an SSI duplicate-record case.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directs entry of correct/wrong SSNs into the M1 field when duplicate records pertain to the same person.</data></node><node id="DATA_SSR_MA"><data key="node_entity_id">DATA_SSR_MA</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Multiple Social Security Number Field MA</data><data key="node_acronym">MA</data><data key="node_domain">Title XVI / Identity Cross-Reference</data><data key="node_description">Supplemental Security Record field used in the duplicate-record workflow when the SSN on the terminated record was also issued to the individual through enumeration.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Condition-specific use in SSIDPP; not a general automatic Numident synchronization field.</data></node><node id="DATA_SSR_OPSQ"><data key="node_entity_id">DATA_SSR_OPSQ</data><data key="node_entity_type">logical_data_element</data><data key="node_canonical_name">SSR Overpayment Sequence Data Segment</data><data key="node_acronym">OPSQ</data><data key="node_domain">Title XVI / Payments &amp; Debt</data><data key="node_description">SSR OPSQ segment carries SSI overpayment sequence information for waiver development and SSA-635 documentation; no DBMS schema inferred.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_SSR_PAYFLAG3"><data key="node_entity_id">DATA_SSR_PAYFLAG3</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Pay Flag 3</data><data key="node_acronym">Pay Flag 3</data><data key="node_domain">Title XVI / Payments / Supplemental Security Record</data><data key="node_description">SSI payment flag used in the CORE erroneous-death correction workflow; an S indicates Treasury returned a credit and Reclamations can overlay it with U before special-voucher reimbursement.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled as an SSR data element. Physical field storage and coding table implementation are not inferred.</data></node><node id="DATA_SSR_PMTH"><data key="node_entity_id">DATA_SSR_PMTH</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Supplemental Security Record Payment History Segment</data><data key="node_acronym">PMTH</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Payment-history segment/display on the Supplemental Security Record used to store check-claim forgery indicators and payment-history status.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-01-27</data><data key="node_confidence">5</data><data key="node_notes">POMS references Payment History - PMTH and the PMTH Segment Display.</data></node><node id="DATA_SSR_RA"><data key="node_entity_id">DATA_SSR_RA</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Supplemental Security Record Residence Field</data><data key="node_acronym">RA</data><data key="node_domain">Title XVI / Address</data><data key="node_description">SSR field used to represent residence or, in certain representative-payee circumstances, the recipient mailing address when it differs from the payee address.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Field semantics vary with representative-payee circumstances; do not equate RA universally with physical residence.</data></node><node id="DATA_SSR_SQD"><data key="node_entity_id">DATA_SSR_SQD</data><data key="node_entity_type">logical_data_element</data><data key="node_canonical_name">SSR Overpayment Sequence Date</data><data key="node_acronym">SQD</data><data key="node_domain">Title XVI / Payments &amp; Debt</data><data key="node_description">SSR OPSQ sequence date (SQD) used to identify pending SSI waiver sequence on SSA-635.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DATA_SSR_UPV_V"><data key="node_entity_id">DATA_SSR_UPV_V</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Underpayment Verification Code V</data><data key="node_acronym">UPV:V</data><data key="node_domain">Title XVI / Underpayments / SSR</data><data key="node_description">Underpayment verification code V used to hold an SSI underpayment while Interim Assistance Reimbursement processing is pending.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS establishes the code and hold behavior.</data></node><node id="DATA_STATE_AGENCY_WORKLOAD_SAMPLING"><data key="node_entity_id">DATA_STATE_AGENCY_WORKLOAD_SAMPLING</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">State Agency Workload Sampling</data><data key="node_acronym">US-GOV-SSA-581</data><data key="node_domain">Disability / DDS / Analytics</data><data key="node_description">Non-public SSA daily data asset used to produce information about distribution of DDS workloads, personnel-resource utilization, and time needed to process individual workloads.</data><data key="node_observed_status">observed_current_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-581. No backend, sampling engine, or relationship to DIODS is inferred without additional evidence.</data></node><node id="DATA_STATE_VEHICLE_TITLE_REG"><data key="node_entity_id">DATA_STATE_VEHICLE_TITLE_REG</data><data key="node_entity_type">external_data_domain</data><data key="node_canonical_name">State Vehicle Title and Registration Information</data><data key="node_acronym">State Vehicle Title/Registration</data><data key="node_domain">Title XVI / Resources / External Verification</data><data key="node_description">State vehicle ownership/title/registration information that SSA employees may obtain from third parties when they suspect an SSI recipient owns an unreported vehicle.</data><data key="node_observed_status">observed_current_external_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">This is a logical external data domain across State sources, not a claim of one national SSA vehicle database.</data></node><node id="DATA_STAT_SUPP_5A_2026"><data key="node_entity_id">DATA_STAT_SUPP_5A_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2026 - Summary of OASDI Benefits in Current-Payment Status (5.A)</data><data key="node_acronym">5.A</data><data key="node_domain">Statistics / OASDI / Publication</data><data key="node_description">2026 Annual Statistical Supplement section reporting OASDI beneficiaries in current-payment status; its tables identify the Master Beneficiary Record as their administrative source.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">2026 edition expands 5.A1 and folds or suppresses statistics formerly published separately in 5.A5, 5.A6, 5.A10, and 5.A16.</data></node><node id="DATA_STAT_SUPP_5L_2026"><data key="node_entity_id">DATA_STAT_SUPP_5L_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2026 - OASDI Representative Payees (5.L)</data><data key="node_acronym">5.L</data><data key="node_domain">Statistical Publications / OASDI / Representative Payee</data><data key="node_description">2026 Annual Statistical Supplement section reporting OASDI beneficiaries in current-payment status with representative payees.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Section 5.L identifies MBR 100-percent data as its source.</data></node><node id="DATA_STAT_SUPP_6A_2026"><data key="node_entity_id">DATA_STAT_SUPP_6A_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2026 - Summary of OASDI Awards (6.A)</data><data key="node_acronym">6.A</data><data key="node_domain">Statistics / Publication</data><data key="node_description">2026 Annual Statistical Supplement section published from SSA administrative program records.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current section identifies Master Beneficiary Record as source; no internal ETL or publication technology inferred.</data></node><node id="DATA_STAT_SUPP_6B_2026"><data key="node_entity_id">DATA_STAT_SUPP_6B_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2026 - OASDI Awards to Retired Workers (6.B)</data><data key="node_acronym">6.B</data><data key="node_domain">Statistics / Publication</data><data key="node_description">2026 Annual Statistical Supplement section published from SSA administrative program records.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current section identifies Master Beneficiary Record as source; no internal ETL or publication technology inferred.</data></node><node id="DATA_STAT_SUPP_6C_2026"><data key="node_entity_id">DATA_STAT_SUPP_6C_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2026 - OASDI Awards to Disabled Workers (6.C)</data><data key="node_acronym">6.C</data><data key="node_domain">Statistics / Publication</data><data key="node_description">2026 Annual Statistical Supplement section published from SSA administrative program records.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current section identifies Master Beneficiary Record as source; no internal ETL or publication technology inferred.</data></node><node id="DATA_STAT_SUPP_6D_2026"><data key="node_entity_id">DATA_STAT_SUPP_6D_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2026 - OASDI Awards to Dependents and Survivors (6.D)</data><data key="node_acronym">6.D</data><data key="node_domain">Statistics / Publication</data><data key="node_description">2026 Annual Statistical Supplement section published from SSA administrative program records.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current section identifies Master Beneficiary Record as source; no internal ETL or publication technology inferred.</data></node><node id="DATA_STAT_SUPP_7A_2026"><data key="node_entity_id">DATA_STAT_SUPP_7A_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2026 - Summary of SSI (7.A)</data><data key="node_acronym">7.A</data><data key="node_domain">Statistics / Publication</data><data key="node_description">2026 Annual Statistical Supplement section published from SSA administrative program records.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current section identifies Supplemental Security Record as source; no internal ETL or publication technology inferred.</data></node><node id="DATA_STAT_SUPP_7E_2026"><data key="node_entity_id">DATA_STAT_SUPP_7E_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2026 - SSI Recipient Characteristics (7.E)</data><data key="node_acronym">7.E</data><data key="node_domain">Statistical Publications / SSI</data><data key="node_description">2026 Annual Statistical Supplement section reporting SSI recipient characteristics including representative-payee, age, sex, living-arrangement and noncitizen statistics.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Section 7.E identifies SSR 100-percent data as its source.</data></node><node id="DATA_STUDENT_EXPECTED_GRAD_DATE"><data key="node_entity_id">DATA_STUDENT_EXPECTED_GRAD_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Student Expected Graduation Date</data><data key="node_acronym">Expected Graduation Date</data><data key="node_domain">Title II / Student Benefits</data><data key="node_description">Expected secondary-school graduation date supplied through student-benefit evidence and used to code the Student Entitlement screen.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">The form supplies the date; public POMS does not establish a stand-alone enterprise field outside the student-benefit workflow.</data></node><node id="DATA_STUDENT_SCHOOL_OPERATING_BASIS"><data key="node_entity_id">DATA_STUDENT_SCHOOL_OPERATING_BASIS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Student School Operating Basis</data><data key="node_acronym">School Operating Basis</data><data key="node_domain">Title II / Student Benefits</data><data key="node_description">School operating basis (yearly or semester/quarterly with or without required re-enrollment) certified by the school official and used to determine student-benefit duration.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational value comes from SSA-1372 certification and is coded in the STUD workflow.</data></node><node id="DATA_SUBMITTED_IDR_LIST"><data key="node_entity_id">DATA_SUBMITTED_IDR_LIST</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Submitted Disability Reports Listing</data><data key="node_domain">Disability / Workload Management</data><data key="node_description">iWMI listing of received Internet Disability Report transmissions requiring field-office action.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS states claimant SSNs appear on the listing the day after IDR submission.</data></node><node id="DATA_SUMS_TAS_CAS_HR_EXTRACT"><data key="node_entity_id">DATA_SUMS_TAS_CAS_HR_EXTRACT</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">SUMS/TAS/CAS Integration</data><data key="node_domain">Enterprise Data / Integration</data><data key="node_description">Current non-public extract of human-resource information used in the SUMS/TAS/CAS integration layer.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-25.</data></node><node id="DATA_SUSPENDED_3P_SUBMITTERS"><data key="node_entity_id">DATA_SUSPENDED_3P_SUBMITTERS</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Suspended Third-Party Submitters</data><data key="node_acronym">Suspended Submitters</data><data key="node_domain">Earnings / Program Integrity</data><data key="node_description">Public BSO page used to identify third-party wage-report submitters suspended from electronic wage reporting when SSA determines publication is appropriate.</data><data key="node_observed_status">observed_current_empty</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA currently states no third-party submitters are suspended. The page is modeled as a publication/control surface, not as proof of the underlying enforcement database.</data></node><node id="DATA_SVB_INDICATOR"><data key="node_entity_id">DATA_SVB_INDICATOR</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Special Veterans Benefit Indicator</data><data key="node_acronym">SVB indicator</data><data key="node_domain">Special Veterans Benefits</data><data key="node_description">Permanent indicator on the Title VIII/SSR record identifying an SVB claim.</data><data key="node_observed_status">current_poms_retained_detailed_topology_old</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="DATA_T16_DD_CHECK_STATS"><data key="node_entity_id">DATA_T16_DD_CHECK_STATS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Supplemental Security Income Direct Deposit and Check Statistics</data><data key="node_acronym">SSI DD/Check Statistics</data><data key="node_domain">Public Data / Title XVI / Payments</data><data key="node_description">SSA public state-level monthly statistics showing SSI check payments, direct-deposit payments, total payments, and percent direct deposit.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">October 2026 publication observed. Internal source database and publication pipeline are not identified on the public page.</data></node><node id="DATA_T2R_COA_ERROR_LOG"><data key="node_entity_id">DATA_T2R_COA_ERROR_LOG</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">T2R Change of Address Notice Error Log</data><data key="node_acronym">T2R COA Error Log</data><data key="node_domain">Title II / Notices / Work Control</data><data key="node_description">Error log receiving incomplete T2R change-of-address notices for systems staff investigation.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Address provenance is explicit: the confirmation notice uses the old mailing address stored on MBR; no separate beneficiary/payee address is available on MBR for this notice.</data></node><node id="DATA_T2R_COA_SKELCOMP"><data key="node_entity_id">DATA_T2R_COA_SKELCOMP</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">T2R Change of Address SKELCOMP Record</data><data key="node_acronym">T2R COA SKELCOMP</data><data key="node_domain">Title II / Notices / Legacy</data><data key="node_description">Legacy notice-composition record formerly generated by T2R for TNA-based formatted notices; generation stopped in October 2022.</data><data key="node_observed_status">retired_2022</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Address provenance is explicit: the confirmation notice uses the old mailing address stored on MBR; no separate beneficiary/payee address is available on MBR for this notice.</data></node><node id="DATA_T2R_COA_XML"><data key="node_entity_id">DATA_T2R_COA_XML</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">T2R Change of Address XML File</data><data key="node_acronym">T2R COA XML</data><data key="node_domain">Title II / Notices / Integration</data><data key="node_description">XML notice data file generated by T2R and used by Customer Communications Management to compose T2R change-of-address confirmation notices beginning in October 2022.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Address provenance is explicit: the confirmation notice uses the old mailing address stored on MBR; no separate beneficiary/payee address is available on MBR for this notice.</data></node><node id="DATA_T2_DD_CHECK_STATS"><data key="node_entity_id">DATA_T2_DD_CHECK_STATS</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Social Security Direct Deposit and Check Statistics</data><data key="node_acronym">Title II DD/Check Statistics</data><data key="node_domain">Public Data / Title II / Payments</data><data key="node_description">SSA public state-level monthly statistics showing Social Security check payments, direct-deposit payments, total payments, and percent direct deposit.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">October 2026 publication observed. Internal source database and publication pipeline are not identified on the public page.</data></node><node id="DATA_T2_OVERPAYMENT_NOTICE"><data key="node_entity_id">DATA_T2_OVERPAYMENT_NOTICE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Title II Overpayment Notice</data><data key="node_acronym">OASDI Overpayment Notice</data><data key="node_domain">Payments / Debt</data><data key="node_description">Written notice to an overpaid Title II individual explaining the overpayment, amount, reason, repayment liability, and required rights/options under current policy.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">Generated through established notice systems such as MACADE, AURORA, or DPS; exact channel is workload-dependent.</data></node><node id="DATA_TAX_GEO_ADDR"><data key="node_entity_id">DATA_TAX_GEO_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Tax-Record Address for Statistical Geographic Assignment</data><data key="node_acronym">Tax-record geographic address</data><data key="node_domain">Address Provenance / Statistics</data><data key="node_description">Address information extracted from worker tax records and used to assign state and county of residence for SSA statistical production/research.</data><data key="node_observed_status">statistical_geographic_input</data><data key="node_observed_as_of">2024-12</data><data key="node_confidence">5</data><data key="node_notes">This is statistical provenance, not an SSA person-master mailing/residence update. Current Earnings and Employment methodology describes W-2 employee residence and addresses matched to self-employment reports.</data></node><node id="DATA_TA_ABLE_ROLLOVER"><data key="node_entity_id">DATA_TA_ABLE_ROLLOVER</data><data key="node_entity_type">business_event</data><data key="node_canonical_name">Trump Account to ABLE Rollover</data><data key="node_acronym">TA-ABLE Rollover</data><data key="node_domain">Title XVI / Resources / ABLE</data><data key="node_description">Trustee-to-trustee transfer of an eligible Trump Account balance to an ABLE account during the calendar year the beneficiary attains age 17.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-07-09</data><data key="node_confidence">5</data><data key="node_notes">Event affects SSI resource treatment; no banking transport or SSA settlement role inferred.</data></node><node id="DATA_TITLE2_APP_FILING_DATE"><data key="node_entity_id">DATA_TITLE2_APP_FILING_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Title II Application Filing Date</data><data key="node_acronym">Application Filing Date</data><data key="node_domain">Title II / Claims / MBR</data><data key="node_description">Title II application filing date, which is the earlier of the valid application receipt date or an applicable protective filing date and can be reflected on the MBR.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS states MCS allows the protective filing date to show as the filing date on MBR to conform to regulations.</data></node><node id="DATA_TITLEII_ZIP_FLAG"><data key="node_entity_id">DATA_TITLEII_ZIP_FLAG</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Title II ZIP Code Flag</data><data key="node_acronym">ZIP Code Flag</data><data key="node_domain">Title II / Address Metadata</data><data key="node_description">Alphanumeric MBR address-control field used for ZIP+4 processing and to record NCOA processing status, including L, P, and X states.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS is dated 2011 but remains in the policy library. L marks notice/verification stage, P indicates MBR address changed from USPS NCOA information, and X suppresses selection for the next NCOA match after beneficiary objection.</data></node><node id="DATA_TITLEII_ZIP_FLAG_DATE"><data key="node_entity_id">DATA_TITLEII_ZIP_FLAG_DATE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Title II ZIP Code Flag Date</data><data key="node_acronym">ZIP Flag Date</data><data key="node_domain">Title II / Address Metadata</data><data key="node_description">Month/year associated with the Title II ZIP Code Flag on the MBR; generated automatically according to SSA ZIP/NCOA policy.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Policy-level field definition; storage beyond the documented MBR association is not inferred.</data></node><node id="DATA_TNEV_TRANSIENT_INPUT"><data key="node_entity_id">DATA_TNEV_TRANSIENT_INPUT</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">TNEV Transient Verification Call Data</data><data key="node_acronym">TNEV Call Data</data><data key="node_domain">Customer Service / Employer / Identity Verification</data><data key="node_description">User credential, employer EIN, and employee identity data collected during an employer-verification call and discarded at the end of the call.</data><data key="node_observed_status">current_documented_transient_data</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current 2025 PIA states the TNEV application does not retain spoken information and data are dropped at end of call.</data></node><node id="DATA_TOEL"><data key="node_entity_id">DATA_TOEL</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Type-of-Event-Level Metadata</data><data key="node_acronym">TOEL</data><data key="node_domain">Processing Center / Work Classification</data><data key="node_description">Hierarchical event classification carried on Paperless Action Control Records to identify the kind of work involved.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS uses TOEL/TOELs terminology; this entity models the metadata concept.</data></node><node id="DATA_TREASURY_CDN"><data key="node_entity_id">DATA_TREASURY_CDN</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Claims Disposition Notice</data><data key="node_acronym">CDN</data><data key="node_domain">Title XVI / Treasury Check Claims</data><data key="node_description">Treasury check-claim status record delivered electronically to SSI systems, including forgery-claim status.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2025-01-27</data><data key="node_confidence">5</data><data key="node_notes">POMS states SSI systems have received an electronic CDN file from Treasury since 2008; transport protocol is not named.</data></node><node id="DATA_TREASURY_CHECK_CLAIMS_PACKAGE"><data key="node_entity_id">DATA_TREASURY_CHECK_CLAIMS_PACKAGE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Treasury Check Claims Package</data><data key="node_acronym">Claims Package</data><data key="node_domain">Payments / Treasury / Nonreceipt</data><data key="node_description">Treasury-generated package for specified missing-check claims, containing claims documents and a check image and made available through TCIS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Mapped at the business-artifact level; Treasury repository implementation is not inferred.</data></node><node id="DATA_TREASURY_PROCESS_MSG"><data key="node_entity_id">DATA_TREASURY_PROCESS_MSG</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Treasury Process Message</data><data key="node_domain">External Exchange / Treasury / Payments</data><data key="node_description">Treasury reply indicating the action taken in response to SSA input; also called a disposition code.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says the message posts to PHUS for Title II and UPTQ for Title XVI.</data></node><node id="DATA_TRUMP_ACCOUNT_RESOURCE"><data key="node_entity_id">DATA_TRUMP_ACCOUNT_RESOURCE</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Trump Account SSI Resource</data><data key="node_acronym">TA</data><data key="node_domain">Title XVI / Resources / Financial Accounts</data><data key="node_description">Tax-advantaged child investment account whose SSI resource treatment changes between the growth period and post-growth period.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-07-09</data><data key="node_confidence">5</data><data key="node_notes">Modeled as an SSI resource type, not as an SSA-owned financial account or repository.</data></node><node id="DATA_UNASSIGNED_SSN"><data key="node_entity_id">DATA_UNASSIGNED_SSN</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Unassigned Social Security Numbers</data><data key="node_acronym">Unassigned SSNs</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Non-public SSA data asset described as a database list of Social Security numbers that have not been assigned.</data><data key="node_observed_status">current_federal_data_catalog</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-160. No relationship to Numident storage or SSNAP assignment logic is inferred from the catalog description alone.</data></node><node id="DATA_UNIQUE_ENTITY_IDENTIFIER"><data key="node_entity_id">DATA_UNIQUE_ENTITY_IDENTIFIER</data><data key="node_entity_type">identifier</data><data key="node_canonical_name">Unique Entity Identifier</data><data key="node_acronym">UEI</data><data key="node_domain">Acquisition / Payments / External Identity</data><data key="node_description">Federal entity identifier obtained through SAM.gov and accepted by SSA with representative travel reimbursement requests.</data><data key="node_observed_status">observed_current_ssa_guidance</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">External federal identifier; not an SSA person identifier and not evidence of a beneficiary identity record.</data></node><node id="DATA_UPLOAD_ROUTING_ZIP"><data key="node_entity_id">DATA_UPLOAD_ROUTING_ZIP</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Upload Documents Field-Office Routing ZIP Code</data><data key="node_acronym">Upload Routing ZIP</data><data key="node_domain">Address Provenance / Digital Intake</data><data key="node_description">Mailing-address ZIP code used by Upload Documents to route a customer submission to the jurisdictional field office.</data><data key="node_observed_status">observed_current_routing_attribute</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Normally sourced from Person Information. If no mailing address is on file in PI, the customer must enter a mailing-address ZIP for routing. Public policy does not state that the customer-entered ZIP updates PI/PERSON or another master record.</data></node><node id="DATA_USDC_INVENTORY_LOG"><data key="node_entity_id">DATA_USDC_INVENTORY_LOG</data><data key="node_entity_type">work_control_artifact</data><data key="node_canonical_name">U.S. Debit Card Inventory Log</data><data key="node_acronym">USDC Inventory Log</data><data key="node_domain">Payments / Field Office Controls</data><data key="node_description">Field-office inventory log used to track receipt and disbursement of U.S. Debit Cards, including last four card digits, issue date, office code, and required signatures.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says the log is stored with card inventory and the required template is available on the TPPS website. No centralized electronic repository is inferred.</data></node><node id="DATA_USPS_119TH_CONG_GEO"><data key="node_entity_id">DATA_USPS_119TH_CONG_GEO</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">USPS Geographic Data for 119th Congressional Districts</data><data key="node_domain">Geography / Published Statistics</data><data key="node_description">USPS geographic data as cited by SSA in 2025 congressional district statistical tables; authoritative source does not identify a particular USPS file or geographic crosswalk algorithm.</data><data key="node_observed_status">documented_2025_data_source</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Publication input only. Not evidence USPS assigns/updates current SSA person addresses.</data></node><node id="DATA_USPS_LOCATE_MAIL_ADDR"><data key="node_entity_id">DATA_USPS_LOCATE_MAIL_ADDR</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">USPS-Supplied Beneficiary Mailing Address</data><data key="node_acronym">USPS Locate Address</data><data key="node_domain">Title II / address provenance</data><data key="node_description">Current beneficiary mailing address obtained from USPS during whereabouts-unknown or undeliverable-mail development.</data><data key="node_observed_status">observed_current_policy_input</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Development input distinct from the separate NCOA mass-change process; no automatic write is inferred for this locate-letter workflow.</data></node><node id="DATA_USPS_NATIONAL_ZIP4"><data key="node_entity_id">DATA_USPS_NATIONAL_ZIP4</data><data key="node_entity_type">external_data_reference</data><data key="node_canonical_name">USPS National ZIP+4 File</data><data key="node_acronym">ZIP+4</data><data key="node_domain">Address / Geographic Reference</data><data key="node_description">National ZIP+4 reference file produced by the U.S. Postal Service and used by SSA statistical production to designate OASDI beneficiary state and county from 9-digit ZIP Codes.</data><data key="node_observed_status">observed_current_statistical_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Do not equate this external reference file with SSA ZIP Code Master File without evidence of physical identity or ingestion implementation.</data></node><node id="DATA_USPS_ZIP_TABLES"><data key="node_entity_id">DATA_USPS_ZIP_TABLES</data><data key="node_entity_type">reference_data_store</data><data key="node_canonical_name">SSA ZIP Tables for Front-End Address Editing</data><data key="node_acronym">ZIP Tables</data><data key="node_domain">Address Provenance / Reference Data</data><data key="node_description">Reference tables used for front-end ZIP Code validation and updated as part of USPS mass change-of-address processing.</data><data key="node_observed_status">documented_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">POMS establishes the tables and their use but does not identify physical platform, database technology, or current owner.</data></node><node id="DATA_US_MAILING_ABROAD_240_CODE"><data key="node_entity_id">DATA_US_MAILING_ABROAD_240_CODE</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">240 Listing Code for U.S. Mailing Address Abroad</data><data key="node_acronym">240 Listing Code</data><data key="node_domain">Title II / International / Address Provenance</data><data key="node_description">Listing code required for a beneficiary residing outside the United States while maintaining a U.S. mailing address, except APO/FPO addresses.</data><data key="node_observed_status">observed_current_policy_attribute</data><data key="node_observed_as_of">2024-02-07</data><data key="node_confidence">5</data><data key="node_notes">Public POMS identifies the control code but not its physical storage location.</data></node><node id="DATA_US_TOTALIZATION_ER"><data key="node_entity_id">DATA_US_TOTALIZATION_ER</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">U.S. Totalization Earnings Record</data><data key="node_domain">Title II / International / Earnings</data><data key="node_description">U.S. coverage/earnings record prepared for transmission to a foreign liaison agency in Totalization processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Generated from MCS in concurrent claims or requested through ICERS in foreign-benefits-only cases.</data></node><node id="DATA_VAMS_VAN"><data key="node_entity_id">DATA_VAMS_VAN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Verification Account Number</data><data key="node_acronym">VAN</data><data key="node_domain">External Data Exchange / Account Management</data><data key="node_description">Unique account identifier issued to verification and data-exchange accounts maintained in VAMS.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Account identifier, not a person identifier.</data></node><node id="DATA_VA_SSI_ADDRESS"><data key="node_entity_id">DATA_VA_SSI_ADDRESS</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">VA/SSI Interface Address Data</data><data key="node_acronym">VA SSI Address</data><data key="node_domain">Title XVI / External Exchange / Address Provenance</data><data key="node_description">Address attributes carried in the VA extract used by the SSI/VA interface, including foreign-address indicator, address type, address data, and ZIP code.</data><data key="node_observed_status">current_documented_interface_attribute</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Classified as external interface data. POMS does not establish automatic update of SSR, MSSICS, PI/PERSON, Numident, or MBR addresses.</data></node><node id="DATA_VENDOR_CAPABILITY_STATEMENT"><data key="node_entity_id">DATA_VENDOR_CAPABILITY_STATEMENT</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA Vendor Repository Capability Statement</data><data key="node_acronym">Vendor Capability Statement</data><data key="node_domain">procurement / market research</data><data key="node_description">Vendor-submitted capability statement and related email metadata/attachments placed into SSA Vendor Information Repository for market research.</data><data key="node_observed_status">observed_current_guidance</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current guidance says repository information remains approximately one year and then is deleted unless resubmitted.</data></node><node id="DATA_WAIVER_2PIN_CONTROL"><data key="node_entity_id">DATA_WAIVER_2PIN_CONTROL</data><data key="node_entity_type">logical_control</data><data key="node_canonical_name">Waiver Second-PIN Authorization Control</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Second credential/authorization recorded in DMS for Title II or direct SSR update for Title XVI; specific database field and authentication infrastructure undisclosed.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical policy authorization control; not a separate credential database.</data></node><node id="DATA_WFID"><data key="node_entity_id">DATA_WFID</data><data key="node_entity_type">data_identifier</data><data key="node_canonical_name">Wage File Identifier</data><data key="node_acronym">WFID</data><data key="node_domain">Earnings / Employer Reporting</data><data key="node_description">Identifier used by SSA to identify a submitted wage report in anomalous-wage investigations.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS states investigative notices identify suspect reports by WFID, EIN, and tax year.</data></node><node id="DATA_WOUNDED_WARRIOR_2016"><data key="node_entity_id">DATA_WOUNDED_WARRIOR_2016</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Wounded Warrior BORG Source Dataset</data><data key="node_acronym">Wounded Warrior</data><data key="node_domain">Person Data / Historical</data><data key="node_description">Wounded Warrior dataset identified as a source for the BORG Person subject area.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">The strategic plan does not describe the dataset schema or its physical system of origin.</data></node><node id="DATA_ZDPC"><data key="node_entity_id">DATA_ZDPC</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ZIP Delivery Point Code</data><data key="node_acronym">ZDPC</data><data key="node_domain">Title II / Title XVI / Address Metadata</data><data key="node_description">Three-position USPS-authorized delivery-point/bar-code element derived by SSA ZIP+4 processing and annotated to MBR and SSR during ZIP maintenance.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS states ZDPC comprises two digits derived from house/box number plus a control character; current runtime technology is not inferred from the age of the policy page.</data></node><node id="DB_ACT_TOR"><data key="node_entity_id">DB_ACT_TOR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Assignment and Correspondence Tracking System - Tactical / Operational Reporting</data><data key="node_acronym">ACT Tactical / Operational Reporting</data><data key="node_domain">Enterprise Workflow / Reporting</data><data key="node_description">Reporting data store for the Assignment and Correspondence Tracking System.</data><data key="node_observed_status">observed_current_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-213.</data></node><node id="DB_AC_WORKING_FILE"><data key="node_entity_id">DB_AC_WORKING_FILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Appeals Council Working File Records</data><data key="node_acronym">AC Working File</data><data key="node_domain">Appeals / Case Development</data><data key="node_description">Internal Appeals Council working file containing analyses, recommendations, request-for-review materials, actions, notices, decisions, transcripts when available, and related communications.</data><data key="node_observed_status">current_sorn_catalog_implementation_detail_from_2018</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN catalog still lists 60-0004; electronic implementation detail comes from 2018 notice.</data></node><node id="DB_ADMIN_PAYMENT_INFO"><data key="node_entity_id">DB_ADMIN_PAYMENT_INFO</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Administrative Payment Information</data><data key="node_domain">Finance / Administrative Payments</data><data key="node_description">Data store containing administrative payment status information.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-244; no application linkage inferred.</data></node><node id="DB_ADMIN_SANCTIONS"><data key="node_entity_id">DB_ADMIN_SANCTIONS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSA Administrative Sanctions Database</data><data key="node_domain">Program Integrity / Administrative Sanctions</data><data key="node_description">Privacy Act system of records for SSA administrative sanctions.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0280. Exact technical relationship to AS Tool/SPAS/client database remains unverified.</data></node><node id="DB_AERO_BYPASS"><data key="node_entity_id">DB_AERO_BYPASS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">AERO BYPASS File</data><data key="node_acronym">AERO BYPASS</data><data key="node_domain">Title II / Earnings Exceptions</data><data key="node_description">Exception/bypass file that generates alerts for manual review when AERO automation should not proceed because of unresolved earnings-record issues.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS revised 2025 explicitly identifies the AERO BYPASS file.</data></node><node id="DB_AFI_MI"><data key="node_entity_id">DB_AFI_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Access To Financial Institutions - Management Information</data><data key="node_acronym">AFI MI</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">Management-information asset covering requests/responses from financial institutions for Title XVI eligibility inquiries.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-07-23</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-3.</data></node><node id="DB_ALJ_WORKING_FILE"><data key="node_entity_id">DB_ALJ_WORKING_FILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Administrative Law Judge Working File Records</data><data key="node_acronym">ALJ Working File</data><data key="node_domain">Hearings / Case Development</data><data key="node_description">Internal hearing-level working file containing case actions, working notes, analyses, worksheets and copies of case-related materials.</data><data key="node_observed_status">current_sorn_catalog_implementation_detail_from_2018</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SORN catalog still lists 60-0005; electronic implementation detail comes from 2018 consolidated notice.</data></node><node id="DB_ALPHIDENT"><data key="node_entity_id">DB_ALPHIDENT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">ALPHIDENT File</data><data key="node_acronym">ALPHIDENT</data><data key="node_domain">Identity Verification / Reference Data</data><data key="node_description">SSA identity reference file used in the prisoner matching operation when inmate SSNs are missing or do not meet verification criteria.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Scope limited to the use documented in prisoner matching POMS.</data></node><node id="DB_APPOINTED_REP"><data key="node_entity_id">DB_APPOINTED_REP</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Appointed Representative Database</data><data key="node_domain">Representation / Data</data><data key="node_description">Database documented by SSA for information collected and maintained about appointed representatives, business entities, registration, appointments, and related activity.</data><data key="node_observed_status">documented_in_current_pia_catalog; implementation_detail_from_2010_pia</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">4</data><data key="node_notes">The detailed implementation description is from the 2010 PIA that remains linked in SSA’s current PIA catalog. Current physical relationship to RASR/AARPS is not published and is not inferred.</data></node><node id="DB_APPOINTED_REP_1099"><data key="node_entity_id">DB_APPOINTED_REP_1099</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Appointed Rep/Attorney Fee Form 1099</data><data key="node_domain">Representation / Fees / Tax Reporting</data><data key="node_description">Data store containing detailed Appointed Representative Suite information supporting appointments, Form 1099 issuance, and representative-claimant relationships.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-104. No physical relationship to RASR or AARPS is inferred.</data></node><node id="DB_APPOINTED_REP_MI_ODS"><data key="node_entity_id">DB_APPOINTED_REP_MI_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Appointed Representative Management Information - Operational Data Store</data><data key="node_domain">Representation / Management Information</data><data key="node_description">Operational data store containing information about appointed representatives used for reporting purposes.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-5. Catalog establishes existence and purpose but does not publish physical upstream/downstream interfaces.</data></node><node id="DB_APPT_SCHED_MI"><data key="node_entity_id">DB_APPT_SCHED_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Appointment Scheduling Management Information</data><data key="node_acronym">Appointment Scheduling MI</data><data key="node_domain">Customer Service / Appointments</data><data key="node_description">Management-information asset providing reports for appointment, leads, and 800 activity, with scheduling explicitly identified in the catalog record.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">Separate Data.gov identifier from Appointment System Management Information. The division of responsibilities between the two assets is not published.</data></node><node id="DB_APPT_SYSTEM_MI"><data key="node_entity_id">DB_APPT_SYSTEM_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Appointment System Management Information</data><data key="node_acronym">Appointment System MI</data><data key="node_domain">Customer Service / Appointments</data><data key="node_description">Management-information asset providing reports for appointment, leads, and 800-number activity.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">SSA Open Data proves the reporting asset exists; it does not publish its physical source-system topology.</data></node><node id="DB_APPT_VISITOR_CUSTOMER_RECORD"><data key="node_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Appointments, Visitor Information, and Customer Service Record System</data><data key="node_domain">Customer Service / Appointments / Identity</data><data key="node_description">Logical Privacy Act system-of-record boundary for visitor, appointment, interview, customer-service, notice, and High Risk alert records.</data><data key="node_observed_status">observed_current_modified_sorn</data><data key="node_observed_as_of">2025-08-20</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0350 says information also resides in additional locations in connection with cloud-based services and a backup location, but does not identify provider, platform, or database technology.</data></node><node id="DB_ARPS_MI"><data key="node_entity_id">DB_ARPS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Appeals Review Processing System Management Information</data><data key="node_acronym">ARPS MI</data><data key="node_domain">Appeals / Analytics</data><data key="node_description">Management-information reports and listings supporting Appeals Council, court and reprographics workload management.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">Architecture boundary is directly documented in the 2018 eDIB PIA; present implementation not independently established.</data></node><node id="DB_AUTHORIZED_REP"><data key="node_entity_id">DB_AUTHORIZED_REP</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Authorized Representative</data><data key="node_domain">Representation / Post-Entitlement</data><data key="node_description">Data asset containing appointed representative data collected after a post-entitlement action occurs.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-291. The catalog does not identify its source application.</data></node><node id="DB_BCAS_T16"><data key="node_entity_id">DB_BCAS_T16</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Benefit Certification And Accounting System - Title XVI</data><data key="node_acronym">BCAS T16</data><data key="node_domain">Title XVI / Accounting</data><data key="node_description">Stores information about certification of Title XVI payments.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DB_BFS_SAVINGS_SECURITY_REG"><data key="node_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">BFS Savings Security Registration File</data><data key="node_acronym">Savings Security Registration File</data><data key="node_domain">Title XVI / External Assets</data><data key="node_description">Bureau of the Fiscal Service registration file used in SSA savings-security matching for SSI recipients and deemors.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly names the BFS savings security registration file; physical database technology and transport are not public.</data></node><node id="DB_BI_REPOSITORY"><data key="node_entity_id">DB_BI_REPOSITORY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Business Intelligence Repository</data><data key="node_acronym">BI Repository</data><data key="node_domain">Enterprise Data / Business Intelligence</data><data key="node_description">Repository providing information on Business Intelligence projects in SSA's Office of Systems.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-226.</data></node><node id="DB_BLACK_LUNG_PAYMENT"><data key="node_entity_id">DB_BLACK_LUNG_PAYMENT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Black Lung Payment System</data><data key="node_domain">Black Lung / Payments</data><data key="node_description">Privacy Act system of records identified by SSA as the Black Lung Payment System.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0045; current catalog includes a November 25, 2025 amendment. Current runtime implementation is not inferred.</data></node><node id="DB_BL_BENEFIT_MASTER"><data key="node_entity_id">DB_BL_BENEFIT_MASTER</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Black Lung Benefit Master Record</data><data key="node_acronym">BL Benefit Master</data><data key="node_domain">Black Lung / Payments</data><data key="node_description">Beneficiary-oriented file historically documented as one of two files within BLPS.</data><data key="node_observed_status">historical_structure_current_exact_status_unconfirmed</data><data key="node_observed_as_of">1987-03-25</data><data key="node_confidence">3</data><data key="node_notes">Current SORN catalog maintains BLPS, but public evidence reviewed does not reconfirm that this internal file decomposition is unchanged.</data></node><node id="DB_BL_PAYMENT_MASTER"><data key="node_entity_id">DB_BL_PAYMENT_MASTER</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Black Lung Payment Master Record</data><data key="node_acronym">BL Payment Master</data><data key="node_domain">Black Lung / Payments</data><data key="node_description">Payment-oriented file historically documented as one of two files within BLPS.</data><data key="node_observed_status">historical_structure_current_exact_status_unconfirmed</data><data key="node_observed_as_of">1987-03-25</data><data key="node_confidence">3</data><data key="node_notes">Current SORN catalog maintains BLPS, but public evidence reviewed does not reconfirm that this internal file decomposition is unchanged.</data></node><node id="DB_BORG_CED"><data key="node_entity_id">DB_BORG_CED</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">BORG Consolidated Enterprise Database</data><data key="node_acronym">BORG / CED</data><data key="node_domain">Enterprise Person Data / Modernization</data><data key="node_description">Historical consolidated relational database designed around person rather than program silos. Phase 1 modeled a Person subject area; Phase 2 modeled Earnings.</data><data key="node_observed_status">historical_development_environment_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">SSA documented the database as implemented in a development environment with ETL rules running. Public evidence does not establish whether BORG was later renamed, replaced, or became the current Person data store.</data></node><node id="DB_CAL_QDD_DM"><data key="node_entity_id">DB_CAL_QDD_DM</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Compassionate Allowance / Quick Disability Determination Datamart</data><data key="node_acronym">CAL/QDD Datamart</data><data key="node_domain">Disability / Analytics</data><data key="node_description">Datamart supporting management evaluation of CAL/QDD effectiveness, predictive-model accuracy and performance goals.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">Do not infer current hosting or continued standalone implementation.</data></node><node id="DB_CCS_PLANNED"><data key="node_entity_id">DB_CCS_PLANNED</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Consolidated Claims System Planned Database</data><data key="node_acronym">CCS database</data><data key="node_domain">Benefits / Claims Modernization</data><data key="node_description">Database SSA planned to establish for the Consolidated Claims System to support future data needs and consolidated-customer scenarios.</data><data key="node_observed_status">historical_planned</data><data key="node_observed_as_of">2019</data><data key="node_confidence">4</data><data key="node_notes">Budget evidence establishes a planned database but does not establish implementation, physical database technology, hosting, or later equivalence to CCE data stores.</data></node><node id="DB_CET_RECORD_SYSTEM"><data key="node_entity_id">DB_CET_RECORD_SYSTEM</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Customer Engagement Tools Record System</data><data key="node_acronym">CET Record System</data><data key="node_domain">Customer Service / Digital Engagement</data><data key="node_description">SSA Privacy Act system of records 60-0383 for Customer Engagement Tools records.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">A 2017 SSA PIA described Dynamic Help, Click to Callback, Message Center, and Click to Chat under Customer Engagement Tools. Those component names are historical context only; Run 39 does not assert they are all current.</data></node><node id="DB_CIRP_MI"><data key="node_entity_id">DB_CIRP_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Comprehensive Integrity Review Process - Management Information</data><data key="node_acronym">CIRP MI</data><data key="node_domain">Program Integrity</data><data key="node_description">Management-information asset for the Comprehensive Integrity Review Process.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-07-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled separately from the CIRP application.</data></node><node id="DB_CLAIMS_FOLDERS_SYSTEM"><data key="node_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Claims Folders System</data><data key="node_domain">Claims / Case Records</data><data key="node_description">Privacy Act system of records 60-0089 containing SSA claims-folder records.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Added as the exact SORN-named logical system of records. Existing Atlas Claims Folder Data remains a broader data-domain object. Physical storage and application boundaries are not inferred from the SORN title.</data></node><node id="DB_CLIENT_SANCTIONS_CONTEXT"><data key="node_entity_id">DB_CLIENT_SANCTIONS_CONTEXT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Client Database (Administrative Sanctions Context)</data><data key="node_acronym">Client Database</data><data key="node_domain">Program Integrity / Administrative Sanctions</data><data key="node_description">Database referred to generically by POMS as the client database accessed through Shared Process Menu for SPAS entries.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Exact identity relative to the Atlas Integrated Client Database entity or SORN 60-0280 is not established by the reviewed source.</data></node><node id="DB_CONTROL_TRACK_WS"><data key="node_entity_id">DB_CONTROL_TRACK_WS</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Control And Tracking Web Service</data><data key="node_acronym">Control And Tracking Web Service</data><data key="node_domain">Enterprise Integration / eServices</data><data key="node_description">Non-public SSA data asset that stores submission control numbers and status inserts used to support eServices Control And Tracking.</data><data key="node_observed_status">observed_current_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-173. Despite the title, the catalog description characterizes it as a store.</data></node><node id="DB_CPMS_MI"><data key="node_entity_id">DB_CPMS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Case Processing Management System Management Information</data><data key="node_acronym">CPMS MI</data><data key="node_domain">Hearings &amp; Appeals / Analytics</data><data key="node_description">Management-information reports and listings supporting hearing-office, regional and national workload management.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">Architecture boundary is directly documented in the 2018 eDIB PIA; present implementation not independently established.</data></node><node id="DB_CSR_ODS"><data key="node_entity_id">DB_CSR_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Customer Service Record Operational Data Store</data><data key="node_acronym">CSR ODS</data><data key="node_domain">Customer Service / Enterprise Data</data><data key="node_description">Operational data store/process used to store field-office visitor counts underlying SSA field-office visitor reporting.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Open Data states SSA has used CSR ODS since October 2008; current implementation details are not public.</data></node><node id="DB_CWOSS_MI"><data key="node_entity_id">DB_CWOSS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Comprehensive Work Opportunities Support System Management Information</data><data key="node_acronym">CWOSS MI</data><data key="node_domain">Ticket to Work / Work Incentives</data><data key="node_description">Management-information asset for CWOSS workload case-management, contract, and payment information supporting Ticket to Work.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">The exact physical boundary between CWOSS and its MI asset is not published.</data></node><node id="DB_DCF"><data key="node_entity_id">DB_DCF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disability Control File</data><data key="node_acronym">DCF</data><data key="node_domain">Post-entitlement Disability</data><data key="node_description">Master repository within the IDMS/DCFS environment containing disability adjudication history and post-entitlement control data, including Title II earnings-verification, work-CDR, Ticket to Work, and related disability-program information.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">2017 IDMS PIA calls DCF the IDMS master file/master repository and states it reads and updates according to MEF, SSR, and MBR; those relationships are time-scoped and do not imply a current transport mechanism.</data></node><node id="DB_DCPS_CORRESP"><data key="node_entity_id">DB_DCPS_CORRESP</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disability Case Processing System Correspondence</data><data key="node_domain">Disability / Correspondence</data><data key="node_description">Non-public asset supporting DCPS correspondence and notices.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-255; keywords include COTS and Thunderhead.</data></node><node id="DB_DCPS_MI"><data key="node_entity_id">DB_DCPS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">DCPS Management Information</data><data key="node_domain">Disability / Analytics</data><data key="node_description">Management-information asset supporting reporting on DCPS disability-claims processing.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Data.gov catalog result.</data></node><node id="DB_DDS_CE_PROVIDER_FILE"><data key="node_entity_id">DB_DDS_CE_PROVIDER_FILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">DDS Consultative Examination Provider File</data><data key="node_acronym">CE Provider File</data><data key="node_domain">Disability / Consultative Examinations</data><data key="node_description">Privacy Act system of records 60-0046 for individuals who perform DDS consultative examinations, including identity, address, credentials, photo ID images, quality/oversight, fees, exclusion information and investigations.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 SORN locates records at State DDS offices, potentially at SSA NCC, and in additional cloud-based service/backup locations. Runtime database, cloud provider and synchronization architecture are not public.</data></node><node id="DB_DIGITAL_IDENTITY_FILE"><data key="node_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Digital Identity File Record System</data><data key="node_acronym">Digital Identity File</data><data key="node_domain">Identity / Digital Authentication</data><data key="node_description">Current Privacy Act electronic record system supporting SSA digital identity processes and auditing, including identity proofing, credential issuance/revocation, authentication, federation, access controls, preference management, and credential management.</data><data key="node_observed_status">observed_current_sorn</data><data key="node_observed_as_of">2025-08-20</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0373. This is an identity/authentication record system, not evidence of a universal enterprise Person master. Its older title included Central Repository of Electronic Authentication Data Master File.</data></node><node id="DB_DIODS"><data key="node_entity_id">DB_DIODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disability Operational Data Store</data><data key="node_acronym">DIODS</data><data key="node_domain">Disability / Analytics</data><data key="node_description">Disability Operational Data Store built from row-level disability case data and used as SSA's definitive data store for disability claims for state-agency workload-management purposes; it supports stored time-period summaries and public workload reporting.</data><data key="node_observed_status">observed_current_definitive_workload_store</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA disability-data documentation states DIODS is built on row-level individual disability cases, stores time-period summaries, and is the definitive SSA data store for state-agency disability workload management. Retroactive row-level corrections do not recalculate already stored summaries; later overlapping summaries can incorporate corrected data.</data></node><node id="DB_DISABILITY_DATABASE_SYSTEM"><data key="node_entity_id">DB_DISABILITY_DATABASE_SYSTEM</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disability Database System</data><data key="node_acronym">DDS Database System</data><data key="node_domain">Disability / Analytics</data><data key="node_description">eDIB subsystem described as extracting disability-claim and continuing-disability-review data for disability operations.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">2018 architecture evidence only; current status unresolved.</data></node><node id="DB_DIS_PRED_MODEL_MI"><data key="node_entity_id">DB_DIS_PRED_MODEL_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disability Predictive Model Project Management Information</data><data key="node_acronym">Disability Predictive Model MI</data><data key="node_domain">Disability / Predictive Analytics</data><data key="node_description">Management-information asset collecting disability evaluation information to support special disability claims processing.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">No mapping to a specific QDD, CAL, or CDR model is inferred without additional evidence.</data></node><node id="DB_DMS_MI"><data key="node_entity_id">DB_DMS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Debt Management Management Information</data><data key="node_acronym">Debt Management MI</data><data key="node_domain">Debt &amp; Overpayments / Analytics</data><data key="node_description">Management-information store for the debt-management process.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">Logical association with DMS is captured with a confidence caveat; the source does not publish physical feed topology.</data></node><node id="DB_DQR_MI"><data key="node_entity_id">DB_DQR_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Disability Quality Review - Management Information</data><data key="node_acronym">DQR MI</data><data key="node_domain">Disability / Quality Review / Management Information</data><data key="node_description">Data store containing information about the review process associated with disability cases.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-19. No direct feed to QRCPS, DICARS, or another quality application is asserted without source evidence.</data></node><node id="DB_DTA_PIN_FILE"><data key="node_entity_id">DB_DTA_PIN_FILE</data><data key="node_entity_type">access_control_store</data><data key="node_canonical_name">Direct Terminal Access PIN File</data><data key="node_acronym">PIN File</data><data key="node_domain">External Exchanges / Identity &amp; Access</data><data key="node_description">Access-control and transaction-attribution store associated with personal identification numbers assigned to approved external-agency users of Direct Terminal Access.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says employee PII is attached to the assigned PIN to capture all transactions performed under that PIN and that the PIN File complies with the Privacy Act. Physical database technology is not disclosed.</data></node><node id="DB_EAP"><data key="node_entity_id">DB_EAP</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Emergency Advance Payment Database</data><data key="node_acronym">EAP database</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Database checked during MSSICS Emergency Advance Payment processing to prevent duplicate EAP issuance.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Named generically as 'EAP data base' in current POMS; underlying platform/database technology is not stated.</data></node><node id="DB_EARNINGS_DW"><data key="node_entity_id">DB_EARNINGS_DW</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Earnings Data Warehouse</data><data key="node_domain">Earnings / Analytics</data><data key="node_description">Data warehouse for management information of the Annual Wage Reporting system.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-198. Data.gov catalog record was refreshed September 29, 2026.</data></node><node id="DB_ECAT_MI"><data key="node_entity_id">DB_ECAT_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Claims Analysis Tool Management Information</data><data key="node_acronym">eCAT MI</data><data key="node_domain">Disability / Analytics</data><data key="node_description">Management-information charts/reports used to monitor eCAT usage and progress.</data><data key="node_observed_status">documented_in_current_pia_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">2018 eDIB PIA architecture; current MI implementation not separately corroborated.</data></node><node id="DB_ECO_DATA"><data key="node_entity_id">DB_ECO_DATA</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">External Collection Operation Data File</data><data key="node_acronym">ECO Data File</data><data key="node_domain">Debt &amp; External Collections</data><data key="node_description">Data store containing data needed to maintain delinquent SSA debts.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-181; keyworded ECO/external collection operation.</data></node><node id="DB_EDIB_CLAIM_FILE"><data key="node_entity_id">DB_EDIB_CLAIM_FILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Disability Claim File</data><data key="node_acronym">eDIB Claim File</data><data key="node_domain">Disability / Electronic Case Records</data><data key="node_description">Privacy Act system of records 60-0320 for electronic disability claim records under Titles II and XVI, including claim/evidence, post-adjudicative actions, electronic messaging selections, and medical-provider metadata.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Exact SORN-named logical system of records. Current 2026 SORN says electronic records are maintained at the NCC and may also be located in additional cloud-based service locations plus backup; it does not establish one-to-one physical equivalence with CEF or the separately named eDIB Cloud platform.</data></node><node id="DB_EDIS_MI"><data key="node_entity_id">DB_EDIS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Disability Management Information</data><data key="node_acronym">Electronic Disability MI</data><data key="node_domain">Disability / Analytics</data><data key="node_description">Management-information asset for disability cases.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">The title suggests association with Electronic Disability, but the public record does not publish a physical feed or component boundary.</data></node><node id="DB_EDPNA_FEE_1099"><data key="node_entity_id">DB_EDPNA_FEE_1099</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Attorney and Eligible Direct Pay Non-Attorney 1099 File</data><data key="node_acronym">Attorney/EDPNA 1099 File</data><data key="node_domain">Representative Services / Finance</data><data key="node_description">File established to support information-return reporting for direct representative fee payments, including representative and affiliated business-entity tax information.</data><data key="node_observed_status">listed_in_current_pia_catalog_and_current_function</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Current public guidance confirms the reporting function; the public record does not establish whether the 2006 physical implementation remains unchanged.</data></node><node id="DB_EIF"><data key="node_entity_id">DB_EIF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Employer Identification File</data><data key="node_acronym">EIF</data><data key="node_domain">Earnings / Employer</data><data key="node_description">File containing employer EIN information provided by IRS.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-182. OPM exchange metadata calls the matched asset Employer Information File (EIF); treated as likely nomenclature alignment but not silently renamed.</data></node><node id="DB_EMAC2"><data key="node_entity_id">DB_EMAC2</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Management of Assignments and Correspondence (EMAC 2)</data><data key="node_acronym">EMAC 2</data><data key="node_domain">Enterprise Workflow / Correspondence</data><data key="node_description">Non-public production data store for control and tracking of high-priority correspondence received in the Office of Public Inquiries.</data><data key="node_observed_status">observed_current_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-569. Its exact physical relationship to APP_EMAC and DB_OPI_CORRESP_CONTROL is unresolved.</data></node><node id="DB_EMODS"><data key="node_entity_id">DB_EMODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Earnings Modernization - Operational Data Store</data><data key="node_acronym">EM ODS</data><data key="node_domain">Earnings / Analytics</data><data key="node_description">Operational data store housing Annual Wage Reporting management information and Social Security Statement statistics.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-26.</data></node><node id="DB_EMPLOYERS_SUBMITTERS"><data key="node_entity_id">DB_EMPLOYERS_SUBMITTERS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Employers and Submitters</data><data key="node_domain">Earnings / Employer</data><data key="node_description">Database supporting processing of wage files for Annual Wage Reporting.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DB_EMPLOYER_CTRL"><data key="node_entity_id">DB_EMPLOYER_CTRL</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Employer Control Data Base</data><data key="node_domain">Earnings / Employer</data><data key="node_description">OCRO-maintained employer annual-wage-report filing/status reference data.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current 2025 instructions continue to use related ERQY data.</data></node><node id="DB_EMPLOYER_SHARED"><data key="node_entity_id">DB_EMPLOYER_SHARED</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Employer Database</data><data key="node_domain">Earnings / Employer</data><data key="node_description">Employer and related tables shared between eWork and SSI Monthly Wage Verification.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DB_ENUM_WAREHOUSE"><data key="node_entity_id">DB_ENUM_WAREHOUSE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Enumeration Warehouse</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Database storing workload-control information for employees managing enumeration workloads.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-07-23</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-199.</data></node><node id="DB_ERE_EXPERT_ADMIN"><data key="node_entity_id">DB_ERE_EXPERT_ADMIN</data><data key="node_entity_type">internal_data_store</data><data key="node_canonical_name">ERE for Experts Admin Table</data><data key="node_acronym">Admin Table</data><data key="node_domain">Hearings / Identity / Authorization</data><data key="node_description">Restricted SSA table identified on the current ERE for Experts page as the location housing expert SSNs used for authentication and authorization.</data><data key="node_observed_status">documented_on_current_page_backend_lineage_uncertain</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">SSA does not identify database technology, platform, retention, or whether the table was re-platformed after CPMS retirement.</data></node><node id="DB_ERE_MI"><data key="node_entity_id">DB_ERE_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Records Express Management Information</data><data key="node_acronym">ERE MI</data><data key="node_domain">Disability Evidence / Analytics</data><data key="node_description">Management-information subsystem associated with Electronic Records Express.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">2018 architecture evidence only.</data></node><node id="DB_ERE_MI_USAGE"><data key="node_entity_id">DB_ERE_MI_USAGE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Records Express Management Information Usage Reporting</data><data key="node_domain">Disability / Evidence Analytics</data><data key="node_description">Management-information store for evidence collected electronically through ERE and prepared for transition to eDIB.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-734.</data></node><node id="DB_ERE_MI_VOLUME"><data key="node_entity_id">DB_ERE_MI_VOLUME</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Records Express Management Information Volume Reporting</data><data key="node_domain">Disability / Evidence Analytics</data><data key="node_description">Management-information store reporting numbers of electronic records processed through the ERE website and each Front End Capture System (FECS).</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-34.</data></node><node id="DB_ERE_OUTBOUND"><data key="node_entity_id">DB_ERE_OUTBOUND</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Medical Evidence-Outbound Requests</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Non-public ERE-related data asset for evidence collected electronically and prepared for transmission to eDIB.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-08</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-211.</data></node><node id="DB_ERHF"><data key="node_entity_id">DB_ERHF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Employer Report History File</data><data key="node_acronym">ERHF</data><data key="node_domain">Earnings / Employer</data><data key="node_description">Database of report-level wage data stored by EIN and tax year supporting employer-side AWR.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-126.</data></node><node id="DB_ERPA_MI"><data key="node_entity_id">DB_ERPA_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Representative Payee Accounting Management Information</data><data key="node_domain">Representative Payee / Analytics</data><data key="node_description">Management-information data for the Representative Payee Accounting process.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Data.gov catalog entry.</data></node><node id="DB_ERPS_MI"><data key="node_entity_id">DB_ERPS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Representative Payee System Management Information</data><data key="node_domain">Representative Payee / Analytics</data><data key="node_description">Database containing report-formatting information and representative-payee-related counts for business-intelligence reporting.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Data.gov catalog entry.</data></node><node id="DB_ESERVICES_MI_STAGE"><data key="node_entity_id">DB_ESERVICES_MI_STAGE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Services MI</data><data key="node_acronym">Electronic Services MI</data><data key="node_domain">Digital Service / Analytics</data><data key="node_description">Staging instance containing information about Client-to-Government electronic-service transactions.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-08</data><data key="node_confidence">5</data><data key="node_notes">Modeled separately from the Electronic Services Operational Data Store because the source explicitly calls this a staging instance; no stage-to-ODS feed is inferred.</data></node><node id="DB_ESERVICE_ODS"><data key="node_entity_id">DB_ESERVICE_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Services Operational Data Store</data><data key="node_acronym">Electronic Services ODS</data><data key="node_domain">Enterprise Data / Digital Services Analytics</data><data key="node_description">Management-information data store used for reporting on electronic-service usage.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-27.</data></node><node id="DB_ESF"><data key="node_entity_id">DB_ESF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Earnings Suspense File</data><data key="node_acronym">ESF</data><data key="node_domain">Earnings</data><data key="node_description">Electronic database containing earnings that cannot post to an individual MEF record because identifying information does not match SSA records.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS continues to state unmatched W-2 wage reports are placed in the Earnings Suspense File instead of being credited to the worker earnings record.</data></node><node id="DB_EWORK_GLOBAL_TABLES"><data key="node_entity_id">DB_EWORK_GLOBAL_TABLES</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Electronic Work Reporting Global Tables</data><data key="node_acronym">EWR Global Tables</data><data key="node_domain">Work Reporting / Reference Data</data><data key="node_description">Global reference values supporting the Electronic Work Reporting process.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-08</data><data key="node_confidence">5</data><data key="node_notes">No direct linkage to eWork, Electronic Wage Reporting, or the planned Work CDR Product is inferred from the title alone.</data></node><node id="DB_FINANCE_IVR"><data key="node_entity_id">DB_FINANCE_IVR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Finance Interactive Voice Response System</data><data key="node_domain">Finance / Vendor Payments</data><data key="node_description">Database supporting phone access to vendor invoice and payment-status reports through an interactive voice response capability.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-194. Catalog describes the database function but not a separate IVR platform topology.</data></node><node id="DB_FODS"><data key="node_entity_id">DB_FODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Fugitive Felon Fraud Operational Data Store</data><data key="node_acronym">FODS</data><data key="node_domain">Program Integrity / Fugitive Felon</data><data key="node_description">Operational data store containing information received from law enforcement agencies about fugitive felons.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-28. Public evidence does not establish physical relationships to FUGFEL, FRATS, FFSCF, or FFAP.</data></node><node id="DB_FOIA_PRIVACY_REQUEST_APPEAL"><data key="node_entity_id">DB_FOIA_PRIVACY_REQUEST_APPEAL</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Freedom of Information Act and Privacy Act Record Request and Appeal System</data><data key="node_domain">Privacy / FOIA Records</data><data key="node_description">SSA Privacy Act system of records 60-0340 for FOIA and Privacy Act record requests and appeals.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SORN catalog validates the record system and November 18, 2025 publication. No backend relationship to the public electronic record-access webforms is inferred.</data></node><node id="DB_FO_MANUAL_OTP_CONTROL"><data key="node_entity_id">DB_FO_MANUAL_OTP_CONTROL</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Field Office Manual OTP Control File</data><data key="node_acronym">FO manual OTP control file</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Field-office control file used to determine whether a Manual One-Time Payment was issued when the payment is not yet reflected on the SSR.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS establishes operational use but does not disclose storage technology, schema, or physical location.</data></node><node id="DB_GARNISHMENT"><data key="node_entity_id">DB_GARNISHMENT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Garnishment DB2 Database</data><data key="node_domain">Title II / Garnishment</data><data key="node_description">DB2 data store used by the automated Garnishment Notice System together with Master Beneficiary Record data.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">The source identifies DB2 technology but does not expose physical schema or hosting.</data></node><node id="DB_GIR"><data key="node_entity_id">DB_GIR</data><data key="node_entity_type">repository</data><data key="node_canonical_name">General Information Retrieval</data><data key="node_acronym">GIR</data><data key="node_domain">records and evidence</data><data key="node_description">Repository housing historical and new IRS Forms 4029 and 4361 received from IRS.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS RM 04906.001.</data></node><node id="DB_HACPS_DATA"><data key="node_entity_id">DB_HACPS_DATA</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Hearing and Appeals Case Processing System Data Store</data><data key="node_acronym">HACPS Data</data><data key="node_domain">Hearings &amp; Appeals</data><data key="node_description">Non-public data store inventoried by SSA as containing all hearings and appeals information.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-86. Logical app/store separation is useful for the Atlas; physical database topology is not published.</data></node><node id="DB_HAVV_ODS"><data key="node_entity_id">DB_HAVV_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Help America Vote Verification Operational Data Store</data><data key="node_acronym">HAVV ODS</data><data key="node_domain">External Data Exchange</data><data key="node_description">Management-information database recording HAVV voter-identification transactions.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-30.</data></node><node id="DB_HA_CASE_CONTROL_RECORDS"><data key="node_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Hearings and Appeals Case Control Records</data><data key="node_acronym">H&amp;A Case Control Records</data><data key="node_domain">Hearings / Appeals / Work Control</data><data key="node_description">Logical system-of-record boundary defined by SORN 60-0009 for hearing and Appeals Council case-control information from hearing request through final Appeals Council disposition.</data><data key="node_observed_status">observed_current_modified_sorn</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SORN scope is authoritative; exact one-to-one physical equivalence with HACPS, OAOCPS, ARPS, or another application is not established. Run 84: field-level categories of record from current SORN 60-0009 are now modeled separately; physical mapping to specific appeals applications remains unresolved.</data></node><node id="DB_HA_MI_ODS"><data key="node_entity_id">DB_HA_MI_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Hearings and Appeals Management Information - Operational Data Store</data><data key="node_acronym">HA MI ODS</data><data key="node_domain">Hearings &amp; Appeals / Analytics</data><data key="node_description">Operational data store used to manage and report on hearings and appeals level cases.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-29; metadata keywords include CPMS.</data></node><node id="DB_HIT_MI"><data key="node_entity_id">DB_HIT_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Health Information Technology Management Information</data><data key="node_acronym">HIT MI</data><data key="node_domain">Disability Evidence / Analytics</data><data key="node_description">Management-information subsystem associated with health-information-technology evidence exchange.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">2018 architecture evidence only.</data></node><node id="DB_HR_ODS"><data key="node_entity_id">DB_HR_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Human Resources Operational Data Store</data><data key="node_acronym">HR ODS</data><data key="node_domain">Enterprise Data / Human Resources</data><data key="node_description">Operational data store containing SSA employee information.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-07-28</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-31.</data></node><node id="DB_HR_ODS_CORE"><data key="node_entity_id">DB_HR_ODS_CORE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Human Resources Operational Data Store Core Services</data><data key="node_acronym">HR ODS Core Services</data><data key="node_domain">Enterprise Data / Human Resources</data><data key="node_description">Current SSA enterprise data asset containing a very small subset of Human Resources Operational Data Store data and supporting the SSA Employee and Office Data Retrieval Core Services function.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-469. The public inventory does not describe replication, refresh cadence, database technology, or physical hosting.</data></node><node id="DB_IDMS"><data key="node_entity_id">DB_IDMS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Identity Management System</data><data key="node_acronym">IDMS</data><data key="node_domain">Enterprise Identity / Workforce Access</data><data key="node_description">SSA Privacy Act system of records 60-0361, Identity Management System, covering identity-management records.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SORN catalog validates the record system. Historical PIA material associates IDMS with PIV identity management, but Run 39 does not infer a current implementation from historical architecture.</data></node><node id="DB_INTERNET_REPORT"><data key="node_entity_id">DB_INTERNET_REPORT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Internet Report Database</data><data key="node_acronym">IDR Database</data><data key="node_domain">Disability / Internet Intake</data><data key="node_description">Database holding Internet Disability Report partials and submitted report data, including inactive/archive states before purge.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS describes storage, archive, retrieval and purge behavior but does not expose platform technology.</data></node><node id="DB_IRES_MI"><data key="node_entity_id">DB_IRES_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Integrated Registration Service (IRES) Management Information</data><data key="node_acronym">IRES MI</data><data key="node_domain">Identity / Internet Registration</data><data key="node_description">Management-information database supporting registration of organizations to SSA internet applications.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">The public source proves the MI database and business purpose but does not expose the underlying IRES application topology.</data></node><node id="DB_IRS_IMF"><data key="node_entity_id">DB_IRS_IMF</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">IRS Individual Master File</data><data key="node_acronym">IMF</data><data key="node_domain">External Data / Taxpayer Address</data><data key="node_description">IRS taxpayer master file used by SSA to obtain mailing addresses for automatic Social Security Statements. Current SSA policy describes it as addressable by SSN and containing taxpayer-provided mailing addresses generally refreshed through tax filing.</data><data key="node_observed_status">observed_current_external_source</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">IRS internal schema, hosting, replication, and SSA transport are not inferred.</data></node><node id="DB_IRS_IRMF"><data key="node_entity_id">DB_IRS_IRMF</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">IRS Information Return Master File</data><data key="node_acronym">IRMF</data><data key="node_domain">External Data / Tax Information</data><data key="node_description">IRS Information Return Master File identified in current SSA/IRS CMA 1016 as the IRS source matched against SSA Title XVI finder data to return unearned-income information, including payee and payer address fields.</data><data key="node_observed_status">observed_current_external_source</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current signed CMA 1016 is effective January 1, 2026 through July 1, 2027 and explicitly names IRMF [Treasury/IRS 22.061]. IRS internal schema, hosting, and SSA transport beyond the agreement are not inferred.</data></node><node id="DB_IRS_NAP_DM1"><data key="node_entity_id">DB_IRS_NAP_DM1</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">IRS National Account Profile DM1 File</data><data key="node_acronym">NAP-DM1</data><data key="node_domain">External Data / IRS / Identity Validation</data><data key="node_description">IRS National Account Profile DM1 file used to validate SSNs and name controls received from SSA before DIFSLA matching against the Information Return Master File.</data><data key="node_observed_status">observed_current_cma_source</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current CMA 1016 explicitly establishes pre-match validation against NAP-DM1. IRS physical database technology is not inferred.</data></node><node id="DB_ISSNRC_ACTIVITY_DW"><data key="node_entity_id">DB_ISSNRC_ACTIVITY_DW</data><data key="node_entity_type">data_warehouse</data><data key="node_canonical_name">Unnamed iSSNRC Activity Data Warehouse</data><data key="node_acronym">iSSNRC Activity DW</data><data key="node_domain">Enumeration; Management Information</data><data key="node_description">A data warehouse explicitly documented by SSA Open Data as storing captured online replacement-card transactions used for usage reporting; public documentation does not name the warehouse.</data><data key="node_observed_status">explicitly_documented_unnamed_store_identity_unresolved</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">Do not equate with SUMS/Electronic Services DW query instances or another warehouse without additional evidence.</data></node><node id="DB_LEGACY_T16_IC_ODS"><data key="node_entity_id">DB_LEGACY_T16_IC_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Legacy Title XVI Initial Claims Operational Data Store</data><data key="node_acronym">Legacy T16 IC ODS</data><data key="node_domain">Title XVI / Initial Claims</data><data key="node_description">Legacy management-information store for Title XVI initial claims.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Inventory still lists the asset but labels it legacy; do not infer that it remains the authoritative current initial-claims store.</data></node><node id="DB_LOCAL_MI_ODS"><data key="node_entity_id">DB_LOCAL_MI_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Local Management Information - Operational Data Store</data><data key="node_acronym">Local MI ODS</data><data key="node_domain">Digital Services / Management Information</data><data key="node_description">Operational data store providing local management information for the Electronic Services application/domain.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-8. Physical feed from Electronic Services staging or ODS is not published.</data></node><node id="DB_LONG_TERM_SSN_FRAUD"><data key="node_entity_id">DB_LONG_TERM_SSN_FRAUD</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Long Term SSN Fraud</data><data key="node_domain">Identity / Program Integrity</data><data key="node_description">Non-public management-information asset supporting ad hoc query and reporting on prevention of SSN cards issued to non-existent children.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-07-28</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-61.</data></node><node id="DB_MADCAP_NOTICES"><data key="node_entity_id">DB_MADCAP_NOTICES</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">MADCAP Notices</data><data key="node_acronym">MADCAP Notices</data><data key="node_domain">Title II / Notices</data><data key="node_description">Data asset supporting notices produced by the Manual Adjustment, Credit, and Award Process (MADCAP) notice system.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-137.</data></node><node id="DB_MAPS"><data key="node_entity_id">DB_MAPS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Medicare Application Processing System Database</data><data key="node_acronym">MAPS database</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS data store explicitly referenced in SSA policy as being updated with agency pension data and supporting Extra Help verification screens.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Physical database technology, schema, hosting, and retention are not publicly established.</data></node><node id="DB_MASTER_REP_PAYEE_FILE"><data key="node_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Master Representative Payee File</data><data key="node_acronym">MRPF</data><data key="node_domain">Representative Payee / Person-Relationship / Address</data><data key="node_description">Core representative-payee record store containing information about representative payees, payee applicants, and beneficiaries or recipients in representative payment.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS expressly states the Master Representative Payee File is part of eRPS. SORN 60-0222 governs the record system. Do not equate this record store with all eRPS management-information stores.</data></node><node id="DB_MCS_PENDING"><data key="node_entity_id">DB_MCS_PENDING</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">MCS Pending File</data><data key="node_acronym">MCS Pending File</data><data key="node_domain">Title II / Claims</data><data key="node_description">Legacy pending-file data store associated with the Modernized Claims System and explicitly identified in SSA post-entitlement modernization planning.</data><data key="node_observed_status">historical_legacy_reference</data><data key="node_observed_as_of">2019</data><data key="node_confidence">5</data><data key="node_notes">FY2020 budget says the file depended on a costly Integrated Database Management System database structure. Current status and physical implementation are not established.</data></node><node id="DB_MDB"><data key="node_entity_id">DB_MDB</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Medicare Database File</data><data key="node_acronym">MDB</data><data key="node_domain">Medicare / Eligibility</data><data key="node_description">SSA Medicare database used to verify Extra Help eligibility and support Medicare outreach/matching.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-05-11</data><data key="node_confidence">5</data><data key="node_notes">Active CMA 1008 identifies SSA SORN 60-0321 and approximately 110 million comparison records.</data></node><node id="DB_MEDICARE_MI"><data key="node_entity_id">DB_MEDICARE_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Medicare Management Information</data><data key="node_acronym">Medicare MI</data><data key="node_domain">Medicare / Analytics</data><data key="node_description">Management-information store for Medicare Part C and Part D premium data, Part D prescription-drug-subsidy processing, and workload management.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">The public catalog does not establish a direct MAPS interface; that relationship is intentionally not inferred.</data></node><node id="DB_MEDICARE_ODS"><data key="node_entity_id">DB_MEDICARE_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Medicare Operational Data Store</data><data key="node_acronym">Medicare ODS</data><data key="node_domain">Medicare / Analytics</data><data key="node_description">Operational data store providing current SUMS Medicare workload data used to update the SUMS Counts Data Warehouse.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data proves this reporting relationship but does not establish a direct MAPS or i1020 physical interface.</data></node><node id="DB_MEDICARE_PARTB_BUYIN"><data key="node_entity_id">DB_MEDICARE_PARTB_BUYIN</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Medicare Part B Buy-In Information System</data><data key="node_domain">Medicare / State Coordination</data><data key="node_description">Privacy Act system of records for Medicare Part B buy-in information.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0268; current catalog includes a November 25, 2025 amendment.</data></node><node id="DB_MEWRK"><data key="node_entity_id">DB_MEWRK</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">MEWRK</data><data key="node_acronym">MEWRK</data><data key="node_domain">Title II / Work CDR Analytics</data><data key="node_description">Management-information database storing data related to development, adjudication, and effectuation of Title II Work Continuing Disability Reviews.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Relationship to eWork or the planned Work CDR Product is not published and is intentionally left unresolved.</data></node><node id="DB_MISF"><data key="node_entity_id">DB_MISF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Management Information Storage Facility</data><data key="node_acronym">MISF</data><data key="node_domain">Title XVI / Management Information</data><data key="node_description">Management-information storage facility that receives duplicate records of SSI I8 alerts under current policy.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Public policy establishes the receiving function but does not disclose physical platform, database technology, retention period, or whether MISF serves other workloads.</data></node><node id="DB_MSHARE"><data key="node_entity_id">DB_MSHARE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Business Information Architecture Shared Tables</data><data key="node_acronym">MSHARE</data><data key="node_domain">Enterprise Data / Business Intelligence</data><data key="node_description">Shared tables/data asset providing common data structures and utilities for SSA's Business Intelligence Architecture.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-56.</data></node><node id="DB_MSP_INFO"><data key="node_entity_id">DB_MSP_INFO</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Medicare Savings Programs Information System</data><data key="node_acronym">MSP Information System</data><data key="node_domain">Medicare / Low-Income Assistance</data><data key="node_description">Privacy Act system of records for Medicare Savings Programs information.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0310; current catalog includes a November 25, 2025 amendment.</data></node><node id="DB_MULTI_SSN_XREF"><data key="node_entity_id">DB_MULTI_SSN_XREF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Multiple Social Security Number Cross Reference File</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Data asset containing cross-reference SSN information.</data><data key="node_observed_status">cataloged_legacy_metadata</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Dataset last updated in 2017; retained as historical/legacy metadata.</data></node><node id="DB_MYSSA_REG_MI"><data key="node_entity_id">DB_MYSSA_REG_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Registration Of Most Everyone Management Information</data><data key="node_domain">Digital Service / Identity Registration</data><data key="node_description">Management-information data tracking the my Social Security suite of services.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-07-28</data><data key="node_confidence">5</data><data key="node_notes">The catalog title is retained verbatim; no unverified expansion or architecture is inferred.</data></node><node id="DB_NARPPF"><data key="node_entity_id">DB_NARPPF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Non-Attorney Representative Prerequisites Process File</data><data key="node_acronym">NARPPF</data><data key="node_domain">Representation / Representative Qualifications</data><data key="node_description">SSA Privacy Act system of records 60-0355 covering the Non-Attorney Representative Prerequisites Process File.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SORN catalog validates the record system; no current technical implementation or relationship to representative applications is inferred.</data></node><node id="DB_NDMIS"><data key="node_entity_id">DB_NDMIS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">National Docketing Management Information System</data><data key="node_acronym">NDMIS</data><data key="node_domain">Hearings / Appeals</data><data key="node_description">SSA Privacy Act system of records 60-0328, National Docketing Management Information System.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SORN catalog validates the record system; no current application architecture, database engine, or relationship to HACPS/ARPS is inferred.</data></node><node id="DB_NDNH"><data key="node_entity_id">DB_NDNH</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">National Directory of New Hires</data><data key="node_acronym">NDNH</data><data key="node_domain">External Data / Earnings &amp; Employment</data><data key="node_description">OCSE database containing new-hire, quarterly wage and quarterly unemployment-compensation information used by SSA for program administration and earnings investigations.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS and active SSA computer-matching agreements corroborate continued use.</data></node><node id="DB_NICMS"><data key="node_entity_id">DB_NICMS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">National Investigative Case Management System</data><data key="node_acronym">NICMS</data><data key="node_domain">OIG / Investigations</data><data key="node_description">Non-public database of fraud allegations and dispositions that warrant further investigation.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-438.</data></node><node id="DB_NID3"><data key="node_entity_id">DB_NID3</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">National Interactive Delinquent Debtors Database</data><data key="node_acronym">NID3</data><data key="node_domain">External Debt Collection</data><data key="node_description">Treasury delinquent-debtor database used in TOP/Benefit Payment Offset matching.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">External Treasury data store; SSA does not operate it.</data></node><node id="DB_NIDD"><data key="node_entity_id">DB_NIDD</data><data key="node_entity_type">reference_data_store</data><data key="node_canonical_name">National Identity Document Database</data><data key="node_acronym">NIDD</data><data key="node_domain">Identity / Enumeration / Document Evidence</data><data key="node_description">SSA reference database listing acceptable and unacceptable identity documents, document descriptions, acceptance limitations, and regional third-level identity-document determinations used in SSN enumeration evidence review.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says regional coordinators use the NIDD User Guide to load acceptable identity documents into SSNAP. Physical database technology and hosting are not disclosed.</data></node><node id="DB_NVF"><data key="node_entity_id">DB_NVF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">National Vendor File</data><data key="node_acronym">NVF</data><data key="node_domain">Disability / Vendor Data</data><data key="node_description">Central repository of DDS vendor information supporting DCPS and other SSA disability activities.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current SSA inventory explicitly describes NVF as a central repository.</data></node><node id="DB_OFFICIAL_UNION_TIME_ODS"><data key="node_entity_id">DB_OFFICIAL_UNION_TIME_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Official Union Time Tracking System Operational Data Store</data><data key="node_domain">Enterprise HR / Labor Relations</data><data key="node_description">Operational data store associated with SSA reporting and accounting of representational activity for American Federation of Government Employees representatives agency-wide.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current Federal Data Catalog entry is non-public and does not disclose the database engine, hosting, refresh process, or interfaces.</data></node><node id="DB_OHA_LEGACY_DB2"><data key="node_entity_id">DB_OHA_LEGACY_DB2</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Office of Hearings and Appeals Legacy Adjudicative Data</data><data key="node_acronym">OHA Legacy DB2</data><data key="node_domain">Hearings &amp; Appeals / Legacy Data</data><data key="node_description">Legacy hearing, appeal and federal-court adjudicative data converted from IDMS to DB2.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-1573; inventory does not establish whether new transactions continue to be written.</data></node><node id="DB_OHO_EXPERT_AVAIL"><data key="node_entity_id">DB_OHO_EXPERT_AVAIL</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">OHO Expert and Reporter Availability and Scheduling Records</data><data key="node_acronym">Expert Availability and Scheduling Records</data><data key="node_domain">Hearings / Experts / Procurement</data><data key="node_description">Paper/electronic records used for availability, scheduling, BPA administration, usage assessment, renewals, invoices, qualifications and related management of experts and verbatim hearing reporters.</data><data key="node_observed_status">current_sorn_catalog_implementation_detail_from_2018</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current catalog lists 60-0012; storage technology is not publicly identified.</data></node><node id="DB_OHO_EXPERT_USAGE"><data key="node_entity_id">DB_OHO_EXPERT_USAGE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">OHO Expert Usage Records</data><data key="node_acronym">Expert Usage Records</data><data key="node_domain">Hearings / Experts / Procurement</data><data key="node_description">Records documenting occasions on which medical, vocational, and other covered experts provided services to hearings operations.</data><data key="node_observed_status">current_sorn_catalog_implementation_detail_from_2018</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">60-0013 remains separately listed even though 60-0012 also states that its records contain usage information; exact physical overlap is unresolved.</data></node><node id="DB_OIG_AUTH_DATA_SOURCE"><data key="node_entity_id">DB_OIG_AUTH_DATA_SOURCE</data><data key="node_entity_type">data_platform</data><data key="node_canonical_name">OIG Authoritative Data Source for Law Enforcement Operations</data><data key="node_domain">OIG Data / Analytics</data><data key="node_description">Authoritative data source created by OIG IT/data-analytics staff to improve business-intelligence reporting for mission-critical law-enforcement operations.</data><data key="node_observed_status">observed_current_fy2026</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes">Public testimony does not identify the product, database engine, schema, or hosting layer.</data></node><node id="DB_ONLINE_EVS"><data key="node_entity_id">DB_ONLINE_EVS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Online Enumeration Verification System</data><data key="node_domain">Identity / SSN Verification</data><data key="node_description">Non-public SSA database supporting several Social Security Number verification systems that verify SSNs against Numident.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-146. Keep separate from Online Enumeration Verification System - Management Information (US-GOV-SSA-42). Constituent verification systems and database technology are not identified by the source. The non-public asset contains PII and FTI. Run 84: Data.gov shows the non-public US-GOV-SSA-146 dataset was last updated September 29, 2026; the catalog still describes it as a database for several SSN verification systems that verify against Numident.</data></node><node id="DB_ONLINE_EVS_MI"><data key="node_entity_id">DB_ONLINE_EVS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Online Enumeration Verification System - Management Information</data><data key="node_domain">Identity Verification</data><data key="node_description">Management-information database for several SSN verification systems that verify against Numident.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-42.</data></node><node id="DB_OPI_CORRESP_CONTROL"><data key="node_entity_id">DB_OPI_CORRESP_CONTROL</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">OPI Correspondence Control System</data><data key="node_acronym">OPI Correspondence Control</data><data key="node_domain">Enterprise Workflow / Correspondence</data><data key="node_description">Non-public production data store for control and tracking of high-priority correspondence received in the Office of Public Inquiries.</data><data key="node_observed_status">observed_current_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-236. It has the same catalog description as EMAC 2 but a different identifier; do not merge without authoritative lineage evidence.</data></node><node id="DB_OWR"><data key="node_entity_id">DB_OWR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Online Wage Reporting System</data><data key="node_acronym">OWR</data><data key="node_domain">Earnings / Employer</data><data key="node_description">Database supporting W-2 and W-2c submissions through SSA internet services.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-04-03</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-147.</data></node><node id="DB_OWR_MI"><data key="node_entity_id">DB_OWR_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Online Wage Reporting Management Information</data><data key="node_acronym">OWR MI</data><data key="node_domain">Earnings / Analytics</data><data key="node_description">Management-information database for W-2/W-2c internet submissions.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-07-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DB_PASS_MI"><data key="node_entity_id">DB_PASS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Plans for Achieving Self-Support Management Information System</data><data key="node_acronym">PASS MIS</data><data key="node_domain">Title XVI / Work Incentives</data><data key="node_description">Privacy Act system of records for Plans for Achieving Self-Support management information.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0255; current catalog includes a January 5, 2024 amendment.</data></node><node id="DB_PCACS_FLAT"><data key="node_entity_id">DB_PCACS_FLAT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">PCACS Flat Files</data><data key="node_acronym">PCACS Flat Files</data><data key="node_domain">Processing Center / Workload Control</data><data key="node_description">Non-public data asset supporting PCACS payment-center workload control, assistance requests and folder-location updating.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-07-28</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-285.</data></node><node id="DB_PEMI"><data key="node_entity_id">DB_PEMI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Post Entitlement Management Information</data><data key="node_acronym">PEMI</data><data key="node_domain">Enterprise Data / Post-Entitlement Analytics</data><data key="node_description">Management-information asset with detail data for more than 500 post-entitlement workload actions drawn from 16 source systems and summarized PE counts.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-713.</data></node><node id="DB_PERSON_STORE"><data key="node_entity_id">DB_PERSON_STORE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Person</data><data key="node_acronym">Person Data Store</data><data key="node_domain">Enterprise Person Data / Identity</data><data key="node_description">SSA cataloged person-centric data store storing information about Social Security Administration customers.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-1698. This establishes a physical/cataloged Person data store, but public evidence does not prove that it is the exact physical backing store of the Person Information application or that all person/program data are centralized here. Current Data.gov metadata records an inventory date of 2017-03-06, which narrows the person-centric store timeline but does not prove identity or continuity with the 2016 BORG/CED implementation.</data></node><node id="DB_PE_MI_DETAIL"><data key="node_entity_id">DB_PE_MI_DETAIL</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Post Entitlement Management Information - Detail Database</data><data key="node_acronym">PE MI Detail</data><data key="node_domain">Title II &amp; XVI / Post-entitlement Analytics</data><data key="node_description">Detailed/aggregate receipt, pending and clearance management information for post-entitlement transactions processed in field offices and processing centers.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-184.</data></node><node id="DB_PE_MI_HISTORY"><data key="node_entity_id">DB_PE_MI_HISTORY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Post Entitlement Management Information - History Database</data><data key="node_acronym">PE MI History</data><data key="node_domain">Title II &amp; XVI / Post-entitlement Analytics</data><data key="node_description">Historical post-entitlement management information for field-office and processing-center transactions.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-185.</data></node><node id="DB_PHUS"><data key="node_entity_id">DB_PHUS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Payment History Update System</data><data key="node_acronym">PHUS</data><data key="node_domain">Title II / Payment History</data><data key="node_description">Title II payment-history system referenced in current POMS and SPS fee-payment processing.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DB_PINFILE"><data key="node_entity_id">DB_PINFILE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Personal Identification Number File</data><data key="node_acronym">PINFile</data><data key="node_domain">Security / Access Control</data><data key="node_description">Privacy Act record system historically and currently cataloged as 60-0214 for access-control information including PIN/password and access-profile information.</data><data key="node_observed_status">current_sorn_catalog_historical_design</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">Current SSA SORN catalog retains 60-0214. The underlying technical implementation may have evolved; do not infer current authentication architecture solely from the older file description.</data></node><node id="DB_PNICS"><data key="node_entity_id">DB_PNICS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSA National Instant Criminal Background Check Database</data><data key="node_acronym">PNICS</data><data key="node_domain">Program Integrity / Representative Payee / External Exchange</data><data key="node_description">SSA data store containing information described by SSA as relevant to individuals prohibited from firearms transactions and shared with the Federal Bureau of Investigation.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-1533. The public inventory states information is shared with the FBI but does not identify the transport, schedule, receiving FBI system, or interface technology.</data></node><node id="DB_PSC_PAPERLESS_MI"><data key="node_entity_id">DB_PSC_PAPERLESS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Program Service Center Paperless Reporting</data><data key="node_acronym">PSC Paperless Reporting</data><data key="node_domain">Processing Center / Document Management Analytics</data><data key="node_description">Management-information reporting asset for daily Program Service Center Paperless statistics.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-08</data><data key="node_confidence">5</data><data key="node_notes">Current reporting does not by itself prove that the 2007 Paperless PSC PIA application and today's Paperless Processing Center implementation are the same technical object.</data></node><node id="DB_RAMP"><data key="node_entity_id">DB_RAMP</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Requests for Accommodation from Members of the Public</data><data key="node_acronym">RAMP</data><data key="node_domain">Customer Service / Accommodation</data><data key="node_description">Privacy Act system of records 60-0378 for standard and non-standard public accommodation requests, request tracking/decisions, correspondence, contact information, disability/impairment information, and related management/research data.</data><data key="node_observed_status">observed_current_modified_sorn</data><data key="node_observed_as_of">2026-01-16</data><data key="node_confidence">5</data><data key="node_notes">Current SORN identifies requesters/third parties plus Claims Folder System, eDIB Claim File, and 60-0350 Appointments/Visitor/Customer Service records as sources. Records are electronic and paper, retrieved by SSN/name, and retained under DAA-0047-2022-0003. No technical relationship to iAccommodate is inferred.</data></node><node id="DB_RECON"><data key="node_entity_id">DB_RECON</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">IRS and SSA Wage Reconciliation Repository</data><data key="node_acronym">RECON</data><data key="node_domain">Earnings / Reconciliation</data><data key="node_description">Repository associated with reconciling employer wages reported to SSA with taxes reported to IRS.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-1482.</data></node><node id="DB_RECON_CTRL"><data key="node_entity_id">DB_RECON_CTRL</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Reconciliation Control Locator Record</data><data key="node_domain">Earnings / Reconciliation</data><data key="node_description">Control records associated with the IRS/SSA wage reconciliation process.</data><data key="node_observed_status">cataloged_legacy_metadata</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Metadata last updated in 2017.</data></node><node id="DB_RECON_DEV"><data key="node_entity_id">DB_RECON_DEV</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Reconciliation Development Worksheet Record</data><data key="node_domain">Earnings / Reconciliation</data><data key="node_description">Development worksheet records associated with IRS/SSA wage reconciliation.</data><data key="node_observed_status">cataloged_legacy_metadata</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Metadata last updated in 2017.</data></node><node id="DB_REP_DISQUAL_SOR"><data key="node_entity_id">DB_REP_DISQUAL_SOR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Representative Disqualification, Suspension, and Non-Recognition Information File</data><data key="node_domain">Representation / Program Integrity</data><data key="node_description">System of records covering disqualified or suspended representatives and persons not recognized as claimant representatives.</data><data key="node_observed_status">current_system_of_records</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0219 remains in SSA's current SORN catalog.</data></node><node id="DB_REP_PAYEE_SURVEY"><data key="node_entity_id">DB_REP_PAYEE_SURVEY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Representative Payee and Beneficiary Survey Data System</data><data key="node_domain">Representative Payee / Research</data><data key="node_description">SSA Privacy Act system of records 60-0370 for representative payee and beneficiary survey data.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SORN catalog validates the record system; no current survey platform or analytical pipeline is inferred.</data></node><node id="DB_ROAR_MASTER"><data key="node_entity_id">DB_ROAR_MASTER</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Recovery of Overpayments Accounting Reporting Master</data><data key="node_acronym">ROAR Master</data><data key="node_domain">Debt &amp; Overpayments</data><data key="node_description">Master data store containing refund/remittance accounting, beneficiary data, overpayment recovery history, and overpayment data for debtors including attorneys and representative payees.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-286.</data></node><node id="DB_RTND"><data key="node_entity_id">DB_RTND</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Routing Transit Number Database</data><data key="node_acronym">RTND</data><data key="node_domain">Payments / Direct Deposit / Reference Data</data><data key="node_description">SSA routing-transit-number reference database exposed through an RTND screen for financial-institution routing information.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Active correspondent-banking POMS explicitly identifies the RTND screen. Physical database technology, ownership, and update feed remain undocumented in the reviewed public material.</data></node><node id="DB_SCDD"><data key="node_entity_id">DB_SCDD</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Counts Demographics Data</data><data key="node_acronym">SCDD</data><data key="node_domain">Enterprise Data / Demographics</data><data key="node_description">Data source for SSA limited-English-proficiency reports, populated by combining SUMS workload data with demographics from SUMS client tables.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-31</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data documentation explicitly describes this lineage.</data></node><node id="DB_SIPEBES_TERRITORY_ADDRESS"><data key="node_entity_id">DB_SIPEBES_TERRITORY_ADDRESS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSA-Initiated PEBES Address System for Certain Territories</data><data key="node_acronym">SIPEBES Territory Address System</data><data key="node_domain">Social Security Statement / Address</data><data key="node_description">System of records established for addresses supplied by Puerto Rico and U.S. territorial governments for Statement recipients not required to file Federal returns.</data><data key="node_observed_status">current_sorn_listing_implementation_uncertain</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">SORN 60-0225 remains in SSA current catalog. Detailed storage/use mechanics are documented historically in 1994; current physical implementation is not assumed.</data></node><node id="DB_SPS_MI"><data key="node_entity_id">DB_SPS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Single Payment System Management Information</data><data key="node_acronym">SPS MI</data><data key="node_domain">Title II / Payments</data><data key="node_description">Non-public management-information data store supporting SPS fee and other Title II payment workloads.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-05</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-60.</data></node><node id="DB_SRF"><data key="node_entity_id">DB_SRF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Source Reference File</data><data key="node_acronym">SRF</data><data key="node_domain">Disability / Reference Data</data><data key="node_description">EDCS state-specific database of doctors, hospitals, schools and other sources used in disability case development.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-01</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 EDCS TOC retains SRF. Detailed database/vendor-extract mechanics come from the 2008 POMS section; do not assume unchanged physical implementation beyond the documented logical function.</data></node><node id="DB_SSI_IC_DO_PROGRAMMATIC"><data key="node_entity_id">DB_SSI_IC_DO_PROGRAMMATIC</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSI Initial Claim District Office Workload Report Programmatic</data><data key="node_domain">Title XVI / Initial Claims Analytics</data><data key="node_description">Weekly programmatic data asset listing SSI initial claims completed, used to generate agency completion counts.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-574. Kept separate from the existing management-information asset because SSA inventories both separately; no feed between them is inferred.</data></node><node id="DB_SSI_IC_DO_WORKLOAD_MI"><data key="node_entity_id">DB_SSI_IC_DO_WORKLOAD_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSI Initial Claims District Office Workload Report Management Information</data><data key="node_acronym">SSI IC DO Workload MI</data><data key="node_domain">Title XVI / Initial Claims Analytics</data><data key="node_description">Weekly list of SSI initial claims completed, used to generate agency completion counts.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">The source does not identify the upstream transaction system, so no physical feed is modeled.</data></node><node id="DB_SSI_IRS_INTERFACE"><data key="node_entity_id">DB_SSI_IRS_INTERFACE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSI IRS Interface Database</data><data key="node_acronym">SSI IRS Database</data><data key="node_domain">Title XVI / IRS Match / Program Integrity</data><data key="node_description">Interface database holding IRS non-wage match information used for SSI alert development and retrieval through MI Central and SSTNG.</data><data key="node_observed_status">observed_current_two_year_retention</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS observed in the September 10, 2026 batch still states that the IRS interface database contains the most recent two years of IRS information and is retrievable through MI Central and SSTNG. Earlier 2026 evidence that the IRS agreement permits longer retention remains a planned/allowed state; public evidence does not establish production implementation of extended retention.</data></node><node id="DB_SSI_PE_ODS"><data key="node_entity_id">DB_SSI_PE_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSI Post Entitlement Operational Data Store</data><data key="node_acronym">PE ODS</data><data key="node_domain">Title XVI / Post-entitlement Work Control</data><data key="node_description">Operational data store used to control and select SSI post-entitlement diary workloads, including IRS 5B computer-match alerts, IRS pension 5H diaries, savings-security interface alerts, and age-18 critical-birthday redeterminations.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled as the Title XVI PE ODS described in current POMS. Current POMS maps IRS 5B match data and 5H pension-diary workload to PE ODS. Kept separate from SUMS Title XVI PEODS and the generic RZ/LI Interface Database because public evidence does not prove physical identity; platform, engine, hosting, and transport remain undisclosed. The 5B POMS says the operational IRS-data database retains the most recent two years; the Atlas does not extend that statement to unrelated PE ODS content.</data></node><node id="DB_SSI_PE_REJECT_MI"><data key="node_entity_id">DB_SSI_PE_REJECT_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSI Post-Eligibility Reject Report Management Information</data><data key="node_domain">Title XVI / Exceptions</data><data key="node_description">Management-information reports/listings of batch post-eligibility transactions that fail to update the SSR.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-577.</data></node><node id="DB_SSI_PE_REJECT_PROG"><data key="node_entity_id">DB_SSI_PE_REJECT_PROG</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSI Post-Eligibility Reject Report Programmatic</data><data key="node_domain">Title XVI / Exceptions</data><data key="node_description">Reports/listings of batch post-eligibility transactions that fail to update the SSR.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-573.</data></node><node id="DB_SSI_WAGE_REPORT_HISTORY"><data key="node_entity_id">DB_SSI_WAGE_REPORT_HISTORY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSI Wage Reporting History</data><data key="node_acronym">SSI Wage Reporting History</data><data key="node_domain">Title XVI / Earnings / Wage Reporting</data><data key="node_description">Person-level history data for telephone and mobile SSI wage reports.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-591. Public catalog does not identify the exact ingestion interface from SSITWR or mobile wage reporting.</data></node><node id="DB_SSNAP_AUDIT"><data key="node_entity_id">DB_SSNAP_AUDIT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSNAP Audit Trail System</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Database logging enumeration transactions processed by SSNAP.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current Data.gov inventory US-GOV-SSA-58, last updated September 29, 2026, describes the database as logging enumeration transactions processed by SSNAP.</data></node><node id="DB_SSNAP_MI"><data key="node_entity_id">DB_SSNAP_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSN Application Process MI</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Management-information asset containing information about the enumeration process.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-154.</data></node><node id="DB_SSNAP_MI_ODS"><data key="node_entity_id">DB_SSNAP_MI_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSN Application Process Management Information - Operational Data Store</data><data key="node_acronym">SSNAP MI ODS</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Enumeration ODS used for ad hoc query and standard management-information reporting.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-59; explicitly documented as DB2 using SUMS standards and architecture.</data></node><node id="DB_SSNAP_TX"><data key="node_entity_id">DB_SSNAP_TX</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSN Application Process Transaction Database</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Database storing data for all transactions in the enumeration process.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">SSA inventory asset associated with the SSN Application Process.</data></node><node id="DB_SSRPT"><data key="node_entity_id">DB_SSRPT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title XVI / Supplemental Security Record Point In Time</data><data key="node_acronym">SSRPT</data><data key="node_domain">Title XVI / Core Record</data><data key="node_description">Point-in-time database holding temporary SSR images during the operating day before nightly SSR batch update.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-07-07</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-429.</data></node><node id="DB_SS_STATEMENT_PREF"><data key="node_entity_id">DB_SS_STATEMENT_PREF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Online, Batch and CICS Social Security Statement</data><data key="node_domain">Social Security Statement / Client Preferences</data><data key="node_description">Daily non-public database containing client preference information for SSA-initiated Social Security Statements, SSN, and disposition information for paper Statements received by the SSN holder.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-163. Relationship to the separately documented Statement History File is not established by the catalog record.</data></node><node id="DB_STATEMENT_HISTORY"><data key="node_entity_id">DB_STATEMENT_HISTORY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Social Security Statement History File</data><data key="node_acronym">Statement History File</data><data key="node_domain">Social Security Statement / History</data><data key="node_description">Electronic file containing Social Security Statement processing history such as last on-request and system-initiated issuance, language, and manual-processing status; current POMS says it can be queried online.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The 1994 SORN established the SIPEBES History File and documented IRS-address provenance. Current POMS confirms the file remains an electronic queryable file, but does not re-document every historical field.</data></node><node id="DB_SUMS_APPEALS_ODS"><data key="node_entity_id">DB_SUMS_APPEALS_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Appeals Operational Data Store</data><data key="node_acronym">SUMS Appeals ODS</data><data key="node_domain">Enterprise Data / Appeals Analytics</data><data key="node_description">Single-source operational data store for agency appeals information used in workload management and business intelligence.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-54.</data></node><node id="DB_SUMS_CDR_ODS"><data key="node_entity_id">DB_SUMS_CDR_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSA Unified Measurement System Continuing Disability Review Operation Data Store</data><data key="node_acronym">SUMS CDR ODS</data><data key="node_domain">Disability / Continuing Disability Review / Analytics</data><data key="node_description">SUMS data store containing management information reporting for the continuing disability review process.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-83. The inventory does not identify a specific transaction-system feed.</data></node><node id="DB_SUMS_CLIENT_TABLES"><data key="node_entity_id">DB_SUMS_CLIENT_TABLES</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Client Tables</data><data key="node_domain">Enterprise Data / Demographics</data><data key="node_description">SUMS Client data/tables described by SSA as a subset of Client data housed in the Integrated Client Database (ICDB); used in SUMS demographics/reporting lineage.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-05-01</data><data key="node_confidence">5</data><data key="node_notes">Public documentation does not expose physical database technology or schema.</data></node><node id="DB_SUMS_COUNTS_DW"><data key="node_entity_id">DB_SUMS_COUNTS_DW</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Counts Data Warehouse</data><data key="node_acronym">SUMS Counts DW</data><data key="node_domain">Enterprise Data / Analytics</data><data key="node_description">Social Security Unified Measurement System data warehouse used as the source for current public workload datasets including Medicare Extra Help decisions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data explicitly names the warehouse and a daily workload feed from Medicare ODS.</data></node><node id="DB_SUMS_EARNINGS_ODS"><data key="node_entity_id">DB_SUMS_EARNINGS_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Earnings Operational Data Store</data><data key="node_acronym">SUMS Earnings ODS</data><data key="node_domain">Enterprise Data / Earnings Analytics</data><data key="node_description">Operational data store supporting information and statistical counts for SUMS earnings data.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current Data.gov inventory US-GOV-SSA-55, last updated September 29, 2026, describes the ODS as supporting information and statistical counts for SUMS earnings data.</data></node><node id="DB_SUMS_ENUM_ODS"><data key="node_entity_id">DB_SUMS_ENUM_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Enumeration Operational Data Store</data><data key="node_acronym">SUMS Enumeration ODS</data><data key="node_domain">Identity &amp; Enumeration / Analytics</data><data key="node_description">Operational data store from which SSA extracts public enumeration processing-time data.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Open Data directly names this store. The precise programmatic source feed is not published and is not inferred.</data></node><node id="DB_SUMS_ES_DW_QUERY"><data key="node_entity_id">DB_SUMS_ES_DW_QUERY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS and Electronic Services Production Data Warehouse Query Instance</data><data key="node_domain">Enterprise Data / Query</data><data key="node_description">Production data-warehouse query instance storing information for query access across the named SUMS/electronic-services warehouse environment.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-202.</data></node><node id="DB_SUMS_MCAS_RZLI_INTERFACE"><data key="node_entity_id">DB_SUMS_MCAS_RZLI_INTERFACE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">RZ/LI Interface Database</data><data key="node_domain">Title XVI / Management Information</data><data key="node_description">Interface database holding alert data retrievable through SUMS/MCAS MI Central for redetermination and limited-issue workloads.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-07</data><data key="node_confidence">4</data><data key="node_notes">Canonical name is descriptive because POMS calls it only "an interface database." No physical database product, schema, or hosting platform is inferred.</data></node><node id="DB_SUMS_T16_IC_ODS"><data key="node_entity_id">DB_SUMS_T16_IC_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Title XVI Initial Claims Operational Data Store</data><data key="node_acronym">SUMS T16 IC ODS</data><data key="node_domain">Title XVI / Initial Claims</data><data key="node_description">Current Title XVI initial-claims store and MI/BI operational data store from submission through adjudication.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov has two inventory records (US-GOV-SSA-64 and US-GOV-SSA-96) describing MI/BI and current-store views of the same named ODS.</data></node><node id="DB_SUMS_T16_PEODS"><data key="node_entity_id">DB_SUMS_T16_PEODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Title XVI Post-Eligibility Operational Data Store</data><data key="node_acronym">PEODS</data><data key="node_domain">Title XVI / Post-Eligibility</data><data key="node_description">Current store for Title XVI redeterminations and limited issues; includes Starz &amp; Stripes workload-control data.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-97.</data></node><node id="DB_SUMS_T2_PE_ODS"><data key="node_entity_id">DB_SUMS_T2_PE_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SUMS Title II Post Entitlement Operational Data Store</data><data key="node_acronym">SUMS T2 PE ODS</data><data key="node_domain">Title II / Post-entitlement Analytics</data><data key="node_description">Operational data store providing standard/ad hoc reporting for Title II post-entitlement changes, reinstatements, payments and checks.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-101.</data></node><node id="DB_SVB_CLAIMS_MI"><data key="node_entity_id">DB_SVB_CLAIMS_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Social Security Title VIII Special Veterans Benefits Claims Development and Management Information System</data><data key="node_acronym">SVB Claims MI</data><data key="node_domain">Special Veterans Benefits</data><data key="node_description">Privacy Act system of records for Title VIII Special Veterans Benefits claims development and management information.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0273; current catalog includes a November 25, 2025 amendment.</data></node><node id="DB_T16_DW_STAGING"><data key="node_entity_id">DB_T16_DW_STAGING</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title 16 Data Warehouse Staging Instance</data><data key="node_domain">Title XVI / Analytics</data><data key="node_description">Staging instance for Title 16 workload-management ODS and post-eligibility data feeding processing-time data to WMDW.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DB_T16_FO_APPEALS_ODS"><data key="node_entity_id">DB_T16_FO_APPEALS_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title XVI Field Office Appeals - Operational Data Store</data><data key="node_acronym">T16 FO Appeals ODS</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Legacy management-information system tracking Title XVI appeals from reconsideration through court adjudicative levels.</data><data key="node_observed_status">legacy_replaced_by_sums_appeals</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">SSA Open Data explicitly says this legacy asset was replaced by SUMS Appeals; the actual cutover date is not published.</data></node><node id="DB_T16_FO_DIARY_MI"><data key="node_entity_id">DB_T16_FO_DIARY_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title XVI Field Office Diary Listing Management Information</data><data key="node_domain">Title XVI / Workload Management</data><data key="node_description">Weekly management-information lists of pending SSI diaries by office.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-575.</data></node><node id="DB_T16_FO_DIARY_PROG"><data key="node_entity_id">DB_T16_FO_DIARY_PROG</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title XVI Field Office Diary Listing Programmatic</data><data key="node_domain">Title XVI / Workload Management</data><data key="node_description">Weekly programmatic lists of pending SSI diaries by office.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-571.</data></node><node id="DB_T2_GARNISH"><data key="node_entity_id">DB_T2_GARNISH</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">T2 Garnishment Process</data><data key="node_acronym">T2 Garnishment</data><data key="node_domain">Title II / Garnishment</data><data key="node_description">Data store supporting garnishment/tax-levy benefit adjustments and payment data for Treasury disbursement to IRS.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-170.</data></node><node id="DB_T2_NOTICES"><data key="node_entity_id">DB_T2_NOTICES</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title 2 Notices</data><data key="node_acronym">T2 Notices</data><data key="node_domain">Title II / Notices</data><data key="node_description">Non-public data store for Title II notice batch-processing information.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-924; metadata tags include MADCAP but no direct application interface is asserted.</data></node><node id="DB_T2_ODS"><data key="node_entity_id">DB_T2_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title 2 Operational Data Store</data><data key="node_acronym">Title 2 ODS</data><data key="node_domain">Title II / Analytics</data><data key="node_description">Non-public Title II data asset that provides processing-time data to the Work Measurement Data Warehouse.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Catalog title is 'Title 2 Data Warehouse'; description calls the asset the Title 2 ODS. Data.gov identifier US-GOV-SSA-205.</data></node><node id="DB_T2_SHARED_CASE"><data key="node_entity_id">DB_T2_SHARED_CASE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">T2 Shared (Case)</data><data key="node_acronym">T2 Shared Case</data><data key="node_domain">Title II / Shared Data</data><data key="node_description">Non-public Title II shared data asset containing data specific to the claim SSN.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DB_T2_SHARED_LEGACY"><data key="node_entity_id">DB_T2_SHARED_LEGACY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title II Shared Database</data><data key="node_acronym">Title II Shared Database</data><data key="node_domain">Title II / Claims</data><data key="node_description">Legacy shared Title II database named in SSA post-entitlement modernization planning as a redundancy target alongside the MCS Pending File and MBR.</data><data key="node_observed_status">historical_legacy_reference</data><data key="node_observed_as_of">2019</data><data key="node_confidence">4</data><data key="node_notes">Not automatically equated with the separately cataloged T2 Shared (Person) store; public evidence in this run does not establish physical equivalence.</data></node><node id="DB_T2_SHARED_PERSON"><data key="node_entity_id">DB_T2_SHARED_PERSON</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">T2 Shared (Person)</data><data key="node_acronym">T2 Shared Person</data><data key="node_domain">Title II / Shared Data</data><data key="node_description">Current non-public Title II shared-person data asset. Historical documentation placed citizenship/lawful-presence information here, but Title II citizenship storage moved to Person Information in June 2021; public evidence does not fully define the asset’s remaining current field scope.</data><data key="node_observed_status">current_inventory_citizenship_migrated</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-169. Title II citizenship storage moved from T2 Shared to Person Information effective June 27, 2021. Do not infer that the entire T2 Shared asset was retired; its remaining current field scope is unresolved.</data></node><node id="DB_T2_WMI"><data key="node_entity_id">DB_T2_WMI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title II Workload Management Information</data><data key="node_acronym">T2 WMI</data><data key="node_domain">Title II / Workload Analytics</data><data key="node_description">Detailed initial-claims data used to summarize workload and task information at office, regional and national levels.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-100.</data></node><node id="DB_TAR"><data key="node_entity_id">DB_TAR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Transaction Accuracy Review</data><data key="node_acronym">TAR</data><data key="node_domain">Title II / Quality</data><data key="node_description">Data asset supporting Transaction Accuracy Review measurement of Title II adjudicative accuracy.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-71.</data></node><node id="DB_TAXY"><data key="node_entity_id">DB_TAXY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Automate The Tax Levy Process (Taxy)</data><data key="node_acronym">Taxy</data><data key="node_domain">Title II / Tax Levy</data><data key="node_description">Data store supporting automation of Title II tax-levy payment adjustments and Treasury disbursement to IRS.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-172.</data></node><node id="DB_TAX_LEVY_NOTICE_DB2"><data key="node_entity_id">DB_TAX_LEVY_NOTICE_DB2</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Tax Levy DB2 Database</data><data key="node_domain">Title II / Tax Levy / Notices</data><data key="node_description">DB2 data store documented as an input to the Tax Levy Notice System.</data><data key="node_observed_status">historical_architecture_component_current_system_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">The database is explicitly documented in the 2006 architecture description while the Tax Levy Notice System remains in the current POMS chapter. Relationship to the separately cataloged Automate The Tax Levy Process (Taxy) data store is unresolved and no merge is inferred.</data></node><node id="DB_TDCP"><data key="node_entity_id">DB_TDCP</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Totalization Data Collection Program Database</data><data key="node_acronym">TDCP database</data><data key="node_domain">Title II / International / Totalization</data><data key="node_description">Logical TDCP data store that houses electronic copies of completed forms for three years and keys records by SSN, agreement code and receipt code.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Mapped as a logical data store only; database engine and hosting are not inferred.</data></node><node id="DB_TITLE2_ODS"><data key="node_entity_id">DB_TITLE2_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Title II Operational Data Store</data><data key="node_acronym">Title II ODS</data><data key="node_domain">Title II / Enterprise Data</data><data key="node_description">Operational data store that receives nightly MCS data and serves as SSA's primary source of management information for initial claims processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data documentation explicitly names this data store and nightly MCS feed.</data></node><node id="DB_TPPS_ODS"><data key="node_entity_id">DB_TPPS_ODS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Third Party Payment System Operational Data Store</data><data key="node_acronym">TPPS ODS</data><data key="node_domain">Enterprise Data / Payment Analytics</data><data key="node_description">Operational data store containing management information on SSA third-party payment transactions.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-08</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-73.</data></node><node id="DB_TRAVEL_BORDER_CROSSING"><data key="node_entity_id">DB_TRAVEL_BORDER_CROSSING</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Travel and Border Crossing Records</data><data key="node_domain">Program Integrity / External Travel Data</data><data key="node_description">Privacy Act system of records 60-0389 holding identity, citizenship/immigration, travel-country, deportation, document, mode, and U.S. arrival/departure information used to establish or verify Title II, Title XVI, and Title XVIII eligibility or entitlement.</data><data key="node_observed_status">observed_current_modified_sorn</data><data key="node_observed_as_of">2025-08-20</data><data key="node_confidence">5</data><data key="node_notes">Current SORN identifies DHS CBP ADIS and covered individuals themselves as record sources; paper/electronic storage; retrieval by name, SSN, and DOB; retention under NARA GRS 4.2 item 130. No downstream master-record update mechanism is stated.</data></node><node id="DB_TREASURY_CIR"><data key="node_entity_id">DB_TREASURY_CIR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Treasury Collection Information Repository</data><data key="node_acronym">CIR</data><data key="node_domain">Payments / Debt / Treasury / External Exchanges</data><data key="node_description">Treasury data archive and reporting tool that provides a single place to view or download settled transaction information from Treasury revenue collection systems; SSA uses CIR in the programmatic remittance lockbox workflow.</data><data key="node_observed_status">observed_current_external_dependency</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS establishes SSA use of CIR for lockbox transactions; no claim is made that SSA operates or hosts the repository.</data></node><node id="DB_TSMI"><data key="node_entity_id">DB_TSMI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Telephone System Management Information</data><data key="node_acronym">TSMI</data><data key="node_domain">Infrastructure / Telephony / Management Information</data><data key="node_description">SSA catalog asset providing configuration, management, function options, maintenance procedures, and management information for the VoIP Station Manager.</data><data key="node_observed_status">catalog_record_present_currentity_unconfirmed</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">4</data><data key="node_notes">Data.gov still exposed the record in 2026 but the underlying dataset was last updated 2018-01-08; current production use is not inferred.</data></node><node id="DB_TTW_PAYMENT"><data key="node_entity_id">DB_TTW_PAYMENT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Ticket-to-Work and Self-Sufficiency Program Payment Database</data><data key="node_domain">Ticket to Work / Payments</data><data key="node_description">Privacy Act system of records for Ticket-to-Work program payment information.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0295; runtime technology and exact application interfaces are not public.</data></node><node id="DB_TTW_PM_MI"><data key="node_entity_id">DB_TTW_PM_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Ticket-to-Work Program Manager Management Information System</data><data key="node_acronym">TTW PM MIS</data><data key="node_domain">Ticket to Work / Management Information</data><data key="node_description">Privacy Act system of records for Ticket-to-Work Program Manager management information.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0300; exact interface to iTOPSS or Ticket Portal is not asserted.</data></node><node id="DB_TTW_WORKLOAD_MI"><data key="node_entity_id">DB_TTW_WORKLOAD_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Ticket To Work Workload - Management Information</data><data key="node_acronym">TTW Workload MI</data><data key="node_domain">Ticket to Work / Work Incentives</data><data key="node_description">Management-information asset covering disability beneficiaries participating in the Ticket to Work/back-to-work program.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Public catalog identifies workload/participant MI but does not disclose physical database technology.</data></node><node id="DB_UNIFIED_ICM_CCE"><data key="node_entity_id">DB_UNIFIED_ICM_CCE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Unified ICM/Unified CCE Databases</data><data key="node_acronym">Unified ICM/CCE</data><data key="node_domain">Customer Service / Telephony</data><data key="node_description">Historical CARE 2020 database architecture in which a central database held N8NN routing configuration and history while a local database held real-time call-center activity.</data><data key="node_observed_status">historical_architecture_current_operation_unverified</data><data key="node_observed_as_of">2017-12-22</data><data key="node_confidence">3</data><data key="node_notes">Official SSA Open Data record remains cataloged in 2026 but its substantive metadata was last modified in 2017. Do not treat this as confirmed current physical architecture.</data></node><node id="DB_USPS_NCOA"><data key="node_entity_id">DB_USPS_NCOA</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">USPS National Change of Address Database</data><data key="node_acronym">NCOA</data><data key="node_domain">External Data / Address</data><data key="node_description">USPS National Change of Address database containing original and new mailing addresses, matched against SSA Title II address records through a licensed vendor.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The licensed vendor used for the matching operation is not identified in the cited public POMS; no vendor is inferred.</data></node><node id="DB_VENDOR_INFO_REPO"><data key="node_entity_id">DB_VENDOR_INFO_REPO</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSA Vendor Information Repository</data><data key="node_domain">Procurement / Market Research</data><data key="node_description">Repository database holding vendor capability information for SSA market research and made available to SSA components.</data><data key="node_observed_status">observed_current_guidance</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Official guidance says vendor information remains approximately one year and must be resubmitted to remain available; database technology is not disclosed. Run 83: current OAG guidance says vendor information remains approximately one year before deletion unless resubmitted. A 2018 SSA Industry Day Q&amp;A described the repository as an internal SharePoint site; current physical implementation remains unconfirmed.</data></node><node id="DB_VENDOR_PAYMENT_UNNAMED"><data key="node_entity_id">DB_VENDOR_PAYMENT_UNNAMED</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Unnamed SSA Vendor Payment Database</data><data key="node_domain">Finance / Vendor Payments</data><data key="node_description">Unnamed SSA database that current SSA vendor guidance says is automatically updated when enrolled vendors change financial information through SAM.</data><data key="node_observed_status">observed_current_unnamed</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The source explicitly says “SSA’s database” but does not provide a system name, schema, platform, hosting, or establish identity with Administrative Payment Information or SSOARS. Keep separate until corroborated.</data></node><node id="DB_VIPR_MI"><data key="node_entity_id">DB_VIPR_MI</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Visitor Intake Processing Re-write Management Information</data><data key="node_acronym">VIPR MI</data><data key="node_domain">Field Office / Customer Service Analytics</data><data key="node_description">Data store containing detailed visitor wait-time, visit, call, and other customer-relationship information related to VIPR and CHIP for ad-hoc management-information querying.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">The source explicitly references both VIPR and CHIP but does not publish source-system interfaces.</data></node><node id="DB_VR_REIMB_CASE"><data key="node_entity_id">DB_VR_REIMB_CASE</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Vocational Rehabilitation Reimbursement Case Processing System</data><data key="node_domain">Vocational Rehabilitation / Reimbursement</data><data key="node_description">Privacy Act system of records for vocational-rehabilitation reimbursement case processing.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SORN 60-0221. Exact technical relationship to current VRRMS is not asserted.</data></node><node id="DB_WEI_REPO"><data key="node_entity_id">DB_WEI_REPO</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Wage and Employment Information Repository</data><data key="node_acronym">WEI Repository</data><data key="node_domain">Earnings / Payroll Data</data><data key="node_description">Secure repository holding wage/employment information obtained through PIE and accessible to SSA workloads.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA says monthly data began in April 2025.</data></node><node id="DB_WMDW"><data key="node_entity_id">DB_WMDW</data><data key="node_entity_type">data_warehouse</data><data key="node_canonical_name">Work Measurement Data Warehouse</data><data key="node_acronym">WMDW</data><data key="node_domain">Enterprise / Work Measurement</data><data key="node_description">Warehouse named by SSA Open Data as the recipient of Title 2 ODS processing-time data.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current Title II and Title XVI Open Data assets explicitly identify WMDW as the recipient of processing-time data; broader physical topology remains unpublished.</data></node><node id="DB_WMI_GARNISHMENT"><data key="node_entity_id">DB_WMI_GARNISHMENT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Workload Management Information For Garnishment</data><data key="node_acronym">Garnishment WMI</data><data key="node_domain">Payments / Garnishment Analytics</data><data key="node_description">Reporting data supporting ad-hoc queries and standard reports for garnishment, including Title II benefit adjustments and payments to Treasury.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Physical relationship to the existing T2 Garnishment Process data store is not published.</data></node><node id="DB_WMI_TAX_LEVY"><data key="node_entity_id">DB_WMI_TAX_LEVY</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Workload Management Information For Tax Levy</data><data key="node_acronym">Tax Levy WMI</data><data key="node_domain">Title II / Tax Levy Analytics</data><data key="node_description">Non-public reporting data for Title II tax-levy payments and Treasury disbursement to IRS.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-07-07</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-70.</data></node><node id="DB_ZIP_CODE_MASTER"><data key="node_entity_id">DB_ZIP_CODE_MASTER</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">ZIP Code Master File</data><data key="node_acronym">ZIP Code Master File</data><data key="node_domain">Address / Postal Reference</data><data key="node_description">Reference file containing ZIP Code and Post Office data, described by SSA as based on USPS address information and updated monthly for ZIP maintenance.</data><data key="node_observed_status">observed_current_policy_reference_implementation_unconfirmed</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Detailed implementation description is substantively dated 2011; current physical store is not established.</data></node><node id="DIARY_R8"><data key="node_entity_id">DIARY_R8</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">R8 Conserved Funds Diary</data><data key="node_acronym">R8</data><data key="node_domain">Title XVI / Representative Payee / Resources</data><data key="node_description">SSI conserved-funds diary set when WBDOC processing of an annual representative-payee accounting report shows conserved funds above the policy threshold.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-02</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says WBDOC enters the CF field in SSR and the case is selected for a subsequent limited-issue/redetermination workload.</data></node><node id="DOC_DIB_CESSATION_EXCLUSION"><data key="node_entity_id">DOC_DIB_CESSATION_EXCLUSION</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DIB Cessation Exclusion Document</data><data key="node_acronym">DIB Cessation Exclusion</data><data key="node_domain">Disability / Work CDR / Effectuation</data><data key="node_description">Document generated by eWork for manual Processing Center effectuation when an automated update cannot be completed.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-14</data><data key="node_confidence">5</data><data key="node_notes">Routed through paperless/Evidence Portal workflows and associated with PCACS DIBCESS action control.</data></node><node id="DOC_IAA_ADMIN_AGREEMENT"><data key="node_entity_id">DOC_IAA_ADMIN_AGREEMENT</data><data key="node_entity_type">agreement_document</data><data key="node_canonical_name">IAA Administrative Agreement</data><data key="node_domain">Data Exchange / Governance / Interagency</data><data key="node_description">Administrative agreement identifying the provisions of an SSA Interagency Agreement package.</data><data key="node_observed_status">observed_current_glossary</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical document artifact; physical document-management implementation is not identified.</data></node><node id="DOC_IAA_OGC_CLEARANCE"><data key="node_entity_id">DOC_IAA_OGC_CLEARANCE</data><data key="node_entity_type">clearance_document</data><data key="node_canonical_name">IAA Office of General Counsel Clearance Memorandum</data><data key="node_acronym">OGC Clearance Memo</data><data key="node_domain">Data Exchange / Governance / Interagency</data><data key="node_description">Office of the General Counsel clearance memorandum included in the SSA Interagency Agreement package.</data><data key="node_observed_status">observed_current_glossary</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical document artifact; storage implementation is not identified.</data></node><node id="DOC_SSI_UNDELIVERABLE_COVER_LETTER"><data key="node_entity_id">DOC_SSI_UNDELIVERABLE_COVER_LETTER</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI Undeliverable Cover Letter</data><data key="node_acronym">UCL</data><data key="node_domain">Title XVI / Address / Notices</data><data key="node_description">Cover letter attached when specified returned SSI notices with appeal rights are re-mailed after SSA locates the claimant, recipient, or payee at a current address.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current TN 54 (06-26) retains the UCL exhibit and re-mailing rule.</data></node><node id="DOC_WAGE_INVESTIGATIVE_NOTICE"><data key="node_entity_id">DOC_WAGE_INVESTIGATIVE_NOTICE</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Electronic Wage Reporting Investigative Notice</data><data key="node_acronym">Investigative Notice</data><data key="node_domain">Earnings / Program Integrity</data><data key="node_description">Notice sent to a wage-report submitter when SSA identifies anomalous wage reports requiring investigation or corrective action.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The notice identifies wage reports by WFID, EIN, and tax year and provides required actions/deadlines.</data></node><node id="DOM_BLACK_LUNG"><data key="node_entity_id">DOM_BLACK_LUNG</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Black Lung Benefit Data</data><data key="node_acronym">Black Lung</data><data key="node_domain">Program Data</data><data key="node_description">Black Lung Part B and Part C benefit/payment information relevant to SSA residual administration, SSI income, and Title II offset.</data><data key="node_observed_status">observed_current_program_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_CITIZENSHIP"><data key="node_entity_id">DOM_CITIZENSHIP</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Citizenship Verification Data</data><data key="node_acronym">Citizenship</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Citizenship-verification information used in state benefit-program exchanges.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_CLAIMFOLDER"><data key="node_entity_id">DOM_CLAIMFOLDER</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Claims Folder Data</data><data key="node_acronym">Claims Folder</data><data key="node_domain">Claims / Evidence</data><data key="node_description">Claim and evidence records governed by claims-folder and electronic-disability records notices.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_DB_RECORD_METADATA"><data key="node_entity_id">DOM_DB_RECORD_METADATA</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Relational Database and Record-Structure Metadata</data><data key="node_domain">Enterprise Data / Metadata</data><data key="node_description">Logical Atlas domain for physical/logical relational-database and record-structure metadata managed by EMR.</data><data key="node_observed_status">logical_domain</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Logical domain only; not asserted as a separate SSA physical system.</data></node><node id="DOM_DEATH"><data key="node_entity_id">DOM_DEATH</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Death Data</data><data key="node_acronym">Death</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Death notifications and related data received or maintained by SSA.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_EARNINGS"><data key="node_entity_id">DOM_EARNINGS</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Earnings Data</data><data key="node_acronym">Earnings</data><data key="node_domain">Earnings</data><data key="node_description">Wage/self-employment/coverage data used in SSA programs and exchange products.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_ENUMERATION"><data key="node_entity_id">DOM_ENUMERATION</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Enumeration / SSN Assignment</data><data key="node_acronym">Enumeration</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Business/data domain covering SSN application, assignment, correction and card issuance.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Separated from SSN verification, which is modeled as DOM_SSNV.</data></node><node id="DOM_E_SERVICES"><data key="node_entity_id">DOM_E_SERVICES</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Electronic Service Usage Data</data><data key="node_acronym">Electronic Services MI</data><data key="node_domain">Enterprise Data / Digital Services Analytics</data><data key="node_description">Management-information domain for usage of SSA electronic services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">Domain node created from the current Electronic Services ODS purpose.</data></node><node id="DOM_IT_CONFIG_ASSET"><data key="node_entity_id">DOM_IT_CONFIG_ASSET</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">IT Configuration and Asset Metadata</data><data key="node_domain">Enterprise IT / Configuration Management</data><data key="node_description">Configuration-item and IT-asset metadata including characteristics, authorized configurations, identifiers, and relationships among components and assets.</data><data key="node_observed_status">observed_current_data_domain</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled directly from the SSA Enterprise Configuration Management System data inventory description and keywords.</data></node><node id="DOM_MEDICARE"><data key="node_entity_id">DOM_MEDICARE</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Medicare-Related Data</data><data key="node_acronym">Medicare</data><data key="node_domain">Medicare</data><data key="node_description">Medicare-related information used in SSA-administered or exchanged workloads.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_PERSON_CUSTOMER_RECORD"><data key="node_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Enterprise Person / Customer Record</data><data key="node_acronym">Person / Customer Record</data><data key="node_domain">Enterprise Person Data</data><data key="node_description">Enterprise logical person/customer-record domain. Current SSA evidence now includes both the Person Information application, positioned as the Customer Record database, and a separately cataloged physical 'Person' data store for SSA customer information.</data><data key="node_observed_status">logical_domain_with_physical_pi_person_storage_established</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Logical enterprise person/customer domain. Authoritative SSA evidence establishes a physical PI/PERSON web-based primary storage application and positions PI as the Customer Record database. A separate Federal Data Catalog asset named Person also exists; public evidence still does not prove that DB_PERSON_STORE is the exact backing store for APP_PERSON_INFO or that all program data are centralized there.</data></node><node id="DOM_PRISONER"><data key="node_entity_id">DOM_PRISONER</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Prisoner Data</data><data key="node_acronym">Prisoner</data><data key="node_domain">Program Integrity</data><data key="node_description">Confinement/release/facility data reported to SSA.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_PROGRAM_DEBT"><data key="node_entity_id">DOM_PROGRAM_DEBT</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Program Debt and Receivables Data</data><data key="node_acronym">Program Debt</data><data key="node_domain">Debt &amp; Overpayments</data><data key="node_description">Debt, receivable, collection, remittance, due-process and recovery information for SSA-administered programs.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_REPPAYEE"><data key="node_entity_id">DOM_REPPAYEE</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Representative Payee Data</data><data key="node_acronym">Rep Payee</data><data key="node_domain">Representative Payee</data><data key="node_description">Representative-payee, beneficiary and related misuse/control data.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_SSNV"><data key="node_entity_id">DOM_SSNV</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">SSN Verification Data</data><data key="node_acronym">SSN Verification</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Data used to verify Social Security numbers and associated identity attributes.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="DOM_SVB"><data key="node_entity_id">DOM_SVB</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Special Veterans Benefits Data</data><data key="node_acronym">SVB</data><data key="node_domain">Program Data</data><data key="node_description">Data concerning Special Veterans Benefits eligibility and payment under SSA-administered programs.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-05-11</data><data key="node_confidence">5</data><data key="node_notes">CMA 1008 explicitly covers SSI and SVB recipients.</data></node><node id="DOM_TITLE16"><data key="node_entity_id">DOM_TITLE16</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Title XVI Benefit Data</data><data key="node_acronym">Title XVI</data><data key="node_domain">Title XVI / SSI</data><data key="node_description">SSI eligibility and payment data referenced by SSA exchange products.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Domain object; source system linkage is added only when directly documented.</data></node><node id="DOM_TITLE2"><data key="node_entity_id">DOM_TITLE2</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Title II Benefit Data</data><data key="node_acronym">Title II</data><data key="node_domain">Title II / Entitlement</data><data key="node_description">Title II entitlement and benefit data referenced by SSA exchange products.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Domain object; source system linkage is added only when directly documented.</data></node><node id="DW_BI_ORACLE_2016"><data key="node_entity_id">DW_BI_ORACLE_2016</data><data key="node_entity_type">data_warehouse</data><data key="node_canonical_name">SSA BI Oracle Data Warehouse (2016)</data><data key="node_acronym">BI Data Warehouse</data><data key="node_domain">Enterprise Data / Analytics</data><data key="node_description">Historical SSA business-intelligence data warehouse described as an Oracle database exceeding 12 terabytes and supporting strategic decision-making.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">The strategic plan distinguishes this existing warehouse from the new EDW being built. Exact database name and later disposition are not public.</data></node><node id="DW_DCPS"><data key="node_entity_id">DW_DCPS</data><data key="node_entity_type">data_warehouse</data><data key="node_canonical_name">Disability Case Processing System Warehouse</data><data key="node_acronym">DCPS Warehouse</data><data key="node_domain">Disability / Analytics</data><data key="node_description">Non-public data warehouse supporting DCPS reporting/analytics.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-253.</data></node><node id="DW_EDW_2016"><data key="node_entity_id">DW_EDW_2016</data><data key="node_entity_type">data_warehouse</data><data key="node_canonical_name">Enterprise Data Warehouse (2016 modernization platform)</data><data key="node_acronym">EDW</data><data key="node_domain">Enterprise Data / Analytics</data><data key="node_description">Agency-wide decision-support data warehouse modernization platform being built in 2016 with Greenplum and Informatica and fed from a Hadoop data lake.</data><data key="node_observed_status">historically_authorized_to_operate_2016</data><data key="node_observed_as_of">2016-11-16</data><data key="node_confidence">5</data><data key="node_notes">SSA testimony states the platform had received an ATO. This entity is time-scoped to the 2016 modernization architecture and is not automatically equated to any current warehouse or Greenplum deployment.</data></node><node id="ENV_ECBSV_ETE"><data key="node_entity_id">ENV_ECBSV_ETE</data><data key="node_entity_type">test_environment</data><data key="node_canonical_name">eCBSV External Testing Environment</data><data key="node_acronym">ETE</data><data key="node_domain">Identity / SSN Verification / External Testing</data><data key="node_description">SSA-provided non-production environment that allows participating eCBSV clients to perform interface testing of client software against the eCBSV verification service.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Separate test registration returns an ETE OAuth Client ID. SSA says ETE is not for high-volume performance testing. Hosting, platform, and environment topology are not public.</data></node><node id="ENV_SYSTEM_ZERO"><data key="node_entity_id">ENV_SYSTEM_ZERO</data><data key="node_entity_type">test_environment</data><data key="node_canonical_name">System Zero</data><data key="node_acronym">System Zero</data><data key="node_domain">Infrastructure / Test Environment</data><data key="node_description">IWS/LAN test system installed at the National Computer Center for experimentation before deployment to pilot field offices.</data><data key="node_observed_status">historical_testbed_1990s</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">OTA says SSA used System Zero to gain experience with IWS/LAN before deploying to 10 pilot field offices.</data></node><node id="EXT_BFS_US_SECURITIES_ACCESS"><data key="node_entity_id">EXT_BFS_US_SECURITIES_ACCESS</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">United States Securities and Access</data><data key="node_domain">External Partner Data / Treasury Securities</data><data key="node_description">Fiscal Service system of records used to match SSA finder-file SSNs against savings-security ownership for CMA 1304.</data><data key="node_observed_status">observed_current_in_active_cma</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">CMA 1304 cites Fiscal Service SORN .014; this Atlas record does not infer underlying product/database technology.</data></node><node id="EXT_CYBERSCOPE"><data key="node_entity_id">EXT_CYBERSCOPE</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">DHS CyberScope</data><data key="node_acronym">CyberScope</data><data key="node_domain">Enterprise Security / FISMA Reporting</data><data key="node_description">Department of Homeland Security reporting tool used for Inspector General FISMA reporting metrics.</data><data key="node_observed_status">observed_current_external_dependency</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">FY2026 OIG says Federal agencies are required to use DHS CyberScope for IG FISMA metric reporting and that OIG reported SSA maturity assessments there.</data></node><node id="EXT_DHS_ADIS"><data key="node_entity_id">EXT_DHS_ADIS</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">DHS Arrival and Departure Information System</data><data key="node_acronym">ADIS</data><data key="node_domain">External Data / Travel / Identity</data><data key="node_description">Department of Homeland Security electronic repository containing U.S. entry and exit information for citizens and non-citizens, fed by multiple DHS components and the Department of State.</data><data key="node_observed_status">observed_current_external_source</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled as an external repository based on current SSA POMS. The Atlas does not infer ADIS internal DHS architecture.</data></node><node id="EXT_FED_DATA_CATALOG"><data key="node_entity_id">EXT_FED_DATA_CATALOG</data><data key="node_entity_type">external_platform</data><data key="node_canonical_name">Federal Data Catalog (Data.gov)</data><data key="node_acronym">Federal Data Catalog</data><data key="node_domain">External Data Governance / Public Catalog</data><data key="node_description">Federal public data catalog used to browse, search, and filter SSA’s comprehensive data inventory and cataloged public data assets.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">External federal catalog/publication layer; does not imply the catalog hosts SSA operational source data.</data></node><node id="EXT_HHS_OIG_LEIE"><data key="node_entity_id">EXT_HHS_OIG_LEIE</data><data key="node_entity_type">external_data_source</data><data key="node_canonical_name">HHS OIG List of Excluded Individuals and Entities</data><data key="node_acronym">LEIE</data><data key="node_domain">External Partner Data / Program Integrity / Medical Providers</data><data key="node_description">HHS OIG exclusion list used by SSA disability records to identify medical examiners or providers whose evidence may not be considered.</data><data key="node_observed_status">observed_current_source</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">eDIB SORN explicitly identifies LEIE as a source for provider exclusion indicators.</data></node><node id="EXT_MA_DTA_CONNECT"><data key="node_entity_id">EXT_MA_DTA_CONNECT</data><data key="node_entity_type">external_application</data><data key="node_canonical_name">Massachusetts DTA Connect</data><data key="node_acronym">DTA Connect</data><data key="node_domain">External Data Exchange / State Records</data><data key="node_description">Massachusetts Department of Transitional Assistance portal through which authorized SSA employees have inquiry-only online access to DTA eligibility records under SASRO.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Access is State-approved and limited. Address and phone information are collateral data and must be verified with other sources.</data></node><node id="EXT_STATE_EBR"><data key="node_entity_id">EXT_STATE_EBR</data><data key="node_entity_type">external_system_family</data><data key="node_canonical_name">State Electronic Birth Registration Systems</data><data key="node_domain">External Partners / Vital Records / Enumeration</data><data key="node_description">Collective family of state electronic birth-registration systems into which hospitals, birthing centers, or licensed midwives enter newborn birth-registration information before state transmission to SSA under EAB.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Represents heterogeneous state-owned systems as a logical system family. No common vendor, protocol, or platform is inferred.</data></node><node id="EXT_TNEV_GRAMMAR_DB"><data key="node_entity_id">EXT_TNEV_GRAMMAR_DB</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">TNEV Telecommunications Vendor Alphanumeric Grammar Database</data><data key="node_acronym">TNEV Grammar Database</data><data key="node_domain">Customer Service / Speech Recognition / External Vendor</data><data key="node_description">Standard alphanumeric grammar database used by SSA’s telecommunications vendor to match a spoken IRES user ID in the TNEV automated application.</data><data key="node_observed_status">current_documented_external_dependency</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">PIA identifies a 2.8 trillion grammar database but does not name the vendor, product, hosting environment, or persistence implementation.</data></node><node id="EXT_WRAPS"><data key="node_entity_id">EXT_WRAPS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Worldwide Refugee Admission Processing System</data><data key="node_acronym">WRAPS</data><data key="node_domain">Identity / Immigration / Legacy Verification</data><data key="node_description">External refugee-admission processing system formerly used by SSA through a fax-verification process for refugee status.</data><data key="node_observed_status">retired_verification_process_with_residual_ssnap_workflow</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says SSA no longer uses the WRAPS fax verification process, but WRAPS questions and workaround functionality may still appear in SSNAP until removed.</data></node><node id="EX_AFI_FI"><data key="node_entity_id">EX_AFI_FI</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">AFI Financial Institution Account Verification Exchange</data><data key="node_acronym">AFI FI Exchange</data><data key="node_domain">External Exchange / Title XVI</data><data key="node_description">Electronic request/response exchange used to obtain bank-account balance information from participating financial institutions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes">Modeled from POMS electronic AFI request/response procedures; nonparticipating or nonresponsive institutions can require alternative/paper verification.</data></node><node id="EX_BEER"><data key="node_entity_id">EX_BEER</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Beneficiary Earnings Exchange Record</data><data key="node_acronym">BEER</data><data key="node_domain">External Data Exchange</data><data key="node_description">Batch exchange providing earnings data to states.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_BENDEX"><data key="node_entity_id">EX_BENDEX</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Beneficiary &amp; Earnings Data Exchange</data><data key="node_acronym">BENDEX</data><data key="node_domain">External Data Exchange</data><data key="node_description">Batch exchange providing Title II and earnings data to state agencies.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_CAWR"><data key="node_entity_id">EX_CAWR</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Combined Annual Wage Reporting</data><data key="node_acronym">CAWR</data><data key="node_domain">External Data Exchange</data><data key="node_description">SSA/IRS program and data exchange for reconciling employer wage reports with federal tax reports.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_CMA1003_DOL_BLC"><data key="node_entity_id">EX_CMA1003_DOL_BLC</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">DOL Black Lung Part C Benefit Payments Match</data><data key="node_acronym">CMA 1003</data><data key="node_domain">Program Integrity / Disability</data><data key="node_description">SSA uses DOL Part C Black Lung benefit data to verify disability benefit amounts.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1004_DOD_RET"><data key="node_entity_id">EX_CMA1004_DOD_RET</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">DoD Military Retirement Match</data><data key="node_acronym">CMA 1004</data><data key="node_domain">Title XVI / SVB / External Data Exchange</data><data key="node_description">SSA uses military retirement and survivor payment data to determine SSI and SVB eligibility and benefit payment amounts.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1005_OPM_CIVIL"><data key="node_entity_id">EX_CMA1005_OPM_CIVIL</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">OPM Civil Service Pension Match</data><data key="node_acronym">CMA 1005</data><data key="node_domain">External Data Exchange / SSI / SVB</data><data key="node_description">Active SSA-OPM computer match in which OPM civil-service pension data support SSA eligibility and payment-accuracy determinations, including SSI and SVB.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA matching catalog lists CMA 1005 active; agreement-specific purposes are retained without inferring an implementation interface.</data></node><node id="EX_CMA1006_RRB_CHICO"><data key="node_entity_id">EX_CMA1006_RRB_CHICO</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">RRB Combined Health Insurance Check Writing Match</data><data key="node_acronym">CMA 1006 / CHICO</data><data key="node_domain">Title XVI / SVB / External Data Exchange</data><data key="node_description">SSA uses RRB CHICO information to verify SSI and SVB eligibility and benefit payments.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1007_RRB_WAGE_BEN"><data key="node_entity_id">EX_CMA1007_RRB_WAGE_BEN</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">RRB/SSA Wage and Benefit Match</data><data key="node_acronym">CMA 1007</data><data key="node_domain">External Data Exchange / Railroad Retirement</data><data key="node_description">SSA and RRB exchange wage and benefit data under a consolidated match used by RRB to administer Railroad Retirement Act benefits.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1010_DHS_NONCIT"><data key="node_entity_id">EX_CMA1010_DHS_NONCIT</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">DHS Noncitizens Suspension and Recovery Match</data><data key="node_acronym">CMA 1010</data><data key="node_domain">Title II / Title XVI / Program Integrity</data><data key="node_description">SSA uses DHS data to identify noncitizens potentially ineligible for SSI or RSDI because of absence or removal from the United States.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1012_CNCS_SSN"><data key="node_entity_id">EX_CMA1012_CNCS_SSN</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">CNCS/AmeriCorps SSN and Citizenship Verification Match</data><data key="node_acronym">CMA 1012</data><data key="node_domain">Identity / External Data Exchange</data><data key="node_description">SSA verifies SSNs and returns recorded citizenship status and a death indicator for approved national-service applicants or award recipients.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1015_DOL_BLB"><data key="node_entity_id">EX_CMA1015_DOL_BLB</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">DOL Black Lung Part B Data Match</data><data key="node_acronym">CMA 1015</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">SSA uses DOL Part B data to verify that recipients receive the correct SSI payment amount.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1016_IRS_DISFLA"><data key="node_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">IRS DIFSLA Match</data><data key="node_acronym">CMA 1016 / DIFSLA</data><data key="node_domain">Title XVI / External Data Exchange</data><data key="node_description">Current SSA/IRS CMA 1016 DIFSLA match uses IRS return information from IRMF to verify eligibility for, and the correct amount of, Title XVI SSI and federally administered supplementary payments.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current signed CMA 1016 is effective 2026-01-01 through 2027-07-01. Prior Atlas description included Medicare; the current signed agreement scopes this match to Title XVI SSI/federally administered supplementary payments.</data></node><node id="EX_CMA1030_VA_INCOME_DEP"><data key="node_entity_id">EX_CMA1030_VA_INCOME_DEP</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">VA Income Dependent Extract Match</data><data key="node_acronym">CMA 1030</data><data key="node_domain">External Data Exchange / Veterans</data><data key="node_description">SSA verifies VA-provided SSNs and supplies SSA benefit data that VA uses to verify benefit payment amounts.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1038_BFS_SAVINGS"><data key="node_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Fiscal Service Savings Bond Match</data><data key="node_acronym">CMA 1038</data><data key="node_domain">Title XVI / Assets / External Data Exchange</data><data key="node_description">SSA uses Fiscal Service savings-security ownership data to verify SSI eligibility and payment amounts where ownership was unreported or incorrectly reported.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1045_OPM_EARN"><data key="node_entity_id">EX_CMA1045_OPM_EARN</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">OPM Earnings-Limit Match</data><data key="node_acronym">CMA 1045</data><data key="node_domain">External Data Exchange / Earnings</data><data key="node_description">SSA-OPM computer match scheduled to begin October 20, 2026, under which SSA will verify OPM-submitted identifiers and disclose matched wage and self-employment information from the Enumeration and MEF record systems for OPM earnings-limit determinations.</data><data key="node_observed_status">scheduled_to_begin_2026-10-20</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The August 19, 2026 Federal Register notice states the match begins October 20, 2026 absent comments requiring republication. As of October 6 it is not yet current operation; transport mechanism and execution cadence are not publicly stated.</data></node><node id="EX_CMA1050_VA_EARNINGS"><data key="node_entity_id">EX_CMA1050_VA_EARNINGS</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">VA Income-Dependent Beneficiary Earnings Match</data><data key="node_acronym">CMA 1050</data><data key="node_domain">Earnings / External Data Exchange / Veterans</data><data key="node_description">VA sends identifying data to SSA; SSA verifies SSNs using Enumeration and discloses matched wage/self-employment earnings from MEF for VA needs-based benefit administration.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1051_ED_SSN_CIT"><data key="node_entity_id">EX_CMA1051_ED_SSN_CIT</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Department of Education SSN and Citizenship Verification Match</data><data key="node_acronym">CMA 1051</data><data key="node_domain">Identity / External Data Exchange / Education</data><data key="node_description">Department of Education uses SSA information to verify SSNs and citizenship status for Title IV financial-aid applicants.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1052_VHA_EARNINGS"><data key="node_entity_id">EX_CMA1052_VHA_EARNINGS</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">VA Earnings Information Match</data><data key="node_acronym">CMA 1052</data><data key="node_domain">Earnings / External Data Exchange / Veterans</data><data key="node_description">SSA discloses return information to Veterans Health Administration to verify earnings supplied by medical-care applicants.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1061_HUD_INCOME"><data key="node_entity_id">EX_CMA1061_HUD_INCOME</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">HUD Tenant Reported Income Match</data><data key="node_acronym">CMA 1061</data><data key="node_domain">External Data Exchange / Income Verification</data><data key="node_description">HUD uses SSA Title II, Title XVI, and Title VII information to verify eligibility for HUD rental-assistance programs.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1071_OPM_BENEFIT"><data key="node_entity_id">EX_CMA1071_OPM_BENEFIT</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">OPM Benefit Data Match</data><data key="node_acronym">CMA 1071</data><data key="node_domain">External Data Exchange / Federal Retirement</data><data key="node_description">SSA-OPM computer match scheduled to begin October 27, 2026. OPM submits name, SSN, date of birth and an SVES indicator; SSA verifies the SSN using Enumeration and, on a match, returns Title II beneficiary status and associated MBR benefit information through SVES.</data><data key="node_observed_status">scheduled_to_begin_2026-10-27</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Corrected to Title II only. The August 6, 2026 Federal Register notice states the re-established match begins October 27, 2026 absent comments requiring republication; no Title XVI or earnings return is described.</data></node><node id="EX_CMA1100_ED_MINE"><data key="node_entity_id">EX_CMA1100_ED_MINE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Department of Education MINE Disability Data Match</data><data key="node_acronym">CMA 1100 / MINE</data><data key="node_domain">Disability / External Data Exchange / Education</data><data key="node_description">Department of Education uses SSA Medical Improvement Not Expected disability information to identify people with permanent disabilities who may qualify for loan discharge.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1304_BFS_PARTD"><data key="node_entity_id">EX_CMA1304_BFS_PARTD</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Fiscal Service Medicare Part D Prescription Drug Subsidy Match</data><data key="node_acronym">CMA 1304</data><data key="node_domain">Medicare / External Data Exchange</data><data key="node_description">SSA sends MDB-derived finder files and uses Fiscal Service savings-security ownership data to verify Extra Help eligibility self-certification.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1305_IRS_PARTD"><data key="node_entity_id">EX_CMA1305_IRS_PARTD</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">IRS Medicare Part D Prescription Drug Subsidy Match</data><data key="node_acronym">CMA 1305</data><data key="node_domain">Medicare / External Data Exchange</data><data key="node_description">SSA uses specified IRS return data to verify self-certified eligibility for Medicare Part D prescription drug subsidy assistance.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1306_OCSE_PARTD"><data key="node_entity_id">EX_CMA1306_OCSE_PARTD</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">OCSE Medicare Part D Prescription Drug Subsidy Match</data><data key="node_acronym">CMA 1306</data><data key="node_domain">Medicare / External Data Exchange</data><data key="node_description">SSA uses OCSE quarterly wage, new-hire, and unemployment data to verify self-certified eligibility for Medicare Part D subsidy assistance.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1307_OPM_PARTD"><data key="node_entity_id">EX_CMA1307_OPM_PARTD</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">OPM Medicare Part D Prescription Drug Subsidy Match</data><data key="node_acronym">CMA 1307</data><data key="node_domain">Medicare / External Data Exchange</data><data key="node_description">SSA uses OPM civil-service benefit and payment data to verify self-certified eligibility for Medicare Part D subsidy assistance.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1308_RRB_PARTD"><data key="node_entity_id">EX_CMA1308_RRB_PARTD</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">RRB Medicare Part D Prescription Drug Subsidy Match</data><data key="node_acronym">CMA 1308</data><data key="node_domain">Medicare / External Data Exchange</data><data key="node_description">SSA uses RRB annuity payment information to verify self-certified eligibility for Medicare Part D subsidy assistance.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA1310_IRS_PREMIUM"><data key="node_entity_id">EX_CMA1310_IRS_PREMIUM</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">IRS Medicare Parts B and D Premium Subsidy Match</data><data key="node_acronym">CMA 1310</data><data key="node_domain">Medicare / External Data Exchange</data><data key="node_description">SSA uses IRS return information to establish correct Medicare Parts B and D premium subsidy adjustments.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Computer Matching Programs page lists the corresponding CMA as active; purpose is documented in the 2026 Annual Matching Activity Report.</data></node><node id="EX_CMA6000_STATE_LEVEL"><data key="node_entity_id">EX_CMA6000_STATE_LEVEL</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">State-Level Federally Funded Benefit Program Match</data><data key="node_acronym">CMA 6000</data><data key="node_domain">External Data Exchange / States</data><data key="node_description">Active state-level model matching program under which SSA can verify SSNs and disclose specified SSA records for administration of federally funded benefit programs.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current active catalog status is authoritative as of 2026-10-04. The static model agreement has an earlier stated term; no undocumented extension mechanism is inferred.</data></node><node id="EX_CMA6003_STATE_AGENCY"><data key="node_entity_id">EX_CMA6003_STATE_AGENCY</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">State Agency Federally Funded Benefit Program Match</data><data key="node_acronym">CMA 6003</data><data key="node_domain">External Data Exchange / States</data><data key="node_description">Active state-agency model matching program under which SSA can verify SSNs and disclose specified SSA records for administration of federally funded benefit programs.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current active catalog status is authoritative as of 2026-10-04. Physical exchange topology varies by participating state agency and is not inferred.</data></node><node id="EX_CMA6004_TRIBAL"><data key="node_entity_id">EX_CMA6004_TRIBAL</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Tribal Entity Federally Funded Benefit Program Match</data><data key="node_acronym">CMA 6004</data><data key="node_domain">External Data Exchange / Tribal</data><data key="node_description">Active tribal-entity model matching program under which SSA can verify SSNs and disclose specified SSA records for administration of federally funded benefit programs.</data><data key="node_observed_status">active_matching_program</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current active catalog status is authoritative as of 2026-10-04. Physical exchange topology is not inferred.</data></node><node id="EX_CMS_ACA_1097"><data key="node_entity_id">EX_CMS_ACA_1097</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">CMS Affordable Care Act Eligibility Verification Match</data><data key="node_acronym">CMA 1097</data><data key="node_domain">External Data Exchange / CMS</data><data key="node_description">Real-time and daily batch exchange supporting Affordable Care Act marketplace eligibility, renewal, redetermination and exemption verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-09</data><data key="node_confidence">5</data><data key="node_notes">Active through September 8, 2027 absent modification/termination.</data></node><node id="EX_CMS_AFES_1094"><data key="node_entity_id">EX_CMS_AFES_1094</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">CMS Medicare Non-Utilization Match for Fraud Analytics</data><data key="node_acronym">CMA 1094</data><data key="node_domain">External Data Exchange / Program Integrity</data><data key="node_description">Active SSA-CMS computer match for Title II beneficiaries age 90+; non-utilization responses support continued-eligibility review and fraud analytics.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA Computer Match 1094 / CMS Computer Match 2024-09.</data></node><node id="EX_CMS_NURSING_1076"><data key="node_entity_id">EX_CMS_NURSING_1076</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">CMS Title XIX Facility Admission and Discharge Match</data><data key="node_acronym">CMA 1076</data><data key="node_domain">External Data Exchange / CMS</data><data key="node_description">Monthly CMS facility match used to identify unreported institutional admissions/discharges affecting SSI payment and living-arrangement rules.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">CMA 1076 is on SSA's active-match list; current POMS documents the D8 workflow.</data></node><node id="EX_CREDIT_BUREAU_REPORTING"><data key="node_entity_id">EX_CREDIT_BUREAU_REPORTING</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Debt Reporting to Credit Repositories</data><data key="node_acronym">Credit Bureau Reporting</data><data key="node_domain">External Data Exchange</data><data key="node_description">Automated reporting and monthly updating of qualifying delinquent SSA debt information to national credit repositories.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_DAS_TREASURY"><data key="node_entity_id">EX_DAS_TREASURY</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Daily Advice of Status</data><data key="node_acronym">DAS</data><data key="node_domain">External Exchange / Treasury / Payments</data><data key="node_description">Electronic Treasury status transmission reporting SSA stop-code processing and whether a check was or was not paid.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS page defines the transmission; transport technology is not specified.</data></node><node id="EX_DTA"><data key="node_entity_id">EX_DTA</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Direct Terminal Access</data><data key="node_acronym">DTA</data><data key="node_domain">External Data Exchange</data><data key="node_description">Real-time access by an authorized Federal agency to certain SSA electronic databases for agreed beneficiary data when other exchange methods do not suffice.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-17</data><data key="node_confidence">5</data><data key="node_notes">Access requires legal, security, and where applicable financial agreements plus approved user access controls.</data></node><node id="EX_EAB"><data key="node_entity_id">EX_EAB</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Enumeration at Birth</data><data key="node_acronym">EAB</data><data key="node_domain">External Data Exchange</data><data key="node_description">State birth-registration process used to request an SSN for a newborn; states can transmit via MFT.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_EAE"><data key="node_entity_id">EX_EAE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Enumeration at Entry</data><data key="node_acronym">EAE</data><data key="node_domain">External Data Exchange</data><data key="node_description">Automated immigrant enumeration exchange in which DoS collects data and DHS/USCIS transmits enumeration data to SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_EBE"><data key="node_entity_id">EX_EBE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Enumeration Beyond Entry</data><data key="node_acronym">EBE</data><data key="node_domain">External Data Exchange</data><data key="node_description">Automated USCIS-to-SSA enumeration exchange for approved I-765, I-485 and N-400 applications requesting an SSN card.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_EIWO"><data key="node_entity_id">EX_EIWO</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Electronic Income Withholding Order Exchange</data><data key="node_acronym">e-IWO</data><data key="node_domain">External Data Exchange / Garnishment</data><data key="node_description">Electronic-file process through which participating states, courts and other garnishing entities send income-withholding orders to SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="EX_EMILRECS"><data key="node_entity_id">EX_EMILRECS</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">eMilrecs</data><data key="node_acronym">eMilrecs</data><data key="node_domain">External Data Exchange / Military Records</data><data key="node_description">SSA/NARA online system for requesting, tracking and receiving documentary evidence of military service.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Interactive authenticated exchange; public policy does not expose transport/API details.</data></node><node id="EX_ENR"><data key="node_entity_id">EX_ENR</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Automated Enrollment</data><data key="node_acronym">ENR</data><data key="node_domain">External Exchange / Direct Deposit</data><data key="node_description">Electronic enrollment process through which participating U.S. financial institutions transmit direct-deposit enrollment information to SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Also called Quick$tart/Quick Start in POMS; financial-institution participation is voluntary.</data></node><node id="EX_EVERIFY"><data key="node_entity_id">EX_EVERIFY</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">SSA E-Verify</data><data key="node_acronym">E-Verify</data><data key="node_domain">External Data Exchange</data><data key="node_description">DHS-owned E-Verify employment-authorization verification program with SSA operational participation for resolving SSN-record mismatches and recording E-Verify case resolution.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Catalog remains available; underlying metadata is 2017.</data></node><node id="EX_FPLS_DRLIF"><data key="node_entity_id">EX_FPLS_DRLIF</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Direct Request Locator Information File</data><data key="node_acronym">DRLIF</data><data key="node_domain">External Data Exchange / Child Support / Earnings</data><data key="node_description">Daily FPLS exchange in which OCSE submits known-SSN finder records to SSA and receives employer address information for up to ten recent employers over four years plus wage amounts.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-677 covers the combined FPLS DRLIF/ESKARI process. SSA source systems for the returned employer/wage data are not named in that record.</data></node><node id="EX_FPLS_ESKARI"><data key="node_entity_id">EX_FPLS_ESKARI</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Earnings System Keyed Applications for SSN Registration Identification</data><data key="node_acronym">ESKARI</data><data key="node_domain">External Data Exchange / Child Support / Identity</data><data key="node_description">Daily FPLS exchange in which OCSE submits finder records with unknown SSNs to SSA for SSN identification; identified SSNs are then recycled into DRLIF processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-677 covers the combined FPLS DRLIF/ESKARI process. The catalog does not name the SSA identity repository or match utility used by ESKARI.</data></node><node id="EX_FTD_ADIS_QUERY"><data key="node_entity_id">EX_FTD_ADIS_QUERY</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Foreign Travel Data ADIS Direct Query Exchange</data><data key="node_acronym">FTD-ADIS Query</data><data key="node_domain">External Data Exchange / Program Integrity</data><data key="node_description">Direct-query exchange used by SSA Foreign Travel Data application to obtain third-party foreign-travel information from DHS ADIS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current mode is direct/ad hoc query access. OIG says SSA is working toward a batch process via a Computer Matching Agreement; that future state is not modeled as current.</data></node><node id="EX_HAVV"><data key="node_entity_id">EX_HAVV</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Help America Vote Verification</data><data key="node_acronym">HAVV</data><data key="node_domain">External Data Exchange</data><data key="node_description">Verification service for voter registration using last four SSN digits, name and DOB, including alive/deceased match status.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_HRS_LINKAGE"><data key="node_entity_id">EX_HRS_LINKAGE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">SSA-Health and Retirement Study Administrative Record Linkage</data><data key="node_acronym">SSA-HRS Linkage</data><data key="node_domain">External Exchanges / Research</data><data key="node_description">Consent-based SSA administrative-record linkage that validates identifying information against Numident and provides matched earnings, disability-application, and benefit extracts to HRS.</data><data key="node_observed_status">documented_ongoing_research_exchange</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">4</data><data key="node_notes">2024 HRS guide documents linkage mechanics and data products; FY2027 SSA budget confirms ongoing HRS support. Current transport protocol and exact 2026 match cadence are not public.</data></node><node id="EX_IBIQ"><data key="node_entity_id">EX_IBIQ</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Interstate Benefit Inquiry</data><data key="node_acronym">IBIQ</data><data key="node_domain">External Data Exchange / State Wage and UI Data</data><data key="node_description">SSA online access to state wage and unemployment records through the Interstate Connection Network.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS uses IBIQ as wage and unemployment-benefit evidence.</data></node><node id="EX_IEDR"><data key="node_entity_id">EX_IEDR</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Internet-Electronic Death Registration</data><data key="node_acronym">I-EDR</data><data key="node_domain">External Data Exchange</data><data key="node_description">Web application allowing state vital statistics offices to verify decedent SSNs and notify SSA of deaths.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_ISVER"><data key="node_entity_id">EX_ISVER</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Department of State Online SSN Verification Exchange</data><data key="node_acronym">ISVER</data><data key="node_domain">External Data Exchange</data><data key="node_description">Real-time SSN verification service for Department of State passport adjudication.</data><data key="node_observed_status">cataloged_legacy_metadata</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Catalog remains available in 2026, but underlying dataset metadata was last updated in 2018.</data></node><node id="EX_LIS"><data key="node_entity_id">EX_LIS</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Low-Income Subsidy Data Exchange</data><data key="node_acronym">LIS</data><data key="node_domain">External Data Exchange</data><data key="node_description">Exchange providing LIS information to states/DC as leads for Medicare Savings Program outreach.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_MEDICARE1144"><data key="node_entity_id">EX_MEDICARE1144</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Medicare 1144 Outreach Data Exchange</data><data key="node_acronym">Medicare 1144</data><data key="node_domain">External Data Exchange / Medicare</data><data key="node_description">Batch exchange that provides approved State agencies lists of people on SSA rolls who may be eligible for specified Medicare/Medicaid cost-sharing or subsidy assistance under Section 1144 outreach.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">POMS expressly calls Medicare 1144 a batch system. Exact transport, file format, receiving State platform, and internal SSA staging components are not publicly established.</data></node><node id="EX_MEF_SSR_MATCH"><data key="node_entity_id">EX_MEF_SSR_MATCH</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Master Earnings File / Supplemental Security Record Match</data><data key="node_acronym">MEF/SSR Match</data><data key="node_domain">External/Internal Match</data><data key="node_description">Semiannual match identifying discrepant earnings and self-employment income for SSI-eligible persons.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_MNUP_CMS_NONUTIL"><data key="node_entity_id">EX_MNUP_CMS_NONUTIL</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">CMS–SSA Medicare Non-Utilization Data Exchange</data><data key="node_acronym">MNUP CMS Exchange</data><data key="node_domain">External Exchange / Program Integrity</data><data key="node_description">Data exchange in which CMS identifies Medicare enrollees with no Part A or Part B use for three or more years for SSA MNUP selection and review.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public policy establishes direction and purpose but not file/API format, transport, cadence, or staging persistence.</data></node><node id="EX_MSP_STATE_REFERRAL"><data key="node_entity_id">EX_MSP_STATE_REFERRAL</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Extra Help to Medicare Savings Program State Referral</data><data key="node_acronym">MSP State Referral</data><data key="node_domain">External Data Exchange / Medicare</data><data key="node_description">SSA transmission of Extra Help application decision data to the appropriate State Medicaid agency to begin the MSP process.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_NUMIDENT_DNP_VERIFY"><data key="node_entity_id">EX_NUMIDENT_DNP_VERIFY</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Numident Verification Through Do Not Pay</data><data key="node_acronym">Numident-DNP Verification</data><data key="node_domain">Identity / External Verification / Payment Integrity</data><data key="node_description">Treasury-designated use of SSA Numident through the Do Not Pay Working System to verify name, SSN, and date of birth for eligible health or income-maintenance program payments and awards.</data><data key="node_observed_status">final_designation_effective_product_availability_varies</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Final designation effective April 10, 2026. September 2026 Treasury catalog lists Payment Verification availability for select programs, Do Not Pay Connect coming soon for select programs, and state usage coming soon through PARIS.</data></node><node id="EX_OCSE_NDNH_1074"><data key="node_entity_id">EX_OCSE_NDNH_1074</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">OCSE NDNH Online Query / CMA 1074</data><data key="node_acronym">CMA 1074 Online Query</data><data key="node_domain">External Data Exchange / Earnings</data><data key="node_description">Active OCSE-SSA matching arrangement supporting online NDNH query access for authorized SSA uses including disability and Ticket-to-Work administration.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA current computer-matching list shows CMA 1074 active; operational query behavior is documented in POMS.</data></node><node id="EX_OCSE_NDNH_1098"><data key="node_entity_id">EX_OCSE_NDNH_1098</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Title II NDNH Quarterly Match</data><data key="node_acronym">CMA 1098</data><data key="node_domain">External Data Exchange / Title II Disability</data><data key="node_description">Active OCSE-SSA computer match using NDNH quarterly wage/unemployment information for Title II Disability Insurance eligibility, continuing entitlement, payment accuracy and overpayment prevention.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA current computer-matching list shows CMA 1098 active.</data></node><node id="EX_OCSE_PENDING"><data key="node_entity_id">EX_OCSE_PENDING</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">OCSE Pending File Match</data><data key="node_acronym">OCSE Pending</data><data key="node_domain">Title II / External Data Exchange</data><data key="node_description">Daily match between SSA's MCS Title II pending file and OCSE's Federal Case Registry, releasing matched Title II information to OCSE.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Data.gov identifier US-GOV-SSA-678.</data></node><node id="EX_OCSE_SSI_WAGE_ALERT"><data key="node_entity_id">EX_OCSE_SSI_WAGE_ALERT</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">OCSE State Wage Alerts</data><data key="node_acronym">OCSE Wage Alert</data><data key="node_domain">External Data Exchange</data><data key="node_description">Quarterly match identifying unreported wage/unemployment data for SSI overpayment detection.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_OIG_NIBRS"><data key="node_entity_id">EX_OIG_NIBRS</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">SSA OIG Automated NIBRS Submission</data><data key="node_acronym">NIBRS</data><data key="node_domain">External Data Exchange / Law Enforcement</data><data key="node_description">Automated process that pulls qualifying data from OIG's Investigative Case Management System and submits it to the FBI under NIBRS protocols.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes">SSA OIG states automated submissions began in FY2026.</data></node><node id="EX_OPM_EARNINGS"><data key="node_entity_id">EX_OPM_EARNINGS</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Office of Personnel Management Earnings Exchange</data><data key="node_acronym">OPM Earnings</data><data key="node_domain">External Data Exchange</data><data key="node_description">Annual OPM-to-SSA earnings file matched against MEF and EIF, with SSA data used by OPM for continued-benefit eligibility.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_PIE"><data key="node_entity_id">EX_PIE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Payroll Information Exchange</data><data key="node_acronym">PIE</data><data key="node_domain">External Data Exchange</data><data key="node_description">Automated exchange through which SSA requests and receives wage and employment information from payroll data providers.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA reported in February 2026 that PIE reached full-scale monthly exchanges in September 2025.</data></node><node id="EX_QQ"><data key="node_entity_id">EX_QQ</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Qualifying Quarters</data><data key="node_acronym">QQ</data><data key="node_domain">External Data Exchange</data><data key="node_description">Exchange showing quarters-of-coverage information and railroad service months.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_SASRO"><data key="node_entity_id">EX_SASRO</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">SSA Access to State Records Online</data><data key="node_acronym">SASRO</data><data key="node_domain">External Data Exchange / State Records</data><data key="node_description">Single-query online access by SSA employees to state records used for SSN assignment and Title II/Title XVI eligibility and payment verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current state agreement model and 2025 POMS corroborate operation.</data></node><node id="EX_SCHIPI"><data key="node_entity_id">EX_SCHIPI</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">State Children's Health Insurance Program - Internet</data><data key="node_acronym">SCHIP-I</data><data key="node_domain">External Data Exchange</data><data key="node_description">Web application for real-time citizenship verification by state agencies.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current Data.gov inventory US-GOV-SSA-603 documents SCHIP routing through SVES and EVS/Numident citizenship verification.</data></node><node id="EX_SDX"><data key="node_entity_id">EX_SDX</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">State Data Exchange</data><data key="node_acronym">SDX</data><data key="node_domain">External Data Exchange</data><data key="node_description">Batch exchange providing Title XVI data to states administering income/health maintenance programs.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_SOLQ"><data key="node_entity_id">EX_SOLQ</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">State Online Query / State Online Query-Internet</data><data key="node_acronym">SOLQ/SOLQ-I</data><data key="node_domain">External Data Exchange</data><data key="node_description">Real-time state access to SSN verification and Title II/Title XVI information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current Data.gov inventory US-GOV-SSA-671 describes SOLQ as real-time state access to SSN verification and Title II/Title XVI data.</data></node><node id="EX_SSA_VA_PAYEE_MISUSE"><data key="node_entity_id">EX_SSA_VA_PAYEE_MISUSE</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">SSA / VA Representative Payee-Fiduciary Misuse Exchange</data><data key="node_domain">External Data Exchange</data><data key="node_description">Case-driven two-way information exchange when the same person serves as an SSA representative payee and VA fiduciary and misuse or improper use is investigated or found.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2025-05-14</data><data key="node_confidence">4</data><data key="node_notes">POMS remains current online with a 2025 batch run; communication is case-driven rather than a documented automated interface.</data></node><node id="EX_SSI_IRS_1099"><data key="node_entity_id">EX_SSI_IRS_1099</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">SSI / IRS 1099 Exchange</data><data key="node_acronym">SSI/IRS 1099</data><data key="node_domain">External Data Exchange</data><data key="node_description">SSA sends a Title XVI finder file to IRS; IRS returns 1099 data used to verify SSI eligibility and payment amount.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_SSOLV"><data key="node_entity_id">EX_SSOLV</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Social Security Online Verification</data><data key="node_acronym">SSOLV</data><data key="node_domain">External Data Exchange</data><data key="node_description">Real-time SSN verification service for state motor-vehicle agencies routed through AAMVA/AAMVAnet.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Operational POMS is from 2020; back-end metadata is 2016.</data></node><node id="EX_STATE_ABLE_MONTHLY"><data key="node_entity_id">EX_STATE_ABLE_MONTHLY</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">State ABLE Program Monthly Data Exchange</data><data key="node_acronym">ABLE Monthly Exchange</data><data key="node_domain">Title XVI / Resources / External Data Exchange</data><data key="node_description">Monthly inbound State ABLE-program reporting used by SSA to identify new ABLE accounts and update qualifying account information in the SSI Claims System.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS establishes monthly cadence and system behavior but not file format, transport protocol, or State-by-State implementation details.</data></node><node id="EX_STATE_BUYIN"><data key="node_entity_id">EX_STATE_BUYIN</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">State Medicare Buy-In Automated Exchange</data><data key="node_acronym">State Buy-In Exchange</data><data key="node_domain">External Data Exchange / Medicare</data><data key="node_description">Daily automated data exchanges among States, SSA, and CMS supporting the Medicare State buy-in program.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-15</data><data key="node_confidence">5</data><data key="node_notes">POMS documents the automated exchange but does not publish protocol, file layout, or middleware.</data></node><node id="EX_SVES"><data key="node_entity_id">EX_SVES</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">State Verification &amp; Exchange System</data><data key="node_acronym">SVES</data><data key="node_domain">External Data Exchange</data><data key="node_description">Batch query system for SSN verification and Title II/Title XVI data; can request information from other exchange systems.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Data Exchange pages continue to list SVES as a batch exchange. The July 2023 manual documents native verification against Numident/MBR/SSR and non-native routing to other exchanges.</data></node><node id="EX_T16_OPM"><data key="node_entity_id">EX_T16_OPM</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Title 16 / Office of Personnel Management Interface</data><data key="node_acronym">T16/OPM</data><data key="node_domain">External Data Exchange</data><data key="node_description">Monthly OPM Civil Service benefit/payment exchange used to verify SSI/SVB eligibility factors.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="EX_TDEX"><data key="node_entity_id">EX_TDEX</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Totalization Data Exchange</data><data key="node_acronym">TDEX</data><data key="node_domain">External Data Exchange / International</data><data key="node_description">Exchange with foreign totalization partners used to identify deaths of U.S. beneficiaries residing abroad.</data><data key="node_observed_status">current_function_corroborated</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Detailed TDEX metadata is from 2017; current GSO independently confirms foreign death data exchange for totalization partner countries.</data></node><node id="EX_TREASURY_OACT_MONTHLY_TRUST_DATA"><data key="node_entity_id">EX_TREASURY_OACT_MONTHLY_TRUST_DATA</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Treasury Monthly Trust Fund Financial and Investment Data</data><data key="node_acronym">Treasury Trust Fund Monthly Data</data><data key="node_domain">Actuarial; Trust Funds; External Exchange</data><data key="node_description">Monthly data flow from the Department of the Treasury to SSA covering Social Security trust-fund financial operations and investment data.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">OACT explicitly states Treasury manages the funds and provides SSA monthly data; transport and staging implementation are not publicly identified.</data></node><node id="EX_UIQ"><data key="node_entity_id">EX_UIQ</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Unemployment Insurance Query</data><data key="node_acronym">UIQ</data><data key="node_domain">External Data Exchange</data><data key="node_description">Real-time access for state UI agencies to SSN verification and Title II payment data via DOL ICON Hub.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Current Data.gov inventory US-GOV-SSA-672, last updated September 29, 2026, describes real-time State UI access to SSN verification and Title II payment data through the DOL ICON Hub.</data></node><node id="EX_US_ROMANIA_TOTALIZATION"><data key="node_entity_id">EX_US_ROMANIA_TOTALIZATION</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">U.S.-Romania Totalization Claims and Liaison Exchange</data><data key="node_domain">External Data Exchange / International</data><data key="node_description">Two-way administrative exchange supporting U.S.-Romania Totalization claims, coverage information, evidence and liaison requests.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">The public evidence validates business artifacts and partner roles but not the network protocol, gateway or transport mechanism.</data></node><node id="EX_VA_CMA1008"><data key="node_entity_id">EX_VA_CMA1008</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">VA Compensation and Pension Payment Match</data><data key="node_acronym">CMA 1008</data><data key="node_domain">External Data Exchange / VA</data><data key="node_description">Monthly encrypted batch match of VA compensation and pension payment data for SSI/SVB payment accuracy and Medicare outreach/Extra Help.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-05-11</data><data key="node_confidence">5</data><data key="node_notes">Active for 18 months from May 11, 2026 unless renewed/terminated.</data></node><node id="EX_VA_VAPT"><data key="node_entity_id">EX_VA_VAPT</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">VA 100 Percent Permanent and Total Disability Rating Exchange</data><data key="node_acronym">VA VAPT Exchange</data><data key="node_domain">External Exchanges / Disability / Identity</data><data key="node_description">Weekly automated exchange through which VA provides SSA information on veterans with 100 percent permanent and total disability compensation ratings.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA verifies SSN and other supplied identity attributes against Numident before storing verified SSNs in PERSON/ICDB.</data></node><node id="FAC_MATPSC"><data key="node_entity_id">FAC_MATPSC</data><data key="node_entity_type">facility</data><data key="node_canonical_name">Mid-Atlantic Program Service Center</data><data key="node_acronym">MATPSC</data><data key="node_domain">Payments / Remittance Processing</data><data key="node_description">SSA national remittance processing site for field-office and debtor programmatic debt payments that require physical forwarding and deposit processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS identifies MATPSC as the national remittance processing site.</data></node><node id="FAC_NCC"><data key="node_entity_id">FAC_NCC</data><data key="node_entity_type">facility</data><data key="node_canonical_name">National Computer Center</data><data key="node_acronym">NCC</data><data key="node_domain">Infrastructure / Legacy Data Center</data><data key="node_description">Legacy SSA data center in Woodlawn, Maryland, that the National Support Center was built to replace. A September 2026 SSA OIG EAB report also uses the term 'National Computer Center' as the SSA destination for state birth-information transmissions through secure electronic interfaces.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">4</data><data key="node_notes">OIG documented migration from NCC to NSC in 2016; this run does not assign a precise retirement date. 2026 OIG current-reference terminology creates a naming/physical-facility ambiguity because earlier OIG evidence said the National Support Center was built to replace the aging NCC. This update records the current reference without asserting that the legacy physical facility remains the hosting site.</data></node><node id="FAC_NSC"><data key="node_entity_id">FAC_NSC</data><data key="node_entity_type">facility</data><data key="node_canonical_name">National Support Center</data><data key="node_acronym">NSC</data><data key="node_domain">Infrastructure / Data Center</data><data key="node_description">SSA data center in Urbana, Maryland, opened as a modern replacement facility for legacy data-center capacity.</data><data key="node_observed_status">observed_current_occupancy</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes">FY2025 financial statements explicitly record benefits from SSA occupancy of NSC.</data></node><node id="FAC_SSC"><data key="node_entity_id">FAC_SSC</data><data key="node_entity_type">facility</data><data key="node_canonical_name">Second Support Center</data><data key="node_acronym">SSC</data><data key="node_domain">Infrastructure / Data Center</data><data key="node_description">SSA second support/data-center facility in North Carolina, historically documented as providing data-computing redundancy.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA current operational-status page says SSC is operating normally. The redundancy role is documented historically and is not assumed unchanged without caveat.</data></node><node id="FEATURE_IAPPEALS_ATTACHMENT_UTILITY"><data key="node_entity_id">FEATURE_IAPPEALS_ATTACHMENT_UTILITY</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">iAppeals Attachment Utility</data><data key="node_acronym">Attachment Utility</data><data key="node_domain">Disability / Evidence / Digital Intake</data><data key="node_description">iAppeals feature that allows Internet users to attach evidence files to an appeal submission; current EDCS policy describes intake and retention handling.</data><data key="node_observed_status">observed_current_workflow_feature</data><data key="node_observed_as_of">2025-12-02</data><data key="node_confidence">5</data><data key="node_notes">Source says up to 10 documents can be submitted through the attachment utility.</data></node><node id="FLAG_EDCS_VAPT38"><data key="node_entity_id">FLAG_EDCS_VAPT38</data><data key="node_entity_type">case_flag</data><data key="node_canonical_name">EDCS Flag 38 Disabled Veteran Rated 100% Permanent and Total</data><data key="node_acronym">Flag 38</data><data key="node_domain">Disability / Electronic Folder</data><data key="node_description">EDCS VAPT case flag attached to matched pending/initiated cases and automatically attached during case creation when SSN exists in the PERSON VAPT segment.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">May also be manually established when claimant provides proof and no system alert exists.</data></node><node id="FMT_EFW2"><data key="node_entity_id">FMT_EFW2</data><data key="node_entity_type">data_format</data><data key="node_canonical_name">Specifications for Filing Forms W-2 Electronically</data><data key="node_acronym">EFW2</data><data key="node_domain">Earnings / Employer</data><data key="node_description">SSA electronic wage-file format for original W-2 submissions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FMT_EFW2C"><data key="node_entity_id">FMT_EFW2C</data><data key="node_entity_type">data_format</data><data key="node_canonical_name">Specifications for Filing Forms W-2c Electronically</data><data key="node_acronym">EFW2C</data><data key="node_domain">Earnings / Employer</data><data key="node_description">SSA electronic wage-file format for corrected W-2c submissions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FMT_SSNVS_FIXED130"><data key="node_entity_id">FMT_SSNVS_FIXED130</data><data key="node_entity_type">data_format</data><data key="node_canonical_name">SSNVS 130-Character Fixed-Width Submission File</data><data key="node_acronym">SSNVS Fixed 130</data><data key="node_domain">Identity Verification / Employer Exchange</data><data key="node_description">Current fixed-width batch input format used to submit up to 250,000 name/SSN records through SSNVS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA requires one 130-character record per request; the file format contains positional fields and a user-control field returned in output.</data></node><node id="FORM_E3759"><data key="node_entity_id">FORM_E3759</data><data key="node_entity_type">form</data><data key="node_canonical_name">Request to Financial Institution for Correct Beneficiary Address</data><data key="node_acronym">E3759</data><data key="node_domain">Title II / Address Development</data><data key="node_description">SSA notice/form sent to the beneficiary's financial institution to request a current mailing address when SSA cannot locate the beneficiary.</data><data key="node_observed_status">observed_current_poms</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS document identifier E3759. A DPS Locate Letter or similar letter may be used instead in the documented workflow.</data></node><node id="FORM_FMS3858"><data key="node_entity_id">FORM_FMS3858</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Claims Document</data><data key="node_acronym">FMS-3858</data><data key="node_domain">Payments / Treasury / Nonreceipt</data><data key="node_description">Claims Document included in the Treasury check claims package.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">No independent SSA application is inferred.</data></node><node id="FORM_FS1133"><data key="node_entity_id">FORM_FS1133</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Claim Against the United States for the Proceeds of a Government Check</data><data key="node_acronym">FS-1133</data><data key="node_domain">Payments / Treasury / Nonreceipt</data><data key="node_description">Treasury claim form completed when a claimant disputes endorsement or receipt of a government check.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA POMS also uses the legacy label FMS-1133.</data></node><node id="FORM_G845"><data key="node_entity_id">FORM_G845</data><data key="node_entity_type">form</data><data key="node_canonical_name">DHS Form G-845 Request for Document Verification</data><data key="node_acronym">G-845</data><data key="node_domain">Identity / Immigration Verification</data><data key="node_description">Manual DHS verification request used when online SAVE cannot be used to verify an alleged lawful-presence status or specified discrepancies/suspect documents require manual verification.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directs a copy of the G-845 and supporting DHS document into the claim folder and establishes follow-up controls.</data></node><node id="FORM_G845_SUPPLEMENT"><data key="node_entity_id">FORM_G845_SUPPLEMENT</data><data key="node_entity_type">form</data><data key="node_canonical_name">Supplement to Form G-845</data><data key="node_acronym">G-845 Supplement</data><data key="node_domain">Identity / Immigration Verification</data><data key="node_description">Supplement used with Form G-845 for specified qualified-alien and other lawful-presence verification situations.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Use is conditional; no separate SSA backend is inferred.</data></node><node id="FORM_HA4608"><data key="node_entity_id">FORM_HA4608</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-4608 Waiver of Your Right to Personal Appearance Before an Administrative Law Judge</data><data key="node_acronym">HA-4608</data><data key="node_domain">Hearings / Appeals / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_HA4631"><data key="node_entity_id">FORM_HA4631</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-4631 Claimant's Recent Medical Treatment</data><data key="node_acronym">HA-4631</data><data key="node_domain">Hearings / Appeals / Evidence</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_HA4632"><data key="node_entity_id">FORM_HA4632</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-4632 Claimant's Medications</data><data key="node_acronym">HA-4632</data><data key="node_domain">Hearings / Appeals / Evidence</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_HA4633"><data key="node_entity_id">FORM_HA4633</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-4633 Claimant's Work Background</data><data key="node_acronym">HA-4633</data><data key="node_domain">Hearings / Appeals / Evidence</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_HA510"><data key="node_entity_id">FORM_HA510</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-510 Waiver of Timely Written Notice of Hearing</data><data key="node_acronym">HA-510</data><data key="node_domain">Hearings / Appeals / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_HA539"><data key="node_entity_id">FORM_HA539</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-539 Notice Regarding Substitution of Party Upon Death of Claimant</data><data key="node_acronym">HA-539</data><data key="node_domain">Hearings / Appeals / Forms</data><data key="node_description">Hearings form used when a party may substitute for a deceased claimant in an administrative proceeding.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current electronic submission; included in the July 25, 2026 conversational-form release.</data></node><node id="FORM_HA85"><data key="node_entity_id">FORM_HA85</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-85 Request to Withdraw a Hearing Request</data><data key="node_acronym">HA-85</data><data key="node_domain">Hearings / Appeals / Forms</data><data key="node_description">Form used by a claimant or representative to request withdrawal of a pending hearing request before the hearing decision is mailed.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current online submission; included in the July 25, 2026 Upload Documents conversational-form release.</data></node><node id="FORM_HA86"><data key="node_entity_id">FORM_HA86</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-86 Request to Withdraw an Appeals Council Request for Review</data><data key="node_acronym">HA-86</data><data key="node_domain">Hearings / Appeals / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_I501"><data key="node_entity_id">FORM_I501</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">Internet Request for Hearing by Administrative Law Judge</data><data key="node_acronym">i501</data><data key="node_domain">Appeals / Digital Forms</data><data key="node_description">Internet appeal form presented within iAppeals for a request for hearing by an Administrative Law Judge.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Modeled as an iAppeals component, not a standalone backend application.</data></node><node id="FORM_I520"><data key="node_entity_id">FORM_I520</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">Internet Request for Appeals Council Review</data><data key="node_acronym">i520</data><data key="node_domain">Appeals / Digital Forms</data><data key="node_description">Internet iAppeals form equivalent to HA-520 for requesting Appeals Council review of a hearing decision or order.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Available within iAppeals since June 16, 2018; modeled as a component rather than a standalone backend application.</data></node><node id="FORM_I561"><data key="node_entity_id">FORM_I561</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">Internet Request for Reconsideration</data><data key="node_acronym">i561</data><data key="node_domain">Appeals / Digital Forms</data><data key="node_description">Internet appeal form presented within iAppeals for a request for reconsideration.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Modeled as an iAppeals component, not a standalone backend application.</data></node><node id="FORM_IRS4029"><data key="node_entity_id">FORM_IRS4029</data><data key="node_entity_type">form</data><data key="node_canonical_name">IRS Form 4029 Application for Exemption From Social Security and Medicare Taxes and Waiver of Benefits</data><data key="node_acronym">Form 4029</data><data key="node_domain">earnings and enumeration</data><data key="node_description">IRS form processed by SSA Religious Exemption Unit procedures for qualifying religious exemptions.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS RM 04906.001.</data></node><node id="FORM_IRS4361"><data key="node_entity_id">FORM_IRS4361</data><data key="node_entity_type">form</data><data key="node_canonical_name">IRS Form 4361 Application for Exemption From Self-Employment Tax for Use by Ministers, Members of Religious Orders and Christian Science Practitioners</data><data key="node_acronym">Form 4361</data><data key="node_domain">earnings and enumeration</data><data key="node_description">IRS religious-exemption form documented as retained in SSA General Information Retrieval repository.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">Current POMS RM 04906.001 identifies GIR as housing historical and new Forms 4029 and 4361 received from IRS.</data></node><node id="FORM_IRS4506"><data key="node_entity_id">FORM_IRS4506</data><data key="node_entity_type">external_form</data><data key="node_canonical_name">IRS Form 4506 Request for Copy of Tax Return</data><data key="node_acronym">Form 4506</data><data key="node_domain">Earnings / IRS / External Evidence</data><data key="node_description">IRS form a number holder may use to request a copy of tax information and arrange for it to be submitted to SSA when information is not available through the standard SSA IRS request route.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">External IRS form referenced by current SSA POMS.</data></node><node id="FORM_IRS4506T"><data key="node_entity_id">FORM_IRS4506T</data><data key="node_entity_type">external_form</data><data key="node_canonical_name">IRS Form 4506-T Request for Transcript of Tax Return</data><data key="node_acronym">Form 4506-T</data><data key="node_domain">Earnings / IRS / External Evidence</data><data key="node_description">IRS transcript-request form a number holder may use to obtain tax information and have it submitted to SSA.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">External IRS form referenced by current SSA POMS.</data></node><node id="FORM_IRS_3857"><data key="node_entity_id">FORM_IRS_3857</data><data key="node_entity_type">form</data><data key="node_canonical_name">IRS Form 3857</data><data key="node_acronym">Form 3857</data><data key="node_domain">Identity / Earnings / IRS</data><data key="node_description">IRS form formally requesting SSA assistance locating and identifying a taxpayer SSN; also serves as an alert of a possible scrambled-earnings problem.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-06-13</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_R105_ECBSV_EINCONSENT"><data key="node_entity_id">FORM_R105_ECBSV_EINCONSENT</data><data key="node_entity_type">consent_form</data><data key="node_canonical_name">eCBSV Permitted Entity EIN Verification Consent</data><data key="node_domain">External Exchanges &amp; Identity</data><data key="node_description">Permitted entity corporate authority executes an EIN consent allowing SSA to verify the business employer identification number with IRS during eCBSV eligibility.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Legal consent for business EIN verification, not individual taxpayer address data.</data></node><node id="FORM_R105_SSA2506"><data key="node_entity_id">FORM_R105_SSA2506</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-2506-BK Quality Review Assumption-of-Jurisdiction Form</data><data key="node_domain">Disability &amp; Quality Review</data><data key="node_description">SSA identifies SSA-2506-BK for a reviewing psychological consultant where Disability Quality Review assumes jurisdiction.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_R105_SSA3023"><data key="node_entity_id">FORM_R105_SSA3023</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3023-F3 Medical Consultant Psychiatric Review Form</data><data key="node_domain">Disability &amp; Quality Review</data><data key="node_description">Psychological consultants may use SSA-3023-F3 to express review of psychiatric review technique findings when requirements are satisfied.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_R105_SSA392"><data key="node_entity_id">FORM_R105_SSA392</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-392 Medical Consultant Physical RFC Review</data><data key="node_domain">Disability &amp; Quality Review</data><data key="node_description">SSA-392 expresses medical consultant agreement or disagreement with the adjudicating component physical residual-functional-capacity assessment.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_R105_SSA392_SUP"><data key="node_entity_id">FORM_R105_SSA392_SUP</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-392-SUP Medical Consultant Mental RFC Review</data><data key="node_domain">Disability &amp; Quality Review</data><data key="node_description">SSA-392-SUP expresses psychiatric medical-review findings about mental residual-functional-capacity assessment.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_R105_SSA416"><data key="node_entity_id">FORM_R105_SSA416</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-416 Case Analysis</data><data key="node_domain">Disability &amp; Quality Review</data><data key="node_description">Consultants and qualifying federal quality reviewers use SSA-416 for case analysis and medical documentation deficiencies under specified policy conditions.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_R194_SAMOA_1199"><data key="node_entity_id">FORM_R194_SAMOA_1199</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1199-OP30 Samoa International Direct Deposit Signup Form</data><data key="node_domain">Title II Payments</data><data key="node_description">SSA identifies the Samoa country-specific IDD sign-up form among accepted input channels.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_R194_SM_1199"><data key="node_entity_id">FORM_R194_SM_1199</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1199-OP38 San Marino International Direct Deposit Signup Form</data><data key="node_domain">Title II Payments</data><data key="node_description">Documented country-specific beneficiary IDD signup form for San Marino.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-01-16</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_R96_HA501U5"><data key="node_entity_id">FORM_R96_HA501U5</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-501-U5 Request for Hearing by Administrative Law Judge</data><data key="node_acronym">HA-501-U5</data><data key="node_domain">Hearings &amp; Appeals / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Request for Hearing by Administrative Law Judge.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_HA520"><data key="node_entity_id">FORM_R96_HA520</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-520 Request for Review of Hearing Decision/Order</data><data key="node_acronym">HA-520</data><data key="node_domain">Hearings &amp; Appeals / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Request for Review of Hearing Decision/Order.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_HAL90"><data key="node_entity_id">FORM_R96_HAL90</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-L90 Request To Show Cause For Failure To Appear</data><data key="node_acronym">HA-L90</data><data key="node_domain">Hearings &amp; Appeals / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Request To Show Cause For Failure To Appear.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1223"><data key="node_entity_id">FORM_R96_SSA1223</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1223 Seizure Witness Questionnaire</data><data key="node_acronym">SSA-1223</data><data key="node_domain">Program Integrity / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Seizure Witness Questionnaire.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA131"><data key="node_entity_id">FORM_R96_SSA131</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-131 Employer Report of Special Wage Payments</data><data key="node_acronym">SSA-131</data><data key="node_domain">Earnings / Employer Reporting / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Employer Report of Special Wage Payments.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1372BK"><data key="node_entity_id">FORM_R96_SSA1372BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1372-BK Advanced Notice of Termination of Child's Benefits</data><data key="node_acronym">SSA-1372-BK</data><data key="node_domain">Title II / Student Benefits / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Advanced Notice of Termination of Child's Benefits.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1372BKFC"><data key="node_entity_id">FORM_R96_SSA1372BKFC</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1372-BK-FC Advanced Notice of Termination of Child's Benefits (Foreign Claims)</data><data key="node_acronym">SSA-1372-BK-FC</data><data key="node_domain">International / Title II / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Advanced Notice of Termination of Child's Benefits (Foreign Claims).</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1383"><data key="node_entity_id">FORM_R96_SSA1383</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1383 Student Reporting Form</data><data key="node_acronym">SSA-1383</data><data key="node_domain">Title II / Student Benefits / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Student Reporting Form.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1383FC"><data key="node_entity_id">FORM_R96_SSA1383FC</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1383-FC Reporting to Social Security Administration by Student Outside the United States</data><data key="node_acronym">SSA-1383-FC</data><data key="node_domain">International / Title II / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Reporting to Social Security Administration by Student Outside the United States.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1391"><data key="node_entity_id">FORM_R96_SSA1391</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1391 Employment Network Payment Request Form</data><data key="node_acronym">SSA-1391</data><data key="node_domain">Ticket to Work / Provider Payments / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Employment Network Payment Request Form.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1458"><data key="node_entity_id">FORM_R96_SSA1458</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1458 Certification By Religious Group</data><data key="node_acronym">SSA-1458</data><data key="node_domain">Coverage / Religious Exemption / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Certification By Religious Group.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1560"><data key="node_entity_id">FORM_R96_SSA1560</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1560 Petition For Authorization To Charge And Collect A Fee For Services Before The Social Security Administration</data><data key="node_acronym">SSA-1560</data><data key="node_domain">Representation / Fees / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Petition For Authorization To Charge And Collect A Fee For Services Before The Social Security Administration.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1691"><data key="node_entity_id">FORM_R96_SSA1691</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1691 Eligible Non-Attorney Representative Application</data><data key="node_acronym">SSA-1691</data><data key="node_domain">Representation / Registration / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Eligible Non-Attorney Representative Application.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1694"><data key="node_entity_id">FORM_R96_SSA1694</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1694 Request for Business Entity Taxpayer Information</data><data key="node_acronym">SSA-1694</data><data key="node_domain">Representation / Business Entity / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Request for Business Entity Taxpayer Information.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1696SUP1"><data key="node_entity_id">FORM_R96_SSA1696SUP1</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1696-SUP1 Claimant's Revocation of the Appointment of a Representative</data><data key="node_acronym">SSA-1696-SUP1</data><data key="node_domain">Representation / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Claimant's Revocation of the Appointment of a Representative.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1696SUP2"><data key="node_entity_id">FORM_R96_SSA1696SUP2</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1696-SUP2 Representative's Withdrawal of Acceptance of Appointment</data><data key="node_acronym">SSA-1696-SUP2</data><data key="node_domain">Representation / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Representative's Withdrawal of Acceptance of Appointment.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1699"><data key="node_entity_id">FORM_R96_SSA1699</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1699 Registration for Appointed Representative Services and Direct Payment</data><data key="node_acronym">SSA-1699</data><data key="node_domain">Representation / Registration / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Registration for Appointed Representative Services and Direct Payment.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA186"><data key="node_entity_id">FORM_R96_SSA186</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-186 Temporary Institutionalization Statement to Maintain Household and Physician Certification</data><data key="node_acronym">SSA-186</data><data key="node_domain">Title XVI / Eligibility / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Temporary Institutionalization Statement to Maintain Household and Physician Certification.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA1945"><data key="node_entity_id">FORM_R96_SSA1945</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1945 Statement Concerning Your Employment in a Job Not Covered by Social Security</data><data key="node_acronym">SSA-1945</data><data key="node_domain">Earnings / Coverage / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Statement Concerning Your Employment in a Job Not Covered by Social Security.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA199"><data key="node_entity_id">FORM_R96_SSA199</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-199 Vocational Rehabilitation Provider Claim</data><data key="node_acronym">SSA-199</data><data key="node_domain">Disability / Work Incentives / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Vocational Rehabilitation Provider Claim.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA21"><data key="node_entity_id">FORM_R96_SSA21</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-21 Supplement to Claim of Person Outside the United States</data><data key="node_acronym">SSA-21</data><data key="node_domain">International / Title II / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Supplement to Claim of Person Outside the United States.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA455OCRSM"><data key="node_entity_id">FORM_R96_SSA455OCRSM</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-455-OCR-SM Disability Update Report (Online Version)</data><data key="node_acronym">SSA-455-OCR-SM</data><data key="node_domain">Disability / CDR / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Disability Update Report (Online Version).</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA4BK"><data key="node_entity_id">FORM_R96_SSA4BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4-BK Application for Child's Insurance Benefits</data><data key="node_acronym">SSA-4-BK</data><data key="node_domain">Title II / Claims / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Application for Child's Insurance Benefits.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA5BK"><data key="node_entity_id">FORM_R96_SSA5BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-5-BK Application For Mother's Or Father's Insurance Benefits</data><data key="node_acronym">SSA-5-BK</data><data key="node_domain">Title II / Claims / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Application For Mother's Or Father's Insurance Benefits.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA723"><data key="node_entity_id">FORM_R96_SSA723</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-723 Statement Regarding the Inferred Death of an Individual by Reason of Continued and Unexplained Absence</data><data key="node_acronym">SSA-723</data><data key="node_domain">Death / Evidence / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Statement Regarding the Inferred Death of an Individual by Reason of Continued and Unexplained Absence.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA731"><data key="node_entity_id">FORM_R96_SSA731</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-731 Notice to Electronic Information Exchange Partners to Provide Contractor List</data><data key="node_acronym">SSA-731</data><data key="node_domain">Data Exchange / Security / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Notice to Electronic Information Exchange Partners to Provide Contractor List.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA770U4"><data key="node_entity_id">FORM_R96_SSA770U4</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-770-U4 Notice Regarding Substitution of Party Upon Death of Claimant Reconsideration of Disability Cessation</data><data key="node_acronym">SSA-770-U4</data><data key="node_domain">Disability / Reconsideration / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Notice Regarding Substitution of Party Upon Death of Claimant Reconsideration of Disability Cessation.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA7F6"><data key="node_entity_id">FORM_R96_SSA7F6</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-7-F6 Application for Parent's Insurance Benefits</data><data key="node_acronym">SSA-7-F6</data><data key="node_domain">Title II / Claims / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Application for Parent's Insurance Benefits.</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_R96_SSA88"><data key="node_entity_id">FORM_R96_SSA88</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-88 Pre-Approval Form for Consent Based Social Security Number Verification (CBSV)</data><data key="node_acronym">SSA-88</data><data key="node_domain">Identity Verification / Forms</data><data key="node_description">Current SSA form listed in the agency forms catalog: Pre-Approval Form for Consent Based Social Security Number Verification (CBSV).</data><data key="node_observed_status">observed_current_forms_catalog</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Electronic-submission relationship added only where the current forms catalog explicitly provides Submit Online.</data></node><node id="FORM_SF270"><data key="node_entity_id">FORM_SF270</data><data key="node_entity_type">form</data><data key="node_canonical_name">SF-270 Request for Advance or Reimbursement</data><data key="node_acronym">SF-270</data><data key="node_domain">Grants / Payments</data><data key="node_description">Federal form SSA grant recipients may email to the appropriate Financial Management Analyst for an advance or reimbursement while electronic payment setup is pending.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA OAG identifies SF-270 as an interim payment-request route; ASAP remains the required electronic payment system for award recipients.</data></node><node id="FORM_SF3881"><data key="node_entity_id">FORM_SF3881</data><data key="node_entity_type">form</data><data key="node_canonical_name">SF 3881 ACH Vendor/Miscellaneous Payment Enrollment Form</data><data key="node_acronym">SF 3881</data><data key="node_domain">Payments / Representative Travel</data><data key="node_description">Federal ACH enrollment form SSA accepts to establish electronic payment information for representative travel reimbursements.</data><data key="node_observed_status">observed_current_ssa_guidance</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="FORM_SF425"><data key="node_entity_id">FORM_SF425</data><data key="node_entity_type">form</data><data key="node_canonical_name">SF-425 Federal Financial Report</data><data key="node_acronym">SF-425</data><data key="node_domain">Grants / Financial Reporting</data><data key="node_description">Federal Financial Report form used by SSA grant recipients to report award financial information, including recipient cost share.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA OAG provides the form, instructions, and reporting guidance; no SSA-specific backing system is inferred.</data></node><node id="FORM_SS5"><data key="node_entity_id">FORM_SS5</data><data key="node_entity_type">form</data><data key="node_canonical_name">Form SS-5 — Application for a Social Security Card</data><data key="node_acronym">SS-5</data><data key="node_domain">Identity / Enumeration</data><data key="node_description">SSA form/application used to request an original, replacement, or corrected Social Security card and to support changes to the electronic SSN record.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Most SSN-card application processing is electronic through SSNAP; paper SS-5 remains used for mail and specified manual-processing situations.</data></node><node id="FORM_SSA10"><data key="node_entity_id">FORM_SSA10</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-10 Application for Widow's or Widower's Insurance Benefits</data><data key="node_acronym">SSA-10</data><data key="node_domain">Title II / Survivors / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA1021"><data key="node_entity_id">FORM_SSA1021</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1021 Appeal of Determination for Extra Help with Medicare Prescription Drug Plan Costs</data><data key="node_acronym">SSA-1021</data><data key="node_domain">Medicare / Extra Help / Appeals</data><data key="node_description">Form used to request an appeal of an SSA determination about Medicare Part D Extra Help.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says this form or MAPS Appeal Application screens can establish the appeal.</data></node><node id="FORM_SSA1128"><data key="node_entity_id">FORM_SSA1128</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1128 Representative Involved</data><data key="node_acronym">SSA-1128</data><data key="node_domain">Representation / Paper Claims</data><data key="node_description">Paper-folder flag used to identify representative involvement and record specified fee/representation indicators on paper claims.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directs staff to affix SSA-1128 to the paper claim folder.</data></node><node id="FORM_SSA1199_FAMILY"><data key="node_entity_id">FORM_SSA1199_FAMILY</data><data key="node_entity_type">form_family</data><data key="node_canonical_name">SSA-1199 International Direct Deposit Sign-Up Forms</data><data key="node_acronym">SSA-1199</data><data key="node_domain">Benefit Payments / International</data><data key="node_description">Country-specific form family used by Title II beneficiaries residing outside the United States to enroll in International Direct Deposit through a foreign financial institution.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Model as a form family rather than creating scores of country-specific entities.</data></node><node id="FORM_SSA11BK"><data key="node_entity_id">FORM_SSA11BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-11-BK Request to be Selected As Payee</data><data key="node_acronym">SSA-11-BK</data><data key="node_domain">Representative Payee / Forms</data><data key="node_description">Paper representative-payee application used when the application cannot be processed through eRPS, including specified applicants who lack an SSN and cannot be assigned one.</data><data key="node_observed_status">observed_current_exception_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS treats faxed, mailed, or dropped-off copies as leads requiring interview follow-up.</data></node><node id="FORM_SSA120"><data key="node_entity_id">FORM_SSA120</data><data key="node_entity_type">form</data><data key="node_canonical_name">Form SSA-120 Application for Access to SSA Systems</data><data key="node_acronym">SSA-120</data><data key="node_domain">External Data Exchange / Access</data><data key="node_description">Individual-access form used to designate each employee who will access SSA systems through Direct Terminal Access.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Submitted to the Office of Information Security under current DTA policy.</data></node><node id="FORM_SSA1222"><data key="node_entity_id">FORM_SSA1222</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1222 Seizure Questionnaire</data><data key="node_acronym">SSA-1222</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA1224"><data key="node_entity_id">FORM_SSA1224</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1224 Headache Questionnaire</data><data key="node_acronym">SSA-1224</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA1235"><data key="node_entity_id">FORM_SSA1235</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1235 Agreement Covering Reimbursable Services</data><data key="node_acronym">SSA-1235</data><data key="node_domain">data exchange governance</data><data key="node_description">Agreement used when SSA provides reimbursable death-information services under the full death-file data-exchange request process.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA death-information request guidance.</data></node><node id="FORM_SSA1372"><data key="node_entity_id">FORM_SSA1372</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Form SSA-1372 - Advance Notice of Termination of Child's Benefits</data><data key="node_acronym">SSA-1372</data><data key="node_domain">Title II / Student Benefits / Evidence</data><data key="node_description">Student-benefit form used to verify full-time elementary or secondary school attendance and support continued Title II child benefits after age 18.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms catalog lists SSA-1372-BK as PDF-only; the current catalog does not expose a Submit Online control for this form.</data></node><node id="FORM_SSA1395_BK"><data key="node_entity_id">FORM_SSA1395_BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1395-BK Receipt and Transmittal Form</data><data key="node_acronym">SSA-1395-BK</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">Manual receipt and transmittal form used only when the Debt Management System is non-functional or unavailable during field-office remittance processing.</data><data key="node_observed_status">observed_current_fallback_form</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS explicitly limits use to DMS non-functionality/unavailability.</data></node><node id="FORM_SSA150"><data key="node_entity_id">FORM_SSA150</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-150 Modified Benefits Formula Questionnaire</data><data key="node_acronym">SSA-150</data><data key="node_domain">Title II / Benefit Computation / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA157"><data key="node_entity_id">FORM_SSA157</data><data key="node_entity_type">form</data><data key="node_canonical_name">Form SSA-157 Data Exchange Request Form</data><data key="node_acronym">SSA-157 / DXRF</data><data key="node_domain">External Data Exchange / Access</data><data key="node_description">Request form an external agency submits to initiate SSA Direct Terminal Access consideration.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current DTA policy names the form Data Exchange Request Form (DXRF), Request for Information from SSA.</data></node><node id="FORM_SSA1719B"><data key="node_entity_id">FORM_SSA1719B</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1719B SSI Post-Eligibility Data Input</data><data key="node_acronym">SSA-1719B</data><data key="node_domain">Title XVI / Post-Eligibility / Address</data><data key="node_description">SSI post-eligibility data-input form that current COA policy permits for entering new mailing/residence information and living-arrangement codes when MSSICS is not used.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-08-07</data><data key="node_confidence">5</data><data key="node_notes">Base POMS text is older, but current transmittal/batch continues to reference this input route.</data></node><node id="FORM_SSA1724F4"><data key="node_entity_id">FORM_SSA1724F4</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1724-F4 Claim for Amounts Due in the Case of a Deceased Beneficiary</data><data key="node_acronym">SSA-1724-F4</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA1774"><data key="node_entity_id">FORM_SSA1774</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1774-U5 Request for Corrective Action</data><data key="node_acronym">SSA-1774-U5</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">Corrective-action request completed by Disability Quality Review to return Group I, Group II, and specified technical deficiencies to the adjudicating component.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS states DQR case-processing data electronically propagates most form sections before reviewer completion.</data></node><node id="FORM_SSA222"><data key="node_entity_id">FORM_SSA222</data><data key="node_entity_type">form</data><data key="node_canonical_name">Form SSA-222 Security Awareness Contractor Personnel Security Certification</data><data key="node_acronym">SSA-222</data><data key="node_domain">External Data Exchange / Access</data><data key="node_description">Security-certification form required when a designated DTA user is a requesting agency contractor.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current DTA policy identifies it as an additional contractor-user prerequisite.</data></node><node id="FORM_SSA2490"><data key="node_entity_id">FORM_SSA2490</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-2490 Application For Benefits Under a U.S. International Social Security Agreement</data><data key="node_acronym">SSA-2490</data><data key="node_domain">Forms / International / Totalization</data><data key="node_description">Current application for benefits under a U.S. international Social Security agreement; current Forms catalog provides Submit Online through Upload Documents.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Submit Online resolves to Upload Documents target=2490. No form-specific backend inferred.</data></node><node id="FORM_SSA25"><data key="node_entity_id">FORM_SSA25</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-25 Certification of Election for Reduced Spouse's Benefits</data><data key="node_acronym">SSA-25</data><data key="node_domain">Title II / Spouse Benefits / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA263"><data key="node_entity_id">FORM_SSA263</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-263 Waiver of Supplemental Security Income Payment Continuation</data><data key="node_acronym">SSA-263</data><data key="node_domain">Title XVI / Appeals / Forms</data><data key="node_description">Form used to waive continued SSI payments during applicable appeal or cessation processing.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current electronic submission; included in the July 25, 2026 conversational-form release.</data></node><node id="FORM_SSA2708"><data key="node_entity_id">FORM_SSA2708</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-2708 Come-In/Call-In Letter</data><data key="node_acronym">SSA-2708</data><data key="node_domain">Program Integrity / Death / Development</data><data key="node_description">Come-in/call-in letter sent when SSA cannot initially verify an alleged death through contact with the alleged decedent or a qualifying first-party reporter.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current September 2026 DATS policy.</data></node><node id="FORM_SSA2855"><data key="node_entity_id">FORM_SSA2855</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-2855 Statement of Funds you Received</data><data key="node_acronym">SSA-2855</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA2935"><data key="node_entity_id">FORM_SSA2935</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-2935 Authorization to the Social Security Administration to Obtain Personal Information</data><data key="node_acronym">SSA-2935</data><data key="node_domain">Forms / Consent / Digital Submission</data><data key="node_description">Authorization form available for electronic completion or PDF upload and subject to additional identity verification for electronic submission.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms page lists electronic submission and additional identity verification.</data></node><node id="FORM_SSA3"><data key="node_entity_id">FORM_SSA3</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3 Marriage Certification</data><data key="node_acronym">SSA-3</data><data key="node_domain">Title II / Family / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA308"><data key="node_entity_id">FORM_SSA308</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-308 Modified Benefits Formula Questionnaire, Foreign Pension</data><data key="node_acronym">SSA-308</data><data key="node_domain">Title II / Forms / Foreign Pension</data><data key="node_description">Current SSA form for modified-benefit-formula foreign-pension information, listed with an online submission route.</data><data key="node_observed_status">observed_current_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms catalog; backend processing path beyond online submission is not inferred.</data></node><node id="FORM_SSA3105"><data key="node_entity_id">FORM_SSA3105</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3105 Important Information About Your Appeal, Waiver Rights, and Repayment Options</data><data key="node_acronym">SSA-3105</data><data key="node_domain">Title II / Debt &amp; Overpayments / Forms</data><data key="node_description">Form allowing an overpaid person to request reconsideration, waiver, an explanation, withholding changes, or repayment options.</data><data key="node_observed_status">historical_form_artifact_current_use_unconfirmed</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">Historical SSA form used for reconsideration, waiver, explanation and repayment choices. Current SSA forms index does not list SSA-3105 and the prior direct PDF URL returned 404 on 2026-10-06; do not treat as a current required form without later validation.</data></node><node id="FORM_SSA3288OP1"><data key="node_entity_id">FORM_SSA3288OP1</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3288-OP1 Consent for Disclosure of Records Protected Under the Privacy Act</data><data key="node_acronym">SSA-3288-OP1</data><data key="node_domain">Forms / Privacy / Digital Intake</data><data key="node_description">SSA consent form currently listed with a Complete Online Form submission route.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms catalog establishes online submission availability. No form-specific backend beyond the existing Upload Documents experience is inferred.</data></node><node id="FORM_SSA3369BK"><data key="node_entity_id">FORM_SSA3369BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3369-BK Work History Report</data><data key="node_acronym">SSA-3369-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA3371BK"><data key="node_entity_id">FORM_SSA3371BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3371-BK Pain Report - Child</data><data key="node_acronym">SSA-3371-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA3373BK"><data key="node_entity_id">FORM_SSA3373BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3373-BK Function Report - Adult</data><data key="node_acronym">SSA-3373-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA3375BK"><data key="node_entity_id">FORM_SSA3375BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3375-BK Function Report - Child Birth to 1st Birthday</data><data key="node_acronym">SSA-3375-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA3376BK"><data key="node_entity_id">FORM_SSA3376BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3376-BK Function Report - Child Age 1 to 3rd Birthday</data><data key="node_acronym">SSA-3376-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA3377BK"><data key="node_entity_id">FORM_SSA3377BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3377-BK Function Report - Child Age 3 to 6th Birthday</data><data key="node_acronym">SSA-3377-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA3378BK"><data key="node_entity_id">FORM_SSA3378BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3378-BK Function Report - Child Age 6 to 12th Birthday</data><data key="node_acronym">SSA-3378-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA3379BK"><data key="node_entity_id">FORM_SSA3379BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3379-BK Function Report - Child Age 12 to 18th Birthday</data><data key="node_acronym">SSA-3379-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA3380BK"><data key="node_entity_id">FORM_SSA3380BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3380-BK Function Report - Adult - Third Party Form</data><data key="node_acronym">SSA-3380-BK</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA371"><data key="node_entity_id">FORM_SSA371</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-371 Request for Reinstatement - Title II</data><data key="node_acronym">SSA-371</data><data key="node_domain">Title II / Disability / Reinstatement</data><data key="node_description">Form used to request reinstatement under Title II.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current electronic submission; included in the July 25, 2026 conversational-form release.</data></node><node id="FORM_SSA372"><data key="node_entity_id">FORM_SSA372</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-372 Request For Reinstatement - Title XVI</data><data key="node_acronym">SSA-372</data><data key="node_domain">Title XVI / Disability / Reinstatement</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA377"><data key="node_entity_id">FORM_SSA377</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-377 Verification Request for Department of State Records</data><data key="node_acronym">SSA-377</data><data key="node_domain">Identity / Enumeration / Evidence Verification</data><data key="node_description">Form used to ask the Department of State to verify U.S. passports, passport cards, FS-240, FS-545, or DS-1350 records.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Available through SSA inForm according to current POMS; internal inForm implementation is not separately mapped in this run.</data></node><node id="FORM_SSA3885"><data key="node_entity_id">FORM_SSA3885</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3885 Government Pension Questionnaire</data><data key="node_acronym">SSA-3885</data><data key="node_domain">Title II / Forms / Government Pension</data><data key="node_description">Current SSA government-pension questionnaire listed with an online submission route.</data><data key="node_observed_status">observed_current_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms catalog; backend processing path beyond online submission is not inferred.</data></node><node id="FORM_SSA408"><data key="node_entity_id">FORM_SSA408</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-408 Route Slip</data><data key="node_acronym">SSA-408</data><data key="node_domain">Disability / Paper Folder Routing</data><data key="node_description">Paper routing form used by Disability Determination Services to route paper disability folders and identify the next destination or required action.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Electronic cases follow separate electronic routing instructions; SSA-408 remains a paper-case routing artifact.</data></node><node id="FORM_SSA4111"><data key="node_entity_id">FORM_SSA4111</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4111 Certification of Election for Reduced Widow(er)'s and Surviving Divorced Spouse's Benefits</data><data key="node_acronym">SSA-4111</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA414_U3"><data key="node_entity_id">FORM_SSA414_U3</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-414-U3 Fee Transmittal Register</data><data key="node_acronym">SSA-414-U3</data><data key="node_domain">Payments / Remittances / Fees</data><data key="node_description">Manual fee transmittal register required for standard-fee remittances in the current field-office remittance process.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS distinguishes this manual standard-fee register from DMS-generated FORT/CCFORT/FODRL reports.</data></node><node id="FORM_SSA4178"><data key="node_entity_id">FORM_SSA4178</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4178 Marital Relationship Questionnaire</data><data key="node_acronym">SSA-4178</data><data key="node_domain">Eligibility / Relationships</data><data key="node_description">Static webform added to customer-initiated Upload Documents in the March 2025 release.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA429"><data key="node_entity_id">FORM_SSA429</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-429 Interagency Agreement Data Sheet</data><data key="node_acronym">SSA-429</data><data key="node_domain">Data Exchange / Governance / Interagency</data><data key="node_description">Interagency Agreement Data Sheet identified by SSA as a required component of an IAA package.</data><data key="node_observed_status">observed_current_glossary</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Form identified by SSA Data Exchange glossary.</data></node><node id="FORM_SSA4346U2"><data key="node_entity_id">FORM_SSA4346U2</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4346-U2 SSI Offset Summary</data><data key="node_acronym">SSA-4346-U2</data><data key="node_domain">Title XVI / Windfall Offset / Computations</data><data key="node_description">Manual SSI Offset Summary used when SSI eComputations is unavailable or cannot complete a windfall-offset computation.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS states this form is the manual equivalent of specified eComputations windfall-result tabs.</data></node><node id="FORM_SSA437BK"><data key="node_entity_id">FORM_SSA437BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-437-BK Complaint Form for Allegations of Discrimination in Programs or Activities Conducted by the Social Security Administration</data><data key="node_acronym">SSA-437-BK</data><data key="node_domain">Civil Rights / Forms</data><data key="node_description">SSA complaint form for allegations of discrimination in SSA-conducted programs or activities; current Forms catalog provides electronic submission.</data><data key="node_observed_status">observed_current_electronic_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Submit Online link routes to the shared Upload Documents path with target 437.</data></node><node id="FORM_SSA44"><data key="node_entity_id">FORM_SSA44</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-44 Medicare Income-Related Monthly Adjustment Amount - Life-Changing Event</data><data key="node_acronym">SSA-44</data><data key="node_domain">Medicare / IRMAA / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA4513"><data key="node_entity_id">FORM_SSA4513</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4513 State Agency Report of Obligations for SSA Disability Programs</data><data key="node_acronym">SSA-4513</data><data key="node_domain">Disability / DDS / Financial Management</data><data key="node_description">State DDS financial-management report of obligations identified in current SSA policy.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Distributed electronically by SDRM; internal form-processing backend not identified.</data></node><node id="FORM_SSA4513_ADD"><data key="node_entity_id">FORM_SSA4513_ADD</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4513 Addendum State Agency Report of Obligations for SSA Disability Programs</data><data key="node_acronym">SSA-4513 Addendum</data><data key="node_domain">Disability / DDS / Financial Management</data><data key="node_description">Addendum to the State Agency Report of Obligations for SSA Disability Programs.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current policy lists the addendum separately among DDS financial-management forms.</data></node><node id="FORM_SSA4514"><data key="node_entity_id">FORM_SSA4514</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4514 Time Report of Personnel Services for Disability Determination Services</data><data key="node_acronym">SSA-4514</data><data key="node_domain">Disability / DDS / Financial Management</data><data key="node_description">State DDS personnel-services time report identified in current SSA financial-management instructions.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No electronic submission workflow is inferred beyond the documented electronic form distribution.</data></node><node id="FORM_SSA4547"><data key="node_entity_id">FORM_SSA4547</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4547 Advance Designation of Representative Payee</data><data key="node_acronym">SSA-4547</data><data key="node_domain">Payee / Person Identity</data><data key="node_description">Paper form SSA uses to collect or update the name, telephone number and optional relationship of advance designees; used alongside online channels.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA454BK"><data key="node_entity_id">FORM_SSA454BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-454-BK Continuing Disability Review Report</data><data key="node_acronym">SSA-454-BK</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">Continuing Disability Review report available through online i454 completion and Upload Documents; current Forms catalog requires additional identity verification for electronic submission.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA4968"><data key="node_entity_id">FORM_SSA4968</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4968 SSI RMA Payment Worksheet</data><data key="node_acronym">SSA-4968</data><data key="node_domain">Title XVI / Computations / Payments</data><data key="node_description">SSI Retrospective Monthly Accounting payment worksheet used as an alternative/manual calculation artifact for emergency advance payments and as a manual computation artifact when eComputations cannot complete required calculations.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directly names the form; no electronic form backend is inferred.</data></node><node id="FORM_SSA5002"><data key="node_entity_id">FORM_SSA5002</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-5002 Report of Contact</data><data key="node_acronym">SSA-5002</data><data key="node_domain">Case Documentation</data><data key="node_description">Report of Contact used to document development; EDCS UAT can create an SSA-5002 and add it to the Certified Electronic Folder.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Used across multiple workflows. This entity represents the form/document, not a storage system.</data></node><node id="FORM_SSA5062"><data key="node_entity_id">FORM_SSA5062</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-5062 Claimant's Statement about Loan of Food or Shelter</data><data key="node_acronym">SSA-5062</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA5064"><data key="node_entity_id">FORM_SSA5064</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-5064 Claimant's Statement About Loan For Shelter</data><data key="node_acronym">SSA-5064</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA521"><data key="node_entity_id">FORM_SSA521</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-521 Request for Withdrawal of Application</data><data key="node_acronym">SSA-521</data><data key="node_domain">Claims / Withdrawal / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA546"><data key="node_entity_id">FORM_SSA546</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-546 Worker's Compensation/Public Disability Questionnaire</data><data key="node_acronym">SSA-546</data><data key="node_domain">Title II Disability / WC-PDB / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA561"><data key="node_entity_id">FORM_SSA561</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-561 Request for Reconsideration</data><data key="node_acronym">SSA-561</data><data key="node_domain">Appeals / Forms</data><data key="node_description">SSA request-for-reconsideration form; current Forms catalog provides electronic submission.</data><data key="node_observed_status">observed_current_electronic_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Submit Online link routes to the shared Upload Documents path with target 561.</data></node><node id="FORM_SSA562U3"><data key="node_entity_id">FORM_SSA562U3</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-562-U3 Request for Assistance / Verification</data><data key="node_acronym">SSA-562-U3</data><data key="node_domain">Title XVI / External Verification</data><data key="node_description">SSA form used in the savings-security workflow to request Bureau of the Fiscal Service ownership verification through the designated SSA office.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Mapped only for the documented BFS verification use; form-wide uses may be broader.</data></node><node id="FORM_SSA632BK"><data key="node_entity_id">FORM_SSA632BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-632-BK Request for Waiver of Overpayment Recovery</data><data key="node_acronym">SSA-632-BK</data><data key="node_domain">Payments / Debt</data><data key="node_description">Form used to request waiver of overpayment recovery; current SSA service offers online completion/upload.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA634"><data key="node_entity_id">FORM_SSA634</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-634 Request for Change in Overpayment Recovery Rate</data><data key="node_acronym">SSA-634</data><data key="node_domain">Payments / Debt</data><data key="node_description">Form used to request a different overpayment recovery rate; SSA documents electronic signing/submission availability.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA635"><data key="node_entity_id">FORM_SSA635</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-635 Waiver Determination</data><data key="node_acronym">SSA-635</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Required for Title II and XVI waiver determinations above $2,000; records amount, fault, rationale, responsible officials and final approval signatures.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA640"><data key="node_entity_id">FORM_SSA640</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-640 Financial Disclosure for Civil Monetary Penalty Debt</data><data key="node_acronym">SSA-640</data><data key="node_domain">Program Integrity / Debt / Forms</data><data key="node_description">Financial disclosure form used by a person with civil monetary penalty debt who requests a change in current payment arrangements.</data><data key="node_observed_status">observed_current_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists electronic submission; POMS documents CMP debt purpose.</data></node><node id="FORM_SSA671"><data key="node_entity_id">FORM_SSA671</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-671 Railroad Employment Questionnaire</data><data key="node_acronym">SSA-671</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA7004"><data key="node_entity_id">FORM_SSA7004</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-7004 Request for Social Security Statement</data><data key="node_acronym">SSA-7004</data><data key="node_domain">Social Security Statement / Forms</data><data key="node_description">Public request form used by individuals who want a paper Social Security Statement mailed to them.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current public help directs users to print, complete, and mail SSA-7004.</data></node><node id="FORM_SSA7104"><data key="node_entity_id">FORM_SSA7104</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-7104 Partnership Questionnaire</data><data key="node_acronym">SSA-7104</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA711"><data key="node_entity_id">FORM_SSA711</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-711 Request for Deceased Individual’s Social Security Record</data><data key="node_acronym">SSA-711</data><data key="node_domain">FOIA / Identity Records</data><data key="node_description">Paper/request form SSA recommends for requesting a deceased person’s SS-5 and related Social Security record through the OEIO FOIA workgroup.</data><data key="node_observed_status">observed_current_foia_form</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA says the form is not mandatory and is expected to be updated in November 2026 for new fees effective 2026-10-01.</data></node><node id="FORM_SSA714"><data key="node_entity_id">FORM_SSA714</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-714 Request for Credit Card Payment</data><data key="node_acronym">SSA-714</data><data key="node_domain">FOIA / Payments</data><data key="node_description">Current SSA form used to submit credit-card payment with mailed FOIA/record requests.</data><data key="node_observed_status">observed_current_foia_payment_form</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA FOIA page directs mailed credit-card payers to use SSA-714.</data></node><node id="FORM_SSA7156"><data key="node_entity_id">FORM_SSA7156</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-7156 Farm Self Employment Questionnaire</data><data key="node_acronym">SSA-7156</data><data key="node_domain">Earnings / Self-Employment</data><data key="node_description">Static webform added to customer-initiated Upload Documents in the March 2025 release.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA7157"><data key="node_entity_id">FORM_SSA7157</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-7157 Farm Arrangement Questionnaire</data><data key="node_acronym">SSA-7157</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA721"><data key="node_entity_id">FORM_SSA721</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-721 Statement of Death By Funeral Director</data><data key="node_acronym">SSA-721</data><data key="node_domain">Death / Enumeration / Survivor Leads</data><data key="node_description">SSA form used by funeral directors to report death information and, when known, surviving spouse or child information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-05-29</data><data key="node_confidence">5</data><data key="node_notes">Current form edition is 10-2024; POMS directs DIPS/Numident processing and limited retention/destruction after processing.</data></node><node id="FORM_SSA753"><data key="node_entity_id">FORM_SSA753</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-753 Statement Regarding Marriage</data><data key="node_acronym">SSA-753</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA754F5"><data key="node_entity_id">FORM_SSA754F5</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-754-F5 Statement of Marital Relationship</data><data key="node_acronym">SSA-754-F5</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA760"><data key="node_entity_id">FORM_SSA760</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-760 Certificate of Support</data><data key="node_acronym">SSA-760</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA765"><data key="node_entity_id">FORM_SSA765</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-765 Response to Notice of Revised Determination</data><data key="node_acronym">SSA-765</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA766"><data key="node_entity_id">FORM_SSA766</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-766 Statement of Self Employment</data><data key="node_acronym">SSA-766</data><data key="node_domain">Earnings / Self-Employment</data><data key="node_description">Static webform added to customer-initiated Upload Documents in the March 2025 release.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA769"><data key="node_entity_id">FORM_SSA769</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-769 Request for Change in Time/Place of Disability Hearing</data><data key="node_acronym">SSA-769</data><data key="node_domain">Hearings / Appeals</data><data key="node_description">Static webform added to customer-initiated Upload Documents in the March 2025 release.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA773"><data key="node_entity_id">FORM_SSA773</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-773 Waiver of Right to Appear - Disability Hearing</data><data key="node_acronym">SSA-773</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed for electronic completion/submission through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA781"><data key="node_entity_id">FORM_SSA781</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-781 Certificate of Responsibility for Welfare and Care of Child</data><data key="node_acronym">SSA-781</data><data key="node_domain">Forms / Title II / Child Benefits</data><data key="node_description">Current SSA form for documenting responsibility for a child's welfare and care; current Forms catalog provides Submit Online through Upload Documents.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Submit Online resolves to Upload Documents target=781. No form-specific backend inferred.</data></node><node id="FORM_SSA783"><data key="node_entity_id">FORM_SSA783</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-783 Statement Regarding Contributions</data><data key="node_acronym">SSA-783</data><data key="node_domain">Title XVI / Contributions</data><data key="node_description">Static webform added to customer-initiated Upload Documents in the March 2025 release.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA787"><data key="node_entity_id">FORM_SSA787</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-787 Medical Source Opinion of Patient’s Capability to Manage Benefits</data><data key="node_acronym">SSA-787</data><data key="node_domain">representative payee / evidence</data><data key="node_description">Preferred SSA form for obtaining medical-source evidence regarding beneficiary capability to manage benefits.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current GN 00502.040.</data></node><node id="FORM_SSA788"><data key="node_entity_id">FORM_SSA788</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-788 Statement of Care and Responsibility for Beneficiary</data><data key="node_acronym">SSA-788</data><data key="node_domain">representative payee / evidence</data><data key="node_description">Form used to obtain third-party custodian lay evidence for capability development when the custodian differs from the payee applicant.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current GN 00502.030.</data></node><node id="FORM_SSA789"><data key="node_entity_id">FORM_SSA789</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-789 Request for Reconsideration - Disability Cessation</data><data key="node_acronym">SSA-789</data><data key="node_domain">Disability / Appeals / Forms</data><data key="node_description">Form used to request reconsideration of a disability cessation determination.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current online completion/upload; included in the July 25, 2026 conversational-form release.</data></node><node id="FORM_SSA792"><data key="node_entity_id">FORM_SSA792</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-792 Statutory Benefit Continuation Election Statement</data><data key="node_acronym">SSA-792</data><data key="node_domain">Disability / Appeals / Benefit Continuation</data><data key="node_description">Election statement used in statutory benefit-continuation processing.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current electronic submission; included in the July 25, 2026 conversational-form release.</data></node><node id="FORM_SSA795"><data key="node_entity_id">FORM_SSA795</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-795 Statement of Claimant or Other Person</data><data key="node_acronym">SSA-795</data><data key="node_domain">Case Documentation</data><data key="node_description">Signed statement used, among other purposes, to document a claimant’s understanding when an SSA field-office address is used as the mailing address.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current GN 02401.050 requires signed SSA-795 storage in the electronic folder for the field-office-address workflow, subject to specified exceptions.</data></node><node id="FORM_SSA8"><data key="node_entity_id">FORM_SSA8</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8 Application for Lump-Sum Death Payment</data><data key="node_acronym">SSA-8</data><data key="node_domain">Title II / Survivors / Forms</data><data key="node_description">Current SSA public form with online completion and PDF-upload submission routes listed on SSA Forms.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists both Complete Online Form and Upload PDF under Submit Online.</data></node><node id="FORM_SSA8000BK"><data key="node_entity_id">FORM_SSA8000BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8000-BK Application for Supplemental Security Income (SSI)</data><data key="node_acronym">SSA-8000-BK</data><data key="node_domain">Title XVI / Forms</data><data key="node_description">Full Supplemental Security Income application form used in paper and certain PERC/deferred-development workflows.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms page and POMS continue to reference this form.</data></node><node id="FORM_SSA8006F4"><data key="node_entity_id">FORM_SSA8006F4</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8006-F4 Statement of Living Arrangements, In-Kind Support and Maintenance</data><data key="node_acronym">SSA-8006-F4</data><data key="node_domain">Title XVI / Living Arrangements / Forms</data><data key="node_description">Paper development form referenced by current SSI redetermination residence procedures.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">4</data><data key="node_notes">Form-level role is validated by current POMS; current standalone public PDF availability was not established in this run.</data></node><node id="FORM_SSA8007"><data key="node_entity_id">FORM_SSA8007</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8007 Statement of Living Arrangements</data><data key="node_acronym">SSA-8007</data><data key="node_domain">Title XVI / Living Arrangements / Forms</data><data key="node_description">Paper development form referenced by current SSI redetermination residence procedures.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">4</data><data key="node_notes">Form-level role is validated by current POMS; current standalone public PDF availability was not established in this run.</data></node><node id="FORM_SSA8008"><data key="node_entity_id">FORM_SSA8008</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8008 Statement of Living Arrangements, In-Kind Support and Maintenance</data><data key="node_acronym">SSA-8008</data><data key="node_domain">Title XVI / Living Arrangements / Forms</data><data key="node_description">Paper development form referenced by current SSI redetermination residence procedures.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">4</data><data key="node_notes">Form-level role is validated by current POMS; current standalone public PDF availability was not established in this run.</data></node><node id="FORM_SSA8010BK"><data key="node_entity_id">FORM_SSA8010BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8010-BK Statement of Income and Resources</data><data key="node_acronym">SSA-8010-BK</data><data key="node_domain">Title XVI / Forms / Income and Resources</data><data key="node_description">Form used to collect income and resource information about specified deemors and in PERC-related development.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current Forms page lists the form; current 2026 POMS describes use and entry into the SSI Claims System/electronic folder.</data></node><node id="FORM_SSA8011F3"><data key="node_entity_id">FORM_SSA8011F3</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8011-F3 Statement of Household Expenses and Contributions</data><data key="node_acronym">SSA-8011-F3</data><data key="node_domain">Title XVI / Living Arrangements / Forms</data><data key="node_description">Legacy SSI living-arrangements form used to document household expenses and contributions for periods before September 30, 2024.</data><data key="node_observed_status">historical_for_pre_2024_periods</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS directs use of SSA-8012 for periods effective September 30, 2024 or later.</data></node><node id="FORM_SSA8012"><data key="node_entity_id">FORM_SSA8012</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8012 Statement of Household Expenses and Contributions</data><data key="node_acronym">SSA-8012</data><data key="node_domain">Title XVI / Living Arrangements / Forms</data><data key="node_description">Current SSI form for a claimant or recipient statement about household expenses and contributions for living-arrangement periods effective September 30, 2024 or later.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies SSA-8012 as successor form for current periods.</data></node><node id="FORM_SSA8203BK"><data key="node_entity_id">FORM_SSA8203BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8203-BK Statement for Determining Continuing Eligibility for Supplemental Security Income Payments</data><data key="node_acronym">SSA-8203-BK</data><data key="node_domain">Title XVI / Redetermination / Forms</data><data key="node_description">Paper SSI redetermination form whose residence and mailing-address questions support redetermination development.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Current POMS references page 9 and residence questions. This entity is policy-validated; current PDF edition not separately asserted in this run.</data></node><node id="FORM_SSA820BK"><data key="node_entity_id">FORM_SSA820BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-820-BK Work Activity Report – Self-Employment</data><data key="node_acronym">SSA-820-BK</data><data key="node_domain">Disability / Work Activity</data><data key="node_description">Work activity report for self-employment; transitioned from the older Adobe Sign e820/821 route to Upload Documents.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA821BK"><data key="node_entity_id">FORM_SSA821BK</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-821-BK Work Activity Report – Employee</data><data key="node_acronym">SSA-821-BK</data><data key="node_domain">Disability / Work Activity</data><data key="node_description">Work activity report for employee wage activity; transitioned from the older Adobe Sign e820/821 route to Upload Documents.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA827"><data key="node_entity_id">FORM_SSA827</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-827 Authorization to Disclose Information to the Social Security Administration</data><data key="node_acronym">SSA-827</data><data key="node_domain">Disability / Evidence Authorization</data><data key="node_description">Authorization form used to permit SSA to obtain medical and other information; supported by electronic signing/submission and requires advanced credential step-up in Upload Documents when submitted through that route.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA8510"><data key="node_entity_id">FORM_SSA8510</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8510 Authorization for the Social Security Administration to Obtain Personal Information</data><data key="node_acronym">SSA-8510</data><data key="node_domain">Forms / Consent / Digital Submission</data><data key="node_description">Authorization form available for electronic completion or PDF upload and subject to additional identity verification for electronic submission.</data><data key="node_observed_status">observed_current_digital_form</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms page lists electronic submission and additional identity verification.</data></node><node id="FORM_SSA8552"><data key="node_entity_id">FORM_SSA8552</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8552 Interview Confirmation</data><data key="node_acronym">SSA-8552</data><data key="node_domain">forms and digital intake</data><data key="node_description">SSA form currently listed with a Complete Online Form and Upload PDF electronic submission route through SSA's Forms experience.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms listing.</data></node><node id="FORM_SSA871"><data key="node_entity_id">FORM_SSA871</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-871 State Agency Schedule of Equipment Purchased for SSA Disability Programs</data><data key="node_acronym">SSA-871</data><data key="node_domain">Disability / DDS / Financial Management</data><data key="node_description">State DDS schedule of equipment purchased for SSA disability programs.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No asset-management database is inferred.</data></node><node id="FORM_SSA872"><data key="node_entity_id">FORM_SSA872</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-872 State Agency Obligational Authorization for SSA Disability Programs</data><data key="node_acronym">SSA-872</data><data key="node_domain">Disability / DDS / Funding</data><data key="node_description">Official SSA funding document authorizing a State disability determination agency to incur obligations against Federal funds for approved disability-program expenses.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says SSA issues the authorization quarterly or at six-to-eight-week intervals as appropriate.</data></node><node id="FORM_SSA89"><data key="node_entity_id">FORM_SSA89</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Form SSA-89 Authorization for SSA to Release SSN Verification</data><data key="node_acronym">SSA-89</data><data key="node_domain">Identity Verification / Consent</data><data key="node_description">SSA consent form authorizing disclosure of Social Security number verification results for consent-based verification services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current eCBSV guidance accepts SSA-89 with wet signature or fillable PDF electronic signature; CBSV enrollment also requires the current SSA-89.</data></node><node id="FORM_SSA93"><data key="node_entity_id">FORM_SSA93</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-93 Quality Review Feedback Report</data><data key="node_acronym">SSA-93</data><data key="node_domain">SSI / Quality Review</data><data key="node_description">Quality-review feedback report used to communicate early-notice findings and field-office corrective actions in SSI quality reviews.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2025-08-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="FORM_SSA_2574"><data key="node_entity_id">FORM_SSA_2574</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-2574 Information About Joint Checking/Savings Accounts Supplemental Security Income</data><data key="node_acronym">SSA-2574</data><data key="node_domain">Title XVI / Resources / Digital Forms</data><data key="node_description">SSI form used to document/rebut presumed ownership of funds in a joint checking or savings account; current Forms supports online completion and upload.</data><data key="node_observed_status">observed_current_form</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">December 2025 Upload Documents release permits individual representative payees to submit SSA-2574 for beneficiaries; current conversational-forms guidance also includes SSA-2574.</data></node><node id="FORM_SSA_L2001"><data key="node_entity_id">FORM_SSA_L2001</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L2001 Address Information Request</data><data key="node_acronym">SSA-L2001</data><data key="node_domain">Address / USPS</data><data key="node_description">SSA form/letter sent to the Postal Service to request current address information during locate development.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Documented in SSI and Title II locate procedures; response is an address lead subject to program development.</data></node><node id="FORM_SSA_L2765_C1"><data key="node_entity_id">FORM_SSA_L2765_C1</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L2765-C1 Request for Self-Employment Information</data><data key="node_acronym">SSA-L2765-C1</data><data key="node_domain">Earnings / Self-Employment / Wage Corrections</data><data key="node_description">Historical DECOR letter informing a self-employed worker of name/SSN discrepancies.</data><data key="node_observed_status">suspended_since_2012</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says this letter used an address derived from IRS-provided data.</data></node><node id="FORM_SSA_L3365_C1"><data key="node_entity_id">FORM_SSA_L3365_C1</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L3365-C1 Request to Employee for Social Security Information</data><data key="node_acronym">SSA-L3365-C1</data><data key="node_domain">Earnings / Wage Corrections</data><data key="node_description">Historical DECOR letter informing an employee of name/SSN discrepancies.</data><data key="node_observed_status">suspended_since_2012</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says this DECOR letter used the employee address derived from Form W-2.</data></node><node id="FORM_SSA_L4002_C1"><data key="node_entity_id">FORM_SSA_L4002_C1</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L4002-C1 Request for Employer Information</data><data key="node_acronym">SSA-L4002-C1</data><data key="node_domain">Earnings / Employer / Wage Corrections</data><data key="node_description">Historical DECOR letter sent to an employer when employee information needed development.</data><data key="node_observed_status">suspended_since_2012</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says employer mailing occurred when the employee address was unavailable or failed USPS-database validation.</data></node><node id="FORM_SSA_L4020"><data key="node_entity_id">FORM_SSA_L4020</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L4020 Prisoner Incentive Payment Recoupment Notice</data><data key="node_acronym">SSA-L4020</data><data key="node_domain">Program Integrity / Prisoner / Debt</data><data key="node_description">Fillable notice used to request return of an incorrectly paid prisoner incentive payment from an institution.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says the template is obtained from inForm.</data></node><node id="FORM_SSA_L501"><data key="node_entity_id">FORM_SSA_L501</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L501 Home Visit Letter</data><data key="node_acronym">SSA-L501</data><data key="node_domain">Title II / Program Integrity / Notices</data><data key="node_description">MNUP appointment notice used when SSA schedules a home-visit interview at the beneficiary residence.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Generated from DPS for MNUP scheduling.</data></node><node id="FORM_SSA_L502"><data key="node_entity_id">FORM_SSA_L502</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L502 Telephone Interview Letter</data><data key="node_acronym">SSA-L502</data><data key="node_domain">Title II / Program Integrity / Notices</data><data key="node_description">MNUP appointment notice used to schedule a telephone interview with the beneficiary and representative payee, if any.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Generated from DPS for MNUP scheduling.</data></node><node id="FORM_SSA_L505"><data key="node_entity_id">FORM_SSA_L505</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L505 Residence Address Request</data><data key="node_acronym">SSA-L505</data><data key="node_domain">Title II / Address Provenance / Notices</data><data key="node_description">MNUP notice used to request a beneficiary residence address when SSA records contain only a mailing address.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">This is address development, not an automatic master-record update.</data></node><node id="FORM_SSA_L676"><data key="node_entity_id">FORM_SSA_L676</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L676 Refusal to Process SSN Application</data><data key="node_acronym">SSA-L676</data><data key="node_domain">Identity &amp; Enumeration / Notices</data><data key="node_description">Written notice used in specified SSN cases to explain that SSA cannot assign an SSN or issue a card when required work authorization or a valid nonwork basis and supporting evidence are not established.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">The notice does not itself verify the applicant documents for a State agency.</data></node><node id="FORM_US_ROMANIA_COC_RO"><data key="node_entity_id">FORM_US_ROMANIA_COC_RO</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Romanian Certificate of Coverage under the U.S.-Romania Agreement</data><data key="node_acronym">Romanian Certificate of Coverage</data><data key="node_domain">International / Totalization</data><data key="node_description">Certificate issued by Romania proving Romanian coverage and corresponding exemption from U.S. coverage on the same earnings.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Transport, persistence, and backend implementation are not disclosed by the public policy.</data></node><node id="FORM_US_ROMANIA_COC_US"><data key="node_entity_id">FORM_US_ROMANIA_COC_US</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">U.S. Certificate of Coverage under the U.S.-Romania Agreement</data><data key="node_acronym">U.S. Certificate of Coverage</data><data key="node_domain">International / Totalization</data><data key="node_description">Certificate proving that the named worker is subject to U.S. Social Security coverage/taxation and exempt from Romanian coverage on the same earnings.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Transport, persistence, and backend implementation are not disclosed by the public policy.</data></node><node id="FUNC_ELAS_VERIFY_PI"><data key="node_entity_id">FUNC_ELAS_VERIFY_PI</data><data key="node_entity_type">workflow_action</data><data key="node_canonical_name">eLAS Verify PI Action</data><data key="node_acronym">Verify PI</data><data key="node_domain">Customer Service / Identity Verification</data><data key="node_description">Action on the eLAS summary page used after staff verifies iAppointment identity data; receipts the UNVER issue and permits verified data to enter CLIENT/ICDB.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-06-26</data><data key="node_confidence">5</data><data key="node_notes">Human-triggered action; implementation mechanics are not inferred.</data></node><node id="FUNC_MAQR"><data key="node_entity_id">FUNC_MAQR</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">Medical Authority for Quality Reviewers</data><data key="node_acronym">MAQR</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">QRCPS-supported capability allowing qualified federal quality reviewers to complete certain medical assessments instead of obtaining MC/PC review.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a feature/task within QRCPS, not a standalone application.</data></node><node id="FUNC_SVB_UPDATE"><data key="node_entity_id">FUNC_SVB_UPDATE</data><data key="node_entity_type">interface</data><data key="node_canonical_name">MSSICS Special Veterans Benefit Update Function</data><data key="node_acronym">SVB update function</data><data key="node_domain">Special Veterans Benefits</data><data key="node_description">Special Veterans Benefit function on the Direct SSR Update path used to post the Title VIII indicator and related record actions.</data><data key="node_observed_status">current_poms_retained_detailed_topology_old</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="GOV_NAFC"><data key="node_entity_id">GOV_NAFC</data><data key="node_entity_type">governance_body</data><data key="node_canonical_name">National Anti-Fraud Committee</data><data key="node_acronym">NAFC</data><data key="node_domain">Program Integrity / Governance</data><data key="node_description">Joint SSA and SSA OIG anti-fraud governance partnership that meets quarterly and holds an annual summit to share information, identify actions, and mitigate fraud-risk vulnerabilities.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a governance body/process, not an application or analytic platform.</data></node><node id="HIST_AJS1"><data key="node_entity_id">HIST_AJS1</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Automated Job Stream 1</data><data key="node_acronym">AJS-1</data><data key="node_domain">Title II / Historical Post-entitlement</data><data key="node_description">Legacy post-entitlement processing system associated with AERO and rate changes.</data><data key="node_observed_status">retired_into_t2r_2014</data><data key="node_observed_as_of">2014-08</data><data key="node_confidence">5</data><data key="node_notes">POMS states T2R incorporated AJS-1 functionality in August 2014.</data></node><node id="HIST_AJS3"><data key="node_entity_id">HIST_AJS3</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Automated Job Stream 3</data><data key="node_acronym">AJS-3</data><data key="node_domain">Title II / Historical Earnings Enforcement</data><data key="node_description">Legacy automated job stream for work-related post-entitlement events and earnings enforcement.</data><data key="node_observed_status">retired_into_t2r_2012</data><data key="node_observed_as_of">2012-08</data><data key="node_confidence">5</data><data key="node_notes">POMS states AJS-3 software was retired and functionality rolled into T2R in August 2012.</data></node><node id="IFACE_CCE_HEALTH_INS"><data key="node_entity_id">IFACE_CCE_HEALTH_INS</data><data key="node_entity_type">interface</data><data key="node_canonical_name">CCE Health Insurance Screen</data><data key="node_domain">Medicare / Claims</data><data key="node_description">CCE screen used to document Medicaid status and initiate State buy-in in applicable cases.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data></node><node id="IFACE_CIS2_ENUM_SSA"><data key="node_entity_id">IFACE_CIS2_ENUM_SSA</data><data key="node_entity_type">interface</data><data key="node_canonical_name">CIS2 Enumeration File to SSA</data><data key="node_domain">Identity / Enumeration / DHS Exchange</data><data key="node_description">DHS outgoing system interface providing enumeration data to SSA’s SSN Enumeration system; interface data is sourced from the DSI data file.</data><data key="node_observed_status">current_partner_inventory</data><data key="node_observed_as_of">2026-02-05</data><data key="node_confidence">5</data><data key="node_notes">DHS Data.gov identifier USCIS-10059-MAJ-10059-011. The current partner inventory does not identify the exact SSA receiving application, transport, file layout, or hosting.</data></node><node id="IFACE_DRIN"><data key="node_entity_id">IFACE_DRIN</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Record Installment Agreement Screen</data><data key="node_acronym">DRIN</data><data key="node_domain">Debt &amp; Collections</data><data key="node_description">DMS input screen used to record Title II installment agreements and trigger overnight ROAR updates.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-25</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="IFACE_DRPF"><data key="node_entity_id">IFACE_DRPF</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Protest/Stop Recovery Request (Field Office)</data><data key="node_acronym">DRPF</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Debt Management System screen used by field offices to record protest/stop-recovery requests such as overpayment explanations.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS/MS references establish the screen and DMS context.</data></node><node id="IFACE_DRPR"><data key="node_entity_id">IFACE_DRPR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Protest/Stop Recovery Request (Processing Center)</data><data key="node_acronym">DRPR</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Debt Management System screen used by processing centers to stop recovery and record explanation/protest activity.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS establishes the screen and DMS context.</data></node><node id="IFACE_DRPT"><data key="node_entity_id">IFACE_DRPT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Protest/Stop Recovery Request (Teleservice Center)</data><data key="node_acronym">DRPT</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Debt Management System screen used by teleservice centers to record protest/stop-recovery requests.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS/MS references establish the screen and DMS context.</data></node><node id="IFACE_FFEL"><data key="node_entity_id">IFACE_FFEL</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Fugitive Felon Suspension and Reinstatement Screen</data><data key="node_acronym">FFEL</data><data key="node_domain">Title II / Program Integrity</data><data key="node_description">Screen used for manual Title II fugitive-felon suspension and reinstatement input in MCS, POS, and MACADE.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="IFACE_MCS_HI19"><data key="node_entity_id">IFACE_MCS_HI19</data><data key="node_entity_type">interface</data><data key="node_canonical_name">MCS HI19 State Buy-In Interface</data><data key="node_acronym">HI19</data><data key="node_domain">Medicare / Claims</data><data key="node_description">MCS interface used by field offices to initiate Medicare Part B state buy-in in applicable public-welfare accretion cases.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">Modeled only to the screen/function level documented in POMS.</data></node><node id="IFACE_NDNH_QUERY"><data key="node_entity_id">IFACE_NDNH_QUERY</data><data key="node_entity_type">interface</data><data key="node_canonical_name">National Directory of New Hires Query</data><data key="node_acronym">NDNH Query</data><data key="node_domain">External Data / Earnings &amp; Employment</data><data key="node_description">Authorized query-only SSA interface/process for looking up NDNH new-hire, wage and unemployment information when investigating earnings.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">The detailed query instructions date from 2016, but the interface remains listed in the current 2026 work-activity POMS chapter and NDNH remains an active matching source.</data></node><node id="IFACE_QMID"><data key="node_entity_id">IFACE_QMID</data><data key="node_entity_type">interface</data><data key="node_canonical_name">CDR Query Medical Information Data Screen</data><data key="node_acronym">QMID</data><data key="node_domain">Disability / CDR</data><data key="node_description">DCF query screen used to review medical diary information relevant to work CDR enforcement alerts.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Listed in current May 2026 POMS and referenced by CDREO alert instructions.</data></node><node id="IFACE_QROP"><data key="node_entity_id">IFACE_QROP</data><data key="node_entity_type">query_interface</data><data key="node_canonical_name">Query Response Overpayment</data><data key="node_acronym">QROP</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Online overpayment query used by FO/TSC staff as one source for explaining Title II overpayments.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS establishes use; internal query protocol is not public.</data></node><node id="IFACE_QWID"><data key="node_entity_id">IFACE_QWID</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Query Work Information Data Screen</data><data key="node_acronym">QWID</data><data key="node_domain">Title II Disability / Work CDR</data><data key="node_description">DCF query screen used to view work-review and earnings-enforcement information including CDREO and QEP alerts.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Listed in current May 2026 POMS work-activity chapter and referenced by current CDREO/QEP instructions.</data></node><node id="IFACE_SSI_DIRECT_SSR"><data key="node_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="node_entity_type">interface</data><data key="node_canonical_name">SSI Claims System Direct SSR Update</data><data key="node_acronym">Direct SSR Update</data><data key="node_domain">Title XVI / Post-Eligibility</data><data key="node_description">SSI Claims System/MSSICS direct-update interface used for specified Title XVI payment, stop-payment, overpayment, and waiver inputs to the Supplemental Security Record.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Logical interface modeled from POMS. Public sources do not disclose protocol, middleware, API, or database connectivity.</data></node><node id="INIT_ASSESSMENT_APPSEC"><data key="node_entity_id">INIT_ASSESSMENT_APPSEC</data><data key="node_entity_type">initiative</data><data key="node_canonical_name">Assessment and Application Security</data><data key="node_domain">Cybersecurity / Application Security</data><data key="node_description">FY2027 initiative to modernize State-agency assessment processes and emphasize dynamic application scanning early in the development lifecycle.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Budget plan; no scanning product or vendor is inferred.</data></node><node id="INIT_CSCRM"><data key="node_entity_id">INIT_CSCRM</data><data key="node_entity_type">initiative</data><data key="node_canonical_name">SSA Cybersecurity Supply Chain Risk Management Program</data><data key="node_acronym">CSCRM</data><data key="node_domain">Cybersecurity / Third-Party Risk</data><data key="node_description">SSA program that assesses and monitors cybersecurity supply-chain risk for third-party vendors, contractors, OEMs, and service providers.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG security page documents pre-award assessment and post-award monitoring.</data></node><node id="INIT_CYBER_MOD_COMPLIANCE"><data key="node_entity_id">INIT_CYBER_MOD_COMPLIANCE</data><data key="node_entity_type">initiative</data><data key="node_canonical_name">Cybersecurity Modernization and Compliance</data><data key="node_domain">Cybersecurity / Modernization</data><data key="node_description">FY2027 initiative to modernize, automate, and integrate cybersecurity tools and processes, streamline authorization, and enhance continuous monitoring.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Budget plan; no product, platform, or vendor is inferred.</data></node><node id="INIT_IDENTITY_ACCESS_RISK"><data key="node_entity_id">INIT_IDENTITY_ACCESS_RISK</data><data key="node_entity_type">initiative</data><data key="node_canonical_name">Identity, Access, and Risk Management</data><data key="node_domain">Cybersecurity / Identity &amp; Risk</data><data key="node_description">FY2027 initiative to expand identity and access management, risk quantification, and insider-threat programs.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Budget plan; not evidence of a single named IAM product or completed deployment.</data></node><node id="INIT_ITOM"><data key="node_entity_id">INIT_ITOM</data><data key="node_entity_type">project</data><data key="node_canonical_name">IT Operations Management Improvements</data><data key="node_acronym">ITOM Improvements</data><data key="node_domain">Infrastructure / Operations</data><data key="node_description">Multi-year effort replacing IT operations management technologies and practices for managing capabilities in a hybrid cloud ecosystem.</data><data key="node_observed_status">in_progress_fy2026</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="INIT_MAINFRAME_RESILIENCE"><data key="node_entity_id">INIT_MAINFRAME_RESILIENCE</data><data key="node_entity_type">project</data><data key="node_canonical_name">Mainframe Business Resilience</data><data key="node_acronym">Business Resilience Automation</data><data key="node_domain">Infrastructure / Resilience</data><data key="node_description">Automation initiative intended to move workloads between data centers when business or environmental circumstances require it.</data><data key="node_observed_status">funded_fy2026</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2026 justification targets 99.99% uptime and 24/7 availability; portfolio table lists $111.4M for Business Resilience Automation.</data></node><node id="INIT_SECOPS_THREAT_RESPONSE"><data key="node_entity_id">INIT_SECOPS_THREAT_RESPONSE</data><data key="node_entity_type">initiative</data><data key="node_canonical_name">Security Operations and Threat Response</data><data key="node_domain">Cybersecurity / Operations</data><data key="node_description">FY2027 initiative for security operations, monitoring, external attack-surface analytics, and threat detection, response, and mitigation capabilities.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Budget plan; no SOC platform or vendor is inferred.</data></node><node id="INIT_SSI_IMPROVEMENT"><data key="node_entity_id">INIT_SSI_IMPROVEMENT</data><data key="node_entity_type">initiative</data><data key="node_canonical_name">SSI Improvement Team and Office</data><data key="node_acronym">SSI Improvement</data><data key="node_domain">Title XVI / Modernization / Program Integrity</data><data key="node_description">Dedicated SSA initiative and office created to improve SSI processing efficiency, reduce improper payments, expand automation, simplify reporting, and implement policy, process, and technology changes.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Created in September 2025. SSA describes this as both an SSI Improvement Team and a dedicated SSI Improvement office.</data></node><node id="INIT_STAT_PUB_MOD"><data key="node_entity_id">INIT_STAT_PUB_MOD</data><data key="node_entity_type">initiative</data><data key="node_canonical_name">Modernization of Statistical Publication Processes</data><data key="node_domain">Research &amp; Statistical Publications / Modernization</data><data key="node_description">SSA multi-year effort to modernize statistical data, tables, reports, and publication workflows for OASDI, SSI, and earnings-related work.</data><data key="node_observed_status">active_multi_year_modernization</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget reports FY2025 SharePoint migration work, FY2026 automation/data-source changes, and FY2027 enhanced EBI tooling.</data></node><node id="INIT_SYSTEMS_MODERNIZATION_PLAN_1980S"><data key="node_entity_id">INIT_SYSTEMS_MODERNIZATION_PLAN_1980S</data><data key="node_entity_type">modernization_initiative</data><data key="node_canonical_name">Systems Modernization Plan (mid-1980s)</data><data key="node_acronym">SMP</data><data key="node_domain">Infrastructure / Historical Modernization</data><data key="node_description">Major SSA modernization initiative that upgraded mainframe computers, storage hardware, and field-office terminal deployment before the IWS/LAN transition.</data><data key="node_observed_status">historical_completed_prior_to_1994</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">OTA identifies the mid-1980s Systems Modernization Plan as the major initiative that stabilized the then-current mainframe environment.</data></node><node id="INT_UPLOAD_DOCS_START"><data key="node_entity_id">INT_UPLOAD_DOCS_START</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Upload Documents Start Endpoint</data><data key="node_domain">Digital Forms / Web Intake</data><data key="node_description">Public secure SSA web entry point at /eSubmit/upload-documents-ui/start that accepts form target and submission-mode parameters for Upload Documents.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Validated from current SSA Forms links across appeals, disability, representative-payee, SSI, and debt forms. The eSubmit path name is an endpoint path; application rename evidence is tracked separately.</data></node><node id="LAKE_HADOOP_2016"><data key="node_entity_id">LAKE_HADOOP_2016</data><data key="node_entity_type">data_lake</data><data key="node_canonical_name">Hadoop Data Lake (2016 EDW source)</data><data key="node_acronym">Hadoop Data Lake</data><data key="node_domain">Enterprise Data / Big Data</data><data key="node_description">Historical Hadoop data lake documented as the upstream source from which Informatica ETL would pull data into the new EDW.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Physical cluster topology, datasets, and retention were not disclosed in the strategic plan.</data></node><node id="MODEL_MINT8"><data key="node_entity_id">MODEL_MINT8</data><data key="node_entity_type">model</data><data key="node_canonical_name">Modeling Income in the Near Term Version 8</data><data key="node_acronym">MINT8</data><data key="node_domain">Research / Microsimulation / Policy</data><data key="node_description">SSA microsimulation model used for projections related to beneficiaries and taxpayers, including distributional analysis of policy options and future beneficiary outcomes.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA methodology says MINT8 is built from SSA administrative records matched to SIPP and uses Trustees Report assumptions.</data></node><node id="MODEL_OACT_BEN_LR"><data key="node_entity_id">MODEL_OACT_BEN_LR</data><data key="node_entity_type">model</data><data key="node_canonical_name">OCACT Long-Range Beneficiary Projection Model</data><data key="node_domain">Actuarial / OASDI Beneficiary Projection</data><data key="node_description">Actuarial Services model used after the first 10 projection years to project beneficiary populations by marital status and benefit type under long-range methods.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Separate from the already-mapped long-range fully-insured model; no software implementation or platform is inferred.</data></node><node id="MODEL_OACT_BEN_SR"><data key="node_entity_id">MODEL_OACT_BEN_SR</data><data key="node_entity_type">model</data><data key="node_canonical_name">OCACT Short-Range Beneficiary Projection Model</data><data key="node_domain">Actuarial / OASDI Beneficiary Projection</data><data key="node_description">Actuarial Services model used for the first 10 years of beneficiary projections, reflecting recent and expected short-term trends and applying award/termination methods described in the 2026 Trustees Report.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Separate from the already-mapped short-range fully-insured model; this entity is beneficiary-projection scoped.</data></node><node id="MODEL_OACT_FI_LR"><data key="node_entity_id">MODEL_OACT_FI_LR</data><data key="node_entity_type">model</data><data key="node_canonical_name">OCACT Long-Range Fully Insured Model</data><data key="node_domain">Actuarial / OASDI Projection</data><data key="node_description">Actuarial long-range model using simulated work histories by sex and birth cohort to project fully insured status and related OASDI eligibility measures.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Logical actuarial model documented in the 2026 Trustees Report; implementation technology is not public.</data></node><node id="MODEL_OACT_FI_SR"><data key="node_entity_id">MODEL_OACT_FI_SR</data><data key="node_entity_type">model</data><data key="node_canonical_name">OCACT Short-Range Fully Insured Model</data><data key="node_domain">Actuarial / OASDI Projection</data><data key="node_description">Actuarial short-range model that extrapolates fully insured percentages using CWHS work-history coverage information, beneficiary administrative data, mortality estimates, projected mortality, and covered-worker projections.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Logical actuarial model documented in the 2026 Trustees Report; implementation technology is not public.</data></node><node id="MODEL_OACT_LABOR_FORCE"><data key="node_entity_id">MODEL_OACT_LABOR_FORCE</data><data key="node_entity_type">model</data><data key="node_canonical_name">OCACT Civilian Labor Force Projection Model</data><data key="node_domain">Actuarial / Economic Projections</data><data key="node_description">Actuarial Services model that projects the civilian labor force by age, sex, marital status, and presence of children using demographic and economic assumptions.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">The Trustees Report describes the model and factors but does not disclose software, platform, programming language, or physical implementation.</data></node><node id="MODEL_OACT_POPULATION"><data key="node_entity_id">MODEL_OACT_POPULATION</data><data key="node_entity_type">model</data><data key="node_canonical_name">OCACT Social Security Area Population Projection Model</data><data key="node_domain">Actuarial / Demographic Projections</data><data key="node_description">Actuarial Services projection model/method that projects the Social Security area population by age, sex, and marital status by combining fertility, mortality, immigration, marriage, and divorce assumptions.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">Logical actuarial model as documented in the 2026 Trustees Report; no implementation technology is inferred.</data></node><node id="MODEL_OASDI_SCENARIO"><data key="node_entity_id">MODEL_OASDI_SCENARIO</data><data key="node_entity_type">model</data><data key="node_canonical_name">OASDI Scenario-Based Projection Model</data><data key="node_domain">Actuarial / OASDI Projection</data><data key="node_description">Traditional scenario-based model used in the Trustees Report with low-cost, intermediate, and high-cost assumptions for key variables.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 Trustees methodology explicitly calls this the scenario-based model. Implementation software and hosting are not inferred.</data></node><node id="MODEL_OASDI_STOCHASTIC"><data key="node_entity_id">MODEL_OASDI_STOCHASTIC</data><data key="node_entity_type">model</data><data key="node_canonical_name">OASDI Stochastic Projection Model</data><data key="node_domain">Actuarial / OASDI Projection</data><data key="node_description">Trustees-report stochastic model that estimates probability distributions for future combined OASI and DI trust-fund financial outcomes using 5,000 simulations.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 Trustees methodology validates the model and its statistical method. Implementation software and hosting are not public in the cited source.</data></node><node id="NETWORK_CAREQUALITY"><data key="node_entity_id">NETWORK_CAREQUALITY</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Carequality Network</data><data key="node_acronym">Carequality</data><data key="node_domain">Health Information Exchange</data><data key="node_description">Interoperability network through which SSA reports nationwide healthcare connectivity alongside eHealth Exchange.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-02-17</data><data key="node_confidence">5</data><data key="node_notes">SSA says it is connected to providers through eHealth Exchange and Carequality.</data></node><node id="NETWORK_TEFCA"><data key="node_entity_id">NETWORK_TEFCA</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Trusted Exchange Framework and Common Agreement Network</data><data key="node_acronym">TEFCA</data><data key="node_domain">Health Information Exchange</data><data key="node_description">Nationwide health-data exchange framework selected for expanded SSA disability evidence access through eHealth Exchange as QHIN.</data><data key="node_observed_status">connection_testing_documented</data><data key="node_observed_as_of">2026-02-17</data><data key="node_confidence">4</data><data key="node_notes">SSA's latest first-party source found in this run said QHIN connection was in testing and expected live in early spring 2026; no later first-party go-live confirmation was found.</data></node><node id="NET_N8NN_AVAYA"><data key="node_entity_id">NET_N8NN_AVAYA</data><data key="node_entity_type">network_platform</data><data key="node_canonical_name">National 800 Number Avaya Network</data><data key="node_acronym">Avaya</data><data key="node_domain">Customer Service / Telephony / Historical Architecture</data><data key="node_description">Avaya network used in parallel with CARE2020 for National 800 Number CSR calls beginning March 31, 2020.</data><data key="node_observed_status">historical_documented_network</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The Open Data source establishes the dual-network period but does not identify exact retirement date or complete Avaya product stack.</data></node><node id="NET_N8NN_CARE2020"><data key="node_entity_id">NET_N8NN_CARE2020</data><data key="node_entity_type">network_platform</data><data key="node_canonical_name">National 800 Number CARE 2020 Network</data><data key="node_acronym">CARE 2020</data><data key="node_domain">Customer Service / Telephony / Historical Architecture</data><data key="node_description">National 800 Number routing/network environment identified by SSA Open Data as CARE 2020.</data><data key="node_observed_status">historical_documented_network</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SSA says it moved to CARE 2020 beginning in 2013; within the 10-year horizon, dual CARE2020/Avaya operation is documented from 2020-03-31.</data></node><node id="NET_SSANET"><data key="node_entity_id">NET_SSANET</data><data key="node_entity_type">network</data><data key="node_canonical_name">SSANet</data><data key="node_acronym">SSANet</data><data key="node_domain">Infrastructure / Network</data><data key="node_description">SSA enterprise data network that connected field-office and teleservice-center terminals to mainframes at the National Computer Center in the early 1990s.</data><data key="node_observed_status">historically_documented_1994</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">OTA describes SSANet as the network carrying transactions between distributed terminals/LANs and Baltimore mainframes.</data></node><node id="NOTICE_ADRP_ANNUAL"><data key="node_entity_id">NOTICE_ADRP_ANNUAL</data><data key="node_entity_type">notice</data><data key="node_canonical_name">ADRP Automated Annual Designee Notice</data><data key="node_domain">Payee / Communications</data><data key="node_description">Annual notice to capable beneficiaries with advance designees and no current payee; includes ordered names and contact details.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="NOTICE_EDCOR"><data key="node_entity_id">NOTICE_EDCOR</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Employer Correction Request Notice</data><data key="node_acronym">EDCOR</data><data key="node_domain">Earnings / Employer / Wage Corrections</data><data key="node_description">Employer educational/no-match notice used to identify submitted W-2 name/SSN combinations that could not be matched to SSA records.</data><data key="node_observed_status">mailing_discontinued_2021</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA employer guidance says mailing ended effective April 2021; examples remain available and POMS preserves historical procedures.</data></node><node id="NOTICE_MAPS_PREDECISION"><data key="node_entity_id">NOTICE_MAPS_PREDECISION</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Extra Help Pre-Decisional Notice</data><data key="node_acronym">Pre-Decisional Notice</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">Advance notice automatically generated by the subsidy determination process when a potential Extra Help denial is identified.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="NOTICE_MSP_L447"><data key="node_entity_id">NOTICE_MSP_L447</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Medicare Savings Program Outreach Notice L447</data><data key="node_acronym">L447</data><data key="node_domain">Medicare / Low-Income Assistance / Outreach</data><data key="node_description">Annual SSA outreach notice sent to beneficiaries identified as potentially eligible for Medicare Savings Programs or Extra Help.</data><data key="node_observed_status">current_annual_notice</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">English and Spanish versions are linked from current SSA Open Data page.</data></node><node id="NOTICE_MSP_L448"><data key="node_entity_id">NOTICE_MSP_L448</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Medicare Savings Program Outreach Notice L448</data><data key="node_acronym">L448</data><data key="node_domain">Medicare / Low-Income Assistance / Outreach</data><data key="node_description">Annual SSA outreach notice sent to beneficiaries identified as potentially eligible for Medicare Savings Programs or Extra Help.</data><data key="node_observed_status">current_annual_notice</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">English and Spanish versions are linked from current SSA Open Data page.</data></node><node id="NOTICE_SURVIVOR_LETTER"><data key="node_entity_id">NOTICE_SURVIVOR_LETTER</data><data key="node_entity_type">notice</data><data key="node_canonical_name">DPS Survivor Letter</data><data key="node_domain">Notices / Survivor Benefits</data><data key="node_description">Letter sent from the DPS General folder when SSA-721 provides a survivor name and address, to alert the survivor to potential benefit entitlement.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-05-29</data><data key="node_confidence">5</data><data key="node_notes">Exact template identifier is not stated in the cited POMS section.</data></node><node id="NOTICE_T2R_COA_CONFIRM"><data key="node_entity_id">NOTICE_T2R_COA_CONFIRM</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Title II Redesign Change of Address Confirmation Notice</data><data key="node_acronym">T2R COA Notice</data><data key="node_domain">Title II / Address / Notices</data><data key="node_description">Fraud-reduction notice sent to the old MBR mailing address after an address change through my Social Security or telephone IVR.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Address provenance is explicit: the confirmation notice uses the old mailing address stored on MBR; no separate beneficiary/payee address is available on MBR for this notice.</data></node><node id="ORG_AAMVA"><data key="node_entity_id">ORG_AAMVA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">American Association of Motor Vehicle Administrators</data><data key="node_acronym">AAMVA</data><data key="node_domain">External Partner</data><data key="node_description">Connectivity/conduit partner between SSA and state motor-vehicle agencies for SSOLV and HAVV.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="ORG_ACCENTURE_FEDERAL"><data key="node_entity_id">ORG_ACCENTURE_FEDERAL</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Accenture Federal Services LLC</data><data key="node_acronym">Accenture Federal</data><data key="node_domain">Vendor</data><data key="node_description">Federal contractor holding SSA BPA 28321321A00040017 for OPTS software and support services.</data><data key="node_observed_status">observed_current_vendor</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_ACCESSAGILITY"><data key="node_entity_id">ORG_ACCESSAGILITY</data><data key="node_entity_type">organization</data><data key="node_canonical_name">AccessAgility LLC</data><data key="node_domain">Vendor / DevSecOps / Software</data><data key="node_description">Federal contractor receiving SSA delivery order 28321326FDX030022 for Sonatype Nexus Repository annual software renewal.</data><data key="node_observed_status">observed_procurement_provider_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Vendor role is based on federal-award data mirrored from USAspending/SAM sources.</data></node><node id="ORG_ADOBE"><data key="node_entity_id">ORG_ADOBE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Adobe</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_APRYSE"><data key="node_entity_id">ORG_APRYSE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Apryse</data><data key="node_domain">Vendor / Document Technology</data><data key="node_description">Vendor/product owner named in SSA procurement for PDFTron PDFNet SDK renewal.</data><data key="node_observed_status">observed_current_procurement</data><data key="node_observed_as_of">2026-04-29</data><data key="node_confidence">5</data></node><node id="ORG_ARDENT_CLOUD"><data key="node_entity_id">ORG_ARDENT_CLOUD</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Ardent Cloud, LLC</data><data key="node_acronym">Ardent Cloud</data><data key="node_domain">Vendor</data><data key="node_description">Federal contractor that performed SSA geographic information system development and support services for OSEP under BPA Call 28321325FA0010051.</data><data key="node_observed_status">historical_observed_vendor</data><data key="node_observed_as_of">2026-06-18</data><data key="node_confidence">5</data><data key="node_notes">Vendor name is taken from USAspending. The company name does not establish that SSA used a cloud platform under this award.</data></node><node id="ORG_ARTICULATE"><data key="node_entity_id">ORG_ARTICULATE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Articulate</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_ATT"><data key="node_entity_id">ORG_ATT</data><data key="node_entity_type">organization</data><data key="node_canonical_name">AT&amp;T</data><data key="node_domain">External Provider / Telecommunications</data><data key="node_description">Commercial cellular network provider explicitly identified in SSA FirstNet procurement context.</data><data key="node_observed_status">observed_external_dependency</data><data key="node_observed_as_of">2026-09-21</data><data key="node_confidence">5</data><data key="node_notes">Modeled as network dependency, not as the awardee for the procurement notice.</data></node><node id="ORG_AVERISOURCE"><data key="node_entity_id">ORG_AVERISOURCE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">AveriSource</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_AWS"><data key="node_entity_id">ORG_AWS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Amazon Web Services</data><data key="node_acronym">AWS</data><data key="node_domain">Vendor / Cloud</data><data key="node_description">Commercial cloud service provider documented in SSA cloud procurement and telephone modernization records.</data><data key="node_observed_status">documented_provider_2025</data><data key="node_observed_as_of">2025-06-30</data><data key="node_confidence">5</data><data key="node_notes">GAO documents AWS as an included commercial cloud provider under SSA's Four Points BPA; SSA's FY2024 AFR documents AWS/Amazon Connect for the National 800 Number.</data></node><node id="ORG_BENEFICIARY_FI"><data key="node_entity_id">ORG_BENEFICIARY_FI</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Beneficiary Financial Institution</data><data key="node_acronym">FI</data><data key="node_domain">External Partner / Address Source</data><data key="node_description">Financial institution holding a beneficiary direct-deposit account and contacted by SSA for current mailing-address information during Title II whereabouts/undeliverable-mail development.</data><data key="node_observed_status">observed_current_policy_role</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Generic external actor category; it is separate from the SSI AFI/eAFI financial-resource verification exchange.</data></node><node id="ORG_BFS"><data key="node_entity_id">ORG_BFS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Bureau of the Fiscal Service</data><data key="node_acronym">BFS</data><data key="node_domain">External Partner</data><data key="node_description">Treasury bureau and computer-matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_BLS"><data key="node_entity_id">ORG_BLS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Bureau of Labor Statistics</data><data key="node_acronym">BLS</data><data key="node_domain">External Partner / Department of Labor</data><data key="node_description">Department of Labor bureau that develops and publishes ORS data for SSA occupational-information modernization.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_BROADCOM"><data key="node_entity_id">ORG_BROADCOM</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Broadcom</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_BU_HDRI"><data key="node_entity_id">ORG_BU_HDRI</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Boston University Health and Disability Research Institute</data><data key="node_acronym">BU-HDRI</data><data key="node_domain">External Partner / Disability Research</data><data key="node_description">Boston University research institute subcontracted by NIH CRC/RMD to develop computerized adaptive testing instruments and study questions for the Functional Assessment Study.</data><data key="node_observed_status">documented_current_pia_role</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">PIA states BU-HDRI subcontracted with Westat for data collection.</data></node><node id="ORG_CARAHSOFT"><data key="node_entity_id">ORG_CARAHSOFT</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Carahsoft Technology Corp.</data><data key="node_domain">Technology Ecosystem / Reseller</data><data key="node_description">Federal technology reseller identified as the legal business name and awardee on SSA ServiceNow software BPA 28321325A00040016.</data><data key="node_observed_status">observed_current_contractor</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">UEI DT8KJHZXVJH5 in FPDS contract record.</data></node><node id="ORG_CBP"><data key="node_entity_id">ORG_CBP</data><data key="node_entity_type">organization</data><data key="node_canonical_name">U.S. Customs and Border Protection</data><data key="node_acronym">CBP</data><data key="node_domain">External Partner / DHS</data><data key="node_description">DHS component that receives immigrant visa enumeration information from the Department of State and updates it when the immigrant is admitted at a U.S. port of entry.</data><data key="node_observed_status">observed_current_partner</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">External partner in EAE chain; no SSA-hosted CBP system is inferred.</data></node><node id="ORG_CDI_UNITS"><data key="node_entity_id">ORG_CDI_UNITS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Cooperative Disability Investigations Units</data><data key="node_acronym">CDI Units</data><data key="node_domain">Program Integrity / Disability Fraud</data><data key="node_description">Nationwide investigative units combining SSA OIG, SSA, DDS, and state/local law-enforcement personnel.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">50 units cover all states, DC, Puerto Rico, and U.S. territories.</data></node><node id="ORG_CENSUS"><data key="node_entity_id">ORG_CENSUS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">U.S. Census Bureau</data><data key="node_acronym">Census</data><data key="node_domain">External Partner</data><data key="node_description">Historical/statistical data partner referenced in SSA SORNs.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="ORG_CMS"><data key="node_entity_id">ORG_CMS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Centers for Medicare &amp; Medicaid Services</data><data key="node_acronym">CMS</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching/data partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_CNCS"><data key="node_entity_id">ORG_CNCS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Corporation for National and Community Service</data><data key="node_acronym">CNCS</data><data key="node_domain">External Partner</data><data key="node_description">Federal agency that adopted the operating name AmeriCorps and participates in SSA Computer Matching Agreement 1012.</data><data key="node_observed_status">active_matching_partner</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">CMA 1012 states CNCS adopted the operating name AmeriCorps in 2020 without changing its legal name.</data></node><node id="ORG_COMERICA"><data key="node_entity_id">ORG_COMERICA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Comerica Bank</data><data key="node_domain">External Partner / Financial Agent</data><data key="node_description">Legacy Direct Express financial agent referenced during the 2026 transition to Fifth Third Bank.</data><data key="node_observed_status">transitioning_legacy</data><data key="node_observed_as_of">2026-05-19</data><data key="node_confidence">5</data><data key="node_notes">Current SSA emergency guidance says existing Comerica cards continue during phased migration.</data></node><node id="ORG_CREDIT_REPOSITORIES"><data key="node_entity_id">ORG_CREDIT_REPOSITORIES</data><data key="node_entity_type">organization</data><data key="node_canonical_name">National Credit Repositories</data><data key="node_domain">External Partner</data><data key="node_description">National holders of credit data receiving eligible SSA delinquent-debt information for credit reporting.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_CREOAL"><data key="node_entity_id">ORG_CREOAL</data><data key="node_entity_type">organization</data><data key="node_canonical_name">CREOAL Consulting LLC</data><data key="node_domain">Vendor</data><data key="node_description">Federal contractor supporting SSA SSOARS and SERS application database administration and operating system services under task order 28321323FDX030012.</data><data key="node_observed_status">observed_current_vendor</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">USAspending identifies CREOAL Consulting LLC as the recipient of the in-progress SSA task order.</data></node><node id="ORG_DAPS"><data key="node_entity_id">ORG_DAPS</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Division of Administrative Payment Services</data><data key="node_acronym">DAPS</data><data key="node_domain">Finance / Administrative Payments</data><data key="node_description">SSA organization component operating the Vendor Payment Center and handling vendor administrative payment inquiries.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Public SSA vendor pages establish the organizational role; no broader accounting-system ownership is inferred.</data></node><node id="ORG_DCR"><data key="node_entity_id">ORG_DCR</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Disability Case Review</data><data key="node_acronym">DCR</data><data key="node_domain">Disability / Federal Adjudication</data><data key="node_description">SSA federal disability processing organization/site that adjudicates specified disability claims and is assuming nationwide medical continuing-disability-review processing from State DDSs.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies DCR as location code V32 for railroad dual-eligibility work. SSA announced nationwide medical CDR transition to DCR in March 2026.</data></node><node id="ORG_DDS"><data key="node_entity_id">ORG_DDS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">State Disability Determination Services</data><data key="node_acronym">DDS</data><data key="node_domain">Disability / State Operations</data><data key="node_description">State agencies/components that develop medical evidence and make disability determinations for SSA under federal program rules.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA/POMS/Data.gov sources refer to DDS as operating users of DCPS and evidence systems.</data></node><node id="ORG_DEISB"><data key="node_entity_id">ORG_DEISB</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Data Exchange Infrastructure Support Branch</data><data key="node_acronym">DEISB</data><data key="node_domain">Enterprise Infrastructure / Data Exchange</data><data key="node_description">SSA branch that leads development, selection, evaluation, implementation, and maintenance of software and hardware supporting data exchange.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS assigns DEISB responsibility for determining whether software-vendor contracts permit Data Exchange Software License Grants.</data></node><node id="ORG_DHS"><data key="node_entity_id">ORG_DHS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Department of Homeland Security</data><data key="node_acronym">DHS</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching/data partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_DHU"><data key="node_entity_id">ORG_DHU</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Disability Hearing Unit</data><data key="node_acronym">DHU</data><data key="node_domain">Disability / Reconsideration Hearings</data><data key="node_description">SSA disability-hearing processing unit receiving medical CDR reconsideration cases and post-transfer updates from field offices.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS repeatedly names DHU. Internal organizational hierarchy and supporting case-control system are not inferred beyond published policy.</data></node><node id="ORG_DIGITAL_SERVICES_ENGAGEMENT"><data key="node_entity_id">ORG_DIGITAL_SERVICES_ENGAGEMENT</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Digital Services Engagement Team</data><data key="node_acronym">Digital Services Engagement Team</data><data key="node_domain">Digital Services / Notices</data><data key="node_description">SSA team documented as the creator of QR codes used in agency notices.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No database, hosting platform, QR generator product, or transport is inferred beyond the documented internal request/control system.</data></node><node id="ORG_DIIAS"><data key="node_entity_id">ORG_DIIAS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Division of Internet/Intranet Application Services</data><data key="node_acronym">DIIAS</data><data key="node_domain">Enterprise Infrastructure / Data Exchange</data><data key="node_description">SSA organizational division named in current data-exchange policy as the parent organization for the Data Exchange Infrastructure Support Branch.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS places DIIAS within the Office of Hardware Engineering. No organizational structure beyond the source wording is inferred.</data></node><node id="ORG_DMDC"><data key="node_entity_id">ORG_DMDC</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Defense Manpower Data Center</data><data key="node_acronym">DMDC</data><data key="node_domain">External Partner</data><data key="node_description">Department of Defense data organization participating in SSA Computer Matching Agreement 1004.</data><data key="node_observed_status">active_matching_partner</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA active matching-program list identifies DMDC as partner for CMA 1004.</data></node><node id="ORG_DNB"><data key="node_entity_id">ORG_DNB</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Dun &amp; Bradstreet</data><data key="node_acronym">D&amp;B</data><data key="node_domain">Vendor</data><data key="node_description">Commercial provider contracted by SSA to supply credit information for new non-governmental fee-for-service organizational representative payees.</data><data key="node_observed_status">observed_current_vendor_role</data><data key="node_observed_as_of">2026-07-15</data><data key="node_confidence">5</data><data key="node_notes">Exact contract award/PIID for this representative-payee credit service was not located in this run.</data></node><node id="ORG_DOL"><data key="node_entity_id">ORG_DOL</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Department of Labor</data><data key="node_acronym">DOL</data><data key="node_domain">External Partner</data><data key="node_description">Federal data exchange/matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_DOS"><data key="node_entity_id">ORG_DOS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Department of State</data><data key="node_acronym">DoS</data><data key="node_domain">External Partner</data><data key="node_description">Federal partner in Enumeration at Entry and passport-related SSN verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_DYNATOUCH"><data key="node_entity_id">ORG_DYNATOUCH</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Dynatouch Corporation</data><data key="node_domain">Vendor / Field Office Technology</data><data key="node_description">Vendor identified as the 2026 recipient of the SSA KioWare maintenance purchase order supporting VIPr kiosks.</data><data key="node_observed_status">observed_current_vendor</data><data key="node_observed_as_of">2026-09-09</data><data key="node_confidence">4</data><data key="node_notes">Vendor/award details corroborated by two federal-award mirrors after direct primary award pages were not machine-resolved.</data></node><node id="ORG_DYNATRACE"><data key="node_entity_id">ORG_DYNATRACE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Dynatrace</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_ED"><data key="node_entity_id">ORG_ED</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Department of Education</data><data key="node_acronym">ED</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_EHEALTH_EXCHANGE"><data key="node_entity_id">ORG_EHEALTH_EXCHANGE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">eHealth Exchange</data><data key="node_domain">External Partner</data><data key="node_description">National health information network partner used by SSA for electronic medical-record exchange and selected as SSA's TEFCA QHIN.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-02-17</data><data key="node_confidence">5</data><data key="node_notes">SSA says live exchanges with eHealth Exchange began in 2009 and continue.</data></node><node id="ORG_EMERGENT_LLC"><data key="node_entity_id">ORG_EMERGENT_LLC</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Emergent, LLC</data><data key="node_domain">Vendor / Software Maintenance</data><data key="node_description">Federal contractor receiving SSA delivery order 28321326FDX030114 for specified Oracle, SERS, and SSOARS software maintenance.</data><data key="node_observed_status">observed_procurement_provider_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Vendor role is based on federal-award data mirrored from USAspending/SAM sources.</data></node><node id="ORG_EMPLOYMENT_NETWORKS"><data key="node_entity_id">ORG_EMPLOYMENT_NETWORKS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Ticket to Work Employment Networks</data><data key="node_acronym">ENs</data><data key="node_domain">External Service Providers</data><data key="node_description">SSA-approved providers that furnish employment and support services to Ticket to Work beneficiaries.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Organizational class, not a single legal entity.</data></node><node id="ORG_EQUIFAX_WS"><data key="node_entity_id">ORG_EQUIFAX_WS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Equifax Workforce Solutions LLC</data><data key="node_acronym">Equifax</data><data key="node_domain">Vendor / External Partner</data><data key="node_description">Payroll data provider currently used by SSA for Payroll Information Exchange.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Directly confirmed by SSA 2026 PIE materials.</data></node><node id="ORG_ESPYR_ACENTRA"><data key="node_entity_id">ORG_ESPYR_ACENTRA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Espyr / Acentra</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_FBI"><data key="node_entity_id">ORG_FBI</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Federal Bureau of Investigation</data><data key="node_acronym">FBI</data><data key="node_domain">External Partner</data><data key="node_description">Federal law-enforcement partner receiving automated NIBRS submissions from SSA OIG.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_FDS"><data key="node_entity_id">ORG_FDS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Federal Disbursement Services</data><data key="node_domain">External Partner / Treasury / Payments</data><data key="node_description">Treasury Fiscal Service component named in the 2026 SSA payment-schedule coordination with Do Not Pay.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled only for the documented payment-schedule coordination; internal organization topology is not inferred beyond Treasury context.</data></node><node id="ORG_FIFTH_THIRD"><data key="node_entity_id">ORG_FIFTH_THIRD</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Fifth Third Bank</data><data key="node_domain">External Partner / Financial Agent</data><data key="node_description">Financial institution selected by Treasury as the new Direct Express financial agent.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-05-19</data><data key="node_confidence">5</data></node><node id="ORG_FIRST_ADVANTAGE"><data key="node_entity_id">ORG_FIRST_ADVANTAGE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">First Advantage</data><data key="node_domain">Vendor / External Partner</data><data key="node_description">Company identified by its primary site as the provider of VerifyAdvantage.</data><data key="node_observed_status">observed_current_vendor</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Vendor relationship is based on the provider's primary site rather than an SSA procurement record.</data></node><node id="ORG_FOUR_POINTS"><data key="node_entity_id">ORG_FOUR_POINTS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Four Points Technology LLC</data><data key="node_acronym">Four Points</data><data key="node_domain">Vendor</data><data key="node_description">Vendor holding SSA's documented commercial cloud services BPA and the 2024 Amazon Connect task order.</data><data key="node_observed_status">documented_awardee_2025</data><data key="node_observed_as_of">2025-06-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_FRBKC"><data key="node_entity_id">ORG_FRBKC</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Federal Reserve Bank of Kansas City</data><data key="node_acronym">FRBKC</data><data key="node_domain">External Partner / Payments</data><data key="node_description">Federal Reserve Bank partner used in SSA International Direct Deposit routing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-25</data><data key="node_confidence">5</data></node><node id="ORG_FRBR"><data key="node_entity_id">ORG_FRBR</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Federal Reserve Bank of Richmond</data><data key="node_acronym">RFRB</data><data key="node_domain">External Partner / Payments</data><data key="node_description">Federal Reserve Bank named in active SSA POMS as the intermediary through which SSA sends Death Notification Entries to U.S. financial institutions.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Routing statement is explicit in active POMS but the detailed DNE section was last revised in 2008, so current implementation technology is not inferred beyond the maintained policy.</data></node><node id="ORG_HIT_PARTNERS"><data key="node_entity_id">ORG_HIT_PARTNERS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Health IT Partner Organizations</data><data key="node_acronym">HIT Partners</data><data key="node_domain">External Partner</data><data key="node_description">Healthcare organizations, HIEs, EHR networks, aggregators, hospitals and practices exchanging electronic medical records with SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-28</data><data key="node_confidence">5</data><data key="node_notes">SSA reported 398 partner organizations and 53,389 participating providers as of 09/14/26.</data></node><node id="ORG_HUD"><data key="node_entity_id">ORG_HUD</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Department of Housing and Urban Development</data><data key="node_acronym">HUD</data><data key="node_domain">External Partner</data><data key="node_description">Federal partner in SSA Computer Matching Agreement 1061 for tenant-reported income verification.</data><data key="node_observed_status">active_matching_partner</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA active matching-program list identifies HUD as partner for CMA 1061.</data></node><node id="ORG_HYPERSCIENCE"><data key="node_entity_id">ORG_HYPERSCIENCE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Hyperscience</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_IBM"><data key="node_entity_id">ORG_IBM</data><data key="node_entity_type">organization</data><data key="node_canonical_name">IBM</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_IMMIXTECH"><data key="node_entity_id">ORG_IMMIXTECH</data><data key="node_entity_type">organization</data><data key="node_canonical_name">immixTechnology, Inc.</data><data key="node_acronym">immixTechnology</data><data key="node_domain">Vendor</data><data key="node_description">Federal contractor receiving SSA's 2026 Pega re-compete award.</data><data key="node_observed_status">observed_current_vendor</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_INFORMATICA"><data key="node_entity_id">ORG_INFORMATICA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Informatica</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_INSIDER_THREAT_RESILIENCY"><data key="node_entity_id">ORG_INSIDER_THREAT_RESILIENCY</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Office of Insider Threat and Resiliency</data><data key="node_domain">Enterprise Security / Insider Threat</data><data key="node_description">SSA office responsible for insider-threat and resiliency functions within the Office of Security and Resiliency.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">OIG identifies this as the principal entity reviewed for the 2026 Insider Threat Program audit.</data></node><node id="ORG_IRS"><data key="node_entity_id">ORG_IRS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Internal Revenue Service</data><data key="node_acronym">IRS</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_IRS_DISCLOSURE_SCANNING_OP"><data key="node_entity_id">ORG_IRS_DISCLOSURE_SCANNING_OP</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">IRS Disclosure Scanning Operation</data><data key="node_acronym">DSO</data><data key="node_domain">External Partner / IRS</data><data key="node_description">IRS operational destination in Atlanta to which SSA sends designated written tax-information requests under current POMS.</data><data key="node_observed_status">observed_current_policy_destination</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Organizational function only; internal IRS system architecture not inferred.</data></node><node id="ORG_IT_IRB"><data key="node_entity_id">ORG_IT_IRB</data><data key="node_entity_type">governance_body</data><data key="node_canonical_name">Information Technology Investment Review Board</data><data key="node_acronym">IT IRB</data><data key="node_domain">Enterprise IT Governance</data><data key="node_description">SSA governance body that votes on IT investment funding and governs the agency IT investment and management process.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">OIG states the board includes the CIO, CFO, and representatives from SSA top-level components; current report covers FY2023-2025 funding decisions.</data></node><node id="ORG_LEIDOS"><data key="node_entity_id">ORG_LEIDOS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Leidos, Inc.</data><data key="node_acronym">Leidos</data><data key="node_domain">Vendor</data><data key="node_description">Historical contractor that provided technical and IT support resources for the SSA DCPS program under a completed federal delivery order.</data><data key="node_observed_status">historical_awardee</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current vendor status is not inferred from the completed award.</data></node><node id="ORG_MEDALLIA"><data key="node_entity_id">ORG_MEDALLIA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Medallia</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_METTEL"><data key="node_entity_id">ORG_METTEL</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Manhattan Telecommunications Corporation, LLC</data><data key="node_acronym">MetTel</data><data key="node_domain">Vendor</data><data key="node_description">Telecommunications contractor documented as providing SSA services under the Grand SLLAM task order.</data><data key="node_observed_status">documented_awardee_2025</data><data key="node_observed_as_of">2025-06-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_MICROSOFT"><data key="node_entity_id">ORG_MICROSOFT</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Microsoft</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_MITRE"><data key="node_entity_id">ORG_MITRE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">The MITRE Corporation</data><data key="node_acronym">MITRE</data><data key="node_domain">Vendor / FFRDC / Technology Advisory</data><data key="node_description">Contractor awarded an SSA delivery order for an independent assessment of SSA network infrastructure and future-state recommendations.</data><data key="node_observed_status">observed_procurement_provider_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Organization role is limited here to the observed 2026 SSA network-assessment award.</data></node><node id="ORG_NAPHSIS"><data key="node_entity_id">ORG_NAPHSIS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">National Association for Public Health Statistics and Information Systems</data><data key="node_acronym">NAPHSIS</data><data key="node_domain">Identity / Vital Records</data><data key="node_description">External partner organization identified by SSA as collaborating on EVVE.</data><data key="node_observed_status">observed_current_partner</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes">Public POMS identifies collaboration; contractual/technical hosting details are not stated.</data></node><node id="ORG_NARA"><data key="node_entity_id">ORG_NARA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">National Archives and Records Administration</data><data key="node_acronym">NARA</data><data key="node_domain">External Partner</data><data key="node_description">Federal records agency and official repository for covered U.S. military personnel records used in SSA military-service verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="ORG_NCHS"><data key="node_entity_id">ORG_NCHS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">National Center for Health Statistics</data><data key="node_acronym">NCHS</data><data key="node_domain">actuarial / external data source</data><data key="node_description">Federal health-statistics organization whose mortality data are used by OCACT in historical and provisional death-rate development.</data><data key="node_observed_status">observed_current_2026_trustees_input</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 Trustees Report identifies NCHS historical, cause-specific, and provisional mortality data as inputs.</data></node><node id="ORG_NEPSC"><data key="node_entity_id">ORG_NEPSC</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Northeastern Program Service Center</data><data key="node_acronym">NEPSC</data><data key="node_domain">Operations / Processing Centers</data><data key="node_description">SSA program service center identified in current POMS as handling the ACDV consumer-dispute process.</data><data key="node_observed_status">observed_current_role_reference</data><data key="node_observed_as_of">2025-05-08</data><data key="node_confidence">5</data><data key="node_notes">Added only for the documented ACDV operational role; no inference about other NEPSC systems or workloads.</data></node><node id="ORG_NIH_CRC_RMD"><data key="node_entity_id">ORG_NIH_CRC_RMD</data><data key="node_entity_type">organization</data><data key="node_canonical_name">NIH Clinical Research Center Rehabilitation Medicine Department</data><data key="node_acronym">NIH CRC/RMD</data><data key="node_domain">Federal Partner / Disability Research</data><data key="node_description">National Institutes of Health Clinical Research Center Rehabilitation Medicine Department, identified in the FAS PIA as the organization conducting the Functional Assessment Study.</data><data key="node_observed_status">documented_current_pia_role</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal partner role is specific to the FAS study documented by the PIA.</data></node><node id="ORG_NTIS"><data key="node_entity_id">ORG_NTIS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">National Technical Information Service</data><data key="node_acronym">NTIS</data><data key="node_domain">External Partner</data><data key="node_description">Department of Commerce service that receives SSA's public death file and distributes the public/Limited Access DMF.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_OAO"><data key="node_entity_id">ORG_OAO</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Appellate Operations</data><data key="node_acronym">OAO</data><data key="node_domain">Appeals Council</data><data key="node_description">SSA component supporting the Appeals Council and federal-court related appellate work.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_OCSE"><data key="node_entity_id">ORG_OCSE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Child Support Enforcement</data><data key="node_acronym">OCSE</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_OHO"><data key="node_entity_id">ORG_OHO</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Hearings Operations</data><data key="node_acronym">OHO</data><data key="node_domain">Hearings &amp; Appeals</data><data key="node_description">SSA component responsible for hearing operations and ALJ adjudication.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_OPENAI"><data key="node_entity_id">ORG_OPENAI</data><data key="node_entity_type">organization</data><data key="node_canonical_name">OpenAI</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_OPLAW"><data key="node_entity_id">ORG_OPLAW</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Program Law</data><data key="node_acronym">OPLaw</data><data key="node_domain">Governance / Legal / Title XVI</data><data key="node_description">SSA legal office consulted by Regional Trust Leads for pooled-trust evaluations before establishing or updating trust precedents.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Named in current SSI trust POMS; organizational placement is not further inferred here.</data></node><node id="ORG_OPM"><data key="node_entity_id">ORG_OPM</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Personnel Management</data><data key="node_acronym">OPM</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_ORSIS"><data key="node_entity_id">ORG_ORSIS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Retirement and Survivors Insurance Systems</data><data key="node_acronym">ORSIS</data><data key="node_domain">Title II / Title XVI / Systems Operations</data><data key="node_description">SSA systems organization identified in POMS as performing automated mass postal change-of-address updates to master files.</data><data key="node_observed_status">documented_current_policy_page_legacy_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">POMS page remains live but its substantive revision predates the 10-year research horizon; current organizational status/name should be revalidated before treating ORSIS as a present-day component.</data></node><node id="ORG_PASS_CADRE"><data key="node_entity_id">ORG_PASS_CADRE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Regional PASS Cadres</data><data key="node_acronym">PASS Cadres</data><data key="node_domain">SSA Internal Operations</data><data key="node_description">Regional PASS specialists/AWICs responsible for PASS development, adjudication, and monitoring.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_PA_AGENCIES"><data key="node_entity_id">ORG_PA_AGENCIES</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Protection and Advocacy System Organizations</data><data key="node_acronym">P&amp;A</data><data key="node_domain">External Partner</data><data key="node_description">State Protection and Advocacy organizations that conduct periodic onsite and other representative-payee reviews and educational visits on SSA behalf.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_PPDX"><data key="node_entity_id">ORG_PPDX</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Program Policy and Data Exchange</data><data key="node_acronym">PPDX</data><data key="node_domain">External Data Exchange / Governance</data><data key="node_description">SSA Law and Policy division serving as the agency focal point for data exchange activities and standardized data-exchange policy and procedures.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-17</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says data exchanges were placed under PPDX in 2026.</data></node><node id="ORG_PRISONS"><data key="node_entity_id">ORG_PRISONS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Federal, State and Local Prisons</data><data key="node_acronym">Prisons</data><data key="node_domain">External Partner</data><data key="node_description">Entities reporting prisoner information to SSA.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_RECLAMATIONS_TEAM"><data key="node_entity_id">ORG_RECLAMATIONS_TEAM</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Reclamations Team</data><data key="node_acronym">Reclaims</data><data key="node_domain">Payments / Internal Control</data><data key="node_description">SSA internal Reclamations Team identified in current POMS as responsible for certain SSI CORE credit corrections and special-voucher reimbursements.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled at the organizational-function level only; exact organizational hierarchy beyond the POMS description is not inferred.</data></node><node id="ORG_ROMANIA_NHPP"><data key="node_entity_id">ORG_ROMANIA_NHPP</data><data key="node_entity_type">organization</data><data key="node_canonical_name">National House of Public Pensions (Romania)</data><data key="node_acronym">NHPP</data><data key="node_domain">External Partner / International</data><data key="node_description">Romanian liaison agency used by SSA for Totalization claims and information exchange.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Romania agreement instructions identify this organization as the Romanian liaison agency.</data></node><node id="ORG_RRB"><data key="node_entity_id">ORG_RRB</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Railroad Retirement Board</data><data key="node_acronym">RRB</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_RTRT"><data key="node_entity_id">ORG_RTRT</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Regional Trust Review Team</data><data key="node_acronym">RTRT</data><data key="node_domain">Title XVI / Resources / Trusts</data><data key="node_description">Regional SSA review function that reviews SSI trust resource determinations submitted by Claims Specialists.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS also identifies trust reviewers and regional trust leads within the review structure.</data></node><node id="ORG_SAU"><data key="node_entity_id">ORG_SAU</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Subsidy Appeals Unit</data><data key="node_acronym">SAU</data><data key="node_domain">SSA Internal Operations</data><data key="node_description">SSA unit involved in MAPS subsidy appeals and manual correction processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_SECURITY_RESILIENCY"><data key="node_entity_id">ORG_SECURITY_RESILIENCY</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Office of Security and Resiliency</data><data key="node_domain">Enterprise Security / Governance</data><data key="node_description">SSA security organization created from a Security and Resiliency consolidation intended to integrate agency security functions, including insider threat.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">OIG says the Commissioner established a Security and Resiliency component in September 2025 and identifies the Office of Security and Resiliency in its 2026 audit scope.</data></node><node id="ORG_SERVICENOW"><data key="node_entity_id">ORG_SERVICENOW</data><data key="node_entity_type">organization</data><data key="node_canonical_name">ServiceNow</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">observed_current_software_provider</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship. FPDS records an SSA FSS BPA for ServiceNow software with ordering through March 29, 2029; Carahsoft is the contract awardee/reseller.</data></node><node id="ORG_SEWP_SOLUTIONS"><data key="node_entity_id">ORG_SEWP_SOLUTIONS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SEWP Solutions LLC</data><data key="node_domain">Technology Procurement / Reseller</data><data key="node_description">Federal contractor holding NASA SEWP V IDV NNG15SC19B, under which SSA placed infrastructure delivery orders.</data><data key="node_observed_status">observed_contract_holder</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">USAspending identifies SEWP Solutions LLC as the recipient for IDV NNG15SC19B.</data></node><node id="ORG_SKILLSOFT_PERCIPIO"><data key="node_entity_id">ORG_SKILLSOFT_PERCIPIO</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Skillsoft / Percipio</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_SSA_BUDGET_FUNCTION"><data key="node_entity_id">ORG_SSA_BUDGET_FUNCTION</data><data key="node_entity_type">organization_function</data><data key="node_canonical_name">SSA Budget Department (Trustees Report Reference)</data><data key="node_acronym">SSA Budget</data><data key="node_domain">SSA Internal / Budget / Actuarial Inputs</data><data key="node_description">Budget function identified in the 2026 Trustees Report as providing estimates for the first several years of the administrative-expense projection.</data><data key="node_observed_status">observed_current_report_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">Entity is intentionally generic because the Trustees Report uses “Budget department” rather than establishing a formal component name.</data></node><node id="ORG_SSA_CENTRAL_PROCESSING"><data key="node_entity_id">ORG_SSA_CENTRAL_PROCESSING</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Central Processing</data><data key="node_acronym">CP</data><data key="node_domain">SSA Internal Operations / Processing Centers</data><data key="node_description">SSA chief-level organization providing centralized oversight of all eight processing centers and managing several backend support functions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA announced the organizational realignment in July 2026; this entity represents the organization, not a technical system.</data></node><node id="ORG_SSA_DIB"><data key="node_entity_id">ORG_SSA_DIB</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Data Integrity Board</data><data key="node_acronym">DIB</data><data key="node_domain">Governance / Data Exchange</data><data key="node_description">SSA governance body whose clearance is required for Computer Matching Agreements under current data-exchange policy.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS requires DIB comments/clearance and DIB Chair signature for CMAs.</data></node><node id="ORG_SSA_FBU"><data key="node_entity_id">ORG_SSA_FBU</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Federal Benefits Units</data><data key="node_acronym">FBU</data><data key="node_domain">International Operations / Customer Service</data><data key="node_description">SSA/embassy or consular units identified as destinations for completed country-specific SSA-1199 International Direct Deposit forms.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Generic organizational concept; individual FBU locations are not enumerated here.</data></node><node id="ORG_SSA_FIELD_OFFICES"><data key="node_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Field Offices</data><data key="node_acronym">FOs</data><data key="node_domain">SSA Internal Operations</data><data key="node_description">SSA field offices that receive matched cases from program-integrity data exchanges for review and development.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Generic organizational class used for workflow mapping; individual office locations are not instantiated in this pass.</data></node><node id="ORG_SSA_FS"><data key="node_entity_id">ORG_SSA_FS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Office of Financial Statements</data><data key="node_acronym">FS</data><data key="node_domain">Finance / Payments</data><data key="node_description">SSA finance unit responsible for processing SERS non-programmatic refund requests and certain foreign-institution checks.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_SSA_ISB"><data key="node_entity_id">ORG_SSA_ISB</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">International Support Branch</data><data key="node_acronym">ISB</data><data key="node_domain">International / Totalization</data><data key="node_description">SSA branch identified as the contact point for U.S. certificate-of-coverage requests under the U.S.-Romania agreement.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Transport, persistence, and backend implementation are not disclosed by the public policy.</data></node><node id="ORG_SSA_OAG"><data key="node_entity_id">ORG_SSA_OAG</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Acquisition and Grants</data><data key="node_acronym">OAG</data><data key="node_domain">Procurement / Grants</data><data key="node_description">SSA organization responsible for agency-wide acquisition and grants programs and identified by SSA as its principal procurement office.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG page establishes role; no internal system topology is inferred.</data></node><node id="ORG_SSA_OAS"><data key="node_entity_id">ORG_SSA_OAS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Acquisition Support</data><data key="node_acronym">OAS</data><data key="node_domain">Procurement / Policy and Cost Analysis</data><data key="node_description">OAG component providing acquisition policy and cost-analysis audit support and administering the purchase card program.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current OAG organizational page; acronym used only as shorthand within Atlas and may overlap with other SSA uses.</data></node><node id="ORG_SSA_OCACT"><data key="node_entity_id">ORG_SSA_OCACT</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of the Chief Actuary</data><data key="node_acronym">OCACT</data><data key="node_domain">Actuarial / Trust Funds</data><data key="node_description">SSA organization responsible for actuarial estimates and projections supporting the OASDI trust funds and related program analysis.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Mapped from the current 2026 Trustees Report methodology; no internal software architecture is inferred from the organizational role.</data></node><node id="ORG_SSA_OEIO"><data key="node_entity_id">ORG_SSA_OEIO</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Office of Earnings and International Operations</data><data key="node_acronym">OEIO</data><data key="node_domain">International Operations / Payments</data><data key="node_description">SSA component identified in current international direct-deposit procedures as a processing and contact point for enrollment requests.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current page names OEIO; no internal application is inferred.</data></node><node id="ORG_SSA_OFPO"><data key="node_entity_id">ORG_SSA_OFPO</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Financial Policy and Operations</data><data key="node_acronym">OFPO</data><data key="node_domain">SSA Internal / Finance</data><data key="node_description">SSA office whose analysts use MCAS for essential cost-accounting functions.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-08-06</data><data key="node_confidence">5</data><data key="node_notes">Organization name is taken directly from current Data.gov metadata; this run does not infer its broader organizational placement.</data></node><node id="ORG_SSA_OGC"><data key="node_entity_id">ORG_SSA_OGC</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Office of the General Counsel</data><data key="node_acronym">OGC</data><data key="node_domain">Enterprise / Legal / Governance</data><data key="node_description">SSA legal office identified in Data Exchange guidance as providing clearance for Interagency Agreement packages.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Organizational role only; internal substructure is not inferred.</data></node><node id="ORG_SSA_OIG"><data key="node_entity_id">ORG_SSA_OIG</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Social Security Administration Office of the Inspector General</data><data key="node_acronym">SSA OIG</data><data key="node_domain">Program Integrity / Investigations</data><data key="node_description">Independent SSA oversight organization conducting criminal investigations, audits, CDI operations, and fraud-related analytics.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_SSA_OITA"><data key="node_entity_id">ORG_SSA_OITA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Information Technology Acquisition</data><data key="node_acronym">OITA</data><data key="node_domain">Procurement / Information Technology</data><data key="node_description">OAG component responsible for acquisition of information technology products and related services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG page identifies OITA and its IT acquisition responsibility.</data></node><node id="ORG_SSA_OOC"><data key="node_entity_id">ORG_SSA_OOC</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Operations Contracts</data><data key="node_acronym">OOC</data><data key="node_domain">Procurement / Non-IT</data><data key="node_description">OAG component responsible for acquisition of headquarters and regional facilities services and other non-IT products and services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current OAG organizational page.</data></node><node id="ORG_SSA_OPD"><data key="node_entity_id">ORG_SSA_OPD</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Office of Privacy and Disclosure</data><data key="node_acronym">OPD</data><data key="node_domain">Privacy / IRS Data</data><data key="node_description">Office responsible for coordinating IRS notification after suspected or confirmed federal tax information disclosure; monitors SSA Loss Reporting Tool.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_SSA_OQI"><data key="node_entity_id">ORG_SSA_OQI</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Office of Quality Improvement</data><data key="node_acronym">OQI</data><data key="node_domain">SSA Internal / Program Integrity / Quality</data><data key="node_description">SSA office named in the current CMA cost-benefit attachment as developer of the DIFSLA profiling module.</data><data key="node_observed_status">historical_or_current_role_uncertain</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">4</data><data key="node_notes">The attachment establishes the development role but does not establish whether OQI retains the same organizational placement/name in 2026.</data></node><node id="ORG_SSA_ORES"><data key="node_entity_id">ORG_SSA_ORES</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Office of Research, Evaluation, and Statistics</data><data key="node_acronym">ORES</data><data key="node_domain">Research / Statistics / Policy</data><data key="node_description">SSA research and statistics organization publishing MINT methodology and distributional projection products.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA MINT overview identifies this office; organizational placement beyond the public page is not inferred.</data></node><node id="ORG_SSA_RQ_GAP"><data key="node_entity_id">ORG_SSA_RQ_GAP</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Risk and Quality Governance and Performance Review</data><data key="node_acronym">RQ/GAP</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">RQ/GAP reviewers assess proposed high-dollar waiver approvals of $20,000 or more and complete final second PIN review per policy.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_SSA_SDRM"><data key="node_entity_id">ORG_SSA_SDRM</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">State Disability Resource Management Division</data><data key="node_acronym">SDRM</data><data key="node_domain">Disability / DDS / Financial Management</data><data key="node_description">SSA Disability Adjudication component identified as distributing State DDS financial-management forms electronically and through an internal intranet site.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source identifies the organizational role; no separate IT system is inferred for the division itself.</data></node><node id="ORG_STATES"><data key="node_entity_id">ORG_STATES</data><data key="node_entity_type">organization</data><data key="node_canonical_name">State Agencies</data><data key="node_acronym">States</data><data key="node_domain">External Partner</data><data key="node_description">State agencies participating in SSA data exchange and matching.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_STATE_AE"><data key="node_entity_id">ORG_STATE_AE</data><data key="node_entity_type">organization</data><data key="node_canonical_name">State Affordable Insurance Exchanges</data><data key="node_acronym">State AEs</data><data key="node_domain">External Partner</data><data key="node_description">State Affordable Insurance Exchanges that use the CMS Hub for eligibility-verification data.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-09</data><data key="node_confidence">5</data><data key="node_notes">CMA 1097 identifies state AEs as consumers of trusted data source results through the Hub.</data></node><node id="ORG_STATE_BVS"><data key="node_entity_id">ORG_STATE_BVS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">State Bureaus of Vital Statistics / Vital Records Agencies</data><data key="node_acronym">State BVS</data><data key="node_domain">External Partner</data><data key="node_description">State and local vital-record authorities transmitting birth/death information used in SSA enumeration/death processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_STATE_DMV"><data key="node_entity_id">ORG_STATE_DMV</data><data key="node_entity_type">organization</data><data key="node_canonical_name">State Departments of Motor Vehicles</data><data key="node_acronym">DMV</data><data key="node_domain">External Partners / Address &amp; Identity</data><data key="node_description">Generic state motor-vehicle agencies documented by SSA as a debtor-location resource during skiptracing.</data><data key="node_observed_status">documented_operational_resource</data><data key="node_observed_as_of">2025-11-20</data><data key="node_confidence">4</data><data key="node_notes">Generic partner class, not a claim of one nationwide SSA-DMV interface or AAMVA-mediated transport.</data></node><node id="ORG_STATE_MEDICAID"><data key="node_entity_id">ORG_STATE_MEDICAID</data><data key="node_entity_type">organization</data><data key="node_canonical_name">State Medicaid Agencies</data><data key="node_acronym">State Medicaid</data><data key="node_domain">External Partner</data><data key="node_description">State agencies that determine Medicaid/MSP eligibility and receive SSA referral information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_STATE_VR_AGENCIES"><data key="node_entity_id">ORG_STATE_VR_AGENCIES</data><data key="node_entity_type">organization</data><data key="node_canonical_name">State Vocational Rehabilitation Agencies</data><data key="node_acronym">State VR Agencies</data><data key="node_domain">External Government Partners</data><data key="node_description">State government components administering public vocational-rehabilitation programs and participating in SSA Ticket/VR reimbursement processes.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Organizational class covering state/territorial VR agencies.</data></node><node id="ORG_STERLING_COMPUTERS"><data key="node_entity_id">ORG_STERLING_COMPUTERS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Sterling Computers Corporation</data><data key="node_acronym">Sterling Computers</data><data key="node_domain">Vendor / Infrastructure</data><data key="node_description">Technology reseller/integrator holding the NASA SEWP V IDV under which SSA placed a 2026 Data Replication Network delivery order.</data><data key="node_observed_status">observed_current_vendor</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Legal business name shown on USAspending IDV record.</data></node><node id="ORG_SVB_CPS"><data key="node_entity_id">ORG_SVB_CPS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Special Veterans Benefits Central Processing Sites</data><data key="node_acronym">SVB CPS</data><data key="node_domain">SSA Internal Operations</data><data key="node_description">Designated SSA central processing sites responsible for SVB applications filed abroad and post-residency case actions.</data><data key="node_observed_status">current_poms_retained_detailed_topology_old</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="ORG_TIBCO"><data key="node_entity_id">ORG_TIBCO</data><data key="node_entity_type">organization</data><data key="node_canonical_name">TIBCO</data><data key="node_acronym">TIBCO</data><data key="node_domain">Vendor / Integration Software</data><data key="node_description">Software vendor identified by SSA as developer and support provider for the Managed File Transfer product used with State Transmission Components.</data><data key="node_observed_status">documented_current_vendor_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">The public SSA FAQ documents an SSA-TIBCO licensing arrangement but does not disclose contract identifier, version, or current reseller.</data></node><node id="ORG_TOTALIZATION_PARTNERS"><data key="node_entity_id">ORG_TOTALIZATION_PARTNERS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Totalization Partner Countries</data><data key="node_domain">External Partner</data><data key="node_description">Foreign countries with U.S. Social Security totalization agreements participating in relevant data exchanges.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current GSO lists a service for totalization partner countries.</data></node><node id="ORG_TRANSUNION"><data key="node_entity_id">ORG_TRANSUNION</data><data key="node_entity_type">organization</data><data key="node_canonical_name">TransUnion</data><data key="node_acronym">TransUnion</data><data key="node_domain">Vendor / Telecommunications / Fraud Prevention</data><data key="node_description">Commercial provider named in SSA procurement records for outbound-call spoof-proofing and call-branding capability.</data><data key="node_observed_status">observed_procurement_provider_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Provider association is explicit in the government award description reproduced by federal-award data mirrors. No broader SSA relationship is inferred.</data></node><node id="ORG_TREASURY"><data key="node_entity_id">ORG_TREASURY</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Department of the Treasury</data><data key="node_acronym">Treasury</data><data key="node_domain">External Partner</data><data key="node_description">Federal department receiving SSI payment files and providing payment-related input to SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_TREASURY_OTA"><data key="node_entity_id">ORG_TREASURY_OTA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Department of the Treasury Office of Tax Analysis</data><data key="node_acronym">OTA</data><data key="node_domain">External Partner / Treasury / Actuarial Inputs</data><data key="node_description">Treasury office whose estimates are used by SSA Actuarial Services in projecting OASDI trust-fund income from taxation of benefits.</data><data key="node_observed_status">observed_current_report_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Role documented directly by the 2026 Trustees Report.</data></node><node id="ORG_TRIBAL_ENTITIES"><data key="node_entity_id">ORG_TRIBAL_ENTITIES</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Tribal Entities</data><data key="node_domain">External Partner</data><data key="node_description">Generic partner class for tribal entities participating with SSA under model computer matching agreement 6004.</data><data key="node_observed_status">active_matching_partner</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Represents partner scope, not a single tribal government.</data></node><node id="ORG_USAO"><data key="node_entity_id">ORG_USAO</data><data key="node_entity_type">organization</data><data key="node_canonical_name">United States Attorney's Office</data><data key="node_acronym">USAO</data><data key="node_domain">External Partner / Federal Court Litigation</data><data key="node_description">United States Attorney office receiving/routing Social Security certified administrative records for federal district court litigation.</data><data key="node_observed_status">observed_current_partner</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled as an external litigation partner category; individual district offices are not enumerated here.</data></node><node id="ORG_USCIS"><data key="node_entity_id">ORG_USCIS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">U.S. Citizenship and Immigration Services</data><data key="node_acronym">USCIS</data><data key="node_domain">External Partner</data><data key="node_description">DHS component providing EAE/EBE enumeration data and participating in E-Verify.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_USDA_FNS"><data key="node_entity_id">ORG_USDA_FNS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">USDA Food and Nutrition Service</data><data key="node_acronym">FNS</data><data key="node_domain">External Partner / Nutrition Assistance</data><data key="node_description">Department of Agriculture component participating with States and SSA in the Combined Application Project.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-08-04</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_USPS"><data key="node_entity_id">ORG_USPS</data><data key="node_entity_type">organization</data><data key="node_canonical_name">United States Postal Service</data><data key="node_acronym">USPS</data><data key="node_domain">External Partner / Address</data><data key="node_description">Federal postal service that supplies National Change of Address information, mass address/ZIP changes, and address-location responses used in SSA address workflows.</data><data key="node_observed_status">observed_current_partner</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_US_BANK"><data key="node_entity_id">ORG_US_BANK</data><data key="node_entity_type">organization</data><data key="node_canonical_name">U.S. Bank</data><data key="node_domain">External Partner</data><data key="node_description">Treasury financial agent identified in SSA POMS as processing lockbox remittances and depositing funds for the government.</data><data key="node_observed_status">documented_lockbox_financial_agent</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Relationship is based on SSA lockbox operating instructions; current Treasury financial-agent arrangements should be periodically revalidated.</data></node><node id="ORG_VA"><data key="node_entity_id">ORG_VA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">U.S. Department of Veterans Affairs</data><data key="node_acronym">VA</data><data key="node_domain">External Partners / Veterans</data><data key="node_description">Federal department that identifies veterans receiving 100 percent permanent and total disability compensation and provides SSA weekly information through an automated data exchange.</data><data key="node_observed_status">observed_current_partner</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS names VA as the source. Component-level ownership of this specific feed is not asserted.</data></node><node id="ORG_VBA"><data key="node_entity_id">ORG_VBA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Veterans Benefits Administration</data><data key="node_acronym">VBA</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_VERIZON"><data key="node_entity_id">ORG_VERIZON</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Verizon Business Network Services, Inc.</data><data key="node_acronym">Verizon</data><data key="node_domain">Vendor</data><data key="node_description">Contractor for SSA's Next Generation Telephony Project.</data><data key="node_observed_status">historical_ngtp_vendor</data><data key="node_observed_as_of">2025-04-23</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_VHA"><data key="node_entity_id">ORG_VHA</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Veterans Health Administration</data><data key="node_acronym">VHA</data><data key="node_domain">External Partner</data><data key="node_description">Federal computer-matching partner.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="ORG_VYOND"><data key="node_entity_id">ORG_VYOND</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Vyond</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_WBDOC"><data key="node_entity_id">ORG_WBDOC</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Wilkes-Barre Data Operations Center</data><data key="node_acronym">WBDOC</data><data key="node_domain">SSA Internal Operations</data><data key="node_description">SSA operations center historically documented as receiving paper wage reports and converting them to electronic wage data for AWR.</data><data key="node_observed_status">documented_architecture</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Detailed source is older; current paper filing remains available but current routing has not been revalidated in this pass.</data></node><node id="ORG_WESTAT"><data key="node_entity_id">ORG_WESTAT</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Westat</data><data key="node_domain">External Partner / Disability Research</data><data key="node_description">External survey/research organization that built and hosts the Functional Assessment Study Calibration SMS and collects participant information under the study chain.</data><data key="node_observed_status">documented_current_pia_role</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">PIA names Westat as an external survey center; no broader SSA-wide vendor relationship is inferred.</data></node><node id="ORG_WINDSURF"><data key="node_entity_id">ORG_WINDSURF</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Windsurf</data><data key="node_domain">Technology Ecosystem / AI Vendor</data><data key="node_description">External technology provider named in SSA's 2025 public AI use-case inventory.</data><data key="node_observed_status">named_vendor_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Vendor association is use-case-specific and does not imply an enterprise-wide or exclusive relationship.</data></node><node id="ORG_WSU"><data key="node_entity_id">ORG_WSU</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Workload Support Units</data><data key="node_acronym">WSU</data><data key="node_domain">SSA Internal Operations</data><data key="node_description">SSA units assigned MAPS verification workload.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PAY_USDC"><data key="node_entity_id">PAY_USDC</data><data key="node_entity_type">payment_instrument</data><data key="node_canonical_name">United States Debit Card</data><data key="node_acronym">USDC</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Electronic debit-card payment instrument used by SSA through TPPS for Emergency Advance Payments and Immediate Payments effective 2026-02-09.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Public POMS does not identify the card network, processor, issuing bank, or internal TPPS implementation; none is inferred.</data></node><node id="PLAT_ACI_2016"><data key="node_entity_id">PLAT_ACI_2016</data><data key="node_entity_type">cloud_platform</data><data key="node_canonical_name">Agency Cloud Infrastructure</data><data key="node_acronym">ACI</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">SSA cloud platform architecture used to provision compute, storage, and network resources for modern development and data platforms, including MDE, BORG CED, and EDW.</data><data key="node_observed_status">historically_authorized_fy2016</data><data key="node_observed_as_of">2016-11-16</data><data key="node_confidence">5</data><data key="node_notes">SSA said the pilot used Amazon Web Services and testified that ACI received SSA's first provisional cloud ATO in FY2016. Current 2026 deployment status is not inferred.</data></node><node id="PLAT_ADDS"><data key="node_entity_id">PLAT_ADDS</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Analytics and Disability Decision Support</data><data key="node_acronym">ADDS</data><data key="node_domain">Disability / Decision Support</data><data key="node_description">SSA disability analytics/decision-support investment that includes IMAGEN.</data><data key="node_observed_status">observed_active_investment</data><data key="node_observed_as_of">2025-06-26</data><data key="node_confidence">5</data><data key="node_notes">GAO says investment began in 2017 and is expected to complete in March 2027.</data></node><node id="PLAT_AVERISOURCE"><data key="node_entity_id">PLAT_AVERISOURCE</data><data key="node_entity_type">platform</data><data key="node_canonical_name">AveriSource Platform</data><data key="node_domain">Application Development / Modernization</data><data key="node_description">Vendor platform identified as the authorized system for SSA intelligent code modernization.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="PLAT_BSO"><data key="node_entity_id">PLAT_BSO</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Business Services Online</data><data key="node_acronym">BSO</data><data key="node_domain">Employer Services</data><data key="node_description">SSA external-service gateway/suite for employer wage reporting and SSN verification, organizational representative-payee reporting, appointed-representative access, and consent-based SSN verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current SSA employer-services guidance continues to direct employers to BSO for wage-report name/SSN error retrieval and correction workflows.</data></node><node id="PLAT_CMS_FDSH"><data key="node_entity_id">PLAT_CMS_FDSH</data><data key="node_entity_type">platform</data><data key="node_canonical_name">CMS Federal Data Services Hub</data><data key="node_acronym">Federal Data Services Hub</data><data key="node_domain">External Data Exchange / CMS</data><data key="node_description">CMS hub platform through which CMS and state Affordable Insurance Exchanges access trusted data-source verification results.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-09</data><data key="node_confidence">5</data><data key="node_notes">CMA 1097 CBA states state AEs access trusted-data-source data through the Hub rather than directly.</data></node><node id="PLAT_EBI"><data key="node_entity_id">PLAT_EBI</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Enterprise Business Intelligence Platform</data><data key="node_acronym">EBI</data><data key="node_domain">Enterprise Data / Research &amp; Statistics</data><data key="node_description">SSA enterprise business-intelligence platform described as providing analytics and data-integration tools for efficient access to and analysis of agency records.</data><data key="node_observed_status">observed_current_budget_program</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">FY2027 Congressional Justification describes EBI-supported data development and planned enhanced EBI tools. Product/vendor stack is not publicly identified.</data></node><node id="PLAT_EDIB"><data key="node_entity_id">PLAT_EDIB</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Electronic Disability System</data><data key="node_acronym">eDIB</data><data key="node_domain">Disability / Electronic Case Processing</data><data key="node_description">Major application / authorization boundary consisting of interrelated subsystems supporting electronic disability intake, development, adjudication, hearings and appeals.</data><data key="node_observed_status">observed_operational_framework</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">2018 PIA remains in current PIA catalog and current POMS continues to use eDIB/electronic-folder concepts. Individual subsystem status is evaluated separately.</data></node><node id="PLAT_EDIB_CLOUD"><data key="node_entity_id">PLAT_EDIB_CLOUD</data><data key="node_entity_type">platform</data><data key="node_canonical_name">eDIB Cloud</data><data key="node_domain">Disability / Cloud</data><data key="node_description">Authorized system named in the SSA AI inventory for the Vocational Assessment Assistant Tool (VAAT).</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Modeled separately from the existing eDIB platform because the public inventory specifically names eDIB Cloud and does not establish that the two are architecturally identical.</data></node><node id="PLAT_ICON_HUB"><data key="node_entity_id">PLAT_ICON_HUB</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Interstate Connection Network Hub</data><data key="node_acronym">ICON Hub</data><data key="node_domain">External Data Exchange / Labor</data><data key="node_description">Department of Labor network hub used for interstate benefit and unemployment-insurance data exchange.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">Current UIQ inventory explicitly identifies the DOL ICON Hub.</data></node><node id="PLAT_INFORMATICA_EDC"><data key="node_entity_id">PLAT_INFORMATICA_EDC</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Informatica Enterprise Data Catalog</data><data key="node_acronym">EDC</data><data key="node_domain">Enterprise Data / Catalog</data><data key="node_description">Enterprise Data Catalog identified as the authorized system for the Data Governance Product use case.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Status and scope reflect the public 2025 SSA AI inventory as consolidated by OMB in April 2026; the inventory may not expose the full system boundary.</data></node><node id="PLAT_MDE"><data key="node_entity_id">PLAT_MDE</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Modern Development Environment</data><data key="node_acronym">MDE</data><data key="node_domain">Application Development / Cloud</data><data key="node_description">Suite of tools and engineering practices SSA established to support modern software development.</data><data key="node_observed_status">historically_documented_aws_platform</data><data key="node_observed_as_of">2016-05-26</data><data key="node_confidence">4</data><data key="node_notes">SSA testified in 2016 that MDE was established in AWS. No claim is made that the 2016 MDE boundary or toolchain is unchanged in 2026.</data></node><node id="PLAT_MODERN_DATA_LAYER"><data key="node_entity_id">PLAT_MODERN_DATA_LAYER</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Modern Data Layer</data><data key="node_acronym">MDL</data><data key="node_domain">Enterprise Data / Integration</data><data key="node_description">SSA modernization initiative intended to create centralized customer-oriented data products connecting front-end applications with backend data stores.</data><data key="node_observed_status">fy2026_budgeted_modernization</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Budget evidence establishes the initiative and design intent; this run does not claim a completed production deployment.</data></node><node id="PLAT_MS_TEAMS"><data key="node_entity_id">PLAT_MS_TEAMS</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Microsoft Teams</data><data key="node_acronym">MS Teams</data><data key="node_domain">Technology / Collaboration</data><data key="node_description">Third-party collaboration/video platform used by SSA for online video hearings.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PLAT_N8NN_CCAAS"><data key="node_entity_id">PLAT_N8NN_CCAAS</data><data key="node_entity_type">platform_category</data><data key="node_canonical_name">National 800 Number Contact Center as a Service</data><data key="node_acronym">N8NN CCaaS</data><data key="node_domain">Customer Service / Telephony / Cloud Contact Center</data><data key="node_description">CCaaS category included in National 800 Number performance metrics beginning March 23, 2023.</data><data key="node_observed_status">documented_metric_scope</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">This generic category does not by itself identify the provider. Separate Atlas evidence establishes the later Amazon Connect transition.</data></node><node id="PLAT_NETWORK"><data key="node_entity_id">PLAT_NETWORK</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Enterprise Wide Mainframe &amp; Distributed Network Telecommunications Services System</data><data key="node_domain">Infrastructure / Network</data><data key="node_description">System/application/project listed in SSA's current PIA catalog; PIA signed 2008-09-08.</data><data key="node_observed_status">listed_in_current_pia_catalog</data><data key="node_observed_as_of">2008-09-08</data><data key="node_confidence">4</data><data key="node_notes">Catalog placement is evidence of a non-retired PIA listing, not by itself proof of current production status.</data></node><node id="PLAT_NGTP"><data key="node_entity_id">PLAT_NGTP</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Next Generation Telephony Project</data><data key="node_acronym">NGTP</data><data key="node_domain">Customer Service / Telephone</data><data key="node_description">SSA telephony modernization platform intended as a unified communications solution replacing legacy telephone systems.</data><data key="node_observed_status">abandoned_for_n8nn_2024</data><data key="node_observed_as_of">2025-04-23</data><data key="node_confidence">5</data><data key="node_notes">OIG says SSA transitioned the National 800 Number away from NGTP on 2024-08-22 after about ten months of use.</data></node><node id="PLAT_NUANCE_IVR"><data key="node_entity_id">PLAT_NUANCE_IVR</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Nuance IVR System</data><data key="node_acronym">Nuance IVR</data><data key="node_domain">Customer Service / Telephony</data><data key="node_description">Interactive voice response system referenced by SSA's current Nuance Application Reporting inventory record.</data><data key="node_observed_status">referenced_by_current_inventory</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">4</data><data key="node_notes">Existence is directly referenced, but no standalone current SSA catalog record or detailed architecture was located in this run.</data></node><node id="PLAT_SHAREPOINT"><data key="node_entity_id">PLAT_SHAREPOINT</data><data key="node_entity_type">platform</data><data key="node_canonical_name">SharePoint</data><data key="node_domain">Enterprise Collaboration / Records</data><data key="node_description">Agency repository platform explicitly cited by SSA for maintaining representative conduct information.</data><data key="node_observed_status">observed_current_enterprise_use</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Only the representative-conduct repository use is established here; enterprise deployment scope/version is not inferred. FY2027 Congressional Justification reports FY2025 upgrading, testing and migration of OASDI, SSI and earnings-related statistical-publication tasks with SharePoint.</data></node><node id="PLAT_TP_CYBER_RISK_MON"><data key="node_entity_id">PLAT_TP_CYBER_RISK_MON</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Third-Party Cyber Risk Monitoring Platform</data><data key="node_domain">Cybersecurity / Third-Party Risk</data><data key="node_description">Agency-selected platform used as a specialized due-diligence tool in SSA third-party cybersecurity risk assessments and continuous monitoring.</data><data key="node_observed_status">observed_current_product_unspecified</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA publicly names the functional platform but not its commercial product, vendor, hosting, or interfaces.</data></node><node id="PORTAL_DEEMING_LISTINGS"><data key="node_entity_id">PORTAL_DEEMING_LISTINGS</data><data key="node_entity_type">internal_portal</data><data key="node_canonical_name">Deeming Listings Page</data><data key="node_acronym">Deeming Listings</data><data key="node_domain">Title XVI / Deeming / Work Control</data><data key="node_description">Internal read-only web page where SSA posts the annual October list of manual-deeming cases that require field-office manual payment computations.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS states these cases are not controlled by SUMS/MCAS MI Central and have no SSR diary.</data></node><node id="PORTAL_SSA_DIGITAL_LIBRARY"><data key="node_entity_id">PORTAL_SSA_DIGITAL_LIBRARY</data><data key="node_entity_type">internal_portal</data><data key="node_canonical_name">SSA Digital Library Electronic Resources Site</data><data key="node_acronym">SSA Digital Library</data><data key="node_domain">Enterprise Knowledge / External Data Access</data><data key="node_description">SSA internal electronic-resources portal used to access subscription resources including J.D. Power Values Online.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Public POMS documents the portal and navigation path; implementation, authentication, and hosting are not disclosed.</data></node><node id="PORTAL_SSA_OPEN_DATA"><data key="node_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="node_entity_type">public_portal</data><data key="node_canonical_name">SSA Open Data Portal</data><data key="node_domain">Enterprise Data / Open Data</data><data key="node_description">SSA public portal for discovering data assets and accessing publicly releasable SSA data and associated metadata.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The portal distinguishes public release from protected SSA administrative data and points users to the Federal Data Catalog for the comprehensive inventory.</data></node><node id="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="node_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="node_entity_type">portal</data><data key="node_canonical_name">SUMS/MCAS MI Central</data><data key="node_acronym">MI Central</data><data key="node_domain">Title XVI / Management Information</data><data key="node_description">SSA SUMS/MCAS management-information portal used to retrieve redetermination/limited-issue workload and alert data.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS describes IRS and pension alert data as retrievable through SUMS/MCAS MI Central and points users to the MI Central Page.</data></node><node id="PROC_1634_MEDICAID"><data key="node_entity_id">PROC_1634_MEDICAID</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Medicaid Eligibility Determination under Section 1634</data><data key="node_acronym">Section 1634 Medicaid</data><data key="node_domain">Title XVI / Medicaid / State Coordination</data><data key="node_description">Process under which SSA makes Medicaid eligibility determinations for qualifying SSI/State supplementary payment recipients in States with a section 1634 agreement.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a program process governed by State agreements; no undocumented exchange file or system is inferred.</data></node><node id="PROC_ACQ360_SURVEY"><data key="node_entity_id">PROC_ACQ360_SURVEY</data><data key="node_entity_type">process</data><data key="node_canonical_name">Acquisition 360 Voluntary Survey</data><data key="node_acronym">Acquisition 360</data><data key="node_domain">Procurement / Acquisition Feedback</data><data key="node_description">SSA acquisition feedback process using FAR provision 52.201-1 in qualifying solicitations posted to SAM.gov; vendor responses are voluntary and anonymous.</data><data key="node_observed_status">observed_current_guidance</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG requires the provision for IT acquisitions over the simplified acquisition threshold and non-IT acquisitions above $10 million estimated life value; encouraged elsewhere.</data></node><node id="PROC_ADMIN_OFFSET"><data key="node_entity_id">PROC_ADMIN_OFFSET</data><data key="node_entity_type">process</data><data key="node_canonical_name">Administrative Offset</data><data key="node_domain">Debt &amp; External Collections</data><data key="node_description">Reduction or withholding of eligible Federal or State payments to collect delinquent SSA debt.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_ADMIN_SANCTIONS"><data key="node_entity_id">PROC_ADMIN_SANCTIONS</data><data key="node_entity_type">process</data><data key="node_canonical_name">Administrative Sanctions Processing</data><data key="node_acronym">Administrative Sanctions</data><data key="node_domain">Program Integrity / Administrative Sanctions</data><data key="node_description">SSA process for imposing or deferring sanctions across Title II and Title XVI and recording the sanction period.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_ADRP_CONTACT"><data key="node_entity_id">PROC_ADRP_CONTACT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">ADRP Advance Designee Contact Development</data><data key="node_domain">Payee / Person Identity</data><data key="node_description">Ordered contact and documentation process for possible future representative payees with minimum contact attempts and confidentiality controls.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_AERO"><data key="node_entity_id">PROC_AERO</data><data key="node_entity_type">process</data><data key="node_canonical_name">Automated Earnings Reappraisal Operation</data><data key="node_acronym">AERO</data><data key="node_domain">Title II / Benefit Recalculation</data><data key="node_description">Post-entitlement earnings reappraisal process used to recompute benefit amounts after earnings changes; legacy AJS-1 system functionality was incorporated into T2R.</data><data key="node_observed_status">observed_current_process</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS still refers to pending and completed AERO actions; represented as a process rather than a separate current system.</data></node><node id="PROC_AFI_GEOREQUEST"><data key="node_entity_id">PROC_AFI_GEOREQUEST</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">e4641 GeoRequest Financial Institution Search</data><data key="node_acronym">GeoRequest</data><data key="node_domain">Title II / Title XVI / Financial Verification</data><data key="node_description">e4641 function allowing up to twelve financial-institution searches in the geographic area where an overpaid individual resides for waiver development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Residence is used to scope the financial-institution search. This does not establish an address update to a master SSA record.</data></node><node id="PROC_ANOMALOUS_WAGE_REVIEW"><data key="node_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Anomalous Electronic Wage Reporting Review</data><data key="node_acronym">Anomalous Wage Review</data><data key="node_domain">Earnings / Program Integrity</data><data key="node_description">SSA process for holding, investigating, accepting/rejecting, and potentially sanctioning anomalous electronic annual wage reports and misuse of electronic wage-reporting services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS applies to SSA electronic wage reporting services and preserves a hold/investigation boundary before suspect wage reports post to earnings records.</data></node><node id="PROC_AOTP"><data key="node_entity_id">PROC_AOTP</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">Automated One-Time Payment</data><data key="node_acronym">A-OTP</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Title XVI one-time payment process used when the SSI system can issue an automated one-time payment; successful A-OTP issuance is annotated on the SSR.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a payment process, not as a standalone application, because current public policy does not name a separate A-OTP application.</data></node><node id="PROC_APRYSE_RENEWAL_2026"><data key="node_entity_id">PROC_APRYSE_RENEWAL_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Apryse PDFTron PDFNet SDK Renewal Solicitation 28321326Q00000144</data><data key="node_domain">Procurement / Document Processing</data><data key="node_description">SSA solicitation for a 12-month software renewal of Apryse PDFTron PDFNet SDK to support DCE.</data><data key="node_observed_status">solicitation_closed</data><data key="node_observed_as_of">2026-05-06</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a solicitation only; no awardee, award value, or contract performance is inferred.</data></node><node id="PROC_AUTO_ENUM_SCREEN"><data key="node_entity_id">PROC_AUTO_ENUM_SCREEN</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Automated Enumeration Screening Process</data><data key="node_domain">Identity / Enumeration / External Verification</data><data key="node_description">SSA Numident verification process/system used for newborn SSN requests submitted through Enumeration at Birth and Department of Homeland Security applications for new and replacement SSNs.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">OIG lists it among five Numident verification systems reviewed in 2026; SSA could not provide management-information reports for it. Physical implementation and interfaces are not disclosed.</data></node><node id="PROC_AWG"><data key="node_entity_id">PROC_AWG</data><data key="node_entity_type">process</data><data key="node_canonical_name">Administrative Wage Garnishment</data><data key="node_acronym">AWG</data><data key="node_domain">Debt &amp; External Collections</data><data key="node_description">Administrative collection process under which employers withhold eligible delinquent SSA debts from disposable wages.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_AWI_CALC"><data key="node_entity_id">PROC_AWI_CALC</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">Average Wage Index Calculation</data><data key="node_acronym">AWI Calculation</data><data key="node_domain">Actuarial / Statistical Production</data><data key="node_description">OACT calculation process that applies growth in current-year versus prior-year raw average wages to the previous AWI to produce the next national Average Wage Index.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OACT methodology is captured at the formula level; implementation software and production platform are not disclosed.</data></node><node id="PROC_AWR"><data key="node_entity_id">PROC_AWR</data><data key="node_entity_type">process</data><data key="node_canonical_name">Annual Wage Reporting</data><data key="node_acronym">AWR</data><data key="node_domain">Earnings</data><data key="node_description">SSA process for receiving, validating, processing and posting annual employer wage reports.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_BL_PARTC_OFFSET"><data key="node_entity_id">PROC_BL_PARTC_OFFSET</data><data key="node_entity_type">process</data><data key="node_canonical_name">Black Lung Part C Offset Processing</data><data key="node_acronym">BL Part C offset</data><data key="node_domain">Title II / Workers Compensation</data><data key="node_description">SSA processing of Black Lung Part C as workers compensation for Title II offset purposes.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Detailed workflow source is older but remains online policy.</data></node><node id="PROC_BL_RESIDUAL_SUPPORT"><data key="node_entity_id">PROC_BL_RESIDUAL_SUPPORT</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSA Residual Black Lung Post-Entitlement Support</data><data key="node_acronym">Black Lung residual support</data><data key="node_domain">Black Lung / Payments</data><data key="node_description">Residual SSA post-entitlement work performed after administration of Part B Black Lung largely transferred to DOL.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">POMS states SSA continues designated post-entitlement actions under a reimbursable agreement; exact workload scope is not fully published.</data></node><node id="PROC_BPO"><data key="node_entity_id">PROC_BPO</data><data key="node_entity_type">process</data><data key="node_canonical_name">Benefit Payment Offset</data><data key="node_acronym">BPO</data><data key="node_domain">Payments / External Offset</data><data key="node_description">Treasury-administered automated process that reduces eligible Title II benefit payments to collect delinquent non-tax debts owed to other Federal agencies.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_BSO_AUTHORIZATION"><data key="node_entity_id">PROC_BSO_AUTHORIZATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Business Services Online Authorization Process</data><data key="node_acronym">BSO Authorization Process</data><data key="node_domain">Earnings / Employer / Identity and Access</data><data key="node_description">Planned updated BSO authorization process supporting optional Employer Signature PIN use for electronic wage reports.</data><data key="node_observed_status">planned_december_2026</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA describes this as anticipated for the annual wage reporting season starting December 2026; it is not modeled as already deployed.</data></node><node id="PROC_BSO_NONSSN_IDME"><data key="node_entity_id">PROC_BSO_NONSSN_IDME</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">BSO Non-SSN ID.me Registration Path</data><data key="node_acronym">BSO Non-SSN Registration</data><data key="node_domain">Employer Services / Identity and Access</data><data key="node_description">2026 registration path allowing a BSO registrant without an SSN to use an ITIN or passport for an ID.me credential before accessing BSO.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SSA guidance says registration may occur regardless of foreign or domestic address and BSO requires MFA. This does not establish that SSA stores the passport, ITIN, or address used by ID.me.</data></node><node id="PROC_CAP"><data key="node_entity_id">PROC_CAP</data><data key="node_entity_type">interagency_program</data><data key="node_canonical_name">Combined Application Project</data><data key="node_acronym">CAP</data><data key="node_domain">Title XVI / External Benefits Coordination</data><data key="node_description">Government partnership that streamlines SNAP enrollment for certain one-person households eligible for SSI; includes standard and modified models.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-08-04</data><data key="node_confidence">5</data><data key="node_notes">Standard CAP involves SSA SSI application/redetermination activity; modified CAP does not require SSA coordination.</data></node><node id="PROC_CAR_USAO_ROUTING"><data key="node_entity_id">PROC_CAR_USAO_ROUTING</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Certified Administrative Record Routing to U.S. Attorney</data><data key="node_acronym">CAR Routing</data><data key="node_domain">Appeals / Federal Court</data><data key="node_description">OAO court-case process for finalizing a CAR, making it available in eView, uploading it to USAfx, completing ARPS actions, and routing it for federal-court filing.</data><data key="node_observed_status">observed_current_hallex</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Paper-file routing remains an exception path in jurisdictions/cases requiring paper.</data></node><node id="PROC_CASEWARE_IDEA_2024"><data key="node_entity_id">PROC_CASEWARE_IDEA_2024</data><data key="node_entity_type">procurement_notice</data><data key="node_canonical_name">Caseware IDEA NLS Subscription Renewal 28321324Q00000074</data><data key="node_acronym">28321324Q00000074</data><data key="node_domain">Procurement / Analytics Software</data><data key="node_description">SSA solicitation for renewal of a concurrent-license subscription for Caseware IDEA NLS software.</data><data key="node_observed_status">inactive_solicitation_2024; award_not_inferred</data><data key="node_observed_as_of">2024-02-13</data><data key="node_confidence">5</data><data key="node_notes">SAM.gov notice states this was a renewal of purchase 28321323P00050024. Awardee and post-2024 operational status are not inferred.</data></node><node id="PROC_CDB_MEDICAID_SDX"><data key="node_entity_id">PROC_CDB_MEDICAID_SDX</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Childhood Disability Beneficiary Medicaid Continuation Notification</data><data key="node_domain">Title II / Medicaid Exchanges</data><data key="node_description">Current POMS says SSA notifies 1634 States via SDX about specified CDB/DAC SSI-loss continuation groups; older notice details are historical and not a new API.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_CDR_MAILER"><data key="node_entity_id">PROC_CDR_MAILER</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Continuing Disability Review Mailer Process</data><data key="node_acronym">CDR Mailer</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">SSA process using the SSA-455 Disability Update Report and scannable variants to screen selected beneficiaries for CDR deferral, full CDR referral, or processing-center review.</data><data key="node_observed_status">observed_current_policy_process</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current retained POMS and 2024 emergency guidance document the process. Older POMS sections describe legacy physical routing through WBDOC/NCC; those details are not generalized as current infrastructure without newer corroboration.</data></node><node id="PROC_CONTINGENT_LIABILITY_RECOVERY"><data key="node_entity_id">PROC_CONTINGENT_LIABILITY_RECOVERY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Contingent Liability Overpayment Recovery Process</data><data key="node_domain">Debt &amp; Overpayments</data><data key="node_description">Business process for transferring, monitoring, and recovering certain OASDI overpayments from overpaid individuals or contingently liable individuals, including benefit withholding and external collection where applicable.</data><data key="node_observed_status">observed_current_process</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">Modeled at the business-process level from OIG and referenced POMS; not a software system.</data></node><node id="PROC_CORRESPONDENT_BANKING"><data key="node_entity_id">PROC_CORRESPONDENT_BANKING</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">Correspondent Banking Direct Deposit</data><data key="node_domain">Payments / International / Direct Deposit</data><data key="node_description">Direct-deposit arrangement in which a U.S. financial institution receives the federal payment and forwards funds to a partner financial institution in the beneficiary country.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS documents direct MBR input through Auto Enrollment or manual FBU/OEIO input and uses RTND as a routing reference.</data></node><node id="PROC_CO_MASS_LOSS_REPLACEMENT"><data key="node_entity_id">PROC_CO_MASS_LOSS_REPLACEMENT</data><data key="node_entity_type">process</data><data key="node_canonical_name">Central Office Mass Loss Systems Replacement Process</data><data key="node_acronym">CO Mass Loss Systems Replacement</data><data key="node_domain">Payments / Paper Checks / Nonreceipt</data><data key="node_description">Central-office process used when SSA declares a qualifying mass loss and centrally handles large volumes of nonreceipt actions rather than requiring individual field-office or teleservice inputs.</data><data key="node_observed_status">observed_current_policy_process</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says DFPC determines whether to implement central-office systems replacement.</data></node><node id="PROC_CPAS"><data key="node_entity_id">PROC_CPAS</data><data key="node_entity_type">process</data><data key="node_canonical_name">Commercial Product Alternative Signature Process</data><data key="node_acronym">CPAS</data><data key="node_domain">Electronic Signatures / Claims and Representation</data><data key="node_description">SSA process for accepting qualifying signatures affixed by approved commercial software products on specified forms and writings.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS distinguishes CPAS from agency-generated e1696/e1693 AdobeSign portals and Upload Documents.</data></node><node id="PROC_CPIC"><data key="node_entity_id">PROC_CPIC</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">Capital Planning and Investment Control Process</data><data key="node_acronym">CPIC</data><data key="node_domain">Enterprise IT Governance</data><data key="node_description">SSA process for planning, selecting, controlling, and evaluating information-technology investments.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">OIG describes four phases: Plan, Select, Control, and Evaluate.</data></node><node id="PROC_CPR"><data key="node_entity_id">PROC_CPR</data><data key="node_entity_type">process</data><data key="node_canonical_name">Cross-Program Recovery</data><data key="node_acronym">CPR</data><data key="node_domain">Debt &amp; Internal Recovery</data><data key="node_description">SSA process for recovering Title II, Title VIII and Title XVI overpayments from benefits payable under another SSA-administered program where authorized.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_CSCRA"><data key="node_entity_id">PROC_CSCRA</data><data key="node_entity_type">process</data><data key="node_canonical_name">Cybersecurity Supply Chain Risk Assessment</data><data key="node_acronym">CSCRA</data><data key="node_domain">Cybersecurity / Acquisition</data><data key="node_description">SSA pre-award cybersecurity supply-chain risk assessment used to determine contractor eligibility and identify mitigating controls.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG page explicitly names the process; implementation workflow beyond documented tools is not inferred.</data></node><node id="PROC_DATA_PIPELINE_RFI_2026"><data key="node_entity_id">PROC_DATA_PIPELINE_RFI_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Data Pipeline Solution RFI 28321326RI0000020</data><data key="node_domain">Procurement / Observability</data><data key="node_description">SSA market-research RFI for a data pipeline solution supporting extensive log creation and retention, aggregation into a single stream, and layered encryption/access control.</data><data key="node_observed_status">rfi_closed</data><data key="node_observed_as_of">2026-05-15</data><data key="node_confidence">5</data><data key="node_notes">Market research only; no deployed product, vendor, or award is inferred.</data></node><node id="PROC_DATS_DEATH_DEVELOPMENT"><data key="node_entity_id">PROC_DATS_DEATH_DEVELOPMENT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DATS Unresolved Death Development Process</data><data key="node_domain">Program Integrity / Death / Identity</data><data key="node_description">Death-alert development workflow for unresolved contacts, including SSA-2708 outreach, a 45-day diary, and DIPS death input as a non-responder if required evidence or contact is not received.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Separate from the erroneous-death correction path already mapped.</data></node><node id="PROC_DCR_MEDICAL_CDR"><data key="node_entity_id">PROC_DCR_MEDICAL_CDR</data><data key="node_entity_type">process</data><data key="node_canonical_name">National Medical CDR Processing at Disability Case Review</data><data key="node_acronym">DCR Medical CDR</data><data key="node_domain">Disability / Program Integrity</data><data key="node_description">Transition of medical Continuing Disability Review processing from State DDSs to SSA Disability Case Review for nationwide federal processing.</data><data key="node_observed_status">transition_announced_in_progress</data><data key="node_observed_as_of">2026-03-12</data><data key="node_confidence">5</data><data key="node_notes">SSA announced the transition March 12, 2026. Public sources establish the operational direction but do not establish a single application or database dedicated to this national workload.</data></node><node id="PROC_DCR_RR_DUAL"><data key="node_entity_id">PROC_DCR_RR_DUAL</data><data key="node_entity_type">process</data><data key="node_canonical_name">DCR Railroad Dual-Eligibility Disability Processing</data><data key="node_acronym">DCR RR Dual Eligibility</data><data key="node_domain">Disability / External Coordination</data><data key="node_description">Workflow in which field offices route qualifying railroad dual-eligibility disability claims to DCR for adjudication and coordination with the Railroad Retirement Board.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-04-16</data><data key="node_confidence">5</data><data key="node_notes">DCR receives the CEF claim in DCPS, adjudicates, and forwards the case to the field office for final processing; paper MDF applies to cases excluded from EDCS.</data></node><node id="PROC_DDS_ACCURACY_REVIEW"><data key="node_entity_id">PROC_DDS_ACCURACY_REVIEW</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS Accuracy Quality Assurance Review</data><data key="node_acronym">DDS Accuracy Review</data><data key="node_domain">Disability / Quality Assurance</data><data key="node_description">SSA review process that samples initial DDS favorable and unfavorable disability determinations to assess compliance and state/national net accuracy.</data><data key="node_observed_status">observed_current_program</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Open Data documentation says approximately 70 favorable and 70 unfavorable determinations from every state are randomly reviewed every three months.</data></node><node id="PROC_DDS_CE_OVERSIGHT"><data key="node_entity_id">PROC_DDS_CE_OVERSIGHT</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS Consultative Examination Oversight Process</data><data key="node_acronym">DDS CE Oversight</data><data key="node_domain">Disability / Consultative Examinations</data><data key="node_description">Annual oversight process covering CE provider quality, credentials, complaints, onsite reviews, provider rosters and fee schedules.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_DDS_STATE_FUNDING_AUTH"><data key="node_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS State Funding Authorization and Drawdown</data><data key="node_acronym">DDS Funding</data><data key="node_domain">Disability / DDS / Funding</data><data key="node_description">Process by which SSA authorizes State DDS obligations and State agencies draw pre-authorized Federal funds through Treasury ASAP.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents SSA-872 authorization and ASAP electronic drawdown; internal SSA budget systems are not inferred.</data></node><node id="PROC_DD_BANK_VERIFICATION"><data key="node_entity_id">PROC_DD_BANK_VERIFICATION</data><data key="node_entity_type">process</data><data key="node_canonical_name">Real-Time Direct Deposit Bank Verification</data><data key="node_acronym">Real-Time Bank Verification</data><data key="node_domain">Payments / Fraud Prevention</data><data key="node_description">SSA fraud-control process applying real-time bank verification to direct-deposit change requests, including Treasury BFS Account Verification Service.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">Verification occurs before or during direct-deposit change processing; no inference that AVS itself writes MBR/SSR payment records.</data></node><node id="PROC_DEBT_SKIPTRACE"><data key="node_entity_id">PROC_DEBT_SKIPTRACE</data><data key="node_entity_type">process</data><data key="node_canonical_name">Debt Skiptracing</data><data key="node_acronym">Skiptracing</data><data key="node_domain">Debt &amp; Overpayments / Address Provenance</data><data key="node_description">Process used to locate debtors when normal telephone or mail contact fails, using sources including credit bureaus, MBR/SSR, MEF, DMV and USPS.</data><data key="node_observed_status">current_retained_poms_process</data><data key="node_observed_as_of">2025-11-20</data><data key="node_confidence">4</data><data key="node_notes">Underlying procedure was revised in 2008 but remains explicitly listed in the current November 2025 debt-recovery POMS subchapter. Implementation details may have changed; only still-published steps are modeled.</data></node><node id="PROC_DECOR_NO_MATCH_MAILING"><data key="node_entity_id">PROC_DECOR_NO_MATCH_MAILING</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Decentralized Correspondence No-Match Mailing</data><data key="node_acronym">DECOR</data><data key="node_domain">Earnings / Wage Corrections / Address Provenance</data><data key="node_description">Historical process that mailed no-match letters to employees, self-employed workers, or employers using addresses available from wage/IRS data and postal validation.</data><data key="node_observed_status">suspended_since_2012</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents the historical process; all listed DECOR letters were suspended effective August 23, 2012.</data></node><node id="PROC_DHS_ALIEN_DEPARTURE_ADDR_DEV"><data key="node_entity_id">PROC_DHS_ALIEN_DEPARTURE_ADDR_DEV</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title II DHS Alien Departure Address Development</data><data key="node_acronym">DHS Alien Departure Address Development</data><data key="node_domain">Title II / Address Provenance</data><data key="node_description">Manual Title II workflow triggered by DHS I-131/reentry-permit information when a beneficiary did not report departure; staff review MBR, develop the correct address, and process qualifying domestic-to-foreign changes through POS PEAD.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">This is evidence of DHS information triggering address development, not a DHS-to-MBR automatic address write.</data></node><node id="PROC_DIFSLA_INDEPENDENT_VERIFY"><data key="node_entity_id">PROC_DIFSLA_INDEPENDENT_VERIFY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DIFSLA Independent Verification Before Adverse Action</data><data key="node_acronym">DIFSLA Independent Verification</data><data key="node_domain">Title XVI / IRS Match / Verification</data><data key="node_description">Required development step in which SSA independently verifies IRS unearned-income match information before denial, suspension, reduction, or termination of benefits.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current CMA expressly requires independent verification and an opportunity to contest; IRS match data is therefore not modeled as an automatic master-record update.</data></node><node id="PROC_DIRA"><data key="node_entity_id">PROC_DIRA</data><data key="node_entity_type">process</data><data key="node_canonical_name">Digital Identity Risk Assessment</data><data key="node_acronym">DIRA</data><data key="node_domain">Identity / Digital Service Governance</data><data key="node_description">SSA assessment required for public-facing applications and automated telephone services to determine required identity-proofing, authentication, and federation security levels.</data><data key="node_observed_status">observed_current_requirement</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">January 2026 SSA procurement requirements explicitly define DIRA scope; this does not establish implementation tooling.</data></node><node id="PROC_DISABILITY_DENIAL_REVIEW"><data key="node_entity_id">PROC_DISABILITY_DENIAL_REVIEW</data><data key="node_entity_type">process</data><data key="node_canonical_name">Disability Denial Review</data><data key="node_acronym">Denial Review</data><data key="node_domain">Disability / Quality Assurance</data><data key="node_description">SSA review of denied DDS disability cases for policy compliance and support by medical and vocational evidence; a statistical model selects cases matching high-error-risk profiles.</data><data key="node_observed_status">observed_current_program</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Open Data documentation covers cases from 52 DDSs and annual national results from FY2013 onward.</data></node><node id="PROC_DISABILITY_OCC_EVAL"><data key="node_entity_id">PROC_DISABILITY_OCC_EVAL</data><data key="node_entity_type">process</data><data key="node_canonical_name">Disability Occupational Information Evaluation</data><data key="node_acronym">Occupational Evaluation</data><data key="node_domain">Disability / Adjudication</data><data key="node_description">Disability adjudication step that evaluates occupational information to determine whether a claimant can perform past work or adjust to other work in the national economy.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical adjudication process established by SSA OIS documentation; no physical application is inferred from this process object.</data></node><node id="PROC_DNP_SOURCE_DATA_CORRECTION"><data key="node_entity_id">PROC_DNP_SOURCE_DATA_CORRECTION</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">Do Not Pay Source Data Correction Process</data><data key="node_acronym">DNP Data Correction</data><data key="node_domain">Data Governance / Payment Integrity</data><data key="node_description">Treasury Do Not Pay correction workflow in which source agencies retain data-quality and correction responsibility and validated corrections are reflected at the original source and within Do Not Pay.</data><data key="node_observed_status">observed_current_governance</data><data key="node_observed_as_of">2026-09-15</data><data key="node_confidence">5</data><data key="node_notes">For Numident, this preserves SSA as the authoritative source/correction point rather than making Do Not Pay a new identity master.</data></node><node id="PROC_DOTEL"><data key="node_entity_id">PROC_DOTEL</data><data key="node_entity_type">process</data><data key="node_canonical_name">District Office Telephone Procedure</data><data key="node_acronym">DOTEL</data><data key="node_domain">SSA Internal Communications</data><data key="node_description">Priority telephone-based intercomponent assistance method for initial entitlement and certain post-entitlement situations.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">A business process rather than an application.</data></node><node id="PROC_DQR_QUALITY_REVIEW"><data key="node_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="node_entity_type">process</data><data key="node_canonical_name">Disability Quality Review Process</data><data key="node_acronym">DQR process</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">Current federal quality-review business process for sampled disability determinations.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes">Separated from the historical DQR case-processing system.</data></node><node id="PROC_DUAL_COA"><data key="node_entity_id">PROC_DUAL_COA</data><data key="node_entity_type">process</data><data key="node_canonical_name">Dual Title II / Title XVI Change of Address Processing</data><data key="node_acronym">Dual COA</data><data key="node_domain">Person / Address</data><data key="node_description">Cross-program change-of-address workflow for concurrent SSI/RSDI cases requiring separate master-record inputs.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly states one input cannot change both MBR and SSR in dual SSI/RSDI cases.</data></node><node id="PROC_DUAL_MBR_SSR_COA"><data key="node_entity_id">PROC_DUAL_MBR_SSR_COA</data><data key="node_entity_type">process</data><data key="node_canonical_name">Dual SSI/RSDI MBR and SSR Change-of-Address Processing</data><data key="node_acronym">Dual MBR/SSR COA</data><data key="node_domain">Person / Address Provenance / Title II / Title XVI</data><data key="node_description">Change-of-address workflow for dually entitled SSI/RSDI cases in which separate inputs are required to update the MBR and SSR; one input cannot change both master records.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Important negative-architecture control: current POMS documents separate master-record updates rather than automatic cross-master address synchronization.</data></node><node id="PROC_DX_SOFTWARE_LICENSE_GRANT"><data key="node_entity_id">PROC_DX_SOFTWARE_LICENSE_GRANT</data><data key="node_entity_type">process</data><data key="node_canonical_name">Data Exchange Software License Grant Process</data><data key="node_domain">External Exchanges / Secure Transfer Governance</data><data key="node_description">Policy-controlled process through which SSA may provide external exchange partners with software licenses needed to communicate securely with SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says DEISB may issue separate test and production licenses when vendor-contract terms allow. The licensed product and vendor vary or are not publicly identified.</data></node><node id="PROC_EAB_TRUMP_ACCOUNT_ENROLLMENT"><data key="node_entity_id">PROC_EAB_TRUMP_ACCOUNT_ENROLLMENT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Enumeration at Birth Trump Account Enrollment Assistance</data><data key="node_acronym">EAB-TA</data><data key="node_domain">Identity / Enumeration / External Program Enrollment</data><data key="node_description">SSA-announced process to use the Enumeration at Birth touchpoint to help parents enroll eligible newborns in Trump Accounts and update hospital guidance/forms.</data><data key="node_observed_status">announced_launch_2026</data><data key="node_observed_as_of">2026-07-03</data><data key="node_confidence">5</data><data key="node_notes">SSA announcement establishes the business process and EAB nexus but does not expose the technical interface to Treasury/IRS account-creation systems.</data></node><node id="PROC_ECO_UNDELIVERABLE"><data key="node_entity_id">PROC_ECO_UNDELIVERABLE</data><data key="node_entity_type">process</data><data key="node_canonical_name">ECO Undeliverable Notice Processing</data><data key="node_domain">Debt &amp; External Collections / Returned Mail</data><data key="node_description">External Collection Operation process for recording returned undeliverable external-collection notices, stopping or reversing specified external-collection actions, and re-requesting a debtor address.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Covers documented Title II and Title XVI pre-offset returned-mail handling. Physical implementation beyond named ECO screens/data structures is not inferred.</data></node><node id="PROC_EDCS_MAINFRAME_PROPAGATION"><data key="node_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS Mainframe Data Propagation</data><data key="node_acronym">EDCS Propagation</data><data key="node_domain">Disability / Person Data</data><data key="node_description">Controlled process by which MCS, MSSICS, ICDB, Numident, SSR, appointment screens, and MBR supply claimant/person and claim data into EDCS, with MCS precedence when a current MCS claim exists.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-03-17</data><data key="node_confidence">5</data><data key="node_notes">Logical propagation process; transport middleware, database technology, and physical staging are not established.</data></node><node id="PROC_EFORM_EXTRA_IDV"><data key="node_entity_id">PROC_EFORM_EXTRA_IDV</data><data key="node_entity_type">process</data><data key="node_canonical_name">Additional Identity Verification for Electronic Form Submission</data><data key="node_acronym">Electronic Form Additional IDV</data><data key="node_domain">Digital Service / Identity / Forms</data><data key="node_description">Additional identity-verification requirement applied by SSA to a limited set of electronically submitted forms.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SSA publicly identifies the affected forms but does not identify the underlying verification technology on the Forms page.</data></node><node id="PROC_EFT_RECLAMATION"><data key="node_entity_id">PROC_EFT_RECLAMATION</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">Automated EFT Reclamation Process</data><data key="node_domain">Payments / Post-Death Reclamation</data><data key="node_description">SSA process for reclaiming Title II or Title XVI direct-deposit payments issued after death, using DNE timing and automated E-stop requests to Treasury where policy criteria are met.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current TN 77 POMS documents 20-day Title II and 30-day Title XVI orbit periods before automated E-stop processing, subject to exclusions.</data></node><node id="PROC_ENH_WAGE_VERIFY"><data key="node_entity_id">PROC_ENH_WAGE_VERIFY</data><data key="node_entity_type">process</data><data key="node_canonical_name">Enhanced Wage Verification Program</data><data key="node_domain">Earnings / Verification / Program Integrity</data><data key="node_description">Annual SSA matching process that applies additional criteria to older unmatched wage reports from the Earnings Suspense File and posts matched wage reports to the Master Earnings File.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">OIG states the program runs annually on wages from three years earlier. The public report does not identify a separate application, database, or implementation technology.</data></node><node id="PROC_ENTERPRISE_CYBER_RISK"><data key="node_entity_id">PROC_ENTERPRISE_CYBER_RISK</data><data key="node_entity_type">process</data><data key="node_canonical_name">Enterprise Cybersecurity Risk Management Process</data><data key="node_domain">Cybersecurity / Risk Management</data><data key="node_description">Agency enterprise process for assessing, accepting, monitoring, aggregating, and responding to cybersecurity risk.</data><data key="node_observed_status">observed_current_with_improvement_actions</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled from FY2026 FISMA findings/recommendations; does not imply a single workflow engine.</data></node><node id="PROC_ERAP"><data key="node_entity_id">PROC_ERAP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Enhanced Representative Availability Process</data><data key="node_acronym">ERAP</data><data key="node_domain">Hearings / Scheduling</data><data key="node_description">Process for collecting and using representative availability when scheduling hearings.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_ERPS_CRIMINAL_BG"><data key="node_entity_id">PROC_ERPS_CRIMINAL_BG</data><data key="node_entity_type">process</data><data key="node_canonical_name">eRPS Criminal Background Check</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">eRPS process that can generate criminal-information work issues for representative-payee applicants and payees.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a business/system process rather than a separate application because POMS does not identify a separate platform.</data></node><node id="PROC_ERPS_EIN_VERIFICATION"><data key="node_entity_id">PROC_ERPS_EIN_VERIFICATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">eRPS Organizational EIN Verification</data><data key="node_acronym">eRPS EIN Verification</data><data key="node_domain">Representative Payee / Employer Identity</data><data key="node_description">eRPS process for verifying an organizational representative payee EIN against the Employer Identification File and resolving discrepancies or overrides.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2023-05-23</data><data key="node_confidence">5</data><data key="node_notes">Manager-controlled workflow; EIF search and eRPS issue mechanics are explicitly documented.</data></node><node id="PROC_ERPS_ORG_MASS_CHANGE"><data key="node_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Organizational Representative Payee Mass Change Process</data><data key="node_domain">Representative Payee / Organizations</data><data key="node_description">One SSA-11 with affected-beneficiary list, beneficiary-specific advance notices, 15-day control, organization merge input and separate residence-address updates if applicable.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_ERPS_QUESTIONABLE_PAYEE_FOLLOWUP"><data key="node_entity_id">PROC_ERPS_QUESTIONABLE_PAYEE_FOLLOWUP</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Questionable Representative Payee Follow-Up</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">Follow-up process used when SSA has questions about a representative payee, including beneficiary/payee contact, diary control, performance review, and documentation of findings.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Follow-up generally occurs within three months under current POMS.</data></node><node id="PROC_ERRONEOUS_DEATH_CORRECTION"><data key="node_entity_id">PROC_ERRONEOUS_DEATH_CORRECTION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Erroneous Death Record Reconciliation</data><data key="node_acronym">Erroneous Death Correction</data><data key="node_domain">Person / Identity / Death</data><data key="node_description">Process for resolving a death alert when the alleged decedent is verified alive and reconciling DATS, DIPS-related alert handling, Numident, and payment-record state.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">The public policy distinguishes alert clearance, death-record correction, and payment-record reconciliation; no single master Person update is inferred.</data></node><node id="PROC_EXTRA_HELP"><data key="node_entity_id">PROC_EXTRA_HELP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Medicare Part D Extra Help Application and Determination</data><data key="node_acronym">Extra Help</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">SSA process for taking, verifying, and determining Medicare Part D low-income subsidy applications.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_EXTRA_HELP_ADDRESS_UPDATE"><data key="node_entity_id">PROC_EXTRA_HELP_ADDRESS_UPDATE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Extra Help Application Address Update Process</data><data key="node_acronym">Extra Help COA</data><data key="node_domain">Medicare / Extra Help / Address</data><data key="node_description">Procedure for developing a recently changed Extra Help mailing address and, when applicable, updating the Title II MBR or SSI SSR under normal program change-of-address procedures.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Address write is conditional and procedural; no direct database-to-database automatic propagation is inferred.</data></node><node id="PROC_EXTRA_HELP_APPEAL"><data key="node_entity_id">PROC_EXTRA_HELP_APPEAL</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Medicare Part D Extra Help Appeal Process</data><data key="node_acronym">Extra Help Appeal</data><data key="node_domain">Medicare / Extra Help / Appeals</data><data key="node_description">SSA administrative appeal process for a Medicare Part D low-income subsidy determination, established in MAPS and routed to the Subsidy Appeals Unit for decision.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS describes telephone or case-review hearing methods; no separate database is inferred.</data></node><node id="PROC_FBU_FALLBACK_MAILING"><data key="node_entity_id">PROC_FBU_FALLBACK_MAILING</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Federal Benefits Unit Last-Resort Mailing Address Process</data><data key="node_acronym">FBU Mailing Fallback</data><data key="node_domain">Title II / International / Address Provenance</data><data key="node_description">Rare last-resort process in which SSA sends mail to a Federal Benefits Unit and considers the FBU address the beneficiary mailing address after other options are exhausted.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2023-12</data><data key="node_confidence">5</data><data key="node_notes">No dedicated FBU address repository or automated program-record update is established.</data></node><node id="PROC_FEE_AGREEMENT_ADMIN_REVIEW"><data key="node_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="node_entity_type">process</data><data key="node_canonical_name">Representative Fee Agreement Administrative Review</data><data key="node_acronym">Fee Agreement Review</data><data key="node_domain">Representation / Fees</data><data key="node_description">Administrative-review workflow for approval/disapproval and fee amount determinations involving OHO/OAO and downstream effectuation components.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_FOREIGN_CARE_OF_MAILING"><data key="node_entity_id">PROC_FOREIGN_CARE_OF_MAILING</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Foreign In-Care-Of Mailing Address Development</data><data key="node_acronym">Foreign C/O</data><data key="node_domain">Title II / International / Address Provenance</data><data key="node_description">Process for accepting a foreign in-care-of mailing address when the beneficiary lives or intends to live with the relative or friend at that address and documents the actual residence and explanation.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2023-12</data><data key="node_confidence">5</data><data key="node_notes">Current POMS page retains 2018 base revision with later transmittal.</data></node><node id="PROC_FO_ADDRESS_AS_MAILING"><data key="node_entity_id">PROC_FO_ADDRESS_AS_MAILING</data><data key="node_entity_type">process</data><data key="node_canonical_name">Field Office Address as Last-Resort Mailing Address</data><data key="node_acronym">C/O SSA</data><data key="node_domain">Title II / Title XVI / Address</data><data key="node_description">Controlled process allowing an SSA field-office address to serve as a claimant/beneficiary mailing address when no workable permanent or alternative mailing address exists.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Requires field-office management approval; policy treats this as last resort and maintains separate local/electronic-folder controls.</data></node><node id="PROC_FPLP"><data key="node_entity_id">PROC_FPLP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Federal Payment Levy Program</data><data key="node_acronym">FPLP</data><data key="node_domain">Payments / Tax Levy</data><data key="node_description">Treasury/IRS process that levies eligible Title II payments for Federal tax debt and sends weekly offset information to SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_FSO"><data key="node_entity_id">PROC_FSO</data><data key="node_entity_type">process</data><data key="node_canonical_name">Federal Salary Offset</data><data key="node_acronym">FSO</data><data key="node_domain">Debt &amp; External Collections</data><data key="node_description">Collection process offsetting Federal employee salary to collect eligible delinquent SSA debt.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_FTI_LOSS_REPORTING"><data key="node_entity_id">PROC_FTI_LOSS_REPORTING</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Federal Tax Information Loss Reporting Workflow</data><data key="node_acronym">FTI loss response</data><data key="node_domain">Privacy / IRS Data</data><data key="node_description">Manager reports suspected federal tax information loss to Loss Reporting Tool; OPD monitors and handles IRS breach notification with affected component.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_HALE_NEW_SSN_DISABILITY"><data key="node_entity_id">PROC_HALE_NEW_SSN_DISABILITY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Disability Claim Processing After Authorized New SSN</data><data key="node_acronym">New-SSN Disability Processing</data><data key="node_domain">Identity &amp; Enumeration / Disability / Privacy</data><data key="node_description">Exception workflow for disability claims or appeals filed under a newly issued SSN when prior or pending claims exist under a former SSN, including HALE-sensitive cases.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS requires reestablishment/exception handling and confidentiality controls.</data></node><node id="PROC_HIT_AUTOMATED_MEDICAL_REQUEST"><data key="node_entity_id">PROC_HIT_AUTOMATED_MEDICAL_REQUEST</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Automated HIT Partner Medical Evidence Request</data><data key="node_domain">Disability / Health IT</data><data key="node_description">MEGAHIT sends automated requests to HIT partners when field office transfers electronic case to DDS, with initial/reconsideration/CDR period boundaries documented.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_HIT_TRADITIONAL_MEDICAL_REQUEST"><data key="node_entity_id">PROC_HIT_TRADITIONAL_MEDICAL_REQUEST</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Traditional Medical Evidence Request</data><data key="node_domain">Disability / Health IT</data><data key="node_description">DCPS traditional medical request through mail, fax, or ERE when HIT partner response cannot supply needed images, tracings, or other evidence.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_HIT_USER_TRIGGERED_REQUEST"><data key="node_entity_id">PROC_HIT_USER_TRIGGERED_REQUEST</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS User-Triggered HIT Partner Request</data><data key="node_domain">Disability / Health IT</data><data key="node_description">DDS may initiate HIT requests through DCPS or MEGAHIT website for absent automatic request, no response after five hours, retrieval error, incomplete evidence, updated consent or newly identified partner.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_IAPPEALS_NUMIDENT_ACCESS_CHECK"><data key="node_entity_id">PROC_IAPPEALS_NUMIDENT_ACCESS_CHECK</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">iAppeals Numident Access Eligibility Check</data><data key="node_acronym">iAppeals Numident Check</data><data key="node_domain">Hearings &amp; Appeals / Identity / Access Control</data><data key="node_description">iAppeals eligibility check that blocks Internet appeal use when the claimant has blocked Internet access or disqualifying special indicator codes on Numident.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2025-12-02</data><data key="node_confidence">5</data><data key="node_notes">No new identity repository is implied; iAppeals consults Numident status.</data></node><node id="PROC_IDD"><data key="node_entity_id">PROC_IDD</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">International Direct Deposit</data><data key="node_acronym">IDD</data><data key="node_domain">Benefit Payments / International</data><data key="node_description">SSA/Treasury process for sending Title II benefit payments to financial institutions outside the United States.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-25</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says IDD is a joint SSA and Federal Reserve Bank of Kansas City service.</data></node><node id="PROC_IDD_MASS_ENROLLMENT"><data key="node_entity_id">PROC_IDD_MASS_ENROLLMENT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">International Direct Deposit Country Mass Enrollment</data><data key="node_acronym">IDD Mass Enrollment</data><data key="node_domain">International / Payments / Direct Deposit</data><data key="node_description">Country-focused enrollment operation used during the first year IDD is available in a country or when SSA seeks to increase electronic-payment participation.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Uses country-designed enrollment forms and outreach; internal campaign tooling is not identified.</data></node><node id="PROC_IL_BIRTH_EVVE"><data key="node_entity_id">PROC_IL_BIRTH_EVVE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Illinois Birth Certificate Number EVVE Verification</data><data key="node_domain">Enumeration / State Vital Records</data><data key="node_description">Illinois policy explains SSA compares NUMIDENT BCN with Illinois certificate formatting and may pad a leading zero for EVVE validation.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_INSIDER_THREAT_PROGRAM"><data key="node_entity_id">PROC_INSIDER_THREAT_PROGRAM</data><data key="node_entity_type">security_program</data><data key="node_canonical_name">SSA Insider Threat Program</data><data key="node_acronym">ITP</data><data key="node_domain">Enterprise Security / Insider Threat</data><data key="node_description">Agency program to deter, detect, monitor, and mitigate risks posed by trusted insiders with authorized access to SSA resources.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">The public OIG report omits sensitive system details; no monitoring tools, data sources, or detection technologies are inferred.</data></node><node id="PROC_INTERCOMP_ASSIST"><data key="node_entity_id">PROC_INTERCOMP_ASSIST</data><data key="node_entity_type">process</data><data key="node_canonical_name">Intercomponent Assistance Request Process</data><data key="node_domain">SSA Internal Operations</data><data key="node_description">SSA process for one office or component to request assistance from another using approved communication/work-control modes.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Parent process synthesized only from the modes explicitly listed in POMS; it does not imply one shared technical platform.</data></node><node id="PROC_IRMAA_NEW_INITIAL"><data key="node_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRMAA New Initial Determination Process</data><data key="node_acronym">New Initial Determination</data><data key="node_domain">Medicare / IRMAA</data><data key="node_description">SSA process for making a new IRMAA determination using qualifying beneficiary-provided information in place of older or inaccurate tax information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_IRP_UPLOAD_DOCS"><data key="node_entity_id">PROC_IRP_UPLOAD_DOCS</data><data key="node_entity_type">process</data><data key="node_canonical_name">Individual Representative Payee Customer-Initiated Upload Documents Submission</data><data key="node_acronym">IRP Upload Documents</data><data key="node_domain">Representative Payee / Digital Intake</data><data key="node_description">Self-service workflow allowing an individual representative payee to authenticate through my Social Security and submit eligible forms/evidence through Upload Documents for a represented beneficiary.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Available beginning December 11, 2025. Organizational representative payees are excluded from this customer-initiated option in the cited guidance.</data></node><node id="PROC_IRS4029_RETURN"><data key="node_entity_id">PROC_IRS4029_RETURN</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRS Form 4029 Return Processing</data><data key="node_acronym">Form 4029 Return Processing</data><data key="node_domain">earnings and enumeration</data><data key="node_description">SSA workflow for an original processed Form 4029 returned from IRS: verify SSN/DOB, suppress Statement, key required information through ESCORR, and scan the form into GIR.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS RM 04906.001.</data></node><node id="PROC_IRS_3857_RESOLUTION"><data key="node_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRS Form 3857 Scrambled Earnings Identity Resolution</data><data key="node_acronym">IRS 3857 Resolution</data><data key="node_domain">Identity / Earnings / Program Integrity</data><data key="node_description">SSA process for resolving IRS Form 3857 identity/scrambled-earnings cases using identity, earnings, employer and benefit queries plus direct contact and postal-address development when needed.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-06-13</data><data key="node_confidence">5</data><data key="node_notes">Current POMS specifies query and direct-contact steps and possible earnings/Numident corrections after evidence development.</data></node><node id="PROC_IRS_SSA_WAGE_RECONCILIATION"><data key="node_entity_id">PROC_IRS_SSA_WAGE_RECONCILIATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRS-SSA Employer Wage Report Reconciliation</data><data key="node_acronym">CAWR Reconciliation</data><data key="node_domain">Earnings / IRS</data><data key="node_description">Process electronically compares employer wages processed by SSA against IRS tax report data by employer EIN and tax year; discrepancies prompt employer development and possible IRS referral.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_IRS_TAXPAYER_MEDIATED"><data key="node_entity_id">PROC_IRS_TAXPAYER_MEDIATED</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Taxpayer-Mediated IRS Tax Information Request for SSA</data><data key="node_acronym">Taxpayer-Mediated IRS Request</data><data key="node_domain">Earnings / IRS / External Evidence</data><data key="node_description">Fallback path in which the number holder requests additional tax information from IRS using Form 4506 or 4506-T and has the information submitted to SSA.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Separate from SSA's direct written IRS Request Template process; transport from taxpayer/IRS to SSA is not inferred.</data></node><node id="PROC_IRS_TAX_INFO_REQUEST"><data key="node_entity_id">PROC_IRS_TAX_INFO_REQUEST</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Written IRS Tax Information Request</data><data key="node_acronym">IRS Tax Information Request</data><data key="node_domain">Earnings / IRS / External Exchange</data><data key="node_description">SSA process for requesting tax return information from IRS when needed for SEI or related determinations and the information cannot be resolved from claimant evidence or SSA online systems.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes">Written route; not the DIFSLA/IRMF automated matching path.</data></node><node id="PROC_KEEP_WHAT_YOU_TAKE"><data key="node_entity_id">PROC_KEEP_WHAT_YOU_TAKE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Keep What You Take Workload Model</data><data key="node_acronym">Keep What You Take</data><data key="node_domain">Field Operations / Workload Routing</data><data key="node_description">Limited-rollout business model under which the office that takes an ASC/WLM initial claim appointment keeps ownership and processes the case through adjudication regardless of claimant residence or local jurisdiction within participating states/territory.</data><data key="node_observed_status">observed_limited_rollout</data><data key="node_observed_as_of">2026-08-29</data><data key="node_confidence">5</data><data key="node_notes">Documented in EM-26017 REV for the expanded WLM/ASC limited rollout.</data></node><node id="PROC_LAWFUL_PRESENCE_VERIFICATION"><data key="node_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Lawful Presence Verification Workflow</data><data key="node_acronym">Lawful Presence Verification</data><data key="node_domain">Identity / Claims / Immigration</data><data key="node_description">Claims workflow that establishes lawful presence using acceptable prior SSA record evidence or DHS documentation, normally using online SAVE when conditions permit and manual G-845 verification when required.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Logical business process. Numident coding alone is expressly not acceptable claim proof under the current policy.</data></node><node id="PROC_MAINFRAME_PRICING_2026"><data key="node_entity_id">PROC_MAINFRAME_PRICING_2026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Mainframe Software Pricing Model Assessment Notice 28321326RNOI00019</data><data key="node_domain">Procurement / Mainframe</data><data key="node_description">SSA notice of intent to sole source an upcoming requirement for IT mainframe software pricing model assessment support services.</data><data key="node_observed_status">pre_award_notice</data><data key="node_observed_as_of">2026-09-23</data><data key="node_confidence">5</data><data key="node_notes">No award or vendor is attached because the official notice is pre-award.</data></node><node id="PROC_MALP"><data key="node_entity_id">PROC_MALP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Medicare Attainments and Leads Process</data><data key="node_acronym">MALP</data><data key="node_domain">Medicare / Claims</data><data key="node_description">Process referenced in current POMS that initiates Title II development or can automatically establish an MBR for an uninsured individual in specified Medicare/SSI situations.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data></node><node id="PROC_MANUAL_FSTOP"><data key="node_entity_id">PROC_MANUAL_FSTOP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Manual F-Stop Processing</data><data key="node_acronym">F-stop</data><data key="node_domain">Payments / Check Stop-Payment</data><data key="node_description">SSA process used to request Treasury status and stop-payment action for checks that should not be paid, including manual corrective actions when an automated stop does not occur.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents separate Title II entry paths and a Title XVI Direct SSR Update path; no single physical F-stop application is inferred.</data></node><node id="PROC_MANUAL_RP_SELECTION"><data key="node_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="node_entity_type">process</data><data key="node_canonical_name">Manual Representative Payee Selection</data><data key="node_domain">Representative Payee / Exception Processing</data><data key="node_description">Rare exception path for payee applicants without an SSN that bypasses eRPS and manually updates Title II or Title XVI payment records.</data><data key="node_observed_status">observed_current_exception_path</data><data key="node_observed_as_of">2026-05-15</data><data key="node_confidence">5</data><data key="node_notes">Current batch POMS retains this exception path.</data></node><node id="PROC_MAPS_PREDECISION"><data key="node_entity_id">PROC_MAPS_PREDECISION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MAPS Pre-Decisional Notice Process</data><data key="node_acronym">MAPS Pre-Decisional Process</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">Process that issues an advance proposed-denial notice, waits for response, accepts new information in MAPS, and automatically recalculates the Extra Help determination.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_MAPS_VERIFICATION"><data key="node_entity_id">PROC_MAPS_VERIFICATION</data><data key="node_entity_type">process</data><data key="node_canonical_name">MAPS Verification Process</data><data key="node_acronym">MAPS verification</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">Process comparing application allegations with agency data and routing material discrepancies for verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_MASS_COA_USPS"><data key="node_entity_id">PROC_MASS_COA_USPS</data><data key="node_entity_type">process</data><data key="node_canonical_name">USPS Mass Change of Address Processing</data><data key="node_acronym">Mass COA</data><data key="node_domain">Title II / Title XVI / Address Maintenance</data><data key="node_description">SSA process for postal mass changes such as ZIP, city-name, street, route, and box conversions, including automated updates to MBR and SSR using postal/ZIP reference data.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Current POMS retains the process, but detailed schedules and internal organization references are substantively older.</data></node><node id="PROC_MA_SCC_ADDRESS_VERIFY"><data key="node_entity_id">PROC_MA_SCC_ADDRESS_VERIFY</data><data key="node_entity_type">process</data><data key="node_canonical_name">Medicare Advantage Residence and SCC Verification</data><data key="node_acronym">MA SCC Verification</data><data key="node_domain">Title II; Medicare; Address</data><data key="node_description">SSA/CMS workflow for resolving discrepancies between a beneficiary residence, the MBR State and County Code, and Medicare Advantage service-area records.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents correction of MBR SCC/address information and, in limited cases, referral to CMS for correction of CMS records.</data></node><node id="PROC_MEDICAL_FOLDER_SEARCH"><data key="node_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="node_entity_type">process</data><data key="node_canonical_name">Medical Folder Location Detective Search</data><data key="node_domain">Disability / Folder Location</data><data key="node_description">Field-office procedure for locating a medical folder by checking multiple claims, disability, workload and query systems.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2024-02-06</data><data key="node_confidence">5</data><data key="node_notes">Modeled from POMS DI 13015.080; this is a business process, not a system.</data></node><node id="PROC_MGD"><data key="node_entity_id">PROC_MGD</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">Master Geographic and Demographic Statistical Production Process</data><data key="node_acronym">MGD process</data><data key="node_domain">Research / Statistics / Earnings</data><data key="node_description">ORES statistical methodology that uses tax-record address information and Numident validation/demographics to assign state/county and demographic attributes to worker records.</data><data key="node_observed_status">research_methodology_under_development</data><data key="node_observed_as_of">2024-12</data><data key="node_confidence">5</data><data key="node_notes">SSA describes the methodology as still under development in December 2024; do not treat it as the proven production methodology for every current publication edition.</data></node><node id="PROC_MNUP"><data key="node_entity_id">PROC_MNUP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Medicare Non-Utilization Project</data><data key="node_acronym">MNUP</data><data key="node_domain">Title II / Program Integrity</data><data key="node_description">Program-integrity process that uses CMS Medicare non-utilization data to select and prioritize certain Title II beneficiaries for continued-eligibility review.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Selection uses domestic address/current-pay/age criteria; no exchange transport is inferred.</data></node><node id="PROC_MNUP_FOREIGN_COA"><data key="node_entity_id">PROC_MNUP_FOREIGN_COA</data><data key="node_entity_type">process</data><data key="node_canonical_name">MNUP Foreign Residence and Change-of-Address Development</data><data key="node_acronym">MNUP Foreign COA</data><data key="node_domain">Title II / Address Provenance / International</data><data key="node_description">Staff-controlled MNUP process for a beneficiary found living abroad, including exact foreign-address development, OEIO verification and applicable change-of-address input, and FO documentation of findings.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS does not name the application into which OEIO inputs the applicable COA; no automatic exchange write is inferred.</data></node><node id="PROC_MOTP"><data key="node_entity_id">PROC_MOTP</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">Manual One-Time Payment</data><data key="node_acronym">M-OTP</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Title XVI manual one-time payment process certified to Treasury by SSA payment-certification staff and manually posted to the SSR after issuance.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a payment process; public policy does not expose the complete internal application stack used by the Payment Certification Branch.</data></node><node id="PROC_MSP_OUTREACH"><data key="node_entity_id">PROC_MSP_OUTREACH</data><data key="node_entity_type">process</data><data key="node_canonical_name">Medicare Savings Programs and Extra Help Outreach</data><data key="node_acronym">MSP Outreach</data><data key="node_domain">Medicare / Low-Income Assistance</data><data key="node_description">SSA process for identifying and mailing outreach to potential MSP and Extra Help eligibles.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_MSSICS_MANCLR"><data key="node_entity_id">PROC_MSSICS_MANCLR</data><data key="node_entity_type">process</data><data key="node_canonical_name">MSSICS MANCLR Manual Clear Process</data><data key="node_acronym">MANCLR</data><data key="node_domain">Title XVI / Claims Processing</data><data key="node_description">Manual MSSICS process used to clear an unarchived pending file before T50 termination in the SSI Duplicate Payment Project.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS names MANCLR MSSICS but public documentation does not expose its physical implementation.</data></node><node id="PROC_NCOA_TITLEII"><data key="node_entity_id">PROC_NCOA_TITLEII</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title II National Change of Address Processing</data><data key="node_acronym">NCOA Processing</data><data key="node_domain">Title II / Address Maintenance</data><data key="node_description">SSA process that matches Title II address records against USPS NCOA data and conditionally applies validated changes, including automatic updates through Title II Redesign for eligible records.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS explicitly states this NCOA process applies to Title II, not Title XVI.</data></node><node id="PROC_NCP"><data key="node_entity_id">PROC_NCP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Numident Correction Processing</data><data key="node_acronym">NCP</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">SSNAP correction process used when a documented keying error permits correction of an existing Numident iteration.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly locates NCP in SSNAP.</data></node><node id="PROC_NOTICE_QR_REPLACE"><data key="node_entity_id">PROC_NOTICE_QR_REPLACE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Paper Notice Enclosure to QR Code Replacement</data><data key="node_acronym">QR Enclosure Replacement</data><data key="node_domain">Notices / Modernization</data><data key="node_description">Agency process for replacing eligible paper notice enclosures with QR codes while retaining paper-copy availability language.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No database, hosting platform, QR generator product, or transport is inferred beyond the documented internal request/control system.</data></node><node id="PROC_NUMIDENT_2026_RECONCILIATION"><data key="node_entity_id">PROC_NUMIDENT_2026_RECONCILIATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2026 Numident Active-SSN Reconciliation Initiative</data><data key="node_domain">Identity &amp; Enumeration / Program Integrity</data><data key="node_description">Agency-reported 2026 initiative to reconcile the SSN database by removing deceased people, updating citizenship data, and verifying individual status.</data><data key="node_observed_status">agency_reported_current_2026</data><data key="node_observed_as_of">2026-08-14</data><data key="node_confidence">5</data><data key="node_notes">SSA reported that more than 10 percent of active SSNs had been updated by August 14, 2026. Public material does not identify the matching algorithms, source systems, or field-level write mechanics.</data></node><node id="PROC_NUMIDENT_ASSOC_RECON"><data key="node_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Numident Associated-Record Reconciliation</data><data key="node_acronym">Numident Cross-Record Reconciliation</data><data key="node_domain">Identity &amp; Enumeration / Cross-System Data Maintenance</data><data key="node_description">Policy-directed process for reviewing and, where necessary, updating associated SSA program records after selected Numident attribute changes.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Represents human/workflow-directed reconciliation, not an inferred automatic synchronization service.</data></node><node id="PROC_NUMIDENT_CROSS_RECORD_UPDATE"><data key="node_entity_id">PROC_NUMIDENT_CROSS_RECORD_UPDATE</data><data key="node_entity_type">process</data><data key="node_canonical_name">Numident Cross-Record Attribute Update Follow-Up</data><data key="node_acronym">Numident Cross-Record Update</data><data key="node_domain">Identity / Person Data</data><data key="node_description">Current operational process requiring staff, after certain Numident attribute changes, to update or review other affected SSA records such as MBR, SSR, and RPS rather than relying on universal automatic propagation.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-06-05</data><data key="node_confidence">5</data><data key="node_notes">For a Numident sex-code update, POMS directs staff to update MBR, SSR, RPS, or other SSA records. For a parent's-name update, staff review MBR/SSR/RPS and initiate or complete needed actions. This models an explicit coordination requirement, not an automatic synchronization service.</data></node><node id="PROC_NUMIDENT_MATCHING_GOV"><data key="node_entity_id">PROC_NUMIDENT_MATCHING_GOV</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">Numident Verification Matching-Criteria Governance</data><data key="node_acronym">Numident Matching Governance</data><data key="node_domain">Identity / Data Exchange / Program Integrity</data><data key="node_description">Cross-component collaboration and periodic risk-assessment control recommended by SSA OIG for developing and maintaining Numident verification matching criteria.</data><data key="node_observed_status">agreed_recommendation_not_verified_implemented</data><data key="node_observed_as_of">2026-09-03</data><data key="node_confidence">5</data><data key="node_notes">SSA agreed with OIG recommendations. This is a governance/control requirement, not a new verification engine.</data></node><node id="PROC_OACT_ADMIN_EXPENSE_PROJ"><data key="node_entity_id">PROC_OACT_ADMIN_EXPENSE_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OACT Administrative Expense Projection</data><data key="node_acronym">Administrative Expense Projection</data><data key="node_domain">Actuarial / OASDI / Cost Projection</data><data key="node_description">Trustees-report projection process for OASDI administrative expenses using historical experience, projected average wages, early-year SSA budget estimates, beneficiary growth, and assumed productivity gains.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public source documents methodology, not internal software or database implementation.</data></node><node id="PROC_OACT_BENEFIT_TAX_PROJ"><data key="node_entity_id">PROC_OACT_BENEFIT_TAX_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OACT Income From Taxation of Benefits Projection</data><data key="node_acronym">Benefit Taxation Projection</data><data key="node_domain">Actuarial / OASDI / Trust Fund Income</data><data key="node_description">Projection process for trust-fund income from federal taxation of OASDI benefits, using Treasury Office of Tax Analysis factors and ratios.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Short-range methodology uses OTA-projected taxable-share and marginal-rate factors; long-range tax ratios also rely on OTA estimates.</data></node><node id="PROC_OACT_COLA"><data key="node_entity_id">PROC_OACT_COLA</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">OACT Cost-of-Living Adjustment Determination</data><data key="node_acronym">COLA Determination</data><data key="node_domain">Actuarial / Automatic Determinations</data><data key="node_description">Statutory process comparing third-quarter CPI-W averages to determine the annual Social Security cost-of-living adjustment.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Latest completed determination for benefits payable in 2026 was 2.8 percent, announced October 24, 2025. No internal software implementation is inferred.</data></node><node id="PROC_OACT_COVERED_EARNINGS_PROJ"><data key="node_entity_id">PROC_OACT_COVERED_EARNINGS_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Covered Earnings Projection</data><data key="node_domain">Actuarial / Earnings / Trust Funds</data><data key="node_description">Actuarial Services method for projecting covered wages by economic sector and covered self-employment net earnings.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public methodology; internal calculation platform is not identified.</data></node><node id="PROC_OACT_DI_BENEFICIARY_PROJ"><data key="node_entity_id">PROC_OACT_DI_BENEFICIARY_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Disabled-Worker Beneficiary Projection</data><data key="node_domain">Actuarial / Disability Insurance</data><data key="node_description">Actuarial Services process combining disabled-worker awards, terminations, and conversions to project the number of disabled workers in current-payment status.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical actuarial method described in the Trustees Report; software platform is not identified.</data></node><node id="PROC_OACT_DI_INCIDENCE_PROJ"><data key="node_entity_id">PROC_OACT_DI_INCIDENCE_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Disabled-Worker Incidence Projection</data><data key="node_domain">Actuarial / Disability Insurance</data><data key="node_description">Actuarial Services method that projects newly awarded disabled-worker beneficiaries using age-sex-specific incidence rates and the projected disability-exposed population.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Methodology entity only. No implementation software or database is inferred.</data></node><node id="PROC_OACT_DI_TERMINATION_PROJ"><data key="node_entity_id">PROC_OACT_DI_TERMINATION_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Disabled-Worker Termination Projection</data><data key="node_domain">Actuarial / Disability Insurance</data><data key="node_description">Actuarial Services method that projects disabled-worker termination rates by age, sex, and reason, and in the long range by duration of entitlement.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Includes death and recovery termination assumptions. No implementation technology is inferred.</data></node><node id="PROC_OACT_FERTILITY_PROJ"><data key="node_entity_id">PROC_OACT_FERTILITY_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Fertility Projection Method</data><data key="node_domain">Actuarial / Demographic Projections</data><data key="node_description">Actuarial Services fertility assumption method based on birth rates by single year of age for ages 14 through 49 and alternative long-range total fertility assumptions.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Methodology only. No underlying software or database is inferred.</data></node><node id="PROC_OACT_IMMIGRATION_PROJ"><data key="node_entity_id">PROC_OACT_IMMIGRATION_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Immigration Projection Method</data><data key="node_domain">Actuarial / Demographic Projections</data><data key="node_description">Actuarial Services immigration assumption method incorporating lawful permanent resident immigration, legal emigration, temporary or unlawfully present immigration, and corresponding emigration/status adjustment flows.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Methodology only. The public report describes four flows and three alternatives; implementation technology is not identified.</data></node><node id="PROC_OACT_MORTALITY_PROJ"><data key="node_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Mortality Projection Method</data><data key="node_acronym">Mortality Projection</data><data key="node_domain">actuarial / demographic projections</data><data key="node_description">Trustees Report method that develops projected central death rates by age group, sex, and cause of death and derives single-year-age death probabilities under three alternatives.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical actuarial method; no software, database, or hosting technology inferred.</data></node><node id="PROC_OACT_PAYROLL_TAX_PROJ"><data key="node_entity_id">PROC_OACT_PAYROLL_TAX_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Payroll Tax Contribution Projection</data><data key="node_domain">Actuarial / Trust Funds / Revenue</data><data key="node_description">Actuarial Services method for projecting payroll tax contributions using statutory collection patterns, scheduled tax rates, taxable wages, and self-employment net earnings.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The report also describes Treasury transfer and later reconciliation mechanics, but no internal software implementation is identified.</data></node><node id="PROC_OACT_RR_FIN_INTERCHANGE"><data key="node_entity_id">PROC_OACT_RR_FIN_INTERCHANGE</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OACT Railroad Retirement Financial Interchange Projection</data><data key="node_acronym">RR Financial Interchange Projection</data><data key="node_domain">Actuarial / OASDI / Railroad Retirement</data><data key="node_description">Projection of future annual financial-interchange amounts between the Railroad Retirement fund and the OASI/DI Trust Funds.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">The public methodology states trends similar to OASDI benefit-cost estimation; internal implementation is not public.</data></node><node id="PROC_OACT_SCHEDULED_BENEFITS"><data key="node_entity_id">PROC_OACT_SCHEDULED_BENEFITS</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OACT Scheduled Benefits Projection</data><data key="node_acronym">Scheduled Benefits Projection</data><data key="node_domain">Actuarial / OASDI / Benefit Projection</data><data key="node_description">Projection process that combines projected beneficiary counts and average monthly benefits; the short-range model calculates scheduled benefits quarterly and the long-range model annually.</data><data key="node_observed_status">observed_current_methodology</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Includes adjustments for retroactive payments and other amounts not reflected in regular monthly scheduled benefits.</data></node><node id="PROC_OACT_TAXABLE_EARNINGS_PROJ"><data key="node_entity_id">PROC_OACT_TAXABLE_EARNINGS_PROJ</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OCACT Taxable Earnings and Payroll Projection</data><data key="node_domain">Actuarial / Earnings / Trust Funds</data><data key="node_description">Actuarial Services method for projecting taxable earnings as the portion of covered earnings subject to OASDI payroll tax and deriving taxable payroll.</data><data key="node_observed_status">observed_current_2026_method</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Uses the contribution and benefit base and adjustments described in the 2026 Trustees Report.</data></node><node id="PROC_OASDI_STATE_COUNTY_ASSIGN"><data key="node_entity_id">PROC_OASDI_STATE_COUNTY_ASSIGN</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">OASDI State and County Geographic Assignment</data><data key="node_domain">Title II / Statistics / Address Provenance</data><data key="node_description">Statistical geographic-assignment process documented for the OASDI state-and-county publication, using MBR beneficiary/payee address information and USPS ZIP+4 county reference data.</data><data key="node_observed_status">observed_current_publication_method</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">For beneficiaries with representative payees, publication state/county designations are those of the representative payees, not necessarily the beneficiaries.</data></node><node id="PROC_OHO_ADDRESS_VERIFY"><data key="node_entity_id">PROC_OHO_ADDRESS_VERIFY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">OHO Claimant Address Verification</data><data key="node_acronym">OHO Address Verification</data><data key="node_domain">Hearings / Address Provenance</data><data key="node_description">OHO process for checking multiple SSA case/query systems and other evidence for updated claimant address/contact information before notices or after unsuccessful contact.</data><data key="node_observed_status">observed_current_hallex</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current HALLEX directs checks of HACPS, FACT, SSID, MDW, CSR and PUPS; it also notes medical evidence and ORS can contain updated address/contact information.</data></node><node id="PROC_OHO_VE_BPA"><data key="node_entity_id">PROC_OHO_VE_BPA</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">OHO Vocational Expert BPA Solicitation and Onboarding</data><data key="node_acronym">VE BPA Process</data><data key="node_domain">Hearings / Procurement</data><data key="node_description">OHO process for obtaining vocational-expert services under Blanket Purchase Agreements, with FedConnect used for vendor registration/application when a solicitation is active.</data><data key="node_observed_status">observed_current_process_no_active_solicitation</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current page explicitly says there is no active BPA solicitation. Process capability and channel are documented without asserting an open procurement.</data></node><node id="PROC_ONGOING_AUTH"><data key="node_entity_id">PROC_ONGOING_AUTH</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Ongoing Authorization</data><data key="node_domain">Enterprise Security / Authorization</data><data key="node_description">Continuous or ongoing security-authorization operating model toward which SSA is transitioning.</data><data key="node_observed_status">transition_in_progress</data><data key="node_observed_as_of">2026-09-24</data><data key="node_confidence">5</data><data key="node_notes">FY2026 OIG says SSA had not fully transitioned to ongoing authorization. The report does not identify the technical implementation or all systems in scope.</data></node><node id="PROC_OVERPAYMENT_WAIVER"><data key="node_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title II and Title XVI Overpayment Waiver Process</data><data key="node_domain">Debt &amp; Overpayments / Waiver</data><data key="node_description">Business process for receiving, developing, deciding, documenting, and routing overpayment waiver requests under Titles II and XVI.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a business process so application/screen roles can be linked without inventing transport architecture.</data></node><node id="PROC_PASS"><data key="node_entity_id">PROC_PASS</data><data key="node_entity_type">process</data><data key="node_canonical_name">Plan to Achieve Self-Support Processing</data><data key="node_acronym">PASS processing</data><data key="node_domain">Title XVI / Work Incentives</data><data key="node_description">Business process for initiating, developing, adjudicating, monitoring, suspending, and terminating PASS plans.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_PAYEE_MEDICAL_CONFIRMATION"><data key="node_entity_id">PROC_PAYEE_MEDICAL_CONFIRMATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Representative Payee Medical Evidence Confirmation Documentation</data><data key="node_domain">Representative Payee / Evidence</data><data key="node_description">Records contacts in eRPS/MCS/CCE RPOC when established, or SSA-5002 stored in NDRed/eView through Evidence Portal when not.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_PA_EVVE_FALLBACK"><data key="node_entity_id">PROC_PA_EVVE_FALLBACK</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Pennsylvania EVVE Failure Verification Fallback</data><data key="node_domain">Enumeration / State Vital Records</data><data key="node_description">Philadelphia-region staff use EVVE first and may fax a copy with PA request for manual vital-record verification if EVVE search fails.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_PBX_RFI_2025"><data key="node_entity_id">PROC_PBX_RFI_2025</data><data key="node_entity_type">procurement_notice</data><data key="node_canonical_name">RFI for Public Branch Exchange (PBX) Functionality - 28321325RI0000022</data><data key="node_acronym">PBX RFI</data><data key="node_domain">Infrastructure / Telephony</data><data key="node_description">SSA RFI for COTS IP-based PBX capabilities needed in field offices as general inquiry lines transition toward Amazon Connect.</data><data key="node_observed_status">rfi_inactive; no_deployment_inferred</data><data key="node_observed_as_of">2025-04-01</data><data key="node_confidence">5</data><data key="node_notes">RFI names required back-office functions such as E911, emergency notification, call park, overhead paging, and administrative capabilities; no award or product selection is inferred.</data></node><node id="PROC_PC_RPA"><data key="node_entity_id">PROC_PC_RPA</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Processing Center Robotic Processing Automation</data><data key="node_domain">Title II / Operations Automation</data><data key="node_description">Production robotic routines available since 2021 to help processing-center technicians with manual awards and post-entitlement actions.</data><data key="node_observed_status">documented_production_since_2021</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_PDAS"><data key="node_entity_id">PROC_PDAS</data><data key="node_entity_type">process</data><data key="node_canonical_name">Payment Delivery Alert System Process</data><data key="node_acronym">PDAS</data><data key="node_domain">Payments / Paper Checks / Nonreceipt</data><data key="node_description">Operational coordination process used by SSA regional and central-office coordinators with USPS to investigate patterns of missing paper benefit checks and determine whether mass-loss action is required.</data><data key="node_observed_status">observed_current_policy_process</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Although the policy calls this the Payment Delivery Alert System, the public source primarily describes a coordination workflow; a dedicated software implementation is not inferred.</data></node><node id="PROC_PERC"><data key="node_entity_id">PROC_PERC</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Preeffectuation Review Contact</data><data key="node_acronym">PERC</data><data key="node_domain">Title XVI / Disability / Effectuation</data><data key="node_description">SSI preeffectuation review performed after specified disability allowances to update or confirm nondisability eligibility and payment factors before effectuation.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current 2025-2026 POMS continues to prescribe full and limited PERC workflows.</data></node><node id="PROC_PER_DISABILITY_REVIEW"><data key="node_entity_id">PROC_PER_DISABILITY_REVIEW</data><data key="node_entity_type">process</data><data key="node_canonical_name">Pre-effectuation Review of Disability Determinations</data><data key="node_acronym">PER Review</data><data key="node_domain">Disability / Quality Assurance</data><data key="node_description">Statutorily required SSA quality review of covered favorable DDS disability determinations before effectuation; cases are selected in part through a statistical model for high probability of substantive error.</data><data key="node_observed_status">observed_current_program</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Public open-data documentation states SSA reviews at least 50 percent of covered favorable Title II and adult SSI determinations and describes a model-based selection method.</data></node><node id="PROC_PIR"><data key="node_entity_id">PROC_PIR</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">Post-Implementation Review Process</data><data key="node_acronym">PIR</data><data key="node_domain">IT Governance / Investment Management</data><data key="node_description">SSA IT-investment review process intended to objectively evaluate implemented or terminated projects and capture lessons, best practices, and actionable recommendations.</data><data key="node_observed_status">paused_after_2024_redevelopment_reported_2026</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">OIG reports no PIRs after November 2024 and states subject-matter experts were developing a new PIR program in January 2026. Current completion/relaunch status is not established.</data></node><node id="PROC_PIV_CARDSTOCK_2026"><data key="node_entity_id">PROC_PIV_CARDSTOCK_2026</data><data key="node_entity_type">procurement_notice</data><data key="node_canonical_name">HSPD-12 PIV Cardstock Replacement and Personalization Services Notice 28321326RNOI00011</data><data key="node_acronym">28321326RNOI00011</data><data key="node_domain">Procurement / Identity Security</data><data key="node_description">SSA special notice of intent to sole source HSPD-12 PIV cardstock replacement and personalization services.</data><data key="node_observed_status">inactive_notice_of_intent</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes">Published July 1, 2026; response date July 7; inactive July 22. The public notice does not name the intended vendor.</data></node><node id="PROC_PPC_STUB"><data key="node_entity_id">PROC_PPC_STUB</data><data key="node_entity_type">process</data><data key="node_canonical_name">Stub Record / Tap-on-the-Shoulder Process</data><data key="node_acronym">Stub Record</data><data key="node_domain">Processing Center / Electronic Workflow</data><data key="node_description">Process that automatically creates a Paperless Action Control Record to alert a technician to fully electronic actionable work.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Historical procedure remains useful architecture evidence; current deployment breadth is not independently established by this source alone.</data></node><node id="PROC_PRISONER_MATCH"><data key="node_entity_id">PROC_PRISONER_MATCH</data><data key="node_entity_type">process</data><data key="node_canonical_name">Automated Inmate Matching Operation</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">Automated matching process that verifies inmate identities and creates PUPS records for verified matches.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="PROC_PUBLIC_INQUIRY_CORR"><data key="node_entity_id">PROC_PUBLIC_INQUIRY_CORR</data><data key="node_entity_type">process</data><data key="node_canonical_name">Public Inquiry Correspondence Processing</data><data key="node_domain">Public Inquiries / Correspondence</data><data key="node_description">Business process for receiving, assigning, managing, and completing responses to public and other external inquiries.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2025-07-14</data><data key="node_confidence">5</data><data key="node_notes">Derived only at the business-process level from SSA's Open Data and EMAC SORN descriptions; no technical integration is inferred.</data></node><node id="PROC_PUPS_IP_RECOUP"><data key="node_entity_id">PROC_PUPS_IP_RECOUP</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Prisoner Incentive Payment Recoupment Process</data><data key="node_acronym">IP Recoupment</data><data key="node_domain">Program Integrity / Prisoner / Debt</data><data key="node_description">Workflow for recovering an incorrectly paid prisoner-report incentive payment from a correctional or mental health institution.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_PW_ACCRETION"><data key="node_entity_id">PROC_PW_ACCRETION</data><data key="node_entity_type">process</data><data key="node_canonical_name">Public Welfare Accretion Process</data><data key="node_acronym">PW Accretion</data><data key="node_domain">Medicare / State Coordination</data><data key="node_description">SSA process for establishing Medicare Part B state buy-in for qualifying Medicaid beneficiaries.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_QEP"><data key="node_entity_id">PROC_QEP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Quarterly Earnings Project</data><data key="node_acronym">QEP</data><data key="node_domain">Title II Disability / Work CDR</data><data key="node_description">Quarterly earnings-based enforcement process using OCSE data to generate work CDR alerts for disability beneficiaries.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies QEP as a current enforcement source using quarterly OCSE earnings.</data></node><node id="PROC_R105_GRANT_CONT"><data key="node_entity_id">PROC_R105_GRANT_CONT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Continuation Grant Application Submission</data><data key="node_domain">Procurement &amp; Grants</data><data key="node_description">Existing grantees use GrantSolutions for continuation grant applications when required by the applicable SSA announcement.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_R105_GRANT_NEW"><data key="node_entity_id">PROC_R105_GRANT_NEW</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Competitive Grant Application Submission</data><data key="node_domain">Procurement &amp; Grants</data><data key="node_description">Applicants register in SAM.gov and submit competitive discretionary grants through Grants.gov; successful grants notified electronically through GrantSolutions.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_R105_ISNO_AUTH_FIX"><data key="node_entity_id">PROC_R105_ISNO_AUTH_FIX</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">iSNO Identity Mismatch Referral and Correction</data><data key="node_domain">Person &amp; Identity</data><data key="node_description">Cross-record mismatch or disqualifying death indicator prompts component referral to field office, which corrects affected records under standard evidence rules and retries iSNO authentication.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_R105_ISNO_NON_CEF"><data key="node_entity_id">PROC_R105_ISNO_NON_CEF</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">iSNO Special-Notice Paper-File Documentation</data><data key="node_domain">Notices &amp; Evidence</data><data key="node_description">Where case lacks certified electronic file, staff complete SSA-5002 and fax to NDRED; DDS puts form in orange MDF section.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_R105_STC_ROUTING"><data key="node_entity_id">PROC_R105_STC_ROUTING</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">State Data Exchange Transfer via STC</data><data key="node_domain">External Exchanges &amp; Governance</data><data key="node_description">If an approved IEA state agency cannot directly receive SSA data, a State Transmission/Transfer Component relays authorized exchange data subject to an STC agreement.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_R105_TEFCA_QHIN_TEST"><data key="node_entity_id">PROC_R105_TEFCA_QHIN_TEST</data><data key="node_entity_type">integration_test_process</data><data key="node_canonical_name">SSA eHealth Exchange QHIN Connection Testing</data><data key="node_domain">Disability &amp; External Exchanges</data><data key="node_description">SSA reported testing its eHealth Exchange QHIN TEFCA connection in February 2026 and predicted spring go-live; no authoritative confirmation of SSA production go-live found during this run.</data><data key="node_observed_status">announced_testing_february_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Do not promote production based on scheduled spring target.</data></node><node id="PROC_R194_SAMOA_IDD"><data key="node_entity_id">PROC_R194_SAMOA_IDD</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Samoa Title II International Direct Deposit Coding Process</data><data key="node_domain">Title II Payments</data><data key="node_description">SSA POMS documents Samoa-specific RTN prefix 66, account country code O and MBR bank-data formatting; applies to Title II international direct deposit.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_R194_SANMARINO_IDD"><data key="node_entity_id">PROC_R194_SANMARINO_IDD</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">San Marino Title II International Direct Deposit Coding Process</data><data key="node_domain">Title II Payments</data><data key="node_description">POMS documents IBAN/SWIFT-BIC inputs, local EUR account requirements, MBR RTN prefix 71 and DAN code C for San Marino.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-01-16</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_R8_CONSERVED_FUNDS_REVIEW"><data key="node_entity_id">PROC_R8_CONSERVED_FUNDS_REVIEW</data><data key="node_entity_type">process</data><data key="node_canonical_name">R8 Conserved Funds Eligibility Review</data><data key="node_acronym">R8 Review</data><data key="node_domain">Title XVI / Representative Payee / Program Integrity</data><data key="node_description">Field-office development process for SSI cases alerted by R8 to evaluate conserved funds and continued resource eligibility.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-07-02</data><data key="node_confidence">5</data><data key="node_notes">Active policy states Title XVI eligibility is questionable at resource-limit levels and requires development when conserved funds are reported at or above applicable thresholds.</data></node><node id="PROC_REAP"><data key="node_entity_id">PROC_REAP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Revised Earnings Adjustment Process</data><data key="node_acronym">REAP</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">Process for certain individual wage adjustments, including suspense-file corrections when ICOR/RCOR cannot perform the adjustment.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Detailed POMS evidence is from 2019.</data></node><node id="PROC_REP_FEE_AGREEMENT"><data key="node_entity_id">PROC_REP_FEE_AGREEMENT</data><data key="node_entity_type">process</data><data key="node_canonical_name">Representative Fee Agreement Process</data><data key="node_domain">Representation / Fees</data><data key="node_description">Administrative process under which a claimant and representative submit a fee agreement for SSA review and authorization; e1693 is an available electronic submission method.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Kept separate from the narrower Representative Fee Agreement Administrative Review entity already in the Atlas.</data></node><node id="PROC_REP_FEE_TAX_REPORTING"><data key="node_entity_id">PROC_REP_FEE_TAX_REPORTING</data><data key="node_entity_type">process</data><data key="node_canonical_name">Representative Direct-Fee Tax Reporting Process</data><data key="node_domain">Representative Services / Finance</data><data key="node_description">Process for SSA reporting qualifying direct representative fee payments on Forms 1099-MISC/1099-NEC and associated entity reporting.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA representative guidance documents the tax-reporting process and business-entity registration rules.</data></node><node id="PROC_REP_PAYEE_CAPABILITY_DEV"><data key="node_entity_id">PROC_REP_PAYEE_CAPABILITY_DEV</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Representative Payee Capability Development</data><data key="node_acronym">Capability Development</data><data key="node_domain">representative payee</data><data key="node_description">SSA development process for determining whether a beneficiary can manage or direct management of benefits using medical, lay, and legal evidence.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Logical business process; no separate system inferred.</data></node><node id="PROC_REP_TRAVEL_EFT"><data key="node_entity_id">PROC_REP_TRAVEL_EFT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Electronic Representative Travel Reimbursement Process</data><data key="node_acronym">Representative Travel EFT</data><data key="node_domain">Payments / Representative Services</data><data key="node_description">SSA process for issuing representative travel reimbursements exclusively by electronic funds transfer beginning March 1, 2026.</data><data key="node_observed_status">observed_current_ssa_guidance</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA guidance establishes payment options but does not identify the internal payment application or Treasury settlement path.</data></node><node id="PROC_RETAP"><data key="node_entity_id">PROC_RETAP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Regular Transcript Attainment and Selection Pass Operation</data><data key="node_acronym">RETAP</data><data key="node_domain">Medicare / Title II</data><data key="node_description">Monthly process that identifies records approaching Medicare entitlement and establishes applicable HI/SMI entitlement on the MBR.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current live POMS documents RETAP; the underlying implementation technology is not disclosed.</data></node><node id="PROC_RIB_STP"><data key="node_entity_id">PROC_RIB_STP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Retirement iClaim Straight-Through Processing</data><data key="node_acronym">STP</data><data key="node_domain">Title II / Retirement Claims</data><data key="node_description">Automated processing path for retirement insurance benefit iClaims; claims with EARQs are ineligible and require technician resolution.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-14</data><data key="node_confidence">5</data><data key="node_notes">This entity models the documented business/automation process, not an independently named software product.</data></node><node id="PROC_RPC"><data key="node_entity_id">PROC_RPC</data><data key="node_entity_type">process</data><data key="node_canonical_name">Request for Program Consultation Process</data><data key="node_acronym">RPC</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">Process allowing DDS to contest certain DQR deficiency citations using an online submission and panel-review workflow.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-18</data><data key="node_confidence">5</data><data key="node_notes">POMS states the process applies only to certified electronic folders.</data></node><node id="PROC_RP_COA"><data key="node_entity_id">PROC_RP_COA</data><data key="node_entity_type">process</data><data key="node_canonical_name">Representative Payee Change-of-Address Processing</data><data key="node_acronym">Rep Payee COA</data><data key="node_domain">Representative Payee / Address Maintenance</data><data key="node_description">Address-change workflow for representative-payee cases, with different propagation rules for Title II, Title XVI, individual payees, institutional payees, and specified exceptions.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">eRPS propagation is not uniform: individual-payee Title XVI changes require MSSICS/SSR action while institutional-payee records correctly established on eRPS can update automatically.</data></node><node id="PROC_RSI_OPEN_DATA_AGGREGATION"><data key="node_entity_id">PROC_RSI_OPEN_DATA_AGGREGATION</data><data key="node_entity_type">process</data><data key="node_canonical_name">RSI Open Data Batch Aggregation</data><data key="node_acronym">RSI Batch Aggregation</data><data key="node_domain">Title II / Analytics / Publication</data><data key="node_description">Batch process described by SSA for preparing and aggregating Title II ODS claims data into national public retirement, survivor, and Medicare application-volume data using DOWR reporting dates.</data><data key="node_observed_status">observed_current_documented_process</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data><data key="node_notes">Logical batch/publication process only; database technology, scheduler, ETL product, and hosting are not identified publicly.</data></node><node id="PROC_SDX_1619_MEDICAID_NOTIFY"><data key="node_entity_id">PROC_SDX_1619_MEDICAID_NOTIFY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Section 1619 Medicaid Continuation Notification via SDX</data><data key="node_acronym">1619 SDX Notification</data><data key="node_domain">Title XVI / State Exchange / Medicaid</data><data key="node_description">SSA process that notifies States through the State Data Exchange that SSI recipients are in section 1619 continuation groups relevant to Medicaid eligibility.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS establishes SDX notification but does not disclose a distinct record type, file name, or transport implementation.</data></node><node id="PROC_SERS_FEE_REFUND"><data key="node_entity_id">PROC_SERS_FEE_REFUND</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SERS Administrative Fee Refund Routing</data><data key="node_domain">Finance / Payments</data><data key="node_description">FO routes refund case information to Office of Financial Statements; FO does not issue refund in SERS; Treasury check goes to supplied mailing address.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_SERS_NONPROGRAMMATIC_FEE"><data key="node_entity_id">PROC_SERS_NONPROGRAMMATIC_FEE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SERS Field Office Non-Programmatic Fee Intake</data><data key="node_domain">Finance / Payments</data><data key="node_description">Field-office standard service fee processing by check or money order with SERS imaging, receipt issue and five-day secure destruction of paper original.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_SERS_SCANNER_OUTAGE_FALLBACK"><data key="node_entity_id">PROC_SERS_SCANNER_OUTAGE_FALLBACK</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SERS Check Scanner Outage Fallback</data><data key="node_domain">Finance / Payments</data><data key="node_description">When SERS scanner fails, SSA uses help desk ticket and may revert to SSA-414 for tracking; FS will not accept checks without ticket.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_SNO"><data key="node_entity_id">PROC_SNO</data><data key="node_entity_type">process</data><data key="node_canonical_name">Special Notice Option Alternate-Format Fulfillment</data><data key="node_acronym">SNO</data><data key="node_domain">Notices / Accessibility</data><data key="node_description">Business process that uses DPS or CHIP to request forms and communications in Braille, data CD, audio CD, or large print and route the request to the special notice option vendor.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">The cited POMS does not name the vendor; no vendor entity is inferred.</data></node><node id="PROC_SSA_DNP_REVISED_SCHEDULE"><data key="node_entity_id">PROC_SSA_DNP_REVISED_SCHEDULE</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">SSA–Do Not Pay Revised Recurring Payment Schedule</data><data key="node_domain">Payments / Program Integrity</data><data key="node_description">Revised recurring-payment preparation schedule coordinated by SSA, Do Not Pay, and Federal Disbursement Services to allow one additional day for SSA payee-information updates before disbursement.</data><data key="node_observed_status">implemented_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Treasury gives examples of late-changing payee status including death, bank-account, and address updates. This does not establish that Do Not Pay writes those fields into SSA master records.</data></node><node id="PROC_SSA_GRANT_APPLICATION"><data key="node_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSA Grant Application and Award Workflow</data><data key="node_domain">Grants / Application and Award</data><data key="node_description">OAG grant workflow from SAM registration and application submission through review and electronic award notification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Competitive discretionary applications use Grants.gov; continuation applications use GrantSolutions when stipulated; successful award notification is via GrantSolutions.</data></node><node id="PROC_SSA_PURCHASE_CARD"><data key="node_entity_id">PROC_SSA_PURCHASE_CARD</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSA Purchase Card Program Administration</data><data key="node_acronym">Purchase Card Program</data><data key="node_domain">Procurement / Purchase Card</data><data key="node_description">SSA purchase-card program administered by the Office of Acquisition Support.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">OAG current page establishes administrative ownership; transaction platform/vendor is not inferred.</data></node><node id="PROC_SSFA_REPROCESS"><data key="node_entity_id">PROC_SSFA_REPROCESS</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Social Security Fairness Act WEP/GPO Reprocessing</data><data key="node_acronym">SSFA reprocessing</data><data key="node_domain">Title II / Modernization History</data><data key="node_description">SSA implementation of repeal of WEP and GPO for payments beginning January 2024, including automated and manual retroactive benefit corrections beginning 2025.</data><data key="node_observed_status">documented_implemented_2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_SSIDPP"><data key="node_entity_id">PROC_SSIDPP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Supplemental Security Income Duplicate Payment Project</data><data key="node_acronym">SSIDPP</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">Annual SSI program-integrity process that identifies duplicate SSR records for the same person, terminates incorrect records, develops resulting overpayments, and preserves cross-reference information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS says the project runs around August and uses case control sheets, Numidents, and SSIDs.</data></node><node id="PROC_SSI_ABAP"><data key="node_entity_id">PROC_SSI_ABAP</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Abbreviated Application Process</data><data key="node_acronym">ABAP</data><data key="node_domain">Title XVI / Claims Intake</data><data key="node_description">Process for formally denying Title XVI claims for clear nonmedical ineligibility using a shortened systems or paper application path.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies the SSI Claims System as the preferred claims-taking method and also references MSSICS procedures.</data></node><node id="PROC_SSI_ABLE_REPORTING"><data key="node_entity_id">PROC_SSI_ABLE_REPORTING</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI ABLE Account Reporting</data><data key="node_acronym">ABLE Reporting</data><data key="node_domain">Title XVI / Resources / External Exchange</data><data key="node_description">Current SSI process in which State ABLE programs send monthly account information to SSA for SSI resource administration; matching reports can automatically update documented account balances in the SSI Claims System.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2026 POMS establishes current monthly State exchange and SSI Claims System workflow. Earlier 2021 SSIRMS/MSSICS evidence remains valid historical architecture; transport/file format remains unspecified.</data></node><node id="PROC_SSI_EARNED_RZ"><data key="node_entity_id">PROC_SSI_EARNED_RZ</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Earned Income Redetermination Process</data><data key="node_acronym">Earned Income RZ</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">SSI redetermination process that develops earned-income allegations and evidence and uses SSI Claims guided processing.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No separate physical RZ application is inferred.</data></node><node id="PROC_SSI_EARNINGS_ALERT_RESOLUTION"><data key="node_entity_id">PROC_SSI_EARNINGS_ALERT_RESOLUTION</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Earnings Alert Resolution Process</data><data key="node_acronym">SSI Earnings Alert Resolution</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">Operational process for developing and resolving SSI earnings discrepancies before recording corrected earnings and payment effects.</data><data key="node_observed_status">observed_current_oig_issue</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">September 23, 2026 OIG reported 417,291 SSI recipients with at least one pending earnings alert and significant delays/incomplete resolution; this process entity does not imply all earnings-alert types share one physical system.</data></node><node id="PROC_SSI_EP_DEATH_RZ"><data key="node_entity_id">PROC_SSI_EP_DEATH_RZ</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Essential-Person Death Redetermination Reselection</data><data key="node_acronym">EP Death RZ</data><data key="node_domain">Title XVI / Redetermination</data><data key="node_description">Workflow in which omission of the RZ initiation date with an essential-person death input generates a D6 alert, deletes the case from PE ODS, and causes profile-D reselection in the next merge.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Models only the explicit work-control behavior.</data></node><node id="PROC_SSI_IAR_UNDERPAYMENT_HOLD"><data key="node_entity_id">PROC_SSI_IAR_UNDERPAYMENT_HOLD</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Interim Assistance Underpayment Hold and Release</data><data key="node_acronym">IAR Hold/Release</data><data key="node_domain">Title XVI / Underpayments / Interim Assistance</data><data key="node_description">Process that holds SSI past-due benefits while interim assistance reimbursement is pending, reimburses the State, and releases remaining underpayment according to payment-priority rules.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a business process spanning SSR, eIAR and underpayment review; no new database or transport is inferred.</data></node><node id="PROC_SSI_INTERSTATE_COA_STAGING"><data key="node_entity_id">PROC_SSI_INTERSTATE_COA_STAGING</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Interstate Change-of-Address Staged Residence Processing</data><data key="node_acronym">SSI Interstate COA</data><data key="node_domain">Title XVI / Address Provenance / Work Control</data><data key="node_description">Process that can stage a new mailing address while temporarily retaining the former residence/State-county and living-arrangement values until the new residence and living arrangement are developed.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-08-07</data><data key="node_confidence">5</data><data key="node_notes">Shows temporal separation of mailing address and residence data; does not imply automatic cross-record synchronization.</data></node><node id="PROC_SSI_IRS_PENSION_MATCH"><data key="node_entity_id">PROC_SSI_IRS_PENSION_MATCH</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI IRS Pension Interface</data><data key="node_acronym">Pension Interface</data><data key="node_domain">Title XVI / IRS Match</data><data key="node_description">IRS pension-interface matching process that compares Form 1099-R pension, annuity, and IRA reports with eligible individuals and deemors on SSR.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents the process; physical matching engine, transport, and staging implementation are not public.</data></node><node id="PROC_SSI_LIQUID_RESOURCE_RZ"><data key="node_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Liquid Resource Redetermination Development</data><data key="node_acronym">Liquid Resource RZ</data><data key="node_domain">Title XVI / Resources / Redetermination</data><data key="node_description">Redetermination workflow that develops liquid-resource allegations and evidence, including IRS alerts and financial-account development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Process uses current SSI Claims/CCE surfaces; no new repository is inferred.</data></node><node id="PROC_SSI_ORAL_INQUIRY_PF"><data key="node_entity_id">PROC_SSI_ORAL_INQUIRY_PF</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Oral Inquiry Protective Filing</data><data key="node_domain">Title XVI / Intake / Protective Filing</data><data key="node_description">SSI protective-filing process in which an oral inquiry can establish a protected filing date when policy criteria are met and the inquiry is documented in SSA systems such as eLAS.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy revision 2020 remains in current POMS batch; eLAS examples remain explicit.</data></node><node id="PROC_SSI_RESIDENCY_DETERMINATION"><data key="node_entity_id">PROC_SSI_RESIDENCY_DETERMINATION</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI State and County Residence Determination</data><data key="node_acronym">SSI Residency Determination</data><data key="node_domain">Title XVI / Address / Residency</data><data key="node_description">SSI workflow for establishing and correcting state and county of residence using allegations and supporting evidence when needed.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Evidence may include rental agreements, banking records, subscription addresses, driver license, utility bills, institutional records, social workers, and representative payees.</data></node><node id="PROC_SSI_RZ_ADDRESS_DEVELOPMENT"><data key="node_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination Address and Residence Development</data><data key="node_acronym">SSI RZ Address Development</data><data key="node_domain">Title XVI / Address / Redetermination</data><data key="node_description">Redetermination workflow that compares alleged residence information with SSR and documents residence and mailing addresses separately in the SSI Claims System.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">If an alleged address is absent from SSR, policy directs development of an unreported change rather than automatic acceptance or overwrite.</data></node><node id="PROC_SSI_SAVE_VERIFICATION"><data key="node_entity_id">PROC_SSI_SAVE_VERIFICATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title XVI SAVE Immigration Verification Workflow</data><data key="node_acronym">SSI SAVE Verification</data><data key="node_domain">Identity / Title XVI / Immigration</data><data key="node_description">Current SSI claims workflow requiring SAVE verification before approval and during redeterminations/status changes, with results documented in CCE and evidence retained in the electronic folder.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SAVE is authoritative for immigration-status verification, but SSA makes the benefit eligibility determination.</data></node><node id="PROC_SSI_SPECIAL_VOUCHER"><data key="node_entity_id">PROC_SSI_SPECIAL_VOUCHER</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">SSI Special Voucher Payment Process</data><data key="node_acronym">Special Voucher</data><data key="node_domain">Title XVI / Payments / Reimbursement</data><data key="node_description">SSI payment process used to reimburse a financial institution or other party owed money after a CORE erroneous-death credit.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies the process but the public source does not identify the internal application or Treasury settlement mechanism used to issue the voucher.</data></node><node id="PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT"><data key="node_entity_id">PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Trump Account Resource Development</data><data key="node_acronym">TA Resource Development</data><data key="node_domain">Title XVI / Resources</data><data key="node_description">SSI development process for documenting, excluding, redeveloping, and eventually counting Trump Account resources, including possible ABLE rollover.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-07-09</data><data key="node_confidence">5</data><data key="node_notes">No undocumented backend, workflow engine, or financial-account interface inferred.</data></node><node id="PROC_SSI_TRUST_REVIEW"><data key="node_entity_id">PROC_SSI_TRUST_REVIEW</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Trust Resource Determination Review</data><data key="node_acronym">SSI Trust Review</data><data key="node_domain">Title XVI / Resources / Trusts</data><data key="node_description">Review workflow for SSI trust resource determinations, including field-office submission, regional review, feedback, effectuation status, reevaluation, and appeal handling.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Operational process spans SSI Claims System/CCE documentation, Evidence Portal, SSITMS, and regional review.</data></node><node id="PROC_SSI_UNDERPAY_PREPAY_REVIEW"><data key="node_entity_id">PROC_SSI_UNDERPAY_PREPAY_REVIEW</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Underpayment Pre-payment Review</data><data key="node_domain">Title XVI / Payments / Program Integrity</data><data key="node_description">Secondary review process for large SSI underpayments to determine whether an underpayment is correct and the recipient is eligible before payment release.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Effective March 16, 2024, SSI underpayments of $15,000 or more require this review; reviewer must be a claims specialist or higher-level employee other than the adjudicator.</data></node><node id="PROC_SSI_VEHICLE_RESOURCE_VERIFY"><data key="node_entity_id">PROC_SSI_VEHICLE_RESOURCE_VERIFY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Vehicle Ownership and Value Verification</data><data key="node_acronym">SSI Vehicle Verification</data><data key="node_domain">Title XVI / Resources / Program Integrity</data><data key="node_description">Staff-controlled process for verifying suspected unreported vehicle ownership through State title/registration information and verifying fair market value for multiple vehicles using an approved valuation source.</data><data key="node_observed_status">observed_current_policy_process</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">OIG describes this as conditional verification rather than routine independent verification of all SSI recipients.</data></node><node id="PROC_SSI_WU_S06"><data key="node_entity_id">PROC_SSI_WU_S06</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Whereabouts Unknown Location and S06 Suspension</data><data key="node_acronym">S06 / WU</data><data key="node_domain">Title XVI / Address / Eligibility</data><data key="node_description">SSI process for attempting to locate a recipient whose whereabouts are unknown and, if unsuccessful, suspending eligibility/payment in S06 status.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS requires locate efforts before suspension and treats external address sources as leads requiring development, not automatic authoritative-address replacement.</data></node><node id="PROC_SSNAP_OTSP"><data key="node_entity_id">PROC_SSNAP_OTSP</data><data key="node_entity_type">workflow_option</data><data key="node_canonical_name">One Time Special Processing</data><data key="node_acronym">OTSP</data><data key="node_domain">Identity / Enumeration / Exception Processing</data><data key="node_description">SSNAP exception-processing option used when required enumeration evidence is not represented in the standard evidence dropdown and policy authorizes special handling.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a workflow option, not a separate application. Public POMS establishes its use with NIDD-reviewed documents and other enumeration exceptions.</data></node><node id="PROC_SSN_SEX_DISCLOSURE"><data key="node_entity_id">PROC_SSN_SEX_DISCLOSURE</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSN Sex Field Verification Disclosure Approval</data><data key="node_acronym">Sex Field Disclosure Approval</data><data key="node_domain">Identity / Data Exchange Governance</data><data key="node_description">Approval process for including the sex field verification indicator in an SSN-verification data exchange, requiring justification and consensus across PPDX, legal, privacy/disclosure, and the business sponsor.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">New requests submit justification through SSA-157/DXRF; renewals use the agreement-renewal process.</data></node><node id="PROC_SSR_MBR_FORCE_FINDER"><data key="node_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSR-to-MBR State Buy-In Forced Finder Correction</data><data key="node_acronym">Forced Finder</data><data key="node_domain">Medicare / State Buy-In / Reconciliation</data><data key="node_description">Field-office correction process that requests a Type M offline query to force an SSR finder and update MBR state buy-in information when SSR and MBR are inconsistent.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Process requires consistent identifying data on SSR and MBR before the interface can occur; physical interface implementation is not inferred.</data></node><node id="PROC_STATE_BUYIN"><data key="node_entity_id">PROC_STATE_BUYIN</data><data key="node_entity_type">process</data><data key="node_canonical_name">Medicare Part B State Buy-In Process</data><data key="node_acronym">State Buy-In</data><data key="node_domain">Medicare / State Coordination</data><data key="node_description">Process under which a State pays Medicare Part B premiums for eligible Medicaid beneficiaries and SSA/CMS coordinate enrollment and corrections.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-15</data><data key="node_confidence">5</data></node><node id="PROC_STP_CLAIMS"><data key="node_entity_id">PROC_STP_CLAIMS</data><data key="node_entity_type">process</data><data key="node_canonical_name">Straight Through Processing</data><data key="node_acronym">STP</data><data key="node_domain">Benefits Processing / Modernization</data><data key="node_description">SSA end-to-end automated claims-processing approach documented for Medicare applications and expanding to certain retirement claims.</data><data key="node_observed_status">observed_current_modernization</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">June 29, 2026 SSA release says more than 340,000 Medicare claims had been processed using STP; no specific platform, codebase, or data-store topology is inferred.</data></node><node id="PROC_STUCK_SWEEPER"><data key="node_entity_id">PROC_STUCK_SWEEPER</data><data key="node_entity_type">process</data><data key="node_canonical_name">Stuck Sweeper</data><data key="node_domain">Representative Payee / Control</data><data key="node_description">Monthly control function documented by OIG that reviews eRPS applications in Ready to Process status over 14 days old and compares them with payment records.</data><data key="node_observed_status">audit_documented_2024</data><data key="node_observed_as_of">2024-09-25</data><data key="node_confidence">4</data><data key="node_notes">Current 2026 operation not independently confirmed in this run.</data></node><node id="PROC_SVB_CLAIM"><data key="node_entity_id">PROC_SVB_CLAIM</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title VIII Special Veterans Benefits Claim Processing</data><data key="node_acronym">SVB claim processing</data><data key="node_domain">Special Veterans Benefits</data><data key="node_description">SSA process for developing, adjudicating, maintaining, and paying Title VIII Special Veterans Benefits claims.</data><data key="node_observed_status">current_poms_retained_detailed_topology_old</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">4</data><data key="node_notes">Detailed processing instructions were revised in 2012 but remained in the 2026 POMS batch. Current SORN/CMA evidence separately confirms the SVB program data remains maintained.</data></node><node id="PROC_SVES_IDENTITY_VERIFICATION"><data key="node_entity_id">PROC_SVES_IDENTITY_VERIFICATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SVES Multi-Record SSN Identity Verification</data><data key="node_acronym">SVES Verification</data><data key="node_domain">External Data Exchange / Identity Verification</data><data key="node_description">SVES verification process that uses EVS functions and checks Numident, MBR, and SSR, permitting a positive verification against any of the three under the documented SVES process.</data><data key="node_observed_status">observed_current_documented_manual</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Manual revised July 2023; verification logic/rules/tolerances are intentionally not disclosed.</data></node><node id="PROC_SYSTEM_INFO_AS_PROOF"><data key="node_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Use of Existing SSA System Information as Acceptable Proof</data><data key="node_acronym">Systems-as-Proof</data><data key="node_domain">Claims / Evidence / Data Reuse</data><data key="node_description">Policy process allowing specified information already present in SSA systems to serve as acceptable proof of entitlement factors when prescribed conditions and proof codes are met.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS identifies MCS, MSSICS, MBR, SSR, Numident, DRAMS, EVID, and Evidence Portal as qualifying sources in defined circumstances.</data></node><node id="PROC_T16_UNDELIV_ADDRESS"><data key="node_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title XVI Undeliverable Notice Address Development</data><data key="node_acronym">SSI Undeliverable Notice</data><data key="node_domain">Title XVI / Address / Notices</data><data key="node_description">Field-office workflow for returned SSI notices: locate the claimant/recipient or payee, correct address when found, and invoke whereabouts-unknown procedures when unsuccessful.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current June 2026 POMS assigns returned SSI notices directly to servicing field offices for address correction and re-mailing.</data></node><node id="PROC_T2_DIRECT_COA"><data key="node_entity_id">PROC_T2_DIRECT_COA</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title II Direct Change of Address Processing</data><data key="node_acronym">Direct COA</data><data key="node_domain">Title II / Address Maintenance</data><data key="node_description">Technician-driven Title II change-of-address processing documented for field offices and teleservice centers, using the Title II post-entitlement/Redesign pathway and separate SSI input where necessary.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Detailed direct-input page is older, but the current June 2026 COA table of contents continues to retain the procedure. Current physical transaction architecture beyond named screens/programs is not inferred.</data></node><node id="PROC_T2_EXR_PROVISIONAL"><data key="node_entity_id">PROC_T2_EXR_PROVISIONAL</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title II EXR Provisional Benefit Initiation</data><data key="node_domain">Title II / Expedited Reinstatement</data><data key="node_description">Process for initiating eligible Title II expedited-reinstatement provisional benefits through POS.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Modeled from current POMS workflow; exact transaction transport is not published.</data></node><node id="PROC_T2_OVERPAY_EXPL"><data key="node_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title II Overpayment Explanation Process</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Operational workflow for explaining Title II overpayment facts and amounts using current SSA query, notice, and debt-management resources.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a business process; relationships do not imply undocumented point-to-point APIs.</data></node><node id="PROC_T2_OVERPAY_NOTICE_GENERATION"><data key="node_entity_id">PROC_T2_OVERPAY_NOTICE_GENERATION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Overpayment Notice Generation</data><data key="node_acronym">Overpayment Notice Generation</data><data key="node_domain">Payments / Debt</data><data key="node_description">Process for issuing written Title II overpayment notice after an employee or automated system discovers an overpayment.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">Policy identifies several notice-generation systems; no single exclusive system is inferred.</data></node><node id="PROC_T2_REINSTATE_PAYEE_T2R"><data key="node_entity_id">PROC_T2_REINSTATE_PAYEE_T2R</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Payee Selection Reinstatement via T2R</data><data key="node_domain">Title II / Payee Integration</data><data key="node_description">For S-6/S-8 situations, eRPS payee selection passes via Title II Redesign to MBR and can automatically reinstate benefit to newly selected payee; S-9 additionally requires POS.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_T2_SSI_ADDR_RECENCY"><data key="node_entity_id">PROC_T2_SSI_ADDR_RECENCY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II / SSI Address Recency Reconciliation</data><data key="node_acronym">Address Recency Reconciliation</data><data key="node_domain">Title II / Title XVI / Address Provenance</data><data key="node_description">Cross-program address-development step that compares the SSR address-change date with the MBR address-updated date and, when the SSI address is newer, uses the SSI address as the current Title II address for a POS update.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Technician-controlled reconciliation documented for Title II undeliverable mail; not an automatic SSR-to-MBR replication mechanism.</data></node><node id="PROC_T2_UNDELIV_ADDRESS"><data key="node_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title II Undeliverable Mail Address Development</data><data key="node_acronym">Undeliverable Mail Address Development</data><data key="node_domain">Title II / Address Maintenance</data><data key="node_description">Process for finding a current Title II beneficiary address after actionable mail is returned, using MBR/SSR comparison, telephone contact, financial institutions when applicable, and USPS, then updating program records through authorized post-entitlement channels.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The process distinguishes sources and requires development rather than treating an external address as automatically authoritative.</data></node><node id="PROC_TAA_MEDICARE"><data key="node_entity_id">PROC_TAA_MEDICARE</data><data key="node_entity_type">process</data><data key="node_canonical_name">Technology Assisted Adjudication for Standard Medicare-Only iClaims</data><data key="node_acronym">TAA</data><data key="node_domain">Title II / Medicare Claims</data><data key="node_description">Automated adjudication process released December 13, 2025 to identify standard Medicare-only internet claims and process qualifying claims to completion in CCE without technician intervention.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2026-01-30</data><data key="node_confidence">5</data><data key="node_notes">Keep separate from the broader FY2027 planned TAA for simple retirement and Medicare already represented elsewhere in the Atlas.</data></node><node id="PROC_TARGETED_WORK_REVIEW"><data key="node_entity_id">PROC_TARGETED_WORK_REVIEW</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Targeted Work Review Process</data><data key="node_acronym">TWRP</data><data key="node_domain">Disability / Earnings</data><data key="node_description">National process launched July 2025 for proposed work CDR decisions based on already available earnings data before requesting additional work reports, with simultaneous evidence and due-process notices.</data><data key="node_observed_status">documented_active_2025_early_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_TICKET_TO_WORK"><data key="node_entity_id">PROC_TICKET_TO_WORK</data><data key="node_entity_type">process</data><data key="node_canonical_name">Ticket to Work Program Transaction Process</data><data key="node_acronym">TTW Process</data><data key="node_domain">Ticket to Work / Work Incentives</data><data key="node_description">Business process for Ticket assignment/status, provider interaction, progress review and milestone/outcome payments.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_TRO"><data key="node_entity_id">PROC_TRO</data><data key="node_entity_type">process</data><data key="node_canonical_name">Tax Refund Offset</data><data key="node_acronym">TRO</data><data key="node_domain">Debt &amp; External Collections</data><data key="node_description">Collection process using Treasury to offset Federal income tax refunds for eligible delinquent SSA debts.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_TTW_EPAY"><data key="node_entity_id">PROC_TTW_EPAY</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">Ticket to Work Electronic Payment Process</data><data key="node_acronym">E-PAY</data><data key="node_domain">Ticket to Work / Payments</data><data key="node_description">Automated SSA Ticket-to-Work payment process for qualified Employment Networks; complements rather than replaces Portal-submitted payment requests.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_UMC_SPECIAL_CDR"><data key="node_entity_id">PROC_UMC_SPECIAL_CDR</data><data key="node_entity_type">process</data><data key="node_canonical_name">Uneffectuated Medical Cessation Special CDR Processing</data><data key="node_acronym">UMC Special CDR</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">Special process for identified uneffectuated medical cessation cases with determinations made before January 1, 2006, including new CDR establishment and effectuation controls.</data><data key="node_observed_status">observed_current_legacy_workload_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current procedure governs a bounded legacy workload; it does not imply new cases are added to UMCCC.</data></node><node id="PROC_UNKNOWN_ADDRESS_CLAIM"><data key="node_entity_id">PROC_UNKNOWN_ADDRESS_CLAIM</data><data key="node_entity_type">process</data><data key="node_canonical_name">Title II Unknown Address Claim Development</data><data key="node_acronym">Unknown Address Claim</data><data key="node_domain">Title II / Claims / Address</data><data key="node_description">Title II claims workflow used when entitlement is established but the claimant’s whereabouts are unknown; uses SSA records and external leads, documents development in MCS, and can result in MBR S-6 suspense.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">MEF and SSR are explicitly queried as locate-lead sources; this does not mean either contains an authoritative current address.</data></node><node id="PROC_UPLOAD_CREDENTIAL_STEPUP"><data key="node_entity_id">PROC_UPLOAD_CREDENTIAL_STEPUP</data><data key="node_entity_type">process</data><data key="node_canonical_name">Upload Documents Credential Step-Up</data><data key="node_domain">Identity / Digital Forms</data><data key="node_description">Authentication step-up process that requires an advanced credential before selected sensitive forms can be electronically submitted.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA Forms page lists SSA-454-BK, SSA-827, SSA-2574, SSA-2935, and SSA-8510 as requiring additional identity verification.</data></node><node id="PROC_UPLOAD_CUSTOMER_INIT"><data key="node_entity_id">PROC_UPLOAD_CUSTOMER_INIT</data><data key="node_entity_type">process</data><data key="node_canonical_name">Upload Documents Customer-Initiated Submission</data><data key="node_acronym">Customer-Initiated Upload</data><data key="node_domain">Digital Intake / Evidence</data><data key="node_description">Self-service Upload Documents workflow allowing authenticated customers to initiate submission of selected SSA forms and evidence without a technician-created request.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Forms became customer-initiated 2025-03-29 and selected evidence followed 2025-06-28. Original/certified evidence remains excluded.</data></node><node id="PROC_UPLOAD_SIGNED_APP_INTAKE"><data key="node_entity_id">PROC_UPLOAD_SIGNED_APP_INTAKE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Upload Documents Signed Benefit Application Intake</data><data key="node_acronym">Upload Signed Application Intake</data><data key="node_domain">Digital Intake / Claims / Signature</data><data key="node_description">Technician processing workflow for benefit applications electronically signed and submitted through Upload Documents.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes">POMS requires technicians to treat these as paper applications operationally, load data into MCS or CCE, receipt ATTEST, and specify the actual signature method in remarks.</data></node><node id="PROC_UPLOAD_TECH_INIT"><data key="node_entity_id">PROC_UPLOAD_TECH_INIT</data><data key="node_entity_type">process</data><data key="node_canonical_name">Upload Documents Technician-Initiated Submission</data><data key="node_acronym">Technician-Initiated Upload</data><data key="node_domain">Digital Intake / Evidence</data><data key="node_description">Original Upload Documents workflow in which an SSA technician creates a request task in TED and the customer receives a link to submit requested forms or evidence.</data><data key="node_observed_status">observed_current_parallel_path</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">EM-25024 says the process was the only path before 2025-03-29; current instructions still distinguish open technician requests from customer-initiated submissions.</data></node><node id="PROC_US_MAILING_BENEF_ABROAD"><data key="node_entity_id">PROC_US_MAILING_BENEF_ABROAD</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">U.S. Mailing Address for Beneficiary Abroad Control</data><data key="node_acronym">US Mailing Abroad</data><data key="node_domain">Title II / International / Address Provenance</data><data key="node_description">Policy control for beneficiaries abroad who use a U.S. mailing address while SSA separately retains the need to know actual residence and, generally, a 240 listing code.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2024-02-07</data><data key="node_confidence">5</data><data key="node_notes">Does not establish a new address repository or synchronization mechanism.</data></node><node id="PROC_VAPT_PRIORITY"><data key="node_entity_id">PROC_VAPT_PRIORITY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">VAPT Priority Disability Claim Processing</data><data key="node_acronym">VAPT Priority Processing</data><data key="node_domain">Disability / Priority Processing</data><data key="node_description">Expedited claim-development and adjudication process for veterans with a VA 100 percent permanent and total disability compensation rating.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">VAPT cases receive priority through all levels; DDS treats the SSA/VA exchange as sufficient VAPT verification and develops a permanent address because claimants may be in transit.</data></node><node id="PROC_VENDOR_REPO_SUBMISSION"><data key="node_entity_id">PROC_VENDOR_REPO_SUBMISSION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Vendor Repository Submission Process</data><data key="node_acronym">Vendor Repository Submission</data><data key="node_domain">procurement / market research</data><data key="node_description">Email-based process by which vendors submit capability statements with prescribed subject tags and attachments for inclusion in SSA market-research repository.</data><data key="node_observed_status">observed_current_guidance</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current guidance specifies VendorRepository@ssa.gov, subject-tag structure, common attachments, and 5MB total size.</data></node><node id="PROC_VR_COST_REIMB"><data key="node_entity_id">PROC_VR_COST_REIMB</data><data key="node_entity_type">process</data><data key="node_canonical_name">Vocational Rehabilitation Cost Reimbursement Process</data><data key="node_acronym">VR Cost Reimbursement</data><data key="node_domain">Vocational Rehabilitation / Reimbursement</data><data key="node_description">SSA process reimbursing State VR agencies when qualifying SSDI/SSI beneficiaries achieve the required sustained earnings outcome.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_WAGE_SCOUTING"><data key="node_entity_id">PROC_WAGE_SCOUTING</data><data key="node_entity_type">process</data><data key="node_canonical_name">Wage Scouting</data><data key="node_acronym">EWSR</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">Earnings-development process initiated through the Wage Scouting screen to identify employer reports or obtain report details when earnings discrepancies cannot be resolved from queries alone.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">EWSR is the published screen identifier in the cited POMS; the letters are not expanded beyond the source label.</data></node><node id="PROC_WAGE_VERIFY"><data key="node_entity_id">PROC_WAGE_VERIFY</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSA Wage Verification Process</data><data key="node_domain">Earnings / Verification</data><data key="node_description">Business process for establishing wage and employment evidence using PIE/PDP data, pay stubs, approved electronic wage-verification services and other sources under program rules.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a process spanning SSI and disability/work workflows; not a single application.</data></node><node id="PROC_WAIVER_2PIN"><data key="node_entity_id">PROC_WAIVER_2PIN</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Overpayment Waiver Approval Second-PIN Review</data><data key="node_acronym">2-PIN</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Waiver approvals exceeding $2,000 require a second reviewer credential; approval signer differs from the initial decision maker; amount tier determines review level.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_WAIVER_PERSONAL_CONFERENCE"><data key="node_entity_id">PROC_WAIVER_PERSONAL_CONFERENCE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Overpayment Waiver Personal Conference Determination</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Waiver factfinding, second adjudicator separation, documented decision, notification, and evidence upload using DMS for Title II or direct SSR update for SSI.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROC_WCPDB_HIGHER_RIB_NOTICE"><data key="node_entity_id">PROC_WCPDB_HIGHER_RIB_NOTICE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">WC/PDB Higher Retirement Benefit Notification Process</data><data key="node_acronym">WC/PDB RIB Notification</data><data key="node_domain">Title II / Disability / Retirement / Customer Service</data><data key="node_description">Process for identifying disabled beneficiaries whose benefits are reduced for workers compensation or public disability benefits, comparing potential retirement benefits, notifying them of filing options, and documenting filing decisions.</data><data key="node_observed_status">observed_current_policy_process</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current OIG review documents the process and policy in force during 2026; no exclusive generating application is inferred.</data></node><node id="PROGRAM_CDI"><data key="node_entity_id">PROGRAM_CDI</data><data key="node_entity_type">program</data><data key="node_canonical_name">Cooperative Disability Investigations Program</data><data key="node_acronym">CDI</data><data key="node_domain">Program Integrity / Disability Fraud</data><data key="node_description">Joint anti-fraud program that investigates questionable disability claims and suspected disability fraud before or after benefit award.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROGRAM_IT_SECURITY"><data key="node_entity_id">PROGRAM_IT_SECURITY</data><data key="node_entity_type">program_area</data><data key="node_canonical_name">IT Security</data><data key="node_acronym">IT Security</data><data key="node_domain">Cybersecurity / Portfolio</data><data key="node_description">SSA FY2027 budget program area covering cybersecurity modernization, identity/access/risk management, security operations/threat response, and assessment/application security initiatives.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Budget-plan entity; does not imply each initiative is fully deployed.</data></node><node id="PROG_HRS"><data key="node_entity_id">PROG_HRS</data><data key="node_entity_type">program</data><data key="node_canonical_name">Health and Retirement Study (HRS)</data><data key="node_acronym">HRS</data><data key="node_domain">Research / External Administrative Data Linkage</data><data key="node_description">University of Michigan longitudinal study of Americans over age 50 that receives consent-based SSA-linked administrative data for approved research use.</data><data key="node_observed_status">ongoing_supported_research_program</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA FY2027 budget describes continuing HRS support through jointly financed cooperative agreements with the National Institute on Aging; internal survey technology is outside Atlas scope.</data></node><node id="PROG_R194_ARDRAW"><data key="node_entity_id">PROG_R194_ARDRAW</data><data key="node_entity_type">grant_program</data><data key="node_canonical_name">Analyzing Relationships Between Disability, Rehabilitation, and Work</data><data key="node_domain">Procurement &amp; Grants</data><data key="node_description">SSA OAG identifies ARDRAW as a research and demonstration grant example.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROG_R194_PABSS"><data key="node_entity_id">PROG_R194_PABSS</data><data key="node_entity_type">grant_program</data><data key="node_canonical_name">Protection and Advocacy for Beneficiaries of Social Security</data><data key="node_domain">Procurement &amp; Grants</data><data key="node_description">SSA OAG identifies PABSS among service grants.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROG_R194_RDRC"><data key="node_entity_id">PROG_R194_RDRC</data><data key="node_entity_type">grant_program</data><data key="node_canonical_name">Retirement and Disability Research Consortium</data><data key="node_domain">Procurement &amp; Grants</data><data key="node_description">SSA OAG identifies RDRC as a research and demonstration grant example.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROG_R194_SPSSB"><data key="node_entity_id">PROG_R194_SPSSB</data><data key="node_entity_type">grant_program</data><data key="node_canonical_name">Strengthening Protections for Social Security Beneficiaries Representative Payee Review Grants</data><data key="node_domain">Procurement &amp; Grants</data><data key="node_description">SSA OAG identifies SPSSB representative-payee service grants covering onsite reviews.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROG_R194_WIPA"><data key="node_entity_id">PROG_R194_WIPA</data><data key="node_entity_type">grant_program</data><data key="node_canonical_name">Work Incentives Planning and Assistance Service Grants</data><data key="node_domain">Procurement &amp; Grants</data><data key="node_description">SSA OAG identifies WIPA as a service grant supporting beneficiaries returning to work.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROG_SNAP"><data key="node_entity_id">PROG_SNAP</data><data key="node_entity_type">external_program</data><data key="node_canonical_name">Supplemental Nutrition Assistance Program</data><data key="node_acronym">SNAP</data><data key="node_domain">External Program / Nutrition Assistance</data><data key="node_description">Federal nutrition assistance program for which CAP streamlines enrollment of eligible SSI recipients.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-08-04</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="PROJ_BI_TOOL_MIGRATION"><data key="node_entity_id">PROJ_BI_TOOL_MIGRATION</data><data key="node_entity_type">project</data><data key="node_canonical_name">Business Intelligence Tool Migration</data><data key="node_domain">Enterprise Analytics / Modernization</data><data key="node_description">SSA IT investment to migrate business-intelligence tooling; OIG lists it among sampled discontinued investments.</data><data key="node_observed_status">canceled_by_2025_03</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">OIG reports a FY2015-2021 investment period, $37.6 million actual cost as of 2025-09-30, and canceled status as of March 2025. Exact cancellation date and target BI platform are not publicly established.</data></node><node id="PROJ_CCS_2019"><data key="node_entity_id">PROJ_CCS_2019</data><data key="node_entity_type">project</data><data key="node_canonical_name">Consolidated Claims System</data><data key="node_acronym">CCS</data><data key="node_domain">Benefits / Claims Modernization</data><data key="node_description">FY2019-FY2022 modernization effort described as a planned consolidated claims system with a modern claims-intake interface and a single place to work RSDI, SSI, and Medicare claims.</data><data key="node_observed_status">historical_planned_effort_lineage_to_cce_unresolved</data><data key="node_observed_as_of">2019</data><data key="node_confidence">4</data><data key="node_notes">FY2020 budget uses the name Consolidated Claims System (CCS). OIG separately says SSA began planning Consolidated Claims Experience (CCE) in 2017. No authoritative source located in this run establishes that CCS and CCE are the same named artifact or a formal rename, so they remain separate with a conflict note.</data></node><node id="PROJ_COMP_SERVICES"><data key="node_entity_id">PROJ_COMP_SERVICES</data><data key="node_entity_type">project</data><data key="node_canonical_name">Title II Computational Services Modernization Initiative</data><data key="node_acronym">Computational Services</data><data key="node_domain">Title II / Computation</data><data key="node_description">Benefits-domain modernization initiative to convert decades-old Title II computational utilities from COBOL into service-oriented implementations written in Java.</data><data key="node_observed_status">historical_modernization_initiative</data><data key="node_observed_as_of">2019</data><data key="node_confidence">5</data><data key="node_notes">FY2020 budget names General Insured Status Utility, GRUMPI, GRATES, and Entitlement/Eligibility Utility as conversion targets.</data></node><node id="PROJ_DEBT_COLLECTION_MOD"><data key="node_entity_id">PROJ_DEBT_COLLECTION_MOD</data><data key="node_entity_type">project</data><data key="node_canonical_name">Debt Collection Modernization</data><data key="node_domain">Debt Modernization</data><data key="node_description">FY2026 program-integrity IT investment for modernizing debt collection, including government-wide shared-service use.</data><data key="node_observed_status">budgeted_fy2026</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">FY2026 Congressional Justification planned $22.9M total cost; this is a budget plan, not an obligation/expenditure total.</data></node><node id="PROJ_DMP"><data key="node_entity_id">PROJ_DMP</data><data key="node_entity_type">project</data><data key="node_canonical_name">Debt Management Product</data><data key="node_acronym">DMP</data><data key="node_domain">Debt Modernization</data><data key="node_description">SSA modernization initiative intended to consolidate debt collection, storage, monitoring, reporting and waiver processing.</data><data key="node_observed_status">conflicting_status_reported_resumed_development_as_of_2026_02</data><data key="node_observed_as_of">2026-02-25</data><data key="node_confidence">4</data><data key="node_notes">FY2025 AFR states SSA is no longer pursuing DMP after the earlier pause; historical OIG reports remain relevant to sunk cost and lessons learned. FY2027 Good Accounting report, with statuses current through 2026-02-25, separately says SSA resumed development of the modernized debt management system in FY2025 and moved closer to implementation. This conflicts with the FY2025 AFR statement that SSA was no longer pursuing DMP; both are retained and current production/implementation status remains unresolved.</data></node><node id="PROJ_DRS"><data key="node_entity_id">PROJ_DRS</data><data key="node_entity_type">project</data><data key="node_canonical_name">Disability Research Surveys</data><data key="node_acronym">DRS</data><data key="node_domain">Disability / Research</data><data key="node_description">Research project encompassing NBS, New Applicant Survey and a planned children/youth survey.</data><data key="node_observed_status">terminated_fy2025</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2026 budget says the DRS vendor contract was terminated in FY2025.</data></node><node id="PROJ_EEA"><data key="node_entity_id">PROJ_EEA</data><data key="node_entity_type">project</data><data key="node_canonical_name">Electronic Evidence Acquisition</data><data key="node_acronym">EEA</data><data key="node_domain">Disability / Medical Evidence</data><data key="node_description">Modernization initiative for electronic submission of medical evidence, HIT-partner interoperability, workload optimization, and ERE modernization.</data><data key="node_observed_status">historical_modernization_fy2024</data><data key="node_observed_as_of">2024</data><data key="node_confidence">5</data><data key="node_notes">FY2025 budget describes FY2024 work; current architecture lineage beyond stated targets is not inferred.</data></node><node id="PROJ_ENHANCED_MEDICAL_ACQ"><data key="node_entity_id">PROJ_ENHANCED_MEDICAL_ACQ</data><data key="node_entity_type">project</data><data key="node_canonical_name">Enhanced Medical Acquisition and Processing</data><data key="node_acronym">Enhanced Medical Acquisition</data><data key="node_domain">Disability / Evidence</data><data key="node_description">FY2027 initiative to update NCPS features used by DDSs, centralize forms and medical-evidence requests, expand case-processing functions, and use AI to help identify determination-ready claims.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">FY2027 requested cost: $2.9 million.</data></node><node id="PROJ_ENTERPRISE_CRM"><data key="node_entity_id">PROJ_ENTERPRISE_CRM</data><data key="node_entity_type">project</data><data key="node_canonical_name">Enterprise Customer Relationship Management System</data><data key="node_acronym">Enterprise CRM</data><data key="node_domain">Customer Service / CRM</data><data key="node_description">Planned enterprise CRM modernization intended to provide a 360-degree customer view and integrate with service-delivery applications.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget request: $46.8M.</data></node><node id="PROJ_ENTERPRISE_DOCUMENT_INTAKE"><data key="node_entity_id">PROJ_ENTERPRISE_DOCUMENT_INTAKE</data><data key="node_entity_type">project</data><data key="node_canonical_name">Enterprise Document Intake</data><data key="node_domain">Evidence / Document Intake</data><data key="node_description">FY2026 modernization initiative allowing customers to upload evidence and signed forms for automatic transmission to downstream systems.</data><data key="node_observed_status">budget_plan_fy2026</data><data key="node_observed_as_of">2025-05-01</data><data key="node_confidence">5</data><data key="node_notes">FY2026 budget request: $36.0M; no named downstream system is inferred.</data></node><node id="PROJ_ENTERPRISE_DOC_MGMT"><data key="node_entity_id">PROJ_ENTERPRISE_DOC_MGMT</data><data key="node_entity_type">project</data><data key="node_canonical_name">Enterprise Document Management Product</data><data key="node_acronym">Enterprise Document Management</data><data key="node_domain">Evidence / Document Management</data><data key="node_description">Planned enterprise document-management product intended to consolidate existing document-management solutions and simplify downstream integration.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget request: $27.4M.</data></node><node id="PROJ_ESERVICES_ENTERPRISE_API"><data key="node_entity_id">PROJ_ESERVICES_ENTERPRISE_API</data><data key="node_entity_type">project</data><data key="node_canonical_name">eServices Commissioner Priority - Enterprise Application Programming Interface Development</data><data key="node_domain">Digital Services / Integration Modernization</data><data key="node_description">Commissioner-priority SSA IT investment for enterprise application-programming-interface development.</data><data key="node_observed_status">canceled_by_2025_03</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">OIG reports FY2021 investment period, $7.9 million actual cost as of 2025-09-30, and canceled status as of March 2025. No specific API gateway, platform, or deployed enterprise service is inferred.</data></node><node id="PROJ_ETDMS"><data key="node_entity_id">PROJ_ETDMS</data><data key="node_entity_type">project</data><data key="node_canonical_name">Enterprise Test Data Management System</data><data key="node_acronym">ETDMS</data><data key="node_domain">Infrastructure / Testing / Data Management</data><data key="node_description">SSA project intended to provide VDB users with enterprise test-data management capabilities for system testing and to coordinate with the Data Access the Life Cycle initiative.</data><data key="node_observed_status">cataloged_project_intent_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current federal data catalog metadata uses future/intended language, so the Atlas does not mark ETDMS as deployed production capability.</data></node><node id="PROJ_EWCDR_FY26"><data key="node_entity_id">PROJ_EWCDR_FY26</data><data key="node_entity_type">project</data><data key="node_canonical_name">Electronic Work Continuing Disability Review</data><data key="node_acronym">eWCDR</data><data key="node_domain">Disability / Work CDR</data><data key="node_description">FY2026 modernization initiative intended to accept wage and employment information from payroll data providers.</data><data key="node_observed_status">budget_plan_fy2026</data><data key="node_observed_as_of">2025-05-01</data><data key="node_confidence">5</data><data key="node_notes">FY2026 budget request: $8.0M. Not asserted to be identical to the FY2027 Work CDR Product.</data></node><node id="PROJ_EXHIBITING_PREP"><data key="node_entity_id">PROJ_EXHIBITING_PREP</data><data key="node_entity_type">project</data><data key="node_canonical_name">Improved Exhibiting and Prep Work</data><data key="node_domain">Adjudication / Evidence Preparation</data><data key="node_description">FY2027 planned updates to adjudication systems to improve evidence review/exhibiting and eliminate duplicate evidence.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget request: $0.4M; affected systems are not named publicly in the budget table.</data></node><node id="PROJ_FORMS_MODERNIZATION"><data key="node_entity_id">PROJ_FORMS_MODERNIZATION</data><data key="node_entity_type">project</data><data key="node_canonical_name">Forms Modernization</data><data key="node_domain">Digital Forms / Claims</data><data key="node_description">FY2026 initiative to let customers fill and submit forms online and make form data available in later benefit-adjudication steps.</data><data key="node_observed_status">budget_plan_fy2026</data><data key="node_observed_as_of">2025-05-01</data><data key="node_confidence">5</data><data key="node_notes">FY2026 budget request: $10.0M.</data></node><node id="PROJ_HEARING_SCHED"><data key="node_entity_id">PROJ_HEARING_SCHED</data><data key="node_entity_type">project</data><data key="node_canonical_name">Streamline Hearing Scheduling Product</data><data key="node_domain">Hearings &amp; Appeals / Scheduling</data><data key="node_description">FY2027 planned product integrated with NCPS to provide representative and ALJ availability and facilitate hearing scheduling.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget request: $11.7M.</data></node><node id="PROJ_IMAGEN_EXPANSION"><data key="node_entity_id">PROJ_IMAGEN_EXPANSION</data><data key="node_entity_type">project</data><data key="node_canonical_name">Increase IMAGEN Adoption and Expansion</data><data key="node_acronym">IMAGEN Expansion</data><data key="node_domain">Disability / AI / Evidence</data><data key="node_description">FY2027 initiative to increase adoption and expand IMAGEN, including integrations with other systems and user-interface improvements.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">FY2027 requested cost: $2.5 million.</data></node><node id="PROJ_MYSSA_ALL_COMMS"><data key="node_entity_id">PROJ_MYSSA_ALL_COMMS</data><data key="node_entity_type">project</data><data key="node_canonical_name">Notices and All Customer Communications on my Social Security</data><data key="node_acronym">All Customer Communications on mySSA</data><data key="node_domain">Digital Service / Communications</data><data key="node_description">FY2027 modernization initiative to make agency-generated written communications and notices accessible online through my Social Security and expand opt-in digital delivery.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget request lists $17.5 million; implementation architecture and relationship to CCM/notice-generation systems are not inferred.</data></node><node id="PROJ_MYSSA_MOBILE"><data key="node_entity_id">PROJ_MYSSA_MOBILE</data><data key="node_entity_type">project</data><data key="node_canonical_name">my Social Security Modernization and Mobile App</data><data key="node_acronym">mySSA Modernization</data><data key="node_domain">Digital Service</data><data key="node_description">Modernization project for my Social Security, including mobile-app capabilities described in FY2027 budget materials.</data><data key="node_observed_status">planned_launch_fy2026_with_fy2027_expansion</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget, issued April 3 2026, says SSA planned to launch the mobile app in FY2026 and invest in expansion during FY2027. No later first-party launch confirmation was located in Run 65; launch completion is not inferred.</data></node><node id="PROJ_NCPS_SCHED_FY26"><data key="node_entity_id">PROJ_NCPS_SCHED_FY26</data><data key="node_entity_type">project</data><data key="node_canonical_name">NCPS Scheduling Initiative</data><data key="node_acronym">NCPS Scheduling</data><data key="node_domain">Hearings &amp; Appeals / Scheduling</data><data key="node_description">FY2026 initiative to integrate calendar availability into NCPS for parties needed to schedule hearings and expose representative availability.</data><data key="node_observed_status">budget_plan_fy2026</data><data key="node_observed_as_of">2025-05-01</data><data key="node_confidence">5</data><data key="node_notes">FY2026 budget request: $3.0M. No identity with the FY2027 Streamline Hearing Scheduling Product is inferred.</data></node><node id="PROJ_NETWORK_ASSESS_2026"><data key="node_entity_id">PROJ_NETWORK_ASSESS_2026</data><data key="node_entity_type">project</data><data key="node_canonical_name">SSA Network Infrastructure Assessment and Future-State Recommendations</data><data key="node_domain">Infrastructure / Network / Modernization</data><data key="node_description">Independent third-party assessment project examining SSA current network infrastructure and recommending a future state.</data><data key="node_observed_status">observed_in_progress_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Government award description validates the assessment scope. Specific network components, findings, target architecture, and recommendations are not public in the award record.</data></node><node id="PROJ_NUMIDENT_VERIFY_CONSOLIDATION"><data key="node_entity_id">PROJ_NUMIDENT_VERIFY_CONSOLIDATION</data><data key="node_entity_type">project</data><data key="node_canonical_name">Centralized Numident Verification Platform Consolidation</data><data key="node_domain">Identity / Data Exchange</data><data key="node_description">Modernization effort to extend an already-established FY2026 centralized data-exchange application by incorporating some Numident-verification systems.</data><data key="node_observed_status">partial_data_exchange_centralization_complete_numident_expansion_planned</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">August 2026 OIG says SSA had already coordinated and combined several data-exchange systems into a centralized application in FY2026, while incorporation of some Numident verification systems remained planned. OIG does not name the application or systems to be incorporated. Run 85 retains OIG September 3, 2026 finding that consolidation is planned but matching-criteria governance and periodic risk assessment also require attention; SSA agreed to OIG recommendations.</data></node><node id="PROJ_OIG_ANALYTICS_PLATFORM"><data key="node_entity_id">PROJ_OIG_ANALYTICS_PLATFORM</data><data key="node_entity_type">project</data><data key="node_canonical_name">OIG Internal Analytics Platform</data><data key="node_domain">OIG Data / Analytics</data><data key="node_description">Analytics platform OIG began building in FY2026 to streamline and expedite data extractions for audits and investigations.</data><data key="node_observed_status">under_construction_fy2026</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes">Testimony describes index-file construction, documentation, and requirements gathering; platform product and final deployment are not public.</data></node><node id="PROJ_PC_IMPROVEMENT"><data key="node_entity_id">PROJ_PC_IMPROVEMENT</data><data key="node_entity_type">project</data><data key="node_canonical_name">Processing Center Improvement</data><data key="node_acronym">PC Improvement</data><data key="node_domain">Title II / Processing Centers</data><data key="node_description">FY2027 modernization initiative to refine and expand processes so fewer items require manual review and fall into Processing Center backlogs.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">FY2027 requested cost: $6.3 million.</data></node><node id="PROJ_PE_MODERNIZATION"><data key="node_entity_id">PROJ_PE_MODERNIZATION</data><data key="node_entity_type">project</data><data key="node_canonical_name">Benefits Post-Entitlement Modernization Initiative</data><data key="node_acronym">PE initiative</data><data key="node_domain">Title II / Post-Entitlement</data><data key="node_description">Benefits-domain initiative intended to streamline post-entitlement processing, reduce exceptions and redundancy, and support more automated entitlement, overpayment, underpayment, accounting, and notice actions.</data><data key="node_observed_status">historical_modernization_initiative</data><data key="node_observed_as_of">2019</data><data key="node_confidence">5</data><data key="node_notes">FY2020 budget describes planned redundancy reduction among the MCS Pending File, Title II Shared Database, and MBR and planned removal of MCS Pending File dependency on legacy IDMS database structure.</data></node><node id="PROJ_RCIRP"><data key="node_entity_id">PROJ_RCIRP</data><data key="node_entity_type">project</data><data key="node_canonical_name">Re-engineered Comprehensive Integrity Review Process Operational Case Workload</data><data key="node_acronym">rCIRP</data><data key="node_domain">Program Integrity / Modernization</data><data key="node_description">SSA re-engineering investment intended to replace or change the legacy Comprehensive Integrity Review Process case-workload approach.</data><data key="node_observed_status">on_hold_after_partial_implementation</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">OIG reports partial implementation in parallel with the legacy process in 2021, IT IRB defunding except contractor support in FY2022, later reversion to the legacy process, and $34.4 million actual cost as of 2025-09-30.</data></node><node id="PROJ_SSI_UNDERPAY_UI"><data key="node_entity_id">PROJ_SSI_UNDERPAY_UI</data><data key="node_entity_type">project</data><data key="node_canonical_name">SSI Underpayments User Interface</data><data key="node_acronym">SSI Underpayments UI</data><data key="node_domain">Title XVI / Payment Accuracy</data><data key="node_description">Planned user interface intended to add systems controls for SSI underpayments, including support for the required two-PIN review process.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-02-25</data><data key="node_confidence">5</data><data key="node_notes">FY2027 Good Accounting report says SSA anticipates beginning development in FY2027.</data></node><node id="PROJ_SSN_CARD_MODERNIZATION"><data key="node_entity_id">PROJ_SSN_CARD_MODERNIZATION</data><data key="node_entity_type">project</data><data key="node_canonical_name">Social Security Number Card Services Modernization</data><data key="node_acronym">SSN Card Services Modernization</data><data key="node_domain">Identity / Enumeration</data><data key="node_description">Planned modernization of SSN card services including a digital solution for customers to view SSN information on mobile devices.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget request: $19.4M.</data></node><node id="PROJ_SSOARS_FMQSMO"><data key="node_entity_id">PROJ_SSOARS_FMQSMO</data><data key="node_entity_type">modernization_project</data><data key="node_canonical_name">SSOARS FM QSMO Core Financial System Replacement</data><data key="node_acronym">FM QSMO replacement</data><data key="node_domain">Finance / Modernization</data><data key="node_description">SSA FY2025 plan to evaluate/procure a Treasury-approved Financial Management Quality Service Management Office core financial system and implementation services, with tentative cutover at beginning of FY2029 if procurement timing is met.</data><data key="node_observed_status">planned_fy2026_procurement_status_unconfirmed</data><data key="node_observed_as_of">2026-01-15</data><data key="node_confidence">4</data><data key="node_notes">Plan stated in FY2025 AFR; this run found no later first-party SSA award/cutover confirmation.</data></node><node id="PROJ_TAA_SIMPLE_RM"><data key="node_entity_id">PROJ_TAA_SIMPLE_RM</data><data key="node_entity_type">project</data><data key="node_canonical_name">Technology Assisted Adjudication for Simple Retirement and Medicare</data><data key="node_domain">Retirement / Medicare Claims</data><data key="node_description">FY2027 planned tool to process simple retirement and Medicare claims and highlight issues in more complex claims for technician review.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget request: $3.4M.</data></node><node id="PROJ_WORK_CDR"><data key="node_entity_id">PROJ_WORK_CDR</data><data key="node_entity_type">project</data><data key="node_canonical_name">Work Continuing Disability Review Product</data><data key="node_acronym">Work CDR Product</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">Planned modernized application supporting work reports, paystubs, work reviews, notices/forms and workload management for disability work CDR processing.</data><data key="node_observed_status">planned_fy2027</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">FY2027 budget request: $8.8M.
Run 103, FY2025 SSA AFR: agency planned a new Electronic Work CDR MVP by end FY2026. Launch as of 2026-10-07 is not independently confirmed; do not mark operational based solely on historical plan.</data></node><node id="PROJ_YTED"><data key="node_entity_id">PROJ_YTED</data><data key="node_entity_type">demonstration_project</data><data key="node_canonical_name">Youth Transition Exploration Demonstration</data><data key="node_acronym">YTED</data><data key="node_domain">Title XVI / Demonstration / Youth Transition</data><data key="node_description">SSA demonstration whose SSI participants are documented in CCE and identified by a special code on the Supplemental Security Record.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-02-06</data><data key="node_confidence">5</data><data key="node_notes">POMS section applies to participants with current SSI entitlement.</data></node><node id="QRY_ALPHADENT"><data key="node_entity_id">QRY_ALPHADENT</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Alphadent File</data><data key="node_acronym">Alphadent</data><data key="node_domain">Identity / Enumeration</data><data key="node_description">SSA master-file query/file referenced in current IRS Form 3857 identity resolution alongside Numident, DEQY, ERQY and MBR.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2025-06-13</data><data key="node_confidence">4</data><data key="node_notes">Public POMS establishes operational use but not physical storage, database technology, field structure, or hosting.</data></node><node id="QRY_COLLECTION"><data key="node_entity_id">QRY_COLLECTION</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Collection Query</data><data key="node_domain">Debt &amp; Overpayments / Queries</data><data key="node_description">SSA query capability used in overpayment and Treasury Offset Program case review alongside MBR, ROAR, PHUS, SSR, and Evidence Portal.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">4</data><data key="node_notes">OIG names Collection Query but does not describe its technical implementation or data source.</data></node><node id="QRY_DEQY"><data key="node_entity_id">QRY_DEQY</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Detail Earnings Query</data><data key="node_acronym">DEQY</data><data key="node_domain">Earnings / Queries</data><data key="node_description">Immediate online query that displays detailed earnings and related data extracted from the Master Earnings File and Employer Identification File.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="QRY_EARQ_LEGACY"><data key="node_entity_id">QRY_EARQ_LEGACY</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Legacy Earnings Alert Query</data><data key="node_acronym">EARQ</data><data key="node_domain">Earnings / Queries</data><data key="node_description">Legacy Earnings Alert Queries display used through PCOM and explicitly retained for interim operational use in July 2026.</data><data key="node_observed_status">legacy_but_instructed_for_interim_use</data><data key="node_observed_as_of">2026-07-14</data><data key="node_confidence">5</data><data key="node_notes">Emergency message calls this the legacy EARQ system/application in PCOM; retirement date is not public.</data></node><node id="QRY_ECO_MASTER"><data key="node_entity_id">QRY_ECO_MASTER</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">ECO Master Query</data><data key="node_acronym">ECO Master Query</data><data key="node_domain">Debt &amp; External Collections / Queries</data><data key="node_description">Query used to review ECO Master information including AWG status, employer information, notice history and related external-collection data.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2022-08-22</data><data key="node_confidence">5</data><data key="node_notes">Accessible from the External Collection Operation Menu (TRMU) under current public POMS.</data></node><node id="QRY_ERPC_SEARCH"><data key="node_entity_id">QRY_ERPC_SEARCH</data><data key="node_entity_type">query_interface</data><data key="node_canonical_name">eRPC Search Data / Text Search</data><data key="node_acronym">RPC Search</data><data key="node_domain">Disability / Program Consultation Analytics</data><data key="node_description">Search functions in eRPC used to locate RPC cases by case number or criteria and search case narrative text.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="QRY_FACT"><data key="node_entity_id">QRY_FACT</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Full Account Query</data><data key="node_acronym">FACT</data><data key="node_domain">Title II / Queries</data><data key="node_description">Full MBR query used to inspect Title II beneficiary/account history.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA procedures continue to direct FACT use.</data></node><node id="QRY_HEAR"><data key="node_entity_id">QRY_HEAR</data><data key="node_entity_type">query_interface</data><data key="node_canonical_name">Hearing Query Selection Screen</data><data key="node_acronym">HEAR</data><data key="node_domain">Hearings &amp; Appeals / Queries</data><data key="node_description">Medical-hearing status query available from the Queries link on the eView Case Documents tab after CPMS retirement.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current EM identifies HEAR as the post-CPMS medical-hearing status lookup path.</data></node><node id="QRY_HIQR"><data key="node_entity_id">QRY_HIQR</data><data key="node_entity_type">query_interface</data><data key="node_canonical_name">HI/SMI Query Response</data><data key="node_acronym">HIQR</data><data key="node_domain">Medicare / Queries</data><data key="node_description">Query response screen used to verify Medicare start dates, billing information, and Medicare card issuance after TAA processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-01-30</data><data key="node_confidence">5</data><data key="node_notes">Architecture and authoritative backing store are not stated in the public emergency message.</data></node><node id="QRY_MEDQ"><data key="node_entity_id">QRY_MEDQ</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Medicare Query System</data><data key="node_acronym">MEDQ</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">SSA query system used in MAPS verification procedures to view prior agency-data entries including OPM/IRS information.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No implementation or storage technology inferred.</data></node><node id="QRY_OFFLINE_CCTL"><data key="node_entity_id">QRY_OFFLINE_CCTL</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Offline SSI Case Control Query</data><data key="node_acronym">OFFLINE CCTL</data><data key="node_domain">Title XVI / Queries</data><data key="node_description">Offline SSI case-control query referenced in current field-office folder-location procedures.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2024-02-06</data><data key="node_confidence">4</data><data key="node_notes">Current POMS reference establishes use, not underlying implementation.</data></node><node id="QRY_OHAQ"><data key="node_entity_id">QRY_OHAQ</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Office of Hearings and Appeals Query</data><data key="node_acronym">OHAQ</data><data key="node_domain">Hearings &amp; Appeals / Queries</data><data key="node_description">Legacy hearing-query tool still referenced in a 2024 field-office medical-folder search procedure.</data><data key="node_observed_status">legacy_query_still_referenced_2024</data><data key="node_observed_as_of">2024-02-06</data><data key="node_confidence">4</data><data key="node_notes">OAO removed OHAQ from a required Appeals Council query list in 2019, but current POMS still references it for folder-location detective work.</data></node><node id="QRY_QRSL"><data key="node_entity_id">QRY_QRSL</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Query Response Selection List</data><data key="node_acronym">QRSL</data><data key="node_domain">Enterprise Queries</data><data key="node_description">Query selection interface used to obtain benefit, payment and related query responses.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current debt and nonreceipt procedures continue to direct QRSL use.</data></node><node id="QRY_SEQY"><data key="node_entity_id">QRY_SEQY</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Summary Earnings Query</data><data key="node_acronym">SEQY</data><data key="node_domain">Earnings / Queries</data><data key="node_description">Immediate online query that displays yearly earnings totals derived from the Master Earnings File.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="QRY_SSID"><data key="node_entity_id">QRY_SSID</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">Supplemental Security Income Display</data><data key="node_acronym">SSID</data><data key="node_domain">Title XVI / Queries</data><data key="node_description">Query display used to review Supplemental Security Record information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSI and hearing procedures continue to require SSID.</data></node><node id="QRY_WMHH"><data key="node_entity_id">QRY_WMHH</data><data key="node_entity_type">query_system</data><data key="node_canonical_name">WMS History Query</data><data key="node_acronym">WMHH</data><data key="node_domain">SSA Internal Operations / Workload Routing</data><data key="node_description">Query used by staff to review recent case movement when routing claims or post-entitlement work.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">4</data><data key="node_notes">POMS names WMHH as WMS History Query but does not expand WMS or publish its hosting/topology.</data></node><node id="QUERY_THIS"><data key="node_entity_id">QUERY_THIS</data><data key="node_entity_type">query_interface</data><data key="node_canonical_name">THIS Query</data><data key="node_acronym">THIS</data><data key="node_domain">Disability / CDR / Query</data><data key="node_description">SSA query checked for an exception when an expected Title II CDR update has not posted and no DIBCESS issue is present.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-08-12</data><data key="node_confidence">4</data><data key="node_notes">POMS names the THIS query but does not expand the acronym or document its backend in the public instruction.</data></node><node id="R106_E001"><data key="node_entity_id">R106_E001</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Non-Claimant Requestor Screen</data><data key="node_acronym">ANCR</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Non-claimant requestor screen used to document a third-party SSI reconsideration request.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational instruction revised 2023-10-05; no physical persistence, DBMS, or transport inferred.</data></node><node id="R106_E002"><data key="node_entity_id">R106_E002</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Appeal Report of Contact Screen</data><data key="node_acronym">RPOC</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Report of Contact appeal screen documenting third-party SSI reconsideration communications.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational instruction revised 2023-10-05; no physical persistence, DBMS, or transport inferred.</data></node><node id="R106_E003"><data key="node_entity_id">R106_E003</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Appeal Disposition Screen</data><data key="node_acronym">ADIS</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Appeal disposition screen used to record SSI reconsideration dismissal or withdrawal.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational instruction revised 2023-10-05; no physical persistence, DBMS, or transport inferred.</data></node><node id="R106_E004"><data key="node_entity_id">R106_E004</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Appeal List or Appeal Status Screen</data><data key="node_acronym">APLS</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Appeal listing/status screen referenced in reconsideration dismissal instructions.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational instruction revised 2023-10-05; no physical persistence, DBMS, or transport inferred.</data></node><node id="R106_E005"><data key="node_entity_id">R106_E005</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Core Appeal Data Screen</data><data key="node_acronym">ACAD</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Core appeal data screen with notice date used to evaluate timeliness and payment-continuation routing.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational instruction revised 2023-10-05; no physical persistence, DBMS, or transport inferred.</data></node><node id="R106_E006"><data key="node_entity_id">R106_E006</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Withdraw Appeal Evaluation Screen</data><data key="node_acronym">AWDE</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Withdrawal evaluation screen used when a claimant withdraws an SSI appeal.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational instruction revised 2023-10-05; no physical persistence, DBMS, or transport inferred.</data></node><node id="R106_E007"><data key="node_entity_id">R106_E007</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Withdraw Appeal Explanation Screen</data><data key="node_acronym">AWDW</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Withdrawal explanation screen used for SSI appeal withdrawals.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational instruction revised 2023-10-05; no physical persistence, DBMS, or transport inferred.</data></node><node id="R106_E008"><data key="node_entity_id">R106_E008</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Non-MSSICS SSI Appeal Disposition Screen</data><data key="node_acronym">UAPD</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Appeal disposition input used in non-MSSICS SSI reconsideration dismissals and withdrawals.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Operational instruction revised 2023-10-05; no physical persistence, DBMS, or transport inferred.</data></node><node id="R106_E009"><data key="node_entity_id">R106_E009</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1696 Claimant Appointment of Representative</data><data key="node_acronym">SSA-1696</data><data key="node_domain">Representation / Appeals</data><data key="node_description">Claimant appointment form used when requesting a representative for SSI appeals; unlike SSA-561-U2, appointment requires a signature.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E010"><data key="node_entity_id">R106_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Third-Party Reconsideration Contact Development</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Field office develops third-party requests; uses ANCR/RPOC; seeks timely written claimant confirmation without recognizing mere telephone inquiry as an appeal.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E011"><data key="node_entity_id">R106_E011</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Reconsideration Claimant Confirmation Follow-Up</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">In specified third-party calls, follow up with claimant or recipient after 15 working days and close if response not received under POMS instructions.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E012"><data key="node_entity_id">R106_E012</data><data key="node_entity_type">notice</data><data key="node_canonical_name">SSA-L8165-U2 Important Information Dismissal Notice</data><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Dismissal notice to SSI reconsideration requestor, without an appeal paragraph, under current policy.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E013"><data key="node_entity_id">R106_E013</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Missouri Bureau of Vital Records</data><data key="node_domain">State Vital Records / Identity</data><data key="node_description">State bureau to which SSA sends manual birth-record verification requests when EVVE verification is unsuccessful in Missouri.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E014"><data key="node_entity_id">R106_E014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Missouri EVVE Failed Birth Verification Follow-Up</data><data key="node_domain">Identity / Vital Records</data><data key="node_description">When EVVE birth verification is unsuccessful, SSA prepares a DPS letter with the result printout, birth certificate copy, and SSA-562-U3 for the Missouri vital-records bureau.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E015"><data key="node_entity_id">R106_E015</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L706 Letter to Custodian of Birth Records</data><data key="node_domain">Identity / Vital Records</data><data key="node_description">Release/request letter for obtaining or verifying birth records; Missouri requires notarization in specified cases.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E016"><data key="node_entity_id">R106_E016</data><data key="node_entity_type">form</data><data key="node_canonical_name">Missouri VS-151 Application for Birth or Death Certification</data><data key="node_domain">Identity / Vital Records</data><data key="node_description">Missouri state certification request form offered as an alternative for certain state vital-record requests; state-specific, not an SSA standard form.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E017"><data key="node_entity_id">R106_E017</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Missouri Failed EVVE Birth Verification Request Packet</data><data key="node_domain">Identity / Evidence</data><data key="node_description">Manual follow-up bundle includes unsuccessful EVVE result, copy of birth certificate, and SSA-562-U3 accompanying DPS correspondence.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E018"><data key="node_entity_id">R106_E018</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Section 1634 SSI Medicaid Third-Party Liability Development</data><data key="node_domain">Title XVI / State Medicaid Exchange</data><data key="node_description">Collects third-party health-insurance liability information for applicable 1634 States and supplies resulting details to state Medicaid agencies after allowed claims or qualifying posteligibility changes.</data><data key="node_observed_status">documented_in_2016_poms_2025_regional_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">National instruction revised 2016-07-27 lies ~3 months outside strict rolling period; 2025 regional batch corroborates CCE workflow. Current statewide implementation and transmission mechanism unconfirmed.</data></node><node id="R106_E019"><data key="node_entity_id">R106_E019</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS BMEN Health Expenses Question</data><data key="node_acronym">BMEN</data><data key="node_domain">Title XVI / Medicaid</data><data key="node_description">MSSICS BMEN health-expenses question gates TPL data development in applicable SSI pathways per historical national guidance.</data><data key="node_observed_status">documented_2016_historical</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R106_E020"><data key="node_entity_id">R106_E020</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS BHLT Third-Party Insurance Question</data><data key="node_acronym">BHLT</data><data key="node_domain">Title XVI / Medicaid</data><data key="node_description">MSSICS BHLT holds yes/no/uncertain allegation of health insurance other than Medicare or Medicaid, with adjudication follow-up for uncertain reports.</data><data key="node_observed_status">documented_2016_historical</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R106_E021"><data key="node_entity_id">R106_E021</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS BTPL Third-Party Liability Screens</data><data key="node_acronym">BTPL</data><data key="node_domain">Title XVI / Medicaid</data><data key="node_description">Electronic SSA-8019-U2 equivalent for non-Medicare/Medicaid third-party liability; historical source says free-format insurer/attorney names and addresses.</data><data key="node_observed_status">documented_2016_historical</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R106_E022"><data key="node_entity_id">R106_E022</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-8019-U2 Third-Party Liability Information</data><data key="node_acronym">SSA-8019-U2</data><data key="node_domain">Title XVI / Medicaid</data><data key="node_description">Paper form for claimant, policy-holder, insurer and potential liable party details forwarded to state Medicaid agency where policy requires.</data><data key="node_observed_status">documented_2016_historical</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R106_E023"><data key="node_entity_id">R106_E023</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">BTPL Insurance-Company and Liability-Party Addresses</data><data key="node_domain">Address Provenance / Title XVI / Medicaid</data><data key="node_description">Historical BTPL address input for insurer, attorney and third parties. POMS describes these as free-format in 2016; neither a current residence address nor a proven program-master address write.</data><data key="node_observed_status">historical_2016_data_shape_not_confirmed_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R106_E024"><data key="node_entity_id">R106_E024</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSA-8019-U2 Claimant Contact Address</data><data key="node_domain">Address Provenance / Title XVI / Medicaid</data><data key="node_description">Claimant address field on a paper SSI Medicaid third-party liability form; transaction-specific copy for state development.</data><data key="node_observed_status">documented_2016_historical</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R106_E025"><data key="node_entity_id">R106_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA-to-State Medicaid Third-Party Liability Referral</data><data key="node_domain">External Exchanges / State Medicaid</data><data key="node_description">Allowed SSI cases and qualifying posteligibility changes transmit or route insurer/third-party information to Medicaid agencies in applicable 1634 States; channel not generally identified.</data><data key="node_observed_status">documented_regional_2025_batch</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">2025 regional batch corroborates CCE electronic submission and paper fallback; not necessarily current all-state transport.</data></node><node id="R106_E026"><data key="node_entity_id">R106_E026</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">CCE Health Expenses and Third-Party Liability Page</data><data key="node_domain">Title XVI / State Medicaid</data><data key="node_description">CCE initial and redetermination page for collecting insurance third-party liability information in specified Dallas region POMS instructions.</data><data key="node_observed_status">documented_regional_poms_2025_batch</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">POMS underlying revision 2008 with 2025 batch; regional rather than universal implementation.</data></node><node id="R106_E027"><data key="node_entity_id">R106_E027</data><data key="node_entity_type">form</data><data key="node_canonical_name">SF-1449 Solicitation Contract Order for Commercial Products and Services</data><data key="node_acronym">SF-1449</data><data key="node_domain">Procurement / Acquisition</data><data key="node_description">OAG cites SF-1449 as a funding contract instrument used to inspect funded-through date in the published 2025 lapse-of-funding guidance.</data><data key="node_observed_status">documented_oag_instruction_2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Published OAG shutdown guidance references FY2025 funding; not proof a shutdown is occurring in Oct 2026.</data></node><node id="R106_E028"><data key="node_entity_id">R106_E028</data><data key="node_entity_type">form</data><data key="node_canonical_name">SF-30 Amendment of Solicitation or Modification of Contract</data><data key="node_acronym">SF-30</data><data key="node_domain">Procurement / Acquisition</data><data key="node_description">OAG cites SF-30 as a funding-modification document to inspect funded-through date in its published guidance.</data><data key="node_observed_status">documented_oag_instruction_2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Published OAG shutdown guidance references FY2025 funding; not proof a shutdown is occurring in Oct 2026.</data></node><node id="R106_E029"><data key="node_entity_id">R106_E029</data><data key="node_entity_type">form</data><data key="node_canonical_name">OF-347 Order for Supplies or Services</data><data key="node_acronym">OF-347</data><data key="node_domain">Procurement / Acquisition</data><data key="node_description">OAG cites OF-347 as an order form capable of defining funding coverage for a contract in published lapse guidance.</data><data key="node_observed_status">documented_oag_instruction_2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Published OAG shutdown guidance references FY2025 funding; not proof a shutdown is occurring in Oct 2026.</data></node><node id="R106_E030"><data key="node_entity_id">R106_E030</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Contracting Officer Shutdown Performance Direction</data><data key="node_domain">Procurement / Acquisition</data><data key="node_description">OAG website says only SSA contracting officers can direct contractors whether performance continues during a funding lapse; COR staff may issue technical guidance but not continuation authorization.</data><data key="node_observed_status">published_contingency_guidance</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R106_E031"><data key="node_entity_id">R106_E031</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Revolutionary FAR Overhaul Guidance Publication</data><data key="node_domain">Procurement / Acquisition</data><data key="node_description">OAG publishes OFPP RFO FAQs regarding federal FAR overhaul under Executive Order 14275 and OMB memorandum M-25-26; SSA-specific internal adoption effects not established.</data><data key="node_observed_status">published_current_oag_guidance</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R106_E032"><data key="node_entity_id">R106_E032</data><data key="node_entity_type">service_capability</data><data key="node_canonical_name">SSA eSignature Electronic Forms Submission Option (2024)</data><data key="node_domain">Digital Services / Evidence Intake</data><data key="node_description">September 2024 SSA release says representatives can request electronic signature and customers submit selected signed forms and evidence through online eSignature/Upload Documents option.</data><data key="node_observed_status">announced_operational_2024</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E033"><data key="node_entity_id">R106_E033</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Technician-Sent eSignature Document Request Link</data><data key="node_domain">Digital Services / Evidence Intake</data><data key="node_description">SSA representative sends a link to customer requesting selected forms or evidence using announced 2024 eSignature/upload flow.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R106_E034"><data key="node_entity_id">R106_E034</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">2024 Electronic Document Request Link</data><data key="node_domain">Digital Services / Evidence Intake</data><data key="node_description">Customer-facing link initiated by SSA staff for specified form or evidence submission in eSignature/Upload Documents.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">URL token format, expiry, transmission mechanism and hosting not described.</data></node><node id="R106_E035"><data key="node_entity_id">R106_E035</data><data key="node_entity_type">service_capability</data><data key="node_canonical_name">SSA Forms Catalog High-Assurance Upload Step-Up Cohort</data><data key="node_domain">Digital Services / Identity Verification</data><data key="node_description">Current public Forms catalog lists five forms requiring additional identity verification for electronic submission: SSA-454-BK, SSA-827, SSA-2574, SSA-2935, and SSA-8510.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R107_E001"><data key="node_entity_id">R107_E001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI All-Allowance AFI Account Verification Requirement</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">Since 2026-05-04, all SSI initial claim allowances, applicable reopenings, and reversals establishing initial eligibility require AFI verification regardless of alleged resources.</data><data key="node_observed_status">effective_since_2026-05-04</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E002"><data key="node_entity_id">R107_E002</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">AFI Geographic Search Response</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">AFI geographic search response used to develop previously undisclosed financial accounts; a negative search is not a master-address update.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E003"><data key="node_entity_id">R107_E003</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">AFI Relationship-Related Financial Search</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">AFI request search involving applicable claimant relationships; documented as an input requirement for initial SSI allowances.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E004"><data key="node_entity_id">R107_E004</data><data key="node_entity_type">exchange_artifact</data><data key="node_canonical_name">AFI Financial Institution Sub-Request Response</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">Responses for AFI sub-requests may remain outstanding under policy when initial award is adjudicated, subject to processing rules.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E005"><data key="node_entity_id">R107_E005</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Unidentified AFI Financial Institution Liaison Vendor</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">SSA operational policy instructs an AFI vendor to liaise with participating financial institutions when electronic responses need follow-up; product and vendor identity not established.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">External vendor function, identity, contract, transport, DBMS and retention unspecified. Do not merge with licensed USPS NCOA vendor.</data></node><node id="R107_E006"><data key="node_entity_id">R107_E006</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4641 Financial Institution Records Authorization and Request (Paper)</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">Paper SSA-4641 used to request financial records from financial institutions that are not participating in AFI electronic verification.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E007"><data key="node_entity_id">R107_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">AFI Nonparticipating Financial Institution Verification Fallback</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">For nonparticipating financial institutions SSA sends paper SSA-4641 through mail or fax to seek records.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E008"><data key="node_entity_id">R107_E008</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">AFI Alternative Financial Evidence Adjudication and Later Response Reconciliation</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">Technicians may use complete bank statements, other FI records, or last-resort signed statement when AFI requests are pending and later handle AFI results as a separate posteligibility event.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E009"><data key="node_entity_id">R107_E009</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">AFI Historical Account Balance Verification Window</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">SSA instructs verification of financial balances for up to 25 prior months in applicable scenarios; this is a request/development window, not evidence of backend retention.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Up-to-25-month verification lookback; no inference of repository retention duration.</data></node><node id="R107_E010"><data key="node_entity_id">R107_E010</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Financial Institution First-of-Month Resource Value</data><data key="node_domain">Title XVI / Resource Computation</data><data key="node_description">SSI FI account resources use opening balance on first day of month or closing balance on last day of preceding month, subject to applicable exclusions.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E011"><data key="node_entity_id">R107_E011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">AFI Waiver Financial-Evidence Reuse for SSI Eligibility</data><data key="node_domain">Title XVI / Overpayment Waiver</data><data key="node_description">Where required permission exists, FI verification obtained for Title II or XVI defeat-the-purpose waiver assessment may be reused to verify SSI resource months.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E012"><data key="node_entity_id">R107_E012</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Financial Institution Verification Permission Status</data><data key="node_domain">Title XVI / Consent &amp; Legal Use</data><data key="node_description">Claimant, recipient, and deemor financial-information consent status and collection dates recorded in SSI Claims Financial Institutions Permission page; duration valid until a terminating event.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E013"><data key="node_entity_id">R107_E013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Financial Permission Grant, Revocation, and Termination Process</data><data key="node_domain">Title XVI / Consent &amp; Legal Use</data><data key="node_description">Permission is prospectively terminated upon written cancellation, deeming end, final nonappealable claim denial, or benefits eligibility termination; prior legally obtained period remains valid.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E014"><data key="node_entity_id">R107_E014</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Deemor Financial Permission Good-Cause Exemption</data><data key="node_domain">Title XVI / Consent &amp; Legal Use</data><data key="node_description">Good cause for missing deemor consent, documented on FI permission page and Report of Contact or EVID; based on abuse/harassment or deemor noncooperation subject to limits.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E015"><data key="node_entity_id">R107_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Financial Permission Harassment or Abuse Good-Cause Development</data><data key="node_domain">Title XVI / Consent &amp; Legal Use</data><data key="node_description">Corroborating police, court, health or qualifying first-hand statements may support a good-cause exception from deemor consent; redevelop if circumstances change.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E016"><data key="node_entity_id">R107_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Financial Permission Deemor Failure-to-Cooperate Good-Cause Development</data><data key="node_domain">Title XVI / Consent &amp; Legal Use</data><data key="node_description">Good-faith claimant effort and SSA assistance may support good cause where a deemor refuses permission, excluding specified guardian, payee and sponsor circumstances.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E017"><data key="node_entity_id">R107_E017</data><data key="node_entity_type">notice</data><data key="node_canonical_name">DPS Financial Permission Request – Claimant (T16) Notice</data><data key="node_domain">Title XVI / Notice &amp; Work Control</data><data key="node_description">Claimant/recipient-specific DPS financial permission request letter used when permission cannot be obtained in person or by telephone.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E018"><data key="node_entity_id">R107_E018</data><data key="node_entity_type">notice</data><data key="node_canonical_name">DPS Financial Permission Request – Deemor (T16) Notice</data><data key="node_domain">Title XVI / Notice &amp; Work Control</data><data key="node_description">Deemor-specific DPS financial permission request letter with language separate from claimant request.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E019"><data key="node_entity_id">R107_E019</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Financial Permission Request 15-Day Development Follow-Up</data><data key="node_domain">Title XVI / Notice &amp; Work Control</data><data key="node_description">SSI permission request controlled for 15-day follow-up via worksheet or MDW tickle when response is pending.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E020"><data key="node_entity_id">R107_E020</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Payment Status Code N18 – Financial Permission Refusal</data><data key="node_domain">Title XVI / Eligibility Control</data><data key="node_description">SSI initial-claim denial code N18 when claimant or deemor fails to provide needed financial permission and no relevant good cause applies; N18 also has other refusal uses.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E021"><data key="node_entity_id">R107_E021</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Payment Status Code N05 – Financial Permission Suspension</data><data key="node_domain">Title XVI / Eligibility Control</data><data key="node_description">SSI posteligibility payment status N05 applied when financial permission is refused or canceled without applicable good cause after notice; N05 also has other uses.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E022"><data key="node_entity_id">R107_E022</data><data key="node_entity_type">notice</data><data key="node_canonical_name">DPS Refused Financial Permission – Disapproved Claim (T16) Notice</data><data key="node_domain">Title XVI / Notice &amp; Work Control</data><data key="node_description">Manual refusal/financial permission denial notice sourced through DPS with an ORS copy under policy.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E023"><data key="node_entity_id">R107_E023</data><data key="node_entity_type">notice</data><data key="node_canonical_name">DPS Refused Financial Permission – Suspension (T16) Notice</data><data key="node_domain">Title XVI / Notice &amp; Work Control</data><data key="node_description">Manual financial permission suspension notice sourced from DPS and sent to ORS with policy-prescribed effective date.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E024"><data key="node_entity_id">R107_E024</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Financial Permission Denial or Suspension Remarks</data><data key="node_domain">Title XVI / Eligibility Control</data><data key="node_description">Financial permission refusal/deemor good-cause exception reason recorded in SSI record remarks when N18 denial or N05 suspension used.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E025"><data key="node_entity_id">R107_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Claims Financial Permission Status-Change Recording</data><data key="node_domain">Title XVI / Consent &amp; Legal Use</data><data key="node_description">After a final permission status, subsequent change uses new Financial Institutions Permission page iteration; policy describes manual clearance/reseed when iteration limitations occur.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E026"><data key="node_entity_id">R107_E026</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">POS PEWE Earnings Report Input Screen</data><data key="node_acronym">PEWE</data><data key="node_domain">Title II / Earnings &amp; Work</data><data key="node_description">PEWE screen used by FO, PSC, or TSC to input reported annual earnings, nonservice months, and special wage payments through Title II Post-Entitlement System.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E027"><data key="node_entity_id">R107_E027</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Closed-Year Annual Work Report Processing</data><data key="node_domain">Title II / Earnings &amp; Work</data><data key="node_description">Beneficiaries or authorized representatives may report closed-year earnings via phone, visit or mail; SSA employees input annual reports through PEWE as needed.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E028"><data key="node_entity_id">R107_E028</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EEO Employer Identification Number Matching Gate</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">EEO compares current and prior-year MEF employer EIN detail before automated work-earnings enforcement selection to allow late postings.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E029"><data key="node_entity_id">R107_E029</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">EEO RSI Finder File for Deferred EIN-Match Cases</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">Cases failing EIN match during first two enforcement passes are sent to the RSI finder file for subsequent selection; physical format and persistence are undocumented.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Authoritative policy calls it an RSI finder file. Do not infer DBMS, cloud storage, batch mechanism or retention.</data></node><node id="R107_E030"><data key="node_entity_id">R107_E030</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EEO Total Reported Earnings for Deduction Purposes</data><data key="node_acronym">TRE</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">EEO calculates Total Reported Earnings (TRE) using covered and noncovered earnings in MEF for earnings test deduction decisions.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E031"><data key="node_entity_id">R107_E031</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Title II Current-Year Earnings Estimate for Work Enforcement</data><data key="node_acronym">CYE</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">Current-year estimate used in earnings test handling; field offices seek a current estimate during beneficiary contacts when not already shown.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E032"><data key="node_entity_id">R107_E032</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EEO Three-Pass Annual Enforcement Selection</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">EEO runs in June, September and February following the close of year, considering current enforcement year and three prior years, with policy-described EIN matching differences.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E033"><data key="node_entity_id">R107_E033</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EEO Potential Underpayment Enforcement Category</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">Earnings test category where MEF-derived TRE suggests additional benefits after withheld payments, subject to stated exception criteria.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E034"><data key="node_entity_id">R107_E034</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EEO TE No. 777 Enforcement Category</data><data key="node_acronym">TE 777</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">Category when annual report missing and enforceable earnings above threshold but case is neither underpayment nor manual-contact category.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E035"><data key="node_entity_id">R107_E035</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EEO Earnings-Test Overpayment Discrepancy Category</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">EEO category where MEF earnings exceed reported or estimated amounts under specified policy thresholds.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E036"><data key="node_entity_id">R107_E036</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EEO TE DIRCON Manual-Review Enforcement Category</data><data key="node_acronym">TE DIRCON</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">EEO directs analyst review before payment when zero/negative TRE, significant discrepancy or FRA nonservice-month issues require judgment; not every case requires direct contact.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E037"><data key="node_entity_id">R107_E037</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Non-Service Month Earnings-Test Attribute</data><data key="node_acronym">NSM</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">MBR nonservice-month data consulted for monthly earnings test grace-year work-deduction computation.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E038"><data key="node_entity_id">R107_E038</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MBR Beneficiary Own Account Number Correction During EEO</data><data key="node_domain">Title II / Identity &amp; Earnings</data><data key="node_description">Policy directs field office to correct the BOAN in MBR when earnings enforcement development establishes an incorrect account number.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Explicit staff-controlled MBR update from identity/earnings development; no automatic Numident change inferred.</data></node><node id="R107_E039"><data key="node_entity_id">R107_E039</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EEO MBR Surname Conflict Resolution Against MEF</data><data key="node_domain">Title II / Identity &amp; Earnings</data><data key="node_description">When EEO reveals surname mismatch, verify with beneficiary; correct MBR if MEF name is right, otherwise leave MBR unchanged.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Conditional personnel action documented; not a general MEF-to-MBR synchronization.</data></node><node id="R107_E040"><data key="node_entity_id">R107_E040</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Earnings Enforcement Precedence Over Benefit Recomputation</data><data key="node_domain">Title II / Earnings &amp; Work</data><data key="node_description">If AERO or requested recomputation and earnings enforcement may create an overpayment, resolve enforcement before recomputation.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E041"><data key="node_entity_id">R107_E041</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EEO Automated Earnings Enforcement Beneficiary Protest Review</data><data key="node_domain">Title II / Debt &amp; Earnings</data><data key="node_description">Beneficiary protest of automated earnings processing may require stopping recovery using DMS DRPR, resolving MEF discrepancy and contacting employer as needed.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E042"><data key="node_entity_id">R107_E042</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Amended Annual Work Report TOER-M Indicator</data><data key="node_domain">Title II / Earnings Enforcement</data><data key="node_description">POMS identifies TOER-M in MBR as a marker for amended annual report relevant to enforcement case selection.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E043"><data key="node_entity_id">R107_E043</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">POS Change-in-PIA Recomputation Input</data><data key="node_acronym">CIP</data><data key="node_domain">Title II / Earnings &amp; Benefit Computation</data><data key="node_description">POS Change in PIA (CIP) action used for a requested recomputation when related annual earnings report is entered through PEWE.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a POS processing input; not proof of separate application or database.</data></node><node id="R107_E044"><data key="node_entity_id">R107_E044</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">eRPS Prior Poor-Performance Payee Selection Approval Process</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">Selection of a payee applicant with poor performance requires documented manager approval in eRPS, followed by performance diary when selected.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E045"><data key="node_entity_id">R107_E045</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Manager Approve Selection Screen</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">Manager action to approve selection of a prior poor-performance payee applicant following case-specific documentation.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E046"><data key="node_entity_id">R107_E046</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Selection-Required Notes Screen</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">eRPS screen for manager approval notes when poor-performance applicant is selected.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E047"><data key="node_entity_id">R107_E047</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Representative Payee Poor Performance Three-Month Follow-Up Diary</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">Three-month diary established on eRPS Add New Issue screen or comparable diary control for SSA-624-F5 performance assessment.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E048"><data key="node_entity_id">R107_E048</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-624-F5 Representative Payee Evaluation</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">Payee evaluation associated with follow-up of selected representative payees with a history of poor performance.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E049"><data key="node_entity_id">R107_E049</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSR UA Representative Payee Performance Diary</data><data key="node_acronym">UA</data><data key="node_domain">Title XVI / Representative Payee</data><data key="node_description">Title XVI SSR diary in DA field used for follow-up of payee with poor past performance.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E050"><data key="node_entity_id">R107_E050</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Savings Bond Future Resource Value Follow-Up</data><data key="node_domain">Title XVI / Resources</data><data key="node_description">SSA schedules RT diary before a savings bond may become countable or redeemable to recontact the claimant for verification.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E051"><data key="node_entity_id">R107_E051</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT 2026 Retirement and Survivor Family Maximum Bend-Point Formula</data><data key="node_domain">Actuarial / Benefit Formula Publication</data><data key="node_description">Published 2026 retirement/survivor family-maximum calculation with PIA segments and bend points 1643, 2371 and 3093; public calculation presentation only.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E052"><data key="node_entity_id">R107_E052</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Maximum-Taxable-Earnings Worker Benefit Examples through 2026</data><data key="node_domain">Actuarial / Benefit Formula Publication</data><data key="node_description">Public OACT historical cohort table showing AIME and monthly benefit examples by retirement age for workers with maximum-taxable earnings; no public ETL architecture provided.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical/operational object only. No unsupported hosting, table, interface transport, DBMS, or automatic master-record write inferred.</data></node><node id="R107_E053"><data key="node_entity_id">R107_E053</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Estimated Average Social Security Benefit Before and After 2026 COLA</data><data key="node_domain">Actuarial / Public Statistics</data><data key="node_description">OACT estimates average benefit changes for categories and families under 2.8-percent 2026 COLA, using actual benefit data through August 2025.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Estimates based on data available through 2025-08; source system/pipeline and scheduler not disclosed.</data></node><node id="R108_E001"><data key="node_entity_id">R108_E001</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">myCOA My Profile Contact Link Input Screen</data><data key="node_acronym">myCOA Contact Link</data><data key="node_domain">person/address</data><data key="node_description">Online input within my Social Security My Profile displays record addresses and permits eligible self-reported address and telephone changes.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E002"><data key="node_entity_id">R108_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">myCOA Self-Service Address Change Eligibility Exclusions</data><data key="node_domain">person/address</data><data key="node_description">Excludes SSI/concurrent address updates, representative-payee cases, prisoners, pending initial claims or appeals, and changes for another individual.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E003"><data key="node_entity_id">R108_E003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">myCOA Title XVI and Concurrent Telephone-Only Update Path</data><data key="node_domain">person/address</data><data key="node_description">Qualifying SSI statuses and concurrent users can change telephone number but cannot update SSI mailing address through myCOA.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E004"><data key="node_entity_id">R108_E004</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">myCOA Change Confirmation Email Mail and Message Center Delivery</data><data key="node_domain">digital_service</data><data key="node_description">After eligible changes myCOA initiates notice by email/mail and a receipt in my Social Security Message Center.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E005"><data key="node_entity_id">R108_E005</data><data key="node_entity_type">logical_data_element</data><data key="node_canonical_name">T2R COA Pre-Change MBR Mailing Address Reference</data><data key="node_acronym">Pre-MBR mailing address</data><data key="node_domain">person/address</data><data key="node_description">Old MBR mailing address is used for a separate fraud-alert notice, even if it belongs to payee rather than beneficiary; not an independent residential-address authority.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E006"><data key="node_entity_id">R108_E006</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">T2R Change-of-Address Fraud Warning Notice Snippet Set</data><data key="node_acronym">COA014/COA015/COA016</data><data key="node_domain">correspondence</data><data key="node_description">Mandatory COA014, COA015, and COA016 text components document MBR change, unauthorized-change follow-up and my Social Security access.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E007"><data key="node_entity_id">R108_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Telephone IVR-Reported Title II Change of Address</data><data key="node_acronym">IVR COA</data><data key="node_domain">person/address</data><data key="node_description">SSA introduced self-service telephone IVR change-of-address path in August 2020; confirmation notice is produced for this route.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E008"><data key="node_entity_id">R108_E008</data><data key="node_entity_type">platform</data><data key="node_canonical_name">Legacy TNA SKELCOMP Notice Composition Architecture</data><data key="node_acronym">TNA</data><data key="node_domain">correspondence</data><data key="node_description">Former notice formatting architecture consumed T2R COA SKELCOMP; superseded by XML/CCM in October 2022.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Historical implementation as documented; no claim of continuing deployment.</data></node><node id="R108_E009"><data key="node_entity_id">R108_E009</data><data key="node_entity_type">process</data><data key="node_canonical_name">T2R Complete-Notice and Error-Log Disposition Control</data><data key="node_domain">correspondence</data><data key="node_description">T2R generates complete standalone COA notices, excludes manual AURORA completion, and routes incomplete notice entries to an error log for staff investigation.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E010"><data key="node_entity_id">R108_E010</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS AD Third-Party Death Verification Alert</data><data key="node_acronym">AD</data><data key="node_domain">identity/death</data><data key="node_description">Third-party report for beneficiary requires verification</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E011"><data key="node_entity_id">R108_E011</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS BX State-Agency Death Report Alert</data><data key="node_acronym">BX</data><data key="node_domain">identity/death</data><data key="node_description">Death information from non-vital-record state agency requires third-party verification</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E012"><data key="node_entity_id">R108_E012</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS CM CMS Death Report Alert</data><data key="node_acronym">CM</data><data key="node_domain">identity/death</data><data key="node_description">CMS-origin death report requires third-party verification</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E013"><data key="node_entity_id">R108_E013</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS VA Veterans Affairs Death Report Alert</data><data key="node_acronym">VA</data><data key="node_domain">identity/death</data><data key="node_description">VA-origin death report requires third-party verification</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E014"><data key="node_entity_id">R108_E014</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS OP OPM Death Report Alert</data><data key="node_acronym">OP</data><data key="node_domain">identity/death</data><data key="node_description">OPM-origin death report requires third-party verification</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E015"><data key="node_entity_id">R108_E015</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS DN Death Name Mismatch Alert</data><data key="node_acronym">DN</data><data key="node_domain">identity/death</data><data key="node_description">DIPS report name mismatch requires development</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E016"><data key="node_entity_id">R108_E016</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS DX Death Report Not Entered Via DIPS Alert</data><data key="node_acronym">DX</data><data key="node_domain">identity/death</data><data key="node_description">Reported death requires a DIPS transaction if not already entered</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E017"><data key="node_entity_id">R108_E017</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS Numident-to-Payment Death Inconsistency Alert</data><data key="node_acronym">NUMI alert</data><data key="node_domain">identity/death</data><data key="node_description">Monthly Numident alert identifies death recorded on Numident but absent on payment record(s) and requires review of which record is correct.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E018"><data key="node_entity_id">R108_E018</data><data key="node_entity_type">process</data><data key="node_canonical_name">DATS Daily DIPS Death Alert Refresh</data><data key="node_domain">identity/death</data><data key="node_description">DIPS alert listing is refreshed daily, unlike Numident discrepancy listing.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E019"><data key="node_entity_id">R108_E019</data><data key="node_entity_type">process</data><data key="node_canonical_name">DATS Monthly Numident Death Reconciliation</data><data key="node_domain">identity/death</data><data key="node_description">Numident/payout discrepancy alert updates on last weekend of month and may persist until next month after correction.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E020"><data key="node_entity_id">R108_E020</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DATS Non-Responder Alleged Death DIPS Processing</data><data key="node_domain">identity/death</data><data key="node_description">Following SSA-2708 and 45-day nonresponse, staff can process alleged death in DIPS under the specifically documented non-responder category.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E021"><data key="node_entity_id">R108_E021</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DATS Verified-Alive Erroneous Death Clearance</data><data key="node_domain">identity/death</data><data key="node_description">Staff verify individual is alive, enter DATS remarks, and clear erroneous death report alert instead of marking deceased.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E022"><data key="node_entity_id">R108_E022</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">DIPS EDR Death-Change Same-Day Second-PIN Clearance</data><data key="node_acronym">EDR change 2-PIN</data><data key="node_domain">identity/death</data><data key="node_description">Changes to Numident deaths sourced from EDR need management second-PIN approval on same day or the transaction must be resubmitted.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E023"><data key="node_entity_id">R108_E023</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">DIPS EDR Death-Delete Same-Day Second-PIN Clearance</data><data key="node_acronym">EDR delete 2-PIN</data><data key="node_domain">identity/death</data><data key="node_description">EDR death-deletion requires management second-PIN approval same day, otherwise DIPS transaction must be reentered.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E024"><data key="node_entity_id">R108_E024</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DIPS Title XVI Death-Removal Manual Correction Following Delete</data><data key="node_domain">identity/death</data><data key="node_description">DIPS Delete removes Numident and Title II death but does not automatically remove Title XVI date of death; technician performs separate SSI corrective action.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E025"><data key="node_entity_id">R108_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DIPS Missing-SSN Death Report Exception and BOAN Development</data><data key="node_acronym">No SSN / BOAN</data><data key="node_domain">identity/death</data><data key="node_description">DIPS requires SSN; technicians must correct Title II BOAN or establish Numident before submitting death except permitted non-BOAN cases.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E026"><data key="node_entity_id">R108_E026</data><data key="node_entity_type">process</data><data key="node_canonical_name">DIPS Overnight Death Transaction Processing</data><data key="node_domain">identity/death</data><data key="node_description">DIPS add/change/delete actions process overnight and staff must verify conditional cross-record posting.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E027"><data key="node_entity_id">R108_E027</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">SSA-721 Disposal After Numident Death Update</data><data key="node_domain">identity/death</data><data key="node_description">After Numident is updated, agency destroys received funeral director SSA-721 (preserving claim-specific input coding where needed).</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E028"><data key="node_entity_id">R108_E028</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA-721 Funeral-Report Survivor Outreach Trigger</data><data key="node_domain">person/address</data><data key="node_description">Surviving spouse/child name and address on SSA-721 may trigger DPS Survivor Letter, but does not automatically change deceased or survivor master addresses.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E029"><data key="node_entity_id">R108_E029</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSA-721 Evidence Screen Code 721</data><data key="node_acronym">EVID 721</data><data key="node_domain">identity/death</data><data key="node_description">When deceased beneficiary has claim, EVID is annotated with 721; received paper SSA-721 destroyed after SSA record updates.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E030"><data key="node_entity_id">R108_E030</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Northern Mariana Islands Social Security System Beneficiary Exception Process</data><data key="node_acronym">NMISSS</data><data key="node_domain">Title II</data><data key="node_description">SSA documents T2R inability to automate certain NMISSS post-entitlement actions, requiring manual PC processing.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E031"><data key="node_entity_id">R108_E031</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Northern Marianas Social Security Beneficiary Special Message</data><data key="node_domain">Title II</data><data key="node_description">MBR Special Message text flags Northern Marianas Islands SS beneficiaries for exceptional processing.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E032"><data key="node_entity_id">R108_E032</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Northern Mariana Island Account Data Indicator</data><data key="node_domain">Title II</data><data key="node_description">Account data may display N Mariana Island, another indicator of NMISSS beneficiary status.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E033"><data key="node_entity_id">R108_E033</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Western Program Service Center Operations Analysis Section</data><data key="node_acronym">WNPSC OAS</data><data key="node_domain">Title II</data><data key="node_description">WNPSC Operations Analysis Section carries manual MACADE processing for NMISSS exceptions, regardless of usual PCOC.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E034"><data key="node_entity_id">R108_E034</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">NMISSS Post-Entitlement POS Exception and Manual MACADE Adjustment</data><data key="node_domain">Title II</data><data key="node_description">POS changes for NMISSS (address, direct deposit, death, work) cause T2R exception and must be sent to WNPSC OAS for manual MACADE action.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E035"><data key="node_entity_id">R108_E035</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MINE or MINE-Equivalent CDR Field Office Screen-Out</data><data key="node_acronym">MINE CDR screen-out</data><data key="node_domain">disability</data><data key="node_description">FO reviews comparison-point determination, medical diary and screening criteria and can refer directly to DDS without a full SSA-454 interview.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E036"><data key="node_entity_id">R108_E036</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Electronic MINE CDR Referral Message</data><data key="node_domain">disability</data><data key="node_description">FO places electronic message MINE or MINE-equivalent CDR on qualifying electronic case before routing to DDS.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E037"><data key="node_entity_id">R108_E037</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Paper MINE CDR Route Slip Annotation</data><data key="node_domain">disability</data><data key="node_description">For paper folder, FO marks route slip when forwarding qualifying MINE referral to DDS.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E038"><data key="node_entity_id">R108_E038</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS MINE-Equivalent Screen-Out Return for Full CDR Interview</data><data key="node_domain">disability</data><data key="node_description">DDS can reject FO MINE characterization and return case for ordinary SSA-454 interview and full medical development.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E039"><data key="node_entity_id">R108_E039</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MINE CDR Comparison Point Decision Medical Evidence Review</data><data key="node_acronym">CPD review</data><data key="node_domain">disability</data><data key="node_description">Prior comparison-point decision and supporting medical evidence must be examined to qualify for MINE treatment.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E040"><data key="node_entity_id">R108_E040</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DCPS Medical Evidence Nonrequest Rationale Case Note</data><data key="node_acronym">DCPS Case Note</data><data key="node_domain">disability/evidence</data><data key="node_description">When DDS does not request records from an identified medical source, name and reason must appear in DCPS Case Note or case-development record.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E041"><data key="node_entity_id">R108_E041</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Traditional Graphical Medical Test Evidence Retrieval</data><data key="node_domain">disability/evidence</data><data key="node_description">DDS requests visual-field tracings, audiograms, PFT graphs, abnormal cardiac stress tests or other graphics through traditional source channels when HIT standard document lacks them.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E042"><data key="node_entity_id">R108_E042</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Post-DDS Decision Field Office Medical Evidence Receipt Review</data><data key="node_domain">disability/evidence</data><data key="node_description">FO triages evidence arriving after DDS determination; paper-folder duplicates retained and marked, electronic-folder follow established CEF procedures.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E043"><data key="node_entity_id">R108_E043</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSA-827 eAuthorization Attestation Input Screen</data><data key="node_acronym">SSA-827 eAuthorization</data><data key="node_domain">disability/evidence</data><data key="node_description">EDCS/eView attestation screen records signer decision and employee witness; accepted submission populates electronic SSA-827.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E044"><data key="node_entity_id">R108_E044</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Electronically Signed SSA-827 Signer and Witness Fields</data><data key="node_domain">disability/evidence</data><data key="node_description">SSA electronically populates signer name/date/identity and attesting employee identity/contact data onto rendered SSA-827.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E045"><data key="node_entity_id">R108_E045</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA-827 Attestation Automatic Electronic Folder Filing</data><data key="node_domain">disability/evidence</data><data key="node_description">Accepted attested SSA-827 is added automatically to electronic folder without scanning or faxing form back.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E046"><data key="node_entity_id">R108_E046</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA-827 i3368/i3441 Internet Click-and-Sign Consent Route</data><data key="node_domain">disability/evidence</data><data key="node_description">Eligible adult signing via Internet i3368 or i3441 records intent by Submit, with electronic signed SSA-827 generated.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E047"><data key="node_entity_id">R108_E047</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">SSA-827 Minor Age Twelve or Older Dual-Signature Rule</data><data key="node_domain">disability/evidence</data><data key="node_description">Some minor claimants aged 12 or older require both child and authorized adult signatures, subject to state privacy-law and policy exceptions.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E048"><data key="node_entity_id">R108_E048</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS CLLP Client Lawful Presence Payment Provision Screen</data><data key="node_acronym">CLLP</data><data key="node_domain">person/immigration</data><data key="node_description">Prior cleared MCS claim CLLP proof and permanent status can support later benefits lawful-presence proof with nonconflicting remarks and verification rules.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E049"><data key="node_entity_id">R108_E049</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident IDN H Permanent Work Authorization Code</data><data key="node_acronym">IDN H</data><data key="node_domain">person/immigration</data><data key="node_description">Code H represents permanent work authorization, not automatic current evidence of U.S. lawful presence; immigration circumstances may have changed.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E050"><data key="node_entity_id">R108_E050</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Lawful Presence Verified-Record Conditional Evidence Reuse</data><data key="node_domain">person/immigration</data><data key="node_description">Prior MBR/SSR/archived MCS/MSSICS proof can be reused only with acceptable codes, claims remarks, unchanged status, and conflict checks; Numident alone insufficient.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E051"><data key="node_entity_id">R108_E051</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA Online SAVE Query Response Person Attribute Set</data><data key="node_acronym">SAVE response attributes</data><data key="node_domain">person/immigration</data><data key="node_description">DHS SAVE online response may expose first/last name, DOB, country of birth, SSN, entry date, status, verification number and eligibility statement; not SSA master record.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E052"><data key="node_entity_id">R108_E052</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">Numident Identity Work-Authorization versus Lawful-Presence Evidence Restriction</data><data key="node_domain">person/immigration</data><data key="node_description">SSA policy expressly says Numident alien data and IDN H do not independently prove lawful presence for payment; additional documentary or DHS status verification required.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E053"><data key="node_entity_id">R108_E053</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Emergency Consultative Exam Report Medical-Source Disclosure</data><data key="node_domain">disability/evidence</data><data key="node_description">When CE results show an imminent life-threatening finding, DDS may send a copy to existing medical source without patient permission under health/safety disclosure exception.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E054"><data key="node_entity_id">R108_E054</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Claimant Notice of Emergency CE Medical-Source Disclosure</data><data key="node_domain">disability/evidence</data><data key="node_description">If DDS discloses emergency CE report without claimant permission, claimant is notified and letter retained in disability folder.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R108_E055"><data key="node_entity_id">R108_E055</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Emergency CE Report ERE or Direct-Fax Release Route</data><data key="node_domain">disability/evidence</data><data key="node_description">DDS sends urgent exam report by expeditious method, ERE or direct fax if available, and phones medical source to advise.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy documents logical or business surface; physical database/hosting/transport not established.</data></node><node id="R109_E001"><data key="node_entity_id">R109_E001</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS Title XVI Prisoner Update Screen (PU16)</data><data key="node_domain">program_integrity/prisoner</data><data key="node_description">PUPS input for Title XVI confinement dates, facility ID, case flags and suspension action codes.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E002"><data key="node_entity_id">R109_E002</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS Prisoner Remarks Screen (PRMK)</data><data key="node_domain">program_integrity/prisoner</data><data key="node_description">PUPS case-level explanation for MSSICS and non-PUPS manual processing, distinct from SSR remarks.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E003"><data key="node_entity_id">R109_E003</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS Prisoner Summary Screen (PUST)</data><data key="node_domain">program_integrity/prisoner</data><data key="node_description">Displays PUPS *PENDING when suspension input has been transmitted but SSR feedback is outstanding.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E004"><data key="node_entity_id">R109_E004</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS Title XVI Prisoner Status Query (P6QY)</data><data key="node_domain">program_integrity/prisoner</data><data key="node_description">Shows PUPS generation date, N22 feedback and corresponding incentive payment amount/date.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E005"><data key="node_entity_id">R109_E005</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Institution Residence Screen (LINS)</data><data key="node_domain">title_xvi/claims</data><data key="node_description">For active MSSICS cases, institution residence screen indicates Prisoner and supports N22 payment processing.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E006"><data key="node_entity_id">R109_E006</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR N22 Prisoner Nonpayment Status</data><data key="node_domain">title_xvi/payment</data><data key="node_description">Title XVI prisoner nonpayment status posted to the SSI payment record.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E007"><data key="node_entity_id">R109_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSR-to-PUPS N22 Suspension Feedback Cycle</data><data key="node_domain">program_integrity/prisoner</data><data key="node_description">SSR feedback following N22 posting changes PUPS case state from PENDING to SUSPENSION and can trigger incentive determination.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E008"><data key="node_entity_id">R109_E008</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">PUPS-Generated SSA-1719B Suspension Transaction</data><data key="node_domain">title_xvi/payment</data><data key="node_description">PUPS builds SSA-1719B suspension input for eligible non-MSSICS recipient cases.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E009"><data key="node_entity_id">R109_E009</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">PUPS PU16 Prisoner Mailing and Residence Address Inputs</data><data key="node_domain">person/address</data><data key="node_description">PU16 interface permits address editing for prisoner notices; no unqualified SSR/Numident address-update behavior is established.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E010"><data key="node_entity_id">R109_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">PUPS Title XVI Automated Suspension Exclusion Routing</data><data key="node_domain">program_integrity/prisoner</data><data key="node_description">When payee, institution, status or other specified conditions prevent automated suspension, FO applies SSI data-input or MSSICS route.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E011"><data key="node_entity_id">R109_E011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">PUPS Manual Reporter Incentive Payment Request and Approval</data><data key="node_domain">program_integrity/incentive</data><data key="node_description">Field Operations or PC coordinator verifies S7/N22 payment status and forwards documented request to Central Office for monthly authorization.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E012"><data key="node_entity_id">R109_E012</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">PUPS Reporter Identification Code (RID)</data><data key="node_domain">program_integrity/incentive</data><data key="node_description">Code associated with the prison reporter, required in manual incentive request.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E013"><data key="node_entity_id">R109_E013</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">PUPS Manual Incentive Payment Exception Control</data><data key="node_domain">program_integrity/incentive</data><data key="node_description">Flags missed MBR S7 or SSR N22 feedback, status exclusions, and disputed payments for manual review.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E014"><data key="node_entity_id">R109_E014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Central Office Monthly Manual Incentive Authorization</data><data key="node_domain">program_integrity/incentive</data><data key="node_description">Central Office authorizes manual reporter incentive payment releases on a monthly cadence after required controls.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E015"><data key="node_entity_id">R109_E015</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS Title II Prisoner Update Screen (PU02)</data><data key="node_domain">program_integrity/prisoner</data><data key="node_description">PUPS Title II clearing of *PENDING prisoner reports before manual incentive processing.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E016"><data key="node_entity_id">R109_E016</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SUMS/MCAS SSN/IRS/SSID Workload Listing Query</data><data key="node_domain">person/irs/address_provenance</data><data key="node_description">MI Central workload-listing query by SSN/IRS/SSID can retrieve IRS 5B/5H interface alerts and informational reports.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E017"><data key="node_entity_id">R109_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI IRS 5B and Pension 5H Workload Release Calendar</data><data key="node_domain">title_xvi/irs_control</data><data key="node_description">5B diaries released October, February, June; 5H pension alerts are released in conjunction with 5B workload.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E018"><data key="node_entity_id">R109_E018</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSID DIAR Segment Dedicated Account Diary Maturity</data><data key="node_domain">title_xvi/control</data><data key="node_description">SSI DI dedicated account diary selection and maturity recorded in SSID DIAR segment.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E019"><data key="node_entity_id">R109_E019</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI Redetermination Priority Diary Profiles and Selection Order</data><data key="node_domain">title_xvi/workload</data><data key="node_description">Policy orders RZ and LI release by profiles and priority diaries, not an independent electronic Person system.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E020"><data key="node_entity_id">R109_E020</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eRPS Organization ID ZIP and Sequence Identifier</data><data key="node_domain">person/payee_identity</data><data key="node_description">eRPS creates unique organization identifier using organization ZIP code plus sequence number; not a beneficiary address credential.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E021"><data key="node_entity_id">R109_E021</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Representative Payee Legal Structure Classification</data><data key="node_domain">person/payee_identity</data><data key="node_description">FO determines Individual versus Organization using legal business structure, not merely the EIN or outward business name.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E022"><data key="node_entity_id">R109_E022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">eRPS Organizational EIN and State Incorporation Evidence Development</data><data key="node_domain">person/payee_identity</data><data key="node_description">FO manager requests IRS or state registration evidence when organizational legal status or EIN conflicts with EIF.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E023"><data key="node_entity_id">R109_E023</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">eRPS Payment Legend Payee Display Name Attribute</data><data key="node_domain">payments/payee</data><data key="node_description">Payee payment legend should show individual or organization name, including DBA where relevant; distinct from proof of identity.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E024"><data key="node_entity_id">R109_E024</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">TreasuryDirect Electronic Savings Bond Account Service</data><data key="node_domain">external/treasury</data><data key="node_description">Treasury official account-based service for holding and transacting electronic U.S. savings bonds.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E025"><data key="node_entity_id">R109_E025</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">TreasuryDirect Current Holdings Summary</data><data key="node_domain">title_xvi/resources</data><data key="node_description">Account-holder supplied verification of electronic bond issue confirmation number, dates, ownership and value.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E026"><data key="node_entity_id">R109_E026</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Stock Bond or Mutual Fund (RSTB) Page</data><data key="node_domain">title_xvi/resources</data><data key="node_description">MSSICS resource documentation page records paper serial number or electronic sequential issue confirmation number and monthly redemption value.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E027"><data key="node_entity_id">R109_E027</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims CMSC Resource Coding Screen</data><data key="node_domain">title_xvi/resources</data><data key="node_description">CMSC screen can record RE21 savings bond case-characteristic coding with MSSICS bond resource entries.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E028"><data key="node_entity_id">R109_E028</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI RE21 Savings Bond Case Characteristic Code</data><data key="node_domain">title_xvi/resources</data><data key="node_description">RE21 code in CG or CMSC identifies savings bond resource characteristic; not a bank address or source of contact data.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E029"><data key="node_entity_id">R109_E029</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Savings Bond Paper versus Electronic Resource Verification</data><data key="node_domain">title_xvi/resources</data><data key="node_description">Staff distinguish paper bonds and claimant-provided TreasuryDirect electronic account Current Holdings evidence; EVID/SSR/MSSICS retain verified case values.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E030"><data key="node_entity_id">R109_E030</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS Select Case Level CDR Hearing Option</data><data key="node_domain">hearings/disability</data><data key="node_description">eCDR cessation appeal intake case-level option in EDCS.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E031"><data key="node_entity_id">R109_E031</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS CDR Hearing Case Creation Confirmation</data><data key="node_domain">hearings/disability</data><data key="node_description">Appeal filing date is imported from MSSICS where available or manually entered when creating CDR hearing.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E032"><data key="node_entity_id">R109_E032</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">EDCS CDR Hearing Person and Representative Contact Data</data><data key="node_domain">person/address</data><data key="node_description">eCDR hearing case includes claimant, attorney, and payee names and addresses plus appeal and statutory continuation information.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E033"><data key="node_entity_id">R109_E033</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title XVI eCDR Appeal SSR Pretransfer Synchronization</data><data key="node_domain">hearings/disability</data><data key="node_description">For SSI-only/concurrent cases, FO documents cessation appeal/SBC election through MSSICS to SSID before EDCS transfer; FO verifies address/phone/representatives on mainframe.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E034"><data key="node_entity_id">R109_E034</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS eCDR Prior Comparison Point Decision Folder Linking</data><data key="node_domain">disability/evidence</data><data key="node_description">EDCS supports linking electronic CPD comparison folder to current eCDR; paper folder is routed physically.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E035"><data key="node_entity_id">R109_E035</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Reopening Affirmative Action in Writing Evidentiary Clock</data><data key="node_domain">title_xvi/reopening</data><data key="node_description">Policy uses receipt date of specified signed communications, financial institution reports or IRS interface alert development to determine reopening procedural dates.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E036"><data key="node_entity_id">R109_E036</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI IRS Interface Alert Reopening Development Trigger</data><data key="node_domain">title_xvi/irs_control</data><data key="node_description">IRS interface alert may prompt resource or income development; alert and development date do not prove resource or address values were correct.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E037"><data key="node_entity_id">R109_E037</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">e1696 Portal Exclusion of Supplemental Attachments</data><data key="node_domain">representation/intake</data><data key="node_description">SSA e1696 online appointment-of-representative route cannot accept other representational document attachments with submitted e1696.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E038"><data key="node_entity_id">R109_E038</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Appointment of Representative Misrouted Form Redirect</data><data key="node_domain">representation/intake</data><data key="node_description">DDS cannot process SSA-1696; it routes form received to servicing SSA field office.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R109_E039"><data key="node_entity_id">R109_E039</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Representative Payee Selection Without SSN Manual Record Update</data><data key="node_domain">person/payee_identity</data><data key="node_description">When a selected payee lacks SSN and cannot receive one, SSA uses paper SSA-11-BK and manual MBR/SSR payee selection.</data><data key="node_observed_status">documented_operational_policy_as_of_referenced_revision</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented policy/data product, not proof of underlying storage, vendor, infrastructure, or automatic update absent explicit source language.</data></node><node id="R110_E001"><data key="node_entity_id">R110_E001</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Information Retrieval Groups (IRG)</data><data key="node_domain">title_ii/paper_evidence</data><data key="node_description">SSANRC and MAMPSC teams supply information/documents from stored Title II paper folders to FO, WSU and PC; do not adjudicate or update screens.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E002"><data key="node_entity_id">R110_E002</data><data key="node_entity_type">facility</data><data key="node_canonical_name">SSA National Records Center (SSANRC)</data><data key="node_domain">title_ii/paper_evidence</data><data key="node_description">SSA facility storing Title II paper claims folders; IRG provides targeted information retrieval.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E003"><data key="node_entity_id">R110_E003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Information Retrieval Group Stored-Folder Information Request</data><data key="node_domain">title_ii/evidence</data><data key="node_description">Staff first check electronic sources and current PCACS location, then request targeted information from IRG rather than defaulting to full paper-folder retrieval.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E004"><data key="node_entity_id">R110_E004</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">PCACS Current Paper Folder Location Indicator</data><data key="node_domain">title_ii/folder_location</data><data key="node_description">PCACS query supplies current location; unlike MBR FLI, it must be refreshed because folders move.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E005"><data key="node_entity_id">R110_E005</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">MBR Folder Location Indicator (FLI)</data><data key="node_domain">title_ii/folder_location</data><data key="node_description">MBR folder-location field explicitly considered unreliable for current paper-folder retrieval under IRG policy.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E006"><data key="node_entity_id">R110_E006</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">PCACS CAVE FILE Location Reference</data><data key="node_domain">title_ii/paper_evidence</data><data key="node_description">PCACS LOCATION field CAVE FILE marker triggers an ADMS request to the SSANRC IRG; no physical store type established.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E007"><data key="node_entity_id">R110_E007</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">PCACS QUES Folder Location Code</data><data key="node_domain">title_ii/paper_evidence</data><data key="node_description">PCACS QUES indicates case folder is not in the National Records Center, so staff must not send an IRG information request.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E008"><data key="node_entity_id">R110_E008</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Administrative Message (ADMS) IRG Request</data><data key="node_domain">title_ii/paper_evidence</data><data key="node_description">PCOM SSA Main Menu -&gt; ADMM option 15 sends targeted IRG administrative requests, with SSN/number holder name and request details.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E009"><data key="node_entity_id">R110_E009</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PCOM Administrative Applications Menu (ADMM)</data><data key="node_domain">title_ii/paper_evidence</data><data key="node_description">Administrative Applications Menu accessed from SSA Main Menu for ADMS requests to SSANRC IRG.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E010"><data key="node_entity_id">R110_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRG Retrieved Paper Information Electronic-Folder Delivery</data><data key="node_domain">title_ii/evidence</data><data key="node_description">IRG may convey retrieved information by telephone, fax, email or upload to an electronic claims folder; no specific transport/retention proven.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E011"><data key="node_entity_id">R110_E011</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">T2Fld Title II Folder Location Toolbar Macro</data><data key="node_domain">disability/record_location</data><data key="node_description">T2Fld macro in Query Master/PCOM toolbar can locate Title II folders; software implementation unconfirmed.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E012"><data key="node_entity_id">R110_E012</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">T16Fld Title XVI Folder Location Toolbar Macro</data><data key="node_domain">disability/record_location</data><data key="node_description">T16Fld macro in Query Master/PCOM toolbar can locate Title XVI folders.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E013"><data key="node_entity_id">R110_E013</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Query Master Toolbar</data><data key="node_domain">disability/record_location</data><data key="node_description">SSA Query Master includes T2Fld/T16Fld folder-location macros as of 2023 POMS; runtime details undisclosed.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E014"><data key="node_entity_id">R110_E014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CDR Comparison Point Decision (CPD) Date Verification</data><data key="node_domain">disability/cdr</data><data key="node_description">SSA identifies most recent favorable medical decision and examiner-signature date from SSA-831/832/833 or decision; requires proper CPD folder.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E015"><data key="node_entity_id">R110_E015</data><data key="node_entity_type">document_repository</data><data key="node_canonical_name">CPD Medical and Vocational Evidence Folder</data><data key="node_domain">disability/cdr</data><data key="node_description">Comparison-point decision folder must contain pertinent medical and vocational evidence from most recent favorable decision.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E016"><data key="node_entity_id">R110_E016</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">eView Initial Case Status Paper-Folder Indicator</data><data key="node_domain">disability/cdr</data><data key="node_description">eView Status/History Initial Case Status Summary checkbox tells staff whether a paper folder was created for a filing.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E017"><data key="node_entity_id">R110_E017</data><data key="node_entity_type">document_repository</data><data key="node_canonical_name">Title XVI Brown Nonmedical Paper Folder</data><data key="node_domain">disability/paper_evidence</data><data key="node_description">Legacy concurrent-case brown folder contains nonmedical Title XVI records and is not itself qualifying CPD folder.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E019"><data key="node_entity_id">R110_E019</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EXR Assistant Folder-Location Workflow</data><data key="node_domain">disability/exr</data><data key="node_description">Named workflow assistant referenced for folder location and potential unable-to-locate form workflows.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">2023 POMS names assistant; future planned custom form within WAC is not proof of deployment.</data></node><node id="R110_E020"><data key="node_entity_id">R110_E020</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">AFL Unable-to-Locate Folder Form Generator</data><data key="node_domain">disability/record_location</data><data key="node_description">POMS describes AFL generating custom SSA-5002 for unable-to-locate folders, with future WAC integration described as planned.</data><data key="node_observed_status">historically_described_planned_WAC_feature</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Expansion of AFL acronym unspecified. Custom Express Forms feature described prospectively in 2023, deployment unverified.</data></node><node id="R110_E021"><data key="node_entity_id">R110_E021</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Work CDR Reconsideration in eWork</data><data key="node_domain">disability/work_cdr</data><data key="node_description">Reconsideration of earnings/work determinations established in eWork; new adjudicator reviews evidence and issues a decision.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E022"><data key="node_entity_id">R110_E022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Work CDR Reopening in eWork</data><data key="node_domain">disability/work_cdr</data><data key="node_description">eWork work-review reopening with revised earnings and work incentive information subject to administrative finality.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E023"><data key="node_entity_id">R110_E023</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eWork Work CDR Direct-Input/Reconsideration Exclusion</data><data key="node_domain">disability/work_cdr</data><data key="node_description">Initial determination outside eWork creates reconsideration exclusion; some reversals excluded from POS direct input.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E024"><data key="node_entity_id">R110_E024</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Work CDR Determination Electronic-Folder and PSC Paperless Multi-Fax</data><data key="node_domain">disability/evidence</data><data key="node_description">When FO decisions require PC action, documentation is faxed to both the certified electronic folder and PC Paperless; barcode for fully electronic cases.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E025"><data key="node_entity_id">R110_E025</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-899-U2 Continuing Disability Review Form</data><data key="node_domain">disability/work_cdr</data><data key="node_description">Named revised or affirming work CDR determination form used in Title II reconsiderations.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E026"><data key="node_entity_id">R110_E026</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">eWork FO-to-PC Work CDR Reconsideration Transfer</data><data key="node_domain">disability/work_cdr</data><data key="node_description">FO forwards eWork reconsideration to PC/DCR when processing cannot be completed locally and dual routes evidence as instructed.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E027"><data key="node_entity_id">R110_E027</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Congressional Inquiry Case Handling</data><data key="node_domain">disability/congressional_service</data><data key="node_description">DDS acknowledges and tracks congressional and White House case inquiries, responding based on folder location and claim status.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E028"><data key="node_entity_id">R110_E028</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DDS Congressional Inquiry Electronic Folder Flag</data><data key="node_domain">disability/congressional_service</data><data key="node_description">DDS marks pending/completed inquiry on folder and electronic folder; not a separate enterprise database.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E029"><data key="node_entity_id">R110_E029</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DDS Congressional Inquiry 20/30-Day Follow-Up Diary</data><data key="node_domain">disability/congressional_service</data><data key="node_description">DDS tracks 20-day deadline after acknowledgement and 30-day interim-report follow-ups until final disposition.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E030"><data key="node_entity_id">R110_E030</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">DDS Congressional Inquiry Interim and Final Responses</data><data key="node_domain">disability/congressional_service</data><data key="node_description">DDS interim and final congressional reply/clearance messages; may include exam, delay and case transfer facts.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E031"><data key="node_entity_id">R110_E031</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">FFSCF Fugitive Felon Disposition and Good-Cause Screen (FFDG)</data><data key="node_domain">program_integrity/fugitive_felon</data><data key="node_description">FFDG screen records protest, disposition and good-cause indicators controlling fugitive felon suspension work.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E032"><data key="node_entity_id">R110_E032</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Fugitive Felon Warrant Information Query (FFWQ)</data><data key="node_domain">program_integrity/fugitive_felon</data><data key="node_description">FFWQ query reveals source of warrant report so protest is annotated using appropriate rules.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E033"><data key="node_entity_id">R110_E033</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Fugitive Felon Deferred Overpayment Recovery Case</data><data key="node_domain">payments/debt</data><data key="node_description">When beneficiary protests under qualifying circumstances and disposition is pending, staff defer overpayment recovery while maintaining case control.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E034"><data key="node_entity_id">R110_E034</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">ROAR Protest/Stop Recovery Request Code 14</data><data key="node_domain">payments/debt</data><data key="node_description">ROAR code 14 prevents recovery of certain closed-period fugitive-felon overpayments pending disposition.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E035"><data key="node_entity_id">R110_E035</data><data key="node_entity_type">form</data><data key="node_canonical_name">2795 Fugitive Felon Processing Exclusion Form</data><data key="node_domain">program_integrity/fugitive_felon</data><data key="node_description">Paper PSC referral artifact for closed fugitive felon suspension cases; documented instructions prohibit faxing deferred case material.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E036"><data key="node_entity_id">R110_E036</data><data key="node_entity_type">interface</data><data key="node_canonical_name">FFSCF Title II Suspension Finder Transaction</data><data key="node_domain">program_integrity/fugitive_felon</data><data key="node_description">FFSCF sends applicable finder to Title II to post fugitive-felon history / status, subject to protests and case rules.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E037"><data key="node_entity_id">R110_E037</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">TRO ECO Pre-Offset Notice Delivery Record</data><data key="node_domain">payments/debt</data><data key="node_description">Pre-offset notice sent at AVC verified address or recent MBR/SSR fallback; after Nov 2015 notice is retained in ORS.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E038"><data key="node_entity_id">R110_E038</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">ROAR Transaction Correction (SMTC) Screen</data><data key="node_domain">payments/debt</data><data key="node_description">Used to delete old ROAR debt on successful returned-notice review before same debt reestablished at new establishment date.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E039"><data key="node_entity_id">R110_E039</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">ROAR Establish Debt (SMED) Screen</data><data key="node_domain">payments/debt</data><data key="node_description">Reestablishes ROAR debt with new establishment date after verified undeliverable original notice.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E040"><data key="node_entity_id">R110_E040</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Stop Offset (TRSO) Screen</data><data key="node_domain">payments/debt</data><data key="node_description">TOP menu screen used to delete deceased debtor from TOP after death verification.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E041"><data key="node_entity_id">R110_E041</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Record Bankruptcy Petition (DFBP) Screen</data><data key="node_domain">payments/debt</data><data key="node_description">Record petition or bankruptcy judgment as decision pending to prevent collection while processed.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E042"><data key="node_entity_id">R110_E042</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Correct Offset Amount (TRCA) Screen</data><data key="node_domain">payments/debt</data><data key="node_description">PC uses correct offset amount screen for agency refund after improper Treasury offset on unresolved timely waiver/reconsideration/hearing.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E043"><data key="node_entity_id">R110_E043</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Stop Collection Action (TRSC) Screen</data><data key="node_domain">payments/debt</data><data key="node_description">Stop collection when final review establishes debt not past due or not legally enforceable.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E044"><data key="node_entity_id">R110_E044</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Terminate Collection (DFTE) Screen</data><data key="node_domain">payments/debt</data><data key="node_description">Control used to terminate/re-activate external collection processing after described review outcomes.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E049"><data key="node_entity_id">R110_E049</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">TRO Undeliverable Original Notice Debt Reestablishment</data><data key="node_domain">payments/debt</data><data key="node_description">When original notice was undeliverable and no substitute was mailed, send new notice, delete and reestablish ROAR debt with current date and renewed rights.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E050"><data key="node_entity_id">R110_E050</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">TRO AVC Verified Address / MBR-SSR Recency Fallback Rule</data><data key="node_domain">address_provenance/debt_notice</data><data key="node_description">AVC verified address used first; otherwise MBR/SSR address updated within one year, otherwise AVC recheck after six months; no master write inferred.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E051"><data key="node_entity_id">R110_E051</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSQM ADDR Segment Request for Supplemental Security Record</data><data key="node_domain">address_provenance/title_ii_title_xvi</data><data key="node_description">SSQM ADDR query retrieves current SSI address and change date to compare with MBR updated timestamp.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E052"><data key="node_entity_id">R110_E052</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">MBR Supplemental Security Income (SID) Data Line</data><data key="node_domain">address_provenance/title_ii_title_xvi</data><data key="node_description">MBR SID data line is lead to query SSR for concurrent beneficiary address.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E055"><data key="node_entity_id">R110_E055</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Title II LAF S6 Whereabouts Unknown Suspension</data><data key="node_domain">title_ii/suspension</data><data key="node_description">If MBR/SSR, phone and FI/USPS development fail for current-pay case, staff post POS LAF S6 and annotate MBR Special Message.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R110_E056"><data key="node_entity_id">R110_E056</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Federal Funding Accountability and Transparency Act Subaward Reporting System (FSRS)</data><data key="node_domain">procurement/grants</data><data key="node_description">SSA grantees issuing qualifying subawards at or above $30,000 must report them through FSRS, except individual subawards under the cited rules.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">SSA OAG FAQ confirms federal reporting website; no SSA internal technical integration inferred.</data></node><node id="R110_E057"><data key="node_entity_id">R110_E057</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Grant Recipient Cost-Share / Program Income Financial Reporting</data><data key="node_domain">procurement/grants</data><data key="node_description">Cost share tracked as actual spending in SF-425 boxes 10(i)-(k); award-generated program income follows award terms and federal rules.</data><data key="node_observed_status">documented_policy_2022_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Named operating element confirmed in public SSA sources. Physical technology/retention and automatic synchronization not inferred.</data></node><node id="R111_E001"><data key="node_entity_id">R111_E001</data><data key="node_entity_type">security_program</data><data key="node_canonical_name">SSA Enterprise Information Security Program</data><data key="node_domain">Enterprise Security / FISMA</data><data key="node_description">Agency-wide information-security program evaluated under FISMA; FY2026 OIG assessed overall maturity at Level 3, Consistently Implemented, and Not Effective.</data><data key="node_observed_status">observed_current_level3_not_effective</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E002"><data key="node_entity_id">R111_E002</data><data key="node_entity_type">enterprise_inventory</data><data key="node_canonical_name">Enterprise Architecture System Inventory</data><data key="node_domain">Enterprise Architecture / Security Asset Management</data><data key="node_description">SSA enterprise architecture inventory of information systems; FY2026 OIG says completeness and accuracy still required refinement.</data><data key="node_observed_status">observed_current_incomplete</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E003"><data key="node_entity_id">R111_E003</data><data key="node_entity_type">enterprise_inventory</data><data key="node_canonical_name">Enterprise Software Inventory</data><data key="node_domain">Enterprise Architecture / Security Asset Management</data><data key="node_description">Enterprise software inventory used in SSA risk and asset management; FY2026 OIG says completeness and accuracy still required improvement.</data><data key="node_observed_status">observed_current_incomplete</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E004"><data key="node_entity_id">R111_E004</data><data key="node_entity_type">enterprise_inventory</data><data key="node_canonical_name">Enterprise Hardware Inventory</data><data key="node_domain">Enterprise Architecture / Security Asset Management</data><data key="node_description">Enterprise hardware inventory used in SSA risk and asset management; FY2026 OIG says completeness and accuracy still required improvement.</data><data key="node_observed_status">observed_current_incomplete</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E005"><data key="node_entity_id">R111_E005</data><data key="node_entity_type">enterprise_inventory</data><data key="node_canonical_name">Enterprise Data Inventory</data><data key="node_domain">Enterprise Data / Security Asset Management</data><data key="node_description">Agency data inventory; FY2026 OIG says SSA did not maintain a comprehensive and accurate inventory of data.</data><data key="node_observed_status">observed_current_incomplete</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E006"><data key="node_entity_id">R111_E006</data><data key="node_entity_type">enterprise_inventory</data><data key="node_canonical_name">Enterprise Metadata Inventory</data><data key="node_domain">Enterprise Data / Metadata / Security</data><data key="node_description">Agency metadata inventory corresponding to data assets; FY2026 OIG says SSA did not maintain a comprehensive and accurate metadata inventory.</data><data key="node_observed_status">observed_current_incomplete</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E007"><data key="node_entity_id">R111_E007</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Information Security Continuous Monitoring Program</data><data key="node_acronym">ISCM</data><data key="node_domain">Enterprise Security / Continuous Monitoring</data><data key="node_description">SSA continuous-monitoring program assessed under FISMA; OIG recommends ensuring all application assets are in monitoring scope and improving vulnerability management.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E008"><data key="node_entity_id">R111_E008</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Privileged Account Management Program</data><data key="node_acronym">PAM</data><data key="node_domain">Enterprise Security / Identity and Access Management</data><data key="node_description">SSA privileged-account oversight and management capability; FY2026 OIG recommends continued improvement in user-account oversight and management.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E009"><data key="node_entity_id">R111_E009</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Configuration Management Program</data><data key="node_domain">Enterprise Security / Configuration Management</data><data key="node_description">SSA configuration-management program assessed under FISMA; OIG says configuration management and risk-based decisions require continued improvement.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E010"><data key="node_entity_id">R111_E010</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Vulnerability Management Process</data><data key="node_domain">Enterprise Security / Vulnerability Management</data><data key="node_description">SSA vulnerability-management process within continuous monitoring; FY2026 OIG recommends continued improvement.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E011"><data key="node_entity_id">R111_E011</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Contingency Planning Program</data><data key="node_domain">Enterprise Security / Resilience</data><data key="node_description">SSA contingency-planning security domain; FY2026 OIG found contingency exercises were not completed for all systems.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E012"><data key="node_entity_id">R111_E012</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Business Impact Analysis Process</data><data key="node_domain">Enterprise Security / Resilience</data><data key="node_description">System business-impact analysis activity within contingency planning; FY2026 OIG found BIAs were not completed for all systems.</data><data key="node_observed_status">observed_current_incomplete</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E013"><data key="node_entity_id">R111_E013</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Enterprise Security Training Program</data><data key="node_domain">Enterprise Security / Training</data><data key="node_description">SSA security-training domain assessed under FISMA. Public audit establishes the program domain but omits sensitive implementation details.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E014"><data key="node_entity_id">R111_E014</data><data key="node_entity_type">it_governance_process</data><data key="node_canonical_name">Inflight Investment Review</data><data key="node_acronym">IIR</data><data key="node_domain">Enterprise IT Governance / CPIC</data><data key="node_description">Semiannual programmatic-area review tracking high-level IT-investment performance and issues, including cost, risk, and value data.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E015"><data key="node_entity_id">R111_E015</data><data key="node_entity_type">it_governance_process</data><data key="node_canonical_name">Value Realization Process</data><data key="node_domain">Enterprise IT Governance / CPIC</data><data key="node_description">Monthly SSA process that develops and tracks value activities against targets established during IT-investment planning.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E016"><data key="node_entity_id">R111_E016</data><data key="node_entity_type">internal_web_application</data><data key="node_canonical_name">Value Realization Website</data><data key="node_domain">Enterprise IT Governance / CPIC</data><data key="node_description">Website used for SSA value-realization reporting; OIG notes DMP value information on the site was incomplete/inconsistent.</data><data key="node_observed_status">observed_historical_2020_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E017"><data key="node_entity_id">R111_E017</data><data key="node_entity_type">it_governance_process</data><data key="node_canonical_name">Quarterly Health Review</data><data key="node_acronym">QHR</data><data key="node_domain">Enterprise IT Governance / CPIC</data><data key="node_description">Quarterly self-assessment for all IT investments covering performance, human capital, risk, contract management, requirements, and incremental development.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E018"><data key="node_entity_id">R111_E018</data><data key="node_entity_type">it_governance_process</data><data key="node_canonical_name">CIO Program Manager Engagement</data><data key="node_domain">Enterprise IT Governance / CPIC</data><data key="node_description">Quarterly CIO and program-manager meeting for major IT investments; program manager proposes CIO rating for Federal IT Dashboard.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E019"><data key="node_entity_id">R111_E019</data><data key="node_entity_type">it_governance_process</data><data key="node_canonical_name">CIO Evaluation</data><data key="node_domain">Enterprise IT Governance / CPIC</data><data key="node_description">Quarterly CIO determination of final major-investment rating using engagement results, followed by reporting to Federal IT Dashboard.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E020"><data key="node_entity_id">R111_E020</data><data key="node_entity_type">external_federal_service</data><data key="node_canonical_name">Federal IT Dashboard</data><data key="node_domain">Federal IT Governance / Public Reporting</data><data key="node_description">Federal website used to publish and track information on Federal IT investments; SSA CIO ratings for major investments are reported to it.</data><data key="node_observed_status">observed_external_current_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E021"><data key="node_entity_id">R111_E021</data><data key="node_entity_type">recommended_control</data><data key="node_canonical_name">Earned Value Management System or Equivalent Investment Measurement</data><data key="node_acronym">EVMS</data><data key="node_domain">Enterprise IT Governance / Performance Management</data><data key="node_description">Cost/schedule/performance measurement capability required by OMB and recommended by OIG for SSA; public audit does not establish that SSA had implemented EVMS as of Aug 2026.</data><data key="node_observed_status">recommended_not_confirmed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E022"><data key="node_entity_id">R111_E022</data><data key="node_entity_type">it_governance_process</data><data key="node_canonical_name">TechStat Review Process</data><data key="node_domain">Enterprise IT Governance / CPIC</data><data key="node_description">Federal-style troubled-investment review that OIG recommended SSA reestablish in its CPIC process; current reestablishment not proven.</data><data key="node_observed_status">recommended_reestablishment_not_confirmed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E023"><data key="node_entity_id">R111_E023</data><data key="node_entity_type">governance_role</data><data key="node_canonical_name">IT Programmatic Area Lead</data><data key="node_domain">Enterprise IT Governance / CPIC</data><data key="node_description">SSA programmatic-area role that annually prioritized IT investments in FY2023-FY2025 and participated in CPIC portfolio controls.</data><data key="node_observed_status">documented_fy2023_2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E024"><data key="node_entity_id">R111_E024</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Division of Financial Management</data><data key="node_domain">Financial Management / IT Governance</data><data key="node_description">Division containing the Technology and Financial Support Branch reviewed by OIG for SSA Post-Implementation Reviews.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E025"><data key="node_entity_id">R111_E025</data><data key="node_entity_type">organization_component</data><data key="node_canonical_name">Technology and Financial Support Branch</data><data key="node_domain">Financial Management / IT Governance</data><data key="node_description">Branch within the Division of Financial Management responsible for the PIR area reviewed by OIG.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E026"><data key="node_entity_id">R111_E026</data><data key="node_entity_type">governance_data_artifact</data><data key="node_canonical_name">Post-Implementation Review Final Report</data><data key="node_domain">Enterprise IT Governance / PIR</data><data key="node_description">Expected final PIR output containing actionable insights on how SSA can improve investments and investment processes.</data><data key="node_observed_status">documented_required_output</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E027"><data key="node_entity_id">R111_E027</data><data key="node_entity_type">leadership_role</data><data key="node_canonical_name">Head of Insider Threat and Resiliency</data><data key="node_domain">Enterprise Security / Insider Threat</data><data key="node_description">SSA leadership role named in January 2026 to lead insider-threat and resiliency functions.</data><data key="node_observed_status">observed_current_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E028"><data key="node_entity_id">R111_E028</data><data key="node_entity_type">leadership_role</data><data key="node_canonical_name">Information Sharing and Safeguarding Senior Official</data><data key="node_acronym">ISSSO</data><data key="node_domain">Enterprise Security / Information Sharing</data><data key="node_description">SSA senior official role required under Executive Order 13587; in Jan 2026 held by the Head of Insider Threat and Resiliency.</data><data key="node_observed_status">observed_current_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E029"><data key="node_entity_id">R111_E029</data><data key="node_entity_type">security_training_process</data><data key="node_canonical_name">Insider Threat Awareness Training Program</data><data key="node_domain">Enterprise Security / Insider Threat</data><data key="node_description">SSA insider-threat awareness training program for cleared employees and, by SSA policy, all active employees.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E030"><data key="node_entity_id">R111_E030</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">Personnel Separation System-Access Revocation Process</data><data key="node_domain">Enterprise Security / Personnel Security</data><data key="node_description">Separation process for disabling system access and terminating/revoking authenticators and credentials; OIG reviewed SSA implementation and found deficiencies.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E031"><data key="node_entity_id">R111_E031</data><data key="node_entity_type">security_record</data><data key="node_canonical_name">Insider Threat Inquiry Report</data><data key="node_domain">Enterprise Security / Insider Threat</data><data key="node_description">SSA documented record for insider-threat matters and response actions; OIG sampled inquiry reports and found deficiencies.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E032"><data key="node_entity_id">R111_E032</data><data key="node_entity_type">security_record</data><data key="node_canonical_name">Annual Insider Threat Self-Assessment Report</data><data key="node_domain">Enterprise Security / Insider Threat</data><data key="node_description">Annual SSA self-assessment/report of compliance with insider-threat policies to the NITTF Senior Information Sharing and Safeguarding Steering Committee.</data><data key="node_observed_status">observed_current_improvement_needed</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E033"><data key="node_entity_id">R111_E033</data><data key="node_entity_type">external_federal_organization</data><data key="node_canonical_name">National Insider Threat Task Force</data><data key="node_acronym">NITTF</data><data key="node_domain">Federal Security / Insider Threat</data><data key="node_description">Federal task force receiving annual insider-threat compliance reporting and issuing minimum standards.</data><data key="node_observed_status">external_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E034"><data key="node_entity_id">R111_E034</data><data key="node_entity_type">deployment_process</data><data key="node_canonical_name">AWS Connect Agency Rollout Process</data><data key="node_domain">Customer Service / Telephony / Cloud</data><data key="node_description">SSA staged Amazon Connect deployment across N8NN, field offices, card centers, processing centers, international call center, DDS and disability units during 2024-2026.</data><data key="node_observed_status">observed_rollout_2024_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E035"><data key="node_entity_id">R111_E035</data><data key="node_entity_type">deployment_plan</data><data key="node_canonical_name">AWS Connect Rollout Schedule</data><data key="node_domain">Customer Service / Telephony / Cloud</data><data key="node_description">OIG Appendix B rollout schedule: field offices/card centers in 2025; processing centers and International Call Center fall 2025; remainder of DDS/DPB/DPU winter 2026; broader components planned spring/summer 2026 and agencywide target September 2026.</data><data key="node_observed_status">documented_plan_and_completed_stages</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E036"><data key="node_entity_id">R111_E036</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Person Multiple Claim Summary Page</data><data key="node_domain">Title XVI / Claims Intake</data><data key="node_description">SSI Claims page used to establish a new claim before selecting abbreviated application processing.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E037"><data key="node_entity_id">R111_E037</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Application Page</data><data key="node_domain">Title XVI / Claims Intake</data><data key="node_description">SSI Claims page where technician selects Abbreviated as application type for a clear technical denial.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E038"><data key="node_entity_id">R111_E038</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Abbreviated Application Reason</data><data key="node_domain">Title XVI / Claims Intake</data><data key="node_description">Reason selected on SSI Application page; determines which additional screens appear in the abbreviated-application path.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E039"><data key="node_entity_id">R111_E039</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-462 SSI Abbreviated Application Data Input Form</data><data key="node_acronym">SSA-462</data><data key="node_domain">Title XVI / Claims Intake / Forms</data><data key="node_description">Form used to establish a systems record for paper abbreviated SSI applications.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E040"><data key="node_entity_id">R111_E040</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CDB Age-18 Pending Disability Determination Process</data><data key="node_acronym">CDB</data><data key="node_domain">Title II / Childhood Disability</data><data key="node_description">For child benefits terminated or approaching termination at age 18, SSA can suspend/diary pending a disability determination and later reinstate/convert if disability is established.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E041"><data key="node_entity_id">R111_E041</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">CDB Determination Pending Processing-Center Diary</data><data key="node_domain">Title II / Childhood Disability / Processing Center</data><data key="node_description">Processing-center diary used when DDIB process cannot be used; annotated CDB determination pending with month/year of age-18 attainment.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E042"><data key="node_entity_id">R111_E042</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">MBR BENE ENT Disability Determination Line</data><data key="node_domain">Title II / MBR / Childhood Disability</data><data key="node_description">MBR BENE ENT line receives disability determination information to enable automatic conversion for qualifying age-18 childhood-disability cases.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R111_E043"><data key="node_entity_id">R111_E043</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Childhood Disability Automatic Conversion</data><data key="node_domain">Title II / Childhood Disability</data><data key="node_description">Automatic conversion enabled after disability determination is posted to MBR BENE ENT line for qualifying age-18 continuation cases.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Validated from authoritative public evidence; undocumented technology, hosting, schema, transport, and write behavior are not inferred.</data></node><node id="R112_E001"><data key="node_entity_id">R112_E001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Direct Deposit Fraud-Alleged Nonreceipt Workflow</data><data key="node_domain">payments / fraud</data><data key="node_description">Technician screens payment nonreceipt and records fraud allegation; triggers trace and potential emergency replacement payment.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E002"><data key="node_entity_id">R112_E002</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Fraud-Alleged Type B Nonreceipt Indicator</data><data key="node_domain">payments / fraud</data><data key="node_description">Fraud-alleged Y indicator entered for each potentially fraudulent type B nonreceipt report.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E003"><data key="node_entity_id">R112_E003</data><data key="node_entity_type">processing_component</data><data key="node_canonical_name">Return Check Action Program REACT</data><data key="node_acronym">REACT</data><data key="node_domain">payments / fraud</data><data key="node_description">REACT processes a nonreceipt claim and records the alleged-fraud event to PHUS.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E004"><data key="node_entity_id">R112_E004</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">PHUS Event 069 Fraud Alleged</data><data key="node_domain">payments / fraud</data><data key="node_description">Fraud-alleged nonreceipt identifier shown on Payment History Update System.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E005"><data key="node_entity_id">R112_E005</data><data key="node_entity_type">application</data><data key="node_canonical_name">Direct Express R14/R16 Request Application</data><data key="node_domain">payments / nonreceipt</data><data key="node_description">Employee application for Direct Express R16 requests involving fraud or redirected card payments.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E006"><data key="node_entity_id">R112_E006</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">CPS Critical Payment Details CRSN Screen</data><data key="node_domain">payments / claims</data><data key="node_description">Screen for processing-center fraud-related remarks when issuing a critical payment.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E007"><data key="node_entity_id">R112_E007</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4904-U2 SSI Monthly Payment Computation Summary</data><data key="node_domain">Title XVI / payments</data><data key="node_description">A-OTP reason-for-payment documentation form used in alleged direct-deposit fraud replacement payments.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E008"><data key="node_entity_id">R112_E008</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Unauthorized Direct Deposit Replacement Payment Review</data><data key="node_domain">payments / fraud</data><data key="node_description">Selects CPS, SSI immediate payment, or automated one-time payment and creates required documented evidence.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E009"><data key="node_entity_id">R112_E009</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">TCIS Integrated View EFT Claim Form Screen</data><data key="node_domain">Treasury / payment claims</data><data key="node_description">Treasury Check Information System Integrated View supports EFT Claim Form retrieval and reprinting and claim status checks.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E010"><data key="node_entity_id">R112_E010</data><data key="node_entity_type">external_form</data><data key="node_canonical_name">Treasury EFT Claim Form for Unauthorized ENR Payment</data><data key="node_domain">Treasury / payment claims</data><data key="node_description">Treasury claim form for loss recovery after unauthorized financial-institution automated enrollment; not used for Direct Express requests.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E011"><data key="node_entity_id">R112_E011</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">TCIS ENR EFT Claim Form Status and Resent Date</data><data key="node_domain">Treasury / payment claims</data><data key="node_description">TCIS-reported EFT claims disposition, reprint/resent dates and financial-institution debit status.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E012"><data key="node_entity_id">R112_E012</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Treasury EFT Claim Undeliverable Address Reconciliation</data><data key="node_domain">address provenance / payments</data><data key="node_description">Reviews failed mailing against current MBR/SSR addresses; develops verified address and conditionally resends EFT Claim Form.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA validation and staff correction only; no TCIS-to-MBR/SSR automated write inferred.</data></node><node id="R112_E013"><data key="node_entity_id">R112_E013</data><data key="node_entity_type">external_report</data><data key="node_canonical_name">Treasury ENR Recovery Debit Detail Report</data><data key="node_domain">Treasury / debt</data><data key="node_description">Treasury fax report identifying returned funds from financial institutions after unauthorized ENR payment redirection.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E014"><data key="node_entity_id">R112_E014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Office of Benefit Accounting and System Analysis SSI Remittance Posting</data><data key="node_domain">Title XVI / debt</data><data key="node_description">Office responsible for applying SSI partial financial-institution credits to SSR overpayment refund data.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E015"><data key="node_entity_id">R112_E015</data><data key="node_entity_type">record_segment</data><data key="node_canonical_name">SSR Overpayment Refund Data OPRR Segment</data><data key="node_acronym">OPRR</data><data key="node_domain">Title XVI / debt</data><data key="node_description">SSR segment for partial recoveries and adjustments including financial-institution fraud remittances.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E016"><data key="node_entity_id">R112_E016</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">SSR District Office Code 534 Fraud Remittance</data><data key="node_domain">Title XVI / debt</data><data key="node_description">Credit indicator for FI fraud-remittance partial returns posted to OPRR.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E017"><data key="node_entity_id">R112_E017</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS ROAR Remittance Exception RRRE Screen</data><data key="node_acronym">RRRE</data><data key="node_domain">Title II / debt</data><data key="node_description">DMS transaction screen applying financial-institution returned credits to the non-entitled debtor overpayment.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E018"><data key="node_entity_id">R112_E018</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">ROAR Direct-Deposit-Fraud 90-Day Diary</data><data key="node_domain">Title II / debt</data><data key="node_description">A 90-day DMS diary for fraud-related nonentitled-debtor overpayment pending recovery/credit resolution.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E019"><data key="node_entity_id">R112_E019</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSR B4 Diary for Excess Fraud-Remittance Decision</data><data key="node_domain">Title XVI / debt</data><data key="node_description">Title XVI B4 diary from Treasury remittance after NT TAC writeoff, requiring resolution by technician.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E020"><data key="node_entity_id">R112_E020</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">SSI NT Transaction Accounting Code for Erroneous Overpayment Decision</data><data key="node_acronym">NT TAC</data><data key="node_domain">Title XVI / debt</data><data key="node_description">SSI code to terminate overpayment collection when replacement payment followed unauthorized redirection.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E021"><data key="node_entity_id">R112_E021</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ROAR Fraud-Related Nonentitled Debtor X Subscript</data><data key="node_domain">Title II / debt</data><data key="node_description">Nonentitled debtor identified with BIC subscript X for fraud-related redirected benefit replacement.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E022"><data key="node_entity_id">R112_E022</data><data key="node_entity_type">status_code</data><data key="node_canonical_name">ROAR Listing Code 119 Alleged Direct Deposit Fraud</data><data key="node_domain">Title II / debt</data><data key="node_description">Fraud case listing used after maturing 90-day diary to terminate collection when no further credit/guidance.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E023"><data key="node_entity_id">R112_E023</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Direct Deposit Request Denial and Nonretention Process</data><data key="node_domain">identity / payments</data><data key="node_description">Checks identity, account title and FI eligibility; may deny and return incomplete SF-1199A without retaining denied request evidence.</data><data key="node_observed_status">policy documented July 2018; applicability observed 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E024"><data key="node_entity_id">R112_E024</data><data key="node_entity_type">form</data><data key="node_canonical_name">SF-1199A Direct Deposit Sign-Up Form</data><data key="node_domain">payments / enrollment</data><data key="node_description">Standard-form deposit signup returned when misdirected, incomplete or invalid, subject to phone resolution.</data><data key="node_observed_status">policy documented July 2018; applicability observed 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E025"><data key="node_entity_id">R112_E025</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L1199 Direct Deposit Request Denial Return Cover Letter</data><data key="node_domain">payments / enrollment</data><data key="node_description">Cover letter used for return of SF-1199A when account title invalid.</data><data key="node_observed_status">policy documented July 2018; applicability observed 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E026"><data key="node_entity_id">R112_E026</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Switzerland Title II International Direct Deposit Dual-Entry Process</data><data key="node_domain">international payments / address</data><data key="node_description">Technicians enter Swiss account information in SSA payment systems and ITS.gov on the same day, with required validation.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E027"><data key="node_entity_id">R112_E027</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Switzerland IDD RTN/DAN Country Encoding</data><data key="node_domain">international payments</data><data key="node_description">SSA Switzerland country prefix in RTN and DAN derived from Swiss IBAN before MBR posting.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E028"><data key="node_entity_id">R112_E028</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Swiss IBAN Submitted by Beneficiary</data><data key="node_domain">international payments / provenance</data><data key="node_description">IBAN originates at financial institution and is supplied by beneficiary for Swiss IDD transaction verification and coding.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E029"><data key="node_entity_id">R112_E029</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">MBR PCOC 8 Foreign Address IDD Eligibility Condition</data><data key="node_domain">Title II / address provenance</data><data key="node_description">Existing MBR address must be foreign for acceptance of qualifying Switzerland IDD information.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E030"><data key="node_entity_id">R112_E030</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Claim Adjudication Identity and Contact-Attribute Review</data><data key="node_domain">person / claims</data><data key="node_description">Adjudicators verify identity, current name/address/direct-deposit/telephone data and resolve conflicting evidence before entitlement determination.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E031"><data key="node_entity_id">R112_E031</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">MCS RPOC Transmitted Contact Entry Lock</data><data key="node_domain">Title II / evidence</data><data key="node_description">After transmission, MCS RPOC entry is locked for amendment and can contain five total screens per claimant segment.</data><data key="node_observed_status">documented operational 2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E032"><data key="node_entity_id">R112_E032</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 OACT Long-Range Disability Assumptions Memorandum</data><data key="node_domain">OACT / publication</data><data key="node_description">June 9 2026 actuarial memo documenting DI incidence, death-termination and recovery assumptions across three projection scenarios.</data><data key="node_observed_status">published 2026-06-09</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E033"><data key="node_entity_id">R112_E033</data><data key="node_entity_type">actuarial_assumption</data><data key="node_canonical_name">2026 DI Disabled-Worker Recovery Rate Assumptions</data><data key="node_domain">OACT / disability</data><data key="node_description">Long-range DI recovery assumptions by age and sex, increased relative to 2025 assumptions partly due to electronic third-party payroll match expectations.</data><data key="node_observed_status">2026 projection assumption</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E034"><data key="node_entity_id">R112_E034</data><data key="node_entity_type">actuarial_assumption</data><data key="node_canonical_name">2026 DI Disabled-Worker Death Termination Improvement Assumptions</data><data key="node_domain">OACT / disability</data><data key="node_description">Age/sex disability mortality improvements informed by general population improvement factors and actual 2025 disabled-worker mortality.</data><data key="node_observed_status">2026 projection assumption</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E035"><data key="node_entity_id">R112_E035</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 DI Disabled-Worker Prevalence Projection</data><data key="node_domain">OACT / disability</data><data key="node_description">Long-run modeled disabled-worker prevalence, derived from incidence and termination/recovery assumptions.</data><data key="node_observed_status">2026 published actuarial projection</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R112_E036"><data key="node_entity_id">R112_E036</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">OACT Disability Projection Short-to-Long-Range Reconciliation</data><data key="node_domain">OACT / methods</data><data key="node_description">Long-range DI model assumption rates are reconciled to short-range projections during first 10 forecast years.</data><data key="node_observed_status">2026 method documentation</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source-bound business/technical concept; physical schema/hosting/retention not inferred.</data></node><node id="R113_E001"><data key="node_entity_id">R113_E001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">FTD SSI Eligibility Third-Party Travel Verification</data><data key="node_domain">SSI / program integrity</data><data key="node_description">Field technician verifies FTD third-party travel results with recipient before SSI entitlement or payment determination.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E002"><data key="node_entity_id">R113_E002</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">FTD Data Results Screen</data><data key="node_domain">SSI / foreign travel</data><data key="node_description">DHS/CBP foreign travel query result displayed in FTD; employees may not copy or print.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E003"><data key="node_entity_id">R113_E003</data><data key="node_entity_type">security_control</data><data key="node_canonical_name">FTD Results No-Copy No-Print Control</data><data key="node_domain">SSI / DHS data handling</data><data key="node_description">SSA prohibits employees from copying/printing foreign-travel data results and directs public requests to CBP.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E004"><data key="node_entity_id">R113_E004</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">CCE SSI Claims Actions Page</data><data key="node_domain">SSI / claims</data><data key="node_description">CCE SSI Claims Actions page exposes FTD direct-query feature.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E005"><data key="node_entity_id">R113_E005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">FTD SSI Citizen Redetermination Expansion</data><data key="node_domain">SSI / redetermination</data><data key="node_description">As of January 2 2026, FTD query permitted for U.S. citizen SSI RZ cases under specified conditions.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E006"><data key="node_entity_id">R113_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">FTD SSI Initial-Claim Payment Development</data><data key="node_domain">SSI / claims</data><data key="node_description">FTD available during SSI initial claims and specified payment development for noncitizens and selected citizens as of Jan 2 2026.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E007"><data key="node_entity_id">R113_E007</data><data key="node_entity_type">scope_control</data><data key="node_canonical_name">FTD RSDI Availability Exclusion</data><data key="node_domain">Title II / architecture status</data><data key="node_description">December 2025 POMS says FTD not yet available in RSDI claims; future release planned, not deployed.</data><data key="node_observed_status">not yet available for RSDI as documented December 2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E008"><data key="node_entity_id">R113_E008</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">FTD DHS Travel Result Third-Party Report</data><data key="node_domain">program integrity / travel</data><data key="node_description">ADIS-derived entry/exit facts in FTD are investigative leads needing verification, not conclusive eligibility data.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E009"><data key="node_entity_id">R113_E009</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Multi-Beneficiary Representative Payee Termination Workflow</data><data key="node_domain">representative payee</data><data key="node_description">SSA coordinates closing of an organizational or individual payee serving multiple beneficiaries; directs a new selection or direct payment.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E010"><data key="node_entity_id">R113_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Representative Payee Closure Quick Response Check</data><data key="node_domain">representative payee / program integrity</data><data key="node_description">FO and RO decide whether rapid site review warranted for terminating multi-beneficiary representative payee.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E011"><data key="node_entity_id">R113_E011</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS List of Active Beneficiaries Screen</data><data key="node_domain">representative payee</data><data key="node_description">eRPS listing identifies currently appointed beneficiaries for a payee; reviewed before organizational termination.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E012"><data key="node_entity_id">R113_E012</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Terminated Beneficiaries List Screen</data><data key="node_domain">representative payee</data><data key="node_description">eRPS terminated beneficiary list used during post-death overpayment and payee cessation assessment.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E013"><data key="node_entity_id">R113_E013</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Terminate Organization/Institution Screen</data><data key="node_domain">representative payee</data><data key="node_description">Management terminates organizational payee in eRPS after beneficiary payment-record transitions.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E014"><data key="node_entity_id">R113_E014</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Fee for Service Screen</data><data key="node_domain">representative payee</data><data key="node_description">Closing fee-for-service payee records stop date and stopped reason on Fee for Service screen before eRPS termination.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E015"><data key="node_entity_id">R113_E015</data><data key="node_entity_type">address_data</data><data key="node_canonical_name">Closing Payee Last-Known Beneficiary Residence Address</data><data key="node_domain">representative payee / address provenance</data><data key="node_description">Closing payee supplies name, current/last known residence address, and telephone number for each beneficiary; case development data, not independent SSR/MBR update.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Observation 2026-10-07; source is current SSA POMS updated 2024; payee-supplied address requires follow-up; no automatic MBR/SSR update established.</data></node><node id="R113_E016"><data key="node_entity_id">R113_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">eRPS Closing Payee Beneficiary List Reconciliation</data><data key="node_domain">representative payee</data><data key="node_description">Staff compare eRPS active roster with departing payee supplied roster and resolve mismatches.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E017"><data key="node_entity_id">R113_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Payee Final Accounting Automated Selection</data><data key="node_domain">Title II / representative payee</data><data key="node_description">Specific criteria automatically select former Title II payees for final accounting following termination.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E018"><data key="node_entity_id">R113_E018</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI and Concurrent Payee Final Accounting Manual Selection</data><data key="node_domain">Title XVI / representative payee</data><data key="node_description">For applicable Title XVI and concurrent cases, FO manually identifies terminated payees for final accounting, including 12-month-or-shorter service rule.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E019"><data key="node_entity_id">R113_E019</data><data key="node_entity_type">financial_record</data><data key="node_canonical_name">Representative Payee Collective Account Beneficiary Ledger</data><data key="node_domain">representative payee</data><data key="node_description">Closing payee holding collective funds must furnish per-beneficiary balance ledger for allocation of conserved funds.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E020"><data key="node_entity_id">R113_E020</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Terminated Payee Conserved Funds Return and Reissuance Workflow</data><data key="node_domain">payments / representative payee</data><data key="node_description">Former payee returns conserved funds belonging to living beneficiaries to SSA for recertification/reissuance to new payee or beneficiary, generally within 30 days.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E021"><data key="node_entity_id">R113_E021</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eRPS Former Payee Death-Overpayment Indicator</data><data key="node_domain">debt / representative payee</data><data key="node_description">eRPS terminated-list death overpayment indicator used for notice and debtor handling after beneficiary death.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E022"><data key="node_entity_id">R113_E022</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">Former-New Payee Identity and Address Disclosure Restriction</data><data key="node_domain">representative payee / identity</data><data key="node_description">SSA limits disclosure between former and successor payees of each other’s identity and address without required consent.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E023"><data key="node_entity_id">R113_E023</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA-DHS Alien Identity and Location Disclosure Process</data><data key="node_domain">external exchanges / legal disclosure</data><data key="node_description">SSA via OPD evaluates DHS request to identify and locate aliens and may supply SSN, contact or selected banking and IP data within governing authority.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E024"><data key="node_entity_id">R113_E024</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">DHS Alien Locator Disclosure Data Elements</data><data key="node_domain">person / address provenance</data><data key="node_description">Subject to legally permitted request, SSA may disclose SSN, address, phone, bank routing/account, email and IP address to DHS; identifies disclosable fields, not authoritative source or database.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">2025 policy lists categories subject to lawful purpose; address is a disclosed attribute whose originating SSA system is unspecified in policy. No DHS update of SSA address inferred.</data></node><node id="R113_E025"><data key="node_entity_id">R113_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DHS Written Identity-Locator Request Screening</data><data key="node_domain">external exchanges / privacy</data><data key="node_description">OPD routes written DHS requests with sufficient identity attributes and legal purpose to determine appropriate SSA disclosure.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E026"><data key="node_entity_id">R113_E026</data><data key="node_entity_type">external_data_exchange</data><data key="node_canonical_name">SSA-to-DHS Nonwork SSN Earnings Annual Electronic Disclosure</data><data key="node_domain">IRS / SSA / DHS</data><data key="node_description">Annual electronic disclosure of post-1997 earnings on alien nonwork-issued SSNs; identifies alien and reporter name/address and earnings amount.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E027"><data key="node_entity_id">R113_E027</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Nonwork SSN Employer and Alien Address Disclosure Attributes</data><data key="node_domain">earnings / address provenance</data><data key="node_description">Post-1997 permitted DHS disclosures include alien name/address, reporter name/address and amount of posted earnings.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Only legally authorized outbound disclosure; does not establish what record supplies addresses, how recent or verified they are, or any update to source records.</data></node><node id="R113_E028"><data key="node_entity_id">R113_E028</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">Pre-1997 Nonwork SSN Earnings Disclosure Restriction</data><data key="node_domain">IRS return information</data><data key="node_description">POMS says IRC limits DHS disclosure of pre-1997 nonwork SSN earnings; exceptional SSA-initiated route handled by OPD.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E029"><data key="node_entity_id">R113_E029</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">DHS EDCOR and DECOR Non-Disclosure Boundary</data><data key="node_domain">earnings / information sharing</data><data key="node_description">SSA does not tell DHS about W-2 suspense file or whether employer got EDCOR/DECOR no-match letters; policy notes DECOR letters suspended.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E030"><data key="node_entity_id">R113_E030</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-7050-F4 Request for Social Security Earnings Information</data><data key="node_domain">earnings / third-party consent</data><data key="node_description">Form to request and authorize release of tax-return-protected detailed earnings information, including program/nonprogram fee rules.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E031"><data key="node_entity_id">R113_E031</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA-3288 Wet Signature Disclosure Route</data><data key="node_domain">privacy / records disclosure</data><data key="node_description">Paper/fillable SSA-3288 requires handwritten wet signature; may be delivered by approved means, with witness rules for mark X.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E032"><data key="node_entity_id">R113_E032</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">Separate Federal Tax and Non-Tax Consent Requirement</data><data key="node_domain">IRS return information</data><data key="node_description">SSA cannot use a single combined authorization for federal tax return and non-tax records; separate consents required.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E033"><data key="node_entity_id">R113_E033</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">SSA Tax Information Consent 120-Day Receipt Window</data><data key="node_domain">IRS return information</data><data key="node_description">Valid tax information consent must reach SSA within 120 days of signature, with earliest SSA receipt date used.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E034"><data key="node_entity_id">R113_E034</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">SSA Medical Record Consent 90-Day Receipt Window</data><data key="node_domain">medical evidence / disclosures</data><data key="node_description">Written medical information consent must be received within 90 days of signed date, with policy exception for nonmedical-only release.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E035"><data key="node_entity_id">R113_E035</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">SSA General Records Consent One-Year Receipt Window</data><data key="node_domain">privacy / disclosure</data><data key="node_description">Valid non-medical non-tax consent must reach SSA within one year from signing.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E036"><data key="node_entity_id">R113_E036</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">SSA Privacy Consent Signature and Electronic Exception Rule</data><data key="node_domain">privacy / electronic signature</data><data key="node_description">SSA ordinarily requires wet signature on paper; SSA-3288-OP1 supports electronic signature, other methods need Office of General Counsel approval.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E037"><data key="node_entity_id">R113_E037</data><data key="node_entity_type">address_data</data><data key="node_canonical_name">SSA-3288 Disclosure Recipient Postal Address Attribute</data><data key="node_domain">consent / address provenance</data><data key="node_description">Consent specifies address of third-party recipient to whom records should be sent; consenting individual address need not be supplied.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Recipient delivery address is NOT a beneficiary residence address. 2025 POMS explicitly says consenting individual address optional; no MBR/SSR/Numident update rule.</data></node><node id="R113_E038"><data key="node_entity_id">R113_E038</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">SSA Record Disclosure Express Consent Scope Validation</data><data key="node_domain">records disclosure</data><data key="node_description">Staff require specific records, intended recipient/purpose and one-time or prescribed disclosure timeframe; blanket all records requests unacceptable.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E039"><data key="node_entity_id">R113_E039</data><data key="node_entity_type">public_data_artifact</data><data key="node_canonical_name">Monthly Statistical Snapshot Archived HTML Tables</data><data key="node_domain">SSA statistics / publication</data><data key="node_description">Monthly HTML editions retained in archive and used to regenerate flattened machine-readable time series, including corrections.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E040"><data key="node_entity_id">R113_E040</data><data key="node_entity_type">publication_process</data><data key="node_canonical_name">Monthly Statistical Snapshot Flat-Series Regeneration Process</data><data key="node_domain">SSA statistics / publication</data><data key="node_description">Monthly regeneration of JSON/CSV flattened files from full archived HTML tables, incorporating any post-publication corrections.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E041"><data key="node_entity_id">R113_E041</data><data key="node_entity_type">data_schema</data><data key="node_canonical_name">Monthly Statistical Snapshot Beta JSON Schema and Variable Metadata</data><data key="node_domain">SSA statistics / open data</data><data key="node_description">JSON files carry measures and dimension IDs, variable names, relationships, units, source and footnote metadata; beta identifiers may change.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E042"><data key="node_entity_id">R113_E042</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot Table 1 Flat-Series JSON</data><data key="node_domain">SSA statistics / open data</data><data key="node_description">Published monthly flattened JSON time-series file for Table 1 (Social Security and SSI Concurrent Recipient Counts), regenerated from archived HTML editions.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E043"><data key="node_entity_id">R113_E043</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot Table 1 Flat-Series CSV</data><data key="node_domain">SSA statistics / open data</data><data key="node_description">Published monthly flattened CSV time-series file for Table 1 (Social Security and SSI Concurrent Recipient Counts), regenerated from archived HTML editions.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E044"><data key="node_entity_id">R113_E044</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot Table 2 Flat-Series JSON</data><data key="node_domain">SSA statistics / open data</data><data key="node_description">Published monthly flattened JSON time-series file for Table 2 (Social Security Benefit Measures), regenerated from archived HTML editions.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E045"><data key="node_entity_id">R113_E045</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot Table 2 Flat-Series CSV</data><data key="node_domain">SSA statistics / open data</data><data key="node_description">Published monthly flattened CSV time-series file for Table 2 (Social Security Benefit Measures), regenerated from archived HTML editions.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E046"><data key="node_entity_id">R113_E046</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot Table 3 Flat-Series JSON</data><data key="node_domain">SSA statistics / open data</data><data key="node_description">Published monthly flattened JSON time-series file for Table 3 (SSI Recipient Measures), regenerated from archived HTML editions.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E047"><data key="node_entity_id">R113_E047</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot Table 3 Flat-Series CSV</data><data key="node_domain">SSA statistics / open data</data><data key="node_description">Published monthly flattened CSV time-series file for Table 3 (SSI Recipient Measures), regenerated from archived HTML editions.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R113_E048"><data key="node_entity_id">R113_E048</data><data key="node_entity_type">business_role</data><data key="node_canonical_name">SSA Contracting Officer Technical Representative Market Research Role</data><data key="node_domain">procurement / OAG</data><data key="node_description">SSA acquisition page says its vendor repository/database was intended to support COTR market research.</data><data key="node_observed_status">historical official acquisition description; current office staffing/system status not established</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Undated SSA OAG page contains historic SAM transition language. This supports existence of published market-research role, not present-day repository deployment or contract technology.</data></node><node id="R113_E049"><data key="node_entity_id">R113_E049</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3288 Consent for Release of Information Form</data><data key="node_domain">privacy / person disclosure</data><data key="node_description">SSA preferred paper/fillable release-of-information consent document for non-tax return records requiring wet signature.</data><data key="node_observed_status">documented policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Documented logical data/workflow element; no physical hosting, interface protocol, DBMS or retention inferred.</data></node><node id="R114_E001"><data key="node_entity_id">R114_E001</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">IRS Return Transaction File</data><data key="node_acronym">RTF</data><data key="node_domain">IRS / Medicare / Tax Return Information</data><data key="node_description">IRS Return Transaction File holds MAGI extracts for Medicare IRMAA matching; the CMA describes it as part of CADE IMF.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">The CMA does not document the storage technology, file layout or transport implementation.</data></node><node id="R114_E002"><data key="node_entity_id">R114_E002</data><data key="node_entity_type">external_data_system</data><data key="node_canonical_name">IRS Customer Account Data Engine Individual Master File Environment</data><data key="node_acronym">CADE IMF</data><data key="node_domain">IRS / Individual Tax Identity</data><data key="node_description">The IRS RTF that supplies MAGI is part of the Customer Account Data Engine Individual Master File, Treasury/IRS 24.030.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">This models an IRS environment and does not claim the SSA master identity record is in CADE.</data></node><node id="R114_E003"><data key="node_entity_id">R114_E003</data><data key="node_entity_type">exchange_data</data><data key="node_canonical_name">IRS IRMAA Return Transaction MAGI Response Data</data><data key="node_domain">Medicare / IRMAA / IRS Financial Data</data><data key="node_description">IRS delivers adjusted gross income, tax-exempt income, tax year and filing status when MAGI exceeds the matching threshold.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">No mailing or residence address is among CMA 1310 specified exchange elements.</data></node><node id="R114_E004"><data key="node_entity_id">R114_E004</data><data key="node_entity_type">exchange_file</data><data key="node_canonical_name">IRMAA Weekly IRS MAGI Request File</data><data key="node_domain">Medicare / IRMAA / IRS Data Exchange</data><data key="node_description">Weekly SSA-to-IRS request includes SSN, name, premium year, threshold and conditional more-recent tax-year indicator.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">51 weekly requests plus an October combined annual exchange are documented. Exact physical format unspecified.</data></node><node id="R114_E005"><data key="node_entity_id">R114_E005</data><data key="node_entity_type">exchange_file</data><data key="node_canonical_name">IRMAA October Annual IRS MAGI Request File</data><data key="node_domain">Medicare / IRMAA / IRS Data Exchange</data><data key="node_description">October annual SSA request covers Part B/Part D enrollees and requested years; contains name, SSN, premium year and threshold information.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E006"><data key="node_entity_id">R114_E006</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">IRMAA Premium Year Tax-Year Fallback Rule</data><data key="node_domain">Medicare / IRMAA / Eligibility Rules</data><data key="node_description">IRS generally extracts PY-2 MAGI; uses PY-3 where PY-2 data unavailable by October 16 preceding the premium year.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E007"><data key="node_entity_id">R114_E007</data><data key="node_entity_type">retention_control</data><data key="node_canonical_name">IRS Matching Input File 90-Day Transitory Retention Control</data><data key="node_domain">IRS / Computer Matching / Retention</data><data key="node_description">IRS retains SSA electronic matching requests about 90 days and destroys them after matching purpose; GRS 5.2 item 010 transitory records.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Applies to described IRS receiving side and particular agreements, not blanket retention for all SSA data.</data></node><node id="R114_E008"><data key="node_entity_id">R114_E008</data><data key="node_entity_type">exchange_file</data><data key="node_canonical_name">Medicare Part D LIS Weekly IRS Unearned-Income Finder File</data><data key="node_domain">Medicare Part D / Low Income Subsidy</data><data key="node_description">SSA sends weekly name/SSN and name-control identifiers for LIS applicants who require additional IRS unearned-income verification.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E009"><data key="node_entity_id">R114_E009</data><data key="node_entity_type">exchange_file</data><data key="node_canonical_name">Medicare Part D LIS Annual IRS Unearned-Income Finder File</data><data key="node_domain">Medicare Part D / Low Income Subsidy</data><data key="node_description">SSA annually submits current LIS recipients for unearned-income IRMF verification, with at least 30 days advance notification to IRS.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E010"><data key="node_entity_id">R114_E010</data><data key="node_entity_type">exchange_data</data><data key="node_canonical_name">Medicare Part D LIS IRS Unearned-Income Response Data</data><data key="node_domain">Medicare Part D / IRS Financial Data</data><data key="node_description">IRS IRMF response to LIS includes payee account, payee and payer names/addresses, TINs, type and amount of income.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E011"><data key="node_entity_id">R114_E011</data><data key="node_entity_type">address_attribute</data><data key="node_canonical_name">IRS LIS Match Payee Mailing Address Attribute</data><data key="node_domain">Medicare Part D / Address Provenance</data><data key="node_description">Payee mailing address in IRS IRMF unearned-income response under LIS matching, distinct from a verified program contact address.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">No explicit current-beneficiary address update rule documented; whether the address component persists in MDB is not established.</data></node><node id="R114_E012"><data key="node_entity_id">R114_E012</data><data key="node_entity_type">address_attribute</data><data key="node_canonical_name">IRS LIS Match Payer Address Attribute</data><data key="node_domain">Medicare Part D / Third Party Provenance</data><data key="node_description">Payer name/address supplied as information-return source attributes for LIS unearned income matching.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Payer address is not necessarily the beneficiary residence.</data></node><node id="R114_E013"><data key="node_entity_id">R114_E013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Medicare Part D LIS IRS Match Independent-Verification Process</data><data key="node_domain">Medicare Part D / Eligibility Integrity</data><data key="node_description">SSA must independently verify IRS unearned-income findings and provide written pre-decision contest rights before adverse LIS action.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E014"><data key="node_entity_id">R114_E014</data><data key="node_entity_type">compliance_report</data><data key="node_canonical_name">SSA IRS Tax Information Safeguard Security Report</data><data key="node_acronym">SSR</data><data key="node_domain">Data Governance / Federal Tax Information</data><data key="node_description">SSA must submit and certify its annual FTI Safeguard Security Report by January 31, describing controls, environments and outstanding actions.</data><data key="node_observed_status">governance_required</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">SSR here means Safeguard Security Report, not Supplemental Security Record.</data></node><node id="R114_E015"><data key="node_entity_id">R114_E015</data><data key="node_entity_type">retention_control</data><data key="node_canonical_name">DIFSLA IRS Finder-File Disposition Control</data><data key="node_domain">Title XVI / IRS / Matching Records</data><data key="node_description">IRS stores SSA matching finder/tickler identifiers approximately 90 days as transitory files; SSA must destroy match files when purpose and legal retention are met.</data><data key="node_observed_status">governance_required</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E016"><data key="node_entity_id">R114_E016</data><data key="node_entity_type">finance_process</data><data key="node_canonical_name">DIFSLA IRS Reimbursable Matching Billing Workflow</data><data key="node_domain">Finance / Interagency / IRS</data><data key="node_description">IRS bills SSA at least monthly for DIFSLA matching via Treasury G-Invoicing, generating an IPAC collection document.</data><data key="node_observed_status">governance_required</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E017"><data key="node_entity_id">R114_E017</data><data key="node_entity_type">federal_finance_document</data><data key="node_canonical_name">FS 7600A and FS 7600B Interagency Agreement Forms</data><data key="node_domain">Finance / Interagency Agreements</data><data key="node_description">Fiscal Service 7600A and 7600B documents specify cost reimbursable terms for IRS DIFSLA matching.</data><data key="node_observed_status">governance_required</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E018"><data key="node_entity_id">R114_E018</data><data key="node_entity_type">external_data_record</data><data key="node_canonical_name">Fiscal Service Definitive Savings Securities Record Set</data><data key="node_domain">Treasury / Savings Securities</data><data key="node_description">Treasury records for engraved or printed paper U.S. savings bonds used in Extra Help ownership verification.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E019"><data key="node_entity_id">R114_E019</data><data key="node_entity_type">external_data_record</data><data key="node_canonical_name">Fiscal Service Book-Entry Savings Securities Record Set</data><data key="node_domain">Treasury / Savings Securities</data><data key="node_description">Treasury or bank electronic book-entry savings security ownership records queried by matched SSN for Medicare Extra Help.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E020"><data key="node_entity_id">R114_E020</data><data key="node_entity_type">exchange_file</data><data key="node_canonical_name">Medicare Extra Help Fiscal Service Savings Securities Finder File</data><data key="node_domain">Medicare Part D / Savings Securities</data><data key="node_description">SSA sends MDB-derived SSN/name identifier finder files to Fiscal Service for savings securities verification.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E021"><data key="node_entity_id">R114_E021</data><data key="node_entity_type">exchange_file</data><data key="node_canonical_name">Medicare Extra Help Savings Securities Match Response File</data><data key="node_domain">Medicare Part D / Savings Securities</data><data key="node_description">Fiscal Service returns definitive or book-entry holdings with security values and dates, or no-match indicator, within five business days.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E022"><data key="node_entity_id">R114_E022</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Medicare Extra Help Savings Security Ownership Alert</data><data key="node_domain">Medicare Part D / Verification</data><data key="node_description">Savings-security alerts require verification before adverse Extra Help action or release of ownership evidence.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E023"><data key="node_entity_id">R114_E023</data><data key="node_entity_type">external_system_of_records</data><data key="node_canonical_name">Fiscal Service United States Securities and Access Records</data><data key="node_domain">Treasury / Securities Identity</data><data key="node_description">Fiscal Service record system .014 United States Securities and Access used to match SSA Medicare Extra Help requests.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E024"><data key="node_entity_id">R114_E024</data><data key="node_entity_type">authorization_process</data><data key="node_canonical_name">Extra Help Savings Securities Ownership Verification Authorization</data><data key="node_domain">Medicare Part D / Evidence Verification</data><data key="node_description">Contested Treasury savings ownership requires applicant signed authorization; SSA routes requests via Minneapolis field office.</data><data key="node_observed_status">documented_in_current_CMA</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E025"><data key="node_entity_id">R114_E025</data><data key="node_entity_type">administrative_process</data><data key="node_canonical_name">SSA Vendor Direct Deposit Maintenance Process</data><data key="node_domain">Finance / Vendor Payments</data><data key="node_description">Current SSA vendor site states SAM financial details automatically update SSA vendor database; non-SAM vendors submit signed SF3881.</data><data key="node_observed_status">documented_in_public_vendor_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E026"><data key="node_entity_id">R114_E026</data><data key="node_entity_type">administrative_data</data><data key="node_canonical_name">SSA Administrative Vendor Payment History</data><data key="node_domain">Finance / Vendor Payments</data><data key="node_description">Purchase order, invoice number, paid amount, dates, interest, penalties and discounts available through Treasury IPP to enrolled vendor only.</data><data key="node_observed_status">documented_in_current_public_service</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E027"><data key="node_entity_id">R114_E027</data><data key="node_entity_type">payment_notification</data><data key="node_canonical_name">Treasury IPP Vendor Payment Remittance Notification</data><data key="node_domain">Finance / Vendor Payments</data><data key="node_description">Treasury IPP vendor-selected email payment notification or detailed remittance information.</data><data key="node_observed_status">documented_in_current_public_service</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E028"><data key="node_entity_id">R114_E028</data><data key="node_entity_type">published_actuarial_dataset</data><data key="node_canonical_name">OACT 2026 Solvency Taxation Proposal Detailed Single-Year Tables</data><data key="node_domain">OACT / Taxation of Benefits / Policy Options</data><data key="node_description">OACT tables show year-by-year projected cost, income, annual balance, and trust fund ratio impacts under hypothetical benefit-tax options, using 2026 Trustees intermediate assumptions.</data><data key="node_observed_status">published_2026_basis</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E029"><data key="node_entity_id">R114_E029</data><data key="node_entity_type">published_actuarial_product</data><data key="node_canonical_name">OACT 2026 Solvency Taxation Proposal Summary and Graphs</data><data key="node_domain">OACT / Taxation of Benefits / Policy Options</data><data key="node_description">OACT publishes summary measures and graphs comparing hypothetical tax-benefit provisions with current law, based on 2026 Trustees intermediate assumptions.</data><data key="node_observed_status">published_2026_basis</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E030"><data key="node_entity_id">R114_E030</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Open Data Annual Deaths While Awaiting ALJ Determination CSV</data><data key="node_domain">Hearings / OACT / Administrative Research</data><data key="node_description">SSA 2018 historical CSV for FY2006–2017 claimant deaths among cases pending ALJ determination, derived from CPMS cases matched to Numident death indicators.</data><data key="node_observed_status">historical_data_file</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Released 2018 (within ten-year source window), underlying series includes pre-2016 years; not proof of current death-alert service.</data></node><node id="R114_E031"><data key="node_entity_id">R114_E031</data><data key="node_entity_type">historical_analytical_process</data><data key="node_canonical_name">OACT CPMS-to-Numident Pending-Hearing Death Research Match</data><data key="node_domain">Hearings / OACT / Identity Death Research</data><data key="node_description">2018 OACT analytical process joins claimant cases pending ALJ decision in CPMS to recorded Numident deaths for public statistics.</data><data key="node_observed_status">historical_2018</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E032"><data key="node_entity_id">R114_E032</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">RSI Internet Receipts and Completions Monthly CSV FY2016 Onward</data><data key="node_domain">Operations / Title II / Open Data</data><data key="node_description">Public monthly aggregate counts by filing channel for retirement/survivor/initial Medicare applications for fiscal years 2016 onward, updated July 10 2026.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E033"><data key="node_entity_id">R114_E033</data><data key="node_entity_type">documented_batch_process</data><data key="node_canonical_name">RSI Claims Operational Data Nightly Aggregation Pipeline</data><data key="node_domain">Operations / Title II / Reporting</data><data key="node_description">SSA extracts MCS claim information nightly to Title II ODS and uses batch processes to aggregate claim receipts and clearances for monthly national publication.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E034"><data key="node_entity_id">R114_E034</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">RSI Quarterly Spoken-Language Preference Public CSV FY2023 Onward</data><data key="node_domain">Customer Service / Language Access / Open Data</data><data key="node_description">Quarterly FY2023 onward national CSV for spoken-language preferences of Title II retirement/survivor claimants, updated March 31 2026.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E035"><data key="node_entity_id">R114_E035</data><data key="node_entity_type">identity_service_rule</data><data key="node_canonical_name">EBE SSN Card Mailing Address Confirmation and Replacement Rule</data><data key="node_domain">Enumeration / Address Provenance</data><data key="node_description">When Numident shows an EBE record under 7 business days old, technicians confirm mailing address; changed address or older cycle date triggers replacement card application with evidence.</data><data key="node_observed_status">historical_2024_guidance</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E036"><data key="node_entity_id">R114_E036</data><data key="node_entity_type">temporary_authentication_data</data><data key="node_canonical_name">iRPA Paper Report Access Identifier Set</data><data key="node_domain">Representative Payee / Online Accounting</data><data key="node_description">iRPA requires beneficiary SSN, type of account, beneficiary identification code, and mailed-form ID from current report request.</data><data key="node_observed_status">documented_2025</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R114_E037"><data key="node_entity_id">R114_E037</data><data key="node_entity_type">temporary_confirmation_record</data><data key="node_canonical_name">Internet Representative Payee Report Confirmation Receipt</data><data key="node_domain">Representative Payee / Digital Intake</data><data key="node_description">Online payee accounting portal generates a report confirmation and says stored for viewing for 30 days.</data><data key="node_observed_status">documented_public_page</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Page displays expired 2020 OMB form-control date; current UI and actual record retention need validation.</data></node><node id="R114_E038"><data key="node_entity_id">R114_E038</data><data key="node_entity_type">adjudication_rule</data><data key="node_canonical_name">IRMAA Highest Probative Tax Evidence Selection Rule</data><data key="node_domain">Medicare / IRMAA / Evidence</data><data key="node_description">On PYTY screen, IRS or other tax data already on file may control under highest-probative-value selection; beneficiary new tax year evidence can be considered when it has higher value.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R115_E001"><data key="node_entity_id">R115_E001</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">2026 OACT Long-Range Demography Process</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Logical demographic forecast process in 2026 OASDI Trustees model; projections for 2026-2100 feed economics, beneficiaries, and actuarial status. Not a claim about software deployment or DBMS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes">Process names from publicly indexed 2026 model document excerpt; high-level population method independently corroborated by Section V.A.</data></node><node id="R115_E002"><data key="node_entity_id">R115_E002</data><data key="node_entity_type">actuarial_subprocess</data><data key="node_canonical_name">2026 OACT Demography Historical Social Security Area Population Subprocess</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Estimates historical Social Security area total and civilian noninstitutionalized populations by age, sex and marital status.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes">Model computational subprocess rather than SSA operational program record or a separately deployed application.</data></node><node id="R115_E003"><data key="node_entity_id">R115_E003</data><data key="node_entity_type">actuarial_subprocess</data><data key="node_canonical_name">2026 OACT Demography Lawful Permanent Resident Immigration Subprocess</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Projects LPR immigrants, eligible emigrants and adjustments from temporary/unlawful status to permanent residence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes">Model computational subprocess rather than SSA operational program record or a separately deployed application.</data></node><node id="R115_E004"><data key="node_entity_id">R115_E004</data><data key="node_entity_type">actuarial_subprocess</data><data key="node_canonical_name">2026 OACT Demography Temporary or Unlawfully Present Immigration Subprocess</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Estimates net flows and populations by demographic category and status, including nonimmigrants and visa overstayers.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes">Model computational subprocess rather than SSA operational program record or a separately deployed application.</data></node><node id="R115_E005"><data key="node_entity_id">R115_E005</data><data key="node_entity_type">actuarial_subprocess</data><data key="node_canonical_name">2026 OACT Demography Marriage Subprocess</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Projects cross-age marriage rates by age of partners to support marital-status population classification.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes">Model computational subprocess rather than SSA operational program record or a separately deployed application.</data></node><node id="R115_E006"><data key="node_entity_id">R115_E006</data><data key="node_entity_type">actuarial_subprocess</data><data key="node_canonical_name">2026 OACT Demography Divorce Subprocess</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Projects divorce rates by age of partners for marital-status population transitions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes">Model computational subprocess rather than SSA operational program record or a separately deployed application.</data></node><node id="R115_E007"><data key="node_entity_id">R115_E007</data><data key="node_entity_type">actuarial_subprocess</data><data key="node_canonical_name">2026 OACT Demography Projected Social Security Area Population Subprocess</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Combines estimated starting stock with births, deaths, immigration, marriage and divorce assumptions to forecast population by age, sex and marital status.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes">Model computational subprocess rather than SSA operational program record or a separately deployed application.</data></node><node id="R115_E008"><data key="node_entity_id">R115_E008</data><data key="node_entity_type">actuarial_model_input</data><data key="node_canonical_name">2026 OACT Social Security Area Starting Population by Age Sex and Marital Status</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Starting stock as of December 31, 2023, derived from US Census population estimates with adjustments for undercount, US territories, overseas citizens, other insured noncitizens, mortality and migration.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E009"><data key="node_entity_id">R115_E009</data><data key="node_entity_type">actuarial_model_output</data><data key="node_canonical_name">2026 OACT Projected Population by Age Sex Marital Status and Year</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Historical and forecast Social Security area population through 2100, classified by age, sex, marital status, with 2026 Trustees demographic assumption scenarios.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E010"><data key="node_entity_id">R115_E010</data><data key="node_entity_type">actuarial_model_output</data><data key="node_canonical_name">2026 OACT Civilian Noninstitutionalized Population Projections</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Model projections for civilian noninstitutionalized population, age-sex-marital classification; named as Demography process output in 2026 model documentation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes" /></node><node id="R115_E011"><data key="node_entity_id">R115_E011</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">2026 OACT Long-Range Economics Process</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Logical major analytical process named in 2026 long-range actuarial model documentation: ange Economics Process. Physical implementation and model transport are not established.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes" /></node><node id="R115_E012"><data key="node_entity_id">R115_E012</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">2026 OACT Long-Range Beneficiaries Process</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Logical major analytical process named in 2026 long-range actuarial model documentation: ange Beneficiaries Process. Physical implementation and model transport are not established.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes" /></node><node id="R115_E013"><data key="node_entity_id">R115_E013</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">2026 OACT Long-Range Trust Fund Operations and Actuarial Status Process</data><data key="node_domain">Actuarial/statistical systems</data><data key="node_description">Logical major analytical process named in 2026 long-range actuarial model documentation: ange Trust Fund Operations and Actuarial Status Process. Physical implementation and model transport are not established.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes" /></node><node id="R115_E014"><data key="node_entity_id">R115_E014</data><data key="node_entity_type">identity_validation_control</data><data key="node_canonical_name">Title II NCOA Exact-Match Candidate Gate</data><data key="node_domain">Identity / Address provenance</data><data key="node_description">SSA selects Title II NCOA cases only when name/middle initial/surname and prior SSA mailing address exactly match USPS prior address; Title XVI excluded.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E015"><data key="node_entity_id">R115_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II NCOA Conditional Automatic MBR Address Posting</data><data key="node_domain">Identity / Address provenance</data><data key="node_description">Title II Redesign automatically posts eligible NCOA addresses only for qualifying direct-deposit/certain nonpayment statuses and absent an intervening change.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E016"><data key="node_entity_id">R115_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II NCOA Beneficiary Call-In Address Verification</data><data key="node_domain">Identity / Address provenance</data><data key="node_description">Call-in notice and beneficiary or representative-payee confirmation required for check recipients, concurrent SSI, specified suspensions, new care-of, PR, and institutional cases.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E017"><data key="node_entity_id">R115_E017</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR NCOA ZIP Flag X Opt-Out</data><data key="node_domain">Identity / Address provenance</data><data key="node_description">MBR ZIP flag X denotes beneficiary request to retain old address; prevents NCOA selection during next matching cycle.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E018"><data key="node_entity_id">R115_E018</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR NCOA ZIP Flag P Posted Update</data><data key="node_domain">Identity / Address provenance</data><data key="node_description">MBR ZIP flag P denotes address changed following NCOA action; supersedes interim L on successful automatic posting.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E019"><data key="node_entity_id">R115_E019</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR NCOA ZIP Flag L Notice Pending</data><data key="node_domain">Identity / Address provenance</data><data key="node_description">MBR ZIP flag L denotes a USPS move notice mailed or verification invitation; flag can persist absent response.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E020"><data key="node_entity_id">R115_E020</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Credit Repository Monthly Debtor Update Batch</data><data key="node_domain">Payments / Debt / Address provenance</data><data key="node_description">Post-selection SSA debt reporting and monthly updates to external repositories include changed debtor addresses, repayments and protest status; eligible Title II cases only.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E021"><data key="node_entity_id">R115_E021</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title XVI Credit Repository Monthly Debtor Update Batch</data><data key="node_domain">Payments / Debt / Address provenance</data><data key="node_description">SSA updates outstanding Title XVI debt information, including changed debtor address, protest and repayments, to national credit repositories monthly.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E022"><data key="node_entity_id">R115_E022</data><data key="node_entity_type">exchange_data_artifact</data><data key="node_canonical_name">SSA Credit Repository Outbound Debtor Identity and Address Record</data><data key="node_domain">Payments / Debt / Address provenance</data><data key="node_description">Outgoing credit reporting record includes debtor name, address, SSN, DOB, debt delinquency date, last payment, and balance, under program-specific legal authority.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E023"><data key="node_entity_id">R115_E023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSA Credit Repository 60-Day Due Process Reporting Gate</data><data key="node_domain">Payments / Debt</data><data key="node_description">Reporting occurs after 60 days from notice or decision on timely review/waiver, whichever occurs later; pending waiver blocks reporting.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E024"><data key="node_entity_id">R115_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">ACDV Consumer Dispute Thirty-Day Federal Response Control</data><data key="node_domain">Program integrity / Debt</data><data key="node_description">Fair Credit Reporting Act control: if SSA fails to verify disputed debt through credit-bureau dispute process within 30 days, the bureau deletes the debt from the credit report.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E025"><data key="node_entity_id">R115_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Credit Bureau Report Removal Authorization Via NEPSC and DMS</data><data key="node_domain">Payments / Debt</data><data key="node_description">Post-report approved protest or bankruptcy discharge is referred through NEPSC/RO to authorized SSA official for credit deletion; manual escalation path, not automatic removal by ordinary SSR correction.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R115_E026"><data key="node_entity_id">R115_E026</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">ESRD Medicare Initial Claims Quarterly Spoken Language Preferences CSV</data><data key="node_acronym">LEP ESRD</data><data key="node_domain">Actuarial/statistical publication pipelines</data><data key="node_description">National quarterly spoken-language volumes for Medicare ESRD-only initial applications, FY2023 onward, federal data catalog US-GOV-SSA-2326; file updated March 31 2026.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R115_E027"><data key="node_entity_id">R115_E027</data><data key="node_entity_type">statistical_publication_process</data><data key="node_canonical_name">ESRD Medicare Initial Claim Language-Preference Aggregation</data><data key="node_domain">Enterprise data / Statistical pipelines</data><data key="node_description">SSA uses SCDD to associate SUMS claim workload counts with client demographics from SUMS client tables and the Integrated Client Database, then publishes ESRD-only quarter volumes.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R115_E028"><data key="node_entity_id">R115_E028</data><data key="node_entity_type">modernization_milestone</data><data key="node_canonical_name">2026 W-2 Online Territory Wage-Reporting Support Planned December 2026</data><data key="node_domain">Earnings / Modernization</data><data key="node_description">2026 SSA W-2 News describes new W-2/W-2C Online as domestic-only initially and anticipates territorial reporting in early December 2026; until then file upload remains an option.</data><data key="node_observed_status">planned_not_verified_deployed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Publication is 2026-01; December 2026 capability future and must not be treated as operational in October 2026.</data></node><node id="R116_E001"><data key="node_entity_id">R116_E001</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSI Tax Interface Payee Name and Mailing Address Attributes</data><data key="node_domain">Address provenance and IRS data</data><data key="node_description">Tax-interface payee is the party named and addressed on payer records, potentially someone other than the SSN holder; not a verified SSA residence or contact address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">POMS SI 02310.040 B.2, B.5. Distinguish financial payer/payee records from beneficiary master-address fields.</data></node><node id="R116_E002"><data key="node_entity_id">R116_E002</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSI Tax Interface Payer Name and Reporting Entity Attributes</data><data key="node_domain">Address provenance and IRS data</data><data key="node_description">Payer identifies the institution or organization submitting Form 1099, W-2 or similar transaction records to IRS/SSA; not beneficiary address evidence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E003"><data key="node_entity_id">R116_E003</data><data key="node_entity_type">retention_control</data><data key="node_canonical_name">SSI Tax Alert Disposition Record Retention Control</data><data key="node_domain">IRS and SSI alerts</data><data key="node_description">Keep the disposition showing payer data and development outcome until following-year alerts are completed; restrict access when maintaining an alert copy as the disposition.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E004"><data key="node_entity_id">R116_E004</data><data key="node_entity_type">retention_control</data><data key="node_canonical_name">SSI Tax Alert Destruction After Verification Control</data><data key="node_domain">IRS and SSI alerts</data><data key="node_description">Destroy tax-data alerts once information has been verified unless the alert itself is used to document case disposition; do not leave a copy in the case file as a general rule.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E005"><data key="node_entity_id">R116_E005</data><data key="node_entity_type">data_retention_observation</data><data key="node_canonical_name">SSI IRS Interface Most-Recent-Two-Tax-Years Retrieval Window</data><data key="node_domain">IRS and SSI alerts</data><data key="node_description">2017 POMS states SSI/IRS interface database holds the most recent two years of IRS data available to technicians via MI Central/SSTNG; does not establish formal backup purge cycle.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">2017 historical policy, 2026 availability unconfirmed.</data></node><node id="R116_E006"><data key="node_entity_id">R116_E006</data><data key="node_entity_type">program_integrity_process</data><data key="node_canonical_name">2026 EAB Apparent Duplicate Infant SSN Remediation Review</data><data key="node_domain">Enumeration and identity</data><data key="node_description">2026 OIG identified 420 apparent duplicate-SSN infants in 2021-2024 EAB records lacking cross-references; recommended case review, possible cross-reference and designation of extra SSNs as retired.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Recommendations accepted, not evidence all 420 cases were corrected.</data></node><node id="R116_E007"><data key="node_entity_id">R116_E007</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">EAB State Electronic Birth Registration Submission Quality Gate</data><data key="node_domain">Enumeration and identity</data><data key="node_description">State BVS submits birth-registration data on a daily or weekly schedule; SSA accepts transmitted data as received rather than modifying source state birth information.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E008"><data key="node_entity_id">R116_E008</data><data key="node_entity_type">audit_finding</data><data key="node_canonical_name">EAB Multiple-SSN Unlinked Identity Risk Observation (2026)</data><data key="node_domain">Enumeration and identity</data><data key="node_description">OIG 2026 audit found 420 apparent duplicate infant numbers in ~13.9 million EAB assignments, a rare but persistent identity-linkage exception.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E009"><data key="node_entity_id">R116_E009</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">DDS Paper Evidence Scan-Verify-Destroy Workflow</data><data key="node_domain">Disability and evidence</data><data key="node_description">Paper source documents received by DDS are locally scanned or routed to a contracted scanning service and placed into CEF; locally scanned DDS originals are destroyed after CEF accessibility is verified.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E010"><data key="node_entity_id">R116_E010</data><data key="node_entity_type">evidence_exception_workflow</data><data key="node_canonical_name">DDS Missing or Unreadable DMA Barcode Manual Indexing Exception</data><data key="node_domain">Disability and evidence</data><data key="node_description">When scanner receives unreadable/missing barcodes, evidence may return to DDS or require manual indexing after scanning to associate the source document with the correct CEF.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E011"><data key="node_entity_id">R116_E011</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">DDS Email or Compact Disc Medical Evidence Conversion Route</data><data key="node_domain">Disability and evidence</data><data key="node_description">DDS prints medical evidence received by insecure email or CD and scans it locally or via contracted scanner to the CEF, warning email senders against future insecure submissions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E012"><data key="node_entity_id">R116_E012</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">DDS Post-Closure Medical Evidence Trailer Workflow</data><data key="node_domain">Disability and evidence</data><data key="node_description">Medical evidence sent from the field office after a DDS case closes is treated as trailer material under DI 81020.140, rather than being assumed attached to an active DDS case.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E013"><data key="node_entity_id">R116_E013</data><data key="node_entity_type">contracted_service</data><data key="node_canonical_name">DDS Contracted Source-Document Scanning Service (Unnamed)</data><data key="node_domain">Disability and evidence</data><data key="node_description">POMS DI 81020.060 confirms use of contract scanning of paper disability evidence; does not identify vendor, contract, transport or hosting.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">No vendor identity inferred.</data></node><node id="R116_E014"><data key="node_entity_id">R116_E014</data><data key="node_entity_type">data_access_control</data><data key="node_canonical_name">MEGAHIT Medical Evidence Request Authorization Gate</data><data key="node_domain">Health IT and disability</data><data key="node_description">MEGAHIT issues HIE medical-record request only when participating source is listed in EDCS and signed/date-stamped SSA-827 image exists in EF.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E015"><data key="node_entity_id">R116_E015</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">MEGAHIT Per-HIE Initial Request Deduplication Control</data><data key="node_domain">Health IT and disability</data><data key="node_description">Multiple claims or multiple health-IT participating sources on one transferred case do not cause repeated initial electronic requests to the same relevant HIE.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E016"><data key="node_entity_id">R116_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MEGAHIT Health Information Exchange Response-Based Payment Rule</data><data key="node_domain">Health IT and disability</data><data key="node_description">SSA pays HIE for valid records response to initial automated request; no payment when only HIT Response/no records document appears. DDS pays for subsequent additional requests to source.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E017"><data key="node_entity_id">R116_E017</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">MEGAHIT Unanswered HIE Request No-Automatic-Retry Control</data><data key="node_domain">Health IT and disability</data><data key="node_description">If initial HIE medical-record request returns no records or no response, MEGAHIT creates HIT Response document and does not issue automatic second request.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E018"><data key="node_entity_id">R116_E018</data><data key="node_entity_type">application_workflow</data><data key="node_canonical_name">e1696 Electronic Appointment Intake via WorkTrack</data><data key="node_domain">Hearings and representation</data><data key="node_description">Electronic SSA-1696-APP image arrives to servicing field office in WorkTrack after claimant executes portal workflow; technicians process representation in RASR.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E019"><data key="node_entity_id">R116_E019</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RASR Case-Specific Representative Appointment Scope</data><data key="node_domain">Hearings and representation</data><data key="node_description">SSA-1696 Section 4 specifies which claims and issues a representative covers. Separate new claim is not automatically covered by prior Title XVI appointment.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E020"><data key="node_entity_id">R116_E020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RASR Representative Entity Affiliation and Fee-Assignment Validation</data><data key="node_domain">Hearings and representation</data><data key="node_description">An appointed representative is an individual; assignment of direct fee payment to an affiliate requires registered organization/EIN and compliant SSA-1696, separate from appointing an organization as representative.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E021"><data key="node_entity_id">R116_E021</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">RASR Default Sole Proprietor Without Fee Entity Information</data><data key="node_domain">Hearings and representation</data><data key="node_description">RASR defaults the representative to sole-proprietor/self-employed coding when SSA-1696 lacks entity information or checks No EIN.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E022"><data key="node_entity_id">R116_E022</data><data key="node_entity_type">address_attribute</data><data key="node_canonical_name">SSA-1696 Paper Signature Witness Mailing Address Attribute</data><data key="node_domain">Address provenance and IRS data</data><data key="node_description">A claimant signing Form SSA-1696 with an X needs two independent witnesses with signatures and complete mailing addresses; witness contacts are not claimant residence addresses.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E023"><data key="node_entity_id">R116_E023</data><data key="node_entity_type">cataloged_database</data><data key="node_canonical_name">Audit Database and Information Tracking System</data><data key="node_domain">Enterprise governance and analytics</data><data key="node_description">SSA non-public data-catalog asset US-GOV-SSA-1607 tracks agency audit reports, performance/compliance audits, recommendations, management actions and related correspondence, including OIG/GAO items.</data><data key="node_observed_status">cataloged_nonpublic</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">First inventoried 2017-12-22; September 2026 catalog metadata does not prove current deployment/DBMS.</data></node><node id="R116_E024"><data key="node_entity_id">R116_E024</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">SSA Audit Recommendations and Follow-Up Action Data Domain</data><data key="node_domain">Enterprise governance and analytics</data><data key="node_description">Non-public audit-tracking information includes recommendations, agency corrective actions, audit correspondence, and internal/external audits.</data><data key="node_observed_status">non_public_asset</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Access restricted; not a public downloadable dataset.</data></node><node id="R116_E025"><data key="node_entity_id">R116_E025</data><data key="node_entity_type">cataloged_application</data><data key="node_canonical_name">Contractor Suitability System</data><data key="node_acronym">CSS</data><data key="node_domain">Procurement and personnel security</data><data key="node_description">SSA non-public data-catalog asset US-GOV-SSA-452 stores contractor personnel associated with SSA contracts, suitability determinations, and dates.</data><data key="node_observed_status">cataloged_nonpublic</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Physical backend/retention not published.</data></node><node id="R116_E026"><data key="node_entity_id">R116_E026</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">SSA Contractor Suitability Determination and Decision-Date Records</data><data key="node_domain">Procurement and personnel security</data><data key="node_description">Data.gov description confirms contractor identities, contract relationship and suitability determination/date; no identity provider, security system integration, or retention inferred.</data><data key="node_observed_status">non_public_asset</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E027"><data key="node_entity_id">R116_E027</data><data key="node_entity_type">external_exchange</data><data key="node_canonical_name">SSA-DoD PERSEREC SSN Verification Exchange</data><data key="node_acronym">DoD PERSEREC</data><data key="node_domain">External exchanges and identity</data><data key="node_description">SSA Data.gov US-GOV-SSA-626 describes restricted-public daily agreement to verify identifying SSN details for DoD DMDC/PERSEREC personnel background checks.</data><data key="node_observed_status">cataloged_restricted_public</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Catalog inventory dated 2016-06-24; daily frequency cataloged as of 2026-09-29. No transport/protocol inferred.</data></node><node id="R116_E028"><data key="node_entity_id">R116_E028</data><data key="node_entity_type">exchange_data</data><data key="node_canonical_name">DoD PERSEREC Applicant SSN Background-Screening Verification Request</data><data key="node_domain">External exchanges and identity</data><data key="node_description">DMDC uses SSA SSN verification for active/reserve military, National Guard, federal civilian and contractor background checks and facility/network access.</data><data key="node_observed_status">restricted_public_data_exchange</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E029"><data key="node_entity_id">R116_E029</data><data key="node_entity_type">adjudication_control</data><data key="node_canonical_name">Child Insurance Benefit Prior Disability Determination Adoption Gate</data><data key="node_domain">Title II disability and benefits</data><data key="node_description">OIG October 2026 review identifies improper initial denials when technicians fail to consider adoption of qualifying prior disability determinations before initiating fresh medical decisions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Audit identifies adherence issue, not a newly deployed automated rule.</data></node><node id="R116_E030"><data key="node_entity_id">R116_E030</data><data key="node_entity_type">payment_control</data><data key="node_canonical_name">CIB Post-Appeal Entitlement Date and Payment Recalculation Control</data><data key="node_domain">Title II disability and benefits</data><data key="node_description">OIG October 2026 audit identifies failures to compute correct entitlement dates and past-due benefits for children initially denied and later approved.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E031"><data key="node_entity_id">R116_E031</data><data key="node_entity_type">adjudication_control</data><data key="node_canonical_name">CIB Missing-Form and Evidence Denial Development Documentation Gate</data><data key="node_domain">Title II disability and benefits</data><data key="node_description">Technicians must document required development efforts before denying CIB disability applications for missing form or evidence; OIG found noncompliance.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E032"><data key="node_entity_id">R116_E032</data><data key="node_entity_type">benefit_workflow</data><data key="node_canonical_name">Workers Compensation/Public Disability Offset Higher Retirement Option Notification</data><data key="node_domain">Title II retirement and disability</data><data key="node_description">SSA must notify potentially affected workers-compensation/public-disability offset beneficiaries that higher retirement insurance benefits may be available; OIG October 2026 found missed notifications and responses.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E033"><data key="node_entity_id">R116_E033</data><data key="node_entity_type">benefit_workflow</data><data key="node_canonical_name">Higher Retirement Benefit Declination and Nonresponse Follow-Up Control</data><data key="node_domain">Title II retirement and disability</data><data key="node_description">SSA follow-up and documentation must capture disabled beneficiaries electing not to file for higher RIB and address nonresponders; audit documents continuing weaknesses after partial automation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E034"><data key="node_entity_id">R116_E034</data><data key="node_entity_type">modernization_observation</data><data key="node_canonical_name">Higher Retirement Option Partial Automated Notification Modernization</data><data key="node_domain">Title II retirement and disability</data><data key="node_description">OIG states SSA automated portions of higher-RIB option notification after 2015 finding; implementation product and effective date not identified, and 2026 deficiencies persist.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">3</data><data key="node_notes">Do not infer platform, full coverage or completion status.</data></node><node id="R116_E035"><data key="node_entity_id">R116_E035</data><data key="node_entity_type">program_integrity_control</data><data key="node_canonical_name">SSI Earnings Alert Timeliness and Complete Resolution Quality Control</data><data key="node_domain">SSI earnings and program integrity</data><data key="node_description">OIG September 2026 audit found large population of wage discrepancy alerts not resolved timely or cleared without all wage evidence documented; control needed for backlog follow-up.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E036"><data key="node_entity_id">R116_E036</data><data key="node_entity_type">legal_processing_rule</data><data key="node_canonical_name">SSI Earnings Alert Administrative Finality Recovery Boundary</data><data key="node_domain">SSI earnings and program integrity</data><data key="node_description">Delayed earnings-alert review can cause incorrect SSI payments to fall outside normal revision/recovery windows under administrative finality; fraud/similar-fault exceptions may apply.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E037"><data key="node_entity_id">R116_E037</data><data key="node_entity_type">eligibility_control</data><data key="node_canonical_name">SSI Liquid Resource Verification Tolerance Exception for Priority Diaries</data><data key="node_domain">Title XVI financial and IRS interfaces</data><data key="node_description">September 2026 SSI policy excludes 5B IRS, 5H pension, SB savings-bond, R8 conserved-funds and DI dedicated-account diaries from ordinary liquid-resource verification tolerance; requires AFI verification.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E038"><data key="node_entity_id">R116_E038</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">SSI External Wage Verification Company Evidence Intake</data><data key="node_domain">SSI earnings and program integrity</data><data key="node_description">POMS permits wage evidence from wage verification providers, but discrepancies require corroboration and staff enter verified wages on SSI Claims wages page or SSR.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Do not infer direct API or provider/vendor name.</data></node><node id="R116_E039"><data key="node_entity_id">R116_E039</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">SSI Wage Verification Evidence Dual Filing in CEF or NDRED</data><data key="node_domain">SSI earnings and program integrity</data><data key="node_description">Verified external wage evidence should be stored in CEF or if none exists NDRED via Evidence Portal, or in locked EVID/Report of Contact under rules.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E040"><data key="node_entity_id">R116_E040</data><data key="node_entity_type">program_integrity_control</data><data key="node_canonical_name">Numident Erroneous Death Removal Reason-Documentation Quality Control</data><data key="node_domain">Identity and death</data><data key="node_description">OIG July 2026 found incomplete documentation of reasons for recording and correcting erroneous death in 45% of sampled corrected cases, degrading downstream inquiry and prevention controls.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E041"><data key="node_entity_id">R116_E041</data><data key="node_entity_type">notice_quality_control</data><data key="node_canonical_name">Title II Overpayment Notice Policy Completeness Review Control</data><data key="node_domain">Payments, debt and correspondence</data><data key="node_description">OIG 2026 reports incorrect amounts, missing appeal/waiver rights and deficient explanations in sampled Title II overpayment notices; identify notice-generation quality risk.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R116_E042"><data key="node_entity_id">R116_E042</data><data key="node_entity_type">payment_control</data><data key="node_canonical_name">SSI Underpayment Deceased-Recipient Nonpayability Review</data><data key="node_domain">Title XVI payment accuracy</data><data key="node_description">OIG 2026 found pending SSI underpayments for deceased recipients that were not payable to anyone; data require validation before release or continued control.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R117_E001"><data key="node_entity_id">R117_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSA-635 Final-Review Evidence Portal Storage Gate</data><data key="node_domain">Debt and Payments</data><data key="node_description">SSA-635 is faxed or imported to Evidence Portal only when final waiver determination is made; if approval still requires review, filing waits until review completes.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E002"><data key="node_entity_id">R117_E002</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSR OPSQ Overpayment Sequence and Sequence Date</data><data key="node_domain">Title XVI</data><data key="node_description">SSR Overpayment Sequence Data segment contains overpayment sequence identifier and SQD date used for SSA-635 waiver traceability.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E003"><data key="node_entity_id">R117_E003</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Title II ROAR Waiver Event Reference</data><data key="node_domain">Title II</data><data key="node_description">SSA-635 references the ROAR event number to identify the Title II overpayment requiring waiver.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E004"><data key="node_entity_id">R117_E004</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Overpayment Waiver Review Disagreement Remand</data><data key="node_domain">Debt and Payments</data><data key="node_description">Nonconcurrence with proposed waiver approval is documented in DMS/CCE and returned for independent decision-maker/personal conference when required.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E005"><data key="node_entity_id">R117_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Administrative Tolerance Original-Debt Amount and Household Gate</data><data key="node_domain">Debt and Payments</data><data key="node_description">Administrative waiver tolerance applies to original overpayment amounts $2,000 or less subject to fault and household-related controls, not a recovered outstanding balance.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E006"><data key="node_entity_id">R117_E006</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Paid-versus-Payable Overpayment Calculation Chart</data><data key="node_domain">Debt and Payments</data><data key="node_description">Technician-prepared calculation and retained evidence used to reconcile paid benefit history against payable amounts, including PHUS transactions and certain withholdings.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E007"><data key="node_entity_id">R117_E007</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Overpayment Supporting-Evidence Lifetime Retention Rule</data><data key="node_domain">Debt and Payments</data><data key="node_description">Manual Title II overpayment evidence, including paid-versus-payable charts, is retained for the life of the overpayment.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E008"><data key="node_entity_id">R117_E008</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI KB Diary Priority-Selection Deferral Control</data><data key="node_domain">Title XVI</data><data key="node_description">When SSR holds a priority-select diary and future KB diary, system issues limited issue for priority diary and defers full age-18 RZ until KB matures.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E009"><data key="node_entity_id">R117_E009</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Age-18 Type-of-Master-Record DI/BI Conversion</data><data key="node_domain">Title XVI</data><data key="node_description">SSI Claims update of living arrangement at 18th birthday changes SSR Type of Master Record to DI/BI; non-SSI Claims cases use SSA-1719B plus SY and TY input.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E010"><data key="node_entity_id">R117_E010</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI KB Diary Incorrect-Date-of-Birth Monthly-Merge Clearance</data><data key="node_domain">Title XVI</data><data key="node_description">Correction of incorrect SSR DOB before age 18 clears profile-K redetermination in next monthly merge run.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E011"><data key="node_entity_id">R117_E011</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Title II Age-18 Child-Benefit Termination 2F Diary</data><data key="node_domain">Title II</data><data key="node_description">Age-18 termination of Title II child benefits causes the system to establish a 2F diary for follow-up.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E013"><data key="node_entity_id">R117_E013</data><data key="node_entity_type">application</data><data key="node_canonical_name">e4345 Windfall Offset Intercomponent Application</data><data key="node_acronym">e4345</data><data key="node_domain">Title II / Title XVI Cross-Program</data><data key="node_description">Web-based SSA-4345-U2 equivalent enables field offices and processing centers to exchange windfall-offset information electronically.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">No claim regarding underlying interface transport or persistence.</data></node><node id="R117_E014"><data key="node_entity_id">R117_E014</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4345-U2 Record of Manual Title II Computation</data><data key="node_domain">Title II / Title XVI Cross-Program</data><data key="node_description">Paper fallback form and e4345-equivalent used for PC/FO manual Title II computation and windfall-offset communications.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E015"><data key="node_entity_id">R117_E015</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI eComps Computation Printout</data><data key="node_domain">Title II / Title XVI Cross-Program</data><data key="node_description">Printout of eComps SSI RMA calculation serves as alternative to paper SSA-4968; stored with offset evidence in electronic folder.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E016"><data key="node_entity_id">R117_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Windfall Offset Unavailable-e4345 Fallback</data><data key="node_domain">Title II / Title XVI Cross-Program</data><data key="node_description">When e4345 unavailable, FO uses paper SSA-4345-U2, enters data later in e4345, and for urgent cases faxes paper through Evidence Portal and notifies PC.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E017"><data key="node_entity_id">R117_E017</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSI CMPH ZIP-Derived State and County Code</data><data key="node_domain">Title XVI / Address Provenance</data><data key="node_description">SSI Claims prepopulates state and county coding in SSR Computation History segment from residence ZIP code for qualifying state supplementary calculations.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E018"><data key="node_entity_id">R117_E018</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Windfall Offset Revised Federal and State Amounts</data><data key="node_domain">Title XVI</data><data key="node_description">Manual windfall computation uses SSR historic federal/state amounts and recalculates NEW FAM/NEW SAM for hypothetical timely Title II payment; result is posted via separate SSR action.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E019"><data key="node_entity_id">R117_E019</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">Accuity Asset Verification Services Inc.</data><data key="node_domain">Procurement</data><data key="node_description">Official SSA FY2022 acquisition forecast identifies Accuity as awardee for nationwide AFI contract 28321321D00060014 beginning 2021.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E020"><data key="node_entity_id">R117_E020</data><data key="node_entity_type">contract</data><data key="node_canonical_name">AFI Nationwide Services Contract 28321321D00060014</data><data key="node_domain">Procurement</data><data key="node_description">Official SSA forecast identifies Accuity AFI award with period 2021-04-25 through 2026-10-24; 2023 OAG data contains related task orders.</data><data key="node_observed_status">historical_award_verified_current_2026_status_unconfirmed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E021"><data key="node_entity_id">R117_E021</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">Experian Identity Verification Procurement Vendor</data><data key="node_domain">Procurement</data><data key="node_description">Official SSA FY2022 forecast states online identification and verification services for retirees and beneficiaries awarded to Experian.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E022"><data key="node_entity_id">R117_E022</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Online Beneficiary Identity Verification Contract 28321321D00060032</data><data key="node_domain">Procurement</data><data key="node_description">Official SSA FY2022 forecast identifies Experian award for online identification and verification services with projected period 2021-09-30 through 2028-09-29.</data><data key="node_observed_status">historical_award_verified_not_live_deployment_evidence</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E023"><data key="node_entity_id">R117_E023</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">ICF Incorporated SSA SAFE Support Vendor</data><data key="node_domain">Procurement</data><data key="node_description">Official SSA FY2022 forecast identifies ICF as awarded contractor for SAFE physical-security application development and maintenance.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E024"><data key="node_entity_id">R117_E024</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SAFE Development and Maintenance Order 28321321FDX030138</data><data key="node_domain">Procurement</data><data key="node_description">2021 SSA task order for Security Automated Features and Enhancements suite development and maintenance awarded to ICF, as recorded in official FY2022 forecast.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E025"><data key="node_entity_id">R117_E025</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">Northrop Grumman SSA Network Infrastructure Vendor</data><data key="node_domain">Procurement</data><data key="node_description">Official FY2022 forecast identifies Northrop Grumman awardee for SSA agency network infrastructure support BPA 28321321A00040008.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E026"><data key="node_entity_id">R117_E026</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Network Infrastructure BPA 28321321A00040008</data><data key="node_domain">Procurement</data><data key="node_description">Official FY2022 forecast documents network infrastructure services award to Northrop Grumman with 2021-08 through 2026-07 planned term.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E027"><data key="node_entity_id">R117_E027</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">Colossal Contracting SSA Infrastructure Vendor</data><data key="node_domain">Procurement</data><data key="node_description">SSA FY2022 forecast reports Colossal Contracting as awardee for network hardware, software and maintenance requirements contract.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E028"><data key="node_entity_id">R117_E028</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Network Equipment Contract 28321322D00060002</data><data key="node_domain">Procurement</data><data key="node_description">Official SSA FY2022 forecast identifies Colossal Contracting award for network infrastructure hardware/software/maintenance, dated 2021-11-19.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E029"><data key="node_entity_id">R117_E029</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">Tyto Athene SSA Multimedia Support Vendor</data><data key="node_domain">Procurement</data><data key="node_description">SSA FY2022 forecast reports Tyto Athene awardee for Multimedia Center Maintenance and Support Services.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E030"><data key="node_entity_id">R117_E030</data><data key="node_entity_type">contract</data><data key="node_canonical_name">Multimedia Center Support Contract 28321322D00060003</data><data key="node_domain">Procurement</data><data key="node_description">SSA FY2022 forecast confirms Tyto Athene award for multimedia center maintenance and support under IDIQ.</data><data key="node_observed_status">historical_award_verified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E031"><data key="node_entity_id">R117_E031</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA OAG November 2023 Award Listing Snapshot</data><data key="node_domain">Procurement</data><data key="node_description">Machine-readable OAG contract-award listing dated November 2, 2023 and exposed as HTML, CSV, XML and JSON; not evidence of live October 2026 award status.</data><data key="node_observed_status">historical_publication_snapshot</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E032"><data key="node_entity_id">R117_E032</data><data key="node_entity_type">procurement_workflow</data><data key="node_canonical_name">SSA Network Infrastructure Services Acquisition</data><data key="node_domain">Procurement</data><data key="node_description">Official SSA FY2022 forecast distinguishes purchased network infrastructure services from a separately awarded network hardware/software requirement.</data><data key="node_observed_status">historical_acquisition</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E033"><data key="node_entity_id">R117_E033</data><data key="node_entity_type">procurement_workflow</data><data key="node_canonical_name">SSA Online Beneficiary Identity Verification Procurement Scope</data><data key="node_domain">Procurement</data><data key="node_description">Historical SSA acquisition purpose of online identification and verification for retirees and beneficiaries; no evidence links specific modern AI application to this contract.</data><data key="node_observed_status">historical_acquisition</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R117_E034"><data key="node_entity_id">R117_E034</data><data key="node_entity_type">procurement_workflow</data><data key="node_canonical_name">SSA Multimedia Center Maintenance Procurement Scope</data><data key="node_domain">Procurement</data><data key="node_description">Historical SSA multimedia center support and maintenance procurement; no claimed backend platform, hardware model, or current operation.</data><data key="node_observed_status">historical_acquisition</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E001"><data key="node_entity_id">R118_E001</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SS-5 Original Microprint Evidence for Numident Correction</data><data key="node_domain">Identity / Enumeration</data><data key="node_description">Original SS-5 image or microprint compared against Numident to prove an input error before SSNAP NCP correction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E002"><data key="node_entity_id">R118_E002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Numident Field Change Dependent Program-Record Reconciliation</data><data key="node_domain">Identity / Program Records</data><data key="node_description">When supported sex field correction occurs, technicians update applicable MBR, SSR, RPS and other SSA records; the policy does not describe automatic physical replication.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Manual/controlled cross-record task; not documented as SSNAP-to-program-record auto-sync.</data></node><node id="R118_E003"><data key="node_entity_id">R118_E003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Numident Parent Name Change Beneficiary and Payee Reconciliation</data><data key="node_domain">Identity / Representative Payee</data><data key="node_description">Following change to child Numident parent name, employee asks whether parent is beneficiary or payee and reviews MBR SSR or RPS for necessary independent actions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E004"><data key="node_entity_id">R118_E004</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Enumeration at Birth Transmitting-Entity Error Documentation</data><data key="node_domain">Identity / State Vital Records</data><data key="node_description">Hospital or other participating entity documentation demonstrating that an error originated in the automatic EAB data source.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E005"><data key="node_entity_id">R118_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSNAP Non-Face-Field Replacement-Card Suppression</data><data key="node_domain">Identity / Enumeration</data><data key="node_description">When changing Numident sex, date/place of birth, or parent name data without changes on card face, suppress card issuance unless customer requested card.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E006"><data key="node_entity_id">R118_E006</data><data key="node_entity_type">identity_validation_control</data><data key="node_canonical_name">Additional Identity Verification Gate for Sensitive SSA Electronic Forms</data><data key="node_domain">Digital Services / Identity</data><data key="node_description">SSA Forms catalog identifies five electronically submitted forms for which additional identity verification is required; precise method not specified.</data><data key="node_observed_status">observed_public_submission_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Only conditional submission gate is documented; no vendor, authentication algorithm or underlying application inferred.</data></node><node id="R118_E007"><data key="node_entity_id">R118_E007</data><data key="node_entity_type">submission_channel</data><data key="node_canonical_name">SSA Forms Directory Complete Online and Upload PDF Routing Options</data><data key="node_domain">Digital Services / Forms</data><data key="node_description">Public SSA Forms directory publishes separate options for in-browser completion and PDF submission for selected hearings and appeal forms; no backend integration is documented.</data><data key="node_observed_status">public_submission_route_observed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E008"><data key="node_entity_id">R118_E008</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">Organizational Payee Mass Change Manual Advance-Notice Control</data><data key="node_domain">Representative Payee / Due Process</data><data key="node_description">For changed common organizational payees, advance notice is sent manually and 15-day diary established; eRPS mass change does not send that notice automatically.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E009"><data key="node_entity_id">R118_E009</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Organizational Payee Mass Change Conditional Beneficiary Residence Update</data><data key="node_domain">Representative Payee / Address Provenance</data><data key="node_description">After common payee reorganization or change, staff conditionally correct affected beneficiary residence using eRPS Beneficiary Address Change screen only when the residence has changed.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Separate from organizational payee contact address; no automatic propagation to MBR/SSR established.</data></node><node id="R118_E010"><data key="node_entity_id">R118_E010</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Common-Payee Mass Change SSA-11 First-Beneficiary Evidence Index</data><data key="node_domain">Representative Payee / Evidence</data><data key="node_description">SSA stores one organizational SSA-11 and affected beneficiary list into NDRED/eView under SSN of first listed beneficiary; eRPS note points to storage SSN.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E011"><data key="node_entity_id">R118_E011</data><data key="node_entity_type">case_note_type</data><data key="node_canonical_name">eRPS CAPA-CURRENT PAYEE CONTACT Report Code</data><data key="node_domain">Representative Payee / Capability</data><data key="node_description">Staff document contact with current payee using CAPA-CURRENT PAYEE CONTACT in eRPS Beneficiary Details Report of Contact for updated capability reviews.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E012"><data key="node_entity_id">R118_E012</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Representative-Payee Capability Report-of-Contact Fallback Routing</data><data key="node_domain">Representative Payee / Evidence</data><data key="node_description">For cases lacking eRPS entry, record payee contact in Title II RPOC or Title XVI CCE ROC, and fallback to SSA-5002 filed in NDRED/eView when unable to establish electronic note.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E013"><data key="node_entity_id">R118_E013</data><data key="node_entity_type">workflow_action</data><data key="node_canonical_name">Appeals Council Additional-Evidence UAT Alert Function</data><data key="node_domain">Disability / Appeals</data><data key="node_description">When evidence arrives at field office for a case pending Appeals Council review, staff fax/upload into electronic folder and use UAT function to notify Council.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">UAT is POMS function name; no unverified expansion, vendor, or persistence technology assigned.</data></node><node id="R118_E014"><data key="node_entity_id">R118_E014</data><data key="node_entity_type">adjudication_rule</data><data key="node_canonical_name">Appeals Council Withdrawal Dismissal Before Subsequent Application</data><data key="node_domain">Disability / Appeals</data><data key="node_description">SSA does not accept a new disability application concurrently with withdrawal request while AC appeal remains pending; AC must dismiss withdrawal first.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E015"><data key="node_entity_id">R118_E015</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">my Social Security Benefit-Statement Five-Year Retrieval and Winter Blackout</data><data key="node_domain">Tax / Beneficiary Services</data><data key="node_description">mySSA permits benefit statement access for five prior paid years; current-year replacement request unavailable mid-December to January 31, with year selection and PDF download.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E016"><data key="node_entity_id">R118_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Deceased-Beneficiary Tax Statement Last-MBR-Address Routing</data><data key="node_domain">Tax / Address Provenance</data><data key="node_description">For tax statements after death, SSA sends benefit statement to last MBR address; eAccess blocks access to deceased beneficiary mySSA account.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E017"><data key="node_entity_id">R118_E017</data><data key="node_entity_type">external_data_service</data><data key="node_canonical_name">South Dakota Workers Compensation Online Case Record Access</data><data key="node_domain">External Evidence / Workers Compensation</data><data key="node_description">SSA POMS documents access to South Dakota online WC records for authorized processing-center personnel; may supply employer, carrier, attorney contacts without completing development.</data><data key="node_observed_status">observed_state_access_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E018"><data key="node_entity_id">R118_E018</data><data key="node_entity_type">internal_portal</data><data key="node_canonical_name">SSA Internal Workers Compensation Resource Page</data><data key="node_domain">Disability / External Evidence</data><data key="node_description">SSA intranet WC Resource Page links to some states online records and lists processing-center personnel with access.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E019"><data key="node_entity_id">R118_E019</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Combined Title II and Title XVI Initial Disability Processing Time CSV FY2016 Onward</data><data key="node_domain">Enterprise Data / Disability Statistics</data><data key="node_description">Published SSA monthly average days to process combined initial claims requiring medical determination, excluding technical denials; monthly files from FY2016 onward.</data><data key="node_observed_status">published_public_data_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E020"><data key="node_entity_id">R118_E020</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Combined Disability Processing Time FY2016 53rd-Week CSV</data><data key="node_domain">Enterprise Data / Disability Statistics</data><data key="node_description">Separate FY2016 53rd reporting week CSV documents SSA workload-reporting boundary exception.</data><data key="node_observed_status">published_public_data_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E021"><data key="node_entity_id">R118_E021</data><data key="node_entity_type">published_actuarial_dataset</data><data key="node_canonical_name">2026 OASDI Trustees Single-Year Income Cost and Balance Table IV.B1</data><data key="node_domain">Actuarial / Public Projections</data><data key="node_description">Official single-year OASI, DI and OASDI trust-fund income rate, cost rate and balance as percentages of taxable payroll, historical 1970–2100 projected.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E022"><data key="node_entity_id">R118_E022</data><data key="node_entity_type">procurement_workflow</data><data key="node_canonical_name">SSA Acquisition 360 Survey Solicitation Provision Threshold Rule</data><data key="node_domain">Procurement / Acquisition Feedback</data><data key="node_description">SSA inserts FAR 52.201-1 in solicitations for IT awards over simplified acquisition threshold and non-IT awards with estimated lifetime value exceeding $10 million; other solicitations optional.</data><data key="node_observed_status">observed_procurement_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E023"><data key="node_entity_id">R118_E023</data><data key="node_entity_type">legal_processing_rule</data><data key="node_canonical_name">SSA Data Exchange Direction and Agreement Authorization Gate</data><data key="node_domain">External Exchanges / Governance</data><data key="node_description">SSA differentiates agreement (governing terms) from exchange (data movement). Incoming/outgoing directions, legal authority, security, feasibility, cost and reimbursement review determine permitted exchange.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E024"><data key="node_entity_id">R118_E024</data><data key="node_entity_type">external_data_service</data><data key="node_canonical_name">State Bureau of Vital Statistics Online Birth-Evidence Verification</data><data key="node_domain">Claims / Identity Evidence</data><data key="node_description">SSA explains field offices may contact state vital-statistics bureaus to verify age/citizenship evidence online; not evidence of full record synchronization.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R118_E025"><data key="node_entity_id">R118_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Retirement Benefit Application Birth-Evidence Development</data><data key="node_domain">Title II / Claim Identity Evidence</data><data key="node_description">SSA explains that field offices may verify claimants birth evidence through a state Bureau of Vital Statistics online, rather than requiring applicant to obtain it independently.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E001"><data key="node_entity_id">R119_E001</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">DOORS Office Location and Operating-Hours Attributes</data><data key="node_domain">enterprise/field-offices</data><data key="node_description">DOORS stores office code, name, address, telephone/fax, and operating hours for SSA public service locations. These are organizational office addresses, not beneficiary or Person addresses.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Quarterly published extract; retention and DOORS platform technology not established.</data></node><node id="R119_E002"><data key="node_entity_id">R119_E002</data><data key="node_entity_type">publication_process</data><data key="node_canonical_name">DOORS Quarterly Office Directory Extract</data><data key="node_domain">public-data/operations</data><data key="node_description">SSA publishes a quarterly extract from the Detailed Office/Organization Resource System and supplements office entries with its 800 telephone number for Office Locator alignment.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E003"><data key="node_entity_id">R119_E003</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Field Office Directory CSV (DOORS-based)</data><data key="node_domain">public-data/field-offices</data><data key="node_description">Quarterly downloadable CSV of field office locations and contact/hours information; published March 9, 2026. Physical publication pipeline is not described.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Administrative organization locations only; source is not a person-address authority.</data></node><node id="R119_E004"><data key="node_entity_id">R119_E004</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Resident Station Directory CSV (DOORS-based)</data><data key="node_domain">public-data/field-offices</data><data key="node_description">Quarterly downloadable CSV of resident station locations and contact/hours information; published March 9, 2026. Physical publication pipeline is not described.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Administrative organization locations only; source is not a person-address authority.</data></node><node id="R119_E005"><data key="node_entity_id">R119_E005</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Video Service Delivery Site Directory CSV (DOORS-based)</data><data key="node_domain">public-data/field-offices</data><data key="node_description">Quarterly downloadable CSV of vsd site locations and contact/hours information; published March 9, 2026. Physical publication pipeline is not described.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Administrative organization locations only; source is not a person-address authority.</data></node><node id="R119_E006"><data key="node_entity_id">R119_E006</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Unidentified Online Direct Deposit Update Database</data><data key="node_domain">payments/direct-deposit</data><data key="node_description">SSA Open Data explicitly says online Title II direct-deposit changes are sent to a database before MBR is updated. Database product, persistence, location, and update transport are unidentified.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Existence of a database documented; canonical physical identifier UNKNOWN. Not a new general Person repository.</data></node><node id="R119_E007"><data key="node_entity_id">R119_E007</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">Internet Direct Deposit Usage Transaction Capture</data><data key="node_domain">public-data/payments</data><data key="node_description">SSA captures Internet direct-deposit transactions as customers access the service; source says usage observations are stored in data stores and warehouses. Physical facilities and precise ETL are not documented.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E008"><data key="node_entity_id">R119_E008</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Online Direct Deposit SSI and Foreign-Address Eligibility Restriction</data><data key="node_domain">payments/direct-deposit</data><data key="node_description">As of July 10, 2026, online direct-deposit self-service is not available for SSI recipients or beneficiaries without a U.S. mailing address. This is a service-eligibility scope, not evidence that an online address changes MBR.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E009"><data key="node_entity_id">R119_E009</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Extra Help Part D Eligibility Decisions Annual State Dataset</data><data key="node_domain">public-data/medicare</data><data key="node_description">Annual national/state dataset of SSA Extra Help determinations and favorable decisions; excludes deemed beneficiaries and applications through state Medicaid agencies; SSA Data Catalog 332 and 1771.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Updated 2025-11-24; aggregate statistics only.</data></node><node id="R119_E010"><data key="node_entity_id">R119_E010</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">Medicare Extra Help Daily Operational Workload Transfer to SUMS Counts Warehouse</data><data key="node_domain">public-data/medicare</data><data key="node_description">SSA states that Medicare Operational Data Store SUMS workload information refreshes the SUMS Counts Data Warehouse daily, from which annual Extra Help state decision statistics derive.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E011"><data key="node_entity_id">R119_E011</data><data key="node_entity_type">logical_address_attribute</data><data key="node_canonical_name">Extra Help Statistical State Derived From Applicant Address</data><data key="node_domain">address-provenance/medicare</data><data key="node_description">The Extra Help decisions dataset defines its state as the state or DC provided in the applicant address; records outside the 50 states and DC appear as No Zip Available. This is a statistical geographic dimension, not proof of MBR or MDB master-address update.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E012"><data key="node_entity_id">R119_E012</data><data key="node_entity_type">external_exchange</data><data key="node_canonical_name">Help America Vote Verification Transaction Service</data><data key="node_domain">identity/state-voter-registration</data><data key="node_description">SSA HAVV provides state voter-registration verification using only the last four SSN digits, name, and birth date and returns matching/death categories. Participation uses authorized state partners.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Cannot infer that the HAVV interface directly queries Numident without separate technical evidence.</data></node><node id="R119_E013"><data key="node_entity_id">R119_E013</data><data key="node_entity_type">exchange_data</data><data key="node_canonical_name">HAVV Four-Digit Voter-Registration Identity Request</data><data key="node_domain">identity/state-voter-registration</data><data key="node_description">Permitted verification request contains last four SSN digits, name, and date of birth; intended for voter registration. Driver-license verification occurs first through state Motor Vehicle Administration.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E014"><data key="node_entity_id">R119_E014</data><data key="node_entity_type">exchange_data</data><data key="node_canonical_name">HAVV Verification and Death-Indicator Response Categories</data><data key="node_domain">identity/state-voter-registration</data><data key="node_description">Documented reply categories: no match, single/multiple matches alive, single/multiple matches deceased, mixed alive/deceased, invalid input. Status is a verification response not a death-update transaction.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E015"><data key="node_entity_id">R119_E015</data><data key="node_entity_type">data_access_control</data><data key="node_canonical_name">HAVV Voter-Registration-Only Disclosure Restriction</data><data key="node_domain">identity/external-exchanges</data><data key="node_description">SSA states HAVV verification requests/results are confidential and must be used only for voter registration; no general address/identity proofing reuse is established.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E016"><data key="node_entity_id">R119_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Employer Signature PIN Optional Election and Mandatory-If-Selected Filing Rule</data><data key="node_domain">earnings/employer-reporting</data><data key="node_description">SSA anticipates an opt-in annual employer PIN with planned December 2026 reporting season. If an employer elects PIN use, its own and delegated third-party W-2 reports must include it. Not established in production as of October 8.</data><data key="node_observed_status">planned</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Future conditional capability, no deployment claim; employer account administrator provides the PIN to authorized submitters.</data></node><node id="R119_E017"><data key="node_entity_id">R119_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI IRS Alert Payer Identity Resolution via DEQY</data><data key="node_domain">program-integrity/IRS</data><data key="node_description">When IRS interest-alert payer name or address is missing/inappropriate, SSA instructs staff to retrieve the detailed earnings query by payer EIN, not request payer name/address from IRS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E018"><data key="node_entity_id">R119_E018</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">IRS Alert Payee EIN versus Beneficiary SSN Collision Test</data><data key="node_domain">identity/IRS</data><data key="node_description">When an IRS alert shows a different payee name/address, SSA may use DEQY to determine whether the alleged SSN actually collides with a company EIN. Such payee addresses cannot be presumed to be the beneficiary address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E019"><data key="node_entity_id">R119_E019</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">SSI IRS Alert Duplicate Interest Posting Disposition</data><data key="node_domain">program-integrity/IRS</data><data key="node_description">SSA instructs to disregard duplicate interest transactions with identical payer/amount, then re-evaluate resource tolerance and clear an alert if no other issue remains.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E020"><data key="node_entity_id">R119_E020</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA IRS Interest Alert Financial-Institution Primary Record Verification</data><data key="node_domain">program-integrity/IRS</data><data key="node_description">When a taxpayer denies ownership of an interest-bearing bank account, SSA obtains signed SSA-4641 and seeks institution records for active and closed interest-bearing items; payer is source of transaction.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E021"><data key="node_entity_id">R119_E021</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination Direct-Deposit Account Resource Development</data><data key="node_domain">Title XVI/resources</data><data key="node_description">An MBR or SSR direct-deposit indicator directs staff to develop the underlying financial account as a possible resource and document it on the CCE Financial Accounts page; indicator does not prove current countable balance.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E022"><data key="node_entity_id">R119_E022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination First-of-Month Financial Account Balance Verification</data><data key="node_domain">Title XVI/resources</data><data key="node_description">When bank development is warranted, SSA evaluates account activity for the balance as of the first day of month and considers holiday/early payday exceptions and cleared/uncleared checks.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E023"><data key="node_entity_id">R119_E023</data><data key="node_entity_type">interface</data><data key="node_canonical_name">SSA I-Main DHS SAVE Claims Verification Entry Route</data><data key="node_domain">identity/lawful-presence</data><data key="node_description">SSA claims processing accesses DHS SAVE through I-Main, whereas enumeration invokes SAVE through SSNAP; SAVE verifies document/status but does not itself determine eligibility.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E024"><data key="node_entity_id">R119_E024</data><data key="node_entity_type">identity_validation_control</data><data key="node_canonical_name">DHS SAVE Response SSN Unverified-Claimant-Identifier Rule</data><data key="node_domain">identity/third-party-evidence</data><data key="node_description">SSA states an SSN included in a DHS SAVE response generally originated from the noncitizen and may be inaccurate. Staff should not treat it as Numident correction evidence or request DHS to correct it.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E025"><data key="node_entity_id">R119_E025</data><data key="node_entity_type">eligibility_control</data><data key="node_canonical_name">Numident IDN H Work-Authorization versus Lawful-Presence Evidence Rule</data><data key="node_domain">identity/benefits</data><data key="node_description">Numident IDN H indicates permanent work authorization, but is not sufficient evidence of lawful U.S. presence for current Title II payment determination; current documentary evidence and lawful-presence verification rules apply.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E026"><data key="node_entity_id">R119_E026</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Electronic Assistance Request Processing Workflow</data><data key="node_domain">disability/evidence</data><data key="node_description">A case-jurisdiction holding DDS/other authorized component sends an electronic assistance request to another component using the DDS case-processing system; original office retains CEF jurisdiction, other office has limited access.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Not all state DDS systems implement the full lifecycle; no universal automated completion presumed.</data></node><node id="R119_E027"><data key="node_entity_id">R119_E027</data><data key="node_entity_type">access_control_artifact</data><data key="node_canonical_name">CEF Electronic Assistance Request Limited Access Control</data><data key="node_domain">disability/evidence</data><data key="node_description">Receiving assistant office is granted Limited Access Control to categorize imaged documents and edit bookmarks/annotations without taking full CEF case jurisdiction.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E028"><data key="node_entity_id">R119_E028</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Assistance Request History Screen</data><data key="node_domain">disability/evidence</data><data key="node_description">eView Status/History tab shows electronic assistance request dates, issues, and jurisdictions for the life of the case. Stored with CEF case context; underlying table/physical DB not specified.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E029"><data key="node_entity_id">R119_E029</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-883 Request for Assistance</data><data key="node_domain">disability/evidence</data><data key="node_description">SSA-883 is one of the forms used for initiating or processing disability Electronic Assistance Requests. The documented form does not establish a separate database.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E030"><data key="node_entity_id">R119_E030</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-4488 DDS Assistance in Obtaining Reports</data><data key="node_domain">disability/evidence</data><data key="node_description">HA-4488 is one of the forms used for initiating or processing disability Electronic Assistance Requests. The documented form does not establish a separate database.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E031"><data key="node_entity_id">R119_E031</data><data key="node_entity_type">form</data><data key="node_canonical_name">HA-4489 DDS Assistance in Obtaining Consultative Examination</data><data key="node_domain">disability/evidence</data><data key="node_description">HA-4489 is one of the forms used for initiating or processing disability Electronic Assistance Requests. The documented form does not establish a separate database.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E032"><data key="node_entity_id">R119_E032</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-5526 Request for Assistance</data><data key="node_domain">disability/evidence</data><data key="node_description">SSA-5526 is one of the forms used for initiating or processing disability Electronic Assistance Requests. The documented form does not establish a separate database.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E033"><data key="node_entity_id">R119_E033</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Field Office Electronic Assistance Request Receive-Only Limitation</data><data key="node_domain">disability/evidence</data><data key="node_description">Field offices may receive but cannot initiate electronic assistance requests in the documented disability AR workflow.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E034"><data key="node_entity_id">R119_E034</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">DDS Legacy Electronic Assistance Request Feature-Gap Fallback</data><data key="node_domain">disability/evidence</data><data key="node_description">Some DDS legacy case systems cannot accept/reject/follow-up/cancel/close/transfer full electronic AR transactions; staff must use telephone or email with documentation in CEF.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Do not generalize to all DDS systems or infer identical current state across jurisdictions.</data></node><node id="R119_E035"><data key="node_entity_id">R119_E035</data><data key="node_entity_type">evidence_exception_workflow</data><data key="node_canonical_name">DDS Local Image Repository Paper-Transmission Exception</data><data key="node_domain">disability/evidence</data><data key="node_description">2025 POMS lists GA, IL, NC, OH, TN and TX as DDS with local image repositories requiring categorized electronic background materials to be printed/sent for some electronic assistance requests. Historical observed policy; October 2026 deployment unverified.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">State list and local repository limitation only as of cited 2025 policy.</data></node><node id="R119_E036"><data key="node_entity_id">R119_E036</data><data key="node_entity_type">data_identifier</data><data key="node_canonical_name">BEPUF 2020 Synthetic Beneficiary Linkage Identifier</data><data key="node_domain">research/public-use</data><data key="node_description">BEPUF 2020 benefits and earnings synthetic subfiles share a synthetic beneficiary ID. Because benefits/monthly benefit credited and earnings are modeled rather than computed by actual benefit rules, record-level pairs cannot be interpreted as programmatically consistent.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E037"><data key="node_entity_id">R119_E037</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">BEPUF 2020 Withdrawn AIME PIA nEarns Derived Variables</data><data key="node_domain">research/public-use</data><data key="node_description">SSA April 24, 2026 errata removed AIME, PIA and nEarns supplementary fields from Benefits Subfile following calculation errors in AIME and PIA. This is a data-product correction, not benefits determination recalculation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E038"><data key="node_entity_id">R119_E038</data><data key="node_entity_type">project</data><data key="node_canonical_name">SSI Recipient-Facing Case Facts Snapshot (SSAB Proposal)</data><data key="node_domain">Title XVI/modernization</data><data key="node_description">The July 25, 2026 Social Security Advisory Board report recommends that SSA develop a snapshot of current SSI case facts visible to recipients and representatives; it does not state this service is deployed.</data><data key="node_observed_status">recommended_not_deployed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E039"><data key="node_entity_id">R119_E039</data><data key="node_entity_type">project</data><data key="node_canonical_name">SSI Mobile Change-Reporting Application (SSAB Proposal)</data><data key="node_domain">Title XVI/modernization</data><data key="node_description">SSAB recommends a mobile SSI app for reporting changes in income, resources, and living arrangements beyond the existing limited wage-reporting service. This is a proposal, not evidence of procurement or deployment.</data><data key="node_observed_status">recommended_not_deployed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R119_E040"><data key="node_entity_id">R119_E040</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">SSI Non-Wage Change Report Auto-Processing Feasibility Assessment (SSAB Recommendation)</data><data key="node_domain">Title XVI/modernization</data><data key="node_description">SSAB urges SSA to evaluate feasibility and risk of automatically processing categories of SSI changes to reduce staff burden; does not demonstrate an existing auto-processing service.</data><data key="node_observed_status">recommended_not_deployed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E001"><data key="node_entity_id">R120_E001</data><data key="node_entity_type">program_record</data><data key="node_canonical_name">Medicare Health Insurance Master Record (HI Master)</data><data key="node_domain">Medicare/identity/address</data><data key="node_description">Health insurance master record separately queryable from the Title II MBR. POMS describes staff correction and reconciliation; no physical DBMS or automated universal person sync is established.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E002"><data key="node_entity_id">R120_E002</data><data key="node_entity_type">form</data><data key="node_canonical_name">CMS-2178-U2 Medicare Entitlement Priority Correction Referral</data><data key="node_domain">Medicare/claims</data><data key="node_description">One-page fillable Medicare entitlement correction form routed to a processing center or CMS; used for HI/MBR inconsistency when direct input cannot fix it; not a routine premium correction.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E003"><data key="node_entity_id">R120_E003</data><data key="node_entity_type">document</data><data key="node_canonical_name">CMS-1966 Medicare Health Insurance Card</data><data key="node_domain">Medicare/service</data><data key="node_description">Medicare health insurance card whose identifying details may require correction under CMS-2178-U2.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E004"><data key="node_entity_id">R120_E004</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MBR and Medicare HI Address Discrepancy Development</data><data key="node_domain">Medicare/address provenance</data><data key="node_description">If both MBR and HI record addresses are wrong, technician attempts POS correction or sends CMS-2178-U2 to a processing center via Paperless; if only HI is wrong, emails CMS. No automatic IRS-derived address correction is implied.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E005"><data key="node_entity_id">R120_E005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">POS Medicare Name and Sex-Code Correction with EDB Downstream Update</data><data key="node_domain">Medicare/person identity</data><data key="node_description">When both Title II MBR and HI record contain incorrect name/sex data, POS direct input can correct them and subsequently update CMS Enrollment Database according to current POMS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E006"><data key="node_entity_id">R120_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CMS Medicare HI-Only Entitlement Error Referral</data><data key="node_domain">Medicare/cross-agency</data><data key="node_description">CMS-2178-U2 routed to CMS for correction of a HI-only record error, with subsequent verification of correction. A separate workflow from SSA MBR update.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E007"><data key="node_entity_id">R120_E007</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">CMS-2178 Medicare Correction 30-Day and 90-Day Follow-up</data><data key="node_domain">Medicare/cross-agency</data><data key="node_description">A response or unresolved correction after 30 working days triggers follow-up; 90 calendar days without resolution leads to CMS regional escalation per HI 00930.080.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E008"><data key="node_entity_id">R120_E008</data><data key="node_entity_type">query_interface</data><data key="node_canonical_name">Medicare HMQ Query (Unexpanded Acronym)</data><data key="node_domain">Medicare/service</data><data key="node_description">Query cited in POMS for verifying Medicare HI data corrections; backend transport not described.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E009"><data key="node_entity_id">R120_E009</data><data key="node_entity_type">query_interface</data><data key="node_canonical_name">Medicare ESQ Query (Unexpanded Acronym)</data><data key="node_domain">Medicare/service</data><data key="node_description">Query cited in POMS for verifying HI-only entitlement record corrections; no backend technology inferred.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E010"><data key="node_entity_id">R120_E010</data><data key="node_entity_type">application</data><data key="node_canonical_name">SSI Redetermination Wizard (RZ WIZ)</data><data key="node_domain">Title XVI/workflow</data><data key="node_description">Policy requires RZ WIZ for limited-issue, redetermination and wage-diary interviews; technical hosting and physical data store undocumented.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E011"><data key="node_entity_id">R120_E011</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI KZ Insured-Status Diary</data><data key="node_domain">Title XVI/Title II nexus</data><data key="node_description">Semiannual April/October SSI diary alerts staff to possible Title II retirement or qualifying disability insured status; policy includes a four-quarter proximity test and disability constraints.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E012"><data key="node_entity_id">R120_E012</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Age-90 KC Limited-Issue Diary</data><data key="node_domain">Title XVI/program integrity</data><data key="node_description">New LI described for SSI recipient or eligible spouse reaching age 90 by fiscal-year end; application to age-90 cases uses KZ/KC-specific policy, not a universal identity correction.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E013"><data key="node_entity_id">R120_E013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Unredetermined Case (UC) Profile Selection</data><data key="node_domain">Title XVI/workload</data><data key="node_description">UC profile can select cases after three months in current/force payment or qualifying 1619(b) status; distinct from regular periodic-review profiles.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E014"><data key="node_entity_id">R120_E014</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI High/Medium/Low Error Profile RZ Scheduling</data><data key="node_domain">Title XVI/workload</data><data key="node_description">2026 POMS schedules HEP/MEP and some LEP profiles annually, while other LEP profiles may run every six years; scheduling varies by category.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E015"><data key="node_entity_id">R120_E015</data><data key="node_entity_type">form</data><data key="node_canonical_name">Treasury Form FMS-1133 Forgery Claim Package</data><data key="node_domain">Treasury/payments</data><data key="node_description">Treasury-issued claims package for possible forged government checks following SSA nonreceipt/stop-payment requests; staff scan to Evidence Portal and forward the full package to Treasury.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E016"><data key="node_entity_id">R120_E016</data><data key="node_entity_type">form</data><data key="node_canonical_name">Treasury Form FMS-3858 Certified Check Photocopy Request</data><data key="node_domain">Treasury/payments</data><data key="node_description">An L-stop produces FMS-3858 and a copy of the check, not an FMS-1133 forgery claim; Treasury will not process photocopies of FMS-1133 for nonreceipt.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E017"><data key="node_entity_id">R120_E017</data><data key="node_entity_type">access_control</data><data key="node_canonical_name">TCIS One-Time FMS-1133 Printable Package Control</data><data key="node_domain">Treasury/payments</data><data key="node_description">FO and processing center may print the form one time through TCIS while printable; teleservice staff cannot print it and must refer through MDW.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E018"><data key="node_entity_id">R120_E018</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Treasury Forgery Versus Handwriting Decision by Check Age</data><data key="node_domain">Treasury/payments</data><data key="node_description">Timely nonreceipt of checks 12 months or younger leads to Treasury forgery determination; older untimely nonreceipt leads to handwriting review without FI reclamation based on age.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E019"><data key="node_entity_id">R120_E019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">FMS-1133 Evidence Portal Intake and Treasury Forwarding</data><data key="node_domain">Treasury/evidence</data><data key="node_description">SSA field office, teleservice center or processing center scans received FMS-1133 pages to Evidence Portal and forwards Treasury package promptly.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E020"><data key="node_entity_id">R120_E020</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">TCIS FMS-1133 vHelp and Operations Analysis Escalation</data><data key="node_domain">Treasury/support</data><data key="node_description">If TCIS package cannot be printed or claim status cannot be established, applicable FO/TSC vHelp or PSC Operations Analysis staff seek Treasury assistance.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E021"><data key="node_entity_id">R120_E021</data><data key="node_entity_type">payment_event</data><data key="node_canonical_name">PHUS Event 169 Unnegotiated Check</data><data key="node_domain">Title II/payments</data><data key="node_description">When REACT processes limited payability credit/correction PHUS records Event 169 UNNEG CK.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E022"><data key="node_entity_id">R120_E022</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">REACT RCLRN N Limited-Payability Notice Indicator</data><data key="node_domain">Title II/payments</data><data key="node_description">REACT ordinarily annotates RCLRN field N and produces notice file after qualifying limited payability event.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E023"><data key="node_entity_id">R120_E023</data><data key="node_entity_type">notice_data</data><data key="node_canonical_name">REACT Automated Uncashed Check Notice File</data><data key="node_domain">Title II/correspondence</data><data key="node_description">Title II LP notice generated following REACT event to ask recipient to identify uncashed checks and sign response. Title XVI does not automatically send same LP notice.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E024"><data key="node_entity_id">R120_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Signed Limited-Payability Repayment Confirmation Gate</data><data key="node_domain">Title II/payments</data><data key="node_description">Signed returned LP notice and status verification are required to authorize repayment; unsigned notice cannot itself authorize check reissue.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E025"><data key="node_entity_id">R120_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Deceased Title II Underpayment Nonnegotiation Verification</data><data key="node_domain">Title II/payments</data><data key="node_description">Benefit authorizer confirms returned, unnegotiated or unreceived payments using REACT output, PHUS or Treasury TCIS before paying proper survivor.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E026"><data key="node_entity_id">R120_E026</data><data key="node_entity_type">data_observation</data><data key="node_canonical_name">Deceased-Beneficiary Surviving-Spouse Shared Check Address Evidence</data><data key="node_domain">Title II/person/address</data><data key="node_description">The spouse receiving checks at same address is one possible element of LISH evidence; it does not validate current residence or initiate address update.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E027"><data key="node_entity_id">R120_E027</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Deceased Beneficiary Conserved Funds Exclusion from Underpayment</data><data key="node_domain">Representative payee/debt</data><data key="node_description">Conserved funds are not a Title II underpayment; deceased beneficiary estate return is separate from statutory underpayment priority and former payee payout.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E028"><data key="node_entity_id">R120_E028</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EAE Enumeration Pending Exception 365-Day Expiration</data><data key="node_domain">Enumeration/identity</data><data key="node_description">EAE transmitted records with Investigate or Not Completed status remain pending up to 365 days before drop if not resolved, as described in December 2024 POMS.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E029"><data key="node_entity_id">R120_E029</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EAE Nonreceipt Replacement Card 14-Day Cycle-Date Rule</data><data key="node_domain">Enumeration/card delivery</data><data key="node_description">For EAE card issuance, a Numident cycle date less than 14 days old generally prompts advice to await mailing; older records can require a replacement card application. SSNAP Special FO nonreceipt excluded.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E030"><data key="node_entity_id">R120_E030</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EBE SSNAP Pending Exception 365-Day Retention</data><data key="node_domain">Enumeration/identity</data><data key="node_description">Unprocessed EBE applications in Investigate or Not Completed status remain pending for 365 days unless evidence submitted to resolve; no implication of Numident issuance.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E031"><data key="node_entity_id">R120_E031</data><data key="node_entity_type">telephony_system</data><data key="node_canonical_name">Field Office Network Enterprise Telephone System (FONE)</data><data key="node_domain">Infrastructure/contact center</data><data key="node_description">SSA identifies national FONE telephone system providing calls to local field offices, underlying network routing details not published in source.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E032"><data key="node_entity_id">R120_E032</data><data key="node_entity_type">historical_network</data><data key="node_canonical_name">TSRP Field-Office Telephone Routing Network (Historical)</data><data key="node_domain">Infrastructure/contact center</data><data key="node_description">SSA Open Data states it completed transition to a new network called TSRP in 2012; not evidence TSRP is still production network in October 2026.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E033"><data key="node_entity_id">R120_E033</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Field Office Answer and Busy Rate Monthly CSV</data><data key="node_domain">Open data/field office</data><data key="node_description">Public CSV (US-GOV-SSA-1414) reporting national FO answer and busy rates since FY2013, updated March 26 2026; sourced from routing vendor feed.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E034"><data key="node_entity_id">R120_E034</data><data key="node_entity_type">external_data_source</data><data key="node_canonical_name">Unnamed Field Office Telephony Routing-Vendor Measures</data><data key="node_domain">Infrastructure/contact center</data><data key="node_description">SSA states the software routing vendor supplies counts; vendor name, product and data mechanism unverified.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E035"><data key="node_entity_id">R120_E035</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">Field Office Call Answer/Busy Dataset Abandon and Overflow Exclusions</data><data key="node_domain">Open data/field office</data><data key="node_description">FO answer/busy rates exclude calls abandoned in queue and calls overflowing past 15-minute maximum without representative service.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E036"><data key="node_entity_id">R120_E036</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSDI Initial Claims Spoken-Language Preference Quarterly CSV FY2023 Onward</data><data key="node_domain">Open data/disability</data><data key="node_description">Public quarterly SSDI initial-claim spoken language series US-GOV-SSA-2332. SCDD combines SUMS workload with SUMS client demographics from Integrated Client Data Base; file updated 2026-03-31.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E037"><data key="node_entity_id">R120_E037</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Blind and Disabled Initial Claims Spoken-Language Preference Quarterly CSV FY2023 Onward</data><data key="node_domain">Open data/Title XVI</data><data key="node_description">Public quarterly SSI blind/disabled initial claims language-preference series US-GOV-SSA-2328; sourced from SCDD and updated 2026-03-31.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E038"><data key="node_entity_id">R120_E038</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA Public AI Use-Case Listing April 2026 CSV</data><data key="node_domain">AI governance/open data</data><data key="node_description">SSA AI public page links a public AI use-case listing CSV updated as of April 2026, including current and planned uses; individual use cases not inspected or asserted.</data><data key="node_observed_status">public_inventory_exists</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E039"><data key="node_entity_id">R120_E039</data><data key="node_entity_type">governance_document</data><data key="node_canonical_name">SSA Enterprise Artificial Intelligence Strategy (Published)</data><data key="node_domain">AI governance</data><data key="node_description">SSA AI transparency page provides enterprise AI strategy under OMB M-25-21; strategy contents and projects not inferred from linked unreviewed PDF.</data><data key="node_observed_status">published</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R120_E040"><data key="node_entity_id">R120_E040</data><data key="node_entity_type">governance_document</data><data key="node_canonical_name">SSA M-25-21 AI Compliance Plan (Published)</data><data key="node_domain">AI governance</data><data key="node_description">SSA AI transparency page links agency compliance plan; existence documented, implementation of individual controls not verified here.</data><data key="node_observed_status">published</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E001"><data key="node_entity_id">R121_E001</data><data key="node_entity_type">process</data><data key="node_canonical_name">Earnings After Death Validation Process</data><data key="node_domain">Earnings / Program Integrity</data><data key="node_description">During AWR validation, the year of reported earnings is compared against death year on Numident; discrepant wages and self-employment require investigation and may be placed in suspense.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E002"><data key="node_entity_id">R121_E002</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Earnings After Death Report Suspense Reason Code</data><data key="node_acronym">EADR</data><data key="node_domain">Earnings / Suspense</data><data key="node_description">EADR marks wages or self-employment earnings occurring after the recorded death year that enter the Earnings Suspense File for tax years 1991 and later.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E003"><data key="node_entity_id">R121_E003</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Earnings After Death Investigate File</data><data key="node_domain">Earnings / Fraud Detection</data><data key="node_description">Office of Systems produces EAD investigate file and sends work to Wilkes-Barre Data Operations Center for verification against worker or employer.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E004"><data key="node_entity_id">R121_E004</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Numident Death-Year AWR Comparison Key</data><data key="node_domain">Person / Earnings</data><data key="node_description">Year of death on Numident compared to reported wage tax year in annual wage-reporting validation; inaccurate death records may produce false EAD suspensions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E005"><data key="node_entity_id">R121_E005</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L4112C1 Employer Earnings After Death Verification Request</data><data key="node_acronym">SSA-L4112C1</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">WBDOC sends request to employer to clarify earnings reported after worker death.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E006"><data key="node_entity_id">R121_E006</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L3400C1 Self-Employed Worker Earnings After Death Notice</data><data key="node_acronym">SSA-L3400C1</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">WBDOC sends this notice to number holder with self-employment earnings after death.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E007"><data key="node_entity_id">R121_E007</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L3044 Earnings Attribution Notice to Employee</data><data key="node_acronym">SSA-L3044</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">When employer has insufficient response, WBDOC may advise person shown on W-2 that reported wages may not belong to them.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E008"><data key="node_entity_id">R121_E008</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Earnings After Death Discrepancy Investigation Response</data><data key="node_domain">Earnings / Corrections</data><data key="node_description">Worker or employer response to WBDOC query routed to OCRO for further resolution and cross-record checks.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E009"><data key="node_entity_id">R121_E009</data><data key="node_entity_type">process</data><data key="node_canonical_name">Earnings After Death Suspense Reinstatement and Identity Correction</data><data key="node_domain">Earnings / Identity / Program Integrity</data><data key="node_description">After development, corrected date of death and SSN attribution are handled separately from reinstating earnings from suspense using IC; 1991-and-later rules differ from TY1988-90 rules.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E010"><data key="node_entity_id">R121_E010</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-3278 OCRO Death-Code Correction Request</data><data key="node_acronym">SSA-3278</data><data key="node_domain">Earnings / Identity</data><data key="node_description">Used for certain ETC=D death-code removal requests before earnings correction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E011"><data key="node_entity_id">R121_E011</data><data key="node_entity_type">screen</data><data key="node_canonical_name">Interactive Corrections Add Wage Earnings Screen</data><data key="node_acronym">EAWG</data><data key="node_domain">Earnings / Historical Corrections</data><data key="node_description">EAWG supports reestablishing offset historical wage earnings for TY1988-1990 following correction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Historic tax-year workflow in current POMS; do not infer currently used for TY2026.</data></node><node id="R121_E012"><data key="node_entity_id">R121_E012</data><data key="node_entity_type">screen</data><data key="node_canonical_name">Interactive Corrections Add Self-Employment Earnings Screen</data><data key="node_acronym">EASE</data><data key="node_domain">Earnings / Historical Corrections</data><data key="node_description">EASE used to reestablish applicable historical self-employment earnings after incorrect death correction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Historic tax-year workflow.</data></node><node id="R121_E013"><data key="node_entity_id">R121_E013</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI N20 Failure to Provide Information Suspension Control</data><data key="node_acronym">N20</data><data key="node_domain">Title XVI / Due Process</data><data key="node_description">N20 requires documented outstanding evidence requests, follow-up, appropriate responsible party and approval by a management support specialist or higher before suspension.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E014"><data key="node_entity_id">R121_E014</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Initial Written Evidence Request 30-Day Control</data><data key="node_domain">Title XVI / Notices</data><data key="node_description">Initial written SSI eligibility/evidence request dated at mailing and generally allows 30 calendar days to comply.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E015"><data key="node_entity_id">R121_E015</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Written Second-Request Notice and 10-Day Control</data><data key="node_domain">Title XVI / Notices</data><data key="node_description">SSTNG or DPS auto-includes SECOND REQUEST on followup; a mailed followup with deadline extension must provide 10 calendar days when required.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E016"><data key="node_entity_id">R121_E016</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI N20 Manager Approval Audit Record</data><data key="node_domain">Title XVI / Payment Control</data><data key="node_description">Records approving manager name/title, date, payment month and followup documentation before N20 suspension.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E017"><data key="node_entity_id">R121_E017</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI N20 Suspension Payment Status Input</data><data key="node_domain">Title XVI / Payment Control</data><data key="node_description">N20 approved suspension entered on CCE Payment Status page or 1719B in non-CCE cases, subject to Goldberg/Kelly notice controls.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E018"><data key="node_entity_id">R121_E018</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSI Undeliverable Mail Appeal-Rights Cover Letter</data><data key="node_domain">Title XVI / Address / Appeals</data><data key="node_description">Undeliverable Cover Letter re-mailed with SSI notice involving appeal rights; receipt can restart appeal period as the notice indicates.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E019"><data key="node_entity_id">R121_E019</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title XVI Returned-Mail N20 Versus S06 Decision Control</data><data key="node_domain">Title XVI / Due Process</data><data key="node_description">Returned notices must trigger location development; inability to locate claimant is not the same as failure to respond to a correctly delivered notice.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E020"><data key="node_entity_id">R121_E020</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Undeliverable Request Reissue with New Date</data><data key="node_domain">Title XVI / Notices</data><data key="node_description">Requests for information, appointments and protective-filing closeouts are retyped and remailed with current date after new address obtained.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E021"><data key="node_entity_id">R121_E021</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II Seven-Year Undeliverable-Mail Death Presumption</data><data key="node_domain">Title II / Address / Death</data><data key="node_description">For an adult non-disabled Title II beneficiary with at least seven years continuous suspension after unsuccessful contact, presume death unless evidence rebuts; not a direct Numident death report.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E022"><data key="node_entity_id">R121_E022</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MBR Undeliverable-Mail Special Message Audit Trail</data><data key="node_domain">Title II / Address Provenance</data><data key="node_description">MBR Special Message annotated with address-development efforts, outcomes and subsequent long-suspension presumption; prior messages must not be deleted.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E023"><data key="node_entity_id">R121_E023</data><data key="node_entity_type">process</data><data key="node_canonical_name">Continuing Disability Review Whereabouts Unknown Address Search</data><data key="node_domain">Disability / Identity / Address</data><data key="node_description">FO reviews MBR/SSR and contacts payee/auxiliaries before requiring SSA-L2001 USPS request, with rules for skipped mail if USPS already reports no forwarding address.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E024"><data key="node_entity_id">R121_E024</data><data key="node_entity_type">form</data><data key="node_canonical_name">Accessible Special Notice Option Undeliverable Mail Cover Letter</data><data key="node_domain">Notices / Accessibility</data><data key="node_description">SNO-specific undeliverable cover letter in DPS/Aurora replaces standard cover letter for notices in Braille, audio, data CD or large print.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E025"><data key="node_entity_id">R121_E025</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Undeliverable Accessible Media Shredding Control</data><data key="node_domain">Notices / Accessibility</data><data key="node_description">Braille, CD, or large-print returned item is shredded when no remailing is required under policy.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E026"><data key="node_entity_id">R121_E026</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA e2960 USA/RO 3 Romania Claims and Liaison eForm</data><data key="node_acronym">SSA e2960 USA/RO 3</data><data key="node_domain">International / Totalization</data><data key="node_description">Digital U.S.-Romania transmittal, request and certification form completed by IBP and Naples FBU via TDCP.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E027"><data key="node_entity_id">R121_E027</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Romania Totalization eForm Claimant Contact Address</data><data key="node_domain">Person / Address / International</data><data key="node_description">Claimant-reported full address and phone on SSA e2960 USA/RO 3 for bilateral processing, not evidence of MBR/Numident address update.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E028"><data key="node_entity_id">R121_E028</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Romania Totalization Birth Registration Number</data><data key="node_domain">Person / External Identifiers</data><data key="node_description">Romanian birth registration number on bilateral claims form; when unavailable, name, DOB, and place-of-birth identifiers provided instead.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E029"><data key="node_entity_id">R121_E029</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Romania Totalization Individual Evidence Certification Flags</data><data key="node_domain">Person / Identity / International</data><data key="node_description">Form certification checks if DOB, death, marriage, divorce, birth country and citizenship have proof on MBR, Numident or prior U.S. award; unverified facts are not certified.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E030"><data key="node_entity_id">R121_E030</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Romania Totalization Medical Evidence and Insurance Period Package</data><data key="node_domain">International / Disability / Earnings</data><data key="node_description">Claims packet may provide U.S. earnings certificate, applications, medical evidence, and requests for Romanian insurance periods or medical evidence.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E031"><data key="node_entity_id">R121_E031</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS Emergency-Clause Disability Jurisdiction Transfer</data><data key="node_domain">Disability / Workload / Governance</data><data key="node_description">Temporary SSA-DDS agreement can route eligible DDS cases, reconsiderations or CDRs to ODO FDU or PSC DCR during state backlog.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E032"><data key="node_entity_id">R121_E032</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS Emergency-Clause Temporary Jurisdiction Agreement</data><data key="node_domain">Disability / Governance</data><data key="node_description">State temporary agreement with SSA specifies effective period, workload and permissible temporary routing to federal disability review components.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E033"><data key="node_entity_id">R121_E033</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSA-831 Emergency-Clause Case Remark</data><data key="node_domain">Disability / Routing</data><data key="node_description">Paper disability case receives Emergency Clause case marker and named DDS in SSA-831 remarks; electronic cases go through EDCS.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E034"><data key="node_entity_id">R121_E034</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Railroad Disability Foreign-Address Jurisdiction Override</data><data key="node_domain">Disability / International / Address</data><data key="node_description">When a dual-eligibility railroad-related disability claimant has foreign address, route case to Office of International Operations V22 ahead of ordinary DCR V32 jurisdiction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E035"><data key="node_entity_id">R121_E035</data><data key="node_entity_type">query</data><data key="node_canonical_name">Railroad Survivor Jurisdiction DRAMS Query</data><data key="node_acronym">DRAMS</data><data key="node_domain">Title II / Railroad / External Exchange</data><data key="node_description">DRAMS query accessed through Query Master or SSA Main Menu to identify whether RRB or SSA has survivor claim jurisdiction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E036"><data key="node_entity_id">R121_E036</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Railroad Disability Case Review V32 Routing Rule</data><data key="node_domain">Disability / Railroad</data><data key="node_description">Career railroad and specified RR disability survivor cases sent to DCR V32; general DDS lacks jurisdiction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E037"><data key="node_entity_id">R121_E037</data><data key="node_entity_type">screen</data><data key="node_canonical_name">Railroad Earnings Data DRRE Screen</data><data key="node_acronym">DRRE</data><data key="node_domain">Title II / Earnings / Railroad</data><data key="node_description">MCS earnings computation screen shows railroad service months by 1937- and post-1995 definitions for DCR insured-status routing.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E038"><data key="node_entity_id">R121_E038</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">iSNO Follow-Up Telephone Confirmation Contact</data><data key="node_domain">Accessibility / Person / Contact</data><data key="node_description">iSNO records phone number when person chooses standard mail plus follow-up phone call within five business days.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E039"><data key="node_entity_id">R121_E039</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">iSNO Three-Record Identity Authentication Acceptance</data><data key="node_domain">Person / Identity / Customer Service</data><data key="node_description">iSNO compares supplied identity data against MBR, SSR and Numident; mismatch requiring staff correction does not itself update all records.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E040"><data key="node_entity_id">R121_E040</data><data key="node_entity_type">screen</data><data key="node_canonical_name">IRCS QPID Incentive-Payee Address Query</data><data key="node_acronym">QPID</data><data key="node_domain">Prisoner Reporting / Addresses</data><data key="node_description">Incentive Payment Identification Query screen displays incentive payment data, facility address and contact information, checked when SSA-L4020 returned.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E041"><data key="node_entity_id">R121_E041</data><data key="node_entity_type">process</data><data key="node_canonical_name">Prisoner Incentive Recoupment Returned-Notice Address Verification</data><data key="node_domain">Program Integrity / Debt / Postal</data><data key="node_description">For returned SSA-L4020, staff review IRCS QPID, USPS forwarding and facility contact to verify correct institutional address and remail.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E042"><data key="node_entity_id">R121_E042</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">ABLE Disability Onset Before Age 46 Eligibility Rule Effective 2026</data><data key="node_domain">Title XVI / Resources / Disability</data><data key="node_description">Beginning Jan 1 2026, eligible ABLE account disability onset age threshold becomes before age 46 instead of before age 26.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R121_E043"><data key="node_entity_id">R121_E043</data><data key="node_entity_type">process</data><data key="node_canonical_name">Overpayment Waiver Personal Conference Returned Notice Control</data><data key="node_domain">Debt / Due Process / Address</data><data key="node_description">If waiver personal conference notice is returned, locate and remail if address found; if not, document efforts on DMS Title II remarks or Title XVI report of contact.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E001"><data key="node_entity_id">R122_E001</data><data key="node_entity_type">data_classification</data><data key="node_canonical_name">SSI IRS 1099 Resource Indicator Classification</data><data key="node_domain">Title XVI / IRS / Program Integrity</data><data key="node_description">The SSI IRS match classifies financial-institution and other tax-information transactions as resource or income-and-resource indicators; classification alone does not verify resources or beneficiary address.</data><data key="node_observed_status">documented_2017_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">2017 POMS threshold and selection rules may differ from current production.</data></node><node id="R122_E002"><data key="node_entity_id">R122_E002</data><data key="node_entity_type">data_classification</data><data key="node_canonical_name">SSI IRS 1099 Income-Only Indicator Classification</data><data key="node_domain">Title XVI / IRS / Program Integrity</data><data key="node_description">SSI IRS interface separately classifies indicators requiring income-only development; not an address verification or direct SSR income update.</data><data key="node_observed_status">documented_2017_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E003"><data key="node_entity_id">R122_E003</data><data key="node_entity_type">rule</data><data key="node_canonical_name">SSI IRS Alert Thresholds by Household Status (2017 Policy)</data><data key="node_domain">Title XVI / IRS / Program Integrity</data><data key="node_description">2017 POMS: individual resource indicator &gt;=$61, couple &gt;=$101, and income indicator &gt;=$1,001 establish controlled alerts, subject to prior-year exception rules and case review.</data><data key="node_observed_status">documented_2017_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E004"><data key="node_entity_id">R122_E004</data><data key="node_entity_type">rule</data><data key="node_canonical_name">SSI IRS Prior-Year Resource Alert Suppression Conditions (2017)</data><data key="node_domain">Title XVI / IRS / Program Integrity</data><data key="node_description">2017 POMS suppresses some repeated 5B diary triggers when annual resource-indicator difference is within $10, or current band $61-$70 individual/$101-$110 couple falls from prior year; technicians may still develop material information.</data><data key="node_observed_status">documented_2017_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E005"><data key="node_entity_id">R122_E005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI IRS Match Release and Selection Schedule (2017)</data><data key="node_domain">Title XVI / IRS / Program Integrity</data><data key="node_description">2017 POMS lists October, March, and June selection groups with corresponding November, May, and July alert availability in the SSI redetermination applications.</data><data key="node_observed_status">documented_2017_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E006"><data key="node_entity_id">R122_E006</data><data key="node_entity_type">governance_document</data><data key="node_canonical_name">Prisoner Incentive Payment MOU Reporting Agreement</data><data key="node_acronym">IPMOU</data><data key="node_domain">Prisoner Reporting / Interagency Agreements</data><data key="node_description">SSA Prisoner Incentive Payment MOU identifies the reporting agency or authority empowered to request official institutional payment-notice mailing-address changes.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Agreements are institutional; not personal beneficiary address authority.</data></node><node id="R122_E007"><data key="node_entity_id">R122_E007</data><data key="node_entity_type">repository_view</data><data key="node_canonical_name">Online Retrieval System PRISONERS Incentive Notice Folder</data><data key="node_domain">Prisoner Reporting / Correspondence</data><data key="node_description">ORS PRISONERS folder holds copies of monthly institution-specific prisoner incentive-payment notices for authorized retrieval by facility identifier.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E008"><data key="node_entity_id">R122_E008</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">IRCS Facility ID Numbers Assigned to Reporter Query (QRI2)</data><data key="node_acronym">QRI2</data><data key="node_domain">Prisoner Reporting / Identity</data><data key="node_description">The IRCS QRI2 reporter query supplies facility identifiers used to locate incentive-payment notices in ORS.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">No unsupported underlying database technology.</data></node><node id="R122_E009"><data key="node_entity_id">R122_E009</data><data key="node_entity_type">correspondence_product</data><data key="node_canonical_name">Monthly Institutional Prisoner Incentive Payment Notice</data><data key="node_domain">Prisoner Reporting / Payments</data><data key="node_description">Monthly electronic-funds-transfer incentive-payment notice names institution and includes payment amount, payment date, count of suspended persons and minimal identifying information.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E010"><data key="node_entity_id">R122_E010</data><data key="node_entity_type">control</data><data key="node_canonical_name">IPMOU Signatory Institutional Notice Address Authorization</data><data key="node_domain">Address Provenance / Institutional</data><data key="node_description">Under April 2026 POMS only institution/agency or authority that signed IPMOU can authorize incentive-payment notice mailing-address update; request forwarded to Field Operations Prisoner Coordinator.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E011"><data key="node_entity_id">R122_E011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Institutional Incentive-Payment Dispute Investigation and Referral</data><data key="node_domain">Prisoner Reporting / Program Integrity</data><data key="node_description">FO compares disputed incentive notice with IRCS/PUPS data and provided banking evidence; if unresolved, routes to Field Operations Prisoner Coordinator and possibly Central Office.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E012"><data key="node_entity_id">R122_E012</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Treasury Institutional Incentive-Payment Offset Exception</data><data key="node_domain">Payments / Treasury / Prisoner</data><data key="node_description">A prison incentive EFT deposit may be reduced by Treasury offset for the institution debt; amount received need not equal the payment amount SSA authorized.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E013"><data key="node_entity_id">R122_E013</data><data key="node_entity_type">actuarial_process</data><data key="node_canonical_name">2026 OASDI Five-Thousand-Path Stochastic Projection Run</data><data key="node_domain">Actuarial / Model Execution</data><data key="node_description">2026 Trustees Appendix VI.E reports 5,000 independently simulated outcome paths with random year-to-year error terms and simulation-specific expected mean variation.</data><data key="node_observed_status">published_model_methodology</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Logical actuarial modeling process, not proof of deployed software product.</data></node><node id="R122_E014"><data key="node_entity_id">R122_E014</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">2026 OASDI Stochastic Demographic Input Variables</data><data key="node_domain">Actuarial / Demographic Modeling</data><data key="node_description">Variables allowed to vary stochastically: fertility, mortality changes, lawful permanent resident arrivals, other immigration, status adjustment, and legal emigration.</data><data key="node_observed_status">published_model_input</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E015"><data key="node_entity_id">R122_E015</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">2026 OASDI Stochastic Economic Input Variables</data><data key="node_domain">Actuarial / Economic Modeling</data><data key="node_description">Stochastic variables include consumer-price changes, changes in real average wages, unemployment rates, and trust fund real yields.</data><data key="node_observed_status">published_model_input</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E016"><data key="node_entity_id">R122_E016</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">2026 OASDI Stochastic Disability Input Variables</data><data key="node_domain">Actuarial / Disability Modeling</data><data key="node_description">Disabled-worker incidence and recovery rates vary in the 2026 stochastic projections.</data><data key="node_observed_status">published_model_input</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E017"><data key="node_entity_id">R122_E017</data><data key="node_entity_type">model_component</data><data key="node_canonical_name">2026 Stochastic Model Random Error and Parameter-Mean Terms</data><data key="node_domain">Actuarial / Model Execution</data><data key="node_description">Each equation assigns annual random error and simulation-specific mean-level variation, which permits parameter uncertainty around expected central tendency.</data><data key="node_observed_status">published_model_methodology</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E018"><data key="node_entity_id">R122_E018</data><data key="node_entity_type">published_data_product</data><data key="node_canonical_name">2026 Trustees Stochastic Cost-Rate Percentile Output</data><data key="node_domain">Actuarial / Publications</data><data key="node_description">Appendix VI.E figure VI.E1 publishes annual OASDI cost-rate median with 80-percent and 95-percent simulated bands; percentile time series do not trace one simulation.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E019"><data key="node_entity_id">R122_E019</data><data key="node_entity_type">published_data_product</data><data key="node_canonical_name">2026 Trustees Stochastic Trust-Fund Ratio Percentile Output</data><data key="node_domain">Actuarial / Publications</data><data key="node_description">Appendix VI.E figure VI.E2 reports projected trust-fund ratio median and 80-percent/95-percent simulated ranges, including a 2032-2039 95-percent depletion-year range.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E020"><data key="node_entity_id">R122_E020</data><data key="node_entity_type">published_data_product</data><data key="node_canonical_name">2026 Trustees Table VI.E1 Scenario-Stochastic Comparison</data><data key="node_domain">Actuarial / Publications</data><data key="node_description">Table VI.E1 compares intermediate, low-cost, high-cost scenario estimates with stochastic medians and 80-percent/95-percent ranges for actuarial balance, unfunded obligation, depletion, and year-75 costs.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E021"><data key="node_entity_id">R122_E021</data><data key="node_entity_type">model_assumption</data><data key="node_canonical_name">2026 Trustees Stochastic Projection Variable-Scope Limitations</data><data key="node_domain">Actuarial / Model Governance</data><data key="node_description">Trustees warn that labor-force participation, retirement, marriage and divorce are not among variables allowed to vary randomly in this stochastic model, so ranges may understate some uncertainty.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E022"><data key="node_entity_id">R122_E022</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">ALJ/PAMC Complaint-Derived Claimant Identity Fields</data><data key="node_domain">Hearings / Privacy / Person Nexus</data><data key="node_description">ALJ/PAMC retains claimant name, SSN, date of birth, address and other information only if provided in an ALJ-bias or misconduct complaint and relevant to its review.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E023"><data key="node_entity_id">R122_E023</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">ALJ/PAMC Judicial Complaint Tracking Identifiers</data><data key="node_domain">Hearings / Accountability</data><data key="node_description">ALJ/PAMC system retains ALJ name, assigned number, tracking and control log identifiers and case-review correspondence to investigate complaints.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E024"><data key="node_entity_id">R122_E024</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">ALJ/PAMC Misconduct Pattern Review Function</data><data key="node_domain">Hearings / Quality / Program Integrity</data><data key="node_description">ALJ/PAMC uses complaint analyses and investigation outcomes to identify patterns of improper ALJ behavior for review and action.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E025"><data key="node_entity_id">R122_E025</data><data key="node_entity_type">legal_control</data><data key="node_canonical_name">ALJ/PAMC Federal Tax Return Information Disclosure Gate</data><data key="node_domain">Hearings / Privacy</data><data key="node_description">ALJ/PAMC PIA bars disclosure of IRC section 6103 return information absent applicable statutory, IRS, or regulatory authorization.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E026"><data key="node_entity_id">R122_E026</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">Functional Assessment Calibration Claimant Contact Extract</data><data key="node_domain">Disability / Research / Address</data><data key="node_description">SSA ODP through NIH and BU-HDRI supplies Westat a study-specific extract of claimant name, age, sex, address, SSN, email and alleged impairment to recruit selected individuals.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Historical study-specific identity data; not a new enterprise Person repository.</data></node><node id="R122_E027"><data key="node_entity_id">R122_E027</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">Functional Assessment Study Health-Provider Contact Details</data><data key="node_domain">Disability / Research / Address</data><data key="node_description">Claimant supplies study contractor names, addresses and phone numbers of primary and secondary treating providers for research invitation and provider survey.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E028"><data key="node_entity_id">R122_E028</data><data key="node_entity_type">research_instrument</data><data key="node_canonical_name">Functional Assessment CAT Physical Demands and Interpersonal Questions</data><data key="node_domain">Disability / Research</data><data key="node_description">Question domains developed by Boston University Health and Disability Research Institute and calibrated from participant responses; not a deployed adjudicative decision engine.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E029"><data key="node_entity_id">R122_E029</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">Functional Assessment De-Identified Calibration Analysis Dataset</data><data key="node_domain">Disability / Research / Governance</data><data key="node_description">Westat shares collected study participant functional information with Boston University Health and Disability Research Institute in non-identifiable form for statistical CAT calibration.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E030"><data key="node_entity_id">R122_E030</data><data key="node_entity_type">verification_control</data><data key="node_canonical_name">TNEV Employer EIN Matching Against SSA Earnings Records</data><data key="node_domain">Identity / Earnings / External Requests</data><data key="node_description">2025 PIA says automated employer telephone SSN verification checks supplied employer EIN against Earnings Recording and Self-Employment Income System, 60-0059.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E031"><data key="node_entity_id">R122_E031</data><data key="node_entity_type">retention_control</data><data key="node_canonical_name">TNEV Call-End Disposal of Spoken Identity and Employer Data</data><data key="node_domain">Identity / Privacy / Telephony</data><data key="node_description">The 2025 PIA states telephone verification application does not retain spoken caller or employee identity details; vendor-transmitted call data are dropped when call ends.</data><data key="node_observed_status">documented_2025_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R122_E032"><data key="node_entity_id">R122_E032</data><data key="node_entity_type">restricted_exchange_product</data><data key="node_canonical_name">Full SSA Death Information File Including State Death Reports</data><data key="node_domain">Death / Data Exchange / Governance</data><data key="node_description">Full SSA death file includes state-source deaths and is available only to authorized government counterparties under section 205(r), not unrestricted public distribution.</data><data key="node_observed_status">documented_official_exchange</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Logical release variant; no inference that separate physical source database exists.</data></node><node id="R122_E033"><data key="node_entity_id">R122_E033</data><data key="node_entity_type">public_exchange_product</data><data key="node_canonical_name">Limited Access Public Death Master File Excluding State Death Reports</data><data key="node_domain">Death / Data Exchange</data><data key="node_description">SSA supplies NTIS public DMF excluding state death records; this differs from government full death information distribution.</data><data key="node_observed_status">documented_official_exchange</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Logical disclosure product derived from SSA death information, not a distinct physical master repository.</data></node><node id="R122_E034"><data key="node_entity_id">R122_E034</data><data key="node_entity_type">oversight_finding</data><data key="node_canonical_name">2026 OIG Incorrect-Death-Removal Documentation Findings</data><data key="node_domain">Identity / Numident / Audit</data><data key="node_description">July 2026 OIG report found technicians failed to document initial incorrect death or removal reasons in 45% of sampled cases, impeding cause and trend investigation.</data><data key="node_observed_status">published_2026_audit</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Sampling finding not whole-population estimate.</data></node><node id="R123_E001"><data key="node_entity_id">R123_E001</data><data key="node_entity_type">unidentified_database</data><data key="node_canonical_name">Unidentified Online Change-of-Address Transaction Database</data><data key="node_domain">Title II / Address Provenance</data><data key="node_description">SSA public documentation says online change-of-address transactions are sent to an unnamed database before updating MBR. Its product, schema, hosting, data retention, transaction mechanism, and physical separation from other systems are not identified.</data><data key="node_observed_status">documented_unidentified_implementation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Logical placeholder for an explicitly reported but unnamed database, not asserted separate physical installation.</data></node><node id="R123_E002"><data key="node_entity_id">R123_E002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Internet Change-of-Address US and Territory Address Eligibility Rule</data><data key="node_domain">Title II / Address Provenance</data><data key="node_description">SSA limits online changes to persons living in and moving to the 50 states, DC, Puerto Rico, US Virgin Islands, Guam, Northern Mariana Islands, or American Samoa; SSI-only and foreign/APO/FPO cases are excluded.</data><data key="node_observed_status">documented_current_public_service</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E003"><data key="node_entity_id">R123_E003</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Internet Change-of-Address Self-Submission Restriction</data><data key="node_domain">Title II / Digital Identity</data><data key="node_description">SSA says only the beneficiary may submit an online address change to their own account; this does not establish the technology used to authenticate that user.</data><data key="node_observed_status">documented_current_public_service</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E004"><data key="node_entity_id">R123_E004</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Internet Change-of-Address Fiscal Year 2016 Onward Monthly CSV</data><data key="node_domain">Public Data / Address Transactions</data><data key="node_description">SSA publishes monthly counts of Internet Change of Address transactions for FY2016 onward in a CSV product, not a record of individual addresses.</data><data key="node_observed_status">published_current</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E005"><data key="node_entity_id">R123_E005</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Internet Change-of-Address FY2016 53rd Workweek CSV</data><data key="node_domain">Public Data / Address Transactions</data><data key="node_description">SSA publishes the extra 53rd reporting-week transaction counts for FY2016 as a separate online-address-change CSV.</data><data key="node_observed_status">published_historical</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E006"><data key="node_entity_id">R123_E006</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">Internet Change-of-Address FY2008-2015 Historical CSV</data><data key="node_domain">Public Data / Address Transactions</data><data key="node_description">SSA provides the older FY2008-FY2015 Internet Change of Address monthly transaction counts as a separate CSV.</data><data key="node_observed_status">published_historical</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E007"><data key="node_entity_id">R123_E007</data><data key="node_entity_type">statistical_extract</data><data key="node_canonical_name">2026 SSI Current Program Participation Complete SSR Extract</data><data key="node_domain">Title XVI / Actuarial / Statistical</data><data key="node_description">The 2026 SSI annual report uses a 100 percent extract of SSR to summarize December 2025 contemporaneous program participation, not a live interface to external programs.</data><data key="node_observed_status">2026_statistical_method</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E008"><data key="node_entity_id">R123_E008</data><data key="node_entity_type">statistical_extract</data><data key="node_canonical_name">2026 SSI Prior Program Participation Ten-Percent SSR Extract</data><data key="node_domain">Title XVI / Actuarial / Statistical</data><data key="node_description">The 2026 SSI report uses a 10 percent extract of SSR to summarize prior participation in selected assistance programs; this is distinct from the current complete extract.</data><data key="node_observed_status">2026_statistical_method</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E009"><data key="node_entity_id">R123_E009</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">2026 SSI Interprogram Participation Statistical Compilation</data><data key="node_domain">Title XVI / Actuarial / Statistical</data><data key="node_description">Statistical compilation integrates distinct current and prior participation SSR extracts into published SSI cross-program participation percentages.</data><data key="node_observed_status">2026_report_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E010"><data key="node_entity_id">R123_E010</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">2026 SSI Annual Report Table V.F1 Program Participation</data><data key="node_domain">Actuarial / SSI / Published Products</data><data key="node_description">December 2025 SSI federally administered recipient participation percentages by age and category, including OASDI, VA disability, TANF/AFDC history and interim assistance reimbursement history.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E011"><data key="node_entity_id">R123_E011</data><data key="node_entity_type">historical_subsystem</data><data key="node_canonical_name">Title II Telephone Applications Subsystem (2017)</data><data key="node_domain">Title II / Telephone Service</data><data key="node_description">2017 Title II PIA groups telephone services for benefit verification letters and replacement form requests; not proof of unchanged 2026 deployment.</data><data key="node_observed_status">documented_2017_current_status_unverified</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E012"><data key="node_entity_id">R123_E012</data><data key="node_entity_type">historical_application</data><data key="node_canonical_name">iBEVE Telephone Benefit Verification Letter Service (2017)</data><data key="node_domain">Title II / Telephone Service</data><data key="node_description">2017 SSA Title II PIA explicitly names iBEVE for telephone requests for proof-of-income letters.</data><data key="node_observed_status">documented_2017_current_status_unverified</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E013"><data key="node_entity_id">R123_E013</data><data key="node_entity_type">historical_customer_service_channel</data><data key="node_canonical_name">Customer Engagement Tools Dynamic Help Channel (2017)</data><data key="node_domain">Digital Service / Contact Center</data><data key="node_description">Dynamic Help listed within 2017 Title II Customer Engagement Tools; no current vendor or product inferred.</data><data key="node_observed_status">historical_documentation_only</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E014"><data key="node_entity_id">R123_E014</data><data key="node_entity_type">historical_customer_service_channel</data><data key="node_canonical_name">Customer Engagement Tools Click to Callback Channel (2017)</data><data key="node_domain">Digital Service / Contact Center</data><data key="node_description">Click to Callback listed within 2017 Title II Customer Engagement Tools.</data><data key="node_observed_status">historical_documentation_only</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E015"><data key="node_entity_id">R123_E015</data><data key="node_entity_type">historical_customer_service_channel</data><data key="node_canonical_name">Customer Engagement Tools Click to Chat Channel (2017)</data><data key="node_domain">Digital Service / Contact Center</data><data key="node_description">Click to Chat listed within 2017 Title II Customer Engagement Tools.</data><data key="node_observed_status">historical_documentation_only</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E016"><data key="node_entity_id">R123_E016</data><data key="node_entity_type">historical_customer_service_channel</data><data key="node_canonical_name">Customer Engagement Tools Message Center Channel (2017)</data><data key="node_domain">Digital Service / Contact Center</data><data key="node_description">2017 PIA lists CET Message Center; not identified as physically identical to later my Social Security Message Center.</data><data key="node_observed_status">historical_documentation_only</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E017"><data key="node_entity_id">R123_E017</data><data key="node_entity_type">historical_subsystem</data><data key="node_canonical_name">Title II Processing Systems Subsystem (2017)</data><data key="node_domain">Title II / Historical 2017 PIA Boundary</data><data key="node_description">2017 grouping for special/critical payment, earnings/employment, claims, customer service, prisoner and railroad processing functions.</data><data key="node_observed_status">2017_taxonomy_unconfirmed_today</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E018"><data key="node_entity_id">R123_E018</data><data key="node_entity_type">historical_subsystem</data><data key="node_canonical_name">Title II Medicare Services Subsystem (2017)</data><data key="node_domain">Title II / Historical 2017 PIA Boundary</data><data key="node_description">2017 grouping for Medicare enrollments, queries, subsidies, awards and calculations.</data><data key="node_observed_status">2017_taxonomy_unconfirmed_today</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E019"><data key="node_entity_id">R123_E019</data><data key="node_entity_type">historical_subsystem</data><data key="node_canonical_name">Title II Notice Services Subsystem (2017)</data><data key="node_domain">Title II / Historical 2017 PIA Boundary</data><data key="node_description">2017 grouping for benefit communications and employee status notifications.</data><data key="node_observed_status">2017_taxonomy_unconfirmed_today</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E020"><data key="node_entity_id">R123_E020</data><data key="node_entity_type">historical_subsystem</data><data key="node_canonical_name">Title II Claims Services Subsystem (2017)</data><data key="node_domain">Title II / Historical 2017 PIA Boundary</data><data key="node_description">2017 grouping for claims information, post-entitlement adjustments and updates.</data><data key="node_observed_status">2017_taxonomy_unconfirmed_today</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E021"><data key="node_entity_id">R123_E021</data><data key="node_entity_type">historical_subsystem</data><data key="node_canonical_name">Title II Accounting Services Subsystem (2017)</data><data key="node_domain">Title II / Historical 2017 PIA Boundary</data><data key="node_description">2017 grouping for reports to Congress, international payments, and statutory financial assistance processes.</data><data key="node_observed_status">2017_taxonomy_unconfirmed_today</data><data key="node_observed_as_of">2017-07-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E022"><data key="node_entity_id">R123_E022</data><data key="node_entity_type">research_assessment_instrument</data><data key="node_canonical_name">Work Disability Functional Assessment Battery Research Instrument</data><data key="node_domain">Disability / Research</data><data key="node_description">Respondent self-report functional assessment developed with NIH and Boston University; explored for medical CDR feasibility. Research instrument, not an SSA adjudication production system.</data><data key="node_observed_status">research_instrument_study_complete_2023</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E023"><data key="node_entity_id">R123_E023</data><data key="node_entity_type">research_instrument_component</data><data key="node_canonical_name">WD-FAB Item Response Theory Question Bank</data><data key="node_domain">Disability / Research</data><data key="node_description">WD-FAB item bank contains over 300 questions and uses Item Response Theory for selecting assessment questions.</data><data key="node_observed_status">research_methodology_documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E024"><data key="node_entity_id">R123_E024</data><data key="node_entity_type">research_method</data><data key="node_canonical_name">WD-FAB Computer Adaptive Testing Selection</data><data key="node_domain">Disability / Research</data><data key="node_description">Computer adaptive testing chooses respondent-specific questions from WD-FAB item bank across eight functioning domains.</data><data key="node_observed_status">research_methodology_documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E025"><data key="node_entity_id">R123_E025</data><data key="node_entity_type">research_data_collection</data><data key="node_canonical_name">WD-FAB Two-Wave Medical CDR Survey (2023)</data><data key="node_domain">Disability / Research</data><data key="node_description">Westat administered two waves of functional-assessment and related survey questions to medical CDR beneficiaries six months apart; collection ended August 2023.</data><data key="node_observed_status">completed_august_2023</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E026"><data key="node_entity_id">R123_E026</data><data key="node_entity_type">research_analysis</data><data key="node_canonical_name">NIH Clinical Center WD-FAB Functional Assessment Analysis</data><data key="node_domain">Disability / Research</data><data key="node_description">NIH Clinical Center rehabilitation researchers analyzed study responses under interagency arrangement for feasibility of applying WD-FAB to medical CDR procedures.</data><data key="node_observed_status">completed_research_analysis</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E027"><data key="node_entity_id">R123_E027</data><data key="node_entity_type">research_publication</data><data key="node_canonical_name">WD-FAB Research Study Final Report</data><data key="node_domain">Disability / Research Data Products</data><data key="node_description">SSA lists a final WD-FAB research study report; this documents research outputs, not clinical decision automation in DDS.</data><data key="node_observed_status">published_research_report</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E028"><data key="node_entity_id">R123_E028</data><data key="node_entity_type">research_demonstration</data><data key="node_canonical_name">Supported Employment Demonstration (2016-2022)</data><data key="node_domain">Disability / Employment Research</data><data key="node_description">SSA Westat mixed-methods randomized demonstration; 2944 enrollees in 30 locations across 20 states; recruitment 2017-2019, participant activity ended March 2022.</data><data key="node_observed_status">historical_demonstration_completed_2022</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E029"><data key="node_entity_id">R123_E029</data><data key="node_entity_type">research_dataset</data><data key="node_canonical_name">SED Baseline and Quarterly Research Interview Dataset</data><data key="node_domain">Disability / Research Data</data><data key="node_description">SED baseline and 12 quarterly participant interviews measuring services, health, employment, income and related outcomes.</data><data key="node_observed_status">historical_research_data</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E030"><data key="node_entity_id">R123_E030</data><data key="node_entity_type">administrative_research_extract</data><data key="node_canonical_name">SED Historical SSA Disability Claim and Payment Outcome Research Extract</data><data key="node_domain">Disability / Research Data</data><data key="node_description">SSA administrative records of claims, appeals, allowance, denials and payment outcomes integrated into SED analyses; this does not establish direct access to underlying master files.</data><data key="node_observed_status">historical_research_extract</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E031"><data key="node_entity_id">R123_E031</data><data key="node_entity_type">research_public_use_dataset</data><data key="node_canonical_name">Supported Employment Demonstration Public-Use File</data><data key="node_domain">Disability / Research Publications</data><data key="node_description">Deidentified analytic file for 2,944 SED participants combining longitudinal surveys and selected SSA administrative outcomes, published for research use in multiple formats.</data><data key="node_observed_status">published_2023</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E032"><data key="node_entity_id">R123_E032</data><data key="node_entity_type">research_disclosure_control</data><data key="node_canonical_name">SED Public-Use Privacy Transformation Process</data><data key="node_domain">Disability / Privacy / Research</data><data key="node_description">SSA public-use release removed direct identifiers, geography/site information, identifying free-text fields, and some rare attributes and coarsened selected variables.</data><data key="node_observed_status">documented_publication_governance</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E033"><data key="node_entity_id">R123_E033</data><data key="node_entity_type">research_release_approval_process</data><data key="node_canonical_name">SED Program Data Disclosure Review Board Review (2023)</data><data key="node_domain">Disability / Privacy / Research</data><data key="node_description">SSA privacy disclosure review process approved release of SED public-use data on May 10 2023 after review of reidentification risks.</data><data key="node_observed_status">completed_2023</data><data key="node_observed_as_of">2023-05-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E034"><data key="node_entity_id">R123_E034</data><data key="node_entity_type">published_csv_dataset</data><data key="node_canonical_name">SED Public Use Data CSV Distribution</data><data key="node_domain">Disability / Research Data Products</data><data key="node_description">CSV distribution of SSA Supported Employment Demonstration Public Use File, as one of the published file formats.</data><data key="node_observed_status">published_public_use</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E035"><data key="node_entity_id">R123_E035</data><data key="node_entity_type">published_sas_dataset</data><data key="node_canonical_name">SED Public Use Data SAS Distribution</data><data key="node_domain">Disability / Research Data Products</data><data key="node_description">SAS distribution of the same SED public-use data; no independent database inferred.</data><data key="node_observed_status">published_public_use</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E036"><data key="node_entity_id">R123_E036</data><data key="node_entity_type">federal_statutory_requirement</data><data key="node_canonical_name">SHARE IT Act Custom Code Repository and Ownership Requirement</data><data key="node_domain">Acquisition / Software Governance</data><data key="node_description">2024 Act directs agencies to own their custom code and hold it in at least one public or private repository accessible to federal employees; does not identify any SSA production code repository.</data><data key="node_observed_status">law_enacted_2024_not_deployment_evidence</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E037"><data key="node_entity_id">R123_E037</data><data key="node_entity_type">federal_statutory_requirement</data><data key="node_canonical_name">SHARE IT Act Custom Software Metadata Publication Requirement</data><data key="node_domain">Enterprise Architecture / Metadata</data><data key="node_description">Federal statute requires publication of metadata for new agency custom-developed code subject to statutory exceptions; does not establish SSA published such metadata.</data><data key="node_observed_status">law_enacted_2024_not_deployment_evidence</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E038"><data key="node_entity_id">R123_E038</data><data key="node_entity_type">federal_statutory_requirement</data><data key="node_canonical_name">SHARE IT Act Custom Code Government-Wide Reuse Rights</data><data key="node_domain">Procurement / Software Rights</data><data key="node_description">Custom software contracts must secure enough rights for governmentwide access, reuse, sharing and modification.</data><data key="node_observed_status">law_enacted_2024_not_deployment_evidence</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E039"><data key="node_entity_id">R123_E039</data><data key="node_entity_type">federal_statutory_requirement</data><data key="node_canonical_name">SHARE IT Act Agency Custom Code Governance Policy</data><data key="node_domain">Enterprise IT / Acquisition Governance</data><data key="node_description">Requires agency CIOs to develop policy on version control, code-sharing, and metadata with Chief Acquisition Officer coordination.</data><data key="node_observed_status">law_enacted_2024_not_deployment_evidence</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E040"><data key="node_entity_id">R123_E040</data><data key="node_entity_type">document_certification_process</data><data key="node_canonical_name">Southwest Region National Records Center Folder Certification Request Workflow</data><data key="node_domain">Records Management / Public Requests</data><data key="node_description">Dallas-area SSA regional supplement directs most field office requests for certified SSA records through the National Records Center folder certification request process; limited to documented region.</data><data key="node_observed_status">regional_policy_documented_2025</data><data key="node_observed_as_of">2025-01-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E041"><data key="node_entity_id">R123_E041</data><data key="node_entity_type">internal_request_portal</data><data key="node_canonical_name">National Records Center Folder Certification Request Site</data><data key="node_domain">Records Management / Public Requests</data><data key="node_description">SSA regional POMS refers to a National Records Center Folder Certification Request Site for certified records requests; URL, vendor, technology and current operational deployment unverified.</data><data key="node_observed_status">referenced_in_2025_regional_policy</data><data key="node_observed_as_of">2025-01-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R123_E042"><data key="node_entity_id">R123_E042</data><data key="node_entity_type">records_disclosure_control</data><data key="node_canonical_name">OEIO Exclusive Certification of Tax Return and Earnings Records</data><data key="node_domain">Earnings / Legal Records</data><data key="node_description">Regional POMS says only SSA Office of Earnings and International Operations certifies earnings records and tax return information (including SEQ and DEQ).</data><data key="node_observed_status">regional_instruction_documented</data><data key="node_observed_as_of">2025-01-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E001"><data key="node_entity_id">R124_E001</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">IRS Form 1099-R Pension and Annuity Return Data in SSI Matching</data><data key="node_domain">SSI / IRS</data><data key="node_description">Pension interface uses SSNs on IRS Form 1099-R and income or retirement-account indicators for comparison with SSR; no individual address propagation established.</data><data key="node_observed_status">historically_documented_data_source</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E002"><data key="node_entity_id">R124_E002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI 5H Pension Alert Historical $12 Variance Criterion</data><data key="node_domain">SSI / Program Integrity</data><data key="node_description">2017 SI 02310.052 posts 5H when pension amount reported to IRS exceeds the comparable SSR unearned-income category by at least $12 for cases eligible from January of the tax year; subsequent cases use a no-entry criterion.</data><data key="node_observed_status">historical_rule_current_setting_unverified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Do not treat the 2017 $12 figure as a verified 2026 configuration.</data></node><node id="R124_E003"><data key="node_entity_id">R124_E003</data><data key="node_entity_type">workload_schedule</data><data key="node_canonical_name">SSI 5B 5H IRS Alert Release Calendar (October February June)</data><data key="node_domain">SSI / IRS</data><data key="node_description">2026 POMS SI 02305.017 lists 5B releases in October, February and June, and 5H with 5B workloads; 2017 SI 02310.045 lists a different IRS information-availability schedule.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">A schedule conflict exists across source revision dates; batch availability and workload release need not be identical.</data></node><node id="R124_E004"><data key="node_entity_id">R124_E004</data><data key="node_entity_type">query_screen</data><data key="node_canonical_name">SUMS MCAS MI Central SSN IRS SSID Workload Query</data><data key="node_domain">SSI / IRS</data><data key="node_description">POMS identifies SSN/IRS/SSID Query Screen under Workload Listing for RZs and LIs to retrieve IRS interface alert information.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E005"><data key="node_entity_id">R124_E005</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Continuing Type F Income Limited-Issue Selection</data><data key="node_domain">SSI / Workloads</data><data key="node_description">Monthly limited-issue releases for continuing Type F TANF/Title IV-E foster care income are identified with CRZD selection indicator F and no SSR diary.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E006"><data key="node_entity_id">R124_E006</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Annual NESE Limited-Issue April Selection</data><data key="node_domain">SSI / Earnings</data><data key="node_description">SSI cases needing prior-year net earnings from self-employment development appear as April limited issues with CRZD selection indicator C; no identifying SSR diary.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E007"><data key="node_entity_id">R124_E007</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Manual Goldberg Kelly Payment Continuation Limited Issue</data><data key="node_domain">SSI / Appeals</data><data key="node_description">Manual Goldberg/Kelly continuation cases require an LI in November, December or January to check appeals and benefit amounts; CRZD selection indicator G and K1 SSR diary.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E008"><data key="node_entity_id">R124_E008</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Goldberg Kelly K1 Appeal Continuation Diary</data><data key="node_domain">SSI / Appeals</data><data key="node_description">SSI POMS identifies K1 diary on SSR for certain manually continued benefits pending appeal.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E009"><data key="node_entity_id">R124_E009</data><data key="node_entity_type">historical_work_control</data><data key="node_canonical_name">SSI D6 Death Diary Previously Triggering Redetermination</data><data key="node_domain">SSI / Death</data><data key="node_description">D6 death diary no longer generates RZ or LI effective October 2005; included as historical status clarification, not a 2026 active control.</data><data key="node_observed_status">discontinued_2005</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E010"><data key="node_entity_id">R124_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Manual SSI Deemed-Income Annual October Workload Release</data><data key="node_domain">SSI / Workloads</data><data key="node_description">Manual deemed-income cases appear on a separate October read-only listing, not in MI Central and without SSR diary, for field-office COLA-related manual computations.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E011"><data key="node_entity_id">R124_E011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI RZ Recipient-Alleged Address Versus SSR Reconciliation</data><data key="node_domain">SSI / Address Provenance</data><data key="node_description">At redetermination ask recipient to state current residence address; compare against SSR and develop unreported moves or temporary absences instead of silently accepting an unmatched address.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E012"><data key="node_entity_id">R124_E012</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Unreported Move Date and Living-Arrangement Development</data><data key="node_domain">SSI / Address Provenance</data><data key="node_description">For unreported residence change, record new residence, dates of move, potential LA/ISM breakpoints and state supplement/Medicaid residence issues.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E013"><data key="node_entity_id">R124_E013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Temporary Absence Development for Unchanged SSR Residence</data><data key="node_domain">SSI / Address Provenance</data><data key="node_description">Where allegation and SSR mismatch but no unreported move occurred, follow temporary-absence development; not a verified change-of-address update.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E014"><data key="node_entity_id">R124_E014</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Living Arrangement Breakpoint Iteration for Address Change</data><data key="node_domain">SSI / Living Arrangements</data><data key="node_description">SSI Claims System requires separate living-arrangement iteration for relevant change-of-address breakpoint when developing LA/ISM.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E015"><data key="node_entity_id">R124_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI State Supplement and Medicaid Residence Review</data><data key="node_domain">SSI / Address Provenance</data><data key="node_description">Document residence changes for Medicaid and State supplementary payment treatment using appropriate regional instructions.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E016"><data key="node_entity_id">R124_E016</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Future Foreign-Travel Month-Before Field Office Diary</data><data key="node_domain">SSI / Residence</data><data key="node_description">During redetermination, set an FO diary for month before reported future foreign travel; source documents development of absences not change-of-address data propagation.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E017"><data key="node_entity_id">R124_E017</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Type-of-Residence Residential Versus Commercial Room Indicator</data><data key="node_domain">SSI / Living Arrangements</data><data key="node_description">2026 redetermination instructions require COMM or RES when a recipient resides in a room and record it on Residence Address and Jurisdiction page.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E018"><data key="node_entity_id">R124_E018</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI Recipient-Spouse Different Residence Indicator</data><data key="node_domain">SSI / Living Arrangements</data><data key="node_description">2026 type-of-residence instructions require REC or spouse annotation for different residences of eligible couple members.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E019"><data key="node_entity_id">R124_E019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Household New Member Protective Filing Assessment</data><data key="node_domain">SSI / Person Nexus</data><data key="node_description">During household composition review, consider whether person who moved in has a protective filing because they are age 65, blind or disabled.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E020"><data key="node_entity_id">R124_E020</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Household Expenses and Contributions Page</data><data key="node_domain">SSI / Living Arrangements</data><data key="node_description">For redetermination household-composition changes, SSA instructs staff to document material information on Household Expenses and Contributions page MS 08110.013.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E021"><data key="node_entity_id">R124_E021</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Non-Institutional Care Page</data><data key="node_domain">SSI / Living Arrangements</data><data key="node_description">Residence type Non-Institutional care activates SSI Claims Non-Institutional Care page; agency placement and payment information are documented.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E022"><data key="node_entity_id">R124_E022</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Non-Institutional Care Placing Agency and ISM Source Contact Information</data><data key="node_domain">SSI / Address Provenance</data><data key="node_description">SSI case may record placing agency information and caregiver name/address as source of in-kind support and maintenance, not as beneficiary mailing address.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E023"><data key="node_entity_id">R124_E023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">AFI Nonresponse 15-Day Alternative-Evidence Trigger</data><data key="node_domain">SSI / Financial Data</data><data key="node_description">Current policy allows alternate FI evidence after an FI fails to respond within 15 days to eAFI or e4641 request.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E024"><data key="node_entity_id">R124_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Foreign FI Account Without Domestic Sister Branch Verification Exception</data><data key="node_domain">SSI / Financial Data</data><data key="node_description">For foreign FI accounts without a domestic sister branch, bank records are accepted under source-specific limits rather than asserting all AFI queries cover foreign institutions.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E025"><data key="node_entity_id">R124_E025</data><data key="node_entity_type">evidence_route</data><data key="node_canonical_name">Claimant Upload Documents Bank Statement and Transaction History</data><data key="node_domain">SSI / Evidence</data><data key="node_description">SSA permits downloaded bank statements and transaction histories supplied through Upload Documents as alternative FI evidence; verification content may need whole-period coverage.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E026"><data key="node_entity_id">R124_E026</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI First-of-Month FI Balance Reconstruction from Transactions</data><data key="node_domain">SSI / Financial Data</data><data key="node_description">SSA permits deriving FOM balance from preceding month-end or sufficient transaction-level statements, with justified deductions/exclusions; not every reported bank balance is countable.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E027"><data key="node_entity_id">R124_E027</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">AFI Delayed Reply After SSI Adjudication Post-Eligibility Handling</data><data key="node_domain">SSI / Financial Data</data><data key="node_description">Alternative evidence can support adjudication while AFI verification remains pending; later electronic responses must be developed post-adjudicatively.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E028"><data key="node_entity_id">R124_E028</data><data key="node_entity_type">modernization_event_data</data><data key="node_canonical_name">SSI All-Award Financial Institution Verification Expansion May 2026</data><data key="node_domain">SSI / Program Integrity</data><data key="node_description">May 4 2026 mandatory AFI for all initial SSI allowances, reopenings and appeal reversals establishing initial eligibility, including blindness and disability, per official emergency message.</data><data key="node_observed_status">effective_2026_05_04</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E029"><data key="node_entity_id">R124_E029</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">eCBSV 2025 Performance Measurement Targets</data><data key="node_domain">Identity / Governance</data><data key="node_description">GAO records December 2025 established performance metrics for eCBSV uptime, response time, incident response time and enrollment processing plus goals for volumes, enrollment and cost.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E030"><data key="node_entity_id">R124_E030</data><data key="node_entity_type">planned_policy_change</data><data key="node_canonical_name">eCBSV Non-Permitted Entity Access Expansion Plan (2026)</data><data key="node_domain">Identity / Governance</data><data key="node_description">GAO states SSA supplied January 2026 plan to expand to non-permitted entities by June 2026; SSA public eligibility page still describes permitted-entity restrictions; plan is not proof of deployment.</data><data key="node_observed_status">plan_reported_deployment_unverified</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E031"><data key="node_entity_id">R124_E031</data><data key="node_entity_type">fee_schedule</data><data key="node_canonical_name">eCBSV April 2025 Annual Transaction-Tier Subscription Fee Schedule</data><data key="node_domain">Identity / Financial Administration</data><data key="node_description">SSA publishes volume-based annual subscription tiers effective April 7 2025; payment and access reflect tier limits rather than per-beneficiary identity records.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R124_E032"><data key="node_entity_id">R124_E032</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eCBSV Valid Agreement and Annual Tier Limit Enforcement</data><data key="node_domain">Identity / Data Exchange</data><data key="node_description">SSA eCBSV technical/enrollment guidance says a transaction beyond annual tier and without a current agreement is not processed; verification requires authentication and authorization.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E001"><data key="node_entity_id">R125_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">PIE Reconsideration Authorization Interruption and Reinstatement Gate</data><data key="node_domain">Title XVI / External Earnings</data><data key="node_description">When a timely reconsideration follows the month of an SSI denial, automated authorization can lapse; staff restore still-valid consent without obtaining a new signature in the documented circumstances.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Not all appeals maintain feed coverage; gaps require other wage evidence.</data></node><node id="R125_E002"><data key="node_entity_id">R125_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">PIE Authorized Prior-Month Payroll Retrieval Window</data><data key="node_domain">Title XVI / Earnings Exchange</data><data key="node_description">At the beginning of each month SSA requests the prior month of employer wages only from participating payroll providers when individual authorization is active; WEI accumulates information while consent is active.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E003"><data key="node_entity_id">R125_E003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">WEI Wage Repository IMAIN Technician Lookup</data><data key="node_domain">Title XVI / Wage Verification</data><data key="node_description">Authorized employees access payroll-provider wage information in the WEI repository using IMAIN search criteria; no physical platform or database product identified.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E004"><data key="node_entity_id">R125_E004</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">PIE Employer EIN Match Gate for Automatic SSI Wage Posting</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">PIE matches payroll-provider EIN to SSI Claims Wages-page EIN and conditionally posts wages through SSI claims to SSR before Goldberg-Kelly cutoff.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E005"><data key="node_entity_id">R125_E005</data><data key="node_entity_type">notice_process</data><data key="node_canonical_name">PIE Employer-Specific Reduced or Resumed Wage Reporting Notice</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">Automated notices alter wage reporting responsibilities for a participating employer, and the resumption notice follows three months without a provider wage feed.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E006"><data key="node_entity_id">R125_E006</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">CCE Payroll Data Provider Disposition Development Documentation Page</data><data key="node_domain">Title XVI / Claims / Earnings</data><data key="node_description">SSA identifies a CCE claims-development page retaining final dispositions of both PDP Pending Wage and PDP Pending Wage Report pages.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E007"><data key="node_entity_id">R125_E007</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">PIE Force-Due or Manual-Deeming Wage Exception</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">When an SSI case is in force-due or manual-deeming conditions, payroll information requires technician review and manual posting rather than unconditional SSR update.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E008"><data key="node_entity_id">R125_E008</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">PIE Disclaimed Employment and Wage Rejection Decision</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">The technician determines whether pending payroll wages belong to the beneficiary, updates or creates employer records as warranted, or rejects the report with documented reasons and related development.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E009"><data key="node_entity_id">R125_E009</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">OCSE S7 SSI Quarterly Overreported Wage Tolerance Rule</data><data key="node_domain">Title XVI / Earnings / Work Control</data><data key="node_description">S7 is an OCSE-to-SSR match where SSR reported wages exceed OCSE wages by at least approximately $250/quarter for a recipient or $500 for a deemor; exact threshold sign and inequalities follow POMS.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Existing S7 canonical name uses State Wage Match even though current operation compares OCSE state-collected data; do not rewrite historical row.</data></node><node id="R125_E010"><data key="node_entity_id">R125_E010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">OCSE S2 SSI Quarterly Underreported Wage Tolerance Rule</data><data key="node_domain">Title XVI / Earnings / Work Control</data><data key="node_description">S2 alerts when OCSE wage data exceed SSR wages beyond the documented quarterly tolerance, separate from the S7 overreported-wage direction.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E011"><data key="node_entity_id">R125_E011</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSIDPP Same-Name Same-Birth-Month-Year Candidate Rule</data><data key="node_domain">Title XVI / Person Identity</data><data key="node_description">Annual SSIDPP first selects potentially duplicate SSI recipient records using equal names and birth month/year before human review; the candidate criterion alone does not prove same person.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E012"><data key="node_entity_id">R125_E012</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSIDPP Field Office Same-Person Record Verification</data><data key="node_domain">Title XVI / Identity / Program Integrity</data><data key="node_description">Field office checks other case records and/or contacts individual or representative payee to verify whether two SSI records actually belong to the same person.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E013"><data key="node_entity_id">R125_E013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSIDPP Office of Systems to Central Operations to Field Office Referral</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">Office of Systems transmits selected case materials to Central Operations, which screens and assigns servicing field offices and regional case lists.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E014"><data key="node_entity_id">R125_E014</data><data key="node_entity_type">retention_control</data><data key="node_canonical_name">SSIDPP Different-Person Match Rejection and Case Material Destruction</data><data key="node_domain">Title XVI / Privacy / Identity</data><data key="node_description">When records selected for apparent duplication actually belong to different people, SSA instructs staff to take no record-correction action and destroy the candidate case material.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E015"><data key="node_entity_id">R125_E015</data><data key="node_entity_type">identity_attribution_rule</data><data key="node_canonical_name">BFS Savings Instrument Named Owner Overrides Displayed SSN</data><data key="node_domain">Title XVI / Treasury / Person</data><data key="node_description">Ownership follows the individual names appearing on savings bonds or securities, regardless of the SSN printed on the instrument; an alert is not proof by itself.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E016"><data key="node_entity_id">R125_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI SB Savings Security Aggregate Value and Two-Match Suppression Gate</data><data key="node_domain">Title XVI / Resources / Work Control</data><data key="node_description">PE ODS SB alert is controlled by total redemption value at or above $1,000 across individuals on an SSR and is suppressed if alerted in either of prior two matches, per current policy text.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Source includes historical examples; do not infer low-level scheduling deployment remains unchanged.</data></node><node id="R125_E017"><data key="node_entity_id">R125_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI SB Savings Bond Ownership Verification Form Package</data><data key="node_domain">Title XVI / External Financial Evidence</data><data key="node_description">Where ownership is material and denied, SSA sends a routed SSA-562-U3 with signed SSA-8510 and a redacted savings security alert for BFS verification.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E018"><data key="node_entity_id">R125_E018</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI SB MSSICS DSAB Versus Non-MSSICS SSR Remarks Disposition</data><data key="node_domain">Title XVI / Resources / Data Provenance</data><data key="node_description">MSSICS uses DSAB and relevant financial pages plus RE21 code; non-MSSICS records use SSR remarks and direct input including payment status where necessary.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E019"><data key="node_entity_id">R125_E019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI E2 Annual COLA Rental Subsidy Reverification Process</data><data key="node_domain">Title XVI / Residence / Living Arrangements</data><data key="node_description">Annual COLA processing creates SSI rental subsidy work when existing rental subsidies remain relevant; staff develop current rent and current market rental value and create an annual living-arrangement period.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E020"><data key="node_entity_id">R125_E020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI E2 Diary Two-Attempt Thirty-Day Unresponsive-Landlord Control</data><data key="node_domain">Title XVI / Residence / Work Control</data><data key="node_description">After two unsuccessful information requests and 30 days, employee documents attempts on a Report of Contact and may clear the E2 diary using UDIA before closing LI/RZ.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E021"><data key="node_entity_id">R125_E021</data><data key="node_entity_type">historical_external_data_attribute</data><data key="node_canonical_name">BFS Pre-January-1974 Series E Bond Registration Name-and-Purchase-Address Key</data><data key="node_domain">Address Provenance / Treasury</data><data key="node_description">For certain older Series E securities BFS historical registration indexes use owner name and address supplied at bond purchase; these are Treasury historical registration addresses, not verified SSA program mailing addresses.</data><data key="node_observed_status">historical_source_rule_documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">POMS describes registration index for older bonds; do not infer SSA persistently ingests addresses from BFS.</data></node><node id="R125_E022"><data key="node_entity_id">R125_E022</data><data key="node_entity_type">historical_external_data_attribute</data><data key="node_canonical_name">BFS Post-January-1974 Treasury Savings Security Owner-SSN Registration Index</data><data key="node_domain">Person Identity / Treasury</data><data key="node_description">For Series E since January 1974 and EE/H/HH savings bonds, POMS describes records indexed by owner or first named joint owner SSN; historic rule not a Numident update.</data><data key="node_observed_status">historical_source_rule_documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E023"><data key="node_entity_id">R125_E023</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRS Treasury-Interest Alert Security Ownership and Provenance Development</data><data key="node_domain">Title XVI / IRS / Treasury</data><data key="node_description">Interest alert from U.S. Treasury securities requires assessment of issuer, redemption, ownership and historical contact information; financial institution or BFS can verify material disputed items.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E024"><data key="node_entity_id">R125_E024</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">DMS Debtor Contact Address Attribute under 2018 PIA</data><data key="node_domain">Payments / Debt / Address Provenance</data><data key="node_description">2018 SSA DMS PIA expressly lists debtor name, address and SSN along with debt actions, amounts, collection methods and due-process requests; it does not identify an originating master-record update path.</data><data key="node_observed_status">historical_2018_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Evidence of collection/use by DMS, not evidence of current address quality or update rules.</data></node><node id="R125_E025"><data key="node_entity_id">R125_E025</data><data key="node_entity_type">security_control</data><data key="node_canonical_name">DMS 2018 Need-to-Know Profiles and Audit Transaction Control</data><data key="node_domain">Debt / Identity / Governance</data><data key="node_description">2018 PIA describes SSA network credential or PIV authentication, system access profiles, need-to-know authorization and sensitive-transaction audit mechanisms.</data><data key="node_observed_status">historical_2018_pia</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E026"><data key="node_entity_id">R125_E026</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot August 2026 Table 1 Unduplicated OASDI-SSI Population</data><data key="node_domain">Statistics / Publication / Person</data><data key="node_description">September 2026 release shows August2026 unduplicated OASDI-only, SSI-only and both program population, sourced to 100-percent MBR and SSR data.</data><data key="node_observed_status">published_2026_09</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Publication-level overlap counts do not identify a physical enterprise Person repository or reveal exact join implementation.</data></node><node id="R125_E027"><data key="node_entity_id">R125_E027</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot August 2026 Table 2 OASDI Benefits</data><data key="node_domain">Statistics / Title II</data><data key="node_description">September 2026 release provides monthly payment aggregates and recipient categories using 100-percent Master Beneficiary Record data.</data><data key="node_observed_status">published_2026_09</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E028"><data key="node_entity_id">R125_E028</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">Monthly Statistical Snapshot August 2026 Table 3 SSI Recipients</data><data key="node_domain">Statistics / Title XVI</data><data key="node_description">September 2026 release provides August recipient, payment and age-band aggregates using 100-percent Supplemental Security Record data.</data><data key="node_observed_status">published_2026_09</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E029"><data key="node_entity_id">R125_E029</data><data key="node_entity_type">publication_business_rule</data><data key="node_canonical_name">Monthly Statistical Snapshot Dual-Entitlement Person Count Suppression Rule</data><data key="node_domain">Person / Statistical Aggregation</data><data key="node_description">SSA counts people with primary and secondary benefit entitlements only once in monthly published beneficiary table; this is a statistical dedup rule, not evidence of a persistent Person master database.</data><data key="node_observed_status">published_2026_09</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E030"><data key="node_entity_id">R125_E030</data><data key="node_entity_type">identity_data_quality_rule</data><data key="node_canonical_name">Numident Documented Original Keying Error Non-Iterative Correction Rule</data><data key="node_domain">Enumeration / Person</data><data key="node_description">A keying error proved against original SS-5 or qualified partner-origin evidence can use SSNAP Numident Correction Processing without creating another Numident iteration.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E031"><data key="node_entity_id">R125_E031</data><data key="node_entity_type">identity_lifecycle_rule</data><data key="node_canonical_name">Numident Unproven-Keying-Error New Application Iteration Rule</data><data key="node_domain">Enumeration / Person</data><data key="node_description">Without original keying-error evidence, documented update requires new SSN application and supporting evidence; appends Numident iteration rather than overwriting original one.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E032"><data key="node_entity_id">R125_E032</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Numident Parent Name Change Conditional Benefit and Payee Review</data><data key="node_domain">Person / Interrecord Update</data><data key="node_description">Parent name corrections require technician to inquire whether parent is TitleII beneficiary, SSI recipient or payee and, if so, separately review MBR, SSR and RPS records.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R125_E033"><data key="node_entity_id">R125_E033</data><data key="node_entity_type">procurement_data_product</data><data key="node_canonical_name">SSA FY2026 Contracting Opportunity Forecast June 2026 Workbook</data><data key="node_domain">Procurement / Market Intelligence</data><data key="node_description">Official SSA OSDBU FY26 contract forecast linked as June22 2026 XLSM; catalog confirms forecast publication but does not independently validate its rows or any awarded contracts.</data><data key="node_observed_status">published_forecast_only</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Official workbook URL present; browser could not parse binary XLSM. Do not assert awards, future obligations or technical products based on forecast.</data></node><node id="R126_E001"><data key="node_entity_id">R126_E001</data><data key="node_entity_type">application</data><data key="node_canonical_name">Vital Records Request Application</data><data key="node_acronym">VRR</data><data key="node_domain">Evidence Procurement / Internal Administration</data><data key="node_description">SSA internal application used to submit and track purchases of state and local vital records after February 2026. The source establishes a request form, stages, and centralized documentation but does not identify vendor, hosting, persistence engine, or transport.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E002"><data key="node_entity_id">R126_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Centralized Vital Records Purchase Workflow (2026)</data><data key="node_domain">Evidence Procurement / Vital Records</data><data key="node_description">Field office submits request, SSA Travel Team checks and places orders, custodians return records to the requesting SSA office, which confirms receipt. Applicable where SmartPay purchase card is unavailable.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E003"><data key="node_entity_id">R126_E003</data><data key="node_entity_type">form</data><data key="node_canonical_name">Vital Records Request Submission Form</data><data key="node_domain">Evidence Procurement / Vital Records</data><data key="node_description">Request in Vital Records Request application includes beneficiary or recipient details, record type and purpose, required proof of identification, and vital-record custodian identity and address.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E004"><data key="node_entity_id">R126_E004</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Vital Records Request Three-Stage Status</data><data key="node_domain">Evidence Procurement / Work Control</data><data key="node_description">Vital-record request status exposed to requesting SSA offices: Requested, Ordered, or Received.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E005"><data key="node_entity_id">R126_E005</data><data key="node_entity_type">evidence_artifact</data><data key="node_canonical_name">Vital Records Request Central Supporting Documentation</data><data key="node_domain">Evidence Procurement / Governance</data><data key="node_description">Forms, ID evidence, payment documentation, and correspondence centrally held on the Vital Records Request site; retention follows agency records policy, exact schedule unverified.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E006"><data key="node_entity_id">R126_E006</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">State Vital-Record Custodian Request Contact Address</data><data key="node_domain">Address Provenance / External Partners</data><data key="node_description">State or local vital-record custodian name and postal address captured as request metadata; not a beneficiary current address.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E007"><data key="node_entity_id">R126_E007</data><data key="node_entity_type">organizational_unit</data><data key="node_canonical_name">SSA Travel Team (Vital Records Ordering Function)</data><data key="node_domain">Administrative Payments</data><data key="node_description">SSA travel/payment function reviews vital-record submissions, places orders, maintains request statuses, and requests receipt confirmation; not evidence of a technology vendor.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E008"><data key="node_entity_id">R126_E008</data><data key="node_entity_type">organizational_unit</data><data key="node_canonical_name">SSA Internal Control Payment Team (Vital Records Treasury Check Exception)</data><data key="node_domain">Administrative Payments</data><data key="node_description">SSA payment team may request Treasury check when card payment and other options are not available; check goes to SSA Travel Team.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E009"><data key="node_entity_id">R126_E009</data><data key="node_entity_type">payment_capability</data><data key="node_canonical_name">Government SmartPay Purchase Card Route for SSA Vital Records</data><data key="node_domain">Federal Procurement / Evidence</data><data key="node_description">Preferred card-payment route for purchasing vital records where agency personnel have card authority and state record custodians accept payment cards. Not an SSA-specific database.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E010"><data key="node_entity_id">R126_E010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2026 Vital Records TPPS Paper-Check Retirement Control</data><data key="node_domain">Modernization / Treasury Payments</data><data key="node_description">Effective 2026-02-09, SSA eliminated paper-check issuance through TPPS for purchasing vital records, subject to government purchase-card and Treasury check exception procedures.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E011"><data key="node_entity_id">R126_E011</data><data key="node_entity_type">public_software</data><data key="node_canonical_name">OACT Social Security Detailed Benefit Calculator</data><data key="node_acronym">AnyPIA</data><data key="node_domain">Actuarial / Benefits Estimation</data><data key="node_description">Publicly downloadable SSA actuarial benefit estimator for historical and projected old-age, survivor, and disability claims; not the official SSA benefit adjudication calculator.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E012"><data key="node_entity_id">R126_E012</data><data key="node_entity_type">software_release</data><data key="node_canonical_name">OACT Detailed Calculator Release 2026.2</data><data key="node_acronym">AnyPIA 2026.2</data><data key="node_domain">Actuarial / Public Data Products</data><data key="node_description">Detailed Calculator version released 2026-07-13 with projected wage and benefit growth assumptions from 2026 Trustees Report; does not establish internal SSA production deployment.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E013"><data key="node_entity_id">R126_E013</data><data key="node_entity_type">model_input</data><data key="node_canonical_name">OACT Detailed Calculator Historical Parameters and Trustees Assumptions</data><data key="node_domain">Actuarial / Public Estimate Assumptions</data><data key="node_description">Calculator historical benefit and wage parameters may be updated manually, but Trustees projection assumptions require the current downloaded release to remain aligned.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E014"><data key="node_entity_id">R126_E014</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Detailed Calculator PIA and Family Maximum Benefit Output</data><data key="node_domain">Actuarial / Public Benefit Estimates</data><data key="node_description">Public calculator computes primary insurance amount, maximum family benefit, reduction or delayed retirement factor and monthly estimated benefit; not a legally controlling determination.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E015"><data key="node_entity_id">R126_E015</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">OACT Detailed Calculator Case Input Record</data><data key="node_domain">Actuarial / Public Benefit Estimates</data><data key="node_description">Public calculator accepts worker date of birth, earnings history, selected benefit type and other case attributes; batch tools consume case files.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E016"><data key="node_entity_id">R126_E016</data><data key="node_entity_type">software_source_release</data><data key="node_canonical_name">OACT Detailed Calculator Public C++ Source Distribution</data><data key="node_domain">Actuarial / Public Code</data><data key="node_description">SSA distributes public calculator C++ source for Windows and legacy Mac variants; includes calculation and windowing code, distinct from internal adjudication code.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E017"><data key="node_entity_id">R126_E017</data><data key="node_entity_type">software_dependency</data><data key="node_canonical_name">Boost C++ Libraries in Public AnyPIA Build</data><data key="node_domain">Actuarial / Public Code</data><data key="node_description">OACT public source documentation identifies Boost C++ dependencies, Windows build using Boost 1.81.0 and historic Mac build 1.33.1; not evidence of enterprise deployment.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E018"><data key="node_entity_id">R126_E018</data><data key="node_entity_type">software_build_configuration</data><data key="node_canonical_name">AnyPIA Windows Visual C++ 2022 Build</data><data key="node_domain">Actuarial / Public Code</data><data key="node_description">Public Windows AnyPIA calculator source is compiled with Microsoft Visual C/C++ 2022, with oactobjs32 and anypia32 project directories.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E019"><data key="node_entity_id">R126_E019</data><data key="node_entity_type">legacy_public_software</data><data key="node_canonical_name">OACT Historical Fortran Benefit Estimator Source</data><data key="node_domain">Actuarial / Historical Public Code</data><data key="node_description">OACT describes an older public Fortran implementation not updated for years. Historic files reference MS-DOS, Unix, IBM mainframe compatibility; this does not establish agency production use.</data><data key="node_observed_status">historical_public_code</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R126_E020"><data key="node_entity_id">R126_E020</data><data key="node_entity_type">public_software</data><data key="node_canonical_name">OACT anypiab Multi-Case Batch Calculator</data><data key="node_acronym">anypiab</data><data key="node_domain">Actuarial / Batch Analysis</data><data key="node_description">Public console calculator reads multiple case records from one .pia file and produces estimated benefit results in a file called OUTPUT.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E021"><data key="node_entity_id">R126_E021</data><data key="node_entity_type">public_software</data><data key="node_canonical_name">OACT anypiac Per-Case Batch Calculator</data><data key="node_acronym">anypiac</data><data key="node_domain">Actuarial / Batch Analysis</data><data key="node_description">Public console calculator reads a list of individual case-file names and generates batch benefit estimates; not a live program-to-SSA database exchange.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E022"><data key="node_entity_id">R126_E022</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">AnyPIA Batch OUTPUT Benefit-Estimate File</data><data key="node_domain">Actuarial / Batch Analysis</data><data key="node_description">Documented batch output includes SSN and DOB from supplied case data, PIA, family maximum, benefit amount, insured status and additional family-member lines where applicable.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E023"><data key="node_entity_id">R126_E023</data><data key="node_entity_type">systems_limitation</data><data key="node_canonical_name">DDS S1 Res Judicata Denial Processing Limitation</data><data key="node_domain">Disability / Title II</data><data key="node_description">Current POMS says DDS cannot input S1 subsequent-claim res judicata denials directly; returns case to field office for processing by MCS EC or MACADE.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E024"><data key="node_entity_id">R126_E024</data><data key="node_entity_type">case_attribute</data><data key="node_canonical_name">SSA-831-U3 Item 35 S1 Denial Basis Code</data><data key="node_domain">Disability / Adjudication Evidence</data><data key="node_description">DDS enters S1 basis code in item 35 of SSA-831-U3 for res judicata determination and returns case for field-office system action.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E025"><data key="node_entity_id">R126_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Field-Office S1 Disability Denial Follow-On Posting</data><data key="node_domain">Disability / Title II</data><data key="node_description">Field office processes DDS S1 denial through MCS Earnings Computation where possible or through MACADE when excluded.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E026"><data key="node_entity_id">R126_E026</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI-Concurrent Childhood Disability Benefit Manual Conversion Exception</data><data key="node_domain">Disability / Title II-XVI</data><data key="node_description">For age-18 child-to-CDB conversion while child receives SSI, POMS directs processing-center manual action rather than assuming POS automatic conversion.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E027"><data key="node_entity_id">R126_E027</data><data key="node_entity_type">external_evidence_process</data><data key="node_canonical_name">U.S. Department of State Consular Vital Records Evidence Request</data><data key="node_domain">Enumeration / International Vital Records</data><data key="node_description">POMS GN 00308.235 describes requests for FS-240 birth records and DS-2060 death reports of citizens abroad from DOS Passport Vital Records Section.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E028"><data key="node_entity_id">R126_E028</data><data key="node_entity_type">external_evidence_artifact</data><data key="node_canonical_name">Consular Report of Birth Abroad FS-240</data><data key="node_acronym">FS-240</data><data key="node_domain">Identity / Vital Records</data><data key="node_description">Department of State report of birth of U.S. citizen abroad; requesting agency may receive government-use evidence under specified conditions.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E029"><data key="node_entity_id">R126_E029</data><data key="node_entity_type">external_evidence_artifact</data><data key="node_canonical_name">Report of Death of a U.S. Citizen Abroad DS-2060</data><data key="node_acronym">DS-2060</data><data key="node_domain">Identity / Death Records</data><data key="node_description">Department of State consular report of death of U.S. citizen abroad, listed in vital-record source instructions.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E030"><data key="node_entity_id">R126_E030</data><data key="node_entity_type">information_control</data><data key="node_canonical_name">Department of State Vital Record Government-Use Marking</data><data key="node_domain">Vital Records / Source Restrictions</data><data key="node_description">POMS explains that government-use records furnished in certain free-of-charge SSA evidence requests are marked Government Use Only or For SSA Use Only.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R126_E031"><data key="node_entity_id">R126_E031</data><data key="node_entity_type">public_service_change</data><data key="node_canonical_name">2026 Freedom 250 Enumeration-at-Birth Commemorative Card Design</data><data key="node_domain">Enumeration / Identity Lifecycle</data><data key="node_description">SSA states the Freedom 250 SSN card design applies only to original Enumeration-at-Birth cards for qualifying newborns during July 2 through December 31, 2026; standard EAB process and data provenance unchanged.</data><data key="node_observed_status">temporary_2026_service</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E001"><data key="node_entity_id">R127_E001</data><data key="node_entity_type">public_calculator</data><data key="node_canonical_name">OACT Social Security Quick Calculator</data><data key="node_domain">actuarial/public_services</data><data key="node_description">Public rough retirement, disability and survivor benefit estimate calculator; derives assumed earnings from user-entered birth date and current-year earnings rather than looking up the user’s official earnings record.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Not SSA production award or payment computation.</data></node><node id="R127_E002"><data key="node_entity_id">R127_E002</data><data key="node_entity_type">calculated_data</data><data key="node_canonical_name">Quick Calculator Assumed Historical Earnings Profile</data><data key="node_domain">actuarial/public_services</data><data key="node_description">Approximate prior covered earnings derived from current-year earnings assumption; user may examine and revise assumptions.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E003"><data key="node_entity_id">R127_E003</data><data key="node_entity_type">public_calculator</data><data key="node_canonical_name">OACT Online Benefits Calculator</data><data key="node_domain">actuarial/public_services</data><data key="node_description">Public retirement benefit calculator requiring the user to enter annual lifetime earnings manually; separate from authenticated personal Social Security account estimates and downloadable AnyPIA.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E004"><data key="node_entity_id">R127_E004</data><data key="node_entity_type">user_provided_data</data><data key="node_canonical_name">OACT Public Manually Entered Annual Earnings Inputs</data><data key="node_domain">actuarial/public_services</data><data key="node_description">Year-by-year earnings supplied by a public calculator user instead of retrieved from authenticated SSA earnings records.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E005"><data key="node_entity_id">R127_E005</data><data key="node_entity_type">public_calculator</data><data key="node_canonical_name">OACT Life Expectancy Calculator</data><data key="node_domain">actuarial/public_services</data><data key="node_description">SSA public life expectancy calculator using age or date of birth and sex to estimate average additional years; statistical estimate not an individual medical determination.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E006"><data key="node_entity_id">R127_E006</data><data key="node_entity_type">published_calculation</data><data key="node_canonical_name">OACT Public Life Expectancy Estimate</data><data key="node_domain">actuarial/statistics</data><data key="node_description">Public age/sex-based statistical lifespan estimate; not a personal eligibility or actuarial forecasting master file.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E007"><data key="node_entity_id">R127_E007</data><data key="node_entity_type">public_data_tool</data><data key="node_canonical_name">OACT Indexing Factors for Earnings Publication Tool</data><data key="node_domain">actuarial/statistics</data><data key="node_description">Publicly published annual indexing factors for earnings, reflecting indexed wage benchmark ratios for eligibility years; not evidence of SSA production computation engine technology.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E008"><data key="node_entity_id">R127_E008</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OACT Public Indexed Earnings Factors by Eligibility Year</data><data key="node_domain">actuarial/statistics</data><data key="node_description">SSA published factors for indexing historical covered earnings using the national average wage indexing series.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E009"><data key="node_entity_id">R127_E009</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">OACT Calculator Channel-Specific Earnings Provenance Rule</data><data key="node_domain">actuarial/identity</data><data key="node_description">Separates account-authenticated earnings-based retirement estimates from public calculator assumptions and user-supplied annual earnings.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E010"><data key="node_entity_id">R127_E010</data><data key="node_entity_type">governance_data</data><data key="node_canonical_name">SSA FY2027 Non-Program Records Fee Schedule</data><data key="node_domain">identity/privacy</data><data key="node_description">Federal Register fee schedule for specified non-program records received beginning October 1, 2026, including original SS-5 ($23), Numident extract ($22), detailed earnings SSA-7050 ($49), and certified copies/requests.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E011"><data key="node_entity_id">R127_E011</data><data key="node_entity_type">disclosure_data_product</data><data key="node_canonical_name">Numident Computer Extract Provided for Records Requests</data><data key="node_domain">identity/privacy</data><data key="node_description">Requested computer extract of SS-5 information from Numident, separately charged from an original SS-5 copy; disclosure is not a correction transaction.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E012"><data key="node_entity_id">R127_E012</data><data key="node_entity_type">disclosure_data_product</data><data key="node_canonical_name">Original SS-5 Application Copy Disclosure</data><data key="node_domain">identity/privacy</data><data key="node_description">Requested original Social Security card application reproduction distinct from a Numident electronic extract; subject to eligibility, privacy and fee rules.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E013"><data key="node_entity_id">R127_E013</data><data key="node_entity_type">disclosed_attribute_set</data><data key="node_canonical_name">SSA-7050 Detailed Earnings Employer Names and Addresses</data><data key="node_domain">earnings/address_provenance</data><data key="node_description">Detailed yearly earnings disclosure contains names and addresses of employers, while free uncertified online yearly earnings statements omit employer identification.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E014"><data key="node_entity_id">R127_E014</data><data key="node_entity_type">service_workflow</data><data key="node_canonical_name">SSA Deceased-Individual SS-5 and Numident FOIA Request Route</data><data key="node_domain">identity/privacy</data><data key="node_description">Deceased-person record request intake through documented SSA-711 and FOIAXpress Public Access Link, with request and eligibility review; not automatic data extraction into program records.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E015"><data key="node_entity_id">R127_E015</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">RASR Single-SSN Multiple-Case Appointment Limitation</data><data key="node_domain">hearings/identity</data><data key="node_description">RASR cannot maintain two individual cases under same number holder SSN for a contemporaneous subsequent claim; employees use MCS or MSSICS to enter the correct appointed representative per case.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E016"><data key="node_entity_id">R127_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Subsequent SSA Claim Representative Appointment Reauthorization</data><data key="node_domain">hearings/representative</data><data key="node_description">A subsequent claim ordinarily requires its own Form SSA-1696; an earlier claim appointment must not be assumed to extend to a new claim.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E017"><data key="node_entity_id">R127_E017</data><data key="node_entity_type">workflow_flag</data><data key="node_canonical_name">EDCS Representative Involved Electronic-Folder Flag</data><data key="node_domain">disability/evidence</data><data key="node_description">Field-office control marking disability electronic claims files as having an appointed representative; staff ensure flag follows applicable case and update after transfer when required.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E018"><data key="node_entity_id">R127_E018</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RASR Principal Representative Notice Routing</data><data key="node_domain">hearings/notifications</data><data key="node_description">For cases with multiple appointed representatives, SSA directs notice/development to designated principal representative and documents the selection; there is a temporary most-recent-appointment fallback when claimant cannot be reached.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E019"><data key="node_entity_id">R127_E019</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">RASR Missing Claimant Address Notice Fallback</data><data key="node_domain">address_provenance/notifications</data><data key="node_description">If RASR fails to issue acknowledgment because claimant address is missing, technicians use DPS/Manage Text Aurora manual acknowledgment.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E020"><data key="node_entity_id">R127_E020</data><data key="node_entity_type">notification</data><data key="node_canonical_name">RASR Representative Entity Fee-Assignment Notice RSR120</data><data key="node_domain">representative/fees</data><data key="node_description">SSA sends notice RSR120 to an affiliated entity when a representative requests assignment of direct authorized fees; rejected entity registration or EIN requires manual DPS notice.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E021"><data key="node_entity_id">R127_E021</data><data key="node_entity_type">master_record_attribute</data><data key="node_canonical_name">MBR Supplemental Income Data SID Line</data><data key="node_domain">title_ii/medicare</data><data key="node_description">Title II Master Beneficiary Record Supplemental Income Data (SID) line showing SSI status (including SISC status codes) used for state Medicare buy-in.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E022"><data key="node_entity_id">R127_E022</data><data key="node_entity_type">program_data_record</data><data key="node_canonical_name">Medicare Buy-In Third-Party Master Record</data><data key="node_domain">medicare/exchanges</data><data key="node_description">Third Party Master (TPM) record for Medicare state buy-in updated from MBR SID status in auto-accrete states, subject to controlled reconciliation.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E023"><data key="node_entity_id">R127_E023</data><data key="node_entity_type">external_exchange_artifact</data><data key="node_canonical_name">State Medicare Buy-In Accretion or Deletion Alert Record</data><data key="node_domain">medicare/exchanges</data><data key="node_description">Status-change alert furnished to state Medicaid buy-in authorities in alert states, depending on corrected MBR SID line.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E024"><data key="node_entity_id">R127_E024</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">State Buy-In SID-to-Third-Party 60-Day Reconciliation Diary</data><data key="node_domain">medicare/operations</data><data key="node_description">For auto-accrete states, field office diaries case 60 days after SID correction and checks whether MBR Third Party line reflects the correction; sends request to processing center if it does not.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E025"><data key="node_entity_id">R127_E025</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI IRS 5B Alert Discovery-Date Provenance Control</data><data key="node_domain">title_xvi/irs</data><data key="node_description">SSI reopening controls require the relevant date of discovered IRS 5B alert evidence or diary/query records; the IRS observation/alert date is not a verified beneficiary address-update date.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E026"><data key="node_entity_id">R127_E026</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2023 OASDI State and ZIP Publication July 2025 Corrected Edition</data><data key="node_domain">enterprise_data/geospatial</data><data key="node_description">Corrected 2023 OASDI beneficiary ZIP code and field-office totals, public release December 2024 and errata posted July 1, 2025 for NY 10506/10509/10590 and NC 27343.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Source records an erratum to the 2023 report, not a modification to the 2026 payment/beneficiary master file.</data></node><node id="R127_E027"><data key="node_entity_id">R127_E027</data><data key="node_entity_type">statistical_privacy_control</data><data key="node_canonical_name">OASDI ZIP Publication Small-Cell Suppression and Controlled Rounding</data><data key="node_domain">enterprise_data/privacy</data><data key="node_description">For 2023 ZIP-level OASDI statistics, suppress ZIP codes with fewer than 15 beneficiaries; counts use controlled rounding to a multiple of five with deviation less than five.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R127_E028"><data key="node_entity_id">R127_E028</data><data key="node_entity_type">procurement_data_product</data><data key="node_canonical_name">SSA FY2026 Small Business Prime and Subcontracting Goals</data><data key="node_domain">procurement/governance</data><data key="node_description">Official SSA FY2026 small business acquisition goals: 36.63 percent prime, 34.89 percent subcontracting; related socioeconomic-category goals are 5 percent each except HUBZone at 3 percent.</data><data key="node_observed_status">documented_as_of_observation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Goals are planned targets, not achieved spend, contract award, or vendor technology deployment.</data></node><node id="R128_E001"><data key="node_entity_id">R128_E001</data><data key="node_entity_type">research_dataset</data><data key="node_canonical_name">Disability Analysis File 2022 Research Release</data><data key="node_domain">research/data_products</data><data key="node_description">Historical DAF22 research dataset documented in April 2024, covering SSA disability-program histories through December 2022; not a live adjudication record.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E002"><data key="node_entity_id">R128_E002</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">SSI Characteristics Extract Record 100% Monthly Snapshot</data><data key="node_acronym">CER</data><data key="node_domain">Title_XVI/data</data><data key="node_description">Monthly SSI program snapshot derived from SSR. Includes selected demographic data such as addresses and resources; snapshots are not retrospectively updated.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E003"><data key="node_entity_id">R128_E003</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">Disabled Beneficiary and Dependents Monthly Snapshot Extract</data><data key="node_acronym">DBAD</data><data key="node_domain">Title_II/data</data><data key="node_description">Monthly OASDI disabled-beneficiary and dependent snapshot extracted from MBR; records are not retrospectively refreshed.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E004"><data key="node_entity_id">R128_E004</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">SSI Longitudinal File</data><data key="node_acronym">SSI-LF</data><data key="node_domain">Title_XVI/statistics</data><data key="node_description">Longitudinal and one-time SSI program history from SSR, including household types, benefit and earnings information; DAF22 extracted it April 2023.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E005"><data key="node_entity_id">R128_E005</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">DAF22 Supplemental Security Record Earnings Custom Extract</data><data key="node_domain">Title_XVI/research</data><data key="node_description">2023 custom SSR earnings extract for DAF22 supplementing standard SSI longitudinal and monthly snapshot files.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E006"><data key="node_entity_id">R128_E006</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">DAF22 Supplemental Security Record Additional Variables Extract</data><data key="node_domain">Title_XVI/research</data><data key="node_description">Custom SSR extract of additional variables not included in the SSI Longitudinal File for the DAF22 build.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E007"><data key="node_entity_id">R128_E007</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">SSA-831 Initial Disability Decision Administrative File</data><data key="node_domain">disability/decisions</data><data key="node_description">Archived DDS initial medical decision records represented on SSA-831 and keyed for research using program-specific SSN and BIC semantics.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E008"><data key="node_entity_id">R128_E008</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">SSA-832 and SSA-833 CDR Decision Administrative Files</data><data key="node_domain">disability/CDR</data><data key="node_description">Archived medical continuing-disability decision records from SSA-832 (SSI) and SSA-833 (SSDI). These do not cover work-only CDRs.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E009"><data key="node_entity_id">R128_E009</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">DAF22 MBR and PHUS Combined Payment Extract</data><data key="node_domain">Title_II/payments</data><data key="node_description">Extract combines MBR with PHUS payment history; PHUS contains actual cash disbursement event timing distinct from MBR entitlement/payment information.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E010"><data key="node_entity_id">R128_E010</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">CER SSI Historical Snapshot Address Attribute</data><data key="node_domain">person/address_provenance</data><data key="node_description">Address captured in SSI monthly CER extraction at a point in time; stale historical copy when later SSR address changes and no retroactive correction in the original snapshot.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Do not infer live record updates from research snapshot.</data></node><node id="R128_E011"><data key="node_entity_id">R128_E011</data><data key="node_entity_type">logical_identifier</data><data key="node_canonical_name">SSI Person Account Number Identifier (PAN)</data><data key="node_acronym">PAN</data><data key="node_domain">person/identity</data><data key="node_description">SSN identifying an individual person inside SSI SSR/CER records; may differ from record HUN when an eligible couple is housed under one record.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E012"><data key="node_entity_id">R128_E012</data><data key="node_entity_type">logical_identifier</data><data key="node_canonical_name">SSI Housed Under Number Identifier (HUN)</data><data key="node_acronym">HUN</data><data key="node_domain">person/identity</data><data key="node_description">SSR record filing key: beneficiary SSN or one eligible spouse’s SSN; potentially represents multiple individuals on one SSR record.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E013"><data key="node_entity_id">R128_E013</data><data key="node_entity_type">logical_identifier</data><data key="node_canonical_name">Title II Claim Account Number Identifier (CAN)</data><data key="node_acronym">CAN</data><data key="node_domain">person/identity</data><data key="node_description">MBR account filing key: SSN of wage earner on whose record benefits are entitled; not necessarily beneficiary’s own SSN.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E014"><data key="node_entity_id">R128_E014</data><data key="node_entity_type">logical_identifier</data><data key="node_canonical_name">Title II Beneficiary Own Account Number Identifier (BOAN)</data><data key="node_acronym">BOAN</data><data key="node_domain">person/identity</data><data key="node_description">MBR beneficiary’s own SSN used to distinguish worker from auxiliary beneficiary under the worker’s CAN and BIC.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E015"><data key="node_entity_id">R128_E015</data><data key="node_entity_type">logical_identifier</data><data key="node_canonical_name">DCF Claimant Own Social Security Number Identifier (COSSN)</data><data key="node_acronym">COSSN</data><data key="node_domain">person/identity</data><data key="node_description">Claimant own SSN used to file the Disability Control File across SSDI and SSI beneficiaries.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E016"><data key="node_entity_id">R128_E016</data><data key="node_entity_type">research_dataset_component</data><data key="node_canonical_name">DAF22 Demographic Component</data><data key="node_domain">research/DAF</data><data key="node_description">Central demographic DAF22 component linking program populations and research analytical files.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E017"><data key="node_entity_id">R128_E017</data><data key="node_entity_type">research_dataset_component</data><data key="node_canonical_name">DAF22 Annual Research Component</data><data key="node_domain">research/DAF</data><data key="node_description">Annualized disability program variables for historical years through 2022.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E018"><data key="node_entity_id">R128_E018</data><data key="node_entity_type">research_dataset_component</data><data key="node_canonical_name">DAF22 Ticket to Work Research Component</data><data key="node_domain">research/DAF</data><data key="node_description">Historical research component recording Ticket to Work program participation.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E019"><data key="node_entity_id">R128_E019</data><data key="node_entity_type">research_dataset_component</data><data key="node_canonical_name">DAF22 Payment Research Component</data><data key="node_domain">research/DAF</data><data key="node_description">Historical provider payments component built using EN cumulative payments and VRRMS extract information.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E020"><data key="node_entity_id">R128_E020</data><data key="node_entity_type">research_data_mart</data><data key="node_canonical_name">DAF22 Ten Percent Research Data Mart</data><data key="node_acronym">DAF10</data><data key="node_domain">research/DAF</data><data key="node_description">Ten-percent DAF component copy selected with documented SSN-digit algorithm; optimized for analysis and testing, but not stratified and not representative of every subgroup.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E021"><data key="node_entity_id">R128_E021</data><data key="node_entity_type">research_data_mart</data><data key="node_canonical_name">DAF22 Awardee Data Mart</data><data key="node_acronym">ADM</data><data key="node_domain">research/DAF</data><data key="node_description">Subset of DAF beneficiaries with documented first SSDI adult or first child/adult SSI payment from 1996 through DAF year; includes constructed first-payment/eligibility timing fields.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E022"><data key="node_entity_id">R128_E022</data><data key="node_entity_type">research_dataset_component</data><data key="node_canonical_name">DAF22 Standalone Continuing Disability Review File</data><data key="node_domain">research/DAF</data><data key="node_description">Standalone CDR data combines Waterfall full medical review information with DCF work/medical and mailer activity; introduced as standalone file in DAF19.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E023"><data key="node_entity_id">R128_E023</data><data key="node_entity_type">administrative_repository</data><data key="node_canonical_name">Waterfall Continuing Disability Review Operational File</data><data key="node_domain">disability/CDR</data><data key="node_description">DCO/ODD/DDRWM CDR master file on SSA MISF mainframe covering centrally initiated periodic full medical reviews; excludes specified FO-initiated, nondecision, and mailer-only reviews.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Documented 2024 source description; not validated as unchanged in 2026.</data></node><node id="R128_E024"><data key="node_entity_id">R128_E024</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">DAF Waterfall Extract File</data><data key="node_domain">disability/CDR</data><data key="node_description">Extract of Waterfall-file records used in DAF22 research preparation.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E025"><data key="node_entity_id">R128_E025</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">DAF Waterfall Track Active File</data><data key="node_domain">disability/CDR</data><data key="node_description">Track Active variant of the Waterfall CDR data used in DAF22 research preparation.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E026"><data key="node_entity_id">R128_E026</data><data key="node_entity_type">logical_data_family</data><data key="node_canonical_name">Disability Control File Person, Medical, Earnings, Ticket and CDR Tables</data><data key="node_domain">disability/person_nexus</data><data key="node_description">Distinct groups/tables within DCF for personal, medical, earnings, Ticket to Work and CDR events; groups have differing occurrence cardinality.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E027"><data key="node_entity_id">R128_E027</data><data key="node_entity_type">research_dataset_component</data><data key="node_canonical_name">DAF22 Standalone Disability Application Research File</data><data key="node_domain">research/DAF</data><data key="node_description">Separate DAF22 application history product prepared through a dedicated construction workflow.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E028"><data key="node_entity_id">R128_E028</data><data key="node_entity_type">research_pipeline</data><data key="node_canonical_name">DAF22 SAS and JCL Research Construction Workflow</data><data key="node_domain">research/DAF</data><data key="node_description">Documented multi-task SAS/JCL research processing, source extraction, QA and data production for DAF22. Not SSA online benefits adjudication code.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E029"><data key="node_entity_id">R128_E029</data><data key="node_entity_type">external_administrative_dataset</data><data key="node_canonical_name">RSA-911 Vocational Rehabilitation Case Service Administrative File</data><data key="node_acronym">RSA-911</data><data key="node_domain">external_exchanges/research</data><data key="node_description">Department of Education Rehabilitation Services Administration participant records; post-July 2017 reporting includes active and closed cases with revised scope; access requires agency permission.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E030"><data key="node_entity_id">R128_E030</data><data key="node_entity_type">research_linkable_dataset</data><data key="node_canonical_name">DAF22 Linkable RSA Vocational Rehabilitation Summary File</data><data key="node_domain">external_exchanges/research</data><data key="node_description">De-identified RSA summary containing records with verified SSNs and generated PINs; can include VR participants absent from main DAF cohort.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E031"><data key="node_entity_id">R128_E031</data><data key="node_entity_type">research_linkable_dataset</data><data key="node_canonical_name">DAF22 RSA-911 Verified SSN File</data><data key="node_domain">external_exchanges/research</data><data key="node_description">Verified-SSN subset of annual RSA-911 research records, de-identified using PIN; permission from Education required.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E032"><data key="node_entity_id">R128_E032</data><data key="node_entity_type">research_linkable_dataset</data><data key="node_canonical_name">DAF22 RSA Mini-DAF Dataset</data><data key="node_domain">external_exchanges/research</data><data key="node_description">DAF component extracts for qualifying RSA participants with de-identified PIN and optional local socioeconomic variables.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E033"><data key="node_entity_id">R128_E033</data><data key="node_entity_type">research_identity_matching_process</data><data key="node_canonical_name">Mathematica-SSA RSA Enumeration Verification Process</data><data key="node_acronym">MPR-EVS</data><data key="node_domain">person/identity</data><data key="node_description">MPR-EVS validates RSA participant SSN with Numident using SSN, sex/gender and birth year because name may be unavailable; operated for DAF research linkage, not general benefit identity proofing.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E034"><data key="node_entity_id">R128_E034</data><data key="node_entity_type">restricted_research_crosswalk</data><data key="node_canonical_name">SSA DAF-RSA SSN to PIN Research Linkage Crosswalk</data><data key="node_domain">person/identity</data><data key="node_description">SSA-maintained controlled crosswalk between SSNs and de-identified PINs for DAF-RSA linkages; not a universal beneficiary Person registry.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E035"><data key="node_entity_id">R128_E035</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">DAF Employment Network Cumulative Payment Report</data><data key="node_domain">Ticket_to_Work/payments</data><data key="node_description">Cumulative EN payment report used to construct DAF TTW provider payments; reports provider, amount, payment date and triggering event.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E036"><data key="node_entity_id">R128_E036</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">DAF Ticket to Work Provider Identification File</data><data key="node_domain">Ticket_to_Work/providers</data><data key="node_description">Provider file identifies EN and state VR provider organizations, DUNS identifiers and contract effective dates; explicitly contains no beneficiary data.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E037"><data key="node_entity_id">R128_E037</data><data key="node_entity_type">restricted_research_dataset</data><data key="node_canonical_name">DAF22 Restricted Master Earnings File Linkable Research Dataset</data><data key="node_domain">earnings/research</data><data key="node_description">MEF-derived annual earnings research file, subject to Internal Revenue Code 6103 and limited to selected SSA staff; includes annual wages, employment and self-employment measures.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E038"><data key="node_entity_id">R128_E038</data><data key="node_entity_type">research_variable</data><data key="node_canonical_name">DAF22 Research Annual Earnings Work Indicator</data><data key="node_domain">earnings/research</data><data key="node_description">Annual positive wages or self-employment indicator constructed from restricted MEF data; third-party payments alone do not constitute work.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E039"><data key="node_entity_id">R128_E039</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">DCF Medical and Work CDR Events in DAF22</data><data key="node_domain">disability/CDR</data><data key="node_description">DCF event/review data includes work and medical CDRs, including mailer-only activity absent from Waterfall full-medical-review file.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E040"><data key="node_entity_id">R128_E040</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">Title II and Title XVI Annual Disability Research File Extracts</data><data key="node_domain">research/disability</data><data key="node_description">Office of Disability Policy annual Disability Research Files for Title II and Title XVI claims; constructed from SSA administrative systems and cover ten-year claim histories.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E041"><data key="node_entity_id">R128_E041</data><data key="node_entity_type">contractor</data><data key="node_canonical_name">Mathematica DAF22 Research Documentation Contractor</data><data key="node_domain">procurement/research</data><data key="node_description">Mathematica identified as SSA DAF22 documentation contractor under reference number 28321322D00060010; does not prove control of SSA production systems.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Documented research contract, not operational IT deployment.</data></node><node id="R128_E042"><data key="node_entity_id">R128_E042</data><data key="node_entity_type">workflow_screen</data><data key="node_canonical_name">MSSICS DIRS IRS Alert Development Documentation Screen</data><data key="node_acronym">DIRS</data><data key="node_domain">Title_XVI/IRS_development</data><data key="node_description">POMS SI 02310.048 instructs recording IRS alert investigation in MSSICS DIRS; policy last revised August 2013, still publicly presented in the September 2026 batch.</data><data key="node_observed_status">historical_policy_revised_2013_observed_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Exact on-screen backend, transaction persistence and current production behavior not established.</data></node><node id="R128_E043"><data key="node_entity_id">R128_E043</data><data key="node_entity_type">third_party_address_attribute</data><data key="node_canonical_name">IRS Alert Taxpayer Address for Ownership Verification</data><data key="node_domain">person/address_provenance</data><data key="node_description">Taxpayer contact/location address present in an IRS transaction alert may be checked against payer documentation to establish whether the recipient is the correct owner; not automatically a current residence.</data><data key="node_observed_status">historical_policy_revised_2013_observed_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R128_E044"><data key="node_entity_id">R128_E044</data><data key="node_entity_type">third_party_address_attribute</data><data key="node_canonical_name">IRS Alert Payer Administrative Office Address</data><data key="node_domain">person/address_provenance</data><data key="node_description">Address displayed for a financial or other payer in an IRS alert may denote corporate administrative offices, not the claimant or local branch.</data><data key="node_observed_status">historical_policy_revised_2013_observed_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R128_E045"><data key="node_entity_id">R128_E045</data><data key="node_entity_type">program_integrity_workflow</data><data key="node_canonical_name">SSI IRS Alert Ownership and Resource Development Process</data><data key="node_domain">Title_XVI/program_integrity</data><data key="node_description">When a taxpayer denies transaction ownership SSA may request evidence, obtain signed authorization, contact a payer, evaluate income/resource attribution and stop unsupported development.</data><data key="node_observed_status">historical_policy_revised_2013_observed_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R128_E046"><data key="node_entity_id">R128_E046</data><data key="node_entity_type">program_integrity_workflow</data><data key="node_canonical_name">SSI IRS Alert Transfer to New Servicing Field Office</data><data key="node_domain">Title_XVI/workload</data><data key="node_description">POMS directs employee to transfer IRS alert and related information when recipient is no longer in originating field office service area.</data><data key="node_observed_status">historical_policy_revised_2013_observed_2026</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R128_E047"><data key="node_entity_id">R128_E047</data><data key="node_entity_type">research_context_dataset</data><data key="node_canonical_name">DAF RSA County-Level Local Area Unemployment Statistics Inputs</data><data key="node_domain">research/external_geography</data><data key="node_description">Monthly county unemployment context obtained from LAUS for qualified RSA participants; geographic association derived from participant county of residence, not a master address update.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R128_E048"><data key="node_entity_id">R128_E048</data><data key="node_entity_type">research_context_dataset</data><data key="node_canonical_name">DAF RSA County-Level Small Area Income and Poverty Estimates Inputs</data><data key="node_domain">research/external_geography</data><data key="node_description">County-level poverty rate and median income variables used in RSA Mini-DAF; historical 1996 county data unavailable as documented.</data><data key="node_observed_status">historical_documented_2024_DAF22</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E001"><data key="node_entity_id">R129_E001</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">N8NN Monthly Average Speed to Answer (ASA) CSV</data><data key="node_domain">contact_center/public_data</data><data key="node_description">SSA publishes national monthly mean seconds that answered agent calls waited in queue. Abandoned calls in queue are excluded. Updated 2026-04-17.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E002"><data key="node_entity_id">R129_E002</data><data key="node_entity_type">statistical_business_rule</data><data key="node_canonical_name">N8NN Answered-Call Queue-Time Denominator Rule</data><data key="node_domain">contact_center/data_quality</data><data key="node_description">Average Speed to Answer is total queue seconds divided by answered agent calls; calls abandoned while queued do not enter the denominator.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E003"><data key="node_entity_id">R129_E003</data><data key="node_entity_type">publication_catalog</data><data key="node_canonical_name">SSA Electronic FOIA Reading Room Proactive Disclosure Index</data><data key="node_domain">governance/open_records</data><data key="node_description">SSA lists proactive disclosures, titles, and public posting dates; indexes released products without specifying their generating systems.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E004"><data key="node_entity_id">R129_E004</data><data key="node_entity_type">procurement_payment_data_product</data><data key="node_canonical_name">FY2019-FY2024 Medical Experts Total Payments FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">September 24, 2026 listing; historical medical expert total payments for FY2019-FY2024; underlying payment source unverified.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E005"><data key="node_entity_id">R129_E005</data><data key="node_entity_type">procurement_payment_data_product</data><data key="node_canonical_name">FY2019-FY2024 Vocational Experts Total Payments FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">September 24, 2026 listing; vocational expert total payments for FY2019-FY2024; underlying contracting system unverified.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E006"><data key="node_entity_id">R129_E006</data><data key="node_entity_type">representative_statistical_product</data><data key="node_canonical_name">FY2025 Top 500 Firms FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">September 4, 2026 SSA listing titled FY2025 Top 500 Firms; ranking methodology not established by listing.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E007"><data key="node_entity_id">R129_E007</data><data key="node_entity_type">representative_statistical_product</data><data key="node_canonical_name">FY2025 Top 500 Representatives FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">September 4, 2026 listing titled FY2025 Top 500 Reps; criteria cannot be established from index alone.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E008"><data key="node_entity_id">R129_E008</data><data key="node_entity_type">hearing_workload_publication</data><data key="node_canonical_name">August 2026 Caseload Analysis Report FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">September 21, 2026 posting titled 2026 08 Caseload Analysis Report; metrics and backend require reading actual report.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E009"><data key="node_entity_id">R129_E009</data><data key="node_entity_type">representative_program_integrity_data_product</data><data key="node_canonical_name">August 2026 Registered Sanctioned Representatives List</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">September 2, 2026 posted index entry covering registered sanctioned representatives; not a live registration feed.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E010"><data key="node_entity_id">R129_E010</data><data key="node_entity_type">representative_program_integrity_data_product</data><data key="node_canonical_name">August 2026 Unregistered Sanctioned Representatives List</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">September 2, 2026 posted index entry covering unregistered sanctioned representatives; not a live registration feed.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E011"><data key="node_entity_id">R129_E011</data><data key="node_entity_type">workload_data_product</data><data key="node_canonical_name">FY2025 SSA Workload FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">March 25, 2026 entry titled FY25 Workload Data; index does not specify tables or administrative system.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E012"><data key="node_entity_id">R129_E012</data><data key="node_entity_type">representative_statistical_product</data><data key="node_canonical_name">FY2016-FY2025 Representative Rates by Adjudicative Level FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">December 5, 2025 entry titled Representative Rates by Adjudicative Level FY 2016 - FY 2025; historical trend not operational case file.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E013"><data key="node_entity_id">R129_E013</data><data key="node_entity_type">research_publication_artifact</data><data key="node_canonical_name">FY2021-FY2023 and FY2025 Employment Networks FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">January 26, 2026 entry titled Employment Networks FYs 2021-2023 and 2025; raw structure not inspected.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E014"><data key="node_entity_id">R129_E014</data><data key="node_entity_type">public_disclosure_document</data><data key="node_canonical_name">March 2025 SSA to DHS Information Transmission FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">Index lists redacted March 3 2025 email transmitting data to DHS, disclosed April 24 2026; contents not reviewed, transmission type unverified.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E015"><data key="node_entity_id">R129_E015</data><data key="node_entity_type">public_disclosure_document</data><data key="node_canonical_name">March 2025 SSA Identity Assurance Memorandum FOIA Release</data><data key="node_domain">foia/public_disclosures</data><data key="node_description">Index lists March 13 memorandum on strengthening identity assurance, posted March 6 2026; contents not reviewed.</data><data key="node_observed_status">public_listing_verified; contents_not_inspected</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E016"><data key="node_entity_id">R129_E016</data><data key="node_entity_type">public_service_catalog</data><data key="node_canonical_name">SSA Forms Search and Digital Submission Capability Catalog (October 2026)</data><data key="node_domain">forms/digital_intake</data><data key="node_description">SSA Forms page lists submission modes per form, including webform, upload PDF, or separate online benefit applications; not every form supports every mode.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E017"><data key="node_entity_id">R129_E017</data><data key="node_entity_type">digital_intake_control</data><data key="node_canonical_name">SSA Electronic Forms Additional Identity Verification Requirement</data><data key="node_domain">forms/identity_proofing</data><data key="node_description">SSA identifies five forms requiring an additional identity verification for electronic submission: SSA-454-BK, SSA-827, SSA-2574, SSA-2935, and SSA-8510.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E018"><data key="node_entity_id">R129_E018</data><data key="node_entity_type">digital_evidence_business_rule</data><data key="node_canonical_name">SSA Upload Documents Original or Certified Evidence Copy Exclusion</data><data key="node_domain">forms/evidence</data><data key="node_description">SSA states it cannot accept original or certified copies of documents electronically through Upload Documents.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E019"><data key="node_entity_id">R129_E019</data><data key="node_entity_type">actuarial_statistical_data_product</data><data key="node_canonical_name">OACT Disabled Worker Applications and Awards Calendar-Year Series</data><data key="node_domain">actuarial/disability</data><data key="node_description">OACT publishes 1965-2025 calendar-year disabled-worker application and award counts, same-year ratios, and awards per 1,000 insured workers; excludes SSI-only, disabled widows and disabled children.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E020"><data key="node_entity_id">R129_E020</data><data key="node_entity_type">statistical_business_rule</data><data key="node_canonical_name">OACT Same-Year Disability Awards-to-Applications Noncohort Ratio</data><data key="node_domain">actuarial/data_quality</data><data key="node_description">OACT warns that awards in a calendar year divided by applications in the same year is not the eventual approval rate of that year’s applicant cohort.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E021"><data key="node_entity_id">R129_E021</data><data key="node_entity_type">statistical_publication_status_change</data><data key="node_canonical_name">Annual Statistical Supplement Table 6.C7 Discontinued in 2026</data><data key="node_domain">actuarial/publication_pipeline</data><data key="node_description">SSA discontinues Table 6.C7 in the 2026 Statistical Supplement because equivalent disabled-worker applications/awards reporting is available through OACT.</data><data key="node_observed_status">discontinued_within_2026_supplement</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E022"><data key="node_entity_id">R129_E022</data><data key="node_entity_type">oversight_research_publication</data><data key="node_canonical_name">SSAB Representative Payee Trends Issue Brief September 2026</data><data key="node_domain">representative_payee/oversight</data><data key="node_description">SSAB examined adult Title II and SSI representative payee trends for 2010-2025; the share of retired beneficiaries with payees declined while disabled adult and SSI aged shares were relatively stable.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E023"><data key="node_entity_id">R129_E023</data><data key="node_entity_type">procurement_organizational_unit</data><data key="node_canonical_name">SSA OITA Division of IT Equipment and Maintenance</data><data key="node_domain">procurement/IT</data><data key="node_description">Listed unit under the Office of Information Technology Acquisition responsible in the OITA contracting officer directory for IT equipment/maintenance procurements.</data><data key="node_observed_status">listed_on_public_OAG_page; directory_revised_2023_11</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E024"><data key="node_entity_id">R129_E024</data><data key="node_entity_type">procurement_organizational_unit</data><data key="node_canonical_name">SSA OITA Division of IT Software and Maintenance</data><data key="node_domain">procurement/IT</data><data key="node_description">Listed unit under the Office of Information Technology Acquisition for software and maintenance procurement; current staffing cannot be inferred from the 2023 directory.</data><data key="node_observed_status">listed_on_public_OAG_page; directory_revised_2023_11</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E025"><data key="node_entity_id">R129_E025</data><data key="node_entity_type">statistical_business_rule</data><data key="node_canonical_name">Hearing Office Workload Negative Adjusted Receipt Rule</data><data key="node_domain">hearings/public_data</data><data key="node_description">Hearing-office workload file can show negative receipts when cases transferred out exceed newly received cases; not a negative number of applications.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E026"><data key="node_entity_id">R129_E026</data><data key="node_entity_type">hearings_statistical_data_product</data><data key="node_canonical_name">FY2026 OHO ALJ Dispositions per Day National Ranking Report</data><data key="node_domain">hearings/public_data</data><data key="node_description">SSA public-use hearings page lists FY2026 national ranking by ALJ dispositions per ALJ day; case-level data or calculation technology is not disclosed on index.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E027"><data key="node_entity_id">R129_E027</data><data key="node_entity_type">hearings_statistical_data_product</data><data key="node_canonical_name">FY2026 OHO Hearing Office Average Processing Time Rankings</data><data key="node_domain">hearings/public_data</data><data key="node_description">SSA publishes hearing-office ranking by average processing time for the FY2026 reporting period; this measure is different from average wait until hearing is held.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E028"><data key="node_entity_id">R129_E028</data><data key="node_entity_type">historical_public_data_product</data><data key="node_canonical_name">OHO In-Person and Video Hearing Public Data Last Available FY2020</data><data key="node_domain">hearings/public_data</data><data key="node_description">SSA public-use page says current in-person/video hearing data unavailable and directs users to archived September 2019-February 2020 data.</data><data key="node_observed_status">historical_last_available_FY2020</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E029"><data key="node_entity_id">R129_E029</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">FY2016-Onward RSI Applications Receipts and Clearances Monthly CSV</data><data key="node_domain">titleII/data_products</data><data key="node_description">SSA publishes monthly national retirement/survivor/Medicare intake and completion data; captures MCS clearances and District Office Workload Report reporting periods.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R129_E030"><data key="node_entity_id">R129_E030</data><data key="node_entity_type">claims_data_attribute</data><data key="node_canonical_name">Internet RSI Application Source Indicator</data><data key="node_domain">titleII/intake</data><data key="node_description">SSA online filing process marks applicable retirement, spouse, and Medicare online claims to distinguish receipt via Internet for management counts.</data><data key="node_observed_status">documented_public_artifact</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E001"><data key="node_entity_id">R130_E001</data><data key="node_entity_type">claims_system_limitation</data><data key="node_canonical_name">SSI Age-65 Claim Filing Date System Limitation</data><data key="node_domain">Title XVI/filing_date</data><data key="node_description">For SSI age-65 attainment in the month of filing, POMS instructs staff in defined circumstances to enter a system filing date different from the legally correct earlier date and record the true date separately.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Only for specified age-65 cases; not for age-18 cases; legally correct filing date remains authoritative.</data></node><node id="R130_E002"><data key="node_entity_id">R130_E002</data><data key="node_entity_type">program_record_attribute</data><data key="node_canonical_name">SSI Age-65 Correct Filing Date SSR Remarks Annotation</data><data key="node_domain">Title XVI/claims_provenance</data><data key="node_description">POMS requires technicians to place the legally correct filing date in SSR remarks when MSSICS must hold a different system date under the age-65 system limitation.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E003"><data key="node_entity_id">R130_E003</data><data key="node_entity_type">workload_accounting_attribute</data><data key="node_canonical_name">Reopened Claim File Date Change Code C</data><data key="node_domain">Title II/reopening/workload</data><data key="node_description">GN 00204.007 directs the MCS Decision Input screen to use file-date-change code C for specified reopened denied claims so management information excludes prior FO1 time.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Code modifies specified field-office elapsed-time calculations, not overall mean elapsed time.</data></node><node id="R130_E004"><data key="node_entity_id">R130_E004</data><data key="node_entity_type">claims_event_timestamp</data><data key="node_canonical_name">Internet iClaim Submitted Completion Date</data><data key="node_domain">Title II/intake/provenance</data><data key="node_description">For an electronically signed first-party iClaim the original Internet Menu (IMNU) completion/submission date determines receipt, not when staff later establishes the claim in MCS.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E005"><data key="node_entity_id">R130_E005</data><data key="node_entity_type">claims_receipt_policy</data><data key="node_canonical_name">Mailed Protective Filing Postmark Five-Day Rule</data><data key="node_domain">cross_program/claims_provenance</data><data key="node_description">For signed applications received just after protective closeout, a qualifying postmark within five days of closeout may establish receipt date.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E006"><data key="node_entity_id">R130_E006</data><data key="node_entity_type">claims_reopening_attribute</data><data key="node_canonical_name">Reopened Claim Material File Date</data><data key="node_domain">cross_program/reopening</data><data key="node_description">For reopening an earlier denial, POMS directs the material file date and application receipt date to reflect the reopening request date; the prior protective filing date remains separately preserved.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E007"><data key="node_entity_id">R130_E007</data><data key="node_entity_type">digital_submission_workflow</data><data key="node_canonical_name">Upload Documents Signed Benefit Application Manual Claims-System Entry</data><data key="node_domain">digital_intake/claims</data><data key="node_description">SSA instructs technicians to process electronically signed benefit applications submitted with Upload Documents as paper applications and manually enter them into MCS or CCE.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E008"><data key="node_entity_id">R130_E008</data><data key="node_entity_type">digital_signature_artifact</data><data key="node_canonical_name">Upload Documents Appended Electronic Signature Page</data><data key="node_domain">digital_intake/evidence</data><data key="node_description">SSA appends a separate electronic signature information page to PDF submissions signed through Upload Documents.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E009"><data key="node_entity_id">R130_E009</data><data key="node_entity_type">claims_signature_control</data><data key="node_canonical_name">MCS Attestation Signature-Method Remarks Control</data><data key="node_domain">digital_intake/work_control</data><data key="node_description">Because MCS automatically propagates ATTEST to DW01 regardless of actual signature method, staff must identify wet signature, Upload Documents, CPAS, or other method in remarks.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E010"><data key="node_entity_id">R130_E010</data><data key="node_entity_type">digital_signature_artifact</data><data key="node_canonical_name">Commercial Product Alternative Signature Certificate Page</data><data key="node_domain">digital_evidence/representatives</data><data key="node_description">POMS permits commercial-product signature date and time on an appended certificate page provided it accompanies the signed form at initial submission.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E011"><data key="node_entity_id">R130_E011</data><data key="node_entity_type">digital_signature_validation_rule</data><data key="node_canonical_name">CPAS Timestamp and Signature-Placement Acceptance Rule</data><data key="node_domain">digital_evidence/policy</data><data key="node_description">CPAS requires signer name in the designated signature area plus date and time on the form or accompanying certificate; a separately submitted late certificate is not accepted.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E012"><data key="node_entity_id">R130_E012</data><data key="node_entity_type">digital_signature_policy_event</data><data key="node_canonical_name">January 18 2025 CPAS Receipt Applicability Threshold</data><data key="node_domain">digital_evidence/modernization</data><data key="node_description">POMS sets January 18, 2025 as the receipt threshold for current commercial-product alternative signature acceptance instructions, with conditional handling of earlier forms.</data><data key="node_observed_status">documented_policy_effective_date</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E013"><data key="node_entity_id">R130_E013</data><data key="node_entity_type">evidence_audit_control</data><data key="node_canonical_name">Evidence Screen Entry Locked After Completion</data><data key="node_domain">evidence/provenance</data><data key="node_description">EVID entries cannot be edited once completed; management has deletion authority. POMS directs additional clarifying notes to MCS RPOC or CCE Report of Contact.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E014"><data key="node_entity_id">R130_E014</data><data key="node_entity_type">evidence_record_attribute</data><data key="node_canonical_name">EVID Cross Reference SSN Field for Concurrent Claims</data><data key="node_domain">evidence/person_nexus</data><data key="node_description">For evidence shared across concurrent or subsequent claims on different SSNs, SSA records it once under the claimant SSN and lists related SSNs in EVID cross-reference fields.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E015"><data key="node_entity_id">R130_E015</data><data key="node_entity_type">evidence_provenance_attribute</data><data key="node_canonical_name">EVID Online State Custodian Source Annotation</data><data key="node_domain">evidence/external_state</data><data key="node_description">When employees retrieve custodian-certified records from state or local online systems, POMS requires the EVID comments to identify state/local online access as evidence source.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E016"><data key="node_entity_id">R130_E016</data><data key="node_entity_type">records_management_control</data><data key="node_canonical_name">Temporary Initial-Claim Evidence Development File Destruction</data><data key="node_domain">evidence/retention</data><data key="node_description">When only temporary photocopies support pending development, staff retain them until initial determination and then destroy the temporary development file following SSA POMS.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E017"><data key="node_entity_id">R130_E017</data><data key="node_entity_type">evidence_audit_rule</data><data key="node_canonical_name">Electronic Evidence Sufficient Audit-Trail Requirement</data><data key="node_domain">evidence/governance</data><data key="node_description">For domestic public records used to prove age, death, marriage, divorce, or citizenship, MCS or CCE entries must retain enough information to retrieve source records; otherwise EVID must be coded.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E018"><data key="node_entity_id">R130_E018</data><data key="node_entity_type">evidence_provenance_rule</data><data key="node_canonical_name">EVID Online State Record Certification Acceptance</data><data key="node_domain">evidence/states</data><data key="node_description">Electronically supplied evidence certified by its state/local custodian can satisfy SSA documentary evidence requirements, subject to proof validity and audit-trail rules.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E019"><data key="node_entity_id">R130_E019</data><data key="node_entity_type">evidence_repository_rule</data><data key="node_canonical_name">Non-Disability Evidence Exclusion from EVID Coding</data><data key="node_domain">evidence/folder_routing</data><data key="node_description">POMS excludes alien-registration cards, medical evidence, and certain WC/PDB documents from EVID screen coding, directing documents to NDRed or CEF by the specified case type.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E020"><data key="node_entity_id">R130_E020</data><data key="node_entity_type">evidence_reuse_rule</data><data key="node_canonical_name">Previously Established Proof Reuse Across MBR SSR Numident</data><data key="node_domain">person_nexus/claims_evidence</data><data key="node_description">POMS permits certain previously established facts, such as age, to be reused from SSA records when enough evidence/audit information exists and criteria align; no universal attribute synchronization is inferred.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E021"><data key="node_entity_id">R130_E021</data><data key="node_entity_type">external_tax_address_source</data><data key="node_canonical_name">Puerto Rico Revenue Agency Statement Mailing Address</data><data key="node_domain">address/territorial_tax</data><data key="node_description">SSA uses Puerto Rico revenue-agency taxpayer files to locate statement recipients not required to file US federal income tax returns; intended for statement mailing only.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E022"><data key="node_entity_id">R130_E022</data><data key="node_entity_type">external_tax_address_source</data><data key="node_canonical_name">U.S. Virgin Islands Revenue Agency Statement Mailing Address</data><data key="node_domain">address/territorial_tax</data><data key="node_description">SSA uses Virgin Islands revenue-agency taxpayer files for statement mailing addresses of eligible individuals not required to file federal tax returns; no master-record update asserted.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E023"><data key="node_entity_id">R130_E023</data><data key="node_entity_type">address_legal_use_constraint</data><data key="node_canonical_name">IRS IMF Address Use for Statements Under 26 USC 6103(m)(7)</data><data key="node_domain">address/IRS/restrictions</data><data key="node_description">SSA identifies IRC section 6103(m)(7) as the permitted basis for using IRS Individual Master File taxpayer addresses for Social Security Statement mailing.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E024"><data key="node_entity_id">R130_E024</data><data key="node_entity_type">public_statement_format</data><data key="node_canonical_name">SSA-7005-SM-OL Online Social Security Statement</data><data key="node_domain">actuarial/communication</data><data key="node_description">SSA provides this online Statement format behind authenticated my Social Security accounts; a separate on-request and system-initiated print format is documented.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E025"><data key="node_entity_id">R130_E025</data><data key="node_entity_type">public_statement_format</data><data key="node_canonical_name">SSA-7005-SM-SI System-Initiated Paper Statement</data><data key="node_domain">actuarial/communication</data><data key="node_description">SSA mails system-initiated Statements to selected qualifying beneficiaries age 60 and older who do not have mySSA accounts and do not receive Title II benefits.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E026"><data key="node_entity_id">R130_E026</data><data key="node_entity_type">public_statement_format</data><data key="node_canonical_name">SSA-7005-SM-OR On-Request Paper Statement</data><data key="node_domain">actuarial/communication</data><data key="node_description">SSA produces this paper Statement upon SSN holder request, including SSA-7004 requests; printed/mailing route differs from automatic statements.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E027"><data key="node_entity_id">R130_E027</data><data key="node_entity_type">undeliverable_correspondence_rule</data><data key="node_canonical_name">Undeliverable Automatic Social Security Statement Destruction</data><data key="node_domain">address/correspondence</data><data key="node_description">Automatic Social Security Statements returned as undeliverable are not remailed. POMS says SSA destroys them without further processing.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E028"><data key="node_entity_id">R130_E028</data><data key="node_entity_type">statement_locale_rule</data><data key="node_canonical_name">Puerto Rico Tax-Address Spanish Statement Mailing Rule</data><data key="node_domain">address/correspondence</data><data key="node_description">Automatic Social Security Statements are prepared in Spanish for Puerto Rico residents whose address was provided by the Puerto Rico government.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E029"><data key="node_entity_id">R130_E029</data><data key="node_entity_type">statement_selection_rule</data><data key="node_canonical_name">Automatic Statement Prior-Request and Pending-Claim Exclusions</data><data key="node_domain">actuarial/recipient_selection</data><data key="node_description">POMS excludes certain prior on-request Statement recipients, pending Title II/Medicare claimants and benefit recipients from automatic Statement selection.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E030"><data key="node_entity_id">R130_E030</data><data key="node_entity_type">digital_identity_input_control</data><data key="node_canonical_name">iAppointment Editable Name DOB Sex But Immutable SSN</data><data key="node_domain">person_nexus/appointment</data><data key="node_description">iAppt accepts SSN/name/DOB/sex propagated from iClaim; claimant can edit name DOB and sex and supply mailing address but cannot change propagated SSN.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E031"><data key="node_entity_id">R130_E031</data><data key="node_entity_type">appointment_access_rule</data><data key="node_canonical_name">iAppointment Existing Claim and Electronic SSN Block Exclusions</data><data key="node_domain">person_nexus/appointment</data><data key="node_description">POMS excludes users with current-payment MBR, pending MCS claim on the SSN, an electronic block, or foreign residence from online iAppt access.</data><data key="node_observed_status">documented_operational_rule</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E032"><data key="node_entity_id">R130_E032</data><data key="node_entity_type">actuarial_data_dimension</data><data key="node_canonical_name">2026 OACT Population Reference Date January July December</data><data key="node_domain">actuarial/statistical_data</data><data key="node_description">OACT downloadable Social Security area population series provides beginning-of-year January 1, midyear July 1, and end-of-year December 31 historical/projection values.</data><data key="node_observed_status">documented_public_data_product</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R130_E033"><data key="node_entity_id">R130_E033</data><data key="node_entity_type">public_service_modernization_feature</data><data key="node_canonical_name">May 2026 mySSA Retirement Calculator Three-Estimate Comparison</data><data key="node_domain">online_service/modernization</data><data key="node_description">SSA describes redesigned Retirement Calculator presenting a bar graph that compares up to three personalized benefit estimates from May 2026 portal redesign.</data><data key="node_observed_status">documented_portal_feature</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E001"><data key="node_entity_id">R131_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">oSSNAP Eligibility-Based Dynamic Application Routing</data><data key="node_domain">Identity / enumeration</data><data key="node_description">Beginning 2026-01-31, oSSNAP assesses original/replacement-card circumstances and sends eligible applicants to fully online or hybrid SSA-office identity workflows.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E002"><data key="node_entity_id">R131_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">oSSNAP Hybrid In-Person Evidence Completion Path</data><data key="node_domain">Identity / enumeration</data><data key="node_description">Online applicants unable to complete qualifying identity/name-change checks receive a hybrid pathway and in-person evidence appointment.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E003"><data key="node_entity_id">R131_E003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">oSSNAP Fully Automated Self-Service Card Path</data><data key="node_domain">Identity / enumeration</data><data key="node_description">Eligible applicants can finish qualified card requests electronically following third-party identity authentication and eligible records verification.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E004"><data key="node_entity_id">R131_E004</data><data key="node_entity_type">transaction_attribute</data><data key="node_canonical_name">oSSNAP Hybrid Online Control Number</data><data key="node_domain">Identity / enumeration</data><data key="node_description">Reference used to resume an oSSNAP hybrid card request at an SSA office; not established as an SSN or authoritative person identifier.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E005"><data key="node_entity_id">R131_E005</data><data key="node_entity_type">identity_control</data><data key="node_canonical_name">Appointment Scheduling Credential Versus Identity Proofing Gate</data><data key="node_domain">Identity / enumeration</data><data key="node_description">A Login.gov IAL1 credential used for scheduling alone is not equivalent to full SSN-card identity evidence verification.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E006"><data key="node_entity_id">R131_E006</data><data key="node_entity_type">modernization_status</data><data key="node_canonical_name">iSSNRC Public-Facing Screen Retirement January 2026</data><data key="node_domain">Identity / enumeration</data><data key="node_description">SSA retired legacy iSSNRC public-facing screens as online card functionality moved into oSSNAP; no documented deletion of historical activity data or backend components.</data><data key="node_observed_status">dated_public_interface_retirement</data><data key="node_observed_as_of">2026-01-31</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E007"><data key="node_entity_id">R131_E007</data><data key="node_entity_type">eligibility_rule</data><data key="node_canonical_name">oSSNAP Online Path Exclusion Conditions</data><data key="node_domain">Identity / enumeration</data><data key="node_description">The new public intake paths exclude stated categories such as adoption/new SSN requests and certain wrong-SSN or special-handling applications.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E008"><data key="node_entity_id">R131_E008</data><data key="node_entity_type">organizational_group</data><data key="node_canonical_name">Designated Scheduling Group for Representative Availability</data><data key="node_domain">Hearings / appeals</data><data key="node_description">Group of representatives whose hearing availability is supplied and managed together in SSA enhanced representative availability processes.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E009"><data key="node_entity_id">R131_E009</data><data key="node_entity_type">workload_planning_period</data><data key="node_canonical_name">ERAP Target Scheduling Month</data><data key="node_domain">Hearings / appeals</data><data key="node_description">SSA hearing-scheduling month for which a representative designated scheduling group submits future availability.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E010"><data key="node_entity_id">R131_E010</data><data key="node_entity_type">operational_rule</data><data key="node_canonical_name">2026 ERAP National Availability Submission Rule</data><data key="node_domain">Hearings / appeals</data><data key="node_description">Beginning with the January 2026 target scheduling month, availability is submitted nationally per designated scheduling group rather than separately by SSA region.</data><data key="node_observed_status">effective 2026 target month</data><data key="node_observed_as_of">2026-01-01</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E011"><data key="node_entity_id">R131_E011</data><data key="node_entity_type">scheduling_rule</data><data key="node_canonical_name">ERAP Five-Month Advance Availability Deadline</data><data key="node_domain">Hearings / appeals</data><data key="node_description">Scheduling groups submit availability by the first day of the month five months before the target scheduling month. Late or missing availability can be treated as fully available.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E012"><data key="node_entity_id">R131_E012</data><data key="node_entity_type">support_process</data><data key="node_canonical_name">OHO External Liaison Availability Submission Assistance</data><data key="node_domain">Hearings / appeals</data><data key="node_description">Hearing scheduling staff can facilitate representative availability submitted outside the portal, including via email, subject to process controls.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E013"><data key="node_entity_id">R131_E013</data><data key="node_entity_type">organization_address_attribute</data><data key="node_canonical_name">eRPS Organization Physical-Location ZIP Code Attribute</data><data key="node_domain">Representative payee / address provenance</data><data key="node_description">ZIP Code of organization physical premises, used with a sequence to construct an eRPS Organization ID. Not a beneficiary residential or mailing address.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E014"><data key="node_entity_id">R131_E014</data><data key="node_entity_type">identifier_construction_rule</data><data key="node_canonical_name">eRPS Organization ID ZIP-Plus-Sequence Key Rule</data><data key="node_domain">Representative payee / person identity</data><data key="node_description">Organizational eRPS identifier incorporates physical ZIP Code and a sequence because EINs do not uniquely identify every organization/site.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E015"><data key="node_entity_id">R131_E015</data><data key="node_entity_type">case_data_rule</data><data key="node_canonical_name">eRPS Joint Guardian Single-SSN Record Constraint</data><data key="node_domain">Representative payee / person identity</data><data key="node_description">For two or more equally responsible individual guardians, eRPS uses the first named guardian SSN as the record key and records additional guardian information in notes.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E016"><data key="node_entity_id">R131_E016</data><data key="node_entity_type">identity_rule</data><data key="node_canonical_name">Representative Payee Individual-versus-Organization Classification Gate</data><data key="node_domain">Representative payee / program records</data><data key="node_description">Sole proprietorships and general/limited partnerships may have EINs but are treated as individual payees; LLCs and other limited-liability entities are treated as organizations.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E017"><data key="node_entity_id">R131_E017</data><data key="node_entity_type">eligibility_rule</data><data key="node_canonical_name">IRMAA Nonreporting Spouse Determination Independence</data><data key="node_domain">Medicare / IRS exchanges</data><data key="node_description">An IRMAA new initial determination applies to requesting beneficiary only; information affecting another spouse or ex-spouse does not automatically change their determination.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E018"><data key="node_entity_id">R131_E018</data><data key="node_entity_type">contact_evidence_attribute</data><data key="node_canonical_name">IRMAA Married-Filing-Separately Spouse Last-Known Address</data><data key="node_domain">Medicare / address provenance</data><data key="node_description">Last-known spouse address may be supplied in a married-filing-separately IRMAA new-initial-determination investigation. It is not a verified beneficiary master-record address.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E019"><data key="node_entity_id">R131_E019</data><data key="node_entity_type">evidence_gate</data><data key="node_canonical_name">IRMAA Amended-Return IRS Acknowledgment Proof Rule</data><data key="node_domain">Medicare / IRS exchanges</data><data key="node_description">When beneficiary alleges corrected or amended IRS tax data, SSA requests applicable IRS acknowledgment, transcript or IRS correction evidence before new initial determination.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E020"><data key="node_entity_id">R131_E020</data><data key="node_entity_type">financial_institution_contact_attribute</data><data key="node_canonical_name">SSI Redetermination Financial-Institution Office Address</data><data key="node_domain">Address provenance / SSI resources</data><data key="node_description">SSA-8203-BK collects names and addresses of banks or other organizations holding beneficiary resources; institution address is not recipient residence.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E021"><data key="node_entity_id">R131_E021</data><data key="node_entity_type">permission_control</data><data key="node_canonical_name">Field-Office SSI Redetermination Financial-Contact Permission Check</data><data key="node_domain">SSI resources / external financial exchange</data><data key="node_description">POMS SI 02305.101 directs field offices to request authorization to contact financial institutions during every initiated SSI redetermination.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E022"><data key="node_entity_id">R131_E022</data><data key="node_entity_type">resource_valuation_rule</data><data key="node_canonical_name">SSI Financial Resource First-Of-Month Early-Payment Exclusion</data><data key="node_domain">SSI resources / payment semantics</data><data key="node_description">An early benefit deposit for a normal next-month SSI payment does not count as a liquid resource on the first of that month in the documented example and rule.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E023"><data key="node_entity_id">R131_E023</data><data key="node_entity_type">notice_product</data><data key="node_canonical_name">IRMAA Annual Verification Reconsideration Affirmation Notice Type 690</data><data key="node_domain">Medicare / notices</data><data key="node_description">Current POMS describes notice type 690 when SSA upholds annual-verification IRMAA reconsideration despite supplied corrected IRS proof.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E024"><data key="node_entity_id">R131_E024</data><data key="node_entity_type">notice_product</data><data key="node_canonical_name">IRMAA Annual Verification Reconsideration Reversal Notice Type 700</data><data key="node_domain">Medicare / notices</data><data key="node_description">Current POMS describes notice type 700 when annual-verification IRMAA reconsideration reverses SSA determination; notice includes appeal rights.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E025"><data key="node_entity_id">R131_E025</data><data key="node_entity_type">identity_contact_attribute</data><data key="node_canonical_name">Numident Suspected-Fraud Application Mailing Address Attribute</data><data key="node_domain">Person / address provenance</data><data key="node_description">SORN 60-0058 identifies mailing/contact information associated with suspected fraud SSN applications, subject to permitted use and disclosure controls.</data><data key="node_observed_status">SORN-documented category</data><data key="node_observed_as_of">2025-11-12</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E026"><data key="node_entity_id">R131_E026</data><data key="node_entity_type">research_publication_rule</data><data key="node_canonical_name">HRS Summary Earnings 2026 Release Excludes Weights File</data><data key="node_domain">Research and administrative-data linkage</data><data key="node_description">HRS restricted Respondent Cross-Year Summary Earnings product page explicitly says Social Security Weights file is not included in its data distribution set; contradicts older Atlas distributed_with edge.</data><data key="node_observed_status">source-dispute requiring historical version reconciliation</data><data key="node_observed_as_of">2026-04-01</data><data key="node_confidence">4</data><data key="node_notes">Existing R83 relationship says HRS weights distributed with Summary Earnings; neither source gives a common release identifier.</data></node><node id="R131_E027"><data key="node_entity_id">R131_E027</data><data key="node_entity_type">publication_data_production</data><data key="node_canonical_name">OACT Monthly Treasury Trust Fund Financial Source Refresh</data><data key="node_domain">Actuarial / statistical data</data><data key="node_description">Treasury supplies monthly trust-fund operations and investments data that SSA presents through OACT historical finance querying and chart products.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E028"><data key="node_entity_id">R131_E028</data><data key="node_entity_type">identity_verification_control</data><data key="node_canonical_name">eRPS Video Interview Applicant Identity Verification Rule</data><data key="node_domain">Representative payee / identity nexus</data><data key="node_description">For qualified remote interviews SSA verifies individual applicant information against Numident; for organizational payees verifies agent, organization address, and EIN.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R131_E029"><data key="node_entity_id">R131_E029</data><data key="node_entity_type">identity_match_limitation</data><data key="node_canonical_name">eRPS Shared Employer Identification Number Nonuniqueness Constraint</data><data key="node_domain">Representative payee / IRS data</data><data key="node_description">Different institutional subdivisions may share a single EIN, while an organization can also have several EINs; management review required when identifying payee organization.</data><data key="node_observed_status">documented operation</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0001"><data key="node_entity_id">R132_E0001</data><data key="node_entity_type">records_category</data><data key="node_canonical_name">DDS Manual Case Control Card Records</data><data key="node_domain">Disability, Records Retention</data><data key="node_description">Manual control cards documenting DDS case intake and release. Retain for at least 12 months after final release from DDS.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Manual records category; not a newly observed current electronic application.</data></node><node id="R132_E0002"><data key="node_entity_id">R132_E0002</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">DDS Consultative Provider Six-Year Audit-Exception Retention Control</data><data key="node_domain">Disability, Records Retention</data><data key="node_description">Purge DDS consultative-provider file every six years except records tied to an open audit.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Governance retention requirement on the already-cataloged DDS consultative examination provider file.</data></node><node id="R132_E0003"><data key="node_entity_id">R132_E0003</data><data key="node_entity_type">records_category</data><data key="node_canonical_name">SSA DDS Data Acquisition and Response File</data><data key="node_domain">Disability, Information Exchange</data><data key="node_description">POMS category containing system-produced tapes, printouts, edits and alerts used for corrections and reconstructing cases.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">POMS does not establish current physical media, DB engine, architecture, or actual live deployment of tapes.</data></node><node id="R132_E0004"><data key="node_entity_id">R132_E0004</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">DDS Data Acquisition and Response File Five-to-Ninety-Day Retention Window</data><data key="node_domain">Disability, Records Retention</data><data key="node_description">POMS specifies a minimum of 5 days for edit corrections and maximum of 90 days for case reconstruction for this DDS file category.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0005"><data key="node_entity_id">R132_E0005</data><data key="node_entity_type">records_category</data><data key="node_canonical_name">DDS Post-Release Nonmedical Residual File</data><data key="node_domain">Disability, Evidence</data><data key="node_description">Nonmedical material retained after DDS case leaves the DDS, until adjudication and as long as needed.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0006"><data key="node_entity_id">R132_E0006</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">DDS Nonmedical Residual File Adjudication-Dependent Disposition</data><data key="node_domain">Disability, Records Retention</data><data key="node_description">Retain nonmedical residual records until claim adjudication; dispose when no longer needed.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0007"><data key="node_entity_id">R132_E0007</data><data key="node_entity_type">data_product_family</data><data key="node_canonical_name">DDS Routine Non-Controlled Statistical and Management Reports</data><data key="node_domain">Disability, Statistics</data><data key="node_description">Routine highlights, cost-reduction and other statistical records classified for six-year disposal.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0008"><data key="node_entity_id">R132_E0008</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">DDS Routine Statistical Report Six-Year Destruction Rule</data><data key="node_domain">Disability, Records Retention</data><data key="node_description">POMS directs destruction of DDS routine noncontrolled reports after six years.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0009"><data key="node_entity_id">R132_E0009</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">DDS Fiscal Voucher and Equipment Records Federal Audit Disposition Rule</data><data key="node_domain">Disability, Financial Governance</data><data key="node_description">DDS equipment/supply files, letter of credit transactions and payment voucher records are destroyed following final resolution of federal audit.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0010"><data key="node_entity_id">R132_E0010</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">DDS General Communication and Reference File Six-Year Rule</data><data key="node_domain">Disability, Records Retention</data><data key="node_description">POMS requires destruction of DDS general communications and reference files after six years.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0011"><data key="node_entity_id">R132_E0011</data><data key="node_entity_type">acquisition_control</data><data key="node_canonical_name">DDS Major Information Technology Acquisition Central Office Approval Gate</data><data key="node_domain">Disability, Procurement</data><data key="node_description">SSA requires advance written central office approval for major DDS central processor and software acquisitions; new/replacement systems require feasibility and cost-benefit documentation.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Policy requirement, not evidence a specific acquisition occurred.</data></node><node id="R132_E0012"><data key="node_entity_id">R132_E0012</data><data key="node_entity_type">documentation_requirement</data><data key="node_canonical_name">DDS New or Replacement IT Feasibility and Cost-Benefit Documentation</data><data key="node_domain">Disability, Procurement</data><data key="node_description">Feasibility study and cost-benefit analysis required before DDS new/replacement hardware or software system procurement; SSADARS is named as a documented exception.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">A mention of SSADARS is not confirmation of October 2026 production deployment.</data></node><node id="R132_E0013"><data key="node_entity_id">R132_E0013</data><data key="node_entity_type">performance_control</data><data key="node_canonical_name">DDS Initial Performance Accuracy 90.6 Percent Corrective-Action Threshold</data><data key="node_domain">Disability, Program Oversight</data><data key="node_description">Disability Adjudication works with state DDS to diagnose and remedy initial-performance accuracy below 90.6 percent.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Threshold stated in October 6, 2026 POMS; not interpreted as individual case outcome or error rate.</data></node><node id="R132_E0014"><data key="node_entity_id">R132_E0014</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">DDS Performance Monitoring Indicators: Aging, Pending, Time, Staffing and PPWY</data><data key="node_domain">Disability, Operational Analytics</data><data key="node_description">SSA reviews processing time, pending workloads, aged cases, staffing levels and production per work year alongside accuracy.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0015"><data key="node_entity_id">R132_E0015</data><data key="node_entity_type">oversight_process</data><data key="node_canonical_name">DDS Continuous Performance Monitoring and QA Data Review</data><data key="node_domain">Disability, Program Oversight</data><data key="node_description">DDSs maintain continuous monitoring using management information, QA review results, workflow analysis and collaboration with SSA regional and HQ staff.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">No identified product/database implementation in official source.</data></node><node id="R132_E0016"><data key="node_entity_id">R132_E0016</data><data key="node_entity_type">data_product_family</data><data key="node_canonical_name">DDS Adjudicator Error and Review-Type Special Management Reports</data><data key="node_domain">Disability, Operational Analytics</data><data key="node_description">DDS management may develop special-purpose error-type, adjudicator-error, CE approval-review and technical-denial review reports.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Optional special reporting capability, not proof these reports are produced uniformly by all DDS.</data></node><node id="R132_E0017"><data key="node_entity_id">R132_E0017</data><data key="node_entity_type">financial_publication_process</data><data key="node_canonical_name">DDS Quarterly Cumulative SSA-4513 Obligation Submission</data><data key="node_domain">Disability, Grants and Funding</data><data key="node_description">State DDS prepares quarterly cumulative, fiscal-year-to-date financial obligation data with SSA-4513 and Addendum; originals sent to SSA Disability Adjudication.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0018"><data key="node_entity_id">R132_E0018</data><data key="node_entity_type">financial_reporting_control</data><data key="node_canonical_name">DDS Prior-Fiscal-Year Unliquidated Obligation Separate Submission</data><data key="node_domain">Disability, Grants and Funding</data><data key="node_description">Each fiscal year with remaining DDS unliquidated obligations requires a separate quarterly SSA-4513 and related cumulative amounts.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0019"><data key="node_entity_id">R132_E0019</data><data key="node_entity_type">financial_review_process</data><data key="node_canonical_name">DDS Selected Three-Transaction Accounting or Invoice Validation Sample</data><data key="node_domain">Disability, Grants and Funding</data><data key="node_description">Disability Adjudication randomly selects one state per quarter to submit three state-selected supporting transactions; accounting-system or invoice evidence is reviewed regionally.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">No common DDS accounting package identified; example source systems are unspecified state systems or invoices.</data></node><node id="R132_E0020"><data key="node_entity_id">R132_E0020</data><data key="node_entity_type">financial_reporting_control</data><data key="node_canonical_name">DDS SSA-4513 Quarter-Close Twenty-Fifth-Day Filing Rule</data><data key="node_domain">Disability, Grants and Funding</data><data key="node_description">Original signed SSA-4513 due to SSA Central Office by the 25th day after quarter end; electronic copy to DA Funding Box.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0021"><data key="node_entity_id">R132_E0021</data><data key="node_entity_type">pilot_program</data><data key="node_canonical_name">BSO January 2026 Responsible Entity Officer and Delegated User Authorization Pilot</data><data key="node_domain">Earnings, Identity and Access</data><data key="node_description">January 10, 2026 pilot of entity-managed Business Services Online access authorizations for Responsible Entity Officers and delegates.</data><data key="node_observed_status">pilot_observed_2026_01</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Announcement promises future full rollout; no evidence pilot reached general production or that new physical identity store was deployed.</data></node><node id="R132_E0022"><data key="node_entity_id">R132_E0022</data><data key="node_entity_type">access_role</data><data key="node_canonical_name">Business Services Online Responsible Entity Officer Delegation Role</data><data key="node_domain">Earnings, Identity and Access</data><data key="node_description">BSO new authorization pilot eligibility centers on company Responsible Entity Officer or delegated user participant.</data><data key="node_observed_status">pilot_observed_2026_01</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0023"><data key="node_entity_id">R132_E0023</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Hearings and Appeals Case-Control Folder-Number Retrieval Key</data><data key="node_domain">Hearings and Appeals, Records</data><data key="node_description">January 2026 SORN 60-0009 describes retrieval by folder number as well as SSN and name.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">SORN retrieval method, not evidence of a unique folder-number-only physical primary key.</data></node><node id="R132_E0024"><data key="node_entity_id">R132_E0024</data><data key="node_entity_type">use_restriction</data><data key="node_canonical_name">Hearings and Appeals Federal Tax Return Information Disclosure Limitation</data><data key="node_domain">Hearings and Appeals, Privacy</data><data key="node_description">HA case-control system records may contain IRS return information, whose authorized sharing remains subject to IRC section 6103.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0025"><data key="node_entity_id">R132_E0025</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">Hearings and Appeals Case-Control NARA Leadership and Legal Retention Schedules</data><data key="node_domain">Hearings and Appeals, Privacy</data><data key="node_description">The 2026 SORN references NARA approved retention schedules DAA-0047-2024-0001 and DAA-0047-2022-0003 for categories they cover.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">These schedule references do not establish universal duration of every case folder.</data></node><node id="R132_E0026"><data key="node_entity_id">R132_E0026</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-450 SSI Manual Claims Input Data Form</data><data key="node_domain">Representative Payee, Title XVI</data><data key="node_description">2018 POMS documents the SSA-450 as a manual alternative together with SSA-1719B for certain SSI representative-payee selections when SSN is unavailable.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Form is documented in POMS; no claim of direct eRPS/SSR synchronization.</data></node><node id="R132_E0027"><data key="node_entity_id">R132_E0027</data><data key="node_entity_type">exception_workflow</data><data key="node_canonical_name">SSI Representative Payee No-SSN Manual SSR Processing Alternative</data><data key="node_domain">Representative Payee, Title XVI</data><data key="node_description">Where a payee has no SSN, SSA documents manual SSI payee selection using SSA-1719B or SSA-450 rather than assuming eRPS self-executes SSR transaction.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R132_E0028"><data key="node_entity_id">R132_E0028</data><data key="node_entity_type">filing_process_rule</data><data key="node_canonical_name">Appeals Council Post-Hearing New Disabling Condition Subsequent-Application Exception</data><data key="node_domain">Hearings and Appeals, Disability</data><data key="node_description">POMS permits a new disability application in prescribed circumstances involving a post-hearing new critical/disabling condition while AC review remains pending; employees document through SSA-5002 and EDCS appeals communication.</data><data key="node_observed_status">documented_operational_process</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">4</data><data key="node_notes">Condition-specific exception; not a general right to submit duplicative claims or automatic EDCS routing.</data></node><node id="R133_E0001"><data key="node_entity_id">R133_E0001</data><data key="node_entity_type">application</data><data key="node_canonical_name">Treasury Online Forms Requestor</data><data key="node_acronym">TOFR</data><data key="node_domain">Payments and debt</data><data key="node_description">SSA Title II program service center request application for Treasury reclamation documents, protests, and abandonment actions, accessed through MAMPSC data input page.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Application named by SSA POMS; hosting/backend/vendor not specified.</data></node><node id="R133_E0002"><data key="node_entity_id">R133_E0002</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Treasury Reclamation Ticket Identifier</data><data key="node_domain">Payments and debt</data><data key="node_description">Reclamation ticket number retrieved from the TCIS Claims Detail tab for Treasury documentation requests.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0003"><data key="node_entity_id">R133_E0003</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">TCIS Reclamation Dashboard</data><data key="node_domain">Payments and debt</data><data key="node_description">Treasury Check Information System dashboard used to retrieve reclamation document images and status; different from TCIS Claims Detail tab.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0004"><data key="node_entity_id">R133_E0004</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Treasury-to-PSC Web-Paperless Document Interface</data><data key="node_domain">Payments and debt</data><data key="node_description">Documented electronic PDF transmission from Treasury into SSA processing-center Paperless through the Web-Paperless interface.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Transport/security protocol and physical staging data store not documented.</data></node><node id="R133_E0005"><data key="node_entity_id">R133_E0005</data><data key="node_entity_type">work_queue</data><data key="node_canonical_name">PSC Development Hold File</data><data key="node_acronym">DHF</data><data key="node_domain">Payments and debt</data><data key="node_description">Paperless action-control holding queue used to diary reclamation-document requests for 30 days and later follow-ups.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0006"><data key="node_entity_id">R133_E0006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Reclamation Documentation Request and Escalation</data><data key="node_domain">Payments and debt</data><data key="node_description">PSC checks TCIS and Paperless before requesting absent Treasury reclamation documents through TOFR, then documents and tracks follow-up.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0007"><data key="node_entity_id">R133_E0007</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Treasury FS-133 Notice of Reclamation</data><data key="node_acronym">FS-133</data><data key="node_domain">Payments and debt</data><data key="node_description">Treasury notice of reclamation to the financial institution, used as part of EFT reclamation and debt accounting.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0008"><data key="node_entity_id">R133_E0008</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Treasury FS-135 Request for Debit</data><data key="node_acronym">FS-135</data><data key="node_domain">Payments and debt</data><data key="node_description">Treasury request for debit of a financial institution account in an EFT reclamation workflow.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0009"><data key="node_entity_id">R133_E0009</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4208 Reclamation Correction Input</data><data key="node_acronym">SSA-4208</data><data key="node_domain">Payments and debt</data><data key="node_description">SSA processing-center accounting input that records adjustments or credits in Accounts Receivable System following reclamation actions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">SSA-4208 may be represented on a data-input page; not a new physical database.</data></node><node id="R133_E0010"><data key="node_entity_id">R133_E0010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Abandon Treasury Check Reclamation</data><data key="node_domain">Payments and debt</data><data key="node_description">SSA reverses an incorrectly initiated check reclamation when erroneous death/date of death caused retrieval of due funds.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0011"><data key="node_entity_id">R133_E0011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Abandon Treasury Electronic Funds Reclamation</data><data key="node_domain">Payments and debt</data><data key="node_description">Separate electronic funds transfer abandonment workflow that has restrictions when Treasury has already returned funds to SSA.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0012"><data key="node_entity_id">R133_E0012</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSI SSR Underpayment Suppression U-TAC</data><data key="node_domain">Title XVI and payments</data><data key="node_description">A U TAC posted to SSR in certain erroneous-death reclamation cases prevents a second incorrect underpayment release.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0013"><data key="node_entity_id">R133_E0013</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSI SSR PMTH Reclamation Credit Payflags 3S/5R</data><data key="node_domain">Title XVI and payments</data><data key="node_description">SSA describes payflag 3 S and payflag 5 R in SSR payment history as codes showing funds credited after reclamation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0014"><data key="node_entity_id">R133_E0014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Payment Reclamation Double-Recovery Exception</data><data key="node_domain">Payments and debt</data><data key="node_description">Reclamation amounts recovered from both a financial institution and another party require reconciliation and potential reversal; not a single normal payment record.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0015"><data key="node_entity_id">R133_E0015</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">PHUS Event 009 Returned Check</data><data key="node_domain">Payments and debt</data><data key="node_description">Returned Title II Treasury payment generally produces event 009 RET CHECK in the Payment History Update System.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0016"><data key="node_entity_id">R133_E0016</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">MBR/PHUS Returned Payment BSPA Reduction</data><data key="node_acronym">BSPA</data><data key="node_domain">Payments and debt</data><data key="node_description">A returned Title II payment generally reduces the BSPA amount on MBR and PHUS, subject to exception/manual processing.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0017"><data key="node_entity_id">R133_E0017</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Treasury Reclamation FI Response Waiting Period</data><data key="node_domain">Payments and debt</data><data key="node_description">Financial institutions generally have 60 days to respond to an EFT Notice of Reclamation before specified documentation escalations.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0018"><data key="node_entity_id">R133_E0018</data><data key="node_entity_type">analytical_model</data><data key="node_canonical_name">2026 SSI Recipient Transition Projection Model</data><data key="node_domain">Actuarial and statistical</data><data key="node_description">OACT 2026 annual SSI program projections use age/sex recipient and transition tabulations, Social Security area population, and federal payment tabulations.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Annual report describes a model; product/implementation technology unspecified.</data></node><node id="R133_E0019"><data key="node_entity_id">R133_E0019</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Historical Current and Suspended Recipient Age-Sex Input</data><data key="node_domain">Actuarial and statistical</data><data key="node_description">Historical tabulations of SSI recipients in current-payment and suspense status, separated by age, sex and eligibility category, are input to projections.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0020"><data key="node_entity_id">R133_E0020</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Recipient Status Transition Age-Sex Input</data><data key="node_domain">Actuarial and statistical</data><data key="node_description">Historical tabulations of entries to and exits from SSI current payment, by eligibility category age and sex, feed OACT projections.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0021"><data key="node_entity_id">R133_E0021</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Historical Federal Payment Age-Sex Input</data><data key="node_domain">Actuarial and statistical</data><data key="node_description">Historical federal payment totals by SSI eligibility class, age and sex are one of the four principal projection model inputs.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0022"><data key="node_entity_id">R133_E0022</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Projection Status Entry/Exit Classification</data><data key="node_domain">Actuarial and statistical</data><data key="node_description">SSI model separates entry from new award versus restoration from suspended status; exits include death, excess income, and other suspensions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0023"><data key="node_entity_id">R133_E0023</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Medical CDR Reconsideration EDCS-to-DCF/MBR Transfer</data><data key="node_domain">Disability and appeals</data><data key="node_description">For electronically transferred Title II medical CDR reconsiderations, EDCS transfer causes DCF and MBR updates with a five-day verification/manual exception rule.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0024"><data key="node_entity_id">R133_E0024</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS Exclusion Appeal Input Screen</data><data key="node_acronym">EEAI</data><data key="node_domain">Disability and appeals</data><data key="node_description">EDCS exclusion input screen used to record certain Title II medical CDR appeal requests into the DCF outside the ordinary EDCS appeal case.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0025"><data key="node_entity_id">R133_E0025</data><data key="node_entity_type">processing_program</data><data key="node_canonical_name">Title II Redesign CDR Appeal Background Program</data><data key="node_acronym">T2R</data><data key="node_domain">Disability and appeals</data><data key="node_description">Documented background program receives DCF appeal information and can update MBR in Title II CDR exception pathways.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Do not infer software language, scheduler, hosting or all-case coverage.</data></node><node id="R133_E0026"><data key="node_entity_id">R133_E0026</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DCF ALJT2EX CDR Hearing Appeal Tickle</data><data key="node_acronym">ALJT2EX</data><data key="node_domain">Disability and appeals</data><data key="node_description">DCF follow-up tickle for certain Title II excluded CDR hearing appeals, which may be absent from the DCF pending file and MI Central.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R133_E0027"><data key="node_entity_id">R133_E0027</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">General Dynamics Information Technology, Inc.</data><data key="node_acronym">GDIT</data><data key="node_domain">Procurement</data><data key="node_description">Federal contractor named in SSA Office of Acquisition and Grants November 2023 historical award listing.</data><data key="node_observed_status">historical_award_observed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Source establishes recipient of award, not installed technology or 2026 contract active status.</data></node><node id="R133_E0028"><data key="node_entity_id">R133_E0028</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA GDIT Database Platform Support Task Order 28321323FDX030127</data><data key="node_domain">Procurement</data><data key="node_description">SSA OAG lists task order under GS-35F-393CA on July 6, 2023, obligation $464,508, PSC DH01, scheduled completion June 8, 2028.</data><data key="node_observed_status">historical_award_observed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">November 2 2023 record; listed completion is planned, not proof work remained active or software deployed in 2026.</data></node><node id="R133_E0029"><data key="node_entity_id">R133_E0029</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA IBM Data Center Products Task Order 28321322FDS030217</data><data key="node_domain">Procurement</data><data key="node_description">SSA OAG lists IBM delivery/task order under SS00-16-60010 on September 9, 2022, obligation $64,000,000, data-center hardware PSC 7C20, scheduled completion March 31, 2026.</data><data key="node_observed_status">historical_award_observed</data><data key="node_observed_as_of">2026-10-08</data><data key="node_confidence">5</data><data key="node_notes">Does not specify model, architecture, actual installed hardware, or current hosting.</data></node><node id="R134_E0001"><data key="node_entity_id">R134_E0001</data><data key="node_entity_type">eligibility_rule</data><data key="node_canonical_name">October 2026 Medicaid Federal Matching Noncitizen Eligibility Restriction</data><data key="node_domain">Title XVI / Medicaid</data><data key="node_description">Federal financial participation for Medicaid coverage generally limited to qualifying residence and citizenship/immigration categories, with specified exceptions.</data><data key="node_observed_status">effective_2026-10-01</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Policy constrains federal financial participation; does not by itself establish new automated SSA eligibility determination or new data exchange.</data></node><node id="R134_E0002"><data key="node_entity_id">R134_E0002</data><data key="node_entity_type">eligibility_rule</data><data key="node_canonical_name">January 2027 SSI-Related Medicaid Two-Month Retroactivity Limit</data><data key="node_domain">Title XVI / Medicaid</data><data key="node_description">Documented prospective reduction in retroactive Medicaid eligibility window for qualifying SSI/State supplement cases from three months to two months.</data><data key="node_observed_status">prospective_not_yet_effective</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Effective 2027-01-01; not deployed as of 2026-10-09.</data></node><node id="R134_E0003"><data key="node_entity_id">R134_E0003</data><data key="node_entity_type">identity_rule</data><data key="node_canonical_name">Numident Employment Authorization Does Not Prove Current Title II Lawful Presence</data><data key="node_domain">Person/Identity Nexus / Title II</data><data key="node_description">Numident IDN H code shows permanent work authorization as of enumeration, but SSA requires independent current lawful-presence evidence or qualifying previous benefit proof.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0004"><data key="node_entity_id">R134_E0004</data><data key="node_entity_type">evidence_rule</data><data key="node_canonical_name">DHS SAVE Verification Response Documentary Evidence Retention Gate</data><data key="node_domain">Person/Identity Nexus / DHS</data><data key="node_description">Immigration documents and SAVE results are retained in electronic folder; evidence flags and supporting foreign identifiers must be separately documented for claims, rather than treating the response as automatic Numident change.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0005"><data key="node_entity_id">R134_E0005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DHS SAVE Inconclusive Response Additional Verification Decision</data><data key="node_domain">Person/Identity Nexus / DHS</data><data key="node_description">When online SAVE status cannot establish relevant lawful presence, SSA follows additional verification including documentary review or G-845 where instructed.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0006"><data key="node_entity_id">R134_E0006</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">SSA-8510 Pen-and-Ink Signature and Non-Attestation Requirement</data><data key="node_domain">Title XVI / Evidence / Identity</data><data key="node_description">SSA POMS SI 00601.100 expressly requires ink signature for SSA-8510 and prohibits replacing consent with claim attestation.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Public SSA Forms also lists electronic submission with additional identity verification: a scanned wet-signed submission could satisfy both. No finding that direct electronic signing is acceptable.</data></node><node id="R134_E0007"><data key="node_entity_id">R134_E0007</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Personal Information Authorization Documentation Page</data><data key="node_domain">Title XVI / Evidence / Identity</data><data key="node_description">Web page where employees document that a separately signed SSA-8510 authorization was secured; not itself an electronic SSA-8510.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0008"><data key="node_entity_id">R134_E0008</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">SSA-8510 Separate Authorization Per External Source</data><data key="node_domain">Title XVI / Evidence</data><data key="node_description">SSA directs employees to obtain one authorization for each third party requiring consent and restricts requests to identified sources/events.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0009"><data key="node_entity_id">R134_E0009</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">SSA-8510 Third-Party Authorization Source Exceptions</data><data key="node_domain">Title XVI / Evidence</data><data key="node_description">POMS separates SSA-8510 from SSA-4641 financial institution, SSA-8240 payroll data, and SSA-827 medical authorizations.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0010"><data key="node_entity_id">R134_E0010</data><data key="node_entity_type">claims_rule</data><data key="node_canonical_name">SSI N05 Historical Unconfirmed Eligibility After Good-Faith Evidence Exhaustion</data><data key="node_domain">Title XVI / Claims</data><data key="node_description">N05 can classify a past nonpayment period with good faith claimant action and exhaustive SSA development when precise past eligibility or amount cannot be confirmed; not an ongoing initial-claim status.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0011"><data key="node_entity_id">R134_E0011</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Initial Claim Evidence Request Thirty-Day and Incremental Extension Rule</data><data key="node_domain">Title XVI / Evidence</data><data key="node_description">SSA normally affords 30 days following SSA-L8009-U3 evidence request and may grant case-specific additional periods in increments up to 30 days.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0012"><data key="node_entity_id">R134_E0012</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DDS Consultative Examination Provider and Fee Schedule Annual November 15 Submission Deadline</data><data key="node_domain">Disability / DDS Oversight</data><data key="node_description">DDS providers list and current CE/MER fee schedules submitted within 45 days of the fiscal year end, generally by November 15.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0013"><data key="node_entity_id">R134_E0013</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">DDS CE Annual Provider Fraud Credential Complaint and Site-Visit Oversight Content</data><data key="node_domain">Disability / DDS Oversight</data><data key="node_description">Annual CE report covers complaints, provider fraud findings, credentials, onsite visits, quality reviews, provider-count shifts and fee changes.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0014"><data key="node_entity_id">R134_E0014</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">IRS Form 3857 SSN-Identity Case Postal Address Discovery Lead</data><data key="node_domain">Address Provenance / IRS / USPS</data><data key="node_description">When IRS requests taxpayer SSN reconciliation and a current postal address is needed, SSA may contact USPS using SSA-L2001; USPS output is a development lead, not documented master-record posting.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source dates from 2025; no persistence duration, auto MBR/SSR/Numident update path, or retention inference.</data></node><node id="R134_E0015"><data key="node_entity_id">R134_E0015</data><data key="node_entity_type">data_catalog</data><data key="node_canonical_name">SSA Authoritative Primary Data Asset Inventory</data><data key="node_domain">Enterprise Data / Publication</data><data key="node_description">Agency published comprehensive inventory of primary originating data assets and public endpoints, with CSV and JSON distributions, with no publication date established on the portal landing page.</data><data key="node_observed_status">public_snapshot</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Inventory listing is catalog metadata, not evidence of physical authoritative databases for each item.</data></node><node id="R134_E0016"><data key="node_entity_id">R134_E0016</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSA Open Data Asset Inventory CSV Distribution</data><data key="node_domain">Enterprise Data / Publication</data><data key="node_description">Public downloadable CSV representation of the SSA comprehensive primary data-asset inventory.</data><data key="node_observed_status">published_asset</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0017"><data key="node_entity_id">R134_E0017</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSA Open Data Asset Inventory JSON Distribution</data><data key="node_domain">Enterprise Data / Publication</data><data key="node_description">Public downloadable JSON representation of the SSA comprehensive primary data-asset inventory.</data><data key="node_observed_status">published_asset</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0018"><data key="node_entity_id">R134_E0018</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Leidos ITSSC Systems Task Order 28321322FDS030130</data><data key="node_domain">Procurement / IT Systems</data><data key="node_description">June 30, 2022, Leidos ITSSC systems task order, federal-award record identifies SSA award, duration and value; precise system stack and application-by-application responsibility are not specified.</data><data key="node_observed_status">historical_award_observed_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">USAspending indexed result showed circa $1.063B obligated and potential $1.204B; values are an observation snapshot, not fixed status or spend by district; parent contract SS001760016.</data></node><node id="R134_E0019"><data key="node_entity_id">R134_E0019</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Deloitte Consulting LLP</data><data key="node_domain">Procurement / Cybersecurity</data><data key="node_description">Contractor receiving SSA February 2025 organization-wide Cyber Security Risk Management program services task order.</data><data key="node_observed_status">federal_contract_vendor</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0020"><data key="node_entity_id">R134_E0020</data><data key="node_entity_type">governance_program</data><data key="node_canonical_name">SSA Cyber Security Risk Management Integrated Program</data><data key="node_domain">Cybersecurity / Governance</data><data key="node_description">Organization-wide CSRM program for leaders and executives to prioritize cyber risk; award description does not establish use of any particular vendor software.</data><data key="node_observed_status">contract_scope_documented</data><data key="node_observed_as_of">2025-02-14</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R134_E0021"><data key="node_entity_id">R134_E0021</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Deloitte CSRM Task Order 28321325FDX030061</data><data key="node_domain">Procurement / Cybersecurity</data><data key="node_description">SSA 2025 Cybersecurity Risk Management consulting delivery order to Deloitte with about $611,391 obligated in federal-award record.</data><data key="node_observed_status">completed_historical_award</data><data key="node_observed_as_of">2025-03-14</data><data key="node_confidence">5</data><data key="node_notes">One-month performance Feb 14 to Mar 14 2025 per USAspending award record; no inferred technology deployment.</data></node><node id="R134_E0022"><data key="node_entity_id">R134_E0022</data><data key="node_entity_type">policy_update</data><data key="node_canonical_name">October 2026 Compassionate Allowances Fourteen-Condition Addition</data><data key="node_domain">Disability / CAL</data><data key="node_description">Public SSA October 2026 update documents 14 additional severe-condition CAL classifications, bringing published list to 314.</data><data key="node_observed_status">announced_as_of_2026-10-01</data><data key="node_observed_as_of">2026-10-01</data><data key="node_confidence">5</data><data key="node_notes">CAL software flagging is confirmed generally; exact case-routing implementation not public. A CAL flag does not mean automatic award.</data></node><node id="R135_E0001"><data key="node_entity_id">R135_E0001</data><data key="node_entity_type">form</data><data key="node_canonical_name">CMS-2728-U3 End-Stage Renal Disease Medical Evidence Report</data><data key="node_acronym">CMS-2728-U3</data><data key="node_domain">Medicare / Medical Evidence</data><data key="node_description">Facility-signed form reporting dialysis/transplant dates and ESRD evidence; available paper or electronic printout.</data><data key="node_observed_status">documented_in_2026_poms</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0002"><data key="node_entity_id">R135_E0002</data><data key="node_entity_type">application</data><data key="node_canonical_name">ESRD Network Standard Information Management Systems</data><data key="node_acronym">SIMS</data><data key="node_domain">CMS / Health Data Exchange</data><data key="node_description">POMS names Standard Information Management Systems for ESRD Network entry of CMS-2728 information.</data><data key="node_observed_status">documented_not_current_deployment_verified</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Do not infer hosting, vendor, database, API, direct SSA integration or continuing deployment.</data></node><node id="R135_E0003"><data key="node_entity_id">R135_E0003</data><data key="node_entity_type">organization</data><data key="node_canonical_name">CMS End-Stage Renal Disease Networks</data><data key="node_acronym">ESRD Networks</data><data key="node_domain">CMS / External Partners</data><data key="node_description">Designated networks receive facility CMS-2728 copies and enter information through SIMS.</data><data key="node_observed_status">documented_in_2026_poms</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0004"><data key="node_entity_id">R135_E0004</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">ESRD Medicare Dialysis, Transplant and Training Dates</data><data key="node_acronym">ESRD clinical event dates</data><data key="node_domain">Medicare / Claims Evidence</data><data key="node_description">CMS-2728 has dialysis, transplant, self-training dates used to establish Medicare eligibility.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0005"><data key="node_entity_id">R135_E0005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">ESRD Medicare Field Office to Processing Center 7 Adjudication</data><data key="node_acronym">ESRD PC7</data><data key="node_domain">Medicare / Title II</data><data key="node_description">End-stage renal disease Medicare claim developed in FO using MCS or CMS-43 and referred to PC7; earnings limitations may require A101.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0006"><data key="node_entity_id">R135_E0006</data><data key="node_entity_type">form</data><data key="node_canonical_name">CMS-43 Application for Health Insurance Benefits Under Medicare for Chronic Renal Disease</data><data key="node_acronym">CMS-43</data><data key="node_domain">Medicare / Claims Intake</data><data key="node_description">Paper ESRD Medicare application entered into MCS by SSA field office.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0007"><data key="node_entity_id">R135_E0007</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS HIKD Kidney Dialysis and Transplant Screen</data><data key="node_acronym">HIKD</data><data key="node_domain">Medicare / Claims Intake</data><data key="node_description">MCS claims screen records relevant dialysis, transplant and training dates.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0008"><data key="node_entity_id">R135_E0008</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS ESRD Claim Input Screen</data><data key="node_acronym">ESRD screen</data><data key="node_domain">Medicare / Claims Intake</data><data key="node_description">MCS screen identifies filing under claimant, spouse or parent insured status for ESRD Medicare.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0009"><data key="node_entity_id">R135_E0009</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">MCS ESRD Cross-Reference SSN and Own-SSN Rule</data><data key="node_acronym">ESRD own SSN and IDN2</data><data key="node_domain">Person / Identity Nexus</data><data key="node_description">ESRD claim starts under claimant own SSN while cross-referencing other entitlement account and spouse or parent insured record.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0010"><data key="node_entity_id">R135_E0010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">CMS-2728 ESRD Medicare Protective Writing Decision</data><data key="node_acronym">ESRD protective writing</data><data key="node_domain">Medicare / Claims Policy</data><data key="node_description">A CMS-2728 can be protective writing when specific filing-intent requirements met; otherwise no protective filing is established.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0011"><data key="node_entity_id">R135_E0011</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Processing Center 7 for ESRD Medicare</data><data key="node_acronym">PC7</data><data key="node_domain">Medicare / Processing</data><data key="node_description">SSA POMS assigns Medicare ESRD adjudication jurisdiction to Processing Center 7.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0012"><data key="node_entity_id">R135_E0012</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA A101 ESRD Earnings Computation Processing Input</data><data key="node_acronym">A101</data><data key="node_domain">Medicare / Manual Exceptions</data><data key="node_description">Manual A101 required for ESRD Medicare claims in documented MCS earnings computation limitation.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0013"><data key="node_entity_id">R135_E0013</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Emergency Advance Same-Day MSSICS-to-SSR Posting Control</data><data key="node_acronym">EAP same-day</data><data key="node_domain">Title XVI / Payment Control</data><data key="node_description">EAP and IP must be established, approved and posted to SSR on same day before TPPS debit card issuance; otherwise overnight propagation issue.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0014"><data key="node_entity_id">R135_E0014</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI USDC Emergency Payment Evidence Portal Receipt</data><data key="node_acronym">SSA-8102 electronic copy</data><data key="node_domain">Title XVI / Payment Evidence</data><data key="node_description">Signed SSA-8102 file copy scanned/uploaded via Evidence Portal after USDC issuance; cashier copy retained for TPPS audit.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0015"><data key="node_entity_id">R135_E0015</data><data key="node_entity_type">governance_rule</data><data key="node_canonical_name">RZwiz NDNH Data Electronic Folder Redaction Requirement</data><data key="node_acronym">NDNH RZwiz redaction</data><data key="node_domain">Title XVI / Privacy</data><data key="node_description">When RZwiz worksheet is retained in electronic folder, remove the NDNH query and any NDNH data from saved worksheet.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0016"><data key="node_entity_id">R135_E0016</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">RZwiz Multi-SSN SSI Redetermination Review Sheet</data><data key="node_acronym">RZwiz worksheet</data><data key="node_domain">Title XVI / Identity Evidence</data><data key="node_description">RZwiz creates side-by-side worksheet from SSID, DEQY, SEQY and NDNH for SSNs associated with an SSR case; may be discarded after interview.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0017"><data key="node_entity_id">R135_E0017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRS SSI Alert Payer EIN Identification via DEQY</data><data key="node_acronym">IRS payer EIN development</data><data key="node_domain">Address Provenance / IRS</data><data key="node_description">For blank or implausible payer name/address in IRS match, obtain DEQY using payer EIN rather than requesting name/address data from IRS.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0018"><data key="node_entity_id">R135_E0018</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">IRS Alert Payer Name and Address Investigative Lead</data><data key="node_acronym">IRS payer address lead</data><data key="node_domain">Address Provenance / External Data</data><data key="node_description">Payer contact attributes on an IRS unearned-income alert used only to identify transaction source, not current SSI claimant residence.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0019"><data key="node_entity_id">R135_E0019</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Bank Account Title Versus Legally Accessible Resources</data><data key="node_acronym">account ownership verification</data><data key="node_domain">Title XVI / Financial Resources</data><data key="node_description">AFI ownership/title indicators require development of withdrawal rights, court restrictions and other factors before funds count as SSI resources.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0020"><data key="node_entity_id">R135_E0020</data><data key="node_entity_type">publication_rule</data><data key="node_canonical_name">HRS April 2026 Respondent Benefits Excludes Social Security Weights File</data><data key="node_acronym">HRS 2026 benefits weights exclusion</data><data key="node_domain">Research / Administrative Linkage</data><data key="node_description">April 2026 HRS Benefits product explicitly excludes Social Security Weights file; earlier Atlas distribution-with edge conflicts by release and requires dating.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0021"><data key="node_entity_id">R135_E0021</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">HRS 2022 Tracker Weights File Separate October 2026 Release</data><data key="node_acronym">HRS Tracker Weights v1</data><data key="node_domain">Research / Data Products</data><data key="node_description">HRS moved general tracker weights from Tracker File to separate Tracker Weights File beginning October 6, 2026; different from SSA restricted Social Security Weights.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R135_E0022"><data key="node_entity_id">R135_E0022</data><data key="node_entity_type">governance_rule</data><data key="node_canonical_name">HRS Linked SSA Benefits Geographic Merge Restriction</data><data key="node_acronym">HRS census division restriction</data><data key="node_domain">Research / Privacy</data><data key="node_description">HRS restrictions prohibit merging SSA-linked administrative data with geographic indicators below Census Division or other restricted datasets without permission.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R136_E0001"><data key="node_entity_id">R136_E0001</data><data key="node_entity_type">notice</data><data key="node_canonical_name">IRS First Backup Withholding B Notice</data><data key="node_domain">person/identity</data><data key="node_description">IRS mismatch notice relayed through a payer; the first notice can lead to taxpayer W-9 correction.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0002"><data key="node_entity_id">R136_E0002</data><data key="node_entity_type">notice</data><data key="node_canonical_name">IRS Second Backup Withholding B Notice</data><data key="node_domain">person/identity</data><data key="node_description">Second mismatch notice; SSA staff can resend current Numident information through SSNAP.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0003"><data key="node_entity_id">R136_E0003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSNAP IRS Update Transaction</data><data key="node_domain">identity/Numident</data><data key="node_description">Explicit SSNAP action sending current Numident identifying data to IRS, creating a new Numident iteration; no beneficiary address-update inference.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0004"><data key="node_entity_id">R136_E0004</data><data key="node_entity_type">data_change_event</data><data key="node_canonical_name">IRS Update Numident New Iteration Event</data><data key="node_domain">identity/Numident</data><data key="node_description">A procedural IRS Update in SSNAP creates a new Numident iteration even if the most recent Numident information was correct.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0005"><data key="node_entity_id">R136_E0005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">B-Notice SSN Versus EIN Classification</data><data key="node_domain">person/identity</data><data key="node_description">SSA must distinguish SSN from EIN including cases involving sole proprietorships; nine-digit values are not interchangeable.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0006"><data key="node_entity_id">R136_E0006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CMS State Buy-In Problem Email Escalation</data><data key="node_domain">Medicare/external exchange</data><data key="node_description">As of April 1 2026, state buy-in exceptions are submitted by email to the CMS designated mailbox rather than physical CMS-1957.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0007"><data key="node_entity_id">R136_E0007</data><data key="node_entity_type">organization</data><data key="node_canonical_name">CMS Division of Medicare System Exceptions and Interfaces</data><data key="node_domain">Medicare/external exchange</data><data key="node_description">CMS Medicare Ombudsman Group division designated to receive state buy-in problem escalations.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0008"><data key="node_entity_id">R136_E0008</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">CMS Buy-In Problem Follow-Up Holding File</data><data key="node_domain">Medicare/external exchange</data><data key="node_description">SSA servicing district or branch offices retain a problem-case control copy with approximately 30-business-day follow-up.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0009"><data key="node_entity_id">R136_E0009</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">CMS-1957 Physical Form Retirement Rule</data><data key="node_domain">Medicare/external exchange</data><data key="node_description">CMS no longer uses physical CMS-1957 beginning April 1 2026; historic form remains cataloged.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0010"><data key="node_entity_id">R136_E0010</data><data key="node_entity_type">transaction</data><data key="node_canonical_name">Health Insurance Replacement Card Request HCRQ</data><data key="node_domain">Medicare/address</data><data key="node_description">Request used by SSA to reissue Medicare cards; retyped address fields can transmit a card-address value to CMS without changing CMS records.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0011"><data key="node_entity_id">R136_E0011</data><data key="node_entity_type">query_screen</data><data key="node_canonical_name">HIQR Medicare Address Inquiry Screen ADDR</data><data key="node_domain">Medicare/address</data><data key="node_description">HI/SMI query flow exposes CMS address via QRHI ADDR screen for reconciliation against the MBR.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0012"><data key="node_entity_id">R136_E0012</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Medicare Card Mailing Address versus CMS Record Boundary</data><data key="node_domain">Medicare/address</data><data key="node_description">HCRQ request may pass an address for card mailing but expressly does not update CMS records when MBR is correct and CMS address is wrong.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0013"><data key="node_entity_id">R136_E0013</data><data key="node_entity_type">form</data><data key="node_canonical_name">CMS-2178-U2 Medicare Entitlement Problem Referral</data><data key="node_domain">Medicare/external exchange</data><data key="node_description">Referral used if Medicare enrollment/card interface cannot be reconciled through SSA actions.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0014"><data key="node_entity_id">R136_E0014</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">State Medicaid Eligibility File</data><data key="node_domain">Medicare/external exchange</data><data key="node_description">State-held eligibility record used to compare SSA State Data Exchange public welfare accretions.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0015"><data key="node_entity_id">R136_E0015</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Public Welfare Accretion Two-Month State Protest Control</data><data key="node_domain">Medicare/external exchange</data><data key="node_description">A state has two months after notification to annul a wrong accretion or establish a closed buy-in period.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0016"><data key="node_entity_id">R136_E0016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI ABLE Matched State Balance Auto-Update Rule</data><data key="node_domain">Title XVI/financial</data><data key="node_description">Once ABLE account information is documented, subsequent matching State reports automatically update account balance information in SSI Claims.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0017"><data key="node_entity_id">R136_E0017</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI ABLE New-Account Match Disposition</data><data key="node_domain">Title XVI/financial</data><data key="node_description">Pending State new-account data requires update/add/reject/decide-later action; decide-later must be resolved before closing certain case events.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0018"><data key="node_entity_id">R136_E0018</data><data key="node_entity_type">capability_limit</data><data key="node_canonical_name">SSI ABLE State Distribution Data Not Yet Available</data><data key="node_domain">Title XVI/financial</data><data key="node_description">As of observed POMS release, distributions are not available from the State ABLE exchange until a future systems release.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0019"><data key="node_entity_id">R136_E0019</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">CDR Five-Day Master-Record Update Control</data><data key="node_domain">disability/appeals</data><data key="node_description">DCF CDR Development Worksheet tickle of five days; verify SSR and MBR propagation and use manual exception action as needed.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0020"><data key="node_entity_id">R136_E0020</data><data key="node_entity_type">capability_limit</data><data key="node_canonical_name">CDR Appeal MI Central Only Exclusion Visibility</data><data key="node_domain">disability/appeals</data><data key="node_description">Appeals excluded from EDCS may be trackable in MI Central but not visible in EDCS.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0021"><data key="node_entity_id">R136_E0021</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">CDR Title II DIBCESS PCACS Follow-Up Gate</data><data key="node_domain">disability/payments</data><data key="node_description">If Title II MBR does not update within five days, staff examine DIBCESS PCACS issue, possible THIS exception, then escalate or manually correct.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0022"><data key="node_entity_id">R136_E0022</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Statutory Benefit Continuation Debt Finality Gate</data><data key="node_domain">Title II/payments/debt</data><data key="node_description">Continuation payments following medical cessation cannot be treated as overpayment until adverse determination is administratively final.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0023"><data key="node_entity_id">R136_E0023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II Overpayment Advance-Notice Collection Hold</data><data key="node_domain">Title II/payments/debt</data><data key="node_description">Advance notice with at least 30-day recovery window; timely debtor response can stop collection.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0024"><data key="node_entity_id">R136_E0024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II Inadequate Overpayment Notice Refund Correction</data><data key="node_domain">Title II/payments/debt</data><data key="node_description">Inadequate notice requires replacement notice, refund of previously withheld amounts, and revised recovery/balance control.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R136_E0025"><data key="node_entity_id">R136_E0025</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">DOS Passport Application SSN Verification Attribute Set</data><data key="node_domain">identity/external exchange</data><data key="node_description">Department of State passport verification request may include name, SSN, date of birth, sex and other identity information; does not imply DOS-to-Numident updates.</data><data key="node_observed_status">documented 2026-10-09</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Scope bound to cited policy and its effective date; does not establish undisclosed hosting, storage or interface transport.</data></node><node id="R137_E0001"><data key="node_entity_id">R137_E0001</data><data key="node_entity_type">external_interface_configuration</data><data key="node_canonical_name">eCBSV External OIDC Issuer Configuration</data><data key="node_domain">identity/external exchange</data><data key="node_description">Permitted entities configure OpenID Connect issuer and OAuth 2.0 settings for authenticating and authorizing external eCBSV access.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0002"><data key="node_entity_id">R137_E0002</data><data key="node_entity_type">identity_claim</data><data key="node_canonical_name">eCBSV OpenID Assertion End-User Permissions</data><data key="node_domain">identity/external exchange</data><data key="node_description">External permitted entity manages end-user permissions, which are supplied as attributes in its OpenID Connect assertion.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0003"><data key="node_entity_id">R137_E0003</data><data key="node_entity_type">test_registration_attribute</data><data key="node_canonical_name">eCBSV ETE OAuth Client Identifier</data><data key="node_domain">identity/external exchange</data><data key="node_description">SSA returns an External Testing Environment OAuth client ID after successful test-environment OIDC issuer registration.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0004"><data key="node_entity_id">R137_E0004</data><data key="node_entity_type">testing_constraint</data><data key="node_canonical_name">eCBSV ETE High-Volume Performance Test Prohibition</data><data key="node_domain">identity/external exchange</data><data key="node_description">SSA states its External Testing Environment is not for high-volume performance testing.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0005"><data key="node_entity_id">R137_E0005</data><data key="node_entity_type">exchange_payload</data><data key="node_canonical_name">eCBSV Verification Result Mismatch and Death Fields</data><data key="node_domain">identity/external exchange</data><data key="node_description">SSA verification API returns yes/no, nonmatching data element explanation, and a death indicator when SSA records show death.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0006"><data key="node_entity_id">R137_E0006</data><data key="node_entity_type">documented_external_interface_technology</data><data key="node_canonical_name">eCBSV REST JSON and JWT OAuth Security Stack</data><data key="node_domain">identity/external exchange</data><data key="node_description">SSA identifies OIDC, OAuth 2.0, JWT, JSON REST and JSON Web Encryption as relevant external technical concepts for directly integrated permitted entities.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Applies to published external eCBSV API, not a general SSA enterprise infrastructure claim.</data></node><node id="R137_E0007"><data key="node_entity_id">R137_E0007</data><data key="node_entity_type">federal_agency</data><data key="node_canonical_name">Social Security Administration (SSA)</data><data key="node_domain">agency/governance</data><data key="node_description">United States federal agency administering Social Security programs and providing intergovernmental administrative data under authorized agreements.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0008"><data key="node_entity_id">R137_E0008</data><data key="node_entity_type">exchange_governance_requirement</data><data key="node_canonical_name">CMA and IEA/F Dual Agreement Requirement for Federally Funded State Programs</data><data key="node_domain">external exchange</data><data key="node_description">State recipients of SSA data for federally funded state-administered programs must execute both a Computer Matching Agreement and IEA/F.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0009"><data key="node_entity_id">R137_E0009</data><data key="node_entity_type">agreement_type</data><data key="node_canonical_name">Reimbursable IEA State-Funded Program Agreement</data><data key="node_domain">external exchange</data><data key="node_description">R-IEA governs state access to SSA data for state-funded, state-administered benefit programs.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0010"><data key="node_entity_id">R137_E0010</data><data key="node_entity_type">agreement_type</data><data key="node_canonical_name">State Transmission Component Transfer Agreement</data><data key="node_domain">external exchange</data><data key="node_description">A separate STC agreement documents transfer/data flow terms and safeguards when an approved state agency receives SSA data through a State Transmission/Transfer Component.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0011"><data key="node_entity_id">R137_E0011</data><data key="node_entity_type">request_channel</data><data key="node_canonical_name">State SSA-157 Online Data Exchange Intake</data><data key="node_domain">external exchange</data><data key="node_description">SSA identifies an online SSA-157 Data Exchange Request Form for state, Tribal and territorial exchange inquiries.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0012"><data key="node_entity_id">R137_E0012</data><data key="node_entity_type">assessment_domain</data><data key="node_canonical_name">CSCRA Foreign Ownership Control and Influence Risk Topic</data><data key="node_domain">procurement/security</data><data key="node_description">SSA CSCRA questionnaire examines foreign ownership, control, and influence of third-party vendors and providers.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0013"><data key="node_entity_id">R137_E0013</data><data key="node_entity_type">assessment_domain</data><data key="node_canonical_name">CSCRA Offshore Labor and Remote Support Risk Topic</data><data key="node_domain">procurement/security</data><data key="node_description">SSA CSCRA questionnaire reviews non-US labor and remote service, maintenance and support locations.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0014"><data key="node_entity_id">R137_E0014</data><data key="node_entity_type">assessment_domain</data><data key="node_canonical_name">CSCRA Counterfeit Product and Imported Parts Risk Topic</data><data key="node_domain">procurement/security</data><data key="node_description">SSA CSCRA questionnaire reviews imported products and parts and counterfeit incident history.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0015"><data key="node_entity_id">R137_E0015</data><data key="node_entity_type">acquisition_security_control</data><data key="node_canonical_name">CSCRA Contractor Eligibility and Mitigating Controls Decision</data><data key="node_domain">procurement/security</data><data key="node_description">Preaward cybersecurity supply chain assessment informs vendor eligibility and required risk-mitigating controls.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0016"><data key="node_entity_id">R137_E0016</data><data key="node_entity_type">postaward_security_control</data><data key="node_canonical_name">CSCRM Third-Party Postaward Lifecycle Risk Review</data><data key="node_domain">procurement/security</data><data key="node_description">After award, SSA tracks third-party risk through onboarding, ongoing contract performance, and contract completion.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0017"><data key="node_entity_id">R137_E0017</data><data key="node_entity_type">oversight_finding</data><data key="node_canonical_name">GAO FY2024 SSA IT Operations Investment Board Oversight Gap</data><data key="node_domain">procurement/IT governance</data><data key="node_description">GAO found SSA IT Investment Review Board lacked a defined process to review operations/maintenance, infrastructure and cybersecurity investments representing about 90% of FY2024 IT spending.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">GAO public 2025 finding; not a current FY2026 remediation-completion assertion.</data></node><node id="R137_E0018"><data key="node_entity_id">R137_E0018</data><data key="node_entity_type">oversight_finding</data><data key="node_canonical_name">GAO FY2022-2024 IT Development Investment Performance Documentation Deficiency</data><data key="node_domain">procurement/IT governance</data><data key="node_description">GAO found incomplete ROI, value realization and performance evidence for selected developments in FY2022-2024 review.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0019"><data key="node_entity_id">R137_E0019</data><data key="node_entity_type">governance_recommendation</data><data key="node_canonical_name">GAO Operations IT Investment Operational Analysis Recommendation</data><data key="node_domain">procurement/IT governance</data><data key="node_description">GAO recommended regular investment analyses and an operations review process; January 2026 SSA responses described intended actions, not proven completion.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Status observed on the GAO page as open following January 2026 planned corrective action.</data></node><node id="R137_E0020"><data key="node_entity_id">R137_E0020</data><data key="node_entity_type">public_statistical_data_product</data><data key="node_canonical_name">OACT Disabled-Worker Applications Awards Payments and Terminations Time Series</data><data key="node_domain">actuarial/statistical</data><data key="node_description">OACT publishes disabled-worker data by calendar year, quarter and month on field office receipts, initial DDS receipts, awards, beneficiaries in current payment, terminations and termination rates.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0021"><data key="node_entity_id">R137_E0021</data><data key="node_entity_type">reporting_period_rule</data><data key="node_canonical_name">OACT Disabled-Worker Weekly Applications Reporting Calendar</data><data key="node_domain">actuarial/statistical</data><data key="node_description">Disabled-worker application workload is tabulated weekly; month has four or five weeks and quarter can have twelve or fourteen weeks, affecting apparent monthly movement.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0022"><data key="node_entity_id">R137_E0022</data><data key="node_entity_type">statistical_interpretation_rule</data><data key="node_canonical_name">OACT Disabled-Worker Awards-to-Applications Noncohort Ratio Limitation</data><data key="node_domain">actuarial/statistical</data><data key="node_description">OACT cautions same-period awards divided by applications is a crude ratio, not application-cohort allowance rate, because awards can stem from prior periods.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0023"><data key="node_entity_id">R137_E0023</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">OACT Disabled-Worker Calculated Termination Rate Method</data><data key="node_domain">actuarial/statistical</data><data key="node_description">OACT estimates terminations using change in entitled population and awards, with denominator approximated as beginning entitled population plus half awards during period.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0024"><data key="node_entity_id">R137_E0024</data><data key="node_entity_type">statistical_quality_note</data><data key="node_canonical_name">OACT Disability Awards Unedited Duplicate Warning</data><data key="node_domain">actuarial/statistical</data><data key="node_description">OACT warns unedited award data may include duplicate cases; award-data caveat applies particularly to data before 2014.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0025"><data key="node_entity_id">R137_E0025</data><data key="node_entity_type">advisory_recommendation</data><data key="node_canonical_name">SSAB Proposed Recipient-Viewable SSI Case Facts Snapshot</data><data key="node_domain">Title XVI/modernization</data><data key="node_description">SSAB proposed that beneficiaries and representatives be able to view SSI case facts and report processing status; no deployed SSI record portal is established.</data><data key="node_observed_status">proposed, not verified deployed</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Recommendation as of July 25, 2026, not system in production.</data></node><node id="R137_E0026"><data key="node_entity_id">R137_E0026</data><data key="node_entity_type">advisory_recommendation</data><data key="node_canonical_name">SSAB Proposed SSI Multi-Category Reporting Mobile Application</data><data key="node_domain">Title XVI/modernization</data><data key="node_description">SSAB proposed mobile SSI reporting of income, resources and living arrangements beyond existing monthly wage submission.</data><data key="node_observed_status">proposed, not verified deployed</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Advisory recommendation, not a product deployment.</data></node><node id="R137_E0027"><data key="node_entity_id">R137_E0027</data><data key="node_entity_type">advisory_finding</data><data key="node_canonical_name">SSAB Reported SSI Nonwage Change Reporting Digital Capability Gap</data><data key="node_domain">Title XVI/modernization</data><data key="node_description">SSAB July 2026 found recipients could not view full SSI record or verify change processing and online change reporting was limited relative to routine categories.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0028"><data key="node_entity_id">R137_E0028</data><data key="node_entity_type">logical_transaction_capture</data><data key="node_canonical_name">Online Title II Change-of-Address Submitted Transaction Capture</data><data key="node_domain">person/address provenance</data><data key="node_description">Official SSA Open Data states internet changes are sent to an unnamed database, subsequently update MBR, and transactions are stored in agency data stores and warehouses for volume reporting.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Publication does not identify a particular database technology or guarantee real-time posting.</data></node><node id="R137_E0029"><data key="node_entity_id">R137_E0029</data><data key="node_entity_type">logical_transaction_capture</data><data key="node_canonical_name">Online Title II Direct Deposit Change Transaction Capture</data><data key="node_domain">Title II/payments</data><data key="node_description">Official SSA Open Data states eligible beneficiary online direct-deposit updates are sent to a database, update MBR, and are captured in data stores/warehouses for aggregate reporting.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No specific physical staging or transport technology established.</data></node><node id="R137_E0030"><data key="node_entity_id">R137_E0030</data><data key="node_entity_type">data_attribute_group</data><data key="node_canonical_name">SSI Financial Institution Account Name Address and Exact Designation Record</data><data key="node_domain">address provenance/Title XVI</data><data key="node_description">POMS instructs technicians to document financial institution name and address, account numbers and exact designation on SSI Claims Financial Institution Accounts page. These are bank, not claimant, addresses.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0031"><data key="node_entity_id">R137_E0031</data><data key="node_entity_type">privacy_procedure</data><data key="node_canonical_name">AFI Automated Telephone Account Security Self-Entry Control</data><data key="node_domain">Title XVI/security</data><data key="node_description">When FI automated phone verification needs security answers or PIN, account holder enters them directly; SSA technician must not request them and must stop methods that compromise credentials.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0032"><data key="node_entity_id">R137_E0032</data><data key="node_entity_type">data_request_option</data><data key="node_canonical_name">e4641 Interest Verification Request Control</data><data key="node_domain">Title XVI/resources</data><data key="node_description">Technician can request interest information through eAFI and e4641 interest selection; paper SSA-4641 has its own interest selection rule.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0033"><data key="node_entity_id">R137_E0033</data><data key="node_entity_type">actuarial_time_dimension</data><data key="node_canonical_name">OACT 2026 Mortality Historical-versus-Projected Cutoff</data><data key="node_domain">actuarial/statistical</data><data key="node_description">2026 Trustees downloadable death probabilities and period life tables separate historical 1900–2023 data from projections for 2024–2100 across three alternative assumption sets.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0034"><data key="node_entity_id">R137_E0034</data><data key="node_entity_type">actuarial_statistical_rule</data><data key="node_canonical_name">OACT 2026 Cohort Life Table Birth-Year Reference Rule</data><data key="node_domain">actuarial/statistical</data><data key="node_description">Cohort life tables use birth year and survival probabilities at successive attained ages, whereas period life tables represent a single calendar-year mortality experience.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R137_E0035"><data key="node_entity_id">R137_E0035</data><data key="node_entity_type">interface_query_availability</data><data key="node_canonical_name">SSI IRS 5B Alert Most-Recent-Two-Tax-Year Availability Window</data><data key="node_domain">IRS/Title XVI/address provenance</data><data key="node_description">POMS SI 02310.045 documents most recent two IRS information years in an interface database retrievable through SUMS/MCAS MI Central and SSTNG. This is a query window, not a deletion-retention rule for IRS master data.</data><data key="node_observed_status">documented / applicability bounded to cited source</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">No inference of undocumentated hosting, database, transport, automatic master-record updates, or current deployment.</data></node><node id="R138_E0001"><data key="node_entity_id">R138_E0001</data><data key="node_entity_type">documented_business_process</data><data key="node_canonical_name">Medical Folder Multi-System Query Reconciliation</data><data key="node_domain">Disability/evidence</data><data key="node_description">When a medical folder cannot be found, employees compare FACT, PCACS, DDSQ, NUMI, OHAQ, QRSL, SSI and MCS development and work history, including other SSNs and prior records.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0002"><data key="node_entity_id">R138_E0002</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Offline CCTL Up-to-Six SSI Folder Location History</data><data key="node_domain">Evidence/folder provenance</data><data key="node_description">The Offline CCTL 8028/AR25 query can provide up to six previous SSI folder location entries to find a folder whose current location field is wrong.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0003"><data key="node_entity_id">R138_E0003</data><data key="node_entity_type">data_quality_constraint</data><data key="node_canonical_name">SSI CCTL Single-Line Location Overwrite Limitation</data><data key="node_domain">Evidence/folder provenance</data><data key="node_description">The case-control line can show the most recent folder location for multiple SSI records and can overwrite an older folder location, so the displayed current location may omit earlier file movement.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0004"><data key="node_entity_id">R138_E0004</data><data key="node_entity_type">data_quality_constraint</data><data key="node_canonical_name">PCACS Field-Office Folder Movement Date Limitation</data><data key="node_domain">Evidence/folder provenance</data><data key="node_description">FO input to PCACS may change a folder location without changing its date; the processing-center control record may not exist until the folder arrives at a PC or OCO.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0005"><data key="node_entity_id">R138_E0005</data><data key="node_entity_type">address_provenance_constraint</data><data key="node_canonical_name">Medical Folder Search MBR/SSID Address Movement Clue</data><data key="node_domain">Person/Address and Evidence</data><data key="node_description">Folder searches may review MBR change-of-address history, SSID TRANS and QRSL Address Query to infer a prior servicing field office; location history is not automatically a verified current residence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0006"><data key="node_entity_id">R138_E0006</data><data key="node_entity_type">identity_linkage_rule</data><data key="node_canonical_name">Medical Folder HUN/FUN and Previous-Spouse Cross-Reference Search</data><data key="node_domain">Person/Identity Nexus</data><data key="node_description">SSA directs folder investigators to search current and historical Housed Under Number and File Under Number, including an ex-spouse or parent SSN, to locate a disability file outside the claimant own SSN record.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0007"><data key="node_entity_id">R138_E0007</data><data key="node_entity_type">legal_use_constraint</data><data key="node_canonical_name">IRS Tax-Administration MBR Address Disclosure Routine-Use Gate</data><data key="node_domain">Address Provenance/IRS data</data><data key="node_description">An IRS tax-administration request for MBR benefit information including a stored address requires a valid IRS request and applicable MBR system-of-records routine use; SSA Privacy Act personnel coordinate disclosure.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0008"><data key="node_entity_id">R138_E0008</data><data key="node_entity_type">documented_access_window</data><data key="node_canonical_name">IRS Prior Ten-Year Federal Tax Information Retrieval in SSA Systems</data><data key="node_domain">IRS Data and Governance</data><data key="node_description">POMS GN 03313.060 says IRS can retrieve federal tax information within SSA systems, such as 1099s, W-2s and W-3s, within the last ten years without contacting SSA; its specific interface, retention and permissions are not documented here.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">A stated ten-year retrieval scope is not a verified universal retention requirement and is not equivalent to the SSI/IRS 5B two-most-recent-tax-years interface lookup window.</data></node><node id="R138_E0009"><data key="node_entity_id">R138_E0009</data><data key="node_entity_type">external_information_return</data><data key="node_canonical_name">IRS Form 8955-SSA Deferred Vested Participant Report</data><data key="node_domain">IRS/Pensions</data><data key="node_description">Employer-plan data reported on Form 8955-SSA supplies a three-digit plan number and nine-digit EIN to identify pension plans for deferred vested participant notices.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0010"><data key="node_entity_id">R138_E0010</data><data key="node_entity_type">publication_or_notice</data><data key="node_canonical_name">SSA-L99-C1 Notice of Potential Private Retirement Benefit</data><data key="node_domain">Title II / External IRS information</data><data key="node_description">SSA sends an SSA-L99-C1 notice with potential private deferred vested pension information supplied via IRS, on request or automatically upon a Social Security claim.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0011"><data key="node_entity_id">R138_E0011</data><data key="node_entity_type">third_party_address</data><data key="node_canonical_name">Private Pension Plan Administrator Mailing Address in IRS-Sourced SSA-L99-C1</data><data key="node_domain">Address Provenance/IRS data</data><data key="node_description">The notice includes the pension plan administrator name and address furnished with the IRS information; this is the employer-plan contact, not evidence of a beneficiary mailing or residence address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0012"><data key="node_entity_id">R138_E0012</data><data key="node_entity_type">external_identifier</data><data key="node_canonical_name">IRS Form 8955-SSA Twelve-Digit Plan Identifier</data><data key="node_domain">Person/Identity and Pensions</data><data key="node_description">For retrieval, SSA combines the 3-digit plan number and 9-digit EIN supplied on Form 8955-SSA to create a 12-digit plan identifier.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0013"><data key="node_entity_id">R138_E0013</data><data key="node_entity_type">address_provenance_constraint</data><data key="node_canonical_name">OASDI County Geography Representative-Payee Address Caveat</data><data key="node_domain">Geographic statistical publication</data><data key="node_description">For OASDI beneficiaries with representative payees, annual state/county tables designate the location of the representative payee, not necessarily the beneficiary residence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0014"><data key="node_entity_id">R138_E0014</data><data key="node_entity_type">statistical_transformation_rule</data><data key="node_canonical_name">OASDI County Disclosure-Controlled Rounding and Dollar Reweighting</data><data key="node_domain">Statistical data product</data><data key="node_description">Tables 4 and 5 protect small populations by controlled rounding county beneficiary counts to multiples of five, followed by proportional benefit-dollar adjustment; state totals remain true totals.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0015"><data key="node_entity_id">R138_E0015</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">OASDI State and County Flattened 1999-2025 Time Series</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">SSA publishes beta CSV and JSON 1999-to-latest flattened longitudinal tables 1 through 5, regenerated from annual HTML archives following corrections, with JSON field and metadata definitions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Years through 2025 on observation date. Dataset is refreshed annually and JSON schema/ids are explicitly beta; do not infer an internal database or ETL technology.</data></node><node id="R138_E0016"><data key="node_entity_id">R138_E0016</data><data key="node_entity_type">publication_pipeline</data><data key="node_canonical_name">OASDI Annual HTML-to-Flat-Series Regeneration</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">SSA states flattened OASDI CSV/JSON files are regenerated annually from archived annual HTML tables, including post-release corrections, rather than preserved immutable once published.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0017"><data key="node_entity_id">R138_E0017</data><data key="node_entity_type">data_semantics_rule</data><data key="node_canonical_name">OASDI Flattened Series ANSI County-Code Historic Null and String Handling</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">Flattened OASDI files insert null ANSI codes for years before 2008 and store 2-digit state and 5-digit county identifiers as strings preserving leading zeroes.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0018"><data key="node_entity_id">R138_E0018</data><data key="node_entity_type">data_contract_caveat</data><data key="node_canonical_name">OASDI Flattened Series Beta Schema Evolution Warning</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">SSA warns flattened series metadata and measure or dimension identifiers can change as the beta publication format develops.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0019"><data key="node_entity_id">R138_E0019</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">OASDI Flattened State-County Table 1 Machine-Readable Product</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">OASDI state/county Table 1 is available as a year-spanning JSON and CSV flattened time series; annual HTML, not individual record data, is the documented input.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0020"><data key="node_entity_id">R138_E0020</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">OASDI Flattened State-County Table 2 Machine-Readable Product</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">OASDI state/county Table 2 is available as a year-spanning JSON and CSV flattened time series; annual HTML, not individual record data, is the documented input.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0021"><data key="node_entity_id">R138_E0021</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">OASDI Flattened State-County Table 3 Machine-Readable Product</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">OASDI state/county Table 3 is available as a year-spanning JSON and CSV flattened time series; annual HTML, not individual record data, is the documented input.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0022"><data key="node_entity_id">R138_E0022</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">OASDI Flattened State-County Table 4 Machine-Readable Product</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">OASDI state/county Table 4 is available as a year-spanning JSON and CSV flattened time series; annual HTML, not individual record data, is the documented input.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0023"><data key="node_entity_id">R138_E0023</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">OASDI Flattened State-County Table 5 Machine-Readable Product</data><data key="node_domain">Public data and statistical publication</data><data key="node_description">OASDI state/county Table 5 is available as a year-spanning JSON and CSV flattened time series; annual HTML, not individual record data, is the documented input.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0024"><data key="node_entity_id">R138_E0024</data><data key="node_entity_type">coverage_rule</data><data key="node_canonical_name">SSI County Statistical Exclusion of State-Administered Supplement Payments</data><data key="node_domain">Title XVI/Public statistics</data><data key="node_description">The SSI by-state-and-county publication covers federal and federally administered state supplements; it excludes payments made under state-administered supplementation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0025"><data key="node_entity_id">R138_E0025</data><data key="node_entity_type">statistical_transformation_rule</data><data key="node_canonical_name">SSI County Statistical Suppression and County Versus State Total Difference</data><data key="node_domain">Title XVI/Public statistics</data><data key="node_description">SSI county values may be suppressed to protect individuals. States include suppressed values in totals; county payment sums may not equal state values due to rounding and unrounded computations.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0026"><data key="node_entity_id">R138_E0026</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">SSI State and County Flattened 1998-2025 Time Series</data><data key="node_domain">Title XVI/Public data</data><data key="node_description">SSI by-state-and-county beta flattened JSON/CSV includes tables 1 and 3 from 1998 onward and Table 2 from 1999 onward; available years extend through latest 2025 release.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Table 4 remains excluded from flat files because inconsistent structure across editions prevents straightforward concatenation.</data></node><node id="R138_E0027"><data key="node_entity_id">R138_E0027</data><data key="node_entity_type">publication_pipeline</data><data key="node_canonical_name">SSI Annual HTML-to-Flat-Series Regeneration</data><data key="node_domain">Title XVI/Public data</data><data key="node_description">SSA annually rebuilds the SSI flattened CSV/JSON series from the complete historical HTML archive including corrections.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0028"><data key="node_entity_id">R138_E0028</data><data key="node_entity_type">publication_limitation</data><data key="node_canonical_name">SSI Optional State Supplement Table 4 No Flattened File</data><data key="node_domain">Title XVI/Public data</data><data key="node_description">The annual SSI county report includes federally administered optional state supplementation Table 4, but SSA has not released a flat cross-year Table 4 due to historical table structure variations.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0029"><data key="node_entity_id">R138_E0029</data><data key="node_entity_type">data_semantics_rule</data><data key="node_canonical_name">SSI Flat Series ANSI Code and Suppression Sentinel Semantics</data><data key="node_domain">Title XVI/Public data</data><data key="node_description">Before 2009 ANSI county codes are null; state and county ANSI codes are string fields. Suppressed numeric measures are string X, and cross-year historical footnotes are standardized.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0030"><data key="node_entity_id">R138_E0030</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">SSI Flattened State-County Table 1 Machine-Readable Product</data><data key="node_domain">Title XVI/Public data</data><data key="node_description">SSI by-state-and-county Table 1 public JSON and CSV flattened historical annual series; not an individual SSI claimant record.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0031"><data key="node_entity_id">R138_E0031</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">SSI Flattened State-County Table 2 Machine-Readable Product</data><data key="node_domain">Title XVI/Public data</data><data key="node_description">SSI by-state-and-county Table 2 public JSON and CSV flattened historical annual series; not an individual SSI claimant record.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0032"><data key="node_entity_id">R138_E0032</data><data key="node_entity_type">statistical_table</data><data key="node_canonical_name">SSI Flattened State-County Table 3 Machine-Readable Product</data><data key="node_domain">Title XVI/Public data</data><data key="node_description">SSI by-state-and-county Table 3 public JSON and CSV flattened historical annual series; not an individual SSI claimant record.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0033"><data key="node_entity_id">R138_E0033</data><data key="node_entity_type">quality_assurance_sampling_process</data><data key="node_canonical_name">RSDI Quality Review Monthly MBR Transaction Sample</data><data key="node_domain">Program integrity/Title II</data><data key="node_description">SSA Quality Review randomly selects monthly cases from recently processed RSDI transactions or MBR updates, and reviewers verify eligibility, payments and documentary or external evidence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0034"><data key="node_entity_id">R138_E0034</data><data key="node_entity_type">security_and_fraud_workflow</data><data key="node_canonical_name">RSDI Quality Review Interviewer Verification and ARIS Referral</data><data key="node_domain">Person/Identity and Program integrity</data><data key="node_description">When beneficiaries verify a purported quality review contact, FO personnel may check employee identity using the Outlook Global Address List; suspicious contacts are referred through the Allegation Referral Intake System.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0035"><data key="node_entity_id">R138_E0035</data><data key="node_entity_type">quality_assurance_workflow</data><data key="node_canonical_name">SSA-93 Corrective Action Ninety-Day Deadline and Extension Record</data><data key="node_domain">Quality review/program integrity</data><data key="node_description">Servicing FO or PC corrects SSA-93-reported deficiencies within 90 days; authorized regional/OCO officials can approve documented extensions through SSA-93 website, which retains requests for audit.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0036"><data key="node_entity_id">R138_E0036</data><data key="node_entity_type">quality_assurance_workflow</data><data key="node_canonical_name">SSA-93 Rebuttal Forty-Five-Day Window</data><data key="node_domain">Quality review/program integrity</data><data key="node_description">Office disputing SSA-93 finding files a rebuttal through the quality review website within 45 calendar days and takes corrective action within 90 days of final rebuttal decision.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0037"><data key="node_entity_id">R138_E0037</data><data key="node_entity_type">quality_assurance_monitoring</data><data key="node_canonical_name">SSA-93 High-Risk Completed Correction Recheck</data><data key="node_domain">Quality review/program integrity</data><data key="node_description">Quality Review centrally examines cases flagged high risk when FO/PC mark corrections complete; website issues automated follow-ups every 15 days when work remains incomplete.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Scope is limited to cited public documentation. No undocumented physical architecture, persistence, or automatic propagation inferred.</data></node><node id="R138_E0038"><data key="node_entity_id">R138_E0038</data><data key="node_entity_type">address_provenance_constraint</data><data key="node_canonical_name">SSA ZIP+4 Postal Mail Formatting Is Not Residence Verification</data><data key="node_domain">Address Provenance/Mail</data><data key="node_description">SSA postal addressing standards require ZIP+4 software for mail delivery-line validation and formatting; successful standardization does not establish the addressee lives there or update any master record.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Formatting of delivery address is not evidence of residential occupancy; no undocumented persistence/record update assumed.</data></node><node id="R139_E0001"><data key="node_entity_id">R139_E0001</data><data key="node_entity_type">documented_organizational_responsibility</data><data key="node_canonical_name">OEEAS 2023 Enumeration Systems Support Responsibility</data><data key="node_domain">Person/Identity</data><data key="node_description">RM 10201.025 identifies Office of Earnings, Enumeration, and Administrative Systems as responsible for requirements, software maintenance, and updates to files used by enumeration, such as Numident.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0002"><data key="node_entity_id">R139_E0002</data><data key="node_entity_type">documented_organizational_responsibility</data><data key="node_canonical_name">OESAE DDBS 2023 Numident Database and Network Operations Responsibility</data><data key="node_domain">Infrastructure/identity</data><data key="node_description">The Office of Enterprise Support, Architecture, and Engineering Division of Data Systems is tasked with programming, operation, and maintenance of enumeration networks and databases including Numident.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0003"><data key="node_entity_id">R139_E0003</data><data key="node_entity_type">documented_business_process</data><data key="node_canonical_name">OTSO SSN Card Print Control-Number Posting Process</data><data key="node_domain">Enumeration/identity</data><data key="node_description">Office of Telecommunications and Systems Operations prints and mails SSN cards and ensures the card control number is captured and posted to Numident.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0004"><data key="node_entity_id">R139_E0004</data><data key="node_entity_type">documented_business_process</data><data key="node_canonical_name">PSC Numident-MBR Enumeration Discrepancy Corrections</data><data key="node_domain">Identity/Title II</data><data key="node_description">Program Service Centers handle SSN card applications triggered by Numident/MBR discrepancies, key certain Numident corrections, and maintain cross-references.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0005"><data key="node_entity_id">R139_E0005</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">EBE Pending SSNAP SSN-Card Mailing Address Recheck</data><data key="node_domain">Person/address provenance</data><data key="node_description">RM 10205.700 directs staff to check applicant mailing address when locating a pending EBE SSNAP record; a changed address or elapsed nonreceipt period leads to a replacement card application. This is not an automatic MBR/SSR or Numident residential-address update.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0006"><data key="node_entity_id">R139_E0006</data><data key="node_entity_type">data_attribute_set</data><data key="node_canonical_name">EBE Pending SSNAP Application Alternate-Identity Matching Fields</data><data key="node_domain">Enumeration/identity</data><data key="node_description">Employee compares pending application ARN, name, date of birth, place of birth, parent names, telephone and mailing address with identity evidence before completing EBE exception processing.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0007"><data key="node_entity_id">R139_E0007</data><data key="node_entity_type">external_program_integrity_data</data><data key="node_canonical_name">OIG-to-Central-Office Representative Payee Conviction List</data><data key="node_domain">Representative payee</data><data key="node_description">OIG provides a list of specified Social Security Act and representative-payee fraud convictions to SSA central staff, who relay it through regional staff for entry into eRPS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0008"><data key="node_entity_id">R139_E0008</data><data key="node_entity_type">documented_business_process</data><data key="node_canonical_name">Regional eRPS Conviction-List Manual Entry Step</data><data key="node_domain">Representative payee/integrity</data><data key="node_description">SSA POMS says regional staff input OIG-supplied conviction lists into eRPS, a human entry step rather than a verified automated OIG interface.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0009"><data key="node_entity_id">R139_E0009</data><data key="node_entity_type">eligibility_decision_rule</data><data key="node_canonical_name">eRPS Mandatory Nonselection on Specified Fraud-Conviction Alert</data><data key="node_domain">Representative payee/program integrity</data><data key="node_description">When documented barred-conviction alert appears, eRPS prevents payee selection; permitted staff must record non-selection reason and give notice.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0010"><data key="node_entity_id">R139_E0010</data><data key="node_entity_type">program_integrity_alert</data><data key="node_canonical_name">eRPS Numident-versus-MBR-SSR Death Discrepancy Alert</data><data key="node_domain">Person/identity/payee</data><data key="node_description">eRPS displays NUMI death alert when Numident death information conflicts with MBR or SSR, and employees must investigate the conflict before selecting payee.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0011"><data key="node_entity_id">R139_E0011</data><data key="node_entity_type">identity_quality_control</data><data key="node_canonical_name">eRPS Applicant Client-Numident Identity Mismatch Alert</data><data key="node_domain">Person/identity/payee</data><data key="node_description">Applicant SSN and eRPS client identity information are compared with Numident; selection or nonselection requires resolving mismatched records.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0012"><data key="node_entity_id">R139_E0012</data><data key="node_entity_type">case_control_rule</data><data key="node_canonical_name">eRPS Prior-Payee Postdeath Overpayment Evidence 180-Day Follow-Up</data><data key="node_domain">Representative payee/payments</data><data key="node_description">For specified evidence of repayment or pending waiver/appeal, eRPS creates a 180-day follow-up issue and alerts when evidence expires.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0013"><data key="node_entity_id">R139_E0013</data><data key="node_entity_type">exception_handling_process</data><data key="node_canonical_name">eRPS Vendor-Communication-Error Background-Check Fallback</data><data key="node_domain">Representative payee/vendor</data><data key="node_description">If integrated eRPS criminal background check has a vendor communication error, staff must perform background check outside eRPS with LexisNexis Accurint and obtain manager confirmation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0014"><data key="node_entity_id">R139_E0014</data><data key="node_entity_type">quality_control_attribute</data><data key="node_canonical_name">eRPS Manager Background-Check Completion Confirmation</data><data key="node_domain">Representative payee/program integrity</data><data key="node_description">Manager must confirm completion of out-of-system background check by indicating background check completed on Selection-Required Notes screen.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0015"><data key="node_entity_id">R139_E0015</data><data key="node_entity_type">disclosure_delivery_workflow</data><data key="node_canonical_name">eView Certified eFolder PDF Send-to-mySSA Message Center</data><data key="node_domain">Disability/evidence</data><data key="node_description">DI 81001.035 directs staff to create selected eFolder PDF and use eView Send to mySSA, delivering to claimant Message Center; transaction success/failure is reported.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0016"><data key="node_entity_id">R139_E0016</data><data key="node_entity_type">disclosure_delivery_workflow</data><data key="node_canonical_name">eView Certified eFolder Encrypted-PDF Secure Email Delivery</data><data key="node_domain">Disability/evidence</data><data key="node_description">DI 81001.035 documents encrypted PDF secure-email export requiring password, address selection and sender authentication; staff record disclosure in eView.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0017"><data key="node_entity_id">R139_E0017</data><data key="node_entity_type">audit_control</data><data key="node_canonical_name">eView Electronic-Folder Disclosure Message Audit Annotation</data><data key="node_domain">Disability/evidence</data><data key="node_description">After sending selected eFolder documents, staff annotate eView Alerts and Messages with what was copied, recipient and date; POMS directs not to set an expiration date on the message.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0018"><data key="node_entity_id">R139_E0018</data><data key="node_entity_type">access_disclosure_control</data><data key="node_canonical_name">CEF Sensitive Document Indicator Disclosure Exclusion</data><data key="node_domain">Disability/evidence</data><data key="node_description">Employees identify documents that cannot be released with the eView Sensitive Document Indicator; such documents are not selected for electronic folder CD/PDF disclosure.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0019"><data key="node_entity_id">R139_E0019</data><data key="node_entity_type">data_classification_rule</data><data key="node_canonical_name">CEF Hearing Audio Exhibits Included in Official Disability Record</data><data key="node_domain">Hearings/evidence</data><data key="node_description">Hearing audio and indexing files kept as exhibits are part of official record and may be copied via eView when case is not pending in OHO or OAO; internal hearing notes are not released.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0020"><data key="node_entity_id">R139_E0020</data><data key="node_entity_type">oversight_finding</data><data key="node_canonical_name">GAO 2025 SSA CIO Eleven Open IT Recommendations</data><data key="node_domain">Governance/IT</data><data key="node_description">GAO-25-108464 identifies 11 outstanding recommendations under SSA CIO purview in July 2025, one classified priority, related to cybersecurity and IT acquisition/management.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Historical recommendation count as of July 2025 only. Current status has not been independently verified.</data></node><node id="R139_E0021"><data key="node_entity_id">R139_E0021</data><data key="node_entity_type">oversight_recommendation</data><data key="node_canonical_name">GAO Recommended SSA Federal Event-Logging Requirements Completion</data><data key="node_domain">Cybersecurity</data><data key="node_description">GAO identifies prior recommendation to fully implement event-logging requirements for detecting, investigating and remediating cyber threats.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">GAO reported recommendation open July 2025; no evidence of Oct 2026 completion status.</data></node><node id="R139_E0022"><data key="node_entity_id">R139_E0022</data><data key="node_entity_type">oversight_recommendation</data><data key="node_canonical_name">GAO SSA Purchased-versus-Active Software License Inventory Reconciliation Recommendation</data><data key="node_domain">IT asset governance</data><data key="node_description">GAO identifies recommendation to compare active software license inventories against acquired licenses for cost and investment decisions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Recommendation status as of July 2025; not proof particular license tool or remediation state.</data></node><node id="R139_E0023"><data key="node_entity_id">R139_E0023</data><data key="node_entity_type">actuarial_model_assumption</data><data key="node_canonical_name">2026 SSI Projection Scheduled-OASDI Benefit Offset Assumption</data><data key="node_domain">Actuarial/Title XVI</data><data key="node_description">2026 SSI annual report projects SSI payments net of scheduled Social Security benefits despite Trustees Report intermediate projection of possible OASI reserve depletion during the SSI projection window.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0024"><data key="node_entity_id">R139_E0024</data><data key="node_entity_type">actuarial_uncertainty</data><data key="node_canonical_name">SSI Projection Potential OASI Depletion Offset-Sensitivity Caveat</data><data key="node_domain">Actuarial/solvency</data><data key="node_description">OACT warns payable OASI benefit reductions after potential reserve depletion could result in higher SSI payments than model estimates, depending on how reductions occur.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0025"><data key="node_entity_id">R139_E0025</data><data key="node_entity_type">actuarial_model_input_dimension</data><data key="node_canonical_name">OACT Labor Force Model Age-Sex-Marital-Status-Children Dimensions</data><data key="node_domain">Actuarial/modeling</data><data key="node_description">2026 Trustees economic methods state actuarial service projects civilian labor force by age, sex, marital status and presence of children.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0026"><data key="node_entity_id">R139_E0026</data><data key="node_entity_type">actuarial_assumption_rule</data><data key="node_canonical_name">OACT Labor Force Participation Disability and Retirement Input Factors</data><data key="node_domain">Actuarial/modeling</data><data key="node_description">Labor force participation projections reflect disability prevalence, education, marriage, mean retirement benefit, economic conditions and life expectancy, under alternative assumptions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0027"><data key="node_entity_id">R139_E0027</data><data key="node_entity_type">statistical_publication</data><data key="node_canonical_name">Annual Statistical Supplement 2025 March 2026 Edition</data><data key="node_domain">Statistical data products</data><data key="node_description">2025 Annual Statistical Supplement completed March 2026 with administrative statistics; original edition later received official correction.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0028"><data key="node_entity_id">R139_E0028</data><data key="node_entity_type">statistical_correction_event</data><data key="node_canonical_name">2025 Statistical Supplement 6.D9 April 16 2026 Lump-Sum Payment Erratum</data><data key="node_domain">Statistical data quality</data><data key="node_description">SSA posted an erratum 2026-04-16 correcting the number of 2024 lump-sum payments in Table 6.D9 of the 2025 Supplement.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0029"><data key="node_entity_id">R139_E0029</data><data key="node_entity_type">records_lifecycle_rule</data><data key="node_canonical_name">SSA Vendor Information Repository Approximate One-Year Deletion Policy</data><data key="node_domain">Procurement/data governance</data><data key="node_description">OAG vendor repository instructions state vendor capability information remains approximately one year and is then deleted unless resubmitted.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0030"><data key="node_entity_id">R139_E0030</data><data key="node_entity_type">intake_quality_control</data><data key="node_canonical_name">SSA Vendor Repository Email Capability Submission 5MB Limit</data><data key="node_domain">Procurement/market research</data><data key="node_description">OAG instructions direct capability statements to designated vendor repository mailbox with sender name, subject and up to three tags; messages including attachments should be at most 5MB.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0031"><data key="node_entity_id">R139_E0031</data><data key="node_entity_type">access_use_rule</data><data key="node_canonical_name">SSA Vendor Repository All-Component Market Research Access</data><data key="node_domain">Procurement/data governance</data><data key="node_description">OAG instructs that vendor capability materials are available to SSA components for market research, not a qualified bidding list or contract award guarantee.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0032"><data key="node_entity_id">R139_E0032</data><data key="node_entity_type">data_release_attribute</data><data key="node_canonical_name">HRS April 2026 Detailed Earnings 869743 Employer-Year Records</data><data key="node_domain">Research/MEF</data><data key="node_description">Restricted HRS Respondent Cross-Year Detail Earnings contains 869,743 respondent/year/employer records for 25,179 consenting respondents with earnings in 1978-2023.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0033"><data key="node_entity_id">R139_E0033</data><data key="node_entity_type">data_quality_constraint</data><data key="node_canonical_name">HRS Detailed Earnings 1978-1979 Incomplete Data Warning</data><data key="node_domain">Research/MEF</data><data key="node_description">HRS warns its 1978 and 1979 detailed earnings years are incomplete, and reports the April 2026 version supersedes earlier detail releases.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0034"><data key="node_entity_id">R139_E0034</data><data key="node_entity_type">publication_distribution_constraint</data><data key="node_canonical_name">HRS April 2026 Detail Earnings Excludes Social Security Weights</data><data key="node_domain">Research/administrative linkage</data><data key="node_description">HRS April 2026 Respondent Cross-Year Detail Earnings distribution explicitly excludes the Social Security Weights file; linkage and geographic merge restrictions apply.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0035"><data key="node_entity_id">R139_E0035</data><data key="node_entity_type">transaction_processing_rule</data><data key="node_canonical_name">SERS Multi-Debtor SSN-By-SSN Shopping Cart Entry</data><data key="node_domain">Title II/Title XVI debt</data><data key="node_description">SSA requires staff to query each debtor SSN separately and add selected programmatic debts into a shopping cart for multi-debtor remittance; aux beneficiary debts appear on beneficiary own SSN.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R139_E0036"><data key="node_entity_id">R139_E0036</data><data key="node_entity_type">exception_handling_process</data><data key="node_canonical_name">SERS Debt Web-Service Failure Legacy DMS Remittance Fallback</data><data key="node_domain">Payment/debt</data><data key="node_description">If SERS or its debt-retrieval web service fails or omits known debts, employees use specified legacy DMS procedures to process remittance.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Official document states the named process/rule; physical implementation, universal deployment, retention, and automatic updates not presumed.</data></node><node id="R140_E0001"><data key="node_entity_id">R140_E0001</data><data key="node_entity_type">address_routing_attribute</data><data key="node_canonical_name">Person Information Mailing ZIP for Upload Documents Work Assignment</data><data key="node_domain">person/address/digital intake</data><data key="node_description">For customer-initiated Upload Documents, SSA uses the ZIP from Person Information mailing address to choose the recipient field office, not verified residence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0002"><data key="node_entity_id">R140_E0002</data><data key="node_entity_type">document_routing_rule</data><data key="node_canonical_name">Customer-Initiated Upload Documents ZIP-Based Field Office Routing</data><data key="node_domain">Digital intake / address provenance</data><data key="node_description">SSA routes successfully submitted forms to the field office associated with the mailing-address ZIP code in Person Information.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0003"><data key="node_entity_id">R140_E0003</data><data key="node_entity_type">conditional_intake_rule</data><data key="node_canonical_name">Upload Documents Missing Person Information Address ZIP Collection</data><data key="node_domain">Digital intake / address provenance</data><data key="node_description">If no mailing address is on file in Person Information, customers supply a mailing ZIP code before submission for work routing; this collection alone is not an authoritative address change.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0004"><data key="node_entity_id">R140_E0004</data><data key="node_entity_type">work_control_artifact</data><data key="node_canonical_name">Upload Documents Field Office WorkTrack Intake and Technician Assignment</data><data key="node_domain">Digital intake / workload</data><data key="node_description">All customer-submitted documents reach the field office via WorkTrack and require assignment to a technician.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0005"><data key="node_entity_id">R140_E0005</data><data key="node_entity_type">digital_service_eligibility_rule</data><data key="node_canonical_name">March 2025 Customer-Initiated Upload Forms-Only Scope</data><data key="node_domain">Digital service / modernization</data><data key="node_description">EM-25024 states 2025-03-29 self-initiated option was for forms; customer-initiated evidence planned for later release, technician evidence tasks available.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0006"><data key="node_entity_id">R140_E0006</data><data key="node_entity_type">digital_form_scope_rule</data><data key="node_canonical_name">Upload Documents March 2025 Technician-Only Benefit Application Form Set</data><data key="node_domain">Digital forms / signature</data><data key="node_description">Forms SSA-1, SSA-2, SSA-8, SSA-10, SSA-8000, SSA-8001, and HA-520 remained technician-initiated via TED as of March 2025.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0007"><data key="node_entity_id">R140_E0007</data><data key="node_entity_type">intra_application_update_rule</data><data key="node_canonical_name">eRPS Capability Note Application Summary-to-Beneficiary Notes Propagation</data><data key="node_domain">Representative payee / person</data><data key="node_description">Saving a Bene Capability Determination note in a new eRPS payee application automatically propagates the determination from application Summary notes to Beneficiary Details notes.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0008"><data key="node_entity_id">R140_E0008</data><data key="node_entity_type">case_documentation_rule</data><data key="node_canonical_name">eRPS Previously Established Beneficiary Capability Note Without New Payee Application</data><data key="node_domain">Representative payee / person</data><data key="node_description">When the beneficiary has an existing eRPS record but no new payee application, staff document the capability decision in Beneficiary Details notes.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0009"><data key="node_entity_id">R140_E0009</data><data key="node_entity_type">administrative_fallback_process</data><data key="node_canonical_name">Capability Determination When eRPS Beneficiary Record Does Not Exist</data><data key="node_domain">Person / representative payee</data><data key="node_description">Without a beneficiary eRPS case, staff document Title II and concurrent capability in MCS Report of Contact or Title XVI-only capability in CCE Report of Contact.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0010"><data key="node_entity_id">R140_E0010</data><data key="node_entity_type">evidence_retention_route</data><data key="node_canonical_name">Capability Determination SSA-5002 Document Repository Fallback</data><data key="node_domain">Person / representative payee</data><data key="node_description">If an MCS/CCE report cannot be established, use SSA-5002 and store it in NDRed or eView through Evidence Portal/eView.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0011"><data key="node_entity_id">R140_E0011</data><data key="node_entity_type">evidence_hierarchy_rule</data><data key="node_canonical_name">SSI Primary and Secondary Wage Evidence Acquisition Priority</data><data key="node_domain">Title XVI / earnings</data><data key="node_description">Policy prioritizes PIE payroll-provider wage records, then pay stubs, SSA-approved verifier information, then other official queries (NDNH/MEF/state) with additional documentation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0012"><data key="node_entity_id">R140_E0012</data><data key="node_entity_type">conditional_automated_update</data><data key="node_canonical_name">PIE EIN-Matched Automated SSI Claim Wage Page Posting</data><data key="node_domain">Title XVI / external earnings exchange</data><data key="node_description">Payroll-provider wages through PIE generally automatically post to SSI Claims Wages page when identifying attributes such as EIN match the SSA record.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0013"><data key="node_entity_id">R140_E0013</data><data key="node_entity_type">update_timing_rule</data><data key="node_canonical_name">PIE SSI Monthly Payroll Update Before Goldberg-Kelly Notice Cutoff</data><data key="node_domain">Title XVI / earnings</data><data key="node_description">Payroll-provider wage information generally updates monthly before Goldberg-Kelly cutoff; not a real-time guarantee.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0014"><data key="node_entity_id">R140_E0014</data><data key="node_entity_type">evidence_classification</data><data key="node_canonical_name">NDNH MEF and State Wage Queries as Secondary SSI Evidence</data><data key="node_domain">Title XVI / earnings data</data><data key="node_description">When primary sources unavailable, NDNH, state inquiry, MEF/W-2, and iTOPSS are secondary wage evidence subject to documentation requirements.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0015"><data key="node_entity_id">R140_E0015</data><data key="node_entity_type">privacy_access_rule</data><data key="node_canonical_name">Non-Approved Wage Verification Website PII Entry Prohibition</data><data key="node_domain">Title XVI / program integrity</data><data key="node_description">SSA staff must not establish online accounts or enter claimant PII at non-SSA-approved wage verification company websites.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0016"><data key="node_entity_id">R140_E0016</data><data key="node_entity_type">evidence_state_rule</data><data key="node_canonical_name">SSI Monthly Wages Reported Versus Verified Evidence Status</data><data key="node_domain">Title XVI / program integrity</data><data key="node_description">SSR distinguishes alleged, reported, and verified wage values; reports marked code 0 can require redevelopment under diary and other specified exceptions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0017"><data key="node_entity_id">R140_E0017</data><data key="node_entity_type">cross_agency_business_process</data><data key="node_canonical_name">Erroneous Death Medicare Advantage and Part D Reinstatement Procedure</data><data key="node_domain">Medicare / death / program integrity</data><data key="node_description">After erroneous SSA death reporting causes CMS plan disenrollment, SSA repairs its records and Part A/B/Title II eligibility as applicable before a manager/authorized PC technician requests CMS Part C/D reinstatement.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0018"><data key="node_entity_id">R140_E0018</data><data key="node_entity_type">dependency_rule</data><data key="node_canonical_name">CMS Part C and D Restoration Prerequisite SSA Record Correction</data><data key="node_domain">Medicare / death</data><data key="node_description">CMS is responsible for plan reinstatement, but SSA must correct death and restore its applicable benefits and Part A/B before referral.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0019"><data key="node_entity_id">R140_E0019</data><data key="node_entity_type">system_scope_limitation</data><data key="node_canonical_name">MAPS Part D Enrollment Visibility Conditional on LIS or Title II Premium Withholding</data><data key="node_domain">Medicare / program records</data><data key="node_description">MAPS may not display Part D for individuals without LIS who are not paying their Part D/MA premiums through Title II withholding.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0020"><data key="node_entity_id">R140_E0020</data><data key="node_entity_type">priority_rule</data><data key="node_canonical_name">Medicare Part C/D Life-Sustaining Medication Reinstatement Priority</data><data key="node_domain">Medicare / urgent service</data><data key="node_description">When erroneous-death disenrollment deprives beneficiary of life-sustaining medication, SSA referral states days of medication remaining and CMS prioritizes urgent reinstatement.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0021"><data key="node_entity_id">R140_E0021</data><data key="node_entity_type">internal_workflow_form</data><data key="node_canonical_name">Medicare Parts C and D Priority Case Referral Tracking Form</data><data key="node_domain">Medicare / interagency referrals</data><data key="node_description">SSA form in internal cmsreferral workflow tracks urgent Medicare Advantage/Part D correction after an erroneous death; internal endpoint is not proof of database technology.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0022"><data key="node_entity_id">R140_E0022</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">CMS MA and Part D Restoration Referral Authorized Requester Gate</data><data key="node_domain">Medicare / interagency service</data><data key="node_description">Only FO manager or designated payment-center technician may request CMS to reinstate Part C/D enrollment after incorrect death report.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0023"><data key="node_entity_id">R140_E0023</data><data key="node_entity_type">conditional_referral_rule</data><data key="node_canonical_name">CMS-2178-U2 Split Routing for MBR Versus HI Master Corrections</data><data key="node_domain">Medicare / address provenance</data><data key="node_description">If both MBR and HI incorrect, try POS or Paperless referral to PC; if only HI record incorrect, send CMS-2178-U2 to CMS by email.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0024"><data key="node_entity_id">R140_E0024</data><data key="node_entity_type">work_control_rule</data><data key="node_canonical_name">CMS-2178-U2 Medicare Entitlement 30-Day Follow-Up and 90-Day Escalation</data><data key="node_domain">Medicare / interagency exceptions</data><data key="node_description">Referral instructions provide 30-working-day follow-up and escalation at 90 calendar days if unresolved, depending on correction scenario.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0025"><data key="node_entity_id">R140_E0025</data><data key="node_entity_type">data_provenance_rule</data><data key="node_canonical_name">SSI Tax Match Taxpayer Versus Payee Versus Payer Role Semantics</data><data key="node_domain">IRS / Person / Address provenance</data><data key="node_description">IRS/MEF alert taxpayer is SSN under which transaction was reported, payee is person or organization on payer records, payer submitted report; payee may be a third party using taxpayer SSN.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0026"><data key="node_entity_id">R140_E0026</data><data key="node_entity_type">data_use_restriction</data><data key="node_canonical_name">SSI Tax Data Alert Name Address and SSN Restricted Tax-Data Classification</data><data key="node_domain">IRS / Address provenance</data><data key="node_description">Tax alert taxpayer name, address, SSN, source, and amounts are tax data under IRC 6103; identical independently verified SSA information has different SSA disclosure handling.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0027"><data key="node_entity_id">R140_E0027</data><data key="node_entity_type">oversight_finding</data><data key="node_canonical_name">September 2026 OIG SSI Earnings Alert Resolution Audit</data><data key="node_domain">Program integrity / earnings</data><data key="node_description">OIG audited pending SSI earnings alerts and reported delayed or incomplete reviews, including estimated improper-payment implications based on its sample.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0028"><data key="node_entity_id">R140_E0028</data><data key="node_entity_type">quality_control_finding</data><data key="node_canonical_name">OIG SSI Earnings Alerts 2026 Pending and Incomplete Development Failure Modes</data><data key="node_domain">Title XVI / work controls</data><data key="node_description">In OIG sample of 100, 63 had reviews not started or not completed, pending average 733 days, and 17 had alerts cleared without recording all earnings.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0029"><data key="node_entity_id">R140_E0029</data><data key="node_entity_type">audit_statistical_caveat</data><data key="node_canonical_name">OIG SSI Earnings Alert Administrative Finality Recovery Limitation Estimate</data><data key="node_domain">Title XVI / debt</data><data key="node_description">OIG estimated $1B improper payments to 333,800 recipients; estimated $664M may be unrecoverable absent fraud or similar fault, $344M potentially recoverable. These are sample-based audit estimates.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0030"><data key="node_entity_id">R140_E0030</data><data key="node_entity_type">statistical_reference_date_rule</data><data key="node_canonical_name">2026 SSI Population Projection Table IV.A1 July 1 Reference Basis</data><data key="node_domain">OACT / statistical production</data><data key="node_description">2026 SSI Annual Report Table IV.A1 population by age subgroup is expressed as of July 1 under Trustees intermediate demographic assumptions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0031"><data key="node_entity_id">R140_E0031</data><data key="node_entity_type">actuarial_method_rule</data><data key="node_canonical_name">2026 SSI Projected Federal Benefit Rate COLA Assumption</data><data key="node_domain">OACT / statistical production</data><data key="node_description">2026 SSI projection table IV.A2 applies January SSI federal benefit rate COLAs identical to OASDI post-eligibility COLAs; scheduled Social Security benefits used for offsets.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R140_E0032"><data key="node_entity_id">R140_E0032</data><data key="node_entity_type">grants_workflow_rule</data><data key="node_canonical_name">SSA Grant Award Notification Through GrantSolutions</data><data key="node_domain">Acquisition and grants</data><data key="node_description">OAG grant instructions say successful applicants receive electronic award notices from GrantSolutions no later than September 30 of the award calendar year.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Direct authoritative source; purpose, date, and caveats govern interpretation; implementation/retention/hosting not inferred.</data></node><node id="R141_E002"><data key="node_entity_id">R141_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Upload Documents Manual Benefit Application Transcription</data><data key="node_acronym" /><data key="node_domain">digital intake/Title II/Title XVI</data><data key="node_description">SSA technician reviews electronically signed PDF or webform and enters information into MCS or CCE as with a paper application; e-submission does not imply straight-through adjudication.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E003"><data key="node_entity_id">R141_E003</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Upload Documents Checkbox-and-Submit Signature Acceptance</data><data key="node_acronym" /><data key="node_domain">digital intake/signatures</data><data key="node_description">Signed application requires check box on Review and Submit page followed by submission; receipt date reflects customer submission date.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E004"><data key="node_entity_id">R141_E004</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Upload Documents MCS ATTEST Remarks Signature-Method Marker</data><data key="node_acronym" /><data key="node_domain">claims/signature provenance</data><data key="node_description">MCS automatically propagates ATTEST to DW01 even when the actual signing method is Upload Documents, CPAS, or wet signature; technician records accurate method in remarks.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E005"><data key="node_entity_id">R141_E005</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Commercial Product Signature Timestamp Certificate</data><data key="node_acronym" /><data key="node_domain">claims/signature provenance</data><data key="node_description">For eligible signed benefit forms, CPAS signature must include signer name, signing date and time in signature area or appended signature certificate page.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E006"><data key="node_entity_id">R141_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CPAS Benefit Application Paper-Equivalent Claims Entry</data><data key="node_acronym" /><data key="node_domain">claims/signatures</data><data key="node_description">Technician verifies compliant CPAS signature and records CPAS in ATTEST remarks when entering SSA-16/SSA-8000/SSA-8001 in MCS or CCE.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E007"><data key="node_entity_id">R141_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS Manual Title XVI Exclusion Case Establishment</data><data key="node_acronym" /><data key="node_domain">Title XVI/disability</data><data key="node_description">Technicians manually create EDCS Title XVI initial/appeal cases for defined MSSICS/CCE exclusions or limitations, not as a universal intake route.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E008"><data key="node_entity_id">R141_E008</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS Manually Created T16 Information Screen</data><data key="node_acronym" /><data key="node_domain">Title XVI/disability</data><data key="node_description">For manually established Title XVI cases, technicians enter admission date when applicable, presumed disability onset date when applicable, and claims representative unit code.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E009"><data key="node_entity_id">R141_E009</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EDCS Manual Title XVI CDR Case Prohibition</data><data key="node_acronym" /><data key="node_domain">Title XVI/disability</data><data key="node_description">Manual Title XVI functionality is not available for initial or appeal CDR cases, including Title XVI age-18 redeterminations.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E010"><data key="node_entity_id">R141_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS Concurrent Hearing Manual Title XVI Allowance Exception</data><data key="node_acronym" /><data key="node_domain">Title II/Title XVI/appeals</data><data key="node_description">When concurrent Title XVI portion was allowed while Title II was denied, EDCS may block electronic Title XVI appeal creation and technicians use manual Title XVI process for concurrent ALJ hearing.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E011"><data key="node_entity_id">R141_E011</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EDCS Manual Title XVI Exclusion Reason</data><data key="node_acronym" /><data key="node_domain">Title XVI/disability</data><data key="node_description">Manual T16 case entry selects reason from dropdown; Other requires explanatory entry, preserving exclusion provenance.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E012"><data key="node_entity_id">R141_E012</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EDCS Partial-Electronic Official Paper Folder Boundary</data><data key="node_acronym" /><data key="node_domain">disability/evidence</data><data key="node_description">EDCS exclusion can produce a partially electronic case whose official claims folder is paper even though electronic case development is possible.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E013"><data key="node_entity_id">R141_E013</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EDCS Prior-Case Medical Source Contact Details</data><data key="node_acronym" /><data key="node_domain">disability/address provenance</data><data key="node_description">Prior closed EDCS case may contain medical source contact address, telephone, visit and appointment dates reusable in new case; not evidence of claimant mailing residence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E014"><data key="node_entity_id">R141_E014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS Copy From Prior Medical-Source Address Reverification</data><data key="node_acronym" /><data key="node_domain">disability/address provenance</data><data key="node_description">Upon copying prior case medical source information into new EDCS case, technician must review and update source address, telephone and visit details; no guaranteed currency.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E015"><data key="node_entity_id">R141_E015</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EDCS Copy From Prior Preserves Historical Source Case</data><data key="node_acronym" /><data key="node_domain">disability/data lineage</data><data key="node_description">Copy from prior propagates selected details into new case; source data remain in original closed EDCS case and editable copy does not delete them.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E016"><data key="node_entity_id">R141_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">TRO Unverified-Stale-Address Six-Month AVC Retry</data><data key="node_acronym" /><data key="node_domain">payments/debt/address provenance</data><data key="node_description">When AVC lacks a good mailing address and MBR/SSR addresses are over one year old, ECO checks AVC again in six months and postpones pre-offset notice pending good address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E017"><data key="node_entity_id">R141_E017</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">TRO Automated AVC Address Requests Separate From DMS Manual Requests</data><data key="node_acronym" /><data key="node_domain">payments/debt/address provenance</data><data key="node_description">Automated ECO address request does not replace or affect separate address inquiries handled by Debt Management Sections.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E018"><data key="node_entity_id">R141_E018</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Redetermination Eligible Couple Dual Signature Rule</data><data key="node_acronym" /><data key="node_domain">Title XVI/signatures</data><data key="node_description">On SSA-8203-BK, both eligible SSI spouses must sign; ineligible spouse generally does not sign spouse block unless acting as representative payee.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E019"><data key="node_entity_id">R141_E019</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Redetermination Mark Signature Witness Rule</data><data key="node_acronym" /><data key="node_domain">Title XVI/signatures</data><data key="node_description">Recipient signature by mark requires two witnesses except one field-office employee witness is sufficient when mark made in employee presence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E020"><data key="node_entity_id">R141_E020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Redetermination Representative Payee Signature Role</data><data key="node_acronym" /><data key="node_domain">Title XVI/payee/signatures</data><data key="node_description">Representative payee signs through approved alternate method for incapable recipient, except when representative payee change coincides with redetermination; incapable recipient signature not required.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E021"><data key="node_entity_id">R141_E021</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI Claims Redetermination SSA-8203-BK Signature Spaces</data><data key="node_acronym" /><data key="node_domain">Title XVI/signatures</data><data key="node_description">SSI Claims RZ printout provides separate signature blocks for recipient, eligible spouse, witnesses, and representative payee.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E022"><data key="node_entity_id">R141_E022</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Authenticated iClaim Versus Unauthenticated Identity Follow-up</data><data key="node_acronym" /><data key="node_domain">Title II/person identity</data><data key="node_description">Authenticated first-party iClaim need not receive second identity interview; unauthenticated submissions require identity verification before claim adjudication.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E023"><data key="node_entity_id">R141_E023</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">iClaim Original Submitted Summary Stored in ORS</data><data key="node_acronym" /><data key="node_domain">Title II/data provenance</data><data key="node_description">After download of iClaim data to MCS, a submitted Internet application summary is automatically retained in Online Retrieval System, separating original applicant assertion from subsequently adjudicated claim.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R141_E024"><data key="node_entity_id">R141_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EDCS Prior Medical Source Address Not Claimant Address</data><data key="node_acronym" /><data key="node_domain">disability/address provenance</data><data key="node_description">Addresses for medical professionals copied across EDCS cases are provider contact attributes, not a verified claimant residence or SSA program master-address update.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Direct official POMS; applies to documented conditional procedure; no unobserved storage, system synchronization, or processing technology implied.</data></node><node id="R142_E001"><data key="node_entity_id">R142_E001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA-11-BK Mailed or Faxed Payee Application Lead</data><data key="node_domain">representative payee/intake</data><data key="node_description">Mailed, faxed or dropped-off SSA-11-BK serves as a lead only; a documented interview and eRPS action are still required.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E002"><data key="node_entity_id">R142_E002</data><data key="node_entity_type">identity_verification</data><data key="node_canonical_name">Representative Payee Remote-Interview Numident Identity Confirmation</data><data key="node_domain">representative payee/identity</data><data key="node_description">Eligible phone or approved-video interviews confirm individual applicant identity using Numident and record method and ID-verified-via-NUMI in eRPS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E003"><data key="node_entity_id">R142_E003</data><data key="node_entity_type">identity_verification</data><data key="node_canonical_name">Organizational Payee Interview Name-Address-EIN Verification</data><data key="node_domain">representative payee/organization</data><data key="node_description">Eligible remote organizational interview verifies name, organizational address and EIN; employee name/title and funds manager are documented in eRPS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E004"><data key="node_entity_id">R142_E004</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Representative Payee Face-to-Face Interview Requirement and Exceptions</data><data key="node_domain">representative payee/service</data><data key="node_description">Face-to-face interview is default; hardship, qualifying repeat payees and specified WSU/CPU cases permit phone or approved video. History of misuse or U.S. resident applicant without SSN require face to face.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E005"><data key="node_entity_id">R142_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eRPS Background-Check Consent Refusal Nonselection</data><data key="node_domain">representative payee/program integrity</data><data key="node_description">For an applicant subject to criminal background screening, refusal to permit screening triggers eRPS nonselection and a documented refusal reason.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E006"><data key="node_entity_id">R142_E006</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eRPS Background-Check Custodial-Relative Exempt Categories</data><data key="node_domain">representative payee/program integrity</data><data key="node_description">POMS identifies specific custodial parents, spouses, grandparents, guardians and qualifying parents of aged-18 beneficiaries exempt from asking permission and conducting screening.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E007"><data key="node_entity_id">R142_E007</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">PUPS Prisoner History Missing Specific Offense Description</data><data key="node_domain">representative payee/program integrity</data><data key="node_description">PUPS confinement history establishes incarceration intervals but does not establish the particular crime; staff independently develop convictions and suitability.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E008"><data key="node_entity_id">R142_E008</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eRPS Payee Interview Left Before Attestation Nonselection</data><data key="node_domain">representative payee/intake</data><data key="node_description">A payee applicant leaving before application attestation is classified Incomplete with circumstances recorded as a Rep Payee Applicant note.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E009"><data key="node_entity_id">R142_E009</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Representative Payee SSA-5002 No-eRPS-Record Interview Evidence Route</data><data key="node_domain">representative payee/evidence</data><data key="node_description">When no eRPS record is established (e.g. undocumented parent applicant without SSN), employee completes SSA-5002 and stores in eView/NDRED through Evidence Portal.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E010"><data key="node_entity_id">R142_E010</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Representative Payee Interview Mode and Hardship Reason Notes</data><data key="node_domain">representative payee/audit</data><data key="node_description">eRPS Rep Payee Applicant note records interview date, face-to-face or remote mode and its reason, suitability reasoning and explanation of duties.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E011"><data key="node_entity_id">R142_E011</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Field-Office Redetermination Financial Institution Contact Permission</data><data key="node_domain">SSI/redetermination</data><data key="node_description">At every field-office-initiated SSI redetermination, permission to contact financial institutions is requested; the permission requirement does not itself establish access to any particular account.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E012"><data key="node_entity_id">R142_E012</data><data key="node_entity_type">data_provenance_rule</data><data key="node_canonical_name">SSI IRS Informational Resource Alert Investigative Lead</data><data key="node_domain">SSI/IRS financial alerts</data><data key="node_description">Informational IRS alert can initiate liquid-resource development; controlled IRS alerts require development through the separate controlled-alert procedure.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E013"><data key="node_entity_id">R142_E013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Direct-Deposit Indicator Financial Account Resource Development</data><data key="node_domain">SSI/resource eligibility</data><data key="node_description">MBR/SSR direct deposit indicators signal financial-account resource development; staff document relevant bank or Direct Express account through CCE Financial Accounts.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E014"><data key="node_entity_id">R142_E014</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI First-of-Month Account Balance Verification</data><data key="node_domain">SSI/resource eligibility</data><data key="node_description">When bank accounts require development, use statements and transaction activity to establish first-of-month countable balance.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E015"><data key="node_entity_id">R142_E015</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSI Redetermination Financial Institution Address Data</data><data key="node_domain">SSI/address provenance</data><data key="node_description">SSA-8203-BK identifies the bank or company and its address as an account-ownership information attribute, not a verified SSI recipient residence or mailing address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E016"><data key="node_entity_id">R142_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Early-Payment First-of-Month Resource Exclusion</data><data key="node_domain">SSI/resource eligibility</data><data key="node_description">When SSI is delivered early due to a weekend or holiday, treat payment according to normal receipt month and exclude advance-payment amount from the first-of-month resource balance where applicable.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E017"><data key="node_entity_id">R142_E017</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Disqualified Representative Home and Business Contact Address Attributes</data><data key="node_domain">person/address provenance/legal representation</data><data key="node_description">2021 SSA PIA lists representative home or business address, phone, fax, email and representative ID separately from claimant or beneficiary address.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2021-04-14</data><data key="node_confidence">5</data><data key="node_notes">2021 PIA inventory. Address identifies representative; no claim about current 2026 system implementation or copying to beneficiary records.</data></node><node id="R142_E018"><data key="node_entity_id">R142_E018</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Representative Suspension Professional-Standing and Investigation Evidence</data><data key="node_domain">legal representation/governance</data><data key="node_description">2021 PIA documents bar/court licensing standing, disciplinary history, government admissions, employer EIN and investigation documents retained under disqualification records.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2021-04-14</data><data key="node_confidence">5</data><data key="node_notes">Governed by SORN 60-0219; operational architecture beyond named repositories not inferred.</data></node><node id="R142_E019"><data key="node_entity_id">R142_E019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2026 OACT Two-Year-Lag Average Wage Index Benefit Calculation</data><data key="node_domain">OACT/statistical production</data><data key="node_description">For eligibility year 2026, historical covered earnings before 2024 use 2024 AWI 69,846.57 for indexing; 2024 and later earnings are not indexed.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E020"><data key="node_entity_id">R142_E020</data><data key="node_entity_type">statistical_parameter</data><data key="node_canonical_name">2026 PIA Formula Two Bend Points and Factors</data><data key="node_domain">OACT/benefit formula</data><data key="node_description">OACT publishes first and second 2026 PIA formula bend points of $1,286 and $7,749, with statutory 90%, 32%, and 15% factors by AIME band.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E021"><data key="node_entity_id">R142_E021</data><data key="node_entity_type">public_calculator</data><data key="node_canonical_name">OACT Online Calculator Self-Entered Annual Covered Earnings</data><data key="node_domain">OACT/public actuarial tools</data><data key="node_description">Browser-based Online Calculator requires user to enter covered earnings for each year, using user-supplied record; public description does not establish SSA earnings-file query.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Public website calculator capability. Do not infer a back-end application API or internal data fetch.</data></node><node id="R142_E022"><data key="node_entity_id">R142_E022</data><data key="node_entity_type">statistical_calculation</data><data key="node_canonical_name">OACT AIME Highest-Earnings-Years Selection and Rounding</data><data key="node_domain">OACT/benefit computation</data><data key="node_description">OACT describes selecting up to 35 highest indexed-earnings years, averaging over corresponding months, and rounding AIME down to the next lower dollar.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E023"><data key="node_entity_id">R142_E023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Medicare Extra Help Application SSI Protective Filing Effect</data><data key="node_domain">Medicare/SSI/claims</data><data key="node_description">Filing an Extra Help application also acts as a protective filing for SSI and can initiate state Medicare Savings Program application referral.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E024"><data key="node_entity_id">R142_E024</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CMS Part D Plan Automatic Selection for Eligible Nonenrollees</data><data key="node_domain">Medicare/Part D</data><data key="node_description">CMS enrolls some Extra Help-eligible individuals not already enrolled in prescription coverage into a selected plan, with opt-out or change procedures.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R142_E025"><data key="node_entity_id">R142_E025</data><data key="node_entity_type">notice_workflow</data><data key="node_canonical_name">Medicare Extra Help Deemed-Status Loss Annual Application Notice</data><data key="node_domain">Medicare/Extra Help</data><data key="node_description">People notified by CMS of loss of deemed status annually receive an Extra Help application; their continued deemed period and next-year application effective date require separate handling.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented administrative pathway; do not infer current physical hosting, automatic master-record updates, persistence or universal scope.</data></node><node id="R143_E0001"><data key="node_entity_id">R143_E0001</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-581 Itemized Earnings Release Authorization</data><data key="node_domain">earnings/disclosure</data><data key="node_description">Written consent authorization requested by pension plans, law firms, and other third parties for itemized earnings under reimbursable agreements; relationship proof needed when a third party consents.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0002"><data key="node_entity_id">R143_E0002</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA-1826 Itemized Statement of Earnings</data><data key="node_domain">earnings/disclosure</data><data key="node_description">Disclosed itemized earnings including quarterly earnings 1937–1978, annual earnings 1979 onward, employer EIN, and reporting employer names and addresses.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0003"><data key="node_entity_id">R143_E0003</data><data key="node_entity_type">legal_agreement</data><data key="node_canonical_name">Third-Party Itemized Earnings Reimbursable Agreement</data><data key="node_domain">earnings/disclosure</data><data key="node_description">Agreement under SSA MOA and SSA-1235 covering third-party itemized earnings disclosures on a reimbursable basis.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0004"><data key="node_entity_id">R143_E0004</data><data key="node_entity_type">organizational_unit</data><data key="node_canonical_name">Earnings Operations Support Pension Fund Staff</data><data key="node_domain">earnings/disclosure</data><data key="node_description">SSA Central Processing Earnings Operations Support staff reviews pension plan and law-firm requests for reimbursable earnings disclosure agreements.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0005"><data key="node_entity_id">R143_E0005</data><data key="node_entity_type">authorization_control</data><data key="node_canonical_name">Third-Party Earnings Disclosure Consent Receipt Within 120 Days</data><data key="node_domain">earnings/disclosure</data><data key="node_description">Applicable IRS consent rule requires SSA receipt of signed consent within 120 days of consent signature for earnings disclosure.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0006"><data key="node_entity_id">R143_E0006</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSA-1826 Reporting Employer Address Attribute</data><data key="node_domain">earnings/address provenance</data><data key="node_description">Names and mailing addresses of reporting employers on an itemized earnings statement; not evidence of wage earner residence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0007"><data key="node_entity_id">R143_E0007</data><data key="node_entity_type">financial_control</data><data key="node_canonical_name">Itemized Earnings Reimbursable Advance and Quarterly Statement Control</data><data key="node_domain">earnings/disclosure</data><data key="node_description">Requesting entity pays estimated SSA service costs in advance, receives quarterly statements, and a refund or additional bill after reconciliation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0008"><data key="node_entity_id">R143_E0008</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Earnings Disclosure Requester Organization and Contact Address</data><data key="node_domain">external organization/address provenance</data><data key="node_description">Earnings requester provides organization address, EIN, and representative contact address; neither address is a claimant address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0009"><data key="node_entity_id">R143_E0009</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Third-Party Pension Plan and Law Firm Earnings Disclosure Use</data><data key="node_domain">earnings/external exchange</data><data key="node_description">Private pension plans and law firms can request individual consent-based itemized earnings for pension eligibility and litigation through reimbursable agreements.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0010"><data key="node_entity_id">R143_E0010</data><data key="node_entity_type">contracted_service</data><data key="node_canonical_name">SSA Telephone Interpreter Service</data><data key="node_domain">language access/operations</data><data key="node_description">SSA-contracted telephone interpretation offered 24 hours per day to clients with limited English proficiency; service provided by an unnamed contractor.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0011"><data key="node_entity_id">R143_E0011</data><data key="node_entity_type">vendor_data_product</data><data key="node_canonical_name">Telephone Interpreter Vendor Daily Usage Observations</data><data key="node_domain">language access/vendor data</data><data key="node_description">The contracted vendor observes daily request count, language used, and length of incoming SSA interpretation calls.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0012"><data key="node_entity_id">R143_E0012</data><data key="node_entity_type">external_reporting_process</data><data key="node_canonical_name">Telephone Interpreter Monthly Vendor Report Transfer to SSA</data><data key="node_domain">language access/external data</data><data key="node_description">Vendor forwards aggregate or detailed usage report to SSA monthly; underlying transport and persistence not described.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0013"><data key="node_entity_id">R143_E0013</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSA Annual Telephone Interpreter Calls by Language CSV</data><data key="node_domain">language access/open data</data><data key="node_description">Annual national telephone-interpreter call counts by language, with years 2018 onward; latest documented update December 31, 2025.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0014"><data key="node_entity_id">R143_E0014</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">Telephone Interpreter Annual Call Count Low-Cell Marking Rule</data><data key="node_domain">language access/publication</data><data key="node_description">Public dataset marks languages with fewer than three calls using an asterisk.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0015"><data key="node_entity_id">R143_E0015</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSA Disability Data Operational Week-to-Calendar Date Translation Table</data><data key="node_domain">disability/statistics</data><data key="node_description">Public SSA_DATES1 translation table in CSV and XLSX supports conversion among SSA weekly, monthly and quarterly periods and fiscal/calendar time.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0016"><data key="node_entity_id">R143_E0016</data><data key="node_entity_type">geographic_data_rule</data><data key="node_canonical_name">DDS Workload Reporting State Is Adjudicating Agency, Not Claimant Residence</data><data key="node_domain">disability/address provenance</data><data key="node_description">State designation in monthly DDS workload statistics refers to the state agency doing disability work, which may differ from claimant state of residence due to workload transfers.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0017"><data key="node_entity_id">R143_E0017</data><data key="node_entity_type">external_data_exchange_process</data><data key="node_canonical_name">DDS-to-SSA Disability Disposition Electronic Reporting Process</data><data key="node_domain">disability/external exchanges</data><data key="node_description">SSA records electronic referrals to state DDS; DDS electronic disposition data return to SSA and contribute to DIODS workload information.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0018"><data key="node_entity_id">R143_E0018</data><data key="node_entity_type">statistical_data_quality_rule</data><data key="node_canonical_name">DIODS Historical Period Summary Non-Recalculation and Later-Period Correction Rule</data><data key="node_domain">disability/analytics</data><data key="node_description">DIODS time-period summaries are stored when computed; later row corrections do not recalculate prior summaries but affect later overlapping summaries.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0019"><data key="node_entity_id">R143_E0019</data><data key="node_entity_type">temporal_data_rule</data><data key="node_canonical_name">SSA Disability Workload Four- or Five-Week Operational Month</data><data key="node_domain">disability/statistics</data><data key="node_description">SSA operational months typically end on last Friday and contain four or five work weeks; quarter covers thirteen weeks.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0020"><data key="node_entity_id">R143_E0020</data><data key="node_entity_type">statistical_data_quality_rule</data><data key="node_canonical_name">DDS Concurrent SSDI-SSI Claim Single Case Counting Rule</data><data key="node_domain">disability/analytics</data><data key="node_description">Simultaneously filed SSDI/SSI concurrent cases generally count once in total DDS workload; separate program breakouts are not additive if counted twice.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0021"><data key="node_entity_id">R143_E0021</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">DDS State Agency Monthly Workload 71-Element CSV and XLS Data Product</data><data key="node_domain">disability/data products</data><data key="node_description">Published state monthly disability workload product includes expanded set of 71 elements, DDS initial, reconsideration and medical CDR counts and SSDI/SSI/concurrent breakouts.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0022"><data key="node_entity_id">R143_E0022</data><data key="node_entity_type">statistical_data_attribute</data><data key="node_canonical_name">DDS Workload FE Aggregate Federal Component State Code</data><data key="node_domain">disability/statistics</data><data key="node_description">State code FE and region FED aggregate disability determination work performed by federal components; not a US state or claimant residence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0023"><data key="node_entity_id">R143_E0023</data><data key="node_entity_type">statistical_data_quality_rule</data><data key="node_canonical_name">DDS Prototype-State Reconsideration Comparability Caveat</data><data key="node_domain">disability/appeals</data><data key="node_description">Historical DDS prototype processing bypassed reconsideration in participating locations; displayed initial and reconsideration monthly counts are not a longitudinal application cohort.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0024"><data key="node_entity_id">R143_E0024</data><data key="node_entity_type">publication_pipeline</data><data key="node_canonical_name">DDS Monthly Workload Full-File Replacement Publication Rule</data><data key="node_domain">disability/publication</data><data key="node_description">Dataset update replaces prior whole downloadable file; public archive of overwritten file versions not available; production metadata carries update date and file version.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0025"><data key="node_entity_id">R143_E0025</data><data key="node_entity_type">actuarial_data_product</data><data key="node_canonical_name">2026 OASDI Trustees Single-Year Table IV.B2 Annual Income Rate Components</data><data key="node_domain">actuarial/statistical products</data><data key="node_description">2026 Trustees supporting table IV.B2 reports components of annual income rates for years 1970–2100 under defined assumptions; OACT supplies Excel access.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0026"><data key="node_entity_id">R143_E0026</data><data key="node_entity_type">actuarial_data_product</data><data key="node_canonical_name">2026 OASDI Trustees Single-Year Table V.A1 Fertility and Mortality Assumptions</data><data key="node_domain">actuarial/statistical products</data><data key="node_description">2026 Trustees supporting table V.A1 publishes fertility and mortality assumptions from 1940–2100 across alternatives, available in Excel.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0027"><data key="node_entity_id">R143_E0027</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Online Medicare Replacement Card Request Address-Change Prerequisite</data><data key="node_domain">medicare/address provenance</data><data key="node_description">Published SSA Medicare card service guidance tells beneficiaries who have moved to report address change before online replacement request processing; not proof of an automatic address update.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R143_E0028"><data key="node_entity_id">R143_E0028</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">FIVR Vendor Administrative Payment Inquiry Scope</data><data key="node_domain">procurement/administrative payments</data><data key="node_description">SSA vendor page states FIVR gives authorized vendors self-service administrative payment status 24 hours a day, separate from beneficiary benefit questions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">As stated in official public material. No inferred physical architecture, current deployment, automated cross-system update, or data-retention duration.</data></node><node id="R144_E0001"><data key="node_entity_id">R144_E0001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Domestic-to-Foreign Address Change Nonresident Alien Tax-Status Development Gate</data><data key="node_domain">Title II / address / tax</data><data key="node_description">For qualifying beneficiaries with AWSC other than 1 or 5, a domestic-to-foreign address change for an intended absence longer than three months requires development of beneficiary tax status; moving address does not by itself prove changed alien status.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">coa: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0002"><data key="node_entity_id">R144_E0002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Foreign-to-Domestic Mailing Address Change Does Not Prove Alien Tax Reclassification</data><data key="node_domain">Title II / address provenance</data><data key="node_description">A foreign-to-domestic mailing address change is not sufficient by itself to reclassify nonresident alien withholding status; a positive indication of changed status triggers development.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">coa: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0003"><data key="node_entity_id">R144_E0003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Foreign Address Tax-Status Development Claims-Folder Forwarding</data><data key="node_domain">Title II / claims evidence</data><data key="node_description">If employees undertake tax-status development during change of address, send supporting evidence such as SSA-795 to the processing center for filing even when the COA itself needs no processing-center referral.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">coa: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0004"><data key="node_entity_id">R144_E0004</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Alien Withholding Status Code (AWSC) Address-Transition Conditional Review</data><data key="node_acronym">AWSC</data><data key="node_domain">Title II / tax status</data><data key="node_description">POMS GN 05010.090 uses AWSC values including 1, 2 and 5 to determine whether particular address transitions require nonresident-alien tax-status development.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">coa: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0005"><data key="node_entity_id">R144_E0005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2025 Advance File No Bendpoint (AFNB) Automated Title II Claims Run</data><data key="node_acronym">AFNB</data><data key="node_domain">Title II / claims automation</data><data key="node_description">MCS Earnings Computation processes qualified AFNB claims in an automated run tied to availability of 2026 bendpoints; instructions dated November 2025 specify automatic start November 24, 2025.</data><data key="node_observed_status">dated_2025_operational_instruction</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0006"><data key="node_entity_id">R144_E0006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Future Month of Entitlement Auto-Initiate (Future MOE AI)</data><data key="node_acronym">MOE AI</data><data key="node_domain">Title II / future entitlement</data><data key="node_description">Future MOE Auto-Initiate holds qualified triggered claims until the future entitlement operational month, and can process certain dual-entitlement cases after another account is established.</data><data key="node_observed_status">documented_2025</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0007"><data key="node_entity_id">R144_E0007</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Earnings Computation Approval (DAPP) Screen AFNB Trigger</data><data key="node_acronym">DAPP</data><data key="node_domain">Title II / MCS</data><data key="node_description">Entering Y on the DAPP screen causes automatic receipt of the MCS ADVFIL issue for qualifying advance-file claims.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0008"><data key="node_entity_id">R144_E0008</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">MCS DW01 ADVFIL Auto-Receipt Work-Control Issue</data><data key="node_acronym">ADVFIL</data><data key="node_domain">Title II / claims</data><data key="node_description">MCS automatically receipts an ADVFIL issue after AFNB DAPP approval, as documented for the 2025-2026 bendpoint transition.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0009"><data key="node_entity_id">R144_E0009</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">MCS DW01 EC Issue System-Generated Tickle Date</data><data key="node_domain">Title II / claims</data><data key="node_description">MCS places a scheduled tickle on an EC issue during AFNB processing; employees must not manually receipt or alter the issue because the automated run uses the date.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0010"><data key="node_entity_id">R144_E0010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">MCS File Date Determination Screen (FDDS) Material File Date Override Gate</data><data key="node_acronym">FDDS</data><data key="node_domain">Title II / claims</data><data key="node_description">The November 2025 policy permits changing FDDS material-file date in specified AFNB hold circumstances, but prohibits the same change for non-AFNB Future MOE claims.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0011"><data key="node_entity_id">R144_E0011</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2025-2026 Benefit Rate Increase and Bendpoint MBR Synchronization Gate</data><data key="node_acronym">BRI</data><data key="node_domain">Title II / benefit computation</data><data key="node_description">November 2025 instructions describe a sequencing interval in which earnings-computation bendpoints and MBR benefit-rate-increase values become available on different dates, requiring some claims to be held.</data><data key="node_observed_status">dated_2025_operational_instruction</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0012"><data key="node_entity_id">R144_E0012</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Future MOE Dual-Entitlement Separate Account Trigger Sequencing</data><data key="node_domain">Title II / cross-account claimant processing</data><data key="node_description">If one dual-entitlement claim has no established MBR and the other has an active record needing COLA adjustment, certain claims must be triggered in sequence; appropriate notifications are included.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0013"><data key="node_entity_id">R144_E0013</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">AFNB Automated Processing Time Excludes Claim Pre-Trigger Wait</data><data key="node_domain">Title II / workload analytics</data><data key="node_description">For AFNB automated cases, operational processing-time measurement excludes the interval from application through triggering and can display zero-day processing time; not equivalent to claimant elapsed wait.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0014"><data key="node_entity_id">R144_E0014</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">AFNB Family Maximum Conflict A101 Manual Processing Exception</data><data key="node_domain">Title II / claims fallback</data><data key="node_description">Some future-entitlement dual-beneficiary cases cannot process through EC when family maximum adjustments are required; POMS specifies A101 manual processing.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">afnb: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0015"><data key="node_entity_id">R144_E0015</data><data key="node_entity_type">payment_process</data><data key="node_canonical_name">Czech Republic Title II International Direct Deposit Process</data><data key="node_acronym">IDD</data><data key="node_domain">Title II / international payments</data><data key="node_description">SSA uses Czech-specific MBR bank coding and a separate Treasury ITS.gov enrollment, with FRB Kansas City and local bank routing for Czech-koruna payments.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">czech: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0016"><data key="node_entity_id">R144_E0016</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1199-OP13 Czech Republic International Direct Deposit Sign-up Form</data><data key="node_domain">Title II / international payments</data><data key="node_description">SSA identifies SSA-1199-OP13 as the Czech Republic IDD sign-up form; incomplete information may be clarified with the Federal Benefits Unit.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">forms: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0017"><data key="node_entity_id">R144_E0017</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Czech Republic IDD Routing and Depositor Account Country Coding</data><data key="node_domain">Title II / payments</data><data key="node_description">POMS codes a Czech local bank routing and account reference into U.S.-format MBR direct-deposit fields, using routing prefix 66 and country indicator C in the depositor account number.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">czech: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0018"><data key="node_entity_id">R144_E0018</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Czech IDD Same-Day MBR and ITS.gov Dual Entry Control</data><data key="node_domain">Title II / payments cross-system</data><data key="node_description">After updating Czech Republic IDD bank data in SSA post-entitlement systems, staff must separately enter corresponding account and identity details into Treasury ITS.gov the same business day; missing data can cause payment rejection.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">czech: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0019"><data key="node_entity_id">R144_E0019</data><data key="node_entity_type">external_organization</data><data key="node_canonical_name">Czech Republic International Direct Deposit Local Processing Financial Institution</data><data key="node_domain">Title II / external banking</data><data key="node_description">A financial institution in Czech Republic serves as local processing bank under SSA international direct deposit; current bank name not specified in POMS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Generic program role only; no named vendor, current contract or physical interface asserted.</data></node><node id="R144_E0020"><data key="node_entity_id">R144_E0020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">MBR Foreign Address Precondition for Czech IDD Updates</data><data key="node_domain">Title II / address provenance</data><data key="node_description">For noninitial Czech IDD bank changes, POMS directs stop if MBR beneficiary address is not coded as foreign (PCOC=8); such address serves as an eligibility gate, not proof of bank-address synchronization.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">czech: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0021"><data key="node_entity_id">R144_E0021</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">Czech IDD ITS.gov Bank Address Versus Beneficiary Address Input</data><data key="node_domain">Title II / address provenance</data><data key="node_description">The ITS.gov entry requires both bank and beneficiary addresses as separate fields; the beneficiary address is entered with Czech country code but no automatic update to the MBR address is established.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">czech: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0022"><data key="node_entity_id">R144_E0022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Czech Republic International Direct Deposit Federal Benefits Unit Deficiency Follow-up</data><data key="node_domain">Title II / external processing</data><data key="node_description">Division of International Operations can send incomplete Czech IDD requests to the servicing Federal Benefits Unit, which contacts the beneficiary or financial institution for details.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">czech: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0023"><data key="node_entity_id">R144_E0023</data><data key="node_entity_type">payment_exception</data><data key="node_canonical_name">FRBKC Czech IDD Incomplete ITS.gov Payment Return</data><data key="node_domain">Title II / international payments</data><data key="node_description">FRB Kansas City rejects or returns Czech IDD payments when SSA has not provided complete bank information in Treasury ITS.gov.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">czech: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0024"><data key="node_entity_id">R144_E0024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">International Direct Deposit Eligibility Based on Beneficiary Residence Abroad</data><data key="node_domain">Title II / geographic address</data><data key="node_description">SSA-1199 public form eligibility requires Title II benefits, residence outside the US, and an eligible foreign bank; return to US residence ends IDD eligibility.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">forms: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0025"><data key="node_entity_id">R144_E0025</data><data key="node_entity_type">research_report</data><data key="node_canonical_name">SSAB 2024 Disability Benefit Effectuation Research Report</data><data key="node_domain">disability / awards to payment</data><data key="node_description">SSAB reviewed the post-allowance steps between disability determination and actual benefit payment, including SSI and DI variations; study is observational research, not evidence of a new SSA operational system.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">ssab_effect: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0026"><data key="node_entity_id">R144_E0026</data><data key="node_entity_type">research_dataset</data><data key="node_canonical_name">SSAB Disability Effectuation Non-SSA Representative-Firm Case Dataset</data><data key="node_domain">disability / third-party analysis</data><data key="node_description">SSAB analyzed data from a large national claimant-representative firm, not a complete official SSA administrative census; results require sample limitations when generalized.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">ssab_effect: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0027"><data key="node_entity_id">R144_E0027</data><data key="node_entity_type">statistical_observation</data><data key="node_canonical_name">SSAB Disability Effectuation SSI Median 2014-2023 Sample Comparison</data><data key="node_domain">disability / payment timeliness</data><data key="node_description">SSAB reports sampled SSI median time from favorable decision to payment rose from about 20 days in 2014 to 77 days in early 2023; DI effectuation often shorter, with a long-tail of delays.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">ssab_effect: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0028"><data key="node_entity_id">R144_E0028</data><data key="node_entity_type">recommendation</data><data key="node_canonical_name">SSAB 2024 Interest on Delayed Disability Past-Due Benefits Recommendation</data><data key="node_domain">disability / policy</data><data key="node_description">SSAB recommended congressional consideration of paying interest on past-due disability benefits when effectuation is delayed; this is a proposal, not a current payment system.</data><data key="node_observed_status">recommended_not_deployed</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">ssab_effect: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0029"><data key="node_entity_id">R144_E0029</data><data key="node_entity_type">research_report</data><data key="node_canonical_name">SSAB 2025 Benefits Among Adults Aged 62 to Full Retirement Age Research</data><data key="node_domain">retirement / disability / HRS</data><data key="node_description">SSAB used Health and Retirement Study self-reports among respondents age 62 to full retirement age with work-limiting health issues to assess program participation and information gaps.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">ssab_older: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0030"><data key="node_entity_id">R144_E0030</data><data key="node_entity_type">research_dataset</data><data key="node_canonical_name">HRS Self-Reported Late-Career Work Limitation and Benefit Participation Subpopulation</data><data key="node_domain">research / self-reported disability</data><data key="node_description">Study subgroup is HRS participants aged 62 through full retirement age reporting work-limiting health conditions; survey responses must not be relabeled as SSA administrative data.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">ssab_older: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0031"><data key="node_entity_id">R144_E0031</data><data key="node_entity_type">recommendation</data><data key="node_canonical_name">SSAB 2025 Cross-Program Benefit Awareness Automation Recommendation</data><data key="node_domain">retirement / disability / policy</data><data key="node_description">SSAB recommends SSA explore targeted outreach and automation that identifies potentially missed eligibility across retirement, disability and SSI; no implementation established.</data><data key="node_observed_status">recommended_not_deployed</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">ssab_older: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0032"><data key="node_entity_id">R144_E0032</data><data key="node_entity_type">oversight_report</data><data key="node_canonical_name">SSA FY2025 Purchase and Travel Charge Card OIG Risk Assessment</data><data key="node_domain">procurement / finance</data><data key="node_description">SSA OIG announced in April 2026 that FY2025 charge-card program risk was low, based on FY2025 activity and management controls; assessment does not establish the card processing vendor or payment system.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">cards: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0033"><data key="node_entity_id">R144_E0033</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Travel Card and Centrally Billed Charge Card Program</data><data key="node_domain">agency administration / procurement</data><data key="node_description">OIG reports an SSA travel card and centrally billed account program separate from SSA purchase cards, with FY2025 spending estimated at about $2 million.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">cards: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0034"><data key="node_entity_id">R144_E0034</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">SSA FY2025 Semiannual Joint Charge Card Violation Report Delayed Submission</data><data key="node_domain">procurement / financial oversight</data><data key="node_description">SSA did not file required FY2025 semiannual joint violation reports during FY2025; in March 2026 it submitted the FY2025 report, per OIG.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">cards: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0035"><data key="node_entity_id">R144_E0035</data><data key="node_entity_type">historical_control</data><data key="node_canonical_name">SSA February 2025 Temporary One-Dollar Charge Card Transaction Limit</data><data key="node_domain">procurement / purchase cards</data><data key="node_description">As an action relating to a February 2025 executive order, SSA set single transaction limits to $1 on purchase and travel cards for the temporary 30-day restriction described by OIG.</data><data key="node_observed_status">historical_2025_control</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">cards: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R144_E0036"><data key="node_entity_id">R144_E0036</data><data key="node_entity_type">governance_artifact_type</data><data key="node_canonical_name">SSA Purchase and Travel Card Management Plans</data><data key="node_domain">procurement / charge cards</data><data key="node_description">SSA maintains agency management plans that set safeguards, internal controls and procedures to prevent misuse or delinquency in purchase, travel and centrally billed accounts.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">cards: scoped to the named source and revision date. No automatic cross-system updates, transport, persistence, hosting or production inference.</data></node><node id="R145_E0001"><data key="node_entity_id">R145_E0001</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSNAP Foreign-Passport Evidence Submitted Metadata</data><data key="node_acronym" /><data key="node_domain">Person/Identity Nexus</data><data key="node_description">For enumeration applicants using current DHS lawful-alien documents and an unexpired foreign passport, SSNAP Summary Evidence Submitted records passport name, DOB, number, issuing country, issue date, and expiry if not already represented in passport-number field.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">These are identity-document details, not independently verified residence or benefit master-record attributes.</data></node><node id="R145_E0002"><data key="node_entity_id">R145_E0002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Enumeration Non-REAL-ID State Document Identity Acceptance Rule</data><data key="node_acronym" /><data key="node_domain">Enumeration / Identity</data><data key="node_description">A permanent U.S. state driver license or non-driver card marked NOT FOR FEDERAL IDENTIFICATION remains acceptable as primary SSN-applicant identity evidence if other POMS requirements are met; the legend alone is not disqualifying.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">A valid identity document does not prove current domicile or a master address update.</data></node><node id="R145_E0003"><data key="node_entity_id">R145_E0003</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Enumeration Age-Based Primary/Secondary/Third-Level Evidence Escalation</data><data key="node_acronym" /><data key="node_domain">Enumeration / Identity</data><data key="node_description">Enumeration identity proof varies among children 0-5, 6-17, and adults; when primary proof is available within 10 business days secondary proof is not substituted; third-level evidence receives case-by-case handling.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0004"><data key="node_entity_id">R145_E0004</data><data key="node_entity_type">identity_evidence</data><data key="node_canonical_name">Enumeration DHS Document Plus Foreign Passport Evidence Pair</data><data key="node_acronym" /><data key="node_domain">Enumeration / DHS</data><data key="node_description">For many aliens SSA requests a current DHS lawful-alien document together with an unexpired foreign passport; documented exceptions allow DHS lawful-alien evidence alone for specified persons unable to obtain a passport.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0005"><data key="node_entity_id">R145_E0005</data><data key="node_entity_type">records_custody_rule</data><data key="node_canonical_name">Concurrent Disability Title II Paper-Folder Custody at Central Processing</data><data key="node_acronym" /><data key="node_domain">Disability / Title II</data><data key="node_description">SSA Central Processing houses Title II paper folders for concurrent Title II and Title XVI disability cases, rather than all claim folders being colocated.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0006"><data key="node_entity_id">R145_E0006</data><data key="node_entity_type">records_custody_rule</data><data key="node_canonical_name">Concurrent Disability Title XVI Paper-Folder Custody at National Records Center</data><data key="node_acronym" /><data key="node_domain">Disability / Title XVI</data><data key="node_description">The SSA National Records Center holds Title XVI paper folders in concurrent Title II and XVI disability cases.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0007"><data key="node_entity_id">R145_E0007</data><data key="node_entity_type">case_transfer_control</data><data key="node_canonical_name">eCDR Associated Paper Folder Transfer Requirement</data><data key="node_acronym" /><data key="node_domain">Disability / Evidence</data><data key="node_description">When an FO forwards an electronic continuing disability review to DDS, the field office must also forward associated paper folder or folders, if any.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0008"><data key="node_entity_id">R145_E0008</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Concurrent Continuing-Disability Cross-Title Decision Coordination</data><data key="node_acronym" /><data key="node_domain">Disability / Adjudication</data><data key="node_description">DDS generally makes determinations under both Title II and Title XVI for a common disability issue, attempts to resolve unresolved concurrent Title XVI issues, and requests FO clarification when record titles conflict.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0009"><data key="node_entity_id">R145_E0009</data><data key="node_entity_type">case_handling_rule</data><data key="node_canonical_name">Concurrent CDR SSI2 Query Without Title XVI Paper Folder Exception</data><data key="node_acronym" /><data key="node_domain">Disability / Evidence</data><data key="node_description">A Title II case reaching DDS with an SSI2 query ordinarily does not require retrieval of the Title XVI paper folder unless DDS needs additional evidence believed to be in that folder.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0010"><data key="node_entity_id">R145_E0010</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">DDSQ Versus Final SSA-831 Adjudicative Discrepancy Control</data><data key="node_acronym" /><data key="node_domain">Disability / Program Integrity</data><data key="node_description">DDSQ disability decisional information may lag Disability Quality Review revisions; workers must verify critical adjudicative details against the final SSA-831 before action.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0011"><data key="node_entity_id">R145_E0011</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">FO-to-DDS 14-Day Development Status-Control Rule</data><data key="node_acronym" /><data key="node_domain">Disability / FO-DDS Exchange</data><data key="node_description">When the field office cannot immediately fulfill a DDS assistance request, it must control the request and provide development or a status report including expected completion within 14 days.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0012"><data key="node_entity_id">R145_E0012</data><data key="node_entity_type">interface_data_rule</data><data key="node_canonical_name">NDDSS DDSQ Four-Way System Override Suppression Semantics</data><data key="node_acronym" /><data key="node_domain">Disability / Data Exchange</data><data key="node_description">DDSQ SO values N, C, D, Y mean respectively no override; movement only (decision suppressed); decisional only (control suppressed); and all data transmission suppressed.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0013"><data key="node_entity_id">R145_E0013</data><data key="node_entity_type">publication_data_product</data><data key="node_canonical_name">SSA-1099 and SSA-1042S Benefit-Tax Statement Data Product</data><data key="node_acronym">SSA-1099/1042S</data><data key="node_domain">Title II / Tax / Publication</data><data key="node_description">Social Security Benefit Statements report annual benefit amounts relevant to taxation; SSA-1099 covers U.S. citizens/residents and SSA-1042S covers noncitizens/nonresidents. Unlike the earnings Social Security Statement.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Not to be conflated with SSA-7004 or earnings records.</data></node><node id="R145_E0014"><data key="node_entity_id">R145_E0014</data><data key="node_entity_type">digital_access_policy</data><data key="node_canonical_name">mySSA Six-Tax-Year Benefit Statement Online Availability Window</data><data key="node_acronym" /><data key="node_domain">Title II / Digital Service</data><data key="node_description">For benefit-payment years, my Social Security offers current and previous five tax-year SSA-1099/1042S benefit statements; current statement accessible after January 31.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0015"><data key="node_entity_id">R145_E0015</data><data key="node_entity_type">communication_control</data><data key="node_canonical_name">Representative Payee Benefit Statement Mandatory Paper Delivery Exception</data><data key="node_acronym" /><data key="node_domain">Title II / Payee / Postal</data><data key="node_description">Social Security Benefit Statements are mailed to representative payees on record; beneficiaries who have payees cannot opt out of paper notice delivery under cited POMS.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0016"><data key="node_entity_id">R145_E0016</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">Undeliverable SSA-1099/1042S Privacy-Safe Disposal Without Address Development</data><data key="node_acronym" /><data key="node_domain">Address Provenance / Tax Correspondence</data><data key="node_description">Program Service Center workers discard undeliverable benefit tax statements with proper PII disposal and no further address development because such statements are informational.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Undeliverable delivery is not an SSA master-record address-correction trigger.</data></node><node id="R145_E0017"><data key="node_entity_id">R145_E0017</data><data key="node_entity_type">publication_pipeline</data><data key="node_canonical_name">Social Security Benefit Statement Central Correction and Print Pipeline</data><data key="node_acronym" /><data key="node_domain">Title II / Annual Statement</data><data key="node_description">Corrected SSA-1099-SM-C output uses an automated Central Office process and National Computer Center printing and mailing; manual flat-sheet replacements address nonautomatable cases.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">The exact database, scheduling, software and physical hosting are not identified.</data></node><node id="R145_E0018"><data key="node_entity_id">R145_E0018</data><data key="node_entity_type">postal_restriction</data><data key="node_canonical_name">Benefit Statement Foreign-Mail Service Suspension Rule</data><data key="node_acronym" /><data key="node_domain">Address Provenance / Title II</data><data key="node_description">SSA does not mail Forms SSA-1099/1042S to addresses in countries on the USPS international suspension list or covered sanctioned countries/regions under cited policy.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0019"><data key="node_entity_id">R145_E0019</data><data key="node_entity_type">legal_data_classification</data><data key="node_canonical_name">Claimant-Origin Tax Form Versus Official Earnings Record FTI Conversion</data><data key="node_acronym" /><data key="node_domain">IRS / Earnings Provenance</data><data key="node_description">W-2/1040 supplied directly by an individual as claim proof is not tax return information solely by that origin; if SSA uses it to create or amend the official earnings record, the new official earnings record becomes IRC-controlled tax return information.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">This is a legal-use and provenance status change, not a statement about storage technology or address update.</data></node><node id="R145_E0020"><data key="node_entity_id">R145_E0020</data><data key="node_entity_type">legal_access_control</data><data key="node_canonical_name">SSA Federal Tax Return Information Source-Sensitive Access Gate</data><data key="node_acronym" /><data key="node_domain">IRS / Security / Data Governance</data><data key="node_description">Return information maintained for IRS purposes is subject to IRC disclosure and privacy restrictions, with specific permissible field office disclosures to the individual, qualifying claimant, or authorized representative.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0021"><data key="node_entity_id">R145_E0021</data><data key="node_entity_type">program_integrity_status</data><data key="node_canonical_name">EDCOR Employer Wage Name-SSN Mismatch Notification Versus Suspended DECOR</data><data key="node_acronym" /><data key="node_domain">Earnings / Identity</data><data key="node_description">POMS states employer-directed EDCOR notices issue for wage reports with mismatched names/SSNs, while employee-directed DECOR letter mailings remain suspended as of observed policy.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Status is observed 2026-10-09; historical DECOR processing should not be inferred current.</data></node><node id="R145_E0022"><data key="node_entity_id">R145_E0022</data><data key="node_entity_type">statistical_publication</data><data key="node_canonical_name">Fast Facts &amp; Figures About Social Security 2026</data><data key="node_acronym" /><data key="node_domain">Actuarial / Public Data</data><data key="node_description">SSA 2026 Fast Facts statistical chartbook provides insured-worker, beneficiary, covered-earnings, and SSI tabulations with period- and population-specific qualifiers.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Public chartbook and cited data sources do not establish production databases or software.</data></node><node id="R145_E0023"><data key="node_entity_id">R145_E0023</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 Fast Facts Insured Status by Sex 1970–2025 Data Table</data><data key="node_acronym" /><data key="node_domain">Actuarial / Insured Status</data><data key="node_description">Actuarial Services chart compares fully insured and disability-insured percentages for men and women in 1970 and 2025; 2025 fully insured men 90%, women 87%, disability-insured men 79%, women 75%.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0024"><data key="node_entity_id">R145_E0024</data><data key="node_entity_type">statistical_definition</data><data key="node_canonical_name">OACT Social Security Area Denominator Scope for Insured Status</data><data key="node_acronym" /><data key="node_domain">Actuarial / Data Quality</data><data key="node_description">Insured-status population denominator is Social Security area population, including residents, specified territories, selected military/federal workers abroad, covered noncitizens abroad and citizens abroad, not simply U.S. resident census.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0025"><data key="node_entity_id">R145_E0025</data><data key="node_entity_type">eligibility_evidence_rule</data><data key="node_canonical_name">Prior Benefit Record Insured-Status Proof Scope Limitation</data><data key="node_acronym" /><data key="node_domain">Title II / Earnings</data><data key="node_description">Prior benefits evidence of entitlement must prove the specific insured-status test for the new claim; a benefit paid based only on current insured status does not establish full insured status required for parent benefits.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0026"><data key="node_entity_id">R145_E0026</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">MEF Earnings-Correction Query Reconciliation Gate</data><data key="node_acronym" /><data key="node_domain">Earnings / Title II</data><data key="node_description">An earnings correction visible in EARN/ECOR queries should not be accepted as fully reflected in official earnings records until verified against a DEQY or appropriate record; further correction processing may be required.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R145_E0027"><data key="node_entity_id">R145_E0027</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">SSA-1696 Representative Appointment Cross-System Verification Control</data><data key="node_acronym" /><data key="node_domain">Representative / Claims / Disability</data><data key="node_description">Following electronic representative appointment receipt, SSA personnel verify that representation is reflected in the relevant claims and disability processes; a stored appointment alone does not establish all system-specific flags updated.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Model only documented human verification, no inferred real-time propagation.</data></node><node id="R146_E0001"><data key="node_entity_id">R146_E0001</data><data key="node_entity_type">external_system</data><data key="node_canonical_name">IRS Filing Information Returns Electronically (FIRE) ERISA Reporting Channel</data><data key="node_acronym" /><data key="node_domain">IRS / External Exchange</data><data key="node_description">IRS FIRE electronically receives Form 8955-SSA filings and IRS transmits electronic pension-plan participant information to SSA.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Documented historical 2019 procedures, 2026 instructions confirm electronic transfer. No transport protocol or database inferred.</data></node><node id="R146_E0002"><data key="node_entity_id">R146_E0002</data><data key="node_entity_type">database</data><data key="node_canonical_name">SSA ERISA Deferred Vested Benefit Information Database</data><data key="node_acronym" /><data key="node_domain">IRS / Pensions / Person</data><data key="node_description">SSA maintains an ERISA database containing private-plan deferred-vested participant information received through IRS and historical DOL pathways.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Historical operational description 2019; physical storage technology and current migration status unknown.</data></node><node id="R146_E0003"><data key="node_entity_id">R146_E0003</data><data key="node_entity_type">application</data><data key="node_canonical_name">ERISA Automated Image Retrieval System (AIRS)</data><data key="node_acronym" /><data key="node_domain">IRS / Archival Pensions</data><data key="node_description">AIRS stores scanned images from paper Form 8955-SSA filings and supports inquiry into 12-digit document-control-number cases.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Do not conflate this acronym with previously mapped Automated Incident Reporting System.</data></node><node id="R146_E0004"><data key="node_entity_id">R146_E0004</data><data key="node_entity_type">historical_exchange</data><data key="node_canonical_name">DOL ERISA Filing Acceptance System (EFAST) SSA Historical Exchange</data><data key="node_acronym" /><data key="node_domain">IRS / DOL / Historical Exchange</data><data key="node_description">DOL EFAST formerly scanned and electronically transmitted Form 5500 Schedule SSA pension data to SSA before June 2010.</data><data key="node_observed_status">retired_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Historical architecture, not a 2026 active exchange.</data></node><node id="R146_E0005"><data key="node_entity_id">R146_E0005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Wilkes-Barre Paper Form 8955-SSA Scan and Fallout Processing</data><data key="node_acronym" /><data key="node_domain">External Exchange / Pensions</data><data key="node_description">WBDOC processes paper Form 8955-SSA filings received from IRS by scanning, transmission, or exception handling for SSA ERISA records.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">2019 POMS does not establish 2026 technology or current paper volumes.</data></node><node id="R146_E0006"><data key="node_entity_id">R146_E0006</data><data key="node_entity_type">data_lineage_code</data><data key="node_canonical_name">SSA-L99-C1 12-Digit Paper-Source Document Control Number</data><data key="node_acronym" /><data key="node_domain">IRS / ERISA / Publication</data><data key="node_description">Twelve-digit DCN denotes paper Form 8955-SSA processed from IRS, with images stored in AIRS.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0007"><data key="node_entity_id">R146_E0007</data><data key="node_entity_type">data_lineage_code</data><data key="node_canonical_name">SSA-L99-C1 14-Digit Electronic-Source Document Control Number</data><data key="node_acronym" /><data key="node_domain">IRS / ERISA / Publication</data><data key="node_description">Fourteen-digit DCN denotes electronic IRS FIRE-sourced pension filing; SSA states no underlying images are stored.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0008"><data key="node_entity_id">R146_E0008</data><data key="node_entity_type">data_lineage_code</data><data key="node_canonical_name">SSA-L99-C1 M-Prefixed Microfilm Document Control Number</data><data key="node_acronym" /><data key="node_domain">IRS / ERISA / Legacy</data><data key="node_description">M followed by twelve digits identifies pre-2008 paper Schedule SSA/5500 data recorded on microfilm in IRON.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0009"><data key="node_entity_id">R146_E0009</data><data key="node_entity_type">data_access_limitation</data><data key="node_canonical_name">IRS Electronic ERISA Pension Notice No-Source-Image Restriction</data><data key="node_acronym" /><data key="node_domain">IRS / ERISA / Evidence</data><data key="node_description">For 14-digit electronically sourced cases SSA says there is no stored image or additional microfilm record for inquiry.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0010"><data key="node_entity_id">R146_E0010</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">ERISA Pension Plan Administrator Address As-Of Reported Plan Year</data><data key="node_acronym" /><data key="node_domain">Address Provenance / IRS / Pensions</data><data key="node_description">Address on SSA-L99-C1 reflects pension administrator name/address as reported to IRS for plan year, not necessarily current administrator address or participant residence.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0011"><data key="node_entity_id">R146_E0011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Monthly ERISA Deferred-Vested Benefits Notice Check</data><data key="node_acronym" /><data key="node_domain">Title II / Medicare / IRS</data><data key="node_description">For claimants filing Title II or hospital insurance, SSA checks its ERISA records and mails SSA-L99-C1 on a monthly notice cycle when data exists.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0012"><data key="node_entity_id">R146_E0012</data><data key="node_entity_type">evidence_processing_rule</data><data key="node_canonical_name">SSA-1020-OCR Photocopy Non-Scannability Processing Exception</data><data key="node_acronym" /><data key="node_domain">Medicare Part D / Paper Intake</data><data key="node_description">A photocopy of scannable SSA-1020-OCR does not scan; staff enter application in MAPS or complete a new original if MAPS is down.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0013"><data key="node_entity_id">R146_E0013</data><data key="node_entity_type">workflow_exception</data><data key="node_canonical_name">SSA-1020-OCR Resource-Screener WBDOC Exception Routing</data><data key="node_acronym" /><data key="node_domain">Medicare Part D / Intake</data><data key="node_description">If resource question 3 is yes and later answers blank, route paper application to WBDOC rather than ordinary MAPS entry.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0014"><data key="node_entity_id">R146_E0014</data><data key="node_entity_type">retention_processing_rule</data><data key="node_canonical_name">MAPS Extra Help Application Printing Required for Online Retrieval</data><data key="node_acronym" /><data key="node_domain">Medicare Part D / Records</data><data key="node_description">SSA guidance requires printing the MAPS application to ensure that it is stored in Online Retrieval System.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0015"><data key="node_entity_id">R146_E0015</data><data key="node_entity_type">document_retrieval_repository</data><data key="node_canonical_name">Online Retrieval System for MAPS Extra Help Printed Applications</data><data key="node_acronym" /><data key="node_domain">Medicare Part D / Records</data><data key="node_description">Online Retrieval System (ORS) stores printed MAPS applications under the documented print process.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Only states the document retrieval function; does not claim database technology or full retention schedule.</data></node><node id="R146_E0016"><data key="node_entity_id">R146_E0016</data><data key="node_entity_type">person_relationship_rule</data><data key="node_canonical_name">Extra Help Unenumerated Spouse Household and Resource Development Exception</data><data key="node_acronym" /><data key="node_domain">Medicare Part D / Person/Identity</data><data key="node_description">Where spouse cannot obtain SSN after SSA alpha search, MAPS omits spouse entry yet includes spouse income and one additional household member, with conditional combined-resource reporting.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">2026 resource thresholds vary by year; specific dollar amounts not treated as persistent architecture.</data></node><node id="R146_E0017"><data key="node_entity_id">R146_E0017</data><data key="node_entity_type">signature_evidence_rule</data><data key="node_canonical_name">MAPS Part D ATTEST Signature Proxy and Online Retrieval Control</data><data key="node_acronym" /><data key="node_domain">Medicare Part D / Signatures</data><data key="node_description">MAPS employee records claimant affirmation via development worksheet; printed application must be retained for ORS; i1020 uses click-and-sign instead.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0018"><data key="node_entity_id">R146_E0018</data><data key="node_entity_type">program_integrity_data_repository</data><data key="node_canonical_name">RASR Ineligible for Direct Payment Entity (IDPE) List</data><data key="node_acronym" /><data key="node_domain">Representation / Debt / Program Integrity</data><data key="node_description">RASR IDPE list tracks business entities disqualified from direct payment of representative fees when identified excess fee debts are unresolved.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">This is RASR managed list, not an independently demonstrated separate physical DB.</data></node><node id="R146_E0019"><data key="node_entity_id">R146_E0019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA IDPE Coordinator Group Referral and Adjudication Process</data><data key="node_acronym" /><data key="node_domain">Representation / Debt / Program Integrity</data><data key="node_description">FO/PC managers refer unresolved excessive entity fee obligations to an IDPE Coordinator Group following two documented notices and response periods.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0020"><data key="node_entity_id">R146_E0020</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">Representative Entity Excess-Fee Recovery 30-Day Dual-Notice Control</data><data key="node_acronym" /><data key="node_domain">Representation / Debt</data><data key="node_description">For entity debts, technician sends initial MAO104 and final MAO105 notices with two sequential thirty-day response controls before IDPE referral.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0021"><data key="node_entity_id">R146_E0021</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">Individual Representative Excess-Fee 45-Day Follow-Up Control</data><data key="node_acronym" /><data key="node_domain">Representation / Debt</data><data key="node_description">An individual representative has a separate 45-day diary, potential OGC sanction referral and appropriate Debt Management entries.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0022"><data key="node_entity_id">R146_E0022</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">RASR Appointment-Related Report of Contact (ROCD) Screen</data><data key="node_acronym" /><data key="node_domain">Representation / Person</data><data key="node_description">For entity excess fee, technicians record report of contact separately for each representative who assigned direct payment to entity.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0023"><data key="node_entity_id">R146_E0023</data><data key="node_entity_type">notice_product</data><data key="node_canonical_name">MAO104 Initial Collection Action Notice to Representative Entity</data><data key="node_acronym" /><data key="node_domain">Representation / Correspondence</data><data key="node_description">Initial entity fee collection notice issued through DPS or AURORA addressed to registered entity contact.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0024"><data key="node_entity_id">R146_E0024</data><data key="node_entity_type">notice_product</data><data key="node_canonical_name">MAO105 Final Collection Action Notice to Representative Entity</data><data key="node_acronym" /><data key="node_domain">Representation / Correspondence</data><data key="node_description">Final entity fee collection notice after first 30-day period, followed by second 30-day diary.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0025"><data key="node_entity_id">R146_E0025</data><data key="node_entity_type">notice_product</data><data key="node_canonical_name">RSR-122 Notification of Ineligibility for Entity Direct Fee Payment</data><data key="node_acronym" /><data key="node_domain">Representation / Correspondence</data><data key="node_description">RASR produces notice of action terminating entity eligibility after an IDPE record is established; notice not repeated when entity already ineligible.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0026"><data key="node_entity_id">R146_E0026</data><data key="node_entity_type">processing_exception</data><data key="node_canonical_name">Representative Excess-Fee Remittance DMS-PHUS Manual Reconciliation Exception</data><data key="node_acronym" /><data key="node_domain">Representation / Payment Integrity</data><data key="node_description">After Mid-Atlantic PSC remittance accounting, staff may need manual DMS and PHUS entries when automated remittance interface does not occur.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0027"><data key="node_entity_id">R146_E0027</data><data key="node_entity_type">eligibility_control</data><data key="node_canonical_name">SSI IRS 5B Individual and Couple Alert Selection Tolerances</data><data key="node_acronym" /><data key="node_domain">Title XVI / IRS / Program Integrity</data><data key="node_description">IRS income/resource match establishes 5B diary using $61 individual/$101 couple resource indicators and $1,001 income indicators with prior-alert comparison exclusions.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Thresholds documented as 2017 POMS; 2026 current rate not independently reverified.</data></node><node id="R146_E0028"><data key="node_entity_id">R146_E0028</data><data key="node_entity_type">batch_control</data><data key="node_canonical_name">SSI IRS 1099 Three-Batch RZ-LI Alert Calendar</data><data key="node_acronym" /><data key="node_domain">Title XVI / IRS / Analytics</data><data key="node_description">IRS information ordinarily released October, March and June with field-office alert availability around November 1, May 1 and July 1, for defined beneficiary cohorts.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">2017 policy; avoid interpreting this as live observed daily process.</data></node><node id="R146_E0029"><data key="node_entity_id">R146_E0029</data><data key="node_entity_type">review_workflow</data><data key="node_canonical_name">Federal Salary Offset Review Paperless-Paper Dual Routing Control</data><data key="node_acronym" /><data key="node_domain">Payments / Debt / Appeals</data><data key="node_description">For FSO review SSA faxes document packet to DMS paperless for PCACS/Evidence Portal verification while preparing paper appeal folder to Office of Appellate Operations.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0030"><data key="node_entity_id">R146_E0030</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">Federal Salary Offset Field Office Ten-Day Verification Holding Period</data><data key="node_acronym" /><data key="node_domain">Payments / Debt / Evidence</data><data key="node_description">Field office retains a 10-day copy pending confirmation that a processing-center paperless issue was created; if not present, contacts DMS and retransmits.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0031"><data key="node_entity_id">R146_E0031</data><data key="node_entity_type">transaction_contact_rule</data><data key="node_canonical_name">TED One-Time Upload Link Email Address Selection Control</data><data key="node_acronym" /><data key="node_domain">Digital Service / Person</data><data key="node_description">In technician-initiated Upload Documents, TED shows my Social Security email when available but requester can elect another verified email for one-time link; address is per-transaction.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Archived 2024 EM only; do not infer a master-email profile update.</data></node><node id="R146_E0032"><data key="node_entity_id">R146_E0032</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">TED Upload Documents 30-Day Customer Task Auto-Close Control</data><data key="node_acronym" /><data key="node_domain">Digital Intake</data><data key="node_description">Technician-generated eSignature Upload Documents task expires and automatically closes after 30 days if customer does not submit.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Archived May 2024 operating procedure, later releases may differ.</data></node><node id="R146_E0033"><data key="node_entity_id">R146_E0033</data><data key="node_entity_type">architecture_boundary</data><data key="node_canonical_name">WorkTrack Batch Import Versus Customer Upload Separation</data><data key="node_acronym" /><data key="node_domain">Digital Intake / Evidence</data><data key="node_description">WorkTrack Upload batch import is separate from eSignature/Upload Documents customer submission; manuals distinguish the two routes.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0034"><data key="node_entity_id">R146_E0034</data><data key="node_entity_type">modernization_capability</data><data key="node_canonical_name">SSA-827 Fillable eSignature Webform April 2024 Release</data><data key="node_acronym" /><data key="node_domain">Disability / Evidence</data><data key="node_description">SSA introduced fillable webform for SSA-827 as an alternative to PDF; resulting signed form appears in WorkTrack.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Historical dated capability; no current release-state claim.</data></node><node id="R146_E0035"><data key="node_entity_id">R146_E0035</data><data key="node_entity_type">statistical_publication_status</data><data key="node_canonical_name">2026 Annual Statistical Supplement Sectional Release Revision Caveat</data><data key="node_acronym" /><data key="node_domain">Statistical / Publication</data><data key="node_description">2026 supplement issued in sections; all published tables are provisional and subject to correction until full release planned for Feb 28, 2027.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Observed 2026-10-09; planned completion is not proof of future completion.</data></node><node id="R146_E0036"><data key="node_entity_id">R146_E0036</data><data key="node_entity_type">statistical_processing_rule</data><data key="node_canonical_name">Monthly Statistical Snapshot August 2026 MBR-SSR Complete-Count Deduplication Rule</data><data key="node_acronym" /><data key="node_domain">Statistical / Enterprise Data</data><data key="node_description">SSA Monthly Snapshot Table 1 uses 100% MBR and SSR records, counting dual entitlement only once while separately showing concurrent OASDI-SSI recipients.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R146_E0037"><data key="node_entity_id">R146_E0037</data><data key="node_entity_type">statistical_processing_rule</data><data key="node_canonical_name">Monthly SSI Snapshot Retroactive-Payment Average Exclusion Rule</data><data key="node_acronym" /><data key="node_domain">Statistical / SSI</data><data key="node_description">In Monthly Statistical Snapshot, SSI total payments include retroactive amounts but average monthly payment excludes retroactive payments.</data><data key="node_observed_status">documented_procedure</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0001"><data key="node_entity_id">R147_E0001</data><data key="node_entity_type">public_csv_dataset</data><data key="node_canonical_name">ALJ Claimants Pending Determination End-of-Fiscal-Year Dataset 2005–2017</data><data key="node_domain">Disability / Hearings / Statistics</data><data key="node_description">SSA Open Data CSV US-GOV-SSA-2372: OASDI and SSI claimants with pending ALJ cases at fiscal year end, counts by total, living and age (under 18 or 18+); FY2009 limited to April–September.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Historical CPMS microdata (2005-2017); does not demonstrate current CPMS deployment.</data></node><node id="R147_E0002"><data key="node_entity_id">R147_E0002</data><data key="node_entity_type">statistical_interpretation_rule</data><data key="node_canonical_name">Pending ALJ Total Includes Deceased Claimants with Open Cases</data><data key="node_domain">Hearings / Mortality / Statistical Rules</data><data key="node_description">The published ALJ pending total may exceed the alive-at-year-end count because some cases remain open following death for possible benefits to families or estates.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Pending workload denominator and living claimant population are not interchangeable.</data></node><node id="R147_E0003"><data key="node_entity_id">R147_E0003</data><data key="node_entity_type">statistical_coverage_rule</data><data key="node_canonical_name">2009 Pending ALJ Claimant Dataset April–September Coverage Caveat</data><data key="node_domain">Hearings / Workload / Statistical Rules</data><data key="node_description">The pending-ALJ data page flags its 2009 values as April–September only, precluding comparisons as a complete 12-month federal fiscal-year workload without adjustment.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0004"><data key="node_entity_id">R147_E0004</data><data key="node_entity_type">actuarial_statistical_data_product</data><data key="node_canonical_name">Actuarial Note 159 Seven-Table Machine-Readable Mortality Series 2006–2017</data><data key="node_domain">OACT / Disability / Statistics</data><data key="node_description">SSA Open Data US-GOV-SSA-1859 publishes seven CSV tables supporting Actuarial Note 159, including claimant deaths and age-sex-adjusted death rates for individuals awaiting an ALJ determination.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Historical analysis, not current real-time disability claim data.</data></node><node id="R147_E0005"><data key="node_entity_id">R147_E0005</data><data key="node_entity_type">statistical_interpretation_rule</data><data key="node_canonical_name">ALJ Pending Death Rate Age-and-Sex Adjustment Requirement</data><data key="node_domain">OACT / Disability / Statistical Rules</data><data key="node_description">Actuarial Note 159 compares age-sex-adjusted death rates; the seven machine-readable tables must be interpreted in the note context, and raw deaths cannot establish a trend in mortality risks without valid denominators and composition adjustments.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0006"><data key="node_entity_id">R147_E0006</data><data key="node_entity_type">statistical_reporting_rule</data><data key="node_canonical_name">ALJ Workload Fiscal Year End-of-Week Convention</data><data key="node_domain">Hearings / Statistics</data><data key="node_description">SSA workload fiscal year begins on the Saturday following the last Friday of September and ends on the last Friday of September; 52-week and 53-week years may occur.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0007"><data key="node_entity_id">R147_E0007</data><data key="node_entity_type">actuarial_statistical_data_product</data><data key="node_canonical_name">2026 Trustees Report Table VI.H1 OASI Disability-Related Benefit Payments</data><data key="node_domain">OACT / Trust Funds / Disability</data><data key="node_description">2026 OASDI Trustees Report Table VI.H1 provides OASI disabled-related beneficiary counts and scheduled OASI payments for 1960–2025 selected historical years and estimated 2026–2035; 2025 has 1.194 million persons and $16.924 billion.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0008"><data key="node_entity_id">R147_E0008</data><data key="node_entity_type">actuarial_statistical_data_product</data><data key="node_canonical_name">2026 Trustees Report Table VI.H2 Disability-Related OASDI Trust Fund Allocation</data><data key="node_domain">OACT / Trust Funds / Disability</data><data key="node_description">2026 Trustees Report Table VI.H2 shows disability-related OASDI scheduled payments split by DI and OASI trust funds; 2025 total $175.013 billion, DI $158.090 billion, OASI $16.924 billion or 9.7 percent.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0009"><data key="node_entity_id">R147_E0009</data><data key="node_entity_type">actuarial_population_rule</data><data key="node_canonical_name">OASI Disability-Related Payments Exclude Widows and Widowers Age 60+</data><data key="node_domain">OACT / Trust Funds / Classification</data><data key="node_description">Section VI.H disability-related OASI accounting includes adult disabled children, disabled widows/widowers aged 50–59, and certain mothers/fathers caring for disabled children; excludes disabled widows/widowers age 60+ because age eligibility provides entitlement independent of disability.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0010"><data key="node_entity_id">R147_E0010</data><data key="node_entity_type">actuarial_reporting_rule</data><data key="node_canonical_name">2020–2021 January 3 Early Trust Fund Payment Adjustment</data><data key="node_domain">OACT / Trust Funds / Statistical Rules</data><data key="node_description">2026 Trustees Report Tables VI.H1 and VI.H2 adjust 2020 and 2021 to place scheduled January 3, 2021 benefit payments (actually paid December 31, 2020) in the regular 2021 period for calendar-year comparability.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0011"><data key="node_entity_id">R147_E0011</data><data key="node_entity_type">actuarial_projection_rule</data><data key="node_canonical_name">2026 OASI Disability-Related Estimates Use Intermediate Trustee Assumptions</data><data key="node_domain">OACT / Trust Funds / Projection Status</data><data key="node_description">2026 Trustees Tables VI.H1 and VI.H2 provide estimated scheduled payments for 2026–2035 under intermediate assumptions. The 2026 projected OASI disabled-related payment is $17.530 billion, not a finalized FY2026 transaction ledger.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0012"><data key="node_entity_id">R147_E0012</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Office of Analytics, Review, and Oversight (OARO)</data><data key="node_acronym">OARO</data><data key="node_domain">Hearings / Appeals / Organization</data><data key="node_description">SSA organization responsible for Appeals Council review functions including new court case certified administrative record preparation and court-remand processing, as described by SSA FY2026 public workload files.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0013"><data key="node_entity_id">R147_E0013</data><data key="node_entity_type">public_xml_data_product</data><data key="node_canonical_name">FY2026 National New Court Cases Quarterly Receipts, Dispositions and Pending</data><data key="node_domain">Hearings / Federal Courts / Open Data</data><data key="node_description">SSA FY2026 National New Court Cases public XML tracks new federal civil suits following Appeals Council denial, and Appeals Council receipts, dispositions and pending case counts through June 26, 2026.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">FY2026 partial-year report, not full FY2026 total.</data></node><node id="R147_E0014"><data key="node_entity_id">R147_E0014</data><data key="node_entity_type">public_xml_data_product</data><data key="node_canonical_name">FY2026 Court Remands Quarterly Receipts, Dispositions and Pending</data><data key="node_domain">Hearings / Federal Courts / Open Data</data><data key="node_description">SSA FY2026 court-remands public XML tracks federal court remands to SSA for further administrative action and Appeals Council receipts, dispositions and pending cases, through June 26 2026.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">FY2026 partial-year report, not full FY2026 total.</data></node><node id="R147_E0015"><data key="node_entity_id">R147_E0015</data><data key="node_entity_type">judicial_processing_rule</data><data key="node_canonical_name">Appeals Council Certified Administrative Record for New Federal Court Cases</data><data key="node_domain">Hearings / Court / Evidence</data><data key="node_description">For a new federal civil lawsuit following Appeals Council denial, the Appeals Council prepares an administrative record containing a copy of the claim folder and provides it to the court of jurisdiction.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0016"><data key="node_entity_id">R147_E0016</data><data key="node_entity_type">public_xml_data_product</data><data key="node_canonical_name">Court Remands and New Federal Court Cases Filed Annual Series 2010–2025</data><data key="node_domain">Hearings / Courts / Statistics</data><data key="node_description">SSA public XML longitudinal series compares annual court-remand returns with the count of new court cases filed, FY2010–2025; FY2025 had 9,457 court remands and 15,098 newly filed court cases.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0017"><data key="node_entity_id">R147_E0017</data><data key="node_entity_type">statistical_interpretation_rule</data><data key="node_canonical_name">Annual Court Remands versus Court Filings Are Not the Same Case Cohort</data><data key="node_domain">Hearings / Courts / Statistical Rules</data><data key="node_description">Annual court remands often concern lawsuits initiated months or years earlier, so dividing annual court remands by new court filings for the same FY cannot establish an ultimate remand probability for that filing cohort.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0018"><data key="node_entity_id">R147_E0018</data><data key="node_entity_type">public_xml_data_product</data><data key="node_canonical_name">Appeals Council Remands Share of All Review Dispositions FY2010–2025</data><data key="node_domain">Hearings / Appeals / Statistics</data><data key="node_description">SSA longitudinal XML reports Appeals Council remand actions as share of all request-for-review dispositions, 2010–2025; FY2025 13,062 remands out of 84,045 AC review dispositions (15.54 percent).</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R147_E0019"><data key="node_entity_id">R147_E0019</data><data key="node_entity_type">statistical_reporting_rule</data><data key="node_canonical_name">Appeals Fiscal Year 2016 and 2022 52-Week versus 53-Week Variants</data><data key="node_domain">Hearings / Appeals / Statistics</data><data key="node_description">SSA annual Appeals Council and court remand public tables separately report 52-week and 53-week totals for FY2016 and FY2022; comparisons must use consistent fiscal-year period definitions.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R148_E0001"><data key="node_entity_id">R148_E0001</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">FPAR – published hearings and appeals MI table identifier</data><data key="node_acronym">FPAR</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">AC requests for review, receipts, dispositions and certain court-case metrics</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0002"><data key="node_entity_id">R148_E0002</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">FPALT – published court and hearings MI table identifier</data><data key="node_acronym">FPALT</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">New court cases, court remands, and related adjusted receipt/disposition counts</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0003"><data key="node_entity_id">R148_E0003</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">FPASDOH – published hearing-office MI table identifier</data><data key="node_acronym">FPASDOH</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">Hearing office workload, average processing time, dispositions, and reporting period fields</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0004"><data key="node_entity_id">R148_E0004</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">FPDSAR – published Appeals Council MI table identifier</data><data key="node_acronym">FPDSAR</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">Remand and grant-review reporting in the public data dictionary</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0005"><data key="node_entity_id">R148_E0005</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">MALJDOH – published ALJ MI table identifier</data><data key="node_acronym">MALJDOH</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">ALJ names and favorable, partially favorable and unfavorable disposition counts</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0006"><data key="node_entity_id">R148_E0006</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">FPASEF – published electronic/paper folder MI table identifier</data><data key="node_acronym">FPASEF</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">Counts of pending cases in electronic and paper formats</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0007"><data key="node_entity_id">R148_E0007</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">HROFFICE – published hearing office reference table</data><data key="node_acronym">HROFFICE</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">Owning hearing office name shown in public hearing-office reports</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0008"><data key="node_entity_id">R148_E0008</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">MVIDHEAR – published video-hearing MI table identifier</data><data key="node_acronym">MVIDHEAR</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">In-person hearings count in published data dictionary</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0009"><data key="node_entity_id">R148_E0009</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">MVIDYEAR – published video hearing MI table identifier</data><data key="node_acronym">MVIDYEAR</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">Video teleconference hearings count in published data dictionary</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0010"><data key="node_entity_id">R148_E0010</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">WRKUNH – published video opt-out MI table identifier</data><data key="node_acronym">WRKUNH</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">Video hearing opt-out data source</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0011"><data key="node_entity_id">R148_E0011</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">PACAR – published remand reason MI table identifier</data><data key="node_acronym">PACAR</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">Remand reason information in public hearings dictionary</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0012"><data key="node_entity_id">R148_E0012</data><data key="node_entity_type">mi_table_reference</data><data key="node_canonical_name">RMDRSN – published remand reason reference table</data><data key="node_acronym">RMDRSN</data><data key="node_domain">Hearings / Management Information / Published Data Dictionary</data><data key="node_description">Remand reason category source used for top ten remand reports</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0013"><data key="node_entity_id">R148_E0013</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">DSPN_AVGPT: Hearing-Disposition Mean Elapsed Calendar Days</data><data key="node_acronym">DSPN_AVGPT</data><data key="node_domain">Hearings / Published Data Dictionary</data><data key="node_description">SMALLINT NOT NULL; calendar days from hearing request date to disposition date; not days of employee processing time</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0014"><data key="node_entity_id">R148_E0014</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">ADJ_RCVD_CNT: Adjusted Hearing or Review Receipts</data><data key="node_acronym">ADJ_RCVD_CNT</data><data key="node_domain">Hearings / Published Data Dictionary</data><data key="node_description">INTEGER NOT NULL; adjusted receipts, not necessarily gross new receipts</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0015"><data key="node_entity_id">R148_E0015</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">PEND_END_CNT: Pending Cases at Reporting Period End</data><data key="node_acronym">PEND_END_CNT</data><data key="node_domain">Hearings / Published Data Dictionary</data><data key="node_description">INTEGER NOT NULL; excludes cases in CLSD status</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0016"><data key="node_entity_id">R148_E0016</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EFCASES: Electronic Cases Pending Count</data><data key="node_acronym">EFCASES</data><data key="node_domain">Hearings / Published Data Dictionary</data><data key="node_description">INTEGER NOT NULL; electronic-format cases pending at end of period</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0017"><data key="node_entity_id">R148_E0017</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">PAPERCASES: Paper Cases Pending Count</data><data key="node_acronym">PAPERCASES</data><data key="node_domain">Hearings / Published Data Dictionary</data><data key="node_description">INTEGER NOT NULL; paper-format cases pending at end of period</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0018"><data key="node_entity_id">R148_E0018</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">TOTAL_ALJ_DISPOSITIONS_ACROSS_ALL_OFFICES Field</data><data key="node_acronym">TOTAL_ALJ_DISPOSITIONS</data><data key="node_domain">Hearings / Published Data Dictionary</data><data key="node_description">INTEGER NOT NULL; judge-wide total can differ from office-specific judge disposition count</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0019"><data key="node_entity_id">R148_E0019</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">DLY_DSPN_ALJ_ACNT: Dispositions per Day per Available ALJ</data><data key="node_acronym">DLY_DSPN_ALJ_ACNT</data><data key="node_domain">Hearings / Published Data Dictionary</data><data key="node_description">DECIMAL(5,2) NOT NULL; mean per-day dispositions, not judge-specific work time</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0020"><data key="node_entity_id">R148_E0020</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">REMAND_REASON: Administrative or Court Remand Category</data><data key="node_acronym">REMAND_REASON</data><data key="node_domain">Hearings / Published Data Dictionary</data><data key="node_description">CHAR (MULTIPLE) NOT NULL; remand reason category in AC and federal-court reports</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0021"><data key="node_entity_id">R148_E0021</data><data key="node_entity_type">publication_rule</data><data key="node_canonical_name">FY2026 OHO Average Processing Time Measures Calendar Days</data><data key="node_acronym" /><data key="node_domain">Hearings / Performance Reporting</data><data key="node_description">DSPN_AVGPT is calendar days between request and disposition, not active handling or elapsed time from application.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0022"><data key="node_entity_id">R148_E0022</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">FY2026 OHO August 28 Hearing Office Average Processing Time Ranking</data><data key="node_acronym" /><data key="node_domain">Hearings / FY2026 / Public Data</data><data key="node_description">SSA published office rankings through 2026-08-28 with 228 fiscal-year workdays; excludes later reporting periods; satellite offices may be separate.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0023"><data key="node_entity_id">R148_E0023</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">FY2026 OHO August 28 ALJ Dispositions per Day Ranking</data><data key="node_acronym" /><data key="node_domain">Hearings / FY2026 / Public Data</data><data key="node_description">SSA released hearing-office ranking through 2026-08-28 using 228 workdays; not a measure of total effort by individual ALJs.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0024"><data key="node_entity_id">R148_E0024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eRPS Partnership or Sole Proprietorship Individual-Payee Classification</data><data key="node_acronym" /><data key="node_domain">Representative Payee / Identity / Business Classification</data><data key="node_description">Sole proprietors and general/limited partnerships are entered as individual payees under owner/general partner SSN even where EIN exists.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0025"><data key="node_entity_id">R148_E0025</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eRPS Joint-Guardian Single-SSN and Additional-Guardian Note Rule</data><data key="node_acronym" /><data key="node_domain">Representative Payee / Person Identity</data><data key="node_description">Joint guardian cases use SSN of first named guardian as identifier; additional guardian names and SSNs are documented in applicant note.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0026"><data key="node_entity_id">R148_E0026</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">eRPS Organization ID Physical-Location ZIP Provenance</data><data key="node_acronym" /><data key="node_domain">Representative Payee / Organization Identity / Address</data><data key="node_description">Organization ID uses ZIP of physical business location; verified EIN is not independently unique for eRPS organizational identification.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0027"><data key="node_entity_id">R148_E0027</data><data key="node_entity_type">process_boundary</data><data key="node_canonical_name">DHS SAVE Claims versus Enumeration Access-Route Separation</data><data key="node_acronym" /><data key="node_domain">Identity / DHS / External Exchange</data><data key="node_description">Claims use I-Main access to SAVE, while enumeration uses SSNAP; SAVE/USCIS status confirmation is not benefits eligibility adjudication.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0028"><data key="node_entity_id">R148_E0028</data><data key="node_entity_type">evidence_retention_process</data><data key="node_canonical_name">DHS Immigration Evidence Copy and SAVE Response Electronic Filing</data><data key="node_acronym" /><data key="node_domain">Identity / Immigration / Claims Evidence</data><data key="node_description">SSA directs employees to copy immigration document and SAVE response, upload to electronic evidence folder/eView and return original document.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0029"><data key="node_entity_id">R148_E0029</data><data key="node_entity_type">verification_rule</data><data key="node_canonical_name">SAVE Unconfirmed Status Additional Verification Requirement</data><data key="node_acronym" /><data key="node_domain">Identity / DHS / Program Integrity</data><data key="node_description">A SAVE query that does not confirm alleged lawful status does not alone justify suspending benefits; obtain secondary G-845 verification as required.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0030"><data key="node_entity_id">R148_E0030</data><data key="node_entity_type">verification_rule</data><data key="node_canonical_name">Title II DHS Lawful-Presence Document Status-Specific Reverification Schedule</data><data key="node_acronym" /><data key="node_domain">Title II / Immigration / Periodic Verification</data><data key="node_description">2026 evidence matrix specifies verification after defined periods or document expiration for particular immigration categories; no universal fixed-date rule.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0031"><data key="node_entity_id">R148_E0031</data><data key="node_entity_type">person_identity_rule</data><data key="node_canonical_name">Representative Payee ABLE Account Ownership and Signature Authority Separation</data><data key="node_acronym" /><data key="node_domain">Representative Payee / External Financial Account</data><data key="node_description">Beneficiary owns ABLE funds, SSA representative payee may differ from account signatory; payee must have authority to deposit SSA benefits.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0032"><data key="node_entity_id">R148_E0032</data><data key="node_entity_type">payment_control_rule</data><data key="node_canonical_name">ABLE Account Signature Authority Loss Requires Direct-Deposit Change</data><data key="node_acronym" /><data key="node_domain">Representative Payee / Payment Control</data><data key="node_description">When payee loses ABLE signature authority, cannot continue receiving benefits into that account; report and re-evaluate suitability/capability.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0033"><data key="node_entity_id">R148_E0033</data><data key="node_entity_type">financial_provenance_rule</data><data key="node_canonical_name">ABLE Account SSA Conserved Funds Segregation and Two-Year Payee Record Guidance</data><data key="node_acronym" /><data key="node_domain">Representative Payee / Accounting and Retention</data><data key="node_description">Payees advised to preserve records at least two full calendar years; mixed ABLE contributions require tracking SSA benefits separately from non-SSA monies.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0034"><data key="node_entity_id">R148_E0034</data><data key="node_entity_type">financial_process_rule</data><data key="node_canonical_name">ABLE Conserved Funds Payee Change Direct-Signature Transfer Exception</data><data key="node_acronym" /><data key="node_domain">Representative Payee / Payment and Conservation</data><data key="node_description">SSA may approve direct transfer of control/signature authority for ABLE account on payee change; otherwise former payee generally returns conserved benefits.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0035"><data key="node_entity_id">R148_E0035</data><data key="node_entity_type">public_statistical_product</data><data key="node_canonical_name">2026 Annual Statistical Supplement Table 5.L1 OASDI Representative-Payee Beneficiary Counts</data><data key="node_acronym" /><data key="node_domain">OACT / OASDI / Representative Payee</data><data key="node_description">December 2025 MBR 100% population: 4,601,291 of 70,451,490 OASDI beneficiaries have payees; 674,114 of 7,125,880 disabled workers (9.5%).</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R148_E0036"><data key="node_entity_id">R148_E0036</data><data key="node_entity_type">statistical_interpretation_rule</data><data key="node_canonical_name">OHO ALJ Dispositions Across All Hearing Offices Counting Rule</data><data key="node_acronym" /><data key="node_domain">Hearings / Public Data / Geography</data><data key="node_description">Individual ALJ total across offices can differ from dispositions shown for a given hearing office because some ALJs decide cases in multiple offices.</data><data key="node_observed_status">documented publication identifier; current physical deployment not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified name/purpose only; underlying platform, persistence, and current production status not independently established.</data></node><node id="R149_E0001"><data key="node_entity_id">R149_E0001</data><data key="node_entity_type">identity_access_control</data><data key="node_canonical_name">MBR/SSR Field Office In-Person-Only Safety Special Message</data><data key="node_acronym" /><data key="node_domain">Person / Access / Address</data><data key="node_description">A field office alone can add an MBR or SSR special message to require face-to-face proof-of-identity contact when supported by HALE, fraudulent changes or alleged identity theft.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0002"><data key="node_entity_id">R149_E0002</data><data key="node_entity_type">document_evidence</data><data key="node_canonical_name">Signed Beneficiary In-Person-Only Contact Request</data><data key="node_acronym" /><data key="node_domain">Person / Evidentiary Document</data><data key="node_description">Field office must obtain signed documentation for in-person-only handling when the claimant requests such treatment; staff scan evidence into NDRed or eView as appropriate.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0003"><data key="node_entity_id">R149_E0003</data><data key="node_entity_type">information_disclosure_control</data><data key="node_canonical_name">Special-Message No Telephone Release or Address-of-Record Mailing Control</data><data key="node_acronym" /><data key="node_domain">Person / Privacy / Address</data><data key="node_description">For a qualifying in-person-only MBR/SSR marker, no personal information release by telephone, no mail to the address of record in response to telephone inquiry, and no record change based on telephone contact.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0004"><data key="node_entity_id">R149_E0004</data><data key="node_entity_type">policy_constraint</data><data key="node_canonical_name">MBR/SSR Special Message Cannot Serve as Customer Password</data><data key="node_acronym" /><data key="node_domain">Identity / Security</data><data key="node_description">SSA says customer-selected passwords, security phrases and security codes must no longer be placed in MBR or SSR special-message fields.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0005"><data key="node_entity_id">R149_E0005</data><data key="node_entity_type">policy_exception</data><data key="node_canonical_name">MBR/SSR In-Person-Only Marker Routine-Use and Online-Service Exclusions</data><data key="node_acronym" /><data key="node_domain">Person / Privacy</data><data key="node_description">Safety special-message instructions do not displace authorized routine-use third-party disclosures or separately authorized online/automated response password services.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0006"><data key="node_entity_id">R149_E0006</data><data key="node_entity_type">disclosure_process</data><data key="node_canonical_name">Pending-Hearing Evidentiary Record Access Procedure</data><data key="node_acronym" /><data key="node_domain">Hearings / Evidence / Privacy</data><data key="node_description">Claimants and appointed representatives may request evidence that will become part of the hearing record before or during proceedings.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0007"><data key="node_entity_id">R149_E0007</data><data key="node_entity_type">policy_constraint</data><data key="node_canonical_name">Pending-Hearing Requested-Documents-Only Disclosure Rule</data><data key="node_acronym" /><data key="node_domain">Hearings / Evidence</data><data key="node_description">When handling pending-hearing access requests, use requested material by photocopy or electronic folder copy on compact disc, and do not request the entire folder unless necessary.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0008"><data key="node_entity_id">R149_E0008</data><data key="node_entity_type">disclosure_data_product</data><data key="node_canonical_name">Hearing Audio Recording Duplicate on Compact Disc</data><data key="node_acronym" /><data key="node_domain">Hearings / Evidence / Disclosure</data><data key="node_description">SSA records hearings as audio and can provide a duplicate recording on compact disc to a claimant or authorized representative.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0009"><data key="node_entity_id">R149_E0009</data><data key="node_entity_type">policy_constraint</data><data key="node_canonical_name">ALJ-Need Hearing Transcript Production Rule</data><data key="node_acronym" /><data key="node_domain">Hearings / Evidence / Workflow</data><data key="node_description">SSA generally prepares a hearing transcript when an administrative law judge needs one for decision or dismissal; a transcript is not presumed to exist for every hearing.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0010"><data key="node_entity_id">R149_E0010</data><data key="node_entity_type">statistical_publication_series</data><data key="node_canonical_name">OACT Insured-Worker Disability and Death Probability Actuarial Notes 2016.6–2026.6</data><data key="node_acronym" /><data key="node_domain">OACT / Statistical Publications</data><data key="node_description">OACT publicly catalogs annual actuarial notes on insured-worker disability and death probabilities for 2016.6 through 2026.6 with author and publication dates.</data><data key="node_observed_status">historical published note series (2016–2026)</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0011"><data key="node_entity_id">R149_E0011</data><data key="node_entity_type">actuarial_publication</data><data key="node_canonical_name">OACT Actuarial Note 2026.6 Insured-Worker Disability and Death Probabilities</data><data key="node_acronym" /><data key="node_domain">OACT / Disability / Mortality</data><data key="node_description">July 2026 entry in OACT actuarial note series titled Disability and Death Probability Tables for Insured Workers; authored by Johanna Maleh, Brendan Yaw, and Tiffany Bosley.</data><data key="node_observed_status">published July 2026; index evidence only</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0012"><data key="node_entity_id">R149_E0012</data><data key="node_entity_type">publication_format_control</data><data key="node_canonical_name">OACT Actuarial Notes Historical Nonrevision and PDF Update Policy</data><data key="node_acronym" /><data key="node_domain">OACT / Publication Provenance</data><data key="node_description">SSA explains its actuarial notes are historical documents normally not revised and that current note updates are made in PDF only.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0013"><data key="node_entity_id">R149_E0013</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">SASRO State-Record Single-Query IEA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Person / States</data><data key="node_description">The SSA Access to State Records Online agreement allows an SSA single electronic query of defined state records for file updates, SSN assignment, and Title II/XVI eligibility/payment verification; scope varies by signed agreement.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0014"><data key="node_entity_id">R149_E0014</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">2018 Section 103A Foster-Care Placement and Representative-Payee IEA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Representative Payee</data><data key="node_description">State foster-care agencies report minors entering or exiting foster care or changing placements, supporting payee suitability and possible state liability for minors’ overpayments.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0015"><data key="node_entity_id">R149_E0015</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">State ABLE Account Statements and Balances IEA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / SSI / Resources</data><data key="node_description">State ABLE administrators disclose distributions and balances for SSI resource verification, subject to applicable IEA safeguards and program eligibility evaluation.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0016"><data key="node_entity_id">R149_E0016</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">HAVA Voter Last-Four-SSN State Verification IEA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Identity / States</data><data key="node_description">For qualifying voter registrations lacking a driver license, SSA verifies name, DOB and last four SSN digits for state MVA and returns a death indicator if applicable.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0017"><data key="node_entity_id">R149_E0017</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">Interstate Benefit Inquiry ICON Wage and Unemployment IEA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Earnings / States</data><data key="node_description">SSA makes a single electronic inquiry for wage and unemployment information held by state agencies through Interstate Connection Network, for program eligibility or payment development.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0018"><data key="node_entity_id">R149_E0018</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">Motor Vehicle Administration Overnight SSN-Verification IEA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Identity / States</data><data key="node_description">SSA provides overnight batch SSN verification to state motor vehicle agencies to support driver license and identity-card programs.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0019"><data key="node_entity_id">R149_E0019</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">SSOLV AAMVA Connectivity and Billing IEA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Identity / States</data><data key="node_description">AAMVA provides connectivity, billing and help-desk services to MVAs; SSA supplies SSN verification via AAMVA’s network under the SSOLV IEA class.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0020"><data key="node_entity_id">R149_E0020</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">State Transmission Component Data-Conduit IEA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / State Gateway</data><data key="node_description">The designated STC transmits only approved SSA data between SSA and recipient state agencies, but has no authority to change downstream state disclosures or uses.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0021"><data key="node_entity_id">R149_E0021</data><data key="node_entity_type">security_governance_control</data><data key="node_canonical_name">State Transmission Component Three-Year OIS Onsite Security Review</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Security Governance</data><data key="node_description">SSA policy requires Office of Information Security onsite security compliance reviews of a state transmission or transfer component every three years.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0022"><data key="node_entity_id">R149_E0022</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">IEA-F Federally Funded State-Administered Program Agreement Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / States / Governance</data><data key="node_description">IEA-F accompanies applicable state-level matching agreement and specifies the SSA data, authorized systems, delivery method and security terms for federally funded state-administered programs.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0023"><data key="node_entity_id">R149_E0023</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">IEA-S State-Funded State-Administered Program Agreement Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / States / Governance</data><data key="node_description">Stand-alone IEA-S covers state-funded state-administered benefits; financial terms for new data requests may instead require a reimbursable IEA.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0024"><data key="node_entity_id">R149_E0024</data><data key="node_entity_type">information_governance_control</data><data key="node_canonical_name">IEA-F and IEA-S 30-Month Certification of Compliance</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Governance</data><data key="node_description">SSA policy requires a Certification of Compliance document every 30 months for IEA-F and IEA-S; do not treat a template as an executed agreement.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0025"><data key="node_entity_id">R149_E0025</data><data key="node_entity_type">data_exchange_agreement_category</data><data key="node_canonical_name">SSA Research and Statistical Nonadverse-Benefit MOU/MOA Category</data><data key="node_acronym" /><data key="node_domain">Data Exchange / Research</data><data key="node_description">SSA generally uses MOUs or MOAs when sharing data for research or statistics or exchanges that do not directly adversely affect cash benefits and do not qualify as a matching program.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0026"><data key="node_entity_id">R149_E0026</data><data key="node_entity_type">grant_administration_process</data><data key="node_canonical_name">SSA Discretionary Grant External Expert Peer Review</data><data key="node_acronym" /><data key="node_domain">Procurement / Grants / Governance</data><data key="node_description">SSA uses expert peer reviews in evaluating competitive discretionary grant applications after an administrative completeness review.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0027"><data key="node_entity_id">R149_E0027</data><data key="node_entity_type">grant_administration_record</data><data key="node_canonical_name">SSA Grant Budget Detail Worksheet and Narrative Cost Analysis</data><data key="node_acronym" /><data key="node_domain">Procurement / Grants</data><data key="node_description">Grant application includes budget-detail calculations and narrative; SSA grants officer evaluates reasonableness, necessity, allowability and costs under 2 CFR 200.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R149_E0028"><data key="node_entity_id">R149_E0028</data><data key="node_entity_type">grant_administration_control</data><data key="node_canonical_name">SSA Continuation Grant Prior-Year SF-425 Review Control</data><data key="node_acronym" /><data key="node_domain">Procurement / Grants</data><data key="node_description">Before continuation award, grants officer checks prior-year program reports and Federal Financial Report SF-425 have been submitted.</data><data key="node_observed_status">documented policy / published product; current technical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Verified published SSA policy or product; data semantics not equivalent to physical repository, automatic master-record update, or active live integration.</data></node><node id="R150_E0001"><data key="node_entity_id">R150_E0001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Numident sex-code cross-record update requirement</data><data key="node_domain">identity/Numident</data><data key="node_description">When SSA updates a number holder sex-at-birth code in Numident, an employee must update matching MBR, SSR, RPS or other relevant records; instructions do not establish automated synchronization.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0002"><data key="node_entity_id">R150_E0002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Numident parent-name dependent benefit-record review</data><data key="node_domain">identity/Numident</data><data key="node_description">After correcting a parent name on a child Numident, ask whether the parent is a Title II beneficiary, SSI recipient or representative payee and review MBR, SSR or RPS for needed corrections.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0003"><data key="node_entity_id">R150_E0003</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Numident sex-at-birth correction evidence category</data><data key="node_domain">identity/Numident</data><data key="node_description">SSA requires supporting birth or nationality documents under RM 10212.200 before adjusting the Numident sex-at-birth field; a qualifying verified keying error instead follows SSNAP NCP.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0004"><data key="node_entity_id">R150_E0004</data><data key="node_entity_type">interface_data</data><data key="node_canonical_name">Extra Help IRS 1099-INT and 1099-DIV financial-income match</data><data key="node_domain">IRS/Part D</data><data key="node_description">IRS supplies interest, dividend and distribution amounts, not bank account balances, for Medicare Part D Extra Help resource comparison.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0005"><data key="node_entity_id">R150_E0005</data><data key="node_entity_type">derived_data_attribute</data><data key="node_canonical_name">Extra Help interest-derived estimated account balance</data><data key="node_domain">IRS/Part D</data><data key="node_description">Subsidy-determination process estimates financial-account balance using matched interest amount; estimate is agency comparison data rather than an observed bank balance.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0006"><data key="node_entity_id">R150_E0006</data><data key="node_entity_type">decision_control</data><data key="node_canonical_name">Extra Help 2026 financial resource verification thresholds</data><data key="node_domain">Medicare Part D</data><data key="node_description">Published 2026 resource comparison thresholds are $16,590 single and $33,100 married, subject to applicable burial-exclusion adjustment; crossing comparison tolerance selects a verification workflow.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0007"><data key="node_entity_id">R150_E0007</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Extra Help applicant-alleged liquid resources</data><data key="node_domain">Medicare Part D</data><data key="node_description">Application-reported financial resources are compared against agency-derived resource information; inconsistencies may warrant claimant contact and additional evidence.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0008"><data key="node_entity_id">R150_E0008</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MAPS liquid-resource discrepancy reconciliation</data><data key="node_domain">Medicare Part D</data><data key="node_description">Employee checks excluded amounts, asks claimant whether they agree with agency information, reviews account statements or other evidence where needed, and documents a resolution.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0009"><data key="node_entity_id">R150_E0009</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Medicare System Query source attribution for balances</data><data key="node_domain">Medicare Part D</data><data key="node_description">Medicare System Query identifies underlying agency-source information where MAPS summary bank-account and stock/bond fields do not disclose the original source.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0010"><data key="node_entity_id">R150_E0010</data><data key="node_entity_type">decision_control</data><data key="node_canonical_name">MAPS resolved and failure-to-cooperate decision submission</data><data key="node_domain">Medicare Part D</data><data key="node_description">For liquid-resource discrepancies employee records verified amounts and selects Resolved or Failure to Cooperate before submitting to subsidy determination.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0011"><data key="node_entity_id">R150_E0011</data><data key="node_entity_type">evidence_artifact</data><data key="node_canonical_name">CPAS submitter-maintained signing audit certificate</data><data key="node_domain">claims/e-signature</data><data key="node_description">Third-party submitter must be able to produce a digital certificate showing signer, signature date/time, associated email/IP addresses, document-modification status and audit-to-form identifier.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0012"><data key="node_entity_id">R150_E0012</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">CPAS audit certificate three-year submitter retention</data><data key="node_domain">claims/e-signature</data><data key="node_description">Submitter retains the unredacted CPAS digital audit certificate for at least three years after filing with SSA; agency staff are not required to validate vendor audit generation at intake.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0013"><data key="node_entity_id">R150_E0013</data><data key="node_entity_type">evidence_artifact</data><data key="node_canonical_name">CPAS appended per-form signature date-time certificate page</data><data key="node_domain">claims/e-signature</data><data key="node_description">Where required date and time are absent from individual form signature area, a contemporaneously appended certificate page is required for each affected form; a shared page for bundle is insufficient.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0014"><data key="node_entity_id">R150_E0014</data><data key="node_entity_type">decision_control</data><data key="node_canonical_name">CPAS original audit certificate fraud-referral evidentiary prerequisite</data><data key="node_domain">program integrity</data><data key="node_description">Before referring suspected fraudulent commercial product signatures, employees must request original submitter audit certificate as part of case development.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0015"><data key="node_entity_id">R150_E0015</data><data key="node_entity_type">workflow_exception</data><data key="node_canonical_name">RASR first-entry-only CPAS checkbox exception</data><data key="node_domain">representation</data><data key="node_description">When CPAS flag was not coded at creation of RASR appointment, it cannot be edited in RASR; employee annotates MCS DW01 as alternative.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0016"><data key="node_entity_id">R150_E0016</data><data key="node_entity_type">case_status_rule</data><data key="node_canonical_name">DCPS advisory medical assessment designation on DHU transfer</data><data key="node_domain">disability/hearings</data><data key="node_description">For pre-hearing cessation cases sent to DHU, DCPS marks relevant consultant medical assessments Advisory within DDE.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0017"><data key="node_entity_id">R150_E0017</data><data key="node_entity_type">workflow_exception</data><data key="node_canonical_name">eView notes-based advisory label for immutable assessment</data><data key="node_domain">disability/hearings</data><data key="node_description">If medical assessment is already imaged in CEF and cannot be altered, employee adds Advisory to eView document detail Notes field instead of changing the scanned evidence.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0018"><data key="node_entity_id">R150_E0018</data><data key="node_entity_type">evidence_product</data><data key="node_canonical_name">SSA-887 Summary of Evidence chronological CPD separation</data><data key="node_domain">disability/hearings</data><data key="node_description">SSA-887 presents post-Comparison Point Decision medical/vocational evidence in Section A and evidence at CPD in Section B; age-18 redetermination omits CPD evidence.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0019"><data key="node_entity_id">R150_E0019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS less-than-fully-favorable pre-hearing DHU referral</data><data key="node_domain">disability/hearings</data><data key="node_description">Pre-hearing cessation cannot issue less-than-fully-favorable result; DDS transfers to Disability Hearing Unit with case control update and SSA-408 for paper folder.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0020"><data key="node_entity_id">R150_E0020</data><data key="node_entity_type">cross_case_alert</data><data key="node_canonical_name">Compassionate Allowances same-SSN Appeals Council case notification</data><data key="node_domain">disability/appeals</data><data key="node_description">When a new EDCS-transferred DDS case is CAL-selected or CAL-removed while earlier case pending at Appeals Council, eView sends AC message identifying related SSN and CAL status.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0021"><data key="node_entity_id">R150_E0021</data><data key="node_entity_type">work_priority_rule</data><data key="node_canonical_name">Compassionate Allowances priority across adjudication levels after denial</data><data key="node_domain">disability/appeals</data><data key="node_description">Previously CAL-classified disability case retains fast-track priority through appeals even when denied; eView header CAL:Y or MCS/CCE issue evidences past CAL handling.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0022"><data key="node_entity_id">R150_E0022</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">CAL post-transfer field-office 20-day initial-claim tickle</data><data key="node_domain">disability</data><data key="node_description">When CAL condition is identified after DDS transfer, FO marks MCS DW01 or CCE development worksheet with 20-day follow-up for initial claims; appeal cases do not need this tickle.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0023"><data key="node_entity_id">R150_E0023</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">WC/PDB offset proof permanent evidence retention</data><data key="node_domain">payments/disability</data><data key="node_description">Workers compensation and public disability benefit proof must be permanently retained; EVID summarized verification alone does not satisfy permanent proof preservation.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0024"><data key="node_entity_id">R150_E0024</data><data key="node_entity_type">document_routing</data><data key="node_canonical_name">WC/PDB concurrent eFolder and PC Paperless copy requirement</data><data key="node_domain">payments/disability</data><data key="node_description">For electronic claims copy or fax relevant WC/PDB proof into electronic claims folder; when PC action is required also transmit into Processing Center Paperless for access.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0025"><data key="node_entity_id">R150_E0025</data><data key="node_entity_type">access_control</data><data key="node_canonical_name">WC/PDB Paperless Processing Center field-office access limitation</data><data key="node_domain">infrastructure/workflow</data><data key="node_description">Field offices cannot view WC/PDB proof stored exclusively in processing-center Paperless, requiring separate electronic-folder availability for FO use.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0026"><data key="node_entity_id">R150_E0026</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Appeals Council UAT two-day verification and five-day escalation</data><data key="node_domain">hearings/appeals</data><data key="node_description">After sending the AC additional-evidence UAT notification, staff check for response after two business days and escalate if no response within five workdays according to instructions.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0027"><data key="node_entity_id">R150_E0027</data><data key="node_entity_type">decision_control</data><data key="node_canonical_name">Appeals Council post-hearing evidence protective-filing review</data><data key="node_domain">hearings/appeals</data><data key="node_description">Evidence submitted after a hearing may relate to potential subsequent-claim protective filing rather than evidence allowable into current appeal; employee must evaluate policy before disposition.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0028"><data key="node_entity_id">R150_E0028</data><data key="node_entity_type">online_service_rule</data><data key="node_canonical_name">e1696 electronic appointment portal attachment exclusion</data><data key="node_domain">representation</data><data key="node_description">SSA electronic SSA-1696 completion channel does not allow other documents to be uploaded as attachments with the e1696 transaction.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0029"><data key="node_entity_id">R150_E0029</data><data key="node_entity_type">process_separation</data><data key="node_canonical_name">RASR representative appointment versus fee-assignment independent outcome</data><data key="node_domain">representation</data><data key="node_description">A representative appointment may be properly recorded in RASR even when the separate fee-assignment request in same transaction is invalid or requires additional development.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0030"><data key="node_entity_id">R150_E0030</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">SSA vendor capability submissions approximately one-year retention</data><data key="node_domain">procurement</data><data key="node_description">SSA Office of Acquisition and Grants Vendor Repository states submitted capability statements are retained approximately one year and then removed; interested vendors must submit refreshed information.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R150_E0031"><data key="node_entity_id">R150_E0031</data><data key="node_entity_type">document_routing</data><data key="node_canonical_name">Representative communication electronic-versus-paper copy routing</data><data key="node_domain">representation</data><data key="node_description">Representative correspondence copy appears in electronic case retrieval for electronic claims; paper custody cases require directed copy and possible Evidence Portal route to component maintaining folder.</data><data key="node_observed_status">Documented policy or workflow; physical implementation not inferred</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R151_E001"><data key="node_entity_id">R151_E001</data><data key="node_entity_type">identity_update_workflow</data><data key="node_canonical_name">Deceased Numberholder Numident Correction Request</data><data key="node_domain">Person/Identity</data><data key="node_description">For claims purposes, an authorized requester may seek changes to name, date of birth, or citizenship/alien status on a deceased numberholder Numident, following specified evidence review.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E002"><data key="node_entity_id">R151_E002</data><data key="node_entity_type">identity_proofing_requirement</data><data key="node_canonical_name">Deceased Numberholder Requester Identity and Relationship Evidence</data><data key="node_domain">Person/Identity</data><data key="node_description">Employees verify the identity of the person seeking correction and evidence of their relationship with the deceased numberholder.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E003"><data key="node_entity_id">R151_E003</data><data key="node_entity_type">enumeration_workflow_control</data><data key="node_canonical_name">Deceased Numberholder SSNAP Card Issuance Suppression</data><data key="node_domain">Person/Identity</data><data key="node_description">SSNAP Additional Info screen requires suppress card issuance during Numident correction for deceased numberholder.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E004"><data key="node_entity_id">R151_E004</data><data key="node_entity_type">death_update_workflow</data><data key="node_canonical_name">Deceased Numberholder Missing Death Record DIPS Entry</data><data key="node_domain">Person/Identity</data><data key="node_description">Where death not shown on Numident, field office obtains certificate and adds death through DIPS after applicable Numident correction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E005"><data key="node_entity_id">R151_E005</data><data key="node_entity_type">state_government_organization</data><data key="node_canonical_name">Washington State Department of Labor and Industries</data><data key="node_domain">External exchanges</data><data key="node_description">Washington WC payer and recipient of SSA entitlement/offset data sheets under DI 52120.265.</data><data key="node_observed_status">documented_active_partner</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E006"><data key="node_entity_id">R151_E006</data><data key="node_entity_type">form</data><data key="node_canonical_name">Form SSA-1709 Request for Workers Compensation or Public Disability Benefit Information</data><data key="node_domain">Disability/Payments</data><data key="node_description">State WC/PDB evidence form; amended state returns may require recalculation of SSA WC offset; form alone does not provide legal fees.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E007"><data key="node_entity_id">R151_E007</data><data key="node_entity_type">state_notification_form</data><data key="node_canonical_name">Washington Workers Compensation Social Security Benefit Notification and Data Form</data><data key="node_domain">External exchanges</data><data key="node_description">SSA sends state WC data sheet by fax or mail after adjudication and when offset is reimposed; retains copy in appropriate evidence repository.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E008"><data key="node_entity_id">R151_E008</data><data key="node_entity_type">benefit_offset_process</data><data key="node_canonical_name">Washington WC Reverse Jurisdiction Offset Processing</data><data key="node_domain">Disability/Payments</data><data key="node_description">Conditional Title II WC reverse-jurisdiction rule ties state offset and SSA offset to month of SSA adjudication, with age-62 control.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E009"><data key="node_entity_id">R151_E009</data><data key="node_entity_type">claims_system_screen</data><data key="node_canonical_name">MCS WPCL Common Workers Compensation or Public Disability Claim Data Screen</data><data key="node_domain">Disability/Payments</data><data key="node_description">MCS screen for reverse-jurisdiction indicator and start date; temporary input is revised after adjudication for WA reverse-offset cases.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E010"><data key="node_entity_id">R151_E010</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Washington Reverse Offset Age-62 042 Diary Control</data><data key="node_domain">Disability/Payments</data><data key="node_description">SSA establishes a 042 diary with due date four months before the numberholder turns 62 to revisit offset.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E011"><data key="node_entity_id">R151_E011</data><data key="node_entity_type">claims_processing_limit</data><data key="node_canonical_name">Washington WC MCS Auto-Initiate Exclusion</data><data key="node_domain">Disability/Payments</data><data key="node_description">SSA instructs employees not to enter nonmedical completion or auto-initiate for MCS Washington periodic reverse-offset processing cases.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E012"><data key="node_entity_id">R151_E012</data><data key="node_entity_type">claims_processing_workflow</data><data key="node_canonical_name">Washington WC ICF WCCD Manual Processing Alternative</data><data key="node_domain">Disability/Payments</data><data key="node_description">When MCS limits processing of WA WC/PDB, employee enters conditional reverse-jurisdiction information using ICF WCCD screen.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E013"><data key="node_entity_id">R151_E013</data><data key="node_entity_type">evidence_correction_workflow</data><data key="node_canonical_name">Washington WC Reopened Award Amended SSA-1709 Review</data><data key="node_domain">Disability/Payments</data><data key="node_description">Washington L&amp;I can send amended SSA-1709 after reopening/revision; employees must rework SSA offset using corrected information.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E014"><data key="node_entity_id">R151_E014</data><data key="node_entity_type">historical_batch_process</data><data key="node_canonical_name">Historical Weekly PEBES-IRS IMF Address Matching</data><data key="node_domain">Address Provenance and IRS</data><data key="node_description">2015-revised POMS describes name/SSN weekly IRS IMF address request after matching Puerto Rico and Virgin Islands tax agency address files; one-week turnaround in that historical procedure.</data><data key="node_observed_status">historical_as_of_2015</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2015 revised policy; September 2026 website batch does not establish unchanged current weekly implementation. Mailing-use only; no master-record address update inferred.</data></node><node id="R151_E015"><data key="node_entity_id">R151_E015</data><data key="node_entity_type">historical_batch_response</data><data key="node_canonical_name">Historical PEBES IRS Address No-Match Response</data><data key="node_domain">Address Provenance and IRS</data><data key="node_description">2015-revised POMS reported about 15% of weekly IMF Statement address lookups returned no match.</data><data key="node_observed_status">historical_as_of_2015</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Historical percentage, not a current operational rate. No-match does not establish absence of other SSA address information.</data></node><node id="R151_E016"><data key="node_entity_id">R151_E016</data><data key="node_entity_type">address_quality_constraint</data><data key="node_canonical_name">Historical IRS IMF Batch Versus IRS Inquiry Address Difference</data><data key="node_domain">Address Provenance and IRS</data><data key="node_description">2015-revised POMS warns addresses available to IRS direct-contact online users may differ from IMF addresses delivered to SSA through the batch process.</data><data key="node_observed_status">historical_as_of_2015</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Historical system behavior only; not a claim about present IRS synchronization or an SSA master-record write.</data></node><node id="R151_E017"><data key="node_entity_id">R151_E017</data><data key="node_entity_type">published_statistical_table</data><data key="node_canonical_name">2026 Statistical Supplement Table 7.D1 SSI Recipients by Other Income Source</data><data key="node_domain">Actuarial/Statistical products</data><data key="node_description">December 2025 full-population SSR count and average monthly earned/unearned income by SSI eligibility category and age.</data><data key="node_observed_status">published_2026_sectional</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E018"><data key="node_entity_id">R151_E018</data><data key="node_entity_type">published_statistical_table</data><data key="node_canonical_name">2026 Statistical Supplement Table 7.D2 SSI Social Security Benefits by State and Age</data><data key="node_domain">Actuarial/Statistical products</data><data key="node_description">December 2025 table by state/other area, eligibility category and age: percentage with Social Security income and average Social Security amount.</data><data key="node_observed_status">published_2026_sectional</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E019"><data key="node_entity_id">R151_E019</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">2026 SSI Other-Income Table Full-Population SSR Denominator</data><data key="node_domain">Actuarial/Statistical products</data><data key="node_description">Tables 7.D1/7.D2 derive from 100 percent Supplemental Security Record for December 2025, not sampled estimates, with specified SSI eligibility/age categories.</data><data key="node_observed_status">documented_publication_rule</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E020"><data key="node_entity_id">R151_E020</data><data key="node_entity_type">notice_template</data><data key="node_canonical_name">WAV001 Waiver Rights Notice Paragraph</data><data key="node_domain">Payments/Debt</data><data key="node_description">System-generated initial overpayment notice text advises about waiver process, personal conference, appeal, and timing protections.</data><data key="node_observed_status">documented_2026_notice</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R151_E021"><data key="node_entity_id">R151_E021</data><data key="node_entity_type">public_submission_process</data><data key="node_canonical_name">2026 Waiver Request Multichannel SSA-632 Submission Instructions</data><data key="node_domain">Forms/Digital intake</data><data key="node_description">System-generated WAV001 directs over-$2,000 waiver requests to SSA-632 via online route and suggests Upload Documents, mail, or field office delivery; $2,000 or less directs telephone contact.</data><data key="node_observed_status">documented_2026_notice</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">2026-10-09 observed; only attributes established by cited source; no inferred implementation technology or persistence.</data></node><node id="R152_E001"><data key="node_entity_id">R152_E001</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Numident Date-of-Birth Field</data><data key="node_acronym">DOB</data><data key="node_domain">Identity / Person</data><data key="node_description">Date of birth on Numident can differ from DOB previously established for benefit payment, subject to proof and record-specific correction rules.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E002"><data key="node_entity_id">R152_E002</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">MBR Date-of-Birth Proof Code</data><data key="node_acronym">MBR DOB proof</data><data key="node_domain">Title II / Identity</data><data key="node_description">MBR proof categories A/B/C/F/P/Q or no code affect when its DOB can serve as evidence for a Numident change.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E003"><data key="node_entity_id">R152_E003</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSR Date-of-Birth Proof Code</data><data key="node_acronym">SSR DOB proof</data><data key="node_domain">Title XVI / Identity</data><data key="node_description">SSR DOB proof categories B/C/E/F/Q or no code have conditional rules for whether SSA can adopt record age evidence.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E004"><data key="node_entity_id">R152_E004</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Numident DOB Correction Using Benefit-Record Age Proof</data><data key="node_acronym">Age proof reuse</data><data key="node_domain">Identity / Governance</data><data key="node_description">Employees may accept certain MBR/SSR proof codes to correct Numident without additional age evidence, only under category and entitlement conditions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E005"><data key="node_entity_id">R152_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Benefit-Record Date-of-Birth Administrative Finality Restriction</data><data key="node_acronym">Finality</data><data key="node_domain">Identity / Benefits</data><data key="node_description">Even after supported Numident correction, SSA may be prohibited from revising an established MBR or SSR payment determination by administrative-finality rules.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E006"><data key="node_entity_id">R152_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Numident DOB State Vital-Record Collateral Verification</data><data key="node_acronym">BVS age</data><data key="node_domain">Identity / External Exchanges</data><data key="node_description">Employees may verify birth records with state vital statistics; evidence requirements differ for primary and alternative birth evidence.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E007"><data key="node_entity_id">R152_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Numident DOB Keying-Error Evidence Comparison</data><data key="node_acronym">DOB key error</data><data key="node_domain">Identity / Enumeration</data><data key="node_description">Employees compare paper SS-5 or microprint DOB with Numident to identify true keying errors before NCP correction.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E008"><data key="node_entity_id">R152_E008</data><data key="node_entity_type">record</data><data key="node_canonical_name">SS-5 Archived Birthdate Application Evidence</data><data key="node_acronym">SS-5 DOB archive</data><data key="node_domain">Identity / Evidence</data><data key="node_description">Original SS-5 records/microprints accessed for DOB comparison; documentation mentions IRON and SS-5 Reprints links in SSNAP.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E009"><data key="node_entity_id">R152_E009</data><data key="node_entity_type">application_screen</data><data key="node_canonical_name">SSNAP Proof of Age Screen</data><data key="node_acronym">SSNAP POA</data><data key="node_domain">Identity / Enumeration</data><data key="node_description">SSNAP records evidence verification and whether the state Bureau of Vital Statistics confirmed that no birth certificate exists.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S001. </data></node><node id="R152_E010"><data key="node_entity_id">R152_E010</data><data key="node_entity_type">form_platform</data><data key="node_canonical_name">SSA inForms Form-Access Environment</data><data key="node_acronym">inForms</data><data key="node_domain">Customer Forms / Operations</data><data key="node_description">SSA EM-25054 states the revised SSA-821-BK is accessible in inForms; no hosting or storage architecture supplied.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S002. </data></node><node id="R152_E011"><data key="node_entity_id">R152_E011</data><data key="node_entity_type">modernization_workflow</data><data key="node_canonical_name">2025 SSA-821-BK Work Activity Report Redesign</data><data key="node_acronym">821 modernization</data><data key="node_domain">Disability / Forms</data><data key="node_description">2025 EM streamlined work reports, clarified work incentives, removed certain wage-guess tables, and improved Upload Documents compatibility.</data><data key="node_observed_status">implemented_form_revision_2025</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S002. </data></node><node id="R152_E012"><data key="node_entity_id">R152_E012</data><data key="node_entity_type">form_field_change</data><data key="node_canonical_name">SSA-821-BK Prefilled IRS Earnings Table Removal</data><data key="node_acronym">IRS Table</data><data key="node_domain">Earnings / Source Provenance</data><data key="node_description">The revised form removed the former prefilled IRS earnings table in favor of more recent wage information where available.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S002. </data></node><node id="R152_E013"><data key="node_entity_id">R152_E013</data><data key="node_entity_type">form_field_change</data><data key="node_canonical_name">SSA-821-BK Pay Stub Received Indicator</data><data key="node_acronym">Stub receipt flag</data><data key="node_domain">Disability / Evidence</data><data key="node_description">New SSA-821-BK replaces recurring pay-stub tables with an indication that pay stubs were supplied.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S002. </data></node><node id="R152_E014"><data key="node_entity_id">R152_E014</data><data key="node_entity_type">form_field_change</data><data key="node_canonical_name">SSA-821-BK Reason Work Ended Field</data><data key="node_acronym">UWA</data><data key="node_domain">Disability / Work Incentives</data><data key="node_description">Revised form explicitly captures whether employment ended due to disability or another reason, supporting unsuccessful-work-attempt review.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S002. </data></node><node id="R152_E015"><data key="node_entity_id">R152_E015</data><data key="node_entity_type">form_field_change</data><data key="node_canonical_name">SSA-821-BK Work Accommodation and Knowledgeable Source Fields</data><data key="node_acronym">Accommodations</data><data key="node_domain">Disability / Work Incentives</data><data key="node_description">Revised form asks about subsidies, special conditions and people other than employers who may know about workplace accommodations.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S002. </data></node><node id="R152_E016"><data key="node_entity_id">R152_E016</data><data key="node_entity_type">modernization_workflow</data><data key="node_canonical_name">2026 SSA-820-BK Self-Employment Work Report Redesign</data><data key="node_acronym">820 modernization</data><data key="node_domain">Disability / Forms</data><data key="node_description">Revised SSA-820 asks about gig work, anticipated self-employment earnings, and work incentives with improved Upload Documents compatibility.</data><data key="node_observed_status">implemented_form_revision_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S003. </data></node><node id="R152_E017"><data key="node_entity_id">R152_E017</data><data key="node_entity_type">form_field_change</data><data key="node_canonical_name">SSA-820-BK Gig Work Activity Categories</data><data key="node_acronym">Gig work</data><data key="node_domain">Earnings / Work Activity</data><data key="node_description">2026 report recognizes rideshare services, food delivery, and internet content creators as examples of self-employment.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S003. </data></node><node id="R152_E018"><data key="node_entity_id">R152_E018</data><data key="node_entity_type">form_field_change</data><data key="node_canonical_name">SSA-820-BK Expected Self-Employment Income Estimate</data><data key="node_acronym">Future income</data><data key="node_domain">Earnings / Work Activity</data><data key="node_description">2026 self-employment report removes detailed monthly earnings table and includes expected income estimates.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: R152_S003. </data></node><node id="R152_E019"><data key="node_entity_id">R152_E019</data><data key="node_entity_type">application_screen</data><data key="node_canonical_name">eWork Work Review Summary Screen</data><data key="node_acronym">Work Review Summary</data><data key="node_domain">Disability / Earnings</data><data key="node_description">POMS indicates eWork adds employer to this screen when PIE payroll data carry an EIN not already recorded for that beneficiary.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E020"><data key="node_entity_id">R152_E020</data><data key="node_entity_type">application_component</data><data key="node_canonical_name">eWork Pay Stub Table</data><data key="node_acronym">Pay Stub table</data><data key="node_domain">Disability / Earnings</data><data key="node_description">eWork displays PDP wages from PIE and other verified wage data with source attribution.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E021"><data key="node_entity_id">R152_E021</data><data key="node_entity_type">application_screen</data><data key="node_canonical_name">eWork Earnings Details Screen</data><data key="node_acronym">Earnings Detail</data><data key="node_domain">Disability / Earnings</data><data key="node_description">Screen displays monthly earnings and verified-by source codes for use in work continuing disability reviews.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E022"><data key="node_entity_id">R152_E022</data><data key="node_entity_type">exception_workflow</data><data key="node_canonical_name">eWork Payroll-Employer EIN Mismatch Handling</data><data key="node_acronym">EIN reconciliation</data><data key="node_domain">Disability / Earnings</data><data key="node_description">When new PDP wages have employer EIN absent from existing eWork case records, eWork adds employer to review summary.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E023"><data key="node_entity_id">R152_E023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eWork Duplicative Wage Source Priority Order</data><data key="node_acronym">Source order</data><data key="node_domain">Earnings / Governance</data><data key="node_description">For same-employer same-period conflicting wage lines, POMS prioritizes PDP, SSA employee, myWageReport, then employment-network data.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E024"><data key="node_entity_id">R152_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Disability Wage Earned-Month Versus Paid-Month Reconciliation</data><data key="node_acronym">Paid versus earned</data><data key="node_domain">Disability / Earnings</data><data key="node_description">Work determinations prioritize when earnings are earned, with paid-month presumption when actual earning period cannot be established.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E025"><data key="node_entity_id">R152_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Post-Entitlement Work CDR Earnings Verification Priority</data><data key="node_acronym">Post-entitlement verification</data><data key="node_domain">Disability / Work</data><data key="node_description">POMS provides source-priority rules for earnings evidence in post-entitlement work CDR determinations.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E026"><data key="node_entity_id">R152_E026</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Initial Disability Claim Earnings Verification Priority</data><data key="node_acronym">Initial claim verification</data><data key="node_domain">Disability / Initial Claim</data><data key="node_description">POMS identifies separate source priorities for disability onset and expedited reinstatement evaluation.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E027"><data key="node_entity_id">R152_E027</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Ticket Operations Support System</data><data key="node_acronym">iTOPSS</data><data key="node_domain">Disability / Work</data><data key="node_description">POMS states iTOPSS contains pay-stub wage data for Ticket to Work beneficiaries accessible through EDCS Consolidated Wage Page.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E028"><data key="node_entity_id">R152_E028</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L725 Request for Employment Information</data><data key="node_acronym">SSA-L725</data><data key="node_domain">Disability / Earnings</data><data key="node_description">Employer earnings verification request treated as last resort for post-entitlement work activity and as specified initial-claim evidence path.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E029"><data key="node_entity_id">R152_E029</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">SSA-L725 Employer Earnings Inquiry Follow-Up Diary</data><data key="node_acronym">Wage employer diary</data><data key="node_domain">Disability / Workload</data><data key="node_description">SSA POMS identifies 15-day field office and 35-day processing center controls for the employer request in specified cases.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC160. </data></node><node id="R152_E030"><data key="node_entity_id">R152_E030</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">CWHS Self-Employment Schedule SE Residence Address</data><data key="node_acronym">Schedule SE address</data><data key="node_domain">Address Provenance / Statistics</data><data key="node_description">For 2023 county worker tabulation, worker geographic assignment first uses address associated with self-employment earnings reporting.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC_R66_005. </data></node><node id="R152_E031"><data key="node_entity_id">R152_E031</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">CWHS Highest-Medicare-Earnings W-2 Residence Address</data><data key="node_acronym">W-2 address</data><data key="node_domain">Address Provenance / Statistics</data><data key="node_description">For workers without Schedule SE, location uses address from wage report with highest Medicare taxable earnings.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC_R66_005. </data></node><node id="R152_E032"><data key="node_entity_id">R152_E032</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">CWHS Statistical One-Location Residence Assignment</data><data key="node_acronym">Residence assignment</data><data key="node_domain">Address Provenance / Statistics</data><data key="node_description">Worker reported in several states/counties is allocated to one area, primarily year-end residence; self-employment address precedes W-2 chosen by highest Medicare wages.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC_R66_005. </data></node><node id="R152_E033"><data key="node_entity_id">R152_E033</data><data key="node_entity_type">statistical_category</data><data key="node_canonical_name">CWHS Unknown County Residence Category</data><data key="node_acronym">Unknown County</data><data key="node_domain">Statistics / Data Quality</data><data key="node_description">When state is known but county code is unavailable, published tables use Unknown county within state.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC_R66_005. </data></node><node id="R152_E034"><data key="node_entity_id">R152_E034</data><data key="node_entity_type">statistical_control</data><data key="node_canonical_name">CWHS County Small-Cell Disclosure Suppression</data><data key="node_acronym">Disclosure suppression</data><data key="node_domain">Statistics / Privacy</data><data key="node_description">Small values in 2023 earnings and worker tables may be suppressed; state aggregates include suppressed county totals.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC_R66_005. </data></node><node id="R152_E035"><data key="node_entity_id">R152_E035</data><data key="node_entity_type">statistical_limitation</data><data key="node_canonical_name">CWHS One-Percent Worker Sample Geographic Uncertainty</data><data key="node_acronym">Sampling uncertainty</data><data key="node_domain">Statistics / Research</data><data key="node_description">Published 2023 geographic earnings counts are extrapolations from one-percent Continuous Work History Sample with more uncertainty for small cells.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC_R66_005. </data></node><node id="R152_E036"><data key="node_entity_id">R152_E036</data><data key="node_entity_type">statistical_limitation</data><data key="node_canonical_name">SSI Administrative Data Noncountable Program Participation Gap</data><data key="node_acronym">SSI Outside Programs</data><data key="node_domain">Title XVI / Statistics</data><data key="node_description">SSA states SSR does not contain complete information on noncountable external public-assistance program participation.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC_R123_001. </data></node><node id="R152_E037"><data key="node_entity_id">R152_E037</data><data key="node_entity_type">exception_workflow</data><data key="node_canonical_name">EVVE Vital-Records Death-Status Conflict Investigation</data><data key="node_acronym">EVVE death discrepancy</data><data key="node_domain">Identity / Program Integrity</data><data key="node_description">EVVE possible-death indication requires record/identity review before death-data or fraud action where SSA identity records disagree.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC401. </data></node><node id="R152_E038"><data key="node_entity_id">R152_E038</data><data key="node_entity_type">data_quality_alert</data><data key="node_canonical_name">EVVE Modified Birth-Record Alert</data><data key="node_acronym">Amended birth source</data><data key="node_domain">Identity / Provenance</data><data key="node_description">EVVE may return indicator that birth-record information was modified, without specifying which attributes changed.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC401. </data></node><node id="R152_E039"><data key="node_entity_id">R152_E039</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">IRS Form 3857 Taxpayer Contact Initial 30-Workday Diary</data><data key="node_acronym">3857 30-day</data><data key="node_domain">IRS / Program Integrity</data><data key="node_description">Form 3857 direct-contact earnings identity investigation carries an initial 30-workday diary after taxpayer, employer and USPS contact.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC137. </data></node><node id="R152_E040"><data key="node_entity_id">R152_E040</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">IRS Form 3857 Taxpayer Contact Additional 15-Workday Diary</data><data key="node_acronym">3857 15-day</data><data key="node_domain">IRS / Program Integrity</data><data key="node_description">Nonresponsive 3857 case triggers further taxpayer/employer/post-office contact with additional 15-workday diary.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC137. </data></node><node id="R152_E041"><data key="node_entity_id">R152_E041</data><data key="node_entity_type">application_screen</data><data key="node_canonical_name">Item Correction ERMK Remarks Screen</data><data key="node_acronym">ERMK</data><data key="node_domain">Earnings / Audit</data><data key="node_description">SSA technicians annotate Form 3857 taxpayer/employer and post office contact actions on the ICOR ERMK screen.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source: SRC137. </data></node><node id="R153_E001"><data key="node_entity_id">R153_E001</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Medicare Premium Collection Center Lockbox</data><data key="node_acronym">MPCC</data><data key="node_domain">Medicare / Collections</data><data key="node_description">CMS-controlled Medicare premium collection destination in St. Louis; regular monthly or quarterly Part B payments and qualifying mixed remittances go here rather than the Mid-Atlantic PSC.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E002"><data key="node_entity_id">R153_E002</data><data key="node_entity_type">application</data><data key="node_canonical_name">Medicare Premium Direct Billing System</data><data key="node_acronym">DBS</data><data key="node_domain">Medicare / Billing</data><data key="node_description">Medicare premium direct billing system referenced by SSA; when normal electronic premium bills cannot be prepared, PSC may manually issue CMS-500. SSA POMS does not establish its database technology or operator.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001. Do not assume this is an SSA-hosted system.</data></node><node id="R153_E003"><data key="node_entity_id">R153_E003</data><data key="node_entity_type">form</data><data key="node_canonical_name">CMS-500 Medicare Premium Bill</data><data key="node_acronym">CMS-500</data><data key="node_domain">Medicare / Payment</data><data key="node_description">CMS premium bill and payment coupon used to identify beneficiary Medicare number and direct payments to MPCC; a PSC can prepare a manual bill when electronic billing is unavailable.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E004"><data key="node_entity_id">R153_E004</data><data key="node_entity_type">form</data><data key="node_canonical_name">CMS-500A Spanish Medicare Premium Bill</data><data key="node_acronym">CMS-500A</data><data key="node_domain">Medicare / Payment</data><data key="node_description">SSA POMS identifies a Spanish-language version of the CMS-500 premium bill.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E005"><data key="node_entity_id">R153_E005</data><data key="node_entity_type">application</data><data key="node_canonical_name">eFOR Field Office Remittance Application</data><data key="node_acronym">eFOR</data><data key="node_domain">Debt / Medicare / Receipts</data><data key="node_description">Current POMS identifies eFOR as an alternative application for entering and receipting field-office Medicare remittances using designated trust-fund and reason codes. No persistence implementation or hosting inferred.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E006"><data key="node_entity_id">R153_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Field Office Regular Medicare Premium Remittance Routing</data><data key="node_domain">Medicare / Collections</data><data key="node_description">Regular CMS-controlled premiums paid at an SSA field office are receipted and routed with CMS-500 to MPCC rather than MATPSC; transactions appear on the FODRL.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E007"><data key="node_entity_id">R153_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Field Office Retroactive Medicare Premium Routing</data><data key="node_domain">Medicare / Collections</data><data key="node_description">Retroactive Medicare premium installments or lump-sum payments follow designated MATPSC/PSC handling; regular premiums follow CMS lockbox routing, subject to 2026 procedures and historical FORT inconsistency.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E008"><data key="node_entity_id">R153_E008</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Medicare Premium Lockbox DMS Code N-H</data><data key="node_acronym">N/H</data><data key="node_domain">Medicare / Accounting</data><data key="node_description">Code combination: trust-fund N (not applicable) plus reason H (CMS lockbox premium), recorded through DMS or eFOR for ordinary Medicare remittances.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E009"><data key="node_entity_id">R153_E009</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Retroactive Medicare Premium DMS Code O-P</data><data key="node_acronym">O/P</data><data key="node_domain">Medicare / Accounting</data><data key="node_description">Code combination: trust-fund O (other) plus reason P (premium installments), recorded through DMS or eFOR for specified retroactive premium remittances.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E010"><data key="node_entity_id">R153_E010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Medicare Mixed Retroactive and Regular Premium Remittance Exception</data><data key="node_domain">Medicare / Collections</data><data key="node_description">For a single remittance covering lump-sum retroactive and regular monthly Medicare premiums, route full payment to MPCC and notify PSC.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E011"><data key="node_entity_id">R153_E011</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Medicare Premium Remittance Preaward Rejection Rule</data><data key="node_domain">Medicare / Collections</data><data key="node_description">SSA offices should not accept premium before HI/SMI award is prepared because MPCC cannot accept payments before beneficiary record exists.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E012"><data key="node_entity_id">R153_E012</data><data key="node_entity_type">control_risk</data><data key="node_canonical_name">Medicare Premium Incorrect Trust Fund Deposit IPAC Delay Risk</data><data key="node_domain">Medicare / Accounting</data><data key="node_description">2026 SSA instructions caution that incorrectly depositing Medicare premium money into Social Security Trust Funds can trigger IPAC processing and materially delay crediting; not evidence of an intentional SSA-to-IPAC integration.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E013"><data key="node_entity_id">R153_E013</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DMS Field Office Remittance Forwarding Instruction Sheet</data><data key="node_domain">Debt / Accounting</data><data key="node_description">DMS generates forwarding instructions to indicate destination for Medicare and other nonstandard field-office money items.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E014"><data key="node_entity_id">R153_E014</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Medicare Premium Field Office Card Payment Restriction</data><data key="node_domain">Medicare / Collections</data><data key="node_description">SSA POMS GN 02403.030 says credit-card premiums cannot be accepted by SSA field office or by phone; this does not prohibit other payment types/programs from using separate card procedures.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S001.</data></node><node id="R153_E015"><data key="node_entity_id">R153_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">State BVS Electronic SSN Verification Before Death Report</data><data key="node_domain">Identity / External Exchanges</data><data key="node_description">SSA electronically verifies SSNs submitted by participating state BVS agencies prior to the state transmitting a death report linked to a verified number, under applicable SSA-state agreements.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S003.</data></node><node id="R153_E016"><data key="node_entity_id">R153_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">State BVS Verified-SSN Death Report Return Path</data><data key="node_domain">Identity / Death Data</data><data key="node_description">After state BVS receives SSA SSN verification, the agency returns a state EDR death report connected with the verified SSN; governing POMS describes prompt death-related benefit action.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S003.</data></node><node id="R153_E017"><data key="node_entity_id">R153_E017</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">State Vital Statistics Record Disclosure for Age and Marital Evidence</data><data key="node_domain">Identity / Privacy</data><data key="node_description">SSA may disclose appropriate SSA records to state BVS without individual consent under applicable SORN routine uses to obtain age or marital status evidence for enumeration or benefits.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S003.</data></node><node id="R153_E018"><data key="node_entity_id">R153_E018</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA FY2020–FY2024 Annual IT Acquisition Obligation Finding</data><data key="node_domain">Procurement / Oversight</data><data key="node_description">GAO analysis found SSA annually obligated at least $1.4 billion on IT acquisitions in each FY2020 through FY2024; figures are acquisitions, not verified system deployment.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S002.</data></node><node id="R153_E019"><data key="node_entity_id">R153_E019</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">SSA IT Contracting Officer Workload-Based Staffing Assessment (April 2026)</data><data key="node_domain">Procurement / Workforce</data><data key="node_description">GAO reports SSA documented contracting-officer workload and staffing needs using contract award quantity and complexity in April 2026; GAO recommendation 1 closed implemented.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S002.</data></node><node id="R153_E020"><data key="node_entity_id">R153_E020</data><data key="node_entity_type">governance_process</data><data key="node_canonical_name">SSA FY2026 Mandatory IT Contracting Officer Acquisition Training</data><data key="node_domain">Procurement / Workforce</data><data key="node_description">GAO reports SSA developed a FY2026 training plan and assigned mandatory IT acquisition training to address contracting-officer competency gaps; recommendation 2 closed implemented.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S002.</data></node><node id="R153_E021"><data key="node_entity_id">R153_E021</data><data key="node_entity_type">governance_finding</data><data key="node_canonical_name">SSA CIO Contracting Officer Representative Workload-Assessment Open Recommendation</data><data key="node_domain">Procurement / Workforce</data><data key="node_description">GAO recommendation 3 remains open in public report: March 2026 CIO policy requires considering quality workload information, but GAO seeks evidence workload data are documented and used.</data><data key="node_observed_status">recommendation_open</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S002.</data></node><node id="R153_E022"><data key="node_entity_id">R153_E022</data><data key="node_entity_type">governance_finding</data><data key="node_canonical_name">SSA 2019 IT Contracting Officer Training Plan Currency Gap</data><data key="node_domain">Procurement / Workforce</data><data key="node_description">At GAO 2025 review SSA had not updated its contracting-officer training plan since 2019 despite identified acquisition competency deficiencies; subsequently addressed by FY2026 plan.</data><data key="node_observed_status">historical_finding_remediated_2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes">Source R153_S002.</data></node><node id="R154_E001"><data key="node_entity_id">R154_E001</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SERS Order Tracker Remittance Screen</data><data key="node_acronym" /><data key="node_domain">payments/debt</data><data key="node_description">SERS Orders tab provides daily order list, scanned check/money-order image review, and Submit/Update Incorrect Order marking.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E002"><data key="node_entity_id">R154_E002</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">SERS Remittance Supervisor Daily End-of-Day Audit</data><data key="node_acronym" /><data key="node_domain">payments/debt</data><data key="node_description">Remittance supervisor compares SERS Order Tracker daily listing and scanned items against field-office check log; DMS FORT/CCFORT/FODRL are separately reviewed for non-SERS collections.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E003"><data key="node_entity_id">R154_E003</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">SERS Five-Day Negotiable Instrument Secure Custody and Shredding</data><data key="node_acronym" /><data key="node_domain">payments/debt</data><data key="node_description">After SERS scanning and non-negotiable marking, physical checks and money orders are secured for five days and then destroyed; scanned SERS instruments must not be mailed to MATPSC.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E004"><data key="node_entity_id">R154_E004</data><data key="node_entity_type">exception_workflow</data><data key="node_canonical_name">SERS Incorrect Order Flag and MDW Processing-Center Correction</data><data key="node_acronym" /><data key="node_domain">payments/debt</data><data key="node_description">Staff flags an incorrect SERS order in Order Tracker and forwards wrong/correct SSN, beneficiary identification code or establishment date, order number, and requested correction via MDW to PC in specified circumstances.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E005"><data key="node_entity_id">R154_E005</data><data key="node_entity_type">exception_workflow</data><data key="node_canonical_name">SERS Incorrect Scanned Instrument Double-Credit Remediation</data><data key="node_acronym" /><data key="node_domain">payments/debt</data><data key="node_description">If wrong check is scanned for an order, the correct check may require another order; first incorrect credit requires flagging and Help Desk/processing-center adjustment, not assumed immediate automatic reversal.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E006"><data key="node_entity_id">R154_E006</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SERS and DMS Separate Remittance Routing/No Double Mailing</data><data key="node_acronym" /><data key="node_domain">payments/debt</data><data key="node_description">SERS scanned check is electronic transaction; DMS FORT/CCFORT and physical MATPSC transfer apply to eligible non-SERS receipts only; sending SERS checks to MATPSC risks double processing.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E007"><data key="node_entity_id">R154_E007</data><data key="node_entity_type">identity_match_rule</data><data key="node_canonical_name">Treasury TOP Debtor TIN and Four-Letter Name-Control Match</data><data key="node_acronym" /><data key="node_domain">program_integrity</data><data key="node_description">Treasury TOP matches certified disbursements to delinquent debts using taxpayer identification number and name control generally derived from first four characters of last name; for SSA TIN is beneficiary own account number.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E008"><data key="node_entity_id">R154_E008</data><data key="node_entity_type">interagency_business_rule</data><data key="node_canonical_name">SSA Treasury Offset Creditor versus Payment Agency Role Separation</data><data key="node_acronym" /><data key="node_domain">program_integrity</data><data key="node_description">SSA participates in TOP as both creditor and payment agency; TOP does not offset SSA benefits to recover a different SSA program debt, which SSA manages through internal cross-program recovery.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E009"><data key="node_entity_id">R154_E009</data><data key="node_entity_type">workload_control</data><data key="node_canonical_name">ECO 60-Day Treasury Pre-Offset Due Process Notice</data><data key="node_acronym" /><data key="node_domain">program_integrity</data><data key="node_description">External Collection Operation gives debtor at least 60-day planned offset warning and opportunity to resolve or contest before eligible Treasury referral.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E010"><data key="node_entity_id">R154_E010</data><data key="node_entity_type">digital_transaction_workflow</data><data key="node_canonical_name">e1696 Representative-First Claimant-Second Two-Signer Routing</data><data key="node_acronym" /><data key="node_domain">representatives/identity</data><data key="node_description">Representative enters both email contacts, signs in Adobe Sign, then claimant reviews and signs; SSA receives completed electronic appointment only when both participants finish.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E011"><data key="node_entity_id">R154_E011</data><data key="node_entity_type">lifecycle_rule</data><data key="node_canonical_name">e1696 Fifteen-Calendar-Day Outstanding Signature Expiration</data><data key="node_acronym" /><data key="node_domain">representatives/identity</data><data key="node_description">Incomplete electronic representative appointment expires 15 calendar days after representative enters contacts; signer restarts a new form after expiration.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E012"><data key="node_entity_id">R154_E012</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">e1696 Sixty-Minute Inactive Draft-Session Purge</data><data key="node_acronym" /><data key="node_domain">representatives/identity</data><data key="node_description">The public electronic SSA-1696 webpage ends sessions after 60 minutes of inactivity and deletes information entered in that unfinished session; this does not establish backend archival retention.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E013"><data key="node_entity_id">R154_E013</data><data key="node_entity_type">transaction_attribute</data><data key="node_canonical_name">e1696 Representative and Claimant Transaction Email Contacts</data><data key="node_acronym" /><data key="node_domain">person/address provenance</data><data key="node_description">Electronic representative appointment requires a separate valid email for representative and claimant; email routes signing links, not a verified beneficiary mailing address or master-record update.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E014"><data key="node_entity_id">R154_E014</data><data key="node_entity_type">access_control</data><data key="node_canonical_name">e1696 Shared Form-Access Password / Unresettable Credential</data><data key="node_acronym" /><data key="node_domain">identity/protection</data><data key="node_description">Representative creates password used by both signers; SSA cannot reset it and users must restart form after loss; instructions recommend conveying it out-of-band.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E015"><data key="node_entity_id">R154_E015</data><data key="node_entity_type">notification_workflow</data><data key="node_canonical_name">e1696 Daily Pending-Signature Reminder and Mailed Processing Confirmation</data><data key="node_acronym" /><data key="node_domain">representatives/identity</data><data key="node_description">SSA e1696 service sends daily reminders until signing or expiry; electronic receipt copy after completion; SSA subsequently sends a processing notification by postal mail.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E016"><data key="node_entity_id">R154_E016</data><data key="node_entity_type">legal_role_rule</data><data key="node_canonical_name">TreasuryDirect With-Bond Secondary Person Transaction Authority</data><data key="node_acronym" /><data key="node_domain">person/financial ownership</data><data key="node_description">Electronic savings bond With participant may redeem through owner-granted TreasuryDirect transaction authority but is not co-owner while owner is alive; owner may revoke delegated authority.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E017"><data key="node_entity_id">R154_E017</data><data key="node_entity_type">adjudication_rule</data><data key="node_canonical_name">TreasuryDirect Electronic Gift Bond Inaccessible Resource Test</data><data key="node_acronym" /><data key="node_domain">title_xvi/resources</data><data key="node_description">If gift bond purchaser retains it in purchaser TreasuryDirect account and does not grant delivery/access to registered owner, bond is not a presently accessible SSI resource.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E018"><data key="node_entity_id">R154_E018</data><data key="node_entity_type">external_data_attribute</data><data key="node_canonical_name">TreasuryDirect Book-Entry Bond Issue Confirmation Number</data><data key="node_acronym" /><data key="node_domain">treasury/resources</data><data key="node_description">Individual electronic savings bonds use issue-confirmation numbers rather than paper bond serial numbers; account and current holdings remain maintained in TreasuryDirect.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E019"><data key="node_entity_id">R154_E019</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">Savings Bond Source Evidence Documented on SSA EVID Screen</data><data key="node_acronym" /><data key="node_domain">title_xvi/resources</data><data key="node_description">SSA records paper serial number or electronic confirmation number, denomination, series, issue date and redemption value through EVID; no presumption SSA has direct TreasuryDirect account access.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E020"><data key="node_entity_id">R154_E020</data><data key="node_entity_type">program_record_update</data><data key="node_canonical_name">Non-MSSICS SSR Savings Bond Remarks and RE21 Record Update</data><data key="node_acronym" /><data key="node_domain">title_xvi/resources</data><data key="node_description">For non-MSSICS SSI cases staff record verified bond count, value, series and dates in SSR remarks and enter RE21 in case characteristics; separate from automated matching alert.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E021"><data key="node_entity_id">R154_E021</data><data key="node_entity_type">identity_attribution_rule</data><data key="node_canonical_name">Treasury Savings Bond Displayed SSN Is Not Proof of Ownership</data><data key="node_acronym" /><data key="node_domain">person/identity</data><data key="node_description">For savings bond registration, legal owner follows the names on the paper/electronic instrument, not a Social Security number merely printed on the bond; BFS ownership verification may be required.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E022"><data key="node_entity_id">R154_E022</data><data key="node_entity_type">correction_workflow</data><data key="node_canonical_name">IRMAA IRS-Corrected Tax Evidence New Initial Determination</data><data key="node_acronym" /><data key="node_domain">irs/medicare</data><data key="node_description">Beneficiary-provided IRS error letter or transcript plus return can support revised tax-year-specific IRMAA new initial determination through IRMN, PYTY, IRMA, IRRE and EVID.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E023"><data key="node_entity_id">R154_E023</data><data key="node_entity_type">evidence_requirement</data><data key="node_canonical_name">IRMAA IRS Tax-Return Identity-Theft Verification Proof</data><data key="node_acronym" /><data key="node_domain">irs/identity</data><data key="node_description">When asserting IRS tax data were affected by identity theft, beneficiary provides IRS Tax Return Data Base View transcript plus filed return, or qualifying IRS TDS Letter 3538 when no return was required.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E024"><data key="node_entity_id">R154_E024</data><data key="node_entity_type">adjudication_rule</data><data key="node_canonical_name">IRMAA Obvious Tax-Exempt-Interest Transcription-Error Exception</data><data key="node_acronym" /><data key="node_domain">irs/medicare</data><data key="node_description">SSA may accept signed beneficiary tax return instead of IRS correction when TEI difference is clearly a transcription error and no tax audit or protest is pending.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E025"><data key="node_entity_id">R154_E025</data><data key="node_entity_type">procurement_rule</data><data key="node_canonical_name">SSA OAG Unauthorized Contractual Commitment Control</data><data key="node_acronym" /><data key="node_domain">procurement</data><data key="node_description">Before vendor performs services or delivers supplies, SSA requires an approved procurement instrument by delegated contracting officer or authorized micro-purchaser; others cannot legally bind SSA.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E026"><data key="node_entity_id">R154_E026</data><data key="node_entity_type">governance_exception</data><data key="node_canonical_name">SSA OAG FAR 1.602-3 Unauthorized Commitment Ratification</data><data key="node_acronym" /><data key="node_domain">procurement</data><data key="node_description">OAG may ratify qualifying unauthorized commitments under FAR 1.602-3(c), but ratification is discretionary and may require weeks or months; not presumed completed.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R154_E027"><data key="node_entity_id">R154_E027</data><data key="node_entity_type">procurement_rule</data><data key="node_canonical_name">SSA Published Micro-Purchaser Delegated Dollar Limits</data><data key="node_acronym" /><data key="node_domain">procurement</data><data key="node_description">SSA OAG public notice states delegated micro-purchase limits of $2,000 construction, $2,500 services and $10,000 supplies; temporal applicability of these published thresholds needs checking against governing FAR updates.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">4</data><data key="node_notes">Page undated; these are published figures, not an assertion that federal thresholds cannot change.</data></node><node id="R155_E0001"><data key="node_entity_id">R155_E0001</data><data key="node_entity_type">data_flow</data><data key="node_canonical_name">Individual Payee eRPS-to-MBR Overnight Address Propagation</data><data key="node_domain">Person and Address Provenance</data><data key="node_description">Individual payee address change input in eRPS for Title II automatically reaches MBR the following night.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Policy revision 2020; verify live exception handling separately.</data></node><node id="R155_E0002"><data key="node_entity_id">R155_E0002</data><data key="node_entity_type">data_flow</data><data key="node_canonical_name">Individual Payee Title XVI eRPS and MSSICS Dual Address Entry</data><data key="node_domain">Person and Address Provenance</data><data key="node_description">Individual payee address change recorded in eRPS; technician separately uses MSSICS to build SSR because eRPS does not transmit this class of address change to SSR.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0003"><data key="node_entity_id">R155_E0003</data><data key="node_entity_type">data_flow</data><data key="node_canonical_name">Institutional Payee eRPS Cross-Program Address Propagation</data><data key="node_domain">Person and Address Provenance</data><data key="node_description">For correctly linked institutional payee records, an eRPS address update automatically updates associated Title II and Title XVI records.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Narrow institutional exception; not applicable to all individual payees.</data></node><node id="R155_E0004"><data key="node_entity_id">R155_E0004</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">Representative Payee Mailing Change Residence and Custody Reverification</data><data key="node_domain">Person and Address Provenance</data><data key="node_description">When a representative payee changes mailing address, SSA also gathers payee and beneficiary residence and checks custody.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0005"><data key="node_entity_id">R155_E0005</data><data key="node_entity_type">data_maintenance_rule</data><data key="node_canonical_name">MACADE Payee Address Parallel eRPS Update Requirement</data><data key="node_domain">Person and Address Provenance</data><data key="node_description">A processing-center MACADE change-of-address transaction requires separate eRPS entry to update the representative-payee record.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0006"><data key="node_entity_id">R155_E0006</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Manual Correction Process Portal (MCOR)</data><data key="node_domain">Medicare Extra Help</data><data key="node_description">MAPS portal/screen entered from the Development Worksheet for post-determination correction of input errors.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0007"><data key="node_entity_id">R155_E0007</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS SCE and Manual Application Determination Date Screen (DEDS)</data><data key="node_domain">Medicare Extra Help</data><data key="node_description">MAPS screen used to adjust Report Date to ensure appropriate Extra Help subsidy effective dates after correction.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0008"><data key="node_entity_id">R155_E0008</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">MAPS Post-Determination Reapplication Correction Process</data><data key="node_domain">Medicare Extra Help</data><data key="node_description">Creates a new pending Extra Help application populated from an earlier application and requires a new subsidy determination.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0009"><data key="node_entity_id">R155_E0009</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">MAPS Corrected-SSN Partial Data Propagation Exception</data><data key="node_domain">Person/Identity Nexus</data><data key="node_description">When the SSN is changed in a manual correction, certain fields do not propagate to the regenerated application.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0010"><data key="node_entity_id">R155_E0010</data><data key="node_entity_type">data_flow</data><data key="node_canonical_name">MAPS Manual-Correction IRS Data Re-Request</data><data key="node_domain">IRS Provenance</data><data key="node_description">A MAPS manual correction is processed as a new application and causes renewed requests for IRS information; this may create new verification issues.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Does not establish IRS address use, retention, IMF/IRMF source, or automated master-record changes.</data></node><node id="R155_E0011"><data key="node_entity_id">R155_E0011</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">MAPS One Manual Correction Per SSN Per Day Rule</data><data key="node_domain">Medicare Extra Help</data><data key="node_description">MAPS instructions prohibit more than one manual correction action per day for the same SSN.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0012"><data key="node_entity_id">R155_E0012</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">MAPS Technician Error Sixty-Day Correction Window</data><data key="node_domain">Medicare Extra Help</data><data key="node_description">POMS instructs error corrections within 60 days following initial or hearing determination for specified technician-identified errors.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0013"><data key="node_entity_id">R155_E0013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MAPS Corrected Application Subsidy Redetermination</data><data key="node_domain">Medicare Extra Help</data><data key="node_description">Corrected application remains pending until MAPS runs the Subsidy Determination process.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0014"><data key="node_entity_id">R155_E0014</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Direct SSR Update Overpayment Decision Screen (UOPD)</data><data key="node_domain">SSI Debt and Payment</data><data key="node_description">SSI disposition decision menu posted through Direct SSR Update; enumerates waiver, appeal, recovery, referral, bankruptcy and other dispositions.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0015"><data key="node_entity_id">R155_E0015</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">SSI Non-Collection Two-PIN Review Threshold</data><data key="node_domain">SSI Debt and Payment</data><data key="node_description">For noncollect overpayment decisions over $2,000 and under $5,000, obtain claims-specialist-or-higher two-PIN review.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0016"><data key="node_entity_id">R155_E0016</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">SSI Non-Collection Management Concurrence Threshold</data><data key="node_domain">SSI Debt and Payment</data><data key="node_description">For noncollect overpayment decisions of $5,000 or more, field-office management documents concurrence.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0017"><data key="node_entity_id">R155_E0017</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">SSI Non-MSSICS Noncollection Rationale Evidence Route</data><data key="node_domain">SSI Debt and Evidence</data><data key="node_description">Technician documents noncollection reason on SSA-5002 and faxes it and related materials through Evidence Portal into NDRED.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0018"><data key="node_entity_id">R155_E0018</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">SSI Puerto Rico and Virgin Islands Residence Jurisdiction Recode</data><data key="node_domain">Address Provenance</data><data key="node_description">When new residence address is posted for Puerto Rico or U.S. Virgin Islands, system automatically posts jurisdiction FO DIS to SSR; technician transfers MSSICS case to Downtown Manhattan FO 109.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Does not imply incoming IRS address data; source is approved address input.</data></node><node id="R155_E0019"><data key="node_entity_id">R155_E0019</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">Ticket to Work Two-Workday Selection Requery Control</data><data key="node_domain">Ticket to Work</data><data key="node_description">After eligible MBR/SSR/DCF coding correction, staff wait two workdays and request Ticket or General Ticket Query to check ticket selection.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0020"><data key="node_entity_id">R155_E0020</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Ticket to Work General Ticket Query</data><data key="node_domain">Ticket to Work</data><data key="node_description">Eligibility selection query referenced by Ticket-to-Work correction POMS.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0021"><data key="node_entity_id">R155_E0021</data><data key="node_entity_type">address_update_workflow</data><data key="node_canonical_name">Ticket State and County Residence Correction via POS</data><data key="node_domain">Person and Address Provenance</data><data key="node_description">For Title II beneficiary resident in ticket-eligible jurisdiction despite mailing to non-ticket area, POS reflects residence State and County Code.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Mailing and actual residence locations are handled separately.</data></node><node id="R155_E0022"><data key="node_entity_id">R155_E0022</data><data key="node_entity_type">exception_workflow</data><data key="node_canonical_name">Ticket-Eligibility Favorable CDR Result DCF Reconciliation</data><data key="node_domain">Disability, Program Integrity</data><data key="node_description">If favorable medical CDR information appears in DDSQ but not DCF, the Title II PC may input DCF; certain Title XVI cases post to SSR then DCF automatically updates.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R155_E0023"><data key="node_entity_id">R155_E0023</data><data key="node_entity_type">open_data_format</data><data key="node_canonical_name">OAG Headquarters Award History CSV Download</data><data key="node_domain">Acquisitions and Procurement</data><data key="node_description">CSV distribution of SSA OAG headquarters awards; the displayed listing date is November 2, 2023 and excludes modifications/call orders.</data><data key="node_observed_status">historical_snapshot</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical snapshot not evidence of 2026 live awards.</data></node><node id="R155_E0024"><data key="node_entity_id">R155_E0024</data><data key="node_entity_type">open_data_format</data><data key="node_canonical_name">OAG Headquarters Award History XML Download</data><data key="node_domain">Acquisitions and Procurement</data><data key="node_description">XML distribution of the headquarters award listing; as-published date November 2, 2023.</data><data key="node_observed_status">historical_snapshot</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical snapshot not evidence of 2026 live awards.</data></node><node id="R155_E0025"><data key="node_entity_id">R155_E0025</data><data key="node_entity_type">open_data_format</data><data key="node_canonical_name">OAG Headquarters Award History JSON Download</data><data key="node_domain">Acquisitions and Procurement</data><data key="node_description">JSON distribution of the headquarters award listing; as-published date November 2, 2023.</data><data key="node_observed_status">historical_snapshot</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical snapshot not evidence of 2026 live awards.</data></node><node id="R155_E0026"><data key="node_entity_id">R155_E0026</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Table 6.E1 Withheld Retired-Worker Benefits</data><data key="node_domain">Actuarial/Statistical Data</data><data key="node_description">December 2025 MBR 100% data: 295,779 retired-worker benefits withheld; table splits with and without early-retirement reduction and by sex and payment amount.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Published under SSA Research, Statistics and Policy Analysis; not proof of a standalone OACT database.</data></node><node id="R155_E0027"><data key="node_entity_id">R155_E0027</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Table 6.E4 Reasons Benefits Withheld</data><data key="node_domain">Actuarial/Statistical Data</data><data key="node_description">December 2025 complete-population MBR tabulation of benefit withholding reasons and beneficiary categories.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Reason categories include technical entitlement and address unknown.</data></node><node id="R155_E0028"><data key="node_entity_id">R155_E0028</data><data key="node_entity_type">data_quality_category</data><data key="node_canonical_name">2025 OASDI Benefits Withheld Due to Unknown Address Statistical Category</data><data key="node_domain">Address Provenance</data><data key="node_description">December 2025 MBR-based table 6.E4 records 162,312 withheld benefits in address-unknown reason category.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">An aggregate withholding category, not evidence of personal addresses or their sources.</data></node><node id="R155_E0029"><data key="node_entity_id">R155_E0029</data><data key="node_entity_type">data_flow</data><data key="node_canonical_name">SAM-to-SSA Administrative Vendor EFT Update</data><data key="node_domain">Acquisitions and Administrative Payments</data><data key="node_description">SSA states that vendor financial/direct-deposit information changed in SAM automatically updates SSA vendor administrative database.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">SSA does not name physical target database, transport or latency; not a program-benefits bank-account update.</data></node><node id="R155_E0030"><data key="node_entity_id">R155_E0030</data><data key="node_entity_type">work_tracking_rule</data><data key="node_canonical_name">EDCS-Excluded CDR Appeal MI Central Visibility Exception</data><data key="node_domain">Disability and Hearings</data><data key="node_description">Excluded CDR appeals not entered into EDCS are tracked through MI Central rather than routine EDCS case visibility.</data><data key="node_observed_status">documented_as_of</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026 POMS differentiates Title II hearing appeal tickles that may be absent from MI Central, so not universal.</data></node><node id="R156_E0001"><data key="node_entity_id">R156_E0001</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Disability Quality Assurance Performance Accuracy Sample</data><data key="node_domain">disability_quality</data><data key="node_description">DQR quality-assurance sample evaluates adjudicating-component determination correctness and supplies the state performance-accuracy calculation.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0002"><data key="node_entity_id">R156_E0002</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Disability Pre-Effectuation Risk-Selected Sample</data><data key="node_domain">disability_quality</data><data key="node_description">At least half of qualifying favorable adult initial/reconsideration determinations are reviewed; predictive model randomly samples those most likely to be incorrect.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0003"><data key="node_entity_id">R156_E0003</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Disability Targeted Denial Review Discretionary Sample</data><data key="node_domain">disability_quality</data><data key="node_description">TDR selection uses a predictive model of deficiency-prone denied cases; review findings are informational for component performance accuracy but corrective returns are controlled.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0004"><data key="node_entity_id">R156_E0004</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Sample Exclusion Code and Case Routing</data><data key="node_domain">disability_quality</data><data key="node_description">DQR identifies sampled determinations excluded from quality review, codes exclusion in case processing system, and routes case to field office.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0005"><data key="node_entity_id">R156_E0005</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Group I Decisional or Documentation Deficiency</data><data key="node_domain">disability_quality</data><data key="node_description">Group I medical/vocational deficiencies may reverse the allowance or denial; subclassified as decisional or documentation.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0006"><data key="node_entity_id">R156_E0006</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Group II Onset/Ending/Cessation Deficiency</data><data key="node_domain">disability_quality</data><data key="node_description">Group II deficiencies may change onset, ending, or cessation dates, rather than basic allowance/denial.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0007"><data key="node_entity_id">R156_E0007</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Technical Corrective Action (TCA) Classification</data><data key="node_domain">disability_quality</data><data key="node_description">Technical procedural noncompliance category that does not alter the basic disability determination or disability period; different return instrument applies.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0008"><data key="node_entity_id">R156_E0008</data><data key="node_entity_type">form</data><data key="node_canonical_name">DQR Request for Case Action SSA-847-U3</data><data key="node_domain">disability_quality</data><data key="node_description">DQR request for technical corrections; QRCPS propagates claimant SSN/name, claim type/level and adjudicating component; visible in certified electronic folder.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0009"><data key="node_entity_id">R156_E0009</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Request for Case Action Auto-Populated Identity and Claim Fields</data><data key="node_domain">person_identity</data><data key="node_description">From QRCPS, the SSA-847 request inherits claimant SSN, name, claim type, claim level, and adjudicating component. These are transaction fields, not proof of an enterprise person repository.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0010"><data key="node_entity_id">R156_E0010</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">DQR Quality Review Field Office Assistance Request</data><data key="node_domain">disability_quality</data><data key="node_description">QRCPS quality review workflow requests field office development of claimant work activity or other technical issues.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0011"><data key="node_entity_id">R156_E0011</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA-1774-U5 Quality Review Deficiency Auto-Population</data><data key="node_domain">disability_quality</data><data key="node_description">DQR case processing system populates request for corrective action header and multiple sections; onset and issue narrative require human input.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0012"><data key="node_entity_id">R156_E0012</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">DQR Controlled Return for Disability Determination Correction</data><data key="node_domain">disability_quality</data><data key="node_description">Reviewer routes group I/II and outcome-affecting technical deficiencies through QRCPS corrective action, then reexamines full claims record on return.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0013"><data key="node_entity_id">R156_E0013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DQR Final Probability-of-Reversal Review Decision</data><data key="node_domain">disability_quality</data><data key="node_description">Federal quality reviewer makes and documents final probability-of-reversal assessment when the deficiency concerns medical or vocational documentation.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0014"><data key="node_entity_id">R156_E0014</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Substitution-of-Judgment Review Rationale</data><data key="node_domain">disability_quality</data><data key="node_description">Reviewer documents rationale in case processing system for substitution-of-judgment considerations on group I or II decisional deficiency.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0015"><data key="node_entity_id">R156_E0015</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">DQR Assumption of Federal Adjudicative Jurisdiction</data><data key="node_domain">disability_quality</data><data key="node_description">DQR may assume jurisdiction and issue a corrected federal determination, retaining unapproved adjudicating-component originals in audit trail.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0016"><data key="node_entity_id">R156_E0016</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Original Determination Do Not Process Folder Annotation</data><data key="node_domain">disability_evidence</data><data key="node_description">Original SSA-831/832/833 determination remains in certified electronic folder for audit trail but marked Do Not Process after assumption of jurisdiction.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0017"><data key="node_entity_id">R156_E0017</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Original Notice Do Not Release Folder Annotation</data><data key="node_domain">disability_evidence</data><data key="node_description">Original unapproved notice retained in certified electronic folder but annotated Do Not Release when a federal quality determination replaces it.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0018"><data key="node_entity_id">R156_E0018</data><data key="node_entity_type">alert</data><data key="node_canonical_name">DQR Update After Transfer (UAT) Electronic Case Alert</data><data key="node_domain">disability_evidence</data><data key="node_description">Case claim added after transfer may produce alert in eView Alerts and Messages, ROC in Case Data, and SSN History in NCPS case processing.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0019"><data key="node_entity_id">R156_E0019</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DQR Post-Transfer Trailer Evidence Record</data><data key="node_domain">disability_evidence</data><data key="node_description">Additional medical or other evidence arriving during review; adjudicating-component deficiency attributed to evidence available at original clearance, while later evidence may require action.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0020"><data key="node_entity_id">R156_E0020</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DQR Work-History Evidence Query Use Restriction</data><data key="node_domain">earnings</data><data key="node_description">Federal reviewer generally cannot independently obtain SEQY/DEQY/DISCO if query not referenced or present in adjudicating-component case file; specified exceptions when referenced query unclear.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0021"><data key="node_entity_id">R156_E0021</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DQR New-Policy Two-Calendar-Month Grace-Period Control</data><data key="node_domain">disability_quality</data><data key="node_description">DQR may code group I grace-period deficiency related to revised policy as informational, not counted in performance accuracy, during two full calendar months.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0022"><data key="node_entity_id">R156_E0022</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">QRCPS QA Initial Allowance Grace Period Field</data><data key="node_domain">disability_quality</data><data key="node_description">Federal quality reviewer records grace-period code on QA Initial Allowance tab only for qualifying policy-related group I deficiency.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0023"><data key="node_entity_id">R156_E0023</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">DQR Weekly Deficiency Report Technical-Correction Coverage Limitation</data><data key="node_domain">disability_quality</data><data key="node_description">Weekly DQR deficiency report includes only TCAs recorded as regulation-basis-code changes, not all technical corrections.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0024"><data key="node_entity_id">R156_E0024</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DQR Concurrent Disability Split-Sample Reporting Limitation</data><data key="node_domain">disability_quality</data><data key="node_description">For concurrent Title II/Title XVI claims DQR reviews determinations for both claims, while sample review data are recorded only for sampled claim.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0025"><data key="node_entity_id">R156_E0025</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">DQR Group II Controlled-Return Sixty-Day Follow-Up</data><data key="node_domain">disability_quality</data><data key="node_description">For Group II onset, ending and cessation documentation deficiencies, reviewer follows up with adjudicating component after 60 days without corrected determination.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0026"><data key="node_entity_id">R156_E0026</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">RECOOP Accounts Receivable Control (ARC) Code</data><data key="node_domain">payments_debt</data><data key="node_description">RECOOP recovery-controlled SSI case is identified by an ARC code; values govern refund installment and transfer status.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0027"><data key="node_entity_id">R156_E0027</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">RECOOP Monthly SSI Debt Installment Billing</data><data key="node_domain">payments_debt</data><data key="node_description">RECOOP generates monthly debt bills, including bill issued 20 days before next payment due date.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0028"><data key="node_entity_id">R156_E0028</data><data key="node_entity_type">alert</data><data key="node_canonical_name">RECOOP Debtor Contact Section Alert</data><data key="node_domain">payments_debt</data><data key="node_description">RECOOP generates alerts for Debtor Contact Section, not for field offices, when controlling recovery from nonpay SSI debtor.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0029"><data key="node_entity_id">R156_E0029</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">SSI Terminated-to-Reestablished-Record Debt Reconciliation</data><data key="node_domain">payments_debt</data><data key="node_description">When new SSI eligibility period established, transfer overpayment from terminated to reestablished record and close debt on terminated SSR; manual reconciliation applies if not automated.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0030"><data key="node_entity_id">R156_E0030</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Overpayment Reconciliation Menu (UOMN)</data><data key="node_domain">payments_debt</data><data key="node_description">MSSICS Overpayment Menu allows RECONCILIATION of prior terminated-record SSI debt against newly reestablished SSI record.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0031"><data key="node_entity_id">R156_E0031</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Add Manually Computed Overpayment (UOMA) Screen</data><data key="node_domain">payments_debt</data><data key="node_description">For manually transferred unresolved overpayment, employee records balance on reestablished record using MSSICS UOMA.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0032"><data key="node_entity_id">R156_E0032</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSR Q TAC Overpayment Bring-Forward Transaction</data><data key="node_domain">payments_debt</data><data key="node_description">When closing debt on prior record employees enter Q TAC with UOPD selecting overpayment bring-forward.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0033"><data key="node_entity_id">R156_E0033</data><data key="node_entity_type">alert</data><data key="node_canonical_name">SSR B1 Overdue Installment Payment Diary</data><data key="node_domain">payments_debt</data><data key="node_description">B1 diary identifies overdue SSI installment payment linked to G TAC; affects criteria for transfer to reestablished record.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0034"><data key="node_entity_id">R156_E0034</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSR K TAC Cross-Program SSI-to-Title-II Recovery Authorization</data><data key="node_domain">payments_debt</data><data key="node_description">Manual CPR transaction K TAC Recover from Title II Benefits entered using MSSICS UOPD to SSI record for qualifying non-RECOOP debt.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0035"><data key="node_entity_id">R156_E0035</data><data key="node_entity_type">alert</data><data key="node_canonical_name">SSR B8 Cross-Program Recovery Return-to-Payment Diary</data><data key="node_domain">payments_debt</data><data key="node_description">When SSI pay resumes under C01, automated cross-program recovery stops and B8 diary alerts employee to adjust case.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0036"><data key="node_entity_id">R156_E0036</data><data key="node_entity_type">workflow</data><data key="node_canonical_name">SSI 450S Batch Reconciliation for Cross-Program Recovery</data><data key="node_domain">payments_debt</data><data key="node_description">When certain prior terminated records and new SSRs require handling of SSI overpayment K TAC, system uses MSSICS or 450S batch reconciliation.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0037"><data key="node_entity_id">R156_E0037</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSR G TAC SSI Installment Agreement Transaction</data><data key="node_domain">payments_debt</data><data key="node_description">MSSICS UOPD recovery by installments builds G TAC in SSR OPDD segment; collection status constrains transfer of debt.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0038"><data key="node_entity_id">R156_E0038</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">RECOOP Foreign-Debtor Residence-Dependent Recovery Control</data><data key="node_domain">address_provenance</data><data key="node_description">Foreign-resident debtor address must be posted before M TAC except special veterans beneficiaries; Puerto Rico/USVI addresses route through other mechanisms.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0039"><data key="node_entity_id">R156_E0039</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI Financial Institution Name and Address Account Metadata</data><data key="node_domain">address_provenance</data><data key="node_description">SSI employee enters financial institution identity and address associated with account verification; address belongs to bank, not SSI claimant.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0040"><data key="node_entity_id">R156_E0040</data><data key="node_entity_type">alert</data><data key="node_canonical_name">SSI IRS Informational Resource Alert as Development Lead</data><data key="node_domain">irs_financial_provenance</data><data key="node_description">IRS informational alert in SSI liquid-resource redetermination supplies a development lead rather than automatically verified resource or authoritative address.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R156_E0041"><data key="node_entity_id">R156_E0041</data><data key="node_entity_type">alert</data><data key="node_canonical_name">SSI IRS Controlled Resource Alert Requiring Development</data><data key="node_domain">irs_financial_provenance</data><data key="node_description">Controlled IRS alert is a distinct workload item requiring prescribed development; not an automatic resource-value or address update.</data><data key="node_observed_status">documented 2016–2026</data><data key="node_observed_as_of">2026-10-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_CON_ITSSC_CGI"><data key="node_entity_id">R157_CON_ITSSC_CGI</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Historical IT Support Services Contract SS001760018</data><data key="node_domain">Procurement</data><data key="node_description">SSA subcontracting directory names SS001760018 as an Information Technology Support Services Contract and lists R157_ORG_CGI as the prime.</data><data key="node_observed_status">historical_directory_listing</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">No inference about dollar value, contract term, implementation architecture, or operational status in 2026.</data></node><node id="R157_CON_ITSSC_LOCKHEED"><data key="node_entity_id">R157_CON_ITSSC_LOCKHEED</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Historical IT Support Services Contract SS001760016</data><data key="node_domain">Procurement</data><data key="node_description">SSA subcontracting directory names SS001760016 as an Information Technology Support Services Contract and lists R157_ORG_LOCKHEED as the prime.</data><data key="node_observed_status">historical_directory_listing</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">No inference about dollar value, contract term, implementation architecture, or operational status in 2026.</data></node><node id="R157_CON_ITSSC_NORTHROP"><data key="node_entity_id">R157_CON_ITSSC_NORTHROP</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Historical IT Support Services Contract SS001760017</data><data key="node_domain">Procurement</data><data key="node_description">SSA subcontracting directory names SS001760017 as an Information Technology Support Services Contract and lists R157_ORG_NORTHROP as the prime.</data><data key="node_observed_status">historical_directory_listing</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">No inference about dollar value, contract term, implementation architecture, or operational status in 2026.</data></node><node id="R157_CTRL_BK_MBR_MESSAGE"><data key="node_entity_id">R157_CTRL_BK_MBR_MESSAGE</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Title II MBR Bankruptcy-Involved Special Message</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">MBR case annotation identifying bankruptcy for specified BIC and referral to OGC.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_CTRL_BK_WAIVER_HOLD"><data key="node_entity_id">R157_CTRL_BK_WAIVER_HOLD</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Title II Bankruptcy Pending-Waiver Decision Hold</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Waiver adjudication is generally held pending bankruptcy decision unless OGC advises otherwise.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_CTRL_ECDR_5D"><data key="node_entity_id">R157_CTRL_ECDR_5D</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eCDR Cessation Decision Five-Day MBR and SSR Verification</data><data key="node_domain">Disability &amp; Appeals</data><data key="node_description">FO checks MBR and applicable SSID/SSR within five days after decision return and acts manually if update absent.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_CTRL_ECDR_DCF_CDRI"><data key="node_entity_id">R157_CTRL_ECDR_DCF_CDRI</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EDCS-to-DCF CDRI Appeal Posting at Transfer</data><data key="node_domain">Disability &amp; Appeals</data><data key="node_description">DCF CDRI appeal details posted automatically after EDCS transfer; initial CDR movement requires separate action.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_CTRL_ECDR_MAINFRAME_PRECHECK"><data key="node_entity_id">R157_CTRL_ECDR_MAINFRAME_PRECHECK</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eCDR Reconsideration Mainframe Contact and Payee Pretransfer Verification</data><data key="node_domain">Person &amp; Identity</data><data key="node_description">FO must verify and update address, phone, and representative information on mainframe prior to EDCS reconsideration transfer.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documentation does not say which master attribute updates automatically or assert verified residency.</data></node><node id="R157_CTRL_PIE_3MO_NOTICE"><data key="node_entity_id">R157_CTRL_PIE_3MO_NOTICE</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">PIE Three Consecutive Months Without Wage Data Resumption Notice</data><data key="node_domain">SSI &amp; Earnings</data><data key="node_description">SSI automated notice restores employer-specific wage reporting responsibilities after three consecutive months without PDP wage information and a prior reduction notice.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_CTRL_PIE_AUTH_APPEAL"><data key="node_entity_id">R157_CTRL_PIE_AUTH_APPEAL</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">PIE Authorization Continuation and Late-Appeal Gap Rule</data><data key="node_domain">SSI &amp; Earnings</data><data key="node_description">Active authorization persists through timely appeals; after an untimely appeal authorization can lapse and require new WEIA, causing missing monthly PIE wage periods.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_CTRL_PIE_FORCE_DUE"><data key="node_entity_id">R157_CTRL_PIE_FORCE_DUE</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">PIE SSI Nonautomatable Wage Post Exception Conditions</data><data key="node_domain">SSI &amp; Earnings</data><data key="node_description">Certain force-due, manual deeming, terminated, inactive or mismatched SSI cases cannot use the ordinary automated PIE wage-posting path.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_DATA_BK_COURT_NOTICE"><data key="node_entity_id">R157_DATA_BK_COURT_NOTICE</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Electronic Bankruptcy Court Notice to SSA OGC</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Court electronic bankruptcy notification to SSA OGC, which routes Title II cases to processing centers and Title XVI to regional offices.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source speaks of most court notices, not an identified court-SSA API.</data></node><node id="R157_DATA_BK_DMS_REMARKS"><data key="node_entity_id">R157_DATA_BK_DMS_REMARKS</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DMS Bankruptcy Trustee Refund Audit Remarks</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">DMS remarks document the IPAC refund, restoration of debt balance and related actions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_DATA_BK_IPAC_ID"><data key="node_entity_id">R157_DATA_BK_IPAC_ID</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Bankruptcy Trustee Refund IPAC Reference Number</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Office of Finance IPAC identifier returned to PC2 and recorded as part of audit trail.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_DATA_BK_PREPETITION"><data key="node_entity_id">R157_DATA_BK_PREPETITION</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Bankruptcy Prepetition Debt Benefit-Month Classification</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Debt classification by underlying benefit month relative to petition filing date; separate from discovery or assessment date.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_DATA_BK_TRUSTEE_MAIL"><data key="node_entity_id">R157_DATA_BK_TRUSTEE_MAIL</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Bankruptcy Trustee Refund Payment Contact Address</data><data key="node_domain">Address Provenance</data><data key="node_description">Mailing destination associated with trustee/intergovernmental refund; it is not the beneficiary residence or program mailing address.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">The policy includes agency name, EIN, attention, and address for refund processing.</data></node><node id="R157_DATA_NUMIDENT_NL2"><data key="node_entity_id">R157_DATA_NUMIDENT_NL2</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Historical Numident NL2 Name Line for Legal-Name Evidence</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Prior Numident NL2 line can support legal name for certain U.S.-born applicants when current identity and microprint conditions are met.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Evidentiary conditional rule, not a claim that NL2 universally identifies current legal name.</data></node><node id="R157_DATA_OSDBU_SUBDIR"><data key="node_entity_id">R157_DATA_OSDBU_SUBDIR</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA OSDBU Historical Small Business Subcontracting Directory</data><data key="node_domain">Procurement</data><data key="node_description">Official public listing of historical prime contract identification, prime names and subcontracting liaison opportunities.</data><data key="node_observed_status">undated_public_directory</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">The web directory does not establish contract award date, award dollar amount, current exercise of option or SSA technology deployment.</data></node><node id="R157_DOC_DMA_0050"><data key="node_entity_id">R157_DOC_DMA_0050</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CEF DMA Document Type 0050 - Activities of Daily Living</data><data key="node_domain">Disability Evidence</data><data key="node_description">Document Management Architecture index code 0050 specifies Generic ADL questionnaire type when iterations vary. Located in CEF section E.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A classification value, not a separate repository or database table.</data></node><node id="R157_DOC_DMA_0180"><data key="node_entity_id">R157_DOC_DMA_0180</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CEF DMA Document Type 0180 - Claimant-Supplied Medical Evidence</data><data key="node_domain">Disability Evidence</data><data key="node_description">Document Management Architecture index code 0180 specifies Unsolicited medical evidence received from claimant. Located in CEF section F.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A classification value, not a separate repository or database table.</data></node><node id="R157_DOC_DMA_0185"><data key="node_entity_id">R157_DOC_DMA_0185</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CEF DMA Document Type 0185 - Copy of Evidence Request</data><data key="node_domain">Disability Evidence</data><data key="node_description">Document Management Architecture index code 0185 specifies Evidence of unsuccessful medical-record development request. Located in CEF section F.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A classification value, not a separate repository or database table.</data></node><node id="R157_DOC_DMA_0190"><data key="node_entity_id">R157_DOC_DMA_0190</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CEF DMA Document Type 0190 - Copy of Case Development Correspondence</data><data key="node_domain">Disability Evidence</data><data key="node_description">Document Management Architecture index code 0190 specifies DDS outgoing case-development letter; DDS case-processing system automatically images/indexes letter after printing. Located in CEF section E.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A classification value, not a separate repository or database table.</data></node><node id="R157_DOC_DMA_1080"><data key="node_entity_id">R157_DOC_DMA_1080</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CEF DMA Document Type 1080 - Disability Report Work History</data><data key="node_domain">Disability Evidence</data><data key="node_description">Document Management Architecture index code 1080 specifies Returned SSA-3369 Work History report. Located in CEF section E.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A classification value, not a separate repository or database table.</data></node><node id="R157_DOC_DMA_3157"><data key="node_entity_id">R157_DOC_DMA_3157</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CEF DMA Document Type 3157 - Educational Records Medical</data><data key="node_domain">Disability Evidence</data><data key="node_description">Document Management Architecture index code 3157 specifies School records containing IQ scores or other medical information. Located in CEF section F.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A classification value, not a separate repository or database table.</data></node><node id="R157_DOC_DMA_3158"><data key="node_entity_id">R157_DOC_DMA_3158</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CEF DMA Document Type 3158 - Educational Records Nonmedical</data><data key="node_domain">Disability Evidence</data><data key="node_description">Document Management Architecture index code 3158 specifies School records without medical information such as behavioral reports. Located in CEF section E.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A classification value, not a separate repository or database table.</data></node><node id="R157_DOC_DMA_5032"><data key="node_entity_id">R157_DOC_DMA_5032</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">CEF DMA Document Type 5032 - Attorney/Representative-Supplied Medical Evidence</data><data key="node_domain">Disability Evidence</data><data key="node_description">Document Management Architecture index code 5032 specifies Unsolicited medical evidence submitted by representative. Located in CEF section F.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A classification value, not a separate repository or database table.</data></node><node id="R157_ORG_CGI"><data key="node_entity_id">R157_ORG_CGI</data><data key="node_entity_type">organization</data><data key="node_canonical_name">CGI Federal Inc.</data><data key="node_domain">Procurement</data><data key="node_description">Historical SSA OSDBU subcontracting directory identifies organization as prime listed for IT Support Services Contract.</data><data key="node_observed_status">historical_directory_listing</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical directory listing; no current-vendor status inferred.</data></node><node id="R157_ORG_LOCKHEED"><data key="node_entity_id">R157_ORG_LOCKHEED</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Lockheed Martin Corporation</data><data key="node_domain">Procurement</data><data key="node_description">Historical SSA OSDBU subcontracting directory identifies organization as prime listed for IT Support Services Contract.</data><data key="node_observed_status">historical_directory_listing</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical directory listing; no current-vendor status inferred.</data></node><node id="R157_ORG_NORTHROP"><data key="node_entity_id">R157_ORG_NORTHROP</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Northrop Grumman Systems Corporation</data><data key="node_domain">Procurement</data><data key="node_description">Historical SSA OSDBU subcontracting directory identifies organization as prime listed for IT Support Services Contract.</data><data key="node_observed_status">historical_directory_listing</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical directory listing; no current-vendor status inferred.</data></node><node id="R157_PROC_BK_IPAC"><data key="node_entity_id">R157_PROC_BK_IPAC</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Bankruptcy Trustee Intergovernmental Payment Processing</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">Office of Finance issues IPAC payment upon PC2 request and returns IPAC identifier to PC2.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not assume IPAC is used for every SSA bankruptcy refund.</data></node><node id="R157_PROC_BK_PREF_REFUND"><data key="node_entity_id">R157_PROC_BK_PREF_REFUND</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Bankruptcy Preferential Payment Refund and Debt Reinstatement</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">OGC-directed payment refund to trustee through administrative expenses and restoration of appropriate debt balance.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_PROC_BK_STAY"><data key="node_entity_id">R157_PROC_BK_STAY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Bankruptcy Prepetition Collection Stay</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">After OGC notice, stop collections for debt arising before filing and refund collection taken after filing.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Debt arises for the benefit month, not when SSA detects or assesses the overpayment.</data></node><node id="R157_PROC_DMV_NAMESSN"><data key="node_entity_id">R157_PROC_DMV_NAMESSN</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">State DMV Name-SSN Verification and SSN Card Correction Follow-up</data><data key="node_domain">Person &amp; Identity</data><data key="node_description">Some DMV identity-card processes can lead to SSA card correction after electronic name/SSN verification mismatch or jurisdiction rules.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">No automatic DMV-to-Numident change or address-update interface established.</data></node><node id="R157_PROC_ECDR_CPD_PAPER"><data key="node_entity_id">R157_PROC_ECDR_CPD_PAPER</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">eCDR Prior Comparison Point Paper Folder Parallel Transfer</data><data key="node_domain">Disability &amp; Appeals</data><data key="node_description">Paper prior CPD folders travel to DDS when current electronic reconsideration transfers; electronic CPD folders are linked in EDCS.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_PROC_SSNAP_NAME_CORR"><data key="node_entity_id">R157_PROC_SSNAP_NAME_CORR</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSN Card Legal-Name Correction Without Name-Change Event</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">SSN card correction for existing legal name with no intervening legal name-change event.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_RULE_BK_JOINT"><data key="node_entity_id">R157_RULE_BK_JOINT</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Bankruptcy Debtor-Specific Joint and Contingent Liability Control</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">A representative payee or other joint debtor filing bankruptcy does not automatically stop collections against separate non-filing debtors.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R157_RULE_SSI_COHORT_2025"><data key="node_entity_id">R157_RULE_SSI_COHORT_2025</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2025 Simplified SSI Online Cohort Eligibility Rules</data><data key="node_domain">SSI &amp; Digital Service</data><data key="node_description">In June 2025 SSA limited simplified SSI online eligibility by age 18 to 64 years 10 months, concurrent SSDI claim, account, marriage and prior application history, and citizenship with noted noncitizen exceptions.</data><data key="node_observed_status">historical_published_rule</data><data key="node_observed_as_of">2025-06-12</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R157_SVC_SSI_SIMPLIFIED_2025"><data key="node_entity_id">R157_SVC_SSI_SIMPLIFIED_2025</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">2025 Streamlined Online Initial SSI Application Route</data><data key="node_domain">SSI &amp; Digital Service</data><data key="node_description">SSA June 2025 publication described streamlined online SSI filing for certain concurrent SSI/SSDI adult claimants.</data><data key="node_observed_status">historically_reported_available</data><data key="node_observed_as_of">2025-06-12</data><data key="node_confidence">4</data><data key="node_notes">Dated description must not be treated as an October 2026 eligibility guarantee.</data></node><node id="R157_UI_EDCS_CDRI"><data key="node_entity_id">R157_UI_EDCS_CDRI</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS CDR Reconsideration Select Case Level and Transfer Control</data><data key="node_domain">Disability &amp; Appeals</data><data key="node_description">EDCS screen path used to initiate CDR reconsideration and transfer consolidated appeals.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Screen naming corresponds to Select Case Level and Transfer/Updates labels in POMS, not a newly discovered standalone system.</data></node><node id="R158_E0001"><data key="node_entity_id">R158_E0001</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS IT Annual Budget Line-Item Planning</data><data key="node_domain">DDS IT Acquisition</data><data key="node_description">State DDS annual budget explicitly carries separate IT cost line item; submitted through established budget process.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0002"><data key="node_entity_id">R158_E0002</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">DDS Quarterly IT Spending Plan Submission</data><data key="node_domain">DDS IT Acquisition</data><data key="node_description">DDS quarterly spending plan includes IT equipment and service costs, separate from annual budget.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0003"><data key="node_entity_id">R158_E0003</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">DDS Employee IT Developer Personal Services Cost Category</data><data key="node_domain">DDS IT Acquisition</data><data key="node_description">Salary and wages of DDS personnel developing IT systems belong in Personal Services cost projections.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0004"><data key="node_entity_id">R158_E0004</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Outside-DDS State Programmer Indirect Cost Category</data><data key="node_domain">DDS IT Acquisition</data><data key="node_description">Pay of state programmers and other state-related personnel who are not DDS employees is budgeted as Indirect Costs.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0005"><data key="node_entity_id">R158_E0005</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">DDS Private-Vendor IT Development Acquisition Cost Category</data><data key="node_domain">DDS IT Acquisition</data><data key="node_description">Private vendor services developing DDS IT systems are part of system acquisition cost under IT new.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0006"><data key="node_entity_id">R158_E0006</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">DDS IT Maintenance Miscellaneous Cost Category</data><data key="node_domain">DDS IT Acquisition</data><data key="node_description">Ongoing IT maintenance changes are budgeted in the miscellaneous cost category.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0007"><data key="node_entity_id">R158_E0007</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS IT Funding Request Central Office Review Requirement</data><data key="node_domain">DDS IT Acquisition</data><data key="node_description">Requests for new DDS IT equipment or services need required documents and central-office reviews; policy does not identify a deployed acquisition system.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0008"><data key="node_entity_id">R158_E0008</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS Early IT Budget Projection Requirement</data><data key="node_domain">DDS IT Acquisition</data><data key="node_description">DDS should budget reasonably expected IT development without waiting until its full IT approval documentation is finished.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0009"><data key="node_entity_id">R158_E0009</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS IT Proposal Information Security Officer Approval</data><data key="node_domain">DDS IT Security</data><data key="node_description">System proposals require ISO approval; regional ISO consultation begins at planning stage. Published governance policy, not actual approval event.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0010"><data key="node_entity_id">R158_E0010</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS IT Design-Stage PII Security Assessment</data><data key="node_domain">DDS IT Security</data><data key="node_description">DDS feasibility studies, cost benefit analyses and functional requirements must address privacy, confidentiality, safeguards and security implications.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0011"><data key="node_entity_id">R158_E0011</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS Systems Disaster-Recovery Offline Backup Policy</data><data key="node_domain">DDS IT Security</data><data key="node_description">Published instruction requires appropriate backup and describes program copies stored offsite in a fireproof vault; current deployed media, implementation, cloud status not confirmed.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0012"><data key="node_entity_id">R158_E0012</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS System User Hiring and Termination Access Control</data><data key="node_domain">DDS IT Security</data><data key="node_description">Published policy instructs granting authorized new-hire access and revoking terminated employee access; not evidence of particular IAM product.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0013"><data key="node_entity_id">R158_E0013</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS Internal and External Program Abuse Prevention Security Requirement</data><data key="node_domain">DDS IT Security</data><data key="node_description">DDS system safeguards should prevent and detect internal, parent-agency, and external program abuse, and support continuity recovery.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0014"><data key="node_entity_id">R158_E0014</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">SSI OACT Payment-Date Calendar-Year Accounting Basis</data><data key="node_domain">Actuarial &amp; Statistical</data><data key="node_description">2026 SSI annual report IV.C groups federal SSI disbursements according to actual payment date, including December payments due next January.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0015"><data key="node_entity_id">R158_E0015</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">SSI Statistical Supplement Benefit-Due-Month Accounting Basis</data><data key="node_domain">Actuarial &amp; Statistical</data><data key="node_description">Annual Statistical Supplement SSI payment reporting groups payments by month due rather than date issued; not interchangeable with OACT IV.C totals.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0016"><data key="node_entity_id">R158_E0016</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">SSI Treasury-Remitted Overpayment Recovery Accounting Reconciliation</data><data key="node_domain">Actuarial &amp; Statistical</data><data key="node_description">Since 1991 federal budget obligation figures do not subtract certain recovered SSI overpayments remitted directly to Treasury, whereas Statistical Supplement totals do subtract such recoveries.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0017"><data key="node_entity_id">R158_E0017</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">SSI Fiscal-Year Early-Payment Month Count Adjustment</data><data key="node_domain">Actuarial &amp; Statistical</data><data key="node_description">Weekend/holiday advance payments may make a fiscal-year disbursement series effectively reflect 11, 12, or 13 payment months.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0018"><data key="node_entity_id">R158_E0018</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">SSI FBR-Adjusted Federal Payment Projection Calculation</data><data key="node_domain">Actuarial &amp; Statistical</data><data key="node_description">OACT projects average SSI payments from federal benefit rates adjusted for income, marital status and living arrangements, then combines projected average payments with projected federal recipient counts. Software/database unspecified.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0019"><data key="node_entity_id">R158_E0019</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS Consultative Examination Claimant Complaint Intake</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">DDS accepts written or verbal claimant complaints involving CE provider, facility, staff, or CE circumstances; complaints preferably reduced to signed writing.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0020"><data key="node_entity_id">R158_E0020</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS Consultative Examination Complaint Investigation</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">DDS must investigate all CE claimant complaints, take appropriate state-procedure action and notify SSA Disability Adjudication when appropriate.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0021"><data key="node_entity_id">R158_E0021</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">DDS Consultative Examination Egregious Complaint Allegation Type</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Provider complaints may include serious illegal/criminal, sexual harassment, cultural insensitivity, or health and safety allegations. Category is a reported allegation, not a substantiated finding.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0022"><data key="node_entity_id">R158_E0022</data><data key="node_entity_type">process</data><data key="node_canonical_name">EDCS Case-Transfer Mainframe Data Repropagation</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">EDCS automatically repropagates mainframe data at case transfer to refresh its content against mainframe case information.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0023"><data key="node_entity_id">R158_E0023</data><data key="node_entity_type">alert</data><data key="node_canonical_name">EDCS RPS MCS MSSICS Transfer-Time Unavailability Alert</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">EDCS generates an alert if it cannot access RPS, MCS or MSSICS during transfer; claims representative may continue or cancel and transfer later.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0024"><data key="node_entity_id">R158_E0024</data><data key="node_entity_type">process</data><data key="node_canonical_name">EDCS Field-Office Jurisdiction Transfer Prerequisite</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">DDS may receive routing materials but cannot process electronic case when FO failed to transfer EDCS case jurisdiction; FO must transfer it.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0025"><data key="node_entity_id">R158_E0025</data><data key="node_entity_type">process</data><data key="node_canonical_name">EDCS Certified-Electronic-Folder Paper-Exclusion Routing Rule</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">CEF case usually electronically transferred; exclusions or earlier paper folders require attaching printed routing form and sending paper Modular Disability Folder.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0026"><data key="node_entity_id">R158_E0026</data><data key="node_entity_type">process</data><data key="node_canonical_name">EDCS Transfer-Time Signed SSA-827 HIT Trigger Precondition</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">MEGAHIT automated request depends on appropriate signed SSA-827 being in electronic folder at case transfer or within prescribed timing.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0027"><data key="node_entity_id">R158_E0027</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">SSI IRS Alert Payee-Address Taxpayer-Address Attribution Risk</data><data key="node_domain">Person &amp; Address Provenance</data><data key="node_description">IRS and MEF tax data interface defines payee as person/entity whose name/address is in payer records; may be third party using taxpayer SSN. Tax-alert address cannot be assumed verified taxpayer/beneficiary residence.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R158_E0028"><data key="node_entity_id">R158_E0028</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">SSI IRS Alert Independently Verified Data Reclassification Rule</data><data key="node_domain">Person &amp; Address Provenance</data><data key="node_description">SSA preexisting file facts and independently verified FO information are treated as SSA data with normal SSA disclosure procedures even where identical to protected tax-alert contents. No master-record update established.</data><data key="node_observed_status">documented_policy_or_statistical_method</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source identifies administrative method/control. Unless explicitly described, this is not a separate application, physical database, current deployed technology, automated interface or live operational audit.</data></node><node id="R159_E001"><data key="node_entity_id">R159_E001</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Representative Appointment Does Not Authorize Beneficiary Address or Deposit Changes</data><data key="node_domain">Person / Address / Representation</data><data key="node_description">An appointed representative cannot change claimant identity, mailing address, or bank account solely by virtue of an appointment; another independent qualifying authority is required.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not model appointed-representative access as master-record write authority.</data></node><node id="R159_E002"><data key="node_entity_id">R159_E002</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Representative Designated-Associate Administrative Delegation Boundary</data><data key="node_domain">Representation / Privacy</data><data key="node_description">Representative may delegate medical record development and preparation of appeal forms, but not testimony, legal arguments, legal advice or deciding whether to appeal.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E003"><data key="node_entity_id">R159_E003</data><data key="node_entity_type">process</data><data key="node_canonical_name">Appointed Representative Telephone Disclosure RASR and Identity Check</data><data key="node_domain">Representation / Privacy</data><data key="node_description">Telephone release of claimant information requires confirmation of active appointment in RASR and verification of caller identity.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E004"><data key="node_entity_id">R159_E004</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Numident SPIN Code 6 In-Person-Only Representative Disclosure Restriction</data><data key="node_acronym">SPIN 6</data><data key="node_domain">Person / Identity / Privacy</data><data key="node_description">When SPIN 6 appears on Numident, no telephone, mail or fax release to an appointed representative or associate is permitted; request is handled in person at local field office.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Policy control on disclosure, not evidence of the underlying technical enforcement platform.</data></node><node id="R159_E005"><data key="node_entity_id">R159_E005</data><data key="node_entity_type">process</data><data key="node_canonical_name">RASR Temporary Fee-Payment-Only Auxiliary Appointment</data><data key="node_domain">Representative Payee / Title II</data><data key="node_description">For an affected auxiliary beneficiary or eligible spouse without separately appointed representative, SSA creates a temporary payment-only RASR appointment for a primary claimant representative fee, terminating it after certification and release.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">The temporary appointment does not trigger appointment-related notices to primary claimant representative.</data></node><node id="R159_E006"><data key="node_entity_id">R159_E006</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Auxiliary Beneficiary Independent Representation and Notice Opt-Out</data><data key="node_domain">Title II / Representation</data><data key="node_description">An affected auxiliary beneficiary can appoint their own representative or notify SSA in writing to restrict representation/notice access by the primary claimant representative.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E007"><data key="node_entity_id">R159_E007</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Federal Court Attorney Limited Fee-Notice Disclosure Without SSA Appointment</data><data key="node_domain">Representation / Privacy</data><data key="node_description">Attorney in federal court but not appointed before SSA may receive limited information to support a court fee petition, not unrestricted claim-file access absent appointment/consent.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E008"><data key="node_entity_id">R159_E008</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Representative Administrative Query Screen Disclosure Restriction</data><data key="node_domain">Representation / Privacy</data><data key="node_description">SSA generally does not provide MBR or other administrative query printouts to appointed representatives; staff should provide specific information in another format if possible.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E009"><data key="node_entity_id">R159_E009</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Development Gerontology Screen</data><data key="node_acronym">DGEN</data><data key="node_domain">Title XVI / Person / Integrity</data><data key="node_description">MSSICS RZ/LI development screen documenting age-90 gerontology interview and its completion.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">POMS specifies DGEN screen and SSR build; physical persistence not described.</data></node><node id="R159_E010"><data key="node_entity_id">R159_E010</data><data key="node_entity_type">application</data><data key="node_canonical_name">CHINET SSI Diary Workload Control Application</data><data key="node_domain">Title XVI / Workload Control</data><data key="node_description">CHINET application in which gerontology KC diaries are available, alongside SSTNG and MI Central listings.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Named operational source as of cited POMS; technology, ownership and hosting not established.</data></node><node id="R159_E011"><data key="node_entity_id">R159_E011</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Gerontology KC Diary Age-90 Three-Year SSR Inactivity Selection</data><data key="node_domain">Title XVI / Integrity</data><data key="node_description">KC diary selection is for SSI-only recipients in C01 current pay who reach or have passed 90, with no SSR activity for at least three years.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Refines existing KC diary entity; does not duplicate it.</data></node><node id="R159_E012"><data key="node_entity_id">R159_E012</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Gerontology Recipient Alive and Identity Interview Verification</data><data key="node_domain">Title XVI / Person / Integrity</data><data key="node_description">Employee must verify recipient identity and that beneficiary is alive even when a representative payee exists; telephone preferred, home visit may be required.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E013"><data key="node_entity_id">R159_E013</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Gerontology Unlocatable S06 Versus Missed-Appointment N20 Control</data><data key="node_domain">Title XVI / Address / Integrity</data><data key="node_description">Use S06 whereabouts-unknown after exhaustive locate efforts; N20 applies to missed interviews when mail is not returned undeliverable, following required attempts.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not treat failed contact as validated address information.</data></node><node id="R159_E014"><data key="node_entity_id">R159_E014</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Gerontology Death Evidence EVID Verification Prerequisite</data><data key="node_domain">Title XVI / Death / Identity</data><data key="node_description">SSI gerontology death documentation must be recorded in EVID; unsupported SSR death date alone is insufficient verified proof.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E015"><data key="node_entity_id">R159_E015</data><data key="node_entity_type">process</data><data key="node_canonical_name">Gerontology Non-MSSICS UDIA Diary Clearance and SSA-1719B</data><data key="node_domain">Title XVI / Workload</data><data key="node_description">For non-MSSICS cases employee clears KC diary via Direct SSR Update UDIA, completes SSA-1719B, and stores SSA-5002 in NDRED.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E016"><data key="node_entity_id">R159_E016</data><data key="node_entity_type">process</data><data key="node_canonical_name">DCF Office-of-Systems Age-18 Case Load and CDR Alert</data><data key="node_domain">Disability / Work Control</data><data key="node_description">SSA Office of Systems loads age-18 redetermination cases into Disability Control File and creates medical CDR alerts on the field office pending list.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E017"><data key="node_entity_id">R159_E017</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">DCF Type 4 Age-18 Direct-Release CDR Classification</data><data key="node_domain">Disability / Work Control</data><data key="node_description">Age-18 redeterminations in DCF appear as Type 4 CDR with age-18/DDS category legend and direct-release event legend.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E018"><data key="node_entity_id">R159_E018</data><data key="node_entity_type">process</data><data key="node_canonical_name">DCF Event 5 Age-18 Nonmedical Screen-Out Review</data><data key="node_domain">Disability / Work Control</data><data key="node_description">Field office may select DCF Event 5 SSR/MBR condition and apply screening rules when a loaded age-18 case fails nonmedical requirements.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E019"><data key="node_entity_id">R159_E019</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Age-18 and Redetermination Combined Interview Scheduling</data><data key="node_domain">Title XVI / Disability</data><data key="node_description">When SSTNG identifies age-18 redetermination alongside SSI RZ, field office coordinates the two interviews; KB diary cases require DDS medical redetermination.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E020"><data key="node_entity_id">R159_E020</data><data key="node_entity_type">process</data><data key="node_canonical_name">Age-18 Prior Adult Medical Determination and SSR TMR Verification</data><data key="node_domain">Title XVI / Disability</data><data key="node_description">Field office reviews prior DDS or OHO medical determinations and SSR Type of Master Record DC-to-DI transition to establish whether adult disability criteria were already applied.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">TMR is an indicator to check, not proof of all supporting adjudicative facts.</data></node><node id="R159_E021"><data key="node_entity_id">R159_E021</data><data key="node_entity_type">notice</data><data key="node_canonical_name">RASR RSR103 Representative Appointment Confirmation</data><data key="node_acronym">RSR103</data><data key="node_domain">Representation / Notices</data><data key="node_description">Notice to appointed representative after appointment, without fee assignment; contains case-level representation acknowledgment.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Published notice exhibit; not evidence that every notice was sent in every case.</data></node><node id="R159_E022"><data key="node_entity_id">R159_E022</data><data key="node_entity_type">notice</data><data key="node_canonical_name">RASR RSR104 Claimant Appointment Confirmation</data><data key="node_acronym">RSR104</data><data key="node_domain">Representation / Notices</data><data key="node_description">Notice to claimant acknowledging SSA processed their appointed representative, supporting awareness and the chance to dispute.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Published notice exhibit; not evidence that every notice was sent in every case.</data></node><node id="R159_E023"><data key="node_entity_id">R159_E023</data><data key="node_entity_type">notice</data><data key="node_canonical_name">RASR RSR106 Revocation Notice to Representative</data><data key="node_acronym">RSR106</data><data key="node_domain">Representation / Notices</data><data key="node_description">Notice to representative that claimant revoked the appointment and that personal-information access ends.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Published notice exhibit; not evidence that every notice was sent in every case.</data></node><node id="R159_E024"><data key="node_entity_id">R159_E024</data><data key="node_entity_type">notice</data><data key="node_canonical_name">RASR RSR107 Representative Withdrawal Notice to Claimant</data><data key="node_acronym">RSR107</data><data key="node_domain">Representation / Notices</data><data key="node_description">Notice to claimant when representative withdraws without necessarily naming a replacement principal representative.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Published notice exhibit; not evidence that every notice was sent in every case.</data></node><node id="R159_E025"><data key="node_entity_id">R159_E025</data><data key="node_entity_type">notice</data><data key="node_canonical_name">RASR RSR108 Representative Withdrawal and Principal Replacement Notice</data><data key="node_acronym">RSR108</data><data key="node_domain">Representation / Notices</data><data key="node_description">Notice to claimant when a representative withdraws and another appointed representative becomes principal.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Published notice exhibit; not evidence that every notice was sent in every case.</data></node><node id="R159_E026"><data key="node_entity_id">R159_E026</data><data key="node_entity_type">notice</data><data key="node_canonical_name">RASR RSR119 Appointment With Entity Fee Assignment Confirmation</data><data key="node_acronym">RSR119</data><data key="node_domain">Representation / Notices</data><data key="node_description">Notice to representative confirming appointment with assignment of authorized direct fee payment to an identified entity and its EIN.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Published notice exhibit; not evidence that every notice was sent in every case.</data></node><node id="R159_E027"><data key="node_entity_id">R159_E027</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Upload Documents Original-or-Certified Evidence Electronic Submission Exclusion</data><data key="node_domain">Digital Intake / Evidence</data><data key="node_description">SSA says original or certified document copies cannot be submitted through Upload Documents; use postal mail or in-person delivery.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Customer-facing 2026 limitation; it does not prohibit all types of scanned evidence.</data></node><node id="R159_E028"><data key="node_entity_id">R159_E028</data><data key="node_entity_type">process</data><data key="node_canonical_name">Gerontology Suspected Fraud OIG Referral with KC Diary Tag</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">When gerontology interview suggests fraud or unreported death, field office submits referral through ARIS and annotates the gerontology limited issue designation.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E029"><data key="node_entity_id">R159_E029</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Gerontology Third-Party Helper Permission and Disclosure Limit</data><data key="node_domain">Title XVI / Privacy</data><data key="node_description">Third-party interview helper can assist after recipient permission and name/contact are documented but does not automatically gain access rights to beneficiary information.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R159_E030"><data key="node_entity_id">R159_E030</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Gerontology Returned Mail and Address-Location Development</data><data key="node_domain">Title XVI / Address Provenance</data><data key="node_description">Returned interview mail or contact failure prompts systematic location development using existing SSA records, Postal Service, financial institutions and other appropriate leads.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">External address leads are not automatically verified SSA program-address updates.</data></node><node id="R160_E0001"><data key="node_entity_id">R160_E0001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RECOOP Title II Death Billing Stop and Alert</data><data key="node_domain">Payments / Debt</data><data key="node_description">MBR-recorded death automatically causes RECOOP to stop billing and produce a death alert.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0002"><data key="node_entity_id">R160_E0002</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">RECOOP Title II Death Alert</data><data key="node_domain">Payments / Debt</data><data key="node_description">Automated alert raised on RECOOP when MBR contains recorded death.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0003"><data key="node_entity_id">R160_E0003</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RECOOP Title XVI Death Debt Deletion</data><data key="node_domain">Payments / Debt</data><data key="node_description">When a death is recorded on SSR, RECOOP automatically deletes the SSI debt.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0004"><data key="node_entity_id">R160_E0004</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Death Debt TAC N or TAC B Disposition Branch</data><data key="node_domain">Payments / Debt</data><data key="node_description">Title XVI estate debt handling uses TAC N to delete uncollectible debt under conditions; TAC B sends case for field office follow-up with thresholds/exceptions.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0005"><data key="node_entity_id">R160_E0005</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Record Installment Agreement DRIN Screen</data><data key="node_domain">Payments / Debt</data><data key="node_description">DMS screen for restarting billing to surviving or other debtors after death of one individual.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0006"><data key="node_entity_id">R160_E0006</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Transfer Jurisdiction DFTJ Screen</data><data key="node_domain">Payments / Debt</data><data key="node_description">Debt Management System screen used in disability-debtor death routing before terminating collection for deceased debtor.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0007"><data key="node_entity_id">R160_E0007</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Debt Death Reporter Contact Attribute Set</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">Reporter name, address, telephone, and relationship are contact evidence for death reporting; not necessarily beneficiary current residence.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Address role=death reporter contact; origin=third-party allegation; NOT beneficiary verified address.</data></node><node id="R160_E0008"><data key="node_entity_id">R160_E0008</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Death Underpayment Recipient Identity and Address Development</data><data key="node_domain">Title II / Payments</data><data key="node_description">Process for establishing identity, recipient priority, contact address, surviving household spouse relationship and optional direct deposit for a deceased beneficiary underpayment.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0009"><data key="node_entity_id">R160_E0009</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Deceased Underpayment Equal Priority Person Address Set</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">Separate names and mailing addresses for each eligible living recipient in highest priority class; not deceased beneficiary address.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Address subject=potential recipient; separate from deceased beneficiary address; no master-record propagation established.</data></node><node id="R160_E0010"><data key="node_entity_id">R160_E0010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II Death Underpayment Priority Class and Anti-Redistribution Rule</data><data key="node_domain">Title II / Payments</data><data key="node_description">Where a higher statutory priority beneficiary is alive, lower classes cannot receive that share; an unavailable recipient share cannot be distributed to others.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0011"><data key="node_entity_id">R160_E0011</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II Death Underpayment Unlocated Address SPA Hold</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">When a current address cannot be located for a highest-priority recipient, hold that person’s share on the MBR SPA field and record MBR special message.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Holding unpaid share due to address uncertainty does not update the recipient address master.</data></node><node id="R160_E0012"><data key="node_entity_id">R160_E0012</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Returned Death Underpayment Check Incorrect-Address SPA Routing</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">When a death underpayment check returns for wrong address, reissue only if file already shows better address; otherwise retain amount on MBR SPA with special message, without new development.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0013"><data key="node_entity_id">R160_E0013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Foreign Deceased Title II Underpayment DIO PC-8 Jurisdiction</data><data key="node_domain">Title II / External Operations</data><data key="node_description">Foreign death underpayment intake, routing and action performed by DIO Payment Center 8 for beneficiary deceased outside US.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0014"><data key="node_entity_id">R160_E0014</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Foreign SSA-1724 Underpayment Inquiry Versus Claim Test</data><data key="node_domain">Title II / Identity</data><data key="node_description">First written inquiry only becomes claim if qualifying underpayment, identifying information, claimant relationship, no known higher-priority person, and applicant signature/address; later requests can qualify.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0015"><data key="node_entity_id">R160_E0015</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Foreign Death Underpayment Treasury Barred Country Recipient Restriction</data><data key="node_domain">Title II / Payments</data><data key="node_description">Residence of underpayment recipient in Treasury-barred country prevents payment there; otherwise eligible share remains posted on MBR SPA; compliant delivery may occur outside barred country.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0016"><data key="node_entity_id">R160_E0016</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Foreign Death Underpayment Recipient Country-of-Residence Attribute</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">Recipient country of actual residence used to determine payment eligibility and delivery restrictions; not an IRS tax-address update.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Address role=surviving recipient residence for payment jurisdiction; not deceased beneficiary mailing address.</data></node><node id="R160_E0017"><data key="node_entity_id">R160_E0017</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Foreign Death Underpayment 60-Day Equal-Priority Evidence Wait</data><data key="node_domain">Title II / Evidence</data><data key="node_description">When eligible equal-priority foreign recipient proof is requested and not supplied in 60 days, pay proven shares and post unproved unpaid share to MBR SPA.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0018"><data key="node_entity_id">R160_E0018</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Foreign Death Underpayment DIO Role and Threshold Assignment</data><data key="node_domain">Title II / Workload</data><data key="node_description">DIO Benefit Authorizers handle first three priority classes and limited small fourth-sixth claims; Claims Specialists handle larger fourth-sixth claims and legal-representative cases.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0019"><data key="node_entity_id">R160_E0019</data><data key="node_entity_type">form</data><data key="node_canonical_name">Form SSA-559 Underpayment Disposition Routing</data><data key="node_domain">Title II / Evidence</data><data key="node_description">SSA-559 used to record disposition of foreign death underpayment before forwarding to appropriate technician.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0020"><data key="node_entity_id">R160_E0020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Deceased Medicare Premium Refund Payer Attribution Rule</data><data key="node_domain">Medicare / Payments</data><data key="node_description">Premium refund follows actual payer identity: deceased beneficiary, another person, or a third-party payer, with documentary verification as instructed.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0021"><data key="node_entity_id">R160_E0021</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Deceased Medicare Premium Refund Payment-Evidence Threshold</data><data key="node_domain">Medicare / Evidence</data><data key="node_description">Individual alleging premiums paid when SSA record does not confirm payer must provide proof if amount &gt;=$50 or signed statement if below $50.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0022"><data key="node_entity_id">R160_E0022</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Medicare Deceased Premium Direct Billing and T2R A80022 Alerts</data><data key="node_domain">Medicare / Payments</data><data key="node_description">Medicare death-premium refund may be initiated by direct billing system alert or T2R A80022 alert, among other information routes.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0023"><data key="node_entity_id">R160_E0023</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CMS Third-Party Medicare Premium Refund Handling</data><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">CMS handles refunds to third-party payers such as state buy-in or organizational group payer when the third party paid premiums.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0024"><data key="node_entity_id">R160_E0024</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-666 Adjustments in Trust Fund Accounts</data><data key="node_domain">Medicare / Accounting</data><data key="node_description">Manual funding form used to document CMS-to-SSA trust-fund transfer for Medicare premium death underpayments processed in MADCAP or SPS.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0025"><data key="node_entity_id">R160_E0025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CMS to SSA Manual Funding for Medicare Death Premium Refund</data><data key="node_domain">Medicare / Accounting</data><data key="node_description">Manual trust-fund adjustment required when using MADCAP or SPS to process Medicare premium death underpayment refunds.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Financial instruction does not establish software interface or transport architecture.</data></node><node id="R160_E0026"><data key="node_entity_id">R160_E0026</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EDCS MCS Before MSSICS Mainframe Propagation Precedence</data><data key="node_domain">Disability / Person Nexus</data><data key="node_description">If a current MCS claim exists, MCS data propagates ahead of MSSICS and other mainframe data. If none exists, active MSSICS and other source records are used; ABAPs do not propagate.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0027"><data key="node_entity_id">R160_E0027</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EDCS Finally Transmitted Internet Disability Report Intake Gate</data><data key="node_domain">Disability / Evidence</data><data key="node_description">EDCS only propagates Internet Disability Report data after claimant finally transmits report; marks unpropagated reports with submission type and reason in eView.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0028"><data key="node_entity_id">R160_E0028</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EDCS Mainframe Field Overlay of Internet Disability Report</data><data key="node_domain">Disability / Person Nexus</data><data key="node_description">On propagation of Internet Disability Report, corresponding mainframe claim fields override Internet report fields, even when mainframe contains no value.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not treat Internet-reported address or phone as authoritative after mainframe overlay without verification.</data></node><node id="R160_E0029"><data key="node_entity_id">R160_E0029</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EDCS Internet Report Record of Change Prepropagation Snapshot</data><data key="node_domain">Disability / Evidence</data><data key="node_description">EDCS captures ROC snapshot before mainframe and exclusion-page information overwrites propagated Internet report information.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0030"><data key="node_entity_id">R160_E0030</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EDCS Mainframe Correction Then Repropagation Requirement</data><data key="node_domain">Disability / Person Nexus</data><data key="node_description">Most propagated EDCS fields cannot be overwritten; staff must correct source data in MCS/MSSICS or other mainframe record then repropagate, with limited allegation/DLI exceptions.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0031"><data key="node_entity_id">R160_E0031</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EDCS Multiple DIB Mainframe Claims Case Creation Stop</data><data key="node_domain">Disability / Workload</data><data key="node_description">EDCS stops case creation and issues alert when it encounters multiple DIB claims for same claimant; employees resolve mainframe claim problem in MCS.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R160_E0032"><data key="node_entity_id">R160_E0032</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II CDR EDCS Appeal Transfer No Separate POS Input</data><data key="node_domain">Disability / Appeals</data><data key="node_description">2026 CDR reconsideration Title II instructions say separate POS input is no longer necessary; EDCS transfer automatically updates DCF and MBR.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0001"><data key="node_entity_id">R161_E0001</data><data key="node_entity_type">identity_correction_workflow</data><data key="node_canonical_name">Disputed Numident Latest Name Prior-Application Review</data><data key="node_domain">Person / Identity</data><data key="node_description">When applicant denies requesting the latest name recorded in Numident, employee requests microprint of prior SS-5 to determine change origin.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0002"><data key="node_entity_id">R161_E0002</data><data key="node_entity_type">publication_rule</data><data key="node_canonical_name">Automatic Social Security Statement No-Address Exclusion</data><data key="node_domain">Statements / Address</data><data key="node_description">Automatic Statement mailing is suppressed when eligible numberholder has no address available; later mailing can resume if exclusion clears.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0003"><data key="node_entity_id">R161_E0003</data><data key="node_entity_type">privacy_rule</data><data key="node_canonical_name">IRS Written Tax-Administration Request and MBR Routine-Use Gate</data><data key="node_domain">External Exchanges / IRS</data><data key="node_description">IRS tax administration requests require a valid written, signed, purpose-specific request and applicable system-of-records routine use before SSA release.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0004"><data key="node_entity_id">R161_E0004</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">IRS Safeguard Compliance Audit SSA Tax Information Access</data><data key="node_domain">External Exchanges / IRS</data><data key="node_description">IRS may access SSA files containing federal tax return information to audit adherence to Internal Revenue Code safeguards, ordinarily coordinated by Central Office.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0005"><data key="node_entity_id">R161_E0005</data><data key="node_entity_type">treasury_matching_control</data><data key="node_canonical_name">FPLP IRS Match Pending Levy Authorization Indicator</data><data key="node_domain">Payments / External Exchanges</data><data key="node_description">IRS weekly delinquent tax debt submissions identify potential matches to be notified to IRS before Treasury levies payments.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0006"><data key="node_entity_id">R161_E0006</data><data key="node_entity_type">tax_return_information_artifact</data><data key="node_canonical_name">IRS Final Notice Before Levy on Social Security Benefits Image</data><data key="node_domain">Payments / IRS</data><data key="node_description">Final Notice image sent from IRS and stored in SSA On-line Retrieval System for FPLP inquiry; protected federal tax return information.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0007"><data key="node_entity_id">R161_E0007</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">FPLP Notice ORS Section 6103 Use and Disclosure Restriction</data><data key="node_domain">Payments / IRS</data><data key="node_description">IRS final levy notices held in ORS are federal tax return information; only authorized inspection, use or disclosure is permitted.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0008"><data key="node_entity_id">R161_E0008</data><data key="node_entity_type">federal_payment_control</data><data key="node_canonical_name">FPLP Treasury Automated Levy Reversal Signal</data><data key="node_domain">Payments / Treasury</data><data key="node_description">When SSA finds levied payment was not due, SSA systems automatically notify Treasury; Fiscal Service reverses levy without employee manual input.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0009"><data key="node_entity_id">R161_E0009</data><data key="node_entity_type">review_selection_rule</data><data key="node_canonical_name">DQR National Virtual Certified Electronic Folder Review Scope</data><data key="node_domain">Disability / Quality</data><data key="node_description">Any DQR review component may virtually review a CEF case regardless of location; quality reviews are CEF only.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0010"><data key="node_entity_id">R161_E0010</data><data key="node_entity_type">logical_reporting_dataset</data><data key="node_canonical_name">DQR Central Office National Quality Review Results Repository</data><data key="node_domain">Disability / Analytics</data><data key="node_description">DQR quality case-processing results transmitted to Central Office, where stored and used for national quality reports; physical repository not identified.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Logical dataset only; storage technology and transport mechanism not established.</data></node><node id="R161_E0011"><data key="node_entity_id">R161_E0011</data><data key="node_entity_type">statistical_product</data><data key="node_canonical_name">DQR National Quality Review Summary Reports</data><data key="node_domain">Disability / Analytics</data><data key="node_description">National reports produced using quality review results sent to Central Office; available to Commissioner, Congress, other components as requested.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0012"><data key="node_entity_id">R161_E0012</data><data key="node_entity_type">case_processing_rule</data><data key="node_canonical_name">DDS eCDR Four-System Case Closure Requirement</data><data key="node_domain">Disability / CDR</data><data key="node_description">At completion of eCDR, case is closed in DCPS, DDS legacy, eView, and NDDSS; policy does not define automatic interface among all four.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R161_E0013"><data key="node_entity_id">R161_E0013</data><data key="node_entity_type">case_routing_rule</data><data key="node_canonical_name">eCDR Post-Determination Age-Neutral Jurisdiction Selection</data><data key="node_domain">Disability / CDR</data><data key="node_description">DDS eCDR postdetermination routing depends on determination, Title II/XVI type, quality review, needed actions; age no longer routing factor.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0001"><data key="node_entity_id">R162_E0001</data><data key="node_entity_type">certified_data_product</data><data key="node_canonical_name">Certified Payment Extract for Legal Evidence</data><data key="node_domain">Payments / Program Integrity</data><data key="node_description">CPE certifies a record of SSA payment transactions for court, fraud hearing, and other authorized legal uses; the extract is a derived product, not an authoritative payment master.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0002"><data key="node_entity_id">R162_E0002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Certified Payment Extract Production</data><data key="node_domain">Payments / Title II</data><data key="node_description">PSC processing assembles the Title II certified payment extract with certification correspondence for qualifying recipients and time periods.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0003"><data key="node_entity_id">R162_E0003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title XVI Certified Payment Extract Production</data><data key="node_domain">Payments / Title XVI</data><data key="node_description">SSA regional-office process prepares a certified SSI payment extract; routing differs from Title II PSC jurisdiction.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0004"><data key="node_entity_id">R162_E0004</data><data key="node_entity_type">legal_evidence_artifact</data><data key="node_canonical_name">CPE Certification of Extract Sworn Statement</data><data key="node_domain">Payments / Evidence</data><data key="node_description">Certification of extract from SSA records authenticates the payment history as an agency-maintained record for legal use.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0005"><data key="node_entity_id">R162_E0005</data><data key="node_entity_type">document_artifact</data><data key="node_canonical_name">CPE Cover Memorandum and Request Correspondence</data><data key="node_domain">Payments / Evidence</data><data key="node_description">CPE correspondence identifies beneficiary, period, recipient or requesting party, and certifications supporting the extract.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0006"><data key="node_entity_id">R162_E0006</data><data key="node_entity_type">data_selection_rule</data><data key="node_canonical_name">CPE Negotiated-Check Inclusion Control</data><data key="node_domain">Payments / Provenance</data><data key="node_description">CPE payment-history extract includes negotiated checks; returned or otherwise non-negotiated checks are excluded.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0007"><data key="node_entity_id">R162_E0007</data><data key="node_entity_type">third_party_address_attribute</data><data key="node_canonical_name">CPE Financial-Institution Name and Address</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">CPE lists relevant bank name and address when financial institution involved; this is the institution address, not verified beneficiary residence or mailing address.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0008"><data key="node_entity_id">R162_E0008</data><data key="node_entity_type">payment_attribute_rule</data><data key="node_canonical_name">CPE Representative-Payee Change Date Annotation</data><data key="node_domain">Payments / Representative Payee</data><data key="node_description">If the beneficiary identification code involved has payee change, CPE opening narrative must annotate change dates.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0009"><data key="node_entity_id">R162_E0009</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CPE OIG CASI Coordination Route</data><data key="node_domain">Program Integrity / OIG</data><data key="node_description">OIG payment-extract requests route through corresponding PSC Center for Automation, Security and Integrity function, flagged CASI; personnel arrange distribution and requester information.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0010"><data key="node_entity_id">R162_E0010</data><data key="node_entity_type">service_level_policy</data><data key="node_canonical_name">CPE 20-Business-Day Priority Handling Control</data><data key="node_domain">Payments / Disclosure</data><data key="node_description">SSA POMS specifies CPE requests as priority work ordinarily processed within 20 business days of receipt.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0011"><data key="node_entity_id">R162_E0011</data><data key="node_entity_type">evidence_verification_rule</data><data key="node_canonical_name">Prior BIC E C G Insured-Status Evidence Exception</data><data key="node_domain">Title II / Earnings</data><data key="node_description">Prior MBR entitlement as mother, child, or lump-sum-death claimant may rely on currently insured status and cannot alone establish fully insured status; use certified earnings.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0012"><data key="node_entity_id">R162_E0012</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">MCS EARN ECOR to MEF Independent Reconciliation</data><data key="node_domain">Earnings / Person</data><data key="node_description">When MCS EARN or ECOR computation-year entries exist, employees compare DEQY to confirm corresponding MEF update; if absent, initiate authorized MEF correction such as ICOR.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0013"><data key="node_entity_id">R162_E0013</data><data key="node_entity_type">evidence_authorization_rule</data><data key="node_canonical_name">Paid-Entitlement Prior-Proof Reuse Gate</data><data key="node_domain">Person / Evidence</data><data key="node_description">Previously established marriage, divorce, age or death proof may be reused only when proven prior entitlement or accepted proof codes support allegation; contradictions require development.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0014"><data key="node_entity_id">R162_E0014</data><data key="node_entity_type">payment_reissue_control</data><data key="node_canonical_name">Limited-Payability Signed Claimant Reply Control</data><data key="node_domain">Title II / Payments</data><data key="node_description">For specified uncashed check repayment cases, PC requires beneficiary signature on returned LP notice before authorizing new payment and checks Treasury/SSA status.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0015"><data key="node_entity_id">R162_E0015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Incomplete Limited-Payability Reply Processing</data><data key="node_domain">Title II / Payments</data><data key="node_description">Unsigned or ambiguous returned LP notices require specific action: return for signature, request clarification, or file unsigned/no-selection notice in paperless without repayment.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0016"><data key="node_entity_id">R162_E0016</data><data key="node_entity_type">communications_rule</data><data key="node_canonical_name">SSI Limited-Payability Credit Direct Contact Rule</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">SSI does not automatically send the Title II LP notice; staff contact recipient directly when SSI limited-payability credit received.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R162_E0017"><data key="node_entity_id">R162_E0017</data><data key="node_entity_type">privacy_access_rule</data><data key="node_canonical_name">Electronic Privacy Record Request Adult Record-Holder Gate</data><data key="node_domain">Person / Privacy</data><data key="node_description">Online records access requires online identity verification, request by the record holder themselves, and age 18 or older. Requests by representatives use alternative channels.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R162_E0018"><data key="node_entity_id">R162_E0018</data><data key="node_entity_type">data_access_scope</data><data key="node_canonical_name">Electronic Privacy Record Request Four-SORN Scope</data><data key="node_domain">Governance / Person</data><data key="node_description">SSA online privacy request supports eligible records across Claims Folders 60-0089, MBR 60-0090, SSI/SVB 60-0103 and eDIB 60-0320, plus listed decision records; not arbitrary SSA datasets.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R162_E0019"><data key="node_entity_id">R162_E0019</data><data key="node_entity_type">federal_form</data><data key="node_canonical_name">SF-270 Request for Advance or Reimbursement for SSA Grant</data><data key="node_domain">Procurement / Grants</data><data key="node_description">SSA grant guidance identifies SF-270 as interim email request option to financial management analyst while establishing ASAP electronic payment account.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R162_E0020"><data key="node_entity_id">R162_E0020</data><data key="node_entity_type">grant_payment_control</data><data key="node_canonical_name">SSA Grantee ASAP Account Registration Requirement</data><data key="node_domain">Procurement / Grants</data><data key="node_description">SSA grant recipients must establish electronic payments account with Treasury ASAP before drawing grant funds; do not construe ASAP as beneficiary payment system.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R162_E0021"><data key="node_entity_id">R162_E0021</data><data key="node_entity_type">grants_application_rule</data><data key="node_canonical_name">SSA Continuation-Grant GrantSolutions Submission Route</data><data key="node_domain">Procurement / Grants</data><data key="node_description">OAG How Do I Apply states continuation grants enter GrantSolutions under announcement instructions; generic FAQ also says grant applications through Grants.gov, creating a qualification to track.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R162_E0022"><data key="node_entity_id">R162_E0022</data><data key="node_entity_type">grants_application_rule</data><data key="node_canonical_name">SSA Competitive Discretionary Grant Grants.gov Submission Route</data><data key="node_domain">Procurement / Grants</data><data key="node_description">OAG How Do I Apply states competitive discretionary grant application is submitted through Grants.gov, with registration in SAM.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R163_E001"><data key="node_entity_id">R163_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">DDS Disability Decision Data-Entry Exclusion Set</data><data key="node_domain">Disability / Case Control</data><data key="node_description">DDS does not enter disability decisional data when OQR-selected, a no-determination case, adverse reopening, deceased claimant, or prescribed claim-type change. Other exceptions apply by title.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E002"><data key="node_entity_id">R163_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Title II Special Claim Decision-Input Exceptions</data><data key="node_domain">Disability / Title II</data><data key="node_description">DDS does not enter Title II decisional data for prisoner, trial-work, MQGE, totalization, CDR 301 and extended-period-of-eligibility case categories.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E003"><data key="node_entity_id">R163_E003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Title XVI Special Claim Decision-Input Exceptions</data><data key="node_domain">Disability / Title XVI</data><data key="node_description">DDS does not enter Title XVI decisional data in systems-limitation cases, reconsideration reversals, or favorable reopenings.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E004"><data key="node_entity_id">R163_E004</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DDS Intake and Clearance Case-Movement Reporting</data><data key="node_domain">Disability / Case Control</data><data key="node_description">DDS must record receipt, clearance, and case movement; POMS references NDDSS querying and state-variable systems input responsibilities.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E005"><data key="node_entity_id">R163_E005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Whereabouts-Unknown Claimant Location Development</data><data key="node_domain">Disability / Address Provenance</data><data key="node_description">DDS procedures to locate absent claimants using USPS, appointed representatives, designated third parties or FO assistance before evaluating evidence in file.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E006"><data key="node_entity_id">R163_E006</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">DDS Appointed Representative Contact-Update Confirmation Gate</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">An appointed representative may give contact leads, but DDS cannot update DCPS claimant address/telephone without claimant confirmation unless the representative is a parent of a minor or legal guardian.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E007"><data key="node_entity_id">R163_E007</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DDS USPS Whereabouts-Unknown 15-Calendar-Day Response Window</data><data key="node_domain">Disability / Address Provenance</data><data key="node_description">DDS may send Form SSA-L2001 to the postmaster and allow 15 calendar days for a response when locating the claimant.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E008"><data key="node_entity_id">R163_E008</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DDS Field Office Location Request 15-Plus-10 Calendar-Day Follow-up</data><data key="node_domain">Disability / Case Control</data><data key="node_description">DDS may send the FO a DCPS assistance request; wait 15 calendar days, then if unanswered follow up allowing another 10 days, retaining DDS case jurisdiction.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E009"><data key="node_entity_id">R163_E009</data><data key="node_entity_type">address_attribute</data><data key="node_canonical_name">SSA-831 Last-Known Claimant Address for Whereabouts-Unknown Case</data><data key="node_domain">Disability / Address Provenance</data><data key="node_description">When proceeding on available evidence for a whereabouts-unknown case, SSA-831 item 5 holds last known address and item 34 describes whereabouts unknown; not current verified residence.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E010"><data key="node_entity_id">R163_E010</data><data key="node_entity_type">adjudication_control</data><data key="node_canonical_name">DDS Whereabouts-Unknown Nonautomatic-Denial Rule</data><data key="node_domain">Disability / Adjudication</data><data key="node_description">A disability claim cannot receive an unfavorable decision solely because the claimant cannot be located; DDS must evaluate the case using existing evidence.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E011"><data key="node_entity_id">R163_E011</data><data key="node_entity_type">identity_validation_control</data><data key="node_canonical_name">iAppointment Unverified-Data CLIENT Admission Gate</data><data key="node_domain">Person / Identity</data><data key="node_description">iAppt populates eLAS protective filings with UNVER issue. Online data stays isolated from CLIENT until claimant SSN and data verified and Verify PI receipts the issue; it never automatically corrects Numident or Person Information.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E012"><data key="node_entity_id">R163_E012</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">iAppointment eLAS Appointment-Notice Suppression Before Verification</data><data key="node_domain">Person / Privacy</data><data key="node_description">eLAS suppresses confirmation notices for iAppt scheduled appointments, preventing disclosure before the UNVER issue has been resolved.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E013"><data key="node_entity_id">R163_E013</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eLAS Internet Appointment Fifth Calendar Screen</data><data key="node_domain">Customer Service / Scheduling</data><data key="node_description">Fifth calendar screen in eLAS is reserved for iAppt appointments rather than FO/TSC ordinary appointment scheduling.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E014"><data key="node_entity_id">R163_E014</data><data key="node_entity_type">notification_workflow</data><data key="node_canonical_name">iAppointment ASL Interpreter Email Escalation to Area Director</data><data key="node_domain">Customer Service / Accessibility</data><data key="node_description">An ASL selection records a remark and emails FO to schedule an interpreter; undeliverable FO email results in Area Director Office mailbox notification.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E015"><data key="node_entity_id">R163_E015</data><data key="node_entity_type">notice_product</data><data key="node_canonical_name">iAppointment Online Protective Filing Closeout Confirmation</data><data key="node_domain">Claims / Digital Intake</data><data key="node_description">iAppt on-screen confirmation includes protective filing closeout language/date, taking the place of an additional FO closeout notice in stated circumstances.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E016"><data key="node_entity_id">R163_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Pre-August-2026 Pandemic Assistance Special Income Development</data><data key="node_domain">Title XVI / Program Rules</data><data key="node_description">For development initiated before 2026-08-21, SSI staff use special pandemic-assistance income exclusion and documentation procedure including CCE Report of Contact and SSA-5002.</data><data key="node_observed_status">historical_policy</data><data key="node_observed_as_of">2026-08-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E017"><data key="node_entity_id">R163_E017</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI August 21 2026 Pandemic Assistance Development Transition</data><data key="node_domain">Title XVI / Program Rules</data><data key="node_description">Beginning 2026-08-21, SSA no longer routinely asks about or separately documents pandemic assistance for listed new SSI development categories; new allegations follow general disaster-assistance procedures.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-08-21</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E018"><data key="node_entity_id">R163_E018</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">CCE Pandemic Assistance Incorrect-Page Overpayment Risk</data><data key="node_domain">Title XVI / Data Quality</data><data key="node_description">Prior special procedure warns not to post pandemic income on CCE Disaster Assistance page because the action can remove deeming allocations and cause erroneous overpayments; historical context, not assertion about new post-cutover workflow.</data><data key="node_observed_status">historical_policy</data><data key="node_observed_as_of">2026-08-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E019"><data key="node_entity_id">R163_E019</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Pandemic Unemployment Income Exclusion Period Reference Table</data><data key="node_domain">Title XVI / Policy Reference</data><data key="node_description">POMS SI 00830.623 publishes state/territory periods relevant to pandemic unemployment assistance and income exclusion; category timing differs across jurisdictions.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E020"><data key="node_entity_id">R163_E020</data><data key="node_entity_type">historical_control</data><data key="node_canonical_name">August 2021 SSI Computations Pandemic Unemployment Automatic Exclusion Change</data><data key="node_domain">Title XVI / Modernization History</data><data key="node_description">POMS documents August 2021 changes to CCE/SSI Computations that automated exclusion for covered pandemic unemployment and obviated related corrective steps.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2021-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E021"><data key="node_entity_id">R163_E021</data><data key="node_entity_type">verification_rule</data><data key="node_canonical_name">AFI Negative Account Search and Historical 25-Month Verification Control</data><data key="node_domain">Title XVI / Resource Verification</data><data key="node_description">When AFI verification is required, negative searches and balance verification up to 25 past months can remain necessary even if claimant supplied alternative evidence.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E022"><data key="node_entity_id">R163_E022</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">SSI Financial Account Alternate Evidence Preference Hierarchy</data><data key="node_domain">Title XVI / Evidence</data><data key="node_description">Accept bank statements first, other financial institution records second, claimant signed statement as last resort when AFI/e4641 not used; electronic Upload Documents statements can qualify.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E023"><data key="node_entity_id">R163_E023</data><data key="node_entity_type">person_relationship_rule</data><data key="node_canonical_name">Financial Account Ownership Versus SSI Countability Control</data><data key="node_domain">Person / Financial Attribution</data><data key="node_description">Account title and ability to withdraw or use funds determine presumed resources, subject to ownership and legal restrictions; being associated with an account or named POD beneficiary is not dispositive.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E024"><data key="node_entity_id">R163_E024</data><data key="node_entity_type">form</data><data key="node_canonical_name">Form SS-5-FS Application for Social Security Card Outside the United States</data><data key="node_domain">Enumeration / Forms</data><data key="node_description">SSA Forms catalog lists SS-5-FS as the paper application for a card outside the United States; this catalog entry does not establish an online application route.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E025"><data key="node_entity_id">R163_E025</data><data key="node_entity_type">form</data><data key="node_canonical_name">Form CMS-1763 Request for Medicare Premium Coverage Termination</data><data key="node_domain">Medicare / Forms</data><data key="node_description">SSA Forms catalog links CMS-1763 for termination of premium Part A, Part B, or Part B immunosuppressive drug coverage; CMS-origin PDF, not evidence of SSA-hosted e-form.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R163_E026"><data key="node_entity_id">R163_E026</data><data key="node_entity_type">publication_catalog</data><data key="node_canonical_name">OACT Public Actuarial Publications Index</data><data key="node_domain">Actuarial / Publication Pipelines</data><data key="node_description">OACT public navigation lists trustees reports, SSI annual reports, program-change estimates, actuarial notes/studies, fact sheets and statistical tables; only a public index, not an inferred internal data pipeline.</data><data key="node_observed_status">policy_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R164_E001"><data key="node_entity_id">R164_E001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title XVI Representative Fee Direct-Payment Eligibility Reconciliation</data><data key="node_domain">representation</data><data key="node_description">Before effectuation, employees reconcile principal representative and fee status across SSR and RASR.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, C.1-C.3. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E002"><data key="node_entity_id">R164_E002</data><data key="node_entity_type">query_service</data><data key="node_canonical_name">RASR EDPNA Direct-Payment Eligibility Query</data><data key="node_domain">representation</data><data key="node_description">RASR query used to confirm nonattorney representative eligibility for direct payment as of effectuation. Not an independent master identity store.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, C.2.b-C.2.d. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E003"><data key="node_entity_id">R164_E003</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS UMEN Appointed Representative Processing Screen</data><data key="node_domain">Title XVI</data><data key="node_description">Screen used with UATH and UFEE to code representative-related Title XVI information to SSR.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, C.1. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E004"><data key="node_entity_id">R164_E004</data><data key="node_entity_type">data_segment</data><data key="node_canonical_name">SSR Overpayment Decision Data OPDD Segment</data><data key="node_domain">Title XVI debt</data><data key="node_description">SSR segment holding collection decisions; certain prior-overpayment decisions must be removed and later reposted during fee withholding.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, C.4.b,C.4.d. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E005"><data key="node_entity_id">R164_E005</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Title XVI Fee Petition 60-Day or 120-Day Follow-up Diary</data><data key="node_domain">representation</data><data key="node_description">Fee petition follow-up is 60 days for administrative decision and 120 days for federal-court decision; processing center handles applicable concurrent cases.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, B,C.4,C.7. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E006"><data key="node_entity_id">R164_E006</data><data key="node_entity_type">transaction_alert</data><data key="node_canonical_name">SSR I9 Alert Requiring IAR Payment by OTP</data><data key="node_domain">Title XVI payments</data><data key="node_description">I9 alert is generated when qualifying IAR underpayment review requires one-time state reimbursement processing.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, C.4.c. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E007"><data key="node_entity_id">R164_E007</data><data key="node_entity_type">business_control</data><data key="node_canonical_name">SSI Fee-Petition Prior-Overpayment Reposting Diary</data><data key="node_domain">Title XVI debt</data><data key="node_description">Removing applicable older collect decisions from OPDD establishes a diary reminding staff to repost the prior decision.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, C.4.b,C.4.d. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E008"><data key="node_entity_id">R164_E008</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">Title XVI Representative Fee Notice Minimum-Necessary Disclosure Control</data><data key="node_domain">representation</data><data key="node_description">Notice disclosure limits apply to former representatives, fee-assignment entity contacts, eligible spouses, and payees; ordinary protected claimant material requires appropriate authority.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, B,C.5-C.6. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E009"><data key="node_entity_id">R164_E009</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSR Representative Eligibility for Direct Payment Attribute</data><data key="node_domain">Title XVI</data><data key="node_description">SSR must reflect principal representative identity and eligibility for direct payment; RASR appointment and waiver must be checked.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, C.1. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E010"><data key="node_entity_id">R164_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title XVI Representative Fee Petition and IAR Withholding Exception Workflow</data><data key="node_domain">Title XVI payments</data><data key="node_description">Withholding/offset behavior depends on interim assistance reimbursement, concurrent Title II benefits, overpayments and prior collect decisions.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S001, C.4.a-C.4.d. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E011"><data key="node_entity_id">R164_E011</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Disability Reopening Administrative Finality and Authority Hierarchy</data><data key="node_domain">disability appeals</data><data key="node_description">Reopening depends on finality, timely grounds and adjudicative jurisdiction: DDS/DHU/ALJ/Appeals Council and FO/PC have different authority.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S002, A,B.2-B.3. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E012"><data key="node_entity_id">R164_E012</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Disability Reopening Prior-Folder Retrieval Prerequisite</data><data key="node_domain">disability evidence</data><data key="node_description">Generally obtain prior folders before reopening, with published exceptions for missing paper folders.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S002, B.2 notes. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E013"><data key="node_entity_id">R164_E013</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Adverse Medical Reopening Medical Improvement Review Standard Gate</data><data key="node_domain">disability appeals</data><data key="node_description">MIRS generally governs revisions from favorable disability decisions to adverse denial/cessation, with stated exceptions. Not used to revise onset dates alone.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S002, B.4. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E014"><data key="node_entity_id">R164_E014</data><data key="node_entity_type">process</data><data key="node_canonical_name">Disability Reopening Due Process and Notice Workflow</data><data key="node_domain">disability appeals</data><data key="node_description">Adverse reopenings require opportunity to submit evidence, revised rationale, notices and the appropriate appeal rights.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S002, D.1-D.3. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E015"><data key="node_entity_id">R164_E015</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-553 Special Determination for Denied Reopening</data><data key="node_domain">disability appeals</data><data key="node_description">SSA permits form SSA-553 or electronic writing (RPOC, DW01) to document reasons for denying a reopening request; do not add appeal rights to that denial notice.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S002, D.4. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E016"><data key="node_entity_id">R164_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Reopening Denial Notification Without Appeal Right</data><data key="node_domain">disability appeals</data><data key="node_description">When SSA declines to reopen, it documents reasons and notifies individual of outcome without providing reopening denial appeal rights.</data><data key="node_observed_status">published_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S002, D.4. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E017"><data key="node_entity_id">R164_E017</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 OASI Trustees Short-Range Operations Table IV.A1</data><data key="node_domain">actuarial statistics</data><data key="node_description">Annual historical/projection table for OASI trust fund income, cost, reserve and trust fund ratio by alternate economic assumption.</data><data key="node_observed_status">2026_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S003, Table IV.A1. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E018"><data key="node_entity_id">R164_E018</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 DI Trustees Short-Range Operations Table IV.A2</data><data key="node_domain">actuarial statistics</data><data key="node_description">Annual historical/projection table for DI trust fund operations and projected reserves under three sets of assumptions.</data><data key="node_observed_status">2026_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S003, Table IV.A2. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E019"><data key="node_entity_id">R164_E019</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Combined OASDI Trustees Short-Range Table IV.A3</data><data key="node_domain">actuarial statistics</data><data key="node_description">Annual projection table for combined trust funds, published as hypothetical combined balances and income/cost estimates.</data><data key="node_observed_status">2026_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S003, Table IV.A3. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R164_E020"><data key="node_entity_id">R164_E020</data><data key="node_entity_type">actuarial_method</data><data key="node_canonical_name">OASDI Short-Range Financial Adequacy 100-Percent Trust-Fund-Ratio Test</data><data key="node_domain">actuarial statistics</data><data key="node_description">Trust fund ratio must meet published short-range criteria: where under 100%, reach 100% in five years without depletion and remain there for rest of ten-year span.</data><data key="node_observed_status">2026_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-10-10 observed. Evidence: R164_S003, IV.A preamble. Models a documented public policy/data-product concept; physical architecture not inferred.</data></node><node id="R165_E001"><data key="node_entity_id">R165_E001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Section 216(h)(3) Written-Acknowledgment Parent-Child Determination</data><data key="node_domain">Title II / Person / Identity</data><data key="node_description">Adjudicator evaluates an NH written acknowledgment identifying a biological child, subject to lifetime, biological relationship and evidence rules.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section A-B; observed 2026-10-10. Entitlement proof process, not universal parent identity master.</data></node><node id="R165_E002"><data key="node_entity_id">R165_E002</data><data key="node_entity_type">evidence_artifact</data><data key="node_canonical_name">Parent-Child Acknowledgment Electronic Writing Evidence</data><data key="node_domain">Title II / Evidence</data><data key="node_description">Emails, text messages and social media writings can count as written acknowledgment when attribution to the NH is adequately established.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section B-C; observed 2026-10-10. Electronic writings are possible claimant evidence, not an SSA inbound integration.</data></node><node id="R165_E003"><data key="node_entity_id">R165_E003</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS DEPC Dependent Children of Number Holder Screen</data><data key="node_acronym">DEPC</data><data key="node_domain">Title II / MCS</data><data key="node_description">MCS dependent-children screen can establish NH acknowledgment when authenticated as the NH application under POMS conditions.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section C.5; observed 2026-10-10. MCS listing alone can be insufficient without APPL/RMKS conditions.</data></node><node id="R165_E004"><data key="node_entity_id">R165_E004</data><data key="node_entity_type">evidence_artifact</data><data key="node_canonical_name">eLAS Parent-Child Claim Appointment Written-Acknowledgment Evidence</data><data key="node_domain">Title II / eLAS / Identity</data><data key="node_description">Appointment record identifying NH contact and named child may protect date of NH written acknowledgment.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section G; observed 2026-10-10. Only when the policy conditions for identity, intent and child identification are met.</data></node><node id="R165_E005"><data key="node_entity_id">R165_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Parent-Child Written-Acknowledgment Effective Date Control</data><data key="node_domain">Title II / Eligibility</data><data key="node_description">Parent-child relationship based on written acknowledgment generally begins on the acknowledgment date unless evidence supports an earlier date.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section F; observed 2026-10-10. Not equivalent to child birth date or entire retroactive benefit period.</data></node><node id="R165_E006"><data key="node_entity_id">R165_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Section 216(h)(3) Biological Parentage Conflict Development</data><data key="node_domain">Title II / Evidence</data><data key="node_description">Staff develop additional parentage evidence if full birth certificate, EAB iteration or other information conflicts with biological relationship.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section D-E; observed 2026-10-10. Unresolved parentage can require a legal opinion; not automatic SSA record correction.</data></node><node id="R165_E007"><data key="node_entity_id">R165_E007</data><data key="node_entity_type">evidence_artifact</data><data key="node_canonical_name">Claimant-Supplied Dependent-Child Tax Return Parentage Evidence</data><data key="node_domain">Title II / Tax Data / Identity</data><data key="node_description">Copy of NH federal or state income tax return listing child as dependent can evidence written acknowledgment.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section C.4; observed 2026-10-10. Policy says IRS and state tax offices do not provide copies of tax returns to SSA in this workflow; no automated tax integration inferred.</data></node><node id="R165_E008"><data key="node_entity_id">R165_E008</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-2519 Child Relationship Statement</data><data key="node_acronym">SSA-2519</data><data key="node_domain">Title II / Forms</data><data key="node_description">Child Relationship Statement form used to identify potential sources of written acknowledgment and relationships.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section C / references; observed 2026-10-10. Listing/use of form only; submission technology not inferred.</data></node><node id="R165_E009"><data key="node_entity_id">R165_E009</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">No Routine IRS or State Tax-Office Return Supply for Child Written-Acknowledgment Evidence</data><data key="node_domain">IRS / Person Evidence Provenance</data><data key="node_description">For this parentage evidence workflow SSA policy says tax offices do not furnish requested income-tax-return copies to SSA; applicants may supply copies.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S001 section C.4; observed 2026-10-10. Scope is this workflow; does not negate other legally authorized IRS-SSA tax data exchanges.</data></node><node id="R165_E010"><data key="node_entity_id">R165_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Nonmarital Child EAB Birth Registration Parentage Presumption</data><data key="node_domain">Title II / Enumeration</data><data key="node_description">Uses qualifying EAB Numident parent attributes or complete birth certificate, under state law, to presume written acknowledgment or paternity order.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R56_011 section A-B; observed 2026-10-10. Only section 216(h)(3) non-marital children and specified documentary/state-law conditions.</data></node><node id="R165_E011"><data key="node_entity_id">R165_E011</data><data key="node_entity_type">policy_data_table</data><data key="node_canonical_name">State-Law Nonmarital Birth Registration Paternity Effective-Date Matrix</data><data key="node_domain">Title II / State Law</data><data key="node_description">POMS chart of jurisdictions, whether paternal written consent/court determination required for birth registration and state-specific effective dates.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R56_011 section B.1; observed 2026-10-10. Published policy reference table, not operational SSA database.</data></node><node id="R165_E012"><data key="node_entity_id">R165_E012</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Birth Certificate Number Holder Informant Signature</data><data key="node_domain">Title II / Vital Records</data><data key="node_description">NH signature as informant with NH listed as parent on full birth certificate may establish written acknowledgment.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R56_011 section A.1.a; observed 2026-10-10. Applies only under cited parent-child procedure.</data></node><node id="R165_E013"><data key="node_entity_id">R165_E013</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EAB Numident Parent-Name Subsequent-Iteration Consistency Check</data><data key="node_domain">Person / Numident / Evidence</data><data key="node_description">Use of EAB MNA/FNA data for parentage requires absence of a different parent name on later Numident iterations under policy.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R56_011 section A.2; observed 2026-10-10. Does not imply changing or back-propagating later Numident attributes.</data></node><node id="R165_E014"><data key="node_entity_id">R165_E014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Certified Court Parentage Order Evidence Intake</data><data key="node_domain">Title II / Evidence / Courts</data><data key="node_description">Employee obtains certified decree/order, verifies supersession questions and submits evidence to NDRed using Evidence Portal.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S002 section C.1; observed 2026-10-10. Evidence routing documented; automated court-to-SSA connection not established.</data></node><node id="R165_E015"><data key="node_entity_id">R165_E015</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Posthumous Parentage Court Order Section 216(h)(3) Exclusion</data><data key="node_domain">Title II / Courts / Eligibility</data><data key="node_description">Court decree or support order must have been made during NH lifetime for this federal-standard pathway; other State-law/other evidence routes may apply.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S002 section A; observed 2026-10-10. Limited to specific child-entitlement pathway.</data></node><node id="R165_E016"><data key="node_entity_id">R165_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Section 216(h)(3) Court-Order Biological Parentage Review</data><data key="node_domain">Title II / Courts / Evidence</data><data key="node_description">Adjudicator reviews certified court decree or support order naming NH/identifiable child, biological relationship and potential inconsistencies.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S002 section A-B; observed 2026-10-10. Legal evidence adjudication, not direct court database synchronization.</data></node><node id="R165_E017"><data key="node_entity_id">R165_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CMS Third-Party Buy-In Health Insurance Master Identity Matching Gate</data><data key="node_domain">Medicare / CMS / Identity</data><data key="node_description">Before State buy-in accretion posts to Third-Party Master, the submitted claim number and demographics must match Medicare Health Insurance Master data.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S003 section B; observed 2026-10-10. CMS Medicare master identity match, not SSA Numident master update.</data></node><node id="R165_E018"><data key="node_entity_id">R165_E018</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">CMS Monthly SSI Buy-In Accretion Alert Record</data><data key="node_domain">Medicare / CMS / States</data><data key="node_description">CMS supplies qualifying informational SSI accretion alerts each month to alert States for Medicaid/Medicare buy-in actions.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S003 section A; observed 2026-10-10. Monthly informational alert, not proof of a successful State accretion.</data></node><node id="R165_E019"><data key="node_entity_id">R165_E019</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">CMS Monthly SSI Buy-In Deletion Alert Record</data><data key="node_domain">Medicare / CMS / States</data><data key="node_description">CMS generates informational deletion alerts to alert States when SSI terminates while an individual remains on buy-in.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S003 section C; observed 2026-10-10. Only defined alert-state and responsibility contexts.</data></node><node id="R165_E020"><data key="node_entity_id">R165_E020</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">CMS State Buy-In Accretion-Deletion Transaction Response Record</data><data key="node_domain">Medicare / CMS / States</data><data key="node_description">CMS Third-Party System issues acknowledgment, reject or interim investigation response for State-initiated accretions/deletions.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S003 section E; observed 2026-10-10. Some exceptions produce a paper record instead of electronic response.</data></node><node id="R165_E021"><data key="node_entity_id">R165_E021</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">CMS State Buy-In Two-Month Retroactive Deletion Limit</data><data key="node_domain">Medicare / CMS / Payments</data><data key="node_description">Buy-in deletion effective date is limited to two months before receipt; system adjusts older requested dates.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S003 section D; observed 2026-10-10. Applies State deletion requests under current described policy.</data></node><node id="R165_E022"><data key="node_entity_id">R165_E022</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">CMS State Buy-In Medicare Entitlement-Date Alignment</data><data key="node_domain">Medicare / CMS / Eligibility</data><data key="node_description">Third-Party System automatically adjusts State buy-in start to Medicare entitlement date when submitted buy-in starts earlier.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S003 section F; observed 2026-10-10. Limited to stated conditions; no global entitlement/date synchronization.</data></node><node id="R165_E023"><data key="node_entity_id">R165_E023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SAVE Single-Character Given or Family Name Discrepancy Tolerance</data><data key="node_domain">DHS / SAVE / Person</data><data key="node_description">SSA may accept a one-character name discrepancy between SAVE response and presented documents when this is the only discrepancy, subject to exceptions.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R119_001 section C.5.b; observed 2026-10-10. Transpositions, omitted/extra characters and contradictory evidence do not automatically qualify.</data></node><node id="R165_E024"><data key="node_entity_id">R165_E024</data><data key="node_entity_type">data_quality_constraint</data><data key="node_canonical_name">SAVE Response Middle-Name Display Omission</data><data key="node_domain">DHS / SAVE / Person</data><data key="node_description">SSA SAVE screen cannot display middle name or initial; difference from immigration document is not by itself a verification discrepancy.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R119_001 section C.5.b; observed 2026-10-10. UI display limitation does not establish that DHS source record lacks middle names.</data></node><node id="R165_E025"><data key="node_entity_id">R165_E025</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SAVE Standalone SSN Discrepancy Acceptance for Claim Verification</data><data key="node_domain">DHS / SAVE / Person</data><data key="node_description">Where SSN line is the only discrepant field in an online SAVE response, current POMS requires no further action on that discrepancy.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R119_001 section C.5.b; observed 2026-10-10. Not proof that mismatched SSN belongs to individual and not permission to update Numident.</data></node><node id="R165_E026"><data key="node_entity_id">R165_E026</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Suspected Fraudulent DHS Document Manual G-845 Verification Path</data><data key="node_domain">DHS / SAVE / Fraud</data><data key="node_description">If submitted immigration document appears fraudulent, SSA follows manual G-845 verification rather than using online SAVE as proof and may refer suspected fraud to OIG.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R119_001 section C.3-C.4; observed 2026-10-10. Restricted to suspect-document scenario; not an assertion of automatic fraud classification.</data></node><node id="R165_E027"><data key="node_entity_id">R165_E027</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CMS State Buy-In Interim Response Investigation and Paper Exception</data><data key="node_domain">Medicare / CMS / States</data><data key="node_description">CMS may issue interim transaction response pending electronic or clerical investigation and occasionally a paper disposition response.</data><data key="node_observed_status">published_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R165_S003 section E; observed 2026-10-10. Specific disposition pathway, no transport format or database design inferred.</data></node><node id="R166_E001"><data key="node_entity_id">R166_E001</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">EDCS SSA-3367 Field Office Disability Report</data><data key="node_domain">Disability / EDCS</data><data key="node_description">Electronic Disability Collect System 3367 report required before FO transfers claim jurisdiction to DDS or OHO.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section preamble and section A. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E002"><data key="node_entity_id">R166_E002</data><data key="node_entity_type">form</data><data key="node_canonical_name">Paper SSA-3367 Field Office Disability Report</data><data key="node_domain">Disability / Intake</data><data key="node_description">Paper alternative used for EDCS exclusions including expedited reinstatement; one complete report for qualifying concurrent exclusions.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section preamble and A. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E003"><data key="node_entity_id">R166_E003</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EDCS 3367 Alleged Onset Date Mainframe-Propagated Attribute</data><data key="node_domain">Disability / Source Precedence</data><data key="node_description">AOD propagates from MCS or MSSICS to EDCS 3367 and normally cannot be manually overwritten; corrections originate in mainframe.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.1.b. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E004"><data key="node_entity_id">R166_E004</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">EDCS 3367 Potential Onset Date Claim-Specific Attribute</data><data key="node_domain">Disability / Intake</data><data key="node_description">Claim-specific potential onset date is editable on EDCS 3367, including at successive Title II levels subject to procedural restrictions.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.1.c. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E005"><data key="node_entity_id">R166_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Field Office 3367 Completion Before Disability Case Transfer</data><data key="node_domain">Disability / Jurisdiction</data><data key="node_description">FO completes paper or electronic SSA-3367 prior to DDS or OHO jurisdiction transfer.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section preamble. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E006"><data key="node_entity_id">R166_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS Alleged Onset Date Correction at Origin and Repropagation</data><data key="node_domain">Disability / Data Quality</data><data key="node_description">For established MCS/MSSICS claim, employee corrects AOD in originating program application and then repropagates to EDCS.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.1.b. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E007"><data key="node_entity_id">R166_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS Onset Date Post-Transfer DDS Update Notification</data><data key="node_domain">Disability / Jurisdiction</data><data key="node_description">After transfer to DDS, AOD changes require Update After Transfer utility to notify DDS.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.1.b. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E008"><data key="node_entity_id">R166_E008</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II EDCS 3367 Potential Onset Date Level-by-Level Completion</data><data key="node_domain">Title II / Disability</data><data key="node_description">FO enters claim-specific POD for initial, reconsideration, hearings and escalated Title II cases before transfer; not entry at Appeals Council or federal court level.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.1.c. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E009"><data key="node_entity_id">R166_E009</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title XVI EDCS 3367 Conditional Potential Onset Date Entry</data><data key="node_domain">Title XVI / Disability</data><data key="node_description">FO enters POD for Title XVI on SSA-3367 only when POD differs from protective filing date or filing date.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.1.c. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E010"><data key="node_entity_id">R166_E010</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">SSA-3367 Number Holder Versus Claimant Identifying Attributes</data><data key="node_domain">Person / Disability</data><data key="node_description">Form separately records NH and claimant name/SSN, with claimant sex and DOB where different, such as auxiliary or survivor disability claim.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.1.a. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E011"><data key="node_entity_id">R166_E011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS 3367 Prior Certified Electronic Folder Filing Propagation</data><data key="node_domain">Disability / History</data><data key="node_description">When EDCS creates CEF for a new initial claim, prior CEF filing information automatically populates the EDCS 3367.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.3. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E012"><data key="node_entity_id">R166_E012</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">EDCS 3367 Prior-Filing Claim and Decision Metadata</data><data key="node_domain">Disability / History</data><data key="node_description">Records prior claim type and SSNs, last decision date, adjudicative level and outcome, earlier folder location and folder-request state.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.3. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E013"><data key="node_entity_id">R166_E013</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EDCS 3367 Prior Disability Termination Failure-to-Cooperate Alert</data><data key="node_domain">Disability / History</data><data key="node_description">FO flags prior disability termination for failure to cooperate so DDS receives the relevant case development warning.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.3. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E014"><data key="node_entity_id">R166_E014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA-3367 Alleged-Onset Discrepancy Claimant Reconciliation</data><data key="node_domain">Disability / Intake</data><data key="node_description">If application and disability report have conflicting alleged onset dates, FO resolves conflict with claimant and records reason in 3367 remarks.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S001, section A.1.b. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E015"><data key="node_entity_id">R166_E015</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS 3367 Miscellaneous DWB and Prior Filing Information Page</data><data key="node_domain">Disability / EDCS</data><data key="node_description">EDCS input page records protective filing date, DLI, DWB dates, and previous filings; user can add prior entries.</data><data key="node_observed_status">documented_2024_transmittal_historical_revision</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Original revision 2014; specific operation not independently proven as of 2026. Source R166_S003, section A.2. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E016"><data key="node_entity_id">R166_E016</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS 3367 Onset and Potential-Onset-Reason Pages</data><data key="node_domain">Disability / EDCS</data><data key="node_description">EDCS 3367 pages identify alleged and potential onset dates and reason for potential onset recommendation.</data><data key="node_observed_status">documented_2024_transmittal_historical_revision</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Source R166_S003, section A.1. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E017"><data key="node_entity_id">R166_E017</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS 3367 Presumptive Disability and Blindness Page</data><data key="node_domain">Title XVI / Disability</data><data key="node_description">EDCS 3367 has SSI presumptive disability/blindness page; documented entry condition requires Title XVI claim in EDCS case.</data><data key="node_observed_status">documented_2024_transmittal_historical_revision</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Source R166_S003, section A.3. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E018"><data key="node_entity_id">R166_E018</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Hearings In-Line Quality Review Fee-Agreement Administrative Review</data><data key="node_domain">Hearings / Representation</data><data key="node_description">Hearings ILQR handles fee-agreement review for cases favorably decided at hearings and Appeals Council levels.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S002, section A.1. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E019"><data key="node_entity_id">R166_E019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Fee Agreement Review Request Electronic B-Section Routing</data><data key="node_domain">Hearings / Evidence</data><data key="node_description">If eView or ENM record exists, receiving component uploads request to B section and emails competent reviewing authority; without record, scan and email attachment, confirm receipt.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S002, section A. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E020"><data key="node_entity_id">R166_E020</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Fee Agreement Review Notice Document and Distribution</data><data key="node_domain">Hearings / Representation</data><data key="node_description">Administrative-review determination notice distributed to requester, other authorized parties and fee decision maker; eView B-section copy when electronic file exists.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S002, section F.1-F.2. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E021"><data key="node_entity_id">R166_E021</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Fee Review Third-Party Claimant and Auxiliary Address Redaction</data><data key="node_domain">Address Provenance / Privacy</data><data key="node_description">Copies to parties lacking disclosure authority must redact claimant or auxiliary beneficiary address, SSN, and protected notice identifiers.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S002, section C.2 / D.1 / F.2. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E022"><data key="node_entity_id">R166_E022</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Fee Review eView Decision Upload Automatic FO-PC Alert</data><data key="node_domain">Hearings / Notifications</data><data key="node_description">SSA HALLEX states uploading fee-review determination to eView alerts field/processing centers through EDCS and Evidence Portal applications; no second manual notification.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S002, section F.2. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E023"><data key="node_entity_id">R166_E023</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Fee Review No Electronic Folder Manual Notification Fallback</data><data key="node_domain">Hearings / Records</data><data key="node_description">When eView upload impossible or only paper/ENM folder exists, reviewer uses claim file and appropriate PC control mailbox for notification.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S002, section F.2. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E024"><data key="node_entity_id">R166_E024</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Fee Agreement Review Thirty-Day Diary and Fifteen-Day Response Window</data><data key="node_domain">Hearings / Representation</data><data key="node_description">Parties have 15 days to provide comments; office diaries review for 30 days. Late-filing explanation uses 15-day reply with 30-day follow-up.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R166_S002, section C.1 / D.1. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E025"><data key="node_entity_id">R166_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Representative Payee Capability Medical Evidence Routing</data><data key="node_domain">Representative Payee / Evidence</data><data key="node_description">SSA policy requires evidence in NDRed under claim number or eView under beneficiary own account number, using Evidence Portal or eView.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC006, section A opening, A.5. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E026"><data key="node_entity_id">R166_E026</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eRPS Medical Evidence Authenticity Report-of-Contact</data><data key="node_domain">Representative Payee / Integrity</data><data key="node_description">When capability medical evidence authenticity requires verification and eRPS case exists, document medical-source confirmation in Beneficiary Details RPOC.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC006, section A.5.a. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E027"><data key="node_entity_id">R166_E027</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">DDS Capability Opinion Versus FO Payee-Capability Determination</data><data key="node_domain">Disability / Representative Payee</data><data key="node_description">DDS may provide capability opinion on SSA-831/832/833, but FO rather than DDS decides whether beneficiary can manage benefits.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC006, section A.8. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E028"><data key="node_entity_id">R166_E028</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Representative Payee Capability Medical Evidence Recency Rule</data><data key="node_domain">Representative Payee / Evidence</data><data key="node_description">Recent medical evaluation evidence within one year is requested when applicable; qualifying older existing evidence can be considered if no recent examination.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC006, section A.2. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E029"><data key="node_entity_id">R166_E029</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eView Claimant SSN Versus Number Holder SSN Case Search</data><data key="node_domain">Person / Disability</data><data key="node_description">eView permits searches by claimant own SSN or number holder SSN in auxiliary disability claims; results not restricted by geographic jurisdiction.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC018, section A / B. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R166_E030"><data key="node_entity_id">R166_E030</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eView EDCS Folder Number Unique-Case Search</data><data key="node_domain">Disability / Folder Identification</data><data key="node_description">eView permits EDCS folder-number search selecting one specific case even when an SSN has multiple filings.</data><data key="node_observed_status">documented_policy_control</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC018, section A / B. Observed 2026-10-10. Do not infer physical storage or automatic cross-system update.</data></node><node id="R167_E001"><data key="node_entity_id">R167_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">IEDS MCS Earnings Computation Exclusion</data><data key="node_domain">Title II / Claims</data><data key="node_description">Independently entitled divorced spouse claims require manual MCS A-101/DOFA and MADCAP rather than normal MCS earnings computation path.</data><data key="node_observed_status">documented_2025_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative RS 00202.100 Independently Entitled Divorced Spouse, section B.6; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E002"><data key="node_entity_id">R167_E002</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">IEDS Unsigned SSA-1 Number Holder Information Intake</data><data key="node_domain">Title II / Person Identity</data><data key="node_description">Claimant may complete selected SSA-1 questions about nonfiling number holder; do not sign; fax to NDRed via Evidence Portal and verify receipt before paper destruction.</data><data key="node_observed_status">documented_2025_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative RS 00202.100 Independently Entitled Divorced Spouse, section B.2; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E003"><data key="node_entity_id">R167_E003</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">IEDS Reciprocal Former-Spouse Whereabouts Non-Disclosure</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">SSA must not divulge either nonfiling number holder whereabouts to divorced-spouse claimant or claimant whereabouts to number holder.</data><data key="node_observed_status">documented_2025_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative RS 00202.100 Independently Entitled Divorced Spouse, section B.4.a; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E004"><data key="node_entity_id">R167_E004</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">IEDS Employer Address Lead Five-Year Eligibility</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">When nonfiling number holder cannot be found, field office may contact an employer identified in SSA records if NH worked there within five years to seek an address; address lead does not itself authorize master-record update.</data><data key="node_observed_status">documented_2025_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative RS 00202.100 Independently Entitled Divorced Spouse, section B.4.b; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E005"><data key="node_entity_id">R167_E005</data><data key="node_entity_type">verification_workflow</data><data key="node_canonical_name">IEDS ICERS Certified Earnings Record Insured-Status Review</data><data key="node_domain">Title II / Earnings</data><data key="node_description">For independently entitled divorced spouse claims, use certified E/R function in ICERS for insured status and PIA computation.</data><data key="node_observed_status">documented_2025_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative RS 00202.100 Independently Entitled Divorced Spouse, section B.5; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E006"><data key="node_entity_id">R167_E006</data><data key="node_entity_type">claims_exception_workflow</data><data key="node_canonical_name">IEDS MCS A101 DOFA MADCAP Manual Effectuation</data><data key="node_domain">Title II / Payments</data><data key="node_description">Allowed IEDS auxiliary claim loads in MCS, is adjudicated via A-101, manually processes DOFA, and carries A101 remarks requesting MADCAP processing.</data><data key="node_observed_status">documented_2025_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative RS 00202.100 Independently Entitled Divorced Spouse, section B.6.a; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E007"><data key="node_entity_id">R167_E007</data><data key="node_entity_type">claims_exception_workflow</data><data key="node_canonical_name">IEDS Number Holder Death Manual Survivor Conversion</data><data key="node_domain">Title II / Survivors</data><data key="node_description">When number holder dies before entitlement in specified IEDS cases, send proof of death and record of contact to payment center to manually convert to surviving divorced spouse benefits.</data><data key="node_observed_status">documented_2025_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative RS 00202.100 Independently Entitled Divorced Spouse, section B.5.f; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E008"><data key="node_entity_id">R167_E008</data><data key="node_entity_type">identity_verification_workflow</data><data key="node_canonical_name">IEDS Nonfiling Number Holder Identity and Evidence Development</data><data key="node_domain">Title II / Person Identity</data><data key="node_description">Field office obtains number holder SSN, proof of age or disability where material; absent proof or whereabouts, claim can be disallowed under prescribed conditions.</data><data key="node_observed_status">documented_2025_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative RS 00202.100 Independently Entitled Divorced Spouse, section B.1-B.4; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E009"><data key="node_entity_id">R167_E009</data><data key="node_entity_type">documented_exchange_behavior</data><data key="node_canonical_name">VA SSR Dependent-Benefit Portion Interface Posting</data><data key="node_domain">Title XVI / Federal Exchanges</data><data key="node_description">SSA VA/SSR interface posts and updates certain VA benefits portions for dependent spouse, child and qualifying dependent parent in SSI posteligibility. No physical transport asserted.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section E; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E010"><data key="node_entity_id">R167_E010</data><data key="node_entity_type">data_attribute_rule</data><data key="node_canonical_name">SSR VA Unearned Income Interface Verification Codes 2 3 4</data><data key="node_domain">Title XVI / Program Records</data><data key="node_description">Verification code 2, 3 or 4 following claim number on SSR unearned income entry indicates posting from VA/SSR interface.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section E/F; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E011"><data key="node_entity_id">R167_E011</data><data key="node_entity_type">income_attribution_rule</data><data key="node_canonical_name">VA Augmented Dependent Payment Attribution for SSI</data><data key="node_domain">Title XVI / External Benefits</data><data key="node_description">Attribute veterans augmented VA income portions according to dependent status and direct VA apportionment; distinguish beneficiary, spouse, child and dependent parent.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section B/C; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E012"><data key="node_entity_id">R167_E012</data><data key="node_entity_type">manual_exception_workflow</data><data key="node_canonical_name">SSI VA Interface Posting Failure Manual Development</data><data key="node_domain">Title XVI / External Exchanges</data><data key="node_description">When VA/SSR interface fails to post or update applicable dependent portions, field office verifies amounts and manually posts necessary VA income.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section E/F; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E013"><data key="node_entity_id">R167_E013</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Veterans Affairs Payment Page</data><data key="node_domain">Title XVI / Claims</data><data key="node_description">SSI claims system VETERANS AFFAIRS PAYMENT page supports updating and correcting qualifying VA benefits and educational benefits entries when pending case exists.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section F.1-F.6; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E014"><data key="node_entity_id">R167_E014</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR VA Dependent PCOC Code D</data><data key="node_domain">Title XVI / Program Records</data><data key="node_description">SSA instructs manual SSI VA dependent income entries of types C/E to include special PCOC D after claim number to designate dependent.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section F.2/F.3; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E015"><data key="node_entity_id">R167_E015</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-L1103-U3 VA Income Verification Request</data><data key="node_domain">Title XVI / Evidence</data><data key="node_description">Supplemental Security Income Request for Information form used to request verification of VA income for months under review.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section D/E; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E016"><data key="node_entity_id">R167_E016</data><data key="node_entity_type">policy_status_change</data><data key="node_canonical_name">VA Needs-Based Apportionment New-Award Restrictions Effective February 2026</data><data key="node_domain">Federal Partner / VA</data><data key="node_description">VA discontinued new needs-based apportionment awards effective 2026-02-09 except certain incarcerated veterans or institutionalized incompetent veterans without fiduciaries; prior awards may continue.</data><data key="node_observed_status">documented_effective_2026-02-09</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section B.2; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E017"><data key="node_entity_id">R167_E017</data><data key="node_entity_type">income_attribution_rule</data><data key="node_canonical_name">SSI Absent Dependent Unapportioned VA Portion Exclusion</data><data key="node_domain">Title XVI / Person/Household</data><data key="node_description">Absent dependent VA augmented portion not apportioned directly generally must not be posted as that absent dependent VA income; erroneous entries require correction subject to finality.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section E/F.4-F.6; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E018"><data key="node_entity_id">R167_E018</data><data key="node_entity_type">program_integrity_workflow</data><data key="node_canonical_name">SSI VA Interface Alert and Diary Exception Review</data><data key="node_domain">Title XVI / Workload Control</data><data key="node_description">SSA requires VA-related SSR interface alerts or diaries to be developed, resolved and cleared or deleted; omitted or rejected postings require follow-up.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section E; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E019"><data key="node_entity_id">R167_E019</data><data key="node_entity_type">verification_workflow</data><data key="node_canonical_name">SSI VA Dependent COLA Non-Posting Review</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">When January COLA for a VA dependent benefit is missing on SSR, SSA directs additional verification and development.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section E; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E020"><data key="node_entity_id">R167_E020</data><data key="node_entity_type">data_coding_rule</data><data key="node_canonical_name">VA Compensation versus Pension SSI Unearned Income Type C E Coding</data><data key="node_domain">Title XVI / Program Records</data><data key="node_description">SSA instructions distinguish VA compensation/pension non-need and need-based payments as Type C or E unearned income and require specific dependent coding.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section F; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E021"><data key="node_entity_id">R167_E021</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">VA Apportionment and SSI Dependent Residence Eligibility Gate</data><data key="node_domain">Title XVI / Address Provenance</data><data key="node_description">SSI VA attribution varies with whether dependent resides with veteran and receives direct apportioned VA payment; residence status must be developed separately from mailbox location.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 00830.314 Augmented Veterans Affairs (VA) Benefits, section C/E/F; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E022"><data key="node_entity_id">R167_E022</data><data key="node_entity_type">modernization_status</data><data key="node_canonical_name">2026 SSI Emergency Payment United States Debit Card Transition</data><data key="node_domain">Payments / Emergency Issuance</data><data key="node_description">SSA issues field-office emergency advance and immediate payments using US Debit Card through TPPS effective 2026-02-09, replacing prior paper-check method for these payments.</data><data key="node_observed_status">documented_effective_2026-02-09</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 02004.001 Emergency Advance Payments and Title XVI Immediate Payments, section A; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E023"><data key="node_entity_id">R167_E023</data><data key="node_entity_type">eligibility_rule</data><data key="node_canonical_name">SSI Emergency Advance Presumptive Disability or Blindness Eligibility</data><data key="node_domain">Title XVI / Disability</data><data key="node_description">SSI applicant can receive emergency advance when presumptive disability or blindness is established and financial emergency conditions satisfied.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 02004.001 Emergency Advance Payments and Title XVI Immediate Payments, section B.1.a/B.1.c; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E024"><data key="node_entity_id">R167_E024</data><data key="node_entity_type">recovery_rule</data><data key="node_canonical_name">SSI Emergency Advance Recovery Retroactive or Six Installments</data><data key="node_domain">Title XVI / Debt</data><data key="node_description">SSA recovers EAP from retroactive SSI payment or, if none due, six equal installments of future monthly SSI payments subject to case-specific exceptions.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 02004.001 Emergency Advance Payments and Title XVI Immediate Payments, section B.1.d; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E025"><data key="node_entity_id">R167_E025</data><data key="node_entity_type">cross_program_allocation_rule</data><data key="node_canonical_name">Concurrent Title II Title XVI Immediate Payment Program Selection</data><data key="node_domain">Title II / Title XVI Payments</data><data key="node_description">When both Title II and XVI benefits due, windfall offset determined first; immediate payment issued from program with sufficient benefit amount under the published priority rules.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 02004.001 Emergency Advance Payments and Title XVI Immediate Payments, section B.2.c; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E026"><data key="node_entity_id">R167_E026</data><data key="node_entity_type">identity_eligibility_rule</data><data key="node_canonical_name">SSI Initial Claim Immediate Payment Valid SSN Requirement</data><data key="node_domain">Person / Payments</data><data key="node_description">An initial-claim immediate payment cannot be issued without a valid SSN, unlike requirements for qualifying emergency advance payments.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 02004.001 Emergency Advance Payments and Title XVI Immediate Payments, section B.2.b; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E027"><data key="node_entity_id">R167_E027</data><data key="node_entity_type">recovery_rule</data><data key="node_canonical_name">SSI Immediate Payment Recovery From Next Regular Payment</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">SSA recovers Title XVI immediate payment amount from first regular payment following issuance.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 02004.001 Emergency Advance Payments and Title XVI Immediate Payments, section B.2.e; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E028"><data key="node_entity_id">R167_E028</data><data key="node_entity_type">payment_policy_rule</data><data key="node_canonical_name">Title XVI Immediate Payment Two-Thousand-Dollar Cap</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Title XVI-only IP maximum $2,000 per eligible individual; concurrent Title II/XVI IP maximum $5,000, subject to amount due and emergency request.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SI 02004.001 Emergency Advance Payments and Title XVI Immediate Payments, section B.2/C; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E029"><data key="node_entity_id">R167_E029</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 Supplement OASDI Geographic Annual Benefit Estimates Table 5.J1</data><data key="node_domain">Actuarial / Statistical Products</data><data key="node_description">Table 5.J1 shows estimated 2025 annual OASDI benefits paid by state or area and category, derived from 100 percent MBR and USPS geographic reference.</data><data key="node_observed_status">published_2026_section</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative Annual Statistical Supplement, 2026, Section 5.J Geographic Data, section Table 5.J1; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E030"><data key="node_entity_id">R167_E030</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 Supplement OASDI Geographic Beneficiary Counts Table 5.J2</data><data key="node_domain">Actuarial / Statistical Products</data><data key="node_description">Table 5.J2 shows December 2025 number of OASDI beneficiaries by type and state/area, using 100 percent MBR and USPS geographic reference.</data><data key="node_observed_status">published_2026_section</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative Annual Statistical Supplement, 2026, Section 5.J Geographic Data, section Table 5.J2; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E031"><data key="node_entity_id">R167_E031</data><data key="node_entity_type">statistical_method_rule</data><data key="node_canonical_name">2026 Supplement 5.J1 Unnegotiated-Check Statistical Caveat</data><data key="node_domain">Actuarial / Payment Statistics</data><data key="node_description">5.J1 benefit estimates do not deduct unnegotiated checks and exclude lump-sum death payments; not a negotiable-payment ledger.</data><data key="node_observed_status">published_2026_section</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative Annual Statistical Supplement, 2026, Section 5.J Geographic Data, section Table 5.J1 Notes; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R167_E032"><data key="node_entity_id">R167_E032</data><data key="node_entity_type">statistical_provenance_rule</data><data key="node_canonical_name">2026 Supplement 5.J USPS-MBR State Assignment Data Lineage</data><data key="node_domain">Address Provenance / Statistical Geography</data><data key="node_description">2026 5.J credits MBR 100 percent data and USPS geographic data; documents aggregate location reference, not person-master address synchronization.</data><data key="node_observed_status">published_2026_section</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative Annual Statistical Supplement, 2026, Section 5.J Geographic Data, section Table 5.J1 Sources; observed 2026-10-10. No undocumented physical implementation, automatic updates or residence inference.</data></node><node id="R168_E001"><data key="node_entity_id">R168_E001</data><data key="node_entity_type">external_data_product</data><data key="node_canonical_name">IRS SSA Weekly SSN and Name-Control Update File</data><data key="node_acronym">SSA weekly N/C file</data><data key="node_domain">External Data / IRS / Identity</data><data key="node_description">IRS manual documents weekly SSA records of SSNs and newly assigned or updated name controls for IMF processing. Historical text refers to weekly tapes; current transport not independently verified.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Manual subsection 3.13.5.16 effective 2022. Avoid inference of Numident as direct feed or current physical tape medium.</data></node><node id="R168_E002"><data key="node_entity_id">R168_E002</data><data key="node_entity_type">external_business_process</data><data key="node_canonical_name">IRS DM-1 TIN and Name-Control Validation Process</data><data key="node_acronym">DM-1 validation</data><data key="node_domain">External Data / IRS / Identity</data><data key="node_description">IRS DM-1 checking directs tax transactions toward valid or invalid IMF account segments using TIN/name-control matching, including proximal matching.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">IRS processing only; name-control mismatches are not automatic SSA corrections.</data></node><node id="R168_E003"><data key="node_entity_id">R168_E003</data><data key="node_entity_type">external_data_classification</data><data key="node_canonical_name">IRS IMF Valid and Invalid Taxpayer Account Segments</data><data key="node_acronym">IMF segments</data><data key="node_domain">External Data / IRS / Identity</data><data key="node_description">Logical IMF account classification determined by matching taxpayer TIN and name control; not a claim about separate physical databases.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Same person may appear in both segments under different tax-period names.</data></node><node id="R168_E004"><data key="node_entity_id">R168_E004</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">IRS National Account Profile (NAP)</data><data key="node_acronym">NAP</data><data key="node_domain">External Data / IRS / Identity</data><data key="node_description">IRS taxpayer entity information profile incorporating DM-1, SSNs, EINs, employee-plan master information, and cross-reference data.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Existing DB_IRS_NAP_DM1 conflates NAP and DM-1; preserve existing record but queue reconciliation.</data></node><node id="R168_E005"><data key="node_entity_id">R168_E005</data><data key="node_entity_type">external_form</data><data key="node_canonical_name">IRS Form 8822 Change of Address</data><data key="node_acronym">IRS 8822</data><data key="node_domain">External Data / IRS / Address</data><data key="node_description">Taxpayer-submitted change-of-address request; IRS manual identifies special handling for requests referencing Social Security Statement mailing.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">The form is submitted to IRS; not evidence of automatic SSA address maintenance.</data></node><node id="R168_E006"><data key="node_entity_id">R168_E006</data><data key="node_entity_type">external_business_process</data><data key="node_canonical_name">IRS Form 8822 Social Security Statement Address Request Handling</data><data key="node_acronym">8822 Statement handling</data><data key="node_domain">External Data / IRS / Address</data><data key="node_description">If IRS entity receives a Form 8822 expressly for a Social Security Statement, active account changes can be made; inactive account requestors are referred to SSA.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Section originally effective 2018; cannot infer automatic IRS-to-SSA benefit address update.</data></node><node id="R168_E007"><data key="node_entity_id">R168_E007</data><data key="node_entity_type">external_record_file</data><data key="node_canonical_name">IRS Processed Form 8822 Alpha File</data><data key="node_acronym">8822 Alpha File</data><data key="node_domain">External Data / IRS / Address</data><data key="node_description">IRS Files Operation Alpha File for qualifying processed Form 8822 documents beginning October 2017; exception for requests already pending/updated.</data><data key="node_observed_status">documented_historical_and_in_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">The manual says defined retention but does not state an exact duration here. Do not assume indefinite retention.</data></node><node id="R168_E008"><data key="node_entity_id">R168_E008</data><data key="node_entity_type">external_application</data><data key="node_canonical_name">IRS Integrated Data Retrieval System (IDRS) Address Change</data><data key="node_acronym">IDRS Address</data><data key="node_domain">External Data / IRS / Address</data><data key="node_description">IRS address-maintenance transaction capability referenced by the manual for changing primary taxpayer IMF account address and identifying change records.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Only IRS internal action established, no access to SSA master data.</data></node><node id="R168_E009"><data key="node_entity_id">R168_E009</data><data key="node_entity_type">external_business_rule</data><data key="node_canonical_name">IRS IMF Joint-Filer Secondary Address Conditional Propagation</data><data key="node_acronym">IMF joint filer address</data><data key="node_domain">External Data / IRS / Address</data><data key="node_description">Under specified joint-return circumstances IRS IMF automatically updates secondary taxpayer address when primary address changes, with documented exceptions and manual overrides.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">The secondary address change may lag up to one week. This is an IRS-internal update only.</data></node><node id="R168_E010"><data key="node_entity_id">R168_E010</data><data key="node_entity_type">external_business_rule</data><data key="node_canonical_name">IRS IMF Name-Control Mismatch and Proximal Match Gate</data><data key="node_acronym">IMF proximal match</data><data key="node_domain">External Data / IRS / Identity</data><data key="node_description">IRS compares return name control with DM-1 values for the TIN, allowing documented proximal matching to address certain errors.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Matching does not establish actual legal identity or update the SSA record.</data></node><node id="R168_E011"><data key="node_entity_id">R168_E011</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR Reported Wage Verification Code Zero</data><data key="node_acronym">SSR wage code 0</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">SSI record shows verification code 0 for qualifying timely wage reports; separate from alleged and independently verified wage categories.</data><data key="node_observed_status">current_poms_2025</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Exceptions require wage development; verification-code semantics do not establish independent confirmation for every wage period.</data></node><node id="R168_E012"><data key="node_entity_id">R168_E012</data><data key="node_entity_type">governance_rule</data><data key="node_canonical_name">SSI Third-Party Wage Query Worker-Agreement Evidence Gate</data><data key="node_acronym">Worker wage agreement</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">IBIQ, NDNH, SASRO, and iTOPSS queries generally require worker agreement and prescribed documentation before use as secondary monthly wage evidence.</data><data key="node_observed_status">current_poms_2025</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A query is not automatically verified wages; preference and conflicting evidence rules apply.</data></node><node id="R168_E013"><data key="node_entity_id">R168_E013</data><data key="node_entity_type">governance_rule</data><data key="node_canonical_name">SSI IBIQ NDNH SASRO Query Evidence Portal Exclusion</data><data key="node_acronym">Wage query EP exclusion</data><data key="node_domain">Title XVI / Earnings / Privacy</data><data key="node_description">SSA policy says staff must not save IBIQ/NDNH/SASRO query printouts in Evidence Portal; document applicable information in authorized forms or Report of Contact.</data><data key="node_observed_status">current_poms_2025</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Prohibition is for specified query printouts, not every type of wage document.</data></node><node id="R168_E014"><data key="node_entity_id">R168_E014</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Quarterly and Annual Wage Monthly Allocation</data><data key="node_acronym">Wage amount allocation</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">Where only quarterly or annual totals exist, employee confirms months worked, preserves verified amounts, and allocates remaining amount to unverified months.</data><data key="node_observed_status">current_poms_2025</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Administrative computation requiring documented allegations; not proof of automated bulk changes to MEF.</data></node><node id="R168_E015"><data key="node_entity_id">R168_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Wage Termination Evidence Development</data><data key="node_acronym">Termination wage evidence</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">Evidence workflow for reported work cessation, requiring last work date, final payday, acceptable corroborating sources, and work-report receipt.</data><data key="node_observed_status">current_poms_2025</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Termination of earnings is not necessarily termination of eligibility or automatic master record closure.</data></node><node id="R168_E016"><data key="node_entity_id">R168_E016</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI Monthly Pay-Stub Evidence and Receipt Record</data><data key="node_acronym">Paystub receipt</data><data key="node_domain">Title XVI / Earnings / Evidence</data><data key="node_description">Documentation for monthly wage pay stubs processed through SSIMWV or Evidence Portal; monthly SSIMWV receipts archived in ORS.</data><data key="node_observed_status">current_poms_2025</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not equate receipt archive with a full copy of original pay stub.</data></node><node id="R168_E017"><data key="node_entity_id">R168_E017</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSR DRDP Recurring Direct Deposit Account Segment</data><data key="node_acronym">DRDP</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">SSR DRDP segment holds regular recurring direct-deposit account information compared with a separate dedicated-account A-OTP routing instruction.</data><data key="node_observed_status">current_poms_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Only field/segment semantics supported; physical storage and account encryption not established.</data></node><node id="R168_E018"><data key="node_entity_id">R168_E018</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Dedicated-Account A-OTP Account Mismatch Reject Gate</data><data key="node_acronym">UP reject</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">When dedicated-account bank details used for one-time past-due payment match DRDP recurring account details, system produces UP reject; payment to a separate account is required.</data><data key="node_observed_status">current_poms_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">This controls A-OTP input; no claim of bank-account ownership verification.</data></node><node id="R168_E019"><data key="node_entity_id">R168_E019</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Direct SSR Update One-Time Payment UPOT Screen</data><data key="node_acronym">UPOT</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">One-Time Payment screen reached through Special Payments Menu in Direct SSR Update for automated one-time deposits into a qualifying dedicated account.</data><data key="node_observed_status">current_poms_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Screen UI documented, no implementation stack inferred.</data></node><node id="R168_E020"><data key="node_entity_id">R168_E020</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Direct SSR Update Special Payments UPSP Menu</data><data key="node_acronym">UPSP</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">Special Payments Menu of Direct SSR Update used to reach UPOT for the separate dedicated account payment.</data><data key="node_observed_status">current_poms_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not assume changes to regular DRDP data.</data></node><node id="R168_E021"><data key="node_entity_id">R168_E021</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Dedicated Account E1 Alert and EA Diary</data><data key="node_acronym">E1/EA</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">System sends E1 alert when EA account-establishment diary matures and follows up every 15 days until resolved by appropriate one-time payment.</data><data key="node_observed_status">current_poms_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">30-day initial diary from notice; no backend job scheduler inferred.</data></node><node id="R168_E022"><data key="node_entity_id">R168_E022</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Past-Due Payment Priority IAR Fees Overpayment</data><data key="node_acronym">SSI benefit priority</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">For qualifying past-due SSI benefits, priority sequence is state interim assistance reimbursement, authorized direct representative fees, then recovery of earlier collectible overpayment.</data><data key="node_observed_status">current_poms_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Rules apply to described cases; priority may vary for different scenarios.</data></node><node id="R168_E023"><data key="node_entity_id">R168_E023</data><data key="node_entity_type">actuarial_input_dataset</data><data key="node_canonical_name">2026 Trustees NCHS Under-65 Mortality Input Series</data><data key="node_acronym">NCHS mortality 2026</data><data key="node_domain">Actuarial / Mortality</data><data key="node_description">NCHS death records and provisional 2025 mortality inputs for below-65 and cause-of-death projections in 2026 Trustees methodology.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Describes statistical source series; not an SSA production data store. Historical base runs outside 10-year search but 2026 publication within horizon.</data></node><node id="R168_E024"><data key="node_entity_id">R168_E024</data><data key="node_entity_type">actuarial_input_dataset</data><data key="node_canonical_name">2026 Trustees Medicare Age-65-Plus Mortality Experience Series</data><data key="node_acronym">Medicare mortality 2026</data><data key="node_domain">Actuarial / Mortality</data><data key="node_description">Medicare deaths and enrollment data form age-65-plus historical mortality experience inputs to Trustees demographic projections.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not infer direct automated CMS feed or access to individual medical records.</data></node><node id="R168_E025"><data key="node_entity_id">R168_E025</data><data key="node_entity_type">actuarial_input_dataset</data><data key="node_canonical_name">2026 Trustees Census Resident Population Baseline Inputs</data><data key="node_acronym">Census resident population</data><data key="node_domain">Actuarial / Demography</data><data key="node_description">Census Bureau residential population information forms a starting source for Social Security area population adjustments and mortality denominators.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Census inputs transformed through adjustments; not identical to actual SSA beneficiary population.</data></node><node id="R168_E026"><data key="node_entity_id">R168_E026</data><data key="node_entity_type">actuarial_input_dataset</data><data key="node_canonical_name">2026 Trustees DHS Border-Crossing Immigration Update Inputs</data><data key="node_acronym">DHS border crossings</data><data key="node_domain">Actuarial / Immigration</data><data key="node_description">Updated 2022-2025 DHS border-crossing information used to revise projected temporary or unlawfully present immigrant entries for 2026 Trustees Report.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Aggregate modelling input, not a new SSA per-person immigration-status interface.</data></node><node id="R168_E027"><data key="node_entity_id">R168_E027</data><data key="node_entity_type">actuarial_method_rule</data><data key="node_canonical_name">2026 Trustees Mortality Regression 2020-2023 Exclusion Rule</data><data key="node_acronym">pandemic regression exclusion</data><data key="node_domain">Actuarial / Mortality</data><data key="node_description">2026 starting death-rate regressions include 2024 data but exclude 2020-2023 to avoid pandemic distortion, with stated methodological transition from earlier reports.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Model-method rule, not dataset deletion or data retention policy.</data></node><node id="R168_E028"><data key="node_entity_id">R168_E028</data><data key="node_entity_type">actuarial_method_rule</data><data key="node_canonical_name">2026 Trustees Age-75-Plus Labor-Force Participation Calibration</data><data key="node_acronym">Age 75+ LFPR calibration</data><data key="node_domain">Actuarial / Workforce</data><data key="node_description">Projection parameters for workers aged 75 and older adjusted using 2011-2024 administrative employment records in 2026 Trustees long-range methods.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Underlying operational employment-record system not identified.</data></node><node id="R168_E029"><data key="node_entity_id">R168_E029</data><data key="node_entity_type">external_business_rule</data><data key="node_canonical_name">IRS Form 8822 Statement-Related Active-Account Gate</data><data key="node_acronym">Active IMF check</data><data key="node_domain">External Data / IRS / Address</data><data key="node_description">For Form 8822 referencing Social Security Statements, IRS changes address when active account exists; inactive accounts prompt IRS referral to SSA.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">IRS policy 3.13.5.52.1 originally dated 2018; no evidence of a new SSA interface.</data></node><node id="R168_E030"><data key="node_entity_id">R168_E030</data><data key="node_entity_type">external_retention_rule</data><data key="node_canonical_name">IRS Form 8822 Alpha File Retention Exception</data><data key="node_acronym">8822 filing exception</data><data key="node_domain">External Data / IRS / Address</data><data key="node_description">IRS retains eligible processed Form 8822 documents, but if address was already updated or change pending, IRS destroys form as classified waste rather than sending it to Alpha File.</data><data key="node_observed_status">documented_in_2025_irs_manual</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Exact retention years not stated; different treatment of case records prevents an inferred universal retention.</data></node><node id="R169_E0001"><data key="node_entity_id">R169_E0001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">RRB Non-Vested Disability Application Referral to SSA FO</data><data key="node_acronym" /><data key="node_domain">Title II / railroad</data><data key="node_description">RRB sends disability application and pertinent claims materials to SSA field office if railroad service is under 120 months, or under 60 months after 1995.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0002"><data key="node_entity_id">R169_E0002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">RRB-SSA Joint Disability Freeze Decision</data><data key="node_acronym" /><data key="node_domain">Title II / railroad</data><data key="node_description">RRB disability annuity filing is deemed SSA freeze application; qualifying potential RSDI entitlement may require joint RRB-SSA disability-freeze decision.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0003"><data key="node_entity_id">R169_E0003</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">RRB Joint Freeze SSA-831 Decision Copy</data><data key="node_acronym" /><data key="node_domain">Title II / railroad</data><data key="node_description">DCR receives two copies of joint RRB-SSA freeze determination; one SSA-831 copy is imaged in its PPC system.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0004"><data key="node_entity_id">R169_E0004</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DCR Joint Freeze Statistical Coding Copy</data><data key="node_acronym" /><data key="node_domain">actuarial/statistics</data><data key="node_description">DCR uses the second copy of the joint freeze determination for statistical and coding purposes; physical statistical repository unidentified.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0005"><data key="node_entity_id">R169_E0005</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">RRB Freeze Unfiled DIB Claims Lead Memorandum</data><data key="node_acronym" /><data key="node_domain">Title II / disability</data><data key="node_description">DCR refers apparently DIB-eligible RRB annuitants without a DIB application to servicing FO for claims-lead contact and SSI screening.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0006"><data key="node_entity_id">R169_E0006</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RRB Joint Freeze SSA SSI Eligibility Screen</data><data key="node_acronym" /><data key="node_domain">Title XVI / railroad</data><data key="node_description">Servicing SSA field office also screens SSI eligibility on DCR referral for potentially unfiled DIB claims; unfiled lead returns with explanation.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0007"><data key="node_entity_id">R169_E0007</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">SSI NHRP Applicant Allegation and Privacy Notice Prequery Gate</data><data key="node_acronym" /><data key="node_domain">Title XVI / resources</data><data key="node_description">Before NHRP search SSA must collect each person's own real-property ownership allegation and deliver Privacy Act notice; an open claim event is required.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R50_007; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0008"><data key="node_entity_id">R169_E0008</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Non-Home Real Property Requests Page</data><data key="node_acronym" /><data key="node_domain">Title XVI / resources</data><data key="node_description">SSI Claims system NHRP requests screen selects individual claimant, recipient or eligible deemor; returns request ID, request status and action required.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R50_007; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0009"><data key="node_entity_id">R169_E0009</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Pending Real Properties Page</data><data key="node_acronym" /><data key="node_domain">Title XVI / resources</data><data key="node_description">Pending Real Properties page has Add, Update, Reject, Decide Later decisions; unresolved pending item prevents claim event closeout.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R50_007; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0010"><data key="node_entity_id">R169_E0010</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSI Accurint Property Ownership Search Lead</data><data key="node_acronym" /><data key="node_domain">Title XVI / resources</data><data key="node_description">LexisNexis Accurint NHRP result is a third-party property lead, not independently established SSI property ownership or resource value; contains PROPERTY LOCATION not current person residence.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R50_007; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0011"><data key="node_entity_id">R169_E0011</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">NHRP Ownership and Value Independent Verification Gate</data><data key="node_acronym" /><data key="node_domain">Title XVI / resources</data><data key="node_description">When ownership is denied or value not ineligible, SSA generally independently verifies LexisNexis property information; follow specific POMS exception for alleged excess-resource ownership.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R50_007; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0012"><data key="node_entity_id">R169_E0012</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">NHRP Previously Rejected Property Address Match</data><data key="node_acronym" /><data key="node_domain">Title XVI / address provenance</data><data key="node_description">Pending Real Properties page notes prior rejections when property address exactly matches previously rejected property for associated SSN; retention period not established.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R50_007; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0013"><data key="node_entity_id">R169_E0013</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI NHRP Mandatory Claim Event Types</data><data key="node_acronym" /><data key="node_domain">Title XVI / resources</data><data key="node_description">Integrated NHRP searches required for full initial claims, high-error-profile C redeterminations, favorable initial-appeal reversals, and denied-claim reopenings.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R50_007; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0014"><data key="node_entity_id">R169_E0014</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">Held Anomalous Electronic Wage Report Unposted Queue State</data><data key="node_acronym" /><data key="node_domain">earnings / integrity</data><data key="node_description">SSA can hold anomalous wage report processing pending investigation; held wage reports do not post to SSA earnings records.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC133; Logical processing state; a physically separate queue or repository is NOT established.</data></node><node id="R169_E0015"><data key="node_entity_id">R169_E0015</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Wage Investigation First Notice Response Clock</data><data key="node_acronym" /><data key="node_domain">earnings / integrity</data><data key="node_description">Submitter ordinarily has 45 calendar days after first investigative notice receipt, with five-day mailing presumption and one possible 15-day extension.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC133; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0016"><data key="node_entity_id">R169_E0016</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Wage Investigation Second Notice Response Clock</data><data key="node_acronym" /><data key="node_domain">earnings / integrity</data><data key="node_description">Second notice provides 15 calendar days from its date to resolve remaining concerns before SSA may reject anomalous reports.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC133; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0017"><data key="node_entity_id">R169_E0017</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Wage Submitter Affiliated Account Suspension Rule</data><data key="node_acronym" /><data key="node_domain">earnings / integrity</data><data key="node_description">SSA may suspend affiliated submitter accounts linked by EIN, third-party filer/consolidator, shared contact information or authorized representatives after investigative noncooperation.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC133; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0018"><data key="node_entity_id">R169_E0018</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Wage Submitter Suspension Administrative Review Clock</data><data key="node_acronym" /><data key="node_domain">earnings / integrity</data><data key="node_description">Submitter may seek suspension review within ten calendar days of notice; SSA reviews request within 30 calendar days of receipt.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC133; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0019"><data key="node_entity_id">R169_E0019</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Wage Report Submitter Documentary Verification Gate</data><data key="node_acronym" /><data key="node_domain">earnings / integrity</data><data key="node_description">SSA reviews employer records, authenticated BSO employer, tax returns or IRS Form 941 evidence; verified legitimate anomalous wage reports resume processing.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC133; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0020"><data key="node_entity_id">R169_E0020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">BSO Electronic Wage Submission Suspension Versus Credential Deactivation</data><data key="node_acronym" /><data key="node_domain">earnings / integrity</data><data key="node_description">Wage filing suspension can prevent new electronic reports while allowing prior-status access; deactivated BSO credentials eliminate access to online wage reporting services.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC133; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0021"><data key="node_entity_id">R169_E0021</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Erroneous Disability Award Advance Due Process Notice and Response</data><data key="node_acronym" /><data key="node_domain">Title II / Title XVI</data><data key="node_description">Advance notice and opportunity to respond are required before adverse reduction/termination after mistaken award/payment; Title II diary and SSI GK rules differ.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S002; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0022"><data key="node_entity_id">R169_E0022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title II Erroneous Disability Award POS S9 to PC T9 Escalation</data><data key="node_acronym" /><data key="node_domain">Title II / payment</data><data key="node_description">SSA FO enters POS S9 miscellaneous suspension; high-priority 2560HP MDW to PC for T9 termination or other authorized termination action after process.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S002; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0023"><data key="node_entity_id">R169_E0023</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Title XVI Erroneous Disability Award Manual SSI Nonpayment Correction</data><data key="node_acronym" /><data key="node_domain">Title XVI / payment</data><data key="node_description">Where system limits automatic GK adjustment, staff input appropriate SSI nonpayment status and explain mismatch by special message on SSR.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S002; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0024"><data key="node_entity_id">R169_E0024</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Erroneous Disability Award Misdirected EFT Recovery Assessment</data><data key="node_acronym" /><data key="node_domain">payments / debt</data><data key="node_description">Misdirected wrong-account payment: Title XVI F-stop plus SSR special message; Title II priority MDW to PC; if not returned PC may establish DMS non-entitled debtor record.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S002; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0025"><data key="node_entity_id">R169_E0025</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Erroneous Disability Award Reopening Expiry Medical CDR Alternative</data><data key="node_acronym" /><data key="node_domain">disability / appeals</data><data key="node_description">When reopening erroneous allowance is barred by administrative finality, SSA initiates continuing disability review with DDS rather than automatically revising old determination.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S002; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0026"><data key="node_entity_id">R169_E0026</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Erroneous Disability Award Determination Versus Debt Appeal Separation</data><data key="node_acronym" /><data key="node_domain">payments / appeals</data><data key="node_description">Disability, monthly payment eligibility and overpayment assessment generally constitute separate initial determinations with separate notices/appeal rights.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source R169_S002; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0027"><data key="node_entity_id">R169_E0027</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS Paper Evidence CEF Access Verification Before Destruction</data><data key="node_acronym" /><data key="node_domain">disability / evidence</data><data key="node_description">DDS destroys locally scanned original source documents only after verifying imaged document is accessible in Certified Electronic Folder; local operating rules govern scan location.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC408; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0028"><data key="node_entity_id">R169_E0028</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">DDS Original Medical Imaging Return and Interpretation-Report Intake</data><data key="node_acronym" /><data key="node_domain">disability / evidence</data><data key="node_description">DDS returns original x-ray film and ultrasound image as irrelevant evidence but scans medically relevant interpretation reports into CEF.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC408; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0029"><data key="node_entity_id">R169_E0029</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Field Office Priority Disability Medical Evidence Fax and Source-Material Retention</data><data key="node_acronym" /><data key="node_domain">disability / evidence</data><data key="node_description">For TERI, QDD, CAL, PD and other specified critical cases, FO faxed medical evidence enters CEF; FO marks EDCS routing sheet and mails source documents to DDS.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC408; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0030"><data key="node_entity_id">R169_E0030</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Standard CAP SSA SSI Interview SNAP Joint Intake</data><data key="node_acronym" /><data key="node_domain">Title XVI / external exchanges</data><data key="node_description">In participating states, SSA field office SSI initial application/redetermination can serve simplified SNAP application and enrollment outreach for eligible one-person household.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R89_001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0031"><data key="node_entity_id">R169_E0031</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Modified CAP State SDX Based SNAP Outreach</data><data key="node_acronym" /><data key="node_domain">Title XVI / external exchanges</data><data key="node_description">States use SDX SSI recipient data to identify SNAP nonparticipants then mail simplified SNAP form returned directly to State SNAP office; no coordinated SSA SNAP application intake.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R89_001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0032"><data key="node_entity_id">R169_E0032</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">CAP State-Specific Program Participation and Eligibility Scope</data><data key="node_acronym" /><data key="node_domain">Title XVI / external exchanges</data><data key="node_description">POMS lists participating states separately for standard versus modified CAP; qualification and simplified SNAP rules vary by state and model.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC_R89_001; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0033"><data key="node_entity_id">R169_E0033</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Consolidated Court Remand Continuing Representative Appointments</data><data key="node_acronym" /><data key="node_domain">hearings / representation</data><data key="node_description">When Appeals Council consolidates federal court remand and later application sharing issue, all still-valid appointments across both claims continue; must identify principal representative.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC409; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0034"><data key="node_entity_id">R169_E0034</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Subsequent Disability Application Missing SSA-1696 No Imported Appointment Rule</data><data key="node_acronym" /><data key="node_domain">disability / representation</data><data key="node_description">Absent new signed SSA-1696 for subsequent claim, SSA does not import former case representative, send decision to them, or withhold fee from new case based on old appointment.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC409; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R169_E0035"><data key="node_entity_id">R169_E0035</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">Representative Appointment Unidentifiable Party Form Destruction</data><data key="node_acronym" /><data key="node_domain">hearings / privacy</data><data key="node_description">Incomplete SSA-1696 missing required identity/signature is not accepted; notice to identifiable submitter and destruction/disposal under agency rules.</data><data key="node_observed_status">Documented administrative process or information artifact</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source SRC409; Do not infer technology, persistence, automatic update, or interface mechanism.</data></node><node id="R170_E001"><data key="node_entity_id">R170_E001</data><data key="node_entity_type">network_platform</data><data key="node_canonical_name">Headquarters Telephone System (legacy)</data><data key="node_acronym">HTS</data><data key="node_domain">Infrastructure / Telephony</data><data key="node_description">2018 NGTP solicitation identified headquarters voice services at Woodlawn, Wabash Avenue and Urbana; historical scope exceeded 14 million calls annually.</data><data key="node_observed_status">historical_2018</data><data key="node_observed_as_of">2018-08-28</data><data key="node_confidence">5</data><data key="node_notes">Legacy scope only; current operational status not inferred.</data></node><node id="R170_E002"><data key="node_entity_id">R170_E002</data><data key="node_entity_type">network_platform</data><data key="node_canonical_name">Telephone System Replacement Project (legacy)</data><data key="node_acronym">TSRP</data><data key="node_domain">Infrastructure / Telephony</data><data key="node_description">2018 NGTP statement of work identified agency-wide voice/fax services at more than 1,500 sites and annual volumes exceeding 90 million calls and 30 million faxes.</data><data key="node_observed_status">historical_2018</data><data key="node_observed_as_of">2018-08-28</data><data key="node_confidence">5</data><data key="node_notes">Site and traffic volume are historical procurement baselines.</data></node><node id="R170_E003"><data key="node_entity_id">R170_E003</data><data key="node_entity_type">organization</data><data key="node_canonical_name">CenturyLink (2019 SSANet task-order contractor)</data><data key="node_domain">Procurement / Telecommunications</data><data key="node_description">GAO records a September 27, 2019, Enterprise Infrastructure Solutions task order to CenturyLink for SSANet support.</data><data key="node_observed_status">historical_2019</data><data key="node_observed_as_of">2019-09-27</data><data key="node_confidence">5</data><data key="node_notes">Current corporate branding and later performance not established by this 2020 protest decision.</data></node><node id="R170_E004"><data key="node_entity_id">R170_E004</data><data key="node_entity_type">contract</data><data key="node_canonical_name">2019 Verizon SSANet EIS task order</data><data key="node_domain">Procurement / Network</data><data key="node_description">SSA issued a September 27, 2019 task order to Verizon for SSANet support under GSA EIS; separate from NGTP award.</data><data key="node_observed_status">historical_2019</data><data key="node_observed_as_of">2019-09-27</data><data key="node_confidence">5</data><data key="node_notes">The contract supports the agency-provided network on which proposed NGTP would rely; current task-order performance unverified.</data></node><node id="R170_E005"><data key="node_entity_id">R170_E005</data><data key="node_entity_type">contract</data><data key="node_canonical_name">2019 CenturyLink SSANet EIS task order</data><data key="node_domain">Procurement / Network</data><data key="node_description">SSA issued a September 27, 2019 EIS task order to CenturyLink for SSANet support.</data><data key="node_observed_status">historical_2019</data><data key="node_observed_as_of">2019-09-27</data><data key="node_confidence">5</data><data key="node_notes">No later option years or successor contract determined.</data></node><node id="R170_E006"><data key="node_entity_id">R170_E006</data><data key="node_entity_type">procurement_record</data><data key="node_canonical_name">NGTP request for proposals 28321318R00000047</data><data key="node_domain">Procurement / Telecommunications</data><data key="node_description">SSA issued NGTP RFP August 28, 2018, to consolidate three historical telephone systems; described voice, video, presence, messaging, web and contact-center requirements.</data><data key="node_observed_status">historical_2018</data><data key="node_observed_as_of">2018-08-28</data><data key="node_confidence">5</data><data key="node_notes">RFP capability is requirement, not proof of deployed functionality.</data></node><node id="R170_E007"><data key="node_entity_id">R170_E007</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">NGTP–SSANet Impaired-Objectivity Organizational Conflict Review</data><data key="node_acronym">OCI</data><data key="node_domain">Procurement / Governance</data><data key="node_description">GAO sustained AT&amp;T protest July 2, 2020 because SSA failed to assess adequately the potential impaired-objectivity conflict arising from Verizon monitoring a network it also supported.</data><data key="node_observed_status">historical_2020</data><data key="node_observed_as_of">2020-07-02</data><data key="node_confidence">5</data><data key="node_notes">GAO decision on contract award, not a determination that the network was technically defective.</data></node><node id="R170_E008"><data key="node_entity_id">R170_E008</data><data key="node_entity_type">contract_requirement</data><data key="node_canonical_name">NGTP Continuous Systems Engineering and WAN Fault Reporting Requirement</data><data key="node_domain">Procurement / Infrastructure</data><data key="node_description">NGTP solicitation required the contractor to assess WAN capacity, quality of service, bandwidth, integration and notify SSA of performance issues, including issues potentially involving its own SSANet contract.</data><data key="node_observed_status">historical_2018</data><data key="node_observed_as_of">2018-08-28</data><data key="node_confidence">5</data><data key="node_notes">Requirement only, not independently verified operational monitoring implementation.</data></node><node id="R170_E009"><data key="node_entity_id">R170_E009</data><data key="node_entity_type">procurement_control</data><data key="node_canonical_name">NGTP Section 508 Evaluation Gate</data><data key="node_domain">Procurement / Accessibility</data><data key="node_description">NGTP evaluated Section 508 compliance in phase I, before price/technical and supply-chain reviews.</data><data key="node_observed_status">historical_2018</data><data key="node_observed_as_of">2018-08-28</data><data key="node_confidence">5</data><data key="node_notes">Solicitation evaluation process; no deployed software accessibility audit is established.</data></node><node id="R170_E010"><data key="node_entity_id">R170_E010</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2018 NGTP Legacy Telephony Volume Baselines</data><data key="node_domain">Infrastructure / Statistical Baselines</data><data key="node_description">Solicitation documented historical &gt;14 million HTS calls, &gt;90 million TSRP calls, &gt;30 million TSRP faxes, and &gt;80 million N8NN calls annually.</data><data key="node_observed_status">historical_2018</data><data key="node_observed_as_of">2018-08-28</data><data key="node_confidence">5</data><data key="node_notes">Volume estimates from procurement background are not current production telemetry.</data></node><node id="R170_E011"><data key="node_entity_id">R170_E011</data><data key="node_entity_type">exchange_governance</data><data key="node_canonical_name">2024–2026 Treasury Do Not Pay Full-Death-File Pilot</data><data key="node_domain">External Data / Program Integrity</data><data key="node_description">Three-year DNP pilot provides Treasury Do Not Pay access to SSA full death data including state-reported deaths, rather than only the less comprehensive public extract.</data><data key="node_observed_status">historical_or_time_limited</data><data key="node_observed_as_of">2026-02-12</data><data key="node_confidence">5</data><data key="node_notes">2026 GAO report described a pilot; do not infer access continues after its term without subsequent legislation.</data></node><node id="R170_E012"><data key="node_entity_id">R170_E012</data><data key="node_entity_type">agreement_program</data><data key="node_canonical_name">September 2023 State Death Data Contract Fee Structure</data><data key="node_domain">External Data / State Vital Records</data><data key="node_description">2023 state death-record contracts resulted in $23.8 million SSA payments in 2024 and used submission timeliness-based fee structure criticized by GAO.</data><data key="node_observed_status">historical_2023</data><data key="node_observed_as_of">2026-02-12</data><data key="node_confidence">5</data><data key="node_notes">Applies to state death data purchases; source data ownership remains with states.</data></node><node id="R170_E013"><data key="node_entity_id">R170_E013</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">2025 SSA State Death Data Multiagency Cost Allocation</data><data key="node_domain">External Data / Finance</data><data key="node_description">SSA estimated $25.9 million 2025 state death record costs and allocated its own 23 percent by share of federal outlays, with remaining 77 percent distributed to Treasury and other users; GAO identified methodology deficiencies.</data><data key="node_observed_status">gaо_questioned_2026</data><data key="node_observed_as_of">2026-02-12</data><data key="node_confidence">5</data><data key="node_notes">Figures are GAO 2025 estimates; not actual 2026 costs or approved cost accounting.</data></node><node id="R170_E014"><data key="node_entity_id">R170_E014</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Treasury 2024 Do Not Pay Full Death Data Pilot Savings Report</data><data key="node_domain">Federal Program Integrity / Reporting</data><data key="node_description">Treasury reported $113.5 million improper payments identified/prevented/recovered in 2024 through full-DMF pilot; $4.6 million cost and 23x return cited by GAO in 2026.</data><data key="node_observed_status">historical_2024</data><data key="node_observed_as_of">2026-02-12</data><data key="node_confidence">5</data><data key="node_notes">These amounts reflect Treasury reporting of first-year pilot, not SSA solely saved payments.</data></node><node id="R170_E015"><data key="node_entity_id">R170_E015</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">GAO-26-107181 State Death Data Cost Recommendations</data><data key="node_domain">Governance / Oversight</data><data key="node_description">Three GAO recommendations to document authorized state fee costs, review negotiated fee schedules and revise proportional federal cost sharing; GAO page showed all open when observed.</data><data key="node_observed_status">open_as_observed</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Open status is observation-specific; do not extrapolate subsequent implementation.</data></node><node id="R170_E016"><data key="node_entity_id">R170_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Representative Appointment Referral to Field Office through WorkTrack</data><data key="node_domain">Disability / Representative Appointments</data><data key="node_description">DDS faxes newly received SSA-1696 appointment to servicing FO and sends assistance request noting WorkTrack fax date; DDS does not itself process appointment.</data><data key="node_observed_status">observed_policy</data><data key="node_observed_as_of">2025-05-06</data><data key="node_confidence">5</data><data key="node_notes">Duplicate existing 1696 may be disposed of; manual administrative referral, not an inferred API.</data></node><node id="R170_E017"><data key="node_entity_id">R170_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Field Office RASR to EDCS Representation Propagation and UAT</data><data key="node_domain">Disability / Cross-Record Updates</data><data key="node_description">FO processes representative appointment in RASR, ensures information propagates into EDCS, then EDCS Update After Transfer updates DCPS when needed.</data><data key="node_observed_status">observed_policy</data><data key="node_observed_as_of">2025-05-06</data><data key="node_confidence">5</data><data key="node_notes">This automatic propagation is explicitly stated by POMS; individual exceptions/technical transport unverified.</data></node><node id="R170_E018"><data key="node_entity_id">R170_E018</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS Claimant Contact Update Requires Independent Claimant Verification</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">An appointed representative is not authorized to change claimant name/address/contact information without independent claimant confirmation. DDS holds proposed change until verified.</data><data key="node_observed_status">observed_policy</data><data key="node_observed_as_of">2025-05-06</data><data key="node_confidence">5</data><data key="node_notes">Only after direct claimant verification can DDS update DCPS and request source system update through FO.</data></node><node id="R170_E019"><data key="node_entity_id">R170_E019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Confirmed Contact Change Referral to FO MCS or MSSICS</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">After confirming claimant contact data, DDS updates DCPS for case development then requests FO change in MCS or MSSICS and UAT release; FO is responsible for claim-source record corrections.</data><data key="node_observed_status">observed_policy</data><data key="node_observed_as_of">2025-05-06</data><data key="node_confidence">5</data><data key="node_notes">Not an automatic DCPS to MBR or Numident update; no update without verification.</data></node><node id="R170_E020"><data key="node_entity_id">R170_E020</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">DDS Unappointed Third-Party Contact Report of Contact</data><data key="node_domain">Person / Evidence / Address Leads</data><data key="node_description">When an unappointed individual contacts DDS, a ROC records their name, phone number, address, with no claimant case information disclosed to the contact.</data><data key="node_observed_status">observed_policy</data><data key="node_observed_as_of">2025-05-06</data><data key="node_confidence">5</data><data key="node_notes">Third-party caller address cannot become claimant residence or benefit mailing address.</data></node><node id="R170_E021"><data key="node_entity_id">R170_E021</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Representative Misconduct and Fraud Referral</data><data key="node_domain">Program Integrity / Disability</data><data key="node_description">DDS personnel may submit Form SSA-166 to OGC and refer fraud/similar-fault allegations through ARIS to OIG.</data><data key="node_observed_status">observed_policy</data><data key="node_observed_as_of">2025-05-06</data><data key="node_confidence">5</data><data key="node_notes">Case-specific suspected violations do not establish any representative actually committed misconduct.</data></node><node id="R170_E022"><data key="node_entity_id">R170_E022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DDS Representative Appointment Revocation or Withdrawal Referral</data><data key="node_domain">Disability / Representative Appointments</data><data key="node_description">DDS logs verbal revocation/withdrawal and asks for signed notice; signed withdrawal is scanned into section B electronic file and sent to FO for processing.</data><data key="node_observed_status">observed_policy</data><data key="node_observed_as_of">2025-05-06</data><data key="node_confidence">5</data><data key="node_notes">DDS does not change registration status simply on verbal notice.</data></node><node id="R170_E023"><data key="node_entity_id">R170_E023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Cross-Channel Protective Filing Duplicate-Check by SSN and Program</data><data key="node_domain">Title II / Title XVI / Identity</data><data key="node_description">Before opening a new protective filing technicians inspect eLAS, EP, TED, WorkTrack and iClaim for unexpired filings under the same SSN and program.</data><data key="node_observed_status">current_policy</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes">Logical cross-system manual review, not common enterprise person database or universal federated search.</data></node><node id="R170_E024"><data key="node_entity_id">R170_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">iClaim Earliest Unexpired Partial Application Protective Date</data><data key="node_domain">Title II / Digital Intake</data><data key="node_description">iClaim can hold up to two partial application records; when both unexpired, the earliest start date controls protective filing if signed claim arrives in closeout period.</data><data key="node_observed_status">current_policy</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes">Protective filing depends on separately signed application and timing; no persistent identity-gateway inference.</data></node><node id="R170_E025"><data key="node_entity_id">R170_E025</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">iClaim Auxiliary Intent to File Not Captured Online</data><data key="node_domain">Title II / Person Identity</data><data key="node_description">iClaim does not collect intent to file for eligible auxiliary family members; FO staff must ask the number holder and record intent or provide closeout.</data><data key="node_observed_status">current_policy</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes">Family member listed on primary claim does not by itself establish auxiliary protective filing.</data></node><node id="R170_E026"><data key="node_entity_id">R170_E026</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eLAS Auxiliary Unscheduled Lead for Protective Filing</data><data key="node_domain">Title II / Title XVI / Work Control</data><data key="node_description">When a number holder expresses intent for child/spouse, field-office technicians can establish separate eLAS unscheduled leads and closeout notices for each qualifying auxiliary.</data><data key="node_observed_status">current_policy</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes">Requires individual intent; auxiliaries are separate people even when NH is their proper applicant.</data></node><node id="R170_E027"><data key="node_entity_id">R170_E027</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-2514 Record of Claimant Intent to File (Scheduling System Outage Fallback)</data><data key="node_acronym">SSA-2514</data><data key="node_domain">Title II / Title XVI / Paper Fallback</data><data key="node_description">When an appointment scheduling system cannot capture protective filing date, employees temporarily record intent on SSA-2514, back-enter upon restoration and destroy the paper form.</data><data key="node_observed_status">current_policy</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes">Form is temporary outage evidence, not an authoritative master person or address record.</data></node><node id="R170_E028"><data key="node_entity_id">R170_E028</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Mailed Protective Writing Two-Contact and Evidence Portal Closeout</data><data key="node_domain">Title II / Title XVI / Evidence</data><data key="node_description">Mailed signed writing contains contact address/telephone; staff attempt contact twice, send DPS manual closeout when no response and store writing plus notice in Evidence Portal.</data><data key="node_observed_status">current_policy</data><data key="node_observed_as_of">2026-04-27</data><data key="node_confidence">5</data><data key="node_notes">Contact address in writing is a supplied lead; POMS does not say it overwrites Numident, MBR or SSR.</data></node><node id="R170_E029"><data key="node_entity_id">R170_E029</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">WorkTrack Future-Appointment Evidence Hold</data><data key="node_domain">Field Operations / Evidence</data><data key="node_description">Proofs arriving before claim appointment/no claim established are faxed into WorkTrack and placed in Hold with Future Appointment reason and appointment date.</data><data key="node_observed_status">limited_rollout_2026</data><data key="node_observed_as_of">2026-08-26</data><data key="node_confidence">5</data><data key="node_notes">Human-managed hold status; not proof of system-level automatic future-claim association.</data></node><node id="R170_E030"><data key="node_entity_id">R170_E030</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">TED WLM Appointment Wrap-Up Work Status Codes</data><data key="node_domain">Customer Service / Work Routing</data><data key="node_description">WLM status categories include Pending-Requeued, Cancelled, Completed, Resolved-Incomplete and Resolved-No Show in TED wrap-up.</data><data key="node_observed_status">limited_rollout_2026</data><data key="node_observed_as_of">2026-08-26</data><data key="node_confidence">5</data><data key="node_notes">Exact underlying status storage schema unverified.</data></node><node id="R170_E031"><data key="node_entity_id">R170_E031</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">WLM Video Evidence Acceptance for Nonoriginal Proofs</data><data key="node_domain">Field Operations / Claims Evidence</data><data key="node_description">WLM claim interview may receive non-original proofs such as W-2s by video while original documents and DHS documents retained by claimant follow different intake routes.</data><data key="node_observed_status">limited_rollout_2026</data><data key="node_observed_as_of">2026-08-26</data><data key="node_confidence">5</data><data key="node_notes">Proof viewing is not an automated scan or permanent document-retention claim.</data></node><node id="R170_E032"><data key="node_entity_id">R170_E032</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">WLM Queue Return Exceptions Exclude Geographic Jurisdiction</data><data key="node_domain">Enterprise Work Management</data><data key="node_description">Work in WLM can return to queue for true conflict/skill/time/topic reasons but geographic claimant residence alone is not an acceptable reason under keep-what-you-take.</data><data key="node_observed_status">limited_rollout_2026</data><data key="node_observed_as_of">2026-08-26</data><data key="node_confidence">5</data><data key="node_notes">Specific limited rollout; not an agency-wide current dispatch mandate.</data></node><node id="R170_E033"><data key="node_entity_id">R170_E033</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSA FY2026 Small Business Prime and Subcontracting Procurement Goals</data><data key="node_domain">Procurement / Statistical Data</data><data key="node_description">OSDBU publicly reports FY2026 total small-business goals of 36.63 percent prime and 34.89 percent subcontract; includes SDVOSB, HUBZone and other goal categories.</data><data key="node_observed_status">public_fy2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Goals, not actual procurement awards, technology usage or confirmed vendor wins.</data></node><node id="R171_E001"><data key="node_entity_id">R171_E001</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts New OASDI Benefit Awards 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 awards for 6.447 million individuals, source: 100 percent Master Beneficiary Record data; award types are tabulated by retired, disabled, survivor and dependent classes.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E002"><data key="node_entity_id">R171_E002</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts Current-Payment OASDI Beneficiaries December 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 December current-payment-status beneficiaries, 70.451 million, source: Master Beneficiary Record 100 percent data.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E003"><data key="node_entity_id">R171_E003</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts Average Monthly OASDI Benefits by Sex December 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 average monthly benefits by sex and entitlement class, sourced from Master Beneficiary Record 100 percent data.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E004"><data key="node_entity_id">R171_E004</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts SSI Average Monthly Payments by Age December 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 December SSI average federally administered payments by age, $715 all ages, from Supplemental Security Record 100 percent data; retroactive payments excluded.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E005"><data key="node_entity_id">R171_E005</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts SSI Eligibility Basis and Age December 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 December SSI eligibility basis by age and impairment categories from Supplemental Security Record 100 percent data.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E006"><data key="node_entity_id">R171_E006</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts SSI Income Sources by Age December 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 December SSI other income source shares by age, including OASDI, other unearned income and earnings, from Supplemental Security Record 100 percent data.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E007"><data key="node_entity_id">R171_E007</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts Cross-Program OASDI and SSI Beneficiaries December 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 December unduplicated beneficiary population of 74.897 million, including 2.534 million with benefits from both OASDI and SSI; sources MBR and SSR 100 percent data, not a single enterprise person repository.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E008"><data key="node_entity_id">R171_E008</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts Disabled Beneficiaries Ages 18-64 by Program December 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 December unduplicated population of 10.102 million disabled beneficiaries ages 18–64 by OASDI and SSI program, from MBR and SSR 100 percent data.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E009"><data key="node_entity_id">R171_E009</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Fast Facts Cross-Program Beneficiaries Aged 65 or Older December 2025 Data Product</data><data key="node_domain">SSA Statistical Products / Publication Lineage</data><data key="node_description">2025 December unduplicated recipients age 65 or older, 58.257 million, combining MBR and SSR 100 percent data.</data><data key="node_observed_status">published_october_2026</data><data key="node_observed_as_of">2026-10</data><data key="node_confidence">5</data><data key="node_notes">Statistical compiled data product; does not establish physical ETL pipeline or beneficiary-level cross-system auto-updates.</data></node><node id="R171_E010"><data key="node_entity_id">R171_E010</data><data key="node_entity_type">published_statistical_report</data><data key="node_canonical_name">Annual Statistical Supplement 2017 Offices and Staff Section</data><data key="node_domain">SSA Statistical Publications</data><data key="node_description">2017 Supplement offices and staffing statistical section with tables 2.F1–2.F3.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2017</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R171_E011"><data key="node_entity_id">R171_E011</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2017 Table 2.F1 SSA Office Counts for 2016</data><data key="node_domain">SSA Operations / Geographic History</data><data key="node_description">Official 2016 office counts include 1,245 field offices, 33 resident stations and 164 hearing offices; sources: Office of Public Service and Operations Support database and ODAR Case Control System.</data><data key="node_observed_status">historical_statistics</data><data key="node_observed_as_of">2016-12</data><data key="node_confidence">5</data><data key="node_notes">Do not map this historic count as current 2026 field office inventory.</data></node><node id="R171_E012"><data key="node_entity_id">R171_E012</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2017 Table 2.F2 SSA Staff Composition September 2016</data><data key="node_domain">SSA Workforce / Statistical Products</data><data key="node_description">Official September 30 2016 count of 63,414 permanent employees and grade/characteristics from Human Resources Management Information System.</data><data key="node_observed_status">historical_statistics</data><data key="node_observed_as_of">2016-09-30</data><data key="node_confidence">5</data><data key="node_notes">Demographic aggregate table, not person-level public data.</data></node><node id="R171_E013"><data key="node_entity_id">R171_E013</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2017 Table 2.F3 SSA Work Years Series 1995-2017</data><data key="node_domain">SSA Workforce / Statistical Products</data><data key="node_description">Official published 1995–2017 full-time permanent staffing and work-year series sourced from SSA Payroll Reports.</data><data key="node_observed_status">historical_statistics</data><data key="node_observed_as_of">2017</data><data key="node_confidence">5</data><data key="node_notes">Historic time series and payroll reports are not proof of database technology or a live interface.</data></node><node id="R171_E014"><data key="node_entity_id">R171_E014</data><data key="node_entity_type">historical_data_repository</data><data key="node_canonical_name">Office of Public Service and Operations Support Office-Count Database (2016)</data><data key="node_domain">SSA Field Operations / Statistical Production</data><data key="node_description">SSA 2017 supplement explicitly identifies the Office of Public Service and Operations Support database as a source for 2016 office counts.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2016</data><data key="node_confidence">4</data><data key="node_notes">Physical hosting, schema, current existence and 2026 office scope unverified.</data></node><node id="R171_E015"><data key="node_entity_id">R171_E015</data><data key="node_entity_type">historical_case_control_system</data><data key="node_canonical_name">ODAR Case Control System (2016 Office Statistics Source)</data><data key="node_domain">Hearings and Appeals / Statistical Production</data><data key="node_description">SSA 2017 supplement explicitly names ODAR Case Control System as a source for offices and hearing-location statistics.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2016</data><data key="node_confidence">4</data><data key="node_notes">2016-era identifier; do not infer still operational or identical to other case systems.</data></node><node id="R171_E016"><data key="node_entity_id">R171_E016</data><data key="node_entity_type">historical_information_system</data><data key="node_canonical_name">SSA Human Resources Management Information System (2016 Reporting Source)</data><data key="node_domain">SSA HR / Statistical Production</data><data key="node_description">SSA 2017 supplement names its Human Resources Management Information System as the source of September 2016 workforce demographics by grade.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2016-09-30</data><data key="node_confidence">4</data><data key="node_notes">Does not identify hosting, schema, or current HR system name.</data></node><node id="R171_E017"><data key="node_entity_id">R171_E017</data><data key="node_entity_type">administrative_data_source</data><data key="node_canonical_name">SSA Payroll Reports (2017 Work-Years Statistical Source)</data><data key="node_domain">SSA HR / Statistical Production</data><data key="node_description">SSA 2017 supplement cites agency Payroll Reports as the source for FY1995–FY2017 headcount/work-year time series.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2017</data><data key="node_confidence">5</data><data key="node_notes">Published reporting source, not a specific technology deployment.</data></node><node id="R171_E018"><data key="node_entity_id">R171_E018</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSA Public-Use Field Office Listing, 2016 (Released June 2017)</data><data key="node_domain">SSA Office Geography / Research</data><data key="node_description">Consolidated historical list of SSA field offices for the 2016 period, released June 2017 for research use and derived in a Disability Research Consortium project.</data><data key="node_observed_status">released_june_2017</data><data key="node_observed_as_of">2017-06</data><data key="node_confidence">5</data><data key="node_notes">Not a 2026 active office roster or proof of current location/status; publication supplies no geocoding reliability guarantee.</data></node><node id="R171_E019"><data key="node_entity_id">R171_E019</data><data key="node_entity_type">research_project</data><data key="node_canonical_name">Disability Research Consortium Who Is Screened Out Office Listing Project</data><data key="node_domain">SSA Research / External Study</data><data key="node_description">The public-use catalog attributes the 2016 office listing to a Disability Research Consortium project called Who Is Screened Out? Application Costs and the Targeting of Disability Programs.</data><data key="node_observed_status">historical</data><data key="node_observed_as_of">2017-06</data><data key="node_confidence">5</data><data key="node_notes">Research lineage only; does not establish current software.</data></node><node id="R172_E001"><data key="node_entity_id">R172_E001</data><data key="node_entity_type">governance_rule</data><data key="node_canonical_name">HRS SSA Earnings Six-Year Prospective Consent Limit</data><data key="node_domain">Identity / Research Consent</data><data key="node_description">HRS SSA-linked earnings access currently has a maximum six-year prospective permission range.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Consent scope is separate from benefit records; does not describe SSA internal data retention.</data></node><node id="R172_E002"><data key="node_entity_id">R172_E002</data><data key="node_entity_type">governance_rule</data><data key="node_canonical_name">HRS SSA Benefits Twelve-Year Prospective Consent Limit</data><data key="node_domain">Identity / Research Consent</data><data key="node_description">HRS SSA-linked benefits access currently has a maximum twelve-year prospective permission range.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E003"><data key="node_entity_id">R172_E003</data><data key="node_entity_type">research_data_control</data><data key="node_canonical_name">HRS SSA Benefits Historical-Record Fallback</data><data key="node_domain">External Research Linkage</data><data key="node_description">When current SSA benefit information is unavailable owing to a respondent not providing renewed consent, the HRS cross-year benefits product may use the most recent prior administrative data.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not treat a missing recent observation as no benefits; not a current SSA master-record update.</data></node><node id="R172_E004"><data key="node_entity_id">R172_E004</data><data key="node_entity_type">research_governance_event</data><data key="node_canonical_name">HRS 2006 Prospective SSA Permission Transition</data><data key="node_domain">External Research Linkage</data><data key="node_description">HRS administrative-data agreements changed in 2006 to permit prospective access to subsequent biennial earnings/benefits updates with re-consent limitations.</data><data key="node_observed_status">documented_historical_policy</data><data key="node_observed_as_of">2006-01-01</data><data key="node_confidence">5</data><data key="node_notes">Historic operational change documented in an April 2026 HRS product page; not claimed as a new 2026 event.</data></node><node id="R172_E005"><data key="node_entity_id">R172_E005</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSA Fast-Track Disability Receipt State Statistics FY2010–2024</data><data key="node_domain">Disability / Public Data</data><data key="node_description">Published state-level annual counts of initial disability cases flagged QDD, Compassionate Allowances, or both, plus DDS electronic receipts and percent fast track; published years FY2010–FY2024.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Reporting state is location of DDS/EST/federal accepting the transferred claim, not necessarily claimant residence.</data></node><node id="R172_E006"><data key="node_entity_id">R172_E006</data><data key="node_entity_type">public_data_distribution</data><data key="node_canonical_name">Fast-Track Disability Receipt CSV FY2010–2024</data><data key="node_domain">Disability / Public Data</data><data key="node_description">CSV distribution of SSA Fast-Track Disability Receipt State Statistics FY2010–2024.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E007"><data key="node_entity_id">R172_E007</data><data key="node_entity_type">public_data_distribution</data><data key="node_canonical_name">Fast-Track Disability Receipt XLSX FY2010–2024</data><data key="node_domain">Disability / Public Data</data><data key="node_description">Excel XLSX distribution of SSA Fast-Track Disability Receipt State Statistics FY2010–2024.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E008"><data key="node_entity_id">R172_E008</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">Fast-Track DDS Acceptance Geography Classification</data><data key="node_domain">Disability / Geographic Attribution</data><data key="node_description">State represents location of the DDS, Extended Service Team or federal component accepting an initial electronic case, not necessarily the claimant residence.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E009"><data key="node_entity_id">R172_E009</data><data key="node_entity_type">statistical_counting_rule</data><data key="node_canonical_name">Fast-Track QDD-CAL Combined Case-Counting Rule</data><data key="node_domain">Disability / Data Lineage</data><data key="node_description">A fast-track case includes QDD, CAL or both; cases are counted by accepted DDS electronic receipts, with overlapping QDD/CAL not an additive total.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E010"><data key="node_entity_id">R172_E010</data><data key="node_entity_type">statistical_counting_rule</data><data key="node_canonical_name">Fast-Track Percentage Accepted-Electronic-Receipt Denominator</data><data key="node_domain">Disability / Data Lineage</data><data key="node_description">State percentage is the ratio of accepted fast-track initial disability receipts to total accepted DDS electronic initial disability receipts for the same FY.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E011"><data key="node_entity_id">R172_E011</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">SSDI Initial Claims Annual Spoken-Language Preferences FY2023-Onward</data><data key="node_domain">Disability / Language / Open Data</data><data key="node_description">SSA Open Data annual-file product of spoken language preferences for SSDI initial claims, starting FY2023, updated November 24 2025.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source title and CSV filename say annual/yearly while body incorrectly describes quarterly. Frequency conflict remains open; do not equate with separately cataloged quarterly dataset.</data></node><node id="R172_E012"><data key="node_entity_id">R172_E012</data><data key="node_entity_type">public_data_distribution</data><data key="node_canonical_name">SSDI Initial Claims Spoken-Language Annual CSV FY2023-Onward</data><data key="node_domain">Disability / Language / Open Data</data><data key="node_description">Public CSV distribution FY23-onwards-LEP-Spklang-IC-T2-Dib-Yrly.csv.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E013"><data key="node_entity_id">R172_E013</data><data key="node_entity_type">publication_metadata_conflict</data><data key="node_canonical_name">SSDI Annual LEP Reporting Period Label Conflict</data><data key="node_domain">Disability / Quality</data><data key="node_description">SSA dataset heading says annual and CSV basename contains Yrly but introductory text says quarterly; frequency ambiguity is recorded rather than silently corrected.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Conflict affects interpretation of time grain, not existence of the file.</data></node><node id="R172_E014"><data key="node_entity_id">R172_E014</data><data key="node_entity_type">published_statistical_input</data><data key="node_canonical_name">Disability Fiscal-Year State Census Eligible-Population Input</data><data key="node_domain">Disability / Statistical Production</data><data key="node_description">Census state-level ages 0-17 and 18-64 population estimates (typically July 1) used as denominators in SSA FY Disability Claim Data.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Different geography from state adjudicating DDS workload. Population source is residence, while workload is adjudicating office.</data></node><node id="R172_E015"><data key="node_entity_id">R172_E015</data><data key="node_entity_type">published_statistical_input</data><data key="node_canonical_name">Disability Fiscal-Year Published Beneficiary Population Input</data><data key="node_domain">Disability / Statistical Production</data><data key="node_description">SSA published SSDI and SSI end-of-calendar-year state-level beneficiary counts serve as separate input to the FY disability claim statistics; includes duplicate-removal treatment for concurrent beneficiaries.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source documents historical table extracts; publication updates may lag workload counts.</data></node><node id="R172_E016"><data key="node_entity_id">R172_E016</data><data key="node_entity_type">publication_update_rule</data><data key="node_canonical_name">Disability Fiscal-Year Two-Phase Publication Update Cycle</data><data key="node_domain">Disability / Publication Pipeline</data><data key="node_description">SSA describes a first FY workload refresh around November and a later population/beneficiary refresh around May. Entire CSV is replaced; old public revisions are not retained at the same URL.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Approximate schedule reported by source, not a committed API SLA.</data></node><node id="R172_E017"><data key="node_entity_id">R172_E017</data><data key="node_entity_type">geographic_provenance_rule</data><data key="node_canonical_name">Disability Fiscal-Year Claim-Location Versus Residence State Boundary</data><data key="node_domain">Disability / Statistical Quality</data><data key="node_description">Annual SSA data combines DDS state-of-processing workload counts with state-of-residence beneficiary and Census denominators; direct state-to-state residence inference from DDS workload is invalid.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E018"><data key="node_entity_id">R172_E018</data><data key="node_entity_type">statistical_counting_rule</data><data key="node_canonical_name">Disability Fiscal-Year Concurrent Benefit Person Counting Rule</data><data key="node_domain">Disability / Identity / Publication</data><data key="node_description">The FY disability dataset counts simultaneous SSI and SSDI disability receipt as one beneficiary for applicable population figures; claim filing/receipt counting follows separate definitions.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R172_E019"><data key="node_entity_id">R172_E019</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">SSI Redetermination No-Change Address Reconciliation Gate</data><data key="node_domain">Title XVI / Address Provenance</data><data key="node_description">At RZ, when a recipient alleges no move or an old/new address already appears on SSR, no further change-of-address development is needed; when absent, employees test unreported move versus temporary absence.</data><data key="node_observed_status">documented_current</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026-09-10 POMS. An allegation alone does not assert a new SSR record change.</data></node><node id="R172_E020"><data key="node_entity_id">R172_E020</data><data key="node_entity_type">restricted_research_data_collection</data><data key="node_canonical_name">Historical NCHS-SSA Linked Administrative Research File Family</data><data key="node_domain">External Research / Data Linkage</data><data key="node_description">Archived federal NCHS documentation identifies restricted survey-linked SSA MBR, SSR, PHUS, Form 831 disability, and MEF summarized quarters-of-coverage files.</data><data key="node_observed_status">documented_historical_not_current_verified</data><data key="node_observed_as_of">2015-01-01</data><data key="node_confidence">4</data><data key="node_notes">Archival evidence predates window and is included only as historical reference; current 2026 SSA exchange status not confirmed.</data></node><node id="R172_E021"><data key="node_entity_id">R172_E021</data><data key="node_entity_type">restricted_research_data_product</data><data key="node_canonical_name">Historical NCHS-SSA Summarized MEF Quarters-of-Coverage Extract</data><data key="node_domain">External Research / Earnings</data><data key="node_description">Historical NCHS linked SSA input described as special extract of summarized quarters of coverage from MEF.</data><data key="node_observed_status">documented_historical_not_current_verified</data><data key="node_observed_as_of">2015-01-01</data><data key="node_confidence">4</data><data key="node_notes">Do not infer current transmission, full MEF availability, or new SSA master record.</data></node><node id="R172_E022"><data key="node_entity_id">R172_E022</data><data key="node_entity_type">research_access_rule</data><data key="node_canonical_name">NCHS Restricted-Use Linked Research Data Center Access Gate</data><data key="node_domain">External Research / Privacy</data><data key="node_description">NCHS says access to restricted linked administrative files requires approved research through its Research Data Center network; this is an access arrangement, not public release of PII.</data><data key="node_observed_status">current_general_nchs_access_control</data><data key="node_observed_as_of">2025-07-17</data><data key="node_confidence">5</data><data key="node_notes">2025 page is program-general; specific 2015 NCHS–SSA files current availability remains unproven.</data></node><node id="R173_E001"><data key="node_entity_id">R173_E001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DEDA Qualified Examiner Initial Adult Medical Signature Process</data><data key="node_domain">Disability / Initial Adjudication</data><data key="node_description">Qualified disability examiner may sign specified medical assessments for fully favorable adult initial physical-impairment cases without medical consultant review subject to program eligibility and site recruitment conditions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E002"><data key="node_entity_id">R173_E002</data><data key="node_entity_type">decision_rule</data><data key="node_canonical_name">DEDA Initial-Cases Fully Favorable Physical-Only Eligibility Gate</data><data key="node_domain">Disability / Medical Decision Authority</data><data key="node_description">Only initial adult physical-impairment cases with established onset date on or before potential onset date and fully favorable result qualify; reconsideration, fraud, medical equivalence, reopened denials and other excluded classes do not qualify.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E003"><data key="node_entity_id">R173_E003</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DEDA Medical Consultant 18-Month Recruitment Evidence Requirement</data><data key="node_domain">Disability / Workforce Governance</data><data key="node_description">Each participating site documents every reasonable effort to recruit medical consultants within prior 18 months; policy specifies compensation, advertising, recruitment outreach, workplace flexibilities, and medical consultant peer outreach.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E004"><data key="node_entity_id">R173_E004</data><data key="node_entity_type">administrative_record</data><data key="node_canonical_name">DEDA Examiner Qualification and Supervisor-Approval Record</data><data key="node_domain">Disability / Workforce Identity</data><data key="node_description">DDS or assisting component maintains documentation of medical-examiner qualification: at least 12 months posttraining adult adjudication experience, demonstrated case analysis and management approval.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E005"><data key="node_entity_id">R173_E005</data><data key="node_entity_type">form_entry_rule</data><data key="node_canonical_name">DEDA SSA-831 Medical-Consultant Signature Omission and Item-34 Remark</data><data key="node_domain">Disability / Decision Evidence</data><data key="node_description">On initial SSA-831 determination under DEDA, leave medical-consultant/pyschological-consultant signature items 32 and 33 blank and enter Disability Examiner Decisional Authority in Item 34 remarks.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E006"><data key="node_entity_id">R173_E006</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-4734 Physical Residual Functional Capacity Assessment</data><data key="node_domain">Disability / Medical Assessment</data><data key="node_description">POMS DI 39563.900 identifies Form SSA-4734 as a physical RFC assessment a qualifying examiner may sign under DEDA.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E007"><data key="node_entity_id">R173_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">DEDA Temporary CDR Age-18 and EXR Extension</data><data key="node_domain">Disability / Medical Decision Authority</data><data key="node_description">October 2026 POMS describes a proposed/temporary one-year expansion to qualifying CDR continuances, fully favorable age-18 redeterminations and favorable adult expedited reinstatements. Source lacks concrete effective and expiration dates.</data><data key="node_observed_status">documented_temporary_start_unresolved</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R173_E008"><data key="node_entity_id">R173_E008</data><data key="node_entity_type">decision_rule</data><data key="node_canonical_name">DEDA CDR Physical-Only Continuance Gate</data><data key="node_domain">Disability / CDR</data><data key="node_description">Only physical-only adult CDR continuances meeting medical-evidence conditions qualify; cessations and cases with prior CPD mental impairment are excluded.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E009"><data key="node_entity_id">R173_E009</data><data key="node_entity_type">decision_rule</data><data key="node_canonical_name">DEDA Fully Favorable Age-18 Redetermination Gate</data><data key="node_domain">Disability / Age-18 Review</data><data key="node_description">Under published temporary extension, a physical-only fully favorable adult-rule age-18 redetermination may qualify; medical equivalence cases and cessations are excluded.</data><data key="node_observed_status">documented_temporary_start_unresolved</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R173_E010"><data key="node_entity_id">R173_E010</data><data key="node_entity_type">decision_rule</data><data key="node_canonical_name">DEDA EXR Same-or-Related Favorable Impairment Gate</data><data key="node_domain">Disability / EXR</data><data key="node_description">Under published extension, adult EXR must involve same or related impairment as comparison point decision and result in favorable physical-only determination under medical improvement standards.</data><data key="node_observed_status">documented_temporary_start_unresolved</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R173_E011"><data key="node_entity_id">R173_E011</data><data key="node_entity_type">form_entry_rule</data><data key="node_canonical_name">DEDA Extension SSA-832 and SSA-833 Remarks and Blank-Signature Control</data><data key="node_domain">Disability / Decision Evidence</data><data key="node_description">For qualifying extension cases, enter Disability Examiner Decisional Authority in remarks item 24 and leave MC/PC signature/specialty/date fields 27,28,30,30A blank.</data><data key="node_observed_status">documented_temporary_start_unresolved</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R173_E012"><data key="node_entity_id">R173_E012</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">DDS Evidence Request Initial Ten-Day and Follow-Up Ten-Day Control</data><data key="node_domain">Disability / Evidence Development</data><data key="node_description">If no response within 10 calendar days after initial claimant evidence/action request, DDS follows up once and allows 10 more calendar days, with good-reason extensions and special-handling exceptions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E013"><data key="node_entity_id">R173_E013</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">DDS Special-Handling Third-Party Before Evidence-In-File Decision</data><data key="node_domain">Disability / Due Process</data><data key="node_description">After noncooperation in special-handling cases, DDS must make reasonable efforts to identify and involve a third party before evidence-in-file determination; continued independent medical development remains required.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E014"><data key="node_entity_id">R173_E014</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">DDS Evidence Follow-Up Minimal Voicemail Disclosure Boundary</data><data key="node_domain">Disability / Contact Privacy</data><data key="node_description">When leaving a voicemail or speaking to another person, DDS omits case identifiers and detailed claim information; sends a call-in letter and documents the contact in SSA-5002 or DCPS and CDW.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E015"><data key="node_entity_id">R173_E015</data><data key="node_entity_type">customer_notice</data><data key="node_canonical_name">DDS Written Consultative Examination Appointment Notice Content</data><data key="node_domain">Disability / Consultative Exam</data><data key="node_description">Required notice describes exam purpose and timing, CE provider name/address/phone where available, government photo ID, interpreter access, expenses, confirmation, missed-CE risk, and DDS contact.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E016"><data key="node_entity_id">R173_E016</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">DDS More-Than-Ten-Day CE Confirmation Follow-Up</data><data key="node_domain">Disability / Consultative Exam</data><data key="node_description">For CE scheduled more than 10 days after notice, lack of confirmation within 10 days triggers a telephone attempt and, where needed, call-in letter; special-handling contact rules differ.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E017"><data key="node_entity_id">R173_E017</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">DDS Short-Notice CE Ten-Day-or-Less Contact and Reschedule Rule</data><data key="node_domain">Disability / Consultative Exam</data><data key="node_description">Appointments within ten days of written notice have special telephone notification and good-reason rescheduling rules; special-handling exceptions require third-party involvement.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E018"><data key="node_entity_id">R173_E018</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">DDS Missed-CE Good-Reason and Special-Handling Escalation</data><data key="node_domain">Disability / Consultative Exam</data><data key="node_description">DDS records no-show, examines good reason when necessary and gives qualifying special-handling cases additional claimant/third-party effort before stopping CE development.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E019"><data key="node_entity_id">R173_E019</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">DDS Correctional-Facility CE Staff-Presence Consent Gate</data><data key="node_domain">Disability / Privacy</data><data key="node_description">Where non-provider corrections staff may be present during on-site CE, DDS requests claimant SSA-3288 or equivalent consent addressing potential disclosure.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E020"><data key="node_entity_id">R173_E020</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">DDS Third-Party Discovery Conditional Eligibility Rule</data><data key="node_domain">Disability / Special Handling</data><data key="node_description">To seek a new assisting contact, DDS checks special-handling status, appointed representative conditions, prior contact information, claimant refusal, and missed evidence or CE requests.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E021"><data key="node_entity_id">R173_E021</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">DDS Claimant-Nominated Third-Party Contact Information</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">Claimant gives third-party name and phone or address for claimant-contact assistance; belongs to the third party and is not claimant verified residential or correspondence address.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E022"><data key="node_entity_id">R173_E022</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">DDS Nonprofessional Third-Party Independent Lookup Restriction</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">DDS must not search for a nonprofessional third party telephone number or address in books/online; professional at a particular location is a stated exception.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E023"><data key="node_entity_id">R173_E023</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">DDS Third-Party Ten-Day Outreach and Identity Verification</data><data key="node_domain">Disability / Special Handling</data><data key="node_description">DDS verifies contact identity, requests assistance with claimant action or CE, documents effort and allows ten additional days where applicable; minimum disclosure and voicemail controls apply.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E024"><data key="node_entity_id">R173_E024</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination Life Insurance Ownership Development</data><data key="node_domain">Title XVI / Resources</data><data key="node_description">SSI Claims redetermination path or SSA-8203-BK question 18 captures owner, insured, company, policy identifier, face value, cash surrender value and loan; conflict with prior allegation triggers development.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E025"><data key="node_entity_id">R173_E025</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSI Life Insurance Insurer Address for Resource Verification</data><data key="node_domain">Title XVI / Address Provenance</data><data key="node_description">The name and address of an insurance company collected under SSA-8203-BK question 18 are provider contact data and must not be represented as the recipient mailing or residence address.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E026"><data key="node_entity_id">R173_E026</data><data key="node_entity_type">decision_rule</data><data key="node_canonical_name">SSI Lapsed-or-Cashed-Out Insurance Historical Value Verification</data><data key="node_domain">Title XVI / Resources</data><data key="node_description">When previously countable policy is cashed or lapses and applicant has no records, SSA contacts insurer and verifies cash surrender value for review period through date of event; below-market transfers require additional development.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E027"><data key="node_entity_id">R173_E027</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">OACT Historical OASI and DI Administrative Expense Table 1957–2025</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">Public OACT table displays administrative expense amounts and administrative expense share of total cost, by OASI and DI trust fund and combined, for calendar years 1957–2025; no internal ETL or system is identified.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R173_E028"><data key="node_entity_id">R173_E028</data><data key="node_entity_type">statistical_counting_rule</data><data key="node_canonical_name">OACT Trust Fund Administrative Expense Percentage of Total Cost</data><data key="node_domain">Actuarial / Statistical Definitions</data><data key="node_description">The OACT table relates administrative expenses to total cost for OASI, DI and combined trust funds by calendar year. It is not an SSA entire-agency appropriations/spending breakdown.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E001"><data key="node_entity_id">R174_E001</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS Exclusion Appeal (EEAI) Screen</data><data key="node_domain">Disability; Appeals</data><data key="node_description">For EDCS-excluded Title II medical-CDR reconsideration and hearings, FO enters appeal request into the DCF using the EEAI screen.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026 POMS section C.2; no database product or transport inferred.</data></node><node id="R174_E002"><data key="node_entity_id">R174_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">EDCS-Excluded Title II Medical CDR Appeal T2R Posting Workflow</data><data key="node_domain">Disability; Payments</data><data key="node_description">Documented workflow: EEAI input creates DCF appeal/SBC data, DCF passes those details to the Title II Redesign background program, and that program automatically updates MBR for qualifying reconsideration.</data><data key="node_observed_status">documented_conditional</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Exclusion pathway, not a universal EDCS case transfer; 2026 DI 12026.025C.2.</data></node><node id="R174_E003"><data key="node_entity_id">R174_E003</data><data key="node_entity_type">exception_control</data><data key="node_canonical_name">Title II CDR Hearing Reversal Manual POS Posting Exception</data><data key="node_domain">Disability; Appeals</data><data key="node_description">For an excluded Title II CDR hearing appeal, hearing affirmation, abandonment, dismissal or withdrawal automatically posts to MBR, but hearing reversal requires POS input to update MBR.</data><data key="node_observed_status">documented_conditional</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">2026 POMS DI 12026.025C.2; do not generalize to all CDR appeals.</data></node><node id="R174_E004"><data key="node_entity_id">R174_E004</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSA-789 Incomplete Hearing and Interpreter Development 15-Day Diary</data><data key="node_domain">Disability; Appeals</data><data key="node_description">If reconsideration SSA-789 lacks hearing-preference or interpreter information and telephone contact fails, FO sends a call-in letter and sets a 15-day diary before forwarding unresolved case.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Specific FO procedural follow-up, not an identified physical diary table.</data></node><node id="R174_E005"><data key="node_entity_id">R174_E005</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Section 6.F OASDI Benefit Terminations</data><data key="node_domain">Statistics; Title II</data><data key="node_description">SSA 2026 statistical section 6.F reports benefits terminated by beneficiary type, reason and year, using 100-percent MBR data.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E006"><data key="node_entity_id">R174_E006</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Table 6.F1 Terminations by Benefit Type 1940–2025</data><data key="node_domain">Statistics; Title II</data><data key="node_description">Published historical series of benefit terminations by year and beneficiary type through 2025. Historical data are publication observations, not revived legacy systems.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E007"><data key="node_entity_id">R174_E007</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Table 6.F2 Terminations by Reason and Benefit Type 2025</data><data key="node_domain">Statistics; Disability</data><data key="node_description">MBR-based counts of 2025 benefit terminations by reasons including death, SGA, medical improvement, noncooperation, and transfer at full retirement age.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E008"><data key="node_entity_id">R174_E008</data><data key="node_entity_type">publication_definition</data><data key="node_canonical_name">OASDI 2025 Termination Reporting Date Versus Effective Date Rule</data><data key="node_domain">Statistics; Title II</data><data key="node_description">Table 6.F2 counts beneficiaries whose benefits terminated during calendar year 2025 without filtering to terminations effective in 2025.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A report-period count, not a master-record event effective-date claim.</data></node><node id="R174_E009"><data key="node_entity_id">R174_E009</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">OASDI Termination Statistics Actuarial Method Comparability Caveat</data><data key="node_domain">Statistics; Actuarial</data><data key="node_description">Table 6.F notes warn that reported figures can differ from Actuarial Services because sources and calculation methods differ.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not equate OACT projections and this MBR administrative publication.</data></node><node id="R174_E010"><data key="node_entity_id">R174_E010</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Disability Cessation Reason Counts 2025</data><data key="node_domain">Statistics; Disability</data><data key="node_description">2025 table 6.F2 reports disability cessation within benefit terminations, including separate medical-improvement, substantial gainful activity and failure-to-cooperate categories; counts are statistics, not individual adjudicative case records.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E011"><data key="node_entity_id">R174_E011</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Section 5.H Beneficiary Families</data><data key="node_domain">Statistics; Person/Identity</data><data key="node_description">Section 5.H publishes statistics on OASDI beneficiary family configurations, primary insurance amounts and monthly family benefits.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E012"><data key="node_entity_id">R174_E012</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Table 5.H1 Beneficiary Family Historical Series</data><data key="node_domain">Statistics; Title II</data><data key="node_description">Historical counts and average benefits for selected retired worker, disabled worker and survivor family groups by year.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E013"><data key="node_entity_id">R174_E013</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Table 5.H2 Family Versus Individual Beneficiary Counts</data><data key="node_domain">Statistics; Person/Identity</data><data key="node_description">Section 5.H2 separately reports number of beneficiary families and individual beneficiaries by selected family groups in December 2025.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Family unit and person count are not equivalent and do not prove a physical Person repository.</data></node><node id="R174_E014"><data key="node_entity_id">R174_E014</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">Historical 5.H1 Sampling-Rate Comparability Rule</data><data key="node_domain">Statistics; Data Provenance</data><data key="node_description">For published family series, MBR-based observations 1945–1984 use varying samples, 1985–2005 use 10-percent sample, and other years use 100-percent data.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Changing sampling design is a reporting attribute, not MBR record retention or a change to master data.</data></node><node id="R174_E015"><data key="node_entity_id">R174_E015</data><data key="node_entity_type">publication_definition</data><data key="node_canonical_name">2026 Statistical Supplement Family Benefit Dual-Entitlement Reporting Rule</data><data key="node_domain">Statistics; Person/Identity</data><data key="node_description">When a disabled worker spouse is also dually entitled as a retired worker, table 5.H2 reports spouse benefit as difference between the spouse entitlement and retired-worker entitlement.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">One individual may have dual entitlements; do not double count people or mistake benefit increments for full individual payments.</data></node><node id="R174_E016"><data key="node_entity_id">R174_E016</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Section 5.M International Agreement Benefits</data><data key="node_domain">Statistics; External Agreements</data><data key="node_description">Section 5.M reports OASDI beneficiary totals and average monthly benefits under U.S. international totalization agreements.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E017"><data key="node_entity_id">R174_E017</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Table 5.M1 Totalization Beneficiaries by Country</data><data key="node_domain">Statistics; External Agreements</data><data key="node_description">Table 5.M1 reports selected-year totals from 1983 through 2025 and country detail for 2025, by benefit type.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E018"><data key="node_entity_id">R174_E018</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">5.M Country-of-Agreement Versus Residential Address Attribution Rule</data><data key="node_domain">Address Provenance; Statistics</data><data key="node_description">Country in the totalization benefit statistical table identifies the applicable agreement-country grouping and cannot be treated as a verified mailing or residential address.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Analytical modeling guardrail from purpose of geographic category; not an SSA statement about beneficiary address. Do not assert country of residence.</data></node><node id="R174_E019"><data key="node_entity_id">R174_E019</data><data key="node_entity_type">publication_definition</data><data key="node_canonical_name">2026 International Agreement Statistics Cell-Suppression Convention</data><data key="node_domain">Statistics; Privacy</data><data key="node_description">Section 5.M uses (X) to suppress potentially disclosive small-category information and marks inapplicable cells separately.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E020"><data key="node_entity_id">R174_E020</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">2026 Statistical Supplement Table 6.E5 Withheld Spouse and Child Benefits by Reason</data><data key="node_domain">Statistics; Title II</data><data key="node_description">December 2025 MBR-based table breaks out payment withholding reasons among spouses, children, disabled adult children and students by basis of entitlement.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R174_E021"><data key="node_entity_id">R174_E021</data><data key="node_entity_type">publication_definition</data><data key="node_canonical_name">2026 OASDI Withholding Address Unknown Reporting Category</data><data key="node_domain">Statistics; Address Provenance</data><data key="node_description">Published Table 6.E4 and 6.E5 list address unknown as a reason for withheld benefits; this is an administrative reporting category, not the acquisition or update of a residence address.</data><data key="node_observed_status">observed_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not convert unknown-address classification into address-change evidence.</data></node><node id="R174_E022"><data key="node_entity_id">R174_E022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Medical CDR Reconsideration Career Railroad and Foreign Case Routing Exception</data><data key="node_domain">Disability; External Partners</data><data key="node_description">For career railroad CDR appeals FO directs folder to Great Lakes Program Service Center; foreign CDR appeals route to Office of Earnings and International Operations rather than normal servicing DDS.</data><data key="node_observed_status">documented_conditional</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Separate jurisdictional document routes; mail address is organizational destination, not claimant address.</data></node><node id="R174_E023"><data key="node_entity_id">R174_E023</data><data key="node_entity_type">organizational_component</data><data key="node_canonical_name">Great Lakes Program Service Center (GLPSC)</data><data key="node_domain">Operations; Disability</data><data key="node_description">SSA organizational destination for career railroad medical-CDR reconsideration folders under DI 12026.025D.2; physical address of this office is not a beneficiary address.</data><data key="node_observed_status">documented_operational</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Operational location in POMS 2026; no inference about facility ownership or successor.</data></node><node id="R175_E0001"><data key="node_entity_id">R175_E0001</data><data key="node_entity_type">financial_data_attribute</data><data key="node_canonical_name">Representative Payee Beneficiary-Owned Fiduciary Account Title</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">Financial account title identifies beneficiary as owner and representative payee as fiduciary; applies to direct deposit and conserved funds.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Does not identify a distinct physical SSA account repository.</data></node><node id="R175_E0002"><data key="node_entity_id">R175_E0002</data><data key="node_entity_type">payment_governance_rule</data><data key="node_canonical_name">Co-Resident Parent or Spouse Payee Personal Checking Account Exception</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">Exception permits some parent or spouse payees to receive benefits to personal checking when co-resident, limited to current expenses, and approved by FO confirmation.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0003"><data key="node_entity_id">R175_E0003</data><data key="node_entity_type">payment_governance_rule</data><data key="node_canonical_name">Payee Personal Savings Account Exception Prohibition</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">Exception for co-resident spouse or parent checking accounts does not extend to personal savings accounts.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0004"><data key="node_entity_id">R175_E0004</data><data key="node_entity_type">external_financial_process</data><data key="node_canonical_name">Government Agency Payee General Depository Pass-through</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">State or local governmental payee may route through mandated general depository account if promptly transferred to protected fiduciary subaccount.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0005"><data key="node_entity_id">R175_E0005</data><data key="node_entity_type">external_account_control</data><data key="node_canonical_name">Government Agency Payee Protected Fiduciary Subaccount</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">Protected government agency subaccount maintains beneficiaries funds separately from government uses.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0006"><data key="node_entity_id">R175_E0006</data><data key="node_entity_type">external_financial_record</data><data key="node_canonical_name">Government Foster-Care Payee Child Cost-of-Care Ledger</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">State/local childcare or foster-care account maintains beneficiary-level deposit and expense ledgers as condition of account-title exception.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0007"><data key="node_entity_id">R175_E0007</data><data key="node_entity_type">identity_governance_rule</data><data key="node_canonical_name">Payee Collective Account Name Match to eRPS</data><data key="node_domain">Person / Representative Payee</data><data key="node_description">Collective account payee name must match the named appointed representative payee in eRPS.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0008"><data key="node_entity_id">R175_E0008</data><data key="node_entity_type">identity_governance_rule</data><data key="node_canonical_name">Organizational Payee DBA and Legal Entity Bank-Title Rule</data><data key="node_domain">Person / Representative Payee</data><data key="node_description">For organizational payee DBA arrangements, account name identifies the actually appointed payee; parent legal corporation is not automatically the payee.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0009"><data key="node_entity_id">R175_E0009</data><data key="node_entity_type">payment_governance_rule</data><data key="node_canonical_name">Subsidiary or Branch Organizational Payee Fiduciary Holder Rule</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">When an organization branch or subsidiary rather than its parent is appointed as payee, collective account titling uses the appointed branch or subsidiary.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0010"><data key="node_entity_id">R175_E0010</data><data key="node_entity_type">payment_governance_rule</data><data key="node_canonical_name">Traditional Trust Account Ineligible as Payee Collective Account</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">A traditional trust fund account cannot serve as representative payee collective account merely by title.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0011"><data key="node_entity_id">R175_E0011</data><data key="node_entity_type">logical_relationship_rule</data><data key="node_canonical_name">Payee Account Beneficiary Ownership and Payee Control Separation</data><data key="node_domain">Person / Representative Payee</data><data key="node_description">Beneficiary retains ownership but no direct access, while the representative payee manages funds in fiduciary capacity.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0012"><data key="node_entity_id">R175_E0012</data><data key="node_entity_type">payment_governance_rule</data><data key="node_canonical_name">Government Agency Childcare-Fund Account Exception</data><data key="node_domain">Representative Payee / Payments</data><data key="node_description">State or local childcare/foster-care account may receive/pay care expenses under the specified beneficiary protection, ledger, and collective-account requirements.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0013"><data key="node_entity_id">R175_E0013</data><data key="node_entity_type">person_governance_rule</data><data key="node_canonical_name">Payee Co-Residence and Current-Expense Verification</data><data key="node_domain">Person / Representative Payee</data><data key="node_description">Field office must confirm parent/spouse payee and beneficiary reside together and funds pay current expenses before personal checking exception.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0014"><data key="node_entity_id">R175_E0014</data><data key="node_entity_type">form</data><data key="node_canonical_name">MA-416 Medical Advisor Evaluation</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Medical Advisor analysis and signature form entered in DCPS; not equivalent to consultant responsibility for the medical determination.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0015"><data key="node_entity_id">R175_E0015</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DCPS Evaluations and Assessments Section</data><data key="node_domain">Disability / Evidence</data><data key="node_description">DCPS section used for SSA-416 and MA-416 medical evaluations for electronic and paper case processing.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0016"><data key="node_entity_id">R175_E0016</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DCPS Impairment Severity and Sign Page</data><data key="node_domain">Disability / Evidence</data><data key="node_description">DCPS page containing the Evaluations and Assessments section for SSA-416 and MA-416.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0017"><data key="node_entity_id">R175_E0017</data><data key="node_entity_type">medical_evaluation_attribute</data><data key="node_canonical_name">SSA-416 Evaluation Period Selector</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Classifies evaluation period as current, date last insured, twelve months after onset, or another period.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0018"><data key="node_entity_id">R175_E0018</data><data key="node_entity_type">medical_evaluation_attribute</data><data key="node_canonical_name">SSA-416 Medical Finding Subject Selector</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Specifies each medical finding evaluated, potentially more than one subject for a 416.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0019"><data key="node_entity_id">R175_E0019</data><data key="node_entity_type">medical_signature_control</data><data key="node_canonical_name">SSA-416 Medical Completion Statement</data><data key="node_domain">Disability / Evidence</data><data key="node_description">MC or PC checks final medical-portion-complete statement only for completed, not preliminary, partial, or advisory evaluations.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0020"><data key="node_entity_id">R175_E0020</data><data key="node_entity_type">medical_signature_metadata</data><data key="node_canonical_name">DCPS Medical Specialty Code and Signature Date Recording</data><data key="node_domain">Disability / Evidence</data><data key="node_description">DCPS sign-and-save actions populate professional specialty code and date signed on SSA-416 or MA-416.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0021"><data key="node_entity_id">R175_E0021</data><data key="node_entity_type">medical_review_process</data><data key="node_canonical_name">DCPS Signed Assessment Unsign-Revise-Resign Workflow</data><data key="node_domain">Disability / Evidence</data><data key="node_description">For needed corrections to signed assessments before DDS closure, unsign, revise, and re-sign. DE cannot edit an MC/PC/MA-signed assessment.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0022"><data key="node_entity_id">R175_E0022</data><data key="node_entity_type">medical_review_role_rule</data><data key="node_canonical_name">Medical Advisor MA-416 Nondecisional Evaluation Scope</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Medical Advisor enters and signs medical analysis on MA-416 rather than signing the overall MC/PC determination.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">The 2026 limited DEDA examiner-signature exception applies to qualified cases and must not be generalized to MA roles.</data></node><node id="R175_E0023"><data key="node_entity_id">R175_E0023</data><data key="node_entity_type">document_intake_process</data><data key="node_canonical_name">Paper Medical Assessment Wet-Signature CEF Intake</data><data key="node_domain">Disability / Evidence</data><data key="node_description">If medical assessments are completed on paper rather than DCPS, require MC/PC wet signature and scan into certified electronic folder.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0024"><data key="node_entity_id">R175_E0024</data><data key="node_entity_type">evidence_quality_rule</data><data key="node_canonical_name">Medical Tracing Scan Legibility Evaluation Rule</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Scanned electrocardiogram or pulmonary tracing may be used despite scale distortion if scale and gridlines remain visible.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0025"><data key="node_entity_id">R175_E0025</data><data key="node_entity_type">source_conflict</data><data key="node_canonical_name">SSA-416 Terminology Conflict General Versus Quality-Review Usage</data><data key="node_domain">Disability / Evidence</data><data key="node_description">DI 24501.006 titles SSA-416 Medical Evaluation while QR 04440.130 contains Case Analysis wording. No canonical historic row is overwritten.</data><data key="node_observed_status">source_naming_conflict</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">General SSA POMS medical evaluation uses Medical Evaluation; QR program appears to retain Case Analysis terminology. Scope and version differences need reconciliation.</data></node><node id="R175_E0026"><data key="node_entity_id">R175_E0026</data><data key="node_entity_type">query_constraint</data><data key="node_canonical_name">eView DEQY Five-Request-Type Selection Limit</data><data key="node_domain">Earnings / Disability</data><data key="node_description">eView DEQY query-selection screen allows at most five selected request-type codes.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0027"><data key="node_entity_id">R175_E0027</data><data key="node_entity_type">query_attribute</data><data key="node_canonical_name">eView DEQY Employer Address Request Type</data><data key="node_domain">Earnings / Address Provenance</data><data key="node_description">DEQY type 8 returns employer address; it is not the claimant residential or mailing address.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0028"><data key="node_entity_id">R175_E0028</data><data key="node_entity_type">query_attribute</data><data key="node_canonical_name">eView DEQY Last Employer Address Request Type</data><data key="node_domain">Earnings / Address Provenance</data><data key="node_description">DEQY available type 9 requests last employer address; describes employer contact location rather than claimant residence.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0029"><data key="node_entity_id">R175_E0029</data><data key="node_entity_type">document_intake_process</data><data key="node_canonical_name">eView Query View-and-Save-to-Electronic-Folder</data><data key="node_domain">Earnings / Disability</data><data key="node_description">eView can request DEQY or SEQY and save query results into case electronic folder via View &amp; Save to EF.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0030"><data key="node_entity_id">R175_E0030</data><data key="node_entity_type">data_access_rule</data><data key="node_canonical_name">eView Query User Profile Access Control</data><data key="node_domain">Earnings / Governance</data><data key="node_description">Access to eView query features depends on the users profile.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0031"><data key="node_entity_id">R175_E0031</data><data key="node_entity_type">historical_user_interface_route</data><data key="node_canonical_name">PCOM Master File Query Menu DEQY Route</data><data key="node_domain">Earnings / Infrastructure</data><data key="node_description">IBM Personal Communications accesses DEQY from Master File Query Menu option 9, as separately documented alongside eView.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0032"><data key="node_entity_id">R175_E0032</data><data key="node_entity_type">data_quality_constraint</data><data key="node_canonical_name">DEQY and SEQY Vocational Task Evidence Limitation</data><data key="node_domain">Disability / Earnings</data><data key="node_description">Earnings queries support identifying time and employer but do not determine the actual type of work performed.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0033"><data key="node_entity_id">R175_E0033</data><data key="node_entity_type">statistical_provenance_rule</data><data key="node_canonical_name">DEQY MEF and EIF Source Combination</data><data key="node_domain">Earnings / Data Lineage</data><data key="node_description">DEQY displays earnings information derived from Master Earnings File and Employer Identification File.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0034"><data key="node_entity_id">R175_E0034</data><data key="node_entity_type">organizational_payment_address</data><data key="node_canonical_name">SSA Portland Remittance-Only Mailing Address</data><data key="node_domain">Payments / Address Provenance</data><data key="node_description">Specified P.O. Box 5480, Portland, Oregon address accepts debt remittances only and cannot be used as correspondence or debtor mailing address.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">The observed 2025-11 policy address may change; do not treat as evergreen or as beneficiary address.</data></node><node id="R175_E0035"><data key="node_entity_id">R175_E0035</data><data key="node_entity_type">debt_collection_process</data><data key="node_canonical_name">Non-Pay Debtor DMS RMKS Repayment Contact Record</data><data key="node_domain">Payments / Debt</data><data key="node_description">Negotiated repayment conversation is entered on DMS RMKS comments screen.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0036"><data key="node_entity_id">R175_E0036</data><data key="node_entity_type">debt_collection_process</data><data key="node_canonical_name">Title XVI MSSICS UOPD Installment Recovery Decision</data><data key="node_domain">Title XVI / Debt</data><data key="node_description">SSI installment amount entered using G TAC through MSSICS UOPD Recover by Installments decision.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0037"><data key="node_entity_id">R175_E0037</data><data key="node_entity_type">debt_policy_rule</data><data key="node_canonical_name">SSA Debt Installment Negotiation Twelve-to-Sixty-Month Schedule</data><data key="node_domain">Payments / Debt</data><data key="node_description">Seek installment amount repaying debt within 12 months, otherwise within 60 months, otherwise highest monthly amount at least $50.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0038"><data key="node_entity_id">R175_E0038</data><data key="node_entity_type">debt_collection_rule</data><data key="node_canonical_name">Debt Default Treasury Offset and Credit Reporting Condition</data><data key="node_domain">Payments / Program Integrity</data><data key="node_description">Defaulted installment collection can trigger Treasury collection; credit reporting and TOP have separate selection/notice conditions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0039"><data key="node_entity_id">R175_E0039</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">SSA Remittance Address Excluded from Correspondence Routing</data><data key="node_domain">Payments / Address Provenance</data><data key="node_description">Policy explicitly restricts Portland payment post-office box to remittances, not program correspondence.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0040"><data key="node_entity_id">R175_E0040</data><data key="node_entity_type">debt_collection_rule</data><data key="node_canonical_name">Non-Pay Full Refund Negotiation Six-Month Future Limit</data><data key="node_domain">Payments / Debt</data><data key="node_description">When negotiating future lump-sum refund, do not agree to a due date more than six months ahead; negotiate installments if later.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R175_E0041"><data key="node_entity_id">R175_E0041</data><data key="node_entity_type">debt_collection_rule</data><data key="node_canonical_name">Debt Due Process Sixty-Day TOP Credit Reporting Warning</data><data key="node_domain">Payments / Debt</data><data key="node_description">Warn eligible debtors about conditional TOP/credit reporting 60 days after due-process notice when payment not received.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_CPU"><data key="node_entity_id">R176_CPU</data><data key="node_entity_type">organization</data><data key="node_canonical_name">SSA Centralized Processing Units (Representative Payee Workloads)</data><data key="node_domain">Representative Payee / SSA Operations</data><data key="node_description">GN 00502.113 documents SSA Centralized Processing Units processing defined representative-payee applicant workloads alongside Workload Support Units; physical site, deployment and technical hosting not specified.</data><data key="node_observed_status">documented_operational_unit</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_DOWR_MONTH"><data key="node_entity_id">R176_DOWR_MONTH</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">District Office Workload Reporting Administrative Month</data><data key="node_domain">Enterprise Data / Work Measurement</data><data key="node_description">DOWR Month is administratively determined monthly reporting period and need not coincide with a calendar month. FY reporting may span 52 or 53 weeks; a 53rd week affected FY2016 web-based change-of-address counts.</data><data key="node_observed_status">documented_data_definition</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_GAO_CROSSWALK"><data key="node_entity_id">R176_GAO_CROSSWALK</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2019-to-2025 GAO SSA Legacy-System Anonymized Identifier Crosswalk</data><data key="node_domain">Infrastructure / Modernization</data><data key="node_description">GAO Table 10 publicly crosswalks SSA 2019 System BC to 2025 System BD, 2019 BB to BE, and 2019 System 10 to BF; actual system names intentionally omitted.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_GAO_SSA_BD"><data key="node_entity_id">R176_GAO_SSA_BD</data><data key="node_entity_type">historical_anonymized_system</data><data key="node_canonical_name">GAO 2025 SSA Anonymous Legacy System BD</data><data key="node_domain">Infrastructure / Modernization</data><data key="node_description">GAO anonymized SSA system BD (2019 pseudonym BC); age 43 years and oldest hardware 3 years in 2025. GAO records supported hardware/software, presence of legacy programming languages, zero-trust capability, and no reported known unremediable cyber vulnerabilities. Modernization completed January 2025 according to SSA agency-reported information; completion of the modernization does not establish the original system was retired.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">GAO deliberately withholds actual name/purpose. Do not map to an identified SSA system or infer current operational state.</data></node><node id="R176_GAO_SSA_BE"><data key="node_entity_id">R176_GAO_SSA_BE</data><data key="node_entity_type">historical_anonymized_system</data><data key="node_canonical_name">GAO 2025 SSA Anonymous Legacy System BE</data><data key="node_domain">Infrastructure / Modernization</data><data key="node_description">GAO anonymized SSA system BE (2019 pseudonym BB); age 39 years and oldest hardware 4 years in 2025. GAO records supported hardware/software, presence of legacy programming languages, zero-trust capability, and no reported known unremediable cyber vulnerabilities. Modernization in progress as of February 2025; agency estimated 10 or more years from February 2025.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">GAO deliberately withholds actual name/purpose. Do not map to an identified SSA system or infer current operational state.</data></node><node id="R176_GAO_SSA_BF"><data key="node_entity_id">R176_GAO_SSA_BF</data><data key="node_entity_type">historical_anonymized_system</data><data key="node_canonical_name">GAO 2025 SSA Anonymous Legacy System BF</data><data key="node_domain">Infrastructure / Modernization</data><data key="node_description">GAO anonymized SSA system BF (2019 pseudonym 10); age 50 years and oldest hardware 4 years in 2025. GAO records supported hardware/software, presence of legacy programming languages, zero-trust capability, and no reported known unremediable cyber vulnerabilities. Modernization in progress as of February 2025; agency estimated 2 or more years from February 2025.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">GAO deliberately withholds actual name/purpose. Do not map to an identified SSA system or infer current operational state.</data></node><node id="R176_PAYEE_APPLICANT_HAS_PAYEE"><data key="node_entity_id">R176_PAYEE_APPLICANT_HAS_PAYEE</data><data key="node_entity_type">eligibility_control</data><data key="node_canonical_name">Representative Payee Applicant Who Has a Payee Mandatory Nonselection</data><data key="node_domain">Representative Payee / Identity</data><data key="node_description">SSA instructs staff to non-select a representative-payee applicant who currently has a representative payee, without gathering additional application data and without exceptions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_PAYEE_REMOTE_WSU_CPU"><data key="node_entity_id">R176_PAYEE_REMOTE_WSU_CPU</data><data key="node_entity_type">policy_rule</data><data key="node_canonical_name">WSU/CPU Custodial-Parent or Spouse Remote Payee Interview Exception</data><data key="node_domain">Representative Payee / Identity</data><data key="node_description">In a WSU or CPU, a custodial parent applying to serve a minor child or custodial spouse applying for spouse can qualify for telephone or approved video interview rather than in-person absent other mandatory face-to-face factors.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_PUPS_OFFENSE_LIMIT"><data key="node_entity_id">R176_PUPS_OFFENSE_LIMIT</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">PUPS Incarceration Dates Not Criminal Offense Identity</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">SSA says PUPS reflects applicant confinement history but does not identify the actual offense; employee must develop details before determining barred-crime status. No automatic inference from imprisonment to barred offense.</data><data key="node_observed_status">documented_data_limitation</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_1719B_TRANSMIT"><data key="node_entity_id">R176_RZ_1719B_TRANSMIT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination SSA-1719B Posteligibility Record Transmission</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">For non-MSSICS SSI RZ, SSA-1719B transmits changed record attributes and RZ-related CG/remarks updates to SSR.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_BTS_TRANSMIT"><data key="node_entity_id">R176_RZ_BTS_TRANSMIT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination MSSICS Build Transaction SSR Transmission</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">For an SSI RZ processed in MSSICS, Build Transaction SSR (BTS) transmits developed eligibility, payment and other record changes to SSR.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_FINAL_COMPLETION"><data key="node_entity_id">R176_RZ_FINAL_COMPLETION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination Final Completion-Indicator Posting</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">SSA instructs employees to transmit RZ completion indicator via SSA-1719B or close the RZ/LI event in MSSICS as the final input.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_FI_PERMISSION"><data key="node_entity_id">R176_RZ_FI_PERMISSION</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination Financial-Institution Contact-Permission Collection</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">SSA says permission to contact financial institutions is sought for all field-office-initiated RZs and WBDOC-to-FO transfers, but not asked for RZs completed by WBDOC.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_HOUSEHOLD_THIRD_PARTY"><data key="node_entity_id">R176_RZ_HOUSEHOLD_THIRD_PARTY</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination Cross-Recipient Household Third-Party Report</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">When an SSI RZ reveals potentially material information about another SSI recipient in the household, it constitutes a third-party report requiring independent development, not a direct record update.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_NO_PAYMENT_UPDATE"><data key="node_entity_id">R176_RZ_NO_PAYMENT_UPDATE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination Nonpayment Address and Phone Data Update Requirement</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">Even when an RZ or LI does not affect payment/eligibility, any confirmed changes including recipient address and telephone must be transmitted to SSR.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_RC_SUPPORT"><data key="node_entity_id">R176_RZ_RC_SUPPORT</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination SSA-1719B Report-of-Contact Change Evidence</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">For qualifying SSI RZ record changes sent via SSA-1719B, SSA requires an RC describing changed elements, correct information, relevant reasons, dates and effects.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_RETRO_CONSOLIDATE"><data key="node_entity_id">R176_RZ_RETRO_CONSOLIDATE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination Retroactive Development Input Consolidation</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">When multiple retroactive issues exist, SSA instructs employees to complete issue development and avoid fragmented inputs for the same issue.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_VP_REJECT"><data key="node_entity_id">R176_RZ_VP_REJECT</data><data key="node_entity_type">exception_control</data><data key="node_canonical_name">SSI Redetermination Outstanding-Priority-Diary VP Reject</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">The RZ clearance generates VP reject if an SSI priority diary is still pending. SSA requires diary resolution before successful clearance.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_RZ_WBDOC_FO"><data key="node_entity_id">R176_RZ_WBDOC_FO</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Redetermination WBDOC-to-Field-Office Transfer Processing</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">For electronically initiated SSI redeterminations transferred from WBDOC to a field office, MSSICS is SSA-preferred completion route.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_UAS459"><data key="node_entity_id">R176_UAS459</data><data key="node_entity_type">external_research_dataset</data><data key="node_canonical_name">Understanding America Study Survey 459 Fourth Wave</data><data key="node_domain">Research / Administrative Data</data><data key="node_description">USC Understanding America Study (UAS) Social Security Communications Channels Preference Survey wave four. 12,809 adult respondents June 2022-July 2024; self-reports on mySSA awareness, registration, intent and security perceptions.</data><data key="node_observed_status">historical_research_data</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Internet panel sampling/research is not an SSA systems interface, and self-reported account enrollment is not a verified SSA account transaction.</data></node><node id="R176_UAS_MYSSA_NOTE"><data key="node_entity_id">R176_UAS_MYSSA_NOTE</data><data key="node_entity_type">statistical_publication</data><data key="node_canonical_name">SSA Research and Statistics Note 2026-01 mySSA Participation and Willingness</data><data key="node_domain">Research / Publications</data><data key="node_description">2026 SSA policy research note analyzes USC UAS survey 459 self-reports of mySSA awareness, registration, willingness and reasons for hesitation.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R176_UAS_MYSSA_SELFREPORT"><data key="node_entity_id">R176_UAS_MYSSA_SELFREPORT</data><data key="node_entity_type">statistical_definition</data><data key="node_canonical_name">Survey-Reported mySSA Account Registration Status</data><data key="node_domain">Research / Data Quality</data><data key="node_description">Survey respondent statement of account-registration status; must not be conflated with independently verified SSA mySSA account creation/authentication or transaction logs.</data><data key="node_observed_status">documented_data_definition</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_ALJ_CPMS_RAW_LINEAGE"><data key="node_entity_id">R177_ALJ_CPMS_RAW_LINEAGE</data><data key="node_entity_type">statistical_publication_rule</data><data key="node_canonical_name">ALJ Public Disposition Data Raw CPMS Source Lineage</data><data key="node_acronym" /><data key="node_domain">Hearings / Appeals / Publications</data><data key="node_description">SSA explicitly identifies raw CPMS as source for the ALJ disposition report. Do not treat public file as the full CPMS case population.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_ALJ_FY26_AUG_XML"><data key="node_entity_id">R177_ALJ_FY26_AUG_XML</data><data key="node_entity_type">public_data_product</data><data key="node_canonical_name">FY2026 ALJ Disposition Data August 28 2026 XML Snapshot</data><data key="node_acronym" /><data key="node_domain">Hearings / Appeals / Publications</data><data key="node_description">SSA public XML data for ALJ dispositions 2025-09-27 through 2026-08-28 by judge and hearing office; monthly published snapshot, not live CPMS query.</data><data key="node_observed_status">public_snapshot_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Web HTML table shows loading error; official XML remains linked. Publication should be snapshotted for reproducibility.</data></node><node id="R177_ALJ_MULTIOFFICE_RULE"><data key="node_entity_id">R177_ALJ_MULTIOFFICE_RULE</data><data key="node_entity_type">statistical_quality_rule</data><data key="node_canonical_name">ALJ Disposition Geography and Multi-Office Attribution Caveat</data><data key="node_acronym" /><data key="node_domain">Hearings / Geography</data><data key="node_description">ALJ figures are reported by hearing office; ALJs can work across offices, so office of disposition is not necessarily judge home office or claimant residence.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_ALJ_WORKTIME_CAVEAT"><data key="node_entity_id">R177_ALJ_WORKTIME_CAVEAT</data><data key="node_entity_type">statistical_quality_rule</data><data key="node_canonical_name">ALJ Disposition Count Nonadjudicative Work-Time Caveat</data><data key="node_acronym" /><data key="node_domain">Hearings / Publications</data><data key="node_description">SSA raw dispositions are not adjusted for ALJ managerial responsibilities, special assignments, part-time employment, union duties, retirement, leave and similar nonadjudication factors.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_OACT_SSI26_VC1"><data key="node_entity_id">R177_OACT_SSI26_VC1</data><data key="node_entity_type">public_statistical_product</data><data key="node_canonical_name">2026 SSI Annual Report Table V.C1 Disabled Adult Application Cohorts</data><data key="node_acronym" /><data key="node_domain">Actuarial / Disability</data><data key="node_description">Calendar-year filing cohort longitudinal initial, reconsideration, and later appeals status for SSI disabled-adult applications. 2025 cohort preliminary as of January 2026.</data><data key="node_observed_status">public_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_OACT_SSI26_VC2"><data key="node_entity_id">R177_OACT_SSI26_VC2</data><data key="node_entity_type">public_statistical_product</data><data key="node_canonical_name">2026 SSI Annual Report Table V.C2 Disabled Child Application Cohorts</data><data key="node_acronym" /><data key="node_domain">Actuarial / Disability</data><data key="node_description">Calendar-year filing cohort longitudinal decisions and appeals statistics for SSI disabled-child applications, with 2025 preliminary estimations and historical revisions.</data><data key="node_observed_status">public_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_OHO_NET_RECEIPTS_RULE"><data key="node_entity_id">R177_OHO_NET_RECEIPTS_RULE</data><data key="node_entity_type">statistical_quality_rule</data><data key="node_canonical_name">OHO Transferred-Out Caseload Negative Net Receipts Caveat</data><data key="node_acronym" /><data key="node_domain">Hearings / Publications</data><data key="node_description">Hearing office workload receipts can be negative when transferred-out cases exceed new receipts in the reporting interval; excludes inference that incoming claims are physically negative.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SDR"><data key="node_entity_id">R177_SDR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSA Structured Data Repository (SDR)</data><data key="node_acronym">SDR</data><data key="node_domain">Disability / Administrative Data</data><data key="node_description">Named SSA administrative source that contributes disability application/appeal records to annual Title XVI Disability Research File. Public source does not identify physical location, technology or completeness.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not assume field-level definitions or automatic feeds. The 2026 source names this repository but does not detail technical operation.</data></node><node id="R177_SS5_PARENT_795_SHRED"><data key="node_entity_id">R177_SS5_PARENT_795_SHRED</data><data key="node_entity_type">document_handling_rule</data><data key="node_canonical_name">Child SSN Missing-Parent-SSN SSA-795 Development and Disposal</data><data key="node_acronym" /><data key="node_domain">Identity / Enumeration</data><data key="node_description">Where SS-5 arrives by mail without required parent SSN, employees may request missing data on SSA-795 and shred SSA-795 if decision is subsequently made to process application.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">This is disposal of designated support statement, not a universal retention rule for child SSN applications.</data></node><node id="R177_SS5_PARENT_ALPHIDENT"><data key="node_entity_id">R177_SS5_PARENT_ALPHIDENT</data><data key="node_entity_type">identity_search_process</data><data key="node_canonical_name">Child SSN Application Missing Parent Alphident Research</data><data key="node_acronym" /><data key="node_domain">Identity / Enumeration</data><data key="node_description">In eligible circumstances employee obtains sufficient parent identifying information and locates assigned SSN via alphident before processing child application.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SS5_PARENT_IRS_REPORT"><data key="node_entity_id">R177_SS5_PARENT_IRS_REPORT</data><data key="node_entity_type">exchange_product</data><data key="node_canonical_name">Child SSN Application Parent SSN Information Furnished to IRS</data><data key="node_acronym" /><data key="node_domain">External Exchanges / Identity</data><data key="node_description">Policy cites Public Law 105-34 as requiring SSA to give parents SSNs from applicable child applications to IRS; timing, transport, file format, and retention are not established.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Outgoing statutory data-sharing obligation only. No assertion of automatic IRS address updates into SSA.</data></node><node id="R177_SS5_PARENT_NOTIFY_ASSIGNED"><data key="node_entity_id">R177_SS5_PARENT_NOTIFY_ASSIGNED</data><data key="node_entity_type">application_notification_control</data><data key="node_canonical_name">SSNAP Parent SSN Assignment Field Office Notification</data><data key="node_acronym" /><data key="node_domain">Identity / Enumeration</data><data key="node_description">When parent and child apply for first SSNs concurrently, the parent application is processed first; SSNAP Verify and Sign has a Notify office of SSN assigned option to alert field office.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SS5_PARENT_NO_SSN_EXCEPTION"><data key="node_entity_id">R177_SS5_PARENT_NO_SSN_EXCEPTION</data><data key="node_entity_type">identity_business_rule</data><data key="node_canonical_name">Child SSN Application Allowed Missing-Parent-SSN Exceptions</data><data key="node_acronym" /><data key="node_domain">Identity / Enumeration</data><data key="node_description">Deceased parent, parent with no SSN, specific State Enumeration-at-Birth gaps, adoption/foster-care unknowns and other accepted reasons allow Unknown SSN or None in SSNAP.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SS5_PARENT_PRINT_HIDE"><data key="node_entity_id">R177_SS5_PARENT_PRINT_HIDE</data><data key="node_entity_type">privacy_display_control</data><data key="node_canonical_name">SSNAP Hidden Parent SSN on Printed Child Application</data><data key="node_acronym" /><data key="node_domain">Identity / Enumeration</data><data key="node_description">When employee locates a missing SSN for a parent who is not the applicant, SSNAP provides Hide SSN on printed application to avoid exposing it to the applicant.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SS5_PARENT_SSNS"><data key="node_entity_id">R177_SS5_PARENT_SSNS</data><data key="node_entity_type">identity_data_attribute_set</data><data key="node_canonical_name">SS-5 Parent SSN Collection for Child Under 18</data><data key="node_acronym" /><data key="node_domain">Identity / Enumeration</data><data key="node_description">Child original or new SSN application ordinarily includes both parents Social Security numbers, with policy-defined exceptions. Parent identifiers are not claimant mailing addresses.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SS5_PARENT_SUSPECT"><data key="node_entity_id">R177_SS5_PARENT_SUSPECT</data><data key="node_entity_type">application_exception_rule</data><data key="node_canonical_name">Child SSN Application Parent SSN Nonverification Suspect Status</data><data key="node_acronym" /><data key="node_domain">Identity / Enumeration</data><data key="node_description">SSNAP displays an alert and places child SSN application in suspect status if an asserted parent SSN fails verification and remains uncorrected.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SS5_PARENT_VERIFY_GATE"><data key="node_entity_id">R177_SS5_PARENT_VERIFY_GATE</data><data key="node_entity_type">identity_verification_rule</data><data key="node_canonical_name">Child SSN Application Parent Numident Name and SSN Verification Gate</data><data key="node_acronym" /><data key="node_domain">Identity / Enumeration</data><data key="node_description">SSNAP verifies parent SSNs and matches application parent name against NAA or NL2 fields in any iteration of parent Numident, with discrepancy development required.</data><data key="node_observed_status">documented_2024</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SSI_FO_RETURN_ADDRESS"><data key="node_entity_id">R177_SSI_FO_RETURN_ADDRESS</data><data key="node_entity_type">organizational_address_attribute</data><data key="node_canonical_name">SSI Notice Servicing Field Office Return Address</data><data key="node_acronym" /><data key="node_domain">Address Provenance / Title XVI</data><data key="node_description">SSA prints servicing field office as return address on SSI notices; routing address is organizational, not beneficiary residence or updated recipient mailing address.</data><data key="node_observed_status">documented_policy_transmittal_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SSI_RETURNED_DECEASED_NOTICE"><data key="node_entity_id">R177_SSI_RETURNED_DECEASED_NOTICE</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Returned Mail Marked Deceased Requires Death-Report Development</data><data key="node_acronym" /><data key="node_domain">Address Provenance / Program Integrity</data><data key="node_description">When returned envelope carries Deceased notation, field office follows reports-of-death procedures rather than assuming confirmed death or auto-updating Numident.</data><data key="node_observed_status">documented_policy_transmittal_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SSI_UNDELIV_APPEAL_SERVICE"><data key="node_entity_id">R177_SSI_UNDELIV_APPEAL_SERVICE</data><data key="node_entity_type">notice_due_process_rule</data><data key="node_canonical_name">SSI Undeliverable Appeal Notice Remailing and Receipt-Date Protection</data><data key="node_acronym" /><data key="node_domain">Title XVI / Appeals</data><data key="node_description">Returned appeal-rights SSI notices require cover-letter treatment and correct re-mailing; upon locating recipient, special rules protect 10/30-day response periods and receipt-based appeal clock.</data><data key="node_observed_status">documented_policy_transmittal_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_SSI_UNDELIV_MAIL_ADDRESS_LEAD"><data key="node_entity_id">R177_SSI_UNDELIV_MAIL_ADDRESS_LEAD</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">SSI USPS-Returned Notice as Investigative Address Lead</data><data key="node_acronym" /><data key="node_domain">Address Provenance / Title XVI</data><data key="node_description">Returned SSI notices route to field office, which attempts to locate claimant or payee and develops a valid address before entering appropriate change. Return does not itself verify a new residence.</data><data key="node_observed_status">documented_policy_transmittal_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Source body states 2005 revision, June 2026 transmittal: do not portray as newly introduced 2026.</data></node><node id="R177_T16_DRF_2025_EST"><data key="node_entity_id">R177_T16_DRF_2025_EST</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">Title XVI Disability Research File 2025 Filing-Cohort Preliminary Estimate</data><data key="node_acronym" /><data key="node_domain">Actuarial / Disability</data><data key="node_description">2026 report estimates 2025 filer decisions through January 2026 using recent disability transactions and historical relationships between early counts and final cohort results. Not a completed research-file cohort.</data><data key="node_observed_status">provisional_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative source expects finalized 2025 filing cohort to replace estimate in 2027 report.</data></node><node id="R177_T16_DRF_APPEAL_INPUT"><data key="node_entity_id">R177_T16_DRF_APPEAL_INPUT</data><data key="node_entity_type">administrative_data_domain</data><data key="node_canonical_name">Title XVI Disability Research File Hearing and Appeals Council Source Data</data><data key="node_acronym" /><data key="node_domain">Disability / Appeals</data><data key="node_description">Hearing and Appeals Council administrative records are matched with SSR and other data to reconstruct an application-to-appeal history; specific contributing physical repositories are not identified in this report.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_T16_DRF_COHORT"><data key="node_entity_id">R177_T16_DRF_COHORT</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">Title XVI Disability Research Filing-Date Cohort Reconciliation</data><data key="node_acronym" /><data key="node_domain">Actuarial / Disability</data><data key="node_description">Build organizes historical SSI disability claims by application filing date even where several administrative inputs lack that date; base sources provide three recent calendar-year cohorts, earlier cohorts receive updates.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_T16_DRF_PERSON_CLAIM_BIAS"><data key="node_entity_id">R177_T16_DRF_PERSON_CLAIM_BIAS</data><data key="node_entity_type">statistical_quality_rule</data><data key="node_canonical_name">Title XVI Claimant-Based Appeals Estimation Undercount Caveat</data><data key="node_acronym" /><data key="node_domain">Person / Identity Nexus</data><data key="node_description">2025 cohort provisional hearing/Appeals Council estimates partly use a claimant-level file instead of a claim-level file; 2026 source warns this may undercount certain historical individual claims.</data><data key="node_observed_status">methodology_caveat</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_T16_DRF_PRODUCTION"><data key="node_entity_id">R177_T16_DRF_PRODUCTION</data><data key="node_entity_type">statistical_production_process</data><data key="node_canonical_name">Title XVI Disability Research File Annual Construction</data><data key="node_acronym" /><data key="node_domain">Actuarial / Disability</data><data key="node_description">SSA Disability Policy annually constructs a longitudinal Title XVI disability applications and appeals research file from SSR and several administrative inputs; approximately 200 steps and 2-4 months of production work.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R177_T16_DRF_SSN_INPUT"><data key="node_entity_id">R177_T16_DRF_SSN_INPUT</data><data key="node_entity_type">administrative_data_domain</data><data key="node_canonical_name">Title XVI Disability Research File SSN Identification Source Records</data><data key="node_acronym" /><data key="node_domain">Person / Identity Nexus</data><data key="node_description">The 2026 SSI report explicitly names Social Security number identification records as inputs to the disability research-file matching process; it does not identify an exact physical Numident table/feed.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Avoid asserting a direct Numident feed absent explicit technical description.</data></node><node id="R178_E0001"><data key="node_entity_id">R178_E0001</data><data key="node_entity_type">initiative</data><data key="node_canonical_name">2008 SSA Electronic Information Exchange Initiative</data><data key="node_domain">External Exchanges</data><data key="node_description">SSA electronic information exchange assessment and report completed September 4 2008; recommendations were later judged obsolete by SSA in June 2011.</data><data key="node_observed_status">historical_superseded</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">EIEI historical planning initiative; not a production data repository.</data></node><node id="R178_E0002"><data key="node_entity_id">R178_E0002</data><data key="node_entity_type">enterprise_inventory</data><data key="node_canonical_name">2013 SSA Expanded Data Exchange Inventory System</data><data key="node_domain">External Exchanges</data><data key="node_description">SSA demonstrated a comprehensive data exchange inventory in September 2013 with partner/exchange details, supporting SSA information systems, and workload statistics.</data><data key="node_observed_status">historical_confirmed_2013</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">The public oversight report does not name vendor, persistence store, or say the system is still deployed in 2026.</data></node><node id="R178_E0003"><data key="node_entity_id">R178_E0003</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2013 SSA Exchange-to-Supporting-System Inventory Mapping</data><data key="node_domain">External Exchanges</data><data key="node_description">Inventory mapping identifies the supporting information systems and participating entities for SSA data exchanges, as documented to GAO in September 2013.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0004"><data key="node_entity_id">R178_E0004</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2013 SSA Exchange Request-Type and Volume Report</data><data key="node_domain">External Exchanges</data><data key="node_description">Exchange-inventory reporting provides numbers and types of data requests received for particular SSA exchange arrangements, per September 2013 GAO follow-up.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0005"><data key="node_entity_id">R178_E0005</data><data key="node_entity_type">governance_finding</data><data key="node_canonical_name">2011 SSA EIEI Recommendation Obsolescence Determination</data><data key="node_domain">External Exchanges</data><data key="node_description">In June 2011 SSA told GAO its 2008 EIEI recommendations had become obsolete owing to changed technology and diminishing resources; does not imply all exchanges ended.</data><data key="node_observed_status">historical_decision</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0006"><data key="node_entity_id">R178_E0006</data><data key="node_entity_type">governance_document</data><data key="node_canonical_name">SSA 2007 IT Strategic Plan (GAO Historical Reference)</data><data key="node_domain">Modernization</data><data key="node_description">SSA prepared an IT strategic plan in 2007 that GAO in 2012 deemed insufficiently updated to agency goals.</data><data key="node_observed_status">historical_plan</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0007"><data key="node_entity_id">R178_E0007</data><data key="node_entity_type">governance_document</data><data key="node_canonical_name">SSA May 2015 Enterprise Architecture Road Map</data><data key="node_domain">Modernization</data><data key="node_description">GAO 2016 follow-up records SSA enterprise architecture road map developed May 2015 with performance targets.</data><data key="node_observed_status">historical_plan</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A road map is not proof of deployed production architecture.</data></node><node id="R178_E0008"><data key="node_entity_id">R178_E0008</data><data key="node_entity_type">modernization_workflow</data><data key="node_canonical_name">SSA 2016 Enterprise Data Model Update Work</data><data key="node_domain">Enterprise Data and Analytics</data><data key="node_description">GAO says SSA was updating its enterprise data model in July 2016 to describe relationships among business processes; completion of update not documented.</data><data key="node_observed_status">historical_in_progress</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0009"><data key="node_entity_id">R178_E0009</data><data key="node_entity_type">oversight_finding</data><data key="node_canonical_name">SSA 2016 Enterprise Architecture Gap Analysis Deficiency</data><data key="node_domain">Modernization</data><data key="node_description">In August 2016 SSA had not completed a comprehensive gap analysis of its current and target enterprise architecture according to GAO follow-up.</data><data key="node_observed_status">historical_open_as_of_2016</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0010"><data key="node_entity_id">R178_E0010</data><data key="node_entity_type">oversight_recommendation</data><data key="node_canonical_name">GAO-Recommended SSA Service-Oriented Architecture Road Map</data><data key="node_domain">Modernization</data><data key="node_description">GAO recommended an SOA road map and linked gap and performance analysis; full plan recommendation closed not implemented in September 2016.</data><data key="node_observed_status">historical_recommendation_only</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not interpret as implemented SOA integration design.</data></node><node id="R178_E0011"><data key="node_entity_id">R178_E0011</data><data key="node_entity_type">governance_body</data><data key="node_canonical_name">SSA Strategic Information Technology Assessment and Review Board</data><data key="node_domain">Modernization</data><data key="node_description">GAO describes SSA investment review board approving IT development projects that undergo quality assurance, confirmed 2016.</data><data key="node_observed_status">historical_confirmed_2016</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0012"><data key="node_entity_id">R178_E0012</data><data key="node_entity_type">quality_assurance_workflow</data><data key="node_canonical_name">2016 SSA IT Project Control-Document Quality Assurance Review</data><data key="node_domain">Modernization</data><data key="node_description">SSA required investment-board approved development projects to undergo QA reviewing project requirements, schedule, and documented risks.</data><data key="node_observed_status">historical_confirmed_2016</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0013"><data key="node_entity_id">R178_E0013</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">2016 SSA IT Quality Review Five-Business-Day Corrective Action Deadline</data><data key="node_domain">Modernization</data><data key="node_description">When a project quality review found noncompliance, project teams had to document corrective action plans and expected dates within five business days.</data><data key="node_observed_status">historical_confirmed_2016</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0014"><data key="node_entity_id">R178_E0014</data><data key="node_entity_type">governance_data_artifact</data><data key="node_canonical_name">2016 Mandatory Multifactor Authentication Project QA Review</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">GAO describes an August 2016 quality review of SSA mandatory multifactor authentication project documents including business process, schedule, and risks.</data><data key="node_observed_status">historical_review_only</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Project review does not prove specific identity database, authentication vendor, or contemporary implementation.</data></node><node id="R178_E0015"><data key="node_entity_id">R178_E0015</data><data key="node_entity_type">governance_data_artifact</data><data key="node_canonical_name">June 2016 mySSA 1099 Postimplementation Review</data><data key="node_domain">Modernization</data><data key="node_description">GAO documented SSA June 2016 postimplementation review of mySSA 1099 service, comparing business assumptions, planned and actual costs and benefits.</data><data key="node_observed_status">historical_completed_review</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0016"><data key="node_entity_id">R178_E0016</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA 2010 IT Support Services Contract SS00-10-60082</data><data key="node_domain">Procurement</data><data key="node_description">SSA awarded 7-year IT support services contract SS00-10-60082 to Northrop Grumman on September 10 2010, with one base year and six annual options.</data><data key="node_observed_status">historical_award</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Different from SSA 2017 ITSSC contracts. $73.5m authorized through option year 1 not total spending.</data></node><node id="R178_E0017"><data key="node_entity_id">R178_E0017</data><data key="node_entity_type">procurement_workflow</data><data key="node_canonical_name">SSA 2010 ITSSC Firm-Fixed-Price and Time-and-Materials Task Orders</data><data key="node_domain">Procurement</data><data key="node_description">2010 SSA ITSSC allowed task orders on firm-fixed-price and time-and-materials basis for skilled software/system support services.</data><data key="node_observed_status">historical_contract_terms</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0018"><data key="node_entity_id">R178_E0018</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">SSAB 2007–2019 SSA Service Channel Historical Data Tables</data><data key="node_domain">Service Delivery</data><data key="node_description">SSAB compiled SSA historical 800-number calls, field-office visitors and online transactions, with nonuniform counting bases.</data><data key="node_observed_status">published_historical_2020</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0019"><data key="node_entity_id">R178_E0019</data><data key="node_entity_type">statistical_counting_rule</data><data key="node_canonical_name">SSA Online Transaction versus Call and Visit Historical Counting Difference</data><data key="node_domain">Service Delivery</data><data key="node_description">An online transaction counted independently while an 800-number call or office visit counted once regardless of number of services provided.</data><data key="node_observed_status">historical_methodology</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0020"><data key="node_entity_id">R178_E0020</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">SSA 2016–2019 Online SSN Replacement Card Share Historical Table</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">SSAB reports first online SSN replacement cards in 2016: 1.1 percent of 8,957,195 replacements. Service not available online before 2016.</data><data key="node_observed_status">historical_statistic</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0021"><data key="node_entity_id">R178_E0021</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">SSA 2008–2019 Disability Online Application Channel Share Table</data><data key="node_domain">Disability</data><data key="node_description">SSAB published initial disability application share online vs in-person/phone; 2008 online 11.1%, 2016 52.1%. Phone versus in-person not separately identified.</data><data key="node_observed_status">historical_statistic</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0022"><data key="node_entity_id">R178_E0022</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">SSAB 1937–2018 Field Office Count Historical Series</data><data key="node_domain">Service Delivery</data><data key="node_description">Historical SSA office inventory series compiled by SSAB; definitions and observation dates changed, including 1996 inclusion of resident stations/card centers.</data><data key="node_observed_status">published_historical_2020</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0023"><data key="node_entity_id">R178_E0023</data><data key="node_entity_type">statistical_counting_rule</data><data key="node_canonical_name">SSA Historical Field Office Count Definition and Reference-Date Change</data><data key="node_domain">Service Delivery</data><data key="node_description">SSAB notes 1996 definition expansion and period-end variations for field office counts, precluding naive comparison of all historic years.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0024"><data key="node_entity_id">R178_E0024</data><data key="node_entity_type">report</data><data key="node_canonical_name">SSI Annual Statistical Report 2008 (September 2009 Edition)</data><data key="node_domain">Title XVI</data><data key="node_description">2008-data SSI report published September 2009 with application, payment, award, recipient and termination statistical tables.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0025"><data key="node_entity_id">R178_E0025</data><data key="node_entity_type">published_statistical_table</data><data key="node_canonical_name">2008 SSI Annual Any-Payment Recipient Table 3</data><data key="node_domain">Title XVI</data><data key="node_description">New table 3 in SSI 2008 report counts recipients with at least one federally administered SSI payment during year; not same as December monthly count.</data><data key="node_observed_status">historical_method_change</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0026"><data key="node_entity_id">R178_E0026</data><data key="node_entity_type">statistical_processing_rule</data><data key="node_canonical_name">2008 SSI Termination Series Revised Methodology From 2006</data><data key="node_domain">Title XVI</data><data key="node_description">Reinstated table 77 used a revised methodology, restarting published annual SSI termination series at calendar year 2006 rather than extending earlier 1998–2005 series.</data><data key="node_observed_status">historical_method_change</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0027"><data key="node_entity_id">R178_E0027</data><data key="node_entity_type">report</data><data key="node_canonical_name">Annual SSDI Statistical Report 2008 (July 2009 Edition)</data><data key="node_domain">Title II</data><data key="node_description">Annual published report on SSDI benefits, award, work activity, applications and terminations. 2009 edition notes 100-percent data since 2001.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0028"><data key="node_entity_id">R178_E0028</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">SSDI Statistical Award Definition and Full-File Series Change (2001 Onward)</data><data key="node_domain">Title II</data><data key="node_description">2009 edition explains since 2001 disability award statistics derive from 100-percent files and award definition includes secondary awards and subsequent disability periods while excluding reinstatements.</data><data key="node_observed_status">historical_method_explained_2009</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Method changed in 2001 before research window; 2009 in-window publication explicitly documents it.</data></node><node id="R178_E0029"><data key="node_entity_id">R178_E0029</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">Historical SIPP-Based Noninstitutionalized Beneficiary Survey Estimates</data><data key="node_domain">Research and Administrative Data</data><data key="node_description">SSDI annual report removed SIPP-based estimates of noninstitutionalized beneficiaries due panel attrition and low administrative-record matching rates.</data><data key="node_observed_status">historical_withdrawn_from_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">A survey linkage issue; not proof of missing operational person records.</data></node><node id="R178_E0030"><data key="node_entity_id">R178_E0030</data><data key="node_entity_type">research_data_collection</data><data key="node_canonical_name">ORES Special Census SIPP Interview of DI and SSI Beneficiaries</data><data key="node_domain">Research and Administrative Data</data><data key="node_description">SSA Office of Research contracted Census Bureau for additional SIPP-based interview of DI and SSI beneficiaries to address reliability concerns; results unavailable for 2009 edition.</data><data key="node_observed_status">historical_reported</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0031"><data key="node_entity_id">R178_E0031</data><data key="node_entity_type">statistical_correction_event</data><data key="node_canonical_name">2008 SSDI Report Tables 25 and 58 Corrected Web Releases</data><data key="node_domain">Publication Pipelines</data><data key="node_description">SSA correction notices report table 25 corrected January 13 2010 and table 58 corrected May 11 2011 after original web/print errors.</data><data key="node_observed_status">historical_correction</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0032"><data key="node_entity_id">R178_E0032</data><data key="node_entity_type">data_format</data><data key="node_canonical_name">SSI Supplemental Security Record Characteristic Record Extract Format</data><data key="node_domain">Title XVI</data><data key="node_description">SSA 2008 Fast Facts cites Supplemental Security Record in Characteristic Record Extract format for 100-percent SSI statistical figures and payment amounts.</data><data key="node_observed_status">historical_format_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Do not assume separate CRE operational database; source names statistical format.</data></node><node id="R178_E0033"><data key="node_entity_id">R178_E0033</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2007 Unduplicated OASDI and SSI Beneficiary Statistical Product</data><data key="node_domain">Person/Identity Nexus</data><data key="node_description">2008 Fast Facts uses MBR and SSR Characteristic Record Extract 100-percent data to report persons receiving OASDI only, SSI only, or both, avoiding double count.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0034"><data key="node_entity_id">R178_E0034</data><data key="node_entity_type">statistical_definition</data><data key="node_canonical_name">2007 SSI Average Monthly Payment Excludes Retroactive Amounts</data><data key="node_domain">Title XVI</data><data key="node_description">2008 Fast Facts says reported average monthly SSI payment excludes retroactive payments, so amount is not full transaction history.</data><data key="node_observed_status">historical_definition</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0035"><data key="node_entity_id">R178_E0035</data><data key="node_entity_type">procurement_data_product</data><data key="node_canonical_name">SSA OAG FY2006–FY2011 Foreign-Manufactured Products Acquisition Reports</data><data key="node_domain">Procurement</data><data key="node_description">OAG FOIA provides FY2006 through FY2011 congressional reports on acquisition of end products manufactured outside US.</data><data key="node_observed_status">historical_discontinued_reporting</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Not a complete vendor spending dataset, procurement database, or system inventory.</data></node><node id="R178_E0036"><data key="node_entity_id">R178_E0036</data><data key="node_entity_type">procurement_rule</data><data key="node_canonical_name">FY2011 Expiration of Foreign-Manufactured Products Congressional Report Requirement</data><data key="node_domain">Procurement</data><data key="node_description">OAG says 41 USC 8302(b)(1) report requirement expired after FY2011 and reporting concluded; FAR case 2013-008 removed obsolete requirement.</data><data key="node_observed_status">historical_ended</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0037"><data key="node_entity_id">R178_E0037</data><data key="node_entity_type">statistical_publication</data><data key="node_canonical_name">Annual Statistical Supplement 2011 (February 2012 Edition)</data><data key="node_domain">Publication Pipelines</data><data key="node_description">SSA 2011 Annual Statistical Supplement published February 2012 and retained with corrections posted in 2025 and 2026.</data><data key="node_observed_status">historical_publication_modified</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0038"><data key="node_entity_id">R178_E0038</data><data key="node_entity_type">statistical_correction_event</data><data key="node_canonical_name">2011 Annual Statistical Supplement Postpublication Errata Record</data><data key="node_domain">Publication Pipelines</data><data key="node_description">Online 2011 edition page documents 2025 corrections to Railroad Retirement transfer amount and 2026 correction to 1970 maximum-family-benefit formula.</data><data key="node_observed_status">historical_updated_2026</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0039"><data key="node_entity_id">R178_E0039</data><data key="node_entity_type">research_publication</data><data key="node_canonical_name">SSAB 2012 Aspects of Disability Decision Making Chartbook</data><data key="node_domain">Disability</data><data key="node_description">2012 third-edition SSAB disability decision making chartbook provides public linked downloadable xlsx dataset and analysis.</data><data key="node_observed_status">historical_research_publication</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0040"><data key="node_entity_id">R178_E0040</data><data key="node_entity_type">research_public_use_dataset</data><data key="node_canonical_name">SSAB Disability Decision-Making 2012 Chartbook Companion XLSX</data><data key="node_domain">Disability</data><data key="node_description">Social Security Advisory Board published chartbook companion research data spreadsheet; secondary analytic resource, not a live administrative datastore.</data><data key="node_observed_status">historical_public_file</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R178_E0041"><data key="node_entity_id">R178_E0041</data><data key="node_entity_type">statistical_counting_rule</data><data key="node_canonical_name">2007 Cross-Program Unduplicated Person Statistical Counting Rule</data><data key="node_domain">Person/Identity Nexus</data><data key="node_description">2008 Fast Facts reported 54.656 million persons receiving OASDI, SSI or both for December 2007, with 2.569 million overlapping; combined count requires deduplication of MBR/SSR populations.</data><data key="node_observed_status">historical_reporting_only</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Method of identity matching unspecified; no physical enterprise Person data store established.</data></node><node id="R179_E0001"><data key="node_entity_id">R179_E0001</data><data key="node_entity_type">historical_workload</data><data key="node_canonical_name">SSC 2009 Electronic Disability Medical Image Production Workload</data><data key="node_domain">Infrastructure/Disability</data><data key="node_description">In May 2009 the North Carolina SSC operated in production and maintained medical images belonging to electronic disability folders, reducing NCC outage exposure.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0002"><data key="node_entity_id">R179_E0002</data><data key="node_entity_type">historical_infrastructure</data><data key="node_canonical_name">SSC 2009 Redundant Office Internet and NCC Communications</data><data key="node_domain">Infrastructure</data><data key="node_description">SSA testified SSC maintained fully redundant communications connections to SSA field offices, the Internet, and NCC by December 2009.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0003"><data key="node_entity_id">R179_E0003</data><data key="node_entity_type">historical_recovery_service</data><data key="node_canonical_name">SSA Pre-2010 Commercial Hot Site Tape Recovery Service</data><data key="node_domain">Infrastructure/Continuity</data><data key="node_description">As of December 2009 SSA relied on transporting backup tapes to a commercial hot site, with an estimated seven-day recovery of only 25 to 30 percent of critical processing capacity.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0004"><data key="node_entity_id">R179_E0004</data><data key="node_entity_type">historical_planned_control</data><data key="node_canonical_name">SSC-to-NCC Hourly Data Synchronization and 24-Hour Recovery Goal for 2012</data><data key="node_domain">Infrastructure/Continuity</data><data key="node_description">In 2009 SSA projected hourly synchronization by 2012 and restoration within 24 hours; documentary evidence does not prove the goal was achieved.</data><data key="node_observed_status">historical_planned</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0005"><data key="node_entity_id">R179_E0005</data><data key="node_entity_type">historical_design_requirement</data><data key="node_canonical_name">NCC-to-NSC Transitional Inter-Application Database Synchronization Requirement (2009)</data><data key="node_domain">Infrastructure/Person Nexus</data><data key="node_description">SSA stated adjudication processes interactively verify and update applicant personal information on multiple systems; migration design specified synchronous performance within 100 kilometers. This is not a single Person repository.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0006"><data key="node_entity_id">R179_E0006</data><data key="node_entity_type">historical_test_observation</data><data key="node_canonical_name">SSC 2010 Disaster-Recovery Test Recovery-Time Observation</data><data key="node_domain">Infrastructure/Continuity</data><data key="node_description">SSA OIG reported tests improved recovery from about ten days in 2009 to fewer than five days in 2010; these were historical test observations, not current service level.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0007"><data key="node_entity_id">R179_E0007</data><data key="node_entity_type">historical_pilot</data><data key="node_canonical_name">SSA 2015 Linux Server Pilot Reported to OIG</data><data key="node_domain">Infrastructure/Modernization</data><data key="node_description">In July 2016 testimony, SSA OIG described SSA reported a 2015 pilot involving Linux servers; the source does not establish universal migration.</data><data key="node_observed_status">historical_pilot</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0008"><data key="node_entity_id">R179_E0008</data><data key="node_entity_type">historical_migration_plan</data><data key="node_canonical_name">SSA 2016 UNIX Middleware-to-Linux Migration Plan</data><data key="node_domain">Infrastructure/Modernization</data><data key="node_description">As of 2016 SSA discussed multi-year plan to move UNIX middle-tier workloads to Linux; full completion status not established.</data><data key="node_observed_status">historical_planned</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0009"><data key="node_entity_id">R179_E0009</data><data key="node_entity_type">historical_modernization_assessment</data><data key="node_canonical_name">SSA 2016 Private Cloud Evaluation Stage</data><data key="node_domain">Infrastructure/Cloud</data><data key="node_description">SSA was exploring private-cloud or public-cloud capabilities as of 2016; potential adoption should not be presented as proof of deployed public cloud.</data><data key="node_observed_status">historical_assessment</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0010"><data key="node_entity_id">R179_E0010</data><data key="node_entity_type">historical_modernization_plan</data><data key="node_canonical_name">SSA 2016 Legacy Master Data to Standard Database Modernization Proposal</data><data key="node_domain">Enterprise Data/Modernization</data><data key="node_description">SSA discussed migrating legacy master data to standardized database technology as a modernization strategy in 2016; source does not identify a successfully migrated physical master repository.</data><data key="node_observed_status">historical_proposed</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0011"><data key="node_entity_id">R179_E0011</data><data key="node_entity_type">historical_exchange_business_control</data><data key="node_canonical_name">Enumeration at Birth Per-Record State Vital Statistics Contract Reimbursement (2011)</data><data key="node_domain">Person Identity/External Exchanges</data><data key="node_description">In 2011 SSA had a contract with each participating state and reimbursed states $2.40 per reported birth record; current reimbursement and agreements not inferred.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0012"><data key="node_entity_id">R179_E0012</data><data key="node_entity_type">historical_identity_discrepancy</data><data key="node_canonical_name">Nonwork SSN Authorization Status and Earnings-Posting Lag Identified in 2011</data><data key="node_domain">Person Identity/Earnings</data><data key="node_description">A work-authorization change not reported to SSA could leave the number holder in an obsolete nonwork SSN classification even after SSA credited earnings. In 2011 SSA was discussing DHS data use, not reporting completed automatic updates.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0013"><data key="node_entity_id">R179_E0013</data><data key="node_entity_type">historical_unimplemented_proposal</data><data key="node_canonical_name">2011 DHS Work Authorization Automatic SSA Update Feasibility Discussion</data><data key="node_domain">Person Identity/External Exchanges</data><data key="node_description">SSA described discussing with DHS feasibility of using DHS work authorization records to update SSA; did not report implementation.</data><data key="node_observed_status">historical_feasibility_only</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0014"><data key="node_entity_id">R179_E0014</data><data key="node_entity_type">historical_identity_assignment_rule</data><data key="node_canonical_name">Pre-2011 SSN Area Number Based on Card Mailing ZIP Code</data><data key="node_domain">Person Identity/Address Provenance</data><data key="node_description">Prior to SSN randomization, SSA testified that the first three SSN digits were determined from the SSN-card application mailing ZIP code; this historical assignment rule does not establish a durable residential location.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0015"><data key="node_entity_id">R179_E0015</data><data key="node_entity_type">historical_control_record</data><data key="node_canonical_name">CFRMS Claims-File SSN Exclusion List</data><data key="node_domain">Disability/Evidence/Hearings</data><data key="node_description">SSN-based exclusion list involved in authorized claims-file access and destruction; its concrete database and retention details not supplied.</data><data key="node_observed_status">historical_documented_in_2018_draft_PIA</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Source is historical draft-named PIA with unsigned approval area. Technology, authorization, and retention should not be projected unchanged to 2026.</data></node><node id="R179_E0016"><data key="node_entity_id">R179_E0016</data><data key="node_entity_type">historical_extraction_pipeline</data><data key="node_canonical_name">2018 Disability Database Daily and Weekly Operational Extracts</data><data key="node_domain">Disability/Evidence/Hearings</data><data key="node_description">PIA states initial disability and CDR claims extracted daily from NDDS, and weekly hearing/other determinations from OHO/Wilkes-Barre.</data><data key="node_observed_status">historical_documented_in_2018_draft_PIA</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Source is historical draft-named PIA with unsigned approval area. Technology, authorization, and retention should not be projected unchanged to 2026.</data></node><node id="R179_E0017"><data key="node_entity_id">R179_E0017</data><data key="node_entity_type">historical_data_provenance</data><data key="node_canonical_name">eDIB Historical Third-Party IRS Information Receipt (2018 PIA)</data><data key="node_domain">Person Identity/Address Provenance</data><data key="node_description">PIA names IRS among many third parties contributing some information to eDIB, without naming IRS source system, specific attributes, update route, or retention. No IRS-to-master-address linkage is established.</data><data key="node_observed_status">historical_source_class_only</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">4</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0018"><data key="node_entity_id">R179_E0018</data><data key="node_entity_type">historical_actuarial_process</data><data key="node_canonical_name">2010 OACT Demography Projection Process</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">2010 OACT group used fertility, mortality, immigration, marriage, divorce, historical and projected populations to supply SSA-area forecasts.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0019"><data key="node_entity_id">R179_E0019</data><data key="node_entity_type">historical_actuarial_process</data><data key="node_canonical_name">2010 OACT Economics Projection Process</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">2010 OACT group assembled BEA national accounts, BLS employment, wages, wages-covered by Social Security, AWI and inflation assumptions.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0020"><data key="node_entity_id">R179_E0020</data><data key="node_entity_type">historical_actuarial_process</data><data key="node_canonical_name">2010 OACT Beneficiaries Projection Process</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">2010 OACT group projected insured, retired, disabled, survivor and auxiliary beneficiary populations from demographic and economic inputs.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0021"><data key="node_entity_id">R179_E0021</data><data key="node_entity_type">historical_actuarial_process</data><data key="node_canonical_name">2010 OACT Trust Fund Operations and Actuarial Status Projection Process</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">2010 OACT group combined projected benefits, payroll tax, taxation of benefits, interest, administrative expenses and railroad interchange into actuarial results.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0022"><data key="node_entity_id">R179_E0022</data><data key="node_entity_type">historical_statistical_input_pipeline</data><data key="node_canonical_name">2010 OACT Mortality Model Historical Birth Death and Medicare Inputs</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">Mortality projection received NCHS/Census death and population histories and Medicare deaths/enrollments for older ages.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0023"><data key="node_entity_id">R179_E0023</data><data key="node_entity_type">historical_statistical_input_pipeline</data><data key="node_canonical_name">2010 OACT Fertility Historical U.S. Birth Statistics Input</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">Fertility group used historical U.S. births and resident female population for age-specific central birth-rate projections.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0024"><data key="node_entity_id">R179_E0024</data><data key="node_entity_type">historical_statistical_input</data><data key="node_canonical_name">2010 OACT BEA National Income and Product Accounts Input</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">Economics group used BEA NIPA economic data for GDP, wage, and income model components.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0025"><data key="node_entity_id">R179_E0025</data><data key="node_entity_type">historical_statistical_input</data><data key="node_canonical_name">2010 OACT BLS Employment and Class-of-Worker Input</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">Economics group used BLS historical employment and labor force data for worker counts and wage projections.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0026"><data key="node_entity_id">R179_E0026</data><data key="node_entity_type">historical_actuarial_model_subprocess</data><data key="node_canonical_name">2010 OACT AWARDS Sample-to-AIME Projection Subprocess</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">The AWARDS subprocess projected AIME distributions for newly entitled OASI and DI benefits from a 10% sample of MBR workers, with earnings histories from MEF and CWHS-based projections.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0027"><data key="node_entity_id">R179_E0027</data><data key="node_entity_type">historical_research_extract</data><data key="node_canonical_name">2010 OACT 225465-Record Newly Entitled Worker Awards Sample</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">A 10% sample of 225465 MBR newly entitled worker records with SSN, sex, birthdate, entitlement, benefit type and taxable earnings histories; sample tied to 2006 entitlements and December 2006–2008 pay status.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0028"><data key="node_entity_id">R179_E0028</data><data key="node_entity_type">historical_actuarial_input</data><data key="node_canonical_name">2010 OACT Continuous Work History Sample Earnings-Pattern Model Input</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">CWHS and MEF-posted earnings distributions supported historical covered earnings samples and projected earnings in AWARDS.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0029"><data key="node_entity_id">R179_E0029</data><data key="node_entity_type">historical_statistical_data_product</data><data key="node_canonical_name">2010 OACT Social Security Area Population Projection by Age Sex Marital Status</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">Demography group projected population in the Social Security area by single age, sex and marital status through 2084 in the 2010 projection set.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0030"><data key="node_entity_id">R179_E0030</data><data key="node_entity_type">historical_actuarial_data_product</data><data key="node_canonical_name">2010 OACT Projected AIME Bend-Point Distribution</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">AWARDS generated projected AIME distributions by age at entitlement, sex and OASI/DI fund for use in benefit-cost projection.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0031"><data key="node_entity_id">R179_E0031</data><data key="node_entity_type">historical_actuarial_input</data><data key="node_canonical_name">2010 OACT Railroad Interchange Projection Input</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">Trust fund group used Railroad Retirement Board data and economic projections to estimate net OASDI-RRB interchange.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0032"><data key="node_entity_id">R179_E0032</data><data key="node_entity_type">historical_actuarial_input</data><data key="node_canonical_name">2010 OACT Treasury OTA Income Taxation of Benefits Projection Input</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">2010 trust fund model used Treasury Office of Tax Analysis income-taxation data with CPS information to project taxed-benefit shares.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0033"><data key="node_entity_id">R179_E0033</data><data key="node_entity_type">historical_statistical_publication_family</data><data key="node_canonical_name">2010 OACT Long-Range Trustees Report Single-Year Data Tables</data><data key="node_domain">Actuarial/Statistical Production</data><data key="node_description">2010 OACT long-range tables published trust-fund operations, assumptions, year-by-year beneficiary counts, population and economic forecasts.</data><data key="node_observed_status">historical_model_as_of_2010</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0034"><data key="node_entity_id">R179_E0034</data><data key="node_entity_type">historical_external_payment_interface</data><data key="node_canonical_name">2013 Bank-Origin ACH Direct Deposit Auto-Enrollment Submission</data><data key="node_domain">Payments/Program Integrity</data><data key="node_description">SSA testified financial institutions electronically sent direct-deposit enrollment information to SSA through an auto-enrollment channel; account change authorization and verification were security concerns.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0035"><data key="node_entity_id">R179_E0035</data><data key="node_entity_type">historical_payment_security_control</data><data key="node_canonical_name">2012 Beneficiary Requested ACH Auto-Enrollment Transaction Block</data><data key="node_domain">Payments/Program Integrity</data><data key="node_description">SSA instituted a beneficiary-requested electronic block starting November 2012 to prevent bank-origin auto-enrollment from changing direct-deposit information, with 20752 requests as of June 2013.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0036"><data key="node_entity_id">R179_E0036</data><data key="node_entity_type">historical_identity_proofing_control</data><data key="node_canonical_name">2013 Direct Deposit Change Employee Identity Verification Requirement</data><data key="node_domain">Payments/Program Integrity</data><data key="node_description">SSA reported March 2013 policy restricting changes of electronic payment details unless the beneficiary spoke with teleservice or field-office staff who verified identity.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0037"><data key="node_entity_id">R179_E0037</data><data key="node_entity_type">historical_federal_payment_control</data><data key="node_canonical_name">2013 Treasury Electronic Payment Requirement Waiver Decision</data><data key="node_domain">Payments/External Exchanges</data><data key="node_description">Treasury rather than SSA controlled waivers from electronic federal benefit payment requirements effective March 2013.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0038"><data key="node_entity_id">R179_E0038</data><data key="node_entity_type">historical_application_pilot</data><data key="node_canonical_name">Electronic Bench Book Three-Hearing-Office Pilot (September 2012)</data><data key="node_domain">Hearings/Appeals</data><data key="node_description">SSA testified electronic bench book was piloted in three hearing offices in September 2012; pilot does not prove nationwide rollout at that time.</data><data key="node_observed_status">historical_pilot</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0039"><data key="node_entity_id">R179_E0039</data><data key="node_entity_type">historical_reporting_application</data><data key="node_canonical_name">How MI Doing ALJ Remand Feedback and Comparative Reporting (2012)</data><data key="node_domain">Hearings/Analytics</data><data key="node_description">SSA testified it built How MI Doing for adjudicators to review remand reasons and compare performance against hearing-office, regional, and national averages. A proposed future link to training modules was not represented as operational.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0040"><data key="node_entity_id">R179_E0040</data><data key="node_entity_type">historical_workflow_service</data><data key="node_canonical_name">CPMS Automated Hearing Noticing Function (2012)</data><data key="node_domain">Hearings/Correspondence</data><data key="node_description">SSA testified CPMS used stored case data to automatically produce hearing-related notices in 2012. Physical document service and print transport unspecified.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0041"><data key="node_entity_id">R179_E0041</data><data key="node_entity_type">historical_workflow_service</data><data key="node_canonical_name">Centralized Hearing Office Printing and Mailing Service (2012)</data><data key="node_domain">Hearings/Correspondence</data><data key="node_description">SSA testified centralized high-volume hearing and appeals printing and mailing was implemented in 2012. Not asserted to consume a particular CPMS interface.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0042"><data key="node_entity_id">R179_E0042</data><data key="node_entity_type">historical_decision_template</data><data key="node_canonical_name">Findings Integrated Templates for Hearing Decisions (2012)</data><data key="node_domain">Hearings/Decision Quality</data><data key="node_description">SSA used Findings Integrated Templates (FIT) to improve the legal sufficiency and preparation efficiency of written ALJ decisions as of 2012.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0043"><data key="node_entity_id">R179_E0043</data><data key="node_entity_type">historical_adjudicative_workflow</data><data key="node_canonical_name">Electronic Hearing Office Process (Electronic Business Process) 2012</data><data key="node_domain">Hearings/Processing</data><data key="node_description">SSA implemented a standardized electronic business process across hearing offices in 2012; not a claim of a single physical enterprise process engine.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0044"><data key="node_entity_id">R179_E0044</data><data key="node_entity_type">historical_external_case_access</data><data key="node_canonical_name">2012 Appointed Representative eFolder and CPMS Claim-Status Self-Service</data><data key="node_domain">Hearings/Representative Authorization</data><data key="node_description">SSA testified appointed representatives with authorized electronic-folder access could obtain hearing-scheduling information and the CPMS claim status for their clients, subject to case-specific access.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R179_E0045"><data key="node_entity_id">R179_E0045</data><data key="node_entity_type">historical_signature_control</data><data key="node_canonical_name">2012 Hearing ALJ and Attorney-Adjudicator Electronic Decision Signing</data><data key="node_domain">Hearings/Decision Quality</data><data key="node_description">SSA testified that ALJs and attorney adjudicators could sign decisions electronically in the 2012 hearing workflow; specific signing product and cryptographic implementation undisclosed.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Historical as-of source; physical deployment, later retirement, and 2026 status unverified.</data></node><node id="R180_E0001"><data key="node_entity_id">R180_E0001</data><data key="node_entity_type">historical_research_matching_process</data><data key="node_canonical_name">Census Survey Respondent Address-Assisted SSN Linkage (2009)</data><data key="node_domain">Person/Identity/Research</data><data key="node_description">Census Bureau research matching combined Numident SSN-application information with address records from IRS, SSA, and other sources to identify survey respondents where respondents had not opted out.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0002"><data key="node_entity_id">R180_E0002</data><data key="node_entity_type">research_address_domain</data><data key="node_canonical_name">Census Survey Identity Resolution Address Inputs from IRS and SSA (2009)</data><data key="node_domain">Address Provenance/Research</data><data key="node_description">Census Bureau used address information originating from IRS, SSA and others solely for survey respondent identity linkage as described in 2009; not an IRS write to SSA master records.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0003"><data key="node_entity_id">R180_E0003</data><data key="node_entity_type">research_governance_control</data><data key="node_canonical_name">Census Survey Respondent Opt-Out Identity Linkage Gate (2009)</data><data key="node_domain">Person/Identity/Privacy</data><data key="node_description">2009 description: respondent informed of federal-data statistical linkage and can opt out; restricts use of address and Numident linkage for research.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0004"><data key="node_entity_id">R180_E0004</data><data key="node_entity_type">research_data_transformation</data><data key="node_canonical_name">Census Linked Administrative Dataset SSN Replacement with Survey Identifier (2009)</data><data key="node_domain">Research/Privacy</data><data key="node_description">After linkage, Census removed SSNs and substituted unique survey identifiers in linked files according to 2009 article.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0005"><data key="node_entity_id">R180_E0005</data><data key="node_entity_type">historical_research_data_exchange</data><data key="node_canonical_name">Verified SSA Administrative Data Extract for Census Survey Linkage (2009)</data><data key="node_domain">Research/Data Sharing</data><data key="node_description">Following EVS validation, SSA extracted appropriate administrative records and sent extracts to Census for linkage with survey data in historical described process.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0006"><data key="node_entity_id">R180_E0006</data><data key="node_entity_type">historical_microsimulation_model</data><data key="node_canonical_name">Financial Eligibility Model (FEM) for SSI Research (2009)</data><data key="node_domain">Actuarial/Research</data><data key="node_description">2009 SSA publication describes FEM use of SIPP-linked administrative data to simulate SSI eligibility, participation, benefits distribution and poverty outcomes.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0007"><data key="node_entity_id">R180_E0007</data><data key="node_entity_type">historical_microsimulation_dataset</data><data key="node_canonical_name">Modeling Income in the Near Term (MINT) Linked Research Dataset (2009)</data><data key="node_domain">Actuarial/Research</data><data key="node_description">2009 SSA publication identifies MINT survey plus SSA administrative earnings, benefit and mortality linkages; does not conflate this historical version with MINT8.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0008"><data key="node_entity_id">R180_E0008</data><data key="node_entity_type">research_access_rule</data><data key="node_canonical_name">Census Special Sworn Status and Title 13 Matched Data Access Control (2009)</data><data key="node_domain">Research/Governance</data><data key="node_description">Matched Census administrative data access required Census authorization, Special Sworn Status and approved purposes/sites; IRS rules apply to tax data.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0009"><data key="node_entity_id">R180_E0009</data><data key="node_entity_type">historical_external_hr_system</data><data key="node_canonical_name">Department of the Interior Federal Personnel/Payroll System (FPPS, 2008-2017)</data><data key="node_domain">Human Resources/External</data><data key="node_description">DOI FPPS processes SSA payroll and personnel actions; 2017 PIA calls it mainframe-based integrated online system; historical scope.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0010"><data key="node_entity_id">R180_E0010</data><data key="node_entity_type">historical_external_service_organization</data><data key="node_canonical_name">DOI National Business Center Payroll and Personnel Shared Service (2008)</data><data key="node_domain">Human Resources/External</data><data key="node_description">Department of Interior National Business Center performed personnel and payroll processing for SSA in 2008 PIA.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0011"><data key="node_entity_id">R180_E0011</data><data key="node_entity_type">historical_operational_data_store</data><data key="node_canonical_name">SSA Human Resources Operational Data Store (HRODS, 2017)</data><data key="node_domain">Human Resources/Data</data><data key="node_description">2017 PIA calls HRODS a database storing HR information for active and inactive SSA employees; 2008 predecessor report describes HRMIS extracts for management information.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0012"><data key="node_entity_id">R180_E0012</data><data key="node_entity_type">historical_workforce_system</data><data key="node_canonical_name">Mainframe Time and Attendance System (MTAS, 2008)</data><data key="node_domain">Human Resources/Timekeeping</data><data key="node_description">2008 HRMIS PIA describes MTAS timekeeper, certifier, administrator daily/pay-period accounting and electronic interchange with DOI FPPS.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0013"><data key="node_entity_id">R180_E0013</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Agency Skills Inventory (ASI)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Skills inventory for supervisors of current and planned workforce competencies.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0014"><data key="node_entity_id">R180_E0014</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Anti-Harassment and Hostile Work Environment Case Tracking System (AHWECTS)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Tracks workplace harassment allegations.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0015"><data key="node_entity_id">R180_E0015</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Employee Data (EEData)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Web-based employee HR viewing, updating and printing interface.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0016"><data key="node_entity_id">R180_E0016</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Equal Employment Opportunity Case Management System (EEOCMS)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Tracks EEO complaints.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0017"><data key="node_entity_id">R180_E0017</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">SSA Human Resources Portal (2017)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Intranet interface supporting HR services and business functions.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0018"><data key="node_entity_id">R180_E0018</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Labor Relations/Employee Relations Workload Management System (LR/ER-WMS)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Tracks labor and employee relations cases.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0019"><data key="node_entity_id">R180_E0019</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Minority Serving Institutions Reporting System (MSIRS)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Produces Agency Minority Serving Institutions reports.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0020"><data key="node_entity_id">R180_E0020</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Official Union Time Tracking System (OUTTS)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Tracks union representatives official time.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0021"><data key="node_entity_id">R180_E0021</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Performance Assessment and Communication System (PACS, HR)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Employee performance plans, discussions and appraisals; not physical-access PACS.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0022"><data key="node_entity_id">R180_E0022</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Payroll Operational Data Store (PayODS)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Provides access to Payroll Analysis Recap Reports and Full Time Equivalency Tracking reports.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0023"><data key="node_entity_id">R180_E0023</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Position Data Application (PDA)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. HR specialist position data, awards and reference tables.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0024"><data key="node_entity_id">R180_E0024</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">SSA Learning Management System (2017)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Stores and retrieves training learning opportunities.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0025"><data key="node_entity_id">R180_E0025</data><data key="node_entity_type">historical_hr_subsystem</data><data key="node_canonical_name">Training Online Nomination System (TONS)</data><data key="node_domain">Human Resources/Applications</data><data key="node_description">2017 HRS PIA identifies named human resources component. Supports supervisor training nominations.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0026"><data key="node_entity_id">R180_E0026</data><data key="node_entity_type">historical_personnel_address_attribute</data><data key="node_canonical_name">SSA Personnel Mailing Address Recorded in Human Resources System (2017)</data><data key="node_domain">Address Provenance/Employees</data><data key="node_description">2017 HRS privacy assessment explicitly lists mailing addresses about employees and other covered workforce individuals; not a benefit claimant or Numident address attribute.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0027"><data key="node_entity_id">R180_E0027</data><data key="node_entity_type">historical_major_application_boundary</data><data key="node_canonical_name">Supplemental Security Income Record Maintenance System (SSIRMS, 2007)</data><data key="node_domain">Title XVI/Title VIII</data><data key="node_description">SSA FY07 PIA identifies historical SSIRMS major application for establishing, maintaining and paying Title XVI SSI and Title VIII Special Veterans Benefits, including beneficiary addresses.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0028"><data key="node_entity_id">R180_E0028</data><data key="node_entity_type">historical_ssi_program_attribute</data><data key="node_canonical_name">SSIRMS Historical Recipient Address and Communications Attributes (2007)</data><data key="node_domain">Address Provenance/Title XVI</data><data key="node_description">SSIRMS PIA explicitly covers person addresses and communication, but does not itself specify automatic IRS origin, persistence rules, or master transaction method.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0029"><data key="node_entity_id">R180_E0029</data><data key="node_entity_type">data_priority_control</data><data key="node_canonical_name">EDCS MCS-First Mainframe Claim Propagation Priority (2013)</data><data key="node_domain">Disability/Person Attributes</data><data key="node_description">POMS states EDCS propagates MCS before other mainframe systems, otherwise active MSSICS and sources, unless abbreviated claims.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0030"><data key="node_entity_id">R180_E0030</data><data key="node_entity_type">case_information_quality_rule</data><data key="node_canonical_name">EDCS Mainframe-over-Internet Disability Report Attribute Precedence (2013)</data><data key="node_domain">Disability/Data Quality</data><data key="node_description">POMS says mainframe data overlays Internet Disability Report field values even if mainframe value is empty; excludes allegation concatenation exception.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0031"><data key="node_entity_id">R180_E0031</data><data key="node_entity_type">record_update_rule</data><data key="node_canonical_name">EDCS Mainframe-Correction-Then-Repropagation Rule (2013)</data><data key="node_domain">Disability/Address Provenance</data><data key="node_description">Most propagated EDCS values including claimed contact data cannot be overkeyed. Staff correct MCS/MSSICS origin and repropagate to EDCS; disability allegation and DLI exceptions exist.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0032"><data key="node_entity_id">R180_E0032</data><data key="node_entity_type">historical_copy_data_quality_rule</data><data key="node_canonical_name">EDCS Copied-Prior-Folder Contact Information Reverification (2013)</data><data key="node_domain">Disability/Address Provenance</data><data key="node_description">POMS requires verifying current contact information when copying historical closed-folder records, including source address and phone, rather than assuming continued correctness.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0033"><data key="node_entity_id">R180_E0033</data><data key="node_entity_type">claims_computation_dependency</data><data key="node_canonical_name">EDCS Disability Insured Status Computation Prerequisite (DLI/DFI)</data><data key="node_domain">Disability/Title II</data><data key="node_description">POMS requires MCS Earnings Computation prior to EDCS entry for first/last insured dates to propagate.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0034"><data key="node_entity_id">R180_E0034</data><data key="node_entity_type">case_propagation_exception</data><data key="node_canonical_name">EDCS Multiple DIB Claims Propagation Halt</data><data key="node_domain">Disability/Claims</data><data key="node_description">EDCS case creation stops with an alert when multiple DIB claims detected; resolve on MCS, and incorrect mainframe transfer can cause false alert.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0035"><data key="node_entity_id">R180_E0035</data><data key="node_entity_type">historical_master_record_segment</data><data key="node_canonical_name">Master Earnings File Earnings Detail Segment (2009)</data><data key="node_domain">Earnings/Data</data><data key="node_description">2009 SSA research explains individual yearly W-2 employer and self-employment postings by employer and wage category, including corrections.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0036"><data key="node_entity_id">R180_E0036</data><data key="node_entity_type">historical_master_record_segment</data><data key="node_canonical_name">Master Earnings File Summary Segment (2009)</data><data key="node_domain">Earnings/Data</data><data key="node_description">2009 SSA research describes yearly consolidated wages, tips, self-employment, QCs and SSN demography with no employer information.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0037"><data key="node_entity_id">R180_E0037</data><data key="node_entity_type">earnings_identity_verification_process</data><data key="node_canonical_name">Historical Name-and-SSN Numident Gate Before MEF Posting (2009)</data><data key="node_domain">Earnings/Person Identity</data><data key="node_description">Before MEF posting SSA matches worker name and SSN to Numident; unresolved items go to Earnings Suspense File.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0038"><data key="node_entity_id">R180_E0038</data><data key="node_entity_type">source_address_attribute</data><data key="node_canonical_name">2009 Employer-Reported W-2 Employee Address Input</data><data key="node_domain">Address Provenance/Earnings</data><data key="node_description">W-2 contains an employer-reported employee name and address, distinct from verified beneficiary residence and without established automatic Numident/MBR/SSR update.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0039"><data key="node_entity_id">R180_E0039</data><data key="node_entity_type">source_address_attribute</data><data key="node_canonical_name">2009 W-2 Employer Name Address and ZIP Input</data><data key="node_domain">Address Provenance/Earnings</data><data key="node_description">2009 publication lists employer name, address, ZIP, EIN as W-2 fields; distinct from worker home address.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0040"><data key="node_entity_id">R180_E0040</data><data key="node_entity_type">earnings_reconciliation_process</data><data key="node_canonical_name">MEF W-2 Wage Total versus W-3 Employer Summary Balancing (2009)</data><data key="node_domain">Earnings/Controls</data><data key="node_description">SSA publication describes balancing totals of W-2 with employer W-3 summary before accepting earnings for posting.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0041"><data key="node_entity_id">R180_E0041</data><data key="node_entity_type">historical_earnings_update_process</data><data key="node_canonical_name">MEF W-2c Negative Offset and Corrected Replacement Posting (2009)</data><data key="node_domain">Earnings/Corrections</data><data key="node_description">SSA research documents separate reversal posting and corrected wage amount after W-2c, rather than deleting the previous Detail Segment record.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0042"><data key="node_entity_id">R180_E0042</data><data key="node_entity_type">historical_research_sample</data><data key="node_canonical_name">Continuous Work History Sample 1-Percent SSA Research Extract (2009)</data><data key="node_domain">Earnings/Research</data><data key="node_description">2009 paper describes CWHS 1-percent SSN sample with MEF earnings, Numident demographics and MBR annual benefits, plus active/inactive partitions.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0043"><data key="node_entity_id">R180_E0043</data><data key="node_entity_type">historical_research_dataset</data><data key="node_canonical_name">CWHS Employee-Employer Covered Wages One-Percent File (2009)</data><data key="node_domain">Earnings/Research</data><data key="node_description">2009 MEF article identifies annual employee-employer file limited to covered wages.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0044"><data key="node_entity_id">R180_E0044</data><data key="node_entity_type">historical_research_dataset</data><data key="node_canonical_name">CWHS Employee-Employer Covered and Noncovered Wages One-Percent File (2009)</data><data key="node_domain">Earnings/Research</data><data key="node_description">2009 MEF article identifies companion annual EE-ER file containing covered and noncovered wages and industry/location info.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0045"><data key="node_entity_id">R180_E0045</data><data key="node_entity_type">historical_research_dataset</data><data key="node_canonical_name">CWHS Longitudinal Employee-Employer Data (LEED, 2009)</data><data key="node_domain">Earnings/Research</data><data key="node_description">2009 MEF article documents annual 1% longitudinal employee-employer research file with geographic/industry characteristics.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0046"><data key="node_entity_id">R180_E0046</data><data key="node_entity_type">historical_research_dataset</data><data key="node_canonical_name">CWHS Annual Self-Employment Snapshot Research File (2009)</data><data key="node_domain">Earnings/Research</data><data key="node_description">2009 MEF article describes annual research snapshot of initial self-employment postings containing IRS-transmitted additional fields not stored in MEF.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0047"><data key="node_entity_id">R180_E0047</data><data key="node_entity_type">research_geographic_attribution_rule</data><data key="node_canonical_name">CWHS Employee-Employer County and Industry Information (2009)</data><data key="node_domain">Geography/Research</data><data key="node_description">CWHS EE-ER employer and employee location and industry do not necessarily establish current place of residence or job geography.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R180_E0048"><data key="node_entity_id">R180_E0048</data><data key="node_entity_type">historical_disclosure_control</data><data key="node_canonical_name">iAppeals 2012 Internal Revenue Code Section 6103 Disclosure Restriction</data><data key="node_domain">Hearings/Governance</data><data key="node_description">2012 PIA says tax return information cannot be disclosed by iAppeals except as allowed by law, IRS or regulations.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-10</data><data key="node_confidence">5</data><data key="node_notes">Documented in dated primary source; 2026 operation, hosting, technical integration, and retention not established.</data></node><node id="R181_E001"><data key="node_entity_id">R181_E001</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">ICDB Shared Name, SSN, Birthdate and Sex Attributes</data><data key="node_domain">Person / Shared Client</data><data key="node_description">The 2007 ICDB PIA lists names, SSNs, dates of birth and sex in the shared Client Data carried across major application systems.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E002"><data key="node_entity_id">R181_E002</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">ICDB Citizenship Country and U.S. Citizenship Basis Attributes</data><data key="node_domain">Person / Citizenship</data><data key="node_description">The 2007 ICDB PIA identifies country of citizenship and basis of U.S. citizenship among common Client Data attributes.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E003"><data key="node_entity_id">R181_E003</data><data key="node_entity_type">data_population</data><data key="node_canonical_name">ICDB Client Records for Persons Without Program Entitlement</data><data key="node_domain">Person / Cross Program</data><data key="node_description">2007 PIA says SSA maintains ICDB client data even for people who are not entitled to Title II or Title XVI benefits.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E004"><data key="node_entity_id">R181_E004</data><data key="node_entity_type">functional_component</data><data key="node_canonical_name">ICDB Cross-Program Shared Data Screens and Access Software</data><data key="node_domain">Enterprise Client Data</data><data key="node_description">2007 ICDB PIA describes databases, common screens and access software that share client information among major program systems.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E005"><data key="node_entity_id">R181_E005</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">CBSV 2008 BSO Registration User Records</data><data key="node_domain">Identity / External Users</data><data key="node_description">2008 CBSV PIA identifies BSO registration database holding requester employee user IDs, company affiliations and other registration PII for authorized third-party verification users.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E006"><data key="node_entity_id">R181_E006</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-88 CBSV Authorized Employee Designation</data><data key="node_domain">Identity / Consent</data><data key="node_description">A company official signs SSA-88 to designate its employees authorized to use CBSV, and SSA OCO matches the designation to a BSO registration user ID.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E007"><data key="node_entity_id">R181_E007</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">CBSV 2008 Company Official Mailed Activation Code</data><data key="node_domain">Identity / Access Authorization</data><data key="node_description">After authorization confirmation SSA mails an activation code to the designated company official to distribute to the approved requester employee.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E008"><data key="node_entity_id">R181_E008</data><data key="node_entity_type">interface</data><data key="node_canonical_name">CBSV 2008 BSO Batch Verification Submission</data><data key="node_domain">Identity / Verification</data><data key="node_description">The 2008 PIA describes CBSV employee users submitting SSN verification requests in batch mode via BSO.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E009"><data key="node_entity_id">R181_E009</data><data key="node_entity_type">interface</data><data key="node_canonical_name">CBSV 2008 BSO Ten-Request Real-Time Submission</data><data key="node_domain">Identity / Verification</data><data key="node_description">The 2008 PIA describes authorized Internet users submitting up to 10 verification requests for real-time response.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E010"><data key="node_entity_id">R181_E010</data><data key="node_entity_type">proposed_interface</data><data key="node_canonical_name">CBSV 2008 Requester-Hosted Web Service Option</data><data key="node_domain">Identity / Verification</data><data key="node_description">The PIA describes an option for third-party requesters to build a compatible real-time web service; planned in 2008, not independently verified as deployed then.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">4</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E011"><data key="node_entity_id">R181_E011</data><data key="node_entity_type">data_governance</data><data key="node_canonical_name">CBSV 2008 Requester Consent Retention Rule</data><data key="node_domain">Identity / Consent</data><data key="node_description">2008 CBSV PIA instructs requesting parties to retain signed consent forms on paper or electronically for seven years after verification.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E012"><data key="node_entity_id">R181_E012</data><data key="node_entity_type">data_governance</data><data key="node_canonical_name">CBSV 2008 Ninety-Day Verification Consent Validity</data><data key="node_domain">Identity / Consent</data><data key="node_description">2008 PIA says verification consent normally lasts 90 days unless the authorizing individual specifies another period.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E013"><data key="node_entity_id">R181_E013</data><data key="node_entity_type">data_governance</data><data key="node_canonical_name">CBSV 2008 Verified SSN Information Redisclosure Restriction</data><data key="node_domain">Identity / Access Restrictions</data><data key="node_description">2008 CBSV agreement prohibits resale and redisclosure of verified SSN information and restricts use to the consented purpose.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-11-05</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E014"><data key="node_entity_id">R181_E014</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2008 Telephone Claim-Status Eight-Digit Confirmation Number</data><data key="node_domain">Customer Service / Authentication</data><data key="node_description">PIA describes an eight-digit confirmation number generated for Title II claims lodged through office, telephone or website and needed for automated status inquiry.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-02-15</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E015"><data key="node_entity_id">R181_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2008 Telephone Claim-Status Identity and Claim Lookup</data><data key="node_domain">Customer Service / Identity</data><data key="node_description">2008 IVR process matches submitted SSN and birthdate against SSN-holder records and confirmation number against Claims Folders System to find the relevant Title II claim.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-02-15</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E016"><data key="node_entity_id">R181_E016</data><data key="node_entity_type">transient_data</data><data key="node_canonical_name">2008 Telephone Claims Status Ephemeral Input Memory</data><data key="node_domain">Customer Service / Privacy</data><data key="node_description">2008 PIA states caller-entered SSN, DOB and confirmation number are encrypted in short-lived memory and erased at call completion, not stored as a new permanent record.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-02-15</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E017"><data key="node_entity_id">R181_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2008 Telephone Claim-Status Postal Confirmation Delivery</data><data key="node_domain">Customer Service / Address</data><data key="node_description">2008 PIA describes sending a confirmation number by postal mail to claimant mailing address when the initial Title II claim was filed by telephone.</data><data key="node_observed_status">historical_2008_pia_design_not_verified_deployment</data><data key="node_observed_as_of">2008-02-15</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E018"><data key="node_entity_id">R181_E018</data><data key="node_entity_type">audit_data</data><data key="node_canonical_name">ATS Timestamped PIN and SSN Transaction Audit Event</data><data key="node_domain">Security / Program Integrity</data><data key="node_description">2017 ATS PIA says auditable transaction records contain employee PIN, timestamp and application-specific values, collected when employees/contractors/public perform auditable actions.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2017-12-20</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E019"><data key="node_entity_id">R181_E019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">ATS PIN-SSN-Office Audit Retrieval Procedure</data><data key="node_domain">Security / Program Integrity</data><data key="node_description">2017 PIA says authorized reviewers can retrieve audit records by personal ID number, SSN, or office/module for investigations of potentially improper actions.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2017-12-20</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E020"><data key="node_entity_id">R181_E020</data><data key="node_entity_type">audit_data</data><data key="node_canonical_name">CIRP 2007 Programmatic Transaction Review Item</data><data key="node_domain">Security / Program Integrity</data><data key="node_description">2007 CIRP PIA describes potential misuse transactions including actor employee PIN, action timestamp, beneficiary SSN and transaction action type.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E021"><data key="node_entity_id">R181_E021</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CIRP 2007 Reviewer Disposition and Case Management</data><data key="node_domain">Security / Program Integrity</data><data key="node_description">CIRP provided authorized staff screens to review flagged transaction case details, record outcomes, report results and refer potential fraud for investigation.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E022"><data key="node_entity_id">R181_E022</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">Everbridge Incorporated (2021 SSA MENS Hosting Contractor)</data><data key="node_domain">Infrastructure / SaaS</data><data key="node_description">SSA 2021 MENS PIA expressly identifies Everbridge Incorporated as the contractor hosting the web-based MENS SaaS application and segregating SSA-owned information.</data><data key="node_observed_status">documented_contract_relationship_2021</data><data key="node_observed_as_of">2021-09-22</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E023"><data key="node_entity_id">R181_E023</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">MENS 2021 Employee and PIV-Contractor Initial Contact Dataset</data><data key="node_domain">Workforce / Emergency Contact</data><data key="node_description">SSA 2021 MENS PIA documents an initial dataset of current employees and PIV card-holding contractors names and SSA email addresses provided to Everbridge.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2021-09-22</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E024"><data key="node_entity_id">R181_E024</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">MENS 2021 Self-Managed After-Hours Contact Channels</data><data key="node_domain">Workforce / Address Provenance</data><data key="node_description">MENS staff and eligible contractors maintain personal phone, email and emergency contact details, separate from beneficiary mailing or residence records.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2021-09-22</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E025"><data key="node_entity_id">R181_E025</data><data key="node_entity_type">architecture_boundary</data><data key="node_canonical_name">MENS 2021 Emergency Notification SaaS Hosting Boundary</data><data key="node_domain">Infrastructure / SaaS</data><data key="node_description">2021 SSA PIA describes web SaaS hosted by Everbridge, with agency-owned data segregated in vendor environment and FIPS 199 Moderate impact level.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2021-09-22</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E026"><data key="node_entity_id">R181_E026</data><data key="node_entity_type">data_governance</data><data key="node_canonical_name">SSA Vendor Repository 2024 Subject-Line Taxonomy Tags</data><data key="node_domain">Procurement / Repository</data><data key="node_description">SSA 2024 vendor-repository submission requires vendor name, subject and up to three business-topic tags in email subject to align with internal information-repository data structure.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2024-03-11</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E027"><data key="node_entity_id">R181_E027</data><data key="node_entity_type">data_governance</data><data key="node_canonical_name">SSA Vendor Repository 2024 Approximately One-Year Deletion Control</data><data key="node_domain">Procurement / Retention</data><data key="node_description">SSA instructions explicitly state vendor capability information remains in its repository for approximately one year then is deleted unless the vendor resubmits.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2024-03-11</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E028"><data key="node_entity_id">R181_E028</data><data key="node_entity_type">statistical_product</data><data key="node_canonical_name">2014 Trustees Report Historical Single-Year Projection Data Collection</data><data key="node_domain">Actuarial / Publication</data><data key="node_description">2014 SSA OACT table index offers tables consistent with the 2014 Trustees Report, including selected historical values and single-year actuarial projections under alternative assumptions.</data><data key="node_observed_status">historically_published</data><data key="node_observed_as_of">2014</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E029"><data key="node_entity_id">R181_E029</data><data key="node_entity_type">statistical_product</data><data key="node_canonical_name">2014 Trustees Single-Year DI Current-Payment Beneficiary Projection Table V.C5</data><data key="node_domain">Actuarial / Disability</data><data key="node_description">2014 Trustees Report supplemental V.C5 includes disability worker and auxiliary beneficiary current-payment projections through calendar year 2090, frozen in the 2014 projection vintage.</data><data key="node_observed_status">historically_published</data><data key="node_observed_as_of">2014</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E030"><data key="node_entity_id">R181_E030</data><data key="node_entity_type">statistical_product</data><data key="node_canonical_name">2014 Trustees Single-Year Trust Fund Operations in Constant 2014 Dollars VI.G7</data><data key="node_domain">Actuarial / Trust Funds</data><data key="node_description">2014 Trustees supplemental table VI.G7 expresses combined OASI/DI trust-fund operations using constant 2014 dollars; vintage and price basis differ from later releases.</data><data key="node_observed_status">historically_published</data><data key="node_observed_as_of">2014</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E031"><data key="node_entity_id">R181_E031</data><data key="node_entity_type">historical_reference</data><data key="node_canonical_name">IRS Project 719 Historic SSA Debt Skiptracing Reference</data><data key="node_domain">Address Provenance / IRS</data><data key="node_description">2008 POMS GN 02210.213 says debtor BOAN is required for IRS Project 719 in skiptracing. Source does not define data contents, mechanism, persistence or any authority to update MBR/SSR.</data><data key="node_observed_status">historically_referenced_unverified_mechanism</data><data key="node_observed_as_of">2008-08-25</data><data key="node_confidence">4</data><data key="node_notes">Named reference only. No automatic IRS address feed, no claim of current Project 719 operation, no update path.</data></node><node id="R181_E032"><data key="node_entity_id">R181_E032</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2013 SMACS Credential-Holder Address Attribute</data><data key="node_domain">Security / Staff Identity and Address</data><data key="node_description">2013 SMACS PIA table lists an address in EPECS and PIV Card Management and SAFE, for employee/contractor credential administration, not claimant residence.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2013-09-30</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R181_E033"><data key="node_entity_id">R181_E033</data><data key="node_entity_type">audit_data</data><data key="node_canonical_name">2013 LSAS Physical Entry Event Log</data><data key="node_domain">Security / Facilities</data><data key="node_description">2013 SMACS PIA describes LENEL Security Access System recording authorized entry/unauthorized access or alarms at protected NCC and adjacent areas; possible use in fraud-related time-and-attendance review.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2013-09-30</data><data key="node_confidence">5</data><data key="node_notes">Direct source documentation; historical observation; not a claim of current production deployment.</data></node><node id="R182_E001"><data key="node_entity_id">R182_E001</data><data key="node_entity_type">software</data><data key="node_canonical_name">Master Data Access Method (MADAM)</data><data key="node_acronym">MADAM</data><data key="node_domain">Enterprise Data / Legacy Master Files</data><data key="node_description">SSA OIG identifies IBM Assembler-based MADAM as a historical file-management mechanism for MBR, SSR, MEF and Numident/Alphident.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E002"><data key="node_entity_id">R182_E002</data><data key="node_entity_type">interface</data><data key="node_canonical_name">MADAM Compatibility Interface During DB2 Migration</data><data key="node_acronym" /><data key="node_domain">Enterprise Data / Application Access</data><data key="node_description">During 2009 mixed storage, the MADAM compatibility interface directed unchanged legacy program calls to either MADAM or DB2 API.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E003"><data key="node_entity_id">R182_E003</data><data key="node_entity_type">interface</data><data key="node_canonical_name">MADAM-to-DB2 Application Programming Interface</data><data key="node_acronym" /><data key="node_domain">Enterprise Data / Application Access</data><data key="node_description">SSA developed a DB2 API to translate legacy MADAM data calls into DB2 queries during master-file migration.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E004"><data key="node_entity_id">R182_E004</data><data key="node_entity_type">modernization_project</data><data key="node_canonical_name">MADAM-to-DB2 Master Files Conversion Project</data><data key="node_acronym" /><data key="node_domain">Infrastructure / Data Modernization</data><data key="node_description">Three-phase historical effort: move four master files to DB2, remove old interface calls, then support direct DB2 access.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E005"><data key="node_entity_id">R182_E005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MADAM-to-DB2 Phase I Master File Migration</data><data key="node_acronym" /><data key="node_domain">Infrastructure / Data Modernization</data><data key="node_description">First conversion stage covered Numident/Alphident, MEF, SSR, MBR; only first two were completed by Nov 2009.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E006"><data key="node_entity_id">R182_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MADAM-to-DB2 Phase II Legacy Application Call Migration</data><data key="node_acronym" /><data key="node_domain">Infrastructure / Data Modernization</data><data key="node_description">Planned program-by-program change from MADAM interface calls to DB2 API; 2010 source does not establish execution.</data><data key="node_observed_status">planned_2010</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E007"><data key="node_entity_id">R182_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">MADAM-to-DB2 Phase III Direct DB2 Application Rewrite</data><data key="node_acronym" /><data key="node_domain">Infrastructure / Data Modernization</data><data key="node_description">Planned revision of application programs to access DB2 directly; no phase III project plan at 2010 audit.</data><data key="node_observed_status">planned_2010</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E008"><data key="node_entity_id">R182_E008</data><data key="node_entity_type">architecture_state</data><data key="node_canonical_name">2009 MADAM and DB2 Mixed Master-File Storage State</data><data key="node_acronym" /><data key="node_domain">Enterprise Data / Historical State</data><data key="node_description">November 2009 snapshot: Numident/Alphident and MEF stored in DB2; MBR and SSR still used MADAM.</data><data key="node_observed_status">observed_2009</data><data key="node_observed_as_of">2009-11</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E009"><data key="node_entity_id">R182_E009</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">2009 Master-File Segments and Subsegments</data><data key="node_acronym" /><data key="node_domain">Enterprise Data / Master File Layout</data><data key="node_description">OIG describes MBR/SSR/MEF/Numident master-file records split into segments and subsegments.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E010"><data key="node_entity_id">R182_E010</data><data key="node_entity_type">architecture_constraint</data><data key="node_canonical_name">MADAM Compressed to DB2 Uncompressed Data-Format Constraint</data><data key="node_acronym" /><data key="node_domain">Infrastructure / Historical Data</data><data key="node_description">2010 OIG reports different compressed/uncompressed representations, requiring some application logic changes beyond file conversion.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E011"><data key="node_entity_id">R182_E011</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">MBR Historical Cross-Program Reference Records</data><data key="node_acronym" /><data key="node_domain">Title II / Person Linkage</data><data key="node_description">2010 OIG Appendix C states MBR holds short references for SSI, Black Lung and Railroad Retirement benefits, not equivalent to full records in those programs.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E012"><data key="node_entity_id">R182_E012</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2009 Alphident Name and Birthdate SSN Lookup Function</data><data key="node_acronym" /><data key="node_domain">Enumeration / Person Identity</data><data key="node_description">Historical OIG description identifies Alphident as SSN lookup by name and birth date when the SSN is unknown.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2010-05-13</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E013"><data key="node_entity_id">R182_E013</data><data key="node_entity_type">general_support_system</data><data key="node_canonical_name">Enterprise Wide Mainframe and Distributed Network Telecommunications Services</data><data key="node_acronym">EWANS</data><data key="node_domain">Infrastructure / Access Management</data><data key="node_description">2008 SSA PIA describes mainframe/distributed telecommunications infrastructure supporting 13 GSS and six major applications.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-09-08</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E014"><data key="node_entity_id">R182_E014</data><data key="node_entity_type">access_control_repository</data><data key="node_canonical_name">TOP SECRET Mainframe User Repository</data><data key="node_acronym">TOP SECRET</data><data key="node_domain">Workforce Identity / Mainframe</data><data key="node_description">2008 PIA explicitly calls TOP SECRET the mainframe repository holding user SSA systems access permissions and PINs.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-09-08</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E015"><data key="node_entity_id">R182_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Management-Approved Mainframe Access Enrollment</data><data key="node_acronym" /><data key="node_domain">Workforce Identity / Access Management</data><data key="node_description">SSA management submitted Form SSA-120 with workforce name and SSN; TOP SECRET granted access and assigned PIN.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-09-08</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E016"><data key="node_entity_id">R182_E016</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Historical SSA Workforce Mainframe Personal Identification Number</data><data key="node_acronym" /><data key="node_domain">Workforce Identity / Access Management</data><data key="node_description">PIA describes a unique employee or contractor PIN used to enter SSA applications through EWANS.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-09-08</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E017"><data key="node_entity_id">R182_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2008 N8NN One-Time Caller Identity Collection and Reuse</data><data key="node_acronym" /><data key="node_domain">Customer Contact / Identity</data><data key="node_description">2008 TVDC PIA describes collecting caller identity once and sharing required elements across automated applications and an agent within the same call.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-10-11</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E018"><data key="node_entity_id">R182_E018</data><data key="node_entity_type">transient_data</data><data key="node_canonical_name">2008 N8NN Ephemeral Encrypted Caller Authentication Payload</data><data key="node_acronym" /><data key="node_domain">Customer Contact / Privacy</data><data key="node_description">Caller SSN, DOB, other requested identifiers stored only in encrypted short-lived call memory; deleted after call and not in system logs.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-10-11</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E019"><data key="node_entity_id">R182_E019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2008 N8NN Conditional Caller Identity Handoff to Agent</data><data key="node_acronym" /><data key="node_domain">Customer Contact / Identity</data><data key="node_description">TVDC sends caller-entered identity elements to live agents only for caller-selected handoff or failed automated verification.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-10-11</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E020"><data key="node_entity_id">R182_E020</data><data key="node_entity_type">authorization_control</data><data key="node_canonical_name">2008 N8NN Automated Telephone and Internet Access Block</data><data key="node_acronym" /><data key="node_domain">Customer Contact / Identity</data><data key="node_description">Individuals can block automated channels; the telephone application offers agent or in-person handling instead.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-10-11</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E021"><data key="node_entity_id">R182_E021</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2008 Telephone Caller Knowledge-Based Authentication Fields</data><data key="node_acronym" /><data key="node_domain">Customer Contact / Identity</data><data key="node_description">PIA lists SSN, DOB, name, mother maiden name, birth place, last payment, claim number and password as possible caller inputs.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-10-11</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E022"><data key="node_entity_id">R182_E022</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">State Electronic Death Registration Verified Report</data><data key="node_acronym" /><data key="node_domain">Person / Death Reporting</data><data key="node_description">2007 DACUS PIA distinguishes state EDR verified death reports from reports requiring conflict investigation.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E023"><data key="node_entity_id">R182_E023</data><data key="node_entity_type">workflow_control</data><data key="node_canonical_name">Non-EDR or Conflicting Death Report Development Alert</data><data key="node_acronym" /><data key="node_domain">Person / Program Integrity</data><data key="node_description">On conflicts from reports other than verified state EDR, DACUS routed an investigative alert to the SSA field office.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E024"><data key="node_entity_id">R182_E024</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2007 DACUS Conditional Numident Death-Posting Route</data><data key="node_acronym" /><data key="node_domain">Person / Identity Update</data><data key="node_description">No conflicts or resolved conflicts allowed DACUS data to pass to SSNEC for Numident posting.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E025"><data key="node_entity_id">R182_E025</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2007 Daily Update Data Exchange Non-State Death Reports</data><data key="node_acronym" /><data key="node_domain">Person / Death Reporting</data><data key="node_description">2007 DACUS PIA describes SSA Daily Update Data Exchange reports of death from nonstate sources.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-28</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E026"><data key="node_entity_id">R182_E026</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">2009 RECS Enumeration-at-Birth and Entry Coverage Limitation</data><data key="node_acronym" /><data key="node_domain">Enumeration / Research Demography</data><data key="node_description">EAB states and DHS EAE did not provide same voluntary race/ethnicity values as in-office SSN application contacts; RECS coverage not universal.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-11-18</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E027"><data key="node_entity_id">R182_E027</data><data key="node_entity_type">data_standard</data><data key="node_canonical_name">2009 RECS Revised Multi-Race and Separate Ethnicity Categories</data><data key="node_acronym" /><data key="node_domain">Enumeration / Statistical Data</data><data key="node_description">PIA describes use of updated OMB categories supporting multiple race selections and separate Hispanic ethnicity.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-11-18</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E028"><data key="node_entity_id">R182_E028</data><data key="node_entity_type">data_retention_rule</data><data key="node_canonical_name">2009 RECS Planned Historical Race/Ethnicity Numident Retention Split</data><data key="node_acronym" /><data key="node_domain">Enumeration / Research Demography</data><data key="node_description">PIA anticipated retaining older race data in SSN-holder master and new entries in RECS after transition; completion not verified.</data><data key="node_observed_status">planned_in_2009</data><data key="node_observed_as_of">2009-11-18</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E029"><data key="node_entity_id">R182_E029</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">2009 RECS Research-Only and Non-Adjudicative Use Restriction</data><data key="node_acronym" /><data key="node_domain">Person / Sensitive Statistical Data</data><data key="node_description">Voluntary race/ethnicity used for research and statistics rather than benefit entitlement; published aggregates non-identifiable.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-11-18</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E030"><data key="node_entity_id">R182_E030</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2007 SSNEC Original SSN Application Parental and Birth Attributes</data><data key="node_acronym" /><data key="node_domain">Person / Enumeration</data><data key="node_description">Original SSN application held names of parents and birthplace, alongside identity and application evidence.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E031"><data key="node_entity_id">R182_E031</data><data key="node_entity_type">control</data><data key="node_canonical_name">2007 SSNEC Suspect or Fraudulent Card Application Block</data><data key="node_acronym" /><data key="node_domain">Person / Enumeration Integrity</data><data key="node_description">Applications tied to suspicious or fraudulent documentation may be flagged to prevent new SSN-card processing.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E032"><data key="node_entity_id">R182_E032</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2007 SSNEC Multiple-SSN Person Cross References</data><data key="node_acronym" /><data key="node_domain">Person / Identity Reconciliation</data><data key="node_description">PIA says system may contain cross-references when more than one SSN was assigned to a person.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E033"><data key="node_entity_id">R182_E033</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2007 FALCON Processing Center Mass Manual Data Entry</data><data key="node_acronym" /><data key="node_domain">Payments / Manual Data Corrections</data><data key="node_description">Processing centers used modified commercial FALCON software to key batches of correction and payment-related inputs passed to other systems.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E034"><data key="node_entity_id">R182_E034</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2007 FALCON External Payment and Overpayment Correction Transactions</data><data key="node_acronym" /><data key="node_domain">Payments / Data Quality</data><data key="node_description">FALCON handled inputs affecting payment, overpayment, underpayment, nonreceipt, stopped or returned payment records in other SSA systems.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E035"><data key="node_entity_id">R182_E035</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2007 FALCON Historical Dormant Class-Action Correction Capability</data><data key="node_acronym" /><data key="node_domain">Administrative Legal Cases / Payments</data><data key="node_description">PIA reports FALCON could key corrections to SSA class-action claimant records but was not used for that purpose in recent years as of 2007.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2007-09-27</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E036"><data key="node_entity_id">R182_E036</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2018 QAS Sampled State and County of Residence Attribute</data><data key="node_acronym" /><data key="node_domain">Disability / Quality Sample Geography</data><data key="node_description">SSA QAS PIA identifies state and county residence information in copied review records; separate from authoritative address master.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2018-12-17</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E037"><data key="node_entity_id">R182_E037</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">2018 QAS Sampled Case Error Finding and Claimant Context</data><data key="node_acronym" /><data key="node_domain">Disability / Quality Review</data><data key="node_description">Quality review cases could include SSN, claim type, income/resources, medical data, errors, contacts, living arrangements and family group.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2018-12-17</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E038"><data key="node_entity_id">R182_E038</data><data key="node_entity_type">publication_collection</data><data key="node_canonical_name">2009 OASDI Trustees Annual Report Vintage</data><data key="node_acronym" /><data key="node_domain">Actuarial / Historical Publications</data><data key="node_description">2009 Trustees report is a dated set of assumptions, observed values and projections, not a live current forecast.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-05-12</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E039"><data key="node_entity_id">R182_E039</data><data key="node_entity_type">publication_product</data><data key="node_canonical_name">2009 OASDI Trustees Supplemental Single-Year Projection Tables</data><data key="node_acronym" /><data key="node_domain">Actuarial / Statistical Data Products</data><data key="node_description">Single-year actuarial supplement expands Trustees Report projections beyond five-year-increment printed tables.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-05-12</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R182_E040"><data key="node_entity_id">R182_E040</data><data key="node_entity_type">scenario_assumptions</data><data key="node_canonical_name">2009 Trustees Low-Cost Intermediate and High-Cost Economic Alternatives</data><data key="node_acronym" /><data key="node_domain">Actuarial / Forecast Governance</data><data key="node_description">Economic alternatives reflect the 2008-2009 recession as understood in May 2009 and should be keyed by report vintage.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-05-12</data><data key="node_confidence">5</data><data key="node_notes">Historical source scoped; not asserted as a current 2026 production component, physical interface, or live application.</data></node><node id="R183_E001"><data key="node_entity_id">R183_E001</data><data key="node_entity_type">historical_architecture</data><data key="node_canonical_name">2009 Eleven-System SSA Outgoing Exchange Architecture</data><data key="node_acronym" /><data key="node_domain">External Exchanges</data><data key="node_description">GAO identified 11 principal outgoing exchange applications serving 75 percent of 2009 outgoing agreements: six batch and five online.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E002"><data key="node_entity_id">R183_E002</data><data key="node_entity_type">historical_processing_pattern</data><data key="node_canonical_name">2009 SSA Six-Application Batch Exchange Group</data><data key="node_acronym" /><data key="node_domain">External Exchanges</data><data key="node_description">GAO identified six exchange applications that responded with consolidated batch files; the grouping is a 2009 observation.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E003"><data key="node_entity_id">R183_E003</data><data key="node_entity_type">historical_processing_pattern</data><data key="node_canonical_name">2009 SSA Five-Application Online Exchange Group</data><data key="node_acronym" /><data key="node_domain">External Exchanges</data><data key="node_description">GAO identified five exchange applications responding to requests in real time, using varied partner transmission mechanisms.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E004"><data key="node_entity_id">R183_E004</data><data key="node_entity_type">historical_service_variant</data><data key="node_canonical_name">Federal Online Query (FOLQ) Designation of SOLQ</data><data key="node_acronym" /><data key="node_domain">External Exchanges</data><data key="node_description">GAO uses FOLQ name for the federal partner variant of State Online Query; the application is a real-time counterpart of SVES.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E005"><data key="node_entity_id">R183_E005</data><data key="node_entity_type">historical_exchange_application</data><data key="node_canonical_name">2009 SSA Earnings System Partner Exchange Application</data><data key="node_acronym" /><data key="node_domain">Earnings</data><data key="node_description">GAO table lists an Earnings System batch application accessing MEF to support employer/federal/state earnings and SSN verification. Distinguish generic category from named current physical system.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">4</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E006"><data key="node_entity_id">R183_E006</data><data key="node_entity_type">service_level_requirement</data><data key="node_canonical_name">2009 AAMVA SSOLV Response-Time Exchange Performance Standard</data><data key="node_acronym" /><data key="node_domain">External Exchanges</data><data key="node_description">GAO reports agreement target: 95 percent of SSOLV requests within 3 seconds and 99 percent within 5 seconds. Historical contractual expectation, not measured result.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E007"><data key="node_entity_id">R183_E007</data><data key="node_entity_type">service_level_requirement</data><data key="node_canonical_name">2009 SSA-Veterans Benefits Exchange 99 Percent Accuracy Requirement</data><data key="node_acronym" /><data key="node_domain">External Exchanges</data><data key="node_description">GAO reports agreement requirement of 99 percent data accuracy for the Veterans Benefits Administration data exchange.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E008"><data key="node_entity_id">R183_E008</data><data key="node_entity_type">historical_statistical_dataset</data><data key="node_canonical_name">FY2007-FY2008 SSA Exchange Transaction Counts by Service</data><data key="node_acronym" /><data key="node_domain">Data/Publication Pipeline</data><data key="node_description">GAO table lists 1.19 billion requests in FY2007 and 1.37 billion in FY2008 across seven key exchange categories, with per-service counts.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E009"><data key="node_entity_id">R183_E009</data><data key="node_entity_type">historical_operational_measure</data><data key="node_canonical_name">January 2008-February 2009 Exchange Systems Incident Trend</data><data key="node_acronym" /><data key="node_domain">External Exchanges</data><data key="node_description">GAO identified about 35 recorded systems problems affecting outgoing exchanges in January 2008-February 2009; most were brief.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E010"><data key="node_entity_id">R183_E010</data><data key="node_entity_type">historical_it_service_management_system</data><data key="node_canonical_name">Change Asset and Problem Reporting System</data><data key="node_acronym" /><data key="node_domain">Infrastructure/ITSM</data><data key="node_description">GAO 2009 documents an agencywide system tracking IT problems, priorities, progress, resolution and validation for data exchanges.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E011"><data key="node_entity_id">R183_E011</data><data key="node_entity_type">historical_operations_component</data><data key="node_canonical_name">2009 SSA 24x7 Network Operations and Monitoring Centers</data><data key="node_acronym" /><data key="node_domain">Infrastructure/ITSM</data><data key="node_description">GAO reports around-the-clock network operations and monitoring centers for IT infrastructure and partner exchange performance.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E012"><data key="node_entity_id">R183_E012</data><data key="node_entity_type">historical_operations_process</data><data key="node_canonical_name">2009 SSA National Data-Exchange Systems Support Desk</data><data key="node_acronym" /><data key="node_domain">Infrastructure/ITSM</data><data key="node_description">GAO reports a national help desk to collect systems incidents and route them for investigation.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E013"><data key="node_entity_id">R183_E013</data><data key="node_entity_type">historical_recovery_action</data><data key="node_canonical_name">2009 SSOLV Backup Network Connection Recovery Example</data><data key="node_acronym" /><data key="node_domain">Infrastructure/ITSM</data><data key="node_description">GAO describes a historical AAMVA network failover action restoring service in 34 seconds. This is a single observed incident, not an SLA.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E014"><data key="node_entity_id">R183_E014</data><data key="node_entity_type">historical_proposed_data_store</data><data key="node_canonical_name">2009 Planned Dedicated E-Verify Verification Database</data><data key="node_acronym" /><data key="node_domain">Modernization</data><data key="node_description">GAO describes an SSA initiative to process E-Verify requests against a dedicated database with continuity and disaster recovery. Planned for August 2009, not verified as completed.</data><data key="node_observed_status">planned</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">4</data><data key="node_notes">The report describes intention; no evidence here establishes deployment or the data synchronization mechanism.</data></node><node id="R183_E015"><data key="node_entity_id">R183_E015</data><data key="node_entity_type">historical_proposed_service</data><data key="node_canonical_name">2009 Proposed Single-Registration Exchange Partner Web Portal</data><data key="node_acronym" /><data key="node_domain">Modernization</data><data key="node_description">SSA IT vision cited by GAO planned a menu-driven exchange portal with secure access and one partner registration process. No evidence of operational delivery.</data><data key="node_observed_status">proposed</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">4</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E016"><data key="node_entity_id">R183_E016</data><data key="node_entity_type">historical_oversight_finding</data><data key="node_canonical_name">2009 Outgoing Exchange Capacity and Target Architecture Gap</data><data key="node_acronym" /><data key="node_domain">Modernization</data><data key="node_description">GAO found lack of workload projections and exchange-specific future target architecture requirements.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009-09-16</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E017"><data key="node_entity_id">R183_E017</data><data key="node_entity_type">restricted_external_address_observation</data><data key="node_canonical_name">Debt Collections Credit-Bureau Address Retrieval</data><data key="node_acronym" /><data key="node_domain">Address Provenance</data><data key="node_description">Debt collectors may retrieve online address information from a credit bureau after returned SSA overpayment notices. Use governed by Fair Credit Reporting Act and SSA collection purpose.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-08-25</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E018"><data key="node_entity_id">R183_E018</data><data key="node_entity_type">historical_conditional_update_process</data><data key="node_canonical_name">Debt Collection Conditional Credit-Bureau-Triggered MBR/SSR Address Correction</data><data key="node_acronym" /><data key="node_domain">Address Provenance</data><data key="node_description">2008 SSA POMS directs employees to remail notice and update MBR/SSR and RECOOP if appropriate after a new credit-bureau address is found in skiptracing. Human action, not automatic feed.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-08-25</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E019"><data key="node_entity_id">R183_E019</data><data key="node_entity_type">historical_workflow_screen</data><data key="node_canonical_name">RECOOP Record Skip Trace (DBST) Screen</data><data key="node_acronym" /><data key="node_domain">Debt/Payments</data><data key="node_description">POMS requires a RECOOP skiptracing case to have actions recorded on the RECORD SKIP TRACE (DBST) screen.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-08-25</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E020"><data key="node_entity_id">R183_E020</data><data key="node_entity_type">historical_legal_access_control</data><data key="node_canonical_name">DMS Credit Report Access and PSC Audit Trail Control</data><data key="node_acronym" /><data key="node_domain">Program Integrity</data><data key="node_description">2008 POMS restricts program debt collection credit bureau queries to legitimate FCRA-permitted purposes and describes local PSC administrator audit reports.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2008-08-25</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E021"><data key="node_entity_id">R183_E021</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Bulgaria International Direct Deposit Country-Specific Bank-Coding Rule</data><data key="node_acronym" /><data key="node_domain">Payments/Debt</data><data key="node_description">2023 POMS: for Bulgaria, MBR uses a 19-character bank information representation and bank-data country code G; complete Bulgarian IBAN is 22 characters.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2023-10-18</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E022"><data key="node_entity_id">R183_E022</data><data key="node_entity_type">business_control</data><data key="node_canonical_name">Bulgaria IDD Same-Business-Day MBR and ITS.gov Entry Gate</data><data key="node_acronym" /><data key="node_domain">Payments/Debt</data><data key="node_description">2023 POMS requires staff to input applicable direct deposit changes in an SSA program system and ITS.gov during the same business day.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2023-10-18</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E023"><data key="node_entity_id">R183_E023</data><data key="node_entity_type">address_dependent_control</data><data key="node_canonical_name">Bulgaria IDD MBR Foreign Address PCOC-8 Preconditions</data><data key="node_acronym" /><data key="node_domain">Address Provenance</data><data key="node_description">MBR must reflect foreign address code PCOC=8 for Bulgaria international direct deposit to be accepted. Location code indicates routing eligibility, not an independently verified residence.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2023-10-18</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E024"><data key="node_entity_id">R183_E024</data><data key="node_entity_type">exception_control</data><data key="node_canonical_name">Bulgaria IDD Incomplete ITS.gov Payment Rejection</data><data key="node_acronym" /><data key="node_domain">Payments/Debt</data><data key="node_description">Inadequate data in ITS.gov can lead Federal Reserve Bank of Kansas City to reject payment and return funds to SSA.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2023-10-18</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E025"><data key="node_entity_id">R183_E025</data><data key="node_entity_type">research_data_governance</data><data key="node_canonical_name">HRS-SSA Restricted Administrative Earnings and Benefit Data Access Boundary</data><data key="node_acronym" /><data key="node_domain">Research/Data Governance</data><data key="node_description">Only authorized researchers can obtain restricted HRS linked SSA earnings and benefits records. Administrative linkage is person-level but disclosure governed by data permissions and access restrictions.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E026"><data key="node_entity_id">R183_E026</data><data key="node_entity_type">research_release_rule</data><data key="node_canonical_name">HRS-SSA Linked Earnings and Benefits Disclosure Masking</data><data key="node_acronym" /><data key="node_domain">Research/Data Governance</data><data key="node_description">SSA research note documents earnings/benefits fields rounded or top-coded in research products to reduce identifiability. This is publication transformation, not a master record change.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E027"><data key="node_entity_id">R183_E027</data><data key="node_entity_type">identity_matching_consent_control</data><data key="node_canonical_name">HRS Consent-Controlled SSA Earnings and Benefits Administrative Linkage</data><data key="node_acronym" /><data key="node_domain">Person/Identity Nexus</data><data key="node_description">2009 SSA research note establishes respondents are asked for consent to link SSA earnings/benefits records to longitudinal survey responses.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2009</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E028"><data key="node_entity_id">R183_E028</data><data key="node_entity_type">jurisdictional_access_rule</data><data key="node_canonical_name">HRS Administrative Linked Data United States Access Restriction</data><data key="node_acronym" /><data key="node_domain">Research/Data Governance</data><data key="node_description">University of Michigan restricted-data listing states linked SSA/CMS/NDI/VA administrative data may not be sent, shared, or accessed outside the United States.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E029"><data key="node_entity_id">R183_E029</data><data key="node_entity_type">vintage_specific_actuarial_output</data><data key="node_canonical_name">2014 Trustees Stochastic Reserve-Depletion Distribution</data><data key="node_acronym" /><data key="node_domain">Actuarial/Statistics</data><data key="node_description">2014 report stochastic 95 percent depletion range 2028-2041; median depletion year 2033. Scenario vintage cannot be compared to 2026 as actual financial events.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2014</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E030"><data key="node_entity_id">R183_E030</data><data key="node_entity_type">statistical_interpretation_rule</data><data key="node_canonical_name">2014 Trustees Stochastic Per-Year Percentile Interpretation Control</data><data key="node_acronym" /><data key="node_domain">Actuarial/Statistics</data><data key="node_description">2014 and subsequent actuarial stochastic year-specific percentile curves need not trace any single simulation across years.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2014</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E031"><data key="node_entity_id">R183_E031</data><data key="node_entity_type">procurement_policy</data><data key="node_canonical_name">SSA Acquisition 360 Voluntary Survey Solicitation Inclusion Rule</data><data key="node_acronym" /><data key="node_domain">Acquisition/Grants</data><data key="node_description">SSA OAG requires acquisition staff to include FAR 52.201-1 Acquisition 360 survey provision for IT solicitations above simplified acquisition threshold and non-IT solicitations estimated above $10m life value.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E032"><data key="node_entity_id">R183_E032</data><data key="node_entity_type">procurement_governance_notice</data><data key="node_canonical_name">SSA Medical Expert Services Bundling Necessity Determination</data><data key="node_acronym" /><data key="node_domain">Acquisition/Grants</data><data key="node_description">OAG publishes a Senior Procurement Executive determination for bundling Medical Expert Services under FAR 7.107-5(b)(1), without proving individual contract award or vendor selection.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E033"><data key="node_entity_id">R183_E033</data><data key="node_entity_type">contracting_organization</data><data key="node_canonical_name">SSA Office of Information Technology Acquisition</data><data key="node_acronym" /><data key="node_domain">Acquisition/Grants</data><data key="node_description">OAG public contact guidance routes IT goods and services correspondence to SSA Office of Information Technology Acquisition.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R183_E034"><data key="node_entity_id">R183_E034</data><data key="node_entity_type">contracting_organization</data><data key="node_canonical_name">SSA Office of Operations Contracts</data><data key="node_acronym" /><data key="node_domain">Acquisition/Grants</data><data key="node_description">OAG public contact guidance separately routes non-IT/facilities and operational acquisitions to operations contracting groups.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Source describes scoped operation or historical period; no unsupported claims of current deployment, transport, automated master-record updates, or persistence.</data></node><node id="R184_E001"><data key="node_entity_id">R184_E001</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Economic Recovery List Database (2009 ARRA Payment Eligibility)</data><data key="node_acronym">ERL</data><data key="node_domain">Cross-Program Identity and Payment Controls</data><data key="node_description">Historical ERL database held one-time American Recovery and Reinvestment Act payment eligibility and status linked by SSN across SSA, RRB and VBA, with IRS/Treasury limited-purpose outputs.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E002"><data key="node_entity_id">R184_E002</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">RRB Client Own SSN Economic Recovery Input File</data><data key="node_acronym">COSSN</data><data key="node_domain">Cross-Agency Exchange</data><data key="node_description">Historical Railroad Retirement Board client-own-SSN input used to check the Economic Recovery List before payment coordination.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E003"><data key="node_entity_id">R184_E003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2009 Economic Recovery Cross-Agency Eligibility Matching</data><data key="node_domain">Cross-Program Identity and Payment Controls</data><data key="node_description">One-to-one comparison of RRB/VBA eligibility submissions against the SSA Economic Recovery List to prevent duplicate statutory one-time payments.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E004"><data key="node_entity_id">R184_E004</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">2009 Economic Recovery Payment Reclamation Status</data><data key="node_domain">Payments and Debt</data><data key="node_description">Historical one-time stimulus benefit returned, reclaimed, nonreceipt and offset status maintained in the ERL context.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E005"><data key="node_entity_id">R184_E005</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">2009 Economic Recovery Deceased-Payee Estate Correspondence Address</data><data key="node_domain">Address Provenance</data><data key="node_description">Historical executor/estate representative mailing address and TIN used conditionally for ARRA payment reissuance, not verified current beneficiary residence.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E006"><data key="node_entity_id">R184_E006</data><data key="node_entity_type">data_exchange</data><data key="node_canonical_name">2009 Economic Recovery IRS Tax-Credit Verification Disclosure</data><data key="node_domain">IRS and SSA Exchange</data><data key="node_description">Limited SSA-to-IRS disclosure supporting Making Work Pay tax-credit processing; does not evidence incoming IRS address updates.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E007"><data key="node_entity_id">R184_E007</data><data key="node_entity_type">data_exchange</data><data key="node_canonical_name">2009 ERL Railroad Board Eligibility Response</data><data key="node_domain">Federal External Exchanges</data><data key="node_description">Eligibility response to RRB from SSA 2009 recovery list matching, used to coordinate one-time benefit duplication.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E008"><data key="node_entity_id">R184_E008</data><data key="node_entity_type">data_exchange</data><data key="node_canonical_name">2009 ERL Veterans Benefits Eligibility Response</data><data key="node_domain">Federal External Exchanges</data><data key="node_description">Eligibility response to VA Veterans Benefits Administration from SSA 2009 recovery list matching.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E009"><data key="node_entity_id">R184_E009</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">800-Number Service Observation Voice Recording Records (60-0362)</data><data key="node_domain">Telephone Service / Privacy</data><data key="node_description">2008 call-quality recordings of specified National 800 Number interactions, captured voice and metadata, under Service Observation Recordings SORN; automatic standard purge after 14 days.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E010"><data key="node_entity_id">R184_E010</data><data key="node_entity_type">application</data><data key="node_canonical_name">2008 Call Detail Management Information Report (60-0363)</data><data key="node_acronym">CDMIR</data><data key="node_domain">Telephone Service / Workforce Management</data><data key="node_description">Web-accessible historical report providing calling and called telephone numbers, date/time, ACD queue, duration, transfers and employee extension operational measurements; three-year record retention reported.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E011"><data key="node_entity_id">R184_E011</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">2008 Service Observation Database (60-0364)</data><data key="node_acronym">SODB</data><data key="node_domain">Telephone Service / Personnel Quality</data><data key="node_description">Historical physical database of sanitized service-observation staff evaluations and aggregates; three-year retention specified in 2008 notice.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E012"><data key="node_entity_id">R184_E012</data><data key="node_entity_type">data_feed</data><data key="node_canonical_name">2008 Automatic Call Distribution and VoIP Vendor Call Event Feed</data><data key="node_domain">Telephone Service / Network</data><data key="node_description">Historical operational telephony call-event and ACD feed to Call Detail report; source does not name commercial vendor.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E013"><data key="node_entity_id">R184_E013</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2008 800-Number Call Quality Observation Assessment Report</data><data key="node_domain">Telephone Service / Personnel Quality</data><data key="node_description">Sanitized service observer assessment compiled after selected 800-number calls; substantive personnel-related data may be retained separately.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E014"><data key="node_entity_id">R184_E014</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">2008 Unsatisfactory Call Observation Extended Retention</data><data key="node_domain">Telephone Service / Privacy</data><data key="node_description">Historical retention exception extended unsatisfactory recorded calls to 60 days rather than routine 14-day deletion.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E015"><data key="node_entity_id">R184_E015</data><data key="node_entity_type">records_collection</data><data key="node_canonical_name">Historical SF-7B Extension for Call-Service Personnel Actions</data><data key="node_acronym">SF-7B</data><data key="node_domain">Employee Records / Privacy</data><data key="node_description">Personnel case record could retain covered service observation recordings for two years after action closure or four years in EEO/litigation-related handling, per 2008 notice.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E016"><data key="node_entity_id">R184_E016</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">2008 Enterprise Telephone Automatic Call Distributor Event Dataset</data><data key="node_domain">Telephone Service / Network</data><data key="node_description">Call origin/called number, call time, hold, transfer and skill group routing metadata from 800-number network; caller phone is not verified identity or residential address.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E017"><data key="node_entity_id">R184_E017</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Abt Associates BOND Implementation Contractor</data><data key="node_domain">Vendors / Contracts</data><data key="node_description">SSA-described outside contractor managing Benefit Offset National Demonstration operations and BOND Operations Data System, historical 2011-2024.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">POMS confirms project ended; do not classify vendor as current deployment.</data></node><node id="R184_E018"><data key="node_entity_id">R184_E018</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Convergys Government Solutions BOND Contact-Center Subcontractor</data><data key="node_domain">Vendors / Contracts</data><data key="node_description">Historical BOND outsourced contact-center subcontractor supporting Abt Associates and participant services.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E019"><data key="node_entity_id">R184_E019</data><data key="node_entity_type">application</data><data key="node_canonical_name">BOND Processing Center PTT Loader</data><data key="node_domain">Title II Payments / BOND</data><data key="node_description">Historical Processing Time Tracker (PTT) loader relayed BSAS processing-limitation alerts into PCACS; POMS does not establish platform, DB or hosting.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R184_E020"><data key="node_entity_id">R184_E020</data><data key="node_entity_type">data_feed</data><data key="node_canonical_name">BOND Daily Earnings Estimate Update Batch</data><data key="node_domain">Title II Payments / BOND</data><data key="node_description">Historical nightly batch update of participants earnings estimates from BODS through BOND services to BSAS; estimated income not verified posted MEF wages.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E021"><data key="node_entity_id">R184_E021</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">BOND Annual Estimated-versus-Actual Earnings Reconciliation</data><data key="node_domain">Disability Work Incentives</data><data key="node_description">Historical annual calculation comparing BSAS participant estimates with actual prior-year MEF postings, generally around August; may result in overpayment or underpayment.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E022"><data key="node_entity_id">R184_E022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">BOND Title II Benefit Offset Posting Transaction</data><data key="node_domain">Title II Payments / BOND</data><data key="node_description">Historical BSAS automated MADCAP offset posting updated MBR DEMO fields; PCACS processing exceptions required OCO manual MACADE action. Applicable only while BOND was in operation.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E023"><data key="node_entity_id">R184_E023</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">BOND Contractor-Origin Participation Notice Outside ORS</data><data key="node_domain">Claims Notices / BOND</data><data key="node_description">Historical BOND enrollment/start and end correspondence handled by demonstration contractor rather than SSA ORS; do not assume archived in ORS.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E024"><data key="node_entity_id">R184_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">BOND Demonstration-Site Assignment and Foreign-Residence Control</data><data key="node_domain">BOND / Address Provenance</data><data key="node_description">Historical demonstration site residence qualification and foreign residence extended travel limit; program assignment is not an authoritative current residential address.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E025"><data key="node_entity_id">R184_E025</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">2008 SUMS/MCAS Staff Session and Office Assignment Metadata</data><data key="node_domain">Management Information / Privacy</data><data key="node_description">Historical SUMS/MCAS MI captures employee PIN, office/work unit, login and time allocation; not beneficiary identity-authority data.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E026"><data key="node_entity_id">R184_E026</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">2008 SUMS/MCAS Service Visitor Location and Correspondence Attributes</data><data key="node_domain">Management Information / Address Provenance</data><data key="node_description">Workload MI with selected claimant/visitor address data for management statistics; does not prove a write to MBR, SSR, Numident.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E027"><data key="node_entity_id">R184_E027</data><data key="node_entity_type">contract_award</data><data key="node_canonical_name">SSA AAMVA Task Order 28321323FDS030015</data><data key="node_domain">Procurement</data><data key="node_description">OAG historical SSA task order under 28321320D00060003 with American Association of Motor Vehicle Administrators; listed October 26 2022 and $1,170,772.</data><data key="node_observed_status">historical_award</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E028"><data key="node_entity_id">R184_E028</data><data key="node_entity_type">contract_award</data><data key="node_canonical_name">SSA AAMVA Task Order 28321324FDS030009</data><data key="node_domain">Procurement</data><data key="node_description">OAG historical SSA AAMVA task order 28321324FDS030009 issued October 23 2023, listing $250,000; does not establish a particular interface scope.</data><data key="node_observed_status">historical_award</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E029"><data key="node_entity_id">R184_E029</data><data key="node_entity_type">statistical_product</data><data key="node_canonical_name">2016 SSDI Annual Statistical Report Publication Vintage</data><data key="node_domain">Disability Statistics / Publications</data><data key="node_description">SSA public 2016 publication vintage; historical reported counts and later corrections must retain source-date provenance.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E030"><data key="node_entity_id">R184_E030</data><data key="node_entity_type">publication_change</data><data key="node_canonical_name">2016 SSDI Annual Statistical Report Table 8 Correction History</data><data key="node_domain">Disability Statistics / Publications</data><data key="node_description">Historical published corrections to annual SSDI Table 8; users should retain publication and update dates instead of overwriting initial snapshot silently.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R184_E031"><data key="node_entity_id">R184_E031</data><data key="node_entity_type">architecture_constraint</data><data key="node_canonical_name">2017 VRRMS Independent Record Processing Boundary</data><data key="node_domain">Disability Evidence / Systems</data><data key="node_description">2017 disability management PIA specifically reports VRRMS did not directly connect to SSA systems from which related source information was obtained.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R185_E001"><data key="node_entity_id">R185_E001</data><data key="node_entity_type">historical_data_asset</data><data key="node_canonical_name">EAMATE Historical Annual Tape Employer Earnings Records</data><data key="node_acronym">EAMATE</data><data key="node_domain">earnings</data><data key="node_description">Historical employer annual earnings detail that had a microfilm representation, and was also accessible through named online query paths.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2022-01-14</data><data key="node_confidence">5</data><data key="node_notes">SSA explicitly states EAMATE years 1978–2000 are no longer held on microfilm; do not infer loss of online records.</data></node><node id="R185_E002"><data key="node_entity_id">R185_E002</data><data key="node_entity_type">application</data><data key="node_canonical_name">EAMATE Online Retrieval</data><data key="node_acronym">EAMATE Online</data><data key="node_domain">earnings</data><data key="node_description">EAMATE electronic retrieval route named in SSA earnings discrepancy development instructions.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2022-01-14</data><data key="node_confidence">5</data><data key="node_notes">No hosting, database technology or current deployment claimed.</data></node><node id="R185_E003"><data key="node_entity_id">R185_E003</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Annual Wage Report Scrambled-Earnings Address Lead</data><data key="node_acronym">AWR address</data><data key="node_domain">address_provenance</data><data key="node_description">Address available in AWR/annual employer report evidence used to locate a worker in an earnings-discrepancy case.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2022-01-14</data><data key="node_confidence">5</data><data key="node_notes">Contact/locator lead only, not authoritative SSA residential address; age and location uncertainty.</data></node><node id="R185_E004"><data key="node_entity_id">R185_E004</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Earnings Discrepancy Case File Latest Address</data><data key="node_acronym">ED case address</data><data key="node_domain">address_provenance</data><data key="node_description">Most current address in the discrepancy case material, given precedence over historical report lead for mailing closeout letters.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2021-11-08</data><data key="node_confidence">5</data><data key="node_notes">Case-file observation may still be stale; no Numident/MBR/SSR update established.</data></node><node id="R185_E005"><data key="node_entity_id">R185_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Scrambled-Earnings Closeout Address Selection Rule</data><data key="node_acronym">ED address rule</data><data key="node_domain">address_provenance</data><data key="node_description">For closeout correspondence, use case-file current address if available; otherwise historical AWR or EAMATE sources; if absent, annotate no address and retain notice in ED folder.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2021-11-08</data><data key="node_confidence">5</data><data key="node_notes">Does not assert automatic update of program-record addresses.</data></node><node id="R185_E006"><data key="node_entity_id">R185_E006</data><data key="node_entity_type">historical_data_asset</data><data key="node_canonical_name">EAMATE 1978–2000 Microfilm Copies No Longer Stored</data><data key="node_acronym">EAMATE microfilm</data><data key="node_domain">earnings</data><data key="node_description">Microfilm of processed EAMATE information for tax years 1978 through 2000; published policy says SSA no longer stores this microfilm.</data><data key="node_observed_status">not_stored_at_observation</data><data key="node_observed_as_of">2022-01-14</data><data key="node_confidence">5</data><data key="node_notes">Electronic access may still exist through EAMATE online/GIR/PCOM, and later status not asserted.</data></node><node id="R185_E007"><data key="node_entity_id">R185_E007</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-5533 U4 Earnings Discrepancy Development Request</data><data key="node_acronym">SSA-5533 U4</data><data key="node_domain">earnings</data><data key="node_description">Form referenced for additional written earnings discrepancy development when telephone contacts cannot resolve evidence gaps.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2022-01-14</data><data key="node_confidence">5</data><data key="node_notes">No claim about current form edition.</data></node><node id="R185_E008"><data key="node_entity_id">R185_E008</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">OCO Earnings Discrepancy Re-Development Workflow</data><data key="node_acronym">ED redevelopment</data><data key="node_domain">earnings</data><data key="node_description">Reopening field-office development when previously available relevant address or evidence was not investigated or multiple FO conclusions conflict.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2022-01-14</data><data key="node_confidence">5</data><data key="node_notes">Employee-controlled workflow with employer contact subject to number-holder permission.</data></node><node id="R185_E009"><data key="node_entity_id">R185_E009</data><data key="node_entity_type">data_asset</data><data key="node_canonical_name">Scrambled Earnings Discrepancy Special Holding File</data><data key="node_acronym">ED holding file</data><data key="node_domain">earnings</data><data key="node_description">Holding file for rechecking subsequent postings to a potentially misused original SSN after October of next calendar year.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2021-11-08</data><data key="node_confidence">5</data><data key="node_notes">Physical/electronic form unspecified.</data></node><node id="R185_E010"><data key="node_entity_id">R185_E010</data><data key="node_entity_type">historical_data_asset</data><data key="node_canonical_name">OCO 1086 Pre-1978 Earnings Microfilm</data><data key="node_acronym">1086 microfilm</data><data key="node_domain">earnings</data><data key="node_description">Historical earnings-detail microfilm for 1937 through 1977, consulted by OCO feedback procedure.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2011-09-01</data><data key="node_confidence">5</data><data key="node_notes">Do not infer retention in October 2026.</data></node><node id="R185_E011"><data key="node_entity_id">R185_E011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">OCO Pre-1978 Earnings Feedback</data><data key="node_acronym">earnings feedback</data><data key="node_domain">earnings</data><data key="node_description">Checks historical 1086 earnings detail and posts validated located earnings to MEF for pre-1978 wage periods.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2011-09-01</data><data key="node_confidence">5</data><data key="node_notes">Different from later-year employer report scouting.</data></node><node id="R185_E012"><data key="node_entity_id">R185_E012</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">OCO Employer Wage Report Scouting</data><data key="node_acronym">wage scouting</data><data key="node_domain">earnings</data><data key="node_description">Searches employer wage reports across online and microfilmed sources, including pre-1978 Form 941 report files and post-1977 ERQY/AWR/EAMATE records.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2011-09-01</data><data key="node_confidence">5</data><data key="node_notes">Do not treat employer address as employee residence.</data></node><node id="R185_E013"><data key="node_entity_id">R185_E013</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Earnings Adjustment Rationale Screen</data><data key="node_acronym">EART</data><data key="node_domain">earnings</data><data key="node_description">ICOR screen used to document special determinations or relevant circumstances underlying corrected earnings.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2011-09-01</data><data key="node_confidence">5</data><data key="node_notes">Screens referenced by POMS, no storage engine established.</data></node><node id="R185_E014"><data key="node_entity_id">R185_E014</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">ICOR Evidence Basis Documentation Without Retaining Copies</data><data key="node_acronym">ICOR basis-only evidence</data><data key="node_domain">earnings</data><data key="node_description">POMS instructs not to retain copies of evidence used to correct an earnings record, but to document the evidence basis in ICOR.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2011-09-01</data><data key="node_confidence">5</data><data key="node_notes">Applies to the cited wage-development process; other evidence-retention rules may differ.</data></node><node id="R185_E015"><data key="node_entity_id">R185_E015</data><data key="node_entity_type">historical_data_asset</data><data key="node_canonical_name">Pre-1978 Employer Quarterly Form 941 Wage Report File</data><data key="node_acronym">941 pre-1978 wage file</data><data key="node_domain">earnings</data><data key="node_description">Pre-1978 employer quarterly records consulted in wage scouting.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2011-09-01</data><data key="node_confidence">5</data><data key="node_notes">Not proof of current file availability.</data></node><node id="R185_E016"><data key="node_entity_id">R185_E016</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRS Form 3857 Post Office Address Development</data><data key="node_acronym">3857 postal development</data><data key="node_domain">identity</data><data key="node_description">SSA Form SSA-L2001 requests post-office address leads for taxpayers involved in IRS Form 3857 scrambled-earnings identity resolution.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-06-13</data><data key="node_confidence">5</data><data key="node_notes">USPS response is a locating lead, not a program master-record update.</data></node><node id="R185_E017"><data key="node_entity_id">R185_E017</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">IRS Form 3857 Numident Cross-Reference Removal After Proof</data><data key="node_acronym">3857 crossref cleanup</data><data key="node_domain">identity</data><data key="node_description">After adequate taxpayer and employer evidence, SSA corrects applicable earnings and removes incorrect Numident cross-references.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-06-13</data><data key="node_confidence">5</data><data key="node_notes">Manual conditional correction; neither IRS-origin address nor auto correction established.</data></node><node id="R185_E018"><data key="node_entity_id">R185_E018</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">IRS Form 3857 Postal Address Investigation Lead</data><data key="node_acronym">3857 post-office address</data><data key="node_domain">address_provenance</data><data key="node_description">Postal response from SSA-L2001 in taxpayer identity and earnings discrepancy investigation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-06-13</data><data key="node_confidence">4</data><data key="node_notes">Actual response content and persistence not described; no automatic master-record update.</data></node><node id="R185_E019"><data key="node_entity_id">R185_E019</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Scrambled Wages Proof of Identity Prerequisite</data><data key="node_acronym">scramble proof gate</data><data key="node_domain">identity</data><data key="node_description">SSA requires identity evidence before correcting scrambled earnings and may use original SS-5 microprints and contemporaneous employer records.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2023-10-11</data><data key="node_confidence">5</data><data key="node_notes">No universal physical person repository inferred.</data></node><node id="R185_E020"><data key="node_entity_id">R185_E020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Scrambled Earnings Move-to-Suspense Rather Than Delete</data><data key="node_acronym">scrambled suspense rule</data><data key="node_domain">earnings</data><data key="node_description">When earnings ownership cannot be established, move wages to suspense rather than deleting wage information.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2023-10-11</data><data key="node_confidence">5</data><data key="node_notes">Does not imply current W-2 address retained on MEF.</data></node><node id="R185_E021"><data key="node_entity_id">R185_E021</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">Latest W-2 Worker Address as Scrambled-Earnings Location Lead</data><data key="node_acronym">latest W-2 address</data><data key="node_domain">address_provenance</data><data key="node_description">An employer-issued W-2 address may help locate an individual misusing an SSN in a scrambled-wages investigation.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2023-10-11</data><data key="node_confidence">5</data><data key="node_notes">Not verified residence; employment and mailing address may differ.</data></node><node id="R185_E022"><data key="node_entity_id">R185_E022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2026 WLM Limited-Rollout Initial Claims Cohort</data><data key="node_acronym">WLM 2026 cohort</data><data key="node_domain">modernization</data><data key="node_description">Limited rollout of WLM/ASC phone initial-claim appointment distribution across named states and American Samoa effective August 29 2026.</data><data key="node_observed_status">limited_rollout</data><data key="node_observed_as_of">2026-08-29</data><data key="node_confidence">4</data><data key="node_notes">SOURCE CONFLICT: Purpose lists 12 jurisdictions while operative workflow lists 14 including Nevada and Tennessee; do not generalize nationwide.</data></node><node id="R185_E023"><data key="node_entity_id">R185_E023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">WLM Claim-Taking Office Retains Case Beyond Geographic Jurisdiction</data><data key="node_acronym">Keep What You Take</data><data key="node_domain">workload</data><data key="node_description">In expanded rollout, office taking initial claim keeps ownership to adjudication even when claimant resides outside its normal jurisdiction.</data><data key="node_observed_status">limited_rollout</data><data key="node_observed_as_of">2026-08-29</data><data key="node_confidence">5</data><data key="node_notes">Applies only to enrolled cohort; not a statewide universal operating assumption.</data></node><node id="R185_E024"><data key="node_entity_id">R185_E024</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">WLM Source Cohort Territory Inconsistency August 2026</data><data key="node_acronym">WLM cohort conflict</data><data key="node_domain">modernization</data><data key="node_description">EM-26017 REV says 12 jurisdictions in section A but 14 in operational sections B/D, adding NV and TN; classification withheld for these two pending later corroboration.</data><data key="node_observed_status">unresolved_conflict</data><data key="node_observed_as_of">2026-08-26</data><data key="node_confidence">5</data><data key="node_notes">Intentional conflict preservation, not silent reconciliation.</data></node><node id="R185_E025"><data key="node_entity_id">R185_E025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Field Office WorkTrack Disability Hearing Evidence Manual eView Forwarding</data><data key="node_acronym">WT-to-eView manual</data><data key="node_domain">disability_evidence</data><data key="node_description">FO technician or manager manually transfers inbound DDS/hearings documents received in WorkTrack to eView when no FO action required.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-02-25</data><data key="node_confidence">5</data><data key="node_notes">Emergency message retention date 2026-08-23; current 2026-10 procedure not independently confirmed.</data></node><node id="R185_E026"><data key="node_entity_id">R185_E026</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">WorkTrack Disability Evidence Form Type and Image Quality Review</data><data key="node_acronym">WT evidence profile QA</data><data key="node_domain">disability_evidence</data><data key="node_description">FO staff verify case location, submitted form type and image quality before eView transfer; correct profile as needed.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-02-25</data><data key="node_confidence">5</data><data key="node_notes">Manual role; avoid inference of automated DDS/eView integration.</data></node><node id="R185_E027"><data key="node_entity_id">R185_E027</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">WorkTrack Manual Document Disposition via NDRED eView or Paperless</data><data key="node_acronym">WT disposition paths</data><data key="node_domain">disability_evidence</data><data key="node_description">WorkTrack marks document processing complete upon disposition through documented destination repository or status action.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-02-25</data><data key="node_confidence">5</data><data key="node_notes">Original/certified evidence rules remain independent.</data></node><node id="R185_E028"><data key="node_entity_id">R185_E028</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Notices Telephone Process Input File (2021)</data><data key="node_acronym">SSI phone notice file</data><data key="node_domain">ssi_notice</data><data key="node_description">SSI Notices subsystem generates a separate file for a telephone call process along with beneficiary notices.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">No voice system, protocol or retention inferred.</data></node><node id="R185_E029"><data key="node_entity_id">R185_E029</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Payment Web Certification Reports (2021)</data><data key="node_acronym">SSI certification report</data><data key="node_domain">ssi_payments</data><data key="node_description">SSI PAYMT creates balancing, verification and certification reports for certification analysts and a Payment Web Certification Tool.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Payment certification reporting, not the actual Treasury disbursement.</data></node><node id="R185_E030"><data key="node_entity_id">R185_E030</data><data key="node_entity_type">application</data><data key="node_canonical_name">Payment Web Certification Tool</data><data key="node_acronym">Payment Web Certification</data><data key="node_domain">ssi_payments</data><data key="node_description">Tool named as recipient of PAYMT certification reports in SSIRMS 2021 PIA.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Underlying implementation and current deployment not established.</data></node><node id="R185_E031"><data key="node_entity_id">R185_E031</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSIRMS Daily Edits Rejected Transaction FO Routing</data><data key="node_acronym">IC/PE rejection routing</data><data key="node_domain">ssi</data><data key="node_description">SSI Daily Edits separates rejected initial-claim/post-eligibility transactions and routes them to field offices for review.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Reject does not automatically alter SSR; exception handling required.</data></node><node id="R185_E032"><data key="node_entity_id">R185_E032</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Financial Verification Certification Exception Reports</data><data key="node_acronym">SSI certification exception</data><data key="node_domain">ssi_payments</data><data key="node_description">Treasury-origin payment exception reports generated for analysts by SSI Financial Verification system.</data><data key="node_observed_status">historical_observation</data><data key="node_observed_as_of">2021-03-25</data><data key="node_confidence">5</data><data key="node_notes">Certification exception reports, not evidence of payments recorded to SSR.</data></node><node id="R186_E001"><data key="node_entity_id">R186_E001</data><data key="node_entity_type">external_lookup_service</data><data key="node_canonical_name">DOJ EOIR Automated Case Information System (ACIS) Website</data><data key="node_acronym">ACIS</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">SSA POMS directs an EOIR status verification through the DOJ EOIR ACIS website; this is a verification lookup, not an SSA-master-record update.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Specific to EOIR evidence in SSI deemed-qualified-alien cases. Storage/transport/retention of ACIS information not specified in cited POMS.</data></node><node id="R186_E002"><data key="node_entity_id">R186_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI EOIR ACIS Immigration Order Verification Workflow</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">SSA verifies claimant EOIR documentation using the EOIR Automated Case Information System and scans EOIR evidence to the Evidence Portal.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">POMS SI 00502.116 F.4.b; verification does not by itself establish SSI eligibility.</data></node><node id="R186_E003"><data key="node_entity_id">R186_E003</data><data key="node_entity_type">evidence_asset</data><data key="node_canonical_name">EOIR Immigration Order Documentary Evidence in SSI Electronic Folder</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">SSA scans EOIR documentation into the Evidence Portal and returns originals to the claimant as part of status determination.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Specific to lawful presence/qualifying status. Do not infer that SSA operates EOIR ACIS.</data></node><node id="R186_E004"><data key="node_entity_id">R186_E004</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Deemed Qualified Alien Battery Eligibility Determination</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">Process for SSI eligibility based on battery/extreme cruelty, subject to immigration verification and separate-residence evidence where applicable.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">A legal eligibility decision; not a physical person record.</data></node><node id="R186_E005"><data key="node_entity_id">R186_E005</data><data key="node_entity_type">program_data_rule</data><data key="node_canonical_name">MSSICS Deemed Qualified Alien Z and Battery Petition Y Coding</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">MSSICS initial SSI award coding uses ALIEN STATUS Z and BATTERY PETITION FILED Y for verified deemed-qualified-alien status.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E006"><data key="node_entity_id">R186_E006</data><data key="node_entity_type">program_data_rule</data><data key="node_canonical_name">SSR Deemed Qualified Alien AR and AQ Exception Coding</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">Outside MSSICS, SSA documents deemed-qualified-alien coding on SSR citizenship/alien AR field and an appropriate AQ exception category.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E007"><data key="node_entity_id">R186_E007</data><data key="node_entity_type">cross_system_rule</data><data key="node_canonical_name">SSI Battery Eligibility MSSICS-versus-SSR Coding Divergence</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">SSA expressly says battery-based SSI eligibility is coded differently on SSR and in MSSICS until further system changes.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not assume identical representation or automatic propagation of status fields.</data></node><node id="R186_E008"><data key="node_entity_id">R186_E008</data><data key="node_entity_type">evidence_domain</data><data key="node_canonical_name">SSI Battery Noncohabitation Residence Evidence</data><data key="node_acronym" /><data key="node_domain">Address Provenance</data><data key="node_description">Documents establishing that battered applicant no longer shares a residence with the abusive person may include court protection orders, work records, utilities, school, rental, shelter, and third-party signed statements.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">These are multiple independently developed provenance sources, not an automatically synchronized current address.</data></node><node id="R186_E009"><data key="node_entity_id">R186_E009</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Battery Changed-Residence 30-Day Development Diary</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">When applicant lives with the batterer, SSA develops proof of separate residence, allows 30 days, and diaries the claim; lack of proof may cause denial.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">This is a conditional adjudicative follow-up, not the SSR 5B IRS alert diary.</data></node><node id="R186_E010"><data key="node_entity_id">R186_E010</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Battery-Based Alien Status AT Diary</data><data key="node_acronym">AT</data><data key="node_domain">Title XVI</data><data key="node_description">SSA creates an AT diary on SSI alien records whose eligibility rests on battery/extreme cruelty conditions.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E011"><data key="node_entity_id">R186_E011</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Battery Prima-Facie Status 150-Day Review Diary</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">SSA diaries prima facie immigration eligibility records for 150 days from determination before reviewing approved petition or changed status.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E012"><data key="node_entity_id">R186_E012</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Battery Status Annual DHS Reverification Diary</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">After favorable petition processing, SSA diaries status annually and re-verifies relevant documents via SAVE until permanent residence is granted.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E013"><data key="node_entity_id">R186_E013</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Battery Alien-Status Loss PR-9 and SSA-1719B Suspension Workflow</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">When battered-alien status or exception is lost, SSA codes AR via PR-9, documents SSR remarks, and sends an N13 1719B transaction; POMS notes a MSSICS limitation.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">POMS technical instructions specify procedure; not evidence of fully automated status updates from DHS.</data></node><node id="R186_E014"><data key="node_entity_id">R186_E014</data><data key="node_entity_type">data_mapping_rule</data><data key="node_canonical_name">SSI IRS Government-Security Interest Payer-EIN Classification Table</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">IRS special-situations policy maps government interest alerts by listed EIN to securities categories including Treasury bills, bonds and notes, savings bonds, and retirement bonds.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">EINs are payer identifiers, not beneficiary SSNs or residential addresses.</data></node><node id="R186_E015"><data key="node_entity_id">R186_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Bureau of Fiscal Service Securities Verification Via Parallel Field Office</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">For questioned federal securities, SSA uses an SSA-562-UF through a designated parallel field office to seek Fiscal Service verification, not direct contact.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Appropriate notice/consent and IRS alert copy with unrelated transactions obscured are required.</data></node><node id="R186_E016"><data key="node_entity_id">R186_E016</data><data key="node_entity_type">disclosure_control</data><data key="node_canonical_name">SSI Treasury Securities SSA-8510 Consent and IRS-Alert Redaction Gate</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">Fiscal Service security verification request includes a signed SSA-8510 and redacted IRS alert. If representative payee signs, special authority language is added.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not infer a generic unrestricted IRS or Treasury information-sharing permission.</data></node><node id="R186_E017"><data key="node_entity_id">R186_E017</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Agricultural Subsidy IRS Alert County-Office Locator Workflow</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">When a recipient denies agricultural subsidy or farm ownership, SSA uses payer-account information and parallel FO 736 to identify appropriate USDA Farm Service Agency county office for verification.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Farm county is a business verification lead, not claimant residential address; unrelated alert data redacted.</data></node><node id="R186_E018"><data key="node_entity_id">R186_E018</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI IRS Tax-Refund Interest Receipt Allegation Rule</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">An IRS payer entry on an interest alert denotes tax-refund interest; POMS directs SSA to ask the recipient for receipt evidence and otherwise accept the date allegation rather than contacting IRS.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E019"><data key="node_entity_id">R186_E019</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">CMS Monthly SSI Medicare Buy-In Accretion Informational Alert</data><data key="node_acronym" /><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">CMS sends participating alert States a monthly informational record identifying SSI recipients potentially eligible for Medicare buy-in accretion.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Informational alert only; an SSA change to Numident/MBR/SSR is not asserted.</data></node><node id="R186_E020"><data key="node_entity_id">R186_E020</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">CMS Monthly SSI Medicare Buy-In Deletion Informational Alert</data><data key="node_acronym" /><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">CMS sends a monthly potential buy-in deletion alert to participating States when system is notified SSI terminated and beneficiary is still on buy-in.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E021"><data key="node_entity_id">R186_E021</data><data key="node_entity_type">data_mapping_rule</data><data key="node_canonical_name">CMS State Buy-In HIM Multi-Field Identity Matching Key</data><data key="node_acronym" /><data key="node_domain">Person/Identity Nexus</data><data key="node_description">Before State accretion to Third-Party Master, record must match HIM on Medicare claim number/BIC plus partial surname, given name, sex and date of birth fields.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">A program-specific matching gate; not evidence of a universal Person physical repository.</data></node><node id="R186_E022"><data key="node_entity_id">R186_E022</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">CMS State Buy-In Action Acknowledgment-Reject-Interim Response Set</data><data key="node_acronym" /><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">CMS Third-Party System returns accepted, rejected with reason, or interim responses to state accretion/deletion requests; interim may require later monthly resolution.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Paper response may substitute for electronic final disposition in exceptions.</data></node><node id="R186_E023"><data key="node_entity_id">R186_E023</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">CMS Medicare Buy-In Accretion Date Entitlement Floor Rule</data><data key="node_acronym" /><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">Third-Party System adjusts state buy-in accretion effective date forward to Medicare entitlement date when state-submitted date precedes entitlement.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E024"><data key="node_entity_id">R186_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">CMS State Buy-In Retroactive Deletion Two-Month Limit</data><data key="node_acronym" /><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">Historical 1972 Commissioners Decision limits deletions to two months retroactive from month buy-in system receives deletion action; POMS revised July 2026.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Rule originated prior to 20-year search window; included because current authoritative POMS describes processing rule.</data></node><node id="R186_E025"><data key="node_entity_id">R186_E025</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">SSA-to-CMS Monthly Medicare Buy-In Death Deletion Record</data><data key="node_acronym" /><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">If SSA receives death information for someone on buy-in, SSA sends a monthly death deletion record to CMS; CMS updates state billing notice.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">This is a documented downstream buy-in deletion, not evidence of death update to Numident from this process.</data></node><node id="R186_E026"><data key="node_entity_id">R186_E026</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">SSA-to-CMS Monthly Medicare Eligibility Loss Deletion Record</data><data key="node_acronym" /><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">SSA sends monthly Medicare-loss deletion actions to CMS when beneficiary loses Medicare eligibility for specified reasons such as disability entitlement cessation.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E027"><data key="node_entity_id">R186_E027</data><data key="node_entity_type">document_data_product</data><data key="node_canonical_name">SSA-1696-APP Electronic Appointment Intake Image</data><data key="node_acronym" /><data key="node_domain">Representative and Hearings</data><data key="node_description">A signed electronic SSA-1696 produces an SSA-1696-APP image received by the servicing field office through WorkTrack for technician processing.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No claim that e1696 portal itself makes an authoritative eRPS appointment without technician review.</data></node><node id="R186_E028"><data key="node_entity_id">R186_E028</data><data key="node_entity_type">service_limit_rule</data><data key="node_canonical_name">2025 TNEV Ten-SSN Maximum Speech Verification Batch</data><data key="node_acronym" /><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">SSA February 2025 PIA says automated telephone employer verification allows employers/authorized third parties to verify at most ten employee SSNs per call.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Design described in 2025 PIA; deployment in 2026 is not independently verified by PIA alone.</data></node><node id="R186_E029"><data key="node_entity_id">R186_E029</data><data key="node_entity_type">authentication_control</data><data key="node_canonical_name">2025 TNEV Single-Attempt IRES Spoken-Credential Gate</data><data key="node_acronym" /><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">TNEV PIA requires speech input of IRES user ID and password with a single authentication attempt before EIN and worker SSN verification.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">PIA describes proposed/defined service, not an asserted ongoing ability in 2026.</data></node><node id="R186_E030"><data key="node_entity_id">R186_E030</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">WEIA Representative-Payee Versus Legal-Guardian Authority Rule</data><data key="node_acronym" /><data key="node_domain">Person/Identity Nexus</data><data key="node_description">A representative payee alone cannot provide wage and employment information authorization for a competent claimant; parent or legal guardian status supplies authority for minor or legally incompetent person.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Explicit legal capacity rule; representative-payee appointment is not equivalent to legal guardianship.</data></node><node id="R186_E031"><data key="node_entity_id">R186_E031</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">WEIA Concurrent Title II and Title XVI Separate Grant Requirement</data><data key="node_acronym" /><data key="node_domain">Person/Identity Nexus</data><data key="node_description">Concurrent SSDI/SSI applicants and recipients must supply program-specific wage information authorization for each program; one program grant does not cover the other.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E032"><data key="node_entity_id">R186_E032</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">WEIA Written Revocation Propagates to Both Programs</data><data key="node_acronym" /><data key="node_domain">Person/Identity Nexus</data><data key="node_description">A signed or attested written WEIA revocation applies to any active Title II and Title XVI authorizations after SSA processes the revocation, without affecting benefit eligibility.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Separate initial grants, but a revocation must be applied to both programs where active.</data></node><node id="R186_E033"><data key="node_entity_id">R186_E033</data><data key="node_entity_type">authorization_workflow</data><data key="node_canonical_name">SSA-8240 Non-SSI-Claims-System Paper-Form Intake and EP Retention</data><data key="node_acronym" /><data key="node_domain">Earnings</data><data key="node_description">For non-SSI Claims system cases, SSA obtains paper SSA-8240, uploads it to Evidence Portal, then records authorization in WEIA application if case later enters the SSI Claims system.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">PIE wages must not be mistaken for authorization by generic third-party SSA-8510 or medical SSA-827.</data></node><node id="R186_E034"><data key="node_entity_id">R186_E034</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">SSA-8510 Wet-Signature Third-Party Information Authorization Gate</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">SSA POMS SI 00601.100 states that SSA-8510 is not attestable and requires a wet signature for third-party evidence; medical SSA-827, wage SSA-8240 and bank SSA-4641 have separate authorization rules.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E035"><data key="node_entity_id">R186_E035</data><data key="node_entity_type">adjudication_control</data><data key="node_canonical_name">DDS Reconsideration De Novo Independent Reviewer Requirement</data><data key="node_acronym" /><data key="node_domain">Disability and Evidence</data><data key="node_description">SSA POMS DI 27001.010 requires a new review by DE/MC/PC other than reviewers at initial disability determination, based on complete old and new evidence.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Different reviewing staff, not an independent physical repository.</data></node><node id="R186_E036"><data key="node_entity_id">R186_E036</data><data key="node_entity_type">development_workflow</data><data key="node_canonical_name">DDS Reconsideration Previously Unresponsive Medical Source Recontact</data><data key="node_acronym" /><data key="node_domain">Disability and Evidence</data><data key="node_description">DDS reconsideration must request evidence from sources missed, unresponsive or not fully developed at initial determination, and develop medical changes after initial determination.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E037"><data key="node_entity_id">R186_E037</data><data key="node_entity_type">evidence_lineage_rule</data><data key="node_canonical_name">DDS Reconsideration Prior Folder Evidence Reuse and Copy Rule</data><data key="node_acronym" /><data key="node_domain">Disability and Evidence</data><data key="node_description">At reconsideration, DDS reviews all available previous paper and electronic disability folders and copies relevant evidence into current folder, maintaining historical claim context.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Copying into current case is not automatic correction of earlier evidence.</data></node><node id="R186_E038"><data key="node_entity_id">R186_E038</data><data key="node_entity_type">development_workflow</data><data key="node_canonical_name">DDS Reconsideration Changed Function Report to DCPS-DDE Documentation</data><data key="node_acronym" /><data key="node_domain">Disability and Evidence</data><data key="node_description">Changed functional allegations at reconsideration require an updated SSA-3373-BK or a documented case note in DCPS written through to DDE; unchanged function does not require another report.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R186_E039"><data key="node_entity_id">R186_E039</data><data key="node_entity_type">evidence_development_rule</data><data key="node_canonical_name">SSI Good-Faith Evidence Development Case-by-Case Extension Rule</data><data key="node_acronym" /><data key="node_domain">Title XVI</data><data key="node_description">SSA POMS SI 00601.100 permits reasonable evidence deadlines extensions within 30-day increments for special circumstances; claimant good-faith and SSA assistance drive appropriate decisions.</data><data key="node_observed_status">documented_as_of_source</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0001"><data key="node_entity_id">R187_E0001</data><data key="node_entity_type">application_component</data><data key="node_canonical_name">SSOARS iStore Procurement Component</data><data key="node_domain">Finance / Accounting</data><data key="node_description">The FY2024 and FY2025 SSA financial reports name iStore as part of SSOARS, an Oracle Federal Financials-based accounting environment.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0002"><data key="node_entity_id">R187_E0002</data><data key="node_entity_type">authentication_service</data><data key="node_canonical_name">SSOARS Service Single Sign-On</data><data key="node_domain">Finance / Identity</data><data key="node_description">SSA identifies a single-sign-on component of SSOARS, with a multifactor-authentication-compliant invoice-approval sign-on implementation/reimplementation reported in 2024 and 2025.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0003"><data key="node_entity_id">R187_E0003</data><data key="node_entity_type">authentication_control</data><data key="node_canonical_name">SSOARS Invoice Approval MFA Single Sign-On Control</data><data key="node_domain">Finance / Cybersecurity</data><data key="node_description">SSOARS invoice-approval users have an SSA-reported MFA-compliant single-sign-on control that was reimplemented during FY2025.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0004"><data key="node_entity_id">R187_E0004</data><data key="node_entity_type">reporting_application</data><data key="node_canonical_name">SSOARS WebFOCUS Reporting Replacement</data><data key="node_domain">Finance / Reporting</data><data key="node_description">FY2024 SSA financial report states WebFOCUS was implemented as a reporting replacement for business intelligence publication and portal tools.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-09-30</data><data key="node_confidence">5</data><data key="node_notes">FY2024 implementation; precise FY2026 live state not independently verified.</data></node><node id="R187_E0005"><data key="node_entity_id">R187_E0005</data><data key="node_entity_type">application_component</data><data key="node_canonical_name">SSOARS Business Intelligence Publisher</data><data key="node_domain">Finance / Reporting</data><data key="node_description">Former SSOARS business-intelligence reporting component; FY2024 SSA report described a planned retirement following WebFOCUS deployment.</data><data key="node_observed_status">historical_retirement_planned</data><data key="node_observed_as_of">2024-09-30</data><data key="node_confidence">5</data><data key="node_notes">Do not assert the planned December 2024 retirement actually occurred.</data></node><node id="R187_E0006"><data key="node_entity_id">R187_E0006</data><data key="node_entity_type">application_component</data><data key="node_canonical_name">SSOARS WebCenter Reporting Portal</data><data key="node_domain">Finance / Reporting</data><data key="node_description">Former SSOARS reporting/portal component; planned retirement was discussed after WebFOCUS implementation in FY2024.</data><data key="node_observed_status">historical_retirement_planned</data><data key="node_observed_as_of">2024-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0007"><data key="node_entity_id">R187_E0007</data><data key="node_entity_type">application_component</data><data key="node_canonical_name">SSOARS Preventive Controls Governor Legacy Software</data><data key="node_domain">Finance / Internal Control</data><data key="node_description">FY2025 financial report says unsupported commercial-off-the-shelf Preventive Controls Governor software was replaced by SSA-developed custom configurations for validations.</data><data key="node_observed_status">replacement_reported_fy2025</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0008"><data key="node_entity_id">R187_E0008</data><data key="node_entity_type">application_component</data><data key="node_canonical_name">SSOARS Custom Financial Form and Field Validations</data><data key="node_domain">Finance / Internal Control</data><data key="node_description">SSA FY2025 reports agency-developed custom configurations replacing unsupported preventive-control software for form and field changes and validations.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0009"><data key="node_entity_id">R187_E0009</data><data key="node_entity_type">application_component</data><data key="node_canonical_name">SSOARS General Ledger Upload Replacement</data><data key="node_domain">Finance / Accounting</data><data key="node_description">FY2025 SSA reports implementing a general-ledger upload solution to replace Oracle technology dependent on ActiveX.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0010"><data key="node_entity_id">R187_E0010</data><data key="node_entity_type">legacy_application_component</data><data key="node_canonical_name">SSOARS Former ActiveX-Dependent General Ledger Upload</data><data key="node_domain">Finance / Accounting</data><data key="node_description">An earlier Oracle-technology general-ledger upload process depended on ActiveX and was replaced in FY2025 according to SSA financial reporting.</data><data key="node_observed_status">superseded_fy2025</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0011"><data key="node_entity_id">R187_E0011</data><data key="node_entity_type">data_standard</data><data key="node_canonical_name">Governmentwide Spending Data Model Version 1.0.1</data><data key="node_domain">Finance / Procurement Data</data><data key="node_description">SSA FY2024 report identifies the Governmentwide Spending Data Model (GSDM) v1.0.1 for DATA Act spending reporting.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0012"><data key="node_entity_id">R187_E0012</data><data key="node_entity_type">data_quality_control</data><data key="node_canonical_name">SSA DATA Act Submission Data Quality Plan</data><data key="node_domain">Finance / Publication</data><data key="node_description">SSA reports maintaining a quality plan with internal controls over input and validation of federal spending submissions to USAspending.gov.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0013"><data key="node_entity_id">R187_E0013</data><data key="node_entity_type">procurement_data_product</data><data key="node_canonical_name">SSA FY2023 Unlinked Federal Award Submission Population</data><data key="node_domain">Procurement / Open Data</data><data key="node_description">SSA FY2024 financial report reports 484 unlinked contract and financial-assistance awards in FY2023; 93 percent were zero-dollar or micropurchase awards. The data may change between federal spending submissions.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2023-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0014"><data key="node_entity_id">R187_E0014</data><data key="node_entity_type">procurement_data_product</data><data key="node_canonical_name">SSA FY2024 Unlinked Federal Award Submission Population</data><data key="node_domain">Procurement / Open Data</data><data key="node_description">SSA FY2024 financial report reports 669 unlinked contract and financial-assistance awards; 95 percent were zero-dollar or micropurchase awards. These are externally unlinked USAspending records, not proof of unrecorded federal obligations.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0015"><data key="node_entity_id">R187_E0015</data><data key="node_entity_type">procurement_data_product</data><data key="node_canonical_name">SSA FY2025 Unlinked Federal Award Submission Population</data><data key="node_domain">Procurement / Open Data</data><data key="node_description">SSA FY2025 financial report identifies 2,512 unlinked award records in FY2025 federal spending submissions; 98 percent were zero-dollar or micropurchase awards, which link internally but not externally on USAspending.gov.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0016"><data key="node_entity_id">R187_E0016</data><data key="node_entity_type">data_quality_constraint</data><data key="node_canonical_name">USAspending Internal-Only Award Linkage Caveat</data><data key="node_domain">Procurement / Geographic Analytics</data><data key="node_description">FY2025 SSA report cautions that certain zero-dollar and micropurchase award records are linkable inside SSA systems but not externally on USAspending.gov and counts change with resubmission.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0017"><data key="node_entity_id">R187_E0017</data><data key="node_entity_type">financial_reporting_control</data><data key="node_canonical_name">SSA Treasury Account Symbol Obligation Reporting Reconciliation</data><data key="node_domain">Finance / Publication</data><data key="node_description">SSA states DATA Act reporting covers every Treasury Account Symbol since second quarter FY2017 and had no obligation reporting difference by FY2025.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0018"><data key="node_entity_id">R187_E0018</data><data key="node_entity_type">data_governance</data><data key="node_canonical_name">SSA Analytics and Improvements Data Inventory Component</data><data key="node_domain">Enterprise / Asset Inventory</data><data key="node_description">FY2025 SSA financial report states the agency established an Analytics and Improvements component to centralize authority for data inventory, using existing tools such as Enterprise Data Catalog with full implementation targeted for January 2026.</data><data key="node_observed_status">established_full_implementation_planned_2026_01</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes">No independent confirmation of target completion by October 2026.</data></node><node id="R187_E0019"><data key="node_entity_id">R187_E0019</data><data key="node_entity_type">data_catalog</data><data key="node_canonical_name">SSA FY2025 Enterprise Data Catalog Inventory Capability</data><data key="node_domain">Enterprise / Data Governance</data><data key="node_description">SSA FY2025 financial report names Enterprise Data Catalog as an existing tool to support centralized data inventories; the report does not identify product vendor or establish a particular integration with a separately cataloged Informatica platform.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes">Vendor/product correspondence to other Atlas entries is unresolved and therefore not asserted.</data></node><node id="R187_E0020"><data key="node_entity_id">R187_E0020</data><data key="node_entity_type">modernization_project</data><data key="node_canonical_name">SSA Centralized Governance Risk and Compliance Platform Transition</data><data key="node_domain">Cybersecurity / Governance</data><data key="node_description">FY2025 financial report describes transition to a new centralized governance, risk and compliance platform to consolidate asset inventories; product, completion, and hosting are not named.</data><data key="node_observed_status">in_transition_fy2025</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0021"><data key="node_entity_id">R187_E0021</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">SSA Enterprise Logging Level 1 Asset Onboarding</data><data key="node_domain">Cybersecurity / Logging</data><data key="node_description">SSA FY2025 says the majority of initial enterprise logging Level 1 asset onboardings were completed under OMB M-21-31.</data><data key="node_observed_status">majority_onboarded_fy2025</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0022"><data key="node_entity_id">R187_E0022</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">SSA Enterprise Logging Level 2 System Onboarding</data><data key="node_domain">Cybersecurity / Logging</data><data key="node_description">SSA FY2025 says it was actively onboarding qualifying information systems to the higher Level 2 logging standard; no total completion attested.</data><data key="node_observed_status">ongoing_fy2025</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0023"><data key="node_entity_id">R187_E0023</data><data key="node_entity_type">audit_finding</data><data key="node_canonical_name">SSA FY2025 FISMA Audit Overall Not Effective Assessment</data><data key="node_domain">Cybersecurity / Oversight</data><data key="node_description">SSA FY2025 AFR reports EY assessed its overall FY2025 FISMA program Not Effective; incident response program separately received Effective rating.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0024"><data key="node_entity_id">R187_E0024</data><data key="node_entity_type">audit_finding</data><data key="node_canonical_name">SSA FY2025 FISMA Incident Response Effective Assessment</data><data key="node_domain">Cybersecurity / Oversight</data><data key="node_description">SSA FY2025 reports EY assessed the incident response domain Effective while overall program was Not Effective.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0025"><data key="node_entity_id">R187_E0025</data><data key="node_entity_type">security_process</data><data key="node_canonical_name">SSOARS CISA Known Exploited Vulnerability Patching Workflow</data><data key="node_domain">Finance / Cybersecurity</data><data key="node_description">FY2025 SSA reports monitoring and patching multiple CISA Known Exploited Vulnerabilities in SSOARS, without naming specific CVEs.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0026"><data key="node_entity_id">R187_E0026</data><data key="node_entity_type">external_identifier</data><data key="node_canonical_name">IRS Individual Taxpayer Identification Number in SSA Earnings Discrepancy Reviews</data><data key="node_domain">Identity / Earnings</data><data key="node_description">POMS RS 01404.254 states an IRS-issued ITIN may be the nine-digit number a person used for employment; that fact alone does not prove intentional fraud or alter the assigned Numident SSN.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0027"><data key="node_entity_id">R187_E0027</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Public Access to Court Electronic Records Federal Court Query</data><data key="node_domain">Federal Judiciary / Verification</data><data key="node_description">SSA regional counsel is directed by POMS to query PACER for federal convictions associated with use of another person’s SSN in a specific Title II claim review.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0028"><data key="node_entity_id">R187_E0028</data><data key="node_entity_type">business_role</data><data key="node_canonical_name">SSA Regional Office Center for Program Support Ensign Referral Role</data><data key="node_domain">SSA / Regional Operations</data><data key="node_description">Regional Center for Program Support receives Title II cross-SSN earnings referrals from field offices, routes them to regional counsel, and relays dispositions to the initiating field office.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0029"><data key="node_entity_id">R187_E0029</data><data key="node_entity_type">business_role</data><data key="node_canonical_name">SSA Regional Counsel Ensign Conviction Review Role</data><data key="node_domain">SSA / Legal</data><data key="node_description">Regional general counsel office queries PACER to assess federal conviction information for Title II Ensign Amendment questions; results returned via CPS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0030"><data key="node_entity_id">R187_E0030</data><data key="node_entity_type">claims_processing_workflow</data><data key="node_canonical_name">Title II Ensign Amendment Cross-SSN Work and Conviction Review</data><data key="node_domain">Title II / Earnings Identity</data><data key="node_description">Documented Title II procedure when insured status is missing and claimant reports work under a different SSN, or when a pertinent federal criminal proceeding is reported; routing is FO to CPS to regional counsel and back.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0031"><data key="node_entity_id">R187_E0031</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Ensign Amendment Fifteen-Day Listing Code 425 Followup Diary</data><data key="node_domain">Title II / Regional Review</data><data key="node_description">POMS requires the field office to diary Ensign referrals for 15 days using listing code 425 and follow up if CPS has not responded.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0032"><data key="node_entity_id">R187_E0032</data><data key="node_entity_type">source_address_attribute</data><data key="node_canonical_name">Ensign Cross-SSN Referral Names and Addresses Used</data><data key="node_domain">Person / Address Provenance</data><data key="node_description">For Ensign regional referral, field office transmits the claimant address of record plus other names and addresses used. These are investigation/referral attributes, not independently verified current residence or master-record updates.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0033"><data key="node_entity_id">R187_E0033</data><data key="node_entity_type">program_integrity_control</data><data key="node_canonical_name">Ensign SSN Knowing Intent Fraud Referral Threshold</data><data key="node_domain">SSA OIG / Fraud Referrals</data><data key="node_description">SSA policy requires knowledge and intent in referral analysis; use of another SSN or IRS-issued ITIN alone is not sufficient to conclude fraud, with all-zero employer placeholder treated as an exception.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-03-20</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0034"><data key="node_entity_id">R187_E0034</data><data key="node_entity_type">administrative_database</data><data key="node_canonical_name">SSA Religious Exemption Unit Form 4029 Database</data><data key="node_domain">Identity / Tax Exemptions</data><data key="node_description">POMS RM 04906.001 documents the Religious Exemption database for retaining and updating IRS Form 4029 exemption-request statuses and related processing records.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2022-12-29</data><data key="node_confidence">5</data><data key="node_notes">Database physical implementation, hosting, retention, and current deployment not specified.</data></node><node id="R187_E0035"><data key="node_entity_id">R187_E0035</data><data key="node_entity_type">reference_database</data><data key="node_canonical_name">Form 1458 Religious Group Lookup Database</data><data key="node_domain">Identity / Tax Exemptions</data><data key="node_description">SSA religious-exemption technicians consult Form 1458 religious-group lookup database and update representative contact details upon signed authorized notice.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2022-12-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0036"><data key="node_entity_id">R187_E0036</data><data key="node_entity_type">external_business_process</data><data key="node_canonical_name">IRS Ministers Waiver Unit Form 4029 Approval Channel</data><data key="node_domain">IRS / Tax Exemptions</data><data key="node_description">IRS Ministers Waiver Unit returns signed approval/denial status for religious exemption IRS Form 4029 and processes certain authorized third-party requests.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2022-12-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0037"><data key="node_entity_id">R187_E0037</data><data key="node_entity_type">identity_attribute</data><data key="node_canonical_name">Numident Q/FICA Religious Tax Exemption Indicator</data><data key="node_domain">Numident / Identity Status</data><data key="node_description">SSA POMS states an approved IRS Form 4029 supports placing Q/FICA waiver indicator on Numident, with SSA staff keying information through ESCORR and reconciling absent indicators.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2022-12-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0038"><data key="node_entity_id">R187_E0038</data><data key="node_entity_type">source_address_attribute</data><data key="node_canonical_name">Religious Exemption Requester Mailing Address for Authentication</data><data key="node_domain">Identity / Address Provenance</data><data key="node_description">SSA POMS permits requesting a current mailing address when authenticating a person requesting a copy/status of IRS Form 4029; not proof of a master residence attribute.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2022-12-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0039"><data key="node_entity_id">R187_E0039</data><data key="node_entity_type">communication_channel</data><data key="node_canonical_name">SSA eMailer Supplemental Evidence Request Channel</data><data key="node_domain">Title XVI / Evidence Development</data><data key="node_description">SSI POMS permits eMailer as supplemental way to request proof or communicate about evidence, but it does not replace statutory mailed SSI notices.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-04-24</data><data key="node_confidence">5</data><data key="node_notes">Product architecture unspecified by POMS; do not presume delivery automation or system integration.</data></node><node id="R187_E0040"><data key="node_entity_id">R187_E0040</data><data key="node_entity_type">notice_business_rule</data><data key="node_canonical_name">SSI N20 Followup Mailed-Notice Requirement</data><data key="node_domain">Title XVI / Notices</data><data key="node_description">Under SSA SSI whereabouts-unknown procedures, mandatory written notices remain mailed even where eMailer may supplement proof requests; direct recipient and payee addresses may differ.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-04-24</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0041"><data key="node_entity_id">R187_E0041</data><data key="node_entity_type">document_retention_rule</data><data key="node_canonical_name">SSI N20 Notice ORS Electronic Copy and Retention</data><data key="node_domain">Title XVI / Notice History</data><data key="node_description">DPS, SSTNG, and other compatible notice generation systems can retain electronic copies through ORS; manually generated notices may require separate electronic document routing. No blanket equivalence of media or retention periods asserted.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-04-24</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0042"><data key="node_entity_id">R187_E0042</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">USPS SSI Returned-Mail Forwarding Address as Investigative Lead</data><data key="node_domain">Title XVI / Address Development</data><data key="node_description">Where undeliverable SSI mail carries a forwarding-address indication, SSA policy calls for further notice/address development, not an automatic SSR update.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-04-24</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0043"><data key="node_entity_id">R187_E0043</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI N20 Unlocated Recipient Followup Timeline</data><data key="node_domain">Title XVI / Notices</data><data key="node_description">Policy includes initial 30-day recipient contact, subsequent 15-day contact and 10-day followup stages for relevant SSI N20 development; steps depend on notice type and responses.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2025-04-24</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0044"><data key="node_entity_id">R187_E0044</data><data key="node_entity_type">data_retention_observation</data><data key="node_canonical_name">SSI IRS Interface Most-Recent-Two-Years Match Data Window</data><data key="node_domain">Title XVI / IRS Interface</data><data key="node_description">SSA POMS SI 02310.045 states its SSI/IRS alert database contains the most recent two years of IRS matching data. This is a rolling data availability observation, not a legal system-wide retention schedule.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2017-01-25</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0045"><data key="node_entity_id">R187_E0045</data><data key="node_entity_type">workload_schedule</data><data key="node_canonical_name">SSI IRS Five-B Diary Scheduled October February June Releases</data><data key="node_domain">Title XVI / Redeterminations</data><data key="node_description">POMS SI 02305.017 (July 2026) specifies 5B IRS-interface diary workload releases in October, February and June, distinct from IRS raw data updates.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-07-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R187_E0046"><data key="node_entity_id">R187_E0046</data><data key="node_entity_type">operational_data_store</data><data key="node_canonical_name">SSI Post-Entitlement Operational Data Store for Pension Alert Review</data><data key="node_domain">Title XVI / IRS Pension Interface</data><data key="node_description">SSI POMS SI 02310.052 instructs technicians to use the Post Entitlement Operational Data Store to identify records carrying 5H pension alert diary before determining which person the data concern.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2017-01-25</data><data key="node_confidence">5</data><data key="node_notes">POMS names PE ODS. Exact storage, retention and physical platform unspecified.</data></node><node id="R187_E0047"><data key="node_entity_id">R187_E0047</data><data key="node_entity_type">income_matching_rule</data><data key="node_canonical_name">SSI 1099-R Pension Five-H Diary Amount Comparison Rule</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">SSA compares IRS 1099-R pension SSN/amount against SSR unearned income; threshold includes at least $12 difference for eligible pre-January claimants, or absent relevant SSR entries for later eligibility.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2017-01-25</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0001"><data key="node_entity_id">R188_E0001</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">IRS-Origin W-2 W-2c and Schedule SE Tax-Form Address for ORES Geography</data><data key="node_acronym">Tax-form address</data><data key="node_domain">Person / Address Provenance / Earnings</data><data key="node_description">Full address as reported on employer or self-employment tax forms; OEIS extracts it in a separate research process to assign geographic codes, not to certify a current beneficiary residence.</data><data key="node_observed_status">historical_research_input_documented</data><data key="node_observed_as_of">2022-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0002"><data key="node_entity_id">R188_E0002</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">OEIS Separate Tax-Form Address Extraction for ORES and OACT</data><data key="node_acronym">OEIS address extract</data><data key="node_domain">Earnings / OACT / Research</data><data key="node_description">Office of Enterprise Information Systems extracts address information from Forms W-2, W-2c and Schedule SE separately from the programmatic annual wage-reporting process.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2022-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0003"><data key="node_entity_id">R188_E0003</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Pitney Bowes Finalist Worker State-County Coding Software in OEIS Research Processing</data><data key="node_acronym">Finalist</data><data key="node_domain">Address / Historical Technology</data><data key="node_description">SSA researchers document use of Pitney Bowes Finalist to generate state-and-county residence codes from addresses in federal tax forms in OEIS processing. No claim about 2026 use or vendor contract.</data><data key="node_observed_status">historical_documented_use</data><data key="node_observed_as_of">2022-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0004"><data key="node_entity_id">R188_E0004</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">MGD Job-Level State and County Code Derived from Tax Form Address</data><data key="node_acronym">job-level SCC</data><data key="node_domain">Earnings / Research / Geographic Coding</data><data key="node_description">State/county code generated at job and tax-form record level before assigning one geographic code to a worker SSN.</data><data key="node_observed_status">historical_research_intermediate</data><data key="node_observed_as_of">2022-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0005"><data key="node_entity_id">R188_E0005</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">MGD Historical Tape File of Tax-Form Geographic Coding Results</data><data key="node_acronym">MGD code tape</data><data key="node_domain">Earnings / Research / Historical Storage</data><data key="node_description">2022 SSA research documents geographic coding outputs extracted into tape files during the original MGD pipeline; storage applies to that historical research design only.</data><data key="node_observed_status">historical_only</data><data key="node_observed_as_of">2022-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0006"><data key="node_entity_id">R188_E0006</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">MGD Tax-Year One-State-County-Code-Per-Worker Selection</data><data key="node_acronym">MGD one SCC selection</data><data key="node_domain">Earnings / Research / Geographic Coding</data><data key="node_description">Process collapses one or more job-level state/county codes into a single code for each SSN within the primary tax-year MGD file.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2022-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0007"><data key="node_entity_id">R188_E0007</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">MGD Gold-Standard Single-Code Worker Records</data><data key="node_acronym">MGD gold-standard</data><data key="node_domain">Earnings / Research / Geographic Coding</data><data key="node_description">Worker records with exactly one county/state code from the OEIS/Finalist extraction; these require no ambiguous geographic assignment.</data><data key="node_observed_status">historical_research_intermediate</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0008"><data key="node_entity_id">R188_E0008</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">MGD ZIP-Code Frequency Imputation for Missing Worker County</data><data key="node_acronym">MGD county imputation</data><data key="node_domain">Earnings / Research / Data Quality</data><data key="node_description">When an SCC is unavailable, uses frequency distribution of known SCCs in gold-standard records sharing ZIP codes to impute county/state; ambiguous multi-code cases use additional defined selection steps.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0009"><data key="node_entity_id">R188_E0009</data><data key="node_entity_type">administrative_extract</data><data key="node_canonical_name">MGD Numident Worker Demographic and SSN Validation Enrichment</data><data key="node_acronym">MGD Numident enrichment</data><data key="node_domain">Person / Identity Nexus / Research</data><data key="node_description">For each SSN, the research process checks presence in Numident and adds sex, date of birth, death, and date the death was posted; absent SSNs are marked invalid and demographics missing.</data><data key="node_observed_status">historical_research_data</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0010"><data key="node_entity_id">R188_E0010</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Master Geographic and Demographic Standalone Tax-Year Research File</data><data key="node_acronym">MGD</data><data key="node_domain">Earnings / Statistical Data Production</data><data key="node_description">One standalone MGD file per primary tax year assembled from tax-form geographic codes and Numident demographics. The 2024 report describes files for tax years 2014–2020, with the subsequent SSA research note documenting 2021.</data><data key="node_observed_status">historical_observed_research_files</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes">Separate from MEF. Historical 2014-2021 research vintages, not an operational address master.</data></node><node id="R188_E0011"><data key="node_entity_id">R188_E0011</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">MGD Thirty-Two-Report Annual Data Processing Audit Package</data><data key="node_acronym">MGD audit reports</data><data key="node_domain">Earnings / Statistical Data Production / Data Quality</data><data key="node_description">The historical MGD process produces 32 reports per year tracking tax input volume, valid SSNs, source forms, coding, demographic coverage and imputations.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0012"><data key="node_entity_id">R188_E0012</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MGD State-and-County Assignment Method Provenance Field</data><data key="node_acronym">SCC method</data><data key="node_domain">Address / Statistical Provenance</data><data key="node_description">MGD output field records how the statistical geography was assigned rather than treating every state/county code as observed directly.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0013"><data key="node_entity_id">R188_E0013</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">MGD Primary Tax-Year-Plus-One Processing-Year Inclusion Rule</data><data key="node_acronym">MGD y+1</data><data key="node_domain">Earnings / Statistical Data Quality</data><data key="node_description">Original MGD builds include primary-tax-year forms processed in the immediately following calendar year; later or earlier processing may be excluded.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0014"><data key="node_entity_id">R188_E0014</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">MGD Late-Filed Tax Form Address Temporal Reliability Caveat</data><data key="node_acronym">tax-form address lag</data><data key="node_domain">Address / Research / Data Quality</data><data key="node_description">Late-reported tax forms may reflect an address from a time other than the analysis year, complicating a residence inference; no SSA master address write is documented.</data><data key="node_observed_status">historical_analytical_limitation</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0015"><data key="node_entity_id">R188_E0015</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">MGD Unmatched Numident SSN Not Necessarily Programmatically Validated</data><data key="node_acronym">MGD invalid SSN</data><data key="node_domain">Person / Identity Nexus / Data Quality</data><data key="node_description">Research file can include SSNs not found in Numident because raw tax-form extraction is distinct from programmatic MEF cleaning and validation; no correction procedure established in this file.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0016"><data key="node_entity_id">R188_E0016</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">MGD Preliminary 2014–2021 Worker Geography and Earnings-Type Counts</data><data key="node_acronym">MGD preliminary</data><data key="node_domain">Research / Public Statistics</data><data key="node_description">SSA 2024 research note provides preliminary worker counts by age, sex, state, and earnings-type categories using 2014–2021 MGD files; it does not establish final official replacement of county earnings publication.</data><data key="node_observed_status">research_preliminary</data><data key="node_observed_as_of">2024</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0017"><data key="node_entity_id">R188_E0017</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MGD Standard FIPS State-County Geographic Code</data><data key="node_acronym">MGD FIPS SCC</data><data key="node_domain">Publications / Geographic Codes</data><data key="node_description">Statistical county codes conforming to standard FIPS classification in the new research process, rather than historical undocumented SSA assignment codes.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2022-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0018"><data key="node_entity_id">R188_E0018</data><data key="node_entity_type">historical_research_sample</data><data key="node_canonical_name">Ten-Percent CWHS Plus All High Earners Statistical Research Sample</data><data key="node_acronym">10-CWHS-HE</data><data key="node_domain">Earnings / Research / Sample</data><data key="node_description">SSA 2022 research describes building a worker sample with 10-percent CWHS frame plus everyone whose earnings exceeded Social Security taxable maximum in any year from 1978 onward, as an intended publication-sample enhancement.</data><data key="node_observed_status">historical_research_development_not_proven_replacement</data><data key="node_observed_as_of">2022-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0019"><data key="node_entity_id">R188_E0019</data><data key="node_entity_type">modernization_plan</data><data key="node_canonical_name">ORES Planned Geographic and Demographic Earnings Publication Upgrade Using MGD</data><data key="node_acronym">MGD publication upgrade</data><data key="node_domain">Publications / Earnings Statistics</data><data key="node_description">2022/2024 SSA research discusses planned linkage of MGD geographic indicators with larger MEF-based earnings sample for county tables and lower suppression; implementation of full production replacement is not established.</data><data key="node_observed_status">historical_plan_only</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">4</data><data key="node_notes">Current 2026 publication algorithm remains unverified.</data></node><node id="R188_E0020"><data key="node_entity_id">R188_E0020</data><data key="node_entity_type">data_quality_rule</data><data key="node_canonical_name">MGD Geographic Output Does Not Contain Taxable Earnings Amounts</data><data key="node_acronym">MGD no earnings</data><data key="node_domain">Earnings / Statistical Data Quality</data><data key="node_description">MGD output alone cannot establish covered or taxable earnings amounts; separate MEF or sample earnings information is necessary for estimated taxable wages.</data><data key="node_observed_status">historically_documented</data><data key="node_observed_as_of">2024-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0021"><data key="node_entity_id">R188_E0021</data><data key="node_entity_type">research_database</data><data key="node_canonical_name">Disability Analysis Support Hub Longitudinal Research Database</data><data key="node_acronym">DASH</data><data key="node_domain">Disability / Research / Appeals</data><data key="node_description">Daily-refreshed longitudinal research database assembled by SSA research office from multiple electronic disability processing and decisional systems; covers initial, reconsideration, hearings and appellate case records.</data><data key="node_observed_status">historical_2022_observation</data><data key="node_observed_as_of">2022-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0022"><data key="node_entity_id">R188_E0022</data><data key="node_entity_type">research_dataset</data><data key="node_canonical_name">Time Reference for Management Information Disability Temporal Dataset</data><data key="node_acronym">MTIME</data><data key="node_domain">Disability / Research / Time</data><data key="node_description">SSA research temporal data set supporting processing-time and survival-period calculations for SSI recipients and DI beneficiaries; used with DASH in 2022 research.</data><data key="node_observed_status">historical_2022_observation</data><data key="node_observed_as_of">2022-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0023"><data key="node_entity_id">R188_E0023</data><data key="node_entity_type">statistical_process</data><data key="node_canonical_name">DASH and MTIME Research Join for Disability Case Analysis</data><data key="node_acronym">DASH-MTIME join</data><data key="node_domain">Disability / Statistical Analysis</data><data key="node_description">Research process combines longitudinal case data from DASH with MTIME dates for QDD cohort analyses.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2022-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0024"><data key="node_entity_id">R188_E0024</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">DASH Case-Level Consolidation of Multiple Disability Claim Records</data><data key="node_acronym">DASH research case</data><data key="node_domain">Disability / Person / Claims</data><data key="node_description">The note distinguishes claims (single application records) from research cases that merge an individual's multiple records into a single case file.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2022-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0025"><data key="node_entity_id">R188_E0025</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">DASH Quick Disability Determination Flag and DDS Receipt Research Population</data><data key="node_acronym">DASH QDD cohort</data><data key="node_domain">Disability / DDS / Statistical</data><data key="node_description">DASH supported analysis of disability determination receipts, flagged and unflagged QDD cases, and applicant survival status for fiscal years 2015–2020.</data><data key="node_observed_status">historical_research_data</data><data key="node_observed_as_of">2022-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0026"><data key="node_entity_id">R188_E0026</data><data key="node_entity_type">statistical_definition</data><data key="node_canonical_name">MTIME Nonstandard Fiscal-Year Boundary (Last Friday September)</data><data key="node_acronym">MTIME fiscal-year</data><data key="node_domain">Disability / Statistics / Time</data><data key="node_description">The 2022 research note defines MTIME fiscal year from last Friday of September to next last Friday, unlike the federal fiscal-year month boundary.</data><data key="node_observed_status">historical_analytical_definition</data><data key="node_observed_as_of">2022-09</data><data key="node_confidence">5</data><data key="node_notes">Do not compare MTIME FY aggregates directly with Oct 1-Sep 30 reports without normalization.</data></node><node id="R188_E0027"><data key="node_entity_id">R188_E0027</data><data key="node_entity_type">workflow_rule</data><data key="node_canonical_name">QDD Priority Disability Case One-Working-Day DDS Assignment Historical Rule</data><data key="node_acronym">QDD one-day DDS</data><data key="node_domain">Disability / DDS / Adjudication</data><data key="node_description">QDD screening design prioritized cases flagged by predictive model for assignment to trained adjudicators within one working day of DDS receipt; flag does not itself determine allowance.</data><data key="node_observed_status">historical_reported_operation</data><data key="node_observed_as_of">2022-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0028"><data key="node_entity_id">R188_E0028</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">OIG ICMS FBI NIBRS Standardized Incident Reporting Dataset</data><data key="node_acronym">NIBRS extract</data><data key="node_domain">OIG / Program Integrity / External Data Exchange</data><data key="node_description">OIG June 2026 testimony reports that NIBRS-certified automated submissions pull incident reporting data from ICMS to FBI; dataset representation does not assert precise schema.</data><data key="node_observed_status">reported_FY2026_active</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0029"><data key="node_entity_id">R188_E0029</data><data key="node_entity_type">development_artifact</data><data key="node_canonical_name">OIG FY2026 Investigative Analytics Index and Requirements Work Product</data><data key="node_acronym">OIG analytics index</data><data key="node_domain">OIG / Program Integrity / Data Analytics</data><data key="node_description">SSA OIG says in FY2026 it began creating index files, requirements and documentation for planned analytics platform supporting audit/investigation extractions.</data><data key="node_observed_status">development_not_verified_production</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0030"><data key="node_entity_id">R188_E0030</data><data key="node_entity_type">digital_intake</data><data key="node_canonical_name">OIG Public Fraud and Imposter Scam Reporting Web-Form Redesign</data><data key="node_acronym">OIG fraud form</data><data key="node_domain">OIG / Program Integrity / Digital Intake</data><data key="node_description">FY2026 testimony documents OIG redesign of public fraud and imposter-scam reporting web forms for better intake quality; exact software and database route not disclosed.</data><data key="node_observed_status">historical_FY2026_work</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0031"><data key="node_entity_id">R188_E0031</data><data key="node_entity_type">investigative_data_product</data><data key="node_canonical_name">OIG Over-100 Earners Cross-SSN Mismatched Number-Holder Referral Review</data><data key="node_acronym">OIG aged-earners referral</data><data key="node_domain">OIG / Person Identity / Program Integrity</data><data key="node_description">OIG FY2026 described ICMS enhancements to review/referral data for individuals over 100 with earnings when SSN does not match true number-holder identifying information.</data><data key="node_observed_status">documented_FY2026_capability</data><data key="node_observed_as_of">2026-06-10</data><data key="node_confidence">5</data><data key="node_notes">Referral/analytics gate only. OIG testimony does not establish direct Numident or MEF updates.</data></node><node id="R188_E0032"><data key="node_entity_id">R188_E0032</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">SSI IRS Alert Physical or Electronic Copy Destruction after Verification</data><data key="node_acronym">SSI tax alert destruction</data><data key="node_domain">IRS / Title XVI / Retention</data><data key="node_description">POMS SI 02310.040 says destroy tax-data alert after verifying data unless retaining it as a disposition record; do not leave original alert in case file.</data><data key="node_observed_status">operational_policy_revised_2020</data><data key="node_observed_as_of">2020-07-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R188_E0033"><data key="node_entity_id">R188_E0033</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">SSI IRS Alert Payee Address as Restricted Tax Data</data><data key="node_acronym">IRS payee address</data><data key="node_domain">Address / IRS / Title XVI</data><data key="node_description">Tax-data definitions explicitly include taxpayer name, address, SSN, payer and transaction details; a payee may be someone using another taxpayer SSN.</data><data key="node_observed_status">operational_policy_revised_2020</data><data key="node_observed_as_of">2020-07-09</data><data key="node_confidence">5</data><data key="node_notes">Restricted IRS alert attribute, not authoritative program mailing/residence data.</data></node><node id="R189_E001"><data key="node_entity_id">R189_E001</data><data key="node_entity_type">legacy_application</data><data key="node_canonical_name">Automated Sample Selection Program (ASSP)</data><data key="node_acronym">ASSP</data><data key="node_domain">Disability / DDS</data><data key="node_description">2012 SSA-authored DDS electronic data-processing documentation identifies an automated QA sample-selection system with a quality-assurance database and federal sample-selection features.</data><data key="node_observed_status">historically_documented_2012</data><data key="node_observed_as_of">2012-08-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E002"><data key="node_entity_id">R189_E002</data><data key="node_entity_type">historical_data_store</data><data key="node_canonical_name">ASSP Quality Assurance Database (2012)</data><data key="node_domain">Disability / DDS</data><data key="node_description">Historical QA database included in automated DDS case sample selection; physical DBMS and subsequent status not described.</data><data key="node_observed_status">historically_documented_2012</data><data key="node_observed_as_of">2012-08-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E003"><data key="node_entity_id">R189_E003</data><data key="node_entity_type">historical_business_function</data><data key="node_canonical_name">ASSP Federal Disability Sample Selection (2012)</data><data key="node_domain">Disability / DDS</data><data key="node_description">Federal sample selection capabilities documented within 2012 ASSP.</data><data key="node_observed_status">historically_documented_2012</data><data key="node_observed_as_of">2012-08-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E004"><data key="node_entity_id">R189_E004</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS Major IT Replacement Feasibility and Cost-Benefit Approval Gate</data><data key="node_domain">Disability / DDS / Procurement</data><data key="node_description">DDS new or replacement hardware/software generally requires complete feasibility study and cost-benefit review with Central Office approval; POMS excepts SSA SSADARS.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E005"><data key="node_entity_id">R189_E005</data><data key="node_entity_type">legacy_or_undetermined_system</data><data key="node_canonical_name">SSADARS (SSA-Developed DDS System Reference)</data><data key="node_acronym">SSADARS</data><data key="node_domain">Disability / DDS</data><data key="node_description">Named SSA-developed DDS system explicitly excepted from DDS replacement-system feasibility review; expansion, underlying stack, and current status not established by public POMS.</data><data key="node_observed_status">named_in_2026_policy_status_unverified</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">4</data><data key="node_notes">Do not infer the acronym expansion, SSA deployment, hosting or stack.</data></node><node id="R189_E006"><data key="node_entity_id">R189_E006</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS Regional Information Security Officer System-Design Approval Gate</data><data key="node_domain">Disability / DDS / Security</data><data key="node_description">DDS feasibility and IT system proposals require regional ISO engagement from initial planning and ISO approval.</data><data key="node_observed_status">documented_2023_policy</data><data key="node_observed_as_of">2023-09-26</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E007"><data key="node_entity_id">R189_E007</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">DDS Offsite Program Backup and Continuity Requirement (2023)</data><data key="node_domain">Disability / DDS / Recovery</data><data key="node_description">2023 DDS security policy requires backups of programs to fireproof offsite storage and recovery planning; not proof of present physical tape reliance.</data><data key="node_observed_status">documented_2023_policy</data><data key="node_observed_as_of">2023-09-26</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E008"><data key="node_entity_id">R189_E008</data><data key="node_entity_type">form_lifecycle_rule</data><data key="node_canonical_name">Post-December-2024 SSA-1696 Current-Edition Acceptance Rule</data><data key="node_domain">Representatives / Identity</data><data key="node_description">2026 POMS rejects obsolete versions signed on or after December 9 2024; appointments established before date remain valid, with later updates needing current form.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E009"><data key="node_entity_id">R189_E009</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">SSA-1696 Representative-Appointment Signature Matrix</data><data key="node_domain">Representatives / Identity</data><data key="node_description">Update to principal representative requires claimant signature; certain representative affiliation/fee assignment details require representative signature; scope, fee arrangement and other claimant additions require both signatures.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E010"><data key="node_entity_id">R189_E010</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">Representative Appointment Claim-Level Scope Non-Propagation Rule (2026)</data><data key="node_domain">Representatives / Identity</data><data key="node_description">SSA honors individual claimant-selected case scope; a representative appointed on Title XVI does not automatically represent a subsequently filed Title II claim.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E011"><data key="node_entity_id">R189_E011</data><data key="node_entity_type">transaction_exception_rule</data><data key="node_canonical_name">SSA-1696 Fee Assignment Failure Does Not Invalidate Appointment</data><data key="node_domain">Representatives / Payment</data><data key="node_description">If SSA cannot process entity-directed fee assignment requested on SSA-1696, SSA continues appointment registration and informs representative; appointment and payment-assignment processing are independent.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E012"><data key="node_entity_id">R189_E012</data><data key="node_entity_type">authorization_rule</data><data key="node_canonical_name">SSA-1696 Entity Affiliation Versus Named Representative Validation</data><data key="node_domain">Representatives / Identity</data><data key="node_description">Entity may receive properly authorized fee assignment but cannot be appointed as the individual claimant representative; affiliation must exist via SSA-1699 registration.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E013"><data key="node_entity_id">R189_E013</data><data key="node_entity_type">resource_valuation_rule</data><data key="node_canonical_name">SSI First-of-Month Financial Account Valuation Rule</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">First-of-month balance, or prior-month final balance when opening balance unavailable, is resource valuation for given month with applicable statutory exclusions.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E014"><data key="node_entity_id">R189_E014</data><data key="node_entity_type">verification_process</data><data key="node_canonical_name">AFI eAFI and e4641 Dual-Component Account Verification</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">AFI program includes eAFI in SSI Claims and separate e4641 website; electronic verifications access FI account balances, fallback uses paper SSA-4641 for nonparticipants.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E015"><data key="node_entity_id">R189_E015</data><data key="node_entity_type">authorization_control</data><data key="node_canonical_name">SSI Financial Verification Permission Recording and Reuse</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">Permission collected in application, redetermination, or SSA-4641 is recorded on SSI Claims Financial Institutions Permission page; waiver evidence may verify relevant SSI months when permission applies.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E016"><data key="node_entity_id">R189_E016</data><data key="node_entity_type">evidence_rule</data><data key="node_canonical_name">SSI AFI Alternative Bank Evidence Priority and Post-Adjudication Review</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">Alternative sequence: complete statements first; then other FI records including telephone; last signed statement; pending AFI responses after adjudication processed separately as post-eligibility action.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E017"><data key="node_entity_id">R189_E017</data><data key="node_entity_type">operational_control</data><data key="node_canonical_name">AFI Required Negative Search and 25-Month Historical Balance Window</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">Where AFI verification required, technicians request negative searches and verify up to 25 prior months even when claimant supplies other evidence.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E018"><data key="node_entity_id">R189_E018</data><data key="node_entity_type">post_eligibility_workflow</data><data key="node_canonical_name">AFI Post-Adjudicative Late Financial Response Processing</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">FI responses arriving after alternative evidence allowed adjudication are processed as distinct post-eligibility work, not retroactively assumed same initial response.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E019"><data key="node_entity_id">R189_E019</data><data key="node_entity_type">attribute_data</data><data key="node_canonical_name">SSI Financial Institution Branch Address Resource Attribute</data><data key="node_domain">Title XVI / Address Provenance</data><data key="node_description">Bank/financial institution name and address recorded on SSI Claims Financial Institution Accounts page with number and account designation; bank contact address, not claimant residence.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E020"><data key="node_entity_id">R189_E020</data><data key="node_entity_type">privacy_control</data><data key="node_canonical_name">SSI AFI Automated Telephone Credential Self-Entry Rule</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">When technicians use FI automated phone access, individuals enter account passwords or PINs; employees may not solicit or enter customer secret credentials and discontinue insecure three-way call.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E021"><data key="node_entity_id">R189_E021</data><data key="node_entity_type">vendor_interaction_rule</data><data key="node_canonical_name">AFI Participating Bank Vendor-Only Verification Escalation</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">Once electronic verification requested from participating FI, vendor rather than SSA technicians must liaise with FI on unresolved information; no vendor company identity asserted.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E022"><data key="node_entity_id">R189_E022</data><data key="node_entity_type">resource_calculation_rule</data><data key="node_canonical_name">SSI AFI Early Deposit and Tax-Refund Balance Exclusion</data><data key="node_domain">Title XVI / Financial Data</data><data key="node_description">When material to SSI eligibility, employees subtract qualifying early benefit deposits and still-excluded tax-refund amounts from account resource balance and document the exclusion on FI account page.</data><data key="node_observed_status">documented_2026_policy</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E023"><data key="node_entity_id">R189_E023</data><data key="node_entity_type">actuarial_scenario</data><data key="node_canonical_name">OACT E2.16 Taxable Earnings Above $250,000 Solvency Proposal (Illustrative)</data><data key="node_domain">Actuarial / Scenario Data</data><data key="node_description">Long-range OASDI proposal E2.16 models expanded payroll-tax base, augmented wage-index assumption, additional AIME+ and 2% factor on covered above-maximum earnings. It is not enacted policy.</data><data key="node_observed_status">illustrative_proposal</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E024"><data key="node_entity_id">R189_E024</data><data key="node_entity_type">actuarial_data_product</data><data key="node_canonical_name">OACT E2.16 Annual Cost-Income-Balance and Trust-Ratio Data Series</data><data key="node_domain">Actuarial / Publication</data><data key="node_description">Annual modeled OASDI cost, income, annual balance, and trust-fund ratio compared with current-law baseline in E2.16 scenario; output vintage must accompany every figure.</data><data key="node_observed_status">illustrative_publication</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E025"><data key="node_entity_id">R189_E025</data><data key="node_entity_type">actuarial_scenario</data><data key="node_canonical_name">OACT G1 Forty-Percent Trust-Fund Equity Investment Model Scenario</data><data key="node_domain">Actuarial / Scenario Data</data><data key="node_description">Hypothetical trust-fund-equity investment phased 2026 to 2040 with 5.8% ultimate real annual assumed return; proposal only, not reported Treasury holdings.</data><data key="node_observed_status">illustrative_proposal</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E026"><data key="node_entity_id">R189_E026</data><data key="node_entity_type">actuarial_data_product</data><data key="node_canonical_name">OACT G1 Equity-Investment Annual Cost-Income Trust-Ratio Data Series</data><data key="node_domain">Actuarial / Publication</data><data key="node_description">Proposed-vs-current-law OASDI annual cost/income rate and trust fund ratio under hypothetical 40% equities allocation with modeled investment return.</data><data key="node_observed_status">illustrative_publication</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E027"><data key="node_entity_id">R189_E027</data><data key="node_entity_type">advisory_statistical_product</data><data key="node_canonical_name">SSAB 2017 Disability Application Cohort Decision-Time Chart Collection</data><data key="node_domain">Disability / Research</data><data key="node_description">SSAB 2017 interactive charts analyze filing-cohort time to disability decision across Title II and XVI and by reached adjudication level; not an SSA production decision system.</data><data key="node_observed_status">historical_publication_2017</data><data key="node_observed_as_of">2017-06-26</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E028"><data key="node_entity_id">R189_E028</data><data key="node_entity_type">statistical_methodology</data><data key="node_canonical_name">SSAB Disability Decision-Time Cohort Pending-Case Bias Warning (2017)</data><data key="node_domain">Disability / Research</data><data key="node_description">Recent-filed cohorts have still-pending applications not counted among completed decisions; displayed decision-time averages for recent cohorts can drift upward as pending long cases finalize.</data><data key="node_observed_status">historical_methodology_2017</data><data key="node_observed_as_of">2017-06-26</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R189_E029"><data key="node_entity_id">R189_E029</data><data key="node_entity_type">consent_activation_rule</data><data key="node_canonical_name">PIE Payroll Data Subscription Activation Notice and Interim Wage Reporting</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">SSA October 2026 advises monthly wage reporting through other channels until notification confirms PIE employer payroll exchange has begun.</data><data key="node_observed_status">documented_2026_public_guidance</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R190_E001"><data key="node_entity_id">R190_E001</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Earnings Public-Use File, 2006</data><data key="node_acronym">EPUF 2006</data><data key="node_domain">Earnings &amp; Research</data><data key="node_description">Public-use earnings microdata released August 2011 from a systematic 1-percent sample of SSNs issued before 2007; primarily drawn from MEF summary segment.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2011-08</data><data key="node_confidence">5</data><data key="node_notes">2006 denotes earnings/vintage, not release date; deidentified statistical file, not MEF operational record.</data></node><node id="R190_E002"><data key="node_entity_id">R190_E002</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">EPUF 2006 Demographic Subfile</data><data key="node_domain">Earnings &amp; Research</data><data key="node_description">Public-use EPUF demographic subfile containing 4,384,254 sampled individual records including aggregate 1937-1950 earnings.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2011-08</data><data key="node_confidence">5</data><data key="node_notes">Includes randomized linkage identifier; not an authoritative person repository.</data></node><node id="R190_E003"><data key="node_entity_id">R190_E003</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">EPUF 2006 Annual Earnings Subfile</data><data key="node_domain">Earnings &amp; Research</data><data key="node_description">Public-use EPUF annual earnings subfile with 60,326,474 records for 3,131,424 persons with positive annual earnings in 1951-2006.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2011-08</data><data key="node_confidence">5</data><data key="node_notes">Year-specific earnings extracts, not claims processing or tax-form addresses.</data></node><node id="R190_E004"><data key="node_entity_id">R190_E004</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">EPUF 2006 Randomized Subfile Linkage Identifier</data><data key="node_domain">Person/Identity Nexus</data><data key="node_description">Random, non-SSN linkage key associating the public-use demographic and annual earnings subfiles.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2011-08</data><data key="node_confidence">5</data><data key="node_notes">Randomized identifier does not prove identity or enable linkage to a live SSA Person master.</data></node><node id="R190_E005"><data key="node_entity_id">R190_E005</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">EPUF 2006 Statistical Disclosure Protection</data><data key="node_domain">Research Governance</data><data key="node_description">EPUF confidentiality processing removes identifying information, adjusts earnings, and zeroes some earnings based on age considerations.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2011-08</data><data key="node_confidence">5</data><data key="node_notes">EPUF is disclosure-modified administrative sampling, unlike fully synthetic BEPUF 2020. Addresses are not published as individual records.</data></node><node id="R190_E006"><data key="node_entity_id">R190_E006</data><data key="node_entity_type">research_method</data><data key="node_canonical_name">EPUF 2006 SSN-Based One-Percent Systematic Sample</data><data key="node_domain">Research Methodology</data><data key="node_description">Systematic 1-percent random sample of all SSNs issued before 2007, with sampling weight 100.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2011-08</data><data key="node_confidence">5</data><data key="node_notes">Sample is of SSNs issued, not a 1-percent random sample of all current beneficiaries.</data></node><node id="R190_E007"><data key="node_entity_id">R190_E007</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI 2010 Geographic-Age-Eligibility-Diagnosis Public-Use Summary Series</data><data key="node_domain">Title XVI &amp; Statistical Publications</data><data key="node_description">Four April 2013 public summary datasets derived from SSI Annual Statistical Report 2010, Tables 10 and 38.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2013-04</data><data key="node_confidence">5</data><data key="node_notes">Statistical outputs do not create, overwrite, or correct SSR.</data></node><node id="R190_E008"><data key="node_entity_id">R190_E008</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI-State-Age-2010.csv</data><data key="node_domain">Title XVI &amp; Statistical Publications</data><data key="node_description">Public summary of SSI recipients by state and age group for 2010; catalog ID US-GOV-SSA-340.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2013-04</data><data key="node_confidence">5</data><data key="node_notes">Aggregate output; no individual address or person location record.</data></node><node id="R190_E009"><data key="node_entity_id">R190_E009</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI-State-Eligibility-2010.csv</data><data key="node_domain">Title XVI &amp; Statistical Publications</data><data key="node_description">Public summary of SSI recipients by state and eligibility category; catalog ID US-GOV-SSA-341.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2013-04</data><data key="node_confidence">5</data><data key="node_notes">Blind and disabled eligibility categories combined for privacy.</data></node><node id="R190_E010"><data key="node_entity_id">R190_E010</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI-Under65-Diag-1-2010.csv</data><data key="node_domain">Title XVI &amp; Statistical Publications</data><data key="node_description">Public under-65 SSI diagnostic summary by SSA region; catalog ID US-GOV-SSA-342.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2013-04</data><data key="node_confidence">5</data><data key="node_notes">Geographic aggregation above state level for disclosure protection.</data></node><node id="R190_E011"><data key="node_entity_id">R190_E011</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI-Under65-Diag-2-2010.csv</data><data key="node_domain">Title XVI &amp; Statistical Publications</data><data key="node_description">Public under-65 SSI diagnostic summary by Census Area; catalog ID US-GOV-SSA-343.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2013-04</data><data key="node_confidence">5</data><data key="node_notes">Geographic aggregation above state level for disclosure protection.</data></node><node id="R190_E012"><data key="node_entity_id">R190_E012</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">SSI 2010 Public-Use Summary Geographic and Eligibility Coarsening</data><data key="node_domain">Research Governance</data><data key="node_description">Privacy-control procedure merging blind and disabled eligibility categories and coarsening diagnostic geographic output to SSA regions or Census Areas.</data><data key="node_observed_status">historical_publication</data><data key="node_observed_as_of">2013-04</data><data key="node_confidence">5</data><data key="node_notes">Released aggregate summaries do not identify claimant residence.</data></node><node id="R190_E013"><data key="node_entity_id">R190_E013</data><data key="node_entity_type">research_dataset</data><data key="node_canonical_name">Ticket Research File (TRF) Used in 2012 Disability Coverage Study</data><data key="node_acronym">TRF</data><data key="node_domain">Disability &amp; Administrative Research</data><data key="node_description">SSA research file of disability applicants and awardees, identified as the source for the 10-percent 2000-entry cohort finder sample in a 2012 linkage study.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2012-08</data><data key="node_confidence">5</data><data key="node_notes">Historical study reports roughly 20 million observations in TRF at time of research; not proof of current size or deployment.</data></node><node id="R190_E014"><data key="node_entity_id">R190_E014</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2012 SSA-to-CMS Disability Cohort Finder File</data><data key="node_domain">External Exchanges &amp; Research</data><data key="node_description">Finder file of SSNs and basic identifiers constructed from a TRF sample for CMS to select Medicare and Medicaid enrollment extracts.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2012-08</data><data key="node_confidence">5</data><data key="node_notes">Specific statistical-study extract; not an asserted enterprise live CMS lookup interface. Legal approval/retention details not in source.</data></node><node id="R190_E015"><data key="node_entity_id">R190_E015</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">CMS Medicare Enrollment Data Base (2012 Study Source)</data><data key="node_domain">Medicare &amp; Research</data><data key="node_description">CMS Medicare enrollment administrative record source used in a historical SSA-CMS disability coverage research study.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2012-08</data><data key="node_confidence">5</data><data key="node_notes">Only study-era data source established; underlying hosting/technology not established.</data></node><node id="R190_E016"><data key="node_entity_id">R190_E016</data><data key="node_entity_type">external_data_store</data><data key="node_canonical_name">CMS Medicaid Analytic Extract (2012 Study Source)</data><data key="node_domain">Medicaid &amp; Research</data><data key="node_description">CMS Medicaid Analytic Extract record source used in a historical SSA-CMS disability coverage research study.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2012-08</data><data key="node_confidence">5</data><data key="node_notes">Analytical source, not evidence of real-time Medicaid coverage synchronization.</data></node><node id="R190_E017"><data key="node_entity_id">R190_E017</data><data key="node_entity_type">research_dataset</data><data key="node_canonical_name">2012 Linked Disability Awardee Medicare-Medicaid Cohort</data><data key="node_domain">Disability &amp; Administrative Research</data><data key="node_description">Merged SSA and CMS study dataset covering 68,798 first-ever adult disability entrants in 2000, with 12 preaward and 72 postaward months.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2012-08</data><data key="node_confidence">5</data><data key="node_notes">Analytical research cohort excludes certain categories; no evidence of changes to MBR, SSR or CMS master records.</data></node><node id="R190_E018"><data key="node_entity_id">R190_E018</data><data key="node_entity_type">research_method</data><data key="node_canonical_name">Disability Coverage Eighty-Four-Month Person-Level Observation Window</data><data key="node_domain">Research Methodology</data><data key="node_description">Twelve preaward and seventy-two postaward months tracked across DI/SSI eligibility and Medicare Part A/full Medicaid coverage for a 2000 award cohort.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2012-08</data><data key="node_confidence">5</data><data key="node_notes">Full Medicaid only, excluding limited QMB/SLMB-only benefit categories.</data></node><node id="R190_E019"><data key="node_entity_id">R190_E019</data><data key="node_entity_type">research_method</data><data key="node_canonical_name">Disability Cohort Medicare Part A and Full Medicaid Coverage Definition</data><data key="node_domain">Research Methodology</data><data key="node_description">2012 analysis defines Medicare coverage through Part A enrollment and Medicaid coverage through full-benefit enrollment.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2012-08</data><data key="node_confidence">5</data><data key="node_notes">Statistics cannot be treated as total Medicaid or Medicare enrollment including limited-benefit coverage.</data></node><node id="R190_E020"><data key="node_entity_id">R190_E020</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">GAO 2025 SSA Purchased-to-Active Software License Inventory Reconciliation Recommendation</data><data key="node_domain">Infrastructure &amp; Acquisition Governance</data><data key="node_description">GAO May 2025 priority recommendation that SSA compare installed/active software license inventories with purchased licenses to improve cost and investment decisions.</data><data key="node_observed_status">recommendation_open_as_of</data><data key="node_observed_as_of">2025-05-22</data><data key="node_confidence">5</data><data key="node_notes">Oversight recommendation only; no new software-license tooling or implementation asserted.</data></node><node id="R191_E001"><data key="node_entity_id">R191_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">MBR DOB B/C Proof-Code Numident Correction Permission (2023)</data><data key="node_domain">Person/Identity Nexus</data><data key="node_description">POMS RM 10210.295C authorizes a Numident DOB change to the matching MBR DOB where MBR age proof code B or C applies; other codes carry specific eligibility limits.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E002"><data key="node_entity_id">R191_E002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSR Q DOB Proof-Code Full Age Development Requirement (2023)</data><data key="node_domain">Person/Identity Nexus</data><data key="node_description">POMS RM 10210.295C requires full age development for SSR date-of-birth proof code Q rather than unconditional use of the SSR DOB to change Numident.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E003"><data key="node_entity_id">R191_E003</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI Interstate Address Change Prior-State Residence Carryforward Rule</data><data key="node_domain">Address Provenance and IRS Data</data><data key="node_description">POMS SI 02306.010 requires staff in specified interstate moves to enter the new mailing address while retaining the previous state/county residence, FLA and OSS codes pending development of actual new living arrangements.</data><data key="node_observed_status">observed_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Interim SSR information can intentionally disagree with newly observed mailing address; do not infer verification or automatic residence update.</data></node><node id="R191_E004"><data key="node_entity_id">R191_E004</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">SSA-8203-BK Separate Mailing and Residence Statement on SSI Redetermination</data><data key="node_domain">Address Provenance and IRS Data</data><data key="node_description">POMS SI 02305.115 requires residence information separately from a different mailing address on paper SSI redeterminations; SSI Claims LRES and APID maintain the separate categories electronically.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E005"><data key="node_entity_id">R191_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Treasury Returned Check Address-Reason SSI S06 Automatic Suspension Trigger</data><data key="node_domain">Title XVI / Address Provenance</data><data key="node_description">POMS SI 02301.240 says SSI records automatically process to S06 when Treasury returns a benefit check for an address-related reason; this is payment eligibility status, not beneficiary address verification.</data><data key="node_observed_status">documented_active_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E006"><data key="node_entity_id">R191_E006</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSI S06 USPS-Locate Requirement and Optional State/Bank Address Leads</data><data key="node_domain">Address Provenance and IRS Data</data><data key="node_description">POMS SI 02301.240 requires FO contact efforts and normally SSA-L2001 postal address request; SASRO state data and financial-institution contacts are optional leads, with findings documented before suspension.</data><data key="node_observed_status">documented_active_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E007"><data key="node_entity_id">R191_E007</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSADARS Disability Hearing Spanish Notice Indicator Printout</data><data key="node_domain">Disability / Hearing Notice Data</data><data key="node_description">POMS DI 33010.025 requires field offices to record need for Spanish-language notices in the folder and SSADARS printout. Source does not describe the physical storage engine.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">SSADARS technical interface and current deployment remain unresolved.</data></node><node id="R191_E008"><data key="node_entity_id">R191_E008</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-381-SP Spanish Notice Waiver</data><data key="node_domain">Disability / Hearings</data><data key="node_description">POMS DI 33010.025 identifies SSA-381-SP as the signed waiver of the right to Spanish notices, accompanied by folder documentation of no need for translation.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E009"><data key="node_entity_id">R191_E009</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Disability Hearing Unit Spanish-Notice Discovery Coordination</data><data key="node_domain">Disability / Hearings</data><data key="node_description">When DHU discovers need for Spanish notices, policy requires folder annotation, schedule update, and notification to FO and DDS.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E010"><data key="node_entity_id">R191_E010</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">2026 ALJ Medical Expert Rationale Memorandum to Hearing Office Chief ALJ</data><data key="node_domain">Hearings and Appeals</data><data key="node_description">HALLEX HA 01250.034 requires an ALJ to email a written explanation for seeking an ME to the HOCALJ before staff schedules testimony or sends ME interrogatories.</data><data key="node_observed_status">documented_effective_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E011"><data key="node_entity_id">R191_E011</data><data key="node_entity_type">control</data><data key="node_canonical_name">2026 ALJ Medical Expert HOCALJ Email and Case Note Checkpoint</data><data key="node_domain">Hearings and Appeals</data><data key="node_description">HALLEX HA 01250.034B requires ALJ-HOCALJ rationale communication and documentation of the communication in a case note before hearing-office staff schedules the expert or sends interrogatories.</data><data key="node_observed_status">documented_effective_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E012"><data key="node_entity_id">R191_E012</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2026 Required Medical Expert Opinion Conditions</data><data key="node_domain">Hearings and Appeals</data><data key="node_description">HALLEX HA 01250.034A lists required ME cases such as explicit court or Appeals Council order, applicable acquiescence ruling, or potential Step 3 medical equivalence, subject to documented rationale.</data><data key="node_observed_status">documented_effective_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E013"><data key="node_entity_id">R191_E013</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2026 Discretionary Medical Expert Opinion Conditions</data><data key="node_domain">Hearings and Appeals</data><data key="node_description">HALLEX HA 01250.034A permits discretion for uncommon impairments, disputed testing, failure to follow treatment, addiction materiality, and difficult onset inference; same rationale prerequisite applies.</data><data key="node_observed_status">documented_effective_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E014"><data key="node_entity_id">R191_E014</data><data key="node_entity_type">publication_status</data><data key="node_canonical_name">2026 Annual Statistical Supplement Section 4.C Insured-Worker Tables Publication Discontinuation</data><data key="node_domain">Actuarial and Statistical Products</data><data key="node_description">SSA 2026 Annual Statistical Supplement says it is discontinuing section 4.C insured-worker tables since equivalent products are already available from OACT Statistical Tables; publication route is moved, not underlying insured-status computation.</data><data key="node_observed_status">announced_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E015"><data key="node_entity_id">R191_E015</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 OACT Table 4.C1 Insured Worker Estimate Series 1940-2026</data><data key="node_domain">Actuarial and Statistical Products</data><data key="node_description">OACT Table 4.C1 publishes fully insured, permanently insured and disability-insured counts through 2026; estimates are drawn from the 2026 Trustees assumptions and partly from the one-percent Continuous Work History Sample, not a population-level operational file.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Counts for 2026 are estimates and may be revised; historical cells are not guaranteed final.</data></node><node id="R191_E016"><data key="node_entity_id">R191_E016</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 OACT Fully-Insured Workers by Age and Sex Table 4.C2</data><data key="node_domain">Actuarial and Statistical Products</data><data key="node_description">OACT Table 4.C2FI presents fully insured worker counts grouped by age and sex through 2026; estimates are statistical aggregates, not extracted individual current benefit records.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E017"><data key="node_entity_id">R191_E017</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 OACT Disability-Insured Workers by Age and Sex Table 4.C2</data><data key="node_domain">Actuarial and Statistical Products</data><data key="node_description">OACT Table 4.C2DI separately reports estimated workers insured for disability benefits by age and sex; do not equate disability-insured status with beneficiary payment status.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E018"><data key="node_entity_id">R191_E018</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 OACT 4.C5 Social Security Area Population and Insured Percentages Table</data><data key="node_domain">Actuarial and Statistical Products</data><data key="node_description">OACT Table 4.C5 provides insured-worker proportions against the Social Security area population denominator; population definition exceeds United States resident census alone.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R191_E019"><data key="node_entity_id">R191_E019</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2026 SSI Recipient or Payee Move Reporting Duty and Reporter Attribution</data><data key="node_domain">Title XVI / Address Provenance</data><data key="node_description">POMS SI 02301.005 states SSI recipients and representative payees must report moves and address changes with reporter identity, subject SSN, facts, and change date, by written, telephone, or in-person routes.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E001"><data key="node_entity_id">R192_E001</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2025 Supplement Table 4.B10 Covered Workers by State, 2023</data><data key="node_domain">Earnings / Statistical Geography</data><data key="node_description">Table 4.B10 state-disaggregated 2023 covered-worker earnings/contributions statistics, based on CWHS 1-percent sample; table identifies state classification limitations.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E002"><data key="node_entity_id">R192_E002</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2025 Supplement Table 4.B12 Medicare Covered Workers by State, 2023</data><data key="node_domain">Earnings / Statistical Geography</data><data key="node_description">Table 4.B12 state-disaggregated 2023 HI taxable earnings/contributions statistics; state assignment derived under same employer-file methodology.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E003"><data key="node_entity_id">R192_E003</data><data key="node_entity_type">source_data_field</data><data key="node_canonical_name">Electronic Employer Wage Report End-of-Year Worker Residence Attribute</data><data key="node_domain">Earnings / Address Provenance</data><data key="node_description">End-of-year worker residence in electronically filed employer wage reports; used for most statistical state assignments in 2025 Supplement tables 4.B10 and 4.B12.</data><data key="node_observed_status">documented_statistical_input</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes">Source is an employer filing. Does not establish the MBR/SSR residence or master-file update.</data></node><node id="R192_E004"><data key="node_entity_id">R192_E004</data><data key="node_entity_type">source_data_field</data><data key="node_canonical_name">Paper Employer Wage Report Employer-Location Geographic Proxy</data><data key="node_domain">Earnings / Statistical Geography</data><data key="node_description">Employer location on paper-filed wage reports used as a fallback state assignment in 2025 supplement; this is not an observed employee residence.</data><data key="node_observed_status">documented_statistical_input</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes">The report does not identify how many employees use each fallback.</data></node><node id="R192_E005"><data key="node_entity_id">R192_E005</data><data key="node_entity_type">statistical_processing_rule</data><data key="node_canonical_name">2025 Supplement CWHS State-Assignment Provenance Rule</data><data key="node_domain">Earnings / Address Provenance</data><data key="node_description">For 2023 covered-worker state estimates, SSA primarily uses worker end-of-year residence from electronic wage reports and uses employer location from paper reports for the remaining records.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E006"><data key="node_entity_id">R192_E006</data><data key="node_entity_type">reference_publication</data><data key="node_canonical_name">2026 OASDI Program Reference for Statistical Publications</data><data key="node_domain">Actuarial / Statistical Publication</data><data key="node_description">Standalone resource launched March 2026 and updated June 2026 replacing OASDI program description and legislative-history material formerly part of Annual Statistical Supplement through 2024.</data><data key="node_observed_status">published_updated_2026</data><data key="node_observed_as_of">2026-06</data><data key="node_confidence">5</data><data key="node_notes">Background reference does not override POMS, regulations or statute.</data></node><node id="R192_E007"><data key="node_entity_id">R192_E007</data><data key="node_entity_type">reference_publication</data><data key="node_canonical_name">SSA Cross-Publication Statistical Glossary, 2025-2026</data><data key="node_domain">Statistical Data Governance</data><data key="node_description">Statistical glossary created December 2025 and updated June 2026 to consolidate terms for Annual Statistical Supplement, DI Annual Statistical Report, and SSI Annual Statistical Report.</data><data key="node_observed_status">published_updated_2026</data><data key="node_observed_as_of">2026-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E008"><data key="node_entity_id">R192_E008</data><data key="node_entity_type">data_definition_rule</data><data key="node_canonical_name">2026 Statistical Glossary Program-Scoped Terminology Labels</data><data key="node_domain">Statistical Data Governance</data><data key="node_description">Glossary tags terms as OASDI, SSI, or both and cautions that current publication notes override simplified general definitions.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E009"><data key="node_entity_id">R192_E009</data><data key="node_entity_type">policy_governance_rule</data><data key="node_canonical_name">2026 OASDI Statistical Reference Policy-Authority Boundary</data><data key="node_domain">Statistical Data Governance</data><data key="node_description">Standalone OASDI statistical reference explicitly states that it is interpretive background and not authoritative SSA program policy.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E010"><data key="node_entity_id">R192_E010</data><data key="node_entity_type">actuarial_data_product</data><data key="node_canonical_name">2022 OACT Beginning-of-Year Social Security Area Population File</data><data key="node_domain">Actuarial / Population</data><data key="node_description">2022 Trustees intermediate-assumptions age-sex-marital-status population download for January 1, 1941 through January 1, 2101, in text/CSV/Excel.</data><data key="node_observed_status">historical_2022_vintage</data><data key="node_observed_as_of">2022</data><data key="node_confidence">5</data><data key="node_notes">Forecast vintage is 2022, not 2026.</data></node><node id="R192_E011"><data key="node_entity_id">R192_E011</data><data key="node_entity_type">actuarial_data_product</data><data key="node_canonical_name">2022 OACT Midyear Social Security Area Population File</data><data key="node_domain">Actuarial / Population</data><data key="node_description">2022 Trustees intermediate-assumptions age-sex-marital-status population download for July 1, 1941 through July 1, 2100.</data><data key="node_observed_status">historical_2022_vintage</data><data key="node_observed_as_of">2022</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E012"><data key="node_entity_id">R192_E012</data><data key="node_entity_type">actuarial_data_product</data><data key="node_canonical_name">2022 OACT End-of-Year Social Security Area Population File</data><data key="node_domain">Actuarial / Population</data><data key="node_description">2022 Trustees intermediate-assumptions age-sex-marital-status population download for December 31, 1940 through December 31, 2100.</data><data key="node_observed_status">historical_2022_vintage</data><data key="node_observed_as_of">2022</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E013"><data key="node_entity_id">R192_E013</data><data key="node_entity_type">data_definition_rule</data><data key="node_canonical_name">2022 OACT Population Begin-End Annual Offset Identity Rule</data><data key="node_domain">Actuarial / Publication Pipelines</data><data key="node_description">2022 OACT documentation states beginning-of-year values equal prior-year end-of-year values, with calendar-year label offset by one.</data><data key="node_observed_status">documented_2022_vintage</data><data key="node_observed_as_of">2022</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E014"><data key="node_entity_id">R192_E014</data><data key="node_entity_type">record_precedence_rule</data><data key="node_canonical_name">Title II SSR Address-Change Date Versus MBR Updated-Date Precedence Rule</data><data key="node_domain">Address Provenance / Title II</data><data key="node_description">For undeliverable Title II correspondence, employees compare SSI SSR ACD date to MBR ADDR Updated date and may use newer SSI address through POS to update MBR.</data><data key="node_observed_status">documented_2023_policy</data><data key="node_observed_as_of">2023-05-26</data><data key="node_confidence">5</data><data key="node_notes">Scope limited to Title II undeliverable mail; not a general automatic cross-program synchronization path.</data></node><node id="R192_E015"><data key="node_entity_id">R192_E015</data><data key="node_entity_type">manual_update_rule</data><data key="node_canonical_name">Title II Financial Institution or USPS Located-Address POS Processing Rule</data><data key="node_domain">Address Provenance / Title II</data><data key="node_description">GN 02605.055 instructs employees to input newly supplied FI/USPS addresses via POS and remail required correspondence after address development.</data><data key="node_observed_status">documented_2023_policy</data><data key="node_observed_as_of">2023-05-26</data><data key="node_confidence">5</data><data key="node_notes">Manual procedure; bank postal information not automatically verified in unrelated SSA programs.</data></node><node id="R192_E016"><data key="node_entity_id">R192_E016</data><data key="node_entity_type">cross_program_workflow</data><data key="node_canonical_name">Concurrent SSI Address Divergence Manual Field-Office Referral</data><data key="node_domain">Address Provenance / Title II and XVI</data><data key="node_description">When Title II beneficiary also receives SSI and new address differs from SSR, PSC/TSC sends Request for Assistance or MDW to FO; FO updates SSI address in SSI Claims System.</data><data key="node_observed_status">documented_2023_policy</data><data key="node_observed_as_of">2023-05-26</data><data key="node_confidence">5</data><data key="node_notes">Explicitly separate T2 POS and T16 SSI Claims transactions.</data></node><node id="R192_E017"><data key="node_entity_id">R192_E017</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II Undeliverable Required-Response Notice Classification</data><data key="node_domain">Notices / Title II</data><data key="node_description">GN 02605.055 separates returned notices requiring response or due-process development from informational mail that can be discarded without further development.</data><data key="node_observed_status">documented_2023_policy</data><data key="node_observed_as_of">2023-05-26</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E018"><data key="node_entity_id">R192_E018</data><data key="node_entity_type">evidence_retention_workflow</data><data key="node_canonical_name">Title II Undeliverable Notice ORS-or-NDRed Preservation Choice</data><data key="node_domain">Notices / Evidence</data><data key="node_description">If undeliverable notice is already in ORS staff can discard returned paper; otherwise fax through Evidence Portal to NDRed after failed address development.</data><data key="node_observed_status">documented_2023_policy</data><data key="node_observed_as_of">2023-05-26</data><data key="node_confidence">5</data><data key="node_notes">Source describes routing; no unsupported retention period or automated linkage inferred.</data></node><node id="R192_E019"><data key="node_entity_id">R192_E019</data><data key="node_entity_type">controlled_cross_record_followup</data><data key="node_canonical_name">Numident Sex-Field Correction Downstream Program-Record Action</data><data key="node_domain">Identity / Numident</data><data key="node_description">RM 10212.200 directs SSA staff who update a Numident sex designation to also update MBR, SSR, RPS or other relevant records.</data><data key="node_observed_status">current_documented_policy</data><data key="node_observed_as_of">2026-06-05</data><data key="node_confidence">5</data><data key="node_notes">Direction to staff; no proof of automatic propagation or change to other fields.</data></node><node id="R192_E020"><data key="node_entity_id">R192_E020</data><data key="node_entity_type">controlled_cross_record_followup</data><data key="node_canonical_name">Numident Parent-Name Correction Program and Payee Follow-Up</data><data key="node_domain">Identity / Numident</data><data key="node_description">Upon correcting Numident child parent-name field, SSA asks whether parent is Title II beneficiary, SSI recipient or payee, then reviews MBR, SSR or RPS and takes needed action.</data><data key="node_observed_status">current_documented_policy</data><data key="node_observed_as_of">2026-06-05</data><data key="node_confidence">5</data><data key="node_notes">May require new representative-payee application rather than automatic synchronization.</data></node><node id="R192_E021"><data key="node_entity_id">R192_E021</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2025 SSI Statistical Report Table 69 Disability Application Outcomes by Filing Cohort</data><data key="node_domain">Disability / SSI Statistical Pipeline</data><data key="node_description">SSI ASR 2025 Table 69 aggregates disability application outcomes 1992-2024 by application filing cohort, tracking technical denials, medical decisions, subsequent denials, awards, allowances and pending cases.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-08</data><data key="node_confidence">5</data><data key="node_notes">DRF 100% dataset; recent filing cohorts incomplete.</data></node><node id="R192_E022"><data key="node_entity_id">R192_E022</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2025 SSI Statistical Report Tables 70-72 Adjudication-Level Allowance Data</data><data key="node_domain">Disability / SSI Statistical Pipeline</data><data key="node_description">SSI ASR 2025 Tables 70-72 publish allowance rates at initial, reconsideration and hearing-or-above levels for SSI-only and concurrent applications.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E023"><data key="node_entity_id">R192_E023</data><data key="node_entity_type">statistical_definition_rule</data><data key="node_canonical_name">2025 SSI Statistical Disability Medical Allowance Versus Final Award Calculation</data><data key="node_domain">Disability / SSI Statistical Governance</data><data key="node_description">SSI ASR defines medical allowance as medical allowances including later technical denials divided by completed medical decisions; award rate excludes subsequent denials from allowances and divides by applications no longer pending.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-08</data><data key="node_confidence">5</data><data key="node_notes">These rates have different denominators and should not be mixed.</data></node><node id="R192_E024"><data key="node_entity_id">R192_E024</data><data key="node_entity_type">statistical_definition_rule</data><data key="node_canonical_name">2025 SSI Disability Research File Pending-Cohort Revision Rule</data><data key="node_domain">Disability / SSI Statistical Governance</data><data key="node_description">SSA warns newer application cohorts have pending decisions and published allowance/award rates will change as adjudication and subsequent technical checks complete.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R192_E025"><data key="node_entity_id">R192_E025</data><data key="node_entity_type">historical_process_rule</data><data key="node_canonical_name">SSI Reconsideration Prototype Ten-State Statistical Period 1999-2020</data><data key="node_domain">Disability / Appeals Research</data><data key="node_description">SSI ASR documents reconsideration omitted in 10 prototype states for applications beginning October 1999, phaseout January 2019 to restoration March 31 2020; this affects level-specific outcome comparison.</data><data key="node_observed_status">historical_1999_2020</data><data key="node_observed_as_of">2026-08</data><data key="node_confidence">5</data><data key="node_notes">Last portion of historical experiment falls within 20-year 2006-2026 research window.</data></node><node id="R192_E026"><data key="node_entity_id">R192_E026</data><data key="node_entity_type">statistical_disclosure_rule</data><data key="node_canonical_name">2025 SSI County-Payment Suppression Does Not Change State Totals Rule</data><data key="node_domain">SSI / Geographic Publication</data><data key="node_description">2025 SSI state-county publication suppresses certain county statistics to avoid disclosing information about individuals while state totals still include suppressed counties.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-08</data><data key="node_confidence">5</data><data key="node_notes">No individual-level address/beneficiary identity is exposed through this public data product.</data></node><node id="R192_E027"><data key="node_entity_id">R192_E027</data><data key="node_entity_type">statistical_processing_rule</data><data key="node_canonical_name">2025 SSI State-County Published Payment Rounding Difference Rule</data><data key="node_domain">SSI / Geographic Publication</data><data key="node_description">2025 SSI report rounds county amounts to whole dollars; state totals are summed from unrounded figures and can differ from displayed rounded county totals.</data><data key="node_observed_status">published_2026</data><data key="node_observed_as_of">2026-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E001"><data key="node_entity_id">R193_E001</data><data key="node_entity_type">application</data><data key="node_canonical_name">DIBwiz Disability Claim Record Locator</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">SSA instructs staff to consult DIBwiz to find claim-related information; POMS explicitly denies interfaces to CPMS, CEF/DMA, and ORS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not infer database, owner, runtime, or additional integrations. Documented absence of three interfaces is specific to policy observation.</data></node><node id="R193_E002"><data key="node_entity_id">R193_E002</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">CEF Multi-System Official Folder Assembly</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Folder copy requires checking several claims, evidence, payee, disability control, and appeals sources rather than treating one digital display as the complete official file.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E003"><data key="node_entity_id">R193_E003</data><data key="node_entity_type">control</data><data key="node_canonical_name">CEF Temporary Green-Section Disclosure Exclusion</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Documents in Current Development/Temporary green section do not constitute releasable official folder material when copying a CEF.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E004"><data key="node_entity_id">R193_E004</data><data key="node_entity_type">control</data><data key="node_canonical_name">CEF Linked Document Export Prerequisite</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Linked CPD/ORS or other documents must be physically copied into current folder before eView CD export; external links alone are not copied.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E005"><data key="node_entity_id">R193_E005</data><data key="node_entity_type">control</data><data key="node_canonical_name">CEF eView Messages Flags and Bookmarks Export Exclusion</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">POMS specifies messages, flags and bookmarks/annotations are not included when copying electronic images to CD; hearing audio rules differ.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E006"><data key="node_entity_id">R193_E006</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">eView ORS-to-CEF Selective Document Import</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Applicable ORS documents are imported into CEF through eView before folder copying rather than automatic full ORS synchronization.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E007"><data key="node_entity_id">R193_E007</data><data key="node_entity_type">process</data><data key="node_canonical_name">DDS Contract-Scanner Medical-Evidence Return Route</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">DDS case-development correspondence identifies contractor scanning PO box as return address and includes indexed DMA barcode; DDS may also provide a DMA fax address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E008"><data key="node_entity_id">R193_E008</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">DMA Evidence Request Barcode and Indexing Header</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">A DMA barcode with indexing information on DDS evidence-request correspondence supports associating returned evidence with the certified electronic folder.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E009"><data key="node_entity_id">R193_E009</data><data key="node_entity_type">data_flow</data><data key="node_canonical_name">EDCS SSA-3368 Work-History-to-SSA-3369 Population</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Work-history data entered on EDCS SSA-3368 propagates to the EDCS SSA-3369 work-history report.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E010"><data key="node_entity_id">R193_E010</data><data key="node_entity_type">control</data><data key="node_canonical_name">SSI EFI Missing Representative-Contact Manual Data-Entry Gate</data><data key="node_domain">Representative Payee &amp; Representation</data><data key="node_description">For Title XVI-only cases with missing appointed representative data in EFI, DDS checks EDCS and SSA-1696 and manually keys name/address/telephone/fax into case-processing system.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E011"><data key="node_entity_id">R193_E011</data><data key="node_entity_type">event</data><data key="node_canonical_name">EDCS Action Page Add Client Contact Work Item</data><data key="node_domain">Representative Payee &amp; Representation</data><data key="node_description">Field office receives EDCS Action Page Request FO to add Client Contact item in designated missing-representative-data scenario.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E012"><data key="node_entity_id">R193_E012</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">HIT MER Yellow-Section Evidence Document</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">HIT Medical Evidence of Record is located in yellow section of the electronic disability folder for DDS review.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E013"><data key="node_entity_id">R193_E013</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">HIT Request Response and SSA-827 Issue Blue-Section Documents</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">HIT Request, HIT No Request, HIT Response, and HIT SSA-827 Issue documents are identified in the blue section of an electronic disability folder.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E014"><data key="node_entity_id">R193_E014</data><data key="node_entity_type">control</data><data key="node_canonical_name">HIT Standard Narrative-Only Graphic Evidence Limitation</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">HIT standard documents include narrative categories; certain graphical medical evidence or images are excluded and require further development when needed.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E015"><data key="node_entity_id">R193_E015</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">HIT User Trigger Electronic Medical-Record Follow-Up</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">DDS instructions direct staff to consider electronic HIT User Trigger to seek additional medical evidence before traditional requests, with ERE available as another route.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E016"><data key="node_entity_id">R193_E016</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">EFI Appointed Representative Contact Attribute Set</data><data key="node_domain">Representative Payee &amp; Representation</data><data key="node_description">Case contact data in an EFI download can include representative name, address, telephone and fax, and may be missing on Title XVI-only transfers.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E017"><data key="node_entity_id">R193_E017</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Outstanding Document Request Query</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">eView query displays unreceipted document requests for eView-created barcodes, including document type, site, request identifier, timestamp, provider, and adjudication level.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E018"><data key="node_entity_id">R193_E018</data><data key="node_entity_type">control</data><data key="node_canonical_name">eView Outstanding-Request Query Barcode-Origin Coverage Limit</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Outstanding Document Request Query excludes barcodes created in DDS legacy systems, CPMS, and ARPS; absence from the list is not proof of no request.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E019"><data key="node_entity_id">R193_E019</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">eView Document Bookmark Audit Metadata</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Bookmark list may expose text, document, page, exhibit, date received, section and user identifier of bookmarking employee.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E020"><data key="node_entity_id">R193_E020</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">eView Categorized Document Page Metadata</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Categorized pages display document, page, category type, source, exhibit, receipt date, and electronic folder section; links open the DMA viewer.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E021"><data key="node_entity_id">R193_E021</data><data key="node_entity_type">access_control</data><data key="node_canonical_name">OHO Hearing-Level Electronic Folder Private Section</data><data key="node_domain">Disability &amp; Evidence</data><data key="node_description">Case Documents tab includes private file section at hearing level accessible only to hearing office with jurisdiction, per historical POMS.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E022"><data key="node_entity_id">R193_E022</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSI Claims Liquid Resource Redetermination Guided Path</data><data key="node_domain">Title XVI</data><data key="node_description">Opening SSI REDETERMINATION event guides technician to screens for documenting liquid-resource allegations and evidence.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E023"><data key="node_entity_id">R193_E023</data><data key="node_entity_type">control</data><data key="node_canonical_name">SSI Financial-Institution Permission at Each FO Redetermination</data><data key="node_domain">Title XVI</data><data key="node_description">FOs must request permission to contact financial institutions when initiating each SSI redetermination.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E024"><data key="node_entity_id">R193_E024</data><data key="node_entity_type">control</data><data key="node_canonical_name">SSI Controlled-versus-Informational IRS Alert Handling</data><data key="node_domain">Address Provenance &amp; IRS Data</data><data key="node_description">Controlled IRS alerts require appropriate development; informational IRS alerts act as investigative leads during SSI liquid-resource redeterminations.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E025"><data key="node_entity_id">R193_E025</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSI Redetermination Financial Institution Business Address</data><data key="node_domain">Address Provenance &amp; IRS Data</data><data key="node_description">SSA-8203-BK captures institution or organization name and address when claimant identifies liquid-resource accounts; this is not a beneficiary residence address.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E026"><data key="node_entity_id">R193_E026</data><data key="node_entity_type">process</data><data key="node_canonical_name">SSI Direct-Deposit Indicator Resource Development Trigger</data><data key="node_domain">Title XVI</data><data key="node_description">A direct-deposit indicator on SSR or MBR prompts further financial-account resource development and recording on CCE Financial Accounts screen.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E027"><data key="node_entity_id">R193_E027</data><data key="node_entity_type">control</data><data key="node_canonical_name">SSI Early-Payment Month-End Financial Resource Adjustment</data><data key="node_domain">Title XVI</data><data key="node_description">Advance SSI payment received before normal month can be excluded from first-of-month resource balance under specified circumstances.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E028"><data key="node_entity_id">R193_E028</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Representative Payee Type Individual-or-Organization Code</data><data key="node_domain">Representative Payee &amp; Representation</data><data key="node_description">Individual/Organization payee-type code is maintained separately on MBR, SSR, and eRPS and drives identifier and payment-legend selection.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E029"><data key="node_entity_id">R193_E029</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">eRPS Organizational Applicant State Registration Evidence Gate</data><data key="node_domain">Representative Payee &amp; Representation</data><data key="node_description">When EIN/name/organization status cannot be verified through EIF, field office manager seeks IRS or state legal registration evidence before classifying organization.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E030"><data key="node_entity_id">R193_E030</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">August 2026 Monthly Benefit Snapshot MBR-SSR Cross-Program Count</data><data key="node_domain">Actuarial &amp; Statistical Products</data><data key="node_description">Published August 2026 snapshot uses 100-percent MBR and SSR counts and avoids double counting for specified concurrent/dual beneficiaries.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R193_E031"><data key="node_entity_id">R193_E031</data><data key="node_entity_type">control</data><data key="node_canonical_name">Monthly Beneficiary Snapshot Cross-Program Deduplication Rule</data><data key="node_domain">Actuarial &amp; Statistical Products</data><data key="node_description">SSA snapshot classifies Social Security-only, SSI-only, and concurrent receipt, counting qualifying primary/secondary Title II entitlement just once.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E001"><data key="node_entity_id">R194_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Samoa IDD Country-Specific RTN 66 and DAN O Account Encoding</data><data key="node_domain">Title II Payments</data><data key="node_description">POMS prescribes Samoa RTN country prefix 66, bank-code lookup in ITS.gov, and account code O on MBR; conflict in textual field lengths is separately logged.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E002"><data key="node_entity_id">R194_E002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Samoa IDD Published Field-Length and Currency Inconsistency</data><data key="node_domain">Payments Data Quality</data><data key="node_description">Published POMS July 2026 contains inconsistent DAN lengths (section E versus F), divergent examples, and an apparently reversed USD/WST step; do not normalize to one definitive format without policy clarification.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E003"><data key="node_entity_id">R194_E003</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">San Marino IDD RTN 71 and DAN C Encoding</data><data key="node_domain">Title II Payments</data><data key="node_description">IBAN-derived routing coding specifies prefix 71 and DAN letter C. A U.S.-residence address on MBR blocks IDD posting.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-01-16</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E004"><data key="node_entity_id">R194_E004</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Foreign-to-Domestic Title II Change of Address IDD Cancellation Gate</data><data key="node_domain">Address Provenance</data><data key="node_description">When beneficiary returns to a U.S. address, international direct deposit cannot continue; verify MBR and process applicable changes via PEAD.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-11-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E005"><data key="node_entity_id">R194_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Foreign-to-Domestic Change of Address Independent Lawful Presence and Tax Development</data><data key="node_domain">Identity &amp; Address</data><data key="node_description">Foreign-to-domestic COA may trigger CLCZ/CLLP lawful-presence development; nonresident alien withholding reviewed separately via PELF.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-11-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E006"><data key="node_entity_id">R194_E006</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">International Operations Jurisdiction Retention After Domestic Move</data><data key="node_domain">Title II Payments</data><data key="node_description">OIO retains jurisdiction while any foreign-address, restricted-country, six-month absence, or totalization condition applies, otherwise transfers to PC1-7 after COA.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2024-11-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E007"><data key="node_entity_id">R194_E007</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Beneficiary Abroad U.S. Mailing Versus Foreign Residence Control</data><data key="node_domain">Address Provenance</data><data key="node_description">Limited U.S.-mailing exceptions for beneficiaries abroad include APO/FPO/DPO, U.S. payee or brief absence. SSA still requires current residence for foreign enforcement.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2017-01-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E008"><data key="node_entity_id">R194_E008</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Payee Without Assignable SSN Title II Manual MACADE Record Update</data><data key="node_domain">Representative Payee</data><data key="node_description">For a payee applicant lacking an assignable SSN, FO completes SSA-11 and refers to PC Paperless; PC enters Title II manual appointment using MACADE and updates MBR.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2018-11-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E009"><data key="node_entity_id">R194_E009</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Payee Without Assignable SSN Title XVI SSA-1719B Manual SSR Update</data><data key="node_domain">Representative Payee</data><data key="node_description">For SSN-less payee selection, field office manually enters Title XVI payee using SSA-1719B or SSA-450 to update SSR.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2018-11-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R194_E010"><data key="node_entity_id">R194_E010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">EAB Newborn Existing SSN No-Additional-Card Posting Rule</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">2010 policy states an EAB request for an infant with an existing assigned SSN can post to Numident without issuing another original card.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2010-01-15</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R195_E_CWHS_ACTIVE_2006"><data key="node_entity_id">R195_E_CWHS_ACTIVE_2006</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">2006 Continuous Work History Sample Active Subfile</data><data key="node_domain">Earnings / Research</data><data key="node_description">2009 article describes 2006 CWHS active portion as 3.3 million sample SSNs with at least one earnings posting on MEF.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_CWHS_INACTIVE_2006"><data key="node_entity_id">R195_E_CWHS_INACTIVE_2006</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">2006 Continuous Work History Sample Inactive Subfile</data><data key="node_domain">Earnings / Research</data><data key="node_description">2009 article describes 2006 CWHS inactive subfile as 1.1 million sample SSNs without posted earnings.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_CWHS_INDUSTRY_2009"><data key="node_entity_id">R195_E_CWHS_INDUSTRY_2009</data><data key="node_entity_type">data_provenance</data><data key="node_canonical_name">Historical CWHS Employer Industry Classification Inputs</data><data key="node_domain">Earnings / Research</data><data key="node_description">2009 document derives CWHS/EE-ER NAICS industry variables from IRS Form SS-4, tax returns and Census Bureau data; Census access required special sworn status and approved projects.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_CWHS_SE_2009"><data key="node_entity_id">R195_E_CWHS_SE_2009</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">Historical CWHS Self-Employment One-Percent Statistical File (2009)</data><data key="node_domain">Earnings / Research</data><data key="node_description">Historical CWHS annual self-employment snapshot includes IRS data not retained on MEF, such as geography, farm/nonfarm split and optional reporting methods.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_CWHS_TIMING_2009"><data key="node_entity_id">R195_E_CWHS_TIMING_2009</data><data key="node_entity_type">data_production_rule</data><data key="node_canonical_name">Historical Annual CWHS MEF January Extract and Validation Schedule</data><data key="node_domain">Earnings / Research</data><data key="node_description">2009 SSA publication states annual MEF-derived CWHS extract in January approximately 13 months after tax year; availability generally spring after validation.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_ERISA_PLAN_ADDR"><data key="node_entity_id">R195_E_ERISA_PLAN_ADDR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SSA ERISA Pension Plan Address Files</data><data key="node_domain">Pensions / Address Provenance</data><data key="node_description">Pension plan contact/address files updated using PBGC plan merger or termination information; not claimant residence.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_IRS_ERISA_QTR"><data key="node_entity_id">R195_E_IRS_ERISA_QTR</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">IRS Quarterly ERISA Pension Plan Administration-Change Files</data><data key="node_domain">Pensions / IRS External Exchanges</data><data key="node_description">IRS sends SSA quarterly files identifying pension plan changes including transfers of plan administration.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MAPS_AEQY"><data key="node_entity_id">R195_E_MAPS_AEQY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Alpha Access to EIF Query (AEQY)</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">PCOM Master File Query menu option used with payer EIN to retrieve pension or annuity payer name/address.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MAPS_DWRC"><data key="node_entity_id">R195_E_MAPS_DWRC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Development Worksheet Report of Contact (DWRC)</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS report-of-contact recording applicant/payer statements, evidence, tax year, verified monthly amount and contact information.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MAPS_EIN"><data key="node_entity_id">R195_E_MAPS_EIN</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">MAPS Detailed Agency Data Payer Employer Identification Number</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">Payer EIN shown in MEDQ Detailed Agency Data and used to query payer contact location.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MAPS_IRS_ANNUITY"><data key="node_entity_id">R195_E_MAPS_IRS_ANNUITY</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">IRS 1099-R Pension and Annuity Agency Data in MAPS</data><data key="node_domain">IRS / Medicare Extra Help</data><data key="node_description">IRS-derived pension/annuity transactions presented in MAPS MEDQ with form type, tax year, EIN and income amount.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MAPS_MEDQ"><data key="node_entity_id">R195_E_MAPS_MEDQ</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Medicare Query Display (MEDQ)</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">Medicare Application Processing System query display used to inspect current and detailed agency pension/annuity information.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MAPS_OLD_IRS_OPM"><data key="node_entity_id">R195_E_MAPS_OLD_IRS_OPM</data><data key="node_entity_type">historical_copy</data><data key="node_canonical_name">Potential Historical IRS-Sourced OPM Pension Entries in MAPS</data><data key="node_domain">Medicare / Data Lifecycle</data><data key="node_description">POMS states earlier IRS-derived OPM pension entries may still be viewable after May 23 2009; direct OPM information is used for current verification.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MAPS_OPM_FIRST"><data key="node_entity_id">R195_E_MAPS_OPM_FIRST</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">MAPS Office of Personnel Management Direct-Pension Data Precedence</data><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">Since May 23, 2009 MAPS no longer posts OPM pension amounts from IRS; OPM direct data are authoritative for this verification to avoid double counting. Older IRS-derived entries may still display.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">As documented in POMS 2011 with 2026 batch; not assertion that this component remains architecturally unchanged in 2026.</data></node><node id="R195_E_MAPS_PAYER_LOCATION"><data key="node_entity_id">R195_E_MAPS_PAYER_LOCATION</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Pension or Annuity Payer Name and Address via EIN Lookup</data><data key="node_domain">Address Provenance / Medicare Extra Help</data><data key="node_description">Payer business contact address returned by PCOM Alpha Access to EIF after looking up EIN from MAPS; not the applicant residence address.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MAPS_RECENCY"><data key="node_entity_id">R195_E_MAPS_RECENCY</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Medicare Extra Help Pension Evidence Recency Selection Rule</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">SSA must use most recent appropriate applicant/payer or agency evidence when verifying disputed pension or annuity income for Extra Help.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MEF_W2W3"><data key="node_entity_id">R195_E_MEF_W2W3</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Employer W-2 to W-3 Wage Report Reconciliation Gate</data><data key="node_domain">Earnings / Integrity</data><data key="node_description">2009 SSA documentation says cumulative employee W-2 amounts must agree with employer W-3 transmittal before posting individual earnings.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_MEF_WEEKLY_2009"><data key="node_entity_id">R195_E_MEF_WEEKLY_2009</data><data key="node_entity_type">data_production_rule</data><data key="node_canonical_name">Historical MEF Weekly Earnings Posting Cadence (2009)</data><data key="node_domain">Earnings / History</data><data key="node_description">2009 SSA research described MEF weekly updating as employer and IRS earnings data arrived continuously; no inference about 2026 cadence.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_OACT_PERIOD_COHORT"><data key="node_entity_id">R195_E_OACT_PERIOD_COHORT</data><data key="node_entity_type">data_definition</data><data key="node_canonical_name">2026 OACT Period Versus Cohort Mortality Data Interpretation</data><data key="node_domain">Actuarial / Mortality</data><data key="node_description">Period life tables describe a given calendar year; cohort life tables track mortality across calendar years for a given birth cohort. Their columns and periods are not interchangeable.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_OACT_SSAREA_POP"><data key="node_entity_id">R195_E_OACT_SSAREA_POP</data><data key="node_entity_type">data_definition</data><data key="node_canonical_name">2026 OACT Social Security Area Population Scope Definition</data><data key="node_domain">Actuarial / Population</data><data key="node_description">Published definition covers 50 states/DC adjusted, territories, U.S. armed forces and federal civilians abroad with dependents, insured noncitizens abroad and other U.S. citizens abroad.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_PBGC"><data key="node_entity_id">R195_E_PBGC</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Pension Benefit Guaranty Corporation</data><data key="node_domain">Pensions / Federal Partners</data><data key="node_description">Federal pension guarantor identified as a source of private pension plan merger and termination information to SSA.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_PBGC_PLAN_CHANGES"><data key="node_entity_id">R195_E_PBGC_PLAN_CHANGES</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">PBGC Pension Plan Termination and Merger Information Supplied to SSA</data><data key="node_domain">Pensions / External Exchanges</data><data key="node_description">PBGC provides SSA Central Office data about plan termination or mergers for pension plan address files under documented ERISA process.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_SSA1099_DEAD_LOGIN"><data key="node_entity_id">R195_E_SSA1099_DEAD_LOGIN</data><data key="node_entity_type">identity_access_control</data><data key="node_canonical_name">eAccess Deceased-Beneficiary mySSA Access Block</data><data key="node_domain">Identity / Digital Services</data><data key="node_description">2025 POMS says eAccess (formerly ROME) blocks a deceased beneficiary my Social Security account.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_SSA1099_DECEASED_MBR"><data key="node_entity_id">R195_E_SSA1099_DECEASED_MBR</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Deceased Beneficiary SSA-1099 Last-MBR-Address Mailing Rule</data><data key="node_domain">Address Provenance / Tax Documents</data><data key="node_description">If beneficiary dies before annual SSA-1099 is issued or received, SSA mails benefit-tax statement to last address on MBR, not a newly verified executor address.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_SSA1099_MFQUERY"><data key="node_entity_id">R195_E_SSA1099_MFQUERY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSA Master File Query 1099 Benefit Statement Replacement Option</data><data key="node_domain">Title II / Tax Documents</data><data key="node_description">FO staff can retrieve benefit-tax statement through SSA Master File Query menu option 1099, with SSA-1099-F2-INST and IRS Notice 703.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_SSA1099_TAX_WINDOW"><data key="node_entity_id">R195_E_SSA1099_TAX_WINDOW</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Current-Year Online Benefit-Tax Statement Mid-December–January Blackout</data><data key="node_domain">Title II / Digital Service</data><data key="node_description">Current SSA-1099/1042S replacement request is unavailable mid-December through Jan 31; earlier five tax years remain accessible.</data><data key="node_observed_status">documented_historical</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_2022_WEEK"><data key="node_entity_id">R195_E_STAT_2022_WEEK</data><data key="node_entity_type">statistical_method</data><data key="node_canonical_name">2022 Fiscal-Year Extra-Week Workload Reporting Difference</data><data key="node_domain">Hearings / Analytics</data><data key="node_description">SSA FY2022 hearing receipts/dispositions 2.F9 excludes extra 2022 week while 2.F11 Appeals Council includes its 1,299 receipts and 2,240 dispositions.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_2024_T2F11"><data key="node_entity_id">R195_E_STAT_2024_T2F11</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">FY2021–FY2024 Appeals Council Workload Statistics (2025 Supplement Table 2.F11)</data><data key="node_domain">Appeals / Publication</data><data key="node_description">ARPS MI source for receipts, dispositions, pending counts; special 2022 53rd-week accounting affects comparability.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_2024_T2F4"><data key="node_entity_id">R195_E_STAT_2024_T2F4</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">FY2024 OASI Claims Received and Processed (2025 Supplement Table 2.F4)</data><data key="node_domain">Title II / Publication</data><data key="node_description">FY2024 OASI claims workload received and processed counts derived from SSA Integrated Work Measurement System.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_2024_T2F5"><data key="node_entity_id">R195_E_STAT_2024_T2F5</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">FY2024 DI Claims Received and Processed (2025 Supplement Table 2.F5)</data><data key="node_domain">Disability / Publication</data><data key="node_description">FY2024 DI claims workload by worker and family or survivor class from Integrated Work Measurement System.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_2024_T2F6"><data key="node_entity_id">R195_E_STAT_2024_T2F6</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">FY2024 SSI Claims Received and Processed (2025 Supplement Table 2.F6)</data><data key="node_domain">Title XVI / Publication</data><data key="node_description">FY2024 SSI claims workload by aged versus blind/disabled class from Integrated Work Measurement System.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_2024_T2F8"><data key="node_entity_id">R195_E_STAT_2024_T2F8</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">FY2021–FY2024 ALJ Dispositions and Availability Measures (2025 Supplement Table 2.F8)</data><data key="node_domain">Hearings / Publication</data><data key="node_description">ALJ averages from CPMS MI; dispositions exclude attorney adjudicator decisions and ALJ availability denominators differ by measure.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_2024_T2F9"><data key="node_entity_id">R195_E_STAT_2024_T2F9</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">FY2022–FY2024 Hearing Receipts, Dispositions and Pending Statistics (2025 Supplement Table 2.F9)</data><data key="node_domain">Hearings / Publication</data><data key="node_description">CPMS MI output by OASI, DI, SSI and concurrent DI/SSI; program category reclassifications and 2022 fiscal-week exception documented.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_2F_DISCONT"><data key="node_entity_id">R195_E_STAT_2F_DISCONT</data><data key="node_entity_type">publication_revision</data><data key="node_canonical_name">2025 Supplement Discontinued Agency Resources and Service Metrics Tables 2.F1–2.F3 and 2.F7</data><data key="node_domain">Enterprise / Publication</data><data key="node_description">SSA discontinued these particular Supplement workload tables and points readers to agency financial and service/improper payment reporting; underlying data not necessarily discontinued.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_ENUM_2024"><data key="node_entity_id">R195_E_STAT_ENUM_2024</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">SSA SSNs Issued 1937–2024 Table 2.F12 (2025 Supplement)</data><data key="node_domain">Identity / Publication</data><data key="node_description">Historical SSN issuance counts; official note warns some people received more than one SSN, so issued number counts are not unique-person counts.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_ENUM_PERF"><data key="node_entity_id">R195_E_STAT_ENUM_PERF</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">SSA Enumeration Performance Reports Statistical Source</data><data key="node_domain">Identity / Publication</data><data key="node_description">SSA Enumeration Performance Reports identified as source for SSNs issued and age distribution in 2025 Supplement Table 2.F12.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R195_E_STAT_SUPP_2025_2F"><data key="node_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">Annual Statistical Supplement 2025 Agency Workloads Section 2.F</data><data key="node_domain">Data Products &amp; Publications</data><data key="node_description">Published 2025 SSA workload chapter tracing distinct claims, hearing, Appeals Council and enumeration data to operational systems; some legacy metrics discontinued.</data><data key="node_observed_status">observed_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Official source documents scope; no unsupported hosting, technology, interface or auto-update inference.</data></node><node id="R196_E001"><data key="node_entity_id">R196_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSPA Section 211 Alien-Worker Insured-Status Gate</data><data key="node_acronym">SSPA 211</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">For alien workers whose first properly assigned SSN is on/after 2004-01-01, requires work-purpose SSN at any time since that date or qualifying B-1/D-1/D-2 admission to meet additional Title II/ESRD Medicare insured-status gate.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E002"><data key="node_entity_id">R196_E002</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Numident Original SSN Assignment Cycle Date and Entry Type O</data><data key="node_acronym">CYD/ETC O</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Earliest original Numident iteration cycle date used as evidence of original SSN assignment date; special cases require additional review.</data><data key="node_observed_status">documented_attribute</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E003"><data key="node_entity_id">R196_E003</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Numident Work Authorization Evidence-Interview Codes H/C and Citizenship Code B</data><data key="node_acronym">IDN H/C CSP B</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">POMS-prescribed codes evaluated for historical employment-authorization eligibility under the SSPA alien worker rule.</data><data key="node_observed_status">documented_attribute</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E004"><data key="node_entity_id">R196_E004</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSPA First Properly Assigned SSN Identity-Precedence Control</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Original SSN assigned based on worker actual identity takes precedence over a later new SSN or someone else’s SSN for Section 211 date test.</data><data key="node_observed_status">documented_rule</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E005"><data key="node_entity_id">R196_E005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSPA Wrong-Number SS-5 and Scrambled-Earnings Development</data><data key="node_domain">Earnings &amp; Identity</data><data key="node_description">Requires SS-5 review, true-numberholder identification and appropriate earnings correction when identity/SSN attribution is inconsistent.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E006"><data key="node_entity_id">R196_E006</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSPA B-1 D-1 D-2 Immigration Admission Alternative</data><data key="node_domain">Title II / Insured Status</data><data key="node_description">Qualifying prior DHS admission as B-1/D-1/D-2 nonimmigrant can satisfy Section 211 alternative, but ordinary quarters-of-coverage tests still apply.</data><data key="node_observed_status">documented_rule</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E007"><data key="node_entity_id">R196_E007</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSPA MCS-Excluded Manual Disallowance Processing</data><data key="node_domain">Title II / Claims</data><data key="node_description">For specified Section 211 disallowances with an SSN, exclude MCS/EC and use MADCAP/MACADE; manual Title II DIB/RSI disallowance codes and list controls apply.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E008"><data key="node_entity_id">R196_E008</data><data key="node_entity_type">notice</data><data key="node_canonical_name">SSPA Section 211 Manual Disallowance Notice DSL008</data><data key="node_acronym">DSL008</data><data key="node_domain">Title II / Notices</data><data key="node_description">DPS initial-claim manual notice template with Section 211 disallowance paragraph DSL008.</data><data key="node_observed_status">documented_notice</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E009"><data key="node_entity_id">R196_E009</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSPA Section 211 Award and Disallowance Listing Codes 291 and 292</data><data key="node_acronym">291/292</data><data key="node_domain">Title II / Claims</data><data key="node_description">Manual case control codes for B-1/D-1/D-2 qualifying award versus Section 211 not-met disallowance.</data><data key="node_observed_status">documented_control</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E010"><data key="node_entity_id">R196_E010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSPA Original-SSN Special-Indicator Regional Review</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Numident special indicator codes 1,2,4,5,7 require regional-office consultation while processing covered insured-status cases.</data><data key="node_observed_status">documented_rule</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R196_E011"><data key="node_entity_id">R196_E011</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">Historical SS-5 Voluntary Race and Ethnicity Response</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Self-reported demographic categories on SS-5 varied by vintage and are not population-complete in later EAB/EAE enumeration processes.</data><data key="node_observed_status">historical_research</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E012"><data key="node_entity_id">R196_E012</data><data key="node_entity_type">governance_control</data><data key="node_canonical_name">EAB and EAE Race-Ethnicity Noncollection Boundary</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Enumeration at Birth and Entry workflows do not transmit birth-certificate medical-use race/ethnicity fields for SSA enumeration; absence is not individual demographic evidence.</data><data key="node_observed_status">historical_research</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E013"><data key="node_entity_id">R196_E013</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2016 SSA Comparative Race-Data Survey Methodology Note</data><data key="node_domain">Research / Statistical</data><data key="node_description">Research note comparing CPS, SIPP, ACS and HRS as alternatives to incomplete SSA enumeration-based demographic records.</data><data key="node_observed_status">published_2016</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E014"><data key="node_entity_id">R196_E014</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">Current Population Survey Annual Social and Economic Supplement</data><data key="node_acronym">CPS/ASEC</data><data key="node_domain">Research / Statistical</data><data key="node_description">BLS/Census survey add-on used for historical SSA OASDI/SSI demographic research with specified recall, age and benefit-reporting limitations.</data><data key="node_observed_status">historical_documentation</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R196_E015"><data key="node_entity_id">R196_E015</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">American Community Survey Demographic Research Source (2016)</data><data key="node_acronym">ACS</data><data key="node_domain">Research / Statistical</data><data key="node_description">Census annual ACS source used to estimate demographic composition of beneficiaries; paper states SSA administrative linkage was unavailable for ACS in comparison.</data><data key="node_observed_status">historical_documentation</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R196_E016"><data key="node_entity_id">R196_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Historical SSA Administrative Race-Series Noncomparability Rule</data><data key="node_domain">Research / Statistical</data><data key="node_description">Historic differences in SS-5 categories and EAB/EAE missingness restrict race analysis; past SSI and OASDI race breakdowns were discontinued after 2002 and 2009 respectively.</data><data key="node_observed_status">historical_research</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">This records historical publication constraints only; the 2002 change predates the run research window.</data></node><node id="R196_E017"><data key="node_entity_id">R196_E017</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2024 Trustees Cohort Life Tables Male CSV (1900-2100)</data><data key="node_domain">Actuarial / Statistical</data><data key="node_description">Downloadable CSV of historic and projected cohort mortality/life functions for males, 2024 Trustees intermediate assumptions; age columns 0-119.</data><data key="node_observed_status">published_2024_vintage</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E018"><data key="node_entity_id">R196_E018</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2024 Trustees Cohort Life Tables Female CSV (1900-2100)</data><data key="node_domain">Actuarial / Statistical</data><data key="node_description">Downloadable CSV of historic and projected cohort mortality/life functions for females, 2024 Trustees intermediate assumptions; age columns 0-119.</data><data key="node_observed_status">published_2024_vintage</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E019"><data key="node_entity_id">R196_E019</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2024 Trustees Period Life Tables Male Historical CSV (1900-2021)</data><data key="node_domain">Actuarial / Statistical</data><data key="node_description">Downloadable male historical period mortality/life table CSV, one calendar-year period at a time; 2024 Trustees historical vintage.</data><data key="node_observed_status">published_2024_vintage</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E020"><data key="node_entity_id">R196_E020</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2024 Trustees Period Life Tables Male Projected CSV (2022-2100)</data><data key="node_domain">Actuarial / Statistical</data><data key="node_description">Downloadable male period life table projected CSV based on intermediate assumptions of 2024 Trustees Report.</data><data key="node_observed_status">published_2024_vintage</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E021"><data key="node_entity_id">R196_E021</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2024 Trustees Period Life Tables Female Historical CSV (1900-2021)</data><data key="node_domain">Actuarial / Statistical</data><data key="node_description">Downloadable female historical period mortality/life table CSV, separate from male and projected series.</data><data key="node_observed_status">published_2024_vintage</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E022"><data key="node_entity_id">R196_E022</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2024 Trustees Period Life Tables Female Projected CSV (2022-2100)</data><data key="node_domain">Actuarial / Statistical</data><data key="node_description">Downloadable female period life table projected CSV based on 2024 Trustees intermediate assumptions.</data><data key="node_observed_status">published_2024_vintage</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E023"><data key="node_entity_id">R196_E023</data><data key="node_entity_type">data_element</data><data key="node_canonical_name">OACT 2024 Life Table Year and Single-Age Column Dimensions</data><data key="node_domain">Actuarial / Statistical</data><data key="node_description">Life table download dimensions: calendar year rows and ages 0 through 119 columns, published separately by sex and projection approach.</data><data key="node_observed_status">published_2024_vintage</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E024"><data key="node_entity_id">R196_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">OACT Life-Table Trustees-Vintage Assumption Precedence</data><data key="node_domain">Actuarial / Statistical</data><data key="node_description">Projected 2024 life table values use intermediate assumptions of 2024 Trustees Report; cannot be substituted for 2026 Trustee-based values without vintage reconciliation.</data><data key="node_observed_status">documented_data_boundary</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E025"><data key="node_entity_id">R196_E025</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2020 HRS-SSA Linked Earnings Study of Denied DI Applicants</data><data key="node_domain">Disability / Research</data><data key="node_description">Social Security Bulletin analytical study linking consenting HRS interview records and administrative earnings to study denied DI applicants over time.</data><data key="node_observed_status">published_2020</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E026"><data key="node_entity_id">R196_E026</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">HRS Linked Summary Earnings File Study Extract (2020)</data><data key="node_domain">Earnings / Research</data><data key="node_description">Analysis-specific use of HRS linked Summary Earnings File records with MEF payroll-covered earnings; not a newly identified operational earnings master.</data><data key="node_observed_status">historical_2020</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E027"><data key="node_entity_id">R196_E027</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">HRS Consent-Limited SSA Earnings Research Linkage</data><data key="node_domain">Research / Privacy</data><data key="node_description">Access to SSA linked earnings file permitted for consenting HRS respondents, with HRS survey conventions and research controls.</data><data key="node_observed_status">historical_2020</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R196_E028"><data key="node_entity_id">R196_E028</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">SSA Public Statistical Publication Forecast and Release Schedule (2026)</data><data key="node_domain">Statistical Publications</data><data key="node_description">Public-facing schedule of anticipated release cycles including monthly, quarterly, annual SSA data products; forecast dates subject to publication changes.</data><data key="node_observed_status">observed_2026_10_11</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0001"><data key="node_entity_id">R197_E0001</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">CMA 1076 Monthly SSI/SVB Finder File (2026 notice)</data><data key="node_domain">Title XVI / Data Exchange</data><data key="node_description">Monthly SSA file of SSI and Special Veterans Benefits eligibility attributes sent to CMS for LTC/MDS matching; specific columns not listed in notice.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No claim of member field names, transport, or host.</data></node><node id="R197_E0002"><data key="node_entity_id">R197_E0002</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">CMA 1076 CMS LTC/MDS Response File (2026 notice)</data><data key="node_domain">Title XVI / Data Exchange</data><data key="node_description">CMS response file following match of SSA monthly finder file against long-term-care Minimum Data Set; useful for facility admission and discharge eligibility review.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0003"><data key="node_entity_id">R197_E0003</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">CMA 1076 Nursing Care Facility Admission and Discharge Events</data><data key="node_domain">Title XVI / Residency</data><data key="node_description">CMS LTC/MDS admission/discharge observations are used to assess SSI medical-facility eligibility and possible SVB non-overseas residence; they are not verified residential mailing addresses.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0004"><data key="node_entity_id">R197_E0004</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2026 CMS Facility-Match SVB Overseas Residence Review</data><data key="node_domain">Address Provenance / SVB</data><data key="node_description">SSA uses CMS institutional facility data to identify SVB beneficiaries who may no longer be residing outside the United States; follow-up verification not specified in notice.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0005"><data key="node_entity_id">R197_E0005</data><data key="node_entity_type">governance_event</data><data key="node_canonical_name">2026 CMS LTC/MDS Matching Effective-Year Correction</data><data key="node_domain">Data Exchange Governance</data><data key="node_description">Federal Register original May 7 notice said June 20 2025; June 22 correction replaces with June 20 2026, and the program is subject to statutory waiting conditions.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0006"><data key="node_entity_id">R197_E0006</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">2026 SSI Fiscal Service Savings Securities Finder (approximately 10 million records)</data><data key="node_domain">Title XVI / Treasury</data><data key="node_description">SSA transmits an approximately 10-million-record finder file of SSNs and names for SSI applicants, recipients and deemors in savings-securities review.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0007"><data key="node_entity_id">R197_E0007</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">2026 SSI Fiscal Service Savings Securities Registration Response</data><data key="node_domain">Title XVI / Treasury</data><data key="node_description">Matched Treasury response lists security purchase amount, account and confirmation numbers, series, issue date, redemption value, and finder-file return date.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0008"><data key="node_entity_id">R197_E0008</data><data key="node_entity_type">data_governance</data><data key="node_canonical_name">2026 SSI Savings Securities Finder-File Scope and Matching Rule</data><data key="node_domain">Title XVI / Treasury</data><data key="node_description">2026 Federal Register specifies roughly 10 million SSI finder-file records and limited use to detecting unreported or incorrectly reported savings securities ownership.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0009"><data key="node_entity_id">R197_E0009</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">2026 CMS ACA Eligibility SSA Verification Request Fields</data><data key="node_domain">External Exchange / Person</data><data key="node_description">CMS submits last name, first name, birthdate, SSN and citizenship indicator to SSA for ACA affordability matching; these are query fields, not an SSA Person master.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0010"><data key="node_entity_id">R197_E0010</data><data key="node_entity_type">exchange_data_product</data><data key="node_canonical_name">2026 SSA ACA Eligibility Verification Conditional Response Fields</data><data key="node_domain">External Exchange / Person</data><data key="node_description">After successful name and SSN match, SSA may return identifying attributes; death, disability and incarceration indicators; Title II annual/monthly income; citizenship/SSN attestation and optionally work quarters.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0011"><data key="node_entity_id">R197_E0011</data><data key="node_entity_type">exchange_governance</data><data key="node_canonical_name">2026 ACA Matching Name-SSN Gate and Disclosure Scope</data><data key="node_domain">External Exchange / Identity</data><data key="node_description">The 2026 CMS notice conditions response on SSA finding a match on supplied SSN and name, and only information available and relevant is returned.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0012"><data key="node_entity_id">R197_E0012</data><data key="node_entity_type">organization</data><data key="node_canonical_name">Program Policy and Data Exchange Division (PPDX)</data><data key="node_domain">Data Exchange Governance</data><data key="node_description">In 2026 SSA Law and Policy assigned responsibility for central agency-wide data exchange activities and standardized policy to PPDX.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0013"><data key="node_entity_id">R197_E0013</data><data key="node_entity_type">historic_organization</data><data key="node_canonical_name">Office of Data Exchange and Policy Publications (ODEPP), 2013</data><data key="node_domain">Data Exchange Governance</data><data key="node_description">SSA established ODEPP in 2013 as centralized policy and data-exchange function; later renamed/reorganized.</data><data key="node_observed_status">historical_2013</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0014"><data key="node_entity_id">R197_E0014</data><data key="node_entity_type">historic_organization</data><data key="node_canonical_name">Office of Data Exchange, Policy Publications and International Negotiations (ODEPPIN), 2018</data><data key="node_domain">Data Exchange Governance</data><data key="node_description">SSA says 2018 ODEPPIN followed ODEPP; in 2025 it merged with Law and Policy, Income Security Programs.</data><data key="node_observed_status">historical_2018_to_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0015"><data key="node_entity_id">R197_E0015</data><data key="node_entity_type">legal_review_process</data><data key="node_canonical_name">SSA Data Exchange Agreement-Type Legal Review</data><data key="node_domain">Privacy / Data Exchange</data><data key="node_description">SSA Program, Fiscal and Disclosure Law and Privacy and Disclosure Law Branch select whether IEA, CMA or MOU is appropriate for proposed exchange.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0016"><data key="node_entity_id">R197_E0016</data><data key="node_entity_type">data_artifact</data><data key="node_canonical_name">SSA-157 Data Exchange Request Legal/Volume/Security Metadata</data><data key="node_domain">Data Exchange Governance</data><data key="node_description">New/expanded request must describe requested data, legal authority, projected volume/frequency, safeguards and previous exchange agreements.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0017"><data key="node_entity_id">R197_E0017</data><data key="node_entity_type">policy_rule</data><data key="node_canonical_name">PPDX Programmatic Versus Administrative Sharing Classification</data><data key="node_domain">Data Exchange Governance</data><data key="node_description">March 2026 POMS excludes administrative payroll sharing and manual transfers from PPDX programmatic exchange definition.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0018"><data key="node_entity_id">R197_E0018</data><data key="node_entity_type">service_pattern</data><data key="node_canonical_name">SSA Real-Time Data Exchange Service Category</data><data key="node_domain">Data Exchange Governance</data><data key="node_description">POMS defines online/web or terminal query followed by immediate sharing of relevant data; not claim that any named exchange uses real-time.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0019"><data key="node_entity_id">R197_E0019</data><data key="node_entity_type">service_pattern</data><data key="node_canonical_name">SSA Overnight Batch Data Exchange Service Category</data><data key="node_domain">Data Exchange Governance</data><data key="node_description">POMS defines generally high-volume grouped overnight information sharing, in contrast with immediate queries.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0020"><data key="node_entity_id">R197_E0020</data><data key="node_entity_type">research_data_product</data><data key="node_canonical_name">CPS/ASEC Linked SSA Detailed Earnings Record Research Series (2005–2021)</data><data key="node_domain">Earnings / Research</data><data key="node_description">Restricted-use linked worker-year samples across nine CPS/ASEC survey files selected 2005–2021 matched to SSA DER for comparison of employer-reported wages and survey responses.</data><data key="node_observed_status">historical_research_2024</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0021"><data key="node_entity_id">R197_E0021</data><data key="node_entity_type">research_data_element</data><data key="node_canonical_name">CPS/ASEC WSAL_VAL Self-Reported Wage and Salary Attribute</data><data key="node_domain">Earnings / Research</data><data key="node_description">Census CPS/ASEC wage/salary WSAL_VAL variable; survey response or imputation, not SSA administrative earnings posting.</data><data key="node_observed_status">historical_research_2024</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0022"><data key="node_entity_id">R197_E0022</data><data key="node_entity_type">research_data_element</data><data key="node_canonical_name">DER W-2 Box 5 Medicare-Taxable Compensation Measure</data><data key="node_domain">Earnings / Research</data><data key="node_description">SSA Detailed Earnings Record wage measure derived from Form W-2 Box 5; includes certain deferred compensation and may differ from self-reported CPS wages.</data><data key="node_observed_status">historical_research_2024</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0023"><data key="node_entity_id">R197_E0023</data><data key="node_entity_type">research_scope_rule</data><data key="node_canonical_name">2024 CPS/DER Wages-Only Study Scope (No Schedule SE)</data><data key="node_domain">Earnings / Research</data><data key="node_description">2024 comparative study excludes self-employment income reported to IRS on Form 1040 Schedule SE, since filing rules and error sources differ.</data><data key="node_observed_status">historical_research_2024</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0024"><data key="node_entity_id">R197_E0024</data><data key="node_entity_type">research_quality_control</data><data key="node_canonical_name">2024 CPS/DER Survey Imputation and Item-Nonresponse Caveat</data><data key="node_domain">Earnings / Research</data><data key="node_description">Linked comparison warns survey nonresponse and imputed wages change the interpretation of differences from employer-reported W-2 amounts.</data><data key="node_observed_status">historical_research_2024</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R197_E0025"><data key="node_entity_id">R197_E0025</data><data key="node_entity_type">statistical_publication</data><data key="node_canonical_name">SSA Research and Statistics Note 2024-01 CPS versus DER Earnings</data><data key="node_domain">Statistics / Publication</data><data key="node_description">March 2024 publication analyzes linked CPS/ASEC vs SSA DER differences for workers age 18–69 and publishes charts and regression tables.</data><data key="node_observed_status">published_2024</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0001"><data key="node_entity_id">R198_E0001</data><data key="node_entity_type">operational_update_rule</data><data key="node_canonical_name">Medical CDR Reconsideration EDCS Transfer Auto-Posting to DCF and MBR</data><data key="node_domain">Disability / Title II</data><data key="node_description">For routine electronic Title II medical CDR appeals EDCS transfer updates DCF and MBR automatically; source specifies this named workflow, not universal EDCS synchronization.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0002"><data key="node_entity_id">R198_E0002</data><data key="node_entity_type">control</data><data key="node_canonical_name">Medical CDR Five-Day MBR/SSR Post-Decision Update Verification</data><data key="node_domain">Disability / Claims</data><data key="node_description">FO verifies post-determination MBR/SSR update within five days; missed MBR update triggers DIBCESS/PCACS review, missed SSR update manual work.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0003"><data key="node_entity_id">R198_E0003</data><data key="node_entity_type">data_exchange_process</data><data key="node_canonical_name">CDR Appeal Update-After-Transfer (UAT) Address Notification</data><data key="node_domain">Disability / Address Provenance</data><data key="node_description">For a claimant-reported address or phone change after folder release FO updates applicable benefit and EDCS records and sends UAT to DDS/DHU; not an outside-source master-record refresh.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0004"><data key="node_entity_id">R198_E0004</data><data key="node_entity_type">manual_control</data><data key="node_canonical_name">CDR Appeal Change of Hearing Site Address Escalation</data><data key="node_domain">Disability / Address Provenance</data><data key="node_description">If changed address changes hearing DDS/DHU site, FO also phones the DHU and follows with an email to be associated with case folder.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0005"><data key="node_entity_id">R198_E0005</data><data key="node_entity_type">exception_workflow</data><data key="node_canonical_name">CDR Appeal DCF Missing-Update Problem Report Control</data><data key="node_domain">Disability / Operations</data><data key="node_description">Where postdecision MBR automatic update fails and no PCACS DIBCESS issue or THIS exception appears, FO submits DCF problem report through established channels.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0006"><data key="node_entity_id">R198_E0006</data><data key="node_entity_type">operational_update_rule</data><data key="node_canonical_name">CDR Reconsideration Title XVI MSSICS-to-EDCS Appeal Data Propagation</data><data key="node_domain">Disability / Title XVI</data><data key="node_description">For SSI CDR reconsideration appeal MSSICS records SSR appeal and SBC election; employees verify appeal information propagated into EDCS before transfer.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0007"><data key="node_entity_id">R198_E0007</data><data key="node_entity_type">processing_rule</data><data key="node_canonical_name">PUPS T2R Pending Suspension Due-Process 15-or-35-Day Window</data><data key="node_domain">Title II / Program Integrity</data><data key="node_description">PUPS title II suspend event is deferred until 15 or 35 days following notice, then T2R attempts MBR LAF S7 update. Filing does not cause immediate suspend.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0008"><data key="node_entity_id">R198_E0008</data><data key="node_entity_type">state_feedback_rule</data><data key="node_canonical_name">PUPS T2R MBR-to-Prisoner-Record Suspension Feedback</data><data key="node_domain">Title II / Program Integrity</data><data key="node_description">When MBR reflects LAF S7, PUPS receives feedback and closes prisoner status to SUSPENSION; exceptions can remain pending even if an MBR change was made.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0009"><data key="node_entity_id">R198_E0009</data><data key="node_entity_type">exception_workload</data><data key="node_canonical_name">PUPS T2R PCACS Prison-or-PRISUS TOEL Exception</data><data key="node_domain">Title II / Program Integrity</data><data key="node_description">When T2R cannot post prisoner suspension to MBR a PCACS action-control record may contain PRISON or PRISUS TOEL2 and related THIS control.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0010"><data key="node_entity_id">R198_E0010</data><data key="node_entity_type">manual_workflow</data><data key="node_canonical_name">PUPS T2R Exception 2790-FAX Processing-Center Fallback</data><data key="node_domain">Title II / Program Integrity</data><data key="node_description">For missing/failed PCACS exception or unposted MBR suspension FO uses a manual 2790-FAX follow-up and transfers PUPS prisoner record to processing center.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0011"><data key="node_entity_id">R198_E0011</data><data key="node_entity_type">external_exchange_data</data><data key="node_canonical_name">BOP Monthly New-and-Transferred-Inmate Report to SSA</data><data key="node_domain">Program Integrity / Federal Prison</data><data key="node_description">BOP monthly data include new inmate admissions and facility movements under reporting agreement, plus conviction/pretrial/probation states.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0012"><data key="node_entity_id">R198_E0012</data><data key="node_entity_type">transformation_rule</data><data key="node_canonical_name">PUPS 3-Digit BOP Facility to 6-Digit IRCS Facility ID Mapping</data><data key="node_domain">Program Integrity / Location Provenance</data><data key="node_description">PUPS converts incoming BOP three-digit facility code into a six-digit facility ID on IRCS for display; facility describes custody location or destination, not claimant residence.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0013"><data key="node_entity_id">R198_E0013</data><data key="node_entity_type">identity_evidence_control</data><data key="node_canonical_name">BOP Inmate Match Event Verification (EVS) Code Gate</data><data key="node_domain">Person/Identity / Program Integrity</data><data key="node_description">PUPS BOP alerts with EVS codes 2,3,4,A,B,E,F require identity verification, whereas V and L are generally treated as valid matches.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0014"><data key="node_entity_id">R198_E0014</data><data key="node_entity_type">address_classification_rule</data><data key="node_canonical_name">BOP Monthly Confinement Facility Move Is Not Residence Update</data><data key="node_domain">Address Provenance / Program Integrity</data><data key="node_description">BOP facility code can change month to month in transfer/in-transit reporting; it is custody-site information, not verified home mailing or residence address.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0015"><data key="node_entity_id">R198_E0015</data><data key="node_entity_type">data_quality_constraint</data><data key="node_canonical_name">BOP Prisoner Report Missing Release-Date Attribute</data><data key="node_domain">Program Integrity / External Data</data><data key="node_description">SSA POMS expressly says BOP does not provide inmate release dates in monthly PUPS reporting; source supplies confinement-related data instead.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0016"><data key="node_entity_id">R198_E0016</data><data key="node_entity_type">identity_evidence_control</data><data key="node_canonical_name">SSI IRS Alert Payer Identity EIN-versus-SSN Collision Review</data><data key="node_domain">IRS / Person/Identity</data><data key="node_description">For alerts naming a payee with company EIN digits resembling recipient SSN, employees compare name/address and obtain DEQY to determine legal payer identity; no direct IRS contact.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0017"><data key="node_entity_id">R198_E0017</data><data key="node_entity_type">address_resolution_rule</data><data key="node_canonical_name">SSI IRS Alert Blank or Implausible Payer Address Resolution</data><data key="node_domain">IRS / Address Provenance</data><data key="node_description">If payer address/name blank or unlikely, SSA instructions use payer EIN on DEQY to identify payer; do not ask IRS directly for payer name/address.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0018"><data key="node_entity_id">R198_E0018</data><data key="node_entity_type">historical_reference_data</data><data key="node_canonical_name">BFS Pre-1974 Savings Bond Name-and-Original-Address Registration Index</data><data key="node_domain">Treasury / Address Provenance</data><data key="node_description">For series E savings bond issued before Jan 1974 Treasury registration can be indexed by owner name/address at purchase; historic location is not current residence.</data><data key="node_observed_status">documented_historical_past</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0019"><data key="node_entity_id">R198_E0019</data><data key="node_entity_type">historical_reference_data</data><data key="node_canonical_name">BFS Post-1973 Savings Bond Owner-SSN Registration Index</data><data key="node_domain">Treasury / Person/Identity</data><data key="node_description">From January 1974 Series E and series EE,H,HH bond registration uses owner or first joint owner SSN rather than pre-1974 name/address basis.</data><data key="node_observed_status">documented_historical_past</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0020"><data key="node_entity_id">R198_E0020</data><data key="node_entity_type">manual_verification_process</data><data key="node_canonical_name">IRS Farm-Subsidy Alert FSA County-Payer Verification Referral</data><data key="node_domain">Title XVI / External Exchange</data><data key="node_description">For ambiguous agricultural subsidies FO contacts county agricultural agency, or FSA via parallel office to determine appropriate county from payee account number.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0021"><data key="node_entity_id">R198_E0021</data><data key="node_entity_type">external_data_attribute</data><data key="node_canonical_name">BFS Savings Securities Book-Entry Account Number Alert Attribute</data><data key="node_domain">Treasury / Title XVI</data><data key="node_description">2026 SB alert may contain account number for electronic book-entry savings security, alongside series, issue date, redemption value and valuation return date.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0022"><data key="node_entity_id">R198_E0022</data><data key="node_entity_type">batch_match_control</data><data key="node_canonical_name">SSI SB Diary Two-Prior-Match Duplicate Suppression Rule</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">SB diary controlled when combined redemption value is &gt;= $1,000 and no alert issued in previous two matches; historic semiannual cadence is described.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0023"><data key="node_entity_id">R198_E0023</data><data key="node_entity_type">identity_evidence_control</data><data key="node_canonical_name">SSI Savings Security Owner-Name Overrides Registration SSN Evidence Rule</data><data key="node_domain">Person/Identity / Resources</data><data key="node_description">POMS ownership is individual whose name appears on instrument regardless of SSN printed on it; a numeric SSN match is not proof of ownership.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0024"><data key="node_entity_id">R198_E0024</data><data key="node_entity_type">verified_record_update</data><data key="node_canonical_name">SSI Savings Security DSAB-to-SSR Diary Clearance Control</data><data key="node_domain">Title XVI / Resource Verification</data><data key="node_description">Employee documents savings-security ownership and values in MSSICS DSAB/stock screens or non-MSSICS SSR remarks; clearing diary is controlled action, not raw BFS auto-post.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0025"><data key="node_entity_id">R198_E0025</data><data key="node_entity_type">annual_batch_rule</data><data key="node_canonical_name">SSI E2 Diary Annual-COLA Rental Subsidy Generation Gate</data><data key="node_domain">Title XVI / Living Arrangement</data><data key="node_description">Annual COLA run sets E2 diary when current LA rental subsidy &gt;0 and SSR payment status is C01, M02 or N01.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0026"><data key="node_entity_id">R198_E0026</data><data key="node_entity_type">historical_processing_rule</data><data key="node_canonical_name">SSI Rental Subsidy September 30 2024 Transition State Exception</data><data key="node_domain">Title XVI / Living Arrangement</data><data key="node_description">2025 COLA fix requires new LA period dated Sept 30 2024 outside named seven states; triggered based on existing residence state field and rental subsidy amount.</data><data key="node_observed_status">historical_transition_2024</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0027"><data key="node_entity_id">R198_E0027</data><data key="node_entity_type">application_validation</data><data key="node_canonical_name">SSI Rental Subsidy Three-System-Edit Annual LA Period Controls</data><data key="node_domain">Title XVI / Living Arrangement</data><data key="node_description">SSA specifies edits for transition-period omission, missing January COLA LA period, and closure with missing transition period on applicable MSSICS pages.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0028"><data key="node_entity_id">R198_E0028</data><data key="node_entity_type">payment_calculation_rule</data><data key="node_canonical_name">SSI Rental Subsidy COLA CMRV and PMV Recalculation</data><data key="node_domain">Title XVI / Living Arrangement</data><data key="node_description">After clerk creates new LA period, system recalculates rental subsidy using Presumed Maximum Value and Current Market Rental Value based on verified monthly rent.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0029"><data key="node_entity_id">R198_E0029</data><data key="node_entity_type">identity_record_control</data><data key="node_canonical_name">SSI Duplicate-Record Two-SSN M1 Cross-Reference Posting</data><data key="node_domain">Person/Identity / Title XVI</data><data key="node_description">When same-person duplicate SSR records generate payments, FO terminates wrong record T20 and cross-records SSNs in M1 fields of both records; MA field if assigned through enumeration.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0030"><data key="node_entity_id">R198_E0030</data><data key="node_entity_type">manual_data_correction</data><data key="node_canonical_name">SSI Duplicate Record No-Payment T50 Cleanup and MSSICS MANCLR</data><data key="node_domain">Title XVI / Person/Identity</data><data key="node_description">Incorrect duplicate SSR records without duplicate payment use T50; unarchived MSSICS pending file is manually cleared before T50 coding.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0031"><data key="node_entity_id">R198_E0031</data><data key="node_entity_type">match_processing_rule</data><data key="node_canonical_name">MEF K6-K7 SSI Earned-Income Diary Suppression and Threshold Control</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">K6 annual MEF earnings exceed SSR by $1000 when eligible by January; K7 deemor special &gt;=$2000 and amended/no SSR earnings; status or existing diary can suppress alerts.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0032"><data key="node_entity_id">R198_E0032</data><data key="node_entity_type">employer_address_observation</data><data key="node_canonical_name">MEF K6-K7 DEQY Employer Name-and-Address Evidence Lookup</data><data key="node_domain">Earnings / Address Provenance</data><data key="node_description">FO requests DEQY to obtain MEF wage amounts, employer name and address for K6/K7 development; employer location is not recipient residence.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0033"><data key="node_entity_id">R198_E0033</data><data key="node_entity_type">information_request_product</data><data key="node_canonical_name">IRS Tax Return Request Cover-Letter and Second-Page PII Template</data><data key="node_domain">IRS / Earnings Evidence</data><data key="node_description">SSA IRS request must be signed by authorized manager and include taxpayer name/address and TIN, tax schedule requested and filing date if known.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0034"><data key="node_entity_id">R198_E0034</data><data key="node_entity_type">external_evidence_product</data><data key="node_canonical_name">IRS Account-or-Return Transcript Written Response for SSA</data><data key="node_domain">IRS / Earnings Evidence</data><data key="node_description">IRS may return account or return transcripts in response to authorized written earnings/self-employment investigation request; 30-day allowance.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0035"><data key="node_entity_id">R198_E0035</data><data key="node_entity_type">retention_scope_rule</data><data key="node_canonical_name">IRS Seven-Year Self-Employment Audit-Adjustment Information Window</data><data key="node_domain">IRS / Earnings Evidence</data><data key="node_description">POMS says IRS will also provide audit adjustments within last seven years resulting in self-employment income or tax change; not general IRS data retention period.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0036"><data key="node_entity_id">R198_E0036</data><data key="node_entity_type">governance_rule</data><data key="node_canonical_name">SASRO Single-Query State Record Legal-Use and Master-Update Boundary</data><data key="node_domain">External Exchanges / Address Provenance</data><data key="node_description">State IEA allows one electronic query and use of state information to update SSA files or assign SSNs or verify eligibility; source does not identify which address field is overwritten.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R198_E0037"><data key="node_entity_id">R198_E0037</data><data key="node_entity_type">procurement_governance_document</data><data key="node_canonical_name">SSA IT Procurement Security and General Privacy Requirements January 2026</data><data key="node_domain">Acquisition / Security</data><data key="node_description">SSA OAG publishes January 2026 standardized IT procurement security and general privacy requirements; publication alone not evidence a particular contract uses a specific version.</data><data key="node_observed_status">documented_policy_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0001"><data key="node_entity_id">R199_E0001</data><data key="node_entity_type">logical_file</data><data key="node_canonical_name">Internet Disability Report Active File</data><data key="node_domain">Disability / Online Intake</data><data key="node_description">The active file houses editable, unsubmitted IDR data; submission or archive ends user editability.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">A logically described file; underlying physical platform and 2026 status not established.</data></node><node id="R199_E0002"><data key="node_entity_id">R199_E0002</data><data key="node_entity_type">logical_file</data><data key="node_canonical_name">Internet Disability Report Inactive Archive File</data><data key="node_domain">Disability / Evidence Retention</data><data key="node_description">Inactive file stores archived reports, accessible to field office query until purge but ineligible for EDCS propagation.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not infer general SSA retention policy from this report-specific historical rule.</data></node><node id="R199_E0003"><data key="node_entity_id">R199_E0003</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IDR Active-to-Inactive Archive Transition</data><data key="node_domain">Disability / Evidence Retention</data><data key="node_description">Archived IDRs move from active file to separate inactive storage after documented triggers, barring further EDCS automatic propagation.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0004"><data key="node_entity_id">R199_E0004</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">IDR i3441 Ninety-Day Archive Trigger</data><data key="node_domain">Disability / Evidence Retention</data><data key="node_description">A 2014 POMS rule archives an i3441 90 days after the internet user started the report.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0005"><data key="node_entity_id">R199_E0005</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">IDR i3368 and i3820 Protective-Filing Expiration Archive Trigger</data><data key="node_domain">Disability / Evidence Retention</data><data key="node_description">For i3368 and i3820, an archive trigger occurs 30 days after expiration of the protective filing period.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0006"><data key="node_entity_id">R199_E0006</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">IDR Archived Inactive 120-Day Purge Rule</data><data key="node_domain">Disability / Evidence Retention</data><data key="node_description">POMS documents automatic purge after an IDR remains in the inactive archive for 120 days.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0007"><data key="node_entity_id">R199_E0007</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">IDR Archived Record EDCS Propagation Prohibition</data><data key="node_domain">Disability / Electronic Evidence</data><data key="node_description">EDCS cannot propagate archived IDRs into an EDCS claim; FO Internet Query Facility access may remain until purge.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0008"><data key="node_entity_id">R199_E0008</data><data key="node_entity_type">record_grouping_rule</data><data key="node_canonical_name">IDR Same-SSN Same-Form Same-Protective-Date Record Set</data><data key="node_domain">Disability / Data Integrity</data><data key="node_description">IDR set-of-records groups reports of the same type, SSN and protective filing date for joint archive or purge.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0009"><data key="node_entity_id">R199_E0009</data><data key="node_entity_type">identity_access_attribute</data><data key="node_canonical_name">IDR Reentry Number Secret</data><data key="node_domain">Disability / Online Identity</data><data key="node_description">Random reentry number for a partial IDR; SSA employees cannot retrieve a lost number under 2014 instructions.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Access credential, not an authoritative SSN or reusable enterprise person identifier.</data></node><node id="R199_E0010"><data key="node_entity_id">R199_E0010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">IDR Final Submission Record Lock</data><data key="node_domain">Disability / Online Intake</data><data key="node_description">Selecting Submit finally transmits an IDR, locks the source record against user editing and permits EDCS propagation.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0011"><data key="node_entity_id">R199_E0011</data><data key="node_entity_type">data_collection_rule</data><data key="node_canonical_name">IDR Provider City-and-State Minimum Entry</data><data key="node_domain">Disability / Provider Information</data><data key="node_description">2014 IDR intake requires doctor first and last names plus city and state but not full address for specified medical provider responses.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Partial provider-location data; not a verified complete provider address.</data></node><node id="R199_E0012"><data key="node_entity_id">R199_E0012</data><data key="node_entity_type">access_control</data><data key="node_canonical_name">IDR Archive Query-Only Field Office Access</data><data key="node_domain">Disability / Evidence Retention</data><data key="node_description">The Internet Query Facility may query or print archived IDR records until purged, but cannot reactivate them for EDCS.</data><data key="node_observed_status">documented_2014</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R199_E0013"><data key="node_entity_id">R199_E0013</data><data key="node_entity_type">system_limitation</data><data key="node_canonical_name">iWMI Follow-Up Tracking Not Automated</data><data key="node_domain">Disability / Workload Management</data><data key="node_description">POMS DI 81007.080 states Internet WMI listing system lacks automated follow-up; unresolved SSNs can remain in its listing.</data><data key="node_observed_status">documented_2017</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Existing source SRC418 reused; no claim regarding 2026 modernization.</data></node><node id="R199_E0014"><data key="node_entity_id">R199_E0014</data><data key="node_entity_type">control_field</data><data key="node_canonical_name">iWMI Internet Query IZ60 Delete Flag and Purge Marker</data><data key="node_domain">Disability / Workload Management</data><data key="node_description">The internet query Delete This Report flag marks the IDR for eventual purge and disables EDCS propagation pending reversal.</data><data key="node_observed_status">documented_2017</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Marking does not immediately delete the record.</data></node><node id="R199_E0015"><data key="node_entity_id">R199_E0015</data><data key="node_entity_type">retention_control</data><data key="node_canonical_name">iWMI Seven-Day Delete Flag Reversal Window</data><data key="node_domain">Disability / Workload Management</data><data key="node_description">POMS DI 81007.080 states an incorrect Delete This Report Y must be removed within seven days to prevent report purge.</data><data key="node_observed_status">documented_2017</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Window documented in 2017 policy; not universal retention rule.</data></node><node id="R199_E0016"><data key="node_entity_id">R199_E0016</data><data key="node_entity_type">workload_product</data><data key="node_canonical_name">iWMI Next-Day Submitted IDR Listing</data><data key="node_domain">Disability / Workload Management</data><data key="node_description">The Submitted Disability Reports Listing displays the submitted report SSN on the day after the internet user submits the IDR.</data><data key="node_observed_status">documented_2017</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">This is an SSN appearing on a work listing, not independent evidence of medical eligibility.</data></node><node id="R199_E0017"><data key="node_entity_id">R199_E0017</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">i3368 Existing DDS Case Propagation Exclusion</data><data key="node_domain">Disability / Electronic Case Development</data><data key="node_description">When another case for the claimant is pending at DDS, normal i3368 propagation into EDCS is not possible under specified conditions.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Use manual comparison and Update After Transfer; not all disability case paths are affected.</data></node><node id="R199_E0018"><data key="node_entity_id">R199_E0018</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">i3368 DDS-Pending Update After Transfer Exception</data><data key="node_domain">Disability / Evidence Exchange</data><data key="node_description">FO obtains internet query/printout, compares i3368 with EDCS 3368 and records discrepancies or new information via EDCS UAT.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented exception path rather than routine propagation.</data></node><node id="R199_E0019"><data key="node_entity_id">R199_E0019</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">i3368 Unsubmitted Partial Manual EDCS Transcription</data><data key="node_domain">Disability / Evidence Intake</data><data key="node_description">Where an i3368 partial cannot be reentered and submitted, FO queries and prints the partial and manually transcribes information into EDCS.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No automatic EDCS import of a partial established.</data></node><node id="R199_E0020"><data key="node_entity_id">R199_E0020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">i3368 iClaim Submission-First Gate</data><data key="node_domain">Disability / Online Intake</data><data key="node_description">From 2014-01-25, an internet user cannot submit i3368 without first submitting iClaim; previously standalone.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Historical transition already in Atlas modernization history; new entity captures transaction precondition.</data></node><node id="R199_E0021"><data key="node_entity_id">R199_E0021</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">i3368 MCS-MSSICS Claim Prior to EDCS Intake Gate</data><data key="node_domain">Disability / Intake Data Lineage</data><data key="node_description">Under DI 81007.035 an existing MCS or MSSICS claim precedes establishing EDCS case and propagating i3368, barring legacy pipeline exceptions.</data><data key="node_observed_status">documented_2023</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Different product repositories, no shared physical database implied.</data></node><node id="R199_E0022"><data key="node_entity_id">R199_E0022</data><data key="node_entity_type">earnings_correction_rule</data><data key="node_canonical_name">Post-Time-Limit Misattributed Wage Transfer</data><data key="node_domain">Earnings / Program Integrity</data><data key="node_description">SSA may revise records after the time limit to transfer incorrectly attributed wages to the appropriate worker or period without changing the overall recorded amount.</data><data key="node_observed_status">documented_2009</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">2009 POMS policy; applicability subject to cited statute.</data></node><node id="R199_E0023"><data key="node_entity_id">R199_E0023</data><data key="node_entity_type">earnings_correction_rule</data><data key="node_canonical_name">Unidentified Worker Wage Suspense Transfer</data><data key="node_domain">Earnings / Program Integrity</data><data key="node_description">Wages determined to belong to an unidentified worker transfer from a numberholder record to the earnings suspense file.</data><data key="node_observed_status">documented_2009</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Requires establishment of misattribution; not automatic reassignment to a named worker.</data></node><node id="R199_E0024"><data key="node_entity_id">R199_E0024</data><data key="node_entity_type">earnings_correction_rule</data><data key="node_canonical_name">Misattributed Self-Employment Income Reallocation</data><data key="node_domain">Earnings / Program Integrity</data><data key="node_description">After time limit, SEI incorrectly credited to an individual may be credited to another when original allocation is demonstrably wrong; existing amount is redistributed.</data><data key="node_observed_status">documented_2009</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">SEI is self-employment income, not Supplemental Security Income; no new tax return automatically required under cited section.</data></node><node id="R199_E0025"><data key="node_entity_id">R199_E0025</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">ICOR Wrong-Period or Wrong-Worker Earnings Correction Action</data><data key="node_domain">Earnings / Systems</data><data key="node_description">Item Correction (ICOR) is prescribed to move wages between workers, periods, or into or out of the suspense file under applicable correction rules.</data><data key="node_observed_status">documented_2009</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Source does not specify transaction transport, physical MEF write mechanism or 2026 deployment.</data></node><node id="R199_E0026"><data key="node_entity_id">R199_E0026</data><data key="node_entity_type">historical_business_rule</data><data key="node_canonical_name">BOND eWork Participation-Specific Notice Suppression</data><data key="node_domain">Disability / Historic Demonstrations</data><data key="node_description">During BOND participation, eWork changed notice behavior to avoid incorrect notices and generated BOND-specific explanatory paragraphs.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">This demonstration ended; not current general eWork notice rule.</data></node><node id="R199_E0027"><data key="node_entity_id">R199_E0027</data><data key="node_entity_type">historical_business_rule</data><data key="node_canonical_name">BOND DCF DEMO Participation End-Date Work Review Gate</data><data key="node_domain">Disability / Historic Demonstrations</data><data key="node_description">At participant exit, eWork historical work review started in month following BOND end date on DCF DEMO screen.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">POMS states BOND ended and L5R no longer operates.</data></node><node id="R199_E0028"><data key="node_entity_id">R199_E0028</data><data key="node_entity_type">historical_business_rule</data><data key="node_canonical_name">BOND Title XVI Independent Address and Earnings Maintenance</data><data key="node_domain">Title XVI / Historic Demonstrations</data><data key="node_description">POMS explicitly allows ordinary FO SSI address, wage and living-arrangement updates for concurrent BOND beneficiaries independent of the demonstration work-review restrictions.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No inference of automatic Title II-Title XVI synchronization.</data></node><node id="R199_E0029"><data key="node_entity_id">R199_E0029</data><data key="node_entity_type">historical_status</data><data key="node_canonical_name">BOND L5R Closed Processing and Unavailable Review Data</data><data key="node_domain">Disability / Historic Demonstrations</data><data key="node_description">POMS now states the demonstration is over, L5R office is no longer operating and requisite BOND review data unavailable.</data><data key="node_observed_status">historical_obsolete</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not execute historical L5R routing instructions as active workflows.</data></node><node id="R200_E001"><data key="node_entity_id">R200_E001</data><data key="node_entity_type">operational_transaction</data><data key="node_canonical_name">SSNAP SAVE Initial Verification Immediate Response</data><data key="node_domain">Enumeration / Identity</data><data key="node_description">SSNAP sends SAVE initial verification in the SSN application path and retrieves the immediate response; critical identity attributes are matched.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E002"><data key="node_entity_id">R200_E002</data><data key="node_entity_type">manual_workflow</data><data key="node_canonical_name">SSNAP SAVE Additional Verification Manual Response Retrieval</data><data key="node_domain">Enumeration / Identity</data><data key="node_description">SAVE Additional Verification is electronic, but the returned AV record does not automatically propagate into SSNAP; FO must query received responses and update the SSN application.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E003"><data key="node_entity_id">R200_E003</data><data key="node_entity_type">manual_workflow</data><data key="node_canonical_name">SSNAP SAVE Third-Level Manual Response Retrieval</data><data key="node_domain">Enumeration / Identity</data><data key="node_description">FO must retrieve receipted electronic third-level SAVE responses through the SSNAP worklist, then update the pending application to import the response.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E004"><data key="node_entity_id">R200_E004</data><data key="node_entity_type">identity_business_rule</data><data key="node_canonical_name">SSNAP SAVE Critical Identifier Selection for IV and AV</data><data key="node_domain">Enumeration / Identity</data><data key="node_description">When both A-number and I-94 are entered, SSNAP uses A-number for IV and I-94 number in AV, per documented verification path.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E005"><data key="node_entity_id">R200_E005</data><data key="node_entity_type">identity_business_rule</data><data key="node_canonical_name">SSNAP SAVE Verification Suspect-to-Verified Status Gate</data><data key="node_domain">Enumeration / Identity</data><data key="node_description">SSNAP matches critical data and updates evidence from Suspect to Verified only when applicable SAVE response satisfies verification.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E006"><data key="node_entity_id">R200_E006</data><data key="node_entity_type">historical_integration_exception</data><data key="node_canonical_name">Discontinued WRAPS Fax Verification Retained in SSNAP User Path</data><data key="node_domain">Enumeration / Identity</data><data key="node_description">February 2025 POMS says the WRAPS fax verification process is no longer used although WRAPS questions and prompts may still appear in SSNAP.</data><data key="node_observed_status">obsolete_workflow_UI_retained</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E007"><data key="node_entity_id">R200_E007</data><data key="node_entity_type">manual_workflow</data><data key="node_canonical_name">SSNAP WRAPS Prompt Workaround to SAVE Additional Verification</data><data key="node_domain">Enumeration / Identity</data><data key="node_description">If legacy WRAPS screens appear following unsuccessful SAVE initial response, FO traverses the prompts and reopens application in update mode to trigger SAVE additional verification.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E008"><data key="node_entity_id">R200_E008</data><data key="node_entity_type">identity_evidence_product</data><data key="node_canonical_name">Refugee SSN Evidence Combination CBP I-94 and DOS Boarding Letter</data><data key="node_domain">Enumeration / Identity</data><data key="node_description">Refugee SSN evidence may comprise CBP I-94 online printout plus DOS transportation boarding letter with admission stamp; select prescribed SSNAP proof type.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E009"><data key="node_entity_id">R200_E009</data><data key="node_entity_type">automated_business_process</data><data key="node_canonical_name">RETAP Monthly Medicare HI and SMI Entitlement Posting</data><data key="node_domain">Title II / Medicare</data><data key="node_description">Regular Transcript Attainment and Selection Pass runs monthly; about four months before age 65 or 25th disability month, posts HI and SMI entitlement on MBR in eligible domestic jurisdictions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E010"><data key="node_entity_id">R200_E010</data><data key="node_entity_type">eligibility_business_rule</data><data key="node_canonical_name">RETAP Puerto Rico and Foreign Address HI-Only Exception</data><data key="node_domain">Medicare / Address Provenance</data><data key="node_description">RETAP establishes only Medicare HI for Puerto Rico and foreign residence; does not automatically enroll the beneficiary in SMI.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E011"><data key="node_entity_id">R200_E011</data><data key="node_entity_type">publication_and_notice_workflow</data><data key="node_canonical_name">CMS Domestic Initial Enrollment Period Package Fulfillment</data><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">SSA sends HI/SMI entitlement data to CMS; CMS mails domestic Medicare initial-enrollment materials about three months before entitlement month.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E012"><data key="node_entity_id">R200_E012</data><data key="node_entity_type">postentitlement_workflow</data><data key="node_canonical_name">Medicare SMI Refusal and CMS Replacement Card Sequence</data><data key="node_domain">Medicare / External Exchanges</data><data key="node_description">Beneficiary may refuse automatically enrolled SMI; SSA processes refusal and CMS issues revised HI-only Medicare card.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E013"><data key="node_entity_id">R200_E013</data><data key="node_entity_type">operational_form</data><data key="node_canonical_name">SSA-409 Post-Adjudicative Routing Form</data><data key="node_acronym">SSA-409</data><data key="node_domain">Disability / Evidence / PC Routing</data><data key="node_description">SSA-409 identifies actionable non-medical eView evidence and the required PC action/TOEL; the form is faxed to Paperless Processing Center.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E014"><data key="node_entity_id">R200_E014</data><data key="node_entity_type">routing_limitation</data><data key="node_canonical_name">eView Evidence Storage Does Not Automatically Alert Processing Center</data><data key="node_domain">Disability / Evidence / PC Routing</data><data key="node_description">POMS explicitly says eView filing does not trigger a PC alert; FO must fax SSA-409 separately to PC Paperless system.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E015"><data key="node_entity_id">R200_E015</data><data key="node_entity_type">document_authority_rule</data><data key="node_canonical_name">EDCS Disability Report Official Record With Paper Exclusion</data><data key="node_domain">Disability / Evidence</data><data key="node_description">For standard EDCS cases, EDCS report is official and paper destroyed after entry; in EDCS exclusion cases paper report is authoritative and filed in Modular Disability Folder.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E016"><data key="node_entity_id">R200_E016</data><data key="node_entity_type">identity_document_linkage_rule</data><data key="node_canonical_name">eView Auxiliary Beneficiary Post-Entitlement Document Indexing Rule</data><data key="node_domain">Person / Disability Evidence</data><data key="node_description">Non-disabled auxiliary PE records use number holder SSN; disabled CDB/DWB auxiliary PE materials use beneficiary own account number.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E017"><data key="node_entity_id">R200_E017</data><data key="node_entity_type">evidence_ingest_control</data><data key="node_canonical_name">eView Non-Medical Fax Barcode Filing and Page Verification</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Employees generate barcode, fax to Regional DMA and inspect eView to verify pages before destroying ordinary paper copies.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E018"><data key="node_entity_id">R200_E018</data><data key="node_entity_type">quality_review_business_rule</data><data key="node_canonical_name">MAQR Documentation-Deficiency-Only Medical Assessment Gate</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">Qualified federal quality reviewers may use MAQR for adult documentation deficiencies categories 41,42,44,47,81; excluded for CDR, disabled-child cases and decisional deficiencies.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E019"><data key="node_entity_id">R200_E019</data><data key="node_entity_type">quality_review_workflow</data><data key="node_canonical_name">QRCPS Medical Consultant or Psychological Consultant Referral</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">Federal reviewer submits coded case-processing referral when MC/PC review required or discretionary; reviewers address specified medical concerns and log findings.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E020"><data key="node_entity_id">R200_E020</data><data key="node_entity_type">document_provenance_rule</data><data key="node_canonical_name">DQR Final Medical Review Forms eView Upload Requirement</data><data key="node_domain">Disability / Quality Review</data><data key="node_description">FQR must upload finalized medical-review forms to eView while retaining original adjudicating medical assessments in folder audit trail.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E021"><data key="node_entity_id">R200_E021</data><data key="node_entity_type">international_payment_address_rule</data><data key="node_canonical_name">IDD Residence Country May Differ From Bank Account Country</data><data key="node_domain">Payments / Address Provenance</data><data key="node_description">October 2026 policy allows a beneficiary resident in one eligible foreign country to bank in another IDD country; resident address and bank location are separate.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E022"><data key="node_entity_id">R200_E022</data><data key="node_entity_type">international_payment_address_rule</data><data key="node_canonical_name">IDD Foreign Residence and Address Eligibility Gate</data><data key="node_domain">Payments / Address Provenance</data><data key="node_description">IDD generally requires outside-US residence and foreign address on file; moving to US ends IDD; Treasury barred-country limits apply.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E023"><data key="node_entity_id">R200_E023</data><data key="node_entity_type">identity_payment_control</data><data key="node_canonical_name">IDD Mailed Signup Requires Identity Verification Before System Update</data><data key="node_domain">Payments / Identity</data><data key="node_description">FBUs or international processors receiving SSA-1199 by mail must authenticate beneficiary before updating IDD enrollment.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E024"><data key="node_entity_id">R200_E024</data><data key="node_entity_type">address_development_process</data><data key="node_canonical_name">Treasury EFT Fraud Claim Undeliverable Mail Address Reconciliation</data><data key="node_domain">Fraud / Address Provenance</data><data key="node_description">When Treasury claim form returns undeliverable, check updated MBR/SSR address. Without a new address, Treasury does not resend and SSA must develop current address.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E025"><data key="node_entity_id">R200_E025</data><data key="node_entity_type">document_availability_rule</data><data key="node_canonical_name">TCIS EFT Claim Form and Direct Express R16 Exclusion</data><data key="node_domain">Payments / Fraud</data><data key="node_description">TCIS Integrated View lets staff print ordinary EFT claim forms, but Direct Express redirected payments use R16 request instead of stored or printed EFT form.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E026"><data key="node_entity_id">R200_E026</data><data key="node_entity_type">fraud_debt_accounting_workflow</data><data key="node_canonical_name">Treasury ENR Returned Funds DMS RRRE Credit and MBR Message</data><data key="node_domain">Debt / Payments</data><data key="node_description">PC receives Treasury FI debit report in Paperless and manually reduces or removes related Title II overpayment using DMS RRRE; posts MBR special message and reviews next workday.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E027"><data key="node_entity_id">R200_E027</data><data key="node_entity_type">fraud_debt_accounting_workflow</data><data key="node_canonical_name">SSI ENR Treasury Returned Credit SSR OPRR and PMTH Posting</data><data key="node_domain">Title XVI / Debt</data><data key="node_description">OBASA posts partial refunded amount to SSR OPRR with DOC 534 and full refund to SSR PMTH; employee reviews overpayment accounting.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E028"><data key="node_entity_id">R200_E028</data><data key="node_entity_type">tax_information_correction_workflow</data><data key="node_canonical_name">Unauthorized ENR Payment Corrected SSA-1099 Statement Procedure</data><data key="node_domain">Title II / Tax Data</data><data key="node_description">When fraudulent redirection inflated SSA-1099 amounts, PC may prepare corrected SSA-1099 including $0 statement when no funds actually received.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Documented operational/policy condition; no inference of current implementation beyond source.</data></node><node id="R200_E029"><data key="node_entity_id">R200_E029</data><data key="node_entity_type">data_processing_relationship</data><data key="node_canonical_name">Internet Direct Deposit Online Transactions Intermediate Posting to MBR</data><data key="node_domain">Title II / Online / Payments</data><data key="node_description">Open Data states my Social Security direct-deposit changes go to database and are updated to MBR; activity volume counts online transactions only, excludes field-office, phone and mailed actions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">4</data><data key="node_notes">SSA Open Data describes intermediate database without naming hosting product; no new physical system is asserted.</data></node><node id="R201_E001"><data key="node_entity_id">R201_E001</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2026 SSI Redetermination Does Not Independently Protect Title II Filing</data><data key="node_acronym">RZ/PF</data><data key="node_domain">Title II &amp; XVI / Filing</data><data key="node_description">Effective April 27, 2026, initiating an SSI redetermination or completing its form no longer independently creates a Title II protective filing date.</data><data key="node_observed_status">policy_effective_2026-04-27</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Previously initiated redeterminations are governed by archived prior policy. No implied automated MBR update.</data></node><node id="R201_E002"><data key="node_entity_id">R201_E002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2026 iAppt Protective Filing Date Auto-Posting to MCS or CCE</data><data key="node_domain">Title II &amp; XVI / Filing</data><data key="node_description">POMS GN 00204.010 describes automated propagation of iAppt protective filing dates to MCS or CCE, requiring employee verification.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">This is a defined appointment/protective-date process; separate from unverified iAppt person-data gate for CLIENT/Numident.</data></node><node id="R201_E003"><data key="node_entity_id">R201_E003</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title II MBR Filing Date Can Reflect Protective Filing Date</data><data key="node_domain">Title II &amp; XVI / Filing</data><data key="node_description">MCS permits the protective filing date to appear as the date of filing on MBR, but claim receipt date remains a separately documented application event.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not conflate signed internet submission date, date input to MCS, and protective date.</data></node><node id="R201_E004"><data key="node_entity_id">R201_E004</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Title XVI Age-65 Claim MSSICS Receipt-Date Exception</data><data key="node_domain">Title II &amp; XVI / Filing</data><data key="node_description">GN 00204.007 identifies an SSI age-65 system exception requiring application receipt date instead of protective filing date in MSSICS.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">4</data><data key="node_notes">Exact eligibility predicates require cross-reference; not a general filing-date change.</data></node><node id="R201_E005"><data key="node_entity_id">R201_E005</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">iClaim Internet Submission Receipt Date</data><data key="node_domain">Title II &amp; XVI / Filing</data><data key="node_description">Electronically signed iClaim receipt date is claimant submission date displayed on IMNU, not the subsequent MCS establishment date.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Receipt date and other protective filing dates must be distinguished.</data></node><node id="R201_E006"><data key="node_entity_id">R201_E006</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RASR Representative Direct-Contact Request Cross-Record Documentation</data><data key="node_domain">Representatives / Contacts</data><data key="node_description">RASR report of contact by itself does not populate MCS RPOC or CCE DROC; technicians manually document representatives request when directly contacting a represented claimant.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Cross-system manual duplicate entry; instructions apply to documented exceptions to representative-first contact policy.</data></node><node id="R201_E007"><data key="node_entity_id">R201_E007</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Representative Direct-Contact Report of Contact MCS RPOC Requirement</data><data key="node_domain">Representatives / Contacts</data><data key="node_description">For direct contact at representative request, technicians create RPOC in MCS as applicable in addition to RASR.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Manual action required because RASR does not automatically update MCS.</data></node><node id="R201_E008"><data key="node_entity_id">R201_E008</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Representative Direct-Contact Report of Contact CCE DROC Requirement</data><data key="node_domain">Representatives / Contacts</data><data key="node_description">For direct contact at representative request, technicians create DROC in CCE as applicable in addition to RASR.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Manual action required because RASR does not automatically update CCE.</data></node><node id="R201_E009"><data key="node_entity_id">R201_E009</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Statutory Blindness Two-Onset-Date Determination</data><data key="node_domain">Disability / Evidence</data><data key="node_description">DDS may establish a nonblind onset date and later statutory blind onset date, which can be represented separately in SSA-831.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Ordinary MCS DICL / Title XVI clearance data do not propagate the later blind onset in the described circumstance.</data></node><node id="R201_E010"><data key="node_entity_id">R201_E010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Later Statutory Blind Onset Nonpropagation to DICL and SSI Clearance</data><data key="node_domain">Disability / Evidence</data><data key="node_description">When nonblind onset predates blindness, later blind onset is in SSA-831 remarks or item 18B rather than propagated DICL/SSI disability clearance fields.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Caseworkers must review SSA-831; do not generalize to all blindness determinations.</data></node><node id="R201_E011"><data key="node_entity_id">R201_E011</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">MCS Adjusted Blind Onset Date Field</data><data key="node_acronym">ABOD</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Specific DICL date for statutory blind insured Title II claimants, controlling later payment-related onset after substantial gainful activity; may differ from medical blindness onset.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">ABOD is no earlier than statutory blind medical onset in documented use; subject to eligibility rules.</data></node><node id="R201_E012"><data key="node_entity_id">R201_E012</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">SSR Type-of-Master-Record and Recipient Blindness Codes</data><data key="node_acronym">TMR/ID</data><data key="node_domain">Title XVI / Disability</data><data key="node_description">Title XVI blind allowance can update SSR TMR and ID field, reflecting codes BI, BS, or BC according to case category.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">DDS corrections require follow-up if the expected SSR fields do not update.</data></node><node id="R201_E013"><data key="node_entity_id">R201_E013</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Pre-December-2012 Statutory Blind Diagnosis Coding</data><data key="node_domain">Disability / Historical</data><data key="node_description">Before December 1, 2012, statutory blindness cases do not use later diagnosis code 3694 and must be recognized by applicable listing codes.</data><data key="node_observed_status">historical_ended_2012</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Use proper vintage when joining 2006-2012 disability statistics.</data></node><node id="R201_E014"><data key="node_entity_id">R201_E014</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Lithuania International Direct Deposit MBR–ITS Dual Entry</data><data key="node_domain">Payments / International</data><data key="node_description">Country-specific process requires approved SSA entry for banking fields plus same-day Treasury ITS.gov enrollment; absence of ITS.gov details leads to reject.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Human-coordinated two-system transaction; do not infer a physical interface or automatic MBR-to-ITS feed.</data></node><node id="R201_E015"><data key="node_entity_id">R201_E015</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Lithuania IDD Treasury ITS Beneficiary Address</data><data key="node_acronym">LT Address</data><data key="node_domain">Address Provenance / Treasury</data><data key="node_description">Treasury ITS.gov collects country-formatted beneficiary address LT/Town/Name as part of Lithuania payment enrollment.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Payment enrollment address, not evidence of update to MBR residential attribute or Numident.</data></node><node id="R201_E016"><data key="node_entity_id">R201_E016</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Lithuania IDD International Bank Account Number</data><data key="node_acronym">IBAN</data><data key="node_domain">Payments / International</data><data key="node_description">Bank-provided Lithuanian IBAN is 20 characters under SSA POMS and is used to derive coded banking data.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not assume a complete 20-character IBAN persists in MBR fields.</data></node><node id="R201_E017"><data key="node_entity_id">R201_E017</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Lithuania IDD MBR Routing Prefix 66</data><data key="node_acronym">RTN66</data><data key="node_domain">Payments / International</data><data key="node_description">Country-specific MBR deposit routing number begins with 66 under multi-country contract and applies derived check-digit procedures.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">This is beneficiary bank routing data, not a personal identifier or residential address.</data></node><node id="R201_E018"><data key="node_entity_id">R201_E018</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Lithuania IDD Depositor Account H Country Code</data><data key="node_acronym">DAN-H</data><data key="node_domain">Payments / International</data><data key="node_description">SSA POMS directs H as first character of depositor account number field for Lithuania.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Procedural text describes 21 coded characters while enumerating H plus 11 account digits; unresolved textual inconsistency.</data></node><node id="R201_E019"><data key="node_entity_id">R201_E019</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-1199-OP34 Lithuania International Direct Deposit Sign-Up</data><data key="node_acronym">SSA-1199-OP34</data><data key="node_domain">Payments / International</data><data key="node_description">Country-specific optional direct-deposit signup form listed as one means of receiving Lithuania bank data.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Form is an intake option, not evidence of fully online self-service submission.</data></node><node id="R201_E020"><data key="node_entity_id">R201_E020</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Lithuania IDD Euro Eligibility Branch Published Conflict</data><data key="node_domain">Payments / International</data><data key="node_description">POMS requires Euro-denominated accounts but published Step 3 directs STOP when the account is in Euros, a logically inconsistent validation branch.</data><data key="node_observed_status">unresolved_source_conflict</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not implement code from contradictory published directions; request SSA confirmation. The step may be a transcription error.</data></node><node id="R201_E021"><data key="node_entity_id">R201_E021</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Lithuania IDD Treasury ITS Financial Institution Data</data><data key="node_domain">Payments / International</data><data key="node_description">ITS.gov separately captures account ownership, account type, IBAN, SWIFT-BIC, payee status and other bank routing information.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Bank location, beneficiary residence and account-routing details are separate concepts.</data></node><node id="R201_E022"><data key="node_entity_id">R201_E022</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Representative Fee IDPE Second-Case Notice Suppression</data><data key="node_domain">Representatives / Debt</data><data key="node_description">RASR does not issue another IDPE notice automatically for a newly recorded fee issue when the entity is already ineligible for direct payment.</data><data key="node_observed_status">documented_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Each excess fee occurrence has its own EIN/claimant SSN fee record; ineligibility persists until all records resolved.</data></node><node id="R201_E023"><data key="node_entity_id">R201_E023</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">IDPE Per-Incident Entity EIN and Claimant SSN Record</data><data key="node_domain">Representatives / Debt</data><data key="node_description">RASR IDPE tracks each erroneous/excess fee issue using entity EIN, specific claimant SSN and amount owed.</data><data key="node_observed_status">documented_2025</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">EIN is representative entity identifier, not claimant SSN; transaction not representative payee record.</data></node><node id="R201_E024"><data key="node_entity_id">R201_E024</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Historic Online BEVE Mailing to Address of Record</data><data key="node_domain">Address Provenance / Communications</data><data key="node_description">Historical SSA policy describes online benefit verification request that automatically mails letter to address of record, using benefit verification system.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">4</data><data key="node_notes">Source revision dated 2011 but includes my Social Security language, so actual feature start not established. No address update inferred.</data></node><node id="R201_E025"><data key="node_entity_id">R201_E025</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Concurrent CDR Paper-and-Electronic Folder Dual Custody Requirement</data><data key="node_domain">Disability / Evidence</data><data key="node_description">For concurrent disability eCDRs, SSA may require transmission of associated Title II and Title XVI paper folders to DDS even when EDCS electronic folder exists.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Do not infer the certified electronic folder includes all paper supporting records.</data></node><node id="R201_E026"><data key="node_entity_id">R201_E026</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">2026 SSI Initial-Award AFI Negative Search Applies Without Resource Allegation</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">Current 2026 policy requires AFI requests for SSI allowances regardless of claimant alleged liquid resources, including reopening/reversal initial eligibility cases.</data><data key="node_observed_status">policy_effective_2026-05-04</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Existing broad AFI expansion captured in earlier Atlas; this entity preserves conditional absence-of-allegation verification detail.</data></node><node id="R201_E027"><data key="node_entity_id">R201_E027</data><data key="node_entity_type">form</data><data key="node_canonical_name">SSA-831 Disability Determination and Transmittal</data><data key="node_acronym">SSA-831</data><data key="node_domain">Disability / Evidence</data><data key="node_description">SSA disability determination/transmittal document, including diagnosis and onset entries for Title II and XVI claims.</data><data key="node_observed_status">documented_2026</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">New canonical form entity; historical derivative research records already existed, now connected to operational onset rules.</data></node><node id="R202_E001"><data key="node_entity_id">R202_E001</data><data key="node_entity_type">external_organization</data><data key="node_canonical_name">Vermont Department for Children and Families</data><data key="node_domain">State Exchanges</data><data key="node_description">Vermont DCF maintains benefits/assistance records queried by approved SSA employees under regional SASRO agreement.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E002"><data key="node_entity_id">R202_E002</data><data key="node_entity_type">external_application</data><data key="node_canonical_name">Vermont DCF ACCESS Eligibility System</data><data key="node_domain">State Exchanges</data><data key="node_description">Vermont ACCESS eligibility system provides authorized SSA field-office staff inquiry-only information about TANF, food assistance and child-support information.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E003"><data key="node_entity_id">R202_E003</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Vermont ACCESS Custodial Benefit and Child Support Evidence</data><data key="node_domain">Title XVI / State Data</data><data key="node_description">In Vermont ACCESS, custodian-sourced TANF/General Assistance benefit amounts, SNAP amounts, household assistance unit, and child support payments have specifically permitted verification uses; child support multi-child cases may require follow-up.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E004"><data key="node_entity_id">R202_E004</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">Vermont ACCESS Collateral Address and Telephone Observations</data><data key="node_domain">Address Provenance</data><data key="node_description">Vermont ACCESS address and telephone information about recipients is collateral state-record information, requiring verification before it can establish an SSA fact.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E005"><data key="node_entity_id">R202_E005</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Vermont SASRO Custodial-versus-Collateral Evidence Rule</data><data key="node_domain">State Data Governance</data><data key="node_description">SSA regional policy permits relying on custodial benefits information under listed conditions but requires independently checking address, SSN, DOB and third-party data; record state, system, date, screen.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E006"><data key="node_entity_id">R202_E006</data><data key="node_entity_type">external_organization</data><data key="node_canonical_name">Connecticut Department of Social Services</data><data key="node_domain">State Exchanges</data><data key="node_description">Connecticut DSS provided SSA field offices access to eligibility information in state Eligibility Management System under SASRO.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E007"><data key="node_entity_id">R202_E007</data><data key="node_entity_type">external_application</data><data key="node_canonical_name">Connecticut DSS Eligibility Management System</data><data key="node_domain">State Exchanges</data><data key="node_description">Connecticut Eligibility Management System (EMS) holds TANF, Medicaid and unemployment benefit information and was accessible to regional SSA employees through a state-managed account.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E008"><data key="node_entity_id">R202_E008</data><data key="node_entity_type">external_data_domain</data><data key="node_canonical_name">Connecticut Department of Labor Unemployment Benefit Custodial Source</data><data key="node_domain">State Exchanges</data><data key="node_description">Connecticut Department of Labor-origin unemployment benefits passed through DSS EMS were treated as verified under regional SASRO guidance; other noncustodial DSS attributes require verification.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E009"><data key="node_entity_id">R202_E009</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Connecticut SASRO CTHS Main Menu Access Route</data><data key="node_domain">State Exchanges</data><data key="node_description">Regional SSA staff entered CTHS from the SSA Main Menu and authenticated with a state-assigned user ID to inquire into Connecticut EMS.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E010"><data key="node_entity_id">R202_E010</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Connecticut SASRO Custodial and Collateral Evidence Classification</data><data key="node_domain">State Data Governance</data><data key="node_description">Connecticut state program benefit and qualifying state unemployment records may be verified via EMS; external income, SSNs and DOBs in EMS are only leads and need source verification.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E011"><data key="node_entity_id">R202_E011</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Ticket Program Manager Contractor Earnings Intake</data><data key="node_domain">Disability / Employment</data><data key="node_description">Ticket Program Manager receives wage reports from Employment Networks or State Vocational Rehabilitation programs and posts participant earnings into iTOPSS.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E012"><data key="node_entity_id">R202_E012</data><data key="node_entity_type">application</data><data key="node_canonical_name">Internet Ticket Operations Provider Support System (iTOPSS)</data><data key="node_domain">Disability / Ticket to Work</data><data key="node_description">SSA Ticket to Work program management system, documented as IDMS subsystem (2017 PIA) and with wage and payment processing under Ticket to Work. No hosting claims beyond published references.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E013"><data key="node_entity_id">R202_E013</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">iTOPSS Ticket Participant Reported Wage Details</data><data key="node_domain">Disability / Earnings</data><data key="node_description">iTOPSS includes wage/pay-stub data supplied by Ticket to Work Employment Networks or State VR and posted by Ticket Program Manager; earnings require SSA verification before program use.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E014"><data key="node_entity_id">R202_E014</data><data key="node_entity_type">batch_process</data><data key="node_canonical_name">iTOPSS Overnight Disability Control File Earnings Update</data><data key="node_domain">Disability / Earnings</data><data key="node_description">SSA POMS states participant wage data posted to iTOPSS updates DCF through overnight batch processing; field offices separately verify income.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E015"><data key="node_entity_id">R202_E015</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">iTOPSS QERN Wage Query View</data><data key="node_domain">Disability / Earnings</data><data key="node_description">SSA technicians can review iTOPSS wage details via QERN inquiry and EDCS Consolidated Wage Page for appropriate income development.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E016"><data key="node_entity_id">R202_E016</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">iTOPSS Wage Evidence Claimant-Concurrence Rule</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">When using third-party iTOPSS wage reports as SSI evidence, staff document claimant agreement, prior attempts to obtain preferred evidence and month of wages; query is not self-validating.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E017"><data key="node_entity_id">R202_E017</data><data key="node_entity_type">document_repository</data><data key="node_canonical_name">SSA Religious Exemption General Information Retrieval (GIR) Repository</data><data key="node_domain">Enumeration / Tax Data</data><data key="node_description">GIR contains scanned historical and new IRS forms 4029 and 4361 returned from IRS under Religious Exemption Unit processes. No enterprise-wide GIR implementation inferred.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E018"><data key="node_entity_id">R202_E018</data><data key="node_entity_type">application</data><data key="node_canonical_name">Enumeration System Correspondence (ESCORR) Application</data><data key="node_domain">Enumeration / Person Identity</data><data key="node_description">SSA Religious Exemption Unit enters required information into ESCORR to code Q/FICA religious tax exemption indicator on Numident when qualifying IRS Form 4029 is returned.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E019"><data key="node_entity_id">R202_E019</data><data key="node_entity_type">document_product</data><data key="node_canonical_name">GIR IRS Forms 4029 and 4361 Archived Documents</data><data key="node_domain">Tax / Identity</data><data key="node_description">Scanned exemption application records received from IRS, maintained in GIR as an administrative document retrieval product.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E020"><data key="node_entity_id">R202_E020</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">IRS Form 4361 Religious Exemption Database Scan Status</data><data key="node_domain">Tax / Identity</data><data key="node_description">After processing IRS Form 4361, SSA Religious Exemption Unit scans the form to GIR and records Scanned status in its religious exemption database.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E021"><data key="node_entity_id">R202_E021</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">Medicare Extra Help Application Address Change Development</data><data key="node_domain">Address Provenance</data><data key="node_description">HI 03010.038 states Extra Help mailing address in MAPS is for correspondence; if address change within preceding three months, Title II updates require POS to MBR, with separate SSI update procedure when applicable; WBDOC handles stated OCR/online form exceptions.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E022"><data key="node_entity_id">R202_E022</data><data key="node_entity_type">data_domain</data><data key="node_canonical_name">MAPS Extra Help Office of Child Support Enforcement Wage Check</data><data key="node_domain">Medicare / Earnings</data><data key="node_description">Extra Help SSA-1020 application permits reconciliation of alleged reduced wages against OCSE wage data, which may lag current wages; discrepancy must be investigated.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E023"><data key="node_entity_id">R202_E023</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">2026 SSI Annual Report Table IV.E Administrative and Beneficiary Services Costs</data><data key="node_domain">OACT / Publication Pipeline</data><data key="node_description">Official 2026 SSI Annual Report IV.E describes and tabulates SSI program share of integrated agency administrative costs, with historical fiscal years and projected data.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E024"><data key="node_entity_id">R202_E024</data><data key="node_entity_type">financial_process</data><data key="node_canonical_name">SSI and OASDI Shared Administrative Cost Allocation and True-Up</data><data key="node_domain">OACT / Finance</data><data key="node_description">Integrated SSA operating expenses are financed through the Limitation on Administrative Expenses account, with trust funds and general funds allocated by accepted cost-analysis method and final settlement after fiscal year.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E025"><data key="node_entity_id">R202_E025</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">SSA Overall Customer Service Satisfaction FY2007-FY2023 CSV</data><data key="node_domain">Enterprise Data / Open Data</data><data key="node_description">Published SSA Open Data CSV covers agency overall customer service satisfaction in fiscal years 2007-2023; page updated March 14, 2024.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E026"><data key="node_entity_id">R202_E026</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">SSA Initial Disability and Hearing Service Satisfaction FY2008-FY2018 CSV</data><data key="node_domain">Disability / Open Data</data><data key="node_description">SSA Open Data customer satisfaction CSV covers initial-disability and hearing-level service fiscal years 2008-2018; dataset page lists update February 8, 2019.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E027"><data key="node_entity_id">R202_E027</data><data key="node_entity_type">external_program</data><data key="node_canonical_name">Department of Justice National Fraud Detection Center (NFDC)</data><data key="node_domain">Federal Partner / Program Integrity</data><data key="node_description">DOJ prosecutor-led multiagency fraud detection coordination center launched August 2026; SSA OIG announced analyst participation; no shared system data interchange specified.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E028"><data key="node_entity_id">R202_E028</data><data key="node_entity_type">governance_activity</data><data key="node_canonical_name">SSA OIG National Fraud Detection Center Participation</data><data key="node_domain">Federal Partner / Program Integrity</data><data key="node_description">SSA OIG signed NFDC charter and committed investigators/analysts to fraud investigation coordination, August 2026 announcement.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E029"><data key="node_entity_id">R202_E029</data><data key="node_entity_type">document_classification</data><data key="node_canonical_name">SSA-827 Certified Electronic Folder Barcode Document Type 1050</data><data key="node_domain">Disability Evidence</data><data key="node_description">SSA paper signed medical-release form 827 has barcode document type 1050 and is imaged to CEF; automatically filed signed electronic SSA-827 must not be faxed again.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R202_E030"><data key="node_entity_id">R202_E030</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">SSA-827 Paper Electronic Folder Legibility Check</data><data key="node_domain">Disability Evidence</data><data key="node_description">Field office employee must verify legible signed SSA-827 in eView before transferring paper-signed form case to DDS, with separate EDCS exclusion MDF handling.</data><data key="node_observed_status">documented_historical_or_policy</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">No assertion of current implementation beyond the cited revision/observation.</data></node><node id="R203_E001"><data key="node_entity_id">R203_E001</data><data key="node_entity_type">data_attribute</data><data key="node_canonical_name">RASR Representative Business Address Attribute</data><data key="node_domain">Representatives / Address Provenance</data><data key="node_description">RASR centrally stores representative business address supplied through signed SSA-1699; business-contact address is not claimant residence.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Registration changes require signed SSA-1699 processed by OCO/DEBS. Confidentiality and use restrictions apply.</data></node><node id="R203_E002"><data key="node_entity_id">R203_E002</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RASR Representative Name Change Numident Prerequisite</data><data key="node_domain">Person/Identity / Representation</data><data key="node_description">RASR name correction requires previous Numident name change followed by an updated SSA-1699 reviewed by DEBS; no automatic identity-to-representative synchronization is established.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Ordered transaction and employee/form handoff.</data></node><node id="R203_E003"><data key="node_entity_id">R203_E003</data><data key="node_entity_type">automated_workflow</data><data key="node_canonical_name">RASR Existing-Affiliation Pending-Claims Propagation</data><data key="node_domain">Representatives / Fees</data><data key="node_description">After DEBS processes changed non-EIN affiliation information on SSA-1699, RASR automatically updates the affiliation information on related pending claims; no SSA-1696 refile required for those updates.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">EIN changes are explicitly excluded from this path.</data></node><node id="R203_E004"><data key="node_entity_id">R203_E004</data><data key="node_entity_type">business_rule</data><data key="node_canonical_name">RASR Affiliation EIN Change as New Affiliation</data><data key="node_domain">Representatives / Fees</data><data key="node_description">An affiliation EIN change is a new affiliation; updated SSA-1696 Section V is required for a pending claim where representative wants the new EIN affiliation.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R203_E005"><data key="node_entity_id">R203_E005</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">Deceased Representative Estate Fee Registration and Verification</data><data key="node_domain">Representatives / Payment</data><data key="node_description">Before authorized direct payment of a deceased representative fee to an estate, SSA develops executor identity/address and processes SSA-1699 estate registration update after specified diary controls.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">The executor is not newly appointed as a claimant representative; 60-day wait and 15-day follow-up documented.</data></node><node id="R203_E006"><data key="node_entity_id">R203_E006</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">RASR Representative Fee 1099-MISC and 1099-NEC Reporting Distinctions</data><data key="node_domain">Representatives / IRS Tax Reporting</data><data key="node_description">SSA reports direct representative fees using 1099-MISC/1099-NEC according to entity affiliation/registration status; only specified same-year payment or contact corrections supported.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">IRS taxpayer forms; no assertion of automatic IRS tax return updates or IRS address synchronization.</data></node><node id="R203_E007"><data key="node_entity_id">R203_E007</data><data key="node_entity_type">documented_interface_limitation</data><data key="node_canonical_name">eRPS Payee Termination Does Not Terminate MBR or SSR Appointment</data><data key="node_domain">Representative Payee / Title II / Title XVI</data><data key="node_description">Terminating a payee relationship within eRPS alone does not terminate payee on MBR or SSR; field office must take a separate direct-pay or new-payee action.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Explicit negative propagation; not a claim that new appointment never updates MBR/SSR.</data></node><node id="R203_E008"><data key="node_entity_id">R203_E008</data><data key="node_entity_type">documented_interface_limitation</data><data key="node_canonical_name">CPR MBR to SSR Debt-Disposition Exchange Limitation</data><data key="node_domain">Title II / Title XVI / Debt</data><data key="node_description">When Title II benefit ledger status changes during cross-program SSI debt recovery, the MBR does not send an SSI overpayment disposition exchange record to the SSR; a processing-center alert is generated instead.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">POMS SI 02220.020E.1 explicitly identifies interface limitation.</data></node><node id="R203_E009"><data key="node_entity_id">R203_E009</data><data key="node_entity_type">work_item</data><data key="node_canonical_name">CPR Processing Center Alert for Interrupted Title II Withholding</data><data key="node_domain">Title II / Title XVI / Debt</data><data key="node_description">During affected cross-program recovery status changes, MBR generates a processing center alert requiring action in lieu of an MBR-to-SSR debt-disposition exchange.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R203_E010"><data key="node_entity_id">R203_E010</data><data key="node_entity_type">work_item</data><data key="node_canonical_name">CPR B8 Diary on Resumption of SSI Current Payment</data><data key="node_domain">Title XVI / Debt</data><data key="node_description">If SSI debtor returns to C01 payment status while CPR remains in progress, automated B8 diary flags possible inappropriate K TAC disposition.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R203_E011"><data key="node_entity_id">R203_E011</data><data key="node_entity_type">documented_workflow_limitation</data><data key="node_canonical_name">CPR DMS DROA Withholding Adjustment and K TAC Staleness</data><data key="node_domain">Title II / Title XVI / Debt</data><data key="node_description">Employee changes Title II recovery withholding via DMS DROA when benefit payable changes; posted SSI K TAC may not reflect actual rate and ROAR is consulted.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Cannot assume displayed K TAC is authoritative for current recovery amount.</data></node><node id="R203_E012"><data key="node_entity_id">R203_E012</data><data key="node_entity_type">documented_workflow_exception</data><data key="node_canonical_name">Foreign-Address Criminal Payee DPS Call-In Notice Exception</data><data key="node_domain">Representative Payee / Address Provenance</data><data key="node_description">When payee with a foreign address requires criminal-history call-in, use DPS instead of ordinary eRPS automated notice and establish a 15-day follow-up.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Address determines correspondence procedure; not an address update.</data></node><node id="R203_E013"><data key="node_entity_id">R203_E013</data><data key="node_entity_type">identity_update_control</data><data key="node_canonical_name">EAB Source Documentation Gate for Numident Keying Correction</data><data key="node_domain">Person/Identity / Enumeration</data><data key="node_description">Correction of documented Enumeration-at-Birth source keying error requires originating participating entity records demonstrating its error before existing Numident iteration correction via NCP.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Otherwise new iteration required; does not imply free-form revision.</data></node><node id="R203_E014"><data key="node_entity_id">R203_E014</data><data key="node_entity_type">external_data_attribute</data><data key="node_canonical_name">IRS NEW SSA Name Control Interim Indicator</data><data key="node_domain">IRS / Person Identity</data><data key="node_description">IRS IMF taxpayer records expose NEW SSA N/C indicator after weekly SSA SSN/name-control update before quarterly DM-1 merge validation.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">IRS-only taxpayer account state; not a write to SSA Numident, MBR or SSR.</data></node><node id="R203_E015"><data key="node_entity_id">R203_E015</data><data key="node_entity_type">external_processing_cycle</data><data key="node_canonical_name">IRS DM-1 Quarterly Name-Control Reconciliation Cycle</data><data key="node_domain">IRS / Person Identity</data><data key="node_description">IRS DM-1 validation merges run in January, April, July, November and reconcile new SSA name controls with IMF valid/invalid segments.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">IRS processing schedule as documented in IRM subsection updated 2022; do not infer SSA system schedule.</data></node><node id="R203_E016"><data key="node_entity_id">R203_E016</data><data key="node_entity_type">historical_automated_workflow</data><data key="node_canonical_name">2007 CDR Failure-to-Cooperate DCF-to-MBR Benefit Resumption</data><data key="node_domain">Title II / Disability / Modernization History</data><data key="node_description">2007 SSA POMS states DCF transfer input after beneficiary cooperation triggers MBR resumption; exception causes processing-center paperless alert and manual action.</data><data key="node_observed_status">historical_documented</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Historical 2007 documented behavior; not asserted as unchanged production implementation in 2026.</data></node><node id="R203_E017"><data key="node_entity_id">R203_E017</data><data key="node_entity_type">publication_control</data><data key="node_canonical_name">OACT Statistical Tables Prepublication Version Boundary</data><data key="node_domain">OACT / Statistical Publications</data><data key="node_description">OACT statistical table catalog notes some tables include prepublication data and identifies which tables appear in Annual Statistical Supplement vs standalone products.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Product freshness and methodological notes require table-level version tracking.</data></node><node id="R203_E018"><data key="node_entity_id">R203_E018</data><data key="node_entity_type">statistical_data_product</data><data key="node_canonical_name">OACT Historical Disabled Worker Beneficiary Statistics Table and Charts</data><data key="node_domain">OACT / Disability Statistics</data><data key="node_description">OACT catalog links recent disabled worker beneficiary data and charts as statistical products outside Annual Statistical Supplement.</data><data key="node_observed_status">documented_process</data><data key="node_observed_as_of">2026-10-11</data><data key="node_confidence">5</data><data key="node_notes">Statistical outputs only; source operational production systems not established by this index.</data></node><node id="R204_E001"><data key="node_entity_id">R204_E001</data><data key="node_entity_type">business_process</data><data key="node_canonical_name">SSA Disaster-Area Address-Based Case Identification</data><data key="node_domain">Address provenance / disaster response</data><data key="node_description">Published procedure uses disaster-area ZIP codes and record addresses to identify affected MBR/SSR cases. This is case classification, not validation or replacement of a residence address.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2010-06-14</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R204_E002"><data key="node_entity_id">R204_E002</data><data key="node_entity_type">record_annotation</data><data key="node_canonical_name">MBR Disaster Procedures Special Message</data><data key="node_domain">Local-source research</data><data key="node_description">Disaster cases are designated in the MBR Special Message field. Staff must not delete or replace the message; records created after initial identification require a post-adjudicative message and listing code.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2010-06-14</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R204_E003"><data key="node_entity_id">R204_E003</data><data key="node_entity_type">record_annotation</data><data key="node_canonical_name">SSR Disaster Case Characteristic Code and Missed-Case Manual Addition</data><data key="node_domain">Local-source research</data><data key="node_description">Affected nonterminated Title XVI records receive a disaster CG code. Field offices may add it as the first CG entry for missed recipients who lived in affected areas and remain displaced.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2010-06-14</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R204_E004"><data key="node_entity_id">R204_E004</data><data key="node_entity_type">document_package</data><data key="node_canonical_name">Italian Benefits Claim Forwarding Evidence Packet in PPC</data><data key="node_domain">International benefits / evidence</data><data key="node_description">A Benefit Earnings Technician stores Italian claim information, certified evidence copies, and the worker US coverage record in DIO PPC before forwarding the claim material to Italy.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2022-03-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R204_E005"><data key="node_entity_id">R204_E005</data><data key="node_entity_type">notice</data><data key="node_canonical_name">Italian Benefits PPC-Generated Forwarding Notice</data><data key="node_domain">Local-source research</data><data key="node_description">PPC automatically generates a forwarding notice, which the Benefit Earnings Technician sends to the applicant. Notice generation and dispatch are distinct actions.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2022-03-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R204_E006"><data key="node_entity_id">R204_E006</data><data key="node_entity_type">operational_constraint</data><data key="node_canonical_name">Italian Benefits Post-Forwarding Status Visibility Boundary</data><data key="node_domain">Local-source research</data><data key="node_description">After a technician forwards the Italian claim, DIO cannot determine its subsequent Italian-benefit claim status. Applicants are directed to the Italian agency; PPC establishes forwarding status.</data><data key="node_observed_status">documented_policy</data><data key="node_observed_as_of">2022-03-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="R204_E007"><data key="node_entity_id">R204_E007</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA IBM Proprietary Support BPA SS000840027</data><data key="node_domain">Procurement / historical technology</data><data key="node_description">Procurement record dated 2009-02-26, modification 1, reports federal action obligation $0.00. Description: THIS REQUISITION IS TO ESTABLISH A NEW BPA FOR IBM PROPRIETARY SUPPORT SERVICES.</data><data key="node_observed_status">documented_historical_procurement</data><data key="node_observed_as_of">2009-02-26</data><data key="node_confidence">4</data><data key="node_notes">Award or BPA evidence only. No assertion of installation, acceptance, production deployment, or current status. Place of performance is not a hosting location.</data></node><node id="R204_E008"><data key="node_entity_id">R204_E008</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Mainframe Hardware BPA SS001140011</data><data key="node_domain">Procurement / historical technology</data><data key="node_description">Procurement record dated 2013-08-19, modification 4, reports federal action obligation $0.00. Description: NEW MAINFRAME HARDWARE BPA</data><data key="node_observed_status">documented_historical_procurement</data><data key="node_observed_as_of">2013-08-19</data><data key="node_confidence">4</data><data key="node_notes">Award or BPA evidence only. No assertion of installation, acceptance, production deployment, or current status. Place of performance is not a hosting location.</data></node><node id="R204_E009"><data key="node_entity_id">R204_E009</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Ab Initio Software and Services BPA SS001440015</data><data key="node_domain">Procurement / historical technology</data><data key="node_description">Procurement record dated 2014-07-14, modification 1, reports federal action obligation $0.00. Description: AB INITIO EXTRACT, TRANSFORM AND LOAD SOFTWARE, MAINTENANCE, CONSULTING SERVICES AND TRAINING BLANKET PURCHASE AGREEMENT (BPA).</data><data key="node_observed_status">documented_historical_procurement</data><data key="node_observed_as_of">2014-07-14</data><data key="node_confidence">4</data><data key="node_notes">Award or BPA evidence only. No assertion of installation, acceptance, production deployment, or current status. Place of performance is not a hosting location.</data></node><node id="R204_E010"><data key="node_entity_id">R204_E010</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Secure Browser Software BPA SS001440044</data><data key="node_domain">Procurement / historical technology</data><data key="node_description">Procurement record dated 2015-07-16, modification 1, reports federal action obligation $0.00. Description: THIS IS A $0 REQUISITION TO ESTABLISH A BPA FOR SECURE BROWSER SOFTWARE</data><data key="node_observed_status">documented_historical_procurement</data><data key="node_observed_as_of">2015-07-16</data><data key="node_confidence">4</data><data key="node_notes">Award or BPA evidence only. No assertion of installation, acceptance, production deployment, or current status. Place of performance is not a hosting location.</data></node><node id="R204_E011"><data key="node_entity_id">R204_E011</data><data key="node_entity_type">contract</data><data key="node_canonical_name">SSA Quality Center Migration Support Call 0006 under SS000840006</data><data key="node_domain">Procurement / historical technology</data><data key="node_description">Procurement record dated 2008-06-27, modification 0, reports federal action obligation $12225.00. Description: DVTT IS RESPONSIBLE FOR UPGRADING AND CONSOLIDATING QUALITY CENTER LICENSES, SOFTWARE, AND DATA FROM SEVERAL DISPARATE SERVERS TO A CENTRALIZED GROUP OF SERVERS TO BE HOUSED BY DESEI.  IN ORDER TO SMOOTHLY MIGRATE MORE THAN 300 PROJECTS AND 1500 USERS ACROSS COMPONENTS, DVTT REQUIRES 80 HOURS OF PREMIUM SUPPORT FROM HP.  SPECIFICALLY, HP WOULD PROVIDE UP TO 40 HOURS OF ON-SITE CONSULTATION IN THE PLANNING PHASE, ASSISTING IN THE UPGRADE TO 9.2, SCOPING OUT HARDWARE REQUIREMENTS AND PROVIDING A FORMAL REPORT DESCRIBING DETAILED RECOMMENDATIONS ON THE HARDWARE AND ARCHITECTURE THAT BEST FITS SSA'S RESOURCES AND NEEDS.  THE REMAINING HOURS WOULD BE USED TO HAVE HP TECHNICAL SUPPORT ON-SITE DURING THE ACTUAL MIGRATION TO QUICKLY RESOLVE ISSUES THAT COULD POTENTIALLY RESULT IN EXTENDED HOURS OF DOWNTIME FOR HUNDREDS OF USERS.</data><data key="node_observed_status">documented_historical_procurement</data><data key="node_observed_as_of">2008-06-27</data><data key="node_confidence">4</data><data key="node_notes">Award or BPA evidence only. No assertion of installation, acceptance, production deployment, or current status. Place of performance is not a hosting location.</data></node><node id="R204_E012"><data key="node_entity_id">R204_E012</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">SOLUTIONS ENGINEERING CORP</data><data key="node_domain">Procurement / vendor</data><data key="node_description">Named procurement recipient in the reviewed SSA record. UEI LCGCHS5JKU39; DUNS 174347849. Identity is as reported in this snapshot; corporate successors are not inferred.</data><data key="node_observed_status">documented_historical_procurement</data><data key="node_observed_as_of">2014-07-14</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R204_E013"><data key="node_entity_id">R204_E013</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">NETCON, INC</data><data key="node_domain">Procurement / vendor</data><data key="node_description">Named procurement recipient in the reviewed SSA record. UEI MK7CB66VH219; DUNS 937665677. Identity is as reported in this snapshot; corporate successors are not inferred.</data><data key="node_observed_status">documented_historical_procurement</data><data key="node_observed_as_of">2015-07-16</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R204_E014"><data key="node_entity_id">R204_E014</data><data key="node_entity_type">vendor</data><data key="node_canonical_name">SPECTRUM SYSTEMS, INC.</data><data key="node_domain">Procurement / vendor</data><data key="node_description">Named procurement recipient in the reviewed SSA record. UEI ZRJRWK5KJP36; DUNS 156992745. Identity is as reported in this snapshot; corporate successors are not inferred.</data><data key="node_observed_status">documented_historical_procurement</data><data key="node_observed_as_of">2008-06-27</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="R205_E001"><data key="node_entity_id">R205_E001</data><data key="node_entity_type">workflow_constraint</data><data key="node_canonical_name">eCDR Post-Transfer Contact Change Manual Entry Boundary</data><data key="node_domain">Disability / data lineage</data><data key="node_description">After eCDR transfer to DDS, contact changes must be keyed into CDR Information or CDR Representative and sent as a UAT. The published general eCDR instruction says this information does not repropagate from MBR or SSR.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2019-11-25</data><data key="node_confidence">5</data><data key="node_notes">Section D note; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E002"><data key="node_entity_id">R205_E002</data><data key="node_entity_type">workflow_constraint</data><data key="node_canonical_name">Age-18 EDCS Post-Transfer Message and SSA-5002 Change Route</data><data key="node_domain">Disability / data lineage</data><data key="node_description">For age-18 redeterminations, the instruction says Update after Transfer is unavailable, MSSICS corrections do not update the transferred EDCS record, and address changes must be reported by message and SSA-5002 narrative.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2016-03-02</data><data key="node_confidence">5</data><data key="node_notes">Section C reminder; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E003"><data key="node_entity_id">R205_E003</data><data key="node_entity_type">record_update_rule</data><data key="node_canonical_name">eCDR EDCS and Master-Record Address Dual Correction Requirement</data><data key="node_domain">Disability / data lineage</data><data key="node_description">During eCDR client identification, staff review the address propagated from MBR/SSR and correct incorrect information both in EDCS and in MBR/SSR. An EDCS correction alone is not asserted to update either master record.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2019-11-25</data><data key="node_confidence">5</data><data key="node_notes">Section B.1; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E004"><data key="node_entity_id">R205_E004</data><data key="node_entity_type">address_provenance_rule</data><data key="node_canonical_name">eCDR Claimant Residence Address When a Payee Exists</data><data key="node_domain">Disability / data lineage</data><data key="node_description">When a representative payee exists, the eCDR Client Identification screen must carry the claimant residence address. This distinguishes the claimant residence from the representative payee contact address.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2019-11-25</data><data key="node_confidence">5</data><data key="node_notes">Section B.1 note; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E005"><data key="node_entity_id">R205_E005</data><data key="node_entity_type">transfer_gate</data><data key="node_canonical_name">Age-18 EDCS Transfer Gate on SSR Adult Type of Master Record</data><data key="node_domain">Disability / data lineage</data><data key="node_description">Age-18 EDCS transfer requires prior verification that SSR Type of Master Record changed from child to adult; staff query SSID the following day. The gate is separate from the already represented conversion process.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2016-03-02</data><data key="node_confidence">5</data><data key="node_notes">Section B and C; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E006"><data key="node_entity_id">R205_E006</data><data key="node_entity_type">date_attribute_rule</data><data key="node_canonical_name">Age-18 EDCS Synthetic Comparison Point Date</data><data key="node_domain">Disability / data lineage</data><data key="node_description">For age-18 redetermination case creation, EDCS fills the CPD field with a date 12 months before CDR case creation and does not permit overkeying. This generated date is not evidence of an actual medical decision on that day.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2016-03-02</data><data key="node_confidence">5</data><data key="node_notes">Section C; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E007"><data key="node_entity_id">R205_E007</data><data key="node_entity_type">data_propagation_rule</data><data key="node_canonical_name">Age-18 DDS Capability Development Manual Input Boundary</data><data key="node_domain">Disability / data lineage</data><data key="node_description">The yes response indicating DDS capability development is needed does not propagate from the mainframe. Once keyed on CDR Information it displays in the SSA-3367 capability field.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2016-03-02</data><data key="node_confidence">5</data><data key="node_notes">Section C important; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E008"><data key="node_entity_id">R205_E008</data><data key="node_entity_type">validation_rule</data><data key="node_canonical_name">EDCS Always Mandatory for Transfer Nonoverridable Edits</data><data key="node_domain">Disability / data lineage</data><data key="node_description">Always Mandatory for Transfer edits must be resolved before EDCS case transfer and cannot be overridden. They are distinct from the separately named Mandatory for Transfer category.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2008-01-24</data><data key="node_confidence">5</data><data key="node_notes">Section B.1.a; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E009"><data key="node_entity_id">R205_E009</data><data key="node_entity_type">access_control_rule</data><data key="node_canonical_name">EDCS Mandatory for Transfer Supervisory PIN Override</data><data key="node_domain">Disability / data lineage</data><data key="node_description">When resolution is impossible, a supervisor using their own PIN may override Mandatory for Transfer edits on Collect Edits. These edits do not apply to FO-to-FO transfer; this does not override the Always Mandatory category.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2008-01-24</data><data key="node_confidence">5</data><data key="node_notes">Section B.1.b; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E010"><data key="node_entity_id">R205_E010</data><data key="node_entity_type">screen</data><data key="node_canonical_name">EDCS Collect Edits Screen</data><data key="node_domain">Disability / data lineage</data><data key="node_description">Collect Edits lists incomplete or incorrect data and its primary screen after an edit check or failed transfer. Selecting an edit legend navigates to the relevant primary screen; the field itself may be on a secondary page.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2008-01-24</data><data key="node_confidence">5</data><data key="node_notes">Section B.1 and B.2.b; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E011"><data key="node_entity_id">R205_E011</data><data key="node_entity_type">record_update_rule</data><data key="node_canonical_name">DOD Benefit Interface Manual SSR Posting Boundary</data><data key="node_domain">SSI / federal data interfaces</data><data key="node_description">The published DOD benefit interface procedure says benefit information is not electronically posted to SSR; changes are posted manually after appropriate development. This is not an automatic address-write pathway.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2013-12-16</data><data key="node_confidence">5</data><data key="node_notes">Section A and B; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E012"><data key="node_entity_id">R205_E012</data><data key="node_entity_type">alert_handling_rule</data><data key="node_canonical_name">DOD Interface Matching Type-L Income No-Action Alert</data><data key="node_domain">SSI / federal data interfaces</data><data key="node_description">The DOD interface can generate an alert even when the pension amount agrees with Type-L income on SSR. Staff may discard that matching-income alert without action. Alert existence alone is not a discrepancy.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2013-12-16</data><data key="node_confidence">5</data><data key="node_notes">Section A; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R205_E013"><data key="node_entity_id">R205_E013</data><data key="node_entity_type">historical_workflow</data><data key="node_canonical_name">DOD Interface March-2007 Field Printer and MISF Alert Routing</data><data key="node_domain">SSI / federal data interfaces</data><data key="node_description">The procedure states that from March 2007 DOD alerts are generated to field-office printers and placed on a facility named Management Information Systems Facility (MISF). No current transport or physical printer topology is inferred.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2013-12-16</data><data key="node_confidence">5</data><data key="node_notes">Section A; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E001"><data key="node_entity_id">R206_E001</data><data key="node_entity_type">computation_rule</data><data key="node_canonical_name">ICF Function 31 Pre-Adjudicate Calculation Boundary</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">ICF function 31 calculates WC/PDB offset without affecting the beneficiary record. Completion requires propagating data to function 32 or 34; function 31 saves only a pre-adjudicate record.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2017-01-26</data><data key="node_confidence">5</data><data key="node_notes">Section C; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E002"><data key="node_entity_id">R206_E002</data><data key="node_entity_type">data_propagation_rule</data><data key="node_canonical_name">ICF Function 32 Input-to-T2R Recalculation Boundary</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">ICF 32 sends input data to T2R rather than authoritative ICF calculation results. T2R recomputes using MBR and T2 Shared data, so manipulated ICF inputs may produce different T2R results. The policy does not specify which physical T2 Shared store is used.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2017-01-26</data><data key="node_confidence">5</data><data key="node_notes">Section C note; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E003"><data key="node_entity_id">R206_E003</data><data key="node_entity_type">application_function</data><data key="node_canonical_name">ICF Function 34 Online Record Entry</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">OREO accepts propagated or manually calculated WC/PDB information, performs no offset calculations, and does not post directly through T2R. A processing-center BA/BTE effectuates the action through MACADE.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2015-11-30</data><data key="node_confidence">5</data><data key="node_notes">Section Introduction; D.1 and D.3; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E004"><data key="node_entity_id">R206_E004</data><data key="node_entity_type">retention_rule</data><data key="node_canonical_name">ICF Single Pre-Adjudicate Record Eighteen-Month Availability</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">Only one pre-adjudicate record is retained at a time in the documented ICF workflow, available for 18 months. It permits calculation scenarios without completing a beneficiary-record change.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2017-01-26</data><data key="node_confidence">5</data><data key="node_notes">Section A.1; C; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E005"><data key="node_entity_id">R206_E005</data><data key="node_entity_type">record_storage_rule</data><data key="node_canonical_name">ICF Adjudicated Datasheet ORS Storage Trigger</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">Adjudicated WC/PDB datasheets are stored in Online Retrieval System once their data is transmitted to T2R or propagated into MACADE. Function 33 supports viewing prior pre-adjudicate and adjudicate data; this does not establish indefinite retention.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2017-01-26</data><data key="node_confidence">5</data><data key="node_notes">Section C; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E006"><data key="node_entity_id">R206_E006</data><data key="node_entity_type">notice_control_rule</data><data key="node_canonical_name">ICF WCEP ENB Field Ignored by T2R Notice Generation</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">T2R ignores notice data entered in the WCEP ENB field when processing ICF 32 inputs. The policy directs OREO when staff must ensure the T2R automated notice is not generated and released.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2015-11-30</data><data key="node_confidence">5</data><data key="node_notes">Section A.5; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E007"><data key="node_entity_id">R206_E007</data><data key="node_entity_type">calculation_tool</data><data key="node_canonical_name">e2455+ WC Offset Calculator</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">The policy names e2455+ as a WC offset calculation tool and states the e2455 tool propagates offset rates into OREO. No physical hosting, vendor or deployment date is inferred.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2015-11-30</data><data key="node_confidence">5</data><data key="node_notes">Section D.1; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E008"><data key="node_entity_id">R206_E008</data><data key="node_entity_type">evidence_workflow</data><data key="node_canonical_name">WC Offset Administrative-Finality Datasheet Dual Filing</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">For protected rates, staff document the pre-adjudicate datasheet and special instructions, fax a copy into NDRed, and processing centers also scan a copy into PPC. An MBR Special Message identifies the protected months and NDRed copy.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2015-11-30</data><data key="node_confidence">5</data><data key="node_notes">Section A.3.a; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E009"><data key="node_entity_id">R206_E009</data><data key="node_entity_type">record_view_rule</data><data key="node_canonical_name">eView Forms View Successful-Transfer Snapshot Semantics</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">Forms view presents disability report information as it existed when the field office successfully transferred the case. It is distinct from Case Data view, which includes later information and UAT changes.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2013-01-10</data><data key="node_confidence">5</data><data key="node_notes">Section A and B; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E010"><data key="node_entity_id">R206_E010</data><data key="node_entity_type">evidence_precedence_rule</data><data key="node_canonical_name">eView SSA-831 Dual Representation and Latest-Image Action Rule</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">eView stores SSA-831 as a Section A Case Documents image and as formatted Case Data. Because multiple versions can exist, the instruction directs action based on the most recent imaged SSA-831 in Section A.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2013-01-10</data><data key="node_confidence">5</data><data key="node_notes">Section B note; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E011"><data key="node_entity_id">R206_E011</data><data key="node_entity_type">audit_provenance_rule</data><data key="node_canonical_name">EDCS ROC Whole-Record Snapshot Comparison Requirement</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">ROC snapshots contain all information in every section and identify the triggering event, actor, office and time, but do not label which information changed. Staff must compare records to determine field changes.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2013-01-10</data><data key="node_confidence">5</data><data key="node_notes">Section C and C.2; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E012"><data key="node_entity_id">R206_E012</data><data key="node_entity_type">retention_boundary</data><data key="node_canonical_name">EDCS Case Deletion Removes Associated ROC History</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">Deleting an EDCS case deletes the entire record including its Records of Change. ROC availability therefore must not be interpreted as an independent immutable retention guarantee.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2013-01-10</data><data key="node_confidence">5</data><data key="node_notes">Section C; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="R206_E013"><data key="node_entity_id">R206_E013</data><data key="node_entity_type">exception_visibility_rule</data><data key="node_canonical_name">eView Internet Disability Report Failed-Propagation Annotation</data><data key="node_domain">Disability / calculation and evidence provenance</data><data key="node_description">When an Internet Disability Report existed but failed to propagate into EDCS, eView Client and Onset Dates in Case Information displays the report type and failure reason.</data><data key="node_observed_status">documented_scoped_policy</data><data key="node_observed_as_of">2013-01-10</data><data key="node_confidence">5</data><data key="node_notes">Section A; retains displayed policy date. No assertion of current physical implementation.</data></node><node id="REPORT_DI_ASR_2024"><data key="node_entity_id">REPORT_DI_ASR_2024</data><data key="node_entity_type">report</data><data key="node_canonical_name">Annual Statistical Report on the Social Security Disability Insurance Program, 2024</data><data key="node_domain">Statistical Publications / Disability Insurance</data><data key="node_description">Annual SSA report presenting program and demographic statistics for Social Security disability beneficiaries and disability application outcomes.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Released December 2025; Federal Data Catalog identifier US-GOV-SSA-3327.</data></node><node id="REPORT_DMS_CCFORT"><data key="node_entity_id">REPORT_DMS_CCFORT</data><data key="node_entity_type">report</data><data key="node_canonical_name">CCFORT Debit/Credit Card Remittance Transmittal</data><data key="node_acronym">CCFORT</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">DMS-generated end-of-day transmittal for debit/credit-card remittance transactions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Source uses acronym CCFORT but does not explicitly expand each letter; canonical label avoids an unsupported expansion.</data></node><node id="REPORT_DMS_FODRL"><data key="node_entity_id">REPORT_DMS_FODRL</data><data key="node_entity_type">report</data><data key="node_canonical_name">Field Office Daily Receipt Listing</data><data key="node_acronym">FODRL</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">DMS-generated daily listing used for auditing and reconciling other program and non-program money.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS.</data></node><node id="REPORT_DMS_FORT"><data key="node_entity_id">REPORT_DMS_FORT</data><data key="node_entity_type">report</data><data key="node_canonical_name">Field Office Remittance Transmittal</data><data key="node_acronym">FORT</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">DMS-generated end-of-day transmittal listing check and money-order remittances that a field office sends to MATPSC.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS.</data></node><node id="REPORT_EARN_EMP_2023"><data key="node_entity_id">REPORT_EARN_EMP_2023</data><data key="node_entity_type">report</data><data key="node_canonical_name">Earnings and Employment Data for Workers Covered Under Social Security and Medicare, by State and County, 2023</data><data key="node_acronym">Earnings and Employment 2023</data><data key="node_domain">Research / Statistics / Earnings</data><data key="node_description">Current SSA statistical report presenting 2023 Social Security and Medicare covered-worker earnings/employment statistics by state and county.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-01</data><data key="node_confidence">5</data><data key="node_notes">Current published tables identify the Continuous Work History Sample 1-percent sample as the source; geographic designations use worker residence/address logic documented in the introduction.</data></node><node id="REPORT_EARN_EMP_SERIES"><data key="node_entity_id">REPORT_EARN_EMP_SERIES</data><data key="node_entity_type">report_series</data><data key="node_canonical_name">Earnings and Employment Data for Workers Covered Under Social Security and Medicare, by State and County</data><data key="node_acronym">Earnings and Employment</data><data key="node_domain">Research / Statistics / Earnings</data><data key="node_description">SSA annual statistical publication series presenting covered-worker earnings and employment by state and county.</data><data key="node_observed_status">observed_current_publication_series</data><data key="node_observed_as_of">2026-01</data><data key="node_confidence">5</data><data key="node_notes">Current 2023 edition was released January 2026. ORES is developing MGD as a larger-population future methodology for this series.</data></node><node id="REPORT_ENUM_MI_LISTING"><data key="node_entity_id">REPORT_ENUM_MI_LISTING</data><data key="node_entity_type">report</data><data key="node_canonical_name">Enumeration Management Information Listing</data><data key="node_acronym">Enumeration MI listing</data><data key="node_domain">Identity &amp; Enumeration / Analytics</data><data key="node_description">Management-information listing referenced by enumeration policy for pending exception work.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Source establishes EBE EM3 inclusion and EAE EM exclusion; underlying report-generation store is not inferred.</data></node><node id="REPORT_FAST_FACTS_2026"><data key="node_entity_id">REPORT_FAST_FACTS_2026</data><data key="node_entity_type">report</data><data key="node_canonical_name">Fast Facts &amp; Figures About Social Security, 2026</data><data key="node_acronym">Fast Facts 2026</data><data key="node_domain">Statistical Publications / OASDI &amp; SSI</data><data key="node_description">October 2026 statistical publication highlighting core Social Security and SSI program statistics.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA states most statistics come from Annual Statistical Supplement; trust-fund operations data come from the 2026 Trustees Report.</data></node><node id="REPORT_OACT_DEMOGRAPHIC_2026"><data key="node_entity_id">REPORT_OACT_DEMOGRAPHIC_2026</data><data key="node_entity_type">data_product</data><data key="node_canonical_name">2026 Long-Range Demographic Assumptions Memorandum</data><data key="node_acronym">2026 Demographic Assumptions</data><data key="node_domain">Actuarial / Trust Funds</data><data key="node_description">OCACT Actuarial Services memorandum specifying fertility, mortality, and immigration assumptions used in the 2026 OASDI Trustees Report.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-06-09</data><data key="node_confidence">5</data><data key="node_notes">Publication/data-product entity; no software implementation is inferred.</data></node><node id="REPORT_OACT_ECONOMIC_2026"><data key="node_entity_id">REPORT_OACT_ECONOMIC_2026</data><data key="node_entity_type">report</data><data key="node_canonical_name">2026 Long-Range Economic Assumptions Memorandum</data><data key="node_acronym">2026 Economic Assumptions Memorandum</data><data key="node_domain">Actuarial / Economic Projections</data><data key="node_description">OCACT memorandum documenting key long-range economic assumptions used for the 2026 OASDI Trustees Report.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-06-09</data><data key="node_confidence">5</data><data key="node_notes">Documents assumptions; no software, database, or execution platform is inferred.</data></node><node id="REPORT_OACT_FACT_SHEET"><data key="node_entity_id">REPORT_OACT_FACT_SHEET</data><data key="node_entity_type">report_series</data><data key="node_canonical_name">Social Security Program Fact Sheet</data><data key="node_acronym">OASDI Fact Sheet</data><data key="node_domain">Actuarial / Statistical Publications</data><data key="node_description">Semiannual OCACT fact sheet presenting recent OASDI beneficiary counts, average benefits, measures of protection, and trust-fund financial data.</data><data key="node_observed_status">observed_current_semiannual</data><data key="node_observed_as_of">2026-06-30</data><data key="node_confidence">5</data><data key="node_notes">Current June 30, 2026 edition observed; physical publication-generation pipeline is not stated.</data></node><node id="REPORT_OASDI_MONTHLY_STATS"><data key="node_entity_id">REPORT_OASDI_MONTHLY_STATS</data><data key="node_entity_type">report_series</data><data key="node_canonical_name">OASDI Monthly Statistics</data><data key="node_domain">Statistical Publications / OASDI</data><data key="node_description">Historical monthly OASDI statistical publication series providing current-payment and award statistics; discontinued after the November 2007 edition but newly cataloged in SSA’s 2026 comprehensive data inventory.</data><data key="node_observed_status">historical_discontinued_currently_cataloged</data><data key="node_observed_as_of">2026-08-24</data><data key="node_confidence">5</data><data key="node_notes">Historical product retained for publication-lineage mapping. Current comparable statistics are available in Monthly Statistical Snapshot and OACT Beneficiary Data.</data></node><node id="REPORT_R194_SUPPLEMENT_2020"><data key="node_entity_id">REPORT_R194_SUPPLEMENT_2020</data><data key="node_entity_type">statistical_publication</data><data key="node_canonical_name">2020 Annual Statistical Supplement Historical Publication Vintage</data><data key="node_domain">Data Products &amp; Publication</data><data key="node_description">SSA 2020 Annual Statistical Supplement completed February 2021 and subsequently corrected in 2022, 2025, and 2026.</data><data key="node_observed_status">documented</data><data key="node_observed_as_of">2021-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="REPORT_SSAB_REPPAYEE_TRENDS_2026"><data key="node_entity_id">REPORT_SSAB_REPPAYEE_TRENDS_2026</data><data key="node_entity_type">report</data><data key="node_canonical_name">SSAB Representative Payee Trends Issue Brief (2026)</data><data key="node_acronym">Representative Payee Trends</data><data key="node_domain">Representative Payee / Research</data><data key="node_description">Social Security Advisory Board issue brief analyzing trends among adult Title II beneficiaries and SSI recipients with representative payees during 2010-2025.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">External advisory analysis; not an SSA operational system.</data></node><node id="REPORT_SSAB_SSI_REPORTING_2026"><data key="node_entity_id">REPORT_SSAB_SSI_REPORTING_2026</data><data key="node_entity_type">report</data><data key="node_canonical_name">Supplemental Security Income and Reporting Requirements (2026)</data><data key="node_acronym">SSI Reporting Requirements</data><data key="node_domain">Title XVI / Advisory / Modernization</data><data key="node_description">2026 SSAB report on SSI change-reporting burden and digital modernization opportunities.</data><data key="node_observed_status">observed_current_advisory_report</data><data key="node_observed_as_of">2026-07-25</data><data key="node_confidence">5</data><data key="node_notes">Recommendations are advisory and are not treated as deployed SSA capabilities or committed implementation plans.</data></node><node id="REPORT_SSI_ANNUAL_2026"><data key="node_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="node_entity_type">report</data><data key="node_canonical_name">2026 SSI Annual Report</data><data key="node_acronym">2026 SSI Annual Report</data><data key="node_domain">Actuarial / SSI / Publications</data><data key="node_description">Annual report on the Supplemental Security Income program with program description, 25-year recipient and cost projections, statutory history, historical/current data, and research summaries.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Issued July 2026 under the statutory annual reporting mandate.</data></node><node id="REPORT_SSI_ASR_2025"><data key="node_entity_id">REPORT_SSI_ASR_2025</data><data key="node_entity_type">report</data><data key="node_canonical_name">SSI Annual Statistical Report, 2025</data><data key="node_domain">Statistical Publications / SSI</data><data key="node_description">Annual SSA statistical publication covering SSI program size, recipients, applications, awards, disability outcomes, and eligibility events for 2025.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Released August 2026; Federal Data Catalog identifier US-GOV-SSA-3417.</data></node><node id="REPORT_STAT_SUPP_2026"><data key="node_entity_id">REPORT_STAT_SUPP_2026</data><data key="node_entity_type">report</data><data key="node_canonical_name">Annual Statistical Supplement, 2026</data><data key="node_domain">Statistical Publications / OASDI &amp; SSI</data><data key="node_description">SSA statistical publication released in sections as data become available, drawing on operational administrative records including MBR and SSR.</data><data key="node_observed_status">partial_release_2026</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-3377. SSA states the 2026 edition is being released in sections with expected completion by 2027-02-28. Run104 2026-10-07: publisher states staged release; all tables may be revised until full edition completion expected 2027-02-28.</data></node><node id="REPORT_STAT_SUPP_SERIES"><data key="node_entity_id">REPORT_STAT_SUPP_SERIES</data><data key="node_entity_type">report_series</data><data key="node_canonical_name">Annual Statistical Supplement to the Social Security Bulletin</data><data key="node_acronym">Annual Statistical Supplement</data><data key="node_domain">Research / Statistics</data><data key="node_description">SSA recurring statistical publication series for program, beneficiary, earnings, and administrative data.</data><data key="node_observed_status">observed_current_publication_series</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Run 66 adds a series-level object so methodology development can be related to the publication family without incorrectly asserting that MGD already produced the 2026 edition.</data></node><node id="REPORT_TRUSTEES_2026"><data key="node_entity_id">REPORT_TRUSTEES_2026</data><data key="node_entity_type">report</data><data key="node_canonical_name">2026 OASDI Trustees Report</data><data key="node_acronym">2026 Trustees Report</data><data key="node_domain">Actuarial / Trust Funds</data><data key="node_description">Annual report on the financial and actuarial status of the OASI and DI Trust Funds, including historical data, projections, assumptions, report tables, and supplemental single-year tables.</data><data key="node_observed_status">observed_current_publication</data><data key="node_observed_as_of">2026-06-09</data><data key="node_confidence">5</data><data key="node_notes">Published by SSA Office of the Chief Actuary.</data></node><node id="REPO_CEF"><data key="node_entity_id">REPO_CEF</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Certified Electronic Folder</data><data key="node_acronym">CEF</data><data key="node_domain">Disability Evidence</data><data key="node_description">Official electronic disability claims folder when certified as electronic.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="REPO_DA_MPRO_SHAREPOINT"><data key="node_entity_id">REPO_DA_MPRO_SHAREPOINT</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Disability Adjudication Medical Professional Relations Officer SharePoint Site</data><data key="node_acronym">DA MPRO SharePoint</data><data key="node_domain">Disability / Consultative Examinations</data><data key="node_description">Named SharePoint site used by DDS components to submit CE oversight reports, provider lists, and CE/MER fee schedules.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-02</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="REPO_DMA_ECLIENT"><data key="node_entity_id">REPO_DMA_ECLIENT</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Document Management Architecture eClient</data><data key="node_acronym">DMA eClient</data><data key="node_domain">Evidence &amp; Documents</data><data key="node_description">eDIB document repository for images and multimedia described inside the Document Management Architecture boundary.</data><data key="node_observed_status">documented_in_2018_edib_pia_current_status_unconfirmed</data><data key="node_observed_as_of">2018-02-01</data><data key="node_confidence">4</data><data key="node_notes">2018 architecture evidence only; current physical implementation unresolved.</data></node><node id="REPO_EF"><data key="node_entity_id">REPO_EF</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Electronic Folder</data><data key="node_acronym">EF</data><data key="node_domain">Disability Evidence</data><data key="node_description">Electronic disability case folder; may or may not be the official folder depending on case status.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-09</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="REPO_EMR"><data key="node_entity_id">REPO_EMR</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Enterprise Metadata Repository</data><data key="node_acronym">EMR</data><data key="node_domain">Enterprise Data / Metadata</data><data key="node_description">Non-public SSA repository of physical and logical metadata about relational databases and record structures.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-180.</data></node><node id="REPO_EVIEW_PRIVATE_SECTION"><data key="node_entity_id">REPO_EVIEW_PRIVATE_SECTION</data><data key="node_entity_type">repository_section</data><data key="node_canonical_name">eView Private Section</data><data key="node_acronym">Private Section of eView</data><data key="node_domain">Disability / Hearings / Evidence</data><data key="node_description">Restricted eView section used to gather, maintain, and view electronic ALJ and Appeals Council working-file documents.</data><data key="node_observed_status">documented_sorn_architecture_2018_current_sorn_catalog</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">2018 SORNs identify the Private Section and say it is accessible only to authorized SSA staff; current implementation details beyond eView are not inferred.</data></node><node id="REPO_L4020_SHAREPOINT"><data key="node_entity_id">REPO_L4020_SHAREPOINT</data><data key="node_entity_type">repository</data><data key="node_canonical_name">SSA-L4020 IP Recoup Forms SharePoint</data><data key="node_acronym">SSA-L4020 SharePoint</data><data key="node_domain">Program Integrity / Prisoner / Records</data><data key="node_description">Universally viewable, view-only SharePoint site used to retain completed SSA-L4020 recoupment notices for inquiry handling.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes">POMS establishes SharePoint technology and view-only access; hosting/version are not inferred.</data></node><node id="REPO_MDF"><data key="node_entity_id">REPO_MDF</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Modular Disability Folder</data><data key="node_acronym">MDF</data><data key="node_domain">Disability / Paper Case Processing</data><data key="node_description">Official paper disability folder for cases excluded from or limited in EDCS/electronic processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly preserves MDF procedures.</data></node><node id="REPO_NDR"><data key="node_entity_id">REPO_NDR</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Non Disability Repository</data><data key="node_acronym">NDR</data><data key="node_domain">Claims / Evidence</data><data key="node_description">Repository described by SSA POMS as the destination for non-disability artifacts faxed with DMA barcodes; NDR is contained within a section of Document Manager Architecture.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS distinguishes NDR storage from the NDRed application. The pre-existing Atlas NDRed record is retained unchanged pending a later schema-normalization pass.</data></node><node id="REPO_NDRED"><data key="node_entity_id">REPO_NDRED</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Non-Disability Repository for Evidentiary Documents</data><data key="node_acronym">NDRed</data><data key="node_domain">Evidence &amp; Documents</data><data key="node_description">Repository for non-disability evidentiary documents accessed/stored through Evidence Portal workflows.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-06-08</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="REPO_PAPER_DISABILITY_FOLDER"><data key="node_entity_id">REPO_PAPER_DISABILITY_FOLDER</data><data key="node_entity_type">repository</data><data key="node_canonical_name">Paper Disability Claims Folder</data><data key="node_acronym">Paper Disability Folder</data><data key="node_domain">Disability / Evidence / Exception Processing</data><data key="node_description">Paper disability claim or appeal folder used when an EDCS case cannot remain fully electronic, including certain former-SSN/new-SSN exception cases.</data><data key="node_observed_status">observed_current_exception_processing</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS requires conversion to a paper folder for specified new-SSN cases; physical storage location and retention implementation are not inferred.</data></node><node id="REPO_PIR_SHARED_SITE"><data key="node_entity_id">REPO_PIR_SHARED_SITE</data><data key="node_entity_type">repository</data><data key="node_canonical_name">PIR Shared Internal Document Site</data><data key="node_acronym">PIR Shared Site</data><data key="node_domain">IT Governance / Investment Management</data><data key="node_description">Unnamed shared internal website SSA used to retain Post-Implementation Review documents.</data><data key="node_observed_status">documented_historical_current_through_2026_audit</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">OIG says the site lacked controls linking dashboard data to source documents. Product/platform is not publicly identified.</data></node><node id="REPO_SOA_SERVICE_REGISTRY"><data key="node_entity_id">REPO_SOA_SERVICE_REGISTRY</data><data key="node_entity_type">repository</data><data key="node_canonical_name">SOA - Service Registry and Repository</data><data key="node_acronym">SOA</data><data key="node_domain">Infrastructure / Service-Oriented Architecture</data><data key="node_description">Registry/repository used to support software distribution and management and to store technical and business metadata for web services, framework components, and legacy utilities.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA enterprise inventory identifier US-GOV-SSA-1791. Source keywords include WSRR but do not establish a vendor/product expansion, so none is inferred.</data></node><node id="REPO_SSA_VENDOR"><data key="node_entity_id">REPO_SSA_VENDOR</data><data key="node_entity_type">repository</data><data key="node_canonical_name">SSA Vendor Repository</data><data key="node_acronym">Vendor Repository</data><data key="node_domain">Acquisition / Vendor Market Research</data><data key="node_description">SSA repository/database containing vendor capability information for market research by SSA personnel.</data><data key="node_observed_status">observed_current_source</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA instructions say information is available to all SSA components for market research and remains in the repository for approximately one year before deletion unless resubmitted.</data></node><node id="REPO_SSITMS_PRECEDENTS"><data key="node_entity_id">REPO_SSITMS_PRECEDENTS</data><data key="node_entity_type">repository</data><data key="node_canonical_name">SSITMS SharePoint Repository for Precedents</data><data key="node_acronym">SSITMS Precedent Repository</data><data key="node_domain">Title XVI / Resources / Trusts</data><data key="node_description">SharePoint repository reached through SSITMS that stores pooled-trust and IGRA trust precedents and related legal evaluations.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS explicitly identifies the repository and instructs Regional Trust Leads to maintain precedents there.</data></node><node id="SCR_MCS_TOTL"><data key="node_entity_id">SCR_MCS_TOTL</data><data key="node_entity_type">interface</data><data key="node_canonical_name">MCS Totalization Screen</data><data key="node_acronym">TOTL</data><data key="node_domain">Title II / International / Earnings</data><data key="node_description">Modernized Claims System Totalization screen used in applicable foreign-benefit/Totalization claims to generate an earnings record for the foreign country.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Logical MCS screen; no separate backend is inferred.</data></node><node id="SERVICE_SSA_PMF"><data key="node_entity_id">SERVICE_SSA_PMF</data><data key="node_entity_type">service</data><data key="node_canonical_name">SSA Print/Mail Facility</data><data key="node_acronym">PMF</data><data key="node_domain">Notices / Printing &amp; Mailing</data><data key="node_description">SSA facility/service identified in current POMS as printing and mailing on-request Social Security Statements.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">No print technology, vendor stack, or hosting boundary inferred.</data></node><node id="STD_SOC"><data key="node_entity_id">STD_SOC</data><data key="node_entity_type">external_data_reference</data><data key="node_canonical_name">Standard Occupational Classification</data><data key="node_acronym">SOC</data><data key="node_domain">Disability / Occupational Data</data><data key="node_description">Federal occupational classification standard used by BLS to classify ORS data; ORS Wave 2 uses the 2018 SOC.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="STORE_SERS_CONSERVED"><data key="node_entity_id">STORE_SERS_CONSERVED</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SERS Conserved Funds Store</data><data key="node_domain">Representative Payee / Remittances</data><data key="node_description">SERS store used for conserved-fund remittances when no associated programmatic debt is found.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-02-01</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="STORE_SERS_PROGRAMMATIC"><data key="node_entity_id">STORE_SERS_PROGRAMMATIC</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">SERS Programmatic Store</data><data key="node_domain">Debt &amp; Remittances</data><data key="node_description">SERS store that retrieves and displays established programmatic debts/overpayments associated with MBR, SSR, ROAR or ECO.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-02-01</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="STRUCT_CDW"><data key="node_entity_id">STRUCT_CDW</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Case Development Worksheet</data><data key="node_acronym">CDW</data><data key="node_domain">Disability / Case Development</data><data key="node_description">Case-development worksheet receiving information from DCPS case notes during disability evidence development.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-01-06</data><data key="node_confidence">5</data><data key="node_notes">Current CE instructions explicitly say DCPS Case Note can write to CDW.</data></node><node id="STRUCT_DDE"><data key="node_entity_id">STRUCT_DDE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Disability Determination Explanation</data><data key="node_acronym">DDE</data><data key="node_domain">Disability / Adjudication</data><data key="node_description">Electronic explanation/rationale structure used in DCPS to document medical and non-medical factors, case notes and determination rationale.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-31</data><data key="node_confidence">5</data><data key="node_notes">Current POMS repeatedly maps DCPS pages and notes to the DDE.</data></node><node id="STRUCT_DSPE"><data key="node_entity_id">STRUCT_DSPE</data><data key="node_entity_type">data_structure</data><data key="node_canonical_name">Post Eligibility Transaction Record</data><data key="node_acronym">DSPE</data><data key="node_domain">Title XVI / Post-Eligibility</data><data key="node_description">Post-eligibility subsection of the Supplemental Security Record.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">US-GOV-SSA-183.</data></node><node id="SURVEY_NBF_1991"><data key="node_entity_id">SURVEY_NBF_1991</data><data key="node_entity_type">survey</data><data key="node_canonical_name">1991 New Beneficiary Follow-up</data><data key="node_acronym">NBF</data><data key="node_domain">Research / Survey Data</data><data key="node_description">Second-round longitudinal survey updating circumstances of New Beneficiary Survey respondents.</data><data key="node_observed_status">historical_completed</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA documents updates to marital status, household composition, economic profile, health, family contacts, postretirement employment, widowhood/divorce effects, household moves, and reasons for moving.</data></node><node id="SURVEY_NBS_1982"><data key="node_entity_id">SURVEY_NBS_1982</data><data key="node_entity_type">survey</data><data key="node_canonical_name">1982 New Beneficiary Survey</data><data key="node_acronym">NBS</data><data key="node_domain">Research / Survey Data</data><data key="node_description">National cross-sectional survey of new beneficiaries that forms the initial survey basis of NBDS.</data><data key="node_observed_status">historical_completed</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA documents demographic, employment, marital, childbearing, household, health, income/assets, and program-knowledge variables.</data></node><node id="SVC_AMAZON_CONNECT"><data key="node_entity_id">SVC_AMAZON_CONNECT</data><data key="node_entity_type">service</data><data key="node_canonical_name">Amazon Connect</data><data key="node_acronym">AWS Connect</data><data key="node_domain">Contact Center / Cloud</data><data key="node_description">Cloud Contact Center as a Service used by SSA for telephony, including toll-free capability.</data><data key="node_observed_status">observed_broad_deployment_2026</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">GAO documented SSA obtaining required toll-free services through Amazon Connect in 2025. This run does not infer the post-option-period contract status in October 2026. Run 21 OIG audit documents rollout to all field offices/card centers, processing centers, International Call Center, and remaining DDS/DPB/DPU by winter 2026; September 2026 agencywide completion appears as a plan, not independently verified completion. OIG September 2026 reported SSA generally experienced improved telephone service platform performance after the August 2024 AWS Connect transition, while identifying BPA oversight/performance-measure weaknesses.</data></node><node id="SVC_APPT_QUESTIONNAIRE"><data key="node_entity_id">SVC_APPT_QUESTIONNAIRE</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">SSA.gov Make an Appointment Questionnaire</data><data key="node_domain">Customer Service / Scheduling</data><data key="node_description">Public SSA.gov questionnaire using conditional logic to guide customers on whether an appointment is needed and how to schedule or complete service.</data><data key="node_observed_status">observed_launched</data><data key="node_observed_as_of">2025-07-21</data><data key="node_confidence">5</data><data key="node_notes">EM-25035 REV describes English/Spanish availability and July 21, 2025 launch.</data></node><node id="SVC_ASAP"><data key="node_entity_id">SVC_ASAP</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Automated Standard Application Payments</data><data key="node_acronym">ASAP</data><data key="node_domain">Grants / Payments</data><data key="node_description">Federal electronic payment-account service that SSA grant recipients are required to establish for grant payments.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG grants FAQ explicitly requires electronic payment accounts with ASAP.</data></node><node id="SVC_AVC"><data key="node_entity_id">SVC_AVC</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Address Verification Contractor Service</data><data key="node_acronym">AVC</data><data key="node_domain">Payments / Debt Collection / Address Provenance</data><data key="node_description">Contractor-supplied address verification service used by SSA External Collection Operation to obtain a verified debtor address before external-collection notices.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2025-05-08</data><data key="node_confidence">5</data><data key="node_notes">The public policy does not identify the contractor/vendor. Treat returned address as an external debt-collection lookup result, not an SSA program-master address.</data></node><node id="SVC_AVS"><data key="node_entity_id">SVC_AVS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Account Verification Service</data><data key="node_acronym">AVS</data><data key="node_domain">Payments / Payment Integrity</data><data key="node_description">Treasury Bureau of the Fiscal Service payment-integrity service used for real-time verification of bank-account existence, status, and ownership.</data><data key="node_observed_status">observed_current_ssa_use</data><data key="node_observed_as_of">2026</data><data key="node_confidence">5</data><data key="node_notes">SSA FY2027 budget says a series of real-time bank-verification checks including AVS was implemented in March 2025.</data></node><node id="SVC_BSO_NAME_SSN_ERRORS"><data key="node_entity_id">SVC_BSO_NAME_SSN_ERRORS</data><data key="node_entity_type">service</data><data key="node_canonical_name">View Wage Report Name/SSN Errors</data><data key="node_acronym">View Name/SSN Errors</data><data key="node_domain">Earnings / Employer / Digital Services</data><data key="node_description">Business Services Online service through which authorized employers or submitters can retrieve wage-report name and SSN mismatch information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Access requires BSO registration and activation-code process; no underlying database is inferred.</data></node><node id="SVC_BWS"><data key="node_entity_id">SVC_BWS</data><data key="node_entity_type">interface</data><data key="node_canonical_name">BOND Web Services</data><data key="node_acronym">BWS</data><data key="node_domain">Disability Demonstrations / BOND</data><data key="node_description">Internet-accessible BOND interface that provided a one-way BODS-to-BSAS data exchange and supported server-to-server ping/bulk-file transfer.</data><data key="node_observed_status">historical_bond_project</data><data key="node_observed_as_of">2017-02-13</data><data key="node_confidence">5</data><data key="node_notes">BOND project architecture; current operation is not inferred.</data></node><node id="SVC_CONTROL_TRACK_WS_MI"><data key="node_entity_id">SVC_CONTROL_TRACK_WS_MI</data><data key="node_entity_type">service</data><data key="node_canonical_name">Control And Tracking Web Service MI</data><data key="node_acronym">Control And Tracking Web Service MI</data><data key="node_domain">Enterprise Integration / eServices</data><data key="node_description">Web service that processes application requests for submission of control numbers and status inserts.</data><data key="node_observed_status">observed_current_catalog</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-14. Do not infer implementation protocol from the term web service.</data></node><node id="SVC_CPARS"><data key="node_entity_id">SVC_CPARS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Contractor Performance Assessment Reporting System</data><data key="node_acronym">CPARS</data><data key="node_domain">Procurement / Contractor Performance</data><data key="node_description">Department of Defense web-enabled application used by SSA to collect and manage contractor past-performance evaluations.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA OAG says SSA has utilized CPARS since October 1, 2010; current production details are controlled by the external service.</data></node><node id="SVC_CROSS_SERVICING"><data key="node_entity_id">SVC_CROSS_SERVICING</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Treasury Cross-Servicing</data><data key="node_domain">External Debt Collection</data><data key="node_description">Fiscal Service delinquent-debt collection service using letters, calls, skip tracing, TOP, private collection agencies and AWG.</data><data key="node_observed_status">observed_current_treasury_service</data><data key="node_observed_as_of">2026-03-16</data><data key="node_confidence">5</data><data key="node_notes">SSA-specific routing through CRS is future/implementation-dependent.</data></node><node id="SVC_CRS"><data key="node_entity_id">SVC_CRS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Centralized Receivables Service</data><data key="node_acronym">CRS</data><data key="node_domain">External Debt Collection</data><data key="node_description">Bureau of the Fiscal Service shared service for current and early-delinquency federal accounts receivable, invoicing, follow-up, payment plans and electronic collection.</data><data key="node_observed_status">ssa_implementation_in_progress</data><data key="node_observed_as_of">2025-08-31</data><data key="node_confidence">5</data><data key="node_notes">SSA FY2025 AFR says SSA is working with Fiscal Service to implement CRS for debtors in non-pay status.</data></node><node id="SVC_DA_SDRM_FORMS_SITE"><data key="node_entity_id">SVC_DA_SDRM_FORMS_SITE</data><data key="node_entity_type">internal_site</data><data key="node_canonical_name">Disability Adjudication SDRM Intranet Financial Forms Site</data><data key="node_acronym">DA SDRM Intranet</data><data key="node_domain">Disability / DDS / Forms Distribution</data><data key="node_description">Internal Disability Adjudication intranet website through which State DDSs can obtain electronic financial-management forms.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled only as the explicitly named intranet distribution surface; hosting and repository technology are not public.</data></node><node id="SVC_DIRECT_EXPRESS"><data key="node_entity_id">SVC_DIRECT_EXPRESS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Direct Express</data><data key="node_acronym">DE</data><data key="node_domain">Benefit Payments / Electronic Payments</data><data key="node_description">Treasury prepaid debit-card program used to receive Federal benefit payments electronically without a conventional bank account.</data><data key="node_observed_status">observed_current_transition</data><data key="node_observed_as_of">2026-05-19</data><data key="node_confidence">5</data><data key="node_notes">New SSA enrollments moved to Fifth Third Bank beginning May 18, 2026 while existing Comerica cardholders transition in phases.</data></node><node id="SVC_DLDV"><data key="node_entity_id">SVC_DLDV</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">AAMVA/DLDV Driver License Data Verification</data><data key="node_acronym">DLDV</data><data key="node_domain">Identity / External Verification</data><data key="node_description">State driver-license/state-ID verification capability used by iSSNRC for participating jurisdictions.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">POMS labels the participation column AAMVA/DLDV but does not expose the service expansion, API, persistence, or exact transport mechanism.</data></node><node id="SVC_DNP"><data key="node_entity_id">SVC_DNP</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Do Not Pay</data><data key="node_domain">External Shared Services / Payment Integrity</data><data key="node_description">Treasury Bureau of the Fiscal Service shared payment-integrity service that provides federal and state agencies centralized access to authoritative data for identity, eligibility, and payment verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">External Treasury shared service. SSA is a data owner for several DNP data sources, but DNP is not modeled as an SSA-hosted platform.</data></node><node id="SVC_DNP_CONNECT"><data key="node_entity_id">SVC_DNP_CONNECT</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Do Not Pay Connect</data><data key="node_domain">External Shared Services / Payment Integrity / API</data><data key="node_description">Secure Treasury Do Not Pay API product for real-time system-to-system eligibility screening, including single or batch queries and returned risk/confidence information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Treasury explicitly documents API access. SSA-specific application consumers are not identified in the reviewed public sources.</data></node><node id="SVC_DNP_WEB"><data key="node_entity_id">SVC_DNP_WEB</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Do Not Pay Web Portal</data><data key="node_domain">External Shared Services / Payment Integrity</data><data key="node_description">Secure Treasury web portal providing on-demand searches, batch-result review, continuous-monitoring alerts, and reporting over Do Not Pay data sources.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">External Treasury service. No SSA-specific user population is inferred.</data></node><node id="SVC_DOCUTECTOR"><data key="node_entity_id">SVC_DOCUTECTOR</data><data key="node_entity_type">external_reference_service</data><data key="node_canonical_name">Docutector</data><data key="node_domain">Identity / Enumeration / Document Authentication</data><data key="node_description">Document-reference service used by SSA employees to compare identity documents with visual standards and exhibits, including foreign driver licenses.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS establishes SSA use but does not establish SSA ownership, hosting, vendor contract, or direct system integration.</data></node><node id="SVC_E1693"><data key="node_entity_id">SVC_E1693</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Electronic Form SSA-1693</data><data key="node_acronym">e1693</data><data key="node_domain">Representation / Digital Forms</data><data key="node_description">SSA electronic service for completing and multi-party signing the Fee Agreement for Representation Before the Social Security Administration.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current secure service supports the initiating representative, claimant, and up to five additional representatives; current page identifies Adobe Sign email workflow.</data></node><node id="SVC_E1696"><data key="node_entity_id">SVC_E1696</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Electronic Form SSA-1696</data><data key="node_acronym">e1696</data><data key="node_domain">Representation / Digital Forms</data><data key="node_description">Fully electronic representative-appointment service through which representative and claimant sign and submit Form SSA-1696.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">POMS states the servicing FO receives an SSA-1696-APP electronic image via WorkTrack.</data></node><node id="SVC_ECBSV_API"><data key="node_entity_id">SVC_ECBSV_API</data><data key="node_entity_type">interface</data><data key="node_canonical_name">eCBSV Verification API</data><data key="node_domain">Identity Verification</data><data key="node_description">Current external verification API exposed for eCBSV permitted entities.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SVC_EE_UTILITY"><data key="node_entity_id">SVC_EE_UTILITY</data><data key="node_entity_type">computational_service</data><data key="node_canonical_name">Entitlement/Eligibility Utility</data><data key="node_acronym">EE</data><data key="node_domain">Title II / Computation</data><data key="node_description">Title II entitlement/eligibility computational utility identified for conversion analysis and modernization.</data><data key="node_observed_status">historical_modernization_target</data><data key="node_observed_as_of">2020</data><data key="node_confidence">5</data><data key="node_notes">Acronym EE is source-explicit in the FY2020 budget; do not confuse this utility with other SSA uses of EE such as earnings-related diaries.</data></node><node id="SVC_EFAX"><data key="node_entity_id">SVC_EFAX</data><data key="node_entity_type">submission_channel</data><data key="node_canonical_name">Electronic Fax</data><data key="node_acronym">eFax</data><data key="node_domain">Enterprise Intake / Representation / Document Submission</data><data key="node_description">Electronic fax submission channel identified by current SSA policy as an accepted route for paper Form SSA-1696 and other document intake.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a submission channel only. The underlying fax platform, vendor, routing service, storage, and gateway architecture remain unverified.</data></node><node id="SVC_EN_PORTAL"><data key="node_entity_id">SVC_EN_PORTAL</data><data key="node_entity_type">external_portal</data><data key="node_canonical_name">Employment Network Portal</data><data key="node_acronym">EN Portal</data><data key="node_domain">Ticket to Work / External Services</data><data key="node_description">Secure web interface through which Employment Networks and State Vocational Rehabilitation users interacted with SSA Ticket to Work functions in the IDMS/iTOPSS environment.</data><data key="node_observed_status">historically_documented_2017</data><data key="node_observed_as_of">2017-02-13</data><data key="node_confidence">4</data><data key="node_notes">2017 architecture evidence only; current portal implementation/name is not inferred.</data></node><node id="SVC_EREWS"><data key="node_entity_id">SVC_EREWS</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Electronic Records Express Web Services</data><data key="node_acronym">EREWS</data><data key="node_domain">Disability / Evidence Exchange</data><data key="node_description">High-volume machine-to-machine Internet interface documented by SSA for business partners to submit electronic disability evidence without a user interface.</data><data key="node_observed_status">documented_historical_2007_current_status_unconfirmed</data><data key="node_observed_as_of">2007-07-02</data><data key="node_confidence">5</data><data key="node_notes">SSA’s 2007 client guide documents the technical interface. A current ERE web page still documents ERE generally, but this run does not claim the 2007 EREWS implementation remains deployed unchanged.</data></node><node id="SVC_ERE_EOR"><data key="node_entity_id">SVC_ERE_EOR</data><data key="node_entity_type">service</data><data key="node_canonical_name">Electronic Outbound Request</data><data key="node_acronym">eOR</data><data key="node_domain">Disability / Evidence</data><data key="node_description">ERE feature for electronic delivery of consultative-examination and evidence request packages and provider responses.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Supports CE/evidence requests, responses and response tracking.</data></node><node id="SVC_ERQY"><data key="node_entity_id">SVC_ERQY</data><data key="node_entity_type">service</data><data key="node_canonical_name">Employer Report Query</data><data key="node_acronym">ERQY</data><data key="node_domain">Earnings / Employer</data><data key="node_description">Employer report/adjustment query used to inspect employer filing and wage-report problem information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SVC_EVVE"><data key="node_entity_id">SVC_EVVE</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Electronic Verification of Vital Events</data><data key="node_acronym">EVVE</data><data key="node_domain">Identity / Enumeration</data><data key="node_description">Verification service used by authorized SSA staff to query participating state vital-record systems for birth-record verification.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Verification only; POMS explicitly says no certification queries. Run 84: current POMS was revalidated and output-level result, state-file-number, and possible-death indicators are now modeled separately.</data></node><node id="SVC_EWRWS"><data key="node_entity_id">SVC_EWRWS</data><data key="node_entity_type">interface</data><data key="node_canonical_name">Electronic Wage Reporting Web Service</data><data key="node_acronym">EWRWS</data><data key="node_domain">Earnings / Employer</data><data key="node_description">Web-service channel for existing payroll/tax-reporting consolidators to submit EFW2 wage reports electronically and retrieve submission status.</data><data key="node_observed_status">observed_current_restricted_onboarding</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current SSA material still describes the service but states SSA is not accepting new EWRWS users/consolidators.</data></node><node id="SVC_FEDCONNECT"><data key="node_entity_id">SVC_FEDCONNECT</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">FedConnect</data><data key="node_acronym">FedConnect</data><data key="node_domain">Procurement / External Service</data><data key="node_description">External federal procurement collaboration/service named by SSA as the required registration and application channel for interested vocational-expert vendors when an OHO BPA solicitation is active.</data><data key="node_observed_status">observed_current_conditional_use</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA states no VE BPA solicitation is currently active. The entity represents the named procurement channel, not an SSA-owned system.</data></node><node id="SVC_FPLS"><data key="node_entity_id">SVC_FPLS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Federal Parent Locator Service</data><data key="node_acronym">FPLS</data><data key="node_domain">External Data Exchange / Child Support</data><data key="node_description">Federal parent-locator process supporting child-support locate requests and containing the DRLIF and ESKARI exchanges documented in SSA inventory.</data><data key="node_observed_status">observed_current_exchange_service</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">SSA inventory describes FPLS function and its two exchanges; it does not identify the SSA-side hosting or source repositories used to fulfill all response fields.</data></node><node id="SVC_GEN_INSURED"><data key="node_entity_id">SVC_GEN_INSURED</data><data key="node_entity_type">computational_service</data><data key="node_canonical_name">General Insured Status Utility</data><data key="node_domain">Title II / Computation</data><data key="node_description">Title II computational utility identified by SSA as a completed or near-completed modernization target in the FY2019 Computational Services initiative.</data><data key="node_observed_status">historical_modernization_target</data><data key="node_observed_as_of">2019</data><data key="node_confidence">5</data><data key="node_notes">Public source does not identify the utility's physical deployment, service endpoint, data store, or current 2026 implementation.</data></node><node id="SVC_GINVOICING"><data key="node_entity_id">SVC_GINVOICING</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">G-Invoicing</data><data key="node_acronym">G-Invoicing</data><data key="node_domain">Finance / Intragovernmental</data><data key="node_description">Governmentwide Treasury intragovernmental buy/sell agreement and transaction service with which SSOARS is integrated.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-01-15</data><data key="node_confidence">5</data><data key="node_notes">SSA FY2025 reporting describes ongoing G-Invoicing releases and controls; other current CMAs also use G-Invoicing/IPAC.</data></node><node id="SVC_GOGOV"><data key="node_entity_id">SVC_GOGOV</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">GO.gov Federal Travel and Expense Solution</data><data key="node_acronym">GO.gov</data><data key="node_domain">Travel / Shared Service</data><data key="node_description">GSA governmentwide cloud travel-and-expense SaaS for civilian agencies; SSA FY2025 planning called for new real-time interfaces during FY2026.</data><data key="node_observed_status">governmentwide_live_ssa_interface_plan_unconfirmed</data><data key="node_observed_as_of">2026-09-21</data><data key="node_confidence">5</data><data key="node_notes">GSA confirms GO.gov is live for early adopters and rolls out through 2027. SSA-specific interface completion was not independently confirmed in this run.</data></node><node id="SVC_GRANTSOLUTIONS"><data key="node_entity_id">SVC_GRANTSOLUTIONS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">GrantSolutions</data><data key="node_acronym">GS</data><data key="node_domain">Grants / Award Management</data><data key="node_description">Federal grants management service used for SSA continuation grant applications and electronic award notifications.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG instructions identify GrantSolutions for continuation grants and successful-application notifications.</data></node><node id="SVC_GRANTS_GOV"><data key="node_entity_id">SVC_GRANTS_GOV</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Grants.gov</data><data key="node_domain">Grants / External Service</data><data key="node_description">Federal grants submission service used for SSA competitive discretionary grant applications.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG grant instructions direct competitive applications through Grants.gov.</data></node><node id="SVC_GRATES"><data key="node_entity_id">SVC_GRATES</data><data key="node_entity_type">computational_service</data><data key="node_canonical_name">General Rates Utility</data><data key="node_acronym">GRATES</data><data key="node_domain">Title II / Computation</data><data key="node_description">Title II computational utility identified as a modernization target in SSA's Benefits-domain Computational Services initiative.</data><data key="node_observed_status">historical_modernization_target</data><data key="node_observed_as_of">2019</data><data key="node_confidence">5</data><data key="node_notes">SSA planned conversion from COBOL; current physical implementation is not established by this historical budget source.</data></node><node id="SVC_GRUMPI"><data key="node_entity_id">SVC_GRUMPI</data><data key="node_entity_type">computational_service</data><data key="node_canonical_name">General Recomputation/Computation Utility for Maximum Benefit and Primary Insurance Amount Information</data><data key="node_acronym">GRUMPI</data><data key="node_domain">Title II / Computation</data><data key="node_description">Title II computational utility for maximum-benefit and primary-insurance-amount computation identified as a modernization target.</data><data key="node_observed_status">historical_modernization_target</data><data key="node_observed_as_of">2019</data><data key="node_confidence">5</data><data key="node_notes">SSA planned conversion from COBOL under the Computational Services initiative; exact current implementation is not established by the source.</data></node><node id="SVC_GSA_EBUY"><data key="node_entity_id">SVC_GSA_EBUY</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">GSA eBuy</data><data key="node_acronym">eBuy</data><data key="node_domain">Procurement / External Service</data><data key="node_description">GSA electronic RFQ/RFP service that SSA says it often uses for products and services under GSA schedules and technology contracts.</data><data key="node_observed_status">observed_current_oag_guidance</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG/OSDBU FAQ.</data></node><node id="SVC_GUVERF02"><data key="node_entity_id">SVC_GUVERF02</data><data key="node_entity_type">service</data><data key="node_canonical_name">SSN Verification Service / GUVERF02</data><data key="node_acronym">GUVERF02</data><data key="node_domain">Identity Verification</data><data key="node_description">Service invoked by Java applications through a WebSphere/CICS interface to compare identity fields with Numident.</data><data key="node_observed_status">cataloged_legacy_metadata</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Underlying inventory metadata is 2018.</data></node><node id="SVC_I1020"><data key="node_entity_id">SVC_I1020</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Internet Extra Help Application</data><data key="node_acronym">i1020</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">Online SSA application for Medicare Part D Extra Help.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS explicitly says i1020 does not use or interface with MAPS screens for initial input.</data></node><node id="SVC_IDME"><data key="node_entity_id">SVC_IDME</data><data key="node_entity_type">service</data><data key="node_canonical_name">ID.me</data><data key="node_domain">External Identity Service</data><data key="node_description">External identity/sign-in service currently accepted for SSA employer services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled only as the current BSO sign-in dependency stated by SSA.</data></node><node id="SVC_IPAC"><data key="node_entity_id">SVC_IPAC</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Intra-Governmental Payment and Collection System</data><data key="node_acronym">IPAC</data><data key="node_domain">Finance / Intragovernmental</data><data key="node_description">Automated standardized interagency funds-transfer mechanism for Federal Program Agencies, defined by SSA Data Exchange guidance as supporting real-time funds transfer between agencies.</data><data key="node_observed_status">defined_in_current_ssa_data_exchange_glossary</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">SSA glossary establishes the system and function but does not by itself establish a specific SSA application integration path.</data></node><node id="SVC_ITS_GOV"><data key="node_entity_id">SVC_ITS_GOV</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">International Treasury Services</data><data key="node_acronym">ITS.gov</data><data key="node_domain">External Payment Service / Treasury</data><data key="node_description">U.S. Treasury system used in IDD processing to maintain or consult international banking and enrollment information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-08-25</data><data key="node_confidence">5</data><data key="node_notes">Current country-specific POMS requires same-day ITS.gov updates for certain IDD actions.</data></node><node id="SVC_JD_POWER_VALUES"><data key="node_entity_id">SVC_JD_POWER_VALUES</data><data key="node_entity_type">external_data_service</data><data key="node_canonical_name">J.D. Power Values Online</data><data key="node_domain">Title XVI / Resource Valuation</data><data key="node_description">Subscription-based vehicle valuation service SSA instructs employees to use for vehicle current market value determinations in SSI resource cases.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">POMS directs staff to the SSA-provided J.D. Power Values Online guide and Average Trade-In Value.</data></node><node id="SVC_LEXISNEXIS_ACCURINT"><data key="node_entity_id">SVC_LEXISNEXIS_ACCURINT</data><data key="node_entity_type">external_data_service</data><data key="node_canonical_name">LexisNexis Accurint</data><data key="node_acronym">Accurint</data><data key="node_domain">External Data / Property &amp; Locate</data><data key="node_description">Commercial third-party data service/database used by SSA’s NHRP electronic search process to identify potential non-home real property ownership and values.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-09-10</data><data key="node_confidence">5</data><data key="node_notes">Authoritative SSA POMS establishes use. Results are leads and may be inaccurate/incomplete; independent verification is required before adverse action unless policy permits accepting the claimant’s allegation.</data></node><node id="SVC_LOGIN_GOV"><data key="node_entity_id">SVC_LOGIN_GOV</data><data key="node_entity_type">service</data><data key="node_canonical_name">Login.gov</data><data key="node_domain">External Identity Service</data><data key="node_description">Federal identity/sign-in service currently accepted for SSA employer services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Modeled only as the current BSO sign-in dependency stated by SSA.</data></node><node id="SVC_MYSSA_ADJ_FORMS"><data key="node_entity_id">SVC_MYSSA_ADJ_FORMS</data><data key="node_entity_type">service</data><data key="node_canonical_name">Online Disability Adjudication Forms</data><data key="node_domain">Digital Service / Appeals</data><data key="node_description">my Social Security capability for online submission of HA-4631, HA-4632 and HA-4633.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-21</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SVC_MYSSA_APPEALS_STATUS"><data key="node_entity_id">SVC_MYSSA_APPEALS_STATUS</data><data key="node_entity_type">service</data><data key="node_canonical_name">Hearings and Appeals Claim Status Tracker</data><data key="node_domain">Digital Service / Appeals</data><data key="node_description">my Social Security service providing hearing- and Appeals Council-level claim status, estimates and milestone updates.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-21</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SVC_MYSSA_HEARING_NOTICES"><data key="node_entity_id">SVC_MYSSA_HEARING_NOTICES</data><data key="node_entity_type">service</data><data key="node_canonical_name">Digital Hearing Notices and Proffer Letters</data><data key="node_domain">Digital Service / Appeals</data><data key="node_description">my Social Security Message Center capability for proffer letters and additional hearing-related notices.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-21</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SVC_MYSSA_MESSAGE_CENTER"><data key="node_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="node_entity_type">service</data><data key="node_canonical_name">my Social Security Message Center</data><data key="node_domain">Digital Service / Notifications</data><data key="node_description">Message-center service within my Social Security used for customer receipts and secure online notices, including hearing-related notices and proffer letters.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Kept separate from the Representative Payee Message Center, which SSA documents for representative-payee business.</data></node><node id="SVC_NATIONAL_800"><data key="node_entity_id">SVC_NATIONAL_800</data><data key="node_entity_type">service</data><data key="node_canonical_name">National 800 Number Service</data><data key="node_acronym">N8NN</data><data key="node_domain">Customer Service / Telephone</data><data key="node_description">SSA's nationwide toll-free telephone service for public customer support and automated services.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current SSA performance pages report National 800 Number service metrics through August 2026.</data></node><node id="SVC_NCOA_LICENSED_VENDOR"><data key="node_entity_id">SVC_NCOA_LICENSED_VENDOR</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Licensed NCOA Matching Service</data><data key="node_acronym">NCOA Licensed Vendor</data><data key="node_domain">External / Address / USPS</data><data key="node_description">Unidentified licensed vendor service through which SSA Title II address records are matched against USPS National Change of Address data four times per year.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">The authoritative source establishes the licensed-vendor function but does not identify the vendor, product, hosting, or transport. No vendor identity is inferred.</data></node><node id="SVC_OFFICE_LOCATOR"><data key="node_entity_id">SVC_OFFICE_LOCATOR</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Social Security Office Locator</data><data key="node_acronym">Office Locator</data><data key="node_domain">Operations / Public Service</data><data key="node_description">Public locator service used to find SSA field offices and related office information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA describes Office Locator as the primary tool for locating offices; DOORS information underpins it.</data></node><node id="SVC_OHO_CENTRAL_PRINT"><data key="node_entity_id">SVC_OHO_CENTRAL_PRINT</data><data key="node_entity_type">service</data><data key="node_canonical_name">OHO Central Print</data><data key="node_domain">Hearings &amp; Appeals / Correspondence</data><data key="node_description">Centralized print/mail service used for most OHO notices, decisions, dismissals and correspondence.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Vendor identity is not asserted in this run.</data></node><node id="SVC_OHO_LOCATOR"><data key="node_entity_id">SVC_OHO_LOCATOR</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">OHO Hearing Office Locator</data><data key="node_acronym">Hearing Office Locator</data><data key="node_domain">Hearings &amp; Appeals / Public Service</data><data key="node_description">Public Office of Hearings Operations locator providing hearing-office addresses, telephone/fax details, hours, mailing addresses, and service-area information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The Data.gov hearing-office location dataset lists the Hearing Office Locator HTML page as a distribution; exact backend data-generation system is not public.</data></node><node id="SVC_ONLINE_BILL_PAY"><data key="node_entity_id">SVC_ONLINE_BILL_PAY</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Online Bill Pay</data><data key="node_domain">External Payment Service</data><data key="node_description">Financial-institution bill-payment channel used to repay SSA debts using the SSA Remittance ID.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-16</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SVC_ONLINE_DIB_APP"><data key="node_entity_id">SVC_ONLINE_DIB_APP</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Online Disability Benefit Application</data><data key="node_acronym">Online DIB Application</data><data key="node_domain">Title II Disability / Digital Service</data><data key="node_description">Named SSA online disability-benefit application surface that records Internet filing and supplies an application for Claims Representative retrieval and entry into MCS.</data><data key="node_observed_status">observed_current_public_service</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data documentation names this surface. Exact physical identity with iClaim or another shared frontend is not established.</data></node><node id="SVC_ONLINE_RIB_APP"><data key="node_entity_id">SVC_ONLINE_RIB_APP</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Online Retirement Benefit Application</data><data key="node_acronym">Online RIB Application</data><data key="node_domain">Title II / Digital Service</data><data key="node_description">Named SSA online retirement-benefit application surface that records Internet filing and supplies an application for Claims Representative retrieval and entry into MCS.</data><data key="node_observed_status">observed_current_public_service</data><data key="node_observed_as_of">2026-07-10</data><data key="node_confidence">5</data><data key="node_notes">Current Open Data documentation names this surface. Its exact physical relationship to the broader iClaim entity is not established and is not inferred.</data></node><node id="SVC_ONLINE_VIDEO_HEARINGS"><data key="node_entity_id">SVC_ONLINE_VIDEO_HEARINGS</data><data key="node_entity_type">service</data><data key="node_canonical_name">SSA Online Video Hearings</data><data key="node_domain">Hearings / Remote Appearance</data><data key="node_description">Remote hearing service allowing claimants and representatives to appear by internet video.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA uses Microsoft Teams; the official proceeding is recorded as audio, not video.</data></node><node id="SVC_OPTS_COC"><data key="node_entity_id">SVC_OPTS_COC</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Online Certificate of Coverage Request Service</data><data key="node_acronym">opts.ssa.gov</data><data key="node_domain">International / Totalization / Digital Service</data><data key="node_description">SSA online service at opts.ssa.gov for employer and self-employed certificate-of-coverage requests.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Transport, persistence, and backend implementation are not disclosed by the public policy.</data></node><node id="SVC_OUTBOUND_CALL_TRUST"><data key="node_entity_id">SVC_OUTBOUND_CALL_TRUST</data><data key="node_entity_type">service</data><data key="node_canonical_name">TransUnion Outbound Call Spoof-Proofing and Call Branding</data><data key="node_acronym">Outbound Call Trust</data><data key="node_domain">Telephony / Customer Service / Fraud Prevention</data><data key="node_description">Procured capability for protecting/authenticating SSA outbound calling and presenting trusted call-branding information.</data><data key="node_observed_status">procured_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Award description establishes procurement, not production deployment. No relationship to Amazon Connect or a specific SSA outbound dialing application is inferred.</data></node><node id="SVC_PARIS"><data key="node_entity_id">SVC_PARIS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Public Assistance Reporting Information System</data><data key="node_acronym">PARIS</data><data key="node_domain">External Shared Services / State Program Integrity</data><data key="node_description">HHS Administration for Children and Families federal-state public-assistance integrity program for interstate and federal data matching; Treasury Do Not Pay serves as its technical service provider.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">External HHS program/data hub with Treasury technical-service support. State access to Numident through PARIS is listed as coming soon on the September 2026 DNP data catalog.</data></node><node id="SVC_PAYGOV"><data key="node_entity_id">SVC_PAYGOV</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Pay.gov</data><data key="node_domain">External Payment Service</data><data key="node_description">Treasury online remittance service used for electronic repayment of eligible SSA Title II and Title XVI program debt.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SVC_PRIVACY_CONSENT"><data key="node_entity_id">SVC_PRIVACY_CONSENT</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Electronic Consent to Disclose Records</data><data key="node_acronym">SSA-3288-OP1</data><data key="node_domain">Privacy / Digital Consent</data><data key="node_description">SSA online webform service allowing an identity-verified adult record holder to electronically consent to disclosure of eligible Privacy Act-protected records to another person or entity.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA POMS recognizes SSA-3288-OP1 as written electronic consent completed and signed electronically on SSA.gov. Current Forms catalog routes the form through the shared Upload Documents/eSubmit completeOnline path.</data></node><node id="SVC_PRIVACY_RECORD_ACCESS"><data key="node_entity_id">SVC_PRIVACY_RECORD_ACCESS</data><data key="node_entity_type">digital_service</data><data key="node_canonical_name">Electronic Request for Access to Your Records</data><data key="node_acronym">SSA-2288-OP1</data><data key="node_domain">Privacy / Digital Records Access</data><data key="node_description">SSA online service allowing an authenticated adult record holder to electronically request access to eligible SSA records, including specified claim, payment, Medicare, medical, application, notice, appeal, and system-of-records content.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current Forms catalog routes SSA-2288-OP1 through the shared Upload Documents/eSubmit completeOnline path. The public source does not disclose the downstream workflow engine or storage implementation.</data></node><node id="SVC_RCC"><data key="node_entity_id">SVC_RCC</data><data key="node_entity_type">service</data><data key="node_canonical_name">Representative Call Center</data><data key="node_acronym">RCC</data><data key="node_domain">Representation / Processing Center Service</data><data key="node_description">SSA dedicated representative telephone service that handles cases pending across processing centers and automatically routes calls based on claimant information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current July 2026 SSA notice and representation pages confirm the RCC remains a single contact point for representative inquiries within its documented scope.</data></node><node id="SVC_RP_MESSAGE_CENTER"><data key="node_entity_id">SVC_RP_MESSAGE_CENTER</data><data key="node_entity_type">service</data><data key="node_canonical_name">Representative Payee Message Center</data><data key="node_domain">Representative Payee / Digital Service</data><data key="node_description">Message-center service for messages, alerts and online notices associated with beneficiaries served by an individual representative payee.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA describes this as a new feature of the Representative Payee Portal; exact launch date not asserted.</data></node><node id="SVC_SAM"><data key="node_entity_id">SVC_SAM</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">System for Award Management</data><data key="node_acronym">SAM</data><data key="node_domain">Procurement / Vendor Registration</data><data key="node_description">Federal contractor/vendor registration service through which enrolled SSA vendors add or update financial information for direct deposit.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA vendor page says SAM financial changes automatically update an SSA database; it does not name that database or describe transport.</data></node><node id="SVC_SAM_GOV"><data key="node_entity_id">SVC_SAM_GOV</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">SAM.gov</data><data key="node_domain">Acquisition &amp; Grants / External Service</data><data key="node_description">Federal System for Award Management service used in SSA grant-application workflow for applicant registration or registration updates.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA OAG current grant instructions require SAM.gov registration, competitive applications through Grants.gov, and continuation applications through GrantSolutions.</data></node><node id="SVC_SAVE"><data key="node_entity_id">SVC_SAVE</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Systematic Alien Verification for Entitlements</data><data key="node_acronym">SAVE</data><data key="node_domain">Identity / Immigration Status</data><data key="node_description">DHS/USCIS inter-governmental online verification service used by SSA to verify immigration status and documents.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-15</data><data key="node_confidence">5</data><data key="node_notes">SAVE supplies verification information; it does not determine benefit eligibility.</data></node><node id="SVC_SELF_LOCK"><data key="node_entity_id">SVC_SELF_LOCK</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">DHS Self Lock</data><data key="node_acronym">Self Lock</data><data key="node_domain">Identity / Employment Verification</data><data key="node_description">DHS myE-Verify feature that locks an SSN against use in E-Verify and Self Check for a defined period and can be extended.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA staff cannot resolve a DHS tentative nonconfirmation caused by Self Lock.</data></node><node id="SVC_SEODR"><data key="node_entity_id">SVC_SEODR</data><data key="node_entity_type">service</data><data key="node_canonical_name">SSA Employee and Office Data Retrieval Core Services</data><data key="node_acronym">SEODR</data><data key="node_domain">Enterprise Services / Human Resources</data><data key="node_description">Core Services function used by SSA management personnel to obtain job-related information about an SSA employee.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">The source identifies SEODR as a Core Services function; interface protocol, hosting boundary, application owner, and client systems are not publicly established.</data></node><node id="SVC_SSA_WEB_STATUS"><data key="node_entity_id">SVC_SSA_WEB_STATUS</data><data key="node_entity_type">public_service</data><data key="node_canonical_name">SSA Web Services Status</data><data key="node_acronym">SSA Status</data><data key="node_domain">Infrastructure / Digital Service Operations</data><data key="node_description">SSA public operational-status service reporting current health and historical incidents for SSA.gov and the my Social Security Webapp.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public operational monitoring surface. It does not expose internal monitoring vendor, telemetry architecture, or incident-management platform.</data></node><node id="SVC_TCIS"><data key="node_entity_id">SVC_TCIS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Treasury Check Information System</data><data key="node_acronym">TCIS</data><data key="node_domain">External Payment Service / Treasury</data><data key="node_description">Treasury system containing check and direct-deposit activity, claims, payment details, check images, and related nonreceipt/stop-payment information used by SSA staff.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="SVC_TCORE"><data key="node_entity_id">SVC_TCORE</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Treasury Check Operations Re-engineering Effort</data><data key="node_acronym">T-CORE</data><data key="node_domain">External / Treasury / Payment Processing</data><data key="node_description">Treasury/Federal Reserve CORE process for deceased-payee check controls. Current SSA policy says the process is now handled by the Kansas City Federal Reserve Bank, matches a Fiscal Service daily death file against checks presented for payment, can deny payment after death, and returns related credits to SSA.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">CORE was implemented in 2000 with the Richmond Federal Reserve Bank; current 2026 POMS explicitly states the process is now handled by the Kansas City Federal Reserve Bank. Transport, format, and Federal Reserve internal implementation remain undisclosed.</data></node><node id="SVC_TOP"><data key="node_entity_id">SVC_TOP</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Treasury Offset Program</data><data key="node_acronym">TOP</data><data key="node_domain">External Debt Collection</data><data key="node_description">Government-wide Fiscal Service matching/offset service used by SSA both as creditor agency and payment agency.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SVC_TRACS"><data key="node_entity_id">SVC_TRACS</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Treasury Receivable Accounting and Collection System</data><data key="node_acronym">TRACS</data><data key="node_domain">External Payment Service / Treasury</data><data key="node_description">Treasury debt recovery and accounting system providing SSA with accounting history for nonreceipt cases, including credits, debits, reclamations, and refunds.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="SVC_TREASURY_IPP"><data key="node_entity_id">SVC_TREASURY_IPP</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Treasury Invoice Processing Platform</data><data key="node_acronym">IPP</data><data key="node_domain">Finance / Vendor Payments</data><data key="node_description">Treasury secure web-based service that manages invoicing from purchase orders through payment notification and provides enrolled SSA vendors payment-history access.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA vendor page establishes current use; public page does not disclose SSA-side interface mechanics.</data></node><node id="SVC_TREASURY_LOCKBOX"><data key="node_entity_id">SVC_TREASURY_LOCKBOX</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Treasury Programmatic Remittance Lockbox</data><data key="node_domain">Debt &amp; Remittances</data><data key="node_description">Treasury/Fiscal Service lockbox banking service used for mailed SSA programmatic remittances.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">2021 implementation remains documented in POMS; July 2026 SSA guidance now emphasizes electronic repayment and no longer asks individuals to mail checks.</data></node><node id="SVC_TREASURY_PAYMENT_VERIFICATION"><data key="node_entity_id">SVC_TREASURY_PAYMENT_VERIFICATION</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Treasury Payment Verification</data><data key="node_domain">External Shared Services / Payments / Program Integrity</data><data key="node_description">Treasury service that automatically screens federal disbursements against authoritative data to help confirm identity and eligibility and flag potentially ineligible payments.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Available to federal agencies using Treasury for payment disbursement. The DNP data catalog lists SSA Numident availability for select programs.</data></node><node id="SVC_TWN"><data key="node_entity_id">SVC_TWN</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">The Work Number</data><data key="node_acronym">TWN</data><data key="node_domain">External Wage Verification</data><data key="node_description">Commercial employment and income verification service approved by SSA as a primary-evidence source when policy conditions and authorization are met.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">SSA policy distinguishes direct/manual use of TWN from automated PIE even though current PDP data may be the same underlying wage information.</data></node><node id="SVC_UNISON_MARKETPLACE"><data key="node_entity_id">SVC_UNISON_MARKETPLACE</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">Unison Marketplace</data><data key="node_acronym">Unison Marketplace</data><data key="node_domain">Procurement / External Service</data><data key="node_description">Online reverse-auction service SSA says it uses to post requirements and select winning bids.</data><data key="node_observed_status">observed_current_oag_guidance</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current OAG/OSDBU FAQ.</data></node><node id="SVC_USAFX"><data key="node_entity_id">SVC_USAFX</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">United States Attorney File Exchange</data><data key="node_acronym">USAfx</data><data key="node_domain">Appeals / Federal Court Exchange</data><data key="node_description">File-exchange service used by SSA court legal assistants to upload a completed Certified Administrative Record and, when appropriate, its segments for the United States Attorney's Office.</data><data key="node_observed_status">observed_current_hallex</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">HALLEX names USAfx but does not disclose ownership, transport protocol, hosting, or retention.</data></node><node id="SVC_VERIFYADV"><data key="node_entity_id">SVC_VERIFYADV</data><data key="node_entity_type">external_service</data><data key="node_canonical_name">VerifyAdvantage</data><data key="node_acronym">VerifyAdvantage</data><data key="node_domain">External Wage Verification</data><data key="node_description">Commercial web-based employment and income verification service approved by SSA as a primary-evidence source when policy conditions and authorization are met.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data></node><node id="SVC_WAGE_FILE_UPLOAD"><data key="node_entity_id">SVC_WAGE_FILE_UPLOAD</data><data key="node_entity_type">service</data><data key="node_canonical_name">Wage File Upload</data><data key="node_domain">Earnings / Employer</data><data key="node_description">BSO electronic wage-file submission service for formatted wage reports.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="SW_KIOWARE"><data key="node_entity_id">SW_KIOWARE</data><data key="node_entity_type">technology</data><data key="node_canonical_name">KioWare</data><data key="node_domain">Field Office / Kiosk Technology</data><data key="node_description">Commercial kiosk-shell software identified in federal procurement records as supporting SSA Visitor Intake Process Rewrite kiosks at field offices.</data><data key="node_observed_status">observed_current_procurement</data><data key="node_observed_as_of">2026-09-09</data><data key="node_confidence">4</data><data key="node_notes">Deployment evidence comes from federal-award mirrors derived from SAM.gov and USAspending/FPDS; treated as secondary corroboration and confidence reduced.</data></node><node id="SYS_ECMS"><data key="node_entity_id">SYS_ECMS</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Enterprise Configuration Management System</data><data key="node_domain">Enterprise IT / Configuration Management</data><data key="node_description">SSA authoritative repository for identifying, recording, tracking, and reporting characteristics, authorized configurations, and relationships of key IT components and assets.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA Open Data marks the dataset non-public with weekly accrual. Database engine, vendor, hosting location, and interfaces are not identified.</data></node><node id="SYS_HOTS_RECORDS"><data key="node_entity_id">SYS_HOTS_RECORDS</data><data key="node_entity_type">system_of_records</data><data key="node_canonical_name">Hearing Office Tracking System of Claimant Cases Records</data><data key="node_acronym">HOTS Records</data><data key="node_domain">Hearings / Work Control</data><data key="node_description">Legacy Privacy Act record-system boundary that tracked hearing-office workload; its records were ordered combined into 60-0009 in April 2026.</data><data key="node_observed_status">sorn_rescinded_records_combined_into_60_0009</data><data key="node_observed_as_of">2026-04-20</data><data key="node_confidence">5</data><data key="node_notes">Represents the legal/records boundary, not a claim that a still-running physical HOTS application existed in 2026.</data></node><node id="SYS_ICDB"><data key="node_entity_id">SYS_ICDB</data><data key="node_entity_type">shared_data_service</data><data key="node_canonical_name">Integrated Client Database</data><data key="node_acronym">ICDB</data><data key="node_domain">Shared Client Data</data><data key="node_description">Shared client-data databases/screens/access software supporting major SSA application systems.</data><data key="node_observed_status">current_open_data_inventory_and_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current June 2026 POMS calls ICDB “CLIENT” and states iAppt unverified data remains isolated from it until verified; current EDCS POMS also names ICDB as a propagation source. Relationship to Person Information remains separate unless explicitly documented.</data></node><node id="SYS_IWMS"><data key="node_entity_id">SYS_IWMS</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">Integrated Work Measurement System</data><data key="node_domain">Enterprise / Work Measurement</data><data key="node_description">SSA work-measurement system used as the source for agency OASI, Disability Insurance, and Supplemental Security Income claims workload statistics.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">The 2025 Annual Statistical Supplement cites the system as the source for FY2024 workload tables. Current platform components and interfaces are not identified by that source.</data></node><node id="SYS_MA_BEACON"><data key="node_entity_id">SYS_MA_BEACON</data><data key="node_entity_type">external_system</data><data key="node_canonical_name">Massachusetts BEACON Eligibility System</data><data key="node_acronym">BEACON</data><data key="node_domain">External Data / State Eligibility</data><data key="node_description">Massachusetts DTA eligibility system whose records are accessed by approved SSA employees through DTA Connect under SASRO.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">No database engine, hosting, or interface protocol inferred.</data></node><node id="SYS_MBR"><data key="node_entity_id">SYS_MBR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Master Beneficiary Record</data><data key="node_acronym">MBR</data><data key="node_domain">Title II / Entitlement</data><data key="node_description">Title II beneficiary/entitlement record used across claims, disability and payment workflows.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes"> Current COA notice policy states the MBR does not store both beneficiary and representative-payee addresses; its old mailing address may belong to either.</data></node><node id="SYS_MDS_1994"><data key="node_entity_id">SYS_MDS_1994</data><data key="node_entity_type">application</data><data key="node_canonical_name">Modernized Disability System</data><data key="node_acronym">MDS</data><data key="node_domain">Disability / Historical Modernization</data><data key="node_description">Disability automation system being developed specifically for IWS/LAN to replace paper applicant files with electronic records, retain medical evidence electronically where possible, and transmit cases electronically to state DDS offices.</data><data key="node_observed_status">historical_development_1994</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">OTA reported more than 100 SSA developers working on MDS and stated no mainframe version was planned. Later disability-system lineage is not inferred without additional evidence.</data></node><node id="SYS_MEF"><data key="node_entity_id">SYS_MEF</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Master Earnings File</data><data key="node_acronym">MEF</data><data key="node_domain">Earnings</data><data key="node_description">SSA master earnings data file used in SSI earnings matching and other workloads.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Added here because current SSA inventory explicitly names MEF in the MEF/SSR match.</data></node><node id="SYS_NUMIDENT"><data key="node_entity_id">SYS_NUMIDENT</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Numident</data><data key="node_acronym">NUMIDENT</data><data key="node_domain">Identity &amp; Enumeration</data><data key="node_description">Numerical Identification System (Numident), SSA system containing information from Social Security card applications and serving as the agency identity/SSN record referenced by current workflows.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Treat as an authoritative identity record; deeper field-level modeling comes later. Current 60-0058 describes the SSN-holder/application record environment as identity/enumeration data, not a universal current-address master. It also states records may exist in additional locations in connection with cloud-based services and business-continuity backup; this does not establish that the Numident production database itself is cloud-hosted. Run 84: SSA reported on 2026-08-14 that it was reconciling the SSN database to remove deceased people, update citizenship data, and verify status; more than 10 percent of active SSNs had been updated. The public release does not expose implementation mechanics. Run 85 correction: Treasury formally designated Numident to the Do Not Pay Working System effective April 10, 2026 for limited name/SSN/DOB verification in eligible health and income-maintenance programs; this does not create a new authoritative person repository.</data></node><node id="SYS_OIS"><data key="node_entity_id">SYS_OIS</data><data key="node_entity_type">system</data><data key="node_canonical_name">Occupational Information System</data><data key="node_acronym">OIS</data><data key="node_domain">Disability / Vocational Evidence</data><data key="node_description">SSA occupational-information system under development to replace the Dictionary of Occupational Titles as the primary occupational information source used in disability adjudication.</data><data key="node_observed_status">in_development</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">SSA states OIS will aggregate occupational data from multiple sources and use ORS as its primary work-requirements source.</data></node><node id="SYS_RPMRCS"><data key="node_entity_id">SYS_RPMRCS</data><data key="node_entity_type">application</data><data key="node_canonical_name">Representative Payee-Misuse Restitution Control System</data><data key="node_acronym">RP-MRCS</data><data key="node_domain">Representative Payee / Misuse</data><data key="node_description">System of records identified in SSA privacy governance for representative-payee misuse restitution control.</data><data key="node_observed_status">current_sorn_catalog</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Current SORN catalog supports maintained record-system status; no current POMS architecture for the application was located in this run.</data></node><node id="SYS_SSI_EARN_ALERT"><data key="node_entity_id">SYS_SSI_EARN_ALERT</data><data key="node_entity_type">processing_system</data><data key="node_canonical_name">SSI Earnings Alert System</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">SSA process/system used to identify discrepancies between SSI recipients’ reported wages and wage information available to SSA and generate earnings alerts for resolution.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-23</data><data key="node_confidence">5</data><data key="node_notes">OIG uses the generic phrase “earnings alert system”; public evidence does not establish a single formal product boundary. POMS documents the S2/OCSE alert mechanics.</data></node><node id="SYS_SSR"><data key="node_entity_id">SYS_SSR</data><data key="node_entity_type">data_store</data><data key="node_canonical_name">Supplemental Security Record</data><data key="node_acronym">SSR</data><data key="node_domain">Title XVI / SSI</data><data key="node_description">SSI record used across claims, disability and eligibility workflows.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_ABINITIO"><data key="node_entity_id">TECH_ABINITIO</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Ab Initio</data><data key="node_domain">Technology</data><data key="node_description">Data-integration software documented for migrating staged NVF data into operational tables.</data><data key="node_observed_status">documented_architecture</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Technology relationship comes from 2018 eDIB PIA.</data></node><node id="TECH_ACH"><data key="node_entity_id">TECH_ACH</data><data key="node_entity_type">network_technology</data><data key="node_canonical_name">Automated Clearing House</data><data key="node_acronym">ACH</data><data key="node_domain">Payments / Financial Network</data><data key="node_description">Federal Reserve-maintained computer network used by financial institutions to transmit and receive electronic credits, debits, SSA direct-deposit NOCs, and DNE traffic.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA POMS describes ACH as the electronic network used for NOC transmission; DNE policy describes RFRB passing DNE information through ACH to U.S. financial institutions.</data></node><node id="TECH_ADOBE_SIGN"><data key="node_entity_id">TECH_ADOBE_SIGN</data><data key="node_entity_type">technology_service</data><data key="node_canonical_name">Adobe Sign</data><data key="node_domain">Digital Forms / Electronic Signatures</data><data key="node_description">Commercial electronic-signature service identified by SSA in current e1693 instructions and current POMS as the technology used by the e1696/e1693 agency portals.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">No SSA contract, tenancy boundary, or broader enterprise use is inferred from portal-level evidence.</data></node><node id="TECH_ADVANCED_ANALYTICS"><data key="node_entity_id">TECH_ADVANCED_ANALYTICS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Advanced Data Analytics</data><data key="node_domain">Technology</data><data key="node_description">Advanced analytics capability used by AFES to identify fraud patterns, generate leads, and conduct fraud-risk analysis.</data><data key="node_observed_status">documented_current_system_capability</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">Capability is documented in the current-catalog AFES PIA; no specific commercial product is inferred.</data></node><node id="TECH_AGENTIC_AI"><data key="node_entity_id">TECH_AGENTIC_AI</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Agentic Artificial Intelligence</data><data key="node_acronym">Agentic AI</data><data key="node_domain">Artificial Intelligence</data><data key="node_description">AI category used by SSA for the Coding Assistance use case in the 2025 inventory.</data><data key="node_observed_status">pre_deployment_use</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data></node><node id="TECH_APACHE_AXIS_14"><data key="node_entity_id">TECH_APACHE_AXIS_14</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Apache Axis 1.4</data><data key="node_acronym">Axis 1.4</data><data key="node_domain">Integration Technology</data><data key="node_description">Apache Axis 1.4 library stack documented in SSA’s EREWS Java client reference implementation.</data><data key="node_observed_status">historically_documented_erews_2007</data><data key="node_observed_as_of">2007-07-02</data><data key="node_confidence">5</data><data key="node_notes">Reference-client technology, not necessarily the server runtime or a current dependency.</data></node><node id="TECH_APACHE_HADOOP"><data key="node_entity_id">TECH_APACHE_HADOOP</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Apache Hadoop</data><data key="node_acronym">Hadoop</data><data key="node_domain">Enterprise Data / Big Data</data><data key="node_description">Open-source distributed data-processing framework SSA evaluated and adopted as a feasible component for Big Data, audit-trail, fraud, and data-lake uses.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Run 54 records authoritative historical use/planning; no claim is made about current 2026 Hadoop deployment.</data></node><node id="TECH_APACHE_SOLR"><data key="node_entity_id">TECH_APACHE_SOLR</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Apache Solr</data><data key="node_acronym">Solr</data><data key="node_domain">Search / Knowledge Management</data><data key="node_description">Open-source search engine identified by SSA as the engine behind 21st Century PolicyNet intelligent search.</data><data key="node_observed_status">deployed</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data></node><node id="TECH_API"><data key="node_entity_id">TECH_API</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Application Programming Interfaces</data><data key="node_acronym">APIs</data><data key="node_domain">Technology</data><data key="node_description">API-based integration approach cited by SSA in modernization plans for simplifying data integration and connecting modernized applications.</data><data key="node_observed_status">documented_modernization_approach</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">No API gateway, protocol or product is inferred.</data></node><node id="TECH_APRYSE_PDFNET"><data key="node_entity_id">TECH_APRYSE_PDFNET</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Apryse PDFTron PDFNet SDK</data><data key="node_acronym">PDFNet SDK</data><data key="node_domain">Technology / Document Processing</data><data key="node_description">Commercial software development kit identified by SSA for annual renewal to support the Document Conversion Engine.</data><data key="node_observed_status">observed_current_procurement</data><data key="node_observed_as_of">2026-04-29</data><data key="node_confidence">5</data></node><node id="TECH_AWS_CLOUDWATCH"><data key="node_entity_id">TECH_AWS_CLOUDWATCH</data><data key="node_entity_type">cloud_service</data><data key="node_canonical_name">AWS CloudWatch</data><data key="node_acronym">CloudWatch</data><data key="node_domain">Infrastructure / Cloud</data><data key="node_description">AWS monitoring service that SSA uses to monitor cloud resources, according to the September 2026 OIG audit.</data><data key="node_observed_status">observed_in_use</data><data key="node_observed_as_of">2026-09-30</data><data key="node_confidence">5</data><data key="node_notes">The public audit does not enumerate which SSA resources or accounts are monitored.</data></node><node id="TECH_CASEWARE_IDEA_NLS"><data key="node_entity_id">TECH_CASEWARE_IDEA_NLS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Caseware IDEA NLS</data><data key="node_acronym">IDEA NLS</data><data key="node_domain">Analytics / Audit Software</data><data key="node_description">Commercial Caseware IDEA NLS software for which SSA solicited a concurrent-license subscription renewal in 2024.</data><data key="node_observed_status">documented_procurement_2024</data><data key="node_observed_as_of">2024-01-25</data><data key="node_confidence">5</data><data key="node_notes">Procurement evidence proves SSA sought renewal of the software subscription; Run 30 does not infer continued use in 2026.</data></node><node id="TECH_CICS"><data key="node_entity_id">TECH_CICS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">CICS</data><data key="node_acronym">CICS</data><data key="node_domain">Technology</data><data key="node_description">Customer Information Control System (CICS), a transaction-processing technology/interface documented in SSA systems history and legacy service metadata.</data><data key="node_observed_status">cataloged_legacy_metadata</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Source metadata is from 2018.</data></node><node id="TECH_COBOL"><data key="node_entity_id">TECH_COBOL</data><data key="node_entity_type">technology</data><data key="node_canonical_name">COBOL</data><data key="node_acronym">COBOL</data><data key="node_domain">Infrastructure / Legacy Mainframe</data><data key="node_description">Common Business-Oriented Language documented by OTA as a major language in SSA's early-1990s IBM mainframe environment.</data><data key="node_observed_status">historically_documented_1994</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">Historical evidence only; current usage is not inferred by this source.</data></node><node id="TECH_COMPUTER_VISION"><data key="node_entity_id">TECH_COMPUTER_VISION</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Computer Vision</data><data key="node_domain">Artificial Intelligence</data><data key="node_description">AI methods that analyze images or scanned documents, including pay-stub and identity-verification imagery.</data><data key="node_observed_status">observed_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data></node><node id="TECH_DB2"><data key="node_entity_id">TECH_DB2</data><data key="node_entity_type">technology</data><data key="node_canonical_name">IBM DB2</data><data key="node_acronym">DB2</data><data key="node_domain">Technology</data><data key="node_description">Database technology explicitly documented for the SSNAP management-information ODS.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_DRN"><data key="node_entity_id">TECH_DRN</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Data Replication Network</data><data key="node_acronym">DRN</data><data key="node_domain">Infrastructure / Mainframe / Disaster Recovery</data><data key="node_description">SSA network capability used by geographically dispersed data centers for resilient, real-time replication of mainframe data and disaster recovery.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current SSA delivery-order description establishes the function but not the network product stack, topology, bandwidth, or named data-center endpoints.</data></node><node id="TECH_DW_MGMT_PRODUCT_2026"><data key="node_entity_id">TECH_DW_MGMT_PRODUCT_2026</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Tanzu Greenplum</data><data key="node_acronym">Greenplum</data><data key="node_domain">Enterprise Data / Analytics</data><data key="node_description">Tanzu Greenplum data-warehouse management software licenses procured under SSA Cloud BPA Call Order 28321326FA0010026 for data processing and analytics.</data><data key="node_observed_status">procured_2026; product_identity_identified</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Exact call-order description identifies Tanzu Greenplum licenses. Version, deployment architecture, datasets, and production use remain unverified.</data></node><node id="TECH_EMC_GREENPLUM_2016"><data key="node_entity_id">TECH_EMC_GREENPLUM_2016</data><data key="node_entity_type">technology</data><data key="node_canonical_name">EMC Greenplum (2016 EDW)</data><data key="node_acronym">EMC Greenplum</data><data key="node_domain">Enterprise Data / Analytics</data><data key="node_description">Greenplum database technology documented as the database platform for SSA's new 2016 Enterprise Data Warehouse.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Kept separate from the 2026 Tanzu Greenplum procurement entity; continuity between the 2016 and 2026 deployments is not established.</data></node><node id="TECH_FIRSTNET"><data key="node_entity_id">TECH_FIRSTNET</data><data key="node_entity_type">technology_service</data><data key="node_canonical_name">FirstNet Priority Communications System</data><data key="node_acronym">FirstNet</data><data key="node_domain">Infrastructure / Emergency Communications</data><data key="node_description">Priority communications service identified by SSA Security and Resilience as the target for centralized emergency communications.</data><data key="node_observed_status">planned_or_selected_target</data><data key="node_observed_as_of">2026-09-21</data><data key="node_confidence">5</data><data key="node_notes">Solicitation describes reliance on AT&amp;T signal and satellite backup requirement.</data></node><node id="TECH_FTMS"><data key="node_entity_id">TECH_FTMS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">File Transfer Management System</data><data key="node_acronym">FTMS</data><data key="node_domain">External Data Exchange / Transfer</data><data key="node_description">SSA file-transfer mechanism documented for receiving and transmitting SVES batch files.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Current SSA support page links the July 2023 SVES/SOLQ manual; no platform/vendor details inferred.</data></node><node id="TECH_GENERATIVE_AI"><data key="node_entity_id">TECH_GENERATIVE_AI</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Generative Artificial Intelligence</data><data key="node_acronym">Generative AI</data><data key="node_domain">Technology</data><data key="node_description">Generative AI capability explicitly identified by SSA as improving automated transcript accuracy in HeaRT.</data><data key="node_observed_status">documented_use</data><data key="node_observed_as_of">2025-03-13</data><data key="node_confidence">5</data><data key="node_notes">No model, vendor, or hosting provider inferred.</data></node><node id="TECH_HTTPS_SSL"><data key="node_entity_id">TECH_HTTPS_SSL</data><data key="node_entity_type">technology</data><data key="node_canonical_name">HTTPS over SSL</data><data key="node_acronym">HTTPS/SSL</data><data key="node_domain">Integration Security</data><data key="node_description">Encrypted HTTP transport documented for EREWS to protect medical information in transit.</data><data key="node_observed_status">historically_documented_erews_2007</data><data key="node_observed_as_of">2007-07-02</data><data key="node_confidence">5</data><data key="node_notes">Historical terminology from the 2007 guide; not a claim about current TLS configuration.</data></node><node id="TECH_IBM_MAINFRAME_1994"><data key="node_entity_id">TECH_IBM_MAINFRAME_1994</data><data key="node_entity_type">technology</data><data key="node_canonical_name">SSA IBM Mainframe Environment (1994)</data><data key="node_acronym">IBM Mainframe</data><data key="node_domain">Infrastructure / Legacy Mainframe</data><data key="node_description">IBM mainframe-centered processing environment at the National Computer Center that processed transactions from field and teleservice terminals and accessed SSA program databases.</data><data key="node_observed_status">historically_documented_1994</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">Time-scoped architecture entity for the early-1990s environment; it is not a claim about a specific current mainframe model.</data></node><node id="TECH_IBM_POWER10"><data key="node_entity_id">TECH_IBM_POWER10</data><data key="node_entity_type">hardware</data><data key="node_canonical_name">IBM Power10</data><data key="node_acronym">Power10</data><data key="node_domain">Infrastructure / Compute</data><data key="node_description">IBM Power10 hardware procured for the Second Support Center as an upgrade to existing IBM Power8.</data><data key="node_observed_status">procured_for_ssc</data><data key="node_observed_as_of">2024-04-11</data><data key="node_confidence">5</data><data key="node_notes">Award evidence proves procurement intent; installation date and current configuration are not publicly established.</data></node><node id="TECH_IBM_POWER8"><data key="node_entity_id">TECH_IBM_POWER8</data><data key="node_entity_type">hardware</data><data key="node_canonical_name">IBM Power8</data><data key="node_acronym">Power8</data><data key="node_domain">Infrastructure / Compute</data><data key="node_description">IBM Power8 hardware referenced as existing at the Second Support Center when SSA procured a Power10 upgrade in 2024.</data><data key="node_observed_status">historical_existing_reference</data><data key="node_observed_as_of">2024-04-11</data><data key="node_confidence">5</data><data key="node_notes">Current status after the Power10 upgrade is not established by the award record.</data></node><node id="TECH_IBM_SNA"><data key="node_entity_id">TECH_IBM_SNA</data><data key="node_entity_type">technology</data><data key="node_canonical_name">IBM Systems Network Architecture</data><data key="node_acronym">SNA</data><data key="node_domain">Infrastructure / Network</data><data key="node_description">IBM Systems Network Architecture protocol family documented as the network protocol used by SSA's mainframe-centered environment in 1994.</data><data key="node_observed_status">historically_documented_1994</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">Historical network protocol evidence.</data></node><node id="TECH_IBM_SUPER_SERVER"><data key="node_entity_id">TECH_IBM_SUPER_SERVER</data><data key="node_entity_type">hardware</data><data key="node_canonical_name">IBM Super Server Appliances</data><data key="node_domain">Infrastructure / Compute</data><data key="node_description">IBM server appliances identified in a 2026 SSA delivery order as supporting both the Second Support Center and National Support Center.</data><data key="node_observed_status">observed_in_use_reference</data><data key="node_observed_as_of">2026-02-09</data><data key="node_confidence">5</data><data key="node_notes">Award description says the appliances support SSC and NSC. The public source does not establish model numbers, operating system, network role beyond the available description, or exact installation topology.</data></node><node id="TECH_IDMS"><data key="node_entity_id">TECH_IDMS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">IDMS</data><data key="node_domain">Technology</data><data key="node_description">Legacy database technology named by SSA as the source platform from which Office of Hearings and Appeals data were converted to DB2.</data><data key="node_observed_status">legacy_documented</data><data key="node_observed_as_of">2026-06-29</data><data key="node_confidence">5</data><data key="node_notes">Vendor/product edition is not inferred beyond the IDMS name in SSA metadata.</data></node><node id="TECH_IDMS_DBMS"><data key="node_entity_id">TECH_IDMS_DBMS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Integrated Database Management System (database technology)</data><data key="node_acronym">IDMS</data><data key="node_domain">Infrastructure / Database</data><data key="node_description">Legacy database-management technology identified by SSA as the costly database structure used for the MCS Pending File.</data><data key="node_observed_status">historical_legacy_technology</data><data key="node_observed_as_of">2019</data><data key="node_confidence">5</data><data key="node_notes">This IDMS means Integrated Database Management System and is not the separately cataloged Integrated Disability Management System application, despite the acronym collision.</data></node><node id="TECH_INFORMATICA_ETL_2016"><data key="node_entity_id">TECH_INFORMATICA_ETL_2016</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Informatica ETL Tool (2016)</data><data key="node_acronym">Informatica ETL</data><data key="node_domain">Enterprise Data / Integration</data><data key="node_description">Informatica extract-transform-load tooling documented for moving data from the Hadoop data lake into the new EDW.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Product edition/version is not specified.</data></node><node id="TECH_IPV6"><data key="node_entity_id">TECH_IPV6</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Internet Protocol Version 6</data><data key="node_acronym">IPv6</data><data key="node_domain">Infrastructure / Network</data><data key="node_description">Network protocol SSA states it is transitioning communications toward as part of infrastructure modernization.</data><data key="node_observed_status">transition_in_progress_fy2026</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_JAVA"><data key="node_entity_id">TECH_JAVA</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Java</data><data key="node_acronym">Java</data><data key="node_domain">Infrastructure / Application Platform</data><data key="node_description">Programming language identified by SSA as the target language for modernized Title II computational services.</data><data key="node_observed_status">historical_modernization_target_technology</data><data key="node_observed_as_of">2019</data><data key="node_confidence">5</data><data key="node_notes">Evidence establishes the modernization target language but not a particular runtime, framework, JDK version, hosting platform, or current deployment.</data></node><node id="TECH_JWE"><data key="node_entity_id">TECH_JWE</data><data key="node_entity_type">technology</data><data key="node_canonical_name">JSON Web Encryption</data><data key="node_acronym">JWE</data><data key="node_domain">Technology</data><data key="node_description">Encryption format documented in eCBSV technical requirements.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_JWT"><data key="node_entity_id">TECH_JWT</data><data key="node_entity_type">technology</data><data key="node_canonical_name">JSON Web Token</data><data key="node_acronym">JWT</data><data key="node_domain">Technology</data><data key="node_description">Token technology documented in eCBSV technical requirements.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_LINUX"><data key="node_entity_id">TECH_LINUX</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Linux</data><data key="node_acronym">Linux</data><data key="node_domain">Infrastructure / Operating System</data><data key="node_description">Operating-system family to which SSA migrated SSOARS hardware environments during FY2025.</data><data key="node_observed_status">observed_ssoars_current_fy2025</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes">FY2025 AFR says SSOARS moved from Solaris to Linux.</data></node><node id="TECH_LMR"><data key="node_entity_id">TECH_LMR</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Handheld Land Mobile Radio Systems</data><data key="node_acronym">LMR</data><data key="node_domain">Infrastructure / Emergency Communications</data><data key="node_description">Legacy handheld radio systems at SSA HQ Campus and National Support Center identified for replacement due to end-of-life/end-of-support conditions.</data><data key="node_observed_status">legacy_replacement_target</data><data key="node_observed_as_of">2026-09-21</data><data key="node_confidence">5</data><data key="node_notes">Status is based on SSA procurement description, not an inventory of every radio asset.</data></node><node id="TECH_MACHINE_LEARNING"><data key="node_entity_id">TECH_MACHINE_LEARNING</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Machine Learning</data><data key="node_acronym">ML</data><data key="node_domain">Technology</data><data key="node_description">Machine-learning capability explicitly identified by GAO as part of ADDS-IMAGEN.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-06-26</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_MAINFRAME"><data key="node_entity_id">TECH_MAINFRAME</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Mainframe</data><data key="node_domain">Technology</data><data key="node_description">Mainframe execution environment explicitly documented for NOVU, SVS and SVS Lite.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-22</data><data key="node_confidence">5</data><data key="node_notes">Generic technology node; not a claim about a specific mainframe model.</data></node><node id="TECH_MFT"><data key="node_entity_id">TECH_MFT</data><data key="node_entity_type">integration_technology</data><data key="node_canonical_name">Managed File Transfer</data><data key="node_acronym">MFT</data><data key="node_domain">External Data Exchange / File Transfer</data><data key="node_description">Licensed file-transfer software used by SSA and state State Transmission Components for secure batch data exchange, including Enumeration at Birth and DFSTATE traffic.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">SSA says MFT was previously called CyberFusion and is developed/supported by TIBCO. Public sources do not disclose the SSA-side product version or hosting architecture.</data></node><node id="TECH_MICROSERVICES"><data key="node_entity_id">TECH_MICROSERVICES</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Microservices Architecture</data><data key="node_acronym">Microservices</data><data key="node_domain">Technology</data><data key="node_description">Modernization architecture approach cited by SSA for centralized data products and replacement of outdated systems.</data><data key="node_observed_status">documented_modernization_approach</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">4</data><data key="node_notes">No specific runtime, framework or vendor is inferred.</data></node><node id="TECH_MONGODB"><data key="node_entity_id">TECH_MONGODB</data><data key="node_entity_type">technology</data><data key="node_canonical_name">MongoDB</data><data key="node_acronym">MongoDB</data><data key="node_domain">Infrastructure / Cloud / Data Platform</data><data key="node_description">Database technology procured by SSA under a 2026 call order on its Commercial Cloud Services BPA.</data><data key="node_observed_status">procured_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Federal-award data mirrors reproduce the government description as a call order for MongoDB. Deployment scope, version, hosting, datasets, and consuming applications are not established.</data></node><node id="TECH_NLP"><data key="node_entity_id">TECH_NLP</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Natural Language Processing</data><data key="node_acronym">NLP</data><data key="node_domain">Artificial Intelligence</data><data key="node_description">AI methods for processing, classifying, translating, searching, or generating human language.</data><data key="node_observed_status">observed_in_2025_ai_inventory</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a technology category from SSA AI inventory classifications and descriptions.</data></node><node id="TECH_OAUTH2"><data key="node_entity_id">TECH_OAUTH2</data><data key="node_entity_type">technology</data><data key="node_canonical_name">OAuth 2.0</data><data key="node_acronym">OAuth 2.0</data><data key="node_domain">Technology</data><data key="node_description">Authorization technology used for eCBSV API access.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_OIDC"><data key="node_entity_id">TECH_OIDC</data><data key="node_entity_type">technology</data><data key="node_canonical_name">OpenID Connect</data><data key="node_acronym">OIDC</data><data key="node_domain">Technology</data><data key="node_description">Authentication/federation technology required for direct eCBSV enrollment/access.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_ORACLE_DATABASE"><data key="node_entity_id">TECH_ORACLE_DATABASE</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Oracle Database Software</data><data key="node_acronym">Oracle Database</data><data key="node_domain">Infrastructure / Database</data><data key="node_description">Oracle database software category covered by SSA software-maintenance delivery order 28321326FDX030114.</data><data key="node_observed_status">procured_maintenance_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Award description establishes maintenance procurement, not a specific Oracle version, deployment, or application dependency.</data></node><node id="TECH_ORACLE_FED_FIN"><data key="node_entity_id">TECH_ORACLE_FED_FIN</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Oracle Federal Financials</data><data key="node_acronym">Oracle Federal Financials</data><data key="node_domain">Finance / COTS</data><data key="node_description">Commercial off-the-shelf financial-management software on which SSA states SSOARS is based.</data><data key="node_observed_status">observed_current_fy2025</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes">Confirmed by FY2025 Agency Financial Report and 2020 SSOARS PIA.</data></node><node id="TECH_ORACLE_MIDDLEWARE"><data key="node_entity_id">TECH_ORACLE_MIDDLEWARE</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Oracle Middleware Software</data><data key="node_acronym">Oracle Middleware</data><data key="node_domain">Infrastructure / Middleware</data><data key="node_description">Oracle middleware software category covered by SSA software-maintenance delivery order 28321326FDX030114.</data><data key="node_observed_status">procured_maintenance_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Award description establishes maintenance procurement, not a specific Oracle middleware product, version, deployment, or application dependency.</data></node><node id="TECH_PCOM"><data key="node_entity_id">TECH_PCOM</data><data key="node_entity_type">technology</data><data key="node_canonical_name">IBM Personal Communications</data><data key="node_acronym">PCOM</data><data key="node_domain">Technology / Terminal Access</data><data key="node_description">IBM terminal-emulation/client technology identified by SSA policy as an access path for DEQY through the Master File Query Menu.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Policy identifies the product by name but does not state the installed version.</data></node><node id="TECH_PEGA_PLATFORM"><data key="node_entity_id">TECH_PEGA_PLATFORM</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Pega Platform</data><data key="node_acronym">Pega</data><data key="node_domain">Technology</data><data key="node_description">Commercial Pega software/SaaS platform procured by SSA under 2026 re-compete award 28321326FDX030072.</data><data key="node_observed_status">observed_current_procurement</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">No application-to-Pega mapping is inferred from the award record.</data></node><node id="TECH_PLSQL"><data key="node_entity_id">TECH_PLSQL</data><data key="node_entity_type">technology</data><data key="node_canonical_name">PL/SQL</data><data key="node_acronym">PL/SQL</data><data key="node_domain">Enterprise Data / Integration</data><data key="node_description">Oracle Procedural Language/Structured Query Language used in custom-coded data-loading processes for the historical SSA BI data warehouse.</data><data key="node_observed_status">historically_documented_2016</data><data key="node_observed_as_of">2016</data><data key="node_confidence">5</data><data key="node_notes">Current usage is not inferred from the 2016 source.</data></node><node id="TECH_PREDICTIVE_ANALYTICS"><data key="node_entity_id">TECH_PREDICTIVE_ANALYTICS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Predictive Analytics</data><data key="node_domain">Technology</data><data key="node_description">Predictive-analytics capability explicitly identified by GAO as part of ADDS-IMAGEN.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-06-26</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_REST_JSON"><data key="node_entity_id">TECH_REST_JSON</data><data key="node_entity_type">technology</data><data key="node_canonical_name">REST API / JSON</data><data key="node_acronym">REST/JSON</data><data key="node_domain">Technology</data><data key="node_description">Request/response interface style documented for eCBSV.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_SALESFORCE"><data key="node_entity_id">TECH_SALESFORCE</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Salesforce Platform</data><data key="node_acronym">Salesforce</data><data key="node_domain">Technology</data><data key="node_description">Commercial SaaS/platform technology identified in the active OPTS BPA's major-program description.</data><data key="node_observed_status">observed_current_procurement</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">No broader SSA Salesforce footprint is inferred.</data></node><node id="TECH_SERS_CHECK_SCANNER"><data key="node_entity_id">TECH_SERS_CHECK_SCANNER</data><data key="node_entity_type">hardware</data><data key="node_canonical_name">SERS Field Office Check Scanner</data><data key="node_domain">Finance / Payments</data><data key="node_description">Physical check/money-order scanner used in SERS intake; product maker, model, integration transport, and deployment inventory unknown.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="TECH_SOAP"><data key="node_entity_id">TECH_SOAP</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Simple Object Access Protocol</data><data key="node_acronym">SOAP</data><data key="node_domain">Integration Technology</data><data key="node_description">XML-based web-service messaging protocol documented for the historical EREWS interface.</data><data key="node_observed_status">historically_documented_erews_2007</data><data key="node_observed_as_of">2007-07-02</data><data key="node_confidence">5</data><data key="node_notes">Scoped to the EREWS developer guide; no claim of enterprise-wide or current use.</data></node><node id="TECH_SOLARIS"><data key="node_entity_id">TECH_SOLARIS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Solaris</data><data key="node_acronym">Solaris</data><data key="node_domain">Infrastructure / Operating System</data><data key="node_description">Prior SSOARS operating-system family replaced by Linux during the FY2025 hardware migration.</data><data key="node_observed_status">retired_for_ssoars_fy2025</data><data key="node_observed_as_of">2025-09-30</data><data key="node_confidence">5</data><data key="node_notes">Status is scoped to SSOARS; do not infer agencywide Solaris retirement.</data></node><node id="TECH_SONATYPE_NEXUS"><data key="node_entity_id">TECH_SONATYPE_NEXUS</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Sonatype Nexus Repository</data><data key="node_acronym">Nexus Repository</data><data key="node_domain">Application Development / Artifact Repository</data><data key="node_description">Software artifact repository product renewed by SSA through delivery order 28321326FDX030022.</data><data key="node_observed_status">procured_renewal_2026</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">Procurement establishes software renewal only. Hosting, version, repositories, development pipelines, and consuming applications are not public in this source.</data></node><node id="TECH_STC_VPN"><data key="node_entity_id">TECH_STC_VPN</data><data key="node_entity_type">network_technology</data><data key="node_canonical_name">State Transmission Component Site-to-Site VPN</data><data key="node_acronym">VPN</data><data key="node_domain">External Data Exchange / Network Security</data><data key="node_description">Direct site-to-site Virtual Private Network connection between a participating state or jurisdiction and SSA as part of the State Transmission Component.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Modeled as the STC network-security component described by SSA; specific VPN product, endpoint technology, and cryptographic implementation are not public.</data></node><node id="TECH_THUNDERHEAD"><data key="node_entity_id">TECH_THUNDERHEAD</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Thunderhead</data><data key="node_domain">Technology</data><data key="node_description">Commercial correspondence/noticing technology identified in current DCPS Correspondence metadata.</data><data key="node_observed_status">observed_current_metadata</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Metadata association does not establish product version or complete implementation topology.</data></node><node id="TECH_TOKEN_RING"><data key="node_entity_id">TECH_TOKEN_RING</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Token Ring LAN</data><data key="node_acronym">Token Ring</data><data key="node_domain">Infrastructure / Network</data><data key="node_description">IBM-associated local-area-network technology selected for SSA's IWS/LAN architecture.</data><data key="node_observed_status">historically_documented_1994</data><data key="node_observed_as_of">1994-04</data><data key="node_confidence">5</data><data key="node_notes">Historical technology selection; current use is not inferred.</data></node><node id="TECH_UIPATH_RPA"><data key="node_entity_id">TECH_UIPATH_RPA</data><data key="node_entity_type">technology</data><data key="node_canonical_name">UiPath Robotic Process Automation Software</data><data key="node_acronym">UiPath</data><data key="node_domain">Infrastructure / Operations Automation</data><data key="node_description">SSA identifies UiPath as software used to create production robotic routines supporting processing center technicians with awards and post-entitlement workloads.</data><data key="node_observed_status">documented_production_2025</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Explicit agency deployment; not infer license quantities, bot scripts, APIs, or 2026 version.</data></node><node id="TECH_UNISON_PRISM"><data key="node_entity_id">TECH_UNISON_PRISM</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Unison PRISM</data><data key="node_acronym">PRISM</data><data key="node_domain">Acquisition / COTS</data><data key="node_description">Commercial contract-writing software documented as the COTS platform used by SSA Streamlined Acquisition System (SSASy).</data><data key="node_observed_status">documented_2020_product_current_ssasy_confirmed</data><data key="node_observed_as_of">2020-05-19</data><data key="node_confidence">5</data><data key="node_notes">SSASy remains current in OAG guidance, but this run did not find a post-2020 first-party statement explicitly reconfirming PRISM product version/deployment.</data></node><node id="TECH_WEBSPHERE"><data key="node_entity_id">TECH_WEBSPHERE</data><data key="node_entity_type">technology</data><data key="node_canonical_name">IBM WebSphere</data><data key="node_acronym">WebSphere</data><data key="node_domain">Technology</data><data key="node_description">Application platform documented for the GUVERF02 SSN Verification Service interface.</data><data key="node_observed_status">cataloged_legacy_metadata</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">3</data><data key="node_notes">Source metadata is from 2018.</data></node><node id="TECH_WSDL"><data key="node_entity_id">TECH_WSDL</data><data key="node_entity_type">technology</data><data key="node_canonical_name">Web Services Description Language</data><data key="node_acronym">WSDL</data><data key="node_domain">Integration Technology</data><data key="node_description">Service-description language used by the historical EREWS interface to define operations and bindings.</data><data key="node_observed_status">historically_documented_erews_2007</data><data key="node_observed_as_of">2007-07-02</data><data key="node_confidence">5</data><data key="node_notes">Scoped to EREWS.</data></node><node id="TECH_WS_SECURITY"><data key="node_entity_id">TECH_WS_SECURITY</data><data key="node_entity_type">technology</data><data key="node_canonical_name">WS-Security</data><data key="node_acronym">WS-Security</data><data key="node_domain">Integration Security</data><data key="node_description">OASIS web-services security standard documented for EREWS authentication/security headers.</data><data key="node_observed_status">historically_documented_erews_2007</data><data key="node_observed_as_of">2007-07-02</data><data key="node_confidence">5</data><data key="node_notes">Historical EREWS implementation evidence only.</data></node><node id="TECH_X509"><data key="node_entity_id">TECH_X509</data><data key="node_entity_type">technology</data><data key="node_canonical_name">X.509 Digital Certificate</data><data key="node_acronym">X.509</data><data key="node_domain">Security / PKI</data><data key="node_description">Public-key digital certificate standard used by the current EWRWS security model for SOAP message digital signatures.</data><data key="node_observed_status">observed_current_for_ewrws</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Captured only where SSA's current-linked EWRWS Terms of Service explicitly requires it.</data></node><node id="TXN_TYPE_M_OFFLINE_QUERY"><data key="node_entity_id">TXN_TYPE_M_OFFLINE_QUERY</data><data key="node_entity_type">query_transaction</data><data key="node_canonical_name">Type M Offline Query</data><data key="node_acronym">Type M</data><data key="node_domain">Medicare / State Buy-In / Query</data><data key="node_description">Offline query request used to force an SSR finder when an SSR-MBR state buy-in interface problem requires correction.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Modeled as the named query transaction; no queue, batch platform, or transport is inferred.</data></node><node id="UI_ADRP_DOCUMENT_CONTACT"><data key="node_entity_id">UI_ADRP_DOCUMENT_CONTACT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">ADRP Document Contact Page</data><data key="node_acronym">Document Contact</data><data key="node_domain">Payee / Person Identity</data><data key="node_description">iMain-accessed ADRP page to record attempts to contact advance designees and beneficiary; unavailable when ADRP launched via MCS or SSI Claims.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_APWA"><data key="node_entity_id">UI_APWA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Application Programmatic Wage Authorization Page</data><data key="node_acronym">APWA</data><data key="node_domain">Earnings / Digital Service</data><data key="node_description">Access page identified in POMS as one route to the Wage and Employment Information Authorization application.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Modeled only as an access point; no separate backend or application boundary is inferred.</data></node><node id="UI_CCE_FIN_ACCOUNTS"><data key="node_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">CCE Financial Accounts Screen</data><data key="node_acronym">Financial Accounts</data><data key="node_domain">Title XVI / Resources / CCE</data><data key="node_description">Consolidated Claims Experience screen used to record financial accounts, including an account used for direct deposit when resource development is required.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies the screen and its use during redetermination resource development.</data></node><node id="UI_CCE_HEALTH_INSURANCE"><data key="node_entity_id">UI_CCE_HEALTH_INSURANCE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">CCE Health Insurance / Medicaid Buy-In Screen</data><data key="node_acronym">CCE Health Insurance</data><data key="node_domain">Medicare / State Coordination</data><data key="node_description">CCE Health Insurance workflow used to record Medicaid status and initiate State buy-in.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_CCE_ROC"><data key="node_entity_id">UI_CCE_ROC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">CCE Report of Contact Page</data><data key="node_acronym">DROC</data><data key="node_domain">Title XVI / Case Documentation</data><data key="node_description">Consolidated Claims Experience page used to document capability determinations for Title XVI-only cases not established in eRPS.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS references MS 07416.002; implementation technology is not inferred.</data></node><node id="UI_CWP"><data key="node_entity_id">UI_CWP</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Consolidated Wage Page</data><data key="node_acronym">CWP</data><data key="node_domain">Disability / Work CDR / Earnings</data><data key="node_description">EDCS page that presents a consolidated view of commonly used wage-data sources for work CDR and related wage verification; the 2021 release specifically included iTOPSS data.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-11</data><data key="node_confidence">5</data><data key="node_notes">Released December 11, 2021 as part of the Work CDR product; current 2025 POMS still directs technicians to CWP in EDCS.</data></node><node id="UI_DCF_DRES"><data key="node_entity_id">UI_DCF_DRES</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DCF Disability Review Establishment Screen</data><data key="node_acronym">DRES</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">Disability Control File screen used to manually establish a new CDR in UMC processing.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public POMS cites MSOM CDR 001.016.</data></node><node id="UI_DCF_IFOA"><data key="node_entity_id">UI_DCF_IFOA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DCF CDR FO Input Screen</data><data key="node_acronym">IFOA</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">Disability Control File input screen used in current UMC procedures to close a prior CDR by recording the prior cessation determination.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public POMS cites MSOM CDR 001.007.</data></node><node id="UI_DCF_IRMK"><data key="node_entity_id">UI_DCF_IRMK</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DCF CDR Remarks Input Screen</data><data key="node_acronym">IRMK</data><data key="node_domain">Disability / Continuing Disability Review</data><data key="node_description">Disability Control File remarks screen used to document that the UMC cessation determination was set aside.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public POMS cites MSOM CDR 001.009.</data></node><node id="UI_DDSQ_MASK"><data key="node_entity_id">UI_DDSQ_MASK</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DDSQ Query Mask</data><data key="node_acronym">DDSQ Mask</data><data key="node_domain">DDS Disability Processing</data><data key="node_description">DDSQ query mask used by field offices to retrieve National Disability Determination Services System case information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_DMA_VIEWER"><data key="node_entity_id">UI_DMA_VIEWER</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Document Management Architecture Viewer</data><data key="node_acronym">DMA Viewer</data><data key="node_domain">Disability / Evidence</data><data key="node_description">Viewer used from EDCS/eView workflows to review and manipulate documents managed through the Document Management Architecture.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-01</data><data key="node_confidence">5</data><data key="node_notes">Current EDCS TOC retains the iAppeals document-receipt workflow; detailed DMA Viewer behavior is documented in the 2023 POMS section. No separate product/vendor is inferred.</data></node><node id="UI_DMS_DMFS"><data key="node_entity_id">UI_DMS_DMFS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Debt Management Function Selection</data><data key="node_acronym">DMFS</data><data key="node_domain">Debt &amp; Overpayments / Work Routing</data><data key="node_description">Workload Management System Debt Management Function Selection screen used within the DMS waiver workflow to transfer jurisdiction to a processing center.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">POMS wording names WMS and DMS in the same action; this record represents the named screen only, not an inferred WMS/DMS physical interface.</data></node><node id="UI_DMS_DRAD"><data key="node_entity_id">UI_DMS_DRAD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Fact/Amount Appeal Disposition</data><data key="node_acronym">DRAD</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Debt Management System screen used to record fact/amount reconsideration and specified Title II waiver-related dispositions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Screen code and DMS context are explicit in current POMS.</data></node><node id="UI_DMS_DRCD"><data key="node_entity_id">UI_DMS_DRCD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Record Compromise Decision</data><data key="node_acronym">DRCD</data><data key="node_domain">Payments / Debt</data><data key="node_description">Debt Management System screen used to record a field-office compromise decision.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current August 2026 POMS identifies DRCD as the Record Compromise Decision screen.</data></node><node id="UI_DMS_DRCW"><data key="node_entity_id">UI_DMS_DRCW</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Review Compromise Approval</data><data key="node_acronym">DRCW</data><data key="node_domain">Payments / Debt</data><data key="node_description">Debt Management System screen used for second-level review of compromise decisions when required.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current August 2026 POMS identifies DRCW as Review Compromise Approval for compromises over $2,000.</data></node><node id="UI_DMS_DRDY"><data key="node_entity_id">UI_DMS_DRDY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">ROAR Diary Processing</data><data key="node_acronym">DRDY</data><data key="node_domain">Debt &amp; Overpayments / Work Control</data><data key="node_description">Debt Management System screen used to establish ROAR diary controls, including 90-day diaries in specified unauthorized-payment cases.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">4</data><data key="node_notes">Direct POMS evidence is from a 2022-revised section still current in the policy corpus; no separate backend is inferred.</data></node><node id="UI_DMS_DROA"><data key="node_entity_id">UI_DMS_DROA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Resume Recovery Screen</data><data key="node_acronym">DROA</data><data key="node_domain">Title II / Debt Management</data><data key="node_description">Debt Management System screen used to resume collection after an overpayment explanation has been provided.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS names the DROA screen and the COM+3 resumption action.</data></node><node id="UI_DMS_DRPC"><data key="node_entity_id">UI_DMS_DRPC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Process Personal Conference Screen</data><data key="node_acronym">DRPC</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">DRPC records Title II personal-conference determination; workflow requires a separate reviewer from DRWD preparer.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_DMS_DRWD"><data key="node_entity_id">UI_DMS_DRWD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Waiver Disposition Screen</data><data key="node_acronym">DRWD</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">DRWD screen posts Title II waiver approval decision to ROAR; used alongside other waiver processing controls.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_DMS_DRWR"><data key="node_entity_id">UI_DMS_DRWR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Review Waiver Disposition Screen</data><data key="node_acronym">DRWR</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">DRWR screen documents Title II waiver approval second review input.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_DMS_RCFR"><data key="node_entity_id">UI_DMS_RCFR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Correct Field Office Receipt Screen</data><data key="node_acronym">RCFR</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">Debt Management System screen used to correct field-office receipt information other than specified amount fields.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS.</data></node><node id="UI_DMS_RCRD"><data key="node_entity_id">UI_DMS_RCRD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Change Field Office Receipt Date Screen</data><data key="node_acronym">RCRD</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">Debt Management System screen used to change a field-office receipt date.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS.</data></node><node id="UI_DMS_REQD"><data key="node_entity_id">UI_DMS_REQD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS REQD Screen</data><data key="node_acronym">REQD</data><data key="node_domain">Payments / Debt / DMS</data><data key="node_description">Debt Management System screen whose Receipt Number field displays the lockbox Individual Reference Number for lockbox-origin remittances.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public POMS identifies the screen acronym but does not expand REQD; no expansion is inferred.</data></node><node id="UI_DMS_RFOR"><data key="node_entity_id">UI_DMS_RFOR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Field Office Remittance Input Screen</data><data key="node_acronym">RFOR</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">Debt Management System screen used by field-office staff to enter remittance information.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS.</data></node><node id="UI_DMS_RMCR"><data key="node_entity_id">UI_DMS_RMCR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Manager Correct/Delete FO Receipt Screen</data><data key="node_acronym">RMCR</data><data key="node_domain">Payments / Debt / Remittances</data><data key="node_description">Debt Management System management screen used for corrections or deletion actions involving remittance or credit amount fields.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current March 2026 POMS.</data></node><node id="UI_DMS_RMKI"><data key="node_entity_id">UI_DMS_RMKI</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">DMS Remarks Index Screen</data><data key="node_acronym">RMKI</data><data key="node_domain">Payments &amp; Debt</data><data key="node_description">RMKI screen allows remark classification for initial waiver determination documentation.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_DMS_RMKS"><data key="node_entity_id">UI_DMS_RMKS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Debt Management System Remarks Screen</data><data key="node_acronym">RMKS</data><data key="node_domain">Payments / Debt</data><data key="node_description">DMS remarks screen used to document financial and other case-development information for debt/compromise actions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current August 2026 POMS expressly directs technicians to document financial circumstances on the DMS RMKS screen.</data></node><node id="UI_DSWM"><data key="node_entity_id">UI_DSWM</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">State Wage Match Development Screen</data><data key="node_acronym">DSWM</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">SSI Claims screen used to clear state/OCSE wage match development and build the transaction sent to the Supplemental Security Record.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">POMS cites MS 04422.016 for the DSWM screen.</data></node><node id="UI_ECO_TRRN"><data key="node_entity_id">UI_ECO_TRRN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">ECO Returned Notice Manual Input Screen</data><data key="node_acronym">TRRN</data><data key="node_domain">Debt &amp; External Collections / Returned Mail</data><data key="node_description">Fallback ECO screen used to input undeliverable External Collections notices when barcode scanning is not possible or notices are returned elsewhere.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_ECO_TRUN"><data key="node_entity_id">UI_ECO_TRUN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">ECO Returned Notice Barcode Scan Screen</data><data key="node_acronym">TRUN</data><data key="node_domain">Debt &amp; External Collections / Returned Mail</data><data key="node_description">ECO screen used by PC7 ODO mailroom staff to scan barcodes on undeliverable External Collections notices.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_EDCS_ACTIONS"><data key="node_entity_id">UI_EDCS_ACTIONS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS Actions Page</data><data key="node_acronym">EDCS Actions</data><data key="node_domain">Disability / Workflow</data><data key="node_description">EDCS page that presents Electronic Assistance Requests and Action Items requiring field-office action on certified electronic folders.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-01</data><data key="node_confidence">5</data><data key="node_notes">Current POMS states ARs/AIs are stored in the EDCS database and the page is reviewed daily.</data></node><node id="UI_EDCS_INTERNET_DOCS"><data key="node_entity_id">UI_EDCS_INTERNET_DOCS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS Internet Documents Page</data><data key="node_acronym">Internet Documents</data><data key="node_domain">Disability / Evidence / EDCS</data><data key="node_description">EDCS case page used to review and control Internet-submitted documents associated with a disability appeal case.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2023-12-28</data><data key="node_confidence">5</data><data key="node_notes">Supports retain/discard actions and commitment to the electronic folder.</data></node><node id="UI_EDCS_MCS_EXCLUSION_INFO"><data key="node_entity_id">UI_EDCS_MCS_EXCLUSION_INFO</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS MCS Exclusion Information Screen</data><data key="node_acronym">MCS Exclusion Information</data><data key="node_domain">Disability / EDCS</data><data key="node_description">EDCS screen used when no current MCS or MSSICS claim/appeal exists; available data from other SSA mainframe sources populate the screen and technicians complete otherwise-propagated fields.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-03-17</data><data key="node_confidence">5</data><data key="node_notes">Not a separate database; screen data then populate other EDCS screens.</data></node><node id="UI_EDCS_PREVIEW_INTERNET_DOCS"><data key="node_entity_id">UI_EDCS_PREVIEW_INTERNET_DOCS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">EDCS Preview Internet Documents Page</data><data key="node_acronym">Preview Internet Documents</data><data key="node_domain">Disability / Evidence / EDCS</data><data key="node_description">EDCS page used before case creation to search, review, retain, or discard Internet documents submitted with iAppeals.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2023-12-28</data><data key="node_confidence">5</data><data key="node_notes">Searches documents by claimant SSN and returns only documents not already associated with an EDCS case.</data></node><node id="UI_EIF_AEQY"><data key="node_entity_id">UI_EIF_AEQY</data><data key="node_entity_type">query_interface</data><data key="node_canonical_name">Employer Identification File Access Query</data><data key="node_acronym">AEQY</data><data key="node_domain">Earnings / Employer Identity</data><data key="node_description">SSA query interface used in current procedures to access employer/EIN information in the Employer Identification File.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">An EIN is not a unique organizational identity key by itself; policy requires verification and discrepancy handling.</data></node><node id="UI_ELAS_RMRK"><data key="node_entity_id">UI_ELAS_RMRK</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eLAS Remarks Screen</data><data key="node_acronym">RMRK</data><data key="node_domain">Customer Service / Appointments</data><data key="node_description">eLAS remarks screen on which iAppointment records non-English language or sign-language assistance needs.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-06-26</data><data key="node_confidence">5</data><data key="node_notes">Current POMS documents message content but not backend persistence.</data></node><node id="UI_ELAS_WKSH"><data key="node_entity_id">UI_ELAS_WKSH</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eLAS Leads/Protective Filing Worksheet Screen</data><data key="node_acronym">WKSH</data><data key="node_domain">Customer Service / Appointments</data><data key="node_description">eLAS worksheet screen that carries the UNVER issue for protective filings and appointments created from iAppointment.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-06-26</data><data key="node_confidence">5</data><data key="node_notes">Screen-level object only.</data></node><node id="UI_ERPC_WORKLOAD_MGMT"><data key="node_entity_id">UI_ERPC_WORKLOAD_MGMT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPC Workload Management Screen</data><data key="node_acronym">Workload Management</data><data key="node_domain">Disability / Program Consultation</data><data key="node_description">eRPC screen used by RPC staff to track, assign, monitor, and timely process Request for Program Consultation cases.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="UI_ERPC_WORKLOAD_SUMMARY"><data key="node_entity_id">UI_ERPC_WORKLOAD_SUMMARY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPC Workload Summary Screen</data><data key="node_acronym">Workload Summary</data><data key="node_domain">Disability / Program Consultation</data><data key="node_description">eRPC screen listing submitted RPCs that are not yet resolved and allowing authorized managers to review pending cases.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="UI_ERPS_ADD_NEW_ISSUE"><data key="node_entity_id">UI_ERPS_ADD_NEW_ISSUE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Add New Issue Screen</data><data key="node_acronym">Add New Issue</data><data key="node_domain">Representative Payee / Work Control</data><data key="node_description">eRPS screen used to establish a follow-up diary for a questionable representative payee.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS cites MS 07408.007.</data></node><node id="UI_ERPS_APPLICANT_ID"><data key="node_entity_id">UI_ERPS_APPLICANT_ID</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Proof of Applicant's Identity Screen</data><data key="node_domain">Representative Payee / Identity</data><data key="node_description">eRPS screen used to document how a representative-payee applicant identity was verified, including NUMI-based verification for telephone or video interviews.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies this screen as MS 07409.011.</data></node><node id="UI_ERPS_BENEFICIARY_ADDRESS_CHANGE"><data key="node_entity_id">UI_ERPS_BENEFICIARY_ADDRESS_CHANGE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Beneficiary Address Change Screen</data><data key="node_acronym">Beneficiary Address Change</data><data key="node_domain">Representative Payee / Address Provenance</data><data key="node_description">eRPS screen used to update beneficiary residence address during representative-payee organizational changes and related address/custody processing.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2025-05-16</data><data key="node_confidence">5</data><data key="node_notes">MS 07414.010; specific backing tables are not established.</data></node><node id="UI_ERPS_BENE_DETAILS"><data key="node_entity_id">UI_ERPS_BENE_DETAILS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Beneficiary Details Screen</data><data key="node_domain">Representative Payee / Beneficiary Record</data><data key="node_description">eRPS screen whose notes hold capability determinations associated with the beneficiary's eRPS record.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">June 2026 POMS directs staff to Beneficiary Details and its notes for capability determinations.</data></node><node id="UI_ERPS_BG_PERMISSION"><data key="node_entity_id">UI_ERPS_BG_PERMISSION</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Permission for Background Check Screen</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">eRPS screen used to record applicant permission before SSA conducts a criminal background check.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies this screen as MS 07409.014.</data></node><node id="UI_ERPS_BG_RESULTS"><data key="node_entity_id">UI_ERPS_BG_RESULTS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Criminal Background Check Results Screen</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">eRPS screen used to present criminal-background information that staff discuss and verify with a payee applicant.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS references the Background Check Results screen and MS 07409.024.</data></node><node id="UI_ERPS_EIN_INFO_FROM_EIF"><data key="node_entity_id">UI_ERPS_EIN_INFO_FROM_EIF</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS EIN Info from EIF Screen</data><data key="node_acronym">EIN Info from EIF</data><data key="node_domain">Representative Payee / Employer Identity</data><data key="node_description">eRPS screen displaying the EIN match result and most recent name entry returned from the Employer Identification File.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2023-05-23</data><data key="node_confidence">5</data><data key="node_notes">MS INTRANETERPS 014.003; screen is not modeled as a repository.</data></node><node id="UI_ERPS_FUGITIVE_FELON"><data key="node_entity_id">UI_ERPS_FUGITIVE_FELON</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Fugitive Felon Information Screen</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">eRPS screen used to display fugitive-felon record information during representative-payee applicant suitability review.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies this screen as MS 07410.003.</data></node><node id="UI_ERPS_LEGAL_GUARDIAN_DETAILS"><data key="node_entity_id">UI_ERPS_LEGAL_GUARDIAN_DETAILS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Legal Guardian Details Screen</data><data key="node_acronym">Legal Guardian Details</data><data key="node_domain">Representative Payee / Legal Evidence</data><data key="node_description">eRPS screen referenced for documenting legal guardian information and existing guardian evidence.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="UI_ERPS_MAKE_NOTE"><data key="node_entity_id">UI_ERPS_MAKE_NOTE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Make Note Screen</data><data key="node_domain">Representative Payee / Case Documentation</data><data key="node_description">eRPS screen used with the Rep Payee Applicant Note Type to document interview circumstances, suitability observations, and criminal-history-related notes.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies this screen as MS 07415.002.</data></node><node id="UI_ERPS_MERGE_ORGANIZATION"><data key="node_entity_id">UI_ERPS_MERGE_ORGANIZATION</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Merge Organization/Institution Screen</data><data key="node_domain">Representative Payee / Organizations</data><data key="node_description">eRPS screen used by FO after due process to execute documented organizational representative payee mass changes.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_ERPS_ORG_BASIC_INFO"><data key="node_entity_id">UI_ERPS_ORG_BASIC_INFO</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Rep Payee Organization Basic Info Screen</data><data key="node_acronym">Organization Basic Info</data><data key="node_domain">Representative Payee / eRPS</data><data key="node_description">eRPS organization-information screen used for organizational representative-payee details; current policy directs staff to use it for public-guardian name and title information in the payment legend.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS cites MS 07414.007 for this screen.</data></node><node id="UI_ERPS_PAYMENT_LEGEND"><data key="node_entity_id">UI_ERPS_PAYMENT_LEGEND</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Payment Legend Screen</data><data key="node_acronym">Payment Legend</data><data key="node_domain">Representative Payee / eRPS</data><data key="node_description">eRPS screen used to record the payment legend, including special naming requirements for joint or public guardians.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current eRPS POMS identifies the Payment Legend screen; physical implementation is not further inferred.</data></node><node id="UI_ERPS_PENDING_APPLICATIONS"><data key="node_entity_id">UI_ERPS_PENDING_APPLICATIONS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Pending Applications Screen</data><data key="node_domain">Representative Payee / Organizations</data><data key="node_description">eRPS screen queried to identify beneficiaries affected by an organizational payee change.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_ERPS_PRISONER_INFO"><data key="node_entity_id">UI_ERPS_PRISONER_INFO</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Prisoner Information Screen</data><data key="node_domain">Representative Payee / Program Integrity</data><data key="node_description">eRPS screen used to display a payee applicant PUPS incarceration record during suitability review.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies this screen as MS 07410.004.</data></node><node id="UI_ERPS_RELATIONSHIP_DETAILS"><data key="node_entity_id">UI_ERPS_RELATIONSHIP_DETAILS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Relationship Details Tab</data><data key="node_domain">Representative Payee / Financial Management</data><data key="node_description">Tab on which staff document representative payee fiduciary ABLE account titling in a note.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_ERPS_ROC_DETAILS"><data key="node_entity_id">UI_ERPS_ROC_DETAILS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Report of Contact Details Screen</data><data key="node_acronym">Report of Contact Details</data><data key="node_domain">Representative Payee / Case Documentation</data><data key="node_description">eRPS screen used to record personal-contact findings during follow-up of questionable representative payees.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS cites MS 07416.002.</data></node><node id="UI_ERPS_RPST"><data key="node_entity_id">UI_ERPS_RPST</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Representative Payee Suitability Screen</data><data key="node_acronym">RPST</data><data key="node_domain">Representative Payee</data><data key="node_description">eRPS/Representative Payee System screen used to document a suitability determination for a fee-for-service organizational payee applicant.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-15</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly directs staff to document the determination in the RPST screen.</data></node><node id="UI_ERPS_SELECTED_LIST"><data key="node_entity_id">UI_ERPS_SELECTED_LIST</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Selected List Screen</data><data key="node_domain">Representative Payee / Organizations</data><data key="node_description">eRPS listing used to identify beneficiaries currently assigned to an organizational payee.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_ERPS_SELECTION_DECISION"><data key="node_entity_id">UI_ERPS_SELECTION_DECISION</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS Rep Payee Selection-Decision Screen</data><data key="node_domain">Representative Payee / Selection</data><data key="node_description">eRPS decision screen used to select or non-select a representative-payee applicant, including barred-crime non-selection outcomes.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS names the Rep Payee Selection-Decision screen; public source does not expose its implementation.</data></node><node id="UI_ERPS_SSA11_INTRO"><data key="node_entity_id">UI_ERPS_SSA11_INTRO</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eRPS SSA-11 Application-Introduction Screen</data><data key="node_domain">Representative Payee / Intake</data><data key="node_description">eRPS application screen used to begin the SSA-11 payee application interview and record interview-channel information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies this screen as MS 07409.002. Physical UI technology is not public.</data></node><node id="UI_EVIEW_ALERTS_MESSAGES"><data key="node_entity_id">UI_EVIEW_ALERTS_MESSAGES</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Alerts &amp; Messages Tab</data><data key="node_acronym">Alerts &amp; Messages</data><data key="node_domain">Disability / eView</data><data key="node_description">eView case tab for alerts and messages associated with an electronic disability case.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="UI_EVIEW_CASE_DOCUMENTS"><data key="node_entity_id">UI_EVIEW_CASE_DOCUMENTS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Case Documents Tab</data><data key="node_acronym">Case Documents</data><data key="node_domain">Disability / eView</data><data key="node_description">eView case tab used to view documents contained in the electronic folder.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="UI_EVIEW_CASE_PROCESS_VIEW"><data key="node_entity_id">UI_EVIEW_CASE_PROCESS_VIEW</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Disability Case Process (View Mode) Screen</data><data key="node_acronym">Disability Case Process</data><data key="node_domain">Disability / eView</data><data key="node_description">Main eView case screen shown after selection of a specific case, containing title bars, tabs, links, and case functions.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="UI_EVIEW_CASE_SELECTION"><data key="node_entity_id">UI_EVIEW_CASE_SELECTION</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Case Selection Screen</data><data key="node_acronym">Case Selection</data><data key="node_domain">Disability / eView</data><data key="node_description">eView screen used to search for and select a specific electronic disability case by claimant identifiers or EDCS Folder Number.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS also calls the results surface the eView Disability Folder Selection screen; retained here as one canonical UI with an alias to avoid duplicate screens.</data></node><node id="UI_EVIEW_EXHIBIT_LIST"><data key="node_entity_id">UI_EVIEW_EXHIBIT_LIST</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Exhibit List Tab</data><data key="node_acronym">Exhibit List</data><data key="node_domain">Hearings &amp; Appeals / eView</data><data key="node_description">eView tab available when an exhibit list exists, including additional OHO/OAO functionality at hearings and Appeals Council levels.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="UI_EVIEW_INTERNET_DOC_HISTORY"><data key="node_entity_id">UI_EVIEW_INTERNET_DOC_HISTORY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Internet Documents History Page</data><data key="node_acronym">Internet Documents History</data><data key="node_domain">Disability / Evidence / eView</data><data key="node_description">eView history page showing document status and retention action for Internet documents after EDCS processing.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2023-12-28</data><data key="node_confidence">5</data><data key="node_notes">Some discarded-document images are permanently deleted while metadata/details remain viewable depending on discard reason.</data></node><node id="UI_EVIEW_STATUS_HISTORY"><data key="node_entity_id">UI_EVIEW_STATUS_HISTORY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">eView Status/History Tab</data><data key="node_acronym">Status/History</data><data key="node_domain">Disability / eView</data><data key="node_description">eView case tab displaying case status and history information.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="UI_IMNU"><data key="node_entity_id">UI_IMNU</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Internet Menu</data><data key="node_acronym">IMNU</data><data key="node_domain">Title II / Internet Claims</data><data key="node_description">Internet Menu referenced by current POMS as the location of the iClaim completion date used to determine an electronically signed Internet application’s submission/receipt date.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">The public POMS identifies the menu and policy role but does not expose its internal implementation; no hosting topology is inferred.</data></node><node id="UI_IRCS_QPID"><data key="node_entity_id">UI_IRCS_QPID</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">IRCS Incentive Payment Identification Query Screen</data><data key="node_acronym">QPID</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">IRCS query screen whose Incentive Payment Data section provides incentive payee name, institutional mailing address, and payment-contact information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_IRMAA_IRLC"><data key="node_entity_id">UI_IRMAA_IRLC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">IRMAA Life-Changing Event Screen</data><data key="node_acronym">IRLC</data><data key="node_domain">Medicare / IRMAA</data><data key="node_description">IRMAA screen used to select a qualifying life-changing event, record the event date, proof status, and remarks.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_IRMAA_IRMA"><data key="node_entity_id">UI_IRMAA_IRMA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">IRMAA Income and Tax Data Screen</data><data key="node_acronym">IRMA</data><data key="node_domain">Medicare / IRMAA</data><data key="node_description">IRMAA screen used in the new-initial-determination sequence to enter adjusted gross income, tax-exempt interest, filing status, source, and proof information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Canonical label is descriptive; SSA policy identifies the IRMA screen and its fields but not a longer formal screen name.</data></node><node id="UI_IRMAA_IRMN"><data key="node_entity_id">UI_IRMAA_IRMN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">IRMAA Request Screen</data><data key="node_acronym">IRMN</data><data key="node_domain">Medicare / IRMAA</data><data key="node_description">IRMAA screen used to establish and process a new-initial-determination request; current policy also uses it to route users to EVID through Shared Processes.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_IRMAA_IRRE"><data key="node_entity_id">UI_IRMAA_IRRE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">IRMAA Results Screen</data><data key="node_acronym">IRRE</data><data key="node_domain">Medicare / IRMAA</data><data key="node_description">IRMAA results screen showing current and recalculated IRMAA data and supporting dismissal or changed-determination processing.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_IRMAA_PYTY"><data key="node_entity_id">UI_IRMAA_PYTY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">IRMAA Premium Year / Tax Year Screen</data><data key="node_acronym">PYTY</data><data key="node_domain">Medicare / IRMAA</data><data key="node_description">IRMAA screen in the current new-initial-determination sequence for premium-year and tax-year information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Expanded screen name inferred only from the documented PY/TY context and screen mnemonic; physical implementation is not inferred.</data></node><node id="UI_MACADE_ATT"><data key="node_entity_id">UI_MACADE_ATT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MACADE ATT Screen</data><data key="node_acronym">ATT</data><data key="node_domain">Representation / Title II</data><data key="node_description">MACADE screen that current appointment policy instructs technicians to review as applicable for current appointed-representative information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Mnemonic expansion and backing store are not stated in the public source.</data></node><node id="UI_MAPS_APPLICANT_INFO"><data key="node_entity_id">UI_MAPS_APPLICANT_INFO</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Applicant Information Screen</data><data key="node_acronym">Applicant Information</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS application screen used to record applicant information for Extra Help applications.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_ATWE"><data key="node_entity_id">UI_MAPS_ATWE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Work Stop Date and Work Expenses for Disability Screen</data><data key="node_acronym">ATWE</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS application screen used to record work-stop date and disability-related work-expense information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_CURRENT_AGENCY_DATA"><data key="node_entity_id">UI_MAPS_CURRENT_AGENCY_DATA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Current Agency Data Screen</data><data key="node_acronym">Current Agency Data</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS screen displaying current agency data used in Extra Help verification, including specified OCSE unemployment information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_DADS"><data key="node_entity_id">UI_MAPS_DADS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Detailed Agency Data Screen</data><data key="node_acronym">Detailed Agency Data</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS screen showing detailed agency-data items; for IRS reports it includes document code, income type, payer EIN, and amount.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_DEV_WORKSHEET"><data key="node_entity_id">UI_MAPS_DEV_WORKSHEET</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Development Worksheet</data><data key="node_acronym">MAPS Development Worksheet</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS worksheet that creates and tracks verification issues for Extra Help applications.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_DWRC"><data key="node_entity_id">UI_MAPS_DWRC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Report of Contact Screen</data><data key="node_acronym">DWRC</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS report-of-contact screen used to document verification development and claimant responses.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_EARNED_INCOME"><data key="node_entity_id">UI_MAPS_EARNED_INCOME</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Earned Income Application Screen</data><data key="node_acronym">Earned Income</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS application screen used to record earned-income information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_INSURANCE_BURIAL_RE"><data key="node_entity_id">UI_MAPS_INSURANCE_BURIAL_RE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Insurance, Burial Information and Real Estate Screen</data><data key="node_acronym">Insurance/Burial/Real Estate</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS application screen for insurance, burial information, and real-estate questions.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_MEDICARE_SAVINGS_PLAN"><data key="node_entity_id">UI_MAPS_MEDICARE_SAVINGS_PLAN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Medicare Savings Plan Application Screen</data><data key="node_acronym">Medicare Savings Plan</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS screen used to record the claimant decision concerning referral of Extra Help application information to the State for Medicare Savings Program consideration.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_PREDECISION_PERIOD"><data key="node_entity_id">UI_MAPS_PREDECISION_PERIOD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Pre-Decisional Period Screen</data><data key="node_acronym">Pre-Decisional Period</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS screen used to review the pre-decisional response period and related pending action.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_RELATIVES_EXPENSE"><data key="node_entity_id">UI_MAPS_RELATIVES_EXPENSE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Number of Relatives and Help with Expense Screen</data><data key="node_acronym">Relatives/Expense</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS application screen for household relatives and help-with-expense information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_SAVINGS_ACCOUNTS"><data key="node_entity_id">UI_MAPS_SAVINGS_ACCOUNTS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Savings and Accounts Screen</data><data key="node_acronym">Savings and Accounts</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS application screen used to record savings and account information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_UNEARNED_INCOME"><data key="node_entity_id">UI_MAPS_UNEARNED_INCOME</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Unearned Income Application Screen</data><data key="node_acronym">Unearned Income</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS application screen used to record unearned-income information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MAPS_VRAI"><data key="node_entity_id">UI_MAPS_VRAI</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MAPS Issue Verification Screen</data><data key="node_acronym">VRAI</data><data key="node_domain">Medicare / Extra Help</data><data key="node_description">MAPS verification screen used to review and resolve discrepancies between application allegations and agency data.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MCS_ADDB"><data key="node_entity_id">UI_MCS_ADDB</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Additional Benefits ADDB Screen</data><data key="node_acronym">ADDB</data><data key="node_domain">Title II / Historical GPO</data><data key="node_description">MCS Additional Benefits screen captured noncovered pension information for GPO initial-claim development applicable only to entitlement months before January 2024.</data><data key="node_observed_status">legacy_pre_2024_processing</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MCS_ADDR"><data key="node_entity_id">UI_MCS_ADDR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Address Screen</data><data key="node_acronym">ADDR</data><data key="node_domain">Title II / Claims / Address</data><data key="node_description">Modernized Claims System screen used to hold the number holder’s last-known address in unknown-address claim processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current GN 01010.300 names the ADDR screen; no separate underlying address database is inferred.</data></node><node id="UI_MCS_CADR"><data key="node_entity_id">UI_MCS_CADR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Claimant Address Screen</data><data key="node_acronym">CADR</data><data key="node_domain">Title II / Claims / Address</data><data key="node_description">Modernized Claims System screen on which staff enter the claimant mailing address during RSDI claims processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly states the CADR mailing address propagates to the MCS ADDR screen.</data></node><node id="UI_MCS_DECI"><data key="node_entity_id">UI_MCS_DECI</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Decision/Diary Control Screen</data><data key="node_acronym">DECI</data><data key="node_domain">Title II / Claims / Control</data><data key="node_description">Modernized Claims System screen used to establish a diary controlling unknown-address development.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current GN 01010.300 directs technicians to establish the address-development diary on DECI.</data></node><node id="UI_MCS_DICL"><data key="node_entity_id">UI_MCS_DICL</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Disability Allowance/Denial Screen</data><data key="node_acronym">DICL</data><data key="node_domain">Title II / Disability / User Interface</data><data key="node_description">Modernized Claims System screen that receives specified disability determination data, including statutory-blind allowance indicators and adjusted blind onset information.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 POMS explicitly identifies the DICL screen.</data></node><node id="UI_MCS_DRRE"><data key="node_entity_id">UI_MCS_DRRE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Railroad Earnings Data Screen</data><data key="node_acronym">DRRE</data><data key="node_domain">Title II / Railroad / Earnings</data><data key="node_description">MCS earnings-computation screen containing railroad service-month entries used to identify career railroad cases.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Source refers to MCS/EC; modeled as an MCS screen without inferring a separate database.</data></node><node id="UI_MCS_DW01"><data key="node_entity_id">UI_MCS_DW01</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Development Worksheet Screen DW01</data><data key="node_acronym">DW01</data><data key="node_domain">Title II / Claims Processing</data><data key="node_description">MCS Development Worksheet screen used to identify assigned WSU and record development remarks or tickles.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Screen-level object; not modeled as a separate backend.</data></node><node id="UI_MCS_DW03"><data key="node_entity_id">UI_MCS_DW03</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS DW03 Screen</data><data key="node_acronym">DW03</data><data key="node_domain">Title II / Claims Processing</data><data key="node_description">MCS screen on which staff annotate field-office code, name, and direct telephone information in the documented WSU workflow.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">4</data><data key="node_notes">POMS identifies DW03 but does not expand the screen code; no expansion is guessed.</data></node><node id="UI_MCS_EARN"><data key="node_entity_id">UI_MCS_EARN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Earnings Screen</data><data key="node_acronym">EARN</data><data key="node_domain">Title II / Earnings</data><data key="node_description">Modernized Claims System earnings screen whose computation-year entries are compared with DEQY to confirm that earnings reached the Master Earnings File.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MCS_ECOR"><data key="node_entity_id">UI_MCS_ECOR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Earnings Correction Screen</data><data key="node_acronym">ECOR</data><data key="node_domain">Title II / Earnings</data><data key="node_description">Modernized Claims System earnings-correction screen whose computation-year entries are compared with DEQY to confirm that earnings reached the Master Earnings File.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MCS_GPOD"><data key="node_entity_id">UI_MCS_GPOD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Government Pension Offset Determination Screen</data><data key="node_acronym">GPOD</data><data key="node_domain">Title II / Historical GPO</data><data key="node_description">Legacy MCS GPOD data propagated through A101 to MACADE when MCS had claim-processing limitations; applies only pre-2024 benefit months.</data><data key="node_observed_status">legacy_pre_2024_processing</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MCS_NHRR"><data key="node_entity_id">UI_MCS_NHRR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Number Holder Railroad Employment Screen</data><data key="node_acronym">NHRR</data><data key="node_domain">Title II / Railroad / Earnings</data><data key="node_description">Modernized Claims System screen #23 containing the number of months a claimant alleges working for the railroad after 1936.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies the screen and business use; field storage is not inferred.</data></node><node id="UI_MCS_NOT2"><data key="node_entity_id">UI_MCS_NOT2</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS NOT2 Screen</data><data key="node_acronym">NOT2</data><data key="node_domain">Representation / Title II</data><data key="node_description">MCS screen that current appointment policy instructs technicians to review as applicable to ensure appointed-representative information is current.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public POMS does not expand the NOT2 mnemonic or identify backing storage.</data></node><node id="UI_MCS_RPOC"><data key="node_entity_id">UI_MCS_RPOC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Report of Contact Screen</data><data key="node_acronym">RPOC</data><data key="node_domain">Title II / Case Documentation</data><data key="node_description">Modernized Claims System Report of Contact screen used to document capability determinations for Title II or concurrent cases not established in eRPS.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS references MS MCS 008.007; implementation technology is not inferred.</data></node><node id="UI_MCS_STUD"><data key="node_entity_id">UI_MCS_STUD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MCS Student Entitlement Screen</data><data key="node_acronym">STUD</data><data key="node_domain">Title II / Student Benefits / MCS</data><data key="node_description">Modernized Claims System screen used to code student entitlement based on expected graduation date, age 19 rules, and the school operating basis certified on SSA-1372.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS cross-references MSOM COMMON 005.029; internal field layout beyond the documented attributes is not inferred.</data></node><node id="UI_MEGAHIT_WEBSITE"><data key="node_entity_id">UI_MEGAHIT_WEBSITE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MEGAHIT Website</data><data key="node_acronym">MEGAHIT website</data><data key="node_domain">Disability / Health IT</data><data key="node_description">Staff-facing website for user-triggered health-information-technology medical evidence requests; hosting and underlying DBMS unidentified.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MNUP_TRANSFER"><data key="node_entity_id">UI_MNUP_TRANSFER</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">MNUP Website TRANSFER Facility</data><data key="node_acronym">TRANSFER</data><data key="node_domain">Title II / Program Integrity / Work Routing</data><data key="node_description">MNUP website facility used to transfer a case to a new servicing field office when appropriate.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Underlying routing implementation is not identified.</data></node><node id="UI_MONET_SMS1"><data key="node_entity_id">UI_MONET_SMS1</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MONET Special Message Data Screen</data><data key="node_acronym">SMS1</data><data key="node_domain">Title II / Post-entitlement</data><data key="node_description">MONET screen used to add Special Message Data to the Master Beneficiary Record.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies the SMS1 screen in MONET.</data></node><node id="UI_MSSICS_ACID"><data key="node_entity_id">UI_MSSICS_ACID</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Claimant Identification Screen</data><data key="node_acronym">ACID</data><data key="node_domain">Title XVI / Person Identity / Claims</data><data key="node_description">MSSICS screen that records identifying information for SSI applications, including place of birth.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly identifies ACID as the MSSICS client identification screen. Physical implementation beyond MSSICS is not inferred.</data></node><node id="UI_MSSICS_ADDR"><data key="node_entity_id">UI_MSSICS_ADDR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Mailing/Payment Address Screen</data><data key="node_acronym">ADDR</data><data key="node_domain">Title XVI / Address / Claims</data><data key="node_description">MSSICS screen referenced by POMS for claimant mailing/payment address.</data><data key="node_observed_status">current_reference_transition_uncertain</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">4</data><data key="node_notes">A 2025-batch POMS page still references ADDR, while September 2026 redetermination policy names the SSI Claims System APID page. The exact transition/equivalence is not inferred.</data></node><node id="UI_MSSICS_DADJ"><data key="node_entity_id">UI_MSSICS_DADJ</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS DADJ Screen</data><data key="node_acronym">DADJ</data><data key="node_domain">Title XVI / Claims / User Interface</data><data key="node_description">MSSICS screen used to enter the initial claim decision during PERC processing.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public POMS names the screen but does not expose physical implementation details.</data></node><node id="UI_MSSICS_DIRS"><data key="node_entity_id">UI_MSSICS_DIRS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS IRS Interface Development</data><data key="node_acronym">DIRS</data><data key="node_domain">Title XVI / IRS Match Development</data><data key="node_description">MSSICS development path used to document and resolve the SSI IRS 5B computer-match diary.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS continues to direct technicians to document full SSI IRS alert development in MSSICS on the DIRS screen. The internal MSOM implementation is not publicly described.</data></node><node id="UI_MSSICS_DPEN"><data key="node_entity_id">UI_MSSICS_DPEN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Pension Interface Development</data><data key="node_acronym">DPEN</data><data key="node_domain">Title XVI / IRS Match / Work Control</data><data key="node_description">MSSICS development screen identified by POMS for documenting development of the SSI Pension Interface 5H diary.</data><data key="node_observed_status">current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS page remains active and was batch-run in 2025, although the underlying MSOM implementation date is older. Backend technology is not public.</data></node><node id="UI_MSSICS_DSAB"><data key="node_entity_id">UI_MSSICS_DSAB</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Savings Bond Interface Development Screen</data><data key="node_acronym">DSAB</data><data key="node_domain">Title XVI / Resources / User Interface</data><data key="node_description">MSSICS screen used to document savings-security ownership verification and clear Savings Security Instrument Match diaries.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS cites MS 04422.015 Savings Bond Interface Development (DSAB). No underlying service or database boundary is inferred.</data></node><node id="UI_MSSICS_DSSR"><data key="node_entity_id">UI_MSSICS_DSSR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS DSSR Screen</data><data key="node_acronym">DSSR</data><data key="node_domain">Title XVI / Claims / User Interface</data><data key="node_description">MSSICS screen used in PERC processing to close the open event after review actions are recorded.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Public POMS names the screen but does not expand the acronym or expose physical implementation details.</data></node><node id="UI_MSSICS_DUEM"><data key="node_entity_id">UI_MSSICS_DUEM</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Unemployment Compensation Match Development Screen</data><data key="node_acronym">DUEM</data><data key="node_domain">Title XVI / User Interface</data><data key="node_description">MSSICS screen used to clear U5 unemployment-compensation match diaries after required development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS names DUEM but public policy does not expose its backing table or service implementation.</data></node><node id="UI_MSSICS_DWO1"><data key="node_entity_id">UI_MSSICS_DWO1</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS DWO1 Development Referral</data><data key="node_acronym">DWO1</data><data key="node_domain">Title XVI / Work Control / Address</data><data key="node_description">MSSICS referral control used to send a moved SSI case to the new field office when living-arrangement or other development remains outstanding.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-08-07</data><data key="node_confidence">4</data><data key="node_notes">Current POMS spells the control DWO1 in one passage and DWOI in another; treated as one logical referral control pending MSOM confirmation.</data></node><node id="UI_MSSICS_DXIX"><data key="node_entity_id">UI_MSSICS_DXIX</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Title XIX Facility Interface Development Screen</data><data key="node_acronym">DXIX</data><data key="node_domain">Title XVI / User Interface</data><data key="node_description">MSSICS interface-development screen used to clear D8 Title XIX facility-match diaries and build the resulting transaction to SSR.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly ties DXIX to D8 clearance.</data></node><node id="UI_MSSICS_ISEI"><data key="node_entity_id">UI_MSSICS_ISEI</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Self-Employment Income Screen</data><data key="node_acronym">iSEI</data><data key="node_domain">Title XVI / Work Incentives</data><data key="node_description">MSSICS screen used to post net earnings from self-employment for approved PASS cases.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MSSICS_MULTI_SSN"><data key="node_entity_id">UI_MSSICS_MULTI_SSN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Multiple SSNs Page</data><data key="node_acronym">Multiple SSNs</data><data key="node_domain">Title XVI / Person Identity / Claims</data><data key="node_description">MSSICS page that collects other names and Social Security numbers used by an applicant for Numident verification.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says the page collects other names/SSNs for Numident verification; it does not establish a separate person master repository.</data></node><node id="UI_MSSICS_PERC"><data key="node_entity_id">UI_MSSICS_PERC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Preeffectuation Review Contact Page</data><data key="node_acronym">PERC Page</data><data key="node_domain">Title XVI / Claims / User Interface</data><data key="node_description">MSSICS page used to record PERC processing, including limited PERC handling and PERC date generation.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">POMS directs MSSICS users to select WITH EXCLUSION on the Preeffectuation Review Contact page for qualifying limited PERCs.</data></node><node id="UI_MSSICS_RFIA"><data key="node_entity_id">UI_MSSICS_RFIA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS Resource Financial Institution Account Screen</data><data key="node_acronym">RFIA</data><data key="node_domain">Title XVI / Work Incentives</data><data key="node_description">MSSICS screen used to exclude PASS/business accounts as resources for approved PASS cases.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_MSSICS_UATH"><data key="node_entity_id">UI_MSSICS_UATH</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS UATH Screen</data><data key="node_acronym">UATH</data><data key="node_domain">Representation / Title XVI</data><data key="node_description">MSSICS screen that current appointment policy instructs technicians to review as applicable for current appointed-representative information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Mnemonic expansion and backing store are not stated in the public source.</data></node><node id="UI_MSSICS_UFEE"><data key="node_entity_id">UI_MSSICS_UFEE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">MSSICS UFEE Screen</data><data key="node_acronym">UFEE</data><data key="node_domain">Representation / Title XVI</data><data key="node_description">MSSICS screen that current appointment policy instructs technicians to review as applicable for current appointed-representative information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Mnemonic expansion and backing store are not stated in the public source.</data></node><node id="UI_NAT_SSI_ALERT"><data key="node_entity_id">UI_NAT_SSI_ALERT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">National SSI Alert System Page</data><data key="node_domain">Title XVI / Program Integrity</data><data key="node_description">SSA page used by field offices to obtain replacement SSI wage alerts.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Current POMS references this page but public documentation does not expose its platform or hosting architecture.</data></node><node id="UI_NDDSS_DDSM"><data key="node_entity_id">UI_NDDSS_DDSM</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">NDDSS Master File Menu</data><data key="node_acronym">DDSM</data><data key="node_domain">DDS Disability Processing</data><data key="node_description">National Disability Determination Services System master-file menu referenced by current FO/DDS coordination policy.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_NED_NEDA"><data key="node_entity_id">UI_NED_NEDA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">NED Address Screen</data><data key="node_acronym">NEDA</data><data key="node_domain">Debt &amp; Overpayments / Address Provenance</data><data key="node_description">NED screen through which a non-entitled debtor domestic address and phone number can be directly changed in the NED database.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2017-10-31</data><data key="node_confidence">5</data><data key="node_notes">Current-live POMS within the ten-year horizon. Public policy does not expose implementation technology.</data></node><node id="UI_PDP_PENDING_WAGE"><data key="node_entity_id">UI_PDP_PENDING_WAGE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PDP Pending Wage Page</data><data key="node_acronym">PDP Pending Wage</data><data key="node_domain">Title XVI / Claims / Earnings</data><data key="node_description">SSI Claims/CCE page displaying PDP wage/employment information that could not match an existing Wages page and requires technician disposition.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Associated with the EE diary; technician can update an existing employer, add a new employer, or reject the information after development.</data></node><node id="UI_PDP_PENDING_WAGE_REPORT"><data key="node_entity_id">UI_PDP_PENDING_WAGE_REPORT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PDP Pending Wage Report Page</data><data key="node_acronym">PDP Pending Wage Report</data><data key="node_domain">Title XVI / Claims / Earnings</data><data key="node_description">SSI Claims/CCE page displaying matched PDP wage information that still requires manual processing before posting, such as force-due or manual-deeming cases.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Wages on this page have not been applied to the SSR until technician action is completed.</data></node><node id="UI_PEPP"><data key="node_entity_id">UI_PEPP</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Provisional Payment Screen</data><data key="node_acronym">PEPP</data><data key="node_domain">Title II / Expedited Reinstatement</data><data key="node_description">Title II Postentitlement Online System screen used to begin eligible expedited-reinstatement provisional benefits.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly identifies the PEPP screen within POS.</data></node><node id="UI_PESP_STOP_PAYMENT"><data key="node_entity_id">UI_PESP_STOP_PAYMENT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Stop Payment Request Input Screen</data><data key="node_acronym">PESP</data><data key="node_domain">Title II / Payments / Stop Payment</data><data key="node_description">RSDHI stop-payment input screen used by a Program Service Center to enter a manual F-stop request.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS identifies PESP as an RSDHI input screen. The Atlas does not infer a separate PESP database or the physical RSDHI implementation.</data></node><node id="UI_PI_CITIZENSHIP_INFO"><data key="node_entity_id">UI_PI_CITIZENSHIP_INFO</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Person Information Citizenship Information</data><data key="node_domain">Identity / Person Information</data><data key="node_description">Person Information detail screen used in CCE to capture U.S. citizenship status and proof information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS GN 00301.286 references MS 08401.007.</data></node><node id="UI_PI_CONTACT"><data key="node_entity_id">UI_PI_CONTACT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Person Information Contact Information</data><data key="node_domain">Person / Contact</data><data key="node_description">Person Information contact-information screen referenced by current address-change policy.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS GN 02605.035 references MS 08401.005.</data></node><node id="UI_PI_DISCREPANCY"><data key="node_entity_id">UI_PI_DISCREPANCY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Person Information Record with Discrepancies</data><data key="node_domain">Person / Data Quality</data><data key="node_description">Person Information discrepancy-resolution screen referenced in retained Title II citizenship instructions.</data><data key="node_observed_status">recent_policy_reference_retention_expired</data><data key="node_observed_as_of">2026-09-27</data><data key="node_confidence">5</data><data key="node_notes">EM-21045 REV referenced MS 08401.004 through its 2026-09-27 retention date. The screen remains historically/recently evidenced, but Run 52 does not claim a current post-retention UI state.</data></node><node id="UI_PI_IDENTITY_INFO"><data key="node_entity_id">UI_PI_IDENTITY_INFO</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Person Information Identity Information</data><data key="node_domain">Identity / Person Information</data><data key="node_description">Person Information detail screen used in CCE to capture identity evidence such as birthplace and birthdate proof information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS GN 00301.286 references MS 08401.006.</data></node><node id="UI_PI_MARRIAGE"><data key="node_entity_id">UI_PI_MARRIAGE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Person Information Marriage Information Details</data><data key="node_domain">Person / Relationships</data><data key="node_description">Person Information marriage-information details screen referenced by current SSI marital-status policy.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS SI 00604.018 references MS 08401.008.</data></node><node id="UI_PI_ON_RECORD"><data key="node_entity_id">UI_PI_ON_RECORD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Person Information on Record</data><data key="node_domain">Identity / Person Information</data><data key="node_description">Person Information page used in CCE evidence documentation and displaying person information including death source-of-notification information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS GN 00301.286 references MS 08401.003. Public evidence establishes the logical screen/page but not its implementation technology.</data></node><node id="UI_POS_CLCZ"><data key="node_entity_id">UI_POS_CLCZ</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Citizenship U.S. and/or Foreign Screen</data><data key="node_acronym">CLCZ</data><data key="node_domain">Title II / Post-Entitlement / Person Identity</data><data key="node_description">POS-path screen that may appear during a foreign-to-domestic change of address when MBR citizenship information is missing or incomplete.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">POMS cross-references MSOM COMMON 005.010; no database technology inferred.</data></node><node id="UI_POS_CLLP"><data key="node_entity_id">UI_POS_CLLP</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Lawful Presence Screen</data><data key="node_acronym">CLLP</data><data key="node_domain">Title II / Post-Entitlement / Person Identity</data><data key="node_description">POS-path screen that may appear during a foreign-to-domestic change of address when lawful-presence information is missing or incomplete.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">POMS cross-references MSOM COMMON 005.011; no database technology inferred.</data></node><node id="UI_POS_LEUS"><data key="node_entity_id">UI_POS_LEUS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">POS Left U.S./Outside of U.S. Screen</data><data key="node_acronym">LEUS</data><data key="node_domain">Title II / International / Residence</data><data key="node_description">POS-path screen used to annotate the date a beneficiary left the United States in applicable domestic-to-foreign address cases.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_POS_NUSC"><data key="node_entity_id">UI_POS_NUSC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">POS Non-U.S. Citizen Coding Screen</data><data key="node_acronym">NUSC</data><data key="node_domain">Title II / International / Citizenship</data><data key="node_description">POS-path screen used in domestic-to-foreign change-of-address processing for non-U.S.-citizen coding when applicable.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_POS_PEAD"><data key="node_entity_id">UI_POS_PEAD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">POS Address/Direct Deposit/Phone Screen</data><data key="node_acronym">PEAD</data><data key="node_domain">Title II / Post-Entitlement / Address</data><data key="node_description">Post Entitlement System screen used for current post-entitlement address, direct-deposit, and telephone changes.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current foreign-address POMS explicitly directs PEAD for current post-entitlement changes.</data></node><node id="UI_POS_PEAF"><data key="node_entity_id">UI_POS_PEAF</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Future POS Address/Direct Deposit/Phone Screen</data><data key="node_acronym">PEAF</data><data key="node_domain">Title II / Post-Entitlement / Address</data><data key="node_description">Post Entitlement System screen used to enter future address, direct-deposit, and telephone changes up to three months in advance.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_POS_PELF"><data key="node_entity_id">UI_POS_PELF</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">POS Alien Tax Update Screen</data><data key="node_acronym">PELF</data><data key="node_domain">Title II / International / Tax</data><data key="node_description">POS-path screen used in domestic-to-foreign change-of-address processing to collect alien-tax information when applicable.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Screen appearance is conditional; no separate backend store inferred.</data></node><node id="UI_PUPS_IPID"><data key="node_entity_id">UI_PUPS_IPID</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS Incentive Payment Identification Data Screen</data><data key="node_acronym">IPID</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">PUPS screen maintained with a facility incentive-payment address and contact information; updates are requested through Field Operations prisoner coordination.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_PUPS_P2QY"><data key="node_entity_id">UI_PUPS_P2QY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS Title II Prisoner Status Query</data><data key="node_acronym">P2QY</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">PUPS Title II status query used to determine whether an incentive payment was made for a prisoner report and to obtain facility identifiers.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_PUPS_QIPA"><data key="node_entity_id">UI_PUPS_QIPA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS QIPA Incentive Payment Screen</data><data key="node_acronym">QIPA</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">PUPS screen used with institutional incentive-payment records when answering SSA-L4020 inquiries.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">4</data><data key="node_notes">POMS names the screen but does not expand QIPA.</data></node><node id="UI_PUPS_QIPD"><data key="node_entity_id">UI_PUPS_QIPD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS QIPD Incentive Payment Screen</data><data key="node_acronym">QIPD</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">PUPS screen used with institutional incentive-payment records when answering SSA-L4020 inquiries.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">4</data><data key="node_notes">POMS names the screen but does not expand QIPD.</data></node><node id="UI_PUPS_T16QY"><data key="node_entity_id">UI_PUPS_T16QY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">PUPS Title XVI Prisoner Status Query</data><data key="node_acronym">T6QY / P6QY</data><data key="node_domain">Program Integrity / Prisoner</data><data key="node_description">PUPS Title XVI status query used in incentive-payment recovery. Current POMS uses both T6QY and P6QY labels in the same section.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-04-14</data><data key="node_confidence">4</data><data key="node_notes">Preserve the source naming inconsistency; do not infer two physical screens without additional evidence.</data></node><node id="UI_R105_ISNO_ACCOM"><data key="node_entity_id">UI_R105_ISNO_ACCOM</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">iSNO Additional Accommodation Information Screen</data><data key="node_domain">Notices &amp; Customer Service</data><data key="node_description">Collects accessible-format accommodation details including mailing address, telephone number, asserted impairment and explanation of alternative formats.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_R105_ISNO_AUTH"><data key="node_entity_id">UI_R105_ISNO_AUTH</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">iSNO Authenticate a Client Screen</data><data key="node_domain">Person &amp; Identity</data><data key="node_description">Intranet Special Notice Option entry uses SSN, birth date and name for cross-record match and lists explicit error conditions, including an existing death indicator.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_R105_ISNO_SELECT"><data key="node_entity_id">UI_R105_ISNO_SELECT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">iSNO Select Option Screen</data><data key="node_domain">Notices &amp; Customer Service</data><data key="node_description">Select Option presents current special-notice communication choice, follow-up telephone, client history and optional confirmation email.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_R105_QRCPS_GENERAL"><data key="node_entity_id">UI_R105_QRCPS_GENERAL</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">QRCPS General Referral Section</data><data key="node_domain">Disability &amp; Quality Review</data><data key="node_description">Quality reviewers may initiate a MAQR Review referral within QRCPS General Referral; managers resolve or route to medical/psychological consultants.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_RASR_ROC"><data key="node_entity_id">UI_RASR_ROC</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">RASR Report of Contact Screen</data><data key="node_acronym">RASR ROC</data><data key="node_domain">Representation / Case Documentation</data><data key="node_description">Report-of-Contact screen within RASR used to document claimant representation intent and representative withdrawal information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly directs technicians to annotate a ROC screen in RASR.</data></node><node id="UI_SAVE_RESPONSE"><data key="node_entity_id">UI_SAVE_RESPONSE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSA SAVE Query Response Screen</data><data key="node_acronym">SAVE Screen</data><data key="node_domain">Identity / Immigration Verification</data><data key="node_description">SSA screen on which selected DHS SAVE response attributes are propagated for claims lawful-presence verification.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Screen-level object only; no separate backend or persistence layer is inferred.</data></node><node id="UI_SHARED_PROCESS_MENU"><data key="node_entity_id">UI_SHARED_PROCESS_MENU</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Shared Process Menu</data><data key="node_domain">Enterprise Operations / Shared Processes</data><data key="node_description">SSA shared menu used in current POMS to access the client database and administrative-sanctions screen.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_SPAS"><data key="node_entity_id">UI_SPAS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Administrative Sanctions Screen</data><data key="node_acronym">SPAS</data><data key="node_domain">Program Integrity / Administrative Sanctions</data><data key="node_description">Screen used to collect information about imposed or deferred administrative sanctions.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_SSIRD"><data key="node_entity_id">UI_SSIRD</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Supplemental Security Income Record Display</data><data key="node_acronym">SSIRD</data><data key="node_domain">Title XVI / Special Veterans Benefits</data><data key="node_description">Display in which the SVB indicator appears in the Case Header segment.</data><data key="node_observed_status">current_poms_retained_detailed_topology_old</data><data key="node_observed_as_of">2026-04-13</data><data key="node_confidence">4</data><data key="node_notes" /></node><node id="UI_SSI_ABLE_ACCOUNT"><data key="node_entity_id">UI_SSI_ABLE_ACCOUNT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System ABLE Account Page</data><data key="node_acronym">ABLE Account Page</data><data key="node_domain">Title XVI / Resources / User Interface</data><data key="node_description">SSI Claims System page used to record ABLE program State, account number, open/close dates, signature authority, and account-balance information.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS calls this the Achieving a Better Life Experience Account page.</data></node><node id="UI_SSI_ABLE_PENDING"><data key="node_entity_id">UI_SSI_ABLE_PENDING</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Pending ABLE Account Page</data><data key="node_acronym">Pending ABLE Page</data><data key="node_domain">Title XVI / Resources / Work Control</data><data key="node_description">SSI Claims System page that displays new State-reported ABLE account information and supports update/add/reject/decide-later resolution when data do not match an existing account.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">A pending decision must be resolved before closing an initial claim, redetermination, or appeal event.</data></node><node id="UI_SSI_ALIEN_STATUS"><data key="node_entity_id">UI_SSI_ALIEN_STATUS</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Alien Status Page</data><data key="node_acronym">Alien Status</data><data key="node_domain">Title XVI / Identity / Immigration</data><data key="node_description">SSI claim page used to document U.S. admission date, alien status code, and whether alien status was verified; referenced in current MSSICS and CCE SSI policy.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Logical page reference across evolving SSI claims terminology; exact physical application boundary is unresolved.</data></node><node id="UI_SSI_APID"><data key="node_entity_id">UI_SSI_APID</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Personal Information Page</data><data key="node_acronym">APID</data><data key="node_domain">Title XVI / Address / Claims</data><data key="node_description">Current SSI Claims System page under General ID used to document mailing address during redetermination processing.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UI_SSI_DORW"><data key="node_entity_id">UI_SSI_DORW</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Over Reported Wage Development Page</data><data key="node_acronym">DORW</data><data key="node_domain">Title XVI / User Interface</data><data key="node_description">SSI Claims page used to resolve S7 overreported-wage discrepancies before building a transaction to SSR.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS names the DORW page in S7 clearance instructions.</data></node><node id="UI_SSI_FI_ACCOUNT"><data key="node_entity_id">UI_SSI_FI_ACCOUNT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Financial Institution Account Page</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">Claims page used to document financial institution accounts, balances, excluded amounts, exclusion reasons, and related file notes.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS also describes this page in CCE; Atlas preserves both logical SSI Claims System and CCE references without assuming implementation identity.</data></node><node id="UI_SSI_FI_PERMISSION"><data key="node_entity_id">UI_SSI_FI_PERMISSION</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Financial Institutions Permission Page</data><data key="node_domain">Title XVI / Financial Verification</data><data key="node_description">SSI Claims System page where SSA records permission to request financial-account balance information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies MS 08108.020; no underlying storage technology is inferred.</data></node><node id="UI_SSI_HOME_RENT"><data key="node_entity_id">UI_SSI_HOME_RENT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Home Ownership and Rental Liability Page</data><data key="node_domain">Title XVI / Living Arrangements</data><data key="node_description">SSI Claims System page on which current rental-subsidy edits evaluate the rental subsidy amount.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current E2 diary policy names the Home Ownership and Rental Liability page; implementation technology is not public.</data></node><node id="UI_SSI_LRES"><data key="node_entity_id">UI_SSI_LRES</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Residence Address and Jurisdiction Page</data><data key="node_acronym">LRES</data><data key="node_domain">Title XVI / Address / Claims</data><data key="node_description">Current SSI Claims System page under Living Arrangements used to document residence address and jurisdiction information.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-09-17</data><data key="node_confidence">5</data><data key="node_notes">Residence information supports State supplementation and categorical Medicaid determinations.</data></node><node id="UI_SSI_OTHER_RESOURCE"><data key="node_entity_id">UI_SSI_OTHER_RESOURCE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Other Resource Page</data><data key="node_acronym">Other Resource Page</data><data key="node_domain">Title XVI / Resources / User Interface</data><data key="node_description">SSI Claims System resource page used, among other purposes, to record ABLE prepaid debit cards and excluded amounts.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-06</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly identifies this page for ABLE prepaid debit-card handling.</data></node><node id="UI_SSI_OTHER_RESOURCES"><data key="node_entity_id">UI_SSI_OTHER_RESOURCES</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Other Resources Page</data><data key="node_acronym">Other Resources</data><data key="node_domain">Title XVI / Claims / Resources</data><data key="node_description">Claims-system page used to record Trump Accounts and other resource types, including custodian, financial institution, account number if known, and alleged/excluded value.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-07-09</data><data key="node_confidence">5</data><data key="node_notes">Public policy does not establish the physical screen implementation boundary between CCE/MSSICS generations.</data></node><node id="UI_SSI_PERSON_STATEMENT"><data key="node_entity_id">UI_SSI_PERSON_STATEMENT</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Person Statement Screen</data><data key="node_domain">Title XVI / Evidence</data><data key="node_description">SSI Claims System screen used to document a claimant or recipient's signed statement when other financial-account evidence is unavailable.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly names the Person Statement screen; UI technology is not public.</data></node><node id="UI_SSI_STATE_LOCAL_TRIBAL"><data key="node_entity_id">UI_SSI_STATE_LOCAL_TRIBAL</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Other State, Local, or Tribal Assistance Page</data><data key="node_domain">Title XVI / Income</data><data key="node_description">SSI Claims System page used to document State, local, or tribal assistance, including State-administered supplemental payments.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies MS 08114.019; no database or service implementation is disclosed.</data></node><node id="UI_SSI_UDIA"><data key="node_entity_id">UI_SSI_UDIA</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims System Update Diaries Screen</data><data key="node_acronym">UDIA</data><data key="node_domain">Title XVI / Post-Eligibility</data><data key="node_description">Direct SSR Update screen used to clear diaries, including E2 when development cannot be completed under current procedure.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Logical UI from POMS/MSOM reference; implementation technology is not public.</data></node><node id="UI_SSI_UMEN"><data key="node_entity_id">UI_SSI_UMEN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Direct SSR Update Menu</data><data key="node_acronym">UMEN</data><data key="node_domain">Title XVI / Post-Eligibility</data><data key="node_description">Direct SSR Update menu from which staff select Diaries before using the Update Diaries screen.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-07-09</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a menu surface within Direct SSR Update; backing implementation not inferred.</data></node><node id="UI_SSI_UOUP"><data key="node_entity_id">UI_SSI_UOUP</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Underpayment Processing Screen</data><data key="node_acronym">UOUP</data><data key="node_domain">Title XVI / Underpayments</data><data key="node_description">Direct SSR Update screen used for underpayment prepayment review and release actions in specified SSI cases.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS identifies UOUP as a Direct SSR Update screen; physical screen persistence is not inferred.</data></node><node id="UI_SSI_UPER"><data key="node_entity_id">UI_SSI_UPER</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Early Missing Check Report Screen</data><data key="node_acronym">UPER</data><data key="node_domain">Title XVI / Payments / Nonreceipt</data><data key="node_description">Title XVI screen used by field offices or teleservice centers for specified operational mass-loss nonreceipt inputs when SSAlerts directs action; available on check-delivery day and the following day.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS warns not to use UPER for ordinary delay-in-delivery situations.</data></node><node id="UI_SSI_UPMR"><data key="node_entity_id">UI_SSI_UPMR</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Missing Recurring or Supplemental Check Screen</data><data key="node_acronym">UPMR</data><data key="node_domain">Title XVI / Payments</data><data key="node_description">SSI screen that examines/display-checks payment-history information and presents possible double-check-negotiation alerts for missing payments.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2025-01-27</data><data key="node_confidence">5</data><data key="node_notes">Current POMS names UPMR and describes B-stop/C-stop processing and second-PIN controls.</data></node><node id="UI_SSI_WAGES_PAGE"><data key="node_entity_id">UI_SSI_WAGES_PAGE</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSI Claims Wages Page</data><data key="node_acronym">Wages Page</data><data key="node_domain">Title XVI / Claims / Earnings</data><data key="node_description">SSI Claims system page containing employer/EIN and wage information used by PIE matching and SSI wage processing.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">A matching EIN permits PIE wage information to update the Wages page automatically; qualifying wages are then submitted to SSR.</data></node><node id="UI_SSNAP_ADDITIONAL_INFO"><data key="node_entity_id">UI_SSNAP_ADDITIONAL_INFO</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSNAP Additional Info Screen</data><data key="node_acronym">Additional Info</data><data key="node_domain">Identity &amp; Enumeration / SSNAP</data><data key="node_description">SSNAP screen that displays the replacement-card count and provides card-suppression controls for Numident updates where a replacement SSN card is not needed.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS establishes the screen and functions; no physical UI technology is inferred.</data></node><node id="UI_SSNAP_PROOF_LEGAL_ALIEN"><data key="node_entity_id">UI_SSNAP_PROOF_LEGAL_ALIEN</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSNAP Proof of Legal Alien Status Screen</data><data key="node_acronym">Proof of Legal Alien Status</data><data key="node_domain">Identity &amp; Enumeration / Immigration</data><data key="node_description">SSNAP screen used in specified nonwork SSN processing to record the nonwork reason and supporting alien-status evidence.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS names the screen; physical storage implementation is not inferred.</data></node><node id="UI_SSNAP_SUMMARY"><data key="node_entity_id">UI_SSNAP_SUMMARY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSNAP Summary Screen</data><data key="node_acronym">Summary</data><data key="node_domain">Identity &amp; Enumeration / SSNAP</data><data key="node_description">SSNAP summary screen whose Remarks field is used to list evidence documents supporting Numident changes when those documents were not otherwise captured in SSNAP.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Logical screen documented by current POMS; backing persistence is not inferred.</data></node><node id="UI_SSR_UOWV"><data key="node_entity_id">UI_SSR_UOWV</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">Waiver Decision</data><data key="node_acronym">UOWV</data><data key="node_domain">Title XVI / Debt Management</data><data key="node_description">Direct Supplemental Security Record update screen used to input Title XVI waiver dismissal/decision actions.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly names UOWV and Direct SSR Update.</data></node><node id="UI_SUMS_MCAS_SSN_IRS_SSID_QUERY"><data key="node_entity_id">UI_SUMS_MCAS_SSN_IRS_SSID_QUERY</data><data key="node_entity_type">user_interface</data><data key="node_canonical_name">SSN/IRS/SSID Query Screen</data><data key="node_domain">Title XVI / Management Information</data><data key="node_description">SUMS/MCAS MI Central query screen used to retrieve alert data by SSN/IRS/SSID within RZ/LI workload listings.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS explicitly names the screen; no implementation technology is disclosed.</data></node><node id="USECASE_TEFCA_GBD"><data key="node_entity_id">USECASE_TEFCA_GBD</data><data key="node_entity_type">exchange_use_case</data><data key="node_canonical_name">TEFCA Government Benefits Determination Use Case</data><data key="node_domain">Disability / Health Information Exchange</data><data key="node_description">TEFCA Government Benefits Determination use case identified by SSA for disability evidence exchange through its selected eHealth Exchange QHIN.</data><data key="node_observed_status">testing_phase_documented</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">SSA announced February 2026 testing and expected spring production; no later first-party source reviewed in this run proves the exact production go-live date.</data></node><node id="UTIL_EDCS_COPY_FROM_PRIOR"><data key="node_entity_id">UTIL_EDCS_COPY_FROM_PRIOR</data><data key="node_entity_type">workflow_feature</data><data key="node_canonical_name">EDCS Copy from Prior Utility</data><data key="node_acronym">Copy from Prior</data><data key="node_domain">Disability / EDCS</data><data key="node_description">EDCS feature that can copy selected details from the most recent closed electronic folder into a subsequent initial EDCS case, subject to review and update.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-03-17</data><data key="node_confidence">5</data><data key="node_notes">Current source does not identify a separate persistence layer for the copy operation.</data></node><node id="UTIL_EDCS_UAT"><data key="node_entity_id">UTIL_EDCS_UAT</data><data key="node_entity_type">utility</data><data key="node_canonical_name">Update-After-Transfer Utility</data><data key="node_acronym">UAT</data><data key="node_domain">Disability / Integration</data><data key="node_description">EDCS utility used after jurisdiction transfer to propagate selected MCS, MSSICS or CCE changes, add SSA-5002 information to the CEF, and add certain claims.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-09-01</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 EDCS TOC retains UAT. POMS TN 67 (12-23) documents the detailed functions; no transport protocol or middleware is inferred.</data></node><node id="UTIL_ESVC_CONTROL_TRACK"><data key="node_entity_id">UTIL_ESVC_CONTROL_TRACK</data><data key="node_entity_type">utility</data><data key="node_canonical_name">eServices Control And Tracking</data><data key="node_domain">Enterprise Integration / eServices</data><data key="node_description">SSA utility that assigns and maintains confirmation numbers used to track information-exchange artifacts.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes">Federal Data Catalog identifier US-GOV-SSA-128.</data></node><node id="UTIL_GUNPUC03"><data key="node_entity_id">UTIL_GUNPUC03</data><data key="node_entity_type">utility</data><data key="node_canonical_name">GUNPUC03</data><data key="node_domain">Identity Verification</data><data key="node_description">General utility used by online SSA applications to retrieve selected Numident data.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UTIL_GUNSCHIP"><data key="node_entity_id">UTIL_GUNSCHIP</data><data key="node_entity_type">utility</data><data key="node_canonical_name">GUNSCHIP</data><data key="node_domain">Identity Verification</data><data key="node_description">General utility used by online SSA applications to retrieve selected Numident data.</data><data key="node_observed_status">current_open_data_inventory</data><data key="node_observed_as_of">2026-09-29</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="UTIL_REMITTANCE_ID"><data key="node_entity_id">UTIL_REMITTANCE_ID</data><data key="node_entity_type">utility</data><data key="node_canonical_name">Remittance ID Generator Utility</data><data key="node_domain">Debt &amp; Remittances</data><data key="node_description">SSA utility that generates the alphanumeric Remittance ID included in electronic-repayment notice language.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-03-30</data><data key="node_confidence">5</data><data key="node_notes">POMS gives generated format ABC12CD34EF.</data></node><node id="VEH_GSA_EIS"><data key="node_entity_id">VEH_GSA_EIS</data><data key="node_entity_type">contract_vehicle</data><data key="node_canonical_name">GSA Enterprise Infrastructure Solutions</data><data key="node_acronym">EIS</data><data key="node_domain">Procurement / Telecommunications</data><data key="node_description">GSA multiple-award IDIQ contract vehicle for next-generation IT, telecommunications, and infrastructure services.</data><data key="node_observed_status">documented_current_2025</data><data key="node_observed_as_of">2025-06-30</data><data key="node_confidence">5</data><data key="node_notes">GAO identifies EIS as the vehicle for SSA's Grand SLLAM task order.</data></node><node id="VEH_ITSSC_2026"><data key="node_entity_id">VEH_ITSSC_2026</data><data key="node_entity_type">contract_vehicle</data><data key="node_canonical_name">IT Support Services Contract Recompete</data><data key="node_acronym">ITSSC</data><data key="node_domain">Procurement / Enterprise IT</data><data key="node_description">SSA solicitation to establish a multiple-award IDIQ for IT support services under Notice 28321326R00000022.</data><data key="node_observed_status">solicitation_open</data><data key="node_observed_as_of">2026-10-03</data><data key="node_confidence">5</data><data key="node_notes">Published September 23, 2026; offers due October 12, 2026 at 10:00 AM EDT. No awardees or contract value are modeled because the solicitation remains pre-award.</data></node><node id="WF_A101"><data key="node_entity_id">WF_A101</data><data key="node_entity_type">transaction_method</data><data key="node_canonical_name">A101</data><data key="node_acronym">A101</data><data key="node_domain">Title II / Claims</data><data key="node_description">MCS award transaction method used for certain Title II allowances that cannot process through Earnings Computation.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-04-20</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a transaction method, not a standalone application.</data></node><node id="WF_EF101"><data key="node_entity_id">WF_EF101</data><data key="node_entity_type">transaction_method</data><data key="node_canonical_name">Electronic Form 101</data><data key="node_acronym">EF101</data><data key="node_domain">Title II / Claims</data><data key="node_description">Electronic Form 101 transaction method used for certain Title II allowances that cannot process through Earnings Computation.</data><data key="node_observed_status">observed_active</data><data key="node_observed_as_of">2026-04-20</data><data key="node_confidence">5</data><data key="node_notes">Modeled as a transaction method, not a standalone application.</data></node><node id="WORK_DATS_DEATH_DEV_45D"><data key="node_entity_id">WORK_DATS_DEATH_DEV_45D</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DATS Death Development 45-Day Diary</data><data key="node_acronym">45-Day Diary</data><data key="node_domain">Program Integrity / Death / Work Control</data><data key="node_description">Forty-five-day follow-up control established after SSA sends SSA-2708 during unresolved death development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public POMS does not disclose the physical diary store or implementation.</data></node><node id="WORK_DDSDEC"><data key="node_entity_id">WORK_DDSDEC</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">DDSDEC Development Issue</data><data key="node_acronym">DDSDEC</data><data key="node_domain">Disability / Railroad / Work Control</data><data key="node_description">Development issue established on MCS and CCE development worksheets for railroad disability cases routed to Disability Case Review, with a 90-day tickle.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Public policy does not disclose physical database technology or persistence beyond the documented system/work-control references.</data></node><node id="WORK_EBE_INVESTIGATE"><data key="node_entity_id">WORK_EBE_INVESTIGATE</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EBE Investigate Pending Status</data><data key="node_acronym">Investigate</data><data key="node_domain">Identity &amp; Enumeration / EBE / Work Control</data><data key="node_description">Pending SSNAP status for an Enumeration Beyond Entry application that generated Enumeration Feedback Message 3 and is listed on the Enumeration MI listing.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says unprocessed EBE applications in this status can remain pending for 365 days unless the applicant supplies required evidence.</data></node><node id="WORK_EBE_NOT_COMPLETED"><data key="node_entity_id">WORK_EBE_NOT_COMPLETED</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">EBE Not Completed Pending Status</data><data key="node_acronym">Not Completed</data><data key="node_domain">Identity &amp; Enumeration / EBE / Work Control</data><data key="node_description">Pending SSNAP status for an Enumeration Beyond Entry application containing errors or missing required information.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Current POMS says unprocessed EBE applications in this status can remain pending for 365 days unless the applicant supplies required evidence.</data></node><node id="WORK_ECO_AWG_RETURN_TX"><data key="node_entity_id">WORK_ECO_AWG_RETURN_TX</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">ECO AWG Returned-Mail Transactions</data><data key="node_acronym">7001/7005</data><data key="node_domain">Debt &amp; External Collections / AWG</data><data key="node_description">Undeliverable-employer-mail transaction controls posted to ECO after centralized scanning: 7001 for returned AWG Employer Packages and 7005 for specified returned garnishment notices.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2022-08-22</data><data key="node_confidence">5</data><data key="node_notes">Transaction codes are work-control records, not separate address masters.</data></node><node id="WORK_ELAS_UNVER"><data key="node_entity_id">WORK_ELAS_UNVER</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eLAS Unverified Data Issue</data><data key="node_acronym">UNVER</data><data key="node_domain">Customer Service / Identity Verification</data><data key="node_description">eLAS worksheet issue identifying iAppointment data as unverified until staff verifies/corrects it and receipts the issue.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-06-26</data><data key="node_confidence">5</data><data key="node_notes">Logical work-control object; no physical queue or table is inferred.</data></node><node id="WORK_ELAS_VAPT_ALERT"><data key="node_entity_id">WORK_ELAS_VAPT_ALERT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eLAS VAPT Time-Sensitive Case Alert</data><data key="node_acronym">VAPT eLAS Alert</data><data key="node_domain">Disability / Work Control</data><data key="node_description">Time-sensitive eLAS alert directing staff to schedule an appointment within three business days for matched VAPT claimants.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Generated when a claimant SSN matches PERSON/ICDB VAPT information.</data></node><node id="WORK_ERPS_CRTOR"><data key="node_entity_id">WORK_ERPS_CRTOR</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eRPS CRTOR Court Order Diary</data><data key="node_acronym">CRTOR</data><data key="node_domain">Representative Payee / Legal Evidence</data><data key="node_description">Ten-calendar-day eRPS diary/work control used to follow up for a required court order after incapability is established with convincing evidence.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data></node><node id="WORK_ERPS_MASS_15_DAY"><data key="node_entity_id">WORK_ERPS_MASS_15_DAY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Organizational Payee Change 15-Day Due-Process Diary</data><data key="node_domain">Representative Payee / Organizations</data><data key="node_description">15-day control before mass payee change, with exceptions when an informed beneficiary agrees earlier.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="WORK_ERPS_QUESTIONABLE_PAYEE_DIARY"><data key="node_entity_id">WORK_ERPS_QUESTIONABLE_PAYEE_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Questionable Representative Payee Follow-Up Diary</data><data key="node_domain">Representative Payee / Work Control</data><data key="node_description">Diary control established for follow-up on a questionable representative payee; eRPS Add New Issue is an authorized method, while policy permits another reliable diary control.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Physical persistence and diary code are not identified by public POMS.</data></node><node id="WORK_ERPS_TERMINATED_RELATIONSHIP"><data key="node_entity_id">WORK_ERPS_TERMINATED_RELATIONSHIP</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eRPS Terminated Relationship Alert</data><data key="node_domain">Payee / Cross-System Consistency</data><data key="node_description">When PC processes certain erroneous Title II terminations/reinstatements via MACADE, eRPS can alert FO because payee relationship is marked terminated.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="WORK_ESPF_ONLPFL"><data key="node_entity_id">WORK_ESPF_ONLPFL</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">eSPF ONLPFL Work Unit</data><data key="node_acronym">ONLPFL</data><data key="node_domain">Customer Service / Protective Filing / Work Control</data><data key="node_description">Historical eLAS employee-name/unit-code marker used to identify eSPF requests and surface them in eLAS, WAC and VIPr appointment processing.</data><data key="node_observed_status">historical_after_espf_retirement</data><data key="node_observed_as_of">2024-11-21</data><data key="node_confidence">5</data><data key="node_notes">Work-control marker, not a database. SSA instructions say all eSPF requests in eLAS were identified by Employee Name and Unit Code ONLPFL.</data></node><node id="WORK_IRMAA_MEDACT"><data key="node_entity_id">WORK_IRMAA_MEDACT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">IRMAA MEDACT Work Control</data><data key="node_acronym">MEDACT</data><data key="node_domain">Medicare / IRMAA</data><data key="node_description">PCACS diary/work-control issue used in current IRMAA evidence follow-up procedures.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Policy also permits a tickle; this record models the named PCACS MEDACT control only.</data></node><node id="WORK_MCS_ATTEST_ISSUE"><data key="node_entity_id">WORK_MCS_ATTEST_ISSUE</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">MCS/CCE ATTEST Issue</data><data key="node_acronym">ATTEST</data><data key="node_domain">Claims / Signature / Work Control</data><data key="node_description">Development/work-control issue used to record receipt of application attestation or another accepted signature method.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-07-22</data><data key="node_confidence">5</data><data key="node_notes">MCS automatically propagates ATTEST to DW01 even when the actual method is Upload Documents, wet signature, or CPAS; remarks disambiguate the signature method.</data></node><node id="WORK_MCS_PROTFL"><data key="node_entity_id">WORK_MCS_PROTFL</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">MCS PROTFL Protective Filing Development Issue</data><data key="node_acronym">PROTFL</data><data key="node_domain">Title II / Claims / Work Control</data><data key="node_description">Development Worksheet issue used in MCS to control the earliest possible protective filing date for a Title II claim.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS says the request date for PROTFL on DW01/02 must reflect the earliest possible protective filing date.</data></node><node id="WORK_MCS_VAPT_ISSUE"><data key="node_entity_id">WORK_MCS_VAPT_ISSUE</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">MCS VAPT 100% PT Issue and Remark</data><data key="node_acronym">100% PT</data><data key="node_domain">Disability / Claims / Work Control</data><data key="node_description">MCS issue and DW01 remark used to identify matched VAPT disability cases.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">MCS adds ISSUE 100% PT and remark VA 100% Perm and Total to DW01.</data></node><node id="WORK_MNUP_15_DAY_DIARY"><data key="node_entity_id">WORK_MNUP_15_DAY_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">MNUP 15-Day Due-Process Diary</data><data key="node_acronym">MNUP 15-Day Diary</data><data key="node_domain">Title II / Program Integrity / Work Control</data><data key="node_description">Fifteen-calendar-day diary established after the final MNUP appointment failure before benefit suspension action.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Physical diary store is not identified.</data></node><node id="WORK_PIE_EE_DIARY"><data key="node_entity_id">WORK_PIE_EE_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">Payroll Information Exchange EE Diary</data><data key="node_acronym">EE Diary</data><data key="node_domain">Title XVI / Earnings</data><data key="node_description">SSI work-control diary created when payroll-provider wage/employment information received through PIE cannot automatically post to the SSI record.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Created for conditions such as EIN mismatch, missing EIN, force-due/manual-deeming or other manual-review conditions.</data></node><node id="WORK_R105_MAQR_TASK"><data key="node_entity_id">WORK_R105_MAQR_TASK</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">QRCPS MAQR Qualification Task</data><data key="node_domain">Disability &amp; Quality Review</data><data key="node_description">Management requests the MAQR task for qualified federal quality reviewers within QRCPS; permits medical assessments in limited documentation-deficiency classes.</data><data key="node_observed_status">documented_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="WORK_RETAP_FUT_PENSION"><data key="node_entity_id">WORK_RETAP_FUT_PENSION</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">RETAP Future Pension Entitlement Alert</data><data key="node_domain">Title II / Historical GPO</data><data key="node_description">For pre-January-2024 entitlement cases, RETAP could issue alert before expected future pension to develop GPO.</data><data key="node_observed_status">legacy_pre_2024_processing</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="WORK_SSI_3D_DIARY"><data key="node_entity_id">WORK_SSI_3D_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI DHS Removal 3D Diary</data><data key="node_acronym">3D</data><data key="node_domain">Title XVI / Immigration / Work Control</data><data key="node_description">PE ODS-controlled diary from SSA monthly matching of DHS removal listings against SSR.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Original section revision predates the 10-year horizon, but the workflow is retained in current 2026 SSI Interfaces policy and TN 64 (09-23).</data></node><node id="WORK_SSI_B3_DIARY"><data key="node_entity_id">WORK_SSI_B3_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI B3 Diary</data><data key="node_acronym">B3</data><data key="node_domain">Title XVI / Earnings / Work Control</data><data key="node_description">Diary set when automated netting and/or automated notice generation cannot complete during an SSI earned-income redetermination.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">Physical storage of the diary is not identified in the public source.</data></node><node id="WORK_SSI_CRITICAL_BDAY"><data key="node_entity_id">WORK_SSI_CRITICAL_BDAY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Critical Birthday Diaries</data><data key="node_acronym">Critical Birthday Diaries</data><data key="node_domain">Title XVI / Post-entitlement / Disability</data><data key="node_description">System-generated diaries used for age-related SSI post-entitlement actions, including age-18 redetermination selection and other critical-age reviews.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-04</data><data key="node_confidence">5</data><data key="node_notes">Current batch POMS lists KB, KC, KE, K8, K9, and KP diary families. Exact generating program and persistence implementation are not named.</data></node><node id="WORK_SSI_D6_ALERT"><data key="node_entity_id">WORK_SSI_D6_ALERT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI D6 Alert</data><data key="node_acronym">D6</data><data key="node_domain">Title XVI / Redetermination / Work Control</data><data key="node_description">Alert generated when an essential-person death input does not include the redetermination initiation date in the documented workflow.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">No standalone alert database is inferred.</data></node><node id="WORK_SSI_D8_DIARY"><data key="node_entity_id">WORK_SSI_D8_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Title XIX Facility Match D8 Diary</data><data key="node_acronym">D8</data><data key="node_domain">Title XVI / Facility / Work Control</data><data key="node_description">Monthly facility-match diary generated from CMS Title XIX/Minimum Data Set information when an SSI recipient admission requires development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">D8 development can result in technician-verified address and living-arrangement changes; the CMS facility address is not treated as an automatic recipient-address update.</data></node><node id="WORK_SSI_E2_DIARY"><data key="node_entity_id">WORK_SSI_E2_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Rental Subsidy E2 Diary</data><data key="node_acronym">E2</data><data key="node_domain">Title XVI / Work Control</data><data key="node_description">SSR diary set during annual systems COLA processing to flag cases requiring potential rental-subsidy development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Set when rental subsidy is greater than zero for the most recent living-arrangement period and specified payment-status conditions are met.</data></node><node id="WORK_SSI_I8_DIARY"><data key="node_entity_id">WORK_SSI_I8_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI DHS Voluntary Departure I8 Diary</data><data key="node_acronym">I8</data><data key="node_domain">Title XVI / Immigration / Work Control</data><data key="node_description">PE ODS-controlled monthly diary derived from DHS reentry-permit information indicating planned departure from the United States.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current policy says duplicate alert records are sent to MISF; displayed address is not modeled as a DHS-sourced automatic SSA address update.</data></node><node id="WORK_SSI_IRS_5B_DIARY"><data key="node_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI IRS 5B Diary</data><data key="node_acronym">5B</data><data key="node_domain">Title XVI / IRS Match / Work Control</data><data key="node_description">SSI work-control diary generated from the IRS 1099 match when income/resource information requires review.</data><data key="node_observed_status">observed_current</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">The 5B diary is posted to SSR as a work-control indicator. It is not evidence that unverified IRS values automatically become verified SSI income/resource facts.</data></node><node id="WORK_SSI_IRS_5H_DIARY"><data key="node_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Pension Interface 5H Diary</data><data key="node_acronym">5H</data><data key="node_domain">Title XVI / IRS Match / Work Control</data><data key="node_description">SSI work-control diary posted when the IRS pension interface identifies reportable discrepancies requiring development.</data><data key="node_observed_status">observed_current_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Tax-data alert requiring development. POMS instructs staff to input developed data to SSR when clearing the diary; the underlying IRS data are not treated as automatically verified program facts.</data></node><node id="WORK_SSI_J3J5_DIARY"><data key="node_entity_id">WORK_SSI_J3J5_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI MEF Overreported Earnings J3/J5 Diaries</data><data key="node_acronym">J3/J5</data><data key="node_domain">Title XVI / Earnings / Work Control</data><data key="node_description">PE ODS-controlled diaries created when SSR annual earnings materially exceed MEF amounts under the documented J3/J5 selection rules.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 SSI Interfaces TOC retains the J3/J5 workflow; resolution can release underpayments.</data></node><node id="WORK_SSI_K6K7_DIARY"><data key="node_entity_id">WORK_SSI_K6K7_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI MEF Underreported Earnings K6/K7 Diaries</data><data key="node_acronym">K6/K7</data><data key="node_domain">Title XVI / Earnings / Work Control</data><data key="node_description">PE ODS-controlled diaries created when MEF annual earnings materially exceed amounts on SSR under the documented K6/K7 selection rules.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current 2026 SSI Interfaces TOC retains the K6/K7 workflow; MEF data are tax data.</data></node><node id="WORK_SSI_KB_DIARY"><data key="node_entity_id">WORK_SSI_KB_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI KB Age-18 Diary</data><data key="node_acronym">KB</data><data key="node_domain">Title XVI / Redeterminations / Work Control</data><data key="node_description">Critical-birthday diary set and selected for a scheduled SSI redetermination in the month the recipient attains age 18.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes" /></node><node id="WORK_SSI_RT_DIARY"><data key="node_entity_id">WORK_SSI_RT_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI RT Diary</data><data key="node_acronym">RT</data><data key="node_domain">Title XVI / Work Control / Resources</data><data key="node_description">SSI diary used to mature future resource-development actions, including age-17 and age-18 Trump Account/ABLE rollover development.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-07-09</data><data key="node_confidence">5</data><data key="node_notes">Diary persistence technology is not identified by public policy.</data></node><node id="WORK_SSI_S2_DIARY"><data key="node_entity_id">WORK_SSI_S2_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI State Wage Record Match S2 Diary</data><data key="node_acronym">S2</data><data key="node_domain">Title XVI / Earnings / Work Control</data><data key="node_description">PE ODS-controlled SSI diary generated when the quarterly OCSE wage comparison identifies materially underreported wages relative to SSR.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Current POMS identifies S2 as an OCSE/SSI earned-income discrepancy diary; current policy table of contents retains the workflow.</data></node><node id="WORK_SSI_S7_DIARY"><data key="node_entity_id">WORK_SSI_S7_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI State Wage Record Match S7 Diary</data><data key="node_acronym">S7</data><data key="node_domain">Title XVI / Earnings / Work Control</data><data key="node_description">PE ODS-controlled SSI diary generated when the quarterly OCSE wage comparison identifies materially overreported wages relative to SSR.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">Section revision is older, but current POMS TN 65 and 2026 SSI Interfaces TOC retain the workflow.</data></node><node id="WORK_SSI_SB_DIARY"><data key="node_entity_id">WORK_SSI_SB_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Savings Security SB Diary</data><data key="node_acronym">SB Diary</data><data key="node_domain">Title XVI / Resources / Interface Work</data><data key="node_description">SSI post-entitlement work control associated with the Bureau of the Fiscal Service savings-security match and controlled through PE ODS.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">POMS directs users to identify records with SB diaries through PE ODS; this does not imply a separate physical diary database.</data></node><node id="WORK_SSI_U5_DIARY"><data key="node_entity_id">WORK_SSI_U5_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Unemployment Compensation Match U5 Diary</data><data key="node_acronym">U5</data><data key="node_domain">Title XVI / Income / Work Control</data><data key="node_description">PE ODS-controlled SSI diary generated by the quarterly OCSE unemployment-compensation comparison when state UC exceeds relevant SSR unearned-income amounts.</data><data key="node_observed_status">observed_current_policy</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">MSSICS clearance uses DUEM; non-MSSICS clearance uses UDIA/Direct SSR Update.</data></node><node id="WORK_SSI_Z7_DIARY"><data key="node_entity_id">WORK_SSI_Z7_DIARY</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">SSI Z7 ZIP Address Alert/Diary</data><data key="node_acronym">Z7</data><data key="node_domain">Title XVI / Address Work Control</data><data key="node_description">Title XVI alert/diary generated when ZIP+4 processing cannot determine the correct ZIP Code and/or ZIP+4 during USPS mass change processing.</data><data key="node_observed_status">documented_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">4</data><data key="node_notes">Current live POMS page is authoritative for the rule, but the underlying transmittal is legacy.</data></node><node id="WORK_SSNAP_SUSPECT_HOLD"><data key="node_entity_id">WORK_SSNAP_SUSPECT_HOLD</data><data key="node_entity_type">work_control_store</data><data key="node_canonical_name">SSNAP Suspect Status Holding File</data><data key="node_acronym">Suspect Status</data><data key="node_domain">Identity / Enumeration / Work Control</data><data key="node_description">Holding-file/work-control state for SSN applications requiring additional evidence verification before normal processing can continue.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-05</data><data key="node_confidence">5</data><data key="node_notes">POMS explicitly calls this a Suspect Status holding file. Physical persistence and database implementation are not disclosed.</data></node><node id="WORK_WCPDB_RIB_ALERT"><data key="node_entity_id">WORK_WCPDB_RIB_ALERT</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">WC/PDB Age 61 Years 9 Months Retirement Option Alert</data><data key="node_acronym">WC/PDB RIB Alert</data><data key="node_domain">Title II / Disability / Retirement / Work Control</data><data key="node_description">One-time system-generated alert when a disabled beneficiary is age 61 years 9 months and workers compensation or public disability offset is involved, prompting review of potential higher retirement benefits.</data><data key="node_observed_status">observed_current_policy_reference</data><data key="node_observed_as_of">2026-10-07</data><data key="node_confidence">5</data><data key="node_notes">OIG states SSA systems generate the alert but does not name the physical alert-generating application.</data></node><node id="WORK_WLM_APPT_QUEUE"><data key="node_entity_id">WORK_WLM_APPT_QUEUE</data><data key="node_entity_type">work_control</data><data key="node_canonical_name">WLM Appointment Queue</data><data key="node_acronym">WLM Appointment Queue</data><data key="node_domain">Field Operations / Workload Routing</data><data key="node_description">Work queue in Workload Management that receives ASC domestic initial-claim telephone appointments and assigns them based on technician skillsets and availability.</data><data key="node_observed_status">observed_limited_rollout</data><data key="node_observed_as_of">2026-08-29</data><data key="node_confidence">5</data><data key="node_notes">Current WLM emergency-message instructions describe the appointment queue and Get Next Work behavior. No underlying queue/database technology is inferred.</data></node><edge id="R100_REL001" source="ORG_SSA_SDRM" target="SVC_DA_SDRM_FORMS_SITE"><data key="edge_relationship_id">R100_REL001</data><data key="edge_source_entity_id">ORG_SSA_SDRM</data><data key="edge_relationship_type">operates</data><data key="edge_target_entity_id">SVC_DA_SDRM_FORMS_SITE</data><data key="edge_operational_context">Current POMS says the State Disability Resource Management Division makes the electronic financial-management forms available through the DA SDRM intranet website.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL002" source="SVC_DA_SDRM_FORMS_SITE" target="FORM_SSA4513"><data key="edge_relationship_id">R100_REL002</data><data key="edge_source_entity_id">SVC_DA_SDRM_FORMS_SITE</data><data key="edge_relationship_type">distributes</data><data key="edge_target_entity_id">FORM_SSA4513</data><data key="edge_operational_context">Current POMS lists this form among the financial-management forms State DDSs can obtain electronically through DA/SDRM.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL003" source="FORM_SSA4513" target="PROC_DDS_STATE_FUNDING_AUTH"><data key="edge_relationship_id">R100_REL003</data><data key="edge_source_entity_id">FORM_SSA4513</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="edge_operational_context">The form is part of the State DDS financial-management/funding control set surrounding SSA disability-program funding.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL004" source="SVC_DA_SDRM_FORMS_SITE" target="FORM_SSA4513_ADD"><data key="edge_relationship_id">R100_REL004</data><data key="edge_source_entity_id">SVC_DA_SDRM_FORMS_SITE</data><data key="edge_relationship_type">distributes</data><data key="edge_target_entity_id">FORM_SSA4513_ADD</data><data key="edge_operational_context">Current POMS lists this form among the financial-management forms State DDSs can obtain electronically through DA/SDRM.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL005" source="FORM_SSA4513_ADD" target="PROC_DDS_STATE_FUNDING_AUTH"><data key="edge_relationship_id">R100_REL005</data><data key="edge_source_entity_id">FORM_SSA4513_ADD</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="edge_operational_context">The form is part of the State DDS financial-management/funding control set surrounding SSA disability-program funding.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL006" source="SVC_DA_SDRM_FORMS_SITE" target="FORM_SSA4514"><data key="edge_relationship_id">R100_REL006</data><data key="edge_source_entity_id">SVC_DA_SDRM_FORMS_SITE</data><data key="edge_relationship_type">distributes</data><data key="edge_target_entity_id">FORM_SSA4514</data><data key="edge_operational_context">Current POMS lists this form among the financial-management forms State DDSs can obtain electronically through DA/SDRM.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL007" source="FORM_SSA4514" target="PROC_DDS_STATE_FUNDING_AUTH"><data key="edge_relationship_id">R100_REL007</data><data key="edge_source_entity_id">FORM_SSA4514</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="edge_operational_context">The form is part of the State DDS financial-management/funding control set surrounding SSA disability-program funding.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL008" source="SVC_DA_SDRM_FORMS_SITE" target="FORM_SSA871"><data key="edge_relationship_id">R100_REL008</data><data key="edge_source_entity_id">SVC_DA_SDRM_FORMS_SITE</data><data key="edge_relationship_type">distributes</data><data key="edge_target_entity_id">FORM_SSA871</data><data key="edge_operational_context">Current POMS lists this form among the financial-management forms State DDSs can obtain electronically through DA/SDRM.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL009" source="FORM_SSA871" target="PROC_DDS_STATE_FUNDING_AUTH"><data key="edge_relationship_id">R100_REL009</data><data key="edge_source_entity_id">FORM_SSA871</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="edge_operational_context">The form is part of the State DDS financial-management/funding control set surrounding SSA disability-program funding.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL010" source="PROC_1634_MEDICAID" target="ORG_STATE_MEDICAID"><data key="edge_relationship_id">R100_REL010</data><data key="edge_source_entity_id">PROC_1634_MEDICAID</data><data key="edge_relationship_type">coordinates_with</data><data key="edge_target_entity_id">ORG_STATE_MEDICAID</data><data key="edge_operational_context">SSA performs Medicaid eligibility determinations under section 1634 agreements with participating States; States retain their Medicaid program responsibilities.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL011" source="FORM_IRS4506" target="PROC_IRS_TAXPAYER_MEDIATED"><data key="edge_relationship_id">R100_REL011</data><data key="edge_source_entity_id">FORM_IRS4506</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_IRS_TAXPAYER_MEDIATED</data><data key="edge_operational_context">Current SSA POMS identifies Form 4506 as a route for a number holder to request additional IRS tax information and have it submitted to SSA.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL012" source="FORM_IRS4506T" target="PROC_IRS_TAXPAYER_MEDIATED"><data key="edge_relationship_id">R100_REL012</data><data key="edge_source_entity_id">FORM_IRS4506T</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_IRS_TAXPAYER_MEDIATED</data><data key="edge_operational_context">Current SSA POMS identifies Form 4506-T as a route for a number holder to request transcript information and have it submitted to SSA.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL013" source="PROC_IRS_TAXPAYER_MEDIATED" target="ORG_IRS"><data key="edge_relationship_id">R100_REL013</data><data key="edge_source_entity_id">PROC_IRS_TAXPAYER_MEDIATED</data><data key="edge_relationship_type">requests_data_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">The taxpayer-mediated fallback obtains tax information from IRS rather than relying on SSA's standard written IRS request path.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL014" source="PROC_IRS_TAXPAYER_MEDIATED" target="DATA_IRS_ACCOUNT_TRANSCRIPT"><data key="edge_relationship_id">R100_REL014</data><data key="edge_source_entity_id">PROC_IRS_TAXPAYER_MEDIATED</data><data key="edge_relationship_type">may_obtain</data><data key="edge_target_entity_id">DATA_IRS_ACCOUNT_TRANSCRIPT</data><data key="edge_operational_context">Form 4506-T can be used to obtain transcript information; current SSA POMS separately defines the IRS Account Transcript used by SSA.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL015" source="PROC_IRS_TAXPAYER_MEDIATED" target="DATA_IRS_RETURN_TRANSCRIPT"><data key="edge_relationship_id">R100_REL015</data><data key="edge_source_entity_id">PROC_IRS_TAXPAYER_MEDIATED</data><data key="edge_relationship_type">may_obtain</data><data key="edge_target_entity_id">DATA_IRS_RETURN_TRANSCRIPT</data><data key="edge_operational_context">Form 4506-T can be used to obtain transcript information; current SSA POMS separately defines the IRS Return Transcript used by SSA.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL016" source="UI_MCS_NHRR" target="APP_MCS"><data key="edge_relationship_id">R100_REL016</data><data key="edge_source_entity_id">UI_MCS_NHRR</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS identifies NHRR as MCS screen #23 used to review alleged railroad employment months.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL017" source="UI_MCS_DRRE" target="APP_MCS"><data key="edge_relationship_id">R100_REL017</data><data key="edge_source_entity_id">UI_MCS_DRRE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS identifies DRRE in the MCS earnings-computation path.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL018" source="DATA_RR96_TD_SM" target="UI_MCS_DRRE"><data key="edge_relationship_id">R100_REL018</data><data key="edge_source_entity_id">DATA_RR96_TD_SM</data><data key="edge_relationship_type">displayed_on</data><data key="edge_target_entity_id">UI_MCS_DRRE</data><data key="edge_operational_context">DRRE displays RR 96-to-date service months; 60 or more months can establish career railroad status.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL019" source="DATA_RR37_TD_SM" target="UI_MCS_DRRE"><data key="edge_relationship_id">R100_REL019</data><data key="edge_source_entity_id">DATA_RR37_TD_SM</data><data key="edge_relationship_type">displayed_on</data><data key="edge_target_entity_id">UI_MCS_DRRE</data><data key="edge_operational_context">DRRE displays RR 1937-to-date service months; 120 or more months can establish career railroad status.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL020" source="UI_MCS_NHRR" target="ORG_DCR"><data key="edge_relationship_id">R100_REL020</data><data key="edge_source_entity_id">UI_MCS_NHRR</data><data key="edge_relationship_type">supports_jurisdiction_screening_for</data><data key="edge_target_entity_id">ORG_DCR</data><data key="edge_operational_context">DCR jurisdiction for career railroad disability cases is screened using railroad employment information reviewed in MCS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL021" source="UI_MCS_DRRE" target="ORG_DCR"><data key="edge_relationship_id">R100_REL021</data><data key="edge_source_entity_id">UI_MCS_DRRE</data><data key="edge_relationship_type">supports_jurisdiction_screening_for</data><data key="edge_target_entity_id">ORG_DCR</data><data key="edge_operational_context">DCR jurisdiction for career railroad disability cases is screened using railroad service-month information on DRRE.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL022" source="PROC_SSI_EP_DEATH_RZ" target="WORK_SSI_D6_ALERT"><data key="edge_relationship_id">R100_REL022</data><data key="edge_source_entity_id">PROC_SSI_EP_DEATH_RZ</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">WORK_SSI_D6_ALERT</data><data key="edge_operational_context">If the RZ initiation date is omitted with an essential-person death input, the system generates a D6 alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL023" source="PROC_SSI_EP_DEATH_RZ" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R100_REL023</data><data key="edge_source_entity_id">PROC_SSI_EP_DEATH_RZ</data><data key="edge_relationship_type">deletes_case_from</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">Current POMS says the system deletes the case from PE ODS when the required RZ initiation date is not transmitted with the death input.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL024" source="PROC_SSI_EP_DEATH_RZ" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R100_REL024</data><data key="edge_source_entity_id">PROC_SSI_EP_DEATH_RZ</data><data key="edge_relationship_type">reselects_case_in</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">Current POMS says the case is reselected as a profile D redetermination during the next merge.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL025" source="UI_CCE_FIN_ACCOUNTS" target="APP_CCE"><data key="edge_relationship_id">R100_REL025</data><data key="edge_source_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Current redetermination policy directs staff to record the direct-deposit financial account as a resource on the CCE Financial Accounts screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL026" source="DATA_MBR_DD_INDICATOR" target="SYS_MBR"><data key="edge_relationship_id">R100_REL026</data><data key="edge_source_entity_id">DATA_MBR_DD_INDICATOR</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS identifies a direct-deposit indicator on MBR as a lead requiring development for a financial account during an SSI redetermination.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL027" source="DATA_SSR_DD_INDICATOR" target="SYS_SSR"><data key="edge_relationship_id">R100_REL027</data><data key="edge_source_entity_id">DATA_SSR_DD_INDICATOR</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS identifies a direct-deposit indicator on SSR as a lead requiring development for a financial account during an SSI redetermination.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL028" source="DATA_MBR_DD_INDICATOR" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">R100_REL028</data><data key="edge_source_entity_id">DATA_MBR_DD_INDICATOR</data><data key="edge_relationship_type">triggers_resource_development_in</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">During an SSI redetermination, the MBR direct-deposit indicator is a lead to develop and record the financial account.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL029" source="DATA_SSR_DD_INDICATOR" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">R100_REL029</data><data key="edge_source_entity_id">DATA_SSR_DD_INDICATOR</data><data key="edge_relationship_type">triggers_resource_development_in</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">During an SSI redetermination, the SSR direct-deposit indicator is a lead to develop and record the financial account.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL030" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">R100_REL030</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">The liquid-resource redetermination process records direct-deposit and other financial accounts on the CCE Financial Accounts screen when development is necessary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL031" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="DATA_SSI_IRS_CONTROLLED_ALERT"><data key="edge_relationship_id">R100_REL031</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">uses_as_lead</data><data key="edge_target_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="edge_operational_context">Current POMS requires development of controlled IRS alerts during resource redeterminations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL032" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="DATA_SSI_IRS_INFORMATIONAL_ALERT"><data key="edge_relationship_id">R100_REL032</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">uses_as_lead</data><data key="edge_target_entity_id">DATA_SSI_IRS_INFORMATIONAL_ALERT</data><data key="edge_operational_context">Current POMS says informational IRS alerts can be used as leads to detect liquid resources during the redetermination interview.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL033" source="FORM_SSA414_U3" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">R100_REL033</data><data key="edge_source_entity_id">FORM_SSA414_U3</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">Current FO remittance policy requires a manually prepared SSA-414-U3 for standard fees while DMS-generated FORT/CCFORT/FODRL control other remittances.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL034" source="PROC_SSI_SAVE_VERIFICATION" target="SVC_SAVE"><data key="edge_relationship_id">R100_REL034</data><data key="edge_source_entity_id">PROC_SSI_SAVE_VERIFICATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">SAVE verification is required for noncitizen Title XVI initial claims prior to approval, redeterminations, and immigration-status changes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL035" source="PROC_SSI_SAVE_VERIFICATION" target="APP_IMAIN"><data key="edge_relationship_id">R100_REL035</data><data key="edge_source_entity_id">PROC_SSI_SAVE_VERIFICATION</data><data key="edge_relationship_type">accesses_via</data><data key="edge_target_entity_id">APP_IMAIN</data><data key="edge_operational_context">Current Title XVI policy directs claims users to access SAVE through I-Main.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL036" source="PROC_SSI_SAVE_VERIFICATION" target="UI_CCE_ROC"><data key="edge_relationship_id">R100_REL036</data><data key="edge_source_entity_id">PROC_SSI_SAVE_VERIFICATION</data><data key="edge_relationship_type">documents_result_in</data><data key="edge_target_entity_id">UI_CCE_ROC</data><data key="edge_operational_context">Current Title XVI policy directs staff to annotate SAVE immigration-status results on the CCE Report of Contact page.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL037" source="PROC_SSI_SAVE_VERIFICATION" target="APP_EP"><data key="edge_relationship_id">R100_REL037</data><data key="edge_source_entity_id">PROC_SSI_SAVE_VERIFICATION</data><data key="edge_relationship_type">stores_response_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Current policy directs staff to retain copies of the immigration document and SAVE response in the electronic folder, including via Evidence Portal.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL038" source="PROC_SSI_SAVE_VERIFICATION" target="APP_EVIEW"><data key="edge_relationship_id">R100_REL038</data><data key="edge_source_entity_id">PROC_SSI_SAVE_VERIFICATION</data><data key="edge_relationship_type">stores_response_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Current policy allows the SAVE response and immigration-document evidence to be retained in the electronic folder/eView.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL039" source="PROC_SSI_SAVE_VERIFICATION" target="DATA_PI_ARN"><data key="edge_relationship_id">R100_REL039</data><data key="edge_source_entity_id">PROC_SSI_SAVE_VERIFICATION</data><data key="edge_relationship_type">writes_verified_identifier_to</data><data key="edge_target_entity_id">DATA_PI_ARN</data><data key="edge_operational_context">If the immigration document includes an Alien Registration Number, current policy directs staff to enter the ARN in Person Information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL040" source="PROC_IDD_MASS_ENROLLMENT" target="PROC_IDD"><data key="edge_relationship_id">R100_REL040</data><data key="edge_source_entity_id">PROC_IDD_MASS_ENROLLMENT</data><data key="edge_relationship_type">subprocess_of</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">Country mass enrollment is a documented operating mode within International Direct Deposit.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL041" source="PROC_IDD_MASS_ENROLLMENT" target="FORM_SSA1199_FAMILY"><data key="edge_relationship_id">R100_REL041</data><data key="edge_source_entity_id">PROC_IDD_MASS_ENROLLMENT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA1199_FAMILY</data><data key="edge_operational_context">IDD country mass-enrollment operations use a country-designed enrollment form; the Atlas models this under the existing SSA-1199 country-form family.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R100_REL042" source="ORG_SSA_OEIO" target="PROC_IDD"><data key="edge_relationship_id">R100_REL042</data><data key="edge_source_entity_id">ORG_SSA_OEIO</data><data key="edge_relationship_type">processes</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">Current international direct-deposit procedures identify OEIO as a processing component for beneficiary enrollment requests outside mass enrollment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL001" source="APP_MAPS" target="UI_MAPS_APPLICANT_INFO"><data key="edge_relationship_id">R101_REL001</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_APPLICANT_INFO</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL002" source="APP_MAPS" target="UI_MAPS_SAVINGS_ACCOUNTS"><data key="edge_relationship_id">R101_REL002</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_SAVINGS_ACCOUNTS</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL003" source="APP_MAPS" target="UI_MAPS_INSURANCE_BURIAL_RE"><data key="edge_relationship_id">R101_REL003</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_INSURANCE_BURIAL_RE</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL004" source="APP_MAPS" target="UI_MAPS_RELATIVES_EXPENSE"><data key="edge_relationship_id">R101_REL004</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_RELATIVES_EXPENSE</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL005" source="APP_MAPS" target="UI_MAPS_UNEARNED_INCOME"><data key="edge_relationship_id">R101_REL005</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_UNEARNED_INCOME</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL006" source="APP_MAPS" target="UI_MAPS_EARNED_INCOME"><data key="edge_relationship_id">R101_REL006</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_EARNED_INCOME</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL007" source="APP_MAPS" target="UI_MAPS_ATWE"><data key="edge_relationship_id">R101_REL007</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_ATWE</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL008" source="APP_MAPS" target="UI_MAPS_MEDICARE_SAVINGS_PLAN"><data key="edge_relationship_id">R101_REL008</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_MEDICARE_SAVINGS_PLAN</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL009" source="APP_MAPS" target="UI_MAPS_DWRC"><data key="edge_relationship_id">R101_REL009</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_DWRC</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL010" source="APP_MAPS" target="UI_MAPS_VRAI"><data key="edge_relationship_id">R101_REL010</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_VRAI</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL011" source="APP_MAPS" target="UI_MAPS_DADS"><data key="edge_relationship_id">R101_REL011</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_DADS</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL012" source="APP_MAPS" target="UI_MAPS_CURRENT_AGENCY_DATA"><data key="edge_relationship_id">R101_REL012</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_CURRENT_AGENCY_DATA</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL013" source="APP_MAPS" target="UI_MAPS_PREDECISION_PERIOD"><data key="edge_relationship_id">R101_REL013</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MAPS_PREDECISION_PERIOD</data><data key="edge_operational_context">Documented MAPS user-interface surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL014" source="APP_MAPS" target="DB_MAPS"><data key="edge_relationship_id">R101_REL014</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DB_MAPS</data><data key="edge_operational_context">Current policy explicitly refers to a MAPS database used for agency-data processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Database technology and hosting not identified.</data></edge><edge id="R101_REL015" source="PROC_MAPS_VERIFICATION" target="UI_MAPS_VRAI"><data key="edge_relationship_id">R101_REL015</data><data key="edge_source_entity_id">PROC_MAPS_VERIFICATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MAPS_VRAI</data><data key="edge_operational_context">Issue Verification screen supports discrepancy verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL016" source="UI_MAPS_VRAI" target="UI_MAPS_DADS"><data key="edge_relationship_id">R101_REL016</data><data key="edge_source_entity_id">UI_MAPS_VRAI</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">UI_MAPS_DADS</data><data key="edge_operational_context">Detailed Agency Data is accessed from the MAPS verification screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL017" source="DATA_MAPS_IRS_AGENCY_DATA" target="UI_MAPS_DADS"><data key="edge_relationship_id">R101_REL017</data><data key="edge_source_entity_id">DATA_MAPS_IRS_AGENCY_DATA</data><data key="edge_relationship_type">displayed_on</data><data key="edge_target_entity_id">UI_MAPS_DADS</data><data key="edge_operational_context">IRS report details are displayed on the Detailed Agency Data screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL018" source="DATA_MAPS_IRS_AGENCY_DATA" target="ORG_IRS"><data key="edge_relationship_id">R101_REL018</data><data key="edge_source_entity_id">DATA_MAPS_IRS_AGENCY_DATA</data><data key="edge_relationship_type">received_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">MAPS IRS agency data originates from IRS information-return reporting.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">IRS may not be originator of underlying payment.</data></edge><edge id="R101_REL019" source="DATA_MAPS_IRS_AGENCY_DATA" target="DB_MAPS"><data key="edge_relationship_id">R101_REL019</data><data key="edge_source_entity_id">DATA_MAPS_IRS_AGENCY_DATA</data><data key="edge_relationship_type">used_in</data><data key="edge_target_entity_id">DB_MAPS</data><data key="edge_operational_context">IRS-derived agency data are used in MAPS verification and resource/income development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Physical persistence for each IRS item not separately documented.</data></edge><edge id="R101_REL020" source="PROC_MAPS_VERIFICATION" target="QRY_MEDQ"><data key="edge_relationship_id">R101_REL020</data><data key="edge_source_entity_id">PROC_MAPS_VERIFICATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">QRY_MEDQ</data><data key="edge_operational_context">MEDQ can be used to view prior OPM/IRS agency-data entries in MAPS verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL021" source="DATA_MAPS_MAILING_ADDRESS" target="APP_MAPS"><data key="edge_relationship_id">R101_REL021</data><data key="edge_source_entity_id">DATA_MAPS_MAILING_ADDRESS</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">Extra Help mailing address is collected in MAPS for correspondence and development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL022" source="PROC_EXTRA_HELP_ADDRESS_UPDATE" target="DATA_MAPS_MAILING_ADDRESS"><data key="edge_relationship_id">R101_REL022</data><data key="edge_source_entity_id">PROC_EXTRA_HELP_ADDRESS_UPDATE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_MAPS_MAILING_ADDRESS</data><data key="edge_operational_context">Change-of-address development begins from the address provided on the Extra Help application.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL023" source="PROC_EXTRA_HELP_ADDRESS_UPDATE" target="SYS_MBR"><data key="edge_relationship_id">R101_REL023</data><data key="edge_source_entity_id">PROC_EXTRA_HELP_ADDRESS_UPDATE</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">If a qualifying recent change involves Title II, staff follow program procedures to update MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic database propagation inferred.</data></edge><edge id="R101_REL024" source="PROC_EXTRA_HELP_ADDRESS_UPDATE" target="SYS_SSR"><data key="edge_relationship_id">R101_REL024</data><data key="edge_source_entity_id">PROC_EXTRA_HELP_ADDRESS_UPDATE</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">If the applicant is an SSI recipient, staff follow normal procedures to update SSR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic database propagation inferred.</data></edge><edge id="R101_REL025" source="APP_MAPS" target="PROC_EXTRA_HELP_ADDRESS_UPDATE"><data key="edge_relationship_id">R101_REL025</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_EXTRA_HELP_ADDRESS_UPDATE</data><data key="edge_operational_context">MAPS application address drives the documented Extra Help address-development procedure.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL026" source="PROC_MAPS_PREDECISION" target="NOTICE_MAPS_PREDECISION"><data key="edge_relationship_id">R101_REL026</data><data key="edge_source_entity_id">PROC_MAPS_PREDECISION</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">NOTICE_MAPS_PREDECISION</data><data key="edge_operational_context">Potential denial causes the subsidy determination process to automatically generate the advance notice.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL027" source="PROC_MAPS_PREDECISION" target="APP_MAPS"><data key="edge_relationship_id">R101_REL027</data><data key="edge_source_entity_id">PROC_MAPS_PREDECISION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">New information received in the response period is entered in MAPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL028" source="PROC_MAPS_PREDECISION" target="UI_MAPS_PREDECISION_PERIOD"><data key="edge_relationship_id">R101_REL028</data><data key="edge_source_entity_id">PROC_MAPS_PREDECISION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MAPS_PREDECISION_PERIOD</data><data key="edge_operational_context">Adjudicators use the MAPS pre-decisional period screen when handling inquiries.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL029" source="PROC_MAPS_PREDECISION" target="PROC_MAPS_VERIFICATION"><data key="edge_relationship_id">R101_REL029</data><data key="edge_source_entity_id">PROC_MAPS_PREDECISION</data><data key="edge_relationship_type">can_invoke</data><data key="edge_target_entity_id">PROC_MAPS_VERIFICATION</data><data key="edge_operational_context">Verification procedures are used when further proof is necessary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Not every pre-decisional case requires verification.</data></edge><edge id="R101_REL030" source="UI_MAPS_MEDICARE_SAVINGS_PLAN" target="EX_MSP_STATE_REFERRAL"><data key="edge_relationship_id">R101_REL030</data><data key="edge_source_entity_id">UI_MAPS_MEDICARE_SAVINGS_PLAN</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">EX_MSP_STATE_REFERRAL</data><data key="edge_operational_context">Screen records whether Extra Help application information is sent to the State for Medicare Savings Program consideration.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL031" source="APP_IRMAA" target="UI_IRMAA_IRMN"><data key="edge_relationship_id">R101_REL031</data><data key="edge_source_entity_id">APP_IRMAA</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_IRMAA_IRMN</data><data key="edge_operational_context">Current POMS identifies the screen in the IRMAA processing sequence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL032" source="APP_IRMAA" target="UI_IRMAA_PYTY"><data key="edge_relationship_id">R101_REL032</data><data key="edge_source_entity_id">APP_IRMAA</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_IRMAA_PYTY</data><data key="edge_operational_context">Current POMS identifies the screen in the IRMAA processing sequence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PYTY canonical label has lower naming confidence.</data></edge><edge id="R101_REL033" source="APP_IRMAA" target="UI_IRMAA_IRLC"><data key="edge_relationship_id">R101_REL033</data><data key="edge_source_entity_id">APP_IRMAA</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_IRMAA_IRLC</data><data key="edge_operational_context">Current POMS identifies the screen in the IRMAA processing sequence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL034" source="APP_IRMAA" target="UI_IRMAA_IRMA"><data key="edge_relationship_id">R101_REL034</data><data key="edge_source_entity_id">APP_IRMAA</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_IRMAA_IRMA</data><data key="edge_operational_context">Current POMS identifies the screen in the IRMAA processing sequence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL035" source="APP_IRMAA" target="UI_IRMAA_IRRE"><data key="edge_relationship_id">R101_REL035</data><data key="edge_source_entity_id">APP_IRMAA</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_IRMAA_IRRE</data><data key="edge_operational_context">Current POMS identifies the screen in the IRMAA processing sequence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL036" source="PROC_IRMAA_NEW_INITIAL" target="APP_IRMAA"><data key="edge_relationship_id">R101_REL036</data><data key="edge_source_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_IRMAA</data><data key="edge_operational_context">New initial determinations are processed in the IRMAA system/screens.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL037" source="PROC_IRMAA_NEW_INITIAL" target="ORG_IRS"><data key="edge_relationship_id">R101_REL037</data><data key="edge_source_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="edge_relationship_type">uses_data_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">IRMAA baseline determinations use tax information IRS provides electronically.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL038" source="PROC_IRMAA_NEW_INITIAL" target="SYS_MBR"><data key="edge_relationship_id">R101_REL038</data><data key="edge_source_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Technicians query MBR when checking current IRMAA-related activity.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL039" source="PROC_IRMAA_NEW_INITIAL" target="APP_EVID"><data key="edge_relationship_id">R101_REL039</data><data key="edge_source_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="edge_relationship_type">documents_evidence_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">All evidence submitted for a new initial determination is recorded on EVID.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL040" source="UI_IRMAA_IRMN" target="APP_EVID"><data key="edge_relationship_id">R101_REL040</data><data key="edge_source_entity_id">UI_IRMAA_IRMN</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">IRMN displays an alert to document proof in EVID.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL041" source="UI_IRMAA_IRMN" target="UI_SHARED_PROCESS_MENU"><data key="edge_relationship_id">R101_REL041</data><data key="edge_source_entity_id">UI_IRMAA_IRMN</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">UI_SHARED_PROCESS_MENU</data><data key="edge_operational_context">PF/Enter from IRMN takes the user to Shared Processes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL042" source="DATA_IRMAA_PROOF_STATUS" target="APP_IRMAA"><data key="edge_relationship_id">R101_REL042</data><data key="edge_source_entity_id">DATA_IRMAA_PROOF_STATUS</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_IRMAA</data><data key="edge_operational_context">IRMAA proof status is maintained on IRMAA screens as PENDING, PROVEN, or NOT PROVEN.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL043" source="WORK_IRMAA_MEDACT" target="APP_PCACS"><data key="edge_relationship_id">R101_REL043</data><data key="edge_source_entity_id">WORK_IRMAA_MEDACT</data><data key="edge_relationship_type">controlled_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">MEDACT is a PCACS diary/work-control issue used for IRMAA evidence follow-up.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL044" source="PROC_IRMAA_NEW_INITIAL" target="WORK_IRMAA_MEDACT"><data key="edge_relationship_id">R101_REL044</data><data key="edge_source_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="edge_relationship_type">can_establish</data><data key="edge_target_entity_id">WORK_IRMAA_MEDACT</data><data key="edge_operational_context">Technicians may establish MEDACT as the named PCACS follow-up control.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL045" source="APP_MCS" target="UI_MCS_EARN"><data key="edge_relationship_id">R101_REL045</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MCS_EARN</data><data key="edge_operational_context">MCS earnings screen used in current proof/correction procedures.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL046" source="APP_MCS" target="UI_MCS_ECOR"><data key="edge_relationship_id">R101_REL046</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_MCS_ECOR</data><data key="edge_operational_context">MCS earnings-correction screen used in current proof/correction procedures.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL047" source="UI_MCS_EARN" target="QRY_DEQY"><data key="edge_relationship_id">R101_REL047</data><data key="edge_source_entity_id">UI_MCS_EARN</data><data key="edge_relationship_type">verified_using</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">Staff compare computation-year EARN entries with DEQY to confirm MEF update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL048" source="UI_MCS_ECOR" target="QRY_DEQY"><data key="edge_relationship_id">R101_REL048</data><data key="edge_source_entity_id">UI_MCS_ECOR</data><data key="edge_relationship_type">verified_using</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">Staff compare computation-year ECOR entries with DEQY to confirm MEF update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL049" source="UI_MCS_EARN" target="SYS_MEF"><data key="edge_relationship_id">R101_REL049</data><data key="edge_source_entity_id">UI_MCS_EARN</data><data key="edge_relationship_type">expected_to_update</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Policy requires verification that EARN entries updated MEF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship models documented outcome, not transport or direct-write mechanism.</data></edge><edge id="R101_REL050" source="UI_MCS_ECOR" target="SYS_MEF"><data key="edge_relationship_id">R101_REL050</data><data key="edge_source_entity_id">UI_MCS_ECOR</data><data key="edge_relationship_type">expected_to_update</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Policy requires verification that ECOR entries updated MEF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship models documented outcome, not transport or direct-write mechanism.</data></edge><edge id="R101_REL051" source="APP_DDSQ" target="APP_NDDSS"><data key="edge_relationship_id">R101_REL051</data><data key="edge_source_entity_id">APP_DDSQ</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_operational_context">Field offices use DDSQ to review NDDSS disability information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL052" source="APP_NDDSS" target="UI_NDDSS_DDSM"><data key="edge_relationship_id">R101_REL052</data><data key="edge_source_entity_id">APP_NDDSS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_NDDSS_DDSM</data><data key="edge_operational_context">Current policy references the NDDSS Master File Menu DDSM.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL053" source="APP_DDSQ" target="UI_DDSQ_MASK"><data key="edge_relationship_id">R101_REL053</data><data key="edge_source_entity_id">APP_DDSQ</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_DDSQ_MASK</data><data key="edge_operational_context">DDSQ uses a query mask for NDDSS case information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL054" source="APP_DDSQ" target="DATA_NDDSS_SO"><data key="edge_relationship_id">R101_REL054</data><data key="edge_source_entity_id">APP_DDSQ</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">DATA_NDDSS_SO</data><data key="edge_operational_context">DDSQ full-query response exposes the documented NDDSS field.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL055" source="APP_NDDSS" target="DATA_NDDSS_SO"><data key="edge_relationship_id">R101_REL055</data><data key="edge_source_entity_id">APP_NDDSS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_NDDSS_SO</data><data key="edge_operational_context">The field is part of NDDSS case information surfaced through DDSQ.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL056" source="APP_DDSQ" target="DATA_NDDSS_DST"><data key="edge_relationship_id">R101_REL056</data><data key="edge_source_entity_id">APP_DDSQ</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">DATA_NDDSS_DST</data><data key="edge_operational_context">DDSQ full-query response exposes the documented NDDSS field.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL057" source="APP_NDDSS" target="DATA_NDDSS_DST"><data key="edge_relationship_id">R101_REL057</data><data key="edge_source_entity_id">APP_NDDSS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_NDDSS_DST</data><data key="edge_operational_context">The field is part of NDDSS case information surfaced through DDSQ.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL058" source="APP_DDSQ" target="DATA_NDDSS_DEC"><data key="edge_relationship_id">R101_REL058</data><data key="edge_source_entity_id">APP_DDSQ</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">DATA_NDDSS_DEC</data><data key="edge_operational_context">DDSQ full-query response exposes the documented NDDSS field.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL059" source="APP_NDDSS" target="DATA_NDDSS_DEC"><data key="edge_relationship_id">R101_REL059</data><data key="edge_source_entity_id">APP_NDDSS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_NDDSS_DEC</data><data key="edge_operational_context">The field is part of NDDSS case information surfaced through DDSQ.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL060" source="DATA_NDDSS_SO" target="APP_NDDSS"><data key="edge_relationship_id">R101_REL060</data><data key="edge_source_entity_id">DATA_NDDSS_SO</data><data key="edge_relationship_type">controls_output_from</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_operational_context">System Override controls transmission of case-movement and/or decisional data from NDDSS to SSA systems.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL061" source="APP_NDDSS" target="CODE_NDDSS_TYP_CD"><data key="edge_relationship_id">R101_REL061</data><data key="edge_source_entity_id">APP_NDDSS</data><data key="edge_relationship_type">uses_status_code</data><data key="edge_target_entity_id">CODE_NDDSS_TYP_CD</data><data key="edge_operational_context">EXR initial case receipt uses TYP=CD.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL062" source="APP_NDDSS" target="CODE_NDDSS_CDT5"><data key="edge_relationship_id">R101_REL062</data><data key="edge_source_entity_id">APP_NDDSS</data><data key="edge_relationship_type">uses_status_code</data><data key="edge_target_entity_id">CODE_NDDSS_CDT5</data><data key="edge_operational_context">EXR uses CDT=5 to distinguish the case from a medical CDR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL063" source="APP_EDCS" target="CODE_EDCS_EXR_INITIAL"><data key="edge_relationship_id">R101_REL063</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">uses_status_code</data><data key="edge_target_entity_id">CODE_EDCS_EXR_INITIAL</data><data key="edge_operational_context">EDCS/eView identifies initial EXR case level.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL064" source="APP_EDCS" target="CODE_EDCS_EXR_RECON"><data key="edge_relationship_id">R101_REL064</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">uses_status_code</data><data key="edge_target_entity_id">CODE_EDCS_EXR_RECON</data><data key="edge_operational_context">EDCS/eView identifies EXR reconsideration case level.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL065" source="CODE_NDDSS_CDT5" target="CODE_NDDSS_TYP_CD"><data key="edge_relationship_id">R101_REL065</data><data key="edge_source_entity_id">CODE_NDDSS_CDT5</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">CODE_NDDSS_TYP_CD</data><data key="edge_operational_context">CDT=5 is used with TYP=CD for EXR case receipt.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL066" source="APP_EDCS" target="APP_NDDSS"><data key="edge_relationship_id">R101_REL066</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">transfers_case_to</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_operational_context">Field office establishes EXR in EDCS and transfers case to DDS, where NDDSS case-receipt coding is applied.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">This is a workflow relationship; transport mechanism is not inferred.</data></edge><edge id="R101_REL067" source="CODE_EDCS_SPECIAL_S" target="DATA_CEF_FLAG"><data key="edge_relationship_id">R101_REL067</data><data key="edge_source_entity_id">CODE_EDCS_SPECIAL_S</data><data key="edge_relationship_type">is_type_of</data><data key="edge_target_entity_id">DATA_CEF_FLAG</data><data key="edge_operational_context">Specific EDCS/eView special-handling flag type within the CEF flag mechanism.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL068" source="APP_EDCS" target="CODE_EDCS_SPECIAL_S"><data key="edge_relationship_id">R101_REL068</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_flag</data><data key="edge_target_entity_id">CODE_EDCS_SPECIAL_S</data><data key="edge_operational_context">EDCS supports creation/display of the documented special-handling flag type.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL069" source="CODE_EDCS_SPECIAL_H" target="DATA_CEF_FLAG"><data key="edge_relationship_id">R101_REL069</data><data key="edge_source_entity_id">CODE_EDCS_SPECIAL_H</data><data key="edge_relationship_type">is_type_of</data><data key="edge_target_entity_id">DATA_CEF_FLAG</data><data key="edge_operational_context">Specific EDCS/eView special-handling flag type within the CEF flag mechanism.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL070" source="APP_EDCS" target="CODE_EDCS_SPECIAL_H"><data key="edge_relationship_id">R101_REL070</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_flag</data><data key="edge_target_entity_id">CODE_EDCS_SPECIAL_H</data><data key="edge_operational_context">EDCS supports creation/display of the documented special-handling flag type.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL071" source="CODE_EDCS_SPECIAL_F" target="DATA_CEF_FLAG"><data key="edge_relationship_id">R101_REL071</data><data key="edge_source_entity_id">CODE_EDCS_SPECIAL_F</data><data key="edge_relationship_type">is_type_of</data><data key="edge_target_entity_id">DATA_CEF_FLAG</data><data key="edge_operational_context">Specific EDCS/eView special-handling flag type within the CEF flag mechanism.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL072" source="APP_EDCS" target="CODE_EDCS_SPECIAL_F"><data key="edge_relationship_id">R101_REL072</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_flag</data><data key="edge_target_entity_id">CODE_EDCS_SPECIAL_F</data><data key="edge_operational_context">EDCS supports creation/display of the documented special-handling flag type.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL073" source="CODE_EDCS_SPECIAL_A" target="DATA_CEF_FLAG"><data key="edge_relationship_id">R101_REL073</data><data key="edge_source_entity_id">CODE_EDCS_SPECIAL_A</data><data key="edge_relationship_type">is_type_of</data><data key="edge_target_entity_id">DATA_CEF_FLAG</data><data key="edge_operational_context">Specific EDCS/eView special-handling flag type within the CEF flag mechanism.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL074" source="APP_EDCS" target="CODE_EDCS_SPECIAL_A"><data key="edge_relationship_id">R101_REL074</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_flag</data><data key="edge_target_entity_id">CODE_EDCS_SPECIAL_A</data><data key="edge_operational_context">EDCS supports creation/display of the documented special-handling flag type.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL075" source="UI_EIF_AEQY" target="DB_EIF"><data key="edge_relationship_id">R101_REL075</data><data key="edge_source_entity_id">UI_EIF_AEQY</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_EIF</data><data key="edge_operational_context">AEQY is used to access Employer Identification File employer/EIN information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R101_REL076" source="PROC_ERPS_EIN_VERIFICATION" target="UI_EIF_AEQY"><data key="edge_relationship_id">R101_REL076</data><data key="edge_source_entity_id">PROC_ERPS_EIN_VERIFICATION</data><data key="edge_relationship_type">can_use</data><data key="edge_target_entity_id">UI_EIF_AEQY</data><data key="edge_operational_context">Current EIN-verification procedures permit AEQY/EIF lookup when resolving organizational EIN information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">eRPS also performs automated EIF checking in documented contexts.</data></edge><edge id="R101_REL077" source="REPORT_FAST_FACTS_2026" target="SYS_MBR"><data key="edge_relationship_id">R101_REL077</data><data key="edge_source_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA states cross-program Fast Facts statistics use 100-percent MBR administrative data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Applies to identified cross-program statistical tables, not every table in the publication.</data></edge><edge id="R101_REL078" source="REPORT_FAST_FACTS_2026" target="SYS_SSR"><data key="edge_relationship_id">R101_REL078</data><data key="edge_source_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA states cross-program Fast Facts statistics use 100-percent SSR administrative data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Applies to identified cross-program statistical tables, not every table in the publication.</data></edge><edge id="R106_REL0001" source="R106_E001" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0001</data><data key="edge_source_entity_id">R106_E001</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies ANCR as an MSSICS SSI appeal screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies ANCR as an MSSICS SSI appeal screen.</data></edge><edge id="R106_REL0002" source="R106_E002" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0002</data><data key="edge_source_entity_id">R106_E002</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies RPOC as an MSSICS SSI appeal screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies RPOC as an MSSICS SSI appeal screen.</data></edge><edge id="R106_REL0003" source="R106_E003" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0003</data><data key="edge_source_entity_id">R106_E003</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies ADIS as an MSSICS SSI appeal screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies ADIS as an MSSICS SSI appeal screen.</data></edge><edge id="R106_REL0004" source="R106_E004" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0004</data><data key="edge_source_entity_id">R106_E004</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies APLS as an MSSICS SSI appeal screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies APLS as an MSSICS SSI appeal screen.</data></edge><edge id="R106_REL0005" source="R106_E005" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0005</data><data key="edge_source_entity_id">R106_E005</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies ACAD as an MSSICS SSI appeal screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies ACAD as an MSSICS SSI appeal screen.</data></edge><edge id="R106_REL0006" source="R106_E006" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0006</data><data key="edge_source_entity_id">R106_E006</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies AWDE as an MSSICS SSI appeal screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies AWDE as an MSSICS SSI appeal screen.</data></edge><edge id="R106_REL0007" source="R106_E007" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0007</data><data key="edge_source_entity_id">R106_E007</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies AWDW as an MSSICS SSI appeal screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies AWDW as an MSSICS SSI appeal screen.</data></edge><edge id="R106_REL0008" source="R106_E010" target="R106_E001"><data key="edge_relationship_id">R106_REL0008</data><data key="edge_source_entity_id">R106_E010</data><data key="edge_relationship_type">records_nonclaimant_requestor_in</data><data key="edge_target_entity_id">R106_E001</data><data key="edge_operational_context">Staff document non-claimant requestor on MSSICS ANCR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Staff document non-claimant requestor on MSSICS ANCR.</data></edge><edge id="R106_REL0009" source="R106_E010" target="R106_E002"><data key="edge_relationship_id">R106_REL0009</data><data key="edge_source_entity_id">R106_E010</data><data key="edge_relationship_type">documents_contact_in</data><data key="edge_target_entity_id">R106_E002</data><data key="edge_operational_context">Staff document third-party appeal contact through MSSICS RPOC.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Staff document third-party appeal contact through MSSICS RPOC.</data></edge><edge id="R106_REL0010" source="R106_E010" target="R106_E011"><data key="edge_relationship_id">R106_REL0010</data><data key="edge_source_entity_id">R106_E010</data><data key="edge_relationship_type">followed_by</data><data key="edge_target_entity_id">R106_E011</data><data key="edge_operational_context">Fifteen-working-day follow-up after third-party appeal inquiry.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Fifteen-working-day follow-up after third-party appeal inquiry.</data></edge><edge id="R106_REL0011" source="R106_E010" target="FORM_SSA561"><data key="edge_relationship_id">R106_REL0011</data><data key="edge_source_entity_id">R106_E010</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA561</data><data key="edge_operational_context">SSA-561-U2 supplies written reconsideration request.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-561-U2 supplies written reconsideration request.</data></edge><edge id="R106_REL0012" source="R106_E010" target="R106_E009"><data key="edge_relationship_id">R106_REL0012</data><data key="edge_source_entity_id">R106_E010</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R106_E009</data><data key="edge_operational_context">SSA-1696 appointment where representative involvement is requested.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-1696 appointment where representative involvement is requested.</data></edge><edge id="R106_REL0013" source="R106_E005" target="R106_E003"><data key="edge_relationship_id">R106_REL0013</data><data key="edge_source_entity_id">R106_E005</data><data key="edge_relationship_type">supplies_notice_date_to</data><data key="edge_target_entity_id">R106_E003</data><data key="edge_operational_context">MSSICS checks appeal notice date for late filing and payment-continuation issues.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MSSICS checks appeal notice date for late filing and payment-continuation issues.</data></edge><edge id="R106_REL0014" source="R106_E003" target="R106_E004"><data key="edge_relationship_id">R106_REL0014</data><data key="edge_source_entity_id">R106_E003</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">R106_E004</data><data key="edge_operational_context">Dismissal policy instructs use of ADIS and APLS appeal screens.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Dismissal policy instructs use of ADIS and APLS appeal screens.</data></edge><edge id="R106_REL0015" source="R106_E003" target="R106_E012"><data key="edge_relationship_id">R106_REL0015</data><data key="edge_source_entity_id">R106_E003</data><data key="edge_relationship_type">records_dismissal_requiring</data><data key="edge_target_entity_id">R106_E012</data><data key="edge_operational_context">SSA-L8165-U2 supplies SSI dismissal notice without appeal paragraph.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-L8165-U2 supplies SSI dismissal notice without appeal paragraph.</data></edge><edge id="R106_REL0016" source="R106_E003" target="R106_E006"><data key="edge_relationship_id">R106_REL0016</data><data key="edge_source_entity_id">R106_E003</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">R106_E006</data><data key="edge_operational_context">MSSICS appeal withdrawal requires ADIS and AWDE.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MSSICS appeal withdrawal requires ADIS and AWDE.</data></edge><edge id="R106_REL0017" source="R106_E003" target="R106_E007"><data key="edge_relationship_id">R106_REL0017</data><data key="edge_source_entity_id">R106_E003</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">R106_E007</data><data key="edge_operational_context">MSSICS appeal withdrawal requires ADIS and AWDW.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MSSICS appeal withdrawal requires ADIS and AWDW.</data></edge><edge id="R106_REL0018" source="R106_E008" target="R106_E012"><data key="edge_relationship_id">R106_REL0018</data><data key="edge_source_entity_id">R106_E008</data><data key="edge_relationship_type">handles_non_mssics_appeal_dismissal</data><data key="edge_target_entity_id">R106_E012</data><data key="edge_operational_context">Non-MSSICS dismissal uses UAPD and sends SSA-L8165-U2.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Non-MSSICS dismissal uses UAPD and sends SSA-L8165-U2.</data></edge><edge id="R106_REL0019" source="APP_DPS" target="R106_E010"><data key="edge_relationship_id">R106_REL0019</data><data key="edge_source_entity_id">APP_DPS</data><data key="edge_relationship_type">supports_correspondence_for</data><data key="edge_target_entity_id">R106_E010</data><data key="edge_operational_context">POMS instructs the field office to use DPS for the SSI reconsideration acknowledgment notice.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS instructs the field office to use DPS for the SSI reconsideration acknowledgment notice.</data></edge><edge id="R106_REL0020" source="R106_E014" target="SVC_EVVE"><data key="edge_relationship_id">R106_REL0020</data><data key="edge_source_entity_id">R106_E014</data><data key="edge_relationship_type">triggered_by_unsuccessful_response_from</data><data key="edge_target_entity_id">SVC_EVVE</data><data key="edge_operational_context">Only an unsuccessful Missouri birth-record EVVE response triggers documented manual follow-up.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only an unsuccessful Missouri birth-record EVVE response triggers documented manual follow-up.</data></edge><edge id="R106_REL0021" source="R106_E014" target="APP_DPS"><data key="edge_relationship_id">R106_REL0021</data><data key="edge_source_entity_id">R106_E014</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">SSA instructs field office to create a letter through DPS after unsuccessful EVVE query.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA instructs field office to create a letter through DPS after unsuccessful EVVE query.</data></edge><edge id="R106_REL0022" source="R106_E014" target="FORM_SSA562U3"><data key="edge_relationship_id">R106_REL0022</data><data key="edge_source_entity_id">R106_E014</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA562U3</data><data key="edge_operational_context">SSA-562-U3 accompanies failed EVVE birth verification request.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-562-U3 accompanies failed EVVE birth verification request.</data></edge><edge id="R106_REL0023" source="R106_E014" target="R106_E017"><data key="edge_relationship_id">R106_REL0023</data><data key="edge_source_entity_id">R106_E014</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">R106_E017</data><data key="edge_operational_context">A letter packet contains failed EVVE printout, birth certificate and SSA-562-U3.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">A letter packet contains failed EVVE printout, birth certificate and SSA-562-U3.</data></edge><edge id="R106_REL0024" source="R106_E017" target="R106_E013"><data key="edge_relationship_id">R106_REL0024</data><data key="edge_source_entity_id">R106_E017</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">R106_E013</data><data key="edge_operational_context">Manual verification package sent to Missouri Bureau of Vital Records.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Manual verification package sent to Missouri Bureau of Vital Records.</data></edge><edge id="R106_REL0025" source="R106_E013" target="ORG_STATE_BVS"><data key="edge_relationship_id">R106_REL0025</data><data key="edge_source_entity_id">R106_E013</data><data key="edge_relationship_type">instance_of</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">Missouri agency is a state vital-records authority.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Missouri agency is a state vital-records authority.</data></edge><edge id="R106_REL0026" source="R106_E015" target="R106_E013"><data key="edge_relationship_id">R106_REL0026</data><data key="edge_source_entity_id">R106_E015</data><data key="edge_relationship_type">used_for_request_to</data><data key="edge_target_entity_id">R106_E013</data><data key="edge_operational_context">Form SSA-L706 is a documented signed release option for Missouri vital-record requests.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Form SSA-L706 is a documented signed release option for Missouri vital-record requests.</data></edge><edge id="R106_REL0027" source="R106_E016" target="R106_E013"><data key="edge_relationship_id">R106_REL0027</data><data key="edge_source_entity_id">R106_E016</data><data key="edge_relationship_type">used_for_request_to</data><data key="edge_target_entity_id">R106_E013</data><data key="edge_operational_context">Missouri VS-151 is a state form used for birth/death certification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Missouri VS-151 is a state form used for birth/death certification.</data></edge><edge id="R106_REL0028" source="R106_E019" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0028</data><data key="edge_source_entity_id">R106_E019</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">MSSICS BMEN health expense question shown in specified SSI claims paths.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">MSSICS BMEN health expense question shown in specified SSI claims paths.</data></edge><edge id="R106_REL0029" source="R106_E020" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0029</data><data key="edge_source_entity_id">R106_E020</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">MSSICS BHLT insurance question documented in initial claims and redeterminations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">MSSICS BHLT insurance question documented in initial claims and redeterminations.</data></edge><edge id="R106_REL0030" source="R106_E021" target="APP_MSSICS"><data key="edge_relationship_id">R106_REL0030</data><data key="edge_source_entity_id">R106_E021</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">BTPL is an MSSICS screen, the electronic equivalent of SSA-8019-U2.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">BTPL is an MSSICS screen, the electronic equivalent of SSA-8019-U2.</data></edge><edge id="R106_REL0031" source="R106_E021" target="R106_E022"><data key="edge_relationship_id">R106_REL0031</data><data key="edge_source_entity_id">R106_E021</data><data key="edge_relationship_type">equivalent_electronic_form_of</data><data key="edge_target_entity_id">R106_E022</data><data key="edge_operational_context">BTPL is the electronic equivalent of SSA-8019-U2 under 2016 instructions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">BTPL is the electronic equivalent of SSA-8019-U2 under 2016 instructions.</data></edge><edge id="R106_REL0032" source="R106_E018" target="R106_E019"><data key="edge_relationship_id">R106_REL0032</data><data key="edge_source_entity_id">R106_E018</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R106_E019</data><data key="edge_operational_context">Health expenses screening controls when to collect TPL allegations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Health expenses screening controls when to collect TPL allegations.</data></edge><edge id="R106_REL0033" source="R106_E018" target="R106_E020"><data key="edge_relationship_id">R106_REL0033</data><data key="edge_source_entity_id">R106_E018</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R106_E020</data><data key="edge_operational_context">Coverage allegation directs information collection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Coverage allegation directs information collection.</data></edge><edge id="R106_REL0034" source="R106_E018" target="R106_E021"><data key="edge_relationship_id">R106_REL0034</data><data key="edge_source_entity_id">R106_E018</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R106_E021</data><data key="edge_operational_context">BTPL captures insurance/other liability details.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">BTPL captures insurance/other liability details.</data></edge><edge id="R106_REL0035" source="R106_E018" target="R106_E022"><data key="edge_relationship_id">R106_REL0035</data><data key="edge_source_entity_id">R106_E018</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R106_E022</data><data key="edge_operational_context">Paper fallback and non-MSSICS SSI applications use SSA-8019-U2.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Paper fallback and non-MSSICS SSI applications use SSA-8019-U2.</data></edge><edge id="R106_REL0036" source="R106_E021" target="R106_E023"><data key="edge_relationship_id">R106_REL0036</data><data key="edge_source_entity_id">R106_E021</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">R106_E023</data><data key="edge_operational_context">2016 POMS describes free-format insurer/attorney and liable-party address fields.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">2016 POMS describes free-format insurer/attorney and liable-party address fields.</data></edge><edge id="R106_REL0037" source="R106_E022" target="R106_E024"><data key="edge_relationship_id">R106_REL0037</data><data key="edge_source_entity_id">R106_E022</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">R106_E024</data><data key="edge_operational_context">Paper SSA-8019-U2 lists SSI claimant contact address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Paper SSA-8019-U2 lists SSI claimant contact address.</data></edge><edge id="R106_REL0038" source="R106_E022" target="R106_E023"><data key="edge_relationship_id">R106_REL0038</data><data key="edge_source_entity_id">R106_E022</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">R106_E023</data><data key="edge_operational_context">Paper form requests insurer and third-party legal addresses.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Paper form requests insurer and third-party legal addresses.</data></edge><edge id="R106_REL0039" source="R106_E018" target="R106_E025"><data key="edge_relationship_id">R106_REL0039</data><data key="edge_source_entity_id">R106_E018</data><data key="edge_relationship_type">sends_allowed_case_information_via</data><data key="edge_target_entity_id">R106_E025</data><data key="edge_operational_context">TPL information forwarded to State Medicaid agency for permitted cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">TPL information forwarded to State Medicaid agency for permitted cases.</data></edge><edge id="R106_REL0040" source="R106_E025" target="ORG_STATE_MEDICAID"><data key="edge_relationship_id">R106_REL0040</data><data key="edge_source_entity_id">R106_E025</data><data key="edge_relationship_type">supplies_details_to</data><data key="edge_target_entity_id">ORG_STATE_MEDICAID</data><data key="edge_operational_context">Allowed TPL cases sent to state Medicaid agency through documented paper/electronic pathways.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Allowed TPL cases sent to state Medicaid agency through documented paper/electronic pathways.</data></edge><edge id="R106_REL0041" source="R106_E025" target="R106_E022"><data key="edge_relationship_id">R106_REL0041</data><data key="edge_source_entity_id">R106_E025</data><data key="edge_relationship_type">may_use_paper_fallback</data><data key="edge_target_entity_id">R106_E022</data><data key="edge_operational_context">Incomplete or non-electronic cases require paper SSA-8019-U2 state routing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Incomplete or non-electronic cases require paper SSA-8019-U2 state routing.</data></edge><edge id="R106_REL0042" source="R106_E026" target="APP_CCE"><data key="edge_relationship_id">R106_REL0042</data><data key="edge_source_entity_id">R106_E026</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Dallas regional instructions refer to CCE TPL page.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Dallas regional instructions refer to CCE TPL page.</data></edge><edge id="R106_REL0043" source="R106_E026" target="R106_E025"><data key="edge_relationship_id">R106_REL0043</data><data key="edge_source_entity_id">R106_E026</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R106_E025</data><data key="edge_operational_context">Regional CCE input provides electronically transmitted TPL data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Regional CCE input provides electronically transmitted TPL data.</data></edge><edge id="R106_REL0044" source="R106_E018" target="PROC_1634_MEDICAID"><data key="edge_relationship_id">R106_REL0044</data><data key="edge_source_entity_id">R106_E018</data><data key="edge_relationship_type">conditional_part_of</data><data key="edge_target_entity_id">PROC_1634_MEDICAID</data><data key="edge_operational_context">TPL collection applies to Section 1634 Medicaid eligibility coordination.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">TPL collection applies to Section 1634 Medicaid eligibility coordination.</data></edge><edge id="R106_REL0045" source="ORG_SSA_OAG" target="R106_E027"><data key="edge_relationship_id">R106_REL0045</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">identifies_contract_funding_document</data><data key="edge_target_entity_id">R106_E027</data><data key="edge_operational_context">OAG instructs contractors to inspect most recent funding documents in the documented 2025 contingency guidance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">OAG instructs contractors to inspect most recent funding documents in the documented 2025 contingency guidance.</data></edge><edge id="R106_REL0046" source="ORG_SSA_OAG" target="R106_E028"><data key="edge_relationship_id">R106_REL0046</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">identifies_contract_funding_document</data><data key="edge_target_entity_id">R106_E028</data><data key="edge_operational_context">OAG instructs contractors to inspect most recent funding documents in the documented 2025 contingency guidance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">OAG instructs contractors to inspect most recent funding documents in the documented 2025 contingency guidance.</data></edge><edge id="R106_REL0047" source="ORG_SSA_OAG" target="R106_E029"><data key="edge_relationship_id">R106_REL0047</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">identifies_contract_funding_document</data><data key="edge_target_entity_id">R106_E029</data><data key="edge_operational_context">OAG instructs contractors to inspect most recent funding documents in the documented 2025 contingency guidance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">OAG instructs contractors to inspect most recent funding documents in the documented 2025 contingency guidance.</data></edge><edge id="R106_REL0048" source="ORG_SSA_OAG" target="R106_E030"><data key="edge_relationship_id">R106_REL0048</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">establishes_authority_for</data><data key="edge_target_entity_id">R106_E030</data><data key="edge_operational_context">OAG states contracting officers, not CORs, determine contract continuation during lapse scenarios.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">OAG states contracting officers, not CORs, determine contract continuation during lapse scenarios.</data></edge><edge id="R106_REL0049" source="ORG_SSA_OAG" target="R106_E031"><data key="edge_relationship_id">R106_REL0049</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R106_E031</data><data key="edge_operational_context">OAG public page links OFPP RFO FAQ and explains initiative; does not establish exact internal acquisition-system modifications.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">OAG public page links OFPP RFO FAQ and explains initiative; does not establish exact internal acquisition-system modifications.</data></edge><edge id="R106_REL0050" source="R106_E032" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R106_REL0050</data><data key="edge_source_entity_id">R106_E032</data><data key="edge_relationship_type">delivered_through</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA announced eSignature/Upload Documents as a combined supported online option.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA announced eSignature/Upload Documents as a combined supported online option.</data></edge><edge id="R106_REL0051" source="R106_E033" target="R106_E032"><data key="edge_relationship_id">R106_REL0051</data><data key="edge_source_entity_id">R106_E033</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">R106_E032</data><data key="edge_operational_context">SSA representative sends customer a digital request to begin selected form/evidence submission.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA representative sends customer a digital request to begin selected form/evidence submission.</data></edge><edge id="R106_REL0052" source="R106_E033" target="R106_E034"><data key="edge_relationship_id">R106_REL0052</data><data key="edge_source_entity_id">R106_E033</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R106_E034</data><data key="edge_operational_context">Customer link is the documented entry point for requested electronic submission.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Customer link is the documented entry point for requested electronic submission.</data></edge><edge id="R106_REL0053" source="R106_E032" target="FORM_SSA789"><data key="edge_relationship_id">R106_REL0053</data><data key="edge_source_entity_id">R106_E032</data><data key="edge_relationship_type">contemporaneous_signature_removal_mentions</data><data key="edge_target_entity_id">FORM_SSA789</data><data key="edge_operational_context">SSA 2024 modernization release separately identifies removal of SSA-789 signature requirement, not signature collection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA 2024 modernization release separately identifies removal of SSA-789 signature requirement, not signature collection.</data></edge><edge id="R106_REL0054" source="R106_E032" target="FORM_SSA827"><data key="edge_relationship_id">R106_REL0054</data><data key="edge_source_entity_id">R106_E032</data><data key="edge_relationship_type">supports_electronic_signature_for</data><data key="edge_target_entity_id">FORM_SSA827</data><data key="edge_operational_context">SSA announced electronic signing/submission for SSA-827 among eligible forms.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA announced electronic signing/submission for SSA-827 among eligible forms.</data></edge><edge id="R106_REL0055" source="R106_E035" target="FORM_SSA454BK"><data key="edge_relationship_id">R106_REL0055</data><data key="edge_source_entity_id">R106_E035</data><data key="edge_relationship_type">lists_identity_stepup_for</data><data key="edge_target_entity_id">FORM_SSA454BK</data><data key="edge_operational_context">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data></edge><edge id="R106_REL0056" source="R106_E035" target="FORM_SSA827"><data key="edge_relationship_id">R106_REL0056</data><data key="edge_source_entity_id">R106_E035</data><data key="edge_relationship_type">lists_identity_stepup_for</data><data key="edge_target_entity_id">FORM_SSA827</data><data key="edge_operational_context">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data></edge><edge id="R106_REL0057" source="R106_E035" target="FORM_SSA_2574"><data key="edge_relationship_id">R106_REL0057</data><data key="edge_source_entity_id">R106_E035</data><data key="edge_relationship_type">lists_identity_stepup_for</data><data key="edge_target_entity_id">FORM_SSA_2574</data><data key="edge_operational_context">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data></edge><edge id="R106_REL0058" source="R106_E035" target="FORM_SSA2935"><data key="edge_relationship_id">R106_REL0058</data><data key="edge_source_entity_id">R106_E035</data><data key="edge_relationship_type">lists_identity_stepup_for</data><data key="edge_target_entity_id">FORM_SSA2935</data><data key="edge_operational_context">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data></edge><edge id="R106_REL0059" source="R106_E035" target="FORM_SSA8510"><data key="edge_relationship_id">R106_REL0059</data><data key="edge_source_entity_id">R106_E035</data><data key="edge_relationship_type">lists_identity_stepup_for</data><data key="edge_target_entity_id">FORM_SSA8510</data><data key="edge_operational_context">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Forms catalog flags this form for additional electronic-submission identity verification.</data></edge><edge id="R106_REL0060" source="R106_E035" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R106_REL0060</data><data key="edge_source_entity_id">R106_E035</data><data key="edge_relationship_type">controls_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Catalog says listed forms need additional identity verification for electronic submission, not that all can be submitted without conditions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Catalog says listed forms need additional identity verification for electronic submission, not that all can be submitted without conditions.</data></edge><edge id="R106_REL0061" source="SYS_MBR" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R106_REL0061</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">documented_source_for</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">August 2026 Monthly Statistical Snapshot uses MBR 100-percent administrative data in beneficiary count table.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">August 2026 Monthly Statistical Snapshot uses MBR 100-percent administrative data in beneficiary count table.</data></edge><edge id="R106_REL0062" source="SYS_SSR" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R106_REL0062</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">documented_source_for</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">August 2026 Monthly Statistical Snapshot uses SSR 100-percent administrative data in beneficiary count table.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">August 2026 Monthly Statistical Snapshot uses SSR 100-percent administrative data in beneficiary count table.</data></edge><edge id="R107_REL0001" source="R107_E001" target="APP_EAFI"><data key="edge_relationship_id">R107_REL0001</data><data key="edge_source_entity_id">R107_E001</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EAFI</data><data key="edge_operational_context">SSI Claims eAFI is the named subsystem used for mandatory FI verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI Claims eAFI is the named subsystem used for mandatory FI verification.</data></edge><edge id="R107_REL0002" source="APP_EAFI" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R107_REL0002</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">POMS explicitly calls eAFI subsystem a component of the SSI Claims system.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly calls eAFI subsystem a component of the SSI Claims system.</data></edge><edge id="R107_REL0003" source="APP_E4641" target="APP_EAFI"><data key="edge_relationship_id">R107_REL0003</data><data key="edge_source_entity_id">APP_E4641</data><data key="edge_relationship_type">complements</data><data key="edge_target_entity_id">APP_EAFI</data><data key="edge_operational_context">SSA identifies eAFI and e4641 website as the two main AFI components.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA identifies eAFI and e4641 website as the two main AFI components.</data></edge><edge id="R107_REL0004" source="R107_E001" target="R107_E002"><data key="edge_relationship_id">R107_REL0004</data><data key="edge_source_entity_id">R107_E001</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R107_E002</data><data key="edge_operational_context">EM-25046 REV requires geographic search for potentially eligible SSI initial allowances.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EM-25046 REV requires geographic search for potentially eligible SSI initial allowances.</data></edge><edge id="R107_REL0005" source="R107_E001" target="R107_E003"><data key="edge_relationship_id">R107_REL0005</data><data key="edge_source_entity_id">R107_E001</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R107_E003</data><data key="edge_operational_context">EM-25046 REV requires applicable relationship-related searches during SSI allowance verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EM-25046 REV requires applicable relationship-related searches during SSI allowance verification.</data></edge><edge id="R107_REL0006" source="R107_E001" target="R107_E004"><data key="edge_relationship_id">R107_REL0006</data><data key="edge_source_entity_id">R107_E001</data><data key="edge_relationship_type">may_have_pending</data><data key="edge_target_entity_id">R107_E004</data><data key="edge_operational_context">Policy permits specified outstanding sub-request/geographic responses without delaying adjudication.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Policy permits specified outstanding sub-request/geographic responses without delaying adjudication.</data></edge><edge id="R107_REL0007" source="R107_E002" target="EX_AFI_FI"><data key="edge_relationship_id">R107_REL0007</data><data key="edge_source_entity_id">R107_E002</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Geographic search is an AFI account verification request/response context.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Geographic search is an AFI account verification request/response context.</data></edge><edge id="R107_REL0008" source="R107_E003" target="EX_AFI_FI"><data key="edge_relationship_id">R107_REL0008</data><data key="edge_source_entity_id">R107_E003</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Relationship-related search is within AFI request scope.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship-related search is within AFI request scope.</data></edge><edge id="R107_REL0009" source="R107_E004" target="EX_AFI_FI"><data key="edge_relationship_id">R107_REL0009</data><data key="edge_source_entity_id">R107_E004</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Sub-request response is an AFI verification artifact.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Sub-request response is an AFI verification artifact.</data></edge><edge id="R107_REL0010" source="R107_E001" target="PROC_PERC"><data key="edge_relationship_id">R107_REL0010</data><data key="edge_source_entity_id">R107_E001</data><data key="edge_relationship_type">developed_during</data><data key="edge_target_entity_id">PROC_PERC</data><data key="edge_operational_context">Deferred SSI disability claims complete FI verification at PERC.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Deferred SSI disability claims complete FI verification at PERC.</data></edge><edge id="R107_REL0011" source="R107_E001" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R107_REL0011</data><data key="edge_source_entity_id">R107_E001</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">All SSI initial allowances since May 4 2026 subject to policy scope.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">All SSI initial allowances since May 4 2026 subject to policy scope.</data></edge><edge id="R107_REL0012" source="R107_E007" target="R107_E006"><data key="edge_relationship_id">R107_REL0012</data><data key="edge_source_entity_id">R107_E007</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R107_E006</data><data key="edge_operational_context">Nonparticipating FI verification uses the mailed/faxed paper SSA-4641; no electronic e4641 website dependency inferred.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Nonparticipating FI verification uses the mailed/faxed paper SSA-4641; no electronic e4641 website dependency inferred.</data></edge><edge id="R107_REL0013" source="R107_E007" target="ORG_BENEFICIARY_FI"><data key="edge_relationship_id">R107_REL0013</data><data key="edge_source_entity_id">R107_E007</data><data key="edge_relationship_type">communicates_with</data><data key="edge_target_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_operational_context">Mail or fax paper verification request to financial institution that does not participate electronically.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mail or fax paper verification request to financial institution that does not participate electronically.</data></edge><edge id="R107_REL0014" source="R107_E005" target="ORG_BENEFICIARY_FI"><data key="edge_relationship_id">R107_REL0014</data><data key="edge_source_entity_id">R107_E005</data><data key="edge_relationship_type">follows_up_with</data><data key="edge_target_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_operational_context">For participating FI, AFI vendor liaises with FI rather than technicians contacting them directly.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">For participating FI, AFI vendor liaises with FI rather than technicians contacting them directly.</data></edge><edge id="R107_REL0015" source="R107_E005" target="EX_AFI_FI"><data key="edge_relationship_id">R107_REL0015</data><data key="edge_source_entity_id">R107_E005</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Vendor liaison is documented for FI electronic-verification exceptions, not as an asserted vendor implementation of the whole exchange.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Vendor liaison is documented for FI electronic-verification exceptions, not as an asserted vendor implementation of the whole exchange.</data></edge><edge id="R107_REL0016" source="R107_E008" target="DATA_FI_BANK_STATEMENT_EVIDENCE"><data key="edge_relationship_id">R107_REL0016</data><data key="edge_source_entity_id">R107_E008</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_FI_BANK_STATEMENT_EVIDENCE</data><data key="edge_operational_context">Bank statements accepted as alternative to AFI response subject to completeness and coverage requirements.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Bank statements accepted as alternative to AFI response subject to completeness and coverage requirements.</data></edge><edge id="R107_REL0017" source="R107_E008" target="EX_AFI_FI"><data key="edge_relationship_id">R107_REL0017</data><data key="edge_source_entity_id">R107_E008</data><data key="edge_relationship_type">reconciles_later</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">AFI results received after adjudication handled as stand-alone posteligibility matter.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">AFI results received after adjudication handled as stand-alone posteligibility matter.</data></edge><edge id="R107_REL0018" source="R107_E009" target="R107_E001"><data key="edge_relationship_id">R107_REL0018</data><data key="edge_source_entity_id">R107_E009</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">R107_E001</data><data key="edge_operational_context">FI balance verification can reach up to 25 prior months; interval is not evidence of storage retention.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FI balance verification can reach up to 25 prior months; interval is not evidence of storage retention.</data></edge><edge id="R107_REL0019" source="R107_E009" target="DATA_FI_BALANCE_HISTORY"><data key="edge_relationship_id">R107_REL0019</data><data key="edge_source_entity_id">R107_E009</data><data key="edge_relationship_type">describes</data><data key="edge_target_entity_id">DATA_FI_BALANCE_HISTORY</data><data key="edge_operational_context">Balance-history request window concerns historical balances received from financial institutions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Balance-history request window concerns historical balances received from financial institutions.</data></edge><edge id="R107_REL0020" source="R107_E010" target="DATA_FI_BALANCE_HISTORY"><data key="edge_relationship_id">R107_REL0020</data><data key="edge_source_entity_id">R107_E010</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">DATA_FI_BALANCE_HISTORY</data><data key="edge_operational_context">First-of-month account resource uses FI month-opening or previous month-ending balance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">First-of-month account resource uses FI month-opening or previous month-ending balance.</data></edge><edge id="R107_REL0021" source="R107_E010" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">R107_REL0021</data><data key="edge_source_entity_id">R107_E010</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">Resource amount belongs to financial account development in CCE; no direct AFI database write path inferred.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Resource amount belongs to financial account development in CCE; no direct AFI database write path inferred.</data></edge><edge id="R107_REL0022" source="R107_E011" target="EX_AFI_FI"><data key="edge_relationship_id">R107_REL0022</data><data key="edge_source_entity_id">R107_E011</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Waiver FI account verification responses may support SSI months with required permission.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Waiver FI account verification responses may support SSI months with required permission.</data></edge><edge id="R107_REL0023" source="R107_E011" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">R107_REL0023</data><data key="edge_source_entity_id">R107_E011</data><data key="edge_relationship_type">documents_in</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">Verified FI balance months may be recorded on CCE FI account resource screen subject to permission.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Verified FI balance months may be recorded on CCE FI account resource screen subject to permission.</data></edge><edge id="R107_REL0024" source="R107_E012" target="UI_SSI_FI_PERMISSION"><data key="edge_relationship_id">R107_REL0024</data><data key="edge_source_entity_id">R107_E012</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">UI_SSI_FI_PERMISSION</data><data key="edge_operational_context">SSI Claims FI Permission page records permission status and collection date.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI Claims FI Permission page records permission status and collection date.</data></edge><edge id="R107_REL0025" source="R107_E012" target="EX_AFI_FI"><data key="edge_relationship_id">R107_REL0025</data><data key="edge_source_entity_id">R107_E012</data><data key="edge_relationship_type">controls_access_to</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Financial permission is eligibility condition and legal prerequisite for SSA to request FI records.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Financial permission is eligibility condition and legal prerequisite for SSA to request FI records.</data></edge><edge id="R107_REL0026" source="R107_E013" target="R107_E012"><data key="edge_relationship_id">R107_REL0026</data><data key="edge_source_entity_id">R107_E013</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R107_E012</data><data key="edge_operational_context">Permission persists until specified prospective termination event.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Permission persists until specified prospective termination event.</data></edge><edge id="R107_REL0027" source="R107_E014" target="UI_SSI_FI_PERMISSION"><data key="edge_relationship_id">R107_REL0027</data><data key="edge_source_entity_id">R107_E014</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">UI_SSI_FI_PERMISSION</data><data key="edge_operational_context">Good-cause exception for missing deemor permission captured on the FI Permission page.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Good-cause exception for missing deemor permission captured on the FI Permission page.</data></edge><edge id="R107_REL0028" source="R107_E015" target="R107_E014"><data key="edge_relationship_id">R107_REL0028</data><data key="edge_source_entity_id">R107_E015</data><data key="edge_relationship_type">establishes</data><data key="edge_target_entity_id">R107_E014</data><data key="edge_operational_context">Documented harassment/abuse or endangerment can justify deemor consent exception.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Documented harassment/abuse or endangerment can justify deemor consent exception.</data></edge><edge id="R107_REL0029" source="R107_E015" target="APP_EVID"><data key="edge_relationship_id">R107_REL0029</data><data key="edge_source_entity_id">R107_E015</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Proof and good-cause reasoning can be documented in EVID or Report of Contact.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Proof and good-cause reasoning can be documented in EVID or Report of Contact.</data></edge><edge id="R107_REL0030" source="R107_E016" target="R107_E014"><data key="edge_relationship_id">R107_REL0030</data><data key="edge_source_entity_id">R107_E016</data><data key="edge_relationship_type">establishes</data><data key="edge_target_entity_id">R107_E014</data><data key="edge_operational_context">Claimant cooperation and SSA attempts documented for possible deemor failure-to-cooperate exception.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Claimant cooperation and SSA attempts documented for possible deemor failure-to-cooperate exception.</data></edge><edge id="R107_REL0031" source="R107_E016" target="UI_SSI_PERSON_STATEMENT"><data key="edge_relationship_id">R107_REL0031</data><data key="edge_source_entity_id">R107_E016</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">UI_SSI_PERSON_STATEMENT</data><data key="edge_operational_context">Signed claimant description can be recorded as SSI Claims Person Statement for noncooperation development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Signed claimant description can be recorded as SSI Claims Person Statement for noncooperation development.</data></edge><edge id="R107_REL0032" source="R107_E016" target="FORM_SSA795"><data key="edge_relationship_id">R107_REL0032</data><data key="edge_source_entity_id">R107_E016</data><data key="edge_relationship_type">can_use</data><data key="edge_target_entity_id">FORM_SSA795</data><data key="edge_operational_context">Signed SSA-795 may document good-faith attempts by claimant to obtain deemor consent.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Signed SSA-795 may document good-faith attempts by claimant to obtain deemor consent.</data></edge><edge id="R107_REL0033" source="R107_E017" target="APP_DPS"><data key="edge_relationship_id">R107_REL0033</data><data key="edge_source_entity_id">R107_E017</data><data key="edge_relationship_type">produced_by</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">DPS general section contains claimant version of financial permission request letter.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DPS general section contains claimant version of financial permission request letter.</data></edge><edge id="R107_REL0034" source="R107_E018" target="APP_DPS"><data key="edge_relationship_id">R107_REL0034</data><data key="edge_source_entity_id">R107_E018</data><data key="edge_relationship_type">produced_by</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">DPS general section contains deemor version with separate language.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DPS general section contains deemor version with separate language.</data></edge><edge id="R107_REL0035" source="R107_E019" target="R107_E017"><data key="edge_relationship_id">R107_REL0035</data><data key="edge_source_entity_id">R107_E019</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">R107_E017</data><data key="edge_operational_context">Financial permission claimant request controlled with 15-day follow-up.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Financial permission claimant request controlled with 15-day follow-up.</data></edge><edge id="R107_REL0036" source="R107_E019" target="R107_E018"><data key="edge_relationship_id">R107_REL0036</data><data key="edge_source_entity_id">R107_E019</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">R107_E018</data><data key="edge_operational_context">Deemor permission request controlled with 15-day follow-up.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Deemor permission request controlled with 15-day follow-up.</data></edge><edge id="R107_REL0037" source="R107_E019" target="APP_MDW_AI"><data key="edge_relationship_id">R107_REL0037</data><data key="edge_source_entity_id">R107_E019</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">Non-SSI-Claims cases use Modernized Development Worksheet 15-day tickle, not an inferred case-diary table.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Non-SSI-Claims cases use Modernized Development Worksheet 15-day tickle, not an inferred case-diary table.</data></edge><edge id="R107_REL0038" source="R107_E022" target="APP_DPS"><data key="edge_relationship_id">R107_REL0038</data><data key="edge_source_entity_id">R107_E022</data><data key="edge_relationship_type">produced_by</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Manual FI-permission denial notice sourced from DPS initial claims section.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Manual FI-permission denial notice sourced from DPS initial claims section.</data></edge><edge id="R107_REL0039" source="R107_E022" target="APP_ORS"><data key="edge_relationship_id">R107_REL0039</data><data key="edge_source_entity_id">R107_E022</data><data key="edge_relationship_type">retained_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Copy of manual SSI financial-permission denial notice is sent to Online Retrieval System.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Copy of manual SSI financial-permission denial notice is sent to Online Retrieval System.</data></edge><edge id="R107_REL0040" source="R107_E023" target="APP_DPS"><data key="edge_relationship_id">R107_REL0040</data><data key="edge_source_entity_id">R107_E023</data><data key="edge_relationship_type">produced_by</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Manual FI-permission suspension notice sourced from DPS post-entitlement section.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Manual FI-permission suspension notice sourced from DPS post-entitlement section.</data></edge><edge id="R107_REL0041" source="R107_E023" target="APP_ORS"><data key="edge_relationship_id">R107_REL0041</data><data key="edge_source_entity_id">R107_E023</data><data key="edge_relationship_type">retained_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Copy of manual SSI financial-permission suspension notice is sent to Online Retrieval System.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Copy of manual SSI financial-permission suspension notice is sent to Online Retrieval System.</data></edge><edge id="R107_REL0042" source="R107_E020" target="R107_E022"><data key="edge_relationship_id">R107_REL0042</data><data key="edge_source_entity_id">R107_E020</data><data key="edge_relationship_type">used_for</data><data key="edge_target_entity_id">R107_E022</data><data key="edge_operational_context">SSI N18 denial for failure to give financial permission requires manual denial notice.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI N18 denial for failure to give financial permission requires manual denial notice.</data></edge><edge id="R107_REL0043" source="R107_E021" target="R107_E023"><data key="edge_relationship_id">R107_REL0043</data><data key="edge_source_entity_id">R107_E021</data><data key="edge_relationship_type">used_for</data><data key="edge_target_entity_id">R107_E023</data><data key="edge_operational_context">SSI N05 suspension for refusal/cancellation financial permission requires manual suspension notice.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI N05 suspension for refusal/cancellation financial permission requires manual suspension notice.</data></edge><edge id="R107_REL0044" source="R107_E020" target="SYS_SSR"><data key="edge_relationship_id">R107_REL0044</data><data key="edge_source_entity_id">R107_E020</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Policy directs appropriate denial status and financial-permission explanation to SSI record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Policy directs appropriate denial status and financial-permission explanation to SSI record.</data></edge><edge id="R107_REL0045" source="R107_E021" target="SYS_SSR"><data key="edge_relationship_id">R107_REL0045</data><data key="edge_source_entity_id">R107_E021</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Policy directs posteligibility financial-permission suspension and remarks to SSI record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Policy directs posteligibility financial-permission suspension and remarks to SSI record.</data></edge><edge id="R107_REL0046" source="R107_E024" target="SYS_SSR"><data key="edge_relationship_id">R107_REL0046</data><data key="edge_source_entity_id">R107_E024</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR remarks document when financial permission refused and whether deemor good cause absent.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSR remarks document when financial permission refused and whether deemor good cause absent.</data></edge><edge id="R107_REL0047" source="R107_E025" target="R107_E012"><data key="edge_relationship_id">R107_REL0047</data><data key="edge_source_entity_id">R107_E025</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">R107_E012</data><data key="edge_operational_context">Financial permission statuses/dated changes recorded on FI Permission page iterations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Financial permission statuses/dated changes recorded on FI Permission page iterations.</data></edge><edge id="R107_REL0048" source="R107_E025" target="UI_SSI_FI_PERMISSION"><data key="edge_relationship_id">R107_REL0048</data><data key="edge_source_entity_id">R107_E025</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_SSI_FI_PERMISSION</data><data key="edge_operational_context">SSI Claims may require second iteration or manual reseed if page iterations exhausted.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI Claims may require second iteration or manual reseed if page iterations exhausted.</data></edge><edge id="R107_REL0049" source="R107_E026" target="APP_POS"><data key="edge_relationship_id">R107_REL0049</data><data key="edge_source_entity_id">R107_E026</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">PEWE is a Post-Entitlement System work/earnings processing screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PEWE is a Post-Entitlement System work/earnings processing screen.</data></edge><edge id="R107_REL0050" source="R107_E027" target="R107_E026"><data key="edge_relationship_id">R107_REL0050</data><data key="edge_source_entity_id">R107_E027</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R107_E026</data><data key="edge_operational_context">FO/PSC/TSC enter reported closed year earnings, NSMs and SWPs on PEWE.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FO/PSC/TSC enter reported closed year earnings, NSMs and SWPs on PEWE.</data></edge><edge id="R107_REL0051" source="R107_E027" target="PROC_AERO"><data key="edge_relationship_id">R107_REL0051</data><data key="edge_source_entity_id">R107_E027</data><data key="edge_relationship_type">may_precede</data><data key="edge_target_entity_id">PROC_AERO</data><data key="edge_operational_context">If recomputation/AERO pending, ensure required annual earnings reports received first.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">If recomputation/AERO pending, ensure required annual earnings reports received first.</data></edge><edge id="R107_REL0052" source="R107_E028" target="SYS_MEF"><data key="edge_relationship_id">R107_REL0052</data><data key="edge_source_entity_id">R107_E028</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">EIN matching looks at previous and current earnings-year MEF details.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EIN matching looks at previous and current earnings-year MEF details.</data></edge><edge id="R107_REL0053" source="R107_E028" target="APP_EEO"><data key="edge_relationship_id">R107_REL0053</data><data key="edge_source_entity_id">R107_E028</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">APP_EEO</data><data key="edge_operational_context">EIN comparison can defer cases in EEO pass one and two.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EIN comparison can defer cases in EEO pass one and two.</data></edge><edge id="R107_REL0054" source="R107_E028" target="R107_E029"><data key="edge_relationship_id">R107_REL0054</data><data key="edge_source_entity_id">R107_E028</data><data key="edge_relationship_type">defers_cases_into</data><data key="edge_target_entity_id">R107_E029</data><data key="edge_operational_context">RSI finder file collects cases failing EIN match during first two passes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">RSI finder file collects cases failing EIN match during first two passes.</data></edge><edge id="R107_REL0055" source="R107_E029" target="R107_E032"><data key="edge_relationship_id">R107_REL0055</data><data key="edge_source_entity_id">R107_E029</data><data key="edge_relationship_type">reselected_by</data><data key="edge_target_entity_id">R107_E032</data><data key="edge_operational_context">RSI finder file cases considered in subsequent enforcement pass as earnings post.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">RSI finder file cases considered in subsequent enforcement pass as earnings post.</data></edge><edge id="R107_REL0056" source="R107_E032" target="APP_EEO"><data key="edge_relationship_id">R107_REL0056</data><data key="edge_source_entity_id">R107_E032</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_EEO</data><data key="edge_operational_context">EEO annual three-cycle selection in June/September/February.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EEO annual three-cycle selection in June/September/February.</data></edge><edge id="R107_REL0057" source="R107_E032" target="SYS_MBR"><data key="edge_relationship_id">R107_REL0057</data><data key="edge_source_entity_id">R107_E032</data><data key="edge_relationship_type">compares</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">EEO compares beneficiary reported/deduction earnings in MBR against posted earnings in MEF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EEO compares beneficiary reported/deduction earnings in MBR against posted earnings in MEF.</data></edge><edge id="R107_REL0058" source="R107_E032" target="SYS_MEF"><data key="edge_relationship_id">R107_REL0058</data><data key="edge_source_entity_id">R107_E032</data><data key="edge_relationship_type">compares</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">EEO detects MEF changes and late employer wage postings over current/prior three years.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EEO detects MEF changes and late employer wage postings over current/prior three years.</data></edge><edge id="R107_REL0059" source="R107_E032" target="R107_E028"><data key="edge_relationship_id">R107_REL0059</data><data key="edge_source_entity_id">R107_E032</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R107_E028</data><data key="edge_operational_context">First two passes gate selected cases using employer matching.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">First two passes gate selected cases using employer matching.</data></edge><edge id="R107_REL0060" source="R107_E030" target="SYS_MEF"><data key="edge_relationship_id">R107_REL0060</data><data key="edge_source_entity_id">R107_E030</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">TRE comprises covered and noncovered MEF earnings for deduction purposes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">TRE comprises covered and noncovered MEF earnings for deduction purposes.</data></edge><edge id="R107_REL0061" source="R107_E030" target="APP_EEO"><data key="edge_relationship_id">R107_REL0061</data><data key="edge_source_entity_id">R107_E030</data><data key="edge_relationship_type">computed_by</data><data key="edge_target_entity_id">APP_EEO</data><data key="edge_operational_context">EEO computes total earnings for enforcement categories.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EEO computes total earnings for enforcement categories.</data></edge><edge id="R107_REL0062" source="R107_E033" target="R107_E030"><data key="edge_relationship_id">R107_REL0062</data><data key="edge_source_entity_id">R107_E033</data><data key="edge_relationship_type">selected_using</data><data key="edge_target_entity_id">R107_E030</data><data key="edge_operational_context">Potential underpayment based on benefits withheld and enforced earnings.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Potential underpayment based on benefits withheld and enforced earnings.</data></edge><edge id="R107_REL0063" source="R107_E034" target="R107_E030"><data key="edge_relationship_id">R107_REL0063</data><data key="edge_source_entity_id">R107_E034</data><data key="edge_relationship_type">selected_using</data><data key="edge_target_entity_id">R107_E030</data><data key="edge_operational_context">TE 777 category based on earnings against exempt amount and missing annual report.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">TE 777 category based on earnings against exempt amount and missing annual report.</data></edge><edge id="R107_REL0064" source="R107_E035" target="R107_E030"><data key="edge_relationship_id">R107_REL0064</data><data key="edge_source_entity_id">R107_E035</data><data key="edge_relationship_type">selected_using</data><data key="edge_target_entity_id">R107_E030</data><data key="edge_operational_context">EEO overpayment discrepancy uses comparisons to reported and estimated earnings.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EEO overpayment discrepancy uses comparisons to reported and estimated earnings.</data></edge><edge id="R107_REL0065" source="R107_E036" target="R107_E030"><data key="edge_relationship_id">R107_REL0065</data><data key="edge_source_entity_id">R107_E036</data><data key="edge_relationship_type">selected_using</data><data key="edge_target_entity_id">R107_E030</data><data key="edge_operational_context">Manual review triggers include zero/negative earnings, significant differences and NSM/FRA cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Manual review triggers include zero/negative earnings, significant differences and NSM/FRA cases.</data></edge><edge id="R107_REL0066" source="R107_E031" target="R107_E036"><data key="edge_relationship_id">R107_REL0066</data><data key="edge_source_entity_id">R107_E031</data><data key="edge_relationship_type">considered_during</data><data key="edge_target_entity_id">R107_E036</data><data key="edge_operational_context">Field office considers/request current-year estimate during direct contact.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Field office considers/request current-year estimate during direct contact.</data></edge><edge id="R107_REL0067" source="R107_E037" target="SYS_MBR"><data key="edge_relationship_id">R107_REL0067</data><data key="edge_source_entity_id">R107_E037</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Non-service months in MBR inform grace-year earnings-test deduction decisions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Non-service months in MBR inform grace-year earnings-test deduction decisions.</data></edge><edge id="R107_REL0068" source="R107_E037" target="APP_EEO"><data key="edge_relationship_id">R107_REL0068</data><data key="edge_source_entity_id">R107_E037</data><data key="edge_relationship_type">considered_by</data><data key="edge_target_entity_id">APP_EEO</data><data key="edge_operational_context">Enforcement uses existing MBR NSMs in policy-defined grace-year conditions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Enforcement uses existing MBR NSMs in policy-defined grace-year conditions.</data></edge><edge id="R107_REL0069" source="R107_E038" target="SYS_MBR"><data key="edge_relationship_id">R107_REL0069</data><data key="edge_source_entity_id">R107_E038</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">When BOAN wrong, staff correct BOAN on MBR; no Numident update is stated.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">When BOAN wrong, staff correct BOAN on MBR; no Numident update is stated.</data></edge><edge id="R107_REL0070" source="R107_E038" target="APP_EEO"><data key="edge_relationship_id">R107_REL0070</data><data key="edge_source_entity_id">R107_E038</data><data key="edge_relationship_type">triggered_by</data><data key="edge_target_entity_id">APP_EEO</data><data key="edge_operational_context">Earnings-enforcement identity conflict development can reveal incorrect BOAN.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Earnings-enforcement identity conflict development can reveal incorrect BOAN.</data></edge><edge id="R107_REL0071" source="R107_E039" target="SYS_MEF"><data key="edge_relationship_id">R107_REL0071</data><data key="edge_source_entity_id">R107_E039</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Technician verifies correct spelling against beneficiary and MEF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Technician verifies correct spelling against beneficiary and MEF.</data></edge><edge id="R107_REL0072" source="R107_E039" target="SYS_MBR"><data key="edge_relationship_id">R107_REL0072</data><data key="edge_source_entity_id">R107_E039</data><data key="edge_relationship_type">may_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">If MEF surname correct, policy says correct MBR; otherwise MBR unchanged.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">If MEF surname correct, policy says correct MBR; otherwise MBR unchanged.</data></edge><edge id="R107_REL0073" source="R107_E040" target="PROC_AERO"><data key="edge_relationship_id">R107_REL0073</data><data key="edge_source_entity_id">R107_E040</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">PROC_AERO</data><data key="edge_operational_context">Earnings enforcement takes precedence if recomputation may create overpayment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Earnings enforcement takes precedence if recomputation may create overpayment.</data></edge><edge id="R107_REL0074" source="R107_E040" target="APP_EEO"><data key="edge_relationship_id">R107_REL0074</data><data key="edge_source_entity_id">R107_E040</data><data key="edge_relationship_type">depends_on</data><data key="edge_target_entity_id">APP_EEO</data><data key="edge_operational_context">EEO completion precedes requested benefit recomputation for overlapping overpayment cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EEO completion precedes requested benefit recomputation for overlapping overpayment cases.</data></edge><edge id="R107_REL0075" source="R107_E041" target="IFACE_DRPR"><data key="edge_relationship_id">R107_REL0075</data><data key="edge_source_entity_id">R107_E041</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">IFACE_DRPR</data><data key="edge_operational_context">If beneficiary unable to explain discrepancy, stop recovery using DMS DRPR before further development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">If beneficiary unable to explain discrepancy, stop recovery using DMS DRPR before further development.</data></edge><edge id="R107_REL0076" source="R107_E041" target="SYS_MEF"><data key="edge_relationship_id">R107_REL0076</data><data key="edge_source_entity_id">R107_E041</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Beneficiary contest may require source-earnings investigation and employer contact.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Beneficiary contest may require source-earnings investigation and employer contact.</data></edge><edge id="R107_REL0077" source="R107_E042" target="SYS_MBR"><data key="edge_relationship_id">R107_REL0077</data><data key="edge_source_entity_id">R107_E042</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Amended annual report indicator TOER-M is recorded on MBR for EEO selection context.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Amended annual report indicator TOER-M is recorded on MBR for EEO selection context.</data></edge><edge id="R107_REL0078" source="R107_E043" target="APP_POS"><data key="edge_relationship_id">R107_REL0078</data><data key="edge_source_entity_id">R107_E043</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Change in PIA input is a POS action for requested recomputation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Change in PIA input is a POS action for requested recomputation.</data></edge><edge id="R107_REL0079" source="R107_E043" target="R107_E026"><data key="edge_relationship_id">R107_REL0079</data><data key="edge_source_entity_id">R107_E043</data><data key="edge_relationship_type">coordinated_with</data><data key="edge_target_entity_id">R107_E026</data><data key="edge_operational_context">When beneficiary requests recomputation and reports annual earnings, POS processes PEWE and CIP together.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">When beneficiary requests recomputation and reports annual earnings, POS processes PEWE and CIP together.</data></edge><edge id="R107_REL0080" source="APP_EEO" target="APP_T2R"><data key="edge_relationship_id">R107_REL0080</data><data key="edge_source_entity_id">APP_EEO</data><data key="edge_relationship_type">automates_where_eligible</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">Current POMS says EEO automated processing occurs through Title II Redesign.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS says EEO automated processing occurs through Title II Redesign.</data></edge><edge id="R107_REL0081" source="R107_E044" target="APP_ERPS"><data key="edge_relationship_id">R107_REL0081</data><data key="edge_source_entity_id">R107_E044</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Payee selection and manager authorization occur in eRPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Payee selection and manager authorization occur in eRPS.</data></edge><edge id="R107_REL0082" source="R107_E044" target="R107_E045"><data key="edge_relationship_id">R107_REL0082</data><data key="edge_source_entity_id">R107_E044</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R107_E045</data><data key="edge_operational_context">Prior poor performance requires manager approval when selecting applicant.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Prior poor performance requires manager approval when selecting applicant.</data></edge><edge id="R107_REL0083" source="R107_E045" target="APP_ERPS"><data key="edge_relationship_id">R107_REL0083</data><data key="edge_source_entity_id">R107_E045</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Approve Selection appears under eRPS Manager Actions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Approve Selection appears under eRPS Manager Actions.</data></edge><edge id="R107_REL0084" source="R107_E046" target="APP_ERPS"><data key="edge_relationship_id">R107_REL0084</data><data key="edge_source_entity_id">R107_E046</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Selection Required Notes is an eRPS documentation screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Selection Required Notes is an eRPS documentation screen.</data></edge><edge id="R107_REL0085" source="R107_E045" target="R107_E046"><data key="edge_relationship_id">R107_REL0085</data><data key="edge_source_entity_id">R107_E045</data><data key="edge_relationship_type">documented_on</data><data key="edge_target_entity_id">R107_E046</data><data key="edge_operational_context">Manager documents selection authorization on required notes screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Manager documents selection authorization on required notes screen.</data></edge><edge id="R107_REL0086" source="R107_E047" target="UI_ERPS_ADD_NEW_ISSUE"><data key="edge_relationship_id">R107_REL0086</data><data key="edge_source_entity_id">R107_E047</data><data key="edge_relationship_type">created_using</data><data key="edge_target_entity_id">UI_ERPS_ADD_NEW_ISSUE</data><data key="edge_operational_context">Establish three-month review diary in eRPS Add New Issue or another reliable control.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Establish three-month review diary in eRPS Add New Issue or another reliable control.</data></edge><edge id="R107_REL0087" source="R107_E047" target="R107_E048"><data key="edge_relationship_id">R107_REL0087</data><data key="edge_source_entity_id">R107_E047</data><data key="edge_relationship_type">requires_follow_up</data><data key="edge_target_entity_id">R107_E048</data><data key="edge_operational_context">Review poor-performing selected payee through SSA-624-F5 evaluation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Review poor-performing selected payee through SSA-624-F5 evaluation.</data></edge><edge id="R107_REL0088" source="R107_E049" target="SYS_SSR"><data key="edge_relationship_id">R107_REL0088</data><data key="edge_source_entity_id">R107_E049</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI uses SSR diary code/date field for UA poor-performance follow-up.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title XVI uses SSR diary code/date field for UA poor-performance follow-up.</data></edge><edge id="R107_REL0089" source="R107_E049" target="R107_E047"><data key="edge_relationship_id">R107_REL0089</data><data key="edge_source_entity_id">R107_E049</data><data key="edge_relationship_type">complements</data><data key="edge_target_entity_id">R107_E047</data><data key="edge_operational_context">SSR UA diary is an explicitly documented Title XVI alternative control for selected payees.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSR UA diary is an explicitly documented Title XVI alternative control for selected payees.</data></edge><edge id="R107_REL0090" source="R107_E050" target="WORK_SSI_RT_DIARY"><data key="edge_relationship_id">R107_REL0090</data><data key="edge_source_entity_id">R107_E050</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">WORK_SSI_RT_DIARY</data><data key="edge_operational_context">RT diary tracks future redeemability/value of savings bond for resource reevaluation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">RT diary tracks future redeemability/value of savings bond for resource reevaluation.</data></edge><edge id="R107_REL0091" source="R107_E050" target="APP_MSSICS"><data key="edge_relationship_id">R107_REL0091</data><data key="edge_source_entity_id">R107_E050</data><data key="edge_relationship_type">may_be_set_via</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS allows savings bond RT diary through MSSICS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS allows savings bond RT diary through MSSICS.</data></edge><edge id="R107_REL0092" source="R107_E050" target="IFACE_SSI_DIRECT_SSR"><data key="edge_relationship_id">R107_REL0092</data><data key="edge_source_entity_id">R107_E050</data><data key="edge_relationship_type">may_be_set_via</data><data key="edge_target_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_operational_context">POMS allows savings bond RT diary through Direct SSR Update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS allows savings bond RT diary through Direct SSR Update.</data></edge><edge id="R107_REL0093" source="R107_E051" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R107_REL0093</data><data key="edge_source_entity_id">R107_E051</data><data key="edge_relationship_type">publishes_related_values_to</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">Published 2026 family-maximum bend points are also tabulated in OACT Automatic Determinations series.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Published 2026 family-maximum bend points are also tabulated in OACT Automatic Determinations series.</data></edge><edge id="R107_REL0094" source="R107_E052" target="DOM_EARNINGS"><data key="edge_relationship_id">R107_REL0094</data><data key="edge_source_entity_id">R107_E052</data><data key="edge_relationship_type">uses_derived_concepts_from</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Benefit example table uses indexed earnings and AIME concepts but no underlying data extract route specified.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Benefit example table uses indexed earnings and AIME concepts but no underlying data extract route specified.</data></edge><edge id="R107_REL0095" source="R107_E053" target="PROC_OACT_COLA"><data key="edge_relationship_id">R107_REL0095</data><data key="edge_source_entity_id">R107_E053</data><data key="edge_relationship_type">is_related_to</data><data key="edge_target_entity_id">PROC_OACT_COLA</data><data key="edge_operational_context">Estimates illustrate effect of December 2025 cost-of-living adjustment first payable January 2026.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Estimates illustrate effect of December 2025 cost-of-living adjustment first payable January 2026.</data></edge><edge id="R107_REL0096" source="WORK_SSI_IRS_5B_DIARY" target="R107_E001"><data key="edge_relationship_id">R107_REL0096</data><data key="edge_source_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_relationship_type">triggers_mandatory_verification</data><data key="edge_target_entity_id">R107_E001</data><data key="edge_operational_context">Resource-related diary requires FI account verification for SSI RZ/LI even below general $400 tolerance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Resource-related diary requires FI account verification for SSI RZ/LI even below general $400 tolerance.</data></edge><edge id="R107_REL0097" source="WORK_SSI_IRS_5H_DIARY" target="R107_E001"><data key="edge_relationship_id">R107_REL0097</data><data key="edge_source_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_relationship_type">triggers_mandatory_verification</data><data key="edge_target_entity_id">R107_E001</data><data key="edge_operational_context">Resource-related diary requires FI account verification for SSI RZ/LI even below general $400 tolerance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Resource-related diary requires FI account verification for SSI RZ/LI even below general $400 tolerance.</data></edge><edge id="R107_REL0098" source="WORK_SSI_SB_DIARY" target="R107_E001"><data key="edge_relationship_id">R107_REL0098</data><data key="edge_source_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_relationship_type">triggers_mandatory_verification</data><data key="edge_target_entity_id">R107_E001</data><data key="edge_operational_context">Resource-related diary requires FI account verification for SSI RZ/LI even below general $400 tolerance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Resource-related diary requires FI account verification for SSI RZ/LI even below general $400 tolerance.</data></edge><edge id="R107_REL0099" source="DIARY_R8" target="R107_E001"><data key="edge_relationship_id">R107_REL0099</data><data key="edge_source_entity_id">DIARY_R8</data><data key="edge_relationship_type">triggers_mandatory_verification</data><data key="edge_target_entity_id">R107_E001</data><data key="edge_operational_context">Resource-related diary requires FI account verification for SSI RZ/LI even below general $400 tolerance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Resource-related diary requires FI account verification for SSI RZ/LI even below general $400 tolerance.</data></edge><edge id="R108_REL0001" source="APP_MYCOA" target="R108_E001"><data key="edge_relationship_id">R108_REL0001</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">exposes_input_surface</data><data key="edge_target_entity_id">R108_E001</data><data key="edge_operational_context">myCOA entry point is Contact Link under My Profile.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">myCOA entry point is Contact Link under My Profile.</data></edge><edge id="R108_REL0002" source="APP_MYCOA" target="R108_E002"><data key="edge_relationship_id">R108_REL0002</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">enforces_case_eligibility_exclusions</data><data key="edge_target_entity_id">R108_E002</data><data key="edge_operational_context">Self-service address updates exclude payees, prisoners, pending claims/appeals and SSI addresses.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Self-service address updates exclude payees, prisoners, pending claims/appeals and SSI addresses.</data></edge><edge id="R108_REL0003" source="APP_MYCOA" target="R108_E003"><data key="edge_relationship_id">R108_REL0003</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">supports_telephone_only_for_ssi</data><data key="edge_target_entity_id">R108_E003</data><data key="edge_operational_context">SSI and concurrent users can change telephone number, but not mailing address, with listed eligibility statuses.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI and concurrent users can change telephone number, but not mailing address, with listed eligibility statuses.</data></edge><edge id="R108_REL0004" source="APP_MYCOA" target="R108_E004"><data key="edge_relationship_id">R108_REL0004</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">initiates_change_notifications</data><data key="edge_target_entity_id">R108_E004</data><data key="edge_operational_context">Online change confirmation delivered in email, mail and my Social Security message center.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Online change confirmation delivered in email, mail and my Social Security message center.</data></edge><edge id="R108_REL0005" source="R108_E004" target="SVC_MYSSA_MESSAGE_CENTER"><data key="edge_relationship_id">R108_REL0005</data><data key="edge_source_entity_id">R108_E004</data><data key="edge_relationship_type">publishes_receipt_to</data><data key="edge_target_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_operational_context">The customer receives a change receipt in their Message Center.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">The customer receives a change receipt in their Message Center.</data></edge><edge id="R108_REL0006" source="APP_MYCOA" target="APP_T2R"><data key="edge_relationship_id">R108_REL0006</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">supplies_title_ii_change_requests_to</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">T2R processes customer Title II address/telephone input with existing batches.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">T2R processes customer Title II address/telephone input with existing batches.</data></edge><edge id="R108_REL0007" source="APP_T2R" target="SYS_MBR"><data key="edge_relationship_id">R108_REL0007</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">conditionally_posts_title_ii_address_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Validated overnight Title II master-record change; future-effective addresses stay pending until effective month.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Validated overnight Title II master-record change; future-effective addresses stay pending until effective month.</data></edge><edge id="R108_REL0008" source="APP_MYCOA" target="DATA_MYCOA_PENDING_FUTURE_ADDRESS"><data key="edge_relationship_id">R108_REL0008</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">uses_pending_future_effective_address_data</data><data key="edge_target_entity_id">DATA_MYCOA_PENDING_FUTURE_ADDRESS</data><data key="edge_operational_context">Title II online address changes may be scheduled up to 90 days ahead, pending appropriate processing month.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title II online address changes may be scheduled up to 90 days ahead, pending appropriate processing month.</data></edge><edge id="R108_REL0009" source="APP_MYCOA" target="SYS_SSR"><data key="edge_relationship_id">R108_REL0009</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">conditionally_posts_title_xvi_telephone_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Phone changes (not SSI mail address updates) appear in SSR overnight, subject to eligibility.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Phone changes (not SSI mail address updates) appear in SSR overnight, subject to eligibility.</data></edge><edge id="R108_REL0010" source="R108_E002" target="R108_E001"><data key="edge_relationship_id">R108_REL0010</data><data key="edge_source_entity_id">R108_E002</data><data key="edge_relationship_type">restricts_address_submission_to_own_record</data><data key="edge_target_entity_id">R108_E001</data><data key="edge_operational_context">Internet account holder cannot change other family members under same account.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Internet account holder cannot change other family members under same account.</data></edge><edge id="R108_REL0011" source="NOTICE_T2R_COA_CONFIRM" target="R108_E005"><data key="edge_relationship_id">R108_REL0011</data><data key="edge_source_entity_id">NOTICE_T2R_COA_CONFIRM</data><data key="edge_relationship_type">uses_prior_mailing_address</data><data key="edge_target_entity_id">R108_E005</data><data key="edge_operational_context">Fraud warning is mailed to old MBR mailing address regardless of actual payee/beneficiary residence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Fraud warning is mailed to old MBR mailing address regardless of actual payee/beneficiary residence.</data></edge><edge id="R108_REL0012" source="R108_E005" target="DATA_MBR_MAILING_ADDRESS"><data key="edge_relationship_id">R108_REL0012</data><data key="edge_source_entity_id">R108_E005</data><data key="edge_relationship_type">reads_prior_value_from</data><data key="edge_target_entity_id">DATA_MBR_MAILING_ADDRESS</data><data key="edge_operational_context">MBR only stores one address context, which may be representative payee mailing address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MBR only stores one address context, which may be representative payee mailing address.</data></edge><edge id="R108_REL0013" source="NOTICE_T2R_COA_CONFIRM" target="R108_E006"><data key="edge_relationship_id">R108_REL0013</data><data key="edge_source_entity_id">NOTICE_T2R_COA_CONFIRM</data><data key="edge_relationship_type">uses_text_snippets</data><data key="edge_target_entity_id">R108_E006</data><data key="edge_operational_context">Notice includes COA014/COA015/COA016 mandatory warning snippets.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Notice includes COA014/COA015/COA016 mandatory warning snippets.</data></edge><edge id="R108_REL0014" source="R108_E007" target="NOTICE_T2R_COA_CONFIRM"><data key="edge_relationship_id">R108_REL0014</data><data key="edge_source_entity_id">R108_E007</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">NOTICE_T2R_COA_CONFIRM</data><data key="edge_operational_context">Telephone IVR address changes generate T2R standalone anti-fraud confirmation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Telephone IVR address changes generate T2R standalone anti-fraud confirmation.</data></edge><edge id="R108_REL0016" source="APP_T2R" target="NOTICE_T2R_COA_CONFIRM"><data key="edge_relationship_id">R108_REL0016</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">generates_change_fraud_notice</data><data key="edge_target_entity_id">NOTICE_T2R_COA_CONFIRM</data><data key="edge_operational_context">T2R creates standalone COA confirmation after eligible address changes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">T2R creates standalone COA confirmation after eligible address changes.</data></edge><edge id="R108_REL0017" source="DATA_T2R_COA_SKELCOMP" target="R108_E008"><data key="edge_relationship_id">R108_REL0017</data><data key="edge_source_entity_id">DATA_T2R_COA_SKELCOMP</data><data key="edge_relationship_type">was_formatted_by_historical</data><data key="edge_target_entity_id">R108_E008</data><data key="edge_operational_context">Historical pre-October-2022 SKELCOMP-based notice formatting.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Historical pre-October-2022 SKELCOMP-based notice formatting.</data></edge><edge id="R108_REL0018" source="R108_E008" target="APP_CCM"><data key="edge_relationship_id">R108_REL0018</data><data key="edge_source_entity_id">R108_E008</data><data key="edge_relationship_type">was_superseded_by</data><data key="edge_target_entity_id">APP_CCM</data><data key="edge_operational_context">October 2022 T2R transitioned to XML notice file for CCM composition.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">October 2022 T2R transitioned to XML notice file for CCM composition.</data></edge><edge id="R108_REL0019" source="DATA_T2R_COA_XML" target="APP_CCM"><data key="edge_relationship_id">R108_REL0019</data><data key="edge_source_entity_id">DATA_T2R_COA_XML</data><data key="edge_relationship_type">is_composed_into_notices_by</data><data key="edge_target_entity_id">APP_CCM</data><data key="edge_operational_context">New CCM application consumes T2R COA XML file to compose fully formed notice.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">New CCM application consumes T2R COA XML file to compose fully formed notice.</data></edge><edge id="R108_REL0020" source="APP_T2R" target="R108_E009"><data key="edge_relationship_id">R108_REL0020</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">enforces_automated_notice_completion</data><data key="edge_target_entity_id">R108_E009</data><data key="edge_operational_context">T2R does not manually complete partial change-of-address notices with AURORA.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">T2R does not manually complete partial change-of-address notices with AURORA.</data></edge><edge id="R108_REL0021" source="R108_E009" target="DATA_T2R_COA_ERROR_LOG"><data key="edge_relationship_id">R108_REL0021</data><data key="edge_source_entity_id">R108_E009</data><data key="edge_relationship_type">routes_incomplete_notices_to</data><data key="edge_target_entity_id">DATA_T2R_COA_ERROR_LOG</data><data key="edge_operational_context">Incomplete notices are removed from output and recorded for systems staff investigation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Incomplete notices are removed from output and recorded for systems staff investigation.</data></edge><edge id="R108_REL0022" source="APP_T2R" target="SVC_MYSSA_MESSAGE_CENTER"><data key="edge_relationship_id">R108_REL0022</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">supports_myssa_notice_delivery_through</data><data key="edge_target_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_operational_context">October 2022 COA digital Message Center alert uses CCM/MySSA for online notice availability.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">October 2022 COA digital Message Center alert uses CCM/MySSA for online notice availability.</data></edge><edge id="R108_REL0023" source="APP_DATS" target="R108_E010"><data key="edge_relationship_id">R108_REL0023</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">presents_death_alert_code</data><data key="edge_target_entity_id">R108_E010</data><data key="edge_operational_context">Third-party report for beneficiary requires verification</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Third-party report for beneficiary requires verification</data></edge><edge id="R108_REL0024" source="APP_DATS" target="R108_E011"><data key="edge_relationship_id">R108_REL0024</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">presents_death_alert_code</data><data key="edge_target_entity_id">R108_E011</data><data key="edge_operational_context">Death information from non-vital-record state agency requires third-party verification</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Death information from non-vital-record state agency requires third-party verification</data></edge><edge id="R108_REL0025" source="APP_DATS" target="R108_E012"><data key="edge_relationship_id">R108_REL0025</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">presents_death_alert_code</data><data key="edge_target_entity_id">R108_E012</data><data key="edge_operational_context">CMS-origin death report requires third-party verification</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">CMS-origin death report requires third-party verification</data></edge><edge id="R108_REL0026" source="APP_DATS" target="R108_E013"><data key="edge_relationship_id">R108_REL0026</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">presents_death_alert_code</data><data key="edge_target_entity_id">R108_E013</data><data key="edge_operational_context">VA-origin death report requires third-party verification</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">VA-origin death report requires third-party verification</data></edge><edge id="R108_REL0027" source="APP_DATS" target="R108_E014"><data key="edge_relationship_id">R108_REL0027</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">presents_death_alert_code</data><data key="edge_target_entity_id">R108_E014</data><data key="edge_operational_context">OPM-origin death report requires third-party verification</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">OPM-origin death report requires third-party verification</data></edge><edge id="R108_REL0028" source="APP_DATS" target="R108_E015"><data key="edge_relationship_id">R108_REL0028</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">presents_death_alert_code</data><data key="edge_target_entity_id">R108_E015</data><data key="edge_operational_context">DIPS report name mismatch requires development</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DIPS report name mismatch requires development</data></edge><edge id="R108_REL0029" source="APP_DATS" target="R108_E016"><data key="edge_relationship_id">R108_REL0029</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">presents_death_alert_code</data><data key="edge_target_entity_id">R108_E016</data><data key="edge_operational_context">Reported death requires a DIPS transaction if not already entered</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Reported death requires a DIPS transaction if not already entered</data></edge><edge id="R108_REL0030" source="APP_DATS" target="R108_E017"><data key="edge_relationship_id">R108_REL0030</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">lists_monthly_numident_payment_discrepancy</data><data key="edge_target_entity_id">R108_E017</data><data key="edge_operational_context">Numident death not posted to payment record appears on separate monthly NUMI alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Numident death not posted to payment record appears on separate monthly NUMI alert.</data></edge><edge id="R108_REL0031" source="APP_DATS" target="R108_E018"><data key="edge_relationship_id">R108_REL0031</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">refreshes_dips_alerts_using</data><data key="edge_target_entity_id">R108_E018</data><data key="edge_operational_context">DIPS alert codes listed daily.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DIPS alert codes listed daily.</data></edge><edge id="R108_REL0032" source="APP_DATS" target="R108_E019"><data key="edge_relationship_id">R108_REL0032</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">refreshes_numident_payment_mismatch_using</data><data key="edge_target_entity_id">R108_E019</data><data key="edge_operational_context">NUMI death alert runs last weekend of month.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">NUMI death alert runs last weekend of month.</data></edge><edge id="R108_REL0033" source="R108_E019" target="SYS_NUMIDENT"><data key="edge_relationship_id">R108_REL0033</data><data key="edge_source_entity_id">R108_E019</data><data key="edge_relationship_type">reconciles_death_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Check death status and decide whether Numident is correct.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Check death status and decide whether Numident is correct.</data></edge><edge id="R108_REL0034" source="R108_E019" target="SYS_MBR"><data key="edge_relationship_id">R108_REL0034</data><data key="edge_source_entity_id">R108_E019</data><data key="edge_relationship_type">reconciles_death_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Relevant Title II payment record may need manual death termination or suspension.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relevant Title II payment record may need manual death termination or suspension.</data></edge><edge id="R108_REL0035" source="R108_E019" target="SYS_SSR"><data key="edge_relationship_id">R108_REL0035</data><data key="edge_source_entity_id">R108_E019</data><data key="edge_relationship_type">reconciles_death_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Relevant Title XVI payment record may require manual death correction.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relevant Title XVI payment record may require manual death correction.</data></edge><edge id="R108_REL0036" source="R108_E020" target="WORK_DATS_DEATH_DEV_45D"><data key="edge_relationship_id">R108_REL0036</data><data key="edge_source_entity_id">R108_E020</data><data key="edge_relationship_type">requires_prior_development</data><data key="edge_target_entity_id">WORK_DATS_DEATH_DEV_45D</data><data key="edge_operational_context">DATS nonresponse outcome follows 45-day letter diary when no verification is obtained.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DATS nonresponse outcome follows 45-day letter diary when no verification is obtained.</data></edge><edge id="R108_REL0037" source="R108_E020" target="APP_DIPS"><data key="edge_relationship_id">R108_REL0037</data><data key="edge_source_entity_id">R108_E020</data><data key="edge_relationship_type">submits_death_transaction_through</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">Alleged death can be submitted in DIPS as non-responder following required 45-day development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Alleged death can be submitted in DIPS as non-responder following required 45-day development.</data></edge><edge id="R108_REL0038" source="APP_DATS" target="R108_E021"><data key="edge_relationship_id">R108_REL0038</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">supports_verified_alive_clearance</data><data key="edge_target_entity_id">R108_E021</data><data key="edge_operational_context">First-party evidence an individual is alive supports erroneous-death clearing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">First-party evidence an individual is alive supports erroneous-death clearing.</data></edge><edge id="R108_REL0039" source="R108_E016" target="APP_DIPS"><data key="edge_relationship_id">R108_REL0039</data><data key="edge_source_entity_id">R108_E016</data><data key="edge_relationship_type">requires_submission_via</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">DX code directs staff to enter death report using DIPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DX code directs staff to enter death report using DIPS.</data></edge><edge id="R108_REL0040" source="R108_E017" target="R108_E019"><data key="edge_relationship_id">R108_REL0040</data><data key="edge_source_entity_id">R108_E017</data><data key="edge_relationship_type">triggers_manual_correction_review</data><data key="edge_target_entity_id">R108_E019</data><data key="edge_operational_context">Staff determine whether to amend Numident or payment record; no unconditional overwrite.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Staff determine whether to amend Numident or payment record; no unconditional overwrite.</data></edge><edge id="R108_REL0041" source="DATA_DMF" target="R108_E021"><data key="edge_relationship_id">R108_REL0041</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">can_require_death_pii_removal_after</data><data key="edge_target_entity_id">R108_E021</data><data key="edge_operational_context">Erroneous death clearing prevents identifiable information about living person remaining on DMF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Erroneous death clearing prevents identifiable information about living person remaining on DMF.</data></edge><edge id="R108_REL0042" source="APP_DIPS" target="R108_E022"><data key="edge_relationship_id">R108_REL0042</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">requires_extra_approval_for_edr_changes</data><data key="edge_target_entity_id">R108_E022</data><data key="edge_operational_context">EDR change transactions require same-day two-PIN clearance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EDR change transactions require same-day two-PIN clearance.</data></edge><edge id="R108_REL0043" source="APP_DIPS" target="R108_E023"><data key="edge_relationship_id">R108_REL0043</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">requires_extra_approval_for_edr_deletions</data><data key="edge_target_entity_id">R108_E023</data><data key="edge_operational_context">EDR delete transactions require same-day two-PIN clearance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EDR delete transactions require same-day two-PIN clearance.</data></edge><edge id="R108_REL0044" source="APP_DIPS" target="R108_E024"><data key="edge_relationship_id">R108_REL0044</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">does_not_auto_remove_title_xvi_death</data><data key="edge_target_entity_id">R108_E024</data><data key="edge_operational_context">Title XVI death removal needs separate post-DIPS corrective action.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title XVI death removal needs separate post-DIPS corrective action.</data></edge><edge id="R108_REL0045" source="R108_E024" target="SYS_SSR"><data key="edge_relationship_id">R108_REL0045</data><data key="edge_source_entity_id">R108_E024</data><data key="edge_relationship_type">requires_separate_ssr_correction</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">DIPS cannot automatically delete date of death from SSI payment record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DIPS cannot automatically delete date of death from SSI payment record.</data></edge><edge id="R108_REL0046" source="APP_DIPS" target="R108_E025"><data key="edge_relationship_id">R108_REL0046</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">requires_ssn_or_exception_development</data><data key="edge_target_entity_id">R108_E025</data><data key="edge_operational_context">DIPS relies on SSN and may require BOAN update or deceased enumeration.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DIPS relies on SSN and may require BOAN update or deceased enumeration.</data></edge><edge id="R108_REL0047" source="R108_E025" target="SYS_NUMIDENT"><data key="edge_relationship_id">R108_REL0047</data><data key="edge_source_entity_id">R108_E025</data><data key="edge_relationship_type">requires_numident_establishment_where_applicable</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">DIPS entry must await Numident establishment if BOAN mandatory.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DIPS entry must await Numident establishment if BOAN mandatory.</data></edge><edge id="R108_REL0048" source="R108_E025" target="SYS_MBR"><data key="edge_relationship_id">R108_REL0048</data><data key="edge_source_entity_id">R108_E025</data><data key="edge_relationship_type">requires_title_ii_boan_update_if_already_enumerated</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Existing SSN missing as BOAN on MBR must be corrected before ordinary DIPS processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Existing SSN missing as BOAN on MBR must be corrected before ordinary DIPS processing.</data></edge><edge id="R108_REL0049" source="APP_DIPS" target="R108_E026"><data key="edge_relationship_id">R108_REL0049</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">posts_death_using_overnight_processing</data><data key="edge_target_entity_id">R108_E026</data><data key="edge_operational_context">DIPS transactions process overnight, post to Numident and usually to payment systems; exceptions apply.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DIPS transactions process overnight, post to Numident and usually to payment systems; exceptions apply.</data></edge><edge id="R108_REL0050" source="R108_E026" target="SYS_NUMIDENT"><data key="edge_relationship_id">R108_REL0050</data><data key="edge_source_entity_id">R108_E026</data><data key="edge_relationship_type">writes_death_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Numident is SSA official death source in redesigned flow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Numident is SSA official death source in redesigned flow.</data></edge><edge id="R108_REL0051" source="R108_E026" target="SYS_MBR"><data key="edge_relationship_id">R108_REL0051</data><data key="edge_source_entity_id">R108_E026</data><data key="edge_relationship_type">normally_posts_death_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Death generally flows automatically to payment system but requires monitoring of exceptions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Death generally flows automatically to payment system but requires monitoring of exceptions.</data></edge><edge id="R108_REL0052" source="R108_E026" target="SYS_SSR"><data key="edge_relationship_id">R108_REL0052</data><data key="edge_source_entity_id">R108_E026</data><data key="edge_relationship_type">normally_posts_death_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Death generally flows to benefit payment system; delete exception applies for Title XVI.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Death generally flows to benefit payment system; delete exception applies for Title XVI.</data></edge><edge id="R108_REL0053" source="FORM_SSA721" target="R108_E027"><data key="edge_relationship_id">R108_REL0053</data><data key="edge_source_entity_id">FORM_SSA721</data><data key="edge_relationship_type">has_post_update_document_disposal_rule</data><data key="edge_target_entity_id">R108_E027</data><data key="edge_operational_context">Physical SSA-721 destroyed after death information posted to Numident.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Physical SSA-721 destroyed after death information posted to Numident.</data></edge><edge id="R108_REL0054" source="FORM_SSA721" target="R108_E028"><data key="edge_relationship_id">R108_REL0054</data><data key="edge_source_entity_id">FORM_SSA721</data><data key="edge_relationship_type">initiates_survivor_outreach_when_address_supplied</data><data key="edge_target_entity_id">R108_E028</data><data key="edge_operational_context">Survivor name/address treated as correspondence-contact lead.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Survivor name/address treated as correspondence-contact lead.</data></edge><edge id="R108_REL0055" source="R108_E028" target="DATA_SSA721_SURVIVOR_ADDRESS"><data key="edge_relationship_id">R108_REL0055</data><data key="edge_source_entity_id">R108_E028</data><data key="edge_relationship_type">uses_survivor_address_from</data><data key="edge_target_entity_id">DATA_SSA721_SURVIVOR_ADDRESS</data><data key="edge_operational_context">Surviving-family contact address is source field, not authoritative person residence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Surviving-family contact address is source field, not authoritative person residence.</data></edge><edge id="R108_REL0056" source="R108_E028" target="NOTICE_SURVIVOR_LETTER"><data key="edge_relationship_id">R108_REL0056</data><data key="edge_source_entity_id">R108_E028</data><data key="edge_relationship_type">uses_notice</data><data key="edge_target_entity_id">NOTICE_SURVIVOR_LETTER</data><data key="edge_operational_context">DPS Survivor Letter selected from General folder when SSA-721 names/address available.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DPS Survivor Letter selected from General folder when SSA-721 names/address available.</data></edge><edge id="R108_REL0057" source="R108_E028" target="APP_DPS"><data key="edge_relationship_id">R108_REL0057</data><data key="edge_source_entity_id">R108_E028</data><data key="edge_relationship_type">draws_notice_from</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">DPS General folder contains survivor outreach notice.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DPS General folder contains survivor outreach notice.</data></edge><edge id="R108_REL0058" source="FORM_SSA721" target="R108_E029"><data key="edge_relationship_id">R108_REL0058</data><data key="edge_source_entity_id">FORM_SSA721</data><data key="edge_relationship_type">may_require_evid_documentation</data><data key="edge_target_entity_id">R108_E029</data><data key="edge_operational_context">Beneficiary claim with SSA-721 invokes EVID code 721.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Beneficiary claim with SSA-721 invokes EVID code 721.</data></edge><edge id="R108_REL0059" source="SYS_MBR" target="R108_E031"><data key="edge_relationship_id">R108_REL0059</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">can_contain_nmiss_special_message</data><data key="edge_target_entity_id">R108_E031</data><data key="edge_operational_context">NMISSS can be recognized via MBR special message.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">NMISSS can be recognized via MBR special message.</data></edge><edge id="R108_REL0060" source="SYS_MBR" target="R108_E032"><data key="edge_relationship_id">R108_REL0060</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">can_contain_nmiss_account_indicator</data><data key="edge_target_entity_id">R108_E032</data><data key="edge_operational_context">NMISSS may be recognizable from MBR Account data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">NMISSS may be recognizable from MBR Account data.</data></edge><edge id="R108_REL0061" source="APP_T2R" target="R108_E030"><data key="edge_relationship_id">R108_REL0061</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">cannot_automate_nmiss_actions</data><data key="edge_target_entity_id">R108_E030</data><data key="edge_operational_context">Title II Redesign documented exception for Northern Mariana Islands beneficiaries.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title II Redesign documented exception for Northern Mariana Islands beneficiaries.</data></edge><edge id="R108_REL0062" source="APP_POS" target="R108_E034"><data key="edge_relationship_id">R108_REL0062</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">generates_nmiss_exception_to</data><data key="edge_target_entity_id">R108_E034</data><data key="edge_operational_context">FO still inputs PE changes in POS, with manual PC follow-up.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FO still inputs PE changes in POS, with manual PC follow-up.</data></edge><edge id="R108_REL0063" source="R108_E030" target="R108_E034"><data key="edge_relationship_id">R108_REL0063</data><data key="edge_source_entity_id">R108_E030</data><data key="edge_relationship_type">requires_manual_adjustment_route</data><data key="edge_target_entity_id">R108_E034</data><data key="edge_operational_context">Change of address, direct deposit, death termination and earnings reports are examples.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Change of address, direct deposit, death termination and earnings reports are examples.</data></edge><edge id="R108_REL0064" source="R108_E034" target="APP_MACADE"><data key="edge_relationship_id">R108_REL0064</data><data key="edge_source_entity_id">R108_E034</data><data key="edge_relationship_type">is_resolved_using</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">WNPSC OAS processes exceptions through manual adjustment credit and award data entry.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">WNPSC OAS processes exceptions through manual adjustment credit and award data entry.</data></edge><edge id="R108_REL0065" source="R108_E034" target="R108_E033"><data key="edge_relationship_id">R108_REL0065</data><data key="edge_source_entity_id">R108_E034</data><data key="edge_relationship_type">is_queued_for</data><data key="edge_target_entity_id">R108_E033</data><data key="edge_operational_context">FO requests WNPSC OAS intervention despite MBR PCOC jurisdiction.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FO requests WNPSC OAS intervention despite MBR PCOC jurisdiction.</data></edge><edge id="R108_REL0066" source="R108_E033" target="APP_MACADE"><data key="edge_relationship_id">R108_REL0066</data><data key="edge_source_entity_id">R108_E033</data><data key="edge_relationship_type">processes_nmiss_exceptions_via</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">Manual processing, not automatic Title II Redesign.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Manual processing, not automatic Title II Redesign.</data></edge><edge id="R108_REL0067" source="R108_E035" target="R108_E039"><data key="edge_relationship_id">R108_REL0067</data><data key="edge_source_entity_id">R108_E035</data><data key="edge_relationship_type">requires_prior_comparison_point_evidence_review</data><data key="edge_target_entity_id">R108_E039</data><data key="edge_operational_context">FO checks CPD and supporting evidence before MINE screen-out.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FO checks CPD and supporting evidence before MINE screen-out.</data></edge><edge id="R108_REL0068" source="R108_E035" target="SYS_MBR"><data key="edge_relationship_id">R108_REL0068</data><data key="edge_source_entity_id">R108_E035</data><data key="edge_relationship_type">uses_existing_master_record_medical_diaries</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA medical diary attributes in MBR can be inaccurate or absent and require development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA medical diary attributes in MBR can be inaccurate or absent and require development.</data></edge><edge id="R108_REL0069" source="R108_E035" target="SYS_SSR"><data key="edge_relationship_id">R108_REL0069</data><data key="edge_source_entity_id">R108_E035</data><data key="edge_relationship_type">uses_existing_master_record_medical_diaries</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA medical diary attributes in SSR may need review and correction.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA medical diary attributes in SSR may need review and correction.</data></edge><edge id="R108_REL0070" source="R108_E035" target="FORM_SSA454BK"><data key="edge_relationship_id">R108_REL0070</data><data key="edge_source_entity_id">R108_E035</data><data key="edge_relationship_type">avoids_full_interview_using</data><data key="edge_target_entity_id">FORM_SSA454BK</data><data key="edge_operational_context">Qualified MINE review allows bypassing routine SSA-454 full interview at initial FO stage.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Qualified MINE review allows bypassing routine SSA-454 full interview at initial FO stage.</data></edge><edge id="R108_REL0071" source="R108_E035" target="FORM_SSA5002"><data key="edge_relationship_id">R108_REL0071</data><data key="edge_source_entity_id">R108_E035</data><data key="edge_relationship_type">documents_basis_on</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">FO records rationale in SSA-5002, scanned to eFolder or paper case.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FO records rationale in SSA-5002, scanned to eFolder or paper case.</data></edge><edge id="R108_REL0072" source="R108_E035" target="R108_E036"><data key="edge_relationship_id">R108_REL0072</data><data key="edge_source_entity_id">R108_E035</data><data key="edge_relationship_type">adds_electronic_referral_message</data><data key="edge_target_entity_id">R108_E036</data><data key="edge_operational_context">Electronic files use explicit MINE referral message.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Electronic files use explicit MINE referral message.</data></edge><edge id="R108_REL0073" source="R108_E035" target="R108_E037"><data key="edge_relationship_id">R108_REL0073</data><data key="edge_source_entity_id">R108_E035</data><data key="edge_relationship_type">adds_paper_referral_annotation</data><data key="edge_target_entity_id">R108_E037</data><data key="edge_operational_context">Paper folder uses route slip.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Paper folder uses route slip.</data></edge><edge id="R108_REL0074" source="R108_E035" target="R108_E038"><data key="edge_relationship_id">R108_REL0074</data><data key="edge_source_entity_id">R108_E035</data><data key="edge_relationship_type">may_be_returned_by_dds_for_full_interview</data><data key="edge_target_entity_id">R108_E038</data><data key="edge_operational_context">DDS may disagree with FO exclusion designation and require full interview.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DDS may disagree with FO exclusion designation and require full interview.</data></edge><edge id="R108_REL0075" source="R108_E038" target="FORM_SSA454BK"><data key="edge_relationship_id">R108_REL0075</data><data key="edge_source_entity_id">R108_E038</data><data key="edge_relationship_type">requires_completed_form</data><data key="edge_target_entity_id">FORM_SSA454BK</data><data key="edge_operational_context">FO completes full CDR interview upon DDS return.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FO completes full CDR interview upon DDS return.</data></edge><edge id="R108_REL0076" source="R108_E036" target="APP_EDCS"><data key="edge_relationship_id">R108_REL0076</data><data key="edge_source_entity_id">R108_E036</data><data key="edge_relationship_type">is_associated_with_case_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">POMS instructs electronic CDR EDCS case procedures, without transport inference.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS instructs electronic CDR EDCS case procedures, without transport inference.</data></edge><edge id="R108_REL0077" source="APP_DCPS" target="R108_E040"><data key="edge_relationship_id">R108_REL0077</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">records_medical_source_nonrequest_reason</data><data key="edge_target_entity_id">R108_E040</data><data key="edge_operational_context">DDS documentation obligation when not requesting source evidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DDS documentation obligation when not requesting source evidence.</data></edge><edge id="R108_REL0078" source="R108_E040" target="FORM_SSA5002"><data key="edge_relationship_id">R108_REL0078</data><data key="edge_source_entity_id">R108_E040</data><data key="edge_relationship_type">may_be_documented_on</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">Nonrequest reason can be in DCPS Case Note, worksheet or SSA-5002.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Nonrequest reason can be in DCPS Case Note, worksheet or SSA-5002.</data></edge><edge id="R108_REL0079" source="R108_E041" target="APP_MEGAHIT"><data key="edge_relationship_id">R108_REL0079</data><data key="edge_source_entity_id">R108_E041</data><data key="edge_relationship_type">supplements_missing_graphics_in</data><data key="edge_target_entity_id">APP_MEGAHIT</data><data key="edge_operational_context">Some diagnostic graphics absent from standard HIT document and require traditional follow-up.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Some diagnostic graphics absent from standard HIT document and require traditional follow-up.</data></edge><edge id="R108_REL0080" source="R108_E041" target="APP_ERE"><data key="edge_relationship_id">R108_REL0080</data><data key="edge_source_entity_id">R108_E041</data><data key="edge_relationship_type">can_use_traditional_evidence_request_channel</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">DDS can send traditional requests via mail, fax, ERE.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DDS can send traditional requests via mail, fax, ERE.</data></edge><edge id="R108_REL0081" source="APP_DCPS" target="R108_E041"><data key="edge_relationship_id">R108_REL0081</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">supports_traditional_medical_evidence_requests</data><data key="edge_target_entity_id">R108_E041</data><data key="edge_operational_context">DCPS creates traditional medical evidence request.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DCPS creates traditional medical evidence request.</data></edge><edge id="R108_REL0082" source="R108_E042" target="REPO_CEF"><data key="edge_relationship_id">R108_REL0082</data><data key="edge_source_entity_id">R108_E042</data><data key="edge_relationship_type">uses_existing_electronic_case_folder</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Post-DDS medical evidence on electronic case follows CEF routing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Post-DDS medical evidence on electronic case follows CEF routing.</data></edge><edge id="R108_REL0083" source="R108_E042" target="FORM_SSA5002"><data key="edge_relationship_id">R108_REL0083</data><data key="edge_source_entity_id">R108_E042</data><data key="edge_relationship_type">can_use_fo_report_of_contact</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">FO documents necessary post-decision evidence handling where applicable.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">FO documents necessary post-decision evidence handling where applicable.</data></edge><edge id="R108_REL0084" source="APP_EDCS" target="R108_E043"><data key="edge_relationship_id">R108_REL0084</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">exposes_827_attestation_screen</data><data key="edge_target_entity_id">R108_E043</data><data key="edge_operational_context">SSA or DDS employee can attest and submit through EDCS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA or DDS employee can attest and submit through EDCS.</data></edge><edge id="R108_REL0085" source="APP_EVIEW" target="R108_E043"><data key="edge_relationship_id">R108_REL0085</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">exposes_827_attestation_screen</data><data key="edge_target_entity_id">R108_E043</data><data key="edge_operational_context">SSA or DDS employee can attest and submit through eView.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA or DDS employee can attest and submit through eView.</data></edge><edge id="R108_REL0086" source="R108_E043" target="R108_E044"><data key="edge_relationship_id">R108_REL0086</data><data key="edge_source_entity_id">R108_E043</data><data key="edge_relationship_type">renders_signed_form_attributes_into</data><data key="edge_target_entity_id">R108_E044</data><data key="edge_operational_context">Form contains claimant and employee signature/witness attributes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Form contains claimant and employee signature/witness attributes.</data></edge><edge id="R108_REL0087" source="R108_E044" target="FORM_SSA827"><data key="edge_relationship_id">R108_REL0087</data><data key="edge_source_entity_id">R108_E044</data><data key="edge_relationship_type">is_retained_as</data><data key="edge_target_entity_id">FORM_SSA827</data><data key="edge_operational_context">Electronic rendering forms part of signed SSA-827.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Electronic rendering forms part of signed SSA-827.</data></edge><edge id="R108_REL0088" source="R108_E043" target="R108_E045"><data key="edge_relationship_id">R108_REL0088</data><data key="edge_source_entity_id">R108_E043</data><data key="edge_relationship_type">initiates_auto_file</data><data key="edge_target_entity_id">R108_E045</data><data key="edge_operational_context">After attestation system auto-adds signed SSA-827 to electronic folder.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">After attestation system auto-adds signed SSA-827 to electronic folder.</data></edge><edge id="R108_REL0089" source="R108_E045" target="REPO_CEF"><data key="edge_relationship_id">R108_REL0089</data><data key="edge_source_entity_id">R108_E045</data><data key="edge_relationship_type">files_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Accepted signed form automatically associated with electronic folder.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Accepted signed form automatically associated with electronic folder.</data></edge><edge id="R108_REL0090" source="APP_I3368" target="R108_E046"><data key="edge_relationship_id">R108_REL0090</data><data key="edge_source_entity_id">APP_I3368</data><data key="edge_relationship_type">supports_827_click_and_sign</data><data key="edge_target_entity_id">R108_E046</data><data key="edge_operational_context">Adult claimant signs SSA-827 via submit of i3368.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Adult claimant signs SSA-827 via submit of i3368.</data></edge><edge id="R108_REL0091" source="APP_I3441" target="R108_E046"><data key="edge_relationship_id">R108_REL0091</data><data key="edge_source_entity_id">APP_I3441</data><data key="edge_relationship_type">supports_827_click_and_sign</data><data key="edge_target_entity_id">R108_E046</data><data key="edge_operational_context">Adult claimant signs SSA-827 via submit of i3441 appeal report.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Adult claimant signs SSA-827 via submit of i3441 appeal report.</data></edge><edge id="R108_REL0092" source="R108_E046" target="FORM_SSA827"><data key="edge_relationship_id">R108_REL0092</data><data key="edge_source_entity_id">R108_E046</data><data key="edge_relationship_type">produces_electronic_signed</data><data key="edge_target_entity_id">FORM_SSA827</data><data key="edge_operational_context">Electronic authorizations signed when claimant submits internet disability report.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Electronic authorizations signed when claimant submits internet disability report.</data></edge><edge id="R108_REL0093" source="R108_E047" target="FORM_SSA827"><data key="edge_relationship_id">R108_REL0093</data><data key="edge_source_entity_id">R108_E047</data><data key="edge_relationship_type">constrains_signature_on</data><data key="edge_target_entity_id">FORM_SSA827</data><data key="edge_operational_context">12+ minors may require dual signatures, with documented privacy exceptions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">12+ minors may require dual signatures, with documented privacy exceptions.</data></edge><edge id="R108_REL0094" source="APP_MCS" target="R108_E048"><data key="edge_relationship_id">R108_REL0094</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">contains_lawful_presence_proof_screen</data><data key="edge_target_entity_id">R108_E048</data><data key="edge_operational_context">Cleared/archived MCS CLLP records include proof and status fields for conditional evidence reuse.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Cleared/archived MCS CLLP records include proof and status fields for conditional evidence reuse.</data></edge><edge id="R108_REL0095" source="SYS_NUMIDENT" target="R108_E049"><data key="edge_relationship_id">R108_REL0095</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">can_record_work_auth_code</data><data key="edge_target_entity_id">R108_E049</data><data key="edge_operational_context">Numident IDN H may represent permanent DHS work authorization.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Numident IDN H may represent permanent DHS work authorization.</data></edge><edge id="R108_REL0096" source="SYS_NUMIDENT" target="R108_E052"><data key="edge_relationship_id">R108_REL0096</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">is_not_sufficient_lawful_presence_evidence_for</data><data key="edge_target_entity_id">R108_E052</data><data key="edge_operational_context">Numident coding cannot alone establish lawful presence for benefit payments.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Numident coding cannot alone establish lawful presence for benefit payments.</data></edge><edge id="R108_REL0097" source="R108_E050" target="DATA_MBR_LAW_PRS"><data key="edge_relationship_id">R108_REL0097</data><data key="edge_source_entity_id">R108_E050</data><data key="edge_relationship_type">checks_prior_title_ii_proof_in</data><data key="edge_target_entity_id">DATA_MBR_LAW_PRS</data><data key="edge_operational_context">MBR LAW PRS proof requires acceptable permanent/reverification code and no discrepancies.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MBR LAW PRS proof requires acceptable permanent/reverification code and no discrepancies.</data></edge><edge id="R108_REL0098" source="R108_E050" target="R108_E048"><data key="edge_relationship_id">R108_REL0098</data><data key="edge_source_entity_id">R108_E050</data><data key="edge_relationship_type">checks_prior_mcs_claim_proof_in</data><data key="edge_target_entity_id">R108_E048</data><data key="edge_operational_context">MCS archived CLLP may contain qualifying previous lawful-presence evidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MCS archived CLLP may contain qualifying previous lawful-presence evidence.</data></edge><edge id="R108_REL0099" source="R108_E050" target="SYS_SSR"><data key="edge_relationship_id">R108_REL0099</data><data key="edge_source_entity_id">R108_E050</data><data key="edge_relationship_type">checks_prior_ssi_eligibility_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI alien status codes and supporting verification considered with limits.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI alien status codes and supporting verification considered with limits.</data></edge><edge id="R108_REL0100" source="R108_E050" target="R108_E052"><data key="edge_relationship_id">R108_REL0100</data><data key="edge_source_entity_id">R108_E050</data><data key="edge_relationship_type">rejects_numident_as_standalone_proof</data><data key="edge_target_entity_id">R108_E052</data><data key="edge_operational_context">Current eligibility must not be inferred from Numident work authorization coding.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Current eligibility must not be inferred from Numident work authorization coding.</data></edge><edge id="R108_REL0101" source="SVC_SAVE" target="R108_E051"><data key="edge_relationship_id">R108_REL0101</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">provides_immigration_status_query_attributes</data><data key="edge_target_entity_id">R108_E051</data><data key="edge_operational_context">DHS response is queried and compared with original immigration documents.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DHS response is queried and compared with original immigration documents.</data></edge><edge id="R108_REL0102" source="R108_E051" target="R108_E050"><data key="edge_relationship_id">R108_REL0102</data><data key="edge_source_entity_id">R108_E051</data><data key="edge_relationship_type">provides_conditional_evidence_for</data><data key="edge_target_entity_id">R108_E050</data><data key="edge_operational_context">Verify original DHS evidence and resolve conflicts; SAVE response alone may require escalation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Verify original DHS evidence and resolve conflicts; SAVE response alone may require escalation.</data></edge><edge id="R108_REL0103" source="FORM_G845" target="R108_E050"><data key="edge_relationship_id">R108_REL0103</data><data key="edge_source_entity_id">FORM_G845</data><data key="edge_relationship_type">supports_manual_verification_when_save_inconclusive</data><data key="edge_target_entity_id">R108_E050</data><data key="edge_operational_context">SSA requires G-845 escalation when online SAVE result cannot verify lawful presence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA requires G-845 escalation when online SAVE result cannot verify lawful presence.</data></edge><edge id="R108_REL0104" source="R108_E053" target="R108_E054"><data key="edge_relationship_id">R108_REL0104</data><data key="edge_source_entity_id">R108_E053</data><data key="edge_relationship_type">requires_claimant_notification_using</data><data key="edge_target_entity_id">R108_E054</data><data key="edge_operational_context">Patient is notified when CE report disclosed without consent under imminent harm criteria.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Patient is notified when CE report disclosed without consent under imminent harm criteria.</data></edge><edge id="R108_REL0105" source="R108_E053" target="R108_E055"><data key="edge_relationship_id">R108_REL0105</data><data key="edge_source_entity_id">R108_E053</data><data key="edge_relationship_type">uses_expedient_release_channel</data><data key="edge_target_entity_id">R108_E055</data><data key="edge_operational_context">ERE or fax can be used; no undocumented transport assumptions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">ERE or fax can be used; no undocumented transport assumptions.</data></edge><edge id="R108_REL0106" source="R108_E055" target="APP_ERE"><data key="edge_relationship_id">R108_REL0106</data><data key="edge_source_entity_id">R108_E055</data><data key="edge_relationship_type">can_use</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">ERE is a permissible emergency report delivery route.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">ERE is a permissible emergency report delivery route.</data></edge><edge id="R108_REL0107" source="R108_E054" target="REPO_CEF"><data key="edge_relationship_id">R108_REL0107</data><data key="edge_source_entity_id">R108_E054</data><data key="edge_relationship_type">filed_in_case_folder</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Letter is placed in disability folder Section E, if electronic case. Source does not require separate repository.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Letter is placed in disability folder Section E, if electronic case. Source does not require separate repository.</data></edge><edge id="R109_REL0001" source="APP_PUPS" target="R109_E001"><data key="edge_relationship_id">R109_REL0001</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">has_documented_screen</data><data key="edge_target_entity_id">R109_E001</data><data key="edge_operational_context">Named PUPS screen documented for Title XVI prisoner processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Named PUPS screen documented for Title XVI prisoner processing.</data></edge><edge id="R109_REL0002" source="APP_PUPS" target="R109_E002"><data key="edge_relationship_id">R109_REL0002</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">has_documented_screen</data><data key="edge_target_entity_id">R109_E002</data><data key="edge_operational_context">Named PUPS screen documented for Title XVI prisoner processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Named PUPS screen documented for Title XVI prisoner processing.</data></edge><edge id="R109_REL0003" source="APP_PUPS" target="R109_E003"><data key="edge_relationship_id">R109_REL0003</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">has_documented_screen</data><data key="edge_target_entity_id">R109_E003</data><data key="edge_operational_context">Named PUPS screen documented for Title XVI prisoner processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Named PUPS screen documented for Title XVI prisoner processing.</data></edge><edge id="R109_REL0004" source="APP_PUPS" target="R109_E004"><data key="edge_relationship_id">R109_REL0004</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">has_documented_screen</data><data key="edge_target_entity_id">R109_E004</data><data key="edge_operational_context">Named PUPS screen documented for Title XVI prisoner processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Named PUPS screen documented for Title XVI prisoner processing.</data></edge><edge id="R109_REL0005" source="APP_MSSICS" target="R109_E005"><data key="edge_relationship_id">R109_REL0005</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">has_institution_residence_screen</data><data key="edge_target_entity_id">R109_E005</data><data key="edge_operational_context">Active SSI Claims/MSSICS cases use institution residence to record prisoner status.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Active SSI Claims/MSSICS cases use institution residence to record prisoner status.</data></edge><edge id="R109_REL0006" source="R109_E001" target="R109_E009"><data key="edge_relationship_id">R109_REL0006</data><data key="edge_source_entity_id">R109_E001</data><data key="edge_relationship_type">records_address_input</data><data key="edge_target_entity_id">R109_E009</data><data key="edge_operational_context">PU16 may edit mailing and residence address for prisoner-related notices; actual authoritative address destination unspecified.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PU16 may edit mailing and residence address for prisoner-related notices; actual authoritative address destination unspecified.</data></edge><edge id="R109_REL0007" source="R109_E001" target="R109_E008"><data key="edge_relationship_id">R109_REL0007</data><data key="edge_source_entity_id">R109_E001</data><data key="edge_relationship_type">initiates_suspension_transaction</data><data key="edge_target_entity_id">R109_E008</data><data key="edge_operational_context">PUPS creates SSA-1719B suspension transaction for qualifying non-MSSICS records.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PUPS creates SSA-1719B suspension transaction for qualifying non-MSSICS records.</data></edge><edge id="R109_REL0008" source="R109_E008" target="FORM_SSA1719B"><data key="edge_relationship_id">R109_REL0008</data><data key="edge_source_entity_id">R109_E008</data><data key="edge_relationship_type">based_on_documented_input_form</data><data key="edge_target_entity_id">FORM_SSA1719B</data><data key="edge_operational_context">SSA-1719B is also used as manual suspension route when PUPS editing fails.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-1719B is also used as manual suspension route when PUPS editing fails.</data></edge><edge id="R109_REL0009" source="SYS_SSR" target="R109_E007"><data key="edge_relationship_id">R109_REL0009</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">reports_n22_status_to</data><data key="edge_target_entity_id">R109_E007</data><data key="edge_operational_context">SSR sends suspension feedback to PUPS only after N22 posts.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSR sends suspension feedback to PUPS only after N22 posts.</data></edge><edge id="R109_REL0010" source="R109_E007" target="APP_PUPS"><data key="edge_relationship_id">R109_REL0010</data><data key="edge_source_entity_id">R109_E007</data><data key="edge_relationship_type">updates_work_state_in</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">*PENDING changes to SUSPENSION after receipt of SSR N22 confirmation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">*PENDING changes to SUSPENSION after receipt of SSR N22 confirmation.</data></edge><edge id="R109_REL0011" source="R109_E006" target="SYS_SSR"><data key="edge_relationship_id">R109_REL0011</data><data key="edge_source_entity_id">R109_E006</data><data key="edge_relationship_type">posted_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR payment record carries Title XVI nonpayment status N22.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSR payment record carries Title XVI nonpayment status N22.</data></edge><edge id="R109_REL0012" source="R109_E005" target="R109_E006"><data key="edge_relationship_id">R109_REL0012</data><data key="edge_source_entity_id">R109_E005</data><data key="edge_relationship_type">supports_conditional_posting_of</data><data key="edge_target_entity_id">R109_E006</data><data key="edge_operational_context">Active MSSICS case uses institutional residence details; SSR posts N22.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Active MSSICS case uses institutional residence details; SSR posts N22.</data></edge><edge id="R109_REL0013" source="APP_PUPS" target="R109_E010"><data key="edge_relationship_id">R109_REL0013</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">applies_processing_exclusion</data><data key="edge_target_entity_id">R109_E010</data><data key="edge_operational_context">For rep-payee/temporary institutionalization/Goldberg-Kelly/special pay statuses some N22 suspensions require alternative processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">For rep-payee/temporary institutionalization/Goldberg-Kelly/special pay statuses some N22 suspensions require alternative processing.</data></edge><edge id="R109_REL0014" source="R109_E010" target="APP_MSSICS"><data key="edge_relationship_id">R109_REL0014</data><data key="edge_source_entity_id">R109_E010</data><data key="edge_relationship_type">routes_to_staff_processing_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">PUPS cannot automate certain active/special Title XVI records; other input/manual actions required.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PUPS cannot automate certain active/special Title XVI records; other input/manual actions required.</data></edge><edge id="R109_REL0015" source="R109_E003" target="R109_E007"><data key="edge_relationship_id">R109_REL0015</data><data key="edge_source_entity_id">R109_E003</data><data key="edge_relationship_type">displays_status_of</data><data key="edge_target_entity_id">R109_E007</data><data key="edge_operational_context">*PENDING on PUST flags SSR feedback not yet received; operational control, not necessarily an error in SSR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">*PENDING on PUST flags SSR feedback not yet received; operational control, not necessarily an error in SSR.</data></edge><edge id="R109_REL0016" source="R109_E004" target="R109_E007"><data key="edge_relationship_id">R109_REL0016</data><data key="edge_source_entity_id">R109_E004</data><data key="edge_relationship_type">records_result_of</data><data key="edge_target_entity_id">R109_E007</data><data key="edge_operational_context">P6QY displays incentive determination following N22 feedback when eligible.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">P6QY displays incentive determination following N22 feedback when eligible.</data></edge><edge id="R109_REL0017" source="APP_PUPS" target="DATA_PUPS_FACILITY_ID"><data key="edge_relationship_id">R109_REL0017</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">uses_prisoner_facility_identifier</data><data key="edge_target_entity_id">DATA_PUPS_FACILITY_ID</data><data key="edge_operational_context">PUPS PU16 records facility code for prison reports.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PUPS PU16 records facility code for prison reports.</data></edge><edge id="R109_REL0018" source="APP_PUPS" target="R109_E011"><data key="edge_relationship_id">R109_REL0018</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">allows_manual_exception_review</data><data key="edge_target_entity_id">R109_E011</data><data key="edge_operational_context">Automated incentive computation may fail for specified MBR/SSR status conditions or reported amount disputes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Automated incentive computation may fail for specified MBR/SSR status conditions or reported amount disputes.</data></edge><edge id="R109_REL0019" source="R109_E011" target="R109_E006"><data key="edge_relationship_id">R109_REL0019</data><data key="edge_source_entity_id">R109_E011</data><data key="edge_relationship_type">requires_status_precondition</data><data key="edge_target_entity_id">R109_E006</data><data key="edge_operational_context">SSI manual reporter payment only after N22 suspension record exists for corresponding period.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI manual reporter payment only after N22 suspension record exists for corresponding period.</data></edge><edge id="R109_REL0020" source="R109_E011" target="R109_E012"><data key="edge_relationship_id">R109_REL0020</data><data key="edge_source_entity_id">R109_E011</data><data key="edge_relationship_type">uses_reporter_identifier</data><data key="edge_target_entity_id">R109_E012</data><data key="edge_operational_context">Manual incentive request includes RID and FID along with beneficiary identifier, reporting and confinement dates.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Manual incentive request includes RID and FID along with beneficiary identifier, reporting and confinement dates.</data></edge><edge id="R109_REL0021" source="R109_E011" target="R109_E013"><data key="edge_relationship_id">R109_REL0021</data><data key="edge_source_entity_id">R109_E011</data><data key="edge_relationship_type">subject_to_exception_control</data><data key="edge_target_entity_id">R109_E013</data><data key="edge_operational_context">PUPS cannot calculate incentives automatically when suspension feedback is absent or payment status excluded.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PUPS cannot calculate incentives automatically when suspension feedback is absent or payment status excluded.</data></edge><edge id="R109_REL0022" source="R109_E011" target="R109_E014"><data key="edge_relationship_id">R109_REL0022</data><data key="edge_source_entity_id">R109_E011</data><data key="edge_relationship_type">authorizes_on_monthly_cycle_via</data><data key="edge_target_entity_id">R109_E014</data><data key="edge_operational_context">Central Office staff review and authorize manual payments monthly.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Central Office staff review and authorize manual payments monthly.</data></edge><edge id="R109_REL0023" source="APP_PUPS" target="R109_E015"><data key="edge_relationship_id">R109_REL0023</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">has_documented_screen</data><data key="edge_target_entity_id">R109_E015</data><data key="edge_operational_context">PU02 is used to clear pending Title II PUPS control.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PU02 is used to clear pending Title II PUPS control.</data></edge><edge id="R109_REL0024" source="R109_E015" target="R109_E011"><data key="edge_relationship_id">R109_REL0024</data><data key="edge_source_entity_id">R109_E015</data><data key="edge_relationship_type">documents_exception_for</data><data key="edge_target_entity_id">R109_E011</data><data key="edge_operational_context">Type of Action 2 clears a PUPS exception control prior to central request.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Type of Action 2 clears a PUPS exception control prior to central request.</data></edge><edge id="R109_REL0025" source="R109_E002" target="R109_E011"><data key="edge_relationship_id">R109_REL0025</data><data key="edge_source_entity_id">R109_E002</data><data key="edge_relationship_type">captures_exception_reason_for</data><data key="edge_target_entity_id">R109_E011</data><data key="edge_operational_context">PRMK annotation records exception and the rationale for manual incentive payment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PRMK annotation records exception and the rationale for manual incentive payment.</data></edge><edge id="R109_REL0026" source="UI_PUPS_P2QY" target="R109_E013"><data key="edge_relationship_id">R109_REL0026</data><data key="edge_source_entity_id">UI_PUPS_P2QY</data><data key="edge_relationship_type">documents_absence_of_incentive_for</data><data key="edge_target_entity_id">R109_E013</data><data key="edge_operational_context">P2QY Reason for No Incentive Payment explains automated Title II nonpayment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">P2QY Reason for No Incentive Payment explains automated Title II nonpayment.</data></edge><edge id="R109_REL0027" source="DB_SSI_IRS_INTERFACE" target="R109_E016"><data key="edge_relationship_id">R109_REL0027</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">exposes_alerts_through</data><data key="edge_target_entity_id">R109_E016</data><data key="edge_operational_context">Controlled and informational IRS match alerts can be retrieved from the interface database through MI Central workload listings.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Controlled and informational IRS match alerts can be retrieved from the interface database through MI Central workload listings.</data></edge><edge id="R109_REL0028" source="R109_E016" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R109_REL0028</data><data key="edge_source_entity_id">R109_E016</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">SSN/IRS/SSID Query Screen is provided under workload listing in SUMS/MCAS MI Central.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSN/IRS/SSID Query Screen is provided under workload listing in SUMS/MCAS MI Central.</data></edge><edge id="R109_REL0029" source="R109_E017" target="WORK_SSI_IRS_5B_DIARY"><data key="edge_relationship_id">R109_REL0029</data><data key="edge_source_entity_id">R109_E017</data><data key="edge_relationship_type">schedules</data><data key="edge_target_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_operational_context">Release cycle documented as October, February and June.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Release cycle documented as October, February and June.</data></edge><edge id="R109_REL0030" source="R109_E017" target="WORK_SSI_IRS_5H_DIARY"><data key="edge_relationship_id">R109_REL0030</data><data key="edge_source_entity_id">R109_E017</data><data key="edge_relationship_type">schedules</data><data key="edge_target_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_operational_context">5H pension alerts appear in conjunction with 5B workloads.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">5H pension alerts appear in conjunction with 5B workloads.</data></edge><edge id="R109_REL0031" source="APP_RZWIZ" target="R109_E019"><data key="edge_relationship_id">R109_REL0031</data><data key="edge_source_entity_id">APP_RZWIZ</data><data key="edge_relationship_type">required_for</data><data key="edge_target_entity_id">R109_E019</data><data key="edge_operational_context">RZ WIZ is mandatory for LI/RZ and listed wage-related diary interviews.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">RZ WIZ is mandatory for LI/RZ and listed wage-related diary interviews.</data></edge><edge id="R109_REL0032" source="APP_SSTNG" target="R109_E019"><data key="edge_relationship_id">R109_REL0032</data><data key="edge_source_entity_id">APP_SSTNG</data><data key="edge_relationship_type">supports_selection_of</data><data key="edge_target_entity_id">R109_E019</data><data key="edge_operational_context">SSTNG is permitted to select workloads by redetermination profile and priority diary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSTNG is permitted to select workloads by redetermination profile and priority diary.</data></edge><edge id="R109_REL0033" source="SYS_SSR" target="R109_E018"><data key="edge_relationship_id">R109_REL0033</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains_workload_control</data><data key="edge_target_entity_id">R109_E018</data><data key="edge_operational_context">SSID DIAR records DI dedicated account diary maturity information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSID DIAR records DI dedicated account diary maturity information.</data></edge><edge id="R109_REL0034" source="R109_E019" target="APP_RZWIZ"><data key="edge_relationship_id">R109_REL0034</data><data key="edge_source_entity_id">R109_E019</data><data key="edge_relationship_type">routes_for_development_using</data><data key="edge_target_entity_id">APP_RZWIZ</data><data key="edge_operational_context">RZ WIZ supports LI / RZ interview development, not tax data master record synchronization.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">RZ WIZ supports LI / RZ interview development, not tax data master record synchronization.</data></edge><edge id="R109_REL0035" source="R109_E017" target="DB_SSI_IRS_INTERFACE"><data key="edge_relationship_id">R109_REL0035</data><data key="edge_source_entity_id">R109_E017</data><data key="edge_relationship_type">uses_interface_stage_not_master_update</data><data key="edge_target_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_operational_context">IRS alert availability and diary release do not prove IRS-derived address changes to MBR, SSR or Numident.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">IRS alert availability and diary release do not prove IRS-derived address changes to MBR, SSR or Numident.</data></edge><edge id="R109_REL0036" source="DATA_REP_PAYEE_TYPE" target="SYS_MBR"><data key="edge_relationship_id">R109_REL0036</data><data key="edge_source_entity_id">DATA_REP_PAYEE_TYPE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Individual/Organization payee type explicitly coded on MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Individual/Organization payee type explicitly coded on MBR.</data></edge><edge id="R109_REL0037" source="DATA_REP_PAYEE_TYPE" target="SYS_SSR"><data key="edge_relationship_id">R109_REL0037</data><data key="edge_source_entity_id">DATA_REP_PAYEE_TYPE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Individual/Organization payee type explicitly coded on SSR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Individual/Organization payee type explicitly coded on SSR.</data></edge><edge id="R109_REL0038" source="R109_E020" target="APP_ERPS"><data key="edge_relationship_id">R109_REL0038</data><data key="edge_source_entity_id">R109_E020</data><data key="edge_relationship_type">used_as_identifier_within</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">eRPS generates organizational payee identifier from ZIP code and sequence number.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">eRPS generates organizational payee identifier from ZIP code and sequence number.</data></edge><edge id="R109_REL0039" source="R109_E021" target="DATA_REP_PAYEE_TYPE"><data key="edge_relationship_id">R109_REL0039</data><data key="edge_source_entity_id">R109_E021</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">DATA_REP_PAYEE_TYPE</data><data key="edge_operational_context">Limited-liability organization classified as Organization; sole proprietor/partnership often Individual despite EIN.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Limited-liability organization classified as Organization; sole proprietor/partnership often Individual despite EIN.</data></edge><edge id="R109_REL0040" source="R109_E021" target="R109_E022"><data key="edge_relationship_id">R109_REL0040</data><data key="edge_source_entity_id">R109_E021</data><data key="edge_relationship_type">requires_ein_or_registration_verification</data><data key="edge_target_entity_id">R109_E022</data><data key="edge_operational_context">Conflicting EIF evidence or name requires IRS or state legal-registration development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Conflicting EIF evidence or name requires IRS or state legal-registration development.</data></edge><edge id="R109_REL0041" source="R109_E022" target="DB_EIF"><data key="edge_relationship_id">R109_REL0041</data><data key="edge_source_entity_id">R109_E022</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_EIF</data><data key="edge_operational_context">Organizational EIN compared with SSA Employer Identification File.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Organizational EIN compared with SSA Employer Identification File.</data></edge><edge id="R109_REL0042" source="R109_E022" target="UI_EIF_AEQY"><data key="edge_relationship_id">R109_REL0042</data><data key="edge_source_entity_id">R109_E022</data><data key="edge_relationship_type">accesses</data><data key="edge_target_entity_id">UI_EIF_AEQY</data><data key="edge_operational_context">AEQY used to check organizational EIN records in EIF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">AEQY used to check organizational EIN records in EIF.</data></edge><edge id="R109_REL0043" source="R109_E023" target="UI_ERPS_PAYMENT_LEGEND"><data key="edge_relationship_id">R109_REL0043</data><data key="edge_source_entity_id">R109_E023</data><data key="edge_relationship_type">entered_using</data><data key="edge_target_entity_id">UI_ERPS_PAYMENT_LEGEND</data><data key="edge_operational_context">Payment legend screen records legal or DBA business name and individual name where appropriate.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Payment legend screen records legal or DBA business name and individual name where appropriate.</data></edge><edge id="R109_REL0044" source="R109_E021" target="R109_E023"><data key="edge_relationship_id">R109_REL0044</data><data key="edge_source_entity_id">R109_E021</data><data key="edge_relationship_type">controls_display_attribute</data><data key="edge_target_entity_id">R109_E023</data><data key="edge_operational_context">Payment legend contents depend on individual versus organizational payee classification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Payment legend contents depend on individual versus organizational payee classification.</data></edge><edge id="R109_REL0045" source="R109_E024" target="R109_E025"><data key="edge_relationship_id">R109_REL0045</data><data key="edge_source_entity_id">R109_E024</data><data key="edge_relationship_type">produces_customer_accessible</data><data key="edge_target_entity_id">R109_E025</data><data key="edge_operational_context">Beneficiary can print current holdings summary for SSA SSI asset verification; no direct SSA API established.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Beneficiary can print current holdings summary for SSA SSI asset verification; no direct SSA API established.</data></edge><edge id="R109_REL0046" source="R109_E025" target="R109_E029"><data key="edge_relationship_id">R109_REL0046</data><data key="edge_source_entity_id">R109_E025</data><data key="edge_relationship_type">used_as_evidence_in</data><data key="edge_target_entity_id">R109_E029</data><data key="edge_operational_context">SSI technician verifies current amount, issue date and confirmation number from claimant supplied summary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI technician verifies current amount, issue date and confirmation number from claimant supplied summary.</data></edge><edge id="R109_REL0047" source="R109_E029" target="APP_EVID"><data key="edge_relationship_id">R109_REL0047</data><data key="edge_source_entity_id">R109_E029</data><data key="edge_relationship_type">documents_ownership_and_value_using</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Staff enter issue information and redemption values on EVID screens.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Staff enter issue information and redemption values on EVID screens.</data></edge><edge id="R109_REL0048" source="R109_E029" target="R109_E026"><data key="edge_relationship_id">R109_REL0048</data><data key="edge_source_entity_id">R109_E029</data><data key="edge_relationship_type">records_claim_detail_on</data><data key="edge_target_entity_id">R109_E026</data><data key="edge_operational_context">MSSICS record uses RSTB page to document savings bond item and monthly values.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MSSICS record uses RSTB page to document savings bond item and monthly values.</data></edge><edge id="R109_REL0049" source="R109_E029" target="SYS_SSR"><data key="edge_relationship_id">R109_REL0049</data><data key="edge_source_entity_id">R109_E029</data><data key="edge_relationship_type">may_document_in_non_mssics</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Non-MSSICS cases record values and series in SSR Remarks.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Non-MSSICS cases record values and series in SSR Remarks.</data></edge><edge id="R109_REL0050" source="R109_E026" target="R109_E027"><data key="edge_relationship_id">R109_REL0050</data><data key="edge_source_entity_id">R109_E026</data><data key="edge_relationship_type">has_resource_code_entered_on</data><data key="edge_target_entity_id">R109_E027</data><data key="edge_operational_context">CMSC houses RE21 code for MSSICS bond cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">CMSC houses RE21 code for MSSICS bond cases.</data></edge><edge id="R109_REL0051" source="R109_E027" target="R109_E028"><data key="edge_relationship_id">R109_REL0051</data><data key="edge_source_entity_id">R109_E027</data><data key="edge_relationship_type">records_code</data><data key="edge_target_entity_id">R109_E028</data><data key="edge_operational_context">CMSC code RE21; no extra CG field detail for MSSICS cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">CMSC code RE21; no extra CG field detail for MSSICS cases.</data></edge><edge id="R109_REL0052" source="SYS_SSR" target="R109_E028"><data key="edge_relationship_id">R109_REL0052</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">may_carry_code</data><data key="edge_target_entity_id">R109_E028</data><data key="edge_operational_context">Non-MSSICS case carries RE21 in CG field with bond details in SSR remarks.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Non-MSSICS case carries RE21 in CG field with bond details in SSR remarks.</data></edge><edge id="R109_REL0053" source="R109_E024" target="ORG_TREASURY"><data key="edge_relationship_id">R109_REL0053</data><data key="edge_source_entity_id">R109_E024</data><data key="edge_relationship_type">is_managed_by</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Treasury operates TreasuryDirect; not evidence of an automated SSA financial interface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Treasury operates TreasuryDirect; not evidence of an automated SSA financial interface.</data></edge><edge id="R109_REL0054" source="APP_EDCS" target="R109_E030"><data key="edge_relationship_id">R109_REL0054</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">exposes_case_level_selection</data><data key="edge_target_entity_id">R109_E030</data><data key="edge_operational_context">EDCS has Select Case Level CDR Hearing option.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EDCS has Select Case Level CDR Hearing option.</data></edge><edge id="R109_REL0055" source="R109_E030" target="R109_E031"><data key="edge_relationship_id">R109_REL0055</data><data key="edge_source_entity_id">R109_E030</data><data key="edge_relationship_type">initiates_case_creation</data><data key="edge_target_entity_id">R109_E031</data><data key="edge_operational_context">Select CDR Hearing then confirm filing date and case creation in EDCS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Select CDR Hearing then confirm filing date and case creation in EDCS.</data></edge><edge id="R109_REL0056" source="R109_E031" target="R109_E032"><data key="edge_relationship_id">R109_REL0056</data><data key="edge_source_entity_id">R109_E031</data><data key="edge_relationship_type">captures_case_information</data><data key="edge_target_entity_id">R109_E032</data><data key="edge_operational_context">Hearing request includes claimant, attorney, payee contact identifiers and addresses.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Hearing request includes claimant, attorney, payee contact identifiers and addresses.</data></edge><edge id="R109_REL0057" source="APP_EDCS" target="APP_EVIEW"><data key="edge_relationship_id">R109_REL0057</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">viewable_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">eCDR hearing processed in EDCS and viewed in eView.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">eCDR hearing processed in EDCS and viewed in eView.</data></edge><edge id="R109_REL0058" source="R109_E033" target="APP_MSSICS"><data key="edge_relationship_id">R109_REL0058</data><data key="edge_source_entity_id">R109_E033</data><data key="edge_relationship_type">requires_existing_ssi_system_update</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Prior to SSI/concurrent EDCS case creation, FO records medical appeal and statutory continuation in MSSICS/SSID.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Prior to SSI/concurrent EDCS case creation, FO records medical appeal and statutory continuation in MSSICS/SSID.</data></edge><edge id="R109_REL0059" source="R109_E033" target="SYS_SSR"><data key="edge_relationship_id">R109_REL0059</data><data key="edge_source_entity_id">R109_E033</data><data key="edge_relationship_type">updates_appeal_information_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA instructs staff to document appeal before EDCS transfer; this is controlled workflow, not unsolicited EDCS-to-SSR sync.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA instructs staff to document appeal before EDCS transfer; this is controlled workflow, not unsolicited EDCS-to-SSR sync.</data></edge><edge id="R109_REL0060" source="R109_E033" target="R109_E032"><data key="edge_relationship_id">R109_REL0060</data><data key="edge_source_entity_id">R109_E033</data><data key="edge_relationship_type">precedes_transfer_of</data><data key="edge_target_entity_id">R109_E032</data><data key="edge_operational_context">Field office verifies and updates correct address, telephone and representative data on mainframe first.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Field office verifies and updates correct address, telephone and representative data on mainframe first.</data></edge><edge id="R109_REL0061" source="APP_EDCS" target="R109_E034"><data key="edge_relationship_id">R109_REL0061</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_linking_of</data><data key="edge_target_entity_id">R109_E034</data><data key="edge_operational_context">Electronic comparison-point decision folder can be linked to eCDR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Electronic comparison-point decision folder can be linked to eCDR.</data></edge><edge id="R109_REL0062" source="R109_E034" target="REPO_CEF"><data key="edge_relationship_id">R109_REL0062</data><data key="edge_source_entity_id">R109_E034</data><data key="edge_relationship_type">involves_document_archive</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Electronic comparison point decision materials are part of official electronic case context.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Electronic comparison point decision materials are part of official electronic case context.</data></edge><edge id="R109_REL0063" source="R109_E032" target="SYS_MBR"><data key="edge_relationship_id">R109_REL0063</data><data key="edge_source_entity_id">R109_E032</data><data key="edge_relationship_type">may_include_source_record_address_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Field office examines MBR and other mainframe records prior to EDCS transfer, not evidence of EDCS automatic MBR address updates.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Field office examines MBR and other mainframe records prior to EDCS transfer, not evidence of EDCS automatic MBR address updates.</data></edge><edge id="R109_REL0064" source="R109_E032" target="SYS_SSR"><data key="edge_relationship_id">R109_REL0064</data><data key="edge_source_entity_id">R109_E032</data><data key="edge_relationship_type">may_include_source_record_address_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI recipient data checked in SSR, including relevant contact fields.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI recipient data checked in SSR, including relevant contact fields.</data></edge><edge id="R109_REL0065" source="R109_E032" target="FORM_SSA792"><data key="edge_relationship_id">R109_REL0065</data><data key="edge_source_entity_id">R109_E032</data><data key="edge_relationship_type">contains_status_information_about</data><data key="edge_target_entity_id">FORM_SSA792</data><data key="edge_operational_context">SSI continuing-benefit election tracked when applicable.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSI continuing-benefit election tracked when applicable.</data></edge><edge id="R109_REL0066" source="R109_E035" target="R109_E036"><data key="edge_relationship_id">R109_REL0066</data><data key="edge_source_entity_id">R109_E035</data><data key="edge_relationship_type">uses_conditional_evidence_from</data><data key="edge_target_entity_id">R109_E036</data><data key="edge_operational_context">IRS interface alert may initiate development subject to special affirmative action in writing dating rules.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">IRS interface alert may initiate development subject to special affirmative action in writing dating rules.</data></edge><edge id="R109_REL0067" source="R109_E036" target="DB_SSI_IRS_INTERFACE"><data key="edge_relationship_id">R109_REL0067</data><data key="edge_source_entity_id">R109_E036</data><data key="edge_relationship_type">originates_as_alert_in</data><data key="edge_target_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_operational_context">IRS alert originates from interface-stage information, not beneficiary address master-record write.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">IRS alert originates from interface-stage information, not beneficiary address master-record write.</data></edge><edge id="R109_REL0068" source="R109_E035" target="APP_EVID"><data key="edge_relationship_id">R109_REL0068</data><data key="edge_source_entity_id">R109_E035</data><data key="edge_relationship_type">may_use_financial_evidence_from</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Evidence or report may be recorded, accepted or contradicted according to reopening criteria; not automatic SSR correction.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence or report may be recorded, accepted or contradicted according to reopening criteria; not automatic SSR correction.</data></edge><edge id="R109_REL0069" source="SYS_MBR" target="APP_MCS"><data key="edge_relationship_id">R109_REL0069</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">is_reusable_proof_source_under_conditions_for</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Prior established proof can be reused when associated proof code is valid and there is no material conflict.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Prior established proof can be reused when associated proof code is valid and there is no material conflict.</data></edge><edge id="R109_REL0070" source="SYS_NUMIDENT" target="APP_MCS"><data key="edge_relationship_id">R109_REL0070</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">is_reusable_proof_source_under_conditions_for</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Birth/age and other proof use is conditional on validity, not universal truth for every benefit issue.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Birth/age and other proof use is conditional on validity, not universal truth for every benefit issue.</data></edge><edge id="R109_REL0071" source="SYS_SSR" target="APP_MSSICS"><data key="edge_relationship_id">R109_REL0071</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">is_reusable_proof_source_under_conditions_for</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Prior coded proof is reusable for certain factors of entitlement when consistent with current claim.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Prior coded proof is reusable for certain factors of entitlement when consistent with current claim.</data></edge><edge id="R109_REL0072" source="R109_E039" target="SYS_MBR"><data key="edge_relationship_id">R109_REL0072</data><data key="edge_source_entity_id">R109_E039</data><data key="edge_relationship_type">manually_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA-11-BK route without SSN requires manually updating Title II payee selection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-11-BK route without SSN requires manually updating Title II payee selection.</data></edge><edge id="R109_REL0073" source="R109_E039" target="SYS_SSR"><data key="edge_relationship_id">R109_REL0073</data><data key="edge_source_entity_id">R109_E039</data><data key="edge_relationship_type">manually_updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA-11-BK route without SSN requires manually updating Title XVI payee selection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-11-BK route without SSN requires manually updating Title XVI payee selection.</data></edge><edge id="R109_REL0074" source="R109_E039" target="APP_EVIEW"><data key="edge_relationship_id">R109_REL0074</data><data key="edge_source_entity_id">R109_E039</data><data key="edge_relationship_type">can_retain_paper_evidence_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">SSA-11-BK can be retained in eView via Evidence Portal or in NDRED as applicable; no universal CEF storage claim.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-11-BK can be retained in eView via Evidence Portal or in NDRED as applicable; no universal CEF storage claim.</data></edge><edge id="R110_REL0001" source="R110_E001" target="R110_E002"><data key="edge_relationship_id">R110_REL0001</data><data key="edge_source_entity_id">R110_E001</data><data key="edge_relationship_type">operates_at</data><data key="edge_target_entity_id">R110_E002</data><data key="edge_operational_context">SSANRC operates an IRG for Title II paper-folder information retrieval.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0002" source="R110_E003" target="R110_E001"><data key="edge_relationship_id">R110_REL0002</data><data key="edge_source_entity_id">R110_E003</data><data key="edge_relationship_type">performed_by</data><data key="edge_target_entity_id">R110_E001</data><data key="edge_operational_context">IRG handles targeted stored-folder data/document retrieval, not claims adjudication.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0003" source="R110_E003" target="APP_PCACS"><data key="edge_relationship_id">R110_REL0003</data><data key="edge_source_entity_id">R110_E003</data><data key="edge_relationship_type">queries_for_current_location</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">PCACS queried for current folder location before requesting paper file.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0004" source="APP_PCACS" target="R110_E004"><data key="edge_relationship_id">R110_REL0004</data><data key="edge_source_entity_id">APP_PCACS</data><data key="edge_relationship_type">exposes_folder_location</data><data key="edge_target_entity_id">R110_E004</data><data key="edge_operational_context">Current folder location is obtained from current PCACS query.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0005" source="SYS_MBR" target="R110_E005"><data key="edge_relationship_id">R110_REL0005</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">has_folder_location_indicator</data><data key="edge_target_entity_id">R110_E005</data><data key="edge_operational_context">MBR FLI not relied on as current paper-folder location.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0006" source="R110_E004" target="R110_E006"><data key="edge_relationship_id">R110_REL0006</data><data key="edge_source_entity_id">R110_E004</data><data key="edge_relationship_type">may_indicate</data><data key="edge_target_entity_id">R110_E006</data><data key="edge_operational_context">CAVE FILE location triggers SSANRC IRG administrative request.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0007" source="R110_E004" target="R110_E007"><data key="edge_relationship_id">R110_REL0007</data><data key="edge_source_entity_id">R110_E004</data><data key="edge_relationship_type">may_indicate</data><data key="edge_target_entity_id">R110_E007</data><data key="edge_operational_context">QUES location means not at SSANRC; do not request IRG.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0008" source="R110_E006" target="R110_E008"><data key="edge_relationship_id">R110_REL0008</data><data key="edge_source_entity_id">R110_E006</data><data key="edge_relationship_type">triggers_request</data><data key="edge_target_entity_id">R110_E008</data><data key="edge_operational_context">CAVE FILE uses ADMS routing in PCOM to SSANRC IRG.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0009" source="R110_E009" target="R110_E008"><data key="edge_relationship_id">R110_REL0009</data><data key="edge_source_entity_id">R110_E009</data><data key="edge_relationship_type">provides_request_function</data><data key="edge_target_entity_id">R110_E008</data><data key="edge_operational_context">ADMM function #15 from SSA Main Menu routes ADMS requests.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0010" source="R110_E001" target="R110_E010"><data key="edge_relationship_id">R110_REL0010</data><data key="edge_source_entity_id">R110_E001</data><data key="edge_relationship_type">can_deliver_via</data><data key="edge_target_entity_id">R110_E010</data><data key="edge_operational_context">IRG response can be telephone, fax, email, or electronic folder upload.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0011" source="R110_E010" target="REPO_CEF"><data key="edge_relationship_id">R110_REL0011</data><data key="edge_source_entity_id">R110_E010</data><data key="edge_relationship_type">can_place_document_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">IRG may upload retrieved paper documents into the electronic claims folder when appropriate.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0012" source="R110_E003" target="ORG_WSU"><data key="edge_relationship_id">R110_REL0012</data><data key="edge_source_entity_id">R110_E003</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_WSU</data><data key="edge_operational_context">IRG retrieval serves workload support units alongside FO and PC.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0013" source="R110_E003" target="APP_EP"><data key="edge_relationship_id">R110_REL0013</data><data key="edge_source_entity_id">R110_E003</data><data key="edge_relationship_type">prefers_existing_electronic_evidence</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Do not contact IRG when needed documents are already in Evidence Portal, MBR, MCS or EVID.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0014" source="R110_E003" target="APP_PCACS"><data key="edge_relationship_id">R110_REL0014</data><data key="edge_source_entity_id">R110_E003</data><data key="edge_relationship_type">requires_pending_action_check</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">PCACS/Evidence Portal query checks if PC action is already pending.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0015" source="R110_E013" target="R110_E011"><data key="edge_relationship_id">R110_REL0015</data><data key="edge_source_entity_id">R110_E013</data><data key="edge_relationship_type">contains_macro</data><data key="edge_target_entity_id">R110_E011</data><data key="edge_operational_context">Query Master/PCOM toolbar contains T2Fld Title II folder location macro.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0016" source="R110_E013" target="R110_E012"><data key="edge_relationship_id">R110_REL0016</data><data key="edge_source_entity_id">R110_E013</data><data key="edge_relationship_type">contains_macro</data><data key="edge_target_entity_id">R110_E012</data><data key="edge_operational_context">Query Master/PCOM toolbar contains T16Fld Title XVI folder location macro.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0017" source="R110_E011" target="R110_E015"><data key="edge_relationship_id">R110_REL0017</data><data key="edge_source_entity_id">R110_E011</data><data key="edge_relationship_type">provides_folder_location_for</data><data key="edge_target_entity_id">R110_E015</data><data key="edge_operational_context">T2Fld can locate relevant Title II paper comparison-point folder.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0018" source="R110_E012" target="R110_E015"><data key="edge_relationship_id">R110_REL0018</data><data key="edge_source_entity_id">R110_E012</data><data key="edge_relationship_type">provides_folder_location_for</data><data key="edge_target_entity_id">R110_E015</data><data key="edge_operational_context">T16Fld can locate relevant Title XVI paper comparison-point folder.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0019" source="APP_EVIEW" target="R110_E016"><data key="edge_relationship_id">R110_REL0019</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">exposes_case_status_indicator</data><data key="edge_target_entity_id">R110_E016</data><data key="edge_operational_context">eView Status/History shows paper-folder-created indicator.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0020" source="R110_E014" target="R110_E016"><data key="edge_relationship_id">R110_REL0020</data><data key="edge_source_entity_id">R110_E014</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">R110_E016</data><data key="edge_operational_context">Verify paper/electronic status in eView before sending CPD folder to DDS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0021" source="R110_E014" target="R110_E015"><data key="edge_relationship_id">R110_REL0021</data><data key="edge_source_entity_id">R110_E014</data><data key="edge_relationship_type">identifies</data><data key="edge_target_entity_id">R110_E015</data><data key="edge_operational_context">CPD folder is most recent favorable medical/vocational decision evidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0022" source="R110_E015" target="REPO_CEF"><data key="edge_relationship_id">R110_REL0022</data><data key="edge_source_entity_id">R110_E015</data><data key="edge_relationship_type">may_be</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Most CPD folders are CEF; eView confirms electronic CPD.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0023" source="R110_E017" target="R110_E015"><data key="edge_relationship_id">R110_REL0023</data><data key="edge_source_entity_id">R110_E017</data><data key="edge_relationship_type">is_not_a_qualifying</data><data key="edge_target_entity_id">R110_E015</data><data key="edge_operational_context">Brown nonmedical Title XVI folder may contain a decision but lacks medical CPD evidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0024" source="R110_E015" target="APP_EVIEW"><data key="edge_relationship_id">R110_REL0024</data><data key="edge_source_entity_id">R110_E015</data><data key="edge_relationship_type">is_associated_with</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">eView provides case documents and decision date/medical evidence supporting CPD determination.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0025" source="APP_WAC" target="R110_E015"><data key="edge_relationship_id">R110_REL0025</data><data key="edge_source_entity_id">APP_WAC</data><data key="edge_relationship_type">provides_folder_location_for</data><data key="edge_target_entity_id">R110_E015</data><data key="edge_operational_context">WAC offers folder location information alongside toolbar macros.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0026" source="COMP_CDR_DEV_TOOLBOX" target="R110_E015"><data key="edge_relationship_id">R110_REL0026</data><data key="edge_source_entity_id">COMP_CDR_DEV_TOOLBOX</data><data key="edge_relationship_type">uses_folder_location_context</data><data key="edge_target_entity_id">R110_E015</data><data key="edge_operational_context">CDR Toolbox workflows identify CPD folder; implementation details not stated.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0027" source="R110_E019" target="R110_E015"><data key="edge_relationship_id">R110_REL0027</data><data key="edge_source_entity_id">R110_E019</data><data key="edge_relationship_type">uses_folder_location_context</data><data key="edge_target_entity_id">R110_E015</data><data key="edge_operational_context">EXR Assistant named in folder location documentation; implementation details not established.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0028" source="R110_E020" target="R110_E014"><data key="edge_relationship_id">R110_REL0028</data><data key="edge_source_entity_id">R110_E020</data><data key="edge_relationship_type">generates_potential_unable_to_locate_document</data><data key="edge_target_entity_id">R110_E014</data><data key="edge_operational_context">AFL-generated custom 5002 for unable-to-locate folder; planned WAC Express Forms availability not confirmed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0029" source="APP_EWORK" target="R110_E021"><data key="edge_relationship_id">R110_REL0029</data><data key="edge_source_entity_id">APP_EWORK</data><data key="edge_relationship_type">hosts_reconsideration</data><data key="edge_target_entity_id">R110_E021</data><data key="edge_operational_context">eWork establishes and processes Title II work-issue reconsiderations except documented exclusions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0030" source="APP_EWORK" target="R110_E022"><data key="edge_relationship_id">R110_REL0030</data><data key="edge_source_entity_id">APP_EWORK</data><data key="edge_relationship_type">hosts_reopening</data><data key="edge_target_entity_id">R110_E022</data><data key="edge_operational_context">eWork establishes reviews and prompts for reopened work determinations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0031" source="R110_E021" target="R110_E023"><data key="edge_relationship_id">R110_REL0031</data><data key="edge_source_entity_id">R110_E021</data><data key="edge_relationship_type">may_create</data><data key="edge_target_entity_id">R110_E023</data><data key="edge_operational_context">Original determination outside eWork triggers reconsideration exclusion.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0032" source="R110_E021" target="R110_E025"><data key="edge_relationship_id">R110_REL0032</data><data key="edge_source_entity_id">R110_E021</data><data key="edge_relationship_type">can_document_with</data><data key="edge_target_entity_id">R110_E025</data><data key="edge_operational_context">SSA-899-U2 may record work-issue affirmance or reversal.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0033" source="R110_E021" target="FORM_SSA821BK"><data key="edge_relationship_id">R110_REL0033</data><data key="edge_source_entity_id">R110_E021</data><data key="edge_relationship_type">uses_evidence_form</data><data key="edge_target_entity_id">FORM_SSA821BK</data><data key="edge_operational_context">SSA-821-BK is used to supplement employee earnings/work allegations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0034" source="R110_E021" target="FORM_SSA820BK"><data key="edge_relationship_id">R110_REL0034</data><data key="edge_source_entity_id">R110_E021</data><data key="edge_relationship_type">uses_evidence_form</data><data key="edge_target_entity_id">FORM_SSA820BK</data><data key="edge_operational_context">SSA-820 is used for self-employment issues.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0035" source="R110_E021" target="DB_DCF"><data key="edge_relationship_id">R110_REL0035</data><data key="edge_source_entity_id">R110_E021</data><data key="edge_relationship_type">effectuates_revised_result_on</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Reconsideration reversal entails staff input of revised earnings and determination information to DCF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0036" source="R110_E022" target="APP_EWORK"><data key="edge_relationship_id">R110_REL0036</data><data key="edge_source_entity_id">R110_E022</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">Reopening a prior work review established and completed in eWork.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0037" source="R110_E023" target="APP_POS"><data key="edge_relationship_id">R110_REL0037</data><data key="edge_source_entity_id">R110_E023</data><data key="edge_relationship_type">restricts</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Certain work reconsideration reversals are POS direct-input exclusions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0038" source="R110_E021" target="R110_E024"><data key="edge_relationship_id">R110_REL0038</data><data key="edge_source_entity_id">R110_E021</data><data key="edge_relationship_type">retains_work_evidence_through</data><data key="edge_target_entity_id">R110_E024</data><data key="edge_operational_context">Completed determinations, SSA-820/821 and evidence copied into electronic folder and PC paperless as required.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0039" source="R110_E024" target="APP_EVIEW"><data key="edge_relationship_id">R110_REL0039</data><data key="edge_source_entity_id">R110_E024</data><data key="edge_relationship_type">sends_to</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Electronic folder may receive faxed documents with barcode.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0040" source="R110_E024" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">R110_REL0040</data><data key="edge_source_entity_id">R110_E024</data><data key="edge_relationship_type">sends_to</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">Further PC action requires parallel fax to PSC Paperless.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0041" source="R110_E026" target="APP_EWORK"><data key="edge_relationship_id">R110_REL0041</data><data key="edge_source_entity_id">R110_E026</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">FO or PC transfers work reconsideration using eWork.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0042" source="R110_E026" target="APP_DOORS"><data key="edge_relationship_id">R110_REL0042</data><data key="edge_source_entity_id">R110_E026</data><data key="edge_relationship_type">uses_address_book</data><data key="edge_target_entity_id">APP_DOORS</data><data key="edge_operational_context">Paperless fax number / FO fax number is obtained from DOORS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0043" source="R110_E026" target="R110_E024"><data key="edge_relationship_id">R110_REL0043</data><data key="edge_source_entity_id">R110_E026</data><data key="edge_relationship_type">performs_document_routing</data><data key="edge_target_entity_id">R110_E024</data><data key="edge_operational_context">Work review may require simultaneous faxing of case documents to electronic and paperless repositories.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0044" source="R110_E027" target="ORG_DDS"><data key="edge_relationship_id">R110_REL0044</data><data key="edge_source_entity_id">R110_E027</data><data key="edge_relationship_type">handled_by</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">DDS has responsibilities for congressional inquiries on its pending and decided cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0045" source="R110_E027" target="R110_E028"><data key="edge_relationship_id">R110_REL0045</data><data key="edge_source_entity_id">R110_E027</data><data key="edge_relationship_type">creates_flag</data><data key="edge_target_entity_id">R110_E028</data><data key="edge_operational_context">DDS flags the folder for inquiry and sends electronic-folder alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0046" source="R110_E027" target="R110_E029"><data key="edge_relationship_id">R110_REL0046</data><data key="edge_source_entity_id">R110_E027</data><data key="edge_relationship_type">creates_diary</data><data key="edge_target_entity_id">R110_E029</data><data key="edge_operational_context">20-day final response diary or 30-day interim diary, with recurring 30-day follow-ups.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0047" source="R110_E027" target="R110_E030"><data key="edge_relationship_id">R110_REL0047</data><data key="edge_source_entity_id">R110_E027</data><data key="edge_relationship_type">generates_response</data><data key="edge_target_entity_id">R110_E030</data><data key="edge_operational_context">DDS prepares interim status and final/clearance messages.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0048" source="R110_E028" target="REPO_CEF"><data key="edge_relationship_id">R110_REL0048</data><data key="edge_source_entity_id">R110_E028</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DDS may put inquiry flag or alert in electronic folder.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0049" source="R110_E029" target="R110_E030"><data key="edge_relationship_id">R110_REL0049</data><data key="edge_source_entity_id">R110_E029</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">R110_E030</data><data key="edge_operational_context">Calendar diary controls interim and final responses.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0050" source="R110_E027" target="FORM_SSA408"><data key="edge_relationship_id">R110_REL0050</data><data key="edge_source_entity_id">R110_E027</data><data key="edge_relationship_type">routes_paper_inquiry_with</data><data key="edge_target_entity_id">FORM_SSA408</data><data key="edge_operational_context">Paper-folder congressional inquiry uses SSA-408 route slip for routing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0051" source="R110_E027" target="APP_EVIEW"><data key="edge_relationship_id">R110_REL0051</data><data key="edge_source_entity_id">R110_E027</data><data key="edge_relationship_type">uses_decision_evidence</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">When case is electronic, DDS adds inquiry flag and relevant records to electronic folder.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0052" source="APP_FFSCF" target="R110_E031"><data key="edge_relationship_id">R110_REL0052</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">R110_E031</data><data key="edge_operational_context">FFDG updates timely protests, dispositions and good cause.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0053" source="APP_FFSCF" target="R110_E032"><data key="edge_relationship_id">R110_REL0053</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">has_query</data><data key="edge_target_entity_id">R110_E032</data><data key="edge_operational_context">FFWQ warrant-information source differentiates batch/OIG/third-party reports.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0054" source="R110_E032" target="R110_E031"><data key="edge_relationship_id">R110_REL0054</data><data key="edge_source_entity_id">R110_E032</data><data key="edge_relationship_type">guides_protest_entry_into</data><data key="edge_target_entity_id">R110_E031</data><data key="edge_operational_context">Warrant source governs protest data entered on FFDG.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0055" source="R110_E033" target="R110_E031"><data key="edge_relationship_id">R110_REL0055</data><data key="edge_source_entity_id">R110_E033</data><data key="edge_relationship_type">requires_control_on</data><data key="edge_target_entity_id">R110_E031</data><data key="edge_operational_context">FO documents allowed protest/denied good-cause status in FFDG for closed-period cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0056" source="R110_E033" target="R110_E034"><data key="edge_relationship_id">R110_REL0056</data><data key="edge_source_entity_id">R110_E033</data><data key="edge_relationship_type">uses_stop_recovery_code</data><data key="edge_target_entity_id">R110_E034</data><data key="edge_operational_context">ROAR Protest/Stop recovery code 14 defers recovery pending warrant outcome.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0057" source="R110_E034" target="APP_ROAR"><data key="edge_relationship_id">R110_REL0057</data><data key="edge_source_entity_id">R110_E034</data><data key="edge_relationship_type">entered_on</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">ROAR holds code 14 and stops debt recovery.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0058" source="R110_E033" target="R110_E035"><data key="edge_relationship_id">R110_REL0058</data><data key="edge_source_entity_id">R110_E033</data><data key="edge_relationship_type">transmits_paper_processing_form</data><data key="edge_target_entity_id">R110_E035</data><data key="edge_operational_context">FO sends 2795 processing exclusion to PSC, with deferred documentation by mail rather than fax.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0059" source="R110_E033" target="APP_MACADE"><data key="edge_relationship_id">R110_REL0059</data><data key="edge_source_entity_id">R110_E033</data><data key="edge_relationship_type">requires_manual_suspension_processing</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">PSC posts deferred closed-period S9 through MADCAP/MACADE rather than FFEL.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0060" source="APP_FFSCF" target="R110_E036"><data key="edge_relationship_id">R110_REL0060</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">may_send_title_ii_finder</data><data key="edge_target_entity_id">R110_E036</data><data key="edge_operational_context">FFSCF sends Title II finder for eligible closed period or prospective fugitive-felon suspension.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0061" source="R110_E036" target="SYS_MBR"><data key="edge_relationship_id">R110_REL0061</data><data key="edge_source_entity_id">R110_E036</data><data key="edge_relationship_type">posts_history_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Finder can post FUGFEL status and S9 closed suspension period to MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0062" source="R110_E033" target="SYS_MBR"><data key="edge_relationship_id">R110_REL0062</data><data key="edge_source_entity_id">R110_E033</data><data key="edge_relationship_type">uses_record_for_identification</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA identifies Title II warrant/debt record before disposition.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0063" source="R110_E033" target="APP_ERPS"><data key="edge_relationship_id">R110_REL0063</data><data key="edge_source_entity_id">R110_E033</data><data key="edge_relationship_type">check_representative_payee_suitability</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Staff check representative payee status when claimant has outstanding felony warrant.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0064" source="APP_ECO" target="R110_E037"><data key="edge_relationship_id">R110_REL0064</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">prepares</data><data key="edge_target_entity_id">R110_E037</data><data key="edge_operational_context">ECO sends pre-offset notice after selecting debt for TRO.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0065" source="R110_E037" target="R110_E050"><data key="edge_relationship_id">R110_REL0065</data><data key="edge_source_entity_id">R110_E037</data><data key="edge_relationship_type">uses_address_rule</data><data key="edge_target_entity_id">R110_E050</data><data key="edge_operational_context">ECO notice address chosen by AVC verified address or recency fallback.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0066" source="R110_E050" target="SVC_AVC"><data key="edge_relationship_id">R110_REL0066</data><data key="edge_source_entity_id">R110_E050</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SVC_AVC</data><data key="edge_operational_context">ECO obtains external verified mailing address from Address Verification Contractor.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0067" source="R110_E050" target="DATA_AVC_DEBTOR_ADDR"><data key="edge_relationship_id">R110_REL0067</data><data key="edge_source_entity_id">R110_E050</data><data key="edge_relationship_type">may_use</data><data key="edge_target_entity_id">DATA_AVC_DEBTOR_ADDR</data><data key="edge_operational_context">AVC returns usable address for debt notice; not automatic program-record address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0068" source="R110_E050" target="SYS_MBR"><data key="edge_relationship_id">R110_REL0068</data><data key="edge_source_entity_id">R110_E050</data><data key="edge_relationship_type">falls_back_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">If AVC fails, recent MBR address may be used for notice mailing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0069" source="R110_E050" target="SYS_SSR"><data key="edge_relationship_id">R110_REL0069</data><data key="edge_source_entity_id">R110_E050</data><data key="edge_relationship_type">falls_back_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">If AVC fails, recent SSR address may be used for notice mailing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0070" source="R110_E037" target="R110_E049"><data key="edge_relationship_id">R110_REL0070</data><data key="edge_source_entity_id">R110_E037</data><data key="edge_relationship_type">supports_review</data><data key="edge_target_entity_id">R110_E049</data><data key="edge_operational_context">Undeliverable initial notice can trigger review and debt reestablishment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0071" source="R110_E049" target="R110_E038"><data key="edge_relationship_id">R110_REL0071</data><data key="edge_source_entity_id">R110_E049</data><data key="edge_relationship_type">deletes_old_debt_through</data><data key="edge_target_entity_id">R110_E038</data><data key="edge_operational_context">SMTC deletes prior ROAR debt after verified original notice nonreceipt.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0072" source="R110_E049" target="R110_E039"><data key="edge_relationship_id">R110_REL0072</data><data key="edge_source_entity_id">R110_E049</data><data key="edge_relationship_type">reestablishes_debt_through</data><data key="edge_target_entity_id">R110_E039</data><data key="edge_operational_context">SMED reestablishes debt using current establishment date.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0073" source="R110_E038" target="APP_ROAR"><data key="edge_relationship_id">R110_REL0073</data><data key="edge_source_entity_id">R110_E038</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">SMTC changes ROAR debt state; confirmation query next day.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0074" source="R110_E039" target="APP_ROAR"><data key="edge_relationship_id">R110_REL0074</data><data key="edge_source_entity_id">R110_E039</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">SMED creates corrected establishment date in ROAR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0075" source="APP_DMS" target="R110_E040"><data key="edge_relationship_id">R110_REL0075</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R110_E040</data><data key="edge_operational_context">DMS TOP menu accesses Stop Offset TRSO.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0076" source="APP_DMS" target="R110_E041"><data key="edge_relationship_id">R110_REL0076</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R110_E041</data><data key="edge_operational_context">DMS DFBP records bankruptcy-pending control.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0077" source="APP_DMS" target="R110_E042"><data key="edge_relationship_id">R110_REL0077</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R110_E042</data><data key="edge_operational_context">DMS TRCA corrects offset/agency refund.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0078" source="APP_DMS" target="R110_E043"><data key="edge_relationship_id">R110_REL0078</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R110_E043</data><data key="edge_operational_context">DMS TRSC stops external collection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0079" source="APP_DMS" target="R110_E044"><data key="edge_relationship_id">R110_REL0079</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R110_E044</data><data key="edge_operational_context">DMS DFTE terminates collection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0080" source="APP_DMS" target="IFACE_DRPF"><data key="edge_relationship_id">R110_REL0080</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">IFACE_DRPF</data><data key="edge_operational_context">FO screen for protests/stop recovery.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0081" source="APP_DMS" target="IFACE_DRPT"><data key="edge_relationship_id">R110_REL0081</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">IFACE_DRPT</data><data key="edge_operational_context">TSC screen for protests/stop recovery.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0082" source="APP_DMS" target="IFACE_DRPR"><data key="edge_relationship_id">R110_REL0082</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">IFACE_DRPR</data><data key="edge_operational_context">PC screen for protests/stop recovery.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0083" source="APP_DMS" target="UI_DMS_RMKS"><data key="edge_relationship_id">R110_REL0083</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">UI_DMS_RMKS</data><data key="edge_operational_context">RMKS stores contact remarks.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0084" source="R110_E040" target="PROC_TRO"><data key="edge_relationship_id">R110_REL0084</data><data key="edge_source_entity_id">R110_E040</data><data key="edge_relationship_type">stops_offset_for</data><data key="edge_target_entity_id">PROC_TRO</data><data key="edge_operational_context">TRSO may remove deceased debtor from Treasury Offset Program.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0085" source="R110_E041" target="PROC_TRO"><data key="edge_relationship_id">R110_REL0085</data><data key="edge_source_entity_id">R110_E041</data><data key="edge_relationship_type">pauses_collection_in</data><data key="edge_target_entity_id">PROC_TRO</data><data key="edge_operational_context">Pending bankruptcy petition prevents further collection action as appropriate.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0086" source="R110_E042" target="PROC_TRO"><data key="edge_relationship_id">R110_REL0086</data><data key="edge_source_entity_id">R110_E042</data><data key="edge_relationship_type">may_issue_agency_refund_for</data><data key="edge_target_entity_id">PROC_TRO</data><data key="edge_operational_context">Pending initial waiver, reconsideration or hearing can require agency refund of tax offset.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0087" source="R110_E043" target="APP_ECO"><data key="edge_relationship_id">R110_REL0087</data><data key="edge_source_entity_id">R110_E043</data><data key="edge_relationship_type">deactivates</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">TRSC deactivates external collection when debt non-enforceable.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0088" source="R110_E049" target="UI_DMS_RMKS"><data key="edge_relationship_id">R110_REL0088</data><data key="edge_source_entity_id">R110_E049</data><data key="edge_relationship_type">updates_contact_in</data><data key="edge_target_entity_id">UI_DMS_RMKS</data><data key="edge_operational_context">Technicians document claimed nonreceipt and current debtor contact in debt remarks.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0089" source="R110_E037" target="APP_ORS"><data key="edge_relationship_id">R110_REL0089</data><data key="edge_source_entity_id">R110_E037</data><data key="edge_relationship_type">retained_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">ECO notices issued after November 2015 stored in Online Retrieval System.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0090" source="PROC_TRO" target="SYS_NUMIDENT"><data key="edge_relationship_id">R110_REL0090</data><data key="edge_source_entity_id">PROC_TRO</data><data key="edge_relationship_type">selects_debt_using</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">TRO eligibility selection uses ROAR, MBR and Numident data; not a new person store.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0091" source="PROC_TRO" target="SYS_MBR"><data key="edge_relationship_id">R110_REL0091</data><data key="edge_source_entity_id">PROC_TRO</data><data key="edge_relationship_type">selects_debt_using</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">TRO selection uses MBR LAF and beneficiary identifiers.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0092" source="PROC_TRO" target="APP_ROAR"><data key="edge_relationship_id">R110_REL0092</data><data key="edge_source_entity_id">PROC_TRO</data><data key="edge_relationship_type">selects_debt_using</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">TRO selection depends on ROAR balance and debt status.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0093" source="R110_E051" target="SYS_SSR"><data key="edge_relationship_id">R110_REL0093</data><data key="edge_source_entity_id">R110_E051</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSQM ADDR segment queries SSI address and ACD.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0094" source="R110_E052" target="SYS_SSR"><data key="edge_relationship_id">R110_REL0094</data><data key="edge_source_entity_id">R110_E052</data><data key="edge_relationship_type">prompts_staff_to_query</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">MBR SID line leads staff to SSR address review.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0095" source="SYS_MBR" target="R110_E052"><data key="edge_relationship_id">R110_REL0095</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">has_data_line</data><data key="edge_target_entity_id">R110_E052</data><data key="edge_operational_context">SID data line references SSI involvement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0096" source="SYS_MBR" target="DATA_MBR_ADDR_UPDATED"><data key="edge_relationship_id">R110_REL0096</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">has_address_timestamp</data><data key="edge_target_entity_id">DATA_MBR_ADDR_UPDATED</data><data key="edge_operational_context">MBR ADDR Updated used for recency comparison.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0097" source="R110_E051" target="DATA_SSR_ACD"><data key="edge_relationship_id">R110_REL0097</data><data key="edge_source_entity_id">R110_E051</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">DATA_SSR_ACD</data><data key="edge_operational_context">SSI address-change date ACD returned by SSQM ADDR query.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0098" source="DATA_MBR_ADDR_UPDATED" target="DATA_SSR_ACD"><data key="edge_relationship_id">R110_REL0098</data><data key="edge_source_entity_id">DATA_MBR_ADDR_UPDATED</data><data key="edge_relationship_type">compared_with</data><data key="edge_target_entity_id">DATA_SSR_ACD</data><data key="edge_operational_context">If SSI ACD newer than MBR ADDR Updated, use more current SSR address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0099" source="PROC_T2_UNDELIV_ADDRESS" target="R110_E051"><data key="edge_relationship_id">R110_REL0099</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">R110_E051</data><data key="edge_operational_context">Undeliverable mail work compares MBR and SSR through SSQM ADDR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0100" source="PROC_T2_UNDELIV_ADDRESS" target="ORG_BENEFICIARY_FI"><data key="edge_relationship_id">R110_REL0100</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">contacts</data><data key="edge_target_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_operational_context">If direct deposit, staff request address from financial institution.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0101" source="PROC_T2_UNDELIV_ADDRESS" target="FORM_E3759"><data key="edge_relationship_id">R110_REL0101</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">uses_address_request</data><data key="edge_target_entity_id">FORM_E3759</data><data key="edge_operational_context">E3759 bank address request/locate letter sent for undeliverable mail.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0102" source="PROC_T2_UNDELIV_ADDRESS" target="FORM_SSA_L2001"><data key="edge_relationship_id">R110_REL0102</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">uses_address_request</data><data key="edge_target_entity_id">FORM_SSA_L2001</data><data key="edge_operational_context">SSA-L2001 requests address information from USPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0103" source="PROC_T2_UNDELIV_ADDRESS" target="APP_POS"><data key="edge_relationship_id">R110_REL0103</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">uses_program_update</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">New verified FI/USPS address entered through POS to MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0104" source="APP_POS" target="SYS_MBR"><data key="edge_relationship_id">R110_REL0104</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">posts_controlled_address_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">FO/PC inputs verified address through POS for Title II.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0105" source="PROC_T2_UNDELIV_ADDRESS" target="APP_MDW_AI"><data key="edge_relationship_id">R110_REL0105</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">may_trigger</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">PSC/TSC send MDW or request assistance to FO for concurrent SSR mismatch.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0106" source="PROC_T2_UNDELIV_ADDRESS" target="SYS_SSR"><data key="edge_relationship_id">R110_REL0106</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">requires_separate_ssi_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">FO must update SSI Claims System to correct SSR if different from new MBR address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0107" source="PROC_T2_UNDELIV_ADDRESS" target="R110_E055"><data key="edge_relationship_id">R110_REL0107</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">may_suspend_unlocated_beneficiary</data><data key="edge_target_entity_id">R110_E055</data><data key="edge_operational_context">If no good contact address, staff suspend current-pay case LAF S6.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0108" source="R110_E055" target="SYS_MBR"><data key="edge_relationship_id">R110_REL0108</data><data key="edge_source_entity_id">R110_E055</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">LAF S6 posted via POS following exhausted whereabouts development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0109" source="PROC_T2_UNDELIV_ADDRESS" target="APP_MONET"><data key="edge_relationship_id">R110_REL0109</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">requires_special_message_entry</data><data key="edge_target_entity_id">APP_MONET</data><data key="edge_operational_context">MONET or other authorized MBR Special Message documents attempts and outcome.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0110" source="PROC_T2_UNDELIV_ADDRESS" target="REPO_NDRED"><data key="edge_relationship_id">R110_REL0110</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">retains_notice_if_not_in_ors</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">If notice not in ORS, fax returned due-process notice via Evidence Portal to NDRed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0111" source="R110_E057" target="FORM_SF425"><data key="edge_relationship_id">R110_REL0111</data><data key="edge_source_entity_id">R110_E057</data><data key="edge_relationship_type">reported_through</data><data key="edge_target_entity_id">FORM_SF425</data><data key="edge_operational_context">Federal Financial Report records grantee share/actual cost share, SF425 boxes 10i-k.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0112" source="R110_E057" target="SVC_GRANTSOLUTIONS"><data key="edge_relationship_id">R110_REL0112</data><data key="edge_source_entity_id">R110_E057</data><data key="edge_relationship_type">guided_by_award_terms</data><data key="edge_target_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_operational_context">Award-specific grants administration and reporting terms govern frequency; this does not imply an internal system integration.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0113" source="SVC_ASAP" target="FORM_SF270"><data key="edge_relationship_id">R110_REL0113</data><data key="edge_source_entity_id">SVC_ASAP</data><data key="edge_relationship_type">serves_grant_payment_accounts</data><data key="edge_target_entity_id">FORM_SF270</data><data key="edge_operational_context">Grant awardees must establish ASAP payment account; interim advance/reimbursement uses SF-270.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R110_REL0114" source="R110_E056" target="R110_E057"><data key="edge_relationship_id">R110_REL0114</data><data key="edge_source_entity_id">R110_E056</data><data key="edge_relationship_type">receives_subaward_reports_from</data><data key="edge_target_entity_id">R110_E057</data><data key="edge_operational_context">Qualifying grantees report $30,000 or greater subawards to FSRS under FFATA/2 CFR Part 170.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Explicitly documented process/interface relationship. No unstated automated transport or master-record write is implied.</data></edge><edge id="R111_REL0001" source="R111_E001" target="R111_E002"><data key="edge_relationship_id">R111_REL0001</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">maintains_inventory</data><data key="edge_target_entity_id">R111_E002</data><data key="edge_operational_context">SSA enterprise information-security program includes/refines the identified inventory as part of risk and asset management.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0002" source="R111_E001" target="R111_E003"><data key="edge_relationship_id">R111_REL0002</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">maintains_inventory</data><data key="edge_target_entity_id">R111_E003</data><data key="edge_operational_context">SSA enterprise information-security program includes/refines the identified inventory as part of risk and asset management.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0003" source="R111_E001" target="R111_E004"><data key="edge_relationship_id">R111_REL0003</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">maintains_inventory</data><data key="edge_target_entity_id">R111_E004</data><data key="edge_operational_context">SSA enterprise information-security program includes/refines the identified inventory as part of risk and asset management.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0004" source="R111_E001" target="R111_E005"><data key="edge_relationship_id">R111_REL0004</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">maintains_inventory</data><data key="edge_target_entity_id">R111_E005</data><data key="edge_operational_context">SSA enterprise information-security program includes/refines the identified inventory as part of risk and asset management.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0005" source="R111_E001" target="R111_E006"><data key="edge_relationship_id">R111_REL0005</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">maintains_inventory</data><data key="edge_target_entity_id">R111_E006</data><data key="edge_operational_context">SSA enterprise information-security program includes/refines the identified inventory as part of risk and asset management.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0006" source="R111_E001" target="R111_E007"><data key="edge_relationship_id">R111_REL0006</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">includes_security_domain</data><data key="edge_target_entity_id">R111_E007</data><data key="edge_operational_context">Program/domain evaluated as part of SSA FY2026 FISMA security program.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0007" source="R111_E001" target="R111_E008"><data key="edge_relationship_id">R111_REL0007</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">includes_security_domain</data><data key="edge_target_entity_id">R111_E008</data><data key="edge_operational_context">Program/domain evaluated as part of SSA FY2026 FISMA security program.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0008" source="R111_E001" target="R111_E009"><data key="edge_relationship_id">R111_REL0008</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">includes_security_domain</data><data key="edge_target_entity_id">R111_E009</data><data key="edge_operational_context">Program/domain evaluated as part of SSA FY2026 FISMA security program.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0009" source="R111_E001" target="R111_E011"><data key="edge_relationship_id">R111_REL0009</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">includes_security_domain</data><data key="edge_target_entity_id">R111_E011</data><data key="edge_operational_context">Program/domain evaluated as part of SSA FY2026 FISMA security program.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0010" source="R111_E001" target="R111_E013"><data key="edge_relationship_id">R111_REL0010</data><data key="edge_source_entity_id">R111_E001</data><data key="edge_relationship_type">includes_security_domain</data><data key="edge_target_entity_id">R111_E013</data><data key="edge_operational_context">Program/domain evaluated as part of SSA FY2026 FISMA security program.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0011" source="R111_E007" target="R111_E010"><data key="edge_relationship_id">R111_REL0011</data><data key="edge_source_entity_id">R111_E007</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R111_E010</data><data key="edge_operational_context">Continuous-monitoring recommendation explicitly includes improving vulnerability management.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0012" source="R111_E011" target="R111_E012"><data key="edge_relationship_id">R111_REL0012</data><data key="edge_source_entity_id">R111_E011</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R111_E012</data><data key="edge_operational_context">OIG groups incomplete business-impact analyses with contingency-planning deficiencies.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0013" source="R111_E014" target="PROC_CPIC"><data key="edge_relationship_id">R111_REL0013</data><data key="edge_source_entity_id">R111_E014</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">Named monitoring control in SSA Capital Planning and Investment Control process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0014" source="R111_E015" target="PROC_CPIC"><data key="edge_relationship_id">R111_REL0014</data><data key="edge_source_entity_id">R111_E015</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">Named monitoring control in SSA Capital Planning and Investment Control process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0015" source="R111_E017" target="PROC_CPIC"><data key="edge_relationship_id">R111_REL0015</data><data key="edge_source_entity_id">R111_E017</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">Named monitoring control in SSA Capital Planning and Investment Control process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0016" source="R111_E018" target="PROC_CPIC"><data key="edge_relationship_id">R111_REL0016</data><data key="edge_source_entity_id">R111_E018</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">Named monitoring control in SSA Capital Planning and Investment Control process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0017" source="R111_E019" target="PROC_CPIC"><data key="edge_relationship_id">R111_REL0017</data><data key="edge_source_entity_id">R111_E019</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">Named monitoring control in SSA Capital Planning and Investment Control process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0018" source="R111_E014" target="R111_E023"><data key="edge_relationship_id">R111_REL0018</data><data key="edge_source_entity_id">R111_E014</data><data key="edge_relationship_type">applies_to_role</data><data key="edge_target_entity_id">R111_E023</data><data key="edge_operational_context">Inflight review is semiannual by programmatic area.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0019" source="R111_E015" target="R111_E016"><data key="edge_relationship_id">R111_REL0019</data><data key="edge_source_entity_id">R111_E015</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R111_E016</data><data key="edge_operational_context">OIG testing refers to SSA Value Realization website used to track value measures.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0020" source="R111_E018" target="R111_E020"><data key="edge_relationship_id">R111_REL0020</data><data key="edge_source_entity_id">R111_E018</data><data key="edge_relationship_type">proposes_rating_to</data><data key="edge_target_entity_id">R111_E020</data><data key="edge_operational_context">Program Manager proposes CIO ratings for the Federal IT Dashboard.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0021" source="R111_E019" target="R111_E020"><data key="edge_relationship_id">R111_REL0021</data><data key="edge_source_entity_id">R111_E019</data><data key="edge_relationship_type">publishes_final_rating_to</data><data key="edge_target_entity_id">R111_E020</data><data key="edge_operational_context">CIO final rating for major investments is reported to Federal IT Dashboard.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0022" source="R111_E021" target="PROC_CPIC"><data key="edge_relationship_id">R111_REL0022</data><data key="edge_source_entity_id">R111_E021</data><data key="edge_relationship_type">recommended_for</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">OIG recommends SSA implement EVMS or equivalent to integrate cost, schedule, and performance measurement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0023" source="R111_E022" target="PROC_CPIC"><data key="edge_relationship_id">R111_REL0023</data><data key="edge_source_entity_id">R111_E022</data><data key="edge_relationship_type">recommended_for</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">OIG recommends reestablishing TechStat reviews in CPIC.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0024" source="APP_IT_INVESTMENT_MGMT_TOOL" target="PROC_CPIC"><data key="edge_relationship_id">R111_REL0024</data><data key="edge_source_entity_id">APP_IT_INVESTMENT_MGMT_TOOL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">SSA tracks investment risks, contingency plans, mitigation plans, and resolutions in the Investment Management Tool.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0025" source="R111_E025" target="R111_E024"><data key="edge_relationship_id">R111_REL0025</data><data key="edge_source_entity_id">R111_E025</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">R111_E024</data><data key="edge_operational_context">OIG identifies Technology and Financial Support Branch within Division of Financial Management.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0026" source="PROC_PIR" target="R111_E025"><data key="edge_relationship_id">R111_REL0026</data><data key="edge_source_entity_id">PROC_PIR</data><data key="edge_relationship_type">reviewed_within</data><data key="edge_target_entity_id">R111_E025</data><data key="edge_operational_context">OIG principal entity for PIR audit was Technology and Financial Support Branch.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0027" source="PROC_PIR" target="R111_E026"><data key="edge_relationship_id">R111_REL0027</data><data key="edge_source_entity_id">PROC_PIR</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R111_E026</data><data key="edge_operational_context">SSA PIR policy describes completed report as final output with actionable insights.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0028" source="REPO_PIR_SHARED_SITE" target="R111_E026"><data key="edge_relationship_id">R111_REL0028</data><data key="edge_source_entity_id">REPO_PIR_SHARED_SITE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">R111_E026</data><data key="edge_operational_context">SSA relies on a shared internal website for PIR document storage; report files are distinct from dashboard data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0029" source="DASH_PIR_SUMMARY" target="PROC_PIR"><data key="edge_relationship_id">R111_REL0029</data><data key="edge_source_entity_id">DASH_PIR_SUMMARY</data><data key="edge_relationship_type">summarizes</data><data key="edge_target_entity_id">PROC_PIR</data><data key="edge_operational_context">Agency dashboard holds summary metrics compared with PIR documents on shared site.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0030" source="R111_E027" target="ORG_INSIDER_THREAT_RESILIENCY"><data key="edge_relationship_id">R111_REL0030</data><data key="edge_source_entity_id">R111_E027</data><data key="edge_relationship_type">leads</data><data key="edge_target_entity_id">ORG_INSIDER_THREAT_RESILIENCY</data><data key="edge_operational_context">SSA named a Head of Insider Threat and Resiliency in January 2026.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0031" source="R111_E027" target="R111_E028"><data key="edge_relationship_id">R111_REL0031</data><data key="edge_source_entity_id">R111_E027</data><data key="edge_relationship_type">also_serves_as</data><data key="edge_target_entity_id">R111_E028</data><data key="edge_operational_context">Same official also serves as SSA Information Sharing and Safeguarding Senior Official.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0032" source="PROC_INSIDER_THREAT_PROGRAM" target="R111_E029"><data key="edge_relationship_id">R111_REL0032</data><data key="edge_source_entity_id">PROC_INSIDER_THREAT_PROGRAM</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R111_E029</data><data key="edge_operational_context">Documented operating control within SSA Insider Threat Program.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0033" source="PROC_INSIDER_THREAT_PROGRAM" target="R111_E030"><data key="edge_relationship_id">R111_REL0033</data><data key="edge_source_entity_id">PROC_INSIDER_THREAT_PROGRAM</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R111_E030</data><data key="edge_operational_context">Documented operating control within SSA Insider Threat Program.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0034" source="PROC_INSIDER_THREAT_PROGRAM" target="R111_E031"><data key="edge_relationship_id">R111_REL0034</data><data key="edge_source_entity_id">PROC_INSIDER_THREAT_PROGRAM</data><data key="edge_relationship_type">documents_cases_in</data><data key="edge_target_entity_id">R111_E031</data><data key="edge_operational_context">SSA maintains documented insider-threat inquiry reports and response actions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0035" source="PROC_INSIDER_THREAT_PROGRAM" target="R111_E032"><data key="edge_relationship_id">R111_REL0035</data><data key="edge_source_entity_id">PROC_INSIDER_THREAT_PROGRAM</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R111_E032</data><data key="edge_operational_context">SSA policy requires annual insider-threat self-assessment reporting.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0036" source="R111_E032" target="R111_E033"><data key="edge_relationship_id">R111_REL0036</data><data key="edge_source_entity_id">R111_E032</data><data key="edge_relationship_type">reported_to</data><data key="edge_target_entity_id">R111_E033</data><data key="edge_operational_context">Annual report submitted to NITTF Senior Information Sharing and Safeguarding Steering Committee.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0037" source="R111_E030" target="APP_PIV"><data key="edge_relationship_id">R111_REL0037</data><data key="edge_source_entity_id">R111_E030</data><data key="edge_relationship_type">revokes_or_terminates</data><data key="edge_target_entity_id">APP_PIV</data><data key="edge_operational_context">Separation control includes terminating/revoking credentials; PIV handling is part of documented termination procedures.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0038" source="R111_E034" target="SVC_AMAZON_CONNECT"><data key="edge_relationship_id">R111_REL0038</data><data key="edge_source_entity_id">R111_E034</data><data key="edge_relationship_type">deploys</data><data key="edge_target_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_operational_context">Amazon Connect was progressively deployed across SSA organizations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0039" source="R111_E034" target="R111_E035"><data key="edge_relationship_id">R111_REL0039</data><data key="edge_source_entity_id">R111_E034</data><data key="edge_relationship_type">follows</data><data key="edge_target_entity_id">R111_E035</data><data key="edge_operational_context">OIG documents rollout schedule and staged deployment milestones.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0040" source="SVC_AMAZON_CONNECT" target="APP_ECC"><data key="edge_relationship_id">R111_REL0040</data><data key="edge_source_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_relationship_type">selected_as_future_platform_for</data><data key="edge_target_entity_id">APP_ECC</data><data key="edge_operational_context">Commissioner approved AWS Connect in June 2024 for N8NN and future Enterprise Contact Center solution.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0041" source="CON_AWS_CONNECT_2024" target="SVC_AMAZON_CONNECT"><data key="edge_relationship_id">R111_REL0041</data><data key="edge_source_entity_id">CON_AWS_CONNECT_2024</data><data key="edge_relationship_type">funds</data><data key="edge_target_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_operational_context">Cloud BPA Call Order 5 funded AWS Connect CCaaS beginning August 1, 2024.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0042" source="PROC_SSI_ABAP" target="R111_E036"><data key="edge_relationship_id">R111_REL0042</data><data key="edge_source_entity_id">PROC_SSI_ABAP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R111_E036</data><data key="edge_operational_context">New SSI claim is established on Person Multiple Claim Summary page for SSI Claims System ABAP.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0043" source="R111_E036" target="R111_E037"><data key="edge_relationship_id">R111_REL0043</data><data key="edge_source_entity_id">R111_E036</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">R111_E037</data><data key="edge_operational_context">Claim setup proceeds to Supplemental Security Income Application page.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0044" source="R111_E037" target="R111_E038"><data key="edge_relationship_id">R111_REL0044</data><data key="edge_source_entity_id">R111_E037</data><data key="edge_relationship_type">captures</data><data key="edge_target_entity_id">R111_E038</data><data key="edge_operational_context">Abbreviated application reason determines additional screens in path.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0045" source="PROC_SSI_ABAP" target="R111_E039"><data key="edge_relationship_id">R111_REL0045</data><data key="edge_source_entity_id">PROC_SSI_ABAP</data><data key="edge_relationship_type">uses_manual_input_form</data><data key="edge_target_entity_id">R111_E039</data><data key="edge_operational_context">Paper abbreviated applications use SSA-462 to establish systems record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0046" source="PROC_SSI_ABAP" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R111_REL0046</data><data key="edge_source_entity_id">PROC_SSI_ABAP</data><data key="edge_relationship_type">implemented_in</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">SSA says SSI Claims System is preferred claims-taking method for ABAP.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0047" source="R111_E040" target="R111_E041"><data key="edge_relationship_id">R111_REL0047</data><data key="edge_source_entity_id">R111_E040</data><data key="edge_relationship_type">uses_work_control</data><data key="edge_target_entity_id">R111_E041</data><data key="edge_operational_context">PC diaries for pending CDB determination where DDIB process cannot be used.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0048" source="R111_E040" target="APP_MDW_AI"><data key="edge_relationship_id">R111_REL0048</data><data key="edge_source_entity_id">R111_E040</data><data key="edge_relationship_type">notifies_processing_center_via</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">Field office may notify PC via Modernized Development Worksheet that disability determination is pending.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0049" source="R111_E040" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">R111_REL0049</data><data key="edge_source_entity_id">R111_E040</data><data key="edge_relationship_type">can_notify_processing_center_via</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">Policy also permits faxing into PC paperless queue.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0050" source="R111_E042" target="SYS_MBR"><data key="edge_relationship_id">R111_REL0050</data><data key="edge_source_entity_id">R111_E042</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Disability determination is posted in BENE ENT line on MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0051" source="R111_E040" target="R111_E042"><data key="edge_relationship_id">R111_REL0051</data><data key="edge_source_entity_id">R111_E040</data><data key="edge_relationship_type">posts_determination_to</data><data key="edge_target_entity_id">R111_E042</data><data key="edge_operational_context">When disability is established, PC posts determination to MBR BENE ENT line.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0052" source="R111_E042" target="R111_E043"><data key="edge_relationship_id">R111_REL0052</data><data key="edge_source_entity_id">R111_E042</data><data key="edge_relationship_type">enables</data><data key="edge_target_entity_id">R111_E043</data><data key="edge_operational_context">Posting disability determination to BENE ENT enables automatic conversion.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R111_REL0053" source="R111_E043" target="SYS_MBR"><data key="edge_relationship_id">R111_REL0053</data><data key="edge_source_entity_id">R111_E043</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Automatic conversion continues child entitlement based on disability in MBR processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship limited to the documented operational context; no additional transport, hosting, persistence, or automatic master-record behavior is inferred.</data></edge><edge id="R112_R001" source="R112_E001" target="R112_E002"><data key="edge_relationship_id">R112_R001</data><data key="edge_source_entity_id">R112_E001</data><data key="edge_relationship_type">records_flag</data><data key="edge_target_entity_id">R112_E002</data><data key="edge_operational_context">Fraud allegation enters Y flag per nonreceipt payment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R002" source="R112_E002" target="R112_E003"><data key="edge_relationship_id">R112_R002</data><data key="edge_source_entity_id">R112_E002</data><data key="edge_relationship_type">processed_by</data><data key="edge_target_entity_id">R112_E003</data><data key="edge_operational_context">Type B fraud nonreceipt is processed by REACT and generates trace.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R003" source="R112_E003" target="R112_E004"><data key="edge_relationship_id">R112_R003</data><data key="edge_source_entity_id">R112_E003</data><data key="edge_relationship_type">posts_event_to</data><data key="edge_target_entity_id">R112_E004</data><data key="edge_operational_context">REACT allegation becomes PHUS event 069.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R004" source="R112_E004" target="DB_PHUS"><data key="edge_relationship_id">R112_R004</data><data key="edge_source_entity_id">R112_E004</data><data key="edge_relationship_type">displayed_in</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">PHUS stores fraud allegation event 069.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R005" source="R112_E001" target="R112_E005"><data key="edge_relationship_id">R112_R005</data><data key="edge_source_entity_id">R112_E001</data><data key="edge_relationship_type">may_request</data><data key="edge_target_entity_id">R112_E005</data><data key="edge_operational_context">Direct Express cases use R16 request.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R006" source="R112_E001" target="R112_E008"><data key="edge_relationship_id">R112_R006</data><data key="edge_source_entity_id">R112_E001</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">R112_E008</data><data key="edge_operational_context">Allegation triggers selected reimbursement decision.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R007" source="R112_E008" target="APP_CPS"><data key="edge_relationship_id">R112_R007</data><data key="edge_source_entity_id">R112_E008</data><data key="edge_relationship_type">may_issue_through</data><data key="edge_target_entity_id">APP_CPS</data><data key="edge_operational_context">A qualifying replacement may use CPS critical payment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R008" source="R112_E008" target="PROC_AOTP"><data key="edge_relationship_id">R112_R008</data><data key="edge_source_entity_id">R112_E008</data><data key="edge_relationship_type">may_issue_through</data><data key="edge_target_entity_id">PROC_AOTP</data><data key="edge_operational_context">Title XVI replacement may use automated one-time payment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R009" source="R112_E008" target="R112_E006"><data key="edge_relationship_id">R112_R009</data><data key="edge_source_entity_id">R112_E008</data><data key="edge_relationship_type">documents_processing_note_on</data><data key="edge_target_entity_id">R112_E006</data><data key="edge_operational_context">Fraud note on CPS Critical Payment Details CRSN screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R010" source="R112_E006" target="APP_CPS"><data key="edge_relationship_id">R112_R010</data><data key="edge_source_entity_id">R112_E006</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">APP_CPS</data><data key="edge_operational_context">CRSN Critical Payment Details is a CPS user interface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R011" source="R112_E008" target="FORM_SSA795"><data key="edge_relationship_id">R112_R011</data><data key="edge_source_entity_id">R112_E008</data><data key="edge_relationship_type">retains_signed_statement</data><data key="edge_target_entity_id">FORM_SSA795</data><data key="edge_operational_context">Title II CPS/IP fraud case requires SSA-795.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R012" source="R112_E008" target="DATA_SSA8102"><data key="edge_relationship_id">R112_R012</data><data key="edge_source_entity_id">R112_E008</data><data key="edge_relationship_type">retains_receipt</data><data key="edge_target_entity_id">DATA_SSA8102</data><data key="edge_operational_context">Title XVI immediate payment requires SSA-8102.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R013" source="R112_E008" target="R112_E007"><data key="edge_relationship_id">R112_R013</data><data key="edge_source_entity_id">R112_E008</data><data key="edge_relationship_type">retains_monthly_computation</data><data key="edge_target_entity_id">R112_E007</data><data key="edge_operational_context">Title XVI A-OTP requires SSA-4904-U2.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R014" source="R112_E007" target="REPO_EF"><data key="edge_relationship_id">R112_R014</data><data key="edge_source_entity_id">R112_E007</data><data key="edge_relationship_type">filed_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Signed SSI fraud-supporting SSA-4904-U2 is imaged to electronic folder or NDRED.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R015" source="R112_E001" target="SYS_MBR"><data key="edge_relationship_id">R112_R015</data><data key="edge_source_entity_id">R112_E001</data><data key="edge_relationship_type">records_special_message_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Fraud-related CPS/A-OTP special message may be posted on MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R016" source="R112_E001" target="SYS_SSR"><data key="edge_relationship_id">R112_R016</data><data key="edge_source_entity_id">R112_E001</data><data key="edge_relationship_type">records_remarks_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Fraud-related replacement remarks may be posted to SSR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R017" source="R112_E009" target="SVC_TCIS"><data key="edge_relationship_id">R112_R017</data><data key="edge_source_entity_id">R112_E009</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">TCIS Integrated View is a documented claims user interface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R018" source="R112_E009" target="R112_E010"><data key="edge_relationship_id">R112_R018</data><data key="edge_source_entity_id">R112_E009</data><data key="edge_relationship_type">renders_for_printing</data><data key="edge_target_entity_id">R112_E010</data><data key="edge_operational_context">TCIS Integrated View provides claim form printing; not available for Direct Express.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R019" source="R112_E009" target="R112_E011"><data key="edge_relationship_id">R112_R019</data><data key="edge_source_entity_id">R112_E009</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">R112_E011</data><data key="edge_operational_context">TCIS ENR claim-detail disposition/resent/reprint state.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R020" source="R112_E010" target="EX_ENR"><data key="edge_relationship_id">R112_R020</data><data key="edge_source_entity_id">R112_E010</data><data key="edge_relationship_type">issued_after_unauthorized</data><data key="edge_target_entity_id">EX_ENR</data><data key="edge_operational_context">Form used for alleged payment redirection via automated enrollment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R021" source="R112_E010" target="REPO_EF"><data key="edge_relationship_id">R112_R021</data><data key="edge_source_entity_id">R112_E010</data><data key="edge_relationship_type">retained_as_copy_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">SSA can place a copy of completed claim form in electronic folder or NDRED.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R022" source="R112_E010" target="R112_E005"><data key="edge_relationship_id">R112_R022</data><data key="edge_source_entity_id">R112_E010</data><data key="edge_relationship_type">excluded_for</data><data key="edge_target_entity_id">R112_E005</data><data key="edge_operational_context">Direct Express redirections use R16 instead of EFT Claim Form.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R023" source="R112_E011" target="R112_E012"><data key="edge_relationship_id">R112_R023</data><data key="edge_source_entity_id">R112_E011</data><data key="edge_relationship_type">exposes_status_for</data><data key="edge_target_entity_id">R112_E012</data><data key="edge_operational_context">Undeliverable / resent states drive address follow-up.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R024" source="R112_E012" target="SYS_MBR"><data key="edge_relationship_id">R112_R024</data><data key="edge_source_entity_id">R112_E012</data><data key="edge_relationship_type">compares_current_mail_address_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For Title II claims, staff review current MBR address before reprint/resend.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R025" source="R112_E012" target="SYS_SSR"><data key="edge_relationship_id">R112_R025</data><data key="edge_source_entity_id">R112_E012</data><data key="edge_relationship_type">compares_current_mail_address_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">For Title XVI claims, staff review current SSR address before reprint/resend.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R026" source="R112_E012" target="R112_E009"><data key="edge_relationship_id">R112_R026</data><data key="edge_source_entity_id">R112_E012</data><data key="edge_relationship_type">generates_followup_in</data><data key="edge_target_entity_id">R112_E009</data><data key="edge_operational_context">Claim form reprint after identity and address review uses TCIS Integrated View.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R027" source="R112_E013" target="ORG_TREASURY"><data key="edge_relationship_id">R112_R027</data><data key="edge_source_entity_id">R112_E013</data><data key="edge_relationship_type">supplied_by</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Treasury transmits FI returned credit detail.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R028" source="R112_E013" target="R112_E017"><data key="edge_relationship_id">R112_R028</data><data key="edge_source_entity_id">R112_E013</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R112_E017</data><data key="edge_operational_context">Processing-center technicians apply credit after reviewing ENR debit detail.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R029" source="R112_E013" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">R112_R029</data><data key="edge_source_entity_id">R112_E013</data><data key="edge_relationship_type">received_in</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">Returned credit detail is received into processing-center Paperless.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R030" source="R112_E014" target="R112_E015"><data key="edge_relationship_id">R112_R030</data><data key="edge_source_entity_id">R112_E014</data><data key="edge_relationship_type">posts_to</data><data key="edge_target_entity_id">R112_E015</data><data key="edge_operational_context">OBASA partial returned credit posted to SSR OPRR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R031" source="R112_E015" target="SYS_SSR"><data key="edge_relationship_id">R112_R031</data><data key="edge_source_entity_id">R112_E015</data><data key="edge_relationship_type">segment_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">OPRR records are in the SSR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R032" source="R112_E015" target="R112_E016"><data key="edge_relationship_id">R112_R032</data><data key="edge_source_entity_id">R112_E015</data><data key="edge_relationship_type">uses_credit_code</data><data key="edge_target_entity_id">R112_E016</data><data key="edge_operational_context">Financial institution remittance posted with DOC 534.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R033" source="R112_E017" target="APP_DMS"><data key="edge_relationship_id">R112_R033</data><data key="edge_source_entity_id">R112_E017</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">RRRE is DMS ROAR remittance exception screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R034" source="R112_E017" target="APP_ROAR"><data key="edge_relationship_id">R112_R034</data><data key="edge_source_entity_id">R112_E017</data><data key="edge_relationship_type">adjusts_debt_on</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">Returned FI credit reduces/removes ROAR overpayment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R035" source="R112_E017" target="R112_E021"><data key="edge_relationship_id">R112_R035</data><data key="edge_source_entity_id">R112_E017</data><data key="edge_relationship_type">adjusts_nonentitled_debtor</data><data key="edge_target_entity_id">R112_E021</data><data key="edge_operational_context">Fraud credit applied to X-subscript nonentitled debtor record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R036" source="R112_E021" target="APP_ROAR"><data key="edge_relationship_id">R112_R036</data><data key="edge_source_entity_id">R112_E021</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">Fraud X-subscript is carried on ROAR debt record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R037" source="R112_E021" target="R112_E018"><data key="edge_relationship_id">R112_R037</data><data key="edge_source_entity_id">R112_E021</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">R112_E018</data><data key="edge_operational_context">Fraud X-subscript overpayment controlled by 90-day diary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R038" source="R112_E018" target="UI_DMS_DRDY"><data key="edge_relationship_id">R112_R038</data><data key="edge_source_entity_id">R112_E018</data><data key="edge_relationship_type">managed_through</data><data key="edge_target_entity_id">UI_DMS_DRDY</data><data key="edge_operational_context">ROAR DRDY screen holds 90-day diary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R039" source="R112_E018" target="R112_E022"><data key="edge_relationship_id">R112_R039</data><data key="edge_source_entity_id">R112_E018</data><data key="edge_relationship_type">closed_with</data><data key="edge_target_entity_id">R112_E022</data><data key="edge_operational_context">Listing code 119 after matured 90-day diary where no new guidance or credit.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R040" source="R112_E020" target="R112_E019"><data key="edge_relationship_id">R112_R040</data><data key="edge_source_entity_id">R112_E020</data><data key="edge_relationship_type">suspends_collection_for</data><data key="edge_target_entity_id">R112_E019</data><data key="edge_operational_context">Treasury later credit after NT TAC writeoff generates B4 work.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R041" source="R112_E019" target="SYS_SSR"><data key="edge_relationship_id">R112_R041</data><data key="edge_source_entity_id">R112_E019</data><data key="edge_relationship_type">alerts_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR remittance excess decision appears in MPMT and diary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R042" source="R112_E023" target="DATA_DDFP_BLOCK"><data key="edge_relationship_id">R112_R042</data><data key="edge_source_entity_id">R112_E023</data><data key="edge_relationship_type">enforces</data><data key="edge_target_entity_id">DATA_DDFP_BLOCK</data><data key="edge_operational_context">Fraud prevention block precludes direct deposit changes by telephone.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R043" source="R112_E023" target="R112_E024"><data key="edge_relationship_id">R112_R043</data><data key="edge_source_entity_id">R112_E023</data><data key="edge_relationship_type">may_return</data><data key="edge_target_entity_id">R112_E024</data><data key="edge_operational_context">Denied invalid or incomplete financial institution forms can be returned.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R044" source="R112_E023" target="R112_E025"><data key="edge_relationship_id">R112_R044</data><data key="edge_source_entity_id">R112_E023</data><data key="edge_relationship_type">may_include_cover</data><data key="edge_target_entity_id">R112_E025</data><data key="edge_operational_context">Invalid account title request returned with SSA-L1199.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R045" source="R112_E025" target="R112_E024"><data key="edge_relationship_id">R112_R045</data><data key="edge_source_entity_id">R112_E025</data><data key="edge_relationship_type">encloses</data><data key="edge_target_entity_id">R112_E024</data><data key="edge_operational_context">SSA-L1199 is a cover for rejected SF-1199A.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R046" source="R112_E026" target="SYS_MBR"><data key="edge_relationship_id">R112_R046</data><data key="edge_source_entity_id">R112_E026</data><data key="edge_relationship_type">updates_banking_information_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Documented staff entry through MCS/POS/MACADE causes Switzerland IDD bank-data processing on MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R047" source="R112_E026" target="SVC_ITS_GOV"><data key="edge_relationship_id">R112_R047</data><data key="edge_source_entity_id">R112_E026</data><data key="edge_relationship_type">requires_dual_entry_at</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">SSA explicitly requires parallel same-day ITS.gov input.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R048" source="R112_E026" target="R112_E027"><data key="edge_relationship_id">R112_R048</data><data key="edge_source_entity_id">R112_E026</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R112_E027</data><data key="edge_operational_context">Swiss bank data encoded into MBR routing/account fields.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R049" source="R112_E028" target="R112_E027"><data key="edge_relationship_id">R112_R049</data><data key="edge_source_entity_id">R112_E028</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R112_E027</data><data key="edge_operational_context">Beneficiary-submitted IBAN is the input source for derived routing/account codes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R050" source="R112_E026" target="R112_E029"><data key="edge_relationship_id">R112_R050</data><data key="edge_source_entity_id">R112_E026</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R112_E029</data><data key="edge_operational_context">Foreign address PCOC=8 must already be reflected on MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R051" source="R112_E029" target="SYS_MBR"><data key="edge_relationship_id">R112_R051</data><data key="edge_source_entity_id">R112_E029</data><data key="edge_relationship_type">checked_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PCOC=8 tested against current MBR address; not an automatic update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R052" source="R112_E026" target="DATA_ITS_BENEFICIARY_ADDRESS"><data key="edge_relationship_id">R112_R052</data><data key="edge_source_entity_id">R112_E026</data><data key="edge_relationship_type">records_beneficiary_address_at</data><data key="edge_target_entity_id">DATA_ITS_BENEFICIARY_ADDRESS</data><data key="edge_operational_context">ITS.gov requires beneficiary address in CH/Town/Name representation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R053" source="R112_E026" target="DATA_ITS_BANK_ADDRESS"><data key="edge_relationship_id">R112_R053</data><data key="edge_source_entity_id">R112_E026</data><data key="edge_relationship_type">records_bank_address_at</data><data key="edge_target_entity_id">DATA_ITS_BANK_ADDRESS</data><data key="edge_operational_context">ITS.gov also records bank address separately from beneficiary address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R054" source="R112_E026" target="ORG_FRBKC"><data key="edge_relationship_id">R112_R054</data><data key="edge_source_entity_id">R112_E026</data><data key="edge_relationship_type">relies_on_payment_routing_via</data><data key="edge_target_entity_id">ORG_FRBKC</data><data key="edge_operational_context">FRB Kansas City routes to Swiss processing bank and local FI.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R055" source="R112_E030" target="UI_MCS_RPOC"><data key="edge_relationship_id">R112_R055</data><data key="edge_source_entity_id">R112_E030</data><data key="edge_relationship_type">checks_prior_documentation_on</data><data key="edge_target_entity_id">UI_MCS_RPOC</data><data key="edge_operational_context">Current adjudicator reviews RPOC and evidence documentation during adjudication.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R056" source="R112_E031" target="UI_MCS_RPOC"><data key="edge_relationship_id">R112_R056</data><data key="edge_source_entity_id">R112_E031</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">UI_MCS_RPOC</data><data key="edge_operational_context">MCS RPOC transmitted entries locked, five screens per claimant segment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R057" source="R112_E032" target="R112_E033"><data key="edge_relationship_id">R112_R057</data><data key="edge_source_entity_id">R112_E032</data><data key="edge_relationship_type">publishes_assumption</data><data key="edge_target_entity_id">R112_E033</data><data key="edge_operational_context">Recovery assumptions described in OACT disability memorandum.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R058" source="R112_E032" target="R112_E034"><data key="edge_relationship_id">R112_R058</data><data key="edge_source_entity_id">R112_E032</data><data key="edge_relationship_type">publishes_assumption</data><data key="edge_target_entity_id">R112_E034</data><data key="edge_operational_context">Mortality improvement assumptions described in memo.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R059" source="R112_E032" target="R112_E035"><data key="edge_relationship_id">R112_R059</data><data key="edge_source_entity_id">R112_E032</data><data key="edge_relationship_type">publishes_projection</data><data key="edge_target_entity_id">R112_E035</data><data key="edge_operational_context">Disability prevalence outlook is published in memo.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R060" source="R112_E032" target="R112_E036"><data key="edge_relationship_id">R112_R060</data><data key="edge_source_entity_id">R112_E032</data><data key="edge_relationship_type">documents_method</data><data key="edge_target_entity_id">R112_E036</data><data key="edge_operational_context">Short and long-term model timing is explicitly documented.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R061" source="R112_E032" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R112_R061</data><data key="edge_source_entity_id">R112_E032</data><data key="edge_relationship_type">supports_report</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Memorandum provides assumptions used in 2026 Trustees report.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R062" source="R112_E035" target="R112_E033"><data key="edge_relationship_id">R112_R062</data><data key="edge_source_entity_id">R112_E035</data><data key="edge_relationship_type">derived_from_assumptions</data><data key="edge_target_entity_id">R112_E033</data><data key="edge_operational_context">Long-range prevalence affected by recovered beneficiaries and incidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R112_R063" source="R112_E035" target="R112_E034"><data key="edge_relationship_id">R112_R063</data><data key="edge_source_entity_id">R112_E035</data><data key="edge_relationship_type">derived_from_assumptions</data><data key="edge_target_entity_id">R112_E034</data><data key="edge_operational_context">Mortality termination component in long-run disability projection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Observed process and evidence only. No undocumented automated sync, deployment, database, or retention inferred.</data></edge><edge id="R113_R001" source="APP_FTD" target="R113_E002"><data key="edge_relationship_id">R113_R001</data><data key="edge_source_entity_id">APP_FTD</data><data key="edge_relationship_type">exposes_result_on</data><data key="edge_target_entity_id">R113_E002</data><data key="edge_operational_context">FTD results appear on Data Results screen; staff cannot duplicate the screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R002" source="R113_E002" target="R113_E003"><data key="edge_relationship_id">R113_R002</data><data key="edge_source_entity_id">R113_E002</data><data key="edge_relationship_type">subject_to_no_copy_rule</data><data key="edge_target_entity_id">R113_E003</data><data key="edge_operational_context">FTD results screen shall never be copied or printed by technician; CBP handles direct copies for requester.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R003" source="R113_E004" target="APP_FTD"><data key="edge_relationship_id">R113_R003</data><data key="edge_source_entity_id">R113_E004</data><data key="edge_relationship_type">offers_query_feature</data><data key="edge_target_entity_id">APP_FTD</data><data key="edge_operational_context">FTD is available on CCE SSI Claims Actions page.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R004" source="APP_CCE" target="R113_E004"><data key="edge_relationship_id">R113_R004</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">contains_ssi_actions_page</data><data key="edge_target_entity_id">R113_E004</data><data key="edge_operational_context">CCE contains SSI Claims Actions page; no database technology established.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R005" source="APP_FTD" target="R113_E008"><data key="edge_relationship_id">R113_R005</data><data key="edge_source_entity_id">APP_FTD</data><data key="edge_relationship_type">provides_third_party_travel_report</data><data key="edge_target_entity_id">R113_E008</data><data key="edge_operational_context">DHS ADIS results used as leads; require claimant verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R006" source="R113_E008" target="R113_E001"><data key="edge_relationship_id">R113_R006</data><data key="edge_source_entity_id">R113_E008</data><data key="edge_relationship_type">requires_verification_through</data><data key="edge_target_entity_id">R113_E001</data><data key="edge_operational_context">Travel information requires independent verification before SSI payment action.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R007" source="APP_FTD" target="R113_E005"><data key="edge_relationship_id">R113_R007</data><data key="edge_source_entity_id">APP_FTD</data><data key="edge_relationship_type">supports_2026_citizen_redeterminations</data><data key="edge_target_entity_id">R113_E005</data><data key="edge_operational_context">Effective Jan 2 2026 selected U.S. citizen SSI RZ workloads added.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R008" source="APP_FTD" target="R113_E006"><data key="edge_relationship_id">R113_R008</data><data key="edge_source_entity_id">APP_FTD</data><data key="edge_relationship_type">supports_2026_initial_claim_development</data><data key="edge_target_entity_id">R113_E006</data><data key="edge_operational_context">Effective Jan 2 2026 selected SSI initial-payment development; noncitizen all cases and citizen certain cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R009" source="APP_FTD" target="R113_E007"><data key="edge_relationship_id">R113_R009</data><data key="edge_source_entity_id">APP_FTD</data><data key="edge_relationship_type">excludes_current_rsdi_use</data><data key="edge_target_entity_id">R113_E007</data><data key="edge_operational_context">Dec 2025 instructions say not yet available in RSDI. Do not promote planned expansion to operational.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R010" source="EXT_DHS_ADIS" target="R113_E008"><data key="edge_relationship_id">R113_R010</data><data key="edge_source_entity_id">EXT_DHS_ADIS</data><data key="edge_relationship_type">provides_source_records_for</data><data key="edge_target_entity_id">R113_E008</data><data key="edge_operational_context">ADIS is DHS-maintained entry/exit repository; FTD provides query access rather than declared replicated master data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R011" source="ORG_CBP" target="R113_E008"><data key="edge_relationship_id">R113_R011</data><data key="edge_source_entity_id">ORG_CBP</data><data key="edge_relationship_type">owns_public_copies_of</data><data key="edge_target_entity_id">R113_E008</data><data key="edge_operational_context">Employees refer FTD travel results requests to CBP Information Center.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R012" source="APP_ERPS" target="R113_E009"><data key="edge_relationship_id">R113_R012</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">supports_multi_payee_closure</data><data key="edge_target_entity_id">R113_E009</data><data key="edge_operational_context">Payee cessation requires active roster validation, new selection, payment-record changes and final accounting.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R013" source="R113_E009" target="R113_E010"><data key="edge_relationship_id">R113_R013</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">uses_rapid_check_when_warranted</data><data key="edge_target_entity_id">R113_E010</data><data key="edge_operational_context">FO/RO determine quick response site review when mass payee closes or fails.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R014" source="APP_ERPS" target="R113_E011"><data key="edge_relationship_id">R113_R014</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">has_active_beneficiary_screen</data><data key="edge_target_entity_id">R113_E011</data><data key="edge_operational_context">Current active list retrieved for organizational or individual payee before closure.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R015" source="APP_ERPS" target="R113_E012"><data key="edge_relationship_id">R113_R015</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">has_terminated_beneficiary_screen</data><data key="edge_target_entity_id">R113_E012</data><data key="edge_operational_context">Terminated list used for death-overpayment work.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R016" source="APP_ERPS" target="R113_E013"><data key="edge_relationship_id">R113_R016</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">has_organization_termination_screen</data><data key="edge_target_entity_id">R113_E013</data><data key="edge_operational_context">Management uses termination screen once changes for beneficiaries completed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R017" source="APP_ERPS" target="R113_E014"><data key="edge_relationship_id">R113_R017</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">has_fee_for_service_screen</data><data key="edge_target_entity_id">R113_E014</data><data key="edge_operational_context">FFS payees entering stop date and reason before organization termination.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R018" source="R113_E009" target="R113_E015"><data key="edge_relationship_id">R113_R018</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">receives_beneficiary_address_from</data><data key="edge_target_entity_id">R113_E015</data><data key="edge_operational_context">Departing payee supplies current or last-known beneficiary residence addresses; needs reconciliation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R019" source="R113_E016" target="R113_E011"><data key="edge_relationship_id">R113_R019</data><data key="edge_source_entity_id">R113_E016</data><data key="edge_relationship_type">compares_roster_using</data><data key="edge_target_entity_id">R113_E011</data><data key="edge_operational_context">Compare eRPS beneficiary list to information provided by departing payee, resolve discrepancies.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R020" source="UI_ERPS_ROC_DETAILS" target="R113_E016"><data key="edge_relationship_id">R113_R020</data><data key="edge_source_entity_id">UI_ERPS_ROC_DETAILS</data><data key="edge_relationship_type">records_roster_reconciliation_for</data><data key="edge_target_entity_id">R113_E016</data><data key="edge_operational_context">Document contacts and reported data in eRPS Report of Contact Details.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R021" source="R113_E009" target="R113_E016"><data key="edge_relationship_id">R113_R021</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">requires_roster_reconciliation</data><data key="edge_target_entity_id">R113_E016</data><data key="edge_operational_context">Reconcile before all beneficiary relationships ended.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R022" source="R113_E009" target="R113_E017"><data key="edge_relationship_id">R113_R022</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">uses_title_ii_final_accounting</data><data key="edge_target_entity_id">R113_E017</data><data key="edge_operational_context">Title II former payee accounting selected by automated eligibility criteria.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R023" source="R113_E009" target="R113_E018"><data key="edge_relationship_id">R113_R023</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">uses_title_xvi_final_accounting</data><data key="edge_target_entity_id">R113_E018</data><data key="edge_operational_context">Title XVI/concurrent cases involve staff-driven selection for final accounting.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R024" source="R113_E009" target="R113_E020"><data key="edge_relationship_id">R113_R024</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">requires_conserved_funds_action</data><data key="edge_target_entity_id">R113_E020</data><data key="edge_operational_context">Return funds for living beneficiary reissuance; deceased beneficiary funds belong to estate.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R025" source="R113_E020" target="R113_E019"><data key="edge_relationship_id">R113_R025</data><data key="edge_source_entity_id">R113_E020</data><data key="edge_relationship_type">requires_collective_account_allocation</data><data key="edge_target_entity_id">R113_E019</data><data key="edge_operational_context">Former payee provides ledger mapping collective funds to each beneficiary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R026" source="R113_E012" target="R113_E021"><data key="edge_relationship_id">R113_R026</data><data key="edge_source_entity_id">R113_E012</data><data key="edge_relationship_type">displays_death_overpayment_indicator</data><data key="edge_target_entity_id">R113_E021</data><data key="edge_operational_context">Former payee death-overpayment indicator is in terminated list; reconciled in DMS NED.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R027" source="R113_E021" target="APP_NED"><data key="edge_relationship_id">R113_R027</data><data key="edge_source_entity_id">R113_E021</data><data key="edge_relationship_type">may_require_nonentitled_debt_in</data><data key="edge_target_entity_id">APP_NED</data><data key="edge_operational_context">Death overpayment data in eRPS and Non-Entitled Debtor; validate reimbursement separately.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R028" source="R113_E009" target="R113_E022"><data key="edge_relationship_id">R113_R028</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">subject_to_identity_address_privacy_control</data><data key="edge_target_entity_id">R113_E022</data><data key="edge_operational_context">Current POMS limits reciprocal disclosure of former/new payee identity and address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R029" source="R113_E009" target="SYS_MBR"><data key="edge_relationship_id">R113_R029</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">requires_program_record_follow_up_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">eRPS payee termination does not itself terminate MBR payee relationship; FO must select new payee or direct pay.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R030" source="R113_E009" target="SYS_SSR"><data key="edge_relationship_id">R113_R030</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">requires_program_record_follow_up_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">eRPS payee termination does not itself terminate SSR payee relationship; independent downstream action.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R031" source="R113_E009" target="APP_RPMA"><data key="edge_relationship_id">R113_R031</data><data key="edge_source_entity_id">R113_E009</data><data key="edge_relationship_type">records_monitoring_when_applicable_in</data><data key="edge_target_entity_id">APP_RPMA</data><data key="edge_operational_context">If payee under expanded monitoring, update Representative Payee Monitoring Application.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R032" source="ORG_DHS" target="R113_E025"><data key="edge_relationship_id">R113_R032</data><data key="edge_source_entity_id">ORG_DHS</data><data key="edge_relationship_type">can_request_alien_locator_data_via</data><data key="edge_target_entity_id">R113_E025</data><data key="edge_operational_context">DHS request may require OPD processing; ensure alien identity/location or valid law enforcement purpose.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R033" source="R113_E025" target="R113_E023"><data key="edge_relationship_id">R113_R033</data><data key="edge_source_entity_id">R113_E025</data><data key="edge_relationship_type">initiates_permitted_disclosure</data><data key="edge_target_entity_id">R113_E023</data><data key="edge_operational_context">OPD handles requests, controls disclosure purposes and source record applicability.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R034" source="R113_E023" target="R113_E024"><data key="edge_relationship_id">R113_R034</data><data key="edge_source_entity_id">R113_E023</data><data key="edge_relationship_type">may_disclose</data><data key="edge_target_entity_id">R113_E024</data><data key="edge_operational_context">Disclosed data can include contact and banking fields but no source-master authority inferred.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R035" source="ORG_SSA_OPD" target="R113_E023"><data key="edge_relationship_id">R113_R035</data><data key="edge_source_entity_id">ORG_SSA_OPD</data><data key="edge_relationship_type">manages_alien_disclosure</data><data key="edge_target_entity_id">R113_E023</data><data key="edge_operational_context">OPD receives DHS requests from staff and evaluates legal grounds.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R036" source="SYS_NUMIDENT" target="R113_E023"><data key="edge_relationship_id">R113_R036</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">may_supply_identifying_attributes_for</data><data key="edge_target_entity_id">R113_E023</data><data key="edge_operational_context">Numident CSP codes can establish prior alien status; not all locators proven to originate in Numident.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R037" source="ORG_DHS" target="R113_E026"><data key="edge_relationship_id">R113_R037</data><data key="edge_source_entity_id">ORG_DHS</data><data key="edge_relationship_type">receives_annual_nonwork_earnings_data</data><data key="edge_target_entity_id">R113_E026</data><data key="edge_operational_context">SSA annually electronically discloses specified post-1997 nonwork SSN earnings information to DHS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R038" source="R113_E026" target="R113_E027"><data key="edge_relationship_id">R113_R038</data><data key="edge_source_entity_id">R113_E026</data><data key="edge_relationship_type">includes_identifying_and_address_fields</data><data key="edge_target_entity_id">R113_E027</data><data key="edge_operational_context">POMS identifies alien name/address, employer/reporting party name/address and earnings as permitted fields.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R039" source="R113_E026" target="R113_E028"><data key="edge_relationship_id">R113_R039</data><data key="edge_source_entity_id">R113_E026</data><data key="edge_relationship_type">subject_to_pre1997_limitation</data><data key="edge_target_entity_id">R113_E028</data><data key="edge_operational_context">Pre-1997 tax-information disclosure limited; OPD referral required.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R040" source="R113_E023" target="R113_E029"><data key="edge_relationship_id">R113_R040</data><data key="edge_source_entity_id">R113_E023</data><data key="edge_relationship_type">excludes_w2_suspense_and_nomatch_details</data><data key="edge_target_entity_id">R113_E029</data><data key="edge_operational_context">No disclosure to DHS about W-2 suspense or whether EDCOR/DECOR notices delivered or qualified.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R041" source="EX_EVERIFY" target="R113_E023"><data key="edge_relationship_id">R113_R041</data><data key="edge_source_entity_id">EX_EVERIFY</data><data key="edge_relationship_type">uses_separate_numident_routine_use</data><data key="edge_target_entity_id">R113_E023</data><data key="edge_operational_context">E-Verify has a separate Numident SORN routine use; not interchangeable with DHS identity/locator disclosure.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R042" source="R113_E030" target="R113_E033"><data key="edge_relationship_id">R113_R042</data><data key="edge_source_entity_id">R113_E030</data><data key="edge_relationship_type">subject_to_receipt_window</data><data key="edge_target_entity_id">R113_E033</data><data key="edge_operational_context">SSA accepts valid SSA-7050-F4 earnings consent only if received within 120 days of signature.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R043" source="R113_E030" target="R113_E032"><data key="edge_relationship_id">R113_R043</data><data key="edge_source_entity_id">R113_E030</data><data key="edge_relationship_type">requires_separate_tax_consent</data><data key="edge_target_entity_id">R113_E032</data><data key="edge_operational_context">Tax return information and medical or non-tax records cannot share one combined consent request.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R044" source="R113_E030" target="R113_E038"><data key="edge_relationship_id">R113_R044</data><data key="edge_source_entity_id">R113_E030</data><data key="edge_relationship_type">provides_detail_earnings_consent_under</data><data key="edge_target_entity_id">R113_E038</data><data key="edge_operational_context">Detailed earnings requests must identify taxpayer, recipient, record type, period, signature.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R045" source="R113_E031" target="R113_E036"><data key="edge_relationship_id">R113_R045</data><data key="edge_source_entity_id">R113_E031</data><data key="edge_relationship_type">subject_to_signature_policy</data><data key="edge_target_entity_id">R113_E036</data><data key="edge_operational_context">SSA-3288 fillable form must be printed and wet signed; copies with recognizable wet signature allowed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R046" source="FORM_SSA3288OP1" target="R113_E036"><data key="edge_relationship_id">R113_R046</data><data key="edge_source_entity_id">FORM_SSA3288OP1</data><data key="edge_relationship_type">provides_approved_electronic_exception_to</data><data key="edge_target_entity_id">R113_E036</data><data key="edge_operational_context">Electronic SSA-3288-OP1 submitted on SSA website; other electronic signatures require OGC approval.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R047" source="R113_E034" target="R113_E038"><data key="edge_relationship_id">R113_R047</data><data key="edge_source_entity_id">R113_E034</data><data key="edge_relationship_type">requires_express_record_scope_under</data><data key="edge_target_entity_id">R113_E038</data><data key="edge_operational_context">Medical records can be disclosed with proper separate non-tax consent and 90-day receipt rule.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R048" source="R113_E033" target="R113_E030"><data key="edge_relationship_id">R113_R048</data><data key="edge_source_entity_id">R113_E033</data><data key="edge_relationship_type">governs_disclosure_of</data><data key="edge_target_entity_id">R113_E030</data><data key="edge_operational_context">IRS consent rule uses 120-day receipt window for SSA-7050-F4.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R049" source="R113_E038" target="R113_E037"><data key="edge_relationship_id">R113_R049</data><data key="edge_source_entity_id">R113_E038</data><data key="edge_relationship_type">requires_third_party_recipient_address</data><data key="edge_target_entity_id">R113_E037</data><data key="edge_operational_context">Consent names/address of disclosure recipient; consenting individual address not mandatory.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R050" source="R113_E032" target="R113_E034"><data key="edge_relationship_id">R113_R050</data><data key="edge_source_entity_id">R113_E032</data><data key="edge_relationship_type">separates_medical_from_earnings_consent</data><data key="edge_target_entity_id">R113_E034</data><data key="edge_operational_context">SSA rejects combined medical and tax-return data authorization; nonmedical release can have independent signature validity.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R051" source="R113_E036" target="FORM_SSA3288OP1"><data key="edge_relationship_id">R113_R051</data><data key="edge_source_entity_id">R113_E036</data><data key="edge_relationship_type">uses_cleared_electronic_consent</data><data key="edge_target_entity_id">FORM_SSA3288OP1</data><data key="edge_operational_context">Approved electronic-signature channel is SSA-3288-OP1; do not infer support for other forms.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R052" source="R113_E035" target="R113_E038"><data key="edge_relationship_id">R113_R052</data><data key="edge_source_entity_id">R113_E035</data><data key="edge_relationship_type">sets_nonmedical_general_record_limit_for</data><data key="edge_target_entity_id">R113_E038</data><data key="edge_operational_context">General nonmedical/nontax consent documents received within one year; no automatic retention duration inferred.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R053" source="R113_E040" target="R113_E042"><data key="edge_relationship_id">R113_R053</data><data key="edge_source_entity_id">R113_E040</data><data key="edge_relationship_type">publishes_table_1_json</data><data key="edge_target_entity_id">R113_E042</data><data key="edge_operational_context">SSA website exposes JSON file for table 1; dataset can be regenerated following monthly corrections.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R054" source="R113_E042" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R113_R054</data><data key="edge_source_entity_id">R113_E042</data><data key="edge_relationship_type">is_companion_artifact_of</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">Table 1 JSON output is part of existing Monthly Statistical Snapshot flattened time-series product.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R055" source="R113_E042" target="R113_E041"><data key="edge_relationship_id">R113_R055</data><data key="edge_source_entity_id">R113_E042</data><data key="edge_relationship_type">includes_documented_schema</data><data key="edge_target_entity_id">R113_E041</data><data key="edge_operational_context">Table 1 JSON contains source, notes, variables, units, relationships metadata; schema beta.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R056" source="R113_E040" target="R113_E043"><data key="edge_relationship_id">R113_R056</data><data key="edge_source_entity_id">R113_E040</data><data key="edge_relationship_type">publishes_table_1_csv</data><data key="edge_target_entity_id">R113_E043</data><data key="edge_operational_context">SSA website exposes CSV file for table 1; dataset can be regenerated following monthly corrections.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R057" source="R113_E043" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R113_R057</data><data key="edge_source_entity_id">R113_E043</data><data key="edge_relationship_type">is_companion_artifact_of</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">Table 1 CSV output is part of existing Monthly Statistical Snapshot flattened time-series product.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R058" source="R113_E043" target="R113_E041"><data key="edge_relationship_id">R113_R058</data><data key="edge_source_entity_id">R113_E043</data><data key="edge_relationship_type">requires_json_metadata_for_interpretation</data><data key="edge_target_entity_id">R113_E041</data><data key="edge_operational_context">Table 1 CSV consumers are directed to corresponding JSON/edition for metadata.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R059" source="R113_E040" target="R113_E044"><data key="edge_relationship_id">R113_R059</data><data key="edge_source_entity_id">R113_E040</data><data key="edge_relationship_type">publishes_table_2_json</data><data key="edge_target_entity_id">R113_E044</data><data key="edge_operational_context">SSA website exposes JSON file for table 2; dataset can be regenerated following monthly corrections.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R060" source="R113_E044" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R113_R060</data><data key="edge_source_entity_id">R113_E044</data><data key="edge_relationship_type">is_companion_artifact_of</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">Table 2 JSON output is part of existing Monthly Statistical Snapshot flattened time-series product.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R061" source="R113_E044" target="R113_E041"><data key="edge_relationship_id">R113_R061</data><data key="edge_source_entity_id">R113_E044</data><data key="edge_relationship_type">includes_documented_schema</data><data key="edge_target_entity_id">R113_E041</data><data key="edge_operational_context">Table 2 JSON contains source, notes, variables, units, relationships metadata; schema beta.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R062" source="R113_E040" target="R113_E045"><data key="edge_relationship_id">R113_R062</data><data key="edge_source_entity_id">R113_E040</data><data key="edge_relationship_type">publishes_table_2_csv</data><data key="edge_target_entity_id">R113_E045</data><data key="edge_operational_context">SSA website exposes CSV file for table 2; dataset can be regenerated following monthly corrections.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R063" source="R113_E045" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R113_R063</data><data key="edge_source_entity_id">R113_E045</data><data key="edge_relationship_type">is_companion_artifact_of</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">Table 2 CSV output is part of existing Monthly Statistical Snapshot flattened time-series product.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R064" source="R113_E045" target="R113_E041"><data key="edge_relationship_id">R113_R064</data><data key="edge_source_entity_id">R113_E045</data><data key="edge_relationship_type">requires_json_metadata_for_interpretation</data><data key="edge_target_entity_id">R113_E041</data><data key="edge_operational_context">Table 2 CSV consumers are directed to corresponding JSON/edition for metadata.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R065" source="R113_E040" target="R113_E046"><data key="edge_relationship_id">R113_R065</data><data key="edge_source_entity_id">R113_E040</data><data key="edge_relationship_type">publishes_table_3_json</data><data key="edge_target_entity_id">R113_E046</data><data key="edge_operational_context">SSA website exposes JSON file for table 3; dataset can be regenerated following monthly corrections.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R066" source="R113_E046" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R113_R066</data><data key="edge_source_entity_id">R113_E046</data><data key="edge_relationship_type">is_companion_artifact_of</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">Table 3 JSON output is part of existing Monthly Statistical Snapshot flattened time-series product.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R067" source="R113_E046" target="R113_E041"><data key="edge_relationship_id">R113_R067</data><data key="edge_source_entity_id">R113_E046</data><data key="edge_relationship_type">includes_documented_schema</data><data key="edge_target_entity_id">R113_E041</data><data key="edge_operational_context">Table 3 JSON contains source, notes, variables, units, relationships metadata; schema beta.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R068" source="R113_E040" target="R113_E047"><data key="edge_relationship_id">R113_R068</data><data key="edge_source_entity_id">R113_E040</data><data key="edge_relationship_type">publishes_table_3_csv</data><data key="edge_target_entity_id">R113_E047</data><data key="edge_operational_context">SSA website exposes CSV file for table 3; dataset can be regenerated following monthly corrections.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R069" source="R113_E047" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R113_R069</data><data key="edge_source_entity_id">R113_E047</data><data key="edge_relationship_type">is_companion_artifact_of</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">Table 3 CSV output is part of existing Monthly Statistical Snapshot flattened time-series product.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R070" source="R113_E047" target="R113_E041"><data key="edge_relationship_id">R113_R070</data><data key="edge_source_entity_id">R113_E047</data><data key="edge_relationship_type">requires_json_metadata_for_interpretation</data><data key="edge_target_entity_id">R113_E041</data><data key="edge_operational_context">Table 3 CSV consumers are directed to corresponding JSON/edition for metadata.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R071" source="DATA_MONTHLY_STAT_SNAPSHOT" target="R113_E039"><data key="edge_relationship_id">R113_R071</data><data key="edge_source_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_relationship_type">has_archived_html_editions</data><data key="edge_target_entity_id">R113_E039</data><data key="edge_operational_context">HTML Monthly Statistical Snapshot archive is source of flattened time series files.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R072" source="R113_E039" target="R113_E040"><data key="edge_relationship_id">R113_R072</data><data key="edge_source_entity_id">R113_E039</data><data key="edge_relationship_type">is_input_to</data><data key="edge_target_entity_id">R113_E040</data><data key="edge_operational_context">SSA explicitly states monthly regeneration from full HTML archive, including corrections.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R073" source="R113_E040" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R113_R073</data><data key="edge_source_entity_id">R113_E040</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">Companion flattened data product generated monthly from archived HTML.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R074" source="R113_E041" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R113_R074</data><data key="edge_source_entity_id">R113_E041</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">Beta schema keys may change; do not imply stable identifiers for downstream integration.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R075" source="SYS_MBR" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R113_R075</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">is_administrative_data_input_for</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">August 2026 snapshot table 1 explicitly cites 100-percent MBR data, not a physical ETL pipeline.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R076" source="SYS_SSR" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R113_R076</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">is_administrative_data_input_for</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">August 2026 snapshot table 1 explicitly cites 100-percent SSR data; transport not established.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R077" source="PROC_NUMIDENT_ASSOC_RECON" target="SYS_MBR"><data key="edge_relationship_id">R113_R077</data><data key="edge_source_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="edge_relationship_type">requires_staff_action_after_parent_attribute_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">June 2026 policy directs conditional staff review/action for parent-name change; no automatic Numident-to-MBR write.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R078" source="PROC_NUMIDENT_ASSOC_RECON" target="SYS_SSR"><data key="edge_relationship_id">R113_R078</data><data key="edge_source_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="edge_relationship_type">requires_staff_action_after_parent_attribute_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">June 2026 policy directs conditional staff review/action for SSI parent-name cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R079" source="PROC_NUMIDENT_ASSOC_RECON" target="APP_ERPS"><data key="edge_relationship_id">R113_R079</data><data key="edge_source_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="edge_relationship_type">requires_staff_action_after_parent_attribute_update</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">June 2026 policy directs review of representative-payee record when parent data changed; eRPS is not necessarily automatically updated.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R080" source="REPO_SSA_VENDOR" target="R113_E048"><data key="edge_relationship_id">R113_R080</data><data key="edge_source_entity_id">REPO_SSA_VENDOR</data><data key="edge_relationship_type">described_as_market_research_source_for</data><data key="edge_target_entity_id">R113_E048</data><data key="edge_operational_context">Undated SSA OAG acquisition page describes vendor database as used for COTR market research; contemporary deployment not confirmed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R081" source="R113_E049" target="R113_E031"><data key="edge_relationship_id">R113_R081</data><data key="edge_source_entity_id">R113_E049</data><data key="edge_relationship_type">requires_wet_signature_processing</data><data key="edge_target_entity_id">R113_E031</data><data key="edge_operational_context">SSA-3288 paper or fillable form must be physically wet signed and submitted through accepted channels.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R082" source="R113_E049" target="R113_E038"><data key="edge_relationship_id">R113_R082</data><data key="edge_source_entity_id">R113_E049</data><data key="edge_relationship_type">carries_record_specific_consent_under</data><data key="edge_target_entity_id">R113_E038</data><data key="edge_operational_context">SSA-3288 must specify person, recipient, purpose, records and disclosure duration; broad all records requests invalid.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R113_R083" source="R113_E049" target="R113_E037"><data key="edge_relationship_id">R113_R083</data><data key="edge_source_entity_id">R113_E049</data><data key="edge_relationship_type">includes_optional_subject_address_distinct_from</data><data key="edge_target_entity_id">R113_E037</data><data key="edge_operational_context">Address of consenting subject optional; third-party release recipient address required; no master beneficiary update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only documented business or data-product relationship; avoid inferring data persistence, automation or master-record update.</data></edge><edge id="R114_REL001" source="R114_E001" target="R114_E002"><data key="edge_relationship_id">R114_REL001</data><data key="edge_source_entity_id">R114_E001</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">R114_E002</data><data key="edge_operational_context">Current CMA 1310 identifies the Return Transaction File as part of CADE IMF.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL002" source="R114_E002" target="DB_IRS_IMF"><data key="edge_relationship_id">R114_REL002</data><data key="edge_source_entity_id">R114_E002</data><data key="edge_relationship_type">corresponds_to_IRS_system_of_records</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">CADE IMF is Treasury/IRS system of records 24.030 in the current CMA.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL003" source="EX_CMA1310_IRS_PREMIUM" target="R114_E001"><data key="edge_relationship_id">R114_REL003</data><data key="edge_source_entity_id">EX_CMA1310_IRS_PREMIUM</data><data key="edge_relationship_type">retrieves_MAGI_from</data><data key="edge_target_entity_id">R114_E001</data><data key="edge_operational_context">IRS extracts IRMAA MAGI from RTF weekly; output filtered by applicable income threshold.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL004" source="SYS_MBR" target="R114_E004"><data key="edge_relationship_id">R114_REL004</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_identifiers_for</data><data key="edge_target_entity_id">R114_E004</data><data key="edge_operational_context">MBR 60-0090 is the SSA system of records supplying Medicare enrollee identity to IRS for IRMAA.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL005" source="R114_E004" target="ORG_IRS"><data key="edge_relationship_id">R114_REL005</data><data key="edge_source_entity_id">R114_E004</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SSA transmits electronic IRMAA identifiers each Thursday; IRS responds by the following Wednesday.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL006" source="R114_E005" target="ORG_IRS"><data key="edge_relationship_id">R114_REL006</data><data key="edge_source_entity_id">R114_E005</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SSA transmits an annual enrollee request in October in addition to 51 weekly requests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL007" source="R114_E001" target="R114_E003"><data key="edge_relationship_id">R114_REL007</data><data key="edge_source_entity_id">R114_E001</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">R114_E003</data><data key="edge_operational_context">IRS extracts MAGI and tax-year/filing-status elements from the RTF for qualifying enrollees.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL008" source="R114_E003" target="DB_MDB"><data key="edge_relationship_id">R114_REL008</data><data key="edge_source_entity_id">R114_E003</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">DB_MDB</data><data key="edge_operational_context">Current CMA 1310 explicitly states SSA maintains IRS-provided MAGI information in Medicare Database File, SORN 60-0321.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL009" source="R114_E003" target="APP_IRMAA"><data key="edge_relationship_id">R114_REL009</data><data key="edge_source_entity_id">R114_E003</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">APP_IRMAA</data><data key="edge_operational_context">IRMAA determination uses IRS MAGI received under CMA 1310, subject to verification/contest rights.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL010" source="EX_CMA1310_IRS_PREMIUM" target="R114_E006"><data key="edge_relationship_id">R114_REL010</data><data key="edge_source_entity_id">EX_CMA1310_IRS_PREMIUM</data><data key="edge_relationship_type">applies_tax_year_rule</data><data key="edge_target_entity_id">R114_E006</data><data key="edge_operational_context">Current CMA uses PY-2, with PY-3 under defined availability conditions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL011" source="EX_CMA1310_IRS_PREMIUM" target="R114_E007"><data key="edge_relationship_id">R114_REL011</data><data key="edge_source_entity_id">EX_CMA1310_IRS_PREMIUM</data><data key="edge_relationship_type">limited_by_request_retention</data><data key="edge_target_entity_id">R114_E007</data><data key="edge_operational_context">IRS side request files retained about 90 days; SSA has separate NARA disposition for match file.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL012" source="DB_MDB" target="R114_E003"><data key="edge_relationship_id">R114_REL012</data><data key="edge_source_entity_id">DB_MDB</data><data key="edge_relationship_type">stores_IRS_provided</data><data key="edge_target_entity_id">R114_E003</data><data key="edge_operational_context">Current signed CMA names MDB as the repository where IRS-derived MAGI is maintained.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL013" source="DB_MDB" target="R114_E008"><data key="edge_relationship_id">R114_REL013</data><data key="edge_source_entity_id">DB_MDB</data><data key="edge_relationship_type">provides_identifiers_for</data><data key="edge_target_entity_id">R114_E008</data><data key="edge_operational_context">SSA obtains LIS applicant/recipient identifiers from Medicare Database File, SORN 60-0321.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL014" source="DB_MDB" target="R114_E009"><data key="edge_relationship_id">R114_REL014</data><data key="edge_source_entity_id">DB_MDB</data><data key="edge_relationship_type">provides_identifiers_for</data><data key="edge_target_entity_id">R114_E009</data><data key="edge_operational_context">SSA obtains currently eligible LIS recipient identifiers from MDB for annual IRS request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL015" source="R114_E008" target="ORG_IRS"><data key="edge_relationship_id">R114_REL015</data><data key="edge_source_entity_id">R114_E008</data><data key="edge_relationship_type">sent_weekly_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SSA transmits LIS new-applicant requests weekly; IRS returns IRMF extract based on current electronically available tax year.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL016" source="R114_E009" target="ORG_IRS"><data key="edge_relationship_id">R114_REL016</data><data key="edge_source_entity_id">R114_E009</data><data key="edge_relationship_type">sent_annually_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SSA requests one annual verification of current LIS recipients; IRS advance notification at least 30 days.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL017" source="DB_IRS_IRMF" target="R114_E010"><data key="edge_relationship_id">R114_REL017</data><data key="edge_source_entity_id">DB_IRS_IRMF</data><data key="edge_relationship_type">supplies</data><data key="edge_target_entity_id">R114_E010</data><data key="edge_operational_context">IRS extracts unearned-income data from IRMF using its DIFSLA extraction process.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL018" source="EX_CMA1305_IRS_PARTD" target="R114_E008"><data key="edge_relationship_id">R114_REL018</data><data key="edge_source_entity_id">EX_CMA1305_IRS_PARTD</data><data key="edge_relationship_type">uses_weekly_input</data><data key="edge_target_entity_id">R114_E008</data><data key="edge_operational_context">CMA 1305 supports ongoing weekly LIS applicant self-certification checks.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL019" source="EX_CMA1305_IRS_PARTD" target="R114_E009"><data key="edge_relationship_id">R114_REL019</data><data key="edge_source_entity_id">EX_CMA1305_IRS_PARTD</data><data key="edge_relationship_type">uses_annual_input</data><data key="edge_target_entity_id">R114_E009</data><data key="edge_operational_context">CMA 1305 supports annual recipient eligibility verification.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL020" source="R114_E010" target="R114_E011"><data key="edge_relationship_id">R114_REL020</data><data key="edge_source_entity_id">R114_E010</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R114_E011</data><data key="edge_operational_context">Specified LIS response data include payee mailing address, not a documented master-benefit-address overwrite.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL021" source="R114_E010" target="R114_E012"><data key="edge_relationship_id">R114_REL021</data><data key="edge_source_entity_id">R114_E010</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R114_E012</data><data key="edge_operational_context">Specified LIS response data include payer address; it identifies an income source not a beneficiary residence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL022" source="R114_E010" target="DB_MDB"><data key="edge_relationship_id">R114_REL022</data><data key="edge_source_entity_id">R114_E010</data><data key="edge_relationship_type">maintains_unearned_income_information_in</data><data key="edge_target_entity_id">DB_MDB</data><data key="edge_operational_context">Current CMA 1305 states unearned-income information received from IRS is maintained in the SSA Medicare Database File. Does not establish address field persistence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL023" source="R114_E010" target="R114_E013"><data key="edge_relationship_id">R114_REL023</data><data key="edge_source_entity_id">R114_E010</data><data key="edge_relationship_type">requires_independent_verification_before_adverse_LIS_action</data><data key="edge_target_entity_id">R114_E013</data><data key="edge_operational_context">SSA must verify information and provide contest rights before adverse LIS determination or subsidy adjustment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL024" source="EX_CMA1305_IRS_PARTD" target="EX_CMA1016_IRS_DISFLA"><data key="edge_relationship_id">R114_REL024</data><data key="edge_source_entity_id">EX_CMA1305_IRS_PARTD</data><data key="edge_relationship_type">uses_same_extract_process_as</data><data key="edge_target_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_operational_context">LIS IRS extraction uses the same IRS DIFSLA process; different legal purpose and match number from SSI CMA1016.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL025" source="EX_CMA1305_IRS_PARTD" target="R114_E007"><data key="edge_relationship_id">R114_REL025</data><data key="edge_source_entity_id">EX_CMA1305_IRS_PARTD</data><data key="edge_relationship_type">limited_by_IRS_input_retention</data><data key="edge_target_entity_id">R114_E007</data><data key="edge_operational_context">IRS retains the SSA LIS input/tickler files about 90 days under GRS 5.2 item 010 before destruction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL026" source="EX_CMA1016_IRS_DISFLA" target="R114_E014"><data key="edge_relationship_id">R114_REL026</data><data key="edge_source_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_relationship_type">requires_annual_security_reporting</data><data key="edge_target_entity_id">R114_E014</data><data key="edge_operational_context">CMA 1016 requires annual Safeguard Security Report certified by SSA leadership and delivered by January 31.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL027" source="EX_CMA1016_IRS_DISFLA" target="R114_E015"><data key="edge_relationship_id">R114_REL027</data><data key="edge_source_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_relationship_type">requires_match_file_disposition</data><data key="edge_target_entity_id">R114_E015</data><data key="edge_operational_context">SSA match file retention until purpose and NARA requirements met; IRS input file roughly 90 days.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL028" source="R114_E015" target="R114_E007"><data key="edge_relationship_id">R114_REL028</data><data key="edge_source_entity_id">R114_E015</data><data key="edge_relationship_type">uses_IRS_transitory_retention_control</data><data key="edge_target_entity_id">R114_E007</data><data key="edge_operational_context">CMA1016 90-day IRS finder file control is consistent with GRS 5.2 Item 010 transitory files.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL029" source="EX_CMA1016_IRS_DISFLA" target="R114_E016"><data key="edge_relationship_id">R114_REL029</data><data key="edge_source_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_relationship_type">reimbursed_via</data><data key="edge_target_entity_id">R114_E016</data><data key="edge_operational_context">CMA specifies at least monthly IRS invoicing and SSA reimbursement through Treasury federal interagency mechanism.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL030" source="R114_E016" target="SVC_GINVOICING"><data key="edge_relationship_id">R114_REL030</data><data key="edge_source_entity_id">R114_E016</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_GINVOICING</data><data key="edge_operational_context">CMA 1016 calls for Fiscal Service G-Invoicing for FY2026 and beyond.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL031" source="R114_E016" target="SVC_IPAC"><data key="edge_relationship_id">R114_REL031</data><data key="edge_source_entity_id">R114_E016</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">SVC_IPAC</data><data key="edge_operational_context">G-Invoicing generates an Intra-governmental Payment and Collection bill under CMA1016.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL032" source="R114_E016" target="R114_E017"><data key="edge_relationship_id">R114_REL032</data><data key="edge_source_entity_id">R114_E016</data><data key="edge_relationship_type">uses_documentation</data><data key="edge_target_entity_id">R114_E017</data><data key="edge_operational_context">FS7600A and FS7600B define reimbursable interagency costs for the matching program.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL033" source="DB_MDB" target="R114_E020"><data key="edge_relationship_id">R114_REL033</data><data key="edge_source_entity_id">DB_MDB</data><data key="edge_relationship_type">provides_identifiers_for</data><data key="edge_target_entity_id">R114_E020</data><data key="edge_operational_context">MDB SORN 60-0321 supplies Extra Help applicant/recipient identifier extract.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL034" source="R114_E020" target="ORG_BFS"><data key="edge_relationship_id">R114_REL034</data><data key="edge_source_entity_id">R114_E020</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">SSA sends weekly and annual savings securities finder files to Treasury Fiscal Service.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL035" source="ORG_BFS" target="R114_E023"><data key="edge_relationship_id">R114_REL035</data><data key="edge_source_entity_id">ORG_BFS</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">R114_E023</data><data key="edge_operational_context">Fiscal Service compares matched SSNs against SORN .014 securities ownership records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL036" source="R114_E023" target="R114_E018"><data key="edge_relationship_id">R114_REL036</data><data key="edge_source_entity_id">R114_E023</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R114_E018</data><data key="edge_operational_context">Definitive security matches include denomination, serial number, series, issue date and redemption value.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL037" source="R114_E023" target="R114_E019"><data key="edge_relationship_id">R114_REL037</data><data key="edge_source_entity_id">R114_E023</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R114_E019</data><data key="edge_operational_context">Book-entry response includes purchase amount, account/confirmation numbers, issue date and redemption value.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL038" source="R114_E020" target="R114_E021"><data key="edge_relationship_id">R114_REL038</data><data key="edge_source_entity_id">R114_E020</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R114_E021</data><data key="edge_operational_context">Fiscal Service response within five business days; annual recipient file substitutes for one weekly submission.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL039" source="R114_E021" target="R114_E022"><data key="edge_relationship_id">R114_REL039</data><data key="edge_source_entity_id">R114_E021</data><data key="edge_relationship_type">provides_alerts</data><data key="edge_target_entity_id">R114_E022</data><data key="edge_operational_context">Positive savings-security matches generate ownership alerts requiring independent verification.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL040" source="R114_E022" target="R114_E024"><data key="edge_relationship_id">R114_REL040</data><data key="edge_source_entity_id">R114_E022</data><data key="edge_relationship_type">must_be_verified_via</data><data key="edge_target_entity_id">R114_E024</data><data key="edge_operational_context">Disputed bond ownership requires signed authorization and controlled Treasury contact via Minneapolis SSA field office.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL041" source="EX_CMA1304_BFS_PARTD" target="R114_E020"><data key="edge_relationship_id">R114_REL041</data><data key="edge_source_entity_id">EX_CMA1304_BFS_PARTD</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R114_E020</data><data key="edge_operational_context">Savings match is for Medicare Part D Extra Help, not SSI AFI or beneficiary bank address update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL042" source="EX_CMA1304_BFS_PARTD" target="R114_E021"><data key="edge_relationship_id">R114_REL042</data><data key="edge_source_entity_id">EX_CMA1304_BFS_PARTD</data><data key="edge_relationship_type">receives</data><data key="edge_target_entity_id">R114_E021</data><data key="edge_operational_context">Treasury reports matched savings securities or no-match indicator; no address fields in specified response.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL043" source="SVC_SAM_GOV" target="DB_VENDOR_PAYMENT_UNNAMED"><data key="edge_relationship_id">R114_REL043</data><data key="edge_source_entity_id">SVC_SAM_GOV</data><data key="edge_relationship_type">automatically_updates_vendor_financial_information_in</data><data key="edge_target_entity_id">DB_VENDOR_PAYMENT_UNNAMED</data><data key="edge_operational_context">SSA says vendor SAM direct-deposit financial changes automatically update its vendor database; internal database product and field mapping unnamed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL044" source="R114_E025" target="SVC_SAM_GOV"><data key="edge_relationship_id">R114_REL044</data><data key="edge_source_entity_id">R114_E025</data><data key="edge_relationship_type">uses_external_registration</data><data key="edge_target_entity_id">SVC_SAM_GOV</data><data key="edge_operational_context">SAM-enrolled vendor routing/account changes updated in SSA database through SAM.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL045" source="R114_E025" target="FORM_SF3881"><data key="edge_relationship_id">R114_REL045</data><data key="edge_source_entity_id">R114_E025</data><data key="edge_relationship_type">uses_manual_form</data><data key="edge_target_entity_id">FORM_SF3881</data><data key="edge_operational_context">Non-SAM vendors submit signed ACH SF3881 to DAPS; site marks downloadable document archival/historical.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL046" source="ORG_DAPS" target="R114_E025"><data key="edge_relationship_id">R114_REL046</data><data key="edge_source_entity_id">ORG_DAPS</data><data key="edge_relationship_type">processes</data><data key="edge_target_entity_id">R114_E025</data><data key="edge_operational_context">SSA DAPS administers vendor payment enrollment and maintenance; not benefit recipient direct deposit.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL047" source="APP_FIVR" target="R114_E026"><data key="edge_relationship_id">R114_REL047</data><data key="edge_source_entity_id">APP_FIVR</data><data key="edge_relationship_type">provides_query_access_to</data><data key="edge_target_entity_id">R114_E026</data><data key="edge_operational_context">SSA vendor page identifies FIVR as 24/7 automated voice access to administrative vendor payment activity, not proof of a specific DB backend.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL048" source="SVC_TREASURY_IPP" target="R114_E026"><data key="edge_relationship_id">R114_REL048</data><data key="edge_source_entity_id">SVC_TREASURY_IPP</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">R114_E026</data><data key="edge_operational_context">Treasury IPP displays enrolled vendor payment and invoice data from enrollment forward, restricted per vendor.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL049" source="SVC_TREASURY_IPP" target="R114_E027"><data key="edge_relationship_id">R114_REL049</data><data key="edge_source_entity_id">SVC_TREASURY_IPP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R114_E027</data><data key="edge_operational_context">Vendors can receive email notifications or detailed remittance information from Treasury IPP.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL050" source="ORG_DAPS" target="SVC_TREASURY_IPP"><data key="edge_relationship_id">R114_REL050</data><data key="edge_source_entity_id">ORG_DAPS</data><data key="edge_relationship_type">supports_vendor_payments_access_using</data><data key="edge_target_entity_id">SVC_TREASURY_IPP</data><data key="edge_operational_context">SSA vendor center directs administrative vendors to Treasury IPP payment status service.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL051" source="DATA_OACT_SOLVENCY_PROVISIONS" target="R114_E028"><data key="edge_relationship_id">R114_REL051</data><data key="edge_source_entity_id">DATA_OACT_SOLVENCY_PROVISIONS</data><data key="edge_relationship_type">publishes_category_dataset</data><data key="edge_target_entity_id">R114_E028</data><data key="edge_operational_context">Tax-benefit options provide detailed single-year OASDI financial estimate tables; proposed options not deployed benefit/tax policies.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL052" source="DATA_OACT_SOLVENCY_PROVISIONS" target="R114_E029"><data key="edge_relationship_id">R114_REL052</data><data key="edge_source_entity_id">DATA_OACT_SOLVENCY_PROVISIONS</data><data key="edge_relationship_type">publishes_graphs_and_summaries</data><data key="edge_target_entity_id">R114_E029</data><data key="edge_operational_context">Tax-benefit options have summary measures and graphs using 2026 intermediate Trustees assumptions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL053" source="R114_E029" target="R114_E028"><data key="edge_relationship_id">R114_REL053</data><data key="edge_source_entity_id">R114_E029</data><data key="edge_relationship_type">corresponds_to</data><data key="edge_target_entity_id">R114_E028</data><data key="edge_operational_context">Public OACT provides summary graphs and detailed annual tables for the same option set.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL054" source="R114_E031" target="APP_CPMS"><data key="edge_relationship_id">R114_REL054</data><data key="edge_source_entity_id">R114_E031</data><data key="edge_relationship_type">uses_pending_cases_from</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">SSA open-data source identifies CPMS case records pending ALJ determination as input microdata.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL055" source="R114_E031" target="SYS_NUMIDENT"><data key="edge_relationship_id">R114_REL055</data><data key="edge_source_entity_id">R114_E031</data><data key="edge_relationship_type">matches_death_data_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Office of Chief Actuary identifies deaths using Numident data queried for analytical research.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL056" source="R114_E031" target="R114_E030"><data key="edge_relationship_id">R114_REL056</data><data key="edge_source_entity_id">R114_E031</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R114_E030</data><data key="edge_operational_context">Historical 2006–2017 CSV updated June 2018; death data use for publication is not production cross-record mutation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL057" source="R114_E030" target="APP_CPMS"><data key="edge_relationship_id">R114_REL057</data><data key="edge_source_entity_id">R114_E030</data><data key="edge_relationship_type">identifies_claimants_from</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Public statistic covers pending ALJ appeal population as documented in CPMS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL058" source="R114_E033" target="APP_MCS"><data key="edge_relationship_id">R114_REL058</data><data key="edge_source_entity_id">R114_E033</data><data key="edge_relationship_type">reads_claim_information_from</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS holds field-office and internet initial RSI/Medicare claims and corresponding receipt/clearance counts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL059" source="R114_E033" target="DB_TITLE2_ODS"><data key="edge_relationship_id">R114_REL059</data><data key="edge_source_entity_id">R114_E033</data><data key="edge_relationship_type">downloads_nightly_to</data><data key="edge_target_entity_id">DB_TITLE2_ODS</data><data key="edge_operational_context">SSA downloads MCS information nightly into the Title II Operational Data Store, its initial claims management-information source.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL060" source="R114_E033" target="DATA_DOWR"><data key="edge_relationship_id">R114_REL060</data><data key="edge_source_entity_id">R114_E033</data><data key="edge_relationship_type">uses_reporting_periods_from</data><data key="edge_target_entity_id">DATA_DOWR</data><data key="edge_operational_context">District Office Workload Report receipt dates and administrative month conventions define published monthly reporting periods.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL061" source="R114_E033" target="R114_E032"><data key="edge_relationship_id">R114_REL061</data><data key="edge_source_entity_id">R114_E033</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R114_E032</data><data key="edge_operational_context">Batch aggregations of Title II ODS-derived MCS claims and DOWR dates produce national monthly CSV.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL062" source="DB_TITLE2_ODS" target="R114_E032"><data key="edge_relationship_id">R114_REL062</data><data key="edge_source_entity_id">DB_TITLE2_ODS</data><data key="edge_relationship_type">supports_publication_of</data><data key="edge_target_entity_id">R114_E032</data><data key="edge_operational_context">SSA explicitly identifies Title II ODS as source of initial claims management information used to prepare the published counts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL063" source="R114_E034" target="DATA_CLIENT_LANGUAGE_PREF"><data key="edge_relationship_id">R114_REL063</data><data key="edge_source_entity_id">R114_E034</data><data key="edge_relationship_type">published_as_part_of</data><data key="edge_target_entity_id">DATA_CLIENT_LANGUAGE_PREF</data><data key="edge_operational_context">Published quarterly RSI claims spoken-language preference series; source does not identify physical language-preference database.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL064" source="DATA_EBE_USCIS_MAILING_ADDRESS" target="R114_E035"><data key="edge_relationship_id">R114_REL064</data><data key="edge_source_entity_id">DATA_EBE_USCIS_MAILING_ADDRESS</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R114_E035</data><data key="edge_operational_context">EBE postal address supplied on USCIS application is confirmed against current card processing status, not asserted as current residence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL065" source="R114_E035" target="SYS_NUMIDENT"><data key="edge_relationship_id">R114_REL065</data><data key="edge_source_entity_id">R114_E035</data><data key="edge_relationship_type">uses_evidence_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Numident EBE application cycle date determines whether existing card is still in delivery window.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL066" source="R114_E035" target="APP_SSNAP"><data key="edge_relationship_id">R114_REL066</data><data key="edge_source_entity_id">R114_E035</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Changed/stale EBE card mailing address can require SSNAP replacement application; no program-benefit-record address update established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL067" source="APP_IRPA" target="R114_E036"><data key="edge_relationship_id">R114_REL067</data><data key="edge_source_entity_id">APP_IRPA</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R114_E036</data><data key="edge_operational_context">Users must have current paper payee report and report identification codes to use iRPA.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL068" source="APP_IRPA" target="R114_E037"><data key="edge_relationship_id">R114_REL068</data><data key="edge_source_entity_id">APP_IRPA</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R114_E037</data><data key="edge_operational_context">User receives confirmation number; SSA public portal describes 30-day viewing window, not permanent retention.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL069" source="APP_IRPA" target="PLAT_BSO"><data key="edge_relationship_id">R114_REL069</data><data key="edge_source_entity_id">APP_IRPA</data><data key="edge_relationship_type">uses_login_service</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">Organizational payees registering for iRPA are directed through Business Services Online.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL070" source="PLAT_BSO" target="APP_IRPA"><data key="edge_relationship_id">R114_REL070</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">supports_organizational_payee_accounting</data><data key="edge_target_entity_id">APP_IRPA</data><data key="edge_operational_context">SSA BSO currently offers organizational payee accounting using Login.gov/ID.me; individual access through my Social Security.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL071" source="UI_IRMAA_PYTY" target="R114_E038"><data key="edge_relationship_id">R114_REL071</data><data key="edge_source_entity_id">UI_IRMAA_PYTY</data><data key="edge_relationship_type">implements</data><data key="edge_target_entity_id">R114_E038</data><data key="edge_operational_context">PYTY screen selects highest probative tax data or new tax data for beneficiary-initiated new initial IRMAA determination.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL072" source="R114_E038" target="APP_IRMAA"><data key="edge_relationship_id">R114_REL072</data><data key="edge_source_entity_id">R114_E038</data><data key="edge_relationship_type">uses_existing_tax_data_from</data><data key="edge_target_entity_id">APP_IRMAA</data><data key="edge_operational_context">Data on file is considered in beneficiary new initial determinations; does not change underlying IRS data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R114_REL073" source="UI_IRMAA_IRMA" target="UI_IRMAA_PYTY"><data key="edge_relationship_id">R114_REL073</data><data key="edge_source_entity_id">UI_IRMAA_IRMA</data><data key="edge_relationship_type">populated_by</data><data key="edge_target_entity_id">UI_IRMAA_PYTY</data><data key="edge_operational_context">Highest probative data propagates into IRMA screen and locks those copied values against editing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R115_REL001" source="R115_E001" target="PROC_OACT_FERTILITY_PROJ"><data key="edge_relationship_id">R115_REL001</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">includes_previously_cataloged_projection_method</data><data key="edge_target_entity_id">PROC_OACT_FERTILITY_PROJ</data><data key="edge_operational_context">2026 Demography Process contains a fertility or mortality modeling operation; the existing OACT method entity is reused rather than duplicating it.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL002" source="R115_E001" target="PROC_OACT_MORTALITY_PROJ"><data key="edge_relationship_id">R115_REL002</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">includes_previously_cataloged_projection_method</data><data key="edge_target_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_operational_context">2026 Demography Process contains a fertility or mortality modeling operation; the existing OACT method entity is reused rather than duplicating it.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL003" source="R115_E001" target="R115_E002"><data key="edge_relationship_id">R115_REL003</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">contains_documented_model_subprocess</data><data key="edge_target_entity_id">R115_E002</data><data key="edge_operational_context">2026 model documentation names the HISTORICAL SOCIAL SECURITY AREA POPULATION subprocess as a component of Demography.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL004" source="R115_E001" target="R115_E003"><data key="edge_relationship_id">R115_REL004</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">contains_documented_model_subprocess</data><data key="edge_target_entity_id">R115_E003</data><data key="edge_operational_context">2026 model documentation names the LAWFUL PERMANENT RESIDENT IMMIGRATION subprocess as a component of Demography.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL005" source="R115_E001" target="R115_E004"><data key="edge_relationship_id">R115_REL005</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">contains_documented_model_subprocess</data><data key="edge_target_entity_id">R115_E004</data><data key="edge_operational_context">2026 model documentation names the TEMPORARY OR UNLAWFULLY PRESENT IMMIGRATION subprocess as a component of Demography.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL006" source="R115_E001" target="R115_E005"><data key="edge_relationship_id">R115_REL006</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">contains_documented_model_subprocess</data><data key="edge_target_entity_id">R115_E005</data><data key="edge_operational_context">2026 model documentation names the MARRIAGE subprocess as a component of Demography.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL007" source="R115_E001" target="R115_E006"><data key="edge_relationship_id">R115_REL007</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">contains_documented_model_subprocess</data><data key="edge_target_entity_id">R115_E006</data><data key="edge_operational_context">2026 model documentation names the DIVORCE subprocess as a component of Demography.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL008" source="R115_E001" target="R115_E007"><data key="edge_relationship_id">R115_REL008</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">contains_documented_model_subprocess</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">2026 model documentation names the PROJECTED SOCIAL SECURITY AREA POPULATION subprocess as a component of Demography.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL009" source="PROC_OACT_IMMIGRATION_PROJ" target="R115_E003"><data key="edge_relationship_id">R115_REL009</data><data key="edge_source_entity_id">PROC_OACT_IMMIGRATION_PROJ</data><data key="edge_relationship_type">has_demography_component</data><data key="edge_target_entity_id">R115_E003</data><data key="edge_operational_context">Immigration projection incorporates the LPR migration stream; no transport or physical model platform inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL010" source="PROC_OACT_IMMIGRATION_PROJ" target="R115_E004"><data key="edge_relationship_id">R115_REL010</data><data key="edge_source_entity_id">PROC_OACT_IMMIGRATION_PROJ</data><data key="edge_relationship_type">has_demography_component</data><data key="edge_target_entity_id">R115_E004</data><data key="edge_operational_context">Immigration projection incorporates the TEMP migration stream; no transport or physical model platform inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL011" source="R115_E002" target="R115_E007"><data key="edge_relationship_id">R115_REL011</data><data key="edge_source_entity_id">R115_E002</data><data key="edge_relationship_type">supplies_demographic_inputs_to</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">Demography uses the HIST category as a projection input; applies actuarial forecast assumptions rather than individual case records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL012" source="R115_E003" target="R115_E007"><data key="edge_relationship_id">R115_REL012</data><data key="edge_source_entity_id">R115_E003</data><data key="edge_relationship_type">supplies_demographic_inputs_to</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">Demography uses the LPR category as a projection input; applies actuarial forecast assumptions rather than individual case records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL013" source="R115_E004" target="R115_E007"><data key="edge_relationship_id">R115_REL013</data><data key="edge_source_entity_id">R115_E004</data><data key="edge_relationship_type">supplies_demographic_inputs_to</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">Demography uses the TEMP category as a projection input; applies actuarial forecast assumptions rather than individual case records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL014" source="R115_E005" target="R115_E007"><data key="edge_relationship_id">R115_REL014</data><data key="edge_source_entity_id">R115_E005</data><data key="edge_relationship_type">supplies_demographic_inputs_to</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">Demography uses the MARR category as a projection input; applies actuarial forecast assumptions rather than individual case records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL015" source="R115_E006" target="R115_E007"><data key="edge_relationship_id">R115_REL015</data><data key="edge_source_entity_id">R115_E006</data><data key="edge_relationship_type">supplies_demographic_inputs_to</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">Demography uses the DIV category as a projection input; applies actuarial forecast assumptions rather than individual case records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL016" source="PROC_OACT_FERTILITY_PROJ" target="R115_E007"><data key="edge_relationship_id">R115_REL016</data><data key="edge_source_entity_id">PROC_OACT_FERTILITY_PROJ</data><data key="edge_relationship_type">supplies_demographic_assumptions_to</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">Birth-rate assumptions are combined with other demographic assumptions to forecast Social Security area population.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL017" source="PROC_OACT_MORTALITY_PROJ" target="R115_E007"><data key="edge_relationship_id">R115_REL017</data><data key="edge_source_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_relationship_type">supplies_demographic_assumptions_to</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">Mortality assumptions form inputs to the total population projection.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL018" source="R115_E002" target="R115_E008"><data key="edge_relationship_id">R115_REL018</data><data key="edge_source_entity_id">R115_E002</data><data key="edge_relationship_type">establishes_historical_population_basis</data><data key="edge_target_entity_id">R115_E008</data><data key="edge_operational_context">2026 Trustees population methodology identifies December 31, 2023 starting area-population stock and published adjustments.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL019" source="R115_E008" target="R115_E007"><data key="edge_relationship_id">R115_REL019</data><data key="edge_source_entity_id">R115_E008</data><data key="edge_relationship_type">is_projection_base_for</data><data key="edge_target_entity_id">R115_E007</data><data key="edge_operational_context">OACT population projections begin with December 31, 2023 adjusted Social Security area population.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL020" source="R115_E007" target="R115_E009"><data key="edge_relationship_id">R115_REL020</data><data key="edge_source_entity_id">R115_E007</data><data key="edge_relationship_type">publishes_model_output</data><data key="edge_target_entity_id">R115_E009</data><data key="edge_operational_context">2026 projected population estimates are produced by age, sex, marital status to 2100; output is model-derived and not an SSA operational person record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL021" source="R115_E007" target="R115_E010"><data key="edge_relationship_id">R115_REL021</data><data key="edge_source_entity_id">R115_E007</data><data key="edge_relationship_type">produces_model_population_category</data><data key="edge_target_entity_id">R115_E010</data><data key="edge_operational_context">2026 model documentation lists projected civilian noninstitutionalized population by age, sex and marital status.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL022" source="R115_E009" target="DATA_OACT_TR_VA3_POP_DEP"><data key="edge_relationship_id">R115_REL022</data><data key="edge_source_entity_id">R115_E009</data><data key="edge_relationship_type">published_in_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VA3_POP_DEP</data><data key="edge_operational_context">2026 Trustees table V.A3 presents broad age-group historical and projected area-population totals and dependency ratios.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL023" source="R115_E001" target="R115_E011"><data key="edge_relationship_id">R115_REL023</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">provides_projected_population_inputs_to</data><data key="edge_target_entity_id">R115_E011</data><data key="edge_operational_context">2026 OACT model describes demographic outputs flowing to economics, beneficiaries or trust fund/actuarial process.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL024" source="R115_E001" target="R115_E012"><data key="edge_relationship_id">R115_REL024</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">provides_projected_population_inputs_to</data><data key="edge_target_entity_id">R115_E012</data><data key="edge_operational_context">2026 OACT model describes demographic outputs flowing to economics, beneficiaries or trust fund/actuarial process.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL025" source="R115_E001" target="R115_E013"><data key="edge_relationship_id">R115_REL025</data><data key="edge_source_entity_id">R115_E001</data><data key="edge_relationship_type">provides_projected_population_inputs_to</data><data key="edge_target_entity_id">R115_E013</data><data key="edge_operational_context">2026 OACT model describes demographic outputs flowing to economics, beneficiaries or trust fund/actuarial process.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R115_REL026" source="DB_USPS_NCOA" target="R115_E014"><data key="edge_relationship_id">R115_REL026</data><data key="edge_source_entity_id">DB_USPS_NCOA</data><data key="edge_relationship_type">candidate_match_requires</data><data key="edge_target_entity_id">R115_E014</data><data key="edge_operational_context">2019 policy specifies exact matching of identity and prior USPS address; applies Title II only.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL027" source="PROC_NCOA_TITLEII" target="R115_E014"><data key="edge_relationship_id">R115_REL027</data><data key="edge_source_entity_id">PROC_NCOA_TITLEII</data><data key="edge_relationship_type">screens_for</data><data key="edge_target_entity_id">R115_E014</data><data key="edge_operational_context">NCOA Title II processing uses exact-match identity and original-address gate.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL028" source="R115_E014" target="R115_E015"><data key="edge_relationship_id">R115_REL028</data><data key="edge_source_entity_id">R115_E014</data><data key="edge_relationship_type">may_enable</data><data key="edge_target_entity_id">R115_E015</data><data key="edge_operational_context">Qualified NCOA matches for direct deposit or selected nonpayment categories can be automatically posted if no intervening COA.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL029" source="R115_E014" target="R115_E016"><data key="edge_relationship_id">R115_REL029</data><data key="edge_source_entity_id">R115_E014</data><data key="edge_relationship_type">may_require_manual_confirmation</data><data key="edge_target_entity_id">R115_E016</data><data key="edge_operational_context">Other NCOA match categories require a beneficiary/payee call and separate ordinary COA processing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL030" source="R115_E015" target="SYS_MBR"><data key="edge_relationship_id">R115_REL030</data><data key="edge_source_entity_id">R115_E015</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS explicitly states automatic Title II Redesign NCOA posting; not a general USPS-to-SSR or IRS-to-MBR update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL031" source="R115_E015" target="R115_E018"><data key="edge_relationship_id">R115_REL031</data><data key="edge_source_entity_id">R115_E015</data><data key="edge_relationship_type">marks_updated_address_with</data><data key="edge_target_entity_id">R115_E018</data><data key="edge_operational_context">The MBR NCOA L ZIP flag becomes P when the new address posts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL032" source="R115_E016" target="R115_E019"><data key="edge_relationship_id">R115_REL032</data><data key="edge_source_entity_id">R115_E016</data><data key="edge_relationship_type">creates_pending_notice_indicator</data><data key="edge_target_entity_id">R115_E019</data><data key="edge_operational_context">MBR retains L when confirmation not received and record may recur in future NCOA run.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL033" source="R115_E016" target="R115_E017"><data key="edge_relationship_id">R115_REL033</data><data key="edge_source_entity_id">R115_E016</data><data key="edge_relationship_type">may_set_opt_out</data><data key="edge_target_entity_id">R115_E017</data><data key="edge_operational_context">When beneficiary declines USPS address, old address is reinput and X excludes next NCOA selection.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL034" source="DATA_TITLEII_ZIP_FLAG" target="R115_E019"><data key="edge_relationship_id">R115_REL034</data><data key="edge_source_entity_id">DATA_TITLEII_ZIP_FLAG</data><data key="edge_relationship_type">has_documented_ncoa_value</data><data key="edge_target_entity_id">R115_E019</data><data key="edge_operational_context">Specific NCOA values are documented in 2019 POMS; generic ZIP flag already present in Atlas.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL035" source="DATA_TITLEII_ZIP_FLAG" target="R115_E018"><data key="edge_relationship_id">R115_REL035</data><data key="edge_source_entity_id">DATA_TITLEII_ZIP_FLAG</data><data key="edge_relationship_type">has_documented_ncoa_value</data><data key="edge_target_entity_id">R115_E018</data><data key="edge_operational_context">Specific NCOA values are documented in 2019 POMS; generic ZIP flag already present in Atlas.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL036" source="DATA_TITLEII_ZIP_FLAG" target="R115_E017"><data key="edge_relationship_id">R115_REL036</data><data key="edge_source_entity_id">DATA_TITLEII_ZIP_FLAG</data><data key="edge_relationship_type">has_documented_ncoa_value</data><data key="edge_target_entity_id">R115_E017</data><data key="edge_operational_context">Specific NCOA values are documented in 2019 POMS; generic ZIP flag already present in Atlas.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL037" source="R115_E014" target="SYS_SSR"><data key="edge_relationship_id">R115_REL037</data><data key="edge_source_entity_id">R115_E014</data><data key="edge_relationship_type">does_not_post_title_xvi_address</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS expressly limits NCOA processing to Title II, excluding automatic Title XVI/SSR updates.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL038" source="EX_CREDIT_BUREAU_REPORTING" target="R115_E022"><data key="edge_relationship_id">R115_REL038</data><data key="edge_source_entity_id">EX_CREDIT_BUREAU_REPORTING</data><data key="edge_relationship_type">transmits_identity_debt_address_artifact</data><data key="edge_target_entity_id">R115_E022</data><data key="edge_operational_context">Documented outgoing debt/identity/address information; separate from incoming credit bureau address lookups.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL039" source="R115_E022" target="ORG_CREDIT_REPOSITORIES"><data key="edge_relationship_id">R115_REL039</data><data key="edge_source_entity_id">R115_E022</data><data key="edge_relationship_type">is_submitted_to</data><data key="edge_target_entity_id">ORG_CREDIT_REPOSITORIES</data><data key="edge_operational_context">SSA reports delinquent debtor fields to national repositories, which distribute them to smaller credit bureaus.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL040" source="APP_ECO" target="R115_E023"><data key="edge_relationship_id">R115_REL040</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">applies_credit_report_60_day_hold</data><data key="edge_target_entity_id">R115_E023</data><data key="edge_operational_context">Due process notices precede SSA reporting to credit repositories; pending disputes and waivers affect selection.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL041" source="R115_E023" target="R115_E022"><data key="edge_relationship_id">R115_REL041</data><data key="edge_source_entity_id">R115_E023</data><data key="edge_relationship_type">conditions_release_to</data><data key="edge_target_entity_id">R115_E022</data><data key="edge_operational_context">Eligible debt/identity record is only reportable after the due process gate or later required review disposition.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL042" source="R115_E020" target="R115_E022"><data key="edge_relationship_id">R115_REL042</data><data key="edge_source_entity_id">R115_E020</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">R115_E022</data><data key="edge_operational_context">Title II monthly update can include changed address, repayments and collection status.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL043" source="R115_E021" target="R115_E022"><data key="edge_relationship_id">R115_REL043</data><data key="edge_source_entity_id">R115_E021</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">R115_E022</data><data key="edge_operational_context">Title XVI monthly update can include changed address, repayments and protests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL044" source="R115_E020" target="EX_CREDIT_BUREAU_REPORTING"><data key="edge_relationship_id">R115_REL044</data><data key="edge_source_entity_id">R115_E020</data><data key="edge_relationship_type">is_delivered_via</data><data key="edge_target_entity_id">EX_CREDIT_BUREAU_REPORTING</data><data key="edge_operational_context">Title II outgoing report updates flow through existing credit reporting exchange; mechanism not claimed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL045" source="R115_E021" target="EX_CREDIT_BUREAU_REPORTING"><data key="edge_relationship_id">R115_REL045</data><data key="edge_source_entity_id">R115_E021</data><data key="edge_relationship_type">is_delivered_via</data><data key="edge_target_entity_id">EX_CREDIT_BUREAU_REPORTING</data><data key="edge_operational_context">Title XVI outgoing report updates flow through existing credit reporting exchange; mechanism not claimed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL046" source="APP_ACDV" target="R115_E024"><data key="edge_relationship_id">R115_REL046</data><data key="edge_source_entity_id">APP_ACDV</data><data key="edge_relationship_type">has_federal_response_deadline</data><data key="edge_target_entity_id">R115_E024</data><data key="edge_operational_context">Credit bureau dispute through ACDV requires SSA response within 30 days or the bureau deletes the debt item.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL047" source="R115_E024" target="SYS_SSR"><data key="edge_relationship_id">R115_REL047</data><data key="edge_source_entity_id">R115_E024</data><data key="edge_relationship_type">requires_claim_verification_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI ACDV disputes generally resolve by verifying disputed debt fact or amount against the SSR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL048" source="APP_DMS" target="R115_E025"><data key="edge_relationship_id">R115_REL048</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">supports_authorized_credit_report_deletion</data><data key="edge_target_entity_id">R115_E025</data><data key="edge_operational_context">Current SSI instructions identify DMS role in contacting the person with authority to remove debt from credit file.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL049" source="ORG_NEPSC" target="R115_E025"><data key="edge_relationship_id">R115_REL049</data><data key="edge_source_entity_id">ORG_NEPSC</data><data key="edge_relationship_type">coordinates_reported_debt_removal</data><data key="edge_target_entity_id">R115_E025</data><data key="edge_operational_context">NEPSC Program Analyst or Regional Office escalation for approved protest or discharged bankruptcy.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL050" source="R115_E025" target="ORG_CREDIT_REPOSITORIES"><data key="edge_relationship_id">R115_REL050</data><data key="edge_source_entity_id">R115_E025</data><data key="edge_relationship_type">may_delete_from</data><data key="edge_target_entity_id">ORG_CREDIT_REPOSITORIES</data><data key="edge_operational_context">After verified grounds, SSA authorizes deletion at credit repository; actual external record is not an SSA payment master.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL051" source="R115_E021" target="SYS_SSR"><data key="edge_relationship_id">R115_REL051</data><data key="edge_source_entity_id">R115_E021</data><data key="edge_relationship_type">does_not_imply_inbound_credit_address_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA outbound changed-address updates to bureaus do not establish an inbound bureau-to-SSR address correction mechanism.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL052" source="DB_SCDD" target="R115_E027"><data key="edge_relationship_id">R115_REL052</data><data key="edge_source_entity_id">DB_SCDD</data><data key="edge_relationship_type">supplies_demographics_and_workload_to</data><data key="edge_target_entity_id">R115_E027</data><data key="edge_operational_context">SSA Open Data identifies SCDD, populated from SUMS workload and Integrated Client Database-sourced client tables, as source of LEP reports.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R115_REL053" source="DB_SUMS_CLIENT_TABLES" target="R115_E027"><data key="edge_relationship_id">R115_REL053</data><data key="edge_source_entity_id">DB_SUMS_CLIENT_TABLES</data><data key="edge_relationship_type">contributes_client_demographics_to</data><data key="edge_target_entity_id">R115_E027</data><data key="edge_operational_context">SUMS client-table demographics including spoken/written language, sex and age range are input to SCDD aggregation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R115_REL054" source="SYS_ICDB" target="R115_E027"><data key="edge_relationship_id">R115_REL054</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">is_upstream_demographic_record_source_for</data><data key="edge_target_entity_id">R115_E027</data><data key="edge_operational_context">Integrated Client Data Base sources SUMS client tables; relationship is for statistical compilation, not program-record address updates.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R115_REL055" source="R115_E027" target="R115_E026"><data key="edge_relationship_id">R115_REL055</data><data key="edge_source_entity_id">R115_E027</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R115_E026</data><data key="edge_operational_context">SSA publishes official quarterly spoken-language-preference CSV for ESRD Medicare applications, FY2023 onward.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R115_REL056" source="DB_IRS_IMF" target="DATA_IRS_STATEMENT_MAIL_ADDR"><data key="edge_relationship_id">R115_REL056</data><data key="edge_source_entity_id">DB_IRS_IMF</data><data key="edge_relationship_type">supplies_statement_only_address_to</data><data key="edge_target_entity_id">DATA_IRS_STATEMENT_MAIL_ADDR</data><data key="edge_operational_context">IRS IMF taxpayer mailing addresses are used under IRC 6103(m)(7) to mail automatic Social Security Statements; no authority to auto-update MBR/SSR inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL057" source="DATA_IRS_STATEMENT_MAIL_ADDR" target="APP_PEBES"><data key="edge_relationship_id">R115_REL057</data><data key="edge_source_entity_id">DATA_IRS_STATEMENT_MAIL_ADDR</data><data key="edge_relationship_type">used_for_statement_distribution_not_benefits_change</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">PEBES obtains IMF addresses for printing/mailing automatic Statements; documentation does not describe benefit-master address update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL058" source="APP_W2_ONLINE_2026" target="R115_E028"><data key="edge_relationship_id">R115_REL058</data><data key="edge_source_entity_id">APP_W2_ONLINE_2026</data><data key="edge_relationship_type">has_planned_territory_support</data><data key="edge_target_entity_id">R115_E028</data><data key="edge_operational_context">W-2 2026-01 newsletter names early December 2026 as expected territory support date.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R115_REL059" source="SVC_WAGE_FILE_UPLOAD" target="R115_E028"><data key="edge_relationship_id">R115_REL059</data><data key="edge_source_entity_id">SVC_WAGE_FILE_UPLOAD</data><data key="edge_relationship_type">remains_available_during</data><data key="edge_target_entity_id">R115_E028</data><data key="edge_operational_context">SSA described Wage File Upload as territory filing option pending new application support.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL001" source="EX_SSI_IRS_1099" target="R116_E001"><data key="edge_relationship_id">R116_REL001</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">supplies_transaction_payee_data</data><data key="edge_target_entity_id">R116_E001</data><data key="edge_operational_context">POMS describes interface tax data as containing payee address and taxpayer ID, which are not necessarily identical to claimant address.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL002" source="EX_SSI_IRS_1099" target="R116_E002"><data key="edge_relationship_id">R116_REL002</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">supplies_transaction_payer_data</data><data key="edge_target_entity_id">R116_E002</data><data key="edge_operational_context">Transaction record identifies the financial-institution, employer, or agency payer who submitted the report.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL003" source="DB_SSI_IRS_INTERFACE" target="R116_E005"><data key="edge_relationship_id">R116_REL003</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">historically_exposes</data><data key="edge_target_entity_id">R116_E005</data><data key="edge_operational_context">Two recent years of IRS data were available on SSI/IRS interface database per 2017 POMS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL004" source="DB_SSI_IRS_INTERFACE" target="R116_E003"><data key="edge_relationship_id">R116_REL004</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">subject_to_disposition_record_control</data><data key="edge_target_entity_id">R116_E003</data><data key="edge_operational_context">Case-development outcomes must be recorded until following-year alerts complete; do not confuse with IRS interface database retention.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL005" source="DB_SSI_IRS_INTERFACE" target="R116_E004"><data key="edge_relationship_id">R116_REL005</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">subject_to_alert_copy_destruction_control</data><data key="edge_target_entity_id">R116_E004</data><data key="edge_operational_context">Tax-data alert printouts are destroyed after independent verification unless serving as restricted disposition record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL006" source="R116_E001" target="DATA_SSR_AD"><data key="edge_relationship_id">R116_REL006</data><data key="edge_source_entity_id">R116_E001</data><data key="edge_relationship_type">must_not_be_assumed_to_update</data><data key="edge_target_entity_id">DATA_SSR_AD</data><data key="edge_operational_context">Financial transaction payee address is a tax alert, not an SSI address-change directive; no automatic posting verified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL007" source="APP_SSTNG" target="R116_E005"><data key="edge_relationship_id">R116_REL007</data><data key="edge_source_entity_id">APP_SSTNG</data><data key="edge_relationship_type">queries_interface_window</data><data key="edge_target_entity_id">R116_E005</data><data key="edge_operational_context">SSTNG was documented as immediate route for last two years of IRS match data; historical policy as of 2017.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL008" source="PORTAL_SUMS_MCAS_MI_CENTRAL" target="R116_E005"><data key="edge_relationship_id">R116_REL008</data><data key="edge_source_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_relationship_type">queries_interface_window</data><data key="edge_target_entity_id">R116_E005</data><data key="edge_operational_context">MI Central RZ/LI listings provide overnight retrieval of IRS match data by housed-under number.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL009" source="EX_EAB" target="R116_E007"><data key="edge_relationship_id">R116_REL009</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">uses_state_quality_gate</data><data key="edge_target_entity_id">R116_E007</data><data key="edge_operational_context">State BVS birth certificates and state registration are authoritative for incoming EAB registration data; SSA processes records as received.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL010" source="EX_EAB" target="R116_E008"><data key="edge_relationship_id">R116_REL010</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">has_identified_duplicate_risk</data><data key="edge_target_entity_id">R116_E008</data><data key="edge_operational_context">OIG found 420 newborns apparently issued multiple SSNs without corresponding cross-references in Numident.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL011" source="R116_E006" target="R116_E008"><data key="edge_relationship_id">R116_REL011</data><data key="edge_source_entity_id">R116_E006</data><data key="edge_relationship_type">reviews</data><data key="edge_target_entity_id">R116_E008</data><data key="edge_operational_context">OIG recommended reviewing possible duplicate infancy identities case by case, not assuming misuse or automatic corrections.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL012" source="R116_E006" target="DATA_NUMIDENT_MULTI_SSN_XREF_ATTR"><data key="edge_relationship_id">R116_REL012</data><data key="edge_source_entity_id">R116_E006</data><data key="edge_relationship_type">may_require_linking</data><data key="edge_target_entity_id">DATA_NUMIDENT_MULTI_SSN_XREF_ATTR</data><data key="edge_operational_context">Where sufficient evidence exists, additional SSNs may be cross-referenced to the original identity.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL013" source="R116_E006" target="DATA_SSN_RETIREMENT_DESIG"><data key="edge_relationship_id">R116_REL013</data><data key="edge_source_entity_id">R116_E006</data><data key="edge_relationship_type">may_designate_retired</data><data key="edge_target_entity_id">DATA_SSN_RETIREMENT_DESIG</data><data key="edge_operational_context">SSA agreed to review potential duplicates; potential remedy includes designation of additional SSNs as retired.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL014" source="PROC_NCP" target="APP_IRON"><data key="edge_relationship_id">R116_REL014</data><data key="edge_source_entity_id">PROC_NCP</data><data key="edge_relationship_type">requires_documented_original_evidence</data><data key="edge_target_entity_id">APP_IRON</data><data key="edge_operational_context">2026 Numident policy requires review of original SS-5 or microprint or qualifying automated-enumeration source documentation before keying-error correction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL015" source="PROC_NUMIDENT_CROSS_RECORD_UPDATE" target="SYS_MBR"><data key="edge_relationship_id">R116_REL015</data><data key="edge_source_entity_id">PROC_NUMIDENT_CROSS_RECORD_UPDATE</data><data key="edge_relationship_type">requires_program_record_separate_review</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Correcting Numident sex code or parent name can require separately updating beneficiary records, not universal automatic propagation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL016" source="PROC_NUMIDENT_CROSS_RECORD_UPDATE" target="SYS_SSR"><data key="edge_relationship_id">R116_REL016</data><data key="edge_source_entity_id">PROC_NUMIDENT_CROSS_RECORD_UPDATE</data><data key="edge_relationship_type">requires_program_record_separate_review</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Correcting Numident sex code or parent name can require separate SSI record review and action.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL017" source="R116_E009" target="REPO_CEF"><data key="edge_relationship_id">R116_REL017</data><data key="edge_source_entity_id">R116_E009</data><data key="edge_relationship_type">stores_scanned_documents_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">After scanning via onsite DDS scanning or contractor, source documents become electronically accessible in CEF.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL018" source="R116_E009" target="R116_E013"><data key="edge_relationship_id">R116_REL018</data><data key="edge_source_entity_id">R116_E009</data><data key="edge_relationship_type">may_use_contracted_processing</data><data key="edge_target_entity_id">R116_E013</data><data key="edge_operational_context">DDS can send paper source documents to unnamed contracted scanner; no specific vendor established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL019" source="R116_E009" target="REPO_CEF"><data key="edge_relationship_id">R116_REL019</data><data key="edge_source_entity_id">R116_E009</data><data key="edge_relationship_type">requires_post_verification_source_destruction</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DDS destroys originals that it locally scans only after verifying CEF access.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL020" source="R116_E010" target="COMP_DMA"><data key="edge_relationship_id">R116_REL020</data><data key="edge_source_entity_id">R116_E010</data><data key="edge_relationship_type">uses_document_management_architecture</data><data key="edge_target_entity_id">COMP_DMA</data><data key="edge_operational_context">DMA barcodes identify and index medical evidence; missing/unreadable codes require exception work.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL021" source="R116_E010" target="REPO_CEF"><data key="edge_relationship_id">R116_REL021</data><data key="edge_source_entity_id">R116_E010</data><data key="edge_relationship_type">corrects_folder_indexing_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Contract scanner can return improperly indexed material or DDS must manually index the scanned evidence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL022" source="R116_E011" target="REPO_CEF"><data key="edge_relationship_id">R116_REL022</data><data key="edge_source_entity_id">R116_E011</data><data key="edge_relationship_type">converts_media_for</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Email/CD evidence is printed then scanned; sending via ERE avoids the print step.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL023" source="R116_E012" target="REPO_CEF"><data key="edge_relationship_id">R116_REL023</data><data key="edge_source_entity_id">R116_E012</data><data key="edge_relationship_type">routes_trailer_evidence_to</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Post-closure DDS evidence is handled as CEF trailer material under dedicated guidance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL024" source="APP_ERE" target="REPO_CEF"><data key="edge_relationship_id">R116_REL024</data><data key="edge_source_entity_id">APP_ERE</data><data key="edge_relationship_type">automatically_uploads_registered_source_evidence_to</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">ERE submissions from registered medical providers and copy services automatically upload into CEF under DI 81020.060E.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL025" source="COMP_DMA" target="REPO_CEF"><data key="edge_relationship_id">R116_REL025</data><data key="edge_source_entity_id">COMP_DMA</data><data key="edge_relationship_type">routes_barcode_faxes_to</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Medical evidence faxes with DMA barcodes automatically upload to CEF.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL026" source="APP_MEGAHIT" target="R116_E014"><data key="edge_relationship_id">R116_REL026</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">requires_request_authorization</data><data key="edge_target_entity_id">R116_E014</data><data key="edge_operational_context">Both listed EDCS source and signed SSA-827 in EF are required for automated HIE request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL027" source="APP_MEGAHIT" target="R116_E015"><data key="edge_relationship_id">R116_REL027</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">applies_single_initial_request_control</data><data key="edge_target_entity_id">R116_E015</data><data key="edge_operational_context">POMS documents one electronic HIE request even with multiple claims/participating sources in case.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL028" source="APP_MEGAHIT" target="R116_E017"><data key="edge_relationship_id">R116_REL028</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">applies_no_automatic_reissue_rule</data><data key="edge_target_entity_id">R116_E017</data><data key="edge_operational_context">MEGAHIT does not generate another request after HIT Response/no records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL029" source="APP_MEGAHIT" target="R116_E016"><data key="edge_relationship_id">R116_REL029</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">uses_payment_eligibility_rule</data><data key="edge_target_entity_id">R116_E016</data><data key="edge_operational_context">Valid initial HIT medical records response may generate HIE payment; no records response does not.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL030" source="DATA_HIT_REQUEST" target="R116_E015"><data key="edge_relationship_id">R116_REL030</data><data key="edge_source_entity_id">DATA_HIT_REQUEST</data><data key="edge_relationship_type">records_hie_request_metadata</data><data key="edge_target_entity_id">R116_E015</data><data key="edge_operational_context">HIT Request artifact records participating source, HIE, date range and request date in EF yellow back.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL031" source="DATA_HIT_RESPONSE" target="R116_E016"><data key="edge_relationship_id">R116_REL031</data><data key="edge_source_entity_id">DATA_HIT_RESPONSE</data><data key="edge_relationship_type">signals_payment_exclusion_under</data><data key="edge_target_entity_id">R116_E016</data><data key="edge_operational_context">HIT Response only/no records does not trigger HIE response payment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL032" source="APP_EDCS" target="R116_E014"><data key="edge_relationship_id">R116_REL032</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supplies_source_list_for_authorization</data><data key="edge_target_entity_id">R116_E014</data><data key="edge_operational_context">EDCS listed HIE participant sources are prerequisite to MEGAHIT initial requests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL033" source="SVC_E1696" target="R116_E018"><data key="edge_relationship_id">R116_REL033</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">delivers_image_to</data><data key="edge_target_entity_id">R116_E018</data><data key="edge_operational_context">After signed e1696 is submitted, WorkTrack contains the electronic SSA-1696-APP image for servicing FO.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL034" source="R116_E018" target="APP_RASR"><data key="edge_relationship_id">R116_REL034</data><data key="edge_source_entity_id">R116_E018</data><data key="edge_relationship_type">passes_appointment_to</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Servicing field-office staff enter and adjudicate appointment info in RASR after WorkTrack receipt.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL035" source="APP_WORKTRACK" target="R116_E018"><data key="edge_relationship_id">R116_REL035</data><data key="edge_source_entity_id">APP_WORKTRACK</data><data key="edge_relationship_type">supports_receipt_of</data><data key="edge_target_entity_id">R116_E018</data><data key="edge_operational_context">WorkTrack is the named application route for incoming electronically signed SSA-1696-APP.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL036" source="APP_RASR" target="R116_E019"><data key="edge_relationship_id">R116_REL036</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">enforces_claim_specific_scope</data><data key="edge_target_entity_id">R116_E019</data><data key="edge_operational_context">RASR staff follow SSA-1696 claim/issue scope rather than assuming universal representation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL037" source="APP_RASR" target="R116_E020"><data key="edge_relationship_id">R116_REL037</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">validates_fee_assignment_entity</data><data key="edge_target_entity_id">R116_E020</data><data key="edge_operational_context">Representative registration and entity EIN/affiliation must meet rules before directing authorized fees to entity.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL038" source="APP_RASR" target="R116_E021"><data key="edge_relationship_id">R116_REL038</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">defaults_entity_field_with</data><data key="edge_target_entity_id">R116_E021</data><data key="edge_operational_context">If entity info is absent or No EIN box checked, RASR represents the individual as sole proprietor.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL039" source="R116_E022" target="SYS_MBR"><data key="edge_relationship_id">R116_REL039</data><data key="edge_source_entity_id">R116_E022</data><data key="edge_relationship_type">not_claimant_address_update_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Witness mailing addresses on a paper appointment support signature validity, not master beneficiary COA.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL040" source="R116_E022" target="SYS_SSR"><data key="edge_relationship_id">R116_REL040</data><data key="edge_source_entity_id">R116_E022</data><data key="edge_relationship_type">not_claimant_address_update_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Witness mailing addresses are not SSI residence address inputs.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL041" source="R116_E023" target="R116_E024"><data key="edge_relationship_id">R116_REL041</data><data key="edge_source_entity_id">R116_E023</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">R116_E024</data><data key="edge_operational_context">SSA Data.gov catalog describes audit recommendations, related audit correspondence and actions maintained in audit database.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL042" source="R116_E023" target="ORG_SSA_OIG"><data key="edge_relationship_id">R116_REL042</data><data key="edge_source_entity_id">R116_E023</data><data key="edge_relationship_type">supports_review_for</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">Official catalog states audits can be requested by internal/external entities such as OIG/GAO; not an automatic upload claim.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL043" source="R116_E025" target="R116_E026"><data key="edge_relationship_id">R116_REL043</data><data key="edge_source_entity_id">R116_E025</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R116_E026</data><data key="edge_operational_context">SSA catalog says CSS houses contractor information and suitability determination and date.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL044" source="R116_E025" target="ORG_SSA_OAG"><data key="edge_relationship_id">R116_REL044</data><data key="edge_source_entity_id">R116_E025</data><data key="edge_relationship_type">governs_personnel_in_contract_context</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">Contractor Suitability System concerns SSA contract personnel security; no asserted direct IT linkage to contracting apps.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R116_REL045" source="ORG_DMDC" target="R116_E027"><data key="edge_relationship_id">R116_REL045</data><data key="edge_source_entity_id">ORG_DMDC</data><data key="edge_relationship_type">receives_ssn_verification_service_via</data><data key="edge_target_entity_id">R116_E027</data><data key="edge_operational_context">DoD DMDC/PERSEREC catalog describes SSA SSN verification for applicant background screening.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL046" source="R116_E027" target="R116_E028"><data key="edge_relationship_id">R116_REL046</data><data key="edge_source_entity_id">R116_E027</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R116_E028</data><data key="edge_operational_context">Agreement request relates to military/federal/contractor applicant SSN verification; not benefit program information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL047" source="R116_E029" target="APP_EDCS"><data key="edge_relationship_id">R116_REL047</data><data key="edge_source_entity_id">R116_E029</data><data key="edge_relationship_type">affects_disability_decision_consistency</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">OIG confirmed adoption-versus-new medical determination issue; neither EDCS automatic control nor a specific EDCS input operation was verified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R116_REL048" source="R116_E031" target="SYS_MBR"><data key="edge_relationship_id">R116_REL048</data><data key="edge_source_entity_id">R116_E031</data><data key="edge_relationship_type">governs_claim_denial_records</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Process-level Title II claims adjudication issue; not a claimed database-trigger rule.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R116_REL049" source="R116_E030" target="SYS_MBR"><data key="edge_relationship_id">R116_REL049</data><data key="edge_source_entity_id">R116_E030</data><data key="edge_relationship_type">requires_correct_post_approval_record_action</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II CIB entitlement/payment dates must reflect correct initial/adopted disability and policy dates.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R116_REL050" source="R116_E032" target="R116_E033"><data key="edge_relationship_id">R116_REL050</data><data key="edge_source_entity_id">R116_E032</data><data key="edge_relationship_type">has_required_followup</data><data key="edge_target_entity_id">R116_E033</data><data key="edge_operational_context">Audit estimated thousands of missing notices and cases with undocumented election not to file.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL051" source="R116_E032" target="R116_E034"><data key="edge_relationship_id">R116_REL051</data><data key="edge_source_entity_id">R116_E032</data><data key="edge_relationship_type">partially_modernized_by</data><data key="edge_target_entity_id">R116_E034</data><data key="edge_operational_context">OIG confirms some notification automation but gaps remain in 2026.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL052" source="R116_E032" target="SYS_MBR"><data key="edge_relationship_id">R116_REL052</data><data key="edge_source_entity_id">R116_E032</data><data key="edge_relationship_type">reviews_offset_cases_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II workers compensation/public-disability benefit reductions drive eligibility for higher RIB evaluation; not proof a new automated MBR lookup.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R116_REL053" source="SYS_SSI_EARN_ALERT" target="R116_E035"><data key="edge_relationship_id">R116_REL053</data><data key="edge_source_entity_id">SYS_SSI_EARN_ALERT</data><data key="edge_relationship_type">subject_to_timeliness_control</data><data key="edge_target_entity_id">R116_E035</data><data key="edge_operational_context">OIG estimates &gt;400k recipients with pending earnings alerts; case-by-case resolution and wage evidence documentation needed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL054" source="R116_E035" target="R116_E036"><data key="edge_relationship_id">R116_REL054</data><data key="edge_source_entity_id">R116_E035</data><data key="edge_relationship_type">constrained_by</data><data key="edge_target_entity_id">R116_E036</data><data key="edge_operational_context">Administrative-finality periods can bar revision/recovery for earlier improper payments despite subsequent wage verification.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL055" source="DB_SSI_IRS_INTERFACE" target="R116_E037"><data key="edge_relationship_id">R116_REL055</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">creates_exception_to_resource_tolerance_via</data><data key="edge_target_entity_id">R116_E037</data><data key="edge_operational_context">5B IRS resource diary overrides routine SSI liquid resource verification tolerance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL056" source="APP_SSI_FINVERIFY" target="R116_E037"><data key="edge_relationship_id">R116_REL056</data><data key="edge_source_entity_id">APP_SSI_FINVERIFY</data><data key="edge_relationship_type">implements_priority_diary_verification</data><data key="edge_target_entity_id">R116_E037</data><data key="edge_operational_context">AFI verification needed when relevant 5B/5H/SB/R8/DI resource diaries on RZ/LI.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL057" source="SYS_SSR" target="R116_E037"><data key="edge_relationship_id">R116_REL057</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">carries_diaries_requiring_verification</data><data key="edge_target_entity_id">R116_E037</data><data key="edge_operational_context">SSI record diary presence forces financial-account verification regardless of balance below usual tolerance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL058" source="R116_E038" target="SYS_SSR"><data key="edge_relationship_id">R116_REL058</data><data key="edge_source_entity_id">R116_E038</data><data key="edge_relationship_type">requires_reconciliation_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Verified wage information entered by technician on SSI Claims wages page or SSR; not automatic WVC posting.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL059" source="R116_E038" target="R116_E039"><data key="edge_relationship_id">R116_REL059</data><data key="edge_source_entity_id">R116_E038</data><data key="edge_relationship_type">produces_evidence_document_for</data><data key="edge_target_entity_id">R116_E039</data><data key="edge_operational_context">External wage evidence must be recorded and discrepancies resolved under SSI policy.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL060" source="R116_E039" target="REPO_CEF"><data key="edge_relationship_id">R116_REL060</data><data key="edge_source_entity_id">R116_E039</data><data key="edge_relationship_type">may_store_verified_information_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Wage verification documentation can be stored in certified electronic folder.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL061" source="R116_E039" target="REPO_NDRED"><data key="edge_relationship_id">R116_REL061</data><data key="edge_source_entity_id">R116_E039</data><data key="edge_relationship_type">may_store_verified_information_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">NDRED used when CEF unavailable; Evidence Portal carries uploaded supporting documents.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL062" source="R116_E039" target="APP_EVID"><data key="edge_relationship_id">R116_REL062</data><data key="edge_source_entity_id">R116_E039</data><data key="edge_relationship_type">may_use_locked_record_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Technician may use locked EVID or Report of Contact to document wage verification when applicable.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL063" source="PROC_ERRONEOUS_DEATH_CORRECTION" target="R116_E040"><data key="edge_relationship_id">R116_REL063</data><data key="edge_source_entity_id">PROC_ERRONEOUS_DEATH_CORRECTION</data><data key="edge_relationship_type">requires_reason_documentation</data><data key="edge_target_entity_id">R116_E040</data><data key="edge_operational_context">Death-removal reason, initial cause, and correction steps must be documented to preserve audit trail and future case history.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL064" source="R116_E040" target="SYS_NUMIDENT"><data key="edge_relationship_id">R116_REL064</data><data key="edge_source_entity_id">R116_E040</data><data key="edge_relationship_type">protects_authoritative_record</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Death corrections affect identity records and downstream DMF content; QA is not a new automatic DMF synchronization claim.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL065" source="R116_E041" target="APP_ROAR"><data key="edge_relationship_id">R116_REL065</data><data key="edge_source_entity_id">R116_E041</data><data key="edge_relationship_type">applies_to_debt_context_from</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">Overpayment notice QA concerns records used by Title II recovery processing; does not establish automatic ROAR notice generation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="R116_REL066" source="PROC_SSI_UNDERPAY_PREPAY_REVIEW" target="R116_E042"><data key="edge_relationship_id">R116_REL066</data><data key="edge_source_entity_id">PROC_SSI_UNDERPAY_PREPAY_REVIEW</data><data key="edge_relationship_type">includes_deceased_recipient_nonpayability_check</data><data key="edge_target_entity_id">R116_E042</data><data key="edge_operational_context">OIG recommends correcting SSI underpayment records that cannot legally be released after death; manual review and policy controls apply.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL067" source="PORTAL_SUMS_MCAS_MI_CENTRAL" target="DB_SSI_IRS_INTERFACE"><data key="edge_relationship_id">R116_REL067</data><data key="edge_source_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_relationship_type">provides_5b_development_from</data><data key="edge_target_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_operational_context">POMS SI 02310.045 names MI Central and SSTNG as routes for controlled and informational 5B alerts; interface is separate from SSR diary posting.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R116_REL068" source="SYS_SSR" target="DB_SSI_IRS_INTERFACE"><data key="edge_relationship_id">R116_REL068</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">receives_controlled_5b_diary_from</data><data key="edge_target_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_operational_context">IRS transaction resource/income tolerance rules cause 5B controlled diary on SSR; informational alerts may remain query-only.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R117_REL0001" source="FORM_SSA635" target="APP_EP"><data key="edge_relationship_id">R117_REL0001</data><data key="edge_source_entity_id">FORM_SSA635</data><data key="edge_relationship_type">stored_after_final_review_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">SSA-635 is sent to Evidence Portal only after final determination and all applicable review approvals.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R104_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0002" source="R117_E001" target="FORM_SSA635"><data key="edge_relationship_id">R117_REL0002</data><data key="edge_source_entity_id">R117_E001</data><data key="edge_relationship_type">gates_storage_of</data><data key="edge_target_entity_id">FORM_SSA635</data><data key="edge_operational_context">Hold SSA-635 out of EP when waiver approval requires additional review; store after review completes.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R104_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0003" source="R117_E001" target="APP_EP"><data key="edge_relationship_id">R117_REL0003</data><data key="edge_source_entity_id">R117_E001</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Finalized waiver form is faxed or imported to Evidence Portal.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R104_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0004" source="SYS_SSR" target="R117_E002"><data key="edge_relationship_id">R117_REL0004</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains_field</data><data key="edge_target_entity_id">R117_E002</data><data key="edge_operational_context">SSR OPSQ segment carries overpayment sequence number and sequence date recorded on SSA-635.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R104_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0005" source="FORM_SSA635" target="R117_E002"><data key="edge_relationship_id">R117_REL0005</data><data key="edge_source_entity_id">FORM_SSA635</data><data key="edge_relationship_type">references</data><data key="edge_target_entity_id">R117_E002</data><data key="edge_operational_context">Title XVI waiver form records SSR OPSQ sequence ID and SQD date; no update to SSR implied.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R104_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0006" source="FORM_SSA635" target="R117_E003"><data key="edge_relationship_id">R117_REL0006</data><data key="edge_source_entity_id">FORM_SSA635</data><data key="edge_relationship_type">references</data><data key="edge_target_entity_id">R117_E003</data><data key="edge_operational_context">Title II waiver form references ROAR event identifier.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R104_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0007" source="R117_E004" target="APP_DMS"><data key="edge_relationship_id">R117_REL0007</data><data key="edge_source_entity_id">R117_E004</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Title II waiver review disagreements or requests for additional documentation recorded in DMS remarks.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R104_001 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0008" source="R117_E004" target="FORM_SSA635"><data key="edge_relationship_id">R117_REL0008</data><data key="edge_source_entity_id">R117_E004</data><data key="edge_relationship_type">references</data><data key="edge_target_entity_id">FORM_SSA635</data><data key="edge_operational_context">Reviewer may return proposed waiver for missing SSA-635 or insufficient documentation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R104_001 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0009" source="R117_E005" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">R117_REL0009</data><data key="edge_source_entity_id">R117_E005</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">Administrative tolerance depends on ORIGINAL &lt;= $2,000 and household/fault factors, not remaining balance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC03 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0010" source="R117_E006" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">R117_REL0010</data><data key="edge_source_entity_id">R117_E006</data><data key="edge_relationship_type">informs</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">Paid versus payable chart provides overpayment amount and time period used in waiver determinations.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC06 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0011" source="R117_E007" target="R117_E006"><data key="edge_relationship_id">R117_REL0011</data><data key="edge_source_entity_id">R117_E007</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R117_E006</data><data key="edge_operational_context">Manual charts and supporting materials must be retained for lifetime of overpayment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC06 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0012" source="SYS_SSR" target="R117_E008"><data key="edge_relationship_id">R117_REL0012</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">holds_control</data><data key="edge_target_entity_id">R117_E008</data><data key="edge_operational_context">KB and priority-select diary conditions recorded on SSR determine limited issue or full RZ.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R96_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0013" source="R117_E008" target="WORK_SSI_KB_DIARY"><data key="edge_relationship_id">R117_REL0013</data><data key="edge_source_entity_id">R117_E008</data><data key="edge_relationship_type">defers</data><data key="edge_target_entity_id">WORK_SSI_KB_DIARY</data><data key="edge_operational_context">Priority-select diary triggers limited issue and KB RZ waits until diary maturity.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R96_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0014" source="R117_E009" target="SYS_SSR"><data key="edge_relationship_id">R117_REL0014</data><data key="edge_source_entity_id">R117_E009</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">At 18th birthday, SSI Claims living-arrangement update changes Type of Master Record to DI/BI.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R96_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0015" source="R117_E009" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R117_REL0015</data><data key="edge_source_entity_id">R117_E009</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">SSI Claims posts age-18 living arrangement and household/student changes.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R96_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0016" source="R117_E009" target="FORM_SSA1719B"><data key="edge_relationship_id">R117_REL0016</data><data key="edge_source_entity_id">R117_E009</data><data key="edge_relationship_type">fallback_uses</data><data key="edge_target_entity_id">FORM_SSA1719B</data><data key="edge_operational_context">Non-SSI Claims cases transmit RZ and SY/TY inputs via SSA-1719B.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R96_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0017" source="R117_E010" target="WORK_SSI_KB_DIARY"><data key="edge_relationship_id">R117_REL0017</data><data key="edge_source_entity_id">R117_E010</data><data key="edge_relationship_type">clears_after_monthly_merge</data><data key="edge_target_entity_id">WORK_SSI_KB_DIARY</data><data key="edge_operational_context">Correcting erroneous SSR DOB before age 18 clears profile K in next monthly merge.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R96_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0018" source="R117_E011" target="SYS_MBR"><data key="edge_relationship_id">R117_REL0018</data><data key="edge_source_entity_id">R117_E011</data><data key="edge_relationship_type">follows</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II child benefit age-18 termination may set 2F diary on payment record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R96_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0019" source="WORK_SSI_KB_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R117_REL0019</data><data key="edge_source_entity_id">WORK_SSI_KB_DIARY</data><data key="edge_relationship_type">reviewed_with</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">DCF and Post Entitlement ODS used to check when disability redetermination scheduled.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R96_002 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0020" source="APP_ECOMPS" target="R117_E018"><data key="edge_relationship_id">R117_REL0020</data><data key="edge_source_entity_id">APP_ECOMPS</data><data key="edge_relationship_type">computes</data><data key="edge_target_entity_id">R117_E018</data><data key="edge_operational_context">eComps calculates SSI RMA and windfall offset figures for manual Title II/XVI offset.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0021" source="APP_ECOMPS" target="R117_E015"><data key="edge_relationship_id">R117_REL0021</data><data key="edge_source_entity_id">APP_ECOMPS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R117_E015</data><data key="edge_operational_context">eComps printout substitutes for paper SSA-4968 RMA worksheets in certain cases.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0022" source="R117_E015" target="FORM_SSA4968"><data key="edge_relationship_id">R117_REL0022</data><data key="edge_source_entity_id">R117_E015</data><data key="edge_relationship_type">substitutes_for</data><data key="edge_target_entity_id">FORM_SSA4968</data><data key="edge_operational_context">SSA-4968 paper payment worksheet may be replaced by an eComps computation printout.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0023" source="R117_E013" target="R117_E014"><data key="edge_relationship_id">R117_REL0023</data><data key="edge_source_entity_id">R117_E013</data><data key="edge_relationship_type">electronically_replaces</data><data key="edge_target_entity_id">R117_E014</data><data key="edge_operational_context">e4345 is web-based form of SSA-4345-U2, used to exchange windfall offset data between FO and PC.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0024" source="R117_E016" target="R117_E014"><data key="edge_relationship_id">R117_REL0024</data><data key="edge_source_entity_id">R117_E016</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R117_E014</data><data key="edge_operational_context">Paper SSA-4345-U2 fallback when e4345 unavailable; later enter information in e4345.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0025" source="R117_E016" target="APP_EP"><data key="edge_relationship_id">R117_REL0025</data><data key="edge_source_entity_id">R117_E016</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">When urgent, fax SSA-4345-U2 into electronic folder with Evidence Portal and notify PC.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0026" source="R117_E016" target="R117_E013"><data key="edge_relationship_id">R117_REL0026</data><data key="edge_source_entity_id">R117_E016</data><data key="edge_relationship_type">returns_to</data><data key="edge_target_entity_id">R117_E013</data><data key="edge_operational_context">e4345 must be updated after service restored, including paper fallback cases.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0027" source="SYS_SSR" target="R117_E017"><data key="edge_relationship_id">R117_REL0027</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains_field</data><data key="edge_target_entity_id">R117_E017</data><data key="edge_operational_context">SSR CMPH state and county code is prefilled from residence ZIP by SSI Claims.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0028" source="APP_SSI_CLAIMS_LOGICAL" target="R117_E017"><data key="edge_relationship_id">R117_REL0028</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">derives</data><data key="edge_target_entity_id">R117_E017</data><data key="edge_operational_context">Residence ZIP input determines state/county code for SSI supplementary payment computation; not an independent postal address source.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0029" source="R117_E017" target="DATA_SSR_CMPH_SEGMENT"><data key="edge_relationship_id">R117_REL0029</data><data key="edge_source_entity_id">R117_E017</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">DATA_SSR_CMPH_SEGMENT</data><data key="edge_operational_context">SSR Computation History segment contains state/county coding based on residence ZIP.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0030" source="R117_E018" target="SYS_SSR"><data key="edge_relationship_id">R117_REL0030</data><data key="edge_source_entity_id">R117_E018</data><data key="edge_relationship_type">posted_with_separate_action_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Manual windfall offset result must be posted to SSR using SM 01320.201; no automatic transfer inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0031" source="APP_ECOMPS" target="FORM_SSA4346U2"><data key="edge_relationship_id">R117_REL0031</data><data key="edge_source_entity_id">APP_ECOMPS</data><data key="edge_relationship_type">feeds_worksheet_equivalent</data><data key="edge_target_entity_id">FORM_SSA4346U2</data><data key="edge_operational_context">Windfall Results/Offset Summary tabs correspond to paper SSA-4346-U2.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0032" source="R117_E015" target="APP_EP"><data key="edge_relationship_id">R117_REL0032</data><data key="edge_source_entity_id">R117_E015</data><data key="edge_relationship_type">stored_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">For claims without an electronic folder accessible through eView, output may be stored through Evidence Portal/NDRed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0033" source="R117_E013" target="R117_E018"><data key="edge_relationship_id">R117_REL0033</data><data key="edge_source_entity_id">R117_E013</data><data key="edge_relationship_type">supports_cross_component_exchange_for</data><data key="edge_target_entity_id">R117_E018</data><data key="edge_operational_context">Field office and processing center exchange Title II figures needed to compute offset.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from SRC_R30_005 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0034" source="R117_E019" target="R117_E020"><data key="edge_relationship_id">R117_REL0034</data><data key="edge_source_entity_id">R117_E019</data><data key="edge_relationship_type">awarded_contract</data><data key="edge_target_entity_id">R117_E020</data><data key="edge_operational_context">SSA FY2022 forecast identifies the contractor and corresponding SSA awarded contract.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0035" source="R117_E020" target="EX_AFI_FI"><data key="edge_relationship_id">R117_REL0035</data><data key="edge_source_entity_id">R117_E020</data><data key="edge_relationship_type">procures_or_supports</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Accuity was SSA AFI contractor under 2021 award per FY2022 forecast. This does not establish vendor in October 2026.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Historical award evidence only; not proof of modern deployment or exact software platform.</data></edge><edge id="R117_REL0036" source="R117_E021" target="R117_E022"><data key="edge_relationship_id">R117_REL0036</data><data key="edge_source_entity_id">R117_E021</data><data key="edge_relationship_type">awarded_contract</data><data key="edge_target_entity_id">R117_E022</data><data key="edge_operational_context">SSA FY2022 forecast identifies the contractor and corresponding SSA awarded contract.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0037" source="R117_E022" target="R117_E033"><data key="edge_relationship_id">R117_REL0037</data><data key="edge_source_entity_id">R117_E022</data><data key="edge_relationship_type">procures_or_supports</data><data key="edge_target_entity_id">R117_E033</data><data key="edge_operational_context">Experian awarded beneficiary online identification and verification services; mapping to specific deployed SSA application is not proven.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Historical award evidence only; not proof of modern deployment or exact software platform.</data></edge><edge id="R117_REL0038" source="R117_E023" target="R117_E024"><data key="edge_relationship_id">R117_REL0038</data><data key="edge_source_entity_id">R117_E023</data><data key="edge_relationship_type">awarded_contract</data><data key="edge_target_entity_id">R117_E024</data><data key="edge_operational_context">SSA FY2022 forecast identifies the contractor and corresponding SSA awarded contract.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0039" source="R117_E024" target="APP_SAFE"><data key="edge_relationship_id">R117_REL0039</data><data key="edge_source_entity_id">R117_E024</data><data key="edge_relationship_type">procures_or_supports</data><data key="edge_target_entity_id">APP_SAFE</data><data key="edge_operational_context">ICF had SSA SAFE development and maintenance order in 2021.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Historical award evidence only; not proof of modern deployment or exact software platform.</data></edge><edge id="R117_REL0040" source="R117_E025" target="R117_E026"><data key="edge_relationship_id">R117_REL0040</data><data key="edge_source_entity_id">R117_E025</data><data key="edge_relationship_type">awarded_contract</data><data key="edge_target_entity_id">R117_E026</data><data key="edge_operational_context">SSA FY2022 forecast identifies the contractor and corresponding SSA awarded contract.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0041" source="R117_E026" target="PLAT_NETWORK"><data key="edge_relationship_id">R117_REL0041</data><data key="edge_source_entity_id">R117_E026</data><data key="edge_relationship_type">procures_or_supports</data><data key="edge_target_entity_id">PLAT_NETWORK</data><data key="edge_operational_context">Northrop Grumman network infrastructure BPA from 2021; no network topology implied.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Historical award evidence only; not proof of modern deployment or exact software platform.</data></edge><edge id="R117_REL0042" source="R117_E027" target="R117_E028"><data key="edge_relationship_id">R117_REL0042</data><data key="edge_source_entity_id">R117_E027</data><data key="edge_relationship_type">awarded_contract</data><data key="edge_target_entity_id">R117_E028</data><data key="edge_operational_context">SSA FY2022 forecast identifies the contractor and corresponding SSA awarded contract.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0043" source="R117_E028" target="PLAT_NETWORK"><data key="edge_relationship_id">R117_REL0043</data><data key="edge_source_entity_id">R117_E028</data><data key="edge_relationship_type">procures_or_supports</data><data key="edge_target_entity_id">PLAT_NETWORK</data><data key="edge_operational_context">Colossal Contracting network equipment/software supply contract; no deployed product brand implied.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Historical award evidence only; not proof of modern deployment or exact software platform.</data></edge><edge id="R117_REL0044" source="R117_E029" target="R117_E030"><data key="edge_relationship_id">R117_REL0044</data><data key="edge_source_entity_id">R117_E029</data><data key="edge_relationship_type">awarded_contract</data><data key="edge_target_entity_id">R117_E030</data><data key="edge_operational_context">SSA FY2022 forecast identifies the contractor and corresponding SSA awarded contract.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0045" source="R117_E030" target="R117_E034"><data key="edge_relationship_id">R117_REL0045</data><data key="edge_source_entity_id">R117_E030</data><data key="edge_relationship_type">procures_or_supports</data><data key="edge_target_entity_id">R117_E034</data><data key="edge_operational_context">Tyto Athene multimedia support award; no named underlying audiovisual platform inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Historical award evidence only; not proof of modern deployment or exact software platform.</data></edge><edge id="R117_REL0046" source="R117_E020" target="R117_E031"><data key="edge_relationship_id">R117_REL0046</data><data key="edge_source_entity_id">R117_E020</data><data key="edge_relationship_type">appears_in</data><data key="edge_target_entity_id">R117_E031</data><data key="edge_operational_context">OAG November 2023 snapshot lists 2021 contract and several AFI-related delivery orders for Accuity.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC08 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0047" source="R117_E019" target="R107_E005"><data key="edge_relationship_id">R117_REL0047</data><data key="edge_source_entity_id">R117_E019</data><data key="edge_relationship_type">supports_historical_afi_liaison</data><data key="edge_target_entity_id">R107_E005</data><data key="edge_operational_context">Official procurement retrospectively identifies 2021–2026 Accuity contractor, but not necessarily the vendor servicing Oct 2026 transaction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0048" source="R117_E032" target="R117_E026"><data key="edge_relationship_id">R117_REL0048</data><data key="edge_source_entity_id">R117_E032</data><data key="edge_relationship_type">has_historical_support_award</data><data key="edge_target_entity_id">R117_E026</data><data key="edge_operational_context">Network infrastructure services BPA confirmed in SSA historical acquisition forecast.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R117_REL0049" source="R117_E032" target="R117_E028"><data key="edge_relationship_id">R117_REL0049</data><data key="edge_source_entity_id">R117_E032</data><data key="edge_relationship_type">has_separate_equipment_award</data><data key="edge_target_entity_id">R117_E028</data><data key="edge_operational_context">Separate network equipment and software requirements contract confirmed awarded to Colossal Contracting.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence from R117_SRC07 does not establish an undocumented technical interface.</data></edge><edge id="R118_REL0001" source="APP_IRON" target="R118_E001"><data key="edge_relationship_id">R118_REL0001</data><data key="edge_source_entity_id">APP_IRON</data><data key="edge_relationship_type">retrieves_historical_evidence</data><data key="edge_target_entity_id">R118_E001</data><data key="edge_operational_context">IRON provides original SS-5/microprint for keying-error review.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0002" source="APP_SS5_REPRINTS" target="R118_E001"><data key="edge_relationship_id">R118_REL0002</data><data key="edge_source_entity_id">APP_SS5_REPRINTS</data><data key="edge_relationship_type">retrieves_historical_evidence</data><data key="edge_target_entity_id">R118_E001</data><data key="edge_operational_context">SS-5 Reprints provides prior SS-5 for the same correction review.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0003" source="R118_E001" target="PROC_NCP"><data key="edge_relationship_id">R118_REL0003</data><data key="edge_source_entity_id">R118_E001</data><data key="edge_relationship_type">required_by_documented_keying_error_gate</data><data key="edge_target_entity_id">PROC_NCP</data><data key="edge_operational_context">Documented original-application mismatch, or verifiable EAB source error, is needed before NCP.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0004" source="SYS_NUMIDENT" target="R118_E002"><data key="edge_relationship_id">R118_REL0004</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">triggers_conditional_reconciliation</data><data key="edge_target_entity_id">R118_E002</data><data key="edge_operational_context">When Numident sex code changes, policy requires updates to other affected program records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0005" source="R118_E002" target="SYS_MBR"><data key="edge_relationship_id">R118_REL0005</data><data key="edge_source_entity_id">R118_E002</data><data key="edge_relationship_type">requires_applicable_staff_record_action</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Policy requires technicians to update applicable SYS_MBR information after Numident correction; no automatic interface established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0006" source="R118_E002" target="SYS_SSR"><data key="edge_relationship_id">R118_REL0006</data><data key="edge_source_entity_id">R118_E002</data><data key="edge_relationship_type">requires_applicable_staff_record_action</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Policy requires technicians to update applicable SYS_SSR information after Numident correction; no automatic interface established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0007" source="R118_E002" target="APP_ERPS"><data key="edge_relationship_id">R118_REL0007</data><data key="edge_source_entity_id">R118_E002</data><data key="edge_relationship_type">requires_applicable_staff_record_action</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Policy requires technicians to update applicable APP_ERPS information after Numident correction; no automatic interface established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0008" source="DATA_NUMIDENT_PARENT_NAME" target="R118_E003"><data key="edge_relationship_id">R118_REL0008</data><data key="edge_source_entity_id">DATA_NUMIDENT_PARENT_NAME</data><data key="edge_relationship_type">triggers_conditional_reconciliation</data><data key="edge_target_entity_id">R118_E003</data><data key="edge_operational_context">Numident parent-name edit triggers inquiry about parent program/payee roles.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0009" source="R118_E003" target="SYS_MBR"><data key="edge_relationship_id">R118_REL0009</data><data key="edge_source_entity_id">R118_E003</data><data key="edge_relationship_type">may_require_related_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Employee reviews applicable SYS_MBR records and initiates needed corrections, not universal automatic changes.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0010" source="R118_E003" target="SYS_SSR"><data key="edge_relationship_id">R118_REL0010</data><data key="edge_source_entity_id">R118_E003</data><data key="edge_relationship_type">may_require_related_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Employee reviews applicable SYS_SSR records and initiates needed corrections, not universal automatic changes.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0011" source="R118_E003" target="APP_ERPS"><data key="edge_relationship_id">R118_REL0011</data><data key="edge_source_entity_id">R118_E003</data><data key="edge_relationship_type">may_require_related_update</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Employee reviews applicable APP_ERPS records and initiates needed corrections, not universal automatic changes.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0012" source="R118_E004" target="PROC_NCP"><data key="edge_relationship_id">R118_REL0012</data><data key="edge_source_entity_id">R118_E004</data><data key="edge_relationship_type">may_substitute_as_verified_input_error_evidence_for</data><data key="edge_target_entity_id">PROC_NCP</data><data key="edge_operational_context">In established automated-enumeration exchanges, originating-entity documentation can support keying-error correction without an ordinary SS-5.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0013" source="APP_SSNAP" target="R118_E004"><data key="edge_relationship_id">R118_REL0013</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">applies</data><data key="edge_target_entity_id">R118_E004</data><data key="edge_operational_context">SSNAP NCP evaluates substantiated source-entity error for automated enumeration transactions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0014" source="APP_SSNAP" target="R118_E005"><data key="edge_relationship_id">R118_REL0014</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">applies</data><data key="edge_target_entity_id">R118_E005</data><data key="edge_operational_context">SSNAP processes record corrections even when card replacement is unnecessary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0015" source="R118_E005" target="SYS_NUMIDENT"><data key="edge_relationship_id">R118_REL0015</data><data key="edge_source_entity_id">R118_E005</data><data key="edge_relationship_type">separates_record_update_from_card_issuance_on</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">A Numident record attribute may change without printing or issuing a replacement SSN card.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0016" source="APP_UPLOAD_DOCUMENTS" target="R118_E006"><data key="edge_relationship_id">R118_REL0016</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">offers_submissions_subject_to</data><data key="edge_target_entity_id">R118_E006</data><data key="edge_operational_context">Upload Documents is a documented form submission channel, with additional verification required for the listed forms; step-up implementation unspecified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0017" source="FORM_SSA827" target="R118_E006"><data key="edge_relationship_id">R118_REL0017</data><data key="edge_source_entity_id">FORM_SSA827</data><data key="edge_relationship_type">requires_additional_identity_verification_for_online_submission</data><data key="edge_target_entity_id">R118_E006</data><data key="edge_operational_context">SSA Forms catalog explicitly requires further identity verification to electronically submit FORM_SSA827.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0018" source="FORM_SSA_2574" target="R118_E006"><data key="edge_relationship_id">R118_REL0018</data><data key="edge_source_entity_id">FORM_SSA_2574</data><data key="edge_relationship_type">requires_additional_identity_verification_for_online_submission</data><data key="edge_target_entity_id">R118_E006</data><data key="edge_operational_context">SSA Forms catalog explicitly requires further identity verification to electronically submit FORM_SSA_2574.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0019" source="FORM_SSA2935" target="R118_E006"><data key="edge_relationship_id">R118_REL0019</data><data key="edge_source_entity_id">FORM_SSA2935</data><data key="edge_relationship_type">requires_additional_identity_verification_for_online_submission</data><data key="edge_target_entity_id">R118_E006</data><data key="edge_operational_context">SSA Forms catalog explicitly requires further identity verification to electronically submit FORM_SSA2935.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0020" source="FORM_SSA8510" target="R118_E006"><data key="edge_relationship_id">R118_REL0020</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">requires_additional_identity_verification_for_online_submission</data><data key="edge_target_entity_id">R118_E006</data><data key="edge_operational_context">SSA Forms catalog explicitly requires further identity verification to electronically submit FORM_SSA8510.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0021" source="FORM_SSA454BK" target="R118_E006"><data key="edge_relationship_id">R118_REL0021</data><data key="edge_source_entity_id">FORM_SSA454BK</data><data key="edge_relationship_type">requires_additional_identity_verification_for_online_submission</data><data key="edge_target_entity_id">R118_E006</data><data key="edge_operational_context">SSA-454-BK appears in SSA list of five step-up forms.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0022" source="APP_UPLOAD_DOCUMENTS" target="R118_E007"><data key="edge_relationship_id">R118_REL0022</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">offers_public_pdf_submission_route_matching</data><data key="edge_target_entity_id">R118_E007</data><data key="edge_operational_context">SSA Forms describes Upload Documents as its document submission feature, alongside distinct Complete Online Form options; per-form backend unspecified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0023" source="FORM_HA85" target="R118_E007"><data key="edge_relationship_id">R118_REL0023</data><data key="edge_source_entity_id">FORM_HA85</data><data key="edge_relationship_type">offers_both_online_completion_and_pdf_upload_through_ssa_form_directory</data><data key="edge_target_entity_id">R118_E007</data><data key="edge_operational_context">SSA Forms directory presents Complete Online and Upload PDF options for FORM_HA85; this does not prove an automated hearing-case update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0024" source="FORM_HA86" target="R118_E007"><data key="edge_relationship_id">R118_REL0024</data><data key="edge_source_entity_id">FORM_HA86</data><data key="edge_relationship_type">offers_both_online_completion_and_pdf_upload_through_ssa_form_directory</data><data key="edge_target_entity_id">R118_E007</data><data key="edge_operational_context">SSA Forms directory presents Complete Online and Upload PDF options for FORM_HA86; this does not prove an automated hearing-case update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0025" source="FORM_HA539" target="R118_E007"><data key="edge_relationship_id">R118_REL0025</data><data key="edge_source_entity_id">FORM_HA539</data><data key="edge_relationship_type">offers_both_online_completion_and_pdf_upload_through_ssa_form_directory</data><data key="edge_target_entity_id">R118_E007</data><data key="edge_operational_context">SSA Forms directory presents Complete Online and Upload PDF options for FORM_HA539; this does not prove an automated hearing-case update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0026" source="FORM_HA4631" target="R118_E007"><data key="edge_relationship_id">R118_REL0026</data><data key="edge_source_entity_id">FORM_HA4631</data><data key="edge_relationship_type">offers_both_online_completion_and_pdf_upload_through_ssa_form_directory</data><data key="edge_target_entity_id">R118_E007</data><data key="edge_operational_context">SSA Forms directory presents Complete Online and Upload PDF options for FORM_HA4631; this does not prove an automated hearing-case update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0027" source="FORM_HA4632" target="R118_E007"><data key="edge_relationship_id">R118_REL0027</data><data key="edge_source_entity_id">FORM_HA4632</data><data key="edge_relationship_type">offers_both_online_completion_and_pdf_upload_through_ssa_form_directory</data><data key="edge_target_entity_id">R118_E007</data><data key="edge_operational_context">SSA Forms directory presents Complete Online and Upload PDF options for FORM_HA4632; this does not prove an automated hearing-case update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0028" source="FORM_HA4633" target="R118_E007"><data key="edge_relationship_id">R118_REL0028</data><data key="edge_source_entity_id">FORM_HA4633</data><data key="edge_relationship_type">offers_both_online_completion_and_pdf_upload_through_ssa_form_directory</data><data key="edge_target_entity_id">R118_E007</data><data key="edge_operational_context">SSA Forms directory presents Complete Online and Upload PDF options for FORM_HA4633; this does not prove an automated hearing-case update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0029" source="PROC_ERPS_ORG_MASS_CHANGE" target="R118_E008"><data key="edge_relationship_id">R118_REL0029</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">requires_manual_notice_control</data><data key="edge_target_entity_id">R118_E008</data><data key="edge_operational_context">SSA explicitly states eRPS does not automatically issue required group-change advance notice.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0030" source="R118_E008" target="WORK_ERPS_MASS_15_DAY"><data key="edge_relationship_id">R118_REL0030</data><data key="edge_source_entity_id">R118_E008</data><data key="edge_relationship_type">sets</data><data key="edge_target_entity_id">WORK_ERPS_MASS_15_DAY</data><data key="edge_operational_context">Staff establish due-process RPS diary and tickle for 15 days; exceptions documented when beneficiary acknowledges in advance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0031" source="PROC_ERPS_ORG_MASS_CHANGE" target="R118_E009"><data key="edge_relationship_id">R118_REL0031</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">R118_E009</data><data key="edge_operational_context">Payee transfer may require separate affected-beneficiary residence corrections only when addresses have changed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0032" source="R118_E009" target="UI_ERPS_BENEFICIARY_ADDRESS_CHANGE"><data key="edge_relationship_id">R118_REL0032</data><data key="edge_source_entity_id">R118_E009</data><data key="edge_relationship_type">uses_manual_input_screen</data><data key="edge_target_entity_id">UI_ERPS_BENEFICIARY_ADDRESS_CHANGE</data><data key="edge_operational_context">Technician updates beneficiary residence via screen MS 07414.010 when necessary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0033" source="PROC_ERPS_ORG_MASS_CHANGE" target="R118_E010"><data key="edge_relationship_id">R118_REL0033</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">R118_E010</data><data key="edge_operational_context">Mass-change uses one SSA-11 plus complete list of affected beneficiaries; evidence filed by first SSN.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0034" source="R118_E010" target="REPO_NDRED"><data key="edge_relationship_id">R118_REL0034</data><data key="edge_source_entity_id">R118_E010</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">SSA-11 evidence may be uploaded to NDRED using Evidence Portal under first beneficiary SSN.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0035" source="R118_E010" target="APP_EVIEW"><data key="edge_relationship_id">R118_REL0035</data><data key="edge_source_entity_id">R118_E010</data><data key="edge_relationship_type">alternatively_stored_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">SSA-11 evidence may be stored in eView under first beneficiary SSN.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0036" source="UI_ERPS_MAKE_NOTE" target="R118_E010"><data key="edge_relationship_id">R118_REL0036</data><data key="edge_source_entity_id">UI_ERPS_MAKE_NOTE</data><data key="edge_relationship_type">records_pointer_to</data><data key="edge_target_entity_id">R118_E010</data><data key="edge_operational_context">eRPS Make Note records the SSN under which common-payee SSA-11 documentation is stored.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0037" source="UI_ERPS_ROC_DETAILS" target="R118_E011"><data key="edge_relationship_id">R118_REL0037</data><data key="edge_source_entity_id">UI_ERPS_ROC_DETAILS</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R118_E011</data><data key="edge_operational_context">eRPS RPOC documentation uses CAPA-CURRENT PAYEE CONTACT in Report section for payee contact.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0038" source="R118_E011" target="PROC_REP_PAYEE_CAPABILITY_DEV"><data key="edge_relationship_id">R118_REL0038</data><data key="edge_source_entity_id">R118_E011</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_REP_PAYEE_CAPABILITY_DEV</data><data key="edge_operational_context">Contact is evidence for a new payee capability decision before direct payment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0039" source="R118_E012" target="UI_CCE_ROC"><data key="edge_relationship_id">R118_REL0039</data><data key="edge_source_entity_id">R118_E012</data><data key="edge_relationship_type">uses_title_xvi</data><data key="edge_target_entity_id">UI_CCE_ROC</data><data key="edge_operational_context">Non-eRPS SSI capability contacts use CCE Report of Contact with CAPA-CURRENT PAYEE CONTACT narrative.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0040" source="R118_E012" target="FORM_SSA5002"><data key="edge_relationship_id">R118_REL0040</data><data key="edge_source_entity_id">R118_E012</data><data key="edge_relationship_type">fallback_documents_in</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">If electronic RPOC unavailable staff prepare SSA-5002 and store it in evidence repository.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0041" source="FORM_SSA5002" target="REPO_NDRED"><data key="edge_relationship_id">R118_REL0041</data><data key="edge_source_entity_id">FORM_SSA5002</data><data key="edge_relationship_type">may_be_stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Fallback report of contact filed in NDRED via Evidence Portal.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0042" source="R118_E013" target="REPO_EF"><data key="edge_relationship_id">R118_REL0042</data><data key="edge_source_entity_id">R118_E013</data><data key="edge_relationship_type">alerts_new_evidence_uploaded_to</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">UAT notification follows filing of additional evidence into electronic folder; no UAT backend inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0043" source="REPO_EF" target="R118_E013"><data key="edge_relationship_id">R118_REL0043</data><data key="edge_source_entity_id">REPO_EF</data><data key="edge_relationship_type">receives_new_ac_evidence_alert_via</data><data key="edge_target_entity_id">R118_E013</data><data key="edge_operational_context">FO faxes additional evidence to electronic folder then uses UAT notification to AC; no persistence path specified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0044" source="FORM_HA86" target="R118_E014"><data key="edge_relationship_id">R118_REL0044</data><data key="edge_source_entity_id">FORM_HA86</data><data key="edge_relationship_type">used_for</data><data key="edge_target_entity_id">R118_E014</data><data key="edge_operational_context">The pending Appeals Council request must be dismissed before new disability application processing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0045" source="R118_E014" target="APP_EVIEW"><data key="edge_relationship_id">R118_REL0045</data><data key="edge_source_entity_id">R118_E014</data><data key="edge_relationship_type">uses_notice_or_dismissal_condition_for</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Policy distinguishes evidence/documents in electronic appeal folder from approval of withdrawal; no automatic new claim filing inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0046" source="APP_MYSSA" target="R118_E015"><data key="edge_relationship_id">R118_REL0046</data><data key="edge_source_entity_id">APP_MYSSA</data><data key="edge_relationship_type">offers</data><data key="edge_target_entity_id">R118_E015</data><data key="edge_operational_context">mySSA offers SSA-1099/1042S benefit-statement download and limited paper replacement service.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0047" source="R118_E016" target="SYS_MBR"><data key="edge_relationship_id">R118_REL0047</data><data key="edge_source_entity_id">R118_E016</data><data key="edge_relationship_type">reads_last_mail_address_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For deceased individual, SSA mails SSA-1099 to last MBR address.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0048" source="R118_E016" target="APP_MYSSA"><data key="edge_relationship_id">R118_REL0048</data><data key="edge_source_entity_id">R118_E016</data><data key="edge_relationship_type">restricts_portal_use_of</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">eAccess blocks access to deceased beneficiary mySSA accounts; no new address update implied.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0049" source="R118_E018" target="R118_E017"><data key="edge_relationship_id">R118_REL0049</data><data key="edge_source_entity_id">R118_E018</data><data key="edge_relationship_type">documents_available_access_to</data><data key="edge_target_entity_id">R118_E017</data><data key="edge_operational_context">POMS lists South Dakota as state providing authorized SSA online WC record access.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0050" source="R118_E017" target="R118_E018"><data key="edge_relationship_id">R118_REL0050</data><data key="edge_source_entity_id">R118_E017</data><data key="edge_relationship_type">supplies_potential_leads_to</data><data key="edge_target_entity_id">R118_E018</data><data key="edge_operational_context">State online records can provide employer/carrier/attorney contact data, with further development sometimes required.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0051" source="R118_E019" target="DATA_DOWR"><data key="edge_relationship_id">R118_REL0051</data><data key="edge_source_entity_id">R118_E019</data><data key="edge_relationship_type">uses_reporting_month_convention_from</data><data key="edge_target_entity_id">DATA_DOWR</data><data key="edge_operational_context">The CSV uses DOWR administrative workload month, which does not match calendar months exactly.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0052" source="R118_E020" target="R118_E019"><data key="edge_relationship_id">R118_REL0052</data><data key="edge_source_entity_id">R118_E020</data><data key="edge_relationship_type">is_companion_to</data><data key="edge_target_entity_id">R118_E019</data><data key="edge_operational_context">Open Data publishes an explicit FY2016 53rd-week file as companion to monthly processing-time series.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0053" source="DATA_OACT_WORKERS_BEN_TABLE" target="DATA_OACT_TR2026_SINGLE_YEAR"><data key="edge_relationship_id">R118_REL0053</data><data key="edge_source_entity_id">DATA_OACT_WORKERS_BEN_TABLE</data><data key="edge_relationship_type">is_published_in_2026_actuarial_single_year_collection</data><data key="edge_target_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_operational_context">Table IV.B4 publishes 1945–2100 covered-worker and OASDI-beneficiary series with implied ratios; not an internal production interface.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R118_REL0054" source="R118_E021" target="DATA_OACT_TR2026_SINGLE_YEAR"><data key="edge_relationship_id">R118_REL0054</data><data key="edge_source_entity_id">R118_E021</data><data key="edge_relationship_type">belongs_to</data><data key="edge_target_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_operational_context">Published as part of 2026 OASDI Trustees Report single-year tables.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0055" source="ORG_SSA_OAG" target="R118_E022"><data key="edge_relationship_id">R118_REL0055</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">implements</data><data key="edge_target_entity_id">R118_E022</data><data key="edge_operational_context">OAG directs contracting staff to insert Acquisition 360 survey clause on specified awards; responses are anonymous.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0056" source="R118_E022" target="ORG_SSA_OITA"><data key="edge_relationship_id">R118_REL0056</data><data key="edge_source_entity_id">R118_E022</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">ORG_SSA_OITA</data><data key="edge_operational_context">Mandatory provision applies to IT awards over simplified acquisition threshold; not evidence of deployed IT.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0057" source="ORG_SSA_OAG" target="ORG_SSA_OITA"><data key="edge_relationship_id">R118_REL0057</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">assigns_information_technology_contracting_to</data><data key="edge_target_entity_id">ORG_SSA_OITA</data><data key="edge_operational_context">OAG current homepage names Office of IT Acquisition as SSA office for IT product and related services procurement.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0058" source="ORG_SSA_OAG" target="ORG_SSA_OOC"><data key="edge_relationship_id">R118_REL0058</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">assigns_non_it_contracting_to</data><data key="edge_target_entity_id">ORG_SSA_OOC</data><data key="edge_operational_context">OAG current homepage names Office of Operations Contracts for facilities and non-IT products and services.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0059" source="FORM_SSA157" target="R118_E023"><data key="edge_relationship_id">R118_REL0059</data><data key="edge_source_entity_id">FORM_SSA157</data><data key="edge_relationship_type">requests_review_under</data><data key="edge_target_entity_id">R118_E023</data><data key="edge_operational_context">Federal agency and private entity requests for SSA exchange require SSA-157 for centralized SSA review.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0060" source="R118_E023" target="ORG_PPDX"><data key="edge_relationship_id">R118_REL0060</data><data key="edge_source_entity_id">R118_E023</data><data key="edge_relationship_type">governs_partner_exchanges_under</data><data key="edge_target_entity_id">ORG_PPDX</data><data key="edge_operational_context">PPDX manages data exchange agreement process with agency business sponsors; only permitted data and legal use covered.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R118_REL0061" source="R118_E025" target="R118_E024"><data key="edge_relationship_id">R118_REL0061</data><data key="edge_source_entity_id">R118_E025</data><data key="edge_relationship_type">may_use_online_state_vital_records_verification</data><data key="edge_target_entity_id">R118_E024</data><data key="edge_operational_context">SSA benefit application guidance documents optional online BVS verification by field offices, but does not name a persistent SSA system or data feed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0001" source="PROC_AWR" target="R121_E001"><data key="edge_relationship_id">R121_REL0001</data><data key="edge_source_entity_id">PROC_AWR</data><data key="edge_relationship_type">identifies_in_validation</data><data key="edge_target_entity_id">R121_E001</data><data key="edge_operational_context">AWR checks death history by SSN when validating earnings.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0002" source="SYS_NUMIDENT" target="R121_E004"><data key="edge_relationship_id">R121_REL0002</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">provides_death_year</data><data key="edge_target_entity_id">R121_E004</data><data key="edge_operational_context">Numident death-year information is used as a verification key; accuracy must be examined.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0003" source="R121_E004" target="R121_E001"><data key="edge_relationship_id">R121_REL0003</data><data key="edge_source_entity_id">R121_E004</data><data key="edge_relationship_type">compared_with_reported_tax_year</data><data key="edge_target_entity_id">R121_E001</data><data key="edge_operational_context">EAD triggers when death year precedes reported earnings year.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0004" source="R121_E001" target="R121_E002"><data key="edge_relationship_id">R121_REL0004</data><data key="edge_source_entity_id">R121_E001</data><data key="edge_relationship_type">assigns_conditionally</data><data key="edge_target_entity_id">R121_E002</data><data key="edge_operational_context">TY 1991 and later disputed EAD reports use EADR suspense reason.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0005" source="R121_E002" target="DB_ESF"><data key="edge_relationship_id">R121_REL0005</data><data key="edge_source_entity_id">R121_E002</data><data key="edge_relationship_type">stored_as_code_in</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">EADR-tagged earnings are held in Earnings Suspense File pending correction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0006" source="R121_E001" target="R121_E003"><data key="edge_relationship_id">R121_REL0006</data><data key="edge_source_entity_id">R121_E001</data><data key="edge_relationship_type">generates_investigation_file</data><data key="edge_target_entity_id">R121_E003</data><data key="edge_operational_context">Office of Systems generates EAD Investigate File for WBDOC.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0007" source="R121_E003" target="ORG_WBDOC"><data key="edge_relationship_id">R121_REL0007</data><data key="edge_source_entity_id">R121_E003</data><data key="edge_relationship_type">routed_to</data><data key="edge_target_entity_id">ORG_WBDOC</data><data key="edge_operational_context">WBDOC receives investigate file and requests employer/worker evidence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0008" source="R121_E001" target="SYS_MEF"><data key="edge_relationship_id">R121_REL0008</data><data key="edge_source_entity_id">R121_E001</data><data key="edge_relationship_type">historical_pre_1991_processing</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">TY 1988-90 wages offset or self-employment tagged; historical processing, not current rule for modern tax years.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0009" source="R121_E003" target="R121_E005"><data key="edge_relationship_id">R121_REL0009</data><data key="edge_source_entity_id">R121_E003</data><data key="edge_relationship_type">triggers_employer_contact</data><data key="edge_target_entity_id">R121_E005</data><data key="edge_operational_context">WBDOC may seek employer verification with SSA-L4112C1.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0010" source="R121_E003" target="R121_E006"><data key="edge_relationship_id">R121_REL0010</data><data key="edge_source_entity_id">R121_E003</data><data key="edge_relationship_type">triggers_self_employment_contact</data><data key="edge_target_entity_id">R121_E006</data><data key="edge_operational_context">WBDOC may contact self-employed worker.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0011" source="R121_E005" target="R121_E008"><data key="edge_relationship_id">R121_REL0011</data><data key="edge_source_entity_id">R121_E005</data><data key="edge_relationship_type">returns_employer_evidence</data><data key="edge_target_entity_id">R121_E008</data><data key="edge_operational_context">Employer response is reviewed by WBDOC and some are routed to OCRO.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0012" source="R121_E008" target="SYS_NUMIDENT"><data key="edge_relationship_id">R121_REL0012</data><data key="edge_source_entity_id">R121_E008</data><data key="edge_relationship_type">reconciled_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OCRO obtains Numident when resolving worker identity/death and earnings.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0013" source="R121_E008" target="SYS_MBR"><data key="edge_relationship_id">R121_REL0013</data><data key="edge_source_entity_id">R121_E008</data><data key="edge_relationship_type">reconciled_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Claims cases require verifying Title II payment record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0014" source="R121_E008" target="R121_E007"><data key="edge_relationship_id">R121_REL0014</data><data key="edge_source_entity_id">R121_E008</data><data key="edge_relationship_type">can_trigger</data><data key="edge_target_entity_id">R121_E007</data><data key="edge_operational_context">Inadequate employer response can trigger worker advisory letter.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0015" source="R121_E008" target="ORG_WBDOC"><data key="edge_relationship_id">R121_REL0015</data><data key="edge_source_entity_id">R121_E008</data><data key="edge_relationship_type">handled_initially_by</data><data key="edge_target_entity_id">ORG_WBDOC</data><data key="edge_operational_context">WBDOC conducts first-line contact and triage.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0016" source="R121_E008" target="R121_E009"><data key="edge_relationship_id">R121_REL0016</data><data key="edge_source_entity_id">R121_E008</data><data key="edge_relationship_type">reviewed_for_disposition</data><data key="edge_target_entity_id">R121_E009</data><data key="edge_operational_context">OCRO reviews responses and corrects earnings, death, and SSN attribution conditionally.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0017" source="R121_E009" target="APP_DIPS"><data key="edge_relationship_id">R121_REL0017</data><data key="edge_source_entity_id">R121_E009</data><data key="edge_relationship_type">conditionally_removes_erroneous_death</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">ETC=T record correction via DIPS; some D codes use OCRO request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0018" source="R121_E009" target="R121_E010"><data key="edge_relationship_id">R121_REL0018</data><data key="edge_source_entity_id">R121_E009</data><data key="edge_relationship_type">requests_exception_correction</data><data key="edge_target_entity_id">R121_E010</data><data key="edge_operational_context">Certain ETC=D correction paths use SSA-3278 to OCRO.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0019" source="R121_E009" target="DB_ESF"><data key="edge_relationship_id">R121_REL0019</data><data key="edge_source_entity_id">R121_E009</data><data key="edge_relationship_type">can_release_earnings_from</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">If worker alive and SSN correct, earnings reinstated from Suspense once incorrect death corrected.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0020" source="R121_E009" target="SYS_MEF"><data key="edge_relationship_id">R121_REL0020</data><data key="edge_source_entity_id">R121_E009</data><data key="edge_relationship_type">posts_correct_earnings_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">MEF correction occurs through IC rather than automatic correction with Numident death update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0021" source="R121_E009" target="SYS_MBR"><data key="edge_relationship_id">R121_REL0021</data><data key="edge_source_entity_id">R121_E009</data><data key="edge_relationship_type">requires_separate_title_ii_correction</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Claims cases may need independent MBR erroneous death/termination correction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0022" source="R121_E009" target="R121_E011"><data key="edge_relationship_id">R121_REL0022</data><data key="edge_source_entity_id">R121_E009</data><data key="edge_relationship_type">historical_wage_reinstatement</data><data key="edge_target_entity_id">R121_E011</data><data key="edge_operational_context">Historical TY1988-90 incorrect wage offset corrected through EAWG.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0023" source="R121_E009" target="R121_E012"><data key="edge_relationship_id">R121_REL0023</data><data key="edge_source_entity_id">R121_E009</data><data key="edge_relationship_type">historical_self_employment_reinstatement</data><data key="edge_target_entity_id">R121_E012</data><data key="edge_operational_context">Historical self-employment correction uses EASE.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0024" source="R121_E009" target="SYS_NUMIDENT"><data key="edge_relationship_id">R121_REL0024</data><data key="edge_source_entity_id">R121_E009</data><data key="edge_relationship_type">requires_identity_death_reconciliation</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Correct death indicator before suspensed earnings reinstatement, where supported by evidence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0025" source="R121_E013" target="R121_E014"><data key="edge_relationship_id">R121_REL0025</data><data key="edge_source_entity_id">R121_E013</data><data key="edge_relationship_type">requires_initial_notice</data><data key="edge_target_entity_id">R121_E014</data><data key="edge_operational_context">N20 eligibility evidence request generally allows 30 calendar days.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0026" source="R121_E014" target="APP_ORS"><data key="edge_relationship_id">R121_REL0026</data><data key="edge_source_entity_id">R121_E014</data><data key="edge_relationship_type">archives_correspondence_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">ORS stores SSI evidence request produced by SSTNG or DPS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0027" source="R121_E013" target="R121_E015"><data key="edge_relationship_id">R121_REL0027</data><data key="edge_source_entity_id">R121_E013</data><data key="edge_relationship_type">requires_followup_controls</data><data key="edge_target_entity_id">R121_E015</data><data key="edge_operational_context">Written followup includes SECOND REQUEST and appropriate 10-day minimum.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0028" source="R121_E015" target="APP_SSTNG"><data key="edge_relationship_id">R121_REL0028</data><data key="edge_source_entity_id">R121_E015</data><data key="edge_relationship_type">autolabels_second_request_in</data><data key="edge_target_entity_id">APP_SSTNG</data><data key="edge_operational_context">SSTNG follows up and auto-includes second-request labeling.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0029" source="R121_E015" target="APP_DPS"><data key="edge_relationship_id">R121_REL0029</data><data key="edge_source_entity_id">R121_E015</data><data key="edge_relationship_type">autolabels_second_request_in</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">DPS also inserts SECOND REQUEST automatically.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0030" source="R121_E013" target="R121_E016"><data key="edge_relationship_id">R121_REL0030</data><data key="edge_source_entity_id">R121_E013</data><data key="edge_relationship_type">requires_management_approval</data><data key="edge_target_entity_id">R121_E016</data><data key="edge_operational_context">Management support specialist or higher approval documents reason/date and payment month.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0031" source="R121_E016" target="R121_E017"><data key="edge_relationship_id">R121_REL0031</data><data key="edge_source_entity_id">R121_E016</data><data key="edge_relationship_type">authorizes</data><data key="edge_target_entity_id">R121_E017</data><data key="edge_operational_context">Suspension input only after approval and due-process rules.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0032" source="R121_E017" target="APP_CCE"><data key="edge_relationship_id">R121_REL0032</data><data key="edge_source_entity_id">R121_E017</data><data key="edge_relationship_type">recorded_on_payment_status_page</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">CCE Payment Status page supports N20 input where applicable.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0033" source="R121_E017" target="SYS_SSR"><data key="edge_relationship_id">R121_REL0033</data><data key="edge_source_entity_id">R121_E017</data><data key="edge_relationship_type">effects_ssi_payment_status</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">N20 is SSI payment suspension code, not Title II undeliverable mail code.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0034" source="R121_E019" target="PROC_T16_UNDELIV_ADDRESS"><data key="edge_relationship_id">R121_REL0034</data><data key="edge_source_entity_id">R121_E019</data><data key="edge_relationship_type">limits_suspension_before_location_search</data><data key="edge_target_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_operational_context">FO must attempt to locate claimant or payee before applicable whereabouts action.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0035" source="R121_E019" target="R121_E013"><data key="edge_relationship_id">R121_REL0035</data><data key="edge_source_entity_id">R121_E019</data><data key="edge_relationship_type">prevents_inappropriate_status_use</data><data key="edge_target_entity_id">R121_E013</data><data key="edge_operational_context">Undeliverable mail alone should not trigger N20 or N18 for unlocated recipient or payee.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0036" source="R121_E019" target="PROC_SSI_WU_S06"><data key="edge_relationship_id">R121_REL0036</data><data key="edge_source_entity_id">R121_E019</data><data key="edge_relationship_type">may_trigger_whereabouts_s06</data><data key="edge_target_entity_id">PROC_SSI_WU_S06</data><data key="edge_operational_context">Unlocated post-eligibility SSI recipient may trigger S06, with separate safeguards.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0037" source="R121_E018" target="PROC_T16_UNDELIV_ADDRESS"><data key="edge_relationship_id">R121_REL0037</data><data key="edge_source_entity_id">R121_E018</data><data key="edge_relationship_type">used_when_remailing_appeal_notice</data><data key="edge_target_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_operational_context">Appeal-rights notice remailed under cover letter once located.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0038" source="R121_E020" target="PROC_T16_UNDELIV_ADDRESS"><data key="edge_relationship_id">R121_REL0038</data><data key="edge_source_entity_id">R121_E020</data><data key="edge_relationship_type">reissues_request_after_address_development</data><data key="edge_target_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_operational_context">Time-sensitive SSI request requires current date and content updates.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0039" source="R121_E020" target="SYS_SSR"><data key="edge_relationship_id">R121_REL0039</data><data key="edge_source_entity_id">R121_E020</data><data key="edge_relationship_type">may_require_manual_address_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Address changes require SSI system input and living-arrangement development where appropriate.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0040" source="PROC_T2_UNDELIV_ADDRESS" target="R121_E021"><data key="edge_relationship_id">R121_REL0040</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">may_reach_after_continuous_suspense</data><data key="edge_target_entity_id">R121_E021</data><data key="edge_operational_context">At least 7 years of continuous unsuccessful-contact suspension triggers special presumed death rule for defined Title II cases.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0041" source="R121_E021" target="SYS_MBR"><data key="edge_relationship_id">R121_REL0041</data><data key="edge_source_entity_id">R121_E021</data><data key="edge_relationship_type">may_terminate_entitlement_via</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Presumption supports entitlement termination with documented suspension date unless evidence rebuts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0042" source="PROC_T2_UNDELIV_ADDRESS" target="R121_E022"><data key="edge_relationship_id">R121_REL0042</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">documents_location_attempts_in</data><data key="edge_target_entity_id">R121_E022</data><data key="edge_operational_context">MBR SMS records attempts, FI and USPS contacts and outcome.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0043" source="R121_E022" target="SYS_MBR"><data key="edge_relationship_id">R121_REL0043</data><data key="edge_source_entity_id">R121_E022</data><data key="edge_relationship_type">persists_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Prior MBR special messages retained when later address correction/reinstatement occurs.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0044" source="R121_E023" target="SYS_MBR"><data key="edge_relationship_id">R121_REL0044</data><data key="edge_source_entity_id">R121_E023</data><data key="edge_relationship_type">checks_current_contact</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">FO queries MBR for beneficiary telephone and address.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0045" source="R121_E023" target="SYS_SSR"><data key="edge_relationship_id">R121_REL0045</data><data key="edge_source_entity_id">R121_E023</data><data key="edge_relationship_type">checks_current_contact</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">FO checks SSI records and other FO information for locate leads.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0046" source="R121_E023" target="FORM_SSA_L2001"><data key="edge_relationship_id">R121_REL0046</data><data key="edge_source_entity_id">R121_E023</data><data key="edge_relationship_type">may_request_address_from_postal_service</data><data key="edge_target_entity_id">FORM_SSA_L2001</data><data key="edge_operational_context">Form SSA-L2001 submitted except where USPS already reported undeliverable/no forwarding.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0047" source="R121_E023" target="PROC_SSI_WU_S06"><data key="edge_relationship_id">R121_REL0047</data><data key="edge_source_entity_id">R121_E023</data><data key="edge_relationship_type">must_distinguish_ssi_rules</data><data key="edge_target_entity_id">PROC_SSI_WU_S06</data><data key="edge_operational_context">SSI whereabout suspension logic separately controlled from Title II CDR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0048" source="R121_E024" target="APP_DPS"><data key="edge_relationship_id">R121_REL0048</data><data key="edge_source_entity_id">R121_E024</data><data key="edge_relationship_type">available_in</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">SNO mail cover letter under DPS Cover Letters folder.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0049" source="R121_E024" target="PROC_SNO"><data key="edge_relationship_id">R121_REL0049</data><data key="edge_source_entity_id">R121_E024</data><data key="edge_relationship_type">enforces_accessibility_in_returns</data><data key="edge_target_entity_id">PROC_SNO</data><data key="edge_operational_context">Accessible formats require SNO-specific cover letter.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0050" source="R121_E025" target="PROC_SNO"><data key="edge_relationship_id">R121_REL0050</data><data key="edge_source_entity_id">R121_E025</data><data key="edge_relationship_type">specifies_disposal_after_failure</data><data key="edge_target_entity_id">PROC_SNO</data><data key="edge_operational_context">If no remail required, special-media item shredded.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0051" source="R121_E026" target="APP_TDCP"><data key="edge_relationship_id">R121_REL0051</data><data key="edge_source_entity_id">R121_E026</data><data key="edge_relationship_type">completed_via</data><data key="edge_target_entity_id">APP_TDCP</data><data key="edge_operational_context">Form SSA e2960 USA/RO 3 completed in Totalization Data Collection Program.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0052" source="R121_E026" target="EX_US_ROMANIA_TOTALIZATION"><data key="edge_relationship_id">R121_REL0052</data><data key="edge_source_entity_id">R121_E026</data><data key="edge_relationship_type">implements_liaison_exchange</data><data key="edge_target_entity_id">EX_US_ROMANIA_TOTALIZATION</data><data key="edge_operational_context">Transmits claims and related information to Romanian liaison.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0053" source="R121_E026" target="R121_E027"><data key="edge_relationship_id">R121_REL0053</data><data key="edge_source_entity_id">R121_E026</data><data key="edge_relationship_type">captures_claimant_contact</data><data key="edge_target_entity_id">R121_E027</data><data key="edge_operational_context">Full claimant address and telephone used for international claims correspondence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0054" source="R121_E026" target="R121_E028"><data key="edge_relationship_id">R121_REL0054</data><data key="edge_source_entity_id">R121_E026</data><data key="edge_relationship_type">captures_external_person_identifier</data><data key="edge_target_entity_id">R121_E028</data><data key="edge_operational_context">Romanian registration identifier or fallback name DOB place of birth.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0055" source="R121_E026" target="R121_E029"><data key="edge_relationship_id">R121_REL0055</data><data key="edge_source_entity_id">R121_E026</data><data key="edge_relationship_type">validates_certified_identifiers</data><data key="edge_target_entity_id">R121_E029</data><data key="edge_operational_context">Certification refers to records with proof code; unavailable facts marked unknown.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0056" source="R121_E029" target="SYS_NUMIDENT"><data key="edge_relationship_id">R121_REL0056</data><data key="edge_source_entity_id">R121_E029</data><data key="edge_relationship_type">consults_identity_proofs</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Proof of DOB/death/country citizenship may be established by Numident.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0057" source="R121_E029" target="SYS_MBR"><data key="edge_relationship_id">R121_REL0057</data><data key="edge_source_entity_id">R121_E029</data><data key="edge_relationship_type">consults_award_proofs</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR verifies past adjudicated facts where accepted.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0058" source="R121_E026" target="R121_E030"><data key="edge_relationship_id">R121_REL0058</data><data key="edge_source_entity_id">R121_E026</data><data key="edge_relationship_type">transmits_or_requests</data><data key="edge_target_entity_id">R121_E030</data><data key="edge_operational_context">May transmit U.S. earnings, medical evidence and requests to Romanian liaison.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0059" source="R121_E030" target="ORG_ROMANIA_NHPP"><data key="edge_relationship_id">R121_REL0059</data><data key="edge_source_entity_id">R121_E030</data><data key="edge_relationship_type">shared_with</data><data key="edge_target_entity_id">ORG_ROMANIA_NHPP</data><data key="edge_operational_context">Specific Romanian liaison is the National House of Public Pensions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0060" source="R121_E031" target="R121_E032"><data key="edge_relationship_id">R121_REL0060</data><data key="edge_source_entity_id">R121_E031</data><data key="edge_relationship_type">authorized_by</data><data key="edge_target_entity_id">R121_E032</data><data key="edge_operational_context">Temporary agreement identifies work and period.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0061" source="R121_E031" target="R121_E033"><data key="edge_relationship_id">R121_REL0061</data><data key="edge_source_entity_id">R121_E031</data><data key="edge_relationship_type">flags_paper_case</data><data key="edge_target_entity_id">R121_E033</data><data key="edge_operational_context">Paper folder SSA-831 remark identifies emergency clause DDS origin.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0062" source="R121_E031" target="APP_EDCS"><data key="edge_relationship_id">R121_REL0062</data><data key="edge_source_entity_id">R121_E031</data><data key="edge_relationship_type">transfers_electronic_case_via</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Electronic emergency-case folder transferred through EDCS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0063" source="R121_E031" target="APP_MIDAS"><data key="edge_relationship_id">R121_REL0063</data><data key="edge_source_entity_id">R121_E031</data><data key="edge_relationship_type">receipted_by</data><data key="edge_target_entity_id">APP_MIDAS</data><data key="edge_operational_context">DCR/FDU receives transferred case in MIDAS legacy application.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0064" source="R121_E031" target="ORG_DCR"><data key="edge_relationship_id">R121_REL0064</data><data key="edge_source_entity_id">R121_E031</data><data key="edge_relationship_type">temporary_routes_to</data><data key="edge_target_entity_id">ORG_DCR</data><data key="edge_operational_context">DCR can accept specified claims, recon and CDR work through agreement.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0065" source="R121_E034" target="R121_E036"><data key="edge_relationship_id">R121_REL0065</data><data key="edge_source_entity_id">R121_E034</data><data key="edge_relationship_type">overrides</data><data key="edge_target_entity_id">R121_E036</data><data key="edge_operational_context">Foreign mailing address takes precedence over V32 railroad referral.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0066" source="R121_E036" target="ORG_DCR"><data key="edge_relationship_id">R121_REL0066</data><data key="edge_source_entity_id">R121_E036</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">ORG_DCR</data><data key="edge_operational_context">Qualified career railroad or specified survivor claims sent to DCR location V32.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0067" source="R121_E035" target="APP_MCS"><data key="edge_relationship_id">R121_REL0067</data><data key="edge_source_entity_id">R121_E035</data><data key="edge_relationship_type">uses_claims_earnings_context</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">FO can use MCS earnings computations to identify RR survivor jurisdiction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0068" source="R121_E035" target="R121_E036"><data key="edge_relationship_id">R121_REL0068</data><data key="edge_source_entity_id">R121_E035</data><data key="edge_relationship_type">informs_jurisdiction</data><data key="edge_target_entity_id">R121_E036</data><data key="edge_operational_context">DRAMS result determines routing of RR survivor case.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0069" source="R121_E037" target="APP_MCS"><data key="edge_relationship_id">R121_REL0069</data><data key="edge_source_entity_id">R121_E037</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS Earnings Computation DRRE screen lists railroad service months.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0070" source="R121_E037" target="R121_E036"><data key="edge_relationship_id">R121_REL0070</data><data key="edge_source_entity_id">R121_E037</data><data key="edge_relationship_type">determines_career_railroad_criteria</data><data key="edge_target_entity_id">R121_E036</data><data key="edge_operational_context">60 months post-1995 or 120 months any time, with applicable military credit considerations.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0071" source="R121_E039" target="APP_ISNO"><data key="edge_relationship_id">R121_REL0071</data><data key="edge_source_entity_id">R121_E039</data><data key="edge_relationship_type">controls_request_authentication</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">Identity edit messages arise from input compared to Numident, MBR and SSR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0072" source="R121_E039" target="SYS_MBR"><data key="edge_relationship_id">R121_REL0072</data><data key="edge_source_entity_id">R121_E039</data><data key="edge_relationship_type">checks_program_identity_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR is among systems checked, not a single enterprise person record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0073" source="R121_E039" target="SYS_SSR"><data key="edge_relationship_id">R121_REL0073</data><data key="edge_source_entity_id">R121_E039</data><data key="edge_relationship_type">checks_program_identity_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR is among systems checked.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0074" source="R121_E039" target="SYS_NUMIDENT"><data key="edge_relationship_id">R121_REL0074</data><data key="edge_source_entity_id">R121_E039</data><data key="edge_relationship_type">checks_enumeration_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Numident is among systems checked.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0075" source="R121_E038" target="APP_ISNO"><data key="edge_relationship_id">R121_REL0075</data><data key="edge_source_entity_id">R121_E038</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">Phone for 5-business-day follow-up in accessible notice preference.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0076" source="R121_E038" target="PROC_SNO"><data key="edge_relationship_id">R121_REL0076</data><data key="edge_source_entity_id">R121_E038</data><data key="edge_relationship_type">supports_accommodation_delivery</data><data key="edge_target_entity_id">PROC_SNO</data><data key="edge_operational_context">Call back follows mailed notices for selected SNO format.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0077" source="R121_E041" target="R121_E040"><data key="edge_relationship_id">R121_REL0077</data><data key="edge_source_entity_id">R121_E041</data><data key="edge_relationship_type">checks_incentive_payee_contact</data><data key="edge_target_entity_id">R121_E040</data><data key="edge_operational_context">Returned notice compared with QPID incentive payee address and updated facility contact.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0078" source="R121_E040" target="DATA_PUPS_INCENTIVE_PAYEE_ADDRESS"><data key="edge_relationship_id">R121_REL0078</data><data key="edge_source_entity_id">R121_E040</data><data key="edge_relationship_type">exposes_institutional_address</data><data key="edge_target_entity_id">DATA_PUPS_INCENTIVE_PAYEE_ADDRESS</data><data key="edge_operational_context">IRCS payee address belongs to confinement institution or mental health institution, not beneficiary mailing address.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0079" source="R121_E041" target="FORM_SSA_L4020"><data key="edge_relationship_id">R121_REL0079</data><data key="edge_source_entity_id">R121_E041</data><data key="edge_relationship_type">remails</data><data key="edge_target_entity_id">FORM_SSA_L4020</data><data key="edge_operational_context">Incentive payment recoupment notice is re-mailed to verified facility.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0080" source="R121_E041" target="ORG_USPS"><data key="edge_relationship_id">R121_REL0080</data><data key="edge_source_entity_id">R121_E041</data><data key="edge_relationship_type">can_use_returned_forwarding_address</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">Forwarding address on undeliverable SSA-L4020 is only a lead; verify with institution.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0081" source="R121_E042" target="PROC_SSI_ABLE_REPORTING"><data key="edge_relationship_id">R121_REL0081</data><data key="edge_source_entity_id">R121_E042</data><data key="edge_relationship_type">changes_eligibility_development</data><data key="edge_target_entity_id">PROC_SSI_ABLE_REPORTING</data><data key="edge_operational_context">SSI ABLE account reporting and evaluation must follow expanded 2026 eligibility criteria.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0082" source="R121_E042" target="DATA_SSI_ABLE_ACCOUNT"><data key="edge_relationship_id">R121_REL0082</data><data key="edge_source_entity_id">R121_E042</data><data key="edge_relationship_type">governs_countable_account_qualification</data><data key="edge_target_entity_id">DATA_SSI_ABLE_ACCOUNT</data><data key="edge_operational_context">ABLE owner eligibility relies on documented onset threshold, not an assumed automated external IRS data feed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0083" source="R121_E043" target="APP_DMS"><data key="edge_relationship_id">R121_REL0083</data><data key="edge_source_entity_id">R121_E043</data><data key="edge_relationship_type">documents_failed_locator_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Title II unsuccessful address contact recorded in DMS RMKS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0084" source="R121_E043" target="APP_DPS"><data key="edge_relationship_id">R121_REL0084</data><data key="edge_source_entity_id">R121_E043</data><data key="edge_relationship_type">generates_conference_notice_in</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Personal Conference &amp; Folder Review notice available in DPS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R121_REL0085" source="R121_E043" target="PROC_T16_UNDELIV_ADDRESS"><data key="edge_relationship_id">R121_REL0085</data><data key="edge_source_entity_id">R121_E043</data><data key="edge_relationship_type">uses_title_xvi_due_process_locator</data><data key="edge_target_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_operational_context">SSI undeliverable waiver notices use Title XVI whereabouts/notice policy.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0001" source="APP_SSI_IRS_P1099_INTERFACE" target="R122_E001"><data key="edge_relationship_id">R122_REL0001</data><data key="edge_source_entity_id">APP_SSI_IRS_P1099_INTERFACE</data><data key="edge_relationship_type">classifies_tax_transactions_as</data><data key="edge_target_entity_id">R122_E001</data><data key="edge_operational_context">Form 1099 and similar reports are classified into resource or income-and-resource indicators for development, not direct proof of beneficiary address.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0002" source="APP_SSI_IRS_P1099_INTERFACE" target="R122_E002"><data key="edge_relationship_id">R122_REL0002</data><data key="edge_source_entity_id">APP_SSI_IRS_P1099_INTERFACE</data><data key="edge_relationship_type">classifies_tax_transactions_as</data><data key="edge_target_entity_id">R122_E002</data><data key="edge_operational_context">Separate income-only indicators require income verification/development.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0003" source="R122_E003" target="SYS_SSR"><data key="edge_relationship_id">R122_REL0003</data><data key="edge_source_entity_id">R122_E003</data><data key="edge_relationship_type">controls_5b_diary_creation_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The SSI system places controlled 5B diaries on SSR when 2017 thresholds and selection rules are met.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0004" source="R122_E003" target="R122_E001"><data key="edge_relationship_id">R122_REL0004</data><data key="edge_source_entity_id">R122_E003</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R122_E001</data><data key="edge_operational_context">Individual and couple resource thresholds differ under the 2017 POMS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0005" source="R122_E003" target="R122_E002"><data key="edge_relationship_id">R122_REL0005</data><data key="edge_source_entity_id">R122_E003</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R122_E002</data><data key="edge_operational_context">Income-only indicator threshold is $1,001 under 2017 POMS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0006" source="R122_E004" target="R122_E003"><data key="edge_relationship_id">R122_REL0006</data><data key="edge_source_entity_id">R122_E004</data><data key="edge_relationship_type">modifies</data><data key="edge_target_entity_id">R122_E003</data><data key="edge_operational_context">2017 POMS specifies narrowly defined prior-year suppression exceptions; no permanent suppression can be inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0007" source="R122_E005" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R122_REL0007</data><data key="edge_source_entity_id">R122_E005</data><data key="edge_relationship_type">routes_alerts_to</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">2017 POMS lists overnight RZ/LI listing retrieval by HUN in MI Central.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0008" source="R122_E005" target="APP_SSTNG"><data key="edge_relationship_id">R122_REL0008</data><data key="edge_source_entity_id">R122_E005</data><data key="edge_relationship_type">routes_alerts_to</data><data key="edge_target_entity_id">APP_SSTNG</data><data key="edge_operational_context">2017 POMS also lists immediate retrieval of the same data in SSTNG.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0009" source="R122_E001" target="SYS_SSR"><data key="edge_relationship_id">R122_REL0009</data><data key="edge_source_entity_id">R122_E001</data><data key="edge_relationship_type">is_evidence_for_development_not_automatic_update_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Third-party transaction indicator opens redetermination work; SSA requires development and verification before program record action.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0010" source="APP_IRCS" target="R122_E008"><data key="edge_relationship_id">R122_REL0010</data><data key="edge_source_entity_id">APP_IRCS</data><data key="edge_relationship_type">has_reporter_query</data><data key="edge_target_entity_id">R122_E008</data><data key="edge_operational_context">IRCS QRI2 exposes facility ID numbers assigned to a reporter.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0011" source="R122_E008" target="R122_E007"><data key="edge_relationship_id">R122_REL0011</data><data key="edge_source_entity_id">R122_E008</data><data key="edge_relationship_type">supplies_facility_identifier_for</data><data key="edge_target_entity_id">R122_E007</data><data key="edge_operational_context">Six-digit facility ID locates that institution notice in ORS PRISONERS folder; PUPS record includes the same facility code.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0012" source="APP_PUPS" target="R122_E009"><data key="edge_relationship_id">R122_REL0012</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">provides_incentive_payment_identity_context_for</data><data key="edge_target_entity_id">R122_E009</data><data key="edge_operational_context">PUPS holds the specific prisoner record for which the institutional payment was authorized.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0013" source="R122_E009" target="R122_E007"><data key="edge_relationship_id">R122_REL0013</data><data key="edge_source_entity_id">R122_E009</data><data key="edge_relationship_type">retained_copy_in</data><data key="edge_target_entity_id">R122_E007</data><data key="edge_operational_context">SSA retains a monthly institutional incentive-payment notice copy in ORS PRISONERS folder.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0014" source="APP_IRCS" target="R122_E006"><data key="edge_relationship_id">R122_REL0014</data><data key="edge_source_entity_id">APP_IRCS</data><data key="edge_relationship_type">holds_reporting_authority_for</data><data key="edge_target_entity_id">R122_E006</data><data key="edge_operational_context">IRCS Reporter Identification Data (IRID) identifies the institutional reporter under the signed IPMOU.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0015" source="R122_E006" target="R122_E010"><data key="edge_relationship_id">R122_REL0015</data><data key="edge_source_entity_id">R122_E006</data><data key="edge_relationship_type">controls_authorized_address_changes_by</data><data key="edge_target_entity_id">R122_E010</data><data key="edge_operational_context">Only MOU-signatory correctional or mental-health authority can direct mailing-address updates to an incentive-payment notice.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0016" source="R122_E010" target="DATA_PUPS_INCENTIVE_PAYEE_ADDRESS"><data key="edge_relationship_id">R122_REL0016</data><data key="edge_source_entity_id">R122_E010</data><data key="edge_relationship_type">protects_institutional_contact_address</data><data key="edge_target_entity_id">DATA_PUPS_INCENTIVE_PAYEE_ADDRESS</data><data key="edge_operational_context">Institution notice address comes from authorized agency or institutional reporting source, not an SSI or Title II beneficiary residence update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0017" source="R122_E011" target="APP_PUPS"><data key="edge_relationship_id">R122_REL0017</data><data key="edge_source_entity_id">R122_E011</data><data key="edge_relationship_type">reconciles_with</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">FO checks PUPS prisoner records when investigating identity, confinement date, or incentive discrepancies.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0018" source="R122_E011" target="APP_IRCS"><data key="edge_relationship_id">R122_REL0018</data><data key="edge_source_entity_id">R122_E011</data><data key="edge_relationship_type">reconciles_with</data><data key="edge_target_entity_id">APP_IRCS</data><data key="edge_operational_context">FO checks IRCS for reporting facility and incentive payment information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0019" source="R122_E011" target="R122_E007"><data key="edge_relationship_id">R122_REL0019</data><data key="edge_source_entity_id">R122_E011</data><data key="edge_relationship_type">reviews_notice_in</data><data key="edge_target_entity_id">R122_E007</data><data key="edge_operational_context">Institutional disputes require notice review in ORS against facility ID and reported payment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0020" source="R122_E012" target="SVC_TOP"><data key="edge_relationship_id">R122_REL0020</data><data key="edge_source_entity_id">R122_E012</data><data key="edge_relationship_type">may_result_from</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">Treasury may offset amount deposited to institutional bank account for institutional debt unrelated to prisoner-beneficiary address.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0021" source="R122_E009" target="R122_E010"><data key="edge_relationship_id">R122_REL0021</data><data key="edge_source_entity_id">R122_E009</data><data key="edge_relationship_type">subject_to_institutional_address_rule</data><data key="edge_target_entity_id">R122_E010</data><data key="edge_operational_context">Changes to notice delivery address use IPMOU signatory controls; not automatic from payee or claims master-record updates.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0022" source="R122_E011" target="R122_E010"><data key="edge_relationship_id">R122_REL0022</data><data key="edge_source_entity_id">R122_E011</data><data key="edge_relationship_type">escalates_to</data><data key="edge_target_entity_id">R122_E010</data><data key="edge_operational_context">Institutional mailing/bank account change inquiries are routed through authorized prison coordination staff instead of technician self-service changes.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0023" source="MODEL_OASDI_STOCHASTIC" target="R122_E013"><data key="edge_relationship_id">R122_REL0023</data><data key="edge_source_entity_id">MODEL_OASDI_STOCHASTIC</data><data key="edge_relationship_type">implemented_in_published_run</data><data key="edge_target_entity_id">R122_E013</data><data key="edge_operational_context">2026 Trustees describe 5,000 independent stochastic simulations; the process does not identify a database or executable product.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0024" source="R122_E013" target="R122_E014"><data key="edge_relationship_id">R122_REL0024</data><data key="edge_source_entity_id">R122_E013</data><data key="edge_relationship_type">varies_inputs_from</data><data key="edge_target_entity_id">R122_E014</data><data key="edge_operational_context">2026 Trustees stochastic projection methodology identifies these variables/terms as affecting simulation trajectories.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0025" source="R122_E013" target="R122_E015"><data key="edge_relationship_id">R122_REL0025</data><data key="edge_source_entity_id">R122_E013</data><data key="edge_relationship_type">varies_inputs_from</data><data key="edge_target_entity_id">R122_E015</data><data key="edge_operational_context">2026 Trustees stochastic projection methodology identifies these variables/terms as affecting simulation trajectories.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0026" source="R122_E013" target="R122_E016"><data key="edge_relationship_id">R122_REL0026</data><data key="edge_source_entity_id">R122_E013</data><data key="edge_relationship_type">varies_inputs_from</data><data key="edge_target_entity_id">R122_E016</data><data key="edge_operational_context">2026 Trustees stochastic projection methodology identifies these variables/terms as affecting simulation trajectories.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0027" source="R122_E013" target="R122_E017"><data key="edge_relationship_id">R122_REL0027</data><data key="edge_source_entity_id">R122_E013</data><data key="edge_relationship_type">varies_inputs_from</data><data key="edge_target_entity_id">R122_E017</data><data key="edge_operational_context">2026 Trustees stochastic projection methodology identifies these variables/terms as affecting simulation trajectories.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0028" source="R122_E013" target="R122_E018"><data key="edge_relationship_id">R122_REL0028</data><data key="edge_source_entity_id">R122_E013</data><data key="edge_relationship_type">publishes_results_in</data><data key="edge_target_entity_id">R122_E018</data><data key="edge_operational_context">Stochastic scenario results are rendered in named 2026 Trustees figures/table, not as a documented production database.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0029" source="R122_E013" target="R122_E019"><data key="edge_relationship_id">R122_REL0029</data><data key="edge_source_entity_id">R122_E013</data><data key="edge_relationship_type">publishes_results_in</data><data key="edge_target_entity_id">R122_E019</data><data key="edge_operational_context">Stochastic scenario results are rendered in named 2026 Trustees figures/table, not as a documented production database.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0030" source="R122_E013" target="R122_E020"><data key="edge_relationship_id">R122_REL0030</data><data key="edge_source_entity_id">R122_E013</data><data key="edge_relationship_type">publishes_results_in</data><data key="edge_target_entity_id">R122_E020</data><data key="edge_operational_context">Stochastic scenario results are rendered in named 2026 Trustees figures/table, not as a documented production database.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0031" source="R122_E020" target="MODEL_OASDI_SCENARIO"><data key="edge_relationship_id">R122_REL0031</data><data key="edge_source_entity_id">R122_E020</data><data key="edge_relationship_type">compares_with</data><data key="edge_target_entity_id">MODEL_OASDI_SCENARIO</data><data key="edge_operational_context">Appendix Table VI.E1 compares stochastic simulations with low-cost, intermediate, and high-cost alternative scenario results.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0032" source="R122_E021" target="R122_E013"><data key="edge_relationship_id">R122_REL0032</data><data key="edge_source_entity_id">R122_E021</data><data key="edge_relationship_type">qualifies_uncertainty_coverage_of</data><data key="edge_target_entity_id">R122_E013</data><data key="edge_operational_context">The published model excludes random variation for additional demographic and labor-force variables; reported range is not exhaustive uncertainty.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0033" source="APP_ALJ_MISCONDUCT" target="R122_E022"><data key="edge_relationship_id">R122_REL0033</data><data key="edge_source_entity_id">APP_ALJ_MISCONDUCT</data><data key="edge_relationship_type">holds_case_specific_identity_attributes</data><data key="edge_target_entity_id">R122_E022</data><data key="edge_operational_context">ALJ complaint identity and contact fields are retained in complaint system for complaint purposes, not authoritative identity or address update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0034" source="APP_ALJ_MISCONDUCT" target="R122_E023"><data key="edge_relationship_id">R122_REL0034</data><data key="edge_source_entity_id">APP_ALJ_MISCONDUCT</data><data key="edge_relationship_type">uses_judge_tracking_identifiers</data><data key="edge_target_entity_id">R122_E023</data><data key="edge_operational_context">ALJ identifier and control-log numbers support complaint investigation and handling.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0035" source="APP_ALJ_MISCONDUCT" target="R122_E024"><data key="edge_relationship_id">R122_REL0035</data><data key="edge_source_entity_id">APP_ALJ_MISCONDUCT</data><data key="edge_relationship_type">supports_investigative_pattern_detection</data><data key="edge_target_entity_id">R122_E024</data><data key="edge_operational_context">Complaint system aggregates and reviews allegations/outcomes to detect patterns requiring further action.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0036" source="R122_E022" target="DATA_ALJ_PAMC_ADDRESS"><data key="edge_relationship_id">R122_REL0036</data><data key="edge_source_entity_id">R122_E022</data><data key="edge_relationship_type">includes_separately_typed_address</data><data key="edge_target_entity_id">DATA_ALJ_PAMC_ADDRESS</data><data key="edge_operational_context">Complaints may include claimant address as filed; its presence is not evidence of MBR, SSR, or Numident address change.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0037" source="APP_ALJ_MISCONDUCT" target="R122_E025"><data key="edge_relationship_id">R122_REL0037</data><data key="edge_source_entity_id">APP_ALJ_MISCONDUCT</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R122_E025</data><data key="edge_operational_context">PIA explicitly qualifies prohibited disclosure of Federal return information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0038" source="APP_FAS" target="R122_E026"><data key="edge_relationship_id">R122_REL0038</data><data key="edge_source_entity_id">APP_FAS</data><data key="edge_relationship_type">supplies_study_specific_identity_contact_extract</data><data key="edge_target_entity_id">R122_E026</data><data key="edge_operational_context">Research-specific identity and address extract transmitted through NIH and Boston University to Westat for claimant recruitment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0039" source="R122_E026" target="ORG_WESTAT"><data key="edge_relationship_id">R122_REL0039</data><data key="edge_source_entity_id">R122_E026</data><data key="edge_relationship_type">shared_for_study_contact_with</data><data key="edge_target_entity_id">ORG_WESTAT</data><data key="edge_operational_context">Westat uses participant-specific contact addresses only for study eligibility and recruitment mailings.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0040" source="APP_FAS_QDS" target="R122_E028"><data key="edge_relationship_id">R122_REL0040</data><data key="edge_source_entity_id">APP_FAS_QDS</data><data key="edge_relationship_type">elicits_functional_responses_using</data><data key="edge_target_entity_id">R122_E028</data><data key="edge_operational_context">Westat QDS delivers adaptive functional questionnaires via web or telephone interview during calibration study.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0041" source="ORG_WESTAT" target="R122_E027"><data key="edge_relationship_id">R122_REL0041</data><data key="edge_source_entity_id">ORG_WESTAT</data><data key="edge_relationship_type">collects_provider_contacts_for</data><data key="edge_target_entity_id">R122_E027</data><data key="edge_operational_context">Provider addresses and phone numbers are provided by claimants to support recruitment; not SSA-verified residence records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0042" source="ORG_WESTAT" target="R122_E029"><data key="edge_relationship_id">R122_REL0042</data><data key="edge_source_entity_id">ORG_WESTAT</data><data key="edge_relationship_type">shares_non_identifiable_results_as</data><data key="edge_target_entity_id">R122_E029</data><data key="edge_operational_context">Westat shares non-identifiable functional research data with BU-HDRI, rather than an unrestricted claimant PII copy.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0043" source="R122_E029" target="ORG_BU_HDRI"><data key="edge_relationship_id">R122_REL0043</data><data key="edge_source_entity_id">R122_E029</data><data key="edge_relationship_type">analyzed_by</data><data key="edge_target_entity_id">ORG_BU_HDRI</data><data key="edge_operational_context">Boston University analyzes de-identified results to finalize CAT question banks and report findings.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0044" source="R122_E028" target="R122_E029"><data key="edge_relationship_id">R122_REL0044</data><data key="edge_source_entity_id">R122_E028</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">R122_E029</data><data key="edge_operational_context">Functional question banks derive from responses analyzed within the research study.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0045" source="APP_800_EMPVER" target="R122_E030"><data key="edge_relationship_id">R122_REL0045</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">verifies_employer_identifier_via</data><data key="edge_target_entity_id">R122_E030</data><data key="edge_operational_context">Telephone SSN verification checks caller-authorized EIN against SSA earnings records, in addition to SSN-holder record verification.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0046" source="APP_800_EMPVER" target="R122_E031"><data key="edge_relationship_id">R122_REL0046</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">enforces_transient_retention_rule</data><data key="edge_target_entity_id">R122_E031</data><data key="edge_operational_context">Plausible long-lived recordings or person attributes in TNEV must not be inferred from spoken data collection.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0047" source="R122_E031" target="DATA_TNEV_TRANSIENT_INPUT"><data key="edge_relationship_id">R122_REL0047</data><data key="edge_source_entity_id">R122_E031</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DATA_TNEV_TRANSIENT_INPUT</data><data key="edge_operational_context">All data collected/transmitted for TNEV are dropped when call ends, according to 2025 PIA.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0048" source="DATA_DMF" target="R122_E032"><data key="edge_relationship_id">R122_REL0048</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">has_restricted_disclosure_product</data><data key="edge_target_entity_id">R122_E032</data><data key="edge_operational_context">State-sourced deaths are included in full file; section 205(r) restricts eligible government recipients.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0049" source="DATA_DMF" target="R122_E033"><data key="edge_relationship_id">R122_REL0049</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">has_public_disclosure_product</data><data key="edge_target_entity_id">R122_E033</data><data key="edge_operational_context">Public version deliberately omits state-sourced death information, which remains legally restricted.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0050" source="R122_E033" target="ORG_NTIS"><data key="edge_relationship_id">R122_REL0050</data><data key="edge_source_entity_id">R122_E033</data><data key="edge_relationship_type">distributed_through</data><data key="edge_target_entity_id">ORG_NTIS</data><data key="edge_operational_context">SSA supplies public/Limited Access DMF to NTIS for downstream access.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0051" source="R122_E032" target="FORM_SSA157"><data key="edge_relationship_id">R122_REL0051</data><data key="edge_source_entity_id">R122_E032</data><data key="edge_relationship_type">requested_using</data><data key="edge_target_entity_id">FORM_SSA157</data><data key="edge_operational_context">Authorized public benefit-paying agencies or states use the prescribed SSA data-exchange process; form SSA-157 is named for eligible Federal requests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0052" source="R122_E034" target="SYS_NUMIDENT"><data key="edge_relationship_id">R122_REL0052</data><data key="edge_source_entity_id">R122_E034</data><data key="edge_relationship_type">reviews_correction_quality_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG audited incorrect deaths recorded and later removed from Numident for beneficiaries, with inconsistent explanatory documentation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R122_REL0053" source="R122_E034" target="DATA_DMF"><data key="edge_relationship_id">R122_REL0053</data><data key="edge_source_entity_id">R122_E034</data><data key="edge_relationship_type">governs_quality_risk_in</data><data key="edge_target_entity_id">DATA_DMF</data><data key="edge_operational_context">Numident correction controls affect derived Death Master File information and downstream disclosure risks.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R123_REL001" source="APP_MYCOA" target="R123_E001"><data key="edge_relationship_id">R123_REL001</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">sends_submitted_title_ii_address_change_to</data><data key="edge_target_entity_id">R123_E001</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Source explicitly names an intermediate database but does not identify its product, persistence, or physical hosting.</data></edge><edge id="R123_REL002" source="R123_E001" target="SYS_MBR"><data key="edge_relationship_id">R123_REL002</data><data key="edge_source_entity_id">R123_E001</data><data key="edge_relationship_type">supports_documented_downstream_update_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">SSA states that internet change-of-address data is updated to MBR; the specific implementation mechanics and posting frequency are not given by this source.</data></edge><edge id="R123_REL003" source="APP_MYCOA" target="R123_E002"><data key="edge_relationship_id">R123_REL003</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">enforces_documented_geographic_eligibility</data><data key="edge_target_entity_id">R123_E002</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">User must reside in, and move to, an eligible US state, DC, or named territory.</data></edge><edge id="R123_REL004" source="APP_MYCOA" target="R123_E003"><data key="edge_relationship_id">R123_REL004</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">restricts_address_input_to</data><data key="edge_target_entity_id">R123_E003</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">SSA describes beneficiary self-submission; no biometric or vendor inference.</data></edge><edge id="R123_REL005" source="R123_E004" target="APP_MYCOA"><data key="edge_relationship_id">R123_REL005</data><data key="edge_source_entity_id">R123_E004</data><data key="edge_relationship_type">reports_aggregated_transactions_from</data><data key="edge_target_entity_id">APP_MYCOA</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Public counts are aggregate Internet application receipts and do not preserve individual person/address records in the public product.</data></edge><edge id="R123_REL006" source="R123_E005" target="APP_MYCOA"><data key="edge_relationship_id">R123_REL006</data><data key="edge_source_entity_id">R123_E005</data><data key="edge_relationship_type">reports_aggregated_transactions_from</data><data key="edge_target_entity_id">APP_MYCOA</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Public counts are aggregate Internet application receipts and do not preserve individual person/address records in the public product.</data></edge><edge id="R123_REL007" source="R123_E006" target="APP_MYCOA"><data key="edge_relationship_id">R123_REL007</data><data key="edge_source_entity_id">R123_E006</data><data key="edge_relationship_type">reports_aggregated_transactions_from</data><data key="edge_target_entity_id">APP_MYCOA</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Public counts are aggregate Internet application receipts and do not preserve individual person/address records in the public product.</data></edge><edge id="R123_REL008" source="DATA_COA_INET" target="R123_E004"><data key="edge_relationship_id">R123_REL008</data><data key="edge_source_entity_id">DATA_COA_INET</data><data key="edge_relationship_type">comprises_published_subset</data><data key="edge_target_entity_id">R123_E004</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">FY2016 onward monthly CSV part of the public collection.</data></edge><edge id="R123_REL009" source="DATA_COA_INET" target="R123_E005"><data key="edge_relationship_id">R123_REL009</data><data key="edge_source_entity_id">DATA_COA_INET</data><data key="edge_relationship_type">comprises_published_subset</data><data key="edge_target_entity_id">R123_E005</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Separate 53rd reporting week FY2016 CSV.</data></edge><edge id="R123_REL010" source="DATA_COA_INET" target="R123_E006"><data key="edge_relationship_id">R123_REL010</data><data key="edge_source_entity_id">DATA_COA_INET</data><data key="edge_relationship_type">comprises_published_subset</data><data key="edge_target_entity_id">R123_E006</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">FY2008-2015 historical CSV part of collection.</data></edge><edge id="R123_REL011" source="SYS_SSR" target="R123_E007"><data key="edge_relationship_id">R123_REL011</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">supplies_full_current_program_participation_extract_to</data><data key="edge_target_entity_id">R123_E007</data><data key="edge_operational_context">2026 annual SSI report; December 2025 statistics</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">100 percent SSR extract used for current SSI recipient program participation.</data></edge><edge id="R123_REL012" source="SYS_SSR" target="R123_E008"><data key="edge_relationship_id">R123_REL012</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">supplies_ten_percent_prior_participation_extract_to</data><data key="edge_target_entity_id">R123_E008</data><data key="edge_operational_context">2026 annual SSI report; prior participation</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">10 percent SSR extract used for past program participation.</data></edge><edge id="R123_REL013" source="R123_E007" target="R123_E009"><data key="edge_relationship_id">R123_REL013</data><data key="edge_source_entity_id">R123_E007</data><data key="edge_relationship_type">input_to</data><data key="edge_target_entity_id">R123_E009</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Current program participation extract; 100 percent sample.</data></edge><edge id="R123_REL014" source="R123_E008" target="R123_E009"><data key="edge_relationship_id">R123_REL014</data><data key="edge_source_entity_id">R123_E008</data><data key="edge_relationship_type">input_to</data><data key="edge_target_entity_id">R123_E009</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Past program participation extract; 10 percent sample.</data></edge><edge id="R123_REL015" source="R123_E009" target="R123_E010"><data key="edge_relationship_id">R123_REL015</data><data key="edge_source_entity_id">R123_E009</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R123_E010</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Table V.F1 program participation percentages by age group and program.</data></edge><edge id="R123_REL016" source="R123_E010" target="REPORT_SSI_ANNUAL_2026"><data key="edge_relationship_id">R123_REL016</data><data key="edge_source_entity_id">R123_E010</data><data key="edge_relationship_type">published_within</data><data key="edge_target_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Appendix V.F in July 2026 SSI report.</data></edge><edge id="R123_REL017" source="APP_TITLEII_MAJOR" target="R123_E017"><data key="edge_relationship_id">R123_REL017</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_historical_major_subsystem</data><data key="edge_target_entity_id">R123_E017</data><data key="edge_operational_context">PIA signed July 2017</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA Title II system component; no contemporary deployment assertion.</data></edge><edge id="R123_REL018" source="APP_TITLEII_MAJOR" target="R123_E018"><data key="edge_relationship_id">R123_REL018</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_historical_major_subsystem</data><data key="edge_target_entity_id">R123_E018</data><data key="edge_operational_context">PIA signed July 2017</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA Title II system component; no contemporary deployment assertion.</data></edge><edge id="R123_REL019" source="APP_TITLEII_MAJOR" target="R123_E019"><data key="edge_relationship_id">R123_REL019</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_historical_major_subsystem</data><data key="edge_target_entity_id">R123_E019</data><data key="edge_operational_context">PIA signed July 2017</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA Title II system component; no contemporary deployment assertion.</data></edge><edge id="R123_REL020" source="APP_TITLEII_MAJOR" target="R123_E020"><data key="edge_relationship_id">R123_REL020</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_historical_major_subsystem</data><data key="edge_target_entity_id">R123_E020</data><data key="edge_operational_context">PIA signed July 2017</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA Title II system component; no contemporary deployment assertion.</data></edge><edge id="R123_REL021" source="APP_TITLEII_MAJOR" target="R123_E021"><data key="edge_relationship_id">R123_REL021</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_historical_major_subsystem</data><data key="edge_target_entity_id">R123_E021</data><data key="edge_operational_context">PIA signed July 2017</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA Title II system component; no contemporary deployment assertion.</data></edge><edge id="R123_REL022" source="APP_TITLEII_MAJOR" target="R123_E011"><data key="edge_relationship_id">R123_REL022</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_historical_major_subsystem</data><data key="edge_target_entity_id">R123_E011</data><data key="edge_operational_context">PIA signed July 2017</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA telephone application subsystem, not confirmed current.</data></edge><edge id="R123_REL023" source="R123_E011" target="R123_E012"><data key="edge_relationship_id">R123_REL023</data><data key="edge_source_entity_id">R123_E011</data><data key="edge_relationship_type">included_telephone_application</data><data key="edge_target_entity_id">R123_E012</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly iBEVE benefit verification letter functionality in 2017.</data></edge><edge id="R123_REL024" source="APP_CET_SUITE_2016" target="R123_E013"><data key="edge_relationship_id">R123_REL024</data><data key="edge_source_entity_id">APP_CET_SUITE_2016</data><data key="edge_relationship_type">historically_described_contact_channel</data><data key="edge_target_entity_id">R123_E013</data><data key="edge_operational_context">2017 Title II PIA</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA names the channel under Customer Engagement Tools; no current deployment claim.</data></edge><edge id="R123_REL025" source="APP_CET_SUITE_2016" target="R123_E014"><data key="edge_relationship_id">R123_REL025</data><data key="edge_source_entity_id">APP_CET_SUITE_2016</data><data key="edge_relationship_type">historically_described_contact_channel</data><data key="edge_target_entity_id">R123_E014</data><data key="edge_operational_context">2017 Title II PIA</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA names the channel under Customer Engagement Tools; no current deployment claim.</data></edge><edge id="R123_REL026" source="APP_CET_SUITE_2016" target="R123_E015"><data key="edge_relationship_id">R123_REL026</data><data key="edge_source_entity_id">APP_CET_SUITE_2016</data><data key="edge_relationship_type">historically_described_contact_channel</data><data key="edge_target_entity_id">R123_E015</data><data key="edge_operational_context">2017 Title II PIA</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA names the channel under Customer Engagement Tools; no current deployment claim.</data></edge><edge id="R123_REL027" source="APP_CET_SUITE_2016" target="R123_E016"><data key="edge_relationship_id">R123_REL027</data><data key="edge_source_entity_id">APP_CET_SUITE_2016</data><data key="edge_relationship_type">historically_described_contact_channel</data><data key="edge_target_entity_id">R123_E016</data><data key="edge_operational_context">2017 Title II PIA</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2017 PIA names the channel under Customer Engagement Tools; no current deployment claim.</data></edge><edge id="R123_REL028" source="R123_E023" target="R123_E024"><data key="edge_relationship_id">R123_REL028</data><data key="edge_source_entity_id">R123_E023</data><data key="edge_relationship_type">supplies_items_for</data><data key="edge_target_entity_id">R123_E024</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Computer adaptive selection over a bank of more than 300 items.</data></edge><edge id="R123_REL029" source="R123_E024" target="R123_E022"><data key="edge_relationship_id">R123_REL029</data><data key="edge_source_entity_id">R123_E024</data><data key="edge_relationship_type">administers_research_instrument</data><data key="edge_target_entity_id">R123_E022</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">IRT/CAT method for adaptive respondent self-report, not official production disability case scoring.</data></edge><edge id="R123_REL030" source="ORG_WESTAT" target="R123_E025"><data key="edge_relationship_id">R123_REL030</data><data key="edge_source_entity_id">ORG_WESTAT</data><data key="edge_relationship_type">administered_historical_two_wave_survey</data><data key="edge_target_entity_id">R123_E025</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">SSA awarded Westat to administer the assessment and survey; no specific procurement vehicle established.</data></edge><edge id="R123_REL031" source="R123_E025" target="R123_E022"><data key="edge_relationship_id">R123_REL031</data><data key="edge_source_entity_id">R123_E025</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">R123_E022</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Both waves include WD-FAB self-reports and health-related questions; collection complete August 2023.</data></edge><edge id="R123_REL032" source="R123_E025" target="R123_E026"><data key="edge_relationship_id">R123_REL032</data><data key="edge_source_entity_id">R123_E025</data><data key="edge_relationship_type">analyzed_in</data><data key="edge_target_entity_id">R123_E026</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">NIH Clinical Center Rehabilitation Medicine staff analyzed collected data for medical CDR feasibility.</data></edge><edge id="R123_REL033" source="R123_E026" target="R123_E027"><data key="edge_relationship_id">R123_REL033</data><data key="edge_source_entity_id">R123_E026</data><data key="edge_relationship_type">documented_by</data><data key="edge_target_entity_id">R123_E027</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Research study final report available on SSA research page.</data></edge><edge id="R123_REL034" source="R123_E022" target="ORG_BU_HDRI"><data key="edge_relationship_id">R123_REL034</data><data key="edge_source_entity_id">R123_E022</data><data key="edge_relationship_type">developed_with</data><data key="edge_target_entity_id">ORG_BU_HDRI</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">SSA reports working with Boston University to develop assessment instrument.</data></edge><edge id="R123_REL035" source="R123_E026" target="ORG_NIH_CRC_RMD"><data key="edge_relationship_id">R123_REL035</data><data key="edge_source_entity_id">R123_E026</data><data key="edge_relationship_type">conducted_by</data><data key="edge_target_entity_id">ORG_NIH_CRC_RMD</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">NIH Clinical Center rehabilitation medicine analysis.</data></edge><edge id="R123_REL036" source="R123_E028" target="R123_E029"><data key="edge_relationship_id">R123_REL036</data><data key="edge_source_entity_id">R123_E028</data><data key="edge_relationship_type">collected_participant_longitudinal_survey</data><data key="edge_target_entity_id">R123_E029</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Baseline and quarterly surveys across a three-year enrollment period.</data></edge><edge id="R123_REL037" source="R123_E028" target="R123_E030"><data key="edge_relationship_id">R123_REL037</data><data key="edge_source_entity_id">R123_E028</data><data key="edge_relationship_type">assembled_ssa_claim_payment_research_data</data><data key="edge_target_entity_id">R123_E030</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">SSA disability claims and payment outcomes used for research; originating operational systems not specified.</data></edge><edge id="R123_REL038" source="R123_E029" target="R123_E031"><data key="edge_relationship_id">R123_REL038</data><data key="edge_source_entity_id">R123_E029</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">R123_E031</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Repeated survey variables are transformed into public-use fields, with participant-relative quarter indexes.</data></edge><edge id="R123_REL039" source="R123_E030" target="R123_E031"><data key="edge_relationship_id">R123_REL039</data><data key="edge_source_entity_id">R123_E030</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">R123_E031</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">SSA administrative claim/appeal/payment variables included; physical extraction/interface unverified.</data></edge><edge id="R123_REL040" source="R123_E032" target="R123_E031"><data key="edge_relationship_id">R123_REL040</data><data key="edge_source_entity_id">R123_E032</data><data key="edge_relationship_type">protects_release_of</data><data key="edge_target_entity_id">R123_E031</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Dropped names, direct identifiers, geography, site data, free text; recoded some rare details.</data></edge><edge id="R123_REL041" source="R123_E033" target="R123_E031"><data key="edge_relationship_id">R123_REL041</data><data key="edge_source_entity_id">R123_E033</data><data key="edge_relationship_type">authorized_release_of</data><data key="edge_target_entity_id">R123_E031</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Disclosure board approved 2023-05-10.</data></edge><edge id="R123_REL042" source="R123_E031" target="R123_E034"><data key="edge_relationship_id">R123_REL042</data><data key="edge_source_entity_id">R123_E031</data><data key="edge_relationship_type">distributed_as</data><data key="edge_target_entity_id">R123_E034</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Official public-use CSV distribution.</data></edge><edge id="R123_REL043" source="R123_E031" target="R123_E035"><data key="edge_relationship_id">R123_REL043</data><data key="edge_source_entity_id">R123_E031</data><data key="edge_relationship_type">distributed_as</data><data key="edge_target_entity_id">R123_E035</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Official public-use SAS distribution.</data></edge><edge id="R123_REL044" source="ORG_WESTAT" target="R123_E028"><data key="edge_relationship_id">R123_REL044</data><data key="edge_source_entity_id">ORG_WESTAT</data><data key="edge_relationship_type">was_awarded_study_contract_to_support</data><data key="edge_target_entity_id">R123_E028</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">2016 award for SED implementation and evaluation; contract ID not established.</data></edge><edge id="R123_REL045" source="R123_E036" target="R123_E037"><data key="edge_relationship_id">R123_REL045</data><data key="edge_source_entity_id">R123_E036</data><data key="edge_relationship_type">has_related_public_metadata_duty</data><data key="edge_target_entity_id">R123_E037</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Statutory federal requirements do not establish actual SSA implementation.</data></edge><edge id="R123_REL046" source="R123_E038" target="R123_E036"><data key="edge_relationship_id">R123_REL046</data><data key="edge_source_entity_id">R123_E038</data><data key="edge_relationship_type">supports_govwide_software_reuse_governance</data><data key="edge_target_entity_id">R123_E036</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Rights for sharing custom-developed software across government; not an observed deployed source-control solution.</data></edge><edge id="R123_REL047" source="R123_E039" target="R123_E036"><data key="edge_relationship_id">R123_REL047</data><data key="edge_source_entity_id">R123_E039</data><data key="edge_relationship_type">implements_required_controls_for</data><data key="edge_target_entity_id">R123_E036</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">CIO policy obligations under the Act.</data></edge><edge id="R123_REL048" source="R123_E039" target="R123_E037"><data key="edge_relationship_id">R123_REL048</data><data key="edge_source_entity_id">R123_E039</data><data key="edge_relationship_type">implements_required_controls_for</data><data key="edge_target_entity_id">R123_E037</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Metadata access governance required; no assertion of compliance.</data></edge><edge id="R123_REL049" source="R123_E039" target="R123_E038"><data key="edge_relationship_id">R123_REL049</data><data key="edge_source_entity_id">R123_E039</data><data key="edge_relationship_type">implements_required_controls_for</data><data key="edge_target_entity_id">R123_E038</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Acquisition coordination and contracting rights for code reuse.</data></edge><edge id="R123_REL050" source="R123_E040" target="R123_E041"><data key="edge_relationship_id">R123_REL050</data><data key="edge_source_entity_id">R123_E040</data><data key="edge_relationship_type">uses_request_site</data><data key="edge_target_entity_id">R123_E041</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Regional procedures describe internal folder certification request site.</data></edge><edge id="R123_REL051" source="R123_E040" target="R123_E042"><data key="edge_relationship_id">R123_REL051</data><data key="edge_source_entity_id">R123_E040</data><data key="edge_relationship_type">must_separately_route_earnings_certification_to</data><data key="edge_target_entity_id">R123_E042</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Regional instruction reserves tax-return earnings records certification to OEIO.</data></edge><edge id="R123_REL052" source="DATA_DOWR" target="DATA_DIB_INTERNET_APPS_2247"><data key="edge_relationship_id">R123_REL052</data><data key="edge_source_entity_id">DATA_DOWR</data><data key="edge_relationship_type">supplies_claim_receipt_date_for</data><data key="edge_target_entity_id">DATA_DIB_INTERNET_APPS_2247</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Open Data uses District Office Workload Report receipt date to classify disability initial-claim receipts; work reporting dates not necessarily calendar months.</data></edge><edge id="R123_REL053" source="DB_TITLE2_ODS" target="DATA_DIB_INTERNET_APPS_2247"><data key="edge_relationship_id">R123_REL053</data><data key="edge_source_entity_id">DB_TITLE2_ODS</data><data key="edge_relationship_type">supplies_aggregated_claim_count_for</data><data key="edge_target_entity_id">DATA_DIB_INTERNET_APPS_2247</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">SSA says MCS data download to Title II Operational Data Store nightly and counts aggregated by channel.</data></edge><edge id="R123_REL054" source="APP_MCS" target="DB_TITLE2_ODS"><data key="edge_relationship_id">R123_REL054</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">provides_nightly_claim_data_to</data><data key="edge_target_entity_id">DB_TITLE2_ODS</data><data key="edge_operational_context">Initial DIB internet claims fiscal-year statistical reporting</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Official open data states nightly MCS download for initial disability claims; this relates to existing MCS-&gt;ODS pathways.</data></edge><edge id="R124_REL001" source="R124_E001" target="PROC_SSI_IRS_PENSION_MATCH"><data key="edge_relationship_id">R124_REL001</data><data key="edge_source_entity_id">R124_E001</data><data key="edge_relationship_type">provides_pension_comparison_data_to</data><data key="edge_target_entity_id">PROC_SSI_IRS_PENSION_MATCH</data><data key="edge_operational_context">2017 POMS describes Form 1099-R information of eligible individuals and deemors matched to SSR; no IRS-supplied address update is established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL002" source="PROC_SSI_IRS_PENSION_MATCH" target="R124_E002"><data key="edge_relationship_id">R124_REL002</data><data key="edge_source_entity_id">PROC_SSI_IRS_PENSION_MATCH</data><data key="edge_relationship_type">historically_applied_threshold</data><data key="edge_target_entity_id">R124_E002</data><data key="edge_operational_context">Documented 2017 tolerance used for matching report amount to SSR D/L/M/P categories.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL003" source="PROC_SSI_IRS_PENSION_MATCH" target="WORK_SSI_IRS_5H_DIARY"><data key="edge_relationship_id">R124_REL003</data><data key="edge_source_entity_id">PROC_SSI_IRS_PENSION_MATCH</data><data key="edge_relationship_type">generates_ssr_work_control</data><data key="edge_target_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_operational_context">Pension SSN reports and SSR values drive 5H diary creation where criteria satisfied.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL004" source="WORK_SSI_IRS_5H_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R124_REL004</data><data key="edge_source_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_relationship_type">retrieved_via</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">Technicians identify cases with pension diaries through SSI post-entitlement ODS; then obtain an SSID.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL005" source="WORK_SSI_IRS_5H_DIARY" target="R124_E003"><data key="edge_relationship_id">R124_REL005</data><data key="edge_source_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_relationship_type">paired_workload_schedule</data><data key="edge_target_entity_id">R124_E003</data><data key="edge_operational_context">2026 POMS says pension 5H accompanies 5B workload releases.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL006" source="WORK_SSI_IRS_5B_DIARY" target="R124_E003"><data key="edge_relationship_id">R124_REL006</data><data key="edge_source_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_relationship_type">follows_workload_schedule</data><data key="edge_target_entity_id">R124_E003</data><data key="edge_operational_context">2026 policy identifies 5B releases Oct, Feb and June; distinct from 2017 data-availability schedule.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL007" source="R124_E003" target="R124_E004"><data key="edge_relationship_id">R124_REL007</data><data key="edge_source_entity_id">R124_E003</data><data key="edge_relationship_type">offers_tax_interface_query_via</data><data key="edge_target_entity_id">R124_E004</data><data key="edge_operational_context">MI Central query available to authorized technicians with relevant RZ/LI workloads.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL008" source="R124_E004" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R124_REL008</data><data key="edge_source_entity_id">R124_E004</data><data key="edge_relationship_type">accessed_through</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">Under workload listing SSN/IRS/SSID query.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL009" source="R124_E004" target="DB_SSI_IRS_INTERFACE"><data key="edge_relationship_id">R124_REL009</data><data key="edge_source_entity_id">R124_E004</data><data key="edge_relationship_type">retrieves_matching_alerts_from</data><data key="edge_target_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_operational_context">2026 procedures describe the SSI/IRS interface database as lookup source; verify known entity ID exists.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL010" source="R124_E005" target="SYS_SSR"><data key="edge_relationship_id">R124_REL010</data><data key="edge_source_entity_id">R124_E005</data><data key="edge_relationship_type">identified_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">CRZD selection indicator F without a diary; monthly Type F LI release.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL011" source="R124_E006" target="SYS_SSR"><data key="edge_relationship_id">R124_REL011</data><data key="edge_source_entity_id">R124_E006</data><data key="edge_relationship_type">identified_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">CRZD selection indicator C with April tax-record availability; no diary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL012" source="R124_E007" target="R124_E008"><data key="edge_relationship_id">R124_REL012</data><data key="edge_source_entity_id">R124_E007</data><data key="edge_relationship_type">has_diary</data><data key="edge_target_entity_id">R124_E008</data><data key="edge_operational_context">Certain manually continued Goldberg/Kelly benefits have an SSR K1 diary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL013" source="R124_E008" target="SYS_SSR"><data key="edge_relationship_id">R124_REL013</data><data key="edge_source_entity_id">R124_E008</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2026 POMS indicates K1 on SSR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL014" source="R124_E009" target="SYS_SSR"><data key="edge_relationship_id">R124_REL014</data><data key="edge_source_entity_id">R124_E009</data><data key="edge_relationship_type">historically_documented_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">D6 diary once triggered RZs but does not from Oct 2005; preserve historical only.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL015" source="R124_E010" target="DATA_MANUAL_DEEMING_LIST"><data key="edge_relationship_id">R124_REL015</data><data key="edge_source_entity_id">R124_E010</data><data key="edge_relationship_type">uses_read_only_data_listing</data><data key="edge_target_entity_id">DATA_MANUAL_DEEMING_LIST</data><data key="edge_operational_context">October file for manually computed deemed income is explicitly outside MI Central work controls.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL016" source="R124_E010" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R124_REL016</data><data key="edge_source_entity_id">R124_E010</data><data key="edge_relationship_type">not_controlled_by</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">Source explicitly says no SUMS MCAS MI Central control and no SSR diary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL017" source="R124_E011" target="SYS_SSR"><data key="edge_relationship_id">R124_REL017</data><data key="edge_source_entity_id">R124_E011</data><data key="edge_relationship_type">compares_current_allegation_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Claimant states current residence; SSA checks SSR to decide if additional development is necessary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL018" source="R124_E011" target="R124_E012"><data key="edge_relationship_id">R124_REL018</data><data key="edge_source_entity_id">R124_E011</data><data key="edge_relationship_type">may_open</data><data key="edge_target_entity_id">R124_E012</data><data key="edge_operational_context">Mismatch plus an unreported move requires further LA/ISM and residency development.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL019" source="R124_E011" target="R124_E013"><data key="edge_relationship_id">R124_REL019</data><data key="edge_source_entity_id">R124_E011</data><data key="edge_relationship_type">may_open</data><data key="edge_target_entity_id">R124_E013</data><data key="edge_operational_context">No intervening COA prompts temporary-absence development.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL020" source="R124_E012" target="R124_E014"><data key="edge_relationship_id">R124_REL020</data><data key="edge_source_entity_id">R124_E012</data><data key="edge_relationship_type">creates_living_arrangement_iteration</data><data key="edge_target_entity_id">R124_E014</data><data key="edge_operational_context">Relevant change creates separate LA iteration for breakpoint.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL021" source="R124_E012" target="R124_E015"><data key="edge_relationship_id">R124_REL021</data><data key="edge_source_entity_id">R124_E012</data><data key="edge_relationship_type">triggers_conditional_review</data><data key="edge_target_entity_id">R124_E015</data><data key="edge_operational_context">Residence can affect Medicaid and state supplement jurisdiction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL022" source="R124_E012" target="FORM_SSA8006F4"><data key="edge_relationship_id">R124_REL022</data><data key="edge_source_entity_id">R124_E012</data><data key="edge_relationship_type">may_use_form</data><data key="edge_target_entity_id">FORM_SSA8006F4</data><data key="edge_operational_context">RZ procedure permits documentation on SSA-8006/F4 as appropriate.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL023" source="R124_E012" target="FORM_SSA8007"><data key="edge_relationship_id">R124_REL023</data><data key="edge_source_entity_id">R124_E012</data><data key="edge_relationship_type">may_use_form</data><data key="edge_target_entity_id">FORM_SSA8007</data><data key="edge_operational_context">RZ procedure permits documentation on SSA-8007 as appropriate.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL024" source="R124_E012" target="FORM_SSA8008"><data key="edge_relationship_id">R124_REL024</data><data key="edge_source_entity_id">R124_E012</data><data key="edge_relationship_type">may_use_form</data><data key="edge_target_entity_id">FORM_SSA8008</data><data key="edge_operational_context">RZ procedure permits documentation on SSA-8008 as appropriate.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL025" source="R124_E016" target="SYS_SSR"><data key="edge_relationship_id">R124_REL025</data><data key="edge_source_entity_id">R124_E016</data><data key="edge_relationship_type">controls_future_travel_followup_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">When recipient has future foreign travel plans, office diary set for preceding month; no address update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL026" source="R124_E017" target="UI_SSI_LRES"><data key="edge_relationship_id">R124_REL026</data><data key="edge_source_entity_id">R124_E017</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">UI_SSI_LRES</data><data key="edge_operational_context">SSI Claims Residence Address and Jurisdiction page contains type of residence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL027" source="R124_E018" target="FORM_SSA8203BK"><data key="edge_relationship_id">R124_REL027</data><data key="edge_source_entity_id">R124_E018</data><data key="edge_relationship_type">recorded_during_redetermination_on</data><data key="edge_target_entity_id">FORM_SSA8203BK</data><data key="edge_operational_context">Mark REC or spouse for differing claimant and spouse residences.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL028" source="R124_E019" target="R124_E020"><data key="edge_relationship_id">R124_REL028</data><data key="edge_source_entity_id">R124_E019</data><data key="edge_relationship_type">reviews_claimant_cohabitants_during</data><data key="edge_target_entity_id">R124_E020</data><data key="edge_operational_context">Household change screen feeds evaluation of moved-in persons and potential protected filing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL029" source="R124_E020" target="APP_MSSICS"><data key="edge_relationship_id">R124_REL029</data><data key="edge_source_entity_id">R124_E020</data><data key="edge_relationship_type">captures_household_information_during</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">SSI Claims System redetermination path documents household expenses and contributions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL030" source="R124_E021" target="UI_SSI_LRES"><data key="edge_relationship_id">R124_REL030</data><data key="edge_source_entity_id">R124_E021</data><data key="edge_relationship_type">activated_by_residence_type_on</data><data key="edge_target_entity_id">UI_SSI_LRES</data><data key="edge_operational_context">Residence Address and Jurisdiction type non-institutional care opens page for placement and cost data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL031" source="R124_E021" target="R124_E022"><data key="edge_relationship_id">R124_REL031</data><data key="edge_source_entity_id">R124_E021</data><data key="edge_relationship_type">captures</data><data key="edge_target_entity_id">R124_E022</data><data key="edge_operational_context">Placing agency and provider details for ISM development distinct from beneficiary address.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL032" source="R124_E022" target="R124_E021"><data key="edge_relationship_id">R124_REL032</data><data key="edge_source_entity_id">R124_E022</data><data key="edge_relationship_type">supports_case_living_arrangement_development_via</data><data key="edge_target_entity_id">R124_E021</data><data key="edge_operational_context">Agency placement and source contact information determine noninstitutional care and ISM.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL033" source="R124_E023" target="APP_EAFI"><data key="edge_relationship_id">R124_REL033</data><data key="edge_source_entity_id">R124_E023</data><data key="edge_relationship_type">allows_alternative_verification_after</data><data key="edge_target_entity_id">APP_EAFI</data><data key="edge_operational_context">No electronic response after 15 days permits FI statements or alternative proof; not waiver of mandatory verification in all cases.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL034" source="R124_E024" target="EX_AFI_FI"><data key="edge_relationship_id">R124_REL034</data><data key="edge_source_entity_id">R124_E024</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Foreign banking without domestic sister branch is documented exception to source procedures.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL035" source="R124_E025" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R124_REL035</data><data key="edge_source_entity_id">R124_E025</data><data key="edge_relationship_type">uses_service</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Claimant may submit unaltered downloaded statements or bank transaction files through Upload Documents.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL036" source="R124_E025" target="R124_E026"><data key="edge_relationship_id">R124_REL036</data><data key="edge_source_entity_id">R124_E025</data><data key="edge_relationship_type">supports_alternative_balance_development</data><data key="edge_target_entity_id">R124_E026</data><data key="edge_operational_context">Sufficient transaction-level detail permits first-of-month reconstruction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL037" source="R124_E026" target="SYS_SSR"><data key="edge_relationship_id">R124_REL037</data><data key="edge_source_entity_id">R124_E026</data><data key="edge_relationship_type">informs_monthly_resource_eligibility_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Resource development applies first-of-month balance less applicable deductions, not direct trust of any transaction account value.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL038" source="R124_E027" target="APP_EAFI"><data key="edge_relationship_id">R124_REL038</data><data key="edge_source_entity_id">R124_E027</data><data key="edge_relationship_type">applies_when_alternative_evidence_during</data><data key="edge_target_entity_id">APP_EAFI</data><data key="edge_operational_context">Later AFI electronic response requires separate posteligibility handling after adjudication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL039" source="R124_E028" target="APP_EAFI"><data key="edge_relationship_id">R124_REL039</data><data key="edge_source_entity_id">R124_E028</data><data key="edge_relationship_type">expanded_verification_use_of</data><data key="edge_target_entity_id">APP_EAFI</data><data key="edge_operational_context">EM effective 5/4/2026 for SSI initial allowances, reopenings, appeal reversals.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL040" source="R124_E028" target="APP_MSSICS"><data key="edge_relationship_id">R124_REL040</data><data key="edge_source_entity_id">R124_E028</data><data key="edge_relationship_type">requires_before_allowance_exception_handling_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Pre-effectuation review and blank payment status deadlines differ for deferred and simultaneous disability claims.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL041" source="R124_E029" target="APP_ECBSV"><data key="edge_relationship_id">R124_REL041</data><data key="edge_source_entity_id">R124_E029</data><data key="edge_relationship_type">sets_monitoring_targets_for</data><data key="edge_target_entity_id">APP_ECBSV</data><data key="edge_operational_context">GAO documented Dec 2025 eCBSV performance targets in uptime and transaction processing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL042" source="R124_E030" target="APP_ECBSV"><data key="edge_relationship_id">R124_REL042</data><data key="edge_source_entity_id">R124_E030</data><data key="edge_relationship_type">proposes_expansion_of</data><data key="edge_target_entity_id">APP_ECBSV</data><data key="edge_operational_context">Jan 2026 plan targets June 2026; public SSA eligibility still limited to permitted entities; not confirmed deployed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL043" source="R124_E031" target="APP_ECBSV"><data key="edge_relationship_id">R124_REL043</data><data key="edge_source_entity_id">R124_E031</data><data key="edge_relationship_type">governs_enrollment_costs_for</data><data key="edge_target_entity_id">APP_ECBSV</data><data key="edge_operational_context">Subscription fees set according to estimated annual volume, published effective Apr 7 2025.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL044" source="R124_E032" target="APP_ECBSV"><data key="edge_relationship_id">R124_REL044</data><data key="edge_source_entity_id">R124_E032</data><data key="edge_relationship_type">restricts_verification_requests_to</data><data key="edge_target_entity_id">APP_ECBSV</data><data key="edge_operational_context">Annual tier limit and valid agreement restrict requests; no SSN verification if authorization unsuccessful.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL045" source="WORK_SSI_S7_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R124_REL045</data><data key="edge_source_entity_id">WORK_SSI_S7_DIARY</data><data key="edge_relationship_type">compares_ssr_wages_to_ocse</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">S7 diary indicates wage discrepancy versus OCSE quarterly wage data; canonical entity name calls this State Wage Match and must be reconciled.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL046" source="WORK_SSI_S2_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R124_REL046</data><data key="edge_source_entity_id">WORK_SSI_S2_DIARY</data><data key="edge_relationship_type">alerts_on_state_wage_match</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">S2 state wage match has Oct Jan Apr Jul release frequency.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL047" source="WORK_SSI_J3J5_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R124_REL047</data><data key="edge_source_entity_id">WORK_SSI_J3J5_DIARY</data><data key="edge_relationship_type">alerts_on_mismatch_to_mef</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">J3/J5 based on SSR wages higher than MEF; 2026 source gives $1,000/$2,000 yearly deviations.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL048" source="WORK_SSI_D8_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R124_REL048</data><data key="edge_source_entity_id">WORK_SSI_D8_DIARY</data><data key="edge_relationship_type">flags_unreported_medical_facility_admission</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">CMS Minimum Data Set monthly D8 diary identifies unreported medical facility admissions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL049" source="WORK_SSI_3D_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R124_REL049</data><data key="edge_source_entity_id">WORK_SSI_3D_DIARY</data><data key="edge_relationship_type">posts_dhs_removal_match</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">DHS removal match listings generate monthly 3D diary on SSR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R124_REL050" source="WORK_SSI_I8_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R124_REL050</data><data key="edge_source_entity_id">WORK_SSI_I8_DIARY</data><data key="edge_relationship_type">posts_dhs_departure_with_reentry_permit_match</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">DHS voluntary departure with re-entry permit matching generates monthly I8 diary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R125_R001" source="EX_PIE" target="R125_E001"><data key="edge_relationship_id">R125_R001</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">requires_active_individual_authorization</data><data key="edge_target_entity_id">R125_E001</data><data key="edge_operational_context">Claimant, deemor or ineligible child authorization applies to the individual and is voluntary; reconsideration timing can temporarily disable automatic request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R002" source="EX_PIE" target="R125_E002"><data key="edge_relationship_id">R125_R002</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">schedules</data><data key="edge_target_entity_id">R125_E002</data><data key="edge_operational_context">Prior-month wages are requested early each month only for actively authorized persons who work for participating payroll providers.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R003" source="R125_E002" target="DB_WEI_REPO"><data key="edge_relationship_id">R125_R003</data><data key="edge_source_entity_id">R125_E002</data><data key="edge_relationship_type">accumulates_authorized_results_in</data><data key="edge_target_entity_id">DB_WEI_REPO</data><data key="edge_operational_context">Wage and Employment Information repository retains cumulative monthly receipts while authorization remains active; exact deletion timing beyond this rule is not provided.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R004" source="APP_IMAIN" target="R125_E003"><data key="edge_relationship_id">R125_R004</data><data key="edge_source_entity_id">APP_IMAIN</data><data key="edge_relationship_type">provides_lookup_access_to</data><data key="edge_target_entity_id">R125_E003</data><data key="edge_operational_context">POMS identifies IMAIN as technician entry to WEI wage and employment retrieval.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R005" source="R125_E003" target="DB_WEI_REPO"><data key="edge_relationship_id">R125_R005</data><data key="edge_source_entity_id">R125_E003</data><data key="edge_relationship_type">queries_repository</data><data key="edge_target_entity_id">DB_WEI_REPO</data><data key="edge_operational_context">Searches the WEI repository through IMAIN; no physical data engine is specified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R006" source="EX_PIE" target="R125_E004"><data key="edge_relationship_id">R125_R006</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">uses_match_gate</data><data key="edge_target_entity_id">R125_E004</data><data key="edge_operational_context">EIN match gates automatic SSI wage posting.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R007" source="R125_E004" target="UI_SSI_WAGES_PAGE"><data key="edge_relationship_id">R125_R007</data><data key="edge_source_entity_id">R125_E004</data><data key="edge_relationship_type">compares_provider_ein_to</data><data key="edge_target_entity_id">UI_SSI_WAGES_PAGE</data><data key="edge_operational_context">Provider EIN must match EIN on existing SSI Claims Wages page for automatic update of that page.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R008" source="R125_E004" target="SYS_SSR"><data key="edge_relationship_id">R125_R008</data><data key="edge_source_entity_id">R125_E004</data><data key="edge_relationship_type">conditionally_posts_wage_results_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">On successful EIN match, wages go to SSR before the monthly Goldberg-Kelly cutoff, with appropriate notices for adverse actions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R009" source="EX_PIE" target="R125_E005"><data key="edge_relationship_id">R125_R009</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">produces_reporting_change_notices</data><data key="edge_target_entity_id">R125_E005</data><data key="edge_operational_context">Reduced reporting notice follows successful exchange; increased reporting follows three consecutive missing monthly payroll feeds for an employer.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R010" source="APP_CCE" target="R125_E006"><data key="edge_relationship_id">R125_R010</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">hosts</data><data key="edge_target_entity_id">R125_E006</data><data key="edge_operational_context">CCE claims development provides the final disposition page used for resolved PDP pending wage information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R011" source="UI_PDP_PENDING_WAGE" target="R125_E006"><data key="edge_relationship_id">R125_R011</data><data key="edge_source_entity_id">UI_PDP_PENDING_WAGE</data><data key="edge_relationship_type">records_disposition_in</data><data key="edge_target_entity_id">R125_E006</data><data key="edge_operational_context">PDP Pending Wage option selected and final disposition is retained in the documentation page.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R012" source="UI_PDP_PENDING_WAGE_REPORT" target="R125_E006"><data key="edge_relationship_id">R125_R012</data><data key="edge_source_entity_id">UI_PDP_PENDING_WAGE_REPORT</data><data key="edge_relationship_type">records_disposition_in</data><data key="edge_target_entity_id">R125_E006</data><data key="edge_operational_context">Final PDP Pending Wage Report page disposition is retained in CCE.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R013" source="WORK_PIE_EE_DIARY" target="R125_E007"><data key="edge_relationship_id">R125_R013</data><data key="edge_source_entity_id">WORK_PIE_EE_DIARY</data><data key="edge_relationship_type">may_be_caused_by</data><data key="edge_target_entity_id">R125_E007</data><data key="edge_operational_context">Forced-due and manual-deeming records create EE diary conditions and pending wage reports.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R014" source="R125_E007" target="UI_PDP_PENDING_WAGE_REPORT"><data key="edge_relationship_id">R125_R014</data><data key="edge_source_entity_id">R125_E007</data><data key="edge_relationship_type">is_developed_in</data><data key="edge_target_entity_id">UI_PDP_PENDING_WAGE_REPORT</data><data key="edge_operational_context">POMS states force-due/manual-deeming conditions create the Pending Wage Report page for technician disposition.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R015" source="R125_E008" target="UI_PDP_PENDING_WAGE"><data key="edge_relationship_id">R125_R015</data><data key="edge_source_entity_id">R125_E008</data><data key="edge_relationship_type">reviews</data><data key="edge_target_entity_id">UI_PDP_PENDING_WAGE</data><data key="edge_operational_context">Technicians distinguish new employers, existing employers with mismatched EINs, and unrelated or fraudulently attributed employment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R016" source="R125_E008" target="R125_E006"><data key="edge_relationship_id">R125_R016</data><data key="edge_source_entity_id">R125_E008</data><data key="edge_relationship_type">documents_final_decision_in</data><data key="edge_target_entity_id">R125_E006</data><data key="edge_operational_context">A report of contact or other wage development supports the final CCE disposition.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R017" source="WORK_SSI_S7_DIARY" target="R125_E009"><data key="edge_relationship_id">R125_R017</data><data key="edge_source_entity_id">WORK_SSI_S7_DIARY</data><data key="edge_relationship_type">is_triggered_by_discrepancy_rule</data><data key="edge_target_entity_id">R125_E009</data><data key="edge_operational_context">Wages on SSR are greater than OCSE wages in the qualifying quarter; S7 can support eligibility adjustment and possible SSI underpayment release.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R018" source="WORK_SSI_S2_DIARY" target="R125_E010"><data key="edge_relationship_id">R125_R018</data><data key="edge_source_entity_id">WORK_SSI_S2_DIARY</data><data key="edge_relationship_type">is_triggered_by_discrepancy_rule</data><data key="edge_target_entity_id">R125_E010</data><data key="edge_operational_context">OCSE data exceed SSR wages; S2 develops unreported or underreported wages and potential overpayments.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R019" source="R125_E009" target="SYS_SSR"><data key="edge_relationship_id">R125_R019</data><data key="edge_source_entity_id">R125_E009</data><data key="edge_relationship_type">compares_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">S7 compares OCSE quarterly wage indicators with SSR wages; the term State Wage Record Match refers to OCSE state-collected data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R020" source="R125_E010" target="SYS_SSR"><data key="edge_relationship_id">R125_R020</data><data key="edge_source_entity_id">R125_E010</data><data key="edge_relationship_type">compares_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">S2 compares OCSE quarterly wage indicators with SSR wages.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R021" source="APP_SSI_OCSE_INTERFACE" target="R125_E009"><data key="edge_relationship_id">R125_R021</data><data key="edge_source_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="edge_relationship_type">supports_discrepancy_detection_for</data><data key="edge_target_entity_id">R125_E009</data><data key="edge_operational_context">Quarterly OCSE-to-SSR matching is the actual S7 feed context, despite the historical canonical display name.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R022" source="APP_SSI_OCSE_INTERFACE" target="R125_E010"><data key="edge_relationship_id">R125_R022</data><data key="edge_source_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="edge_relationship_type">supports_discrepancy_detection_for</data><data key="edge_target_entity_id">R125_E010</data><data key="edge_operational_context">Quarterly OCSE-to-SSR matching also generates S2 when external wages are higher.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R023" source="PROC_SSIDPP" target="R125_E011"><data key="edge_relationship_id">R125_R023</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">selects_candidates_using</data><data key="edge_target_entity_id">R125_E011</data><data key="edge_operational_context">Same name plus same month and year of birth is a candidate filter, not an automatic identity-merger criterion.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R024" source="R125_E011" target="R125_E012"><data key="edge_relationship_id">R125_R024</data><data key="edge_source_entity_id">R125_E011</data><data key="edge_relationship_type">requires_confirmation_by</data><data key="edge_target_entity_id">R125_E012</data><data key="edge_operational_context">Human verification with case material and claimant or payee prevents false merges.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R025" source="PROC_SSIDPP" target="R125_E013"><data key="edge_relationship_id">R125_R025</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">routes_work_using</data><data key="edge_target_entity_id">R125_E013</data><data key="edge_operational_context">Official policy establishes OSR → OCO → servicing FO responsibility chain.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R026" source="R125_E013" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R125_R026</data><data key="edge_source_entity_id">R125_E013</data><data key="edge_relationship_type">provides_cases_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">OCO assigns field office cases, including tie-breaker when two field offices are involved.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R027" source="R125_E012" target="R125_E014"><data key="edge_relationship_id">R125_R027</data><data key="edge_source_entity_id">R125_E012</data><data key="edge_relationship_type">may_result_in</data><data key="edge_target_entity_id">R125_E014</data><data key="edge_operational_context">If candidate records are different individuals, staff destroy materials and take no identity merge action.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R028" source="R125_E012" target="DATA_SSR_M1"><data key="edge_relationship_id">R125_R028</data><data key="edge_source_entity_id">R125_E012</data><data key="edge_relationship_type">can_require_cross_reference_update</data><data key="edge_target_entity_id">DATA_SSR_M1</data><data key="edge_operational_context">For records proved to be the same individual, policy requires bidirectional multiple-SSN cross-references and correct record termination.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R029" source="R125_E012" target="DATA_SSR_MA"><data key="edge_relationship_id">R125_R029</data><data key="edge_source_entity_id">R125_E012</data><data key="edge_relationship_type">may_require_enumeration_cross_reference</data><data key="edge_target_entity_id">DATA_SSR_MA</data><data key="edge_operational_context">MA field is used when second SSN was also formally issued to the same individual through enumeration.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R030" source="EX_CMA1038_BFS_SAVINGS" target="R125_E015"><data key="edge_relationship_id">R125_R030</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">uses_attribution_rule</data><data key="edge_target_entity_id">R125_E015</data><data key="edge_operational_context">The SSN printed on a savings security may not identify its actual legal owner; names on instrument take precedence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R031" source="WORK_SSI_SB_DIARY" target="R125_E016"><data key="edge_relationship_id">R125_R031</data><data key="edge_source_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_relationship_type">is_issued_under_threshold_gate</data><data key="edge_target_entity_id">R125_E016</data><data key="edge_operational_context">PE ODS controls documented SB alerts subject to aggregate valuation and two-match lookback rule.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R032" source="R125_E016" target="DB_BFS_SAVINGS_SECURITY_REG"><data key="edge_relationship_id">R125_R032</data><data key="edge_source_entity_id">R125_E016</data><data key="edge_relationship_type">uses_registration_data_from</data><data key="edge_target_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="edge_operational_context">BFS ownership and redemption-value registration records are compared against qualifying SSR cases.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R033" source="WORK_SSI_SB_DIARY" target="R125_E017"><data key="edge_relationship_id">R125_R033</data><data key="edge_source_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">R125_E017</data><data key="edge_operational_context">Denied ownership material to eligibility triggers documented BFS ownership verification via signed consent.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R034" source="R125_E017" target="ORG_BFS"><data key="edge_relationship_id">R125_R034</data><data key="edge_source_entity_id">R125_E017</data><data key="edge_relationship_type">requests_verification_from</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">The FO routes signed evidence request through SSA FO675 rather than assuming direct instant data access.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R035" source="WORK_SSI_SB_DIARY" target="R125_E018"><data key="edge_relationship_id">R125_R035</data><data key="edge_source_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_relationship_type">is_cleared_with</data><data key="edge_target_entity_id">R125_E018</data><data key="edge_operational_context">Policy distinguishes documentation on MSSICS DSAB versus non-MSSICS SSR remarks and direct SSR update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R036" source="R125_E018" target="UI_MSSICS_DSAB"><data key="edge_relationship_id">R125_R036</data><data key="edge_source_entity_id">R125_E018</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MSSICS_DSAB</data><data key="edge_operational_context">Savings bond ownership development is documented on DSAB in the relevant MSSICS processing path.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R037" source="R125_E018" target="R109_E028"><data key="edge_relationship_id">R125_R037</data><data key="edge_source_entity_id">R125_E018</data><data key="edge_relationship_type">sets_case_characteristic_in</data><data key="edge_target_entity_id">R109_E028</data><data key="edge_operational_context">RE21 is used when the claimant owns savings securities, with documented resource development.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R038" source="WORK_SSI_E2_DIARY" target="R125_E019"><data key="edge_relationship_id">R125_R038</data><data key="edge_source_entity_id">WORK_SSI_E2_DIARY</data><data key="edge_relationship_type">triggers_review</data><data key="edge_target_entity_id">R125_E019</data><data key="edge_operational_context">E2 diary generated by annual systems COLA run flags rentals that may change SSI in-kind-support treatment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R039" source="R125_E019" target="DATA_SSI_CMRV"><data key="edge_relationship_id">R125_R039</data><data key="edge_source_entity_id">R125_E019</data><data key="edge_relationship_type">recalculates_using</data><data key="edge_target_entity_id">DATA_SSI_CMRV</data><data key="edge_operational_context">Current market rental value (CMRV) is reverified and used in the new living-arrangement period as directed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R040" source="R125_E019" target="R125_E020"><data key="edge_relationship_id">R125_R040</data><data key="edge_source_entity_id">R125_E019</data><data key="edge_relationship_type">applies_nonresponse_control</data><data key="edge_target_entity_id">R125_E020</data><data key="edge_operational_context">Employee follow-up uses two documented attempts and 30 days in the cited exception.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R041" source="R125_E020" target="UI_SSI_UDIA"><data key="edge_relationship_id">R125_R041</data><data key="edge_source_entity_id">R125_E020</data><data key="edge_relationship_type">can_clear_diary_using</data><data key="edge_target_entity_id">UI_SSI_UDIA</data><data key="edge_operational_context">UDIA is a conditional diary clearance interface when information could not be obtained under procedure.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R042" source="DB_BFS_SAVINGS_SECURITY_REG" target="R125_E021"><data key="edge_relationship_id">R125_R042</data><data key="edge_source_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="edge_relationship_type">has_documented_historical_attribute</data><data key="edge_target_entity_id">R125_E021</data><data key="edge_operational_context">Early Series E registration used purchase-time owner name and address, potentially obsolete decades later; storage is at BFS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R043" source="DB_BFS_SAVINGS_SECURITY_REG" target="R125_E022"><data key="edge_relationship_id">R125_R043</data><data key="edge_source_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="edge_relationship_type">has_documented_historical_key</data><data key="edge_target_entity_id">R125_E022</data><data key="edge_operational_context">Later Treasury instrument series have SSN-based owner registration search rather than pre-1974 name-address index.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R044" source="R125_E023" target="R125_E021"><data key="edge_relationship_id">R125_R044</data><data key="edge_source_entity_id">R125_E023</data><data key="edge_relationship_type">may_consult</data><data key="edge_target_entity_id">R125_E021</data><data key="edge_operational_context">For older disputed holdings, staff collect historical purchase address for BFS lookup, not an SSA master address update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R045" source="R125_E023" target="R125_E022"><data key="edge_relationship_id">R125_R045</data><data key="edge_source_entity_id">R125_E023</data><data key="edge_relationship_type">may_consult</data><data key="edge_target_entity_id">R125_E022</data><data key="edge_operational_context">Later disputed holdings may require the owner/joint-owner SSN for BFS record retrieval.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R046" source="QRY_DEQY" target="R125_E023"><data key="edge_relationship_id">R125_R046</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">supports_payer_identity_development_for</data><data key="edge_target_entity_id">R125_E023</data><data key="edge_operational_context">2026 IRS special situations instructs DEQY for missing or implausible payers, not direct IRS address queries.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R047" source="R125_E023" target="SYS_SSR"><data key="edge_relationship_id">R125_R047</data><data key="edge_source_entity_id">R125_E023</data><data key="edge_relationship_type">is_separate_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">IRS security-interest alert is preliminary evidence; verified program findings require development before any SSI change.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R048" source="APP_DMS" target="R125_E024"><data key="edge_relationship_id">R125_R048</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">collects_debtor_contact_attribute</data><data key="edge_target_entity_id">R125_E024</data><data key="edge_operational_context">2018 DMS PIA confirms debtor contact addresses are part of collections program data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R049" source="APP_DMS" target="R125_E025"><data key="edge_relationship_id">R125_R049</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">enforces_privacy_access_controls</data><data key="edge_target_entity_id">R125_E025</data><data key="edge_operational_context">DMS personal information subject to network authentication, access profiles and need-to-know audit controls as of 2018.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R050" source="R125_E024" target="APP_ROAR"><data key="edge_relationship_id">R125_R050</data><data key="edge_source_entity_id">R125_E024</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">2018 PIA cites ROAR-DMS debt and corresponding privacy systems; does not establish that DMS automatically changes MBR or SSR addresses.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R051" source="SYS_MBR" target="R125_E026"><data key="edge_relationship_id">R125_R051</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_complete_record_population_to</data><data key="edge_target_entity_id">R125_E026</data><data key="edge_operational_context">Snapshot Table1 combines 100-percent MBR with 100-percent SSR data to report program overlap without dual entitlement double counts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R052" source="SYS_SSR" target="R125_E026"><data key="edge_relationship_id">R125_R052</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_complete_record_population_to</data><data key="edge_target_entity_id">R125_E026</data><data key="edge_operational_context">Snapshot Table1 also uses 100-percent SSR data; no underlying physical crosswalk is specified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R053" source="SYS_MBR" target="R125_E027"><data key="edge_relationship_id">R125_R053</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_statistical_product</data><data key="edge_target_entity_id">R125_E027</data><data key="edge_operational_context">100-percent MBR source identified explicitly for OASDI monthly snapshot Table2.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R054" source="SYS_SSR" target="R125_E028"><data key="edge_relationship_id">R125_R054</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for_statistical_product</data><data key="edge_target_entity_id">R125_E028</data><data key="edge_operational_context">100-percent SSR source identified explicitly for SSI monthly snapshot Table3.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R055" source="R125_E026" target="R125_E029"><data key="edge_relationship_id">R125_R055</data><data key="edge_source_entity_id">R125_E026</data><data key="edge_relationship_type">applies_person_count_rule</data><data key="edge_target_entity_id">R125_E029</data><data key="edge_operational_context">A person dually entitled on TitleII primary and secondary records appears once in program population count.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R056" source="R125_E026" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R125_R056</data><data key="edge_source_entity_id">R125_E026</data><data key="edge_relationship_type">is_versioned_issue_of</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">August2026 values were released September2026; archive distinguishes issue from recurring product.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R057" source="R125_E027" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R125_R057</data><data key="edge_source_entity_id">R125_E027</data><data key="edge_relationship_type">is_versioned_issue_of</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">August2026 TitleII benefit aggregates are Table2 in the recurring snapshot.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R058" source="R125_E028" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R125_R058</data><data key="edge_source_entity_id">R125_E028</data><data key="edge_relationship_type">is_versioned_issue_of</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">August2026 SSI aggregate figures are Table3 in the recurring snapshot.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R059" source="APP_SSNAP" target="R125_E030"><data key="edge_relationship_id">R125_R059</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">implements_keying_error_rule</data><data key="edge_target_entity_id">R125_E030</data><data key="edge_operational_context">SSNAP NCP is allowed with documented error from original SS5 or qualified enumeration partner evidence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R060" source="R125_E030" target="SYS_NUMIDENT"><data key="edge_relationship_id">R125_R060</data><data key="edge_source_entity_id">R125_E030</data><data key="edge_relationship_type">corrects_iteration_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Keying-error correction can change existing Numident iteration when supported, rather than making a new iteration.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R061" source="APP_IRON" target="R125_E030"><data key="edge_relationship_id">R125_R061</data><data key="edge_source_entity_id">APP_IRON</data><data key="edge_relationship_type">supports_document_review_for</data><data key="edge_target_entity_id">R125_E030</data><data key="edge_operational_context">IRON holds retrievable original SS5 images/microprints used to prove original keying-error claims.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R062" source="APP_SS5_REPRINTS" target="R125_E030"><data key="edge_relationship_id">R125_R062</data><data key="edge_source_entity_id">APP_SS5_REPRINTS</data><data key="edge_relationship_type">supports_document_review_for</data><data key="edge_target_entity_id">R125_E030</data><data key="edge_operational_context">SS5 Reprints can provide historical original application evidence for keying-error review.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R063" source="APP_SSNAP" target="R125_E031"><data key="edge_relationship_id">R125_R063</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">implements_iteration_rule</data><data key="edge_target_entity_id">R125_E031</data><data key="edge_operational_context">SSNAP enters documented new application iteration when keying error cannot be established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R064" source="R125_E031" target="SYS_NUMIDENT"><data key="edge_relationship_id">R125_R064</data><data key="edge_source_entity_id">R125_E031</data><data key="edge_relationship_type">appends_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">No unproven original-value overwrite: new iteration preserves older value as history.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R065" source="R125_E032" target="SYS_MBR"><data key="edge_relationship_id">R125_R065</data><data key="edge_source_entity_id">R125_E032</data><data key="edge_relationship_type">requires_review_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Parent name correction requires separate review/action on Title II information when parent is a beneficiary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R066" source="R125_E032" target="SYS_SSR"><data key="edge_relationship_id">R125_R066</data><data key="edge_source_entity_id">R125_E032</data><data key="edge_relationship_type">requires_review_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Parent name correction may require separate SSI record action, not automatic synchronization.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R067" source="R125_E032" target="APP_ERPS"><data key="edge_relationship_id">R125_R067</data><data key="edge_source_entity_id">R125_E032</data><data key="edge_relationship_type">requires_review_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">RPS payee records may require separate processing; canonical eRPS app context used only to identify payee business function.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R068" source="SYS_NUMIDENT" target="R125_E032"><data key="edge_relationship_id">R125_R068</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">may_trigger_manual_related_record_action</data><data key="edge_target_entity_id">R125_E032</data><data key="edge_operational_context">Numident parent-name correction does not itself prove all benefit or payee records synchronize automatically.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R125_R069" source="ORG_SSA_OAG" target="R125_E033"><data key="edge_relationship_id">R125_R069</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">publishes_forecast_website_for</data><data key="edge_target_entity_id">R125_E033</data><data key="edge_operational_context">OAG-linked OSDBU page publishes FY2026 projected contracting opportunities for vendors, including prospective small-business subcontracting opportunities.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes">Claim is limited to the documented operational context; no unsupported physical implementation inferred.</data></edge><edge id="R126_REL001" source="R126_E002" target="R126_E001"><data key="edge_relationship_id">R126_REL001</data><data key="edge_source_entity_id">R126_E002</data><data key="edge_relationship_type">submitted_through</data><data key="edge_target_entity_id">R126_E001</data><data key="edge_operational_context">SSA technicians open and submit New vital-record requests through Vital Records Request application.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL002" source="R126_E002" target="R126_E003"><data key="edge_relationship_id">R126_REL002</data><data key="edge_source_entity_id">R126_E002</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">R126_E003</data><data key="edge_operational_context">Submission form captures recipient identifying information, record type, purpose, ID and record custodian.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL003" source="R126_E001" target="R126_E004"><data key="edge_relationship_id">R126_REL003</data><data key="edge_source_entity_id">R126_E001</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">R126_E004</data><data key="edge_operational_context">SSA Travel Team updates statuses Requested, Ordered and Received for office visibility.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL004" source="R126_E001" target="R126_E005"><data key="edge_relationship_id">R126_REL004</data><data key="edge_source_entity_id">R126_E001</data><data key="edge_relationship_type">centrally_holds</data><data key="edge_target_entity_id">R126_E005</data><data key="edge_operational_context">Vital-records documentation and correspondence stored on VRR site with agency recordkeeping rules.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL005" source="R126_E003" target="R126_E006"><data key="edge_relationship_id">R126_REL005</data><data key="edge_source_entity_id">R126_E003</data><data key="edge_relationship_type">contains_external_partner_address</data><data key="edge_target_entity_id">R126_E006</data><data key="edge_operational_context">Custodian agency postal address is submitted as external agency contact; no beneficiary address update documented.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL006" source="R126_E002" target="R126_E007"><data key="edge_relationship_id">R126_REL006</data><data key="edge_source_entity_id">R126_E002</data><data key="edge_relationship_type">reviewed_and_ordered_by</data><data key="edge_target_entity_id">R126_E007</data><data key="edge_operational_context">Travel Team reviews submission completeness and places state/local requests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL007" source="R126_E002" target="R126_E009"><data key="edge_relationship_id">R126_REL007</data><data key="edge_source_entity_id">R126_E002</data><data key="edge_relationship_type">uses_preferred_payment_route</data><data key="edge_target_entity_id">R126_E009</data><data key="edge_operational_context">SmartPay purchase card preferred when permitted by State and SSA has access.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL008" source="R126_E002" target="R126_E008"><data key="edge_relationship_id">R126_REL008</data><data key="edge_source_entity_id">R126_E002</data><data key="edge_relationship_type">uses_exception_payment_team</data><data key="edge_target_entity_id">R126_E008</data><data key="edge_operational_context">If alternatives unavailable Internal Control Payment Team requests a Treasury check.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL009" source="R126_E002" target="R126_E010"><data key="edge_relationship_id">R126_REL009</data><data key="edge_source_entity_id">R126_E002</data><data key="edge_relationship_type">obeys</data><data key="edge_target_entity_id">R126_E010</data><data key="edge_operational_context">Paper checks through TPPS discontinued for vital records as of February 9, 2026.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL010" source="R126_E010" target="APP_TPPS"><data key="edge_relationship_id">R126_REL010</data><data key="edge_source_entity_id">R126_E010</data><data key="edge_relationship_type">ends_paper_check_issuance_for</data><data key="edge_target_entity_id">APP_TPPS</data><data key="edge_operational_context">SSA TPPS prior paper-check path for vital-record purchases ceased February 9, 2026; TPPS other functions not necessarily discontinued.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL011" source="R126_E002" target="ORG_STATE_BVS"><data key="edge_relationship_id">R126_REL011</data><data key="edge_source_entity_id">R126_E002</data><data key="edge_relationship_type">requests_certification_from</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">The vital-record custodian sends requested certificates directly to the SSA office, without establishing electronic transmission.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL012" source="R126_E007" target="R126_E001"><data key="edge_relationship_id">R126_REL012</data><data key="edge_source_entity_id">R126_E007</data><data key="edge_relationship_type">tracks_via</data><data key="edge_target_entity_id">R126_E001</data><data key="edge_operational_context">Travel Team keeps Requested/Ordered/Received status available to requesting offices.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL013" source="R126_E003" target="R126_E006"><data key="edge_relationship_id">R126_REL013</data><data key="edge_source_entity_id">R126_E003</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R126_E006</data><data key="edge_operational_context">Form captures state vital-record agency name/address; contact provenance remains external custodian.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL014" source="R126_E012" target="R126_E011"><data key="edge_relationship_id">R126_REL014</data><data key="edge_source_entity_id">R126_E012</data><data key="edge_relationship_type">version_of</data><data key="edge_target_entity_id">R126_E011</data><data key="edge_operational_context">SSA OACT calls released 2026.2 version the current Detailed Calculator.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL015" source="R126_E012" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R126_REL015</data><data key="edge_source_entity_id">R126_E012</data><data key="edge_relationship_type">uses_updated_assumptions_from</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Calculator 2026.2 updates projected benefit/average wage assumptions using 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL016" source="R126_E011" target="R126_E015"><data key="edge_relationship_id">R126_REL016</data><data key="edge_source_entity_id">R126_E011</data><data key="edge_relationship_type">accepts_user_supplied</data><data key="edge_target_entity_id">R126_E015</data><data key="edge_operational_context">The public estimator takes earnings and beneficiary characteristics supplied for each case; not an automatic MBR/MEF lookup.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL017" source="R126_E011" target="R126_E014"><data key="edge_relationship_id">R126_REL017</data><data key="edge_source_entity_id">R126_E011</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R126_E014</data><data key="edge_operational_context">OACT describes public outputs including PIA, maximum family benefit and estimated monthly benefit.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL018" source="R126_E011" target="R126_E013"><data key="edge_relationship_id">R126_REL018</data><data key="edge_source_entity_id">R126_E011</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R126_E013</data><data key="edge_operational_context">Historic constants and prospective assumption sets drive estimated benefits; manual constants update does not refresh stored projections.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL019" source="R126_E016" target="R126_E011"><data key="edge_relationship_id">R126_REL019</data><data key="edge_source_entity_id">R126_E016</data><data key="edge_relationship_type">documents_public_implementation_of</data><data key="edge_target_entity_id">R126_E011</data><data key="edge_operational_context">Public source documents source layout for standalone detailed calculator, not agency production calculation engines.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL020" source="R126_E016" target="R126_E017"><data key="edge_relationship_id">R126_REL020</data><data key="edge_source_entity_id">R126_E016</data><data key="edge_relationship_type">requires_library_for_build</data><data key="edge_target_entity_id">R126_E017</data><data key="edge_operational_context">OACT source docs identify Boost C++ library versions for public code.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL021" source="R126_E018" target="R126_E011"><data key="edge_relationship_id">R126_REL021</data><data key="edge_source_entity_id">R126_E018</data><data key="edge_relationship_type">builds_windows_distribution_of</data><data key="edge_target_entity_id">R126_E011</data><data key="edge_operational_context">SSA documentation identifies Windows source compiled with Microsoft Visual C/C++ 2022.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL022" source="R126_E019" target="R126_E011"><data key="edge_relationship_id">R126_REL022</data><data key="edge_source_entity_id">R126_E019</data><data key="edge_relationship_type">is_historical_variant_of</data><data key="edge_target_entity_id">R126_E011</data><data key="edge_operational_context">OACT says legacy Fortran public calculator not updated for some years; current C++ is distributed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL023" source="R126_E020" target="R126_E015"><data key="edge_relationship_id">R126_REL023</data><data key="edge_source_entity_id">R126_E020</data><data key="edge_relationship_type">batch_calculates_using</data><data key="edge_target_entity_id">R126_E015</data><data key="edge_operational_context">anypiab reads multiple records from single .pia case file.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL024" source="R126_E021" target="R126_E015"><data key="edge_relationship_id">R126_REL024</data><data key="edge_source_entity_id">R126_E021</data><data key="edge_relationship_type">batch_calculates_using</data><data key="edge_target_entity_id">R126_E015</data><data key="edge_operational_context">anypiac reads multiple individual .pia case files using a list-of-files input.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL025" source="R126_E020" target="R126_E022"><data key="edge_relationship_id">R126_REL025</data><data key="edge_source_entity_id">R126_E020</data><data key="edge_relationship_type">writes</data><data key="edge_target_entity_id">R126_E022</data><data key="edge_operational_context">OACT batch documentation explicitly names output file OUTPUT and benefit computation fields.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL026" source="R126_E021" target="R126_E022"><data key="edge_relationship_id">R126_REL026</data><data key="edge_source_entity_id">R126_E021</data><data key="edge_relationship_type">writes</data><data key="edge_target_entity_id">R126_E022</data><data key="edge_operational_context">OACT says anypiac produces the same status and output fields as anypiab.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL027" source="R126_E020" target="R126_E016"><data key="edge_relationship_id">R126_REL027</data><data key="edge_source_entity_id">R126_E020</data><data key="edge_relationship_type">shares_calculation_code_with</data><data key="edge_target_entity_id">R126_E016</data><data key="edge_operational_context">OACT identifies anypiab C++ console project using its Windows calculation libraries.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL028" source="R126_E023" target="R126_E025"><data key="edge_relationship_id">R126_REL028</data><data key="edge_source_entity_id">R126_E023</data><data key="edge_relationship_type">requires_followup_processing</data><data key="edge_target_entity_id">R126_E025</data><data key="edge_operational_context">DDS cannot directly input S1 denial; FO must post after DDS returns claim.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL029" source="R126_E024" target="R126_E025"><data key="edge_relationship_id">R126_REL029</data><data key="edge_source_entity_id">R126_E024</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R126_E025</data><data key="edge_operational_context">SSA-831-U3 item 35 S1 informs FO to process MCS EC or MACADE.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL030" source="R126_E025" target="APP_MCS"><data key="edge_relationship_id">R126_REL030</data><data key="edge_source_entity_id">R126_E025</data><data key="edge_relationship_type">attempts_posting_via</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS Earnings Computation used for S1 denial when possible.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL031" source="R126_E025" target="APP_MACADE"><data key="edge_relationship_id">R126_REL031</data><data key="edge_source_entity_id">R126_E025</data><data key="edge_relationship_type">uses_fallback</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">FO uses MACADE for S1 when MCS Earnings Computation cannot process.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL032" source="R126_E026" target="APP_POS"><data key="edge_relationship_id">R126_REL032</data><data key="edge_source_entity_id">R126_E026</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">POMS directs POS CDB conversion for some aged 17-18 non-exception circumstances, but concurrent SSI requires PC manual handling.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL033" source="R126_E027" target="R126_E028"><data key="edge_relationship_id">R126_REL033</data><data key="edge_source_entity_id">R126_E027</data><data key="edge_relationship_type">requests</data><data key="edge_target_entity_id">R126_E028</data><data key="edge_operational_context">DOS Passport Vital Records Section supplies consular birth evidence for qualifying requests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL034" source="R126_E027" target="R126_E029"><data key="edge_relationship_id">R126_REL034</data><data key="edge_source_entity_id">R126_E027</data><data key="edge_relationship_type">requests</data><data key="edge_target_entity_id">R126_E029</data><data key="edge_operational_context">DOS Passport Vital Records Section supplies death evidence for qualifying requests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL035" source="R126_E027" target="R126_E030"><data key="edge_relationship_id">R126_REL035</data><data key="edge_source_entity_id">R126_E027</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R126_E030</data><data key="edge_operational_context">Qualifying no-fee official SSA evidence is marked restricted government use.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL036" source="R126_E028" target="R126_E030"><data key="edge_relationship_id">R126_REL036</data><data key="edge_source_entity_id">R126_E028</data><data key="edge_relationship_type">may_have</data><data key="edge_target_entity_id">R126_E030</data><data key="edge_operational_context">SSA POMS identifies restricted marking when obtained under Government Use Only request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL037" source="R126_E029" target="R126_E030"><data key="edge_relationship_id">R126_REL037</data><data key="edge_source_entity_id">R126_E029</data><data key="edge_relationship_type">may_have</data><data key="edge_target_entity_id">R126_E030</data><data key="edge_operational_context">SSA POMS identifies restricted marking when obtained under Government Use Only request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R126_REL038" source="R126_E027" target="R126_E002"><data key="edge_relationship_id">R126_REL038</data><data key="edge_source_entity_id">R126_E027</data><data key="edge_relationship_type">complements_vital_records_procurement</data><data key="edge_target_entity_id">R126_E002</data><data key="edge_operational_context">DOS consular vital-record evidence is separate jurisdictional pathway; do not infer that VRR universally handles all DOS requests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R126_REL039" source="R126_E031" target="SYS_NUMIDENT"><data key="edge_relationship_id">R126_REL039</data><data key="edge_source_entity_id">R126_E031</data><data key="edge_relationship_type">does_not_establish_new_master_record</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Commemorative card presentation is not evidence of change to Numident identity master.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R001" source="R127_E001" target="R127_E002"><data key="edge_relationship_id">R127_R001</data><data key="edge_source_entity_id">R127_E001</data><data key="edge_relationship_type">computes_from_assumed_earnings</data><data key="edge_target_entity_id">R127_E002</data><data key="edge_operational_context">Quick Calculator explicitly does not access the individual Social Security earnings record; benefit estimate is rough.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R002" source="R127_E001" target="SYS_MEF"><data key="edge_relationship_id">R127_R002</data><data key="edge_source_entity_id">R127_E001</data><data key="edge_relationship_type">is_separate_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">No authenticated direct MEF retrieval is established by the public calculator documentation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R003" source="R127_E003" target="R127_E004"><data key="edge_relationship_id">R127_R003</data><data key="edge_source_entity_id">R127_E003</data><data key="edge_relationship_type">requires_user_supplied</data><data key="edge_target_entity_id">R127_E004</data><data key="edge_operational_context">Benefit Calculators page distinguishes Online Calculator from authenticated my Social Security estimate by requiring the user to enter earnings.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R004" source="R127_E003" target="R127_E001"><data key="edge_relationship_id">R127_R004</data><data key="edge_source_entity_id">R127_E003</data><data key="edge_relationship_type">is_alternative_to</data><data key="edge_target_entity_id">R127_E001</data><data key="edge_operational_context">Different public estimation workflows; do not assume common computation infrastructure.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R005" source="R127_E003" target="SYS_MEF"><data key="edge_relationship_id">R127_R005</data><data key="edge_source_entity_id">R127_E003</data><data key="edge_relationship_type">is_separate_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Calculator page documents user-entered earnings, not MEF lookup.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R006" source="R127_E005" target="R127_E006"><data key="edge_relationship_id">R127_R006</data><data key="edge_source_entity_id">R127_E005</data><data key="edge_relationship_type">produces_estimate</data><data key="edge_target_entity_id">R127_E006</data><data key="edge_operational_context">Public input and life expectancy result; no personal claims record retrieval documented.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R007" source="R127_E007" target="R127_E008"><data key="edge_relationship_id">R127_R007</data><data key="edge_source_entity_id">R127_E007</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R127_E008</data><data key="edge_operational_context">SSA public indexing-factor tables are calculated/published by eligibility year.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R008" source="R127_E008" target="DATA_AWI_SERIES"><data key="edge_relationship_id">R127_R008</data><data key="edge_source_entity_id">R127_E008</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">DATA_AWI_SERIES</data><data key="edge_operational_context">Factors use the national average wage indexing series under benefit-computation indexing rules.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R009" source="R127_E008" target="PROC_AWI_CALC"><data key="edge_relationship_id">R127_R009</data><data key="edge_source_entity_id">R127_E008</data><data key="edge_relationship_type">relates_to</data><data key="edge_target_entity_id">PROC_AWI_CALC</data><data key="edge_operational_context">Published factors are statistical output; do not infer production runtime system.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R010" source="R127_E009" target="R127_E001"><data key="edge_relationship_id">R127_R010</data><data key="edge_source_entity_id">R127_E009</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R127_E001</data><data key="edge_operational_context">Quick Calculator uses estimated prior earnings rather than official user earnings.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R011" source="R127_E009" target="R127_E003"><data key="edge_relationship_id">R127_R011</data><data key="edge_source_entity_id">R127_E009</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R127_E003</data><data key="edge_operational_context">Online Calculator needs manually entered annual earnings.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R012" source="R127_E009" target="APP_MYSSA"><data key="edge_relationship_id">R127_R012</data><data key="edge_source_entity_id">R127_E009</data><data key="edge_relationship_type">contrasts_with</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">my Social Security Retirement Estimate uses a separately authenticated account channel; do not attribute that access to public calculators.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R013" source="R127_E010" target="R127_E011"><data key="edge_relationship_id">R127_R013</data><data key="edge_source_entity_id">R127_E010</data><data key="edge_relationship_type">sets_fee_for</data><data key="edge_target_entity_id">R127_E011</data><data key="edge_operational_context">New $22 fee for computer extract of SS-5 Numident record, requests received on or after 2026-10-01.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R014" source="R127_E010" target="R127_E012"><data key="edge_relationship_id">R127_R014</data><data key="edge_source_entity_id">R127_E010</data><data key="edge_relationship_type">sets_fee_for</data><data key="edge_target_entity_id">R127_E012</data><data key="edge_operational_context">New $23 fee for copy of original SS-5, requests received on or after 2026-10-01.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R015" source="R127_E011" target="SYS_NUMIDENT"><data key="edge_relationship_id">R127_R015</data><data key="edge_source_entity_id">R127_E011</data><data key="edge_relationship_type">derives_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Computer extract is based on the Numident SS-5 electronic record; not a master record update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R016" source="R127_E012" target="FORM_SS5"><data key="edge_relationship_id">R127_R016</data><data key="edge_source_entity_id">R127_E012</data><data key="edge_relationship_type">documents_form</data><data key="edge_target_entity_id">FORM_SS5</data><data key="edge_operational_context">Original application copy provided under applicable request controls.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R017" source="FORM_SSA711" target="R127_E011"><data key="edge_relationship_id">R127_R017</data><data key="edge_source_entity_id">FORM_SSA711</data><data key="edge_relationship_type">requests_disclosure_of</data><data key="edge_target_entity_id">R127_E011</data><data key="edge_operational_context">The SSA-711 deceased-person record request can request Numident record; disclosure restrictions apply.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R018" source="R127_E013" target="R113_E030"><data key="edge_relationship_id">R127_R018</data><data key="edge_source_entity_id">R127_E013</data><data key="edge_relationship_type">provided_through</data><data key="edge_target_entity_id">R113_E030</data><data key="edge_operational_context">Form SSA-7050 paid detailed yearly earnings disclosure includes employer name/address; $49 per request as of Oct 1 2026.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R019" source="R127_E013" target="APP_MYSSA"><data key="edge_relationship_id">R127_R019</data><data key="edge_source_entity_id">R127_E013</data><data key="edge_relationship_type">differs_from</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Free online Social Security Statement shows yearly earnings but no employer information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R020" source="R127_E013" target="SYS_MBR"><data key="edge_relationship_id">R127_R020</data><data key="edge_source_entity_id">R127_E013</data><data key="edge_relationship_type">is_not_equivalent_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Employer business address from detailed earnings disclosure is not beneficiary mailing/residence address and does not update MBR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R021" source="R127_E010" target="R113_E030"><data key="edge_relationship_id">R127_R021</data><data key="edge_source_entity_id">R127_E010</data><data key="edge_relationship_type">covers</data><data key="edge_target_entity_id">R113_E030</data><data key="edge_operational_context">Detailed yearly earnings information $49 plus $30 optional certification, not free yearly totals.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R022" source="R127_E014" target="FORM_SSA711"><data key="edge_relationship_id">R127_R022</data><data key="edge_source_entity_id">R127_E014</data><data key="edge_relationship_type">accepts</data><data key="edge_target_entity_id">FORM_SSA711</data><data key="edge_operational_context">SSA-711 route for deceased-person SS-5 and Numident records; identity, authority, age and fees considered.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R023" source="R127_E014" target="APP_FOIAXPRESS_PAL"><data key="edge_relationship_id">R127_R023</data><data key="edge_source_entity_id">R127_E014</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_FOIAXPRESS_PAL</data><data key="edge_operational_context">Public Access Link provides FOIA online request route.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R024" source="R127_E014" target="R127_E011"><data key="edge_relationship_id">R127_R024</data><data key="edge_source_entity_id">R127_E014</data><data key="edge_relationship_type">retrieves_copy_of</data><data key="edge_target_entity_id">R127_E011</data><data key="edge_operational_context">May issue SS-5 computer extract under authorized request; disclosure-only copy.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R025" source="R127_E014" target="R127_E012"><data key="edge_relationship_id">R127_R025</data><data key="edge_source_entity_id">R127_E014</data><data key="edge_relationship_type">retrieves_copy_of</data><data key="edge_target_entity_id">R127_E012</data><data key="edge_operational_context">May issue SS-5 original application copy under authorized request; disclosure-only copy.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R026" source="APP_RASR" target="R127_E015"><data key="edge_relationship_id">R127_R026</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">is_subject_to</data><data key="edge_target_entity_id">R127_E015</data><data key="edge_operational_context">Two individual cases under same SSN cannot both be entered in RASR; MCS/MSSICS case-specific updates required.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R027" source="R127_E015" target="APP_MCS"><data key="edge_relationship_id">R127_R027</data><data key="edge_source_entity_id">R127_E015</data><data key="edge_relationship_type">uses_alternative</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Staff must enter the correct representative for simultaneous cases in MCS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R028" source="R127_E015" target="APP_MSSICS"><data key="edge_relationship_id">R127_R028</data><data key="edge_source_entity_id">R127_E015</data><data key="edge_relationship_type">uses_alternative</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Staff must enter the correct representative for simultaneous cases in MSSICS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R029" source="R127_E016" target="R116_E019"><data key="edge_relationship_id">R127_R029</data><data key="edge_source_entity_id">R127_E016</data><data key="edge_relationship_type">scopes_to</data><data key="edge_target_entity_id">R116_E019</data><data key="edge_operational_context">New claim does not inherit appointment; requires properly executed appointment for that particular case.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R030" source="R127_E016" target="R106_E009"><data key="edge_relationship_id">R127_R030</data><data key="edge_source_entity_id">R127_E016</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R106_E009</data><data key="edge_operational_context">SSA-1696 establishes representation for the new claim.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R031" source="R127_E017" target="APP_EDCS"><data key="edge_relationship_id">R127_R031</data><data key="edge_source_entity_id">R127_E017</data><data key="edge_relationship_type">annotates</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">FO ensures Representative Involved flag on EDCS electronic folder when applicable; conditional UAT if not propagated.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R032" source="APP_RASR" target="R127_E017"><data key="edge_relationship_id">R127_R032</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">requires_downstream_reconciliation</data><data key="edge_target_entity_id">R127_E017</data><data key="edge_operational_context">Technicians must confirm EDCS flag; automatic update not guaranteed after jurisdiction transfer.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R033" source="R127_E017" target="DATA_EDCS_UAT_ALERT"><data key="edge_relationship_id">R127_R033</data><data key="edge_source_entity_id">R127_E017</data><data key="edge_relationship_type">can_require</data><data key="edge_target_entity_id">DATA_EDCS_UAT_ALERT</data><data key="edge_operational_context">For reconsideration/hearing jurisdiction transfer, update-after-transfer can be necessary when flag does not update automatically.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R034" source="APP_RASR" target="APP_MCS"><data key="edge_relationship_id">R127_R034</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">requires_downstream_reconciliation</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Staff check applicable MCS representative info screens at adjudication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R035" source="APP_RASR" target="APP_MSSICS"><data key="edge_relationship_id">R127_R035</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">requires_downstream_reconciliation</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Staff check applicable MSSICS representative info screens at adjudication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R036" source="R127_E018" target="UI_RASR_ROC"><data key="edge_relationship_id">R127_R036</data><data key="edge_source_entity_id">R127_E018</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">UI_RASR_ROC</data><data key="edge_operational_context">Claimant choice of principal representative recorded via RASR report of contact or updated signed SSA-1696.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R037" source="R127_E018" target="APP_RASR"><data key="edge_relationship_id">R127_R037</data><data key="edge_source_entity_id">R127_E018</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Notice targeting does not revoke other co-representatives.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R038" source="APP_RASR" target="R127_E019"><data key="edge_relationship_id">R127_R038</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">fallback_when_address_missing</data><data key="edge_target_entity_id">R127_E019</data><data key="edge_operational_context">SSA documents RASR acknowledgment failure caused by missing claimant address; manual correspondence required.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R039" source="R127_E019" target="APP_DPS"><data key="edge_relationship_id">R127_R039</data><data key="edge_source_entity_id">R127_E019</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Manual acknowledgment notice through Document Processing System when RASR fails.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R040" source="R127_E019" target="APP_AURORA"><data key="edge_relationship_id">R127_R040</data><data key="edge_source_entity_id">R127_E019</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_AURORA</data><data key="edge_operational_context">Manual notice also accessible via Manage Text/AURORA.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R041" source="R127_E020" target="APP_RASR"><data key="edge_relationship_id">R127_R041</data><data key="edge_source_entity_id">R127_E020</data><data key="edge_relationship_type">generated_by</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Automated notification RSR120 after valid assignment option.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R042" source="R127_E020" target="APP_DPS"><data key="edge_relationship_id">R127_R042</data><data key="edge_source_entity_id">R127_E020</data><data key="edge_relationship_type">manual_fallback_via</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Failed fee assignment prompts manual DPS notice; does not invalidate otherwise proper representation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R043" source="R127_E020" target="FORM_R96_SSA1699"><data key="edge_relationship_id">R127_R043</data><data key="edge_source_entity_id">R127_E020</data><data key="edge_relationship_type">uses_registration</data><data key="edge_target_entity_id">FORM_R96_SSA1699</data><data key="edge_operational_context">Representative must affiliate with fee entity using SSA-1699 and provide appropriate EIN on SSA-1696.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R044" source="R127_E020" target="R116_E019"><data key="edge_relationship_id">R127_R044</data><data key="edge_source_entity_id">R127_E020</data><data key="edge_relationship_type">does_not_equate_to</data><data key="edge_target_entity_id">R116_E019</data><data key="edge_operational_context">Fee-assignment entity affiliation is different from who is the authorized human representative for a claim.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R045" source="SYS_MBR" target="R127_E021"><data key="edge_relationship_id">R127_R045</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">stores_attribute</data><data key="edge_target_entity_id">R127_E021</data><data key="edge_operational_context">SID line can diverge from actual SSR SSI current-pay state.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R046" source="SYS_SSR" target="R127_E021"><data key="edge_relationship_id">R127_R046</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">can_correct</data><data key="edge_target_entity_id">R127_E021</data><data key="edge_operational_context">Documented forced finder Type M offline query can propagate SSI status to MBR SID if identifying data consistent; requires follow-up confirmation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R047" source="R127_E021" target="R127_E022"><data key="edge_relationship_id">R127_R047</data><data key="edge_source_entity_id">R127_E021</data><data key="edge_relationship_type">triggers_conditional_update</data><data key="edge_target_entity_id">R127_E022</data><data key="edge_operational_context">In auto-accrete states, change to MBR SID updates Third Party Master record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R048" source="PROC_SSR_MBR_FORCE_FINDER" target="R127_E021"><data key="edge_relationship_id">R127_R048</data><data key="edge_source_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="edge_relationship_type">updates_conditional</data><data key="edge_target_entity_id">R127_E021</data><data key="edge_operational_context">Forced finder only succeeds when MBR and SSR identifying data are consistent.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R049" source="R127_E021" target="R127_E023"><data key="edge_relationship_id">R127_R049</data><data key="edge_source_entity_id">R127_E021</data><data key="edge_relationship_type">produces_status_alert</data><data key="edge_target_entity_id">R127_E023</data><data key="edge_operational_context">In alert states SID changes must be reflected before state obtains SSI accretion/deletion alert for coverage decision.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R050" source="R127_E022" target="APP_TPS_BUYIN"><data key="edge_relationship_id">R127_R050</data><data key="edge_source_entity_id">R127_E022</data><data key="edge_relationship_type">is_processed_by</data><data key="edge_target_entity_id">APP_TPS_BUYIN</data><data key="edge_operational_context">Third Party System handles state buy-in downstream of validated MBR/SID changes; do not infer real-time sync.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R051" source="TXN_TYPE_M_OFFLINE_QUERY" target="PROC_SSR_MBR_FORCE_FINDER"><data key="edge_relationship_id">R127_R051</data><data key="edge_source_entity_id">TXN_TYPE_M_OFFLINE_QUERY</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="edge_operational_context">Type M offline query can force SSR finder to update MBR SID when identifiers match.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R052" source="R127_E024" target="R127_E021"><data key="edge_relationship_id">R127_R052</data><data key="edge_source_entity_id">R127_E024</data><data key="edge_relationship_type">verifies</data><data key="edge_target_entity_id">R127_E021</data><data key="edge_operational_context">Initial MBR readback approximately 14 days after forced finder; failure requires HQ correction escalation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R053" source="R127_E024" target="R127_E022"><data key="edge_relationship_id">R127_R053</data><data key="edge_source_entity_id">R127_E024</data><data key="edge_relationship_type">verifies</data><data key="edge_target_entity_id">R127_E022</data><data key="edge_operational_context">For auto-accrete state, diary 60 days after SID update and recheck Third Party line; forward to PC if wrong.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R054" source="R127_E024" target="PROC_SSR_MBR_FORCE_FINDER"><data key="edge_relationship_id">R127_R054</data><data key="edge_source_entity_id">R127_E024</data><data key="edge_relationship_type">requires_manual_follow_up</data><data key="edge_target_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="edge_operational_context">Identifying mismatch yields exception; automation not guaranteed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R055" source="R127_E025" target="UI_MSSICS_DIRS"><data key="edge_relationship_id">R127_R055</data><data key="edge_source_entity_id">R127_E025</data><data key="edge_relationship_type">relates_to</data><data key="edge_target_entity_id">UI_MSSICS_DIRS</data><data key="edge_operational_context">Development of IRS information in SSI proceedings uses dated evidence; not automatic change to SSR addresses.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R056" source="R127_E025" target="SYS_SSR"><data key="edge_relationship_id">R127_R056</data><data key="edge_source_entity_id">R127_E025</data><data key="edge_relationship_type">does_not_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">IRS 5B alert is a development/reopening signal; benefit-record changes require applicable adjudication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R057" source="R127_E026" target="SYS_MBR"><data key="edge_relationship_id">R127_R057</data><data key="edge_source_entity_id">R127_E026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Publication states MBR is principal administrative source and includes only people whose OASDI benefits are currently payable.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R058" source="R127_E026" target="APP_DOORS"><data key="edge_relationship_id">R127_R058</data><data key="edge_source_entity_id">R127_E026</data><data key="edge_relationship_type">uses_geography</data><data key="edge_target_entity_id">APP_DOORS</data><data key="edge_operational_context">DOORS maps field offices to ZIP Codes for published tables; office area may span states.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R127_R059" source="R127_E026" target="R127_E027"><data key="edge_relationship_id">R127_R059</data><data key="edge_source_entity_id">R127_E026</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R127_E027</data><data key="edge_operational_context">2023 published counts use controlled rounding and small cell suppression; not exact counts for small geographic cells.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R001" source="R128_E002" target="SYS_SSR"><data key="edge_relationship_id">R128_R001</data><data key="edge_source_entity_id">R128_E002</data><data key="edge_relationship_type">is_snapshot_extracted_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">CER is a monthly snapshot extracted from SSR, not a live SSR replica; later corrections do not revise earlier CER snapshots.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R002" source="R128_E003" target="SYS_MBR"><data key="edge_relationship_id">R128_R002</data><data key="edge_source_entity_id">R128_E003</data><data key="edge_relationship_type">is_snapshot_extracted_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">DBAD is a monthly snapshot extracted from MBR and is not retroactively rewritten.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R003" source="R128_E004" target="SYS_SSR"><data key="edge_relationship_id">R128_R003</data><data key="edge_source_entity_id">R128_E004</data><data key="edge_relationship_type">derives_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI Longitudinal File derives program, payment, demographic and earnings history from SSR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R004" source="R128_E005" target="SYS_SSR"><data key="edge_relationship_id">R128_R004</data><data key="edge_source_entity_id">R128_E005</data><data key="edge_relationship_type">is_custom_extract_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">DAF22 separately extracts SSR wage data for research compilation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R005" source="R128_E006" target="SYS_SSR"><data key="edge_relationship_id">R128_R005</data><data key="edge_source_entity_id">R128_E006</data><data key="edge_relationship_type">is_custom_extract_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">DAF22 separately extracts SSR additional variables not included in core longitudinal file.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R006" source="R128_E002" target="R128_E010"><data key="edge_relationship_id">R128_R006</data><data key="edge_source_entity_id">R128_E002</data><data key="edge_relationship_type">contains_historical_address_attribute</data><data key="edge_target_entity_id">R128_E010</data><data key="edge_operational_context">CER includes an address at snapshot time; subsequent address changes may not appear retrospectively.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R007" source="R128_E010" target="SYS_SSR"><data key="edge_relationship_id">R128_R007</data><data key="edge_source_entity_id">R128_E010</data><data key="edge_relationship_type">does_not_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Historical research copy has no documented reverse update into authoritative SSR; no downstream address update inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R008" source="R128_E007" target="R128_E001"><data key="edge_relationship_id">R128_R008</data><data key="edge_source_entity_id">R128_E007</data><data key="edge_relationship_type">contributes_disability_decisions_to</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">DAF22 consumes annual 831 initial disability records; research file does not itself adjudicate claims.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R009" source="R128_E008" target="R128_E001"><data key="edge_relationship_id">R128_R009</data><data key="edge_source_entity_id">R128_E008</data><data key="edge_relationship_type">contributes_medical_CDR_decisions_to</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">DAF22 consumes archived SSA-832/833 medical continuing disability determination events.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R010" source="R128_E004" target="R128_E001"><data key="edge_relationship_id">R128_R010</data><data key="edge_source_entity_id">R128_E004</data><data key="edge_relationship_type">provides_longitudinal_data_to</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">SSA source-file documentation explicitly names SSI-LF as major source to DAF22.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R011" source="R128_E002" target="R128_E001"><data key="edge_relationship_id">R128_R011</data><data key="edge_source_entity_id">R128_E002</data><data key="edge_relationship_type">contributes_population_snapshot_to</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">CER monthly snapshot helps define the SSI population in DAF22.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R012" source="R128_E003" target="R128_E001"><data key="edge_relationship_id">R128_R012</data><data key="edge_source_entity_id">R128_E003</data><data key="edge_relationship_type">contributes_population_snapshot_to</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">DBAD monthly snapshot helps define OASDI disability population in DAF22.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R013" source="R128_E009" target="SYS_MBR"><data key="edge_relationship_id">R128_R013</data><data key="edge_source_entity_id">R128_E009</data><data key="edge_relationship_type">combines_data_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR extracts for DAF include PHUS data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R014" source="R128_E009" target="DB_PHUS"><data key="edge_relationship_id">R128_R014</data><data key="edge_source_entity_id">R128_E009</data><data key="edge_relationship_type">combines_payment_history_from</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">PHUS contains actual disbursement-date and cash payment event records rather than entitlement-only amounts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R015" source="R128_E009" target="R128_E001"><data key="edge_relationship_id">R128_R015</data><data key="edge_source_entity_id">R128_E009</data><data key="edge_relationship_type">feeds_payment_history_to</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">Payment history inputs contribute to the DAF historical benefit construction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R016" source="R128_E011" target="SYS_SSR"><data key="edge_relationship_id">R128_R016</data><data key="edge_source_entity_id">R128_E011</data><data key="edge_relationship_type">identifies_a_person_within</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR PAN holds person SSN, while HUN is the filing key for multi-person SSR records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R017" source="R128_E012" target="SYS_SSR"><data key="edge_relationship_id">R128_R017</data><data key="edge_source_entity_id">R128_E012</data><data key="edge_relationship_type">is_filing_key_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR record may cover eligible couple or child plus parents; record HUN and individual PAN need not match.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R018" source="R128_E013" target="SYS_MBR"><data key="edge_relationship_id">R128_R018</data><data key="edge_source_entity_id">R128_E013</data><data key="edge_relationship_type">is_account_filing_key_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR CAN refers to the worker’s SSN on which entitlement is based, not necessarily auxiliary beneficiary’s own SSN.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R019" source="R128_E014" target="SYS_MBR"><data key="edge_relationship_id">R128_R019</data><data key="edge_source_entity_id">R128_E014</data><data key="edge_relationship_type">identifies_beneficiary_within</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR BOAN refers to each beneficiary’s own SSN in a CAN/BIC record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R020" source="R128_E015" target="DB_DCF"><data key="edge_relationship_id">R128_R020</data><data key="edge_source_entity_id">R128_E015</data><data key="edge_relationship_type">indexes_claimant_within</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">DCF files its person-centred CDR, medical and earnings tables using claimant own SSN.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R021" source="R128_E026" target="DB_DCF"><data key="edge_relationship_id">R128_R021</data><data key="edge_source_entity_id">R128_E026</data><data key="edge_relationship_type">stored_as_related_data_groups_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">DCF grouped records can have one person occurrence or repeated medical/earnings/CDR occurrences.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R022" source="R128_E007" target="R128_E011"><data key="edge_relationship_id">R128_R022</data><data key="edge_source_entity_id">R128_E007</data><data key="edge_relationship_type">uses_program_specific_identifier</data><data key="edge_target_entity_id">R128_E011</data><data key="edge_operational_context">In SSI file 831 identifier represents PAN and BIC A; 2024 research documentation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R023" source="R128_E007" target="R128_E013"><data key="edge_relationship_id">R128_R023</data><data key="edge_source_entity_id">R128_E007</data><data key="edge_relationship_type">uses_program_specific_identifier</data><data key="edge_target_entity_id">R128_E013</data><data key="edge_operational_context">In SSDI file 831 identifier represents CAN and an appropriate BIC; 2024 research documentation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R024" source="R128_E040" target="SYS_NUMIDENT"><data key="edge_relationship_id">R128_R024</data><data key="edge_source_entity_id">R128_E040</data><data key="edge_relationship_type">integrates_source_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Disability Research File annual source construction incorporates Numident identity/demographic data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R025" source="R128_E040" target="SYS_MBR"><data key="edge_relationship_id">R128_R025</data><data key="edge_source_entity_id">R128_E040</data><data key="edge_relationship_type">integrates_source_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II Disability Research File draws on MBR and related administrative data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R026" source="R128_E040" target="SYS_SSR"><data key="edge_relationship_id">R128_R026</data><data key="edge_source_entity_id">R128_E040</data><data key="edge_relationship_type">integrates_source_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI Disability Research File draws on SSR and related administrative data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R027" source="R128_E028" target="R128_E001"><data key="edge_relationship_id">R128_R027</data><data key="edge_source_entity_id">R128_E028</data><data key="edge_relationship_type">produced_historical_research_release</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">SAS/JCL workflow and quality checks build DAF22 for research; not claim adjudication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R028" source="R128_E001" target="R128_E016"><data key="edge_relationship_id">R128_R028</data><data key="edge_source_entity_id">R128_E001</data><data key="edge_relationship_type">contains_component</data><data key="edge_target_entity_id">R128_E016</data><data key="edge_operational_context">DAF22 demographic file is a major source-linked analytical component.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R029" source="R128_E001" target="R128_E017"><data key="edge_relationship_id">R128_R029</data><data key="edge_source_entity_id">R128_E001</data><data key="edge_relationship_type">contains_component</data><data key="edge_target_entity_id">R128_E017</data><data key="edge_operational_context">DAF22 annual records are distributed across annual research files.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R030" source="R128_E001" target="R128_E018"><data key="edge_relationship_id">R128_R030</data><data key="edge_source_entity_id">R128_E001</data><data key="edge_relationship_type">contains_component</data><data key="edge_target_entity_id">R128_E018</data><data key="edge_operational_context">DAF22 ticket component records beneficiary TTW participation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R031" source="R128_E001" target="R128_E019"><data key="edge_relationship_id">R128_R031</data><data key="edge_source_entity_id">R128_E001</data><data key="edge_relationship_type">contains_component</data><data key="edge_target_entity_id">R128_E019</data><data key="edge_operational_context">DAF22 payments component contains EN and state VR reimbursement payment extracts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R032" source="R128_E020" target="R128_E001"><data key="edge_relationship_id">R128_R032</data><data key="edge_source_entity_id">R128_E020</data><data key="edge_relationship_type">is_ten_percent_sample_of</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">DAF22 10% mart selects on documented 8th/9th SSN-position rule; not stratified; rare-subgroup analyses may be biased.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R033" source="R128_E021" target="R128_E016"><data key="edge_relationship_id">R128_R033</data><data key="edge_source_entity_id">R128_E021</data><data key="edge_relationship_type">uses_demographic_variables_from</data><data key="edge_target_entity_id">R128_E016</data><data key="edge_operational_context">Awardee Data Mart contains demographic file variables plus computed first-eligibility/payment timing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R034" source="R128_E021" target="R128_E001"><data key="edge_relationship_id">R128_R034</data><data key="edge_source_entity_id">R128_E021</data><data key="edge_relationship_type">is_award_population_subset_of</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">ADM restricts beneficiary scope to first SSDI/SSI payment in 1996-DAF-year period.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R035" source="R128_E022" target="R128_E023"><data key="edge_relationship_id">R128_R035</data><data key="edge_source_entity_id">R128_E022</data><data key="edge_relationship_type">uses_central_medical_reviews_from</data><data key="edge_target_entity_id">R128_E023</data><data key="edge_operational_context">Standalone CDR file takes full medical CDR information from centrally initiated Waterfall records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R036" source="R128_E022" target="R128_E039"><data key="edge_relationship_id">R128_R036</data><data key="edge_source_entity_id">R128_E022</data><data key="edge_relationship_type">uses_work_medic_and_mailer_data_from</data><data key="edge_target_entity_id">R128_E039</data><data key="edge_operational_context">DCF Review/Event tables include work, medical and mailer CDR activity that is not fully in Waterfall.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R037" source="R128_E039" target="DB_DCF"><data key="edge_relationship_id">R128_R037</data><data key="edge_source_entity_id">R128_E039</data><data key="edge_relationship_type">extracts_from</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Review and Event tables are source of DAF medical/work and mailer CDR indicators.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R038" source="R128_E024" target="R128_E023"><data key="edge_relationship_id">R128_R038</data><data key="edge_source_entity_id">R128_E024</data><data key="edge_relationship_type">is_documented_variant_of</data><data key="edge_target_entity_id">R128_E023</data><data key="edge_operational_context">DAF22 uses Waterfall Extract variant for CDR research.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R039" source="R128_E025" target="R128_E023"><data key="edge_relationship_id">R128_R039</data><data key="edge_source_entity_id">R128_E025</data><data key="edge_relationship_type">is_documented_variant_of</data><data key="edge_target_entity_id">R128_E023</data><data key="edge_operational_context">DAF22 uses Waterfall Track Active variant for CDR research.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R040" source="R128_E027" target="R128_E028"><data key="edge_relationship_id">R128_R040</data><data key="edge_source_entity_id">R128_E027</data><data key="edge_relationship_type">is_constructed_by</data><data key="edge_target_entity_id">R128_E028</data><data key="edge_operational_context">DAF22 workflow includes standalone SDR disability application research file construction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R041" source="R128_E035" target="APP_ITOPSS"><data key="edge_relationship_id">R128_R041</data><data key="edge_source_entity_id">R128_E035</data><data key="edge_relationship_type">is_derived_from</data><data key="edge_target_entity_id">APP_ITOPSS</data><data key="edge_operational_context">SSA documents ORDES uses iTOPSS database to evaluate TTW payments, and DAF uses cumulative EN payment report.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R042" source="R128_E035" target="R128_E019"><data key="edge_relationship_id">R128_R042</data><data key="edge_source_entity_id">R128_E035</data><data key="edge_relationship_type">feeds_payments_component</data><data key="edge_target_entity_id">R128_E019</data><data key="edge_operational_context">Cumulative Employment Network report contributes dated payment/trigger information to DAF.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R043" source="R128_E036" target="R128_E019"><data key="edge_relationship_id">R128_R043</data><data key="edge_source_entity_id">R128_E036</data><data key="edge_relationship_type">is_used_to_classify_provider_in</data><data key="edge_target_entity_id">R128_E019</data><data key="edge_operational_context">TTW provider file differentiates EN versus state VR contractors and contains no beneficiary records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R044" source="APP_VRRMS" target="R128_E019"><data key="edge_relationship_id">R128_R044</data><data key="edge_source_entity_id">APP_VRRMS</data><data key="edge_relationship_type">provides_reimbursement_extract_to</data><data key="edge_target_entity_id">R128_E019</data><data key="edge_operational_context">VRRMS state vocational-rehabilitation cost-reimbursement claims feed DAF payment history.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R045" source="R128_E019" target="R128_E001"><data key="edge_relationship_id">R128_R045</data><data key="edge_source_entity_id">R128_E019</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">DAF22 incorporates Ticket to Work and VR reimbursement payments as analytical provider-related records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R046" source="R128_E029" target="ORG_ED"><data key="edge_relationship_id">R128_R046</data><data key="edge_source_entity_id">R128_E029</data><data key="edge_relationship_type">is_provided_by</data><data key="edge_target_entity_id">ORG_ED</data><data key="edge_operational_context">Department of Education RSA-911 vocational rehabilitation administrative reporting feeds SSA research under agreement.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R047" source="R128_E030" target="R128_E029"><data key="edge_relationship_id">R128_R047</data><data key="edge_source_entity_id">R128_E030</data><data key="edge_relationship_type">is_deidentified_extract_of</data><data key="edge_target_entity_id">R128_E029</data><data key="edge_operational_context">Only verified SSN records are made linkable by assigned PIN; not all RSA clients appear in DAF.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R048" source="R128_E031" target="R128_E029"><data key="edge_relationship_id">R128_R048</data><data key="edge_source_entity_id">R128_E031</data><data key="edge_relationship_type">is_verified_extract_of</data><data key="edge_target_entity_id">R128_E029</data><data key="edge_operational_context">RSA-911 files require SSN verification before inclusion in the deidentified DAF-RSA resources.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R049" source="R128_E032" target="R128_E001"><data key="edge_relationship_id">R128_R049</data><data key="edge_source_entity_id">R128_E032</data><data key="edge_relationship_type">joins_approved_program_records_from</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">RSA Mini DAF contains DAF variables only for eligible vocational rehabilitation participants.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R050" source="R128_E033" target="SYS_NUMIDENT"><data key="edge_relationship_id">R128_R050</data><data key="edge_source_entity_id">R128_E033</data><data key="edge_relationship_type">verifies_identifiers_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">MPR-EVS compares SSN, sex/gender, year of birth with Numident; missing name in RSA data constrains matching.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R051" source="R128_E029" target="R128_E033"><data key="edge_relationship_id">R128_R051</data><data key="edge_source_entity_id">R128_E029</data><data key="edge_relationship_type">undergoes_research_verification_by</data><data key="edge_target_entity_id">R128_E033</data><data key="edge_operational_context">RSA SSN checked before SSA assigns PIN and releases DAF-RSA linkage files.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R052" source="R128_E033" target="R128_E034"><data key="edge_relationship_id">R128_R052</data><data key="edge_source_entity_id">R128_E033</data><data key="edge_relationship_type">precedes_pseudonymous_linkage_using</data><data key="edge_target_entity_id">R128_E034</data><data key="edge_operational_context">Verified RSA SSNs are assigned PINs via restricted SSA SSN-PIN crosswalk.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R053" source="R128_E034" target="R128_E030"><data key="edge_relationship_id">R128_R053</data><data key="edge_source_entity_id">R128_E034</data><data key="edge_relationship_type">supports_approved_research_linkage_of</data><data key="edge_target_entity_id">R128_E030</data><data key="edge_operational_context">Crosswalk supports joining RSA and other approved files by PIN without disclosing source SSN to research end users.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R054" source="R128_E030" target="R128_E001"><data key="edge_relationship_id">R128_R054</data><data key="edge_source_entity_id">R128_E030</data><data key="edge_relationship_type">is_linkable_to</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">DAF-RSA research summary links to DAF on corresponding PINs under applicable permissions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R055" source="R128_E037" target="SYS_MEF"><data key="edge_relationship_id">R128_R055</data><data key="edge_source_entity_id">R128_E037</data><data key="edge_relationship_type">is_restricted_extract_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">MEF annual wage and self-employment data are accessible to selected SSA personnel under IRC 6103 restrictions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R056" source="R128_E037" target="R128_E001"><data key="edge_relationship_id">R128_R056</data><data key="edge_source_entity_id">R128_E037</data><data key="edge_relationship_type">is_conditionally_linkable_to</data><data key="edge_target_entity_id">R128_E001</data><data key="edge_operational_context">Authorized SSA staff may link MEF-derived longitudinal earnings to DAF without redisclosure to outside researchers.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R057" source="R128_E038" target="R128_E037"><data key="edge_relationship_id">R128_R057</data><data key="edge_source_entity_id">R128_E038</data><data key="edge_relationship_type">is_derived_from</data><data key="edge_target_entity_id">R128_E037</data><data key="edge_operational_context">Work indicator is based on positive wage/self-employment income, excluding transfer payments from third-party payers.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R058" source="R128_E041" target="R128_E028"><data key="edge_relationship_id">R128_R058</data><data key="edge_source_entity_id">R128_E041</data><data key="edge_relationship_type">documented_research_contractor_for</data><data key="edge_target_entity_id">R128_E028</data><data key="edge_operational_context">2024 Volume 8 names Mathematica contractor and contract 28321322D00060010, not SSA production database host.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R059" source="R128_E045" target="R128_E042"><data key="edge_relationship_id">R128_R059</data><data key="edge_source_entity_id">R128_E045</data><data key="edge_relationship_type">is_documented_in</data><data key="edge_target_entity_id">R128_E042</data><data key="edge_operational_context">MSSICS DIRS receives development notes/results when investigating IRS alerts; no evidence that DIRS directly updates SSR identity or address.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R128_R060" source="R128_E045" target="R128_E043"><data key="edge_relationship_id">R128_R060</data><data key="edge_source_entity_id">R128_E045</data><data key="edge_relationship_type">compares_claimant_evidence_against</data><data key="edge_target_entity_id">R128_E043</data><data key="edge_operational_context">When taxpayer denies ownership, SSA may seek taxpayer address/birthdate/signature from payer to confirm attribution of IRS transaction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R128_R061" source="R128_E044" target="R128_E045"><data key="edge_relationship_id">R128_R061</data><data key="edge_source_entity_id">R128_E044</data><data key="edge_relationship_type">may_represent_corporate_office_instead_of_local_evidence_source</data><data key="edge_target_entity_id">R128_E045</data><data key="edge_operational_context">POMS warns that IRS payer-address may identify administrative headquarters; field office should seek local evidence where feasible.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R128_R062" source="R128_E045" target="R128_E046"><data key="edge_relationship_id">R128_R062</data><data key="edge_source_entity_id">R128_E045</data><data key="edge_relationship_type">routes_cross_service_area_work_via</data><data key="edge_target_entity_id">R128_E046</data><data key="edge_operational_context">POMS directs IRS-alert transfer to new servicing field office if beneficiary has moved.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R128_R063" source="R128_E043" target="SYS_SSR"><data key="edge_relationship_id">R128_R063</data><data key="edge_source_entity_id">R128_E043</data><data key="edge_relationship_type">not_documented_as_automatic_update_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">No automatic SSR address-update pathway is given for an IRS alert address; procedures require ownership verification and separate program action.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R128_R064" source="R128_E043" target="SYS_NUMIDENT"><data key="edge_relationship_id">R128_R064</data><data key="edge_source_entity_id">R128_E043</data><data key="edge_relationship_type">not_documented_as_automatic_update_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Verification of external transaction address does not establish Numident updating.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R128_R065" source="R128_E047" target="R128_E032"><data key="edge_relationship_id">R128_R065</data><data key="edge_source_entity_id">R128_E047</data><data key="edge_relationship_type">adds_county_unemployment_context_to</data><data key="edge_target_entity_id">R128_E032</data><data key="edge_operational_context">RSA Mini DAF merges county-level monthly LAUS unemployment contextual measures; no individual address verification is thereby established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R128_R066" source="R128_E048" target="R128_E032"><data key="edge_relationship_id">R128_R066</data><data key="edge_source_entity_id">R128_E048</data><data key="edge_relationship_type">adds_county_poverty_income_context_to</data><data key="edge_target_entity_id">R128_E032</data><data key="edge_operational_context">RSA Mini DAF includes SAIPE county poverty/income context starting with documented available periods.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R001" source="R129_E001" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R129_R001</data><data key="edge_source_entity_id">R129_E001</data><data key="edge_relationship_type">measures</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">National 800 number agent wait times aggregated by month; not a measure of abandoned calls.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R002" source="R129_E001" target="R129_E002"><data key="edge_relationship_id">R129_R002</data><data key="edge_source_entity_id">R129_E001</data><data key="edge_relationship_type">has_statistical_definition</data><data key="edge_target_entity_id">R129_E002</data><data key="edge_operational_context">Published ASA excludes calls abandoned in the queue and divides queue seconds by answered-agent calls.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R003" source="R129_E001" target="NET_N8NN_CARE2020"><data key="edge_relationship_id">R129_R003</data><data key="edge_source_entity_id">R129_E001</data><data key="edge_relationship_type">documents_2013_network_transition</data><data key="edge_target_entity_id">NET_N8NN_CARE2020</data><data key="edge_operational_context">Page says network transition to CARE 2020 began 2013; historical observation, not current deployment proof.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R004" source="R129_E001" target="PLAT_N8NN_CCAAS"><data key="edge_relationship_id">R129_R004</data><data key="edge_source_entity_id">R129_E001</data><data key="edge_relationship_type">includes_metric_reporting_after_CCAAS_start</data><data key="edge_target_entity_id">PLAT_N8NN_CCAAS</data><data key="edge_operational_context">The page identifies CCaaS metrics beginning March 23, 2023.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R005" source="R129_E003" target="R129_E004"><data key="edge_relationship_id">R129_R005</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E004</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R006" source="R129_E003" target="R129_E005"><data key="edge_relationship_id">R129_R006</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E005</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R007" source="R129_E003" target="R129_E006"><data key="edge_relationship_id">R129_R007</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E006</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R008" source="R129_E003" target="R129_E007"><data key="edge_relationship_id">R129_R008</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E007</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R009" source="R129_E003" target="R129_E008"><data key="edge_relationship_id">R129_R009</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E008</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R010" source="R129_E003" target="R129_E009"><data key="edge_relationship_id">R129_R010</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E009</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R011" source="R129_E003" target="R129_E010"><data key="edge_relationship_id">R129_R011</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E010</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R012" source="R129_E003" target="R129_E011"><data key="edge_relationship_id">R129_R012</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E011</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R013" source="R129_E003" target="R129_E012"><data key="edge_relationship_id">R129_R013</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E012</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R014" source="R129_E003" target="R129_E013"><data key="edge_relationship_id">R129_R014</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E013</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R015" source="R129_E003" target="R129_E014"><data key="edge_relationship_id">R129_R015</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E014</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R016" source="R129_E003" target="R129_E015"><data key="edge_relationship_id">R129_R016</data><data key="edge_source_entity_id">R129_E003</data><data key="edge_relationship_type">lists_posted_disclosure</data><data key="edge_target_entity_id">R129_E015</data><data key="edge_operational_context">SSA FOIA Reading Room provides the title and posting date; further data lineage not inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R017" source="R129_E016" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R129_R017</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">catalogs_submission_option</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA forms page advertises Upload Documents for eligible forms and evidence, with alternative mail and fax options.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R018" source="R129_E016" target="R129_E017"><data key="edge_relationship_id">R129_R018</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">documents_identity_step_up</data><data key="edge_target_entity_id">R129_E017</data><data key="edge_operational_context">Five specified forms have additional identity verification conditions before electronic submission.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R019" source="APP_UPLOAD_DOCUMENTS" target="R129_E018"><data key="edge_relationship_id">R129_R019</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">enforces_evidence_type_exclusion</data><data key="edge_target_entity_id">R129_E018</data><data key="edge_operational_context">Uploaded electronic documents cannot replace original or certified copies where originals are required.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R020" source="R129_E017" target="FORM_SSA454BK"><data key="edge_relationship_id">R129_R020</data><data key="edge_source_entity_id">R129_E017</data><data key="edge_relationship_type">applies_to_form</data><data key="edge_target_entity_id">FORM_SSA454BK</data><data key="edge_operational_context">SSA Forms electronic filing eligibility requires additional identity verification for this specific form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R021" source="R129_E017" target="FORM_SSA827"><data key="edge_relationship_id">R129_R021</data><data key="edge_source_entity_id">R129_E017</data><data key="edge_relationship_type">applies_to_form</data><data key="edge_target_entity_id">FORM_SSA827</data><data key="edge_operational_context">SSA Forms electronic filing eligibility requires additional identity verification for this specific form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R022" source="R129_E017" target="FORM_SSA_2574"><data key="edge_relationship_id">R129_R022</data><data key="edge_source_entity_id">R129_E017</data><data key="edge_relationship_type">applies_to_form</data><data key="edge_target_entity_id">FORM_SSA_2574</data><data key="edge_operational_context">SSA Forms electronic filing eligibility requires additional identity verification for this specific form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R023" source="R129_E017" target="FORM_SSA2935"><data key="edge_relationship_id">R129_R023</data><data key="edge_source_entity_id">R129_E017</data><data key="edge_relationship_type">applies_to_form</data><data key="edge_target_entity_id">FORM_SSA2935</data><data key="edge_operational_context">SSA Forms electronic filing eligibility requires additional identity verification for this specific form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R024" source="R129_E017" target="FORM_SSA8510"><data key="edge_relationship_id">R129_R024</data><data key="edge_source_entity_id">R129_E017</data><data key="edge_relationship_type">applies_to_form</data><data key="edge_target_entity_id">FORM_SSA8510</data><data key="edge_operational_context">SSA Forms electronic filing eligibility requires additional identity verification for this specific form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R025" source="R129_E016" target="FORM_HA85"><data key="edge_relationship_id">R129_R025</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_HA85</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R026" source="R129_E016" target="FORM_HA86"><data key="edge_relationship_id">R129_R026</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_HA86</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R027" source="R129_E016" target="FORM_HA510"><data key="edge_relationship_id">R129_R027</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_HA510</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R028" source="R129_E016" target="FORM_HA539"><data key="edge_relationship_id">R129_R028</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_HA539</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R029" source="R129_E016" target="FORM_HA4631"><data key="edge_relationship_id">R129_R029</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_HA4631</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R030" source="R129_E016" target="FORM_HA4632"><data key="edge_relationship_id">R129_R030</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_HA4632</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R031" source="R129_E016" target="FORM_HA4633"><data key="edge_relationship_id">R129_R031</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_HA4633</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R032" source="R129_E016" target="FORM_SSA44"><data key="edge_relationship_id">R129_R032</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_SSA44</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R033" source="R129_E016" target="FORM_SSA25"><data key="edge_relationship_id">R129_R033</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_SSA25</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R034" source="R129_E016" target="FORM_SSA371"><data key="edge_relationship_id">R129_R034</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_SSA371</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R035" source="R129_E016" target="FORM_SSA372"><data key="edge_relationship_id">R129_R035</data><data key="edge_source_entity_id">R129_E016</data><data key="edge_relationship_type">lists_online_webform_and_pdf_upload_option_for</data><data key="edge_target_entity_id">FORM_SSA372</data><data key="edge_operational_context">SSA Forms 2026 index displays both Complete Online Form and Upload PDF for this form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R036" source="R129_E019" target="R129_E020"><data key="edge_relationship_id">R129_R036</data><data key="edge_source_entity_id">R129_E019</data><data key="edge_relationship_type">has_statistical_definition</data><data key="edge_target_entity_id">R129_E020</data><data key="edge_operational_context">Same-year awards/applications ratio cannot be interpreted as a cohort allowance or award rate.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R037" source="R129_E021" target="R129_E019"><data key="edge_relationship_id">R129_R037</data><data key="edge_source_entity_id">R129_E021</data><data key="edge_relationship_type">superseded_for_publication_by</data><data key="edge_target_entity_id">R129_E019</data><data key="edge_operational_context">Supplement identifies the continuing OACT table as reason Table 6.C7 is dropped.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R038" source="R129_E022" target="DOM_REPPAYEE"><data key="edge_relationship_id">R129_R038</data><data key="edge_source_entity_id">R129_E022</data><data key="edge_relationship_type">analyzes</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">The brief studies representative payee prevalence and administrative advance designation; the web summary does not specify underlying record extraction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R039" source="R129_E023" target="ORG_SSA_OITA"><data key="edge_relationship_id">R129_R039</data><data key="edge_source_entity_id">R129_E023</data><data key="edge_relationship_type">organizational_component_of</data><data key="edge_target_entity_id">ORG_SSA_OITA</data><data key="edge_operational_context">OAG public contracting office directory lists a Division of IT Equipment &amp; Maintenance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R040" source="R129_E024" target="ORG_SSA_OITA"><data key="edge_relationship_id">R129_R040</data><data key="edge_source_entity_id">R129_E024</data><data key="edge_relationship_type">organizational_component_of</data><data key="edge_target_entity_id">ORG_SSA_OITA</data><data key="edge_operational_context">OAG public contracting office directory lists a Division of IT Software &amp; Maintenance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R041" source="DATA_OHO_WORKLOAD_PUBLIC" target="R129_E025"><data key="edge_relationship_id">R129_R041</data><data key="edge_source_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_relationship_type">documents_adjusted_receipts_rule</data><data key="edge_target_entity_id">R129_E025</data><data key="edge_operational_context">Office net receipt figures can be negative when transfers out exceed new receipts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R042" source="R129_E026" target="DATA_OHO_WORKLOAD_PUBLIC"><data key="edge_relationship_id">R129_R042</data><data key="edge_source_entity_id">R129_E026</data><data key="edge_relationship_type">published_alongside</data><data key="edge_target_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_operational_context">Both are separate FY2026 OHO public workload statistics; no underlying software linkage inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R043" source="R129_E027" target="DATA_OHO_WORKLOAD_PUBLIC"><data key="edge_relationship_id">R129_R043</data><data key="edge_source_entity_id">R129_E027</data><data key="edge_relationship_type">published_alongside</data><data key="edge_target_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_operational_context">Average processing time office rankings are published separately from workload counts and hearing-held wait times.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R044" source="R129_E029" target="DATA_RSI_APPLICATION_VOLUMES"><data key="edge_relationship_id">R129_R044</data><data key="edge_source_entity_id">R129_E029</data><data key="edge_relationship_type">monthly_publication_of</data><data key="edge_target_entity_id">DATA_RSI_APPLICATION_VOLUMES</data><data key="edge_operational_context">The 2016-onward CSV is a downloadable statistical publication within the retirement/survivor application volume collection.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R045" source="APP_MCS" target="DB_TITLE2_ODS"><data key="edge_relationship_id">R129_R045</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">nightly_transfers_claim_information_to</data><data key="edge_target_entity_id">DB_TITLE2_ODS</data><data key="edge_operational_context">SSA Open Data documents MCS nightly download to the Title II ODS for initial claims management information; implementation not disclosed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R046" source="R129_E029" target="DB_TITLE2_ODS"><data key="edge_relationship_id">R129_R046</data><data key="edge_source_entity_id">R129_E029</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">DB_TITLE2_ODS</data><data key="edge_operational_context">Title II ODS supports national level claims counts aggregated through batch processing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R047" source="R129_E029" target="DATA_DOWR"><data key="edge_relationship_id">R129_R047</data><data key="edge_source_entity_id">R129_E029</data><data key="edge_relationship_type">uses_reporting_periods_from</data><data key="edge_target_entity_id">DATA_DOWR</data><data key="edge_operational_context">DOWR receipt dates define reporting periods, which can differ from ordinary calendar months.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R129_R048" source="R129_E030" target="APP_MCS"><data key="edge_relationship_id">R129_R048</data><data key="edge_source_entity_id">R129_E030</data><data key="edge_relationship_type">annotates_filing_source_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">SSA states the online system places an Internet-origin indicator on certain online application types; not proof of a separate MCS column.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R129_R049" source="R129_E029" target="R129_E030"><data key="edge_relationship_id">R129_R049</data><data key="edge_source_entity_id">R129_E029</data><data key="edge_relationship_type">groups_by</data><data key="edge_target_entity_id">R129_E030</data><data key="edge_operational_context">Internet versus other application routes contribute to public receipt and clearance counts.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R001" source="R130_E001" target="APP_MSSICS"><data key="edge_relationship_id">R130_R001</data><data key="edge_source_entity_id">R130_E001</data><data key="edge_relationship_type">handled_by</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Defined age-65 Title XVI scenarios use a system-entered date differing from legally correct filing date.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R002" source="R130_E001" target="R130_E002"><data key="edge_relationship_id">R130_R002</data><data key="edge_source_entity_id">R130_E001</data><data key="edge_relationship_type">requires_manual_annotation</data><data key="edge_target_entity_id">R130_E002</data><data key="edge_operational_context">Under system limitation, technician must annotate true earlier filing date in SSR remarks.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R003" source="R130_E002" target="SYS_SSR"><data key="edge_relationship_id">R130_R003</data><data key="edge_source_entity_id">R130_E002</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA explicitly directs true SSI filing date into SSR remarks when system-entered date differs.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R004" source="R130_E003" target="UI_MCS_DECI"><data key="edge_relationship_id">R130_R004</data><data key="edge_source_entity_id">R130_E003</data><data key="edge_relationship_type">entered_on</data><data key="edge_target_entity_id">UI_MCS_DECI</data><data key="edge_operational_context">Reopening of an earlier denial uses FDC=C in MCS Decision Input for FO1 workload accounting.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R005" source="R130_E003" target="R130_E006"><data key="edge_relationship_id">R130_R005</data><data key="edge_source_entity_id">R130_E003</data><data key="edge_relationship_type">documents</data><data key="edge_target_entity_id">R130_E006</data><data key="edge_operational_context">FDC code C applies to reopening requests with material file date and receipt date tied to reopening request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R006" source="R130_E004" target="UI_IMNU"><data key="edge_relationship_id">R130_R006</data><data key="edge_source_entity_id">R130_E004</data><data key="edge_relationship_type">documented_on</data><data key="edge_target_entity_id">UI_IMNU</data><data key="edge_operational_context">Electronically signed first-party iClaim receipt date is the complete date on IMNU.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R007" source="APP_ICLAIM" target="APP_MCS"><data key="edge_relationship_id">R130_R007</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">establishes_receipt_timestamp_before</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">iClaim submission date, not later MCS establishment date, determines receipt for first-party electronic filing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R008" source="R130_E005" target="DATA_TITLE2_APP_FILING_DATE"><data key="edge_relationship_id">R130_R008</data><data key="edge_source_entity_id">R130_E005</data><data key="edge_relationship_type">may_determine</data><data key="edge_target_entity_id">DATA_TITLE2_APP_FILING_DATE</data><data key="edge_operational_context">In specified mail cases postmark within 5 days after closeout can control application receipt date.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R009" source="R130_E006" target="APP_MCS"><data key="edge_relationship_id">R130_R009</data><data key="edge_source_entity_id">R130_E006</data><data key="edge_relationship_type">documented_in_claims_reopening</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MFD for prior denial reopening is same as reopening request receipt date, not original earlier filing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R010" source="APP_UPLOAD_DOCUMENTS" target="R130_E007"><data key="edge_relationship_id">R130_R010</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">requires_staff_processing_via</data><data key="edge_target_entity_id">R130_E007</data><data key="edge_operational_context">POMS says Upload Documents electronically signed benefit applications are manually loaded like paper into MCS or CCE.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R011" source="R130_E007" target="APP_MCS"><data key="edge_relationship_id">R130_R011</data><data key="edge_source_entity_id">R130_E007</data><data key="edge_relationship_type">requires_manual_entry_to</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Employee must enter signed benefit application contents into MCS when applicable.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R012" source="R130_E007" target="APP_CCE"><data key="edge_relationship_id">R130_R012</data><data key="edge_source_entity_id">R130_E007</data><data key="edge_relationship_type">requires_manual_entry_to</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Employee must enter signed benefit application contents into CCE when applicable.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R013" source="APP_UPLOAD_DOCUMENTS" target="R130_E008"><data key="edge_relationship_id">R130_R013</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">appends</data><data key="edge_target_entity_id">R130_E008</data><data key="edge_operational_context">PDF includes separate electronic-signature information page associated with electronic submission.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R014" source="WORK_MCS_ATTEST_ISSUE" target="R130_E009"><data key="edge_relationship_id">R130_R014</data><data key="edge_source_entity_id">WORK_MCS_ATTEST_ISSUE</data><data key="edge_relationship_type">requires_method_annotation</data><data key="edge_target_entity_id">R130_E009</data><data key="edge_operational_context">MCS DW01 ATTEST propagates for signature methods other than formal attestation; signature method must be stated.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R015" source="R130_E009" target="UI_MCS_DW01"><data key="edge_relationship_id">R130_R015</data><data key="edge_source_entity_id">R130_E009</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">UI_MCS_DW01</data><data key="edge_operational_context">Technician remarks identify wet signature, upload docs, or CPAS to avoid ambiguous ATTEST interpretation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R016" source="PROC_CPAS" target="R130_E010"><data key="edge_relationship_id">R130_R016</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">accepts_supporting_artifact</data><data key="edge_target_entity_id">R130_E010</data><data key="edge_operational_context">Commercial signature certificate may carry date and time when attached at initial submission.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R017" source="R130_E011" target="PROC_CPAS"><data key="edge_relationship_id">R130_R017</data><data key="edge_source_entity_id">R130_E011</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_CPAS</data><data key="edge_operational_context">CPAS requires signature name placement plus date and time; separate late certificate unacceptable.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R018" source="R130_E010" target="R130_E011"><data key="edge_relationship_id">R130_R018</data><data key="edge_source_entity_id">R130_E010</data><data key="edge_relationship_type">must_satisfy</data><data key="edge_target_entity_id">R130_E011</data><data key="edge_operational_context">Certificate must accompany signed form and contain date and time if absent on form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R019" source="R130_E012" target="PROC_CPAS"><data key="edge_relationship_id">R130_R019</data><data key="edge_source_entity_id">R130_E012</data><data key="edge_relationship_type">controls_receipt_applicability_of</data><data key="edge_target_entity_id">PROC_CPAS</data><data key="edge_operational_context">POMS threshold applies to CPAS forms submitted on/after January 18, 2025.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R020" source="APP_EVID" target="R130_E013"><data key="edge_relationship_id">R130_R020</data><data key="edge_source_entity_id">APP_EVID</data><data key="edge_relationship_type">has_record_finalization_control</data><data key="edge_target_entity_id">R130_E013</data><data key="edge_operational_context">EVID is locked after completion and can only be deleted by authorized management.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R021" source="R130_E013" target="APP_MCS"><data key="edge_relationship_id">R130_R021</data><data key="edge_source_entity_id">R130_E013</data><data key="edge_relationship_type">subsequent_annotation_via</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Later clarification goes on MCS RPOC or CCE Report of Contact rather than editing locked EVID entry.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R022" source="R130_E013" target="APP_CCE"><data key="edge_relationship_id">R130_R022</data><data key="edge_source_entity_id">R130_E013</data><data key="edge_relationship_type">subsequent_annotation_via</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Later clarification can be entered on CCE Report of Contact page.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R023" source="APP_EVID" target="R130_E014"><data key="edge_relationship_id">R130_R023</data><data key="edge_source_entity_id">APP_EVID</data><data key="edge_relationship_type">has_field</data><data key="edge_target_entity_id">R130_E014</data><data key="edge_operational_context">EVID cross-reference SSN field can link evidence used across concurrent claims filed under different SSNs.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R024" source="R130_E014" target="SYS_MBR"><data key="edge_relationship_id">R130_R024</data><data key="edge_source_entity_id">R130_E014</data><data key="edge_relationship_type">supports_logical_person_reconciliation_between</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Cross-referenced claim SSNs preserve the context of claimant versus claim-account SSNs, not a physical enterprise person store.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R130_R025" source="R130_E015" target="APP_EVID"><data key="edge_relationship_id">R130_R025</data><data key="edge_source_entity_id">R130_E015</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">State/local online custodian provenance is entered in EVID comments when used as certified evidence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R026" source="R130_E016" target="APP_MCS"><data key="edge_relationship_id">R130_R026</data><data key="edge_source_entity_id">R130_E016</data><data key="edge_relationship_type">governs_temporary_evidence_for</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Temporary photocopy files used to develop initial claims are destroyed after adjudication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R027" source="R130_E017" target="APP_MCS"><data key="edge_relationship_id">R130_R027</data><data key="edge_source_entity_id">R130_E017</data><data key="edge_relationship_type">governs_evidence_coding_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS public-record proof entries must include enough audit information or evidence is recorded on EVID.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R028" source="R130_E017" target="APP_PERSON_INFO"><data key="edge_relationship_id">R130_R028</data><data key="edge_source_entity_id">R130_E017</data><data key="edge_relationship_type">governs_evidence_coding_in</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">CCE Person Information needs sufficient public-record detail or EVID entry.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R029" source="R130_E018" target="R130_E015"><data key="edge_relationship_id">R130_R029</data><data key="edge_source_entity_id">R130_E018</data><data key="edge_relationship_type">documents_state_source_in</data><data key="edge_target_entity_id">R130_E015</data><data key="edge_operational_context">Custodian-certified state/local evidence provenance must be traceable through online access source annotation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R030" source="R130_E019" target="REPO_NDRED"><data key="edge_relationship_id">R130_R030</data><data key="edge_source_entity_id">R130_E019</data><data key="edge_relationship_type">directs_alien_registration_evidence_to</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Foreign registration document images go to NDRed via Evidence Portal, not EVID entries.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R031" source="R130_E019" target="REPO_EF"><data key="edge_relationship_id">R130_R031</data><data key="edge_source_entity_id">R130_E019</data><data key="edge_relationship_type">directs_certain_wc_pdb_evidence_to</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">WC/PDB evidence documentation may require permanent storage in Certified Electronic Folder rather than EVID coding.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R032" source="R130_E020" target="SYS_MBR"><data key="edge_relationship_id">R130_R032</data><data key="edge_source_entity_id">R130_E020</data><data key="edge_relationship_type">supports_conditional_reuse_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Prior age or status proofs may be reused when same proof standard and sufficient audit trail exist.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R033" source="R130_E020" target="SYS_SSR"><data key="edge_relationship_id">R130_R033</data><data key="edge_source_entity_id">R130_E020</data><data key="edge_relationship_type">supports_conditional_reuse_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Prior age or status proofs may be reused from SSI record when supported, no automatic synchronization inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R034" source="R130_E020" target="SYS_NUMIDENT"><data key="edge_relationship_id">R130_R034</data><data key="edge_source_entity_id">R130_E020</data><data key="edge_relationship_type">supports_conditional_reuse_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Prior age evidence may be accepted from Numident under POMS, not proof every program record updated.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R035" source="R130_E021" target="APP_PEBES"><data key="edge_relationship_id">R130_R035</data><data key="edge_source_entity_id">R130_E021</data><data key="edge_relationship_type">furnished_to</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">Puerto Rico revenue agency tax files supply mailing addresses to Statement eligibility/production process.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R036" source="R130_E022" target="APP_PEBES"><data key="edge_relationship_id">R130_R036</data><data key="edge_source_entity_id">R130_E022</data><data key="edge_relationship_type">furnished_to</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">Virgin Islands tax files supply mailing addresses for eligible territorial non-federal-tax filers.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R037" source="DB_IRS_IMF" target="R130_E023"><data key="edge_relationship_id">R130_R037</data><data key="edge_source_entity_id">DB_IRS_IMF</data><data key="edge_relationship_type">permitted_address_use_limited_by</data><data key="edge_target_entity_id">R130_E023</data><data key="edge_operational_context">IRS IMF taxpayer address used for automatic statement mailings under IRC 6103(m)(7).</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R038" source="R130_E023" target="DATA_IRS_STATEMENT_MAIL_ADDR"><data key="edge_relationship_id">R130_R038</data><data key="edge_source_entity_id">R130_E023</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">DATA_IRS_STATEMENT_MAIL_ADDR</data><data key="edge_operational_context">Statutory use is Statement production, not general beneficiary address master-record updating.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R039" source="APP_PEBES" target="R130_E024"><data key="edge_relationship_id">R130_R039</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">produces_statement_format</data><data key="edge_target_entity_id">R130_E024</data><data key="edge_operational_context">Online personal Statement variant made available through my Social Security.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R040" source="APP_MYSSA" target="R130_E024"><data key="edge_relationship_id">R130_R040</data><data key="edge_source_entity_id">APP_MYSSA</data><data key="edge_relationship_type">delivers_statement_format</data><data key="edge_target_entity_id">R130_E024</data><data key="edge_operational_context">SSA-7005-SM-OL delivered through authenticated portal.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R041" source="APP_PEBES" target="R130_E025"><data key="edge_relationship_id">R130_R041</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">produces_statement_format</data><data key="edge_target_entity_id">R130_E025</data><data key="edge_operational_context">System-initiated SSA-7005-SM-SI used for eligible automatic paper Statements.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R042" source="APP_PEBES" target="R130_E026"><data key="edge_relationship_id">R130_R042</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">produces_statement_format</data><data key="edge_target_entity_id">R130_E026</data><data key="edge_operational_context">On-request SSA-7005-SM-OR generated for eligible requests.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R043" source="R130_E026" target="SERVICE_SSA_PMF"><data key="edge_relationship_id">R130_R043</data><data key="edge_source_entity_id">R130_E026</data><data key="edge_relationship_type">printed_by</data><data key="edge_target_entity_id">SERVICE_SSA_PMF</data><data key="edge_operational_context">SSA Print/Mail Facility handles on-request Statements, separate from contractor automatic Statement mailing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R044" source="R130_E025" target="R130_E027"><data key="edge_relationship_id">R130_R044</data><data key="edge_source_entity_id">R130_E025</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R130_E027</data><data key="edge_operational_context">Returned automatic Statements are destroyed without remailing under stated POMS procedure.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R045" source="R130_E021" target="R130_E028"><data key="edge_relationship_id">R130_R045</data><data key="edge_source_entity_id">R130_E021</data><data key="edge_relationship_type">determines_locale_in</data><data key="edge_target_entity_id">R130_E028</data><data key="edge_operational_context">Statements automatically issued using Puerto Rican government address use Spanish locale.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R046" source="R130_E029" target="DB_STATEMENT_HISTORY"><data key="edge_relationship_id">R130_R046</data><data key="edge_source_entity_id">R130_E029</data><data key="edge_relationship_type">constrains_selection_by</data><data key="edge_target_entity_id">DB_STATEMENT_HISTORY</data><data key="edge_operational_context">Requests in previous 11 months can exclude recipient from automatic mailing selection.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R047" source="R130_E029" target="APP_WMS"><data key="edge_relationship_id">R130_R047</data><data key="edge_source_entity_id">R130_E029</data><data key="edge_relationship_type">constrains_selection_by</data><data key="edge_target_entity_id">APP_WMS</data><data key="edge_operational_context">Pending Title II claims can exclude recipient from automatic mailing selection.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R048" source="R130_E029" target="SYS_MBR"><data key="edge_relationship_id">R130_R048</data><data key="edge_source_entity_id">R130_E029</data><data key="edge_relationship_type">constrains_selection_by</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR payment/entitlement conditions affect eligible population for automatic mailing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R049" source="R130_E029" target="R130_E025"><data key="edge_relationship_id">R130_R049</data><data key="edge_source_entity_id">R130_E029</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R130_E025</data><data key="edge_operational_context">System-initiated Statement population follows POMS eligibility and exclusion conditions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R050" source="APP_IAPPT" target="R130_E030"><data key="edge_relationship_id">R130_R050</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">restricts_editable_person_inputs_with</data><data key="edge_target_entity_id">R130_E030</data><data key="edge_operational_context">iAppt claimant can change name, DOB and sex but not propagated SSN; mailing address is separately self-reported.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R051" source="R130_E030" target="SYS_NUMIDENT"><data key="edge_relationship_id">R130_R051</data><data key="edge_source_entity_id">R130_E030</data><data key="edge_relationship_type">does_not_automatically_correct</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Appointment attributes are self-supplied and not automatically verified Numident identity updates.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R052" source="R130_E031" target="APP_IAPPT"><data key="edge_relationship_id">R130_R052</data><data key="edge_source_entity_id">R130_E031</data><data key="edge_relationship_type">limits_eligibility_for</data><data key="edge_target_entity_id">APP_IAPPT</data><data key="edge_operational_context">Current-payment MBR, pending MCS claim, SSN electronic block, or foreign residence lead to separate assistance route.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R053" source="R130_E031" target="SYS_MBR"><data key="edge_relationship_id">R130_R053</data><data key="edge_source_entity_id">R130_E031</data><data key="edge_relationship_type">checks_current_benefit_status_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS explicitly cites MBR current-payment as a reason iAppt cannot be accessed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R054" source="R130_E031" target="APP_MCS"><data key="edge_relationship_id">R130_R054</data><data key="edge_source_entity_id">R130_E031</data><data key="edge_relationship_type">checks_pending_claim_status_against</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS explicitly cites a pending MCS claim on claimant SSN as exclusion.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R055" source="R130_E032" target="DATA_OACT_SOCSEC_POP_DOWNLOAD_2026"><data key="edge_relationship_id">R130_R055</data><data key="edge_source_entity_id">R130_E032</data><data key="edge_relationship_type">characterizes</data><data key="edge_target_entity_id">DATA_OACT_SOCSEC_POP_DOWNLOAD_2026</data><data key="edge_operational_context">OACT public population datasets have Jan 1, Jul 1, Dec 31 reference date values across historical and projected timelines.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R056" source="MODEL_OACT_POPULATION" target="R130_E032"><data key="edge_relationship_id">R130_R056</data><data key="edge_source_entity_id">MODEL_OACT_POPULATION</data><data key="edge_relationship_type">supports_publication_with_date_dimensions</data><data key="edge_target_entity_id">R130_E032</data><data key="edge_operational_context">Population projection and reporting products have reference-date semantics, not one undifferentiated population figure.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R130_R057" source="R130_E033" target="APP_MYSSA"><data key="edge_relationship_id">R130_R057</data><data key="edge_source_entity_id">R130_E033</data><data key="edge_relationship_type">public_interface_feature_of</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">May 12 2026 SSA portal redesign added up-to-three estimate comparison chart; technology vendor not identified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R001" source="APP_OSSNAP" target="R131_E001"><data key="edge_relationship_id">R131_R001</data><data key="edge_source_entity_id">APP_OSSNAP</data><data key="edge_relationship_type">routes_using</data><data key="edge_target_entity_id">R131_E001</data><data key="edge_operational_context">EM 26004 establishes dynamic self-service versus hybrid routing effective January 31, 2026.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R002" source="R131_E001" target="R131_E002"><data key="edge_relationship_id">R131_R002</data><data key="edge_source_entity_id">R131_E001</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">R131_E002</data><data key="edge_operational_context">Eligible cases failing online checks are routed to hybrid in-office completion.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R003" source="R131_E001" target="R131_E003"><data key="edge_relationship_id">R131_R003</data><data key="edge_source_entity_id">R131_E001</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">R131_E003</data><data key="edge_operational_context">Eligible adult U.S.-citizen original/replacement-card cases may complete self-service online.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R004" source="R131_E003" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">R131_R004</data><data key="edge_source_entity_id">R131_E003</data><data key="edge_relationship_type">uses_authentication_from</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">Authenticated online path supports Login.gov third-party credentials for eligible applicants.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R005" source="R131_E003" target="SVC_IDME"><data key="edge_relationship_id">R131_R005</data><data key="edge_source_entity_id">R131_E003</data><data key="edge_relationship_type">uses_authentication_from</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">Authenticated online path supports ID.me third-party credentials for eligible applicants.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R006" source="R131_E002" target="R131_E004"><data key="edge_relationship_id">R131_R006</data><data key="edge_source_entity_id">R131_E002</data><data key="edge_relationship_type">establishes_reference</data><data key="edge_target_entity_id">R131_E004</data><data key="edge_operational_context">Hybrid card request generates an online control number for applicant follow-up.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R007" source="R131_E002" target="APP_ESS"><data key="edge_relationship_id">R131_R007</data><data key="edge_source_entity_id">R131_E002</data><data key="edge_relationship_type">offers_appointment_through</data><data key="edge_target_entity_id">APP_ESS</data><data key="edge_operational_context">2026 guidance pairs hybrid card processing with ESS in-person appointment scheduling, generally within 45 days.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R008" source="R131_E002" target="APP_SSNAP"><data key="edge_relationship_id">R131_R008</data><data key="edge_source_entity_id">R131_E002</data><data key="edge_relationship_type">requires_evidence_review_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Hybrid requests require field-office adjudicative steps in SSNAP.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R009" source="R131_E002" target="R131_E005"><data key="edge_relationship_id">R131_R009</data><data key="edge_source_entity_id">R131_E002</data><data key="edge_relationship_type">separates_scheduling_authentication_from</data><data key="edge_target_entity_id">R131_E005</data><data key="edge_operational_context">EM 26004 differentiates appointment scheduling sign-in from the proof required for card issuance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R010" source="R131_E005" target="SYS_NUMIDENT"><data key="edge_relationship_id">R131_R010</data><data key="edge_source_entity_id">R131_E005</data><data key="edge_relationship_type">does_not_authoritatively_update</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Appointment authentication alone neither proves a Numident change nor creates a new authoritative SSN record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R011" source="APP_ISSNRC" target="R131_E006"><data key="edge_relationship_id">R131_R011</data><data key="edge_source_entity_id">APP_ISSNRC</data><data key="edge_relationship_type">public_interface_retired_under</data><data key="edge_target_entity_id">R131_E006</data><data key="edge_operational_context">Legacy public screen functionality incorporated into oSSNAP under streamlining, without asserting its backend database was deleted.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R012" source="R131_E006" target="APP_OSSNAP"><data key="edge_relationship_id">R131_R012</data><data key="edge_source_entity_id">R131_E006</data><data key="edge_relationship_type">public_functionality_transitioned_to</data><data key="edge_target_entity_id">APP_OSSNAP</data><data key="edge_operational_context">EM 26004 announces oSSNAP as successor user-facing card flow.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R013" source="APP_OSSNAP" target="R131_E007"><data key="edge_relationship_id">R131_R013</data><data key="edge_source_entity_id">APP_OSSNAP</data><data key="edge_relationship_type">constrains_online_intake_by</data><data key="edge_target_entity_id">R131_E007</data><data key="edge_operational_context">Exclusions limit eligible self-service and hybrid requests; manual channels still serve exceptions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R014" source="PROC_ERAP" target="R131_E008"><data key="edge_relationship_id">R131_R014</data><data key="edge_source_entity_id">PROC_ERAP</data><data key="edge_relationship_type">groups_representative_availability_by</data><data key="edge_target_entity_id">R131_E008</data><data key="edge_operational_context">ERAP requires one national submission for each DSG.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R015" source="R131_E008" target="R131_E009"><data key="edge_relationship_id">R131_R015</data><data key="edge_source_entity_id">R131_E008</data><data key="edge_relationship_type">submits_availability_for</data><data key="edge_target_entity_id">R131_E009</data><data key="edge_operational_context">DSG provides hearing schedule availability for a designated target scheduling month.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R016" source="PROC_ERAP" target="R131_E010"><data key="edge_relationship_id">R131_R016</data><data key="edge_source_entity_id">PROC_ERAP</data><data key="edge_relationship_type">applies</data><data key="edge_target_entity_id">R131_E010</data><data key="edge_operational_context">SSA implemented national DSG submission for target scheduling month January 2026.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R017" source="PROC_ERAP" target="R131_E011"><data key="edge_relationship_id">R131_R017</data><data key="edge_source_entity_id">PROC_ERAP</data><data key="edge_relationship_type">uses_future_submission_deadline</data><data key="edge_target_entity_id">R131_E011</data><data key="edge_operational_context">National process sets five-month planning horizon and default availability when deadline is missed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R018" source="R131_E011" target="R131_E009"><data key="edge_relationship_id">R131_R018</data><data key="edge_source_entity_id">R131_E011</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R131_E009</data><data key="edge_operational_context">Due date is calculated relative to target scheduling month.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R019" source="APP_REP_AVAIL_PORTAL" target="R131_E008"><data key="edge_relationship_id">R131_R019</data><data key="edge_source_entity_id">APP_REP_AVAIL_PORTAL</data><data key="edge_relationship_type">accepts_availability_for</data><data key="edge_target_entity_id">R131_E008</data><data key="edge_operational_context">The availability portal takes designated group monthly submissions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R020" source="R131_E012" target="PROC_ERAP"><data key="edge_relationship_id">R131_R020</data><data key="edge_source_entity_id">R131_E012</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_ERAP</data><data key="edge_operational_context">External liaison assists representatives submitting ERAP availability by alternate channels.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R021" source="APP_REP_AVAIL_PORTAL" target="APP_MYSSA"><data key="edge_relationship_id">R131_R021</data><data key="edge_source_entity_id">APP_REP_AVAIL_PORTAL</data><data key="edge_relationship_type">authenticates_using</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA representative availability submission portal uses my Social Security access and representative authorization controls.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R022" source="DATA_ERPS_ORG_ID" target="R131_E013"><data key="edge_relationship_id">R131_R022</data><data key="edge_source_entity_id">DATA_ERPS_ORG_ID</data><data key="edge_relationship_type">uses_physical_address_component</data><data key="edge_target_entity_id">R131_E013</data><data key="edge_operational_context">Organizational payee ID uses ZIP of organizational physical location, not beneficiary residence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R023" source="DATA_ERPS_ORG_ID" target="R131_E014"><data key="edge_relationship_id">R131_R023</data><data key="edge_source_entity_id">DATA_ERPS_ORG_ID</data><data key="edge_relationship_type">constructed_under</data><data key="edge_target_entity_id">R131_E014</data><data key="edge_operational_context">SSA assigns organizational identifier using location ZIP plus sequence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R024" source="APP_ERPS" target="R131_E013"><data key="edge_relationship_id">R131_R024</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">holds_attribute</data><data key="edge_target_entity_id">R131_E013</data><data key="edge_operational_context">Physical location is entered for organizational payee registration and affects ID construction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R025" source="APP_ERPS" target="R131_E015"><data key="edge_relationship_id">R131_R025</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">constrains_joint_guardian_record_to</data><data key="edge_target_entity_id">R131_E015</data><data key="edge_operational_context">Joint guardians cannot each serve as independent record key for the same appointment; first named SSN identifies the record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R026" source="R131_E015" target="DATA_ERPS_INDIVIDUAL_ID"><data key="edge_relationship_id">R131_R026</data><data key="edge_source_entity_id">R131_E015</data><data key="edge_relationship_type">uses_identifier_type</data><data key="edge_target_entity_id">DATA_ERPS_INDIVIDUAL_ID</data><data key="edge_operational_context">Joint guardian arrangement is identified by first named guardian SSN, not by a compound person identifier.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R027" source="APP_ERPS" target="R131_E016"><data key="edge_relationship_id">R131_R027</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">uses_classification_rule</data><data key="edge_target_entity_id">R131_E016</data><data key="edge_operational_context">Current POMS says legal structure determines whether applicant is coded Individual or Organization.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R028" source="R131_E016" target="DATA_ERPS_ORG_ID"><data key="edge_relationship_id">R131_R028</data><data key="edge_source_entity_id">R131_E016</data><data key="edge_relationship_type">affects_record_identifier</data><data key="edge_target_entity_id">DATA_ERPS_ORG_ID</data><data key="edge_operational_context">Organization coding results in ZIP-plus-sequence record key.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R029" source="R131_E016" target="PROC_ERPS_EIN_VERIFICATION"><data key="edge_relationship_id">R131_R029</data><data key="edge_source_entity_id">R131_E016</data><data key="edge_relationship_type">requires_manager_ein_verification</data><data key="edge_target_entity_id">PROC_ERPS_EIN_VERIFICATION</data><data key="edge_operational_context">Corporate/government payees require verification of EIN using organizational records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R030" source="R131_E016" target="SYS_MBR"><data key="edge_relationship_id">R131_R030</data><data key="edge_source_entity_id">R131_E016</data><data key="edge_relationship_type">affects_payment_record_type_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Payee type is separately recorded on MBR with program payment information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R031" source="R131_E016" target="SYS_SSR"><data key="edge_relationship_id">R131_R031</data><data key="edge_source_entity_id">R131_E016</data><data key="edge_relationship_type">affects_payment_record_type_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Payee type is separately recorded on SSR with program payment information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R032" source="PROC_IRMAA_NEW_INITIAL" target="R131_E017"><data key="edge_relationship_id">R131_R032</data><data key="edge_source_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="edge_relationship_type">uses_nonautomatic_spouse_propagation_rule</data><data key="edge_target_entity_id">R131_E017</data><data key="edge_operational_context">New determination applies to requesting individual only; spouse/ex-spouse must act separately.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R033" source="PROC_IRMAA_NEW_INITIAL" target="R131_E018"><data key="edge_relationship_id">R131_R033</data><data key="edge_source_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="edge_relationship_type">may_collect_last_known_third_party_contact</data><data key="edge_target_entity_id">R131_E018</data><data key="edge_operational_context">Beneficiary can supply spouse last known address when claiming they did not reside together for an entire tax year.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R034" source="PROC_IRMAA_NEW_INITIAL" target="R131_E019"><data key="edge_relationship_id">R131_R034</data><data key="edge_source_entity_id">PROC_IRMAA_NEW_INITIAL</data><data key="edge_relationship_type">requires_tax_correction_documentation_under</data><data key="edge_target_entity_id">R131_E019</data><data key="edge_operational_context">POMS requires proof of IRS-amended/corrected tax information; allegation alone insufficient.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R035" source="R131_E019" target="DATA_IRS_ACCOUNT_TRANSCRIPT"><data key="edge_relationship_id">R131_R035</data><data key="edge_source_entity_id">R131_E019</data><data key="edge_relationship_type">may_accept</data><data key="edge_target_entity_id">DATA_IRS_ACCOUNT_TRANSCRIPT</data><data key="edge_operational_context">IRS account or related tax transcript can corroborate corrected tax record as appropriate.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">POMS generally mentions IRS transcript, not exact category in each scenario.</data></edge><edge id="R131_R036" source="R131_E019" target="ORG_IRS"><data key="edge_relationship_id">R131_R036</data><data key="edge_source_entity_id">R131_E019</data><data key="edge_relationship_type">uses_source_agency</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Correction must be supported by IRS information before SSA uses a revised MAGI amount.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R037" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="R131_E020"><data key="edge_relationship_id">R131_R037</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">collects_institution_contact_address</data><data key="edge_target_entity_id">R131_E020</data><data key="edge_operational_context">Financial resource interview asks for institution name and address in association with alleged asset.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R038" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="R131_E021"><data key="edge_relationship_id">R131_R038</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R131_E021</data><data key="edge_operational_context">SSI RZ procedure specifies financial institution contact permission requirement.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R039" source="UI_CCE_FIN_ACCOUNTS" target="DATA_SSR_DD_INDICATOR"><data key="edge_relationship_id">R131_R039</data><data key="edge_source_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_relationship_type">records_financial_account_identified_by</data><data key="edge_target_entity_id">DATA_SSR_DD_INDICATOR</data><data key="edge_operational_context">Direct deposit indicator may serve as lead to separately record relevant account as SSI resource.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R040" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="R131_E022"><data key="edge_relationship_id">R131_R040</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">applies_early_payment_exclusion</data><data key="edge_target_entity_id">R131_E022</data><data key="edge_operational_context">Resource calculation examines transaction-level bank history and excludes appropriately advance-dated SSI receipt.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R041" source="R131_E022" target="DATA_FI_BANK_STATEMENT_EVIDENCE"><data key="edge_relationship_id">R131_R041</data><data key="edge_source_entity_id">R131_E022</data><data key="edge_relationship_type">uses_evidence_from</data><data key="edge_target_entity_id">DATA_FI_BANK_STATEMENT_EVIDENCE</data><data key="edge_operational_context">SSA considers bank transactions and documentary record when computing first-of-month countable balance.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R042" source="APP_IRMAA" target="R131_E023"><data key="edge_relationship_id">R131_R042</data><data key="edge_source_entity_id">APP_IRMAA</data><data key="edge_relationship_type">generates_notice_product</data><data key="edge_target_entity_id">R131_E023</data><data key="edge_operational_context">Type 690 communicates reconsideration affirmation after annual verification.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R043" source="APP_IRMAA" target="R131_E024"><data key="edge_relationship_id">R131_R043</data><data key="edge_source_entity_id">APP_IRMAA</data><data key="edge_relationship_type">generates_notice_product</data><data key="edge_target_entity_id">R131_E024</data><data key="edge_operational_context">Type 700 communicates corrected IRMAA decision following reconsideration.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R044" source="SYS_NUMIDENT" target="R131_E025"><data key="edge_relationship_id">R131_R044</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">has_privacy_governed_fraud_contact_category</data><data key="edge_target_entity_id">R131_E025</data><data key="edge_operational_context">Updated SORN 60-0058 includes application-derived contact data for fraud review. It does not imply universal authoritative address status.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R045" source="R131_E025" target="SYS_NUMIDENT"><data key="edge_relationship_id">R131_R045</data><data key="edge_source_entity_id">R131_E025</data><data key="edge_relationship_type">subject_to_governance</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SORN governs purpose and disclosure, not record update behavior.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R046" source="DATA_HRS_SER" target="R131_E026"><data key="edge_relationship_id">R131_R046</data><data key="edge_source_entity_id">DATA_HRS_SER</data><data key="edge_relationship_type">has_current_distribution_exclusion</data><data key="edge_target_entity_id">R131_E026</data><data key="edge_operational_context">HRS product release page explicitly excludes social security weights from this summary earnings distribution.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Competing historical relationship preserved and flagged.</data></edge><edge id="R131_R047" source="EX_TREASURY_OACT_MONTHLY_TRUST_DATA" target="R131_E027"><data key="edge_relationship_id">R131_R047</data><data key="edge_source_entity_id">EX_TREASURY_OACT_MONTHLY_TRUST_DATA</data><data key="edge_relationship_type">feeds_monthly_annual_financial_reporting</data><data key="edge_target_entity_id">R131_E027</data><data key="edge_operational_context">OACT states Treasury manages trust funds and supplies monthly operations/investment information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R048" source="R131_E027" target="DATA_OACT_TRUST_FUND_HOLDINGS"><data key="edge_relationship_id">R131_R048</data><data key="edge_source_entity_id">R131_E027</data><data key="edge_relationship_type">supports_publication_dataset</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_HOLDINGS</data><data key="edge_operational_context">OACT publishes end-of-month investment holdings from monthly Treasury-provided financial information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R049" source="R131_E027" target="DATA_OACT_TRUST_FUND_TRANSACTIONS"><data key="edge_relationship_id">R131_R049</data><data key="edge_source_entity_id">R131_E027</data><data key="edge_relationship_type">supports_publication_dataset</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_TRANSACTIONS</data><data key="edge_operational_context">OACT supplies monthly and annual trust-fund transaction views.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R050" source="APP_ERPS" target="R131_E028"><data key="edge_relationship_id">R131_R050</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">uses_applicant_video_identity_control</data><data key="edge_target_entity_id">R131_E028</data><data key="edge_operational_context">SSA supports approved remote interviews when other requirements permit; NUMIDENT or organizational verification still required.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R051" source="R131_E028" target="SYS_NUMIDENT"><data key="edge_relationship_id">R131_R051</data><data key="edge_source_entity_id">R131_E028</data><data key="edge_relationship_type">checks_individual_identity_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Video identity confirmation for individual applicant uses NUMIDENT.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R052" source="R131_E028" target="R131_E013"><data key="edge_relationship_id">R131_R052</data><data key="edge_source_entity_id">R131_E028</data><data key="edge_relationship_type">checks_organization_location_attribute</data><data key="edge_target_entity_id">R131_E013</data><data key="edge_operational_context">Remote organizational applicant verification includes the organization physical address and EIN; distinct from payee customer residence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R053" source="PROC_ERPS_EIN_VERIFICATION" target="R131_E029"><data key="edge_relationship_id">R131_R053</data><data key="edge_source_entity_id">PROC_ERPS_EIN_VERIFICATION</data><data key="edge_relationship_type">observes_identity_collision_risk</data><data key="edge_target_entity_id">R131_E029</data><data key="edge_operational_context">SSA POMS notes shared or multiple organizational EINs; EIN alone cannot uniquely identify physical payee location.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R131_R054" source="R131_E029" target="DATA_ERPS_ORG_ID"><data key="edge_relationship_id">R131_R054</data><data key="edge_source_entity_id">R131_E029</data><data key="edge_relationship_type">motivates_secondary_organization_identifier</data><data key="edge_target_entity_id">DATA_ERPS_ORG_ID</data><data key="edge_operational_context">eRPS uses physical ZIP plus sequence for internal organization identifier.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0001" source="ORG_DDS" target="R132_E0001"><data key="edge_relationship_id">R132_R0001</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">maintains_records_category</data><data key="edge_target_entity_id">R132_E0001</data><data key="edge_operational_context">DDS case intake/release requires manual case control records retained at least 12 months after final release.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0002" source="ORG_DDS" target="R132_E0003"><data key="edge_relationship_id">R132_R0002</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">maintains_records_category</data><data key="edge_target_entity_id">R132_E0003</data><data key="edge_operational_context">DDS system-produced edits, alerts, tapes and printouts are classified as SSA data acquisition and response records.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0003" source="R132_E0003" target="R132_E0004"><data key="edge_relationship_id">R132_R0003</data><data key="edge_source_entity_id">R132_E0003</data><data key="edge_relationship_type">subject_to_retention_rule</data><data key="edge_target_entity_id">R132_E0004</data><data key="edge_operational_context">Acquire/response records retained for at least five days, at most 90 days, under POMS, for corrections/reconstruction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0004" source="DB_DDS_CE_PROVIDER_FILE" target="R132_E0002"><data key="edge_relationship_id">R132_R0004</data><data key="edge_source_entity_id">DB_DDS_CE_PROVIDER_FILE</data><data key="edge_relationship_type">subject_to_retention_rule</data><data key="edge_target_entity_id">R132_E0002</data><data key="edge_operational_context">Consultative-provider files are purged every six years except in open audits.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0005" source="ORG_DDS" target="R132_E0005"><data key="edge_relationship_id">R132_R0005</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">retains_nonmedical_residual_records</data><data key="edge_target_entity_id">R132_E0005</data><data key="edge_operational_context">Nonmedical DDS leftover case material survives transfer pending adjudication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0006" source="R132_E0005" target="R132_E0006"><data key="edge_relationship_id">R132_R0006</data><data key="edge_source_entity_id">R132_E0005</data><data key="edge_relationship_type">subject_to_retention_rule</data><data key="edge_target_entity_id">R132_E0006</data><data key="edge_operational_context">Residual nonmedical case documentation retained until adjudication, then disposed when no longer needed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0007" source="ORG_DDS" target="R132_E0007"><data key="edge_relationship_id">R132_R0007</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">generates_statistical_product_family</data><data key="edge_target_entity_id">R132_E0007</data><data key="edge_operational_context">DDS maintains noncontrolled, routine statistical and operational reports.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0008" source="R132_E0007" target="R132_E0008"><data key="edge_relationship_id">R132_R0008</data><data key="edge_source_entity_id">R132_E0007</data><data key="edge_relationship_type">subject_to_retention_rule</data><data key="edge_target_entity_id">R132_E0008</data><data key="edge_operational_context">Six-year destruction rule for DDS routine reports.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0009" source="ORG_DDS" target="R132_E0009"><data key="edge_relationship_id">R132_R0009</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">subject_to_fiscal_record_retention</data><data key="edge_target_entity_id">R132_E0009</data><data key="edge_operational_context">Selected vouchers, letter of credit and facilities/equipment records remain until federal audit closure.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0010" source="ORG_DDS" target="R132_E0010"><data key="edge_relationship_id">R132_R0010</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">subject_to_correspondence_record_retention</data><data key="edge_target_entity_id">R132_E0010</data><data key="edge_operational_context">General communication and reference DDS files have a six-year disposal schedule.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0011" source="ORG_DDS" target="R132_E0011"><data key="edge_relationship_id">R132_R0011</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">subject_to_it_acquisition_gate</data><data key="edge_target_entity_id">R132_E0011</data><data key="edge_operational_context">State DDS major IT acquisitions require Central Office advance written approval.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0012" source="R132_E0011" target="R132_E0012"><data key="edge_relationship_id">R132_R0012</data><data key="edge_source_entity_id">R132_E0011</data><data key="edge_relationship_type">requires_feasibility_evidence</data><data key="edge_target_entity_id">R132_E0012</data><data key="edge_operational_context">New or replacement DDS system proposal requires feasibility and cost-benefit analysis.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0013" source="ORG_DDS" target="R132_E0012"><data key="edge_relationship_id">R132_R0013</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">must_document_new_replacement_it</data><data key="edge_target_entity_id">R132_E0012</data><data key="edge_operational_context">DDS IT feasibility studies for State review may substitute if covering all required criteria.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0014" source="ORG_DDS" target="R132_E0013"><data key="edge_relationship_id">R132_R0014</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">subject_to_accuracy_oversight</data><data key="edge_target_entity_id">R132_E0013</data><data key="edge_operational_context">DDS initial performance accuracy below 90.6 percent triggers joint corrective-action analysis.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0015" source="PROC_DDS_ACCURACY_REVIEW" target="R132_E0013"><data key="edge_relationship_id">R132_R0015</data><data key="edge_source_entity_id">PROC_DDS_ACCURACY_REVIEW</data><data key="edge_relationship_type">evaluated_against_threshold</data><data key="edge_target_entity_id">R132_E0013</data><data key="edge_operational_context">Initial performance review effectiveness assessed using 90.6 percent published benchmark.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0016" source="ORG_DDS" target="R132_E0014"><data key="edge_relationship_id">R132_R0016</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">tracked_by_indicator_family</data><data key="edge_target_entity_id">R132_E0014</data><data key="edge_operational_context">Accuracy is evaluated alongside timeliness, pending counts, aged cases, personnel and PPWY.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0017" source="ORG_DDS" target="R132_E0015"><data key="edge_relationship_id">R132_R0017</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">maintains_management_monitoring_process</data><data key="edge_target_entity_id">R132_E0015</data><data key="edge_operational_context">States are responsible for day-to-day monitoring while SSA sets performance standards and provides oversight.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0018" source="R132_E0015" target="R132_E0016"><data key="edge_relationship_id">R132_R0018</data><data key="edge_source_entity_id">R132_E0015</data><data key="edge_relationship_type">may_generate_special_reports</data><data key="edge_target_entity_id">R132_E0016</data><data key="edge_operational_context">DDS management can analyze types of errors, adjudicator error patterns and CE/technical denial review types.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0019" source="R132_E0015" target="R132_E0014"><data key="edge_relationship_id">R132_R0019</data><data key="edge_source_entity_id">R132_E0015</data><data key="edge_relationship_type">uses_performance_indicator_family</data><data key="edge_target_entity_id">R132_E0014</data><data key="edge_operational_context">Continuous DDS monitoring uses management information and QA data; no common IT platform identified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0020" source="DATA_DDS_ACCURACY" target="R132_E0013"><data key="edge_relationship_id">R132_R0020</data><data key="edge_source_entity_id">DATA_DDS_ACCURACY</data><data key="edge_relationship_type">informs_oversight_threshold</data><data key="edge_target_entity_id">R132_E0013</data><data key="edge_operational_context">DDS accuracy statistics help assess compliance with initial-performance standard.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0021" source="ORG_DDS" target="R132_E0017"><data key="edge_relationship_id">R132_R0021</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">submits_quarterly_obligation_reports</data><data key="edge_target_entity_id">R132_E0017</data><data key="edge_operational_context">Quarterly signed SSA-4513 plus appropriate Addendum records financial commitments by federal fiscal year.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0022" source="R132_E0017" target="FORM_SSA4513"><data key="edge_relationship_id">R132_R0022</data><data key="edge_source_entity_id">R132_E0017</data><data key="edge_relationship_type">uses_reporting_form</data><data key="edge_target_entity_id">FORM_SSA4513</data><data key="edge_operational_context">SSA-4513 reports quarter-to-date cumulative obligations for DDS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0023" source="R132_E0017" target="FORM_SSA4513_ADD"><data key="edge_relationship_id">R132_R0023</data><data key="edge_source_entity_id">R132_E0017</data><data key="edge_relationship_type">may_include_addendum</data><data key="edge_target_entity_id">FORM_SSA4513_ADD</data><data key="edge_operational_context">Addendum supplies unliquidated obligations, financial adjustments, indirect cost agreements.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0024" source="R132_E0017" target="R132_E0018"><data key="edge_relationship_id">R132_R0024</data><data key="edge_source_entity_id">R132_E0017</data><data key="edge_relationship_type">separates_prior_year_balances</data><data key="edge_target_entity_id">R132_E0018</data><data key="edge_operational_context">State DDS prepares separate SSA-4513 for each past FY having unliquidated balances.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0025" source="R132_E0017" target="R132_E0020"><data key="edge_relationship_id">R132_R0025</data><data key="edge_source_entity_id">R132_E0017</data><data key="edge_relationship_type">subject_to_filing_deadline</data><data key="edge_target_entity_id">R132_E0020</data><data key="edge_operational_context">Signed SSA-4513 due by 25th day of month following quarter close.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0026" source="PROC_DDS_STATE_FUNDING_AUTH" target="R132_E0017"><data key="edge_relationship_id">R132_R0026</data><data key="edge_source_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="edge_relationship_type">uses_quarterly_obligation_data</data><data key="edge_target_entity_id">R132_E0017</data><data key="edge_operational_context">State DDS financial oversight references fiscal year obligation reporting rather than inferred award or grant disbursement data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0027" source="ORG_DDS" target="R132_E0019"><data key="edge_relationship_id">R132_R0027</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">may_supply_transaction_validation_sample</data><data key="edge_target_entity_id">R132_E0019</data><data key="edge_operational_context">One randomly selected state quarterly supplies three state-selected transactions for SSA regional review.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0028" source="R132_E0019" target="R132_E0017"><data key="edge_relationship_id">R132_R0028</data><data key="edge_source_entity_id">R132_E0019</data><data key="edge_relationship_type">validates_quarterly_obligation_reporting</data><data key="edge_target_entity_id">R132_E0017</data><data key="edge_operational_context">Accounting transactions or invoices are evidence supporting SSA-4513 information.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0029" source="PLAT_BSO" target="R132_E0021"><data key="edge_relationship_id">R132_R0029</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">pilots_access_authorization_flow</data><data key="edge_target_entity_id">R132_E0021</data><data key="edge_operational_context">BSO pilot launched January 10, 2026; avoid treating pilot as agencywide launch.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0030" source="PROC_BSO_AUTHORIZATION" target="R132_E0021"><data key="edge_relationship_id">R132_R0030</data><data key="edge_source_entity_id">PROC_BSO_AUTHORIZATION</data><data key="edge_relationship_type">evaluates_pilot_authorization</data><data key="edge_target_entity_id">R132_E0021</data><data key="edge_operational_context">Employer authorization redesign includes a pilot stage, not evidence of final migration.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0031" source="R132_E0021" target="R132_E0022"><data key="edge_relationship_id">R132_R0031</data><data key="edge_source_entity_id">R132_E0021</data><data key="edge_relationship_type">grants_pilot_access_to_role</data><data key="edge_target_entity_id">R132_E0022</data><data key="edge_operational_context">Pilot permits Responsible Entity Officers and delegated users for participating entities.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0032" source="PLAT_BSO" target="R132_E0022"><data key="edge_relationship_id">R132_R0032</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">recognizes_entity_level_access_role</data><data key="edge_target_entity_id">R132_E0022</data><data key="edge_operational_context">Responsible Entity Officer role manages access for participating employer entities.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0033" source="DB_HA_CASE_CONTROL_RECORDS" target="R132_E0023"><data key="edge_relationship_id">R132_R0033</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">supports_record_retrieval_by</data><data key="edge_target_entity_id">R132_E0023</data><data key="edge_operational_context">SORN documents SSN, name and folder number as retrieval routes.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0034" source="DB_HA_CASE_CONTROL_RECORDS" target="R132_E0024"><data key="edge_relationship_id">R132_R0034</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">governed_by_tax_data_use_restriction</data><data key="edge_target_entity_id">R132_E0024</data><data key="edge_operational_context">IRS return information in HA records remains constrained by IRC 6103.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0035" source="DB_HA_CASE_CONTROL_RECORDS" target="R132_E0025"><data key="edge_relationship_id">R132_R0035</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">subject_to_relevant_nara_schedules</data><data key="edge_target_entity_id">R132_E0025</data><data key="edge_operational_context">H&amp;A SORN references leadership and legal retention schedules for records within applicable categories.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0036" source="PROC_MANUAL_RP_SELECTION" target="R132_E0027"><data key="edge_relationship_id">R132_R0036</data><data key="edge_source_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="edge_relationship_type">uses_title_xvi_manual_exception</data><data key="edge_target_entity_id">R132_E0027</data><data key="edge_operational_context">Rep payee without SSN requires documented manual SSI record processing.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0037" source="R132_E0027" target="R132_E0026"><data key="edge_relationship_id">R132_R0037</data><data key="edge_source_entity_id">R132_E0027</data><data key="edge_relationship_type">accepts_manual_ssi_form</data><data key="edge_target_entity_id">R132_E0026</data><data key="edge_operational_context">SSA-450 provides documented alternate SSI manual input route.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0038" source="R132_E0027" target="FORM_SSA1719B"><data key="edge_relationship_id">R132_R0038</data><data key="edge_source_entity_id">R132_E0027</data><data key="edge_relationship_type">accepts_manual_1719b</data><data key="edge_target_entity_id">FORM_SSA1719B</data><data key="edge_operational_context">SSA-1719B manual input is permitted in applicable no-SSN cases.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R132_R0039" source="R132_E0027" target="SYS_SSR"><data key="edge_relationship_id">R132_R0039</data><data key="edge_source_entity_id">R132_E0027</data><data key="edge_relationship_type">supports_conditional_ssr_record_action</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Specific manual form procedure may update SSR; not an unconditional address or identity cross-system sync.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R132_R0040" source="DB_AC_WORKING_FILE" target="R132_E0028"><data key="edge_relationship_id">R132_R0040</data><data key="edge_source_entity_id">DB_AC_WORKING_FILE</data><data key="edge_relationship_type">subject_to_new_condition_filing_exception</data><data key="edge_target_entity_id">R132_E0028</data><data key="edge_operational_context">Pending AC case may coexist with new application only under specified new-critical/disabling-condition exception.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R132_R0041" source="APP_EDCS" target="R132_E0028"><data key="edge_relationship_id">R132_R0041</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_conditional_appeal_filing_development</data><data key="edge_target_entity_id">R132_E0028</data><data key="edge_operational_context">EDCS Appeals segment receives documentation to support downstream AC processing in specified cases.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R133_R0001" source="R133_E0001" target="R133_E0006"><data key="edge_relationship_id">R133_R0001</data><data key="edge_source_entity_id">R133_E0001</data><data key="edge_relationship_type">accepts_request</data><data key="edge_target_entity_id">R133_E0006</data><data key="edge_operational_context">Title II service-center reclamation document and abandonment requests are entered via TOFR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0002" source="R133_E0006" target="R133_E0001"><data key="edge_relationship_id">R133_R0002</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">uses_application</data><data key="edge_target_entity_id">R133_E0001</data><data key="edge_operational_context">Title II documentation request workflows use TOFR after checking existing systems.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0003" source="R133_E0006" target="SVC_TCIS"><data key="edge_relationship_id">R133_R0003</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">Before seeking a Treasury document, PC checks TCIS Dashboard for available documents.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0004" source="R133_E0006" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">R133_R0004</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">Before seeking Treasury document, PC verifies if Paperless already has its PDF.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0005" source="R133_E0003" target="SVC_TCIS"><data key="edge_relationship_id">R133_R0005</data><data key="edge_source_entity_id">R133_E0003</data><data key="edge_relationship_type">user_interface_of</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">Reclamation document images are accessible on the TCIS Dashboard but not necessarily TCIS Claims Detail.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0006" source="R133_E0006" target="R133_E0003"><data key="edge_relationship_id">R133_R0006</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">R133_E0003</data><data key="edge_operational_context">Treasury Dashboard document presence is checked before TOFR request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0007" source="R133_E0004" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">R133_R0007</data><data key="edge_source_entity_id">R133_E0004</data><data key="edge_relationship_type">transmits_data_to</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">Treasury provides PDF reclamation documents electronically to PSC Paperless via Web-Paperless Interface.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0008" source="R133_E0006" target="R133_E0004"><data key="edge_relationship_id">R133_R0008</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">uses_interface</data><data key="edge_target_entity_id">R133_E0004</data><data key="edge_operational_context">Pre-request check identifies documents arriving via Web-Paperless.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0009" source="R133_E0006" target="DATA_PPC_ACR"><data key="edge_relationship_id">R133_R0009</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">uses_record</data><data key="edge_target_entity_id">DATA_PPC_ACR</data><data key="edge_operational_context">PSC annotates its Action Control Record when TOFR or email inquiry is sent.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0010" source="R133_E0006" target="R133_E0005"><data key="edge_relationship_id">R133_R0010</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">queues_followup_in</data><data key="edge_target_entity_id">R133_E0005</data><data key="edge_operational_context">Action Control Record goes into Development Hold File for 30-day control and second request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0011" source="R133_E0006" target="R133_E0002"><data key="edge_relationship_id">R133_R0011</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">identifies_case_with</data><data key="edge_target_entity_id">R133_E0002</data><data key="edge_operational_context">Treasury reclamation ticket number from TCIS Claims Detail identifies the request.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0012" source="R133_E0002" target="SVC_TCIS"><data key="edge_relationship_id">R133_R0012</data><data key="edge_source_entity_id">R133_E0002</data><data key="edge_relationship_type">retrieved_from</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">TCIS Claims Detail tab records Treasury reclamation ticket identifiers.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0013" source="R133_E0006" target="R133_E0007"><data key="edge_relationship_id">R133_R0013</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">requests</data><data key="edge_target_entity_id">R133_E0007</data><data key="edge_operational_context">FS-133 reclamation notice is one of the documents requested through TOFR.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0014" source="R133_E0006" target="R133_E0008"><data key="edge_relationship_id">R133_R0014</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">requests</data><data key="edge_target_entity_id">R133_E0008</data><data key="edge_operational_context">FS-135 debit request is subject to limited eligibility/availability conditions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0015" source="R133_E0006" target="R133_E0017"><data key="edge_relationship_id">R133_R0015</data><data key="edge_source_entity_id">R133_E0006</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R133_E0017</data><data key="edge_operational_context">Document requests usually wait for the financial institution response period.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0016" source="R133_E0007" target="R133_E0003"><data key="edge_relationship_id">R133_R0016</data><data key="edge_source_entity_id">R133_E0007</data><data key="edge_relationship_type">viewed_in</data><data key="edge_target_entity_id">R133_E0003</data><data key="edge_operational_context">FS-133 image is accessible in TCIS Dashboard under documented conditions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0017" source="R133_E0008" target="R133_E0003"><data key="edge_relationship_id">R133_R0017</data><data key="edge_source_entity_id">R133_E0008</data><data key="edge_relationship_type">viewed_in</data><data key="edge_target_entity_id">R133_E0003</data><data key="edge_operational_context">FS-135 is a Treasury debit request document, distinct from Notice FS-133.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0018" source="R133_E0010" target="R133_E0001"><data key="edge_relationship_id">R133_R0018</data><data key="edge_source_entity_id">R133_E0010</data><data key="edge_relationship_type">uses_application</data><data key="edge_target_entity_id">R133_E0001</data><data key="edge_operational_context">Title II check-reclamation abandonment requests use TOFR via PSC.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0019" source="R133_E0010" target="R133_E0009"><data key="edge_relationship_id">R133_R0019</data><data key="edge_source_entity_id">R133_E0010</data><data key="edge_relationship_type">uses_form</data><data key="edge_target_entity_id">R133_E0009</data><data key="edge_operational_context">After Treasury check abandonment request, SSA-4208 is coded to update debt accounting.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0020" source="R133_E0010" target="R133_E0013"><data key="edge_relationship_id">R133_R0020</data><data key="edge_source_entity_id">R133_E0010</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">R133_E0013</data><data key="edge_operational_context">For Title XVI erroneous death, SSA examines SSR PMTH credits before Treasury abandonment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0021" source="R133_E0013" target="DATA_SSR_PMTH"><data key="edge_relationship_id">R133_R0021</data><data key="edge_source_entity_id">R133_E0013</data><data key="edge_relationship_type">is_attribute_of</data><data key="edge_target_entity_id">DATA_SSR_PMTH</data><data key="edge_operational_context">SSI reclamation credits appear in SSR Payment History PMTH payflag fields.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0022" source="R133_E0012" target="SYS_SSR"><data key="edge_relationship_id">R133_R0022</data><data key="edge_source_entity_id">R133_E0012</data><data key="edge_relationship_type">is_attribute_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI U TAC is a documented flag on the Supplemental Security Record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0023" source="R133_E0010" target="R133_E0012"><data key="edge_relationship_id">R133_R0023</data><data key="edge_source_entity_id">R133_E0010</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">R133_E0012</data><data key="edge_operational_context">If funds already credited on SSI PMTH, employee posts U TAC before Treasury abandons reclamation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0024" source="R133_E0012" target="R133_E0014"><data key="edge_relationship_id">R133_R0024</data><data key="edge_source_entity_id">R133_E0012</data><data key="edge_relationship_type">prevents</data><data key="edge_target_entity_id">R133_E0014</data><data key="edge_operational_context">SSI U-TAC prevents erroneous underpayment re-release after Treasury reverses an incorrect reclamation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0025" source="R133_E0010" target="R133_E0014"><data key="edge_relationship_id">R133_R0025</data><data key="edge_source_entity_id">R133_E0010</data><data key="edge_relationship_type">may_result_in</data><data key="edge_target_entity_id">R133_E0014</data><data key="edge_operational_context">A Treasury return plus family repayment can lead to double recovery and manual reconciliation.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0026" source="R133_E0011" target="PROC_EFT_RECLAMATION"><data key="edge_relationship_id">R133_R0026</data><data key="edge_source_entity_id">R133_E0011</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">PROC_EFT_RECLAMATION</data><data key="edge_operational_context">Separate EFT reversal procedure addresses U.S. bank payment reclamation and excludes already returned SSA credits.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0027" source="R133_E0011" target="R133_E0014"><data key="edge_relationship_id">R133_R0027</data><data key="edge_source_entity_id">R133_E0011</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">R133_E0014</data><data key="edge_operational_context">EFT abandon request does not automatically refund bank when SSA already received payment; use dual-recovery procedures.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0028" source="R133_E0015" target="DB_PHUS"><data key="edge_relationship_id">R133_R0028</data><data key="edge_source_entity_id">R133_E0015</data><data key="edge_relationship_type">is_attribute_of</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">Title II returned payments usually post event 009 RET CHECK to PHUS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0029" source="R133_E0016" target="SYS_MBR"><data key="edge_relationship_id">R133_R0029</data><data key="edge_source_entity_id">R133_E0016</data><data key="edge_relationship_type">is_attribute_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Returned Title II payment normally reduces BSPA on MBR; exceptions require manual posting.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0030" source="R133_E0016" target="DB_PHUS"><data key="edge_relationship_id">R133_R0030</data><data key="edge_source_entity_id">R133_E0016</data><data key="edge_relationship_type">is_attribute_of</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">Returned Title II payment normally also reduces BSPA on PHUS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0031" source="R133_E0018" target="MODEL_OACT_POPULATION"><data key="edge_relationship_id">R133_R0031</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">consumes</data><data key="edge_target_entity_id">MODEL_OACT_POPULATION</data><data key="edge_operational_context">Historical and projected Social Security area population by single-year age and sex is a primary input.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0032" source="R133_E0018" target="R133_E0019"><data key="edge_relationship_id">R133_R0032</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">consumes</data><data key="edge_target_entity_id">R133_E0019</data><data key="edge_operational_context">SSI historical current and suspended recipient counts by age/sex/qualification are a primary input.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0033" source="R133_E0018" target="R133_E0020"><data key="edge_relationship_id">R133_R0033</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">consumes</data><data key="edge_target_entity_id">R133_E0020</data><data key="edge_operational_context">SSI historical status transitions into/out of current payment are a primary input.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0034" source="R133_E0018" target="R133_E0021"><data key="edge_relationship_id">R133_R0034</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">consumes</data><data key="edge_target_entity_id">R133_E0021</data><data key="edge_operational_context">Historical total federal SSI payments by demographic and eligibility categories are a primary input.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0035" source="R133_E0018" target="R133_E0022"><data key="edge_relationship_id">R133_R0035</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">uses_rule</data><data key="edge_target_entity_id">R133_E0022</data><data key="edge_operational_context">Separate projected flow types include awards, reinstatements, death, income suspension and other suspension.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0036" source="R133_E0018" target="DATA_SSI_AR_IVB1_APPLICATIONS"><data key="edge_relationship_id">R133_R0036</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB1_APPLICATIONS</data><data key="edge_operational_context">SSI Annual Report application forecasts form part of published projections; exact table processing not specified.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes">Methodological publication tie, not physical interface.</data></edge><edge id="R133_R0037" source="R133_E0018" target="DATA_SSI_AR_IVA1_POP"><data key="edge_relationship_id">R133_R0037</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">uses_assumptions_from</data><data key="edge_target_entity_id">DATA_SSI_AR_IVA1_POP</data><data key="edge_operational_context">2026 SSI projections incorporate 2026 Trustees population assumptions represented in SSI report Table IV.A1.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0038" source="R133_E0018" target="DATA_SSI_AR_IVA2_FBR"><data key="edge_relationship_id">R133_R0038</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">uses_assumptions_from</data><data key="edge_target_entity_id">DATA_SSI_AR_IVA2_FBR</data><data key="edge_operational_context">2026 SSI payments projection incorporates federal benefit rate assumptions and COLA from Table IV.A2.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0039" source="R133_E0018" target="REPORT_SSI_ANNUAL_2026"><data key="edge_relationship_id">R133_R0039</data><data key="edge_source_entity_id">R133_E0018</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_operational_context">2026 Annual SSI Report publishes model recipient and payment projections for 2026 through 2050.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0040" source="R133_E0023" target="APP_EDCS"><data key="edge_relationship_id">R133_R0040</data><data key="edge_source_entity_id">R133_E0023</data><data key="edge_relationship_type">uses_application</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Title II medical CDR reconsideration is documented and transferred through EDCS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0041" source="APP_EDCS" target="DB_DCF"><data key="edge_relationship_id">R133_R0041</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">For Title II medical CDR reconsideration, EDCS transfer automatically updates DCF; excludes cases outside EDCS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0042" source="APP_EDCS" target="SYS_MBR"><data key="edge_relationship_id">R133_R0042</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For Title II medical CDR reconsideration EDCS transfer automatically updates MBR, with five-day verification and exception paths.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0043" source="R133_E0023" target="SYS_MBR"><data key="edge_relationship_id">R133_R0043</data><data key="edge_source_entity_id">R133_E0023</data><data key="edge_relationship_type">requires_check_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Field office verifies MBR updates within five days and performs manual actions if update fails.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0044" source="R133_E0024" target="DB_DCF"><data key="edge_relationship_id">R133_R0044</data><data key="edge_source_entity_id">R133_E0024</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Excluded Title II CDR reconsideration appeals can be entered in DCF through EDCS EEAI screen.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0045" source="DB_DCF" target="R133_E0025"><data key="edge_relationship_id">R133_R0045</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">R133_E0025</data><data key="edge_operational_context">DCF passes excluded CDR appeal information into Title II background program for MBR update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0046" source="R133_E0025" target="SYS_MBR"><data key="edge_relationship_id">R133_R0046</data><data key="edge_source_entity_id">R133_E0025</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Background program can post excluded Title II CDR appeal request to MBR without POS input.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0047" source="R133_E0024" target="R133_E0026"><data key="edge_relationship_id">R133_R0047</data><data key="edge_source_entity_id">R133_E0024</data><data key="edge_relationship_type">creates_work_control</data><data key="edge_target_entity_id">R133_E0026</data><data key="edge_operational_context">Certain excluded Title II CDR hearing appeals create ALJT2EX tickle in DCF.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0048" source="R133_E0026" target="DB_DCF"><data key="edge_relationship_id">R133_R0048</data><data key="edge_source_entity_id">R133_E0026</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">ALJT2EX tickle may not be visible in DCF pending-file/MI Central regular case lists.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0049" source="R133_E0028" target="R133_E0027"><data key="edge_relationship_id">R133_R0049</data><data key="edge_source_entity_id">R133_E0028</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">R133_E0027</data><data key="edge_operational_context">SSA 2023 OAG historical record identifies GDIT as awardee of 28321323FDX030127.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0050" source="R133_E0029" target="ORG_IBM"><data key="edge_relationship_id">R133_R0050</data><data key="edge_source_entity_id">R133_E0029</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">SSA 2023 OAG record identifies IBM as awardee of 28321322FDS030217.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R133_R0051" source="R133_E0015" target="R133_E0016"><data key="edge_relationship_id">R133_R0051</data><data key="edge_source_entity_id">R133_E0015</data><data key="edge_relationship_type">may_involve</data><data key="edge_target_entity_id">R133_E0016</data><data key="edge_operational_context">PHUS event 009 and MBR/PHUS BSPA reduction are related returned-payment status changes.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0001" source="PROC_1634_MEDICAID" target="R134_E0001"><data key="edge_relationship_id">R134_R0001</data><data key="edge_source_entity_id">PROC_1634_MEDICAID</data><data key="edge_relationship_type">is_subject_to_statutory_rule</data><data key="edge_target_entity_id">R134_E0001</data><data key="edge_operational_context">Section 1634 Medicaid eligibility association is subject to the new citizenship/status federal funding limits.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0002" source="ORG_STATE_MEDICAID" target="R134_E0001"><data key="edge_relationship_id">R134_R0002</data><data key="edge_source_entity_id">ORG_STATE_MEDICAID</data><data key="edge_relationship_type">applies_federal_eligibility_limits_under</data><data key="edge_target_entity_id">R134_E0001</data><data key="edge_operational_context">State Medicaid programs operate under the federal participation rule with listed exceptions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0003" source="PROC_1634_MEDICAID" target="R134_E0002"><data key="edge_relationship_id">R134_R0003</data><data key="edge_source_entity_id">PROC_1634_MEDICAID</data><data key="edge_relationship_type">will_be_subject_to</data><data key="edge_target_entity_id">R134_E0002</data><data key="edge_operational_context">Two-month retroactivity change is future-dated for SSI/SSP Medicaid determinations from January 2027.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0004" source="SYS_SSR" target="PROC_1634_MEDICAID"><data key="edge_relationship_id">R134_R0004</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_ssi_eligibility_context_for</data><data key="edge_target_entity_id">PROC_1634_MEDICAID</data><data key="edge_operational_context">SSI program eligibility serves as Medicaid determination or referral context in relevant Section 1634 states; not an inferred shared database.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0005" source="SYS_NUMIDENT" target="R134_E0003"><data key="edge_relationship_id">R134_R0005</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">subject_to_claims_eligibility_proof_limit</data><data key="edge_target_entity_id">R134_E0003</data><data key="edge_operational_context">Numident work authorization code is not a valid standalone legal presence proof for Title II benefit payment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0006" source="DATA_NUMIDENT_IDN_H" target="R134_E0003"><data key="edge_relationship_id">R134_R0006</data><data key="edge_source_entity_id">DATA_NUMIDENT_IDN_H</data><data key="edge_relationship_type">requires_later_status_proof_under</data><data key="edge_target_entity_id">R134_E0003</data><data key="edge_operational_context">IDN H is historical work authorization not current program eligibility proof.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0007" source="R108_E050" target="DATA_MBR_LAW_PRS"><data key="edge_relationship_id">R134_R0007</data><data key="edge_source_entity_id">R108_E050</data><data key="edge_relationship_type">requires_nonconflicting_previous_claim_evidence_from</data><data key="edge_target_entity_id">DATA_MBR_LAW_PRS</data><data key="edge_operational_context">MBR lawful-presence proof reuse requires qualifying PROOF and STATUS and review of archived claim remarks.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0008" source="R108_E050" target="R108_E048"><data key="edge_relationship_id">R134_R0008</data><data key="edge_source_entity_id">R108_E050</data><data key="edge_relationship_type">requires_nonconflicting_previous_claim_evidence_from</data><data key="edge_target_entity_id">R108_E048</data><data key="edge_operational_context">MCS archived CLLP proof and permanence coding must not have relied on Numident alone.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0009" source="R108_E050" target="UI_SSI_ALIEN_STATUS"><data key="edge_relationship_id">R134_R0009</data><data key="edge_source_entity_id">R108_E050</data><data key="edge_relationship_type">may_use_prior_ssi_alien_status_from</data><data key="edge_target_entity_id">UI_SSI_ALIEN_STATUS</data><data key="edge_operational_context">SSR and prior MSSICS may establish proof only with acceptable codes, validated evidence, and no conflicts.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0010" source="PROC_SSI_SAVE_VERIFICATION" target="R134_E0004"><data key="edge_relationship_id">R134_R0010</data><data key="edge_source_entity_id">PROC_SSI_SAVE_VERIFICATION</data><data key="edge_relationship_type">requires_document_retention_control</data><data key="edge_target_entity_id">R134_E0004</data><data key="edge_operational_context">SSI verification records are documented on CCE Report of Contact and evidence folder; ARN in Person Information when present.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0011" source="R134_E0004" target="APP_EP"><data key="edge_relationship_id">R134_R0011</data><data key="edge_source_entity_id">R134_E0004</data><data key="edge_relationship_type">retains_through</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Policy identifies Evidence Portal as one method for retaining documentary evidence and SAVE response.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0012" source="R134_E0004" target="DATA_PI_ARN"><data key="edge_relationship_id">R134_R0012</data><data key="edge_source_entity_id">R134_E0004</data><data key="edge_relationship_type">records_identifier_in</data><data key="edge_target_entity_id">DATA_PI_ARN</data><data key="edge_operational_context">Alien Registration Number from submitted immigration document entered in Person Information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0013" source="SVC_SAVE" target="R134_E0005"><data key="edge_relationship_id">R134_R0013</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">produces_exception_needing</data><data key="edge_target_entity_id">R134_E0005</data><data key="edge_operational_context">SAVE responses that do not confirm eligibility require additional development, not unexamined record writes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0014" source="R134_E0005" target="FORM_G845"><data key="edge_relationship_id">R134_R0014</data><data key="edge_source_entity_id">R134_E0005</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">FORM_G845</data><data key="edge_operational_context">G-845 used in defined Title II lawful-presence exceptions to inconclusive online SAVE.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0015" source="PROC_LAWFUL_PRESENCE_VERIFICATION" target="R134_E0005"><data key="edge_relationship_id">R134_R0015</data><data key="edge_source_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="edge_relationship_type">uses_alternative_verification</data><data key="edge_target_entity_id">R134_E0005</data><data key="edge_operational_context">Online SAVE must be corroborated by submitted immigration evidence; G-845 pathway available when online response is inapplicable.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0016" source="FORM_SSA8510" target="R134_E0006"><data key="edge_relationship_id">R134_R0016</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">subject_to_signature_rule</data><data key="edge_target_entity_id">R134_E0006</data><data key="edge_operational_context">SSA-8510 is not attestable and requires hand signature under SSI claims policy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0017" source="FORM_SSA8510" target="R134_E0008"><data key="edge_relationship_id">R134_R0017</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">subject_to_source_scope</data><data key="edge_target_entity_id">R134_E0008</data><data key="edge_operational_context">Each requested third-party disclosure requires an appropriately scoped consent.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0018" source="FORM_SSA8510" target="R134_E0009"><data key="edge_relationship_id">R134_R0018</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">subject_to_use_exceptions</data><data key="edge_target_entity_id">R134_E0009</data><data key="edge_operational_context">Financial institution, payroll, and medical authorizations have separate SSA forms.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0019" source="R134_E0007" target="FORM_SSA8510"><data key="edge_relationship_id">R134_R0019</data><data key="edge_source_entity_id">R134_E0007</data><data key="edge_relationship_type">documents_signed_form_receipt</data><data key="edge_target_entity_id">FORM_SSA8510</data><data key="edge_operational_context">SSI web page documents employees secured the signed paper form; it is not the signed form.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0020" source="FORM_SSA8510" target="R107_E006"><data key="edge_relationship_id">R134_R0020</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">excluded_for_financial_institution_authorization</data><data key="edge_target_entity_id">R107_E006</data><data key="edge_operational_context">SSI financial institution requests have separate consent form.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0021" source="FORM_SSA8510" target="DATA_SSA8240"><data key="edge_relationship_id">R134_R0021</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">excluded_for_payroll_provider_authorization</data><data key="edge_target_entity_id">DATA_SSA8240</data><data key="edge_operational_context">Payroll provider wage verification has separate authorization.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0022" source="FORM_SSA8510" target="FORM_SSA827"><data key="edge_relationship_id">R134_R0022</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">excluded_for_medical_information_authorization</data><data key="edge_target_entity_id">FORM_SSA827</data><data key="edge_operational_context">Medical records use SSA-827 authorization.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0023" source="R134_E0010" target="SYS_SSR"><data key="edge_relationship_id">R134_R0023</data><data key="edge_source_entity_id">R134_E0010</data><data key="edge_relationship_type">requires_prior_evidence_development_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">N05 is a legal SSI payment-status determination for past unpaid periods, not a master identity status update.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0024" source="DATA_DDS_CE_PROVIDER_LIST" target="R134_E0012"><data key="edge_relationship_id">R134_R0024</data><data key="edge_source_entity_id">DATA_DDS_CE_PROVIDER_LIST</data><data key="edge_relationship_type">subject_to_submission_deadline</data><data key="edge_target_entity_id">R134_E0012</data><data key="edge_operational_context">Annual provider list is uploaded to DA MPRO SharePoint within 45 days of federal fiscal year end.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0025" source="DATA_DDS_CE_MER_FEE_SCHEDULE" target="R134_E0012"><data key="edge_relationship_id">R134_R0025</data><data key="edge_source_entity_id">DATA_DDS_CE_MER_FEE_SCHEDULE</data><data key="edge_relationship_type">subject_to_submission_deadline</data><data key="edge_target_entity_id">R134_E0012</data><data key="edge_operational_context">Current CE/MER fee schedules are uploaded annually to DA MPRO SharePoint.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0026" source="DATA_DDS_CE_OVERSIGHT_REPORT" target="R134_E0013"><data key="edge_relationship_id">R134_R0026</data><data key="edge_source_entity_id">DATA_DDS_CE_OVERSIGHT_REPORT</data><data key="edge_relationship_type">reports_data_domain</data><data key="edge_target_entity_id">R134_E0013</data><data key="edge_operational_context">Annual CE oversight report includes fraud, site visits, complaints, licensing and medical professional relations activity.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0027" source="DATA_CE_PROVIDER_OVERSIGHT" target="R134_E0013"><data key="edge_relationship_id">R134_R0027</data><data key="edge_source_entity_id">DATA_CE_PROVIDER_OVERSIGHT</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">R134_E0013</data><data key="edge_operational_context">CE provider oversight record categories include related complaint and credential review information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0028" source="PROC_IRS_3857_RESOLUTION" target="R134_E0014"><data key="edge_relationship_id">R134_R0028</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">may_request_postal_contact_lead_under</data><data key="edge_target_entity_id">R134_E0014</data><data key="edge_operational_context">IRS scrambled-earnings/taxpayer SSN investigation may require a USPS address lookup.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0029" source="R134_E0014" target="FORM_SSA_L2001"><data key="edge_relationship_id">R134_R0029</data><data key="edge_source_entity_id">R134_E0014</data><data key="edge_relationship_type">uses_postal_request_form</data><data key="edge_target_entity_id">FORM_SSA_L2001</data><data key="edge_operational_context">SSA-L2001 is mailed to USPS; resulting address not established as verified residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0030" source="R134_E0014" target="ORG_USPS"><data key="edge_relationship_id">R134_R0030</data><data key="edge_source_entity_id">R134_E0014</data><data key="edge_relationship_type">asks_address_from</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">Separate USPS sourced contact lead does not establish IRS/IMF address update.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0031" source="PORTAL_SSA_OPEN_DATA" target="R134_E0015"><data key="edge_relationship_id">R134_R0031</data><data key="edge_source_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_relationship_type">publishes_catalog</data><data key="edge_target_entity_id">R134_E0015</data><data key="edge_operational_context">Public source explicitly calls this SSA primary asset inventory and offers CSV/JSON.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0032" source="R134_E0015" target="R134_E0016"><data key="edge_relationship_id">R134_R0032</data><data key="edge_source_entity_id">R134_E0015</data><data key="edge_relationship_type">publishes_as</data><data key="edge_target_entity_id">R134_E0016</data><data key="edge_operational_context">CSV inventory download advertised on SSA Open Data.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0033" source="R134_E0015" target="R134_E0017"><data key="edge_relationship_id">R134_R0033</data><data key="edge_source_entity_id">R134_E0015</data><data key="edge_relationship_type">publishes_as</data><data key="edge_target_entity_id">R134_E0017</data><data key="edge_operational_context">JSON inventory download advertised on SSA Open Data.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0034" source="R134_E0018" target="ORG_LEIDOS"><data key="edge_relationship_id">R134_R0034</data><data key="edge_source_entity_id">R134_E0018</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_LEIDOS</data><data key="edge_operational_context">USAspending award recipient is Leidos, Inc., for SSA ITSSC systems task order.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0035" source="R134_E0021" target="R134_E0019"><data key="edge_relationship_id">R134_R0035</data><data key="edge_source_entity_id">R134_E0021</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">R134_E0019</data><data key="edge_operational_context">Deloitte received the SSA cyber risk management program task order.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0036" source="R134_E0021" target="R134_E0020"><data key="edge_relationship_id">R134_R0036</data><data key="edge_source_entity_id">R134_E0021</data><data key="edge_relationship_type">supports_program</data><data key="edge_target_entity_id">R134_E0020</data><data key="edge_operational_context">Award scope is professional consulting and support for integrated organizational cyber risk governance, not a documented cyber software product.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0037" source="APP_CAL_SELECTION" target="R134_E0022"><data key="edge_relationship_id">R134_R0037</data><data key="edge_source_entity_id">APP_CAL_SELECTION</data><data key="edge_relationship_type">uses_classification_update</data><data key="edge_target_entity_id">R134_E0022</data><data key="edge_operational_context">SSA describes technology flagging disability applications with CAL-listed conditions; specific flag database or automation interface not established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0038" source="SVC_MYSSA_ADJ_FORMS" target="FORM_HA4631"><data key="edge_relationship_id">R134_R0038</data><data key="edge_source_entity_id">SVC_MYSSA_ADJ_FORMS</data><data key="edge_relationship_type">publicly_supports_submission_of</data><data key="edge_target_entity_id">FORM_HA4631</data><data key="edge_operational_context">September 2026 SSA public notice confirms HA-4631 online claimant submission through my Social Security.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0039" source="SVC_MYSSA_ADJ_FORMS" target="FORM_HA4632"><data key="edge_relationship_id">R134_R0039</data><data key="edge_source_entity_id">SVC_MYSSA_ADJ_FORMS</data><data key="edge_relationship_type">publicly_supports_submission_of</data><data key="edge_target_entity_id">FORM_HA4632</data><data key="edge_operational_context">September 2026 SSA public notice confirms HA-4632 online claimant submission through my Social Security.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0040" source="SVC_MYSSA_ADJ_FORMS" target="FORM_HA4633"><data key="edge_relationship_id">R134_R0040</data><data key="edge_source_entity_id">SVC_MYSSA_ADJ_FORMS</data><data key="edge_relationship_type">publicly_supports_submission_of</data><data key="edge_target_entity_id">FORM_HA4633</data><data key="edge_operational_context">September 2026 SSA public notice confirms HA-4633 online claimant submission through my Social Security.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R134_R0041" source="SVC_MYSSA_MESSAGE_CENTER" target="SVC_MYSSA_HEARING_NOTICES"><data key="edge_relationship_id">R134_R0041</data><data key="edge_source_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_relationship_type">provides_digital_notice_channel_for</data><data key="edge_target_entity_id">SVC_MYSSA_HEARING_NOTICES</data><data key="edge_operational_context">Proffer letters and 26 additional hearings-related notices are accessible in my Social Security Message Center; mail continues.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0001" source="R135_E0001" target="R135_E0004"><data key="edge_relationship_id">R135_R0001</data><data key="edge_source_entity_id">R135_E0001</data><data key="edge_relationship_type">documents</data><data key="edge_target_entity_id">R135_E0004</data><data key="edge_operational_context">CMS-2728 reports dialysis/transplant/training events and physician attestation; used as ESRD Medicare medical evidence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0002" source="R135_E0003" target="R135_E0001"><data key="edge_relationship_id">R135_R0002</data><data key="edge_source_entity_id">R135_E0003</data><data key="edge_relationship_type">receives_copies_of</data><data key="edge_target_entity_id">R135_E0001</data><data key="edge_operational_context">ESRD Network receives the facility copy of the CMS-2728; SSA FO receives its claims-evidence copy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0003" source="R135_E0003" target="R135_E0002"><data key="edge_relationship_id">R135_R0003</data><data key="edge_source_entity_id">R135_E0003</data><data key="edge_relationship_type">enters_information_in</data><data key="edge_target_entity_id">R135_E0002</data><data key="edge_operational_context">An ESRD Network enters CMS-2728 information into SIMS according to current policy; operating status and integration not independently validated.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R135_R0004" source="R135_E0002" target="R135_E0001"><data key="edge_relationship_id">R135_R0004</data><data key="edge_source_entity_id">R135_E0002</data><data key="edge_relationship_type">ingests_claimed_form_data_from</data><data key="edge_target_entity_id">R135_E0001</data><data key="edge_operational_context">POMS states ESRD Networks enter CMS-2728 data via SIMS, not that SSA updates MBR or Numident from SIMS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R135_R0005" source="R135_E0003" target="ORG_CMS"><data key="edge_relationship_id">R135_R0005</data><data key="edge_source_entity_id">R135_E0003</data><data key="edge_relationship_type">escalates_possible_program_abuse_to</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">ESRD Network profile analysis may result in suspected abuse referrals to CMS; process is separate from SSA case adjudication.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R135_R0006" source="R135_E0006" target="APP_MCS"><data key="edge_relationship_id">R135_R0006</data><data key="edge_source_entity_id">R135_E0006</data><data key="edge_relationship_type">entered_into</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">When FO receives paper CMS-43, employee enters ESRD claim into MCS promptly.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0007" source="R135_E0005" target="APP_MCS"><data key="edge_relationship_id">R135_R0007</data><data key="edge_source_entity_id">R135_E0005</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">ESRD Medicare claim is captured via MCS even when a paper CMS-43 initiated intake.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0008" source="R135_E0005" target="R135_E0001"><data key="edge_relationship_id">R135_R0008</data><data key="edge_source_entity_id">R135_E0005</data><data key="edge_relationship_type">collects_evidence_on</data><data key="edge_target_entity_id">R135_E0001</data><data key="edge_operational_context">FO obtains completed CMS-2728 evidence from dialysis facility for adjudication; source alone does not establish automatic electronic transmission.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0009" source="R135_E0005" target="R135_E0011"><data key="edge_relationship_id">R135_R0009</data><data key="edge_source_entity_id">R135_E0005</data><data key="edge_relationship_type">routes_adjudication_to</data><data key="edge_target_entity_id">R135_E0011</data><data key="edge_operational_context">Policy states PC7 has jurisdiction of all ESRD claims; FO adjusts DECI PC jurisdiction when necessary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0010" source="APP_MCS" target="R135_E0007"><data key="edge_relationship_id">R135_R0010</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">has_input_screen</data><data key="edge_target_entity_id">R135_E0007</data><data key="edge_operational_context">HIKD captures dialysis and transplant dates compared with clinician CMS-2728, without assuming automatic health IT interface.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0011" source="APP_MCS" target="R135_E0008"><data key="edge_relationship_id">R135_R0011</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">has_input_screen</data><data key="edge_target_entity_id">R135_E0008</data><data key="edge_operational_context">MCS ESRD screen identifies insured account for cases relying on spouse or parent earnings.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0012" source="APP_MCS" target="R135_E0009"><data key="edge_relationship_id">R135_R0012</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">requires_identity_cross_reference</data><data key="edge_target_entity_id">R135_E0009</data><data key="edge_operational_context">Claimant own SSN used to establish case, even when other SSN supplies insured status; IDN2 stores cross-reference SSN if other record entitlement.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0013" source="R135_E0001" target="R135_E0010"><data key="edge_relationship_id">R135_R0013</data><data key="edge_source_entity_id">R135_E0001</data><data key="edge_relationship_type">may_supply_protective_filing_evidence_under</data><data key="edge_target_entity_id">R135_E0010</data><data key="edge_operational_context">Filing-intent indicator on CMS-2728 can trigger protective writing and appropriate six-month closeout procedure, subject to requirements.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0014" source="R135_E0004" target="R135_E0007"><data key="edge_relationship_id">R135_R0014</data><data key="edge_source_entity_id">R135_E0004</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">R135_E0007</data><data key="edge_operational_context">ESRD clinical dates on signed evidence are developed on MCS HIKD with discrepancies investigated by staff.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0015" source="R135_E0005" target="R135_E0012"><data key="edge_relationship_id">R135_R0015</data><data key="edge_source_entity_id">R135_E0005</data><data key="edge_relationship_type">has_earnings_computation_exception_requiring</data><data key="edge_target_entity_id">R135_E0012</data><data key="edge_operational_context">MCS earnings computation limitation requires field-office A101 for ESRD claims.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0016" source="APP_MSSICS" target="R135_E0013"><data key="edge_relationship_id">R135_R0016</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">subject_to_eap_same_day_control</data><data key="edge_target_entity_id">R135_E0013</data><data key="edge_operational_context">MSSICS establishes and approves SSI EAP and IP, then data must reach SSR on the same day for TPPS propagation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0017" source="R135_E0013" target="SYS_SSR"><data key="edge_relationship_id">R135_R0017</data><data key="edge_source_entity_id">R135_E0013</data><data key="edge_relationship_type">requires_same_day_update_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">EAP or Title XVI immediate payment must be established, approved and transmitted to SSR in same day; otherwise TPPS cannot issue USDC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0018" source="R135_E0013" target="APP_TPPS"><data key="edge_relationship_id">R135_R0018</data><data key="edge_source_entity_id">R135_E0013</data><data key="edge_relationship_type">gates_payment_via</data><data key="edge_target_entity_id">APP_TPPS</data><data key="edge_operational_context">The documented same-day SSR posting requirement controls TPPS issuance of emergency or immediate United States Debit Card.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0019" source="DB_EAP" target="R135_E0013"><data key="edge_relationship_id">R135_R0019</data><data key="edge_source_entity_id">DB_EAP</data><data key="edge_relationship_type">prevents_second_emergency_advance_against</data><data key="edge_target_entity_id">R135_E0013</data><data key="edge_operational_context">EAP database prevents issuance of a second emergency advance on the same claim; it updates after allowed EAP.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0020" source="DATA_SSA8102" target="R135_E0014"><data key="edge_relationship_id">R135_R0020</data><data key="edge_source_entity_id">DATA_SSA8102</data><data key="edge_relationship_type">documented_as</data><data key="edge_target_entity_id">R135_E0014</data><data key="edge_operational_context">Signed SSA-8102 is retained through the Evidence Portal while cashier keeps TPPS audit copy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0021" source="R135_E0014" target="APP_EP"><data key="edge_relationship_id">R135_R0021</data><data key="edge_source_entity_id">R135_E0014</data><data key="edge_relationship_type">retained_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">After USDC release staff upload signed SSA-8102 file copy to SSA Evidence Portal; this is receipt evidence, not bank posting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R135_R0022" source="APP_RZWIZ" target="R135_E0016"><data key="edge_relationship_id">R135_R0022</data><data key="edge_source_entity_id">APP_RZWIZ</data><data key="edge_relationship_type">creates_transient_worksheet</data><data key="edge_target_entity_id">R135_E0016</data><data key="edge_operational_context">RZwiz automatically retrieves and consolidates multi-SSN administrative queries for SSI RZ/LI interviews.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0023" source="R135_E0016" target="R135_E0015"><data key="edge_relationship_id">R135_R0023</data><data key="edge_source_entity_id">R135_E0016</data><data key="edge_relationship_type">subject_to_retention_redaction</data><data key="edge_target_entity_id">R135_E0015</data><data key="edge_operational_context">Any RZwiz review sheet saved to electronic folder must have NDNH query and underlying data removed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0024" source="R135_E0015" target="DB_NDNH"><data key="edge_relationship_id">R135_R0024</data><data key="edge_source_entity_id">R135_E0015</data><data key="edge_relationship_type">protects_restricted_data_in</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">OCSE new-hire data must be stripped from RZwiz worksheet when placed in electronic folder; not a general NDNH database deletion.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0025" source="SYS_SSR" target="R135_E0016"><data key="edge_relationship_id">R135_R0025</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_person_cross_reference_selection_to</data><data key="edge_target_entity_id">R135_E0016</data><data key="edge_operational_context">RZwiz identifies all SSNs associated with SSR and produces cross-SSN worksheet; own and housed-under numbers need careful interpretation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0026" source="R135_E0016" target="DB_NDNH"><data key="edge_relationship_id">R135_R0026</data><data key="edge_source_entity_id">R135_E0016</data><data key="edge_relationship_type">includes_query_data_from</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">RZwiz retrieves NDNH query data for relevant SSNs for authorized interview review, but requires electronic-folder redaction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0027" source="R135_E0017" target="QRY_DEQY"><data key="edge_relationship_id">R135_R0027</data><data key="edge_source_entity_id">R135_E0017</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">SSA policy directs a detailed earnings query by payer EIN to identify questionable payer when IRS alert has blank or inappropriate payer details.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0028" source="R135_E0018" target="R135_E0017"><data key="edge_relationship_id">R135_R0028</data><data key="edge_source_entity_id">R135_E0018</data><data key="edge_relationship_type">investigated_with</data><data key="edge_target_entity_id">R135_E0017</data><data key="edge_operational_context">IRS alert payer name and address is an investigative data element and may be absent or incorrect; employee follows payer EIN query.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0029" source="R135_E0017" target="WORK_SSI_IRS_5B_DIARY"><data key="edge_relationship_id">R135_R0029</data><data key="edge_source_entity_id">R135_E0017</data><data key="edge_relationship_type">supports_development_for</data><data key="edge_target_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_operational_context">5B IRS unearned-income alert investigation may require payer EIN confirmation; does not automatically change SSR master address.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R135_R0030" source="R135_E0017" target="DB_IRS_IRMF"><data key="edge_relationship_id">R135_R0030</data><data key="edge_source_entity_id">R135_E0017</data><data key="edge_relationship_type">uses_interface_data_from</data><data key="edge_target_entity_id">DB_IRS_IRMF</data><data key="edge_operational_context">Income/payer transaction is an IRS matching lead. POMS does not establish automatic posting of payer or taxpayer addresses to Numident/MBR/SSR.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R135_R0031" source="R135_E0019" target="APP_EAFI"><data key="edge_relationship_id">R135_R0031</data><data key="edge_source_entity_id">R135_E0019</data><data key="edge_relationship_type">interprets_evidence_from</data><data key="edge_target_entity_id">APP_EAFI</data><data key="edge_operational_context">eAFI account balance verification is evidence; legal ownership and withdrawal restrictions determine SSI countable resources.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0032" source="R135_E0019" target="APP_CCE"><data key="edge_relationship_id">R135_R0032</data><data key="edge_source_entity_id">R135_E0019</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Direct deposit leads and resource ownership are developed in CCE Financial Institution Account page after evaluation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0033" source="SYS_MBR" target="R135_E0019"><data key="edge_relationship_id">R135_R0033</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">may_indicate_account_for_development_under</data><data key="edge_target_entity_id">R135_E0019</data><data key="edge_operational_context">MBR direct-deposit indicator is a lead to develop account ownership rather than automatic determination of countable resources.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0034" source="SYS_SSR" target="R135_E0019"><data key="edge_relationship_id">R135_R0034</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">may_indicate_account_for_development_under</data><data key="edge_target_entity_id">R135_E0019</data><data key="edge_operational_context">SSR direct-deposit indicator is a lead to develop account ownership rather than automatic determination of countable resources.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0035" source="DATA_HRS_CYBF" target="R135_E0020"><data key="edge_relationship_id">R135_R0035</data><data key="edge_source_entity_id">DATA_HRS_CYBF</data><data key="edge_relationship_type">release_2026_excludes</data><data key="edge_target_entity_id">R135_E0020</data><data key="edge_operational_context">HRS April 2026 Respondent Cross-Year Benefits distribution expressly excludes Social Security Weights file; preserve earlier edge as disputed historical context.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0036" source="R135_E0020" target="DATA_HRS_SS_WEIGHTS"><data key="edge_relationship_id">R135_R0036</data><data key="edge_source_entity_id">R135_E0020</data><data key="edge_relationship_type">identifies_nonincluded_product</data><data key="edge_target_entity_id">DATA_HRS_SS_WEIGHTS</data><data key="edge_operational_context">The 2026 Benefits release expressly excludes Social Security Weights; contradictory baseline distributed_with remains preserved for version-specific review.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0037" source="PROG_HRS" target="R135_E0021"><data key="edge_relationship_id">R135_R0037</data><data key="edge_source_entity_id">PROG_HRS</data><data key="edge_relationship_type">publishes_separately</data><data key="edge_target_entity_id">R135_E0021</data><data key="edge_operational_context">October 6, 2026 HRS Tracker v2 releases weights as separate general Tracker Weights File; not automatically equivalent to SSA restricted Social Security Weights.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0038" source="DATA_HRS_CYBF" target="R135_E0022"><data key="edge_relationship_id">R135_R0038</data><data key="edge_source_entity_id">DATA_HRS_CYBF</data><data key="edge_relationship_type">subject_to_geographic_use_limit</data><data key="edge_target_entity_id">R135_E0022</data><data key="edge_operational_context">Linked SSA/HRS administrative records cannot merge with geography below Census Division and need permission for combination with other restricted files.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0039" source="REPORT_STAT_SUPP_2026" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R135_R0039</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">principal_statistical_source_for</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">SSA Fast Facts &amp; Figures October 2026 reports most statistics derived from Annual Statistical Supplement; counts are dated publication values.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R135_R0040" source="DATA_OACT_COHORT_LIFE_2026" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R135_R0040</data><data key="edge_source_entity_id">DATA_OACT_COHORT_LIFE_2026</data><data key="edge_relationship_type">source_for_trust_fund_figures_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">2026 Fast Facts states its trust fund operations figures are derived from 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R136_R0001" source="ORG_IRS" target="R136_E0001"><data key="edge_relationship_id">R136_R0001</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">issues_discrepancy_trigger_for</data><data key="edge_target_entity_id">R136_E0001</data><data key="edge_operational_context">Payers relay IRS First B Notice on taxpayer-name or TIN mismatch; no specific address field asserted.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0002" source="ORG_IRS" target="R136_E0002"><data key="edge_relationship_id">R136_R0002</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">issues_discrepancy_trigger_for</data><data key="edge_target_entity_id">R136_E0002</data><data key="edge_operational_context">Payers relay Second B Notice when matching discrepancy persists.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0003" source="R136_E0002" target="R136_E0003"><data key="edge_relationship_id">R136_R0003</data><data key="edge_source_entity_id">R136_E0002</data><data key="edge_relationship_type">may_trigger</data><data key="edge_target_entity_id">R136_E0003</data><data key="edge_operational_context">SSA compares notice with most recent Numident iteration and sends an IRS Update through SSNAP when correct.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0004" source="R136_E0001" target="R136_E0003"><data key="edge_relationship_id">R136_R0004</data><data key="edge_source_entity_id">R136_E0001</data><data key="edge_relationship_type">may_trigger</data><data key="edge_target_entity_id">R136_E0003</data><data key="edge_operational_context">SSA may send the correct Numident identifying information to IRS when first or second notice is presented.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0005" source="APP_SSNAP" target="R136_E0003"><data key="edge_relationship_id">R136_R0005</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">R136_E0003</data><data key="edge_operational_context">IRS Update via SSNAP provides current Numident information to IRS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0006" source="R136_E0003" target="ORG_IRS"><data key="edge_relationship_id">R136_R0006</data><data key="edge_source_entity_id">R136_E0003</data><data key="edge_relationship_type">resends_identity_attributes_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">IRS Update sends current Numident name/SSN data; no address-update pathway claimed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0007" source="R136_E0003" target="R136_E0004"><data key="edge_relationship_id">R136_R0007</data><data key="edge_source_entity_id">R136_E0003</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">R136_E0004</data><data key="edge_operational_context">IRS Update creates a new Numident iteration explicitly according to POMS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0008" source="R136_E0004" target="SYS_NUMIDENT"><data key="edge_relationship_id">R136_R0008</data><data key="edge_source_entity_id">R136_E0004</data><data key="edge_relationship_type">is_recorded_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">New Numident iteration created even if previously stored iteration was correct.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0009" source="R136_E0005" target="R136_E0001"><data key="edge_relationship_id">R136_R0009</data><data key="edge_source_entity_id">R136_E0005</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R136_E0001</data><data key="edge_operational_context">First B Notice requires distinguishing taxpayer SSN from business EIN; for first notice taxpayer may use W-9.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0010" source="R136_E0005" target="R136_E0002"><data key="edge_relationship_id">R136_R0010</data><data key="edge_source_entity_id">R136_E0005</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R136_E0002</data><data key="edge_operational_context">Second B Notice includes sole-proprietor exception when EIN is involved.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0011" source="SYS_NUMIDENT" target="R136_E0003"><data key="edge_relationship_id">R136_R0011</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">supplies_current_attributes_for</data><data key="edge_target_entity_id">R136_E0003</data><data key="edge_operational_context">SSA compares most recent Numident with B Notice before deciding to correct via SS-5 or resend to IRS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0012" source="DATA_CMS1957" target="R136_E0006"><data key="edge_relationship_id">R136_R0012</data><data key="edge_source_entity_id">DATA_CMS1957</data><data key="edge_relationship_type">superseded_in_physical_form_by</data><data key="edge_target_entity_id">R136_E0006</data><data key="edge_operational_context">Effective 2026-04-01: paper CMS-1957 is no longer used for CMS State buy-in exception reporting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0013" source="R136_E0006" target="R136_E0007"><data key="edge_relationship_id">R136_R0013</data><data key="edge_source_entity_id">R136_E0006</data><data key="edge_relationship_type">routed_to</data><data key="edge_target_entity_id">R136_E0007</data><data key="edge_operational_context">State buy-in exception email goes to CMS Ombudsman Group division designated for system exceptions and interfaces.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0014" source="R136_E0006" target="R136_E0008"><data key="edge_relationship_id">R136_R0014</data><data key="edge_source_entity_id">R136_E0006</data><data key="edge_relationship_type">tracked_in</data><data key="edge_target_entity_id">R136_E0008</data><data key="edge_operational_context">SSA servicing office retains control copy and records approximately 30-business-day follow-up.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0015" source="R136_E0009" target="DATA_CMS1957"><data key="edge_relationship_id">R136_R0015</data><data key="edge_source_entity_id">R136_E0009</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">DATA_CMS1957</data><data key="edge_operational_context">Dated status rule limits physical form use from 2026-04-01, not a claim that the underlying CMS digital intake is retired.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0016" source="ORG_CMS" target="R136_E0007"><data key="edge_relationship_id">R136_R0016</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">contains_component</data><data key="edge_target_entity_id">R136_E0007</data><data key="edge_operational_context">CMS Medicare Ombudsman Group houses Division of Medicare System Exceptions and Interfaces.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0017" source="PROC_STATE_BUYIN" target="R136_E0006"><data key="edge_relationship_id">R136_R0017</data><data key="edge_source_entity_id">PROC_STATE_BUYIN</data><data key="edge_relationship_type">has_exception_path</data><data key="edge_target_entity_id">R136_E0006</data><data key="edge_operational_context">Normal daily exchanges may fail and require manual email escalation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0018" source="R136_E0011" target="SYS_MBR"><data key="edge_relationship_id">R136_R0018</data><data key="edge_source_entity_id">R136_E0011</data><data key="edge_relationship_type">exposes_address_for_comparison</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">HIQR ADDR screen CMS address compared with Title II MBR; discrepancy determines action.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0019" source="UI_POS_PEAD" target="DATA_MBR_MAILING_ADDRESS"><data key="edge_relationship_id">R136_R0019</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">updates_record</data><data key="edge_target_entity_id">DATA_MBR_MAILING_ADDRESS</data><data key="edge_operational_context">When MBR mailing address is wrong, POS PEAD action updates it, separately from CMS reissue.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0020" source="R136_E0010" target="R136_E0012"><data key="edge_relationship_id">R136_R0020</data><data key="edge_source_entity_id">R136_E0010</data><data key="edge_relationship_type">transmits_card_mailing_address_under</data><data key="edge_target_entity_id">R136_E0012</data><data key="edge_operational_context">Retranscribing address on HCRQ can send correct MBR address to CMS for Medicare card without updating CMS master records.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0021" source="R136_E0010" target="R136_E0013"><data key="edge_relationship_id">R136_R0021</data><data key="edge_source_entity_id">R136_E0010</data><data key="edge_relationship_type">may_be_followed_by</data><data key="edge_target_entity_id">R136_E0013</data><data key="edge_operational_context">Medicare entitlement/card mismatch unresolved through normal interface may require CMS-2178-U2 referral.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0022" source="R136_E0012" target="ORG_CMS"><data key="edge_relationship_id">R136_R0022</data><data key="edge_source_entity_id">R136_E0012</data><data key="edge_relationship_type">is_a_boundary_on</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS card-mailing transmission is not documented to correct underlying CMS records.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0023" source="EX_SDX" target="R136_E0014"><data key="edge_relationship_id">R136_R0023</data><data key="edge_source_entity_id">EX_SDX</data><data key="edge_relationship_type">supplies_state_data_for</data><data key="edge_target_entity_id">R136_E0014</data><data key="edge_operational_context">States compare SDX public welfare accretion record with State Medicaid Eligibility File.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0024" source="R136_E0014" target="PROC_PW_ACCRETION"><data key="edge_relationship_id">R136_R0024</data><data key="edge_source_entity_id">R136_E0014</data><data key="edge_relationship_type">supports_validation_of</data><data key="edge_target_entity_id">PROC_PW_ACCRETION</data><data key="edge_operational_context">State matches its eligibility file with SDX accretion before accepting state premium liability.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0025" source="R136_E0015" target="PROC_PW_ACCRETION"><data key="edge_relationship_id">R136_R0025</data><data key="edge_source_entity_id">R136_E0015</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">PROC_PW_ACCRETION</data><data key="edge_operational_context">Two-month state protest window from billing notification; otherwise state generally remains liable pending deletion.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0026" source="EX_STATE_ABLE_MONTHLY" target="UI_SSI_ABLE_PENDING"><data key="edge_relationship_id">R136_R0026</data><data key="edge_source_entity_id">EX_STATE_ABLE_MONTHLY</data><data key="edge_relationship_type">populates</data><data key="edge_target_entity_id">UI_SSI_ABLE_PENDING</data><data key="edge_operational_context">Monthly State new-account data are displayed on the SSI Claims Pending ABLE page, subject to review.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0027" source="R136_E0017" target="UI_SSI_ABLE_PENDING"><data key="edge_relationship_id">R136_R0027</data><data key="edge_source_entity_id">R136_E0017</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">UI_SSI_ABLE_PENDING</data><data key="edge_operational_context">Mismatch disposition in SSI Claims offers update/add/reject/decide later; later requires action before closure.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0028" source="UI_SSI_ABLE_ACCOUNT" target="R136_E0016"><data key="edge_relationship_id">R136_R0028</data><data key="edge_source_entity_id">UI_SSI_ABLE_ACCOUNT</data><data key="edge_relationship_type">is_source_for</data><data key="edge_target_entity_id">R136_E0016</data><data key="edge_operational_context">Account must first be documented in SSI Claims before subsequent matching State balance updates happen.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0029" source="EX_STATE_ABLE_MONTHLY" target="R136_E0016"><data key="edge_relationship_id">R136_R0029</data><data key="edge_source_entity_id">EX_STATE_ABLE_MONTHLY</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">R136_E0016</data><data key="edge_operational_context">Subsequent matching State reports automatically update recorded ABLE account balances, only after account match.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0030" source="R136_E0016" target="DATA_SSI_ABLE_BALANCE"><data key="edge_relationship_id">R136_R0030</data><data key="edge_source_entity_id">R136_E0016</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_SSI_ABLE_BALANCE</data><data key="edge_operational_context">Conditional auto-update to SSI Claims balance information only; SSR master write not established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0031" source="R136_E0018" target="EX_STATE_ABLE_MONTHLY"><data key="edge_relationship_id">R136_R0031</data><data key="edge_source_entity_id">R136_E0018</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">EX_STATE_ABLE_MONTHLY</data><data key="edge_operational_context">Policy states distribution data unavailable pending future systems release; no inference about later availability.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0032" source="APP_EDCS" target="R136_E0019"><data key="edge_relationship_id">R136_R0032</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R136_E0019</data><data key="edge_operational_context">Transferring appropriate Title II CDR appeals propagates to DCF/MBR, after which five-day verification applies.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0033" source="R136_E0019" target="SYS_MBR"><data key="edge_relationship_id">R136_R0033</data><data key="edge_source_entity_id">R136_E0019</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Five-day update verification and follow-up for continuation/cessation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0034" source="R136_E0019" target="SYS_SSR"><data key="edge_relationship_id">R136_R0034</data><data key="edge_source_entity_id">R136_E0019</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI appeal status must be verified after transfer; manual fallback for failure.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0035" source="R136_E0020" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R136_R0035</data><data key="edge_source_entity_id">R136_E0020</data><data key="edge_relationship_type">tracked_by</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">EDCS-excluded appeals cannot be seen in EDCS and are trackable through MI Central as documented.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0036" source="R136_E0021" target="CTRL_DIBCESS_PCACS"><data key="edge_relationship_id">R136_R0036</data><data key="edge_source_entity_id">R136_E0021</data><data key="edge_relationship_type">requires_check_of</data><data key="edge_target_entity_id">CTRL_DIBCESS_PCACS</data><data key="edge_operational_context">Absent automatic MBR posting at five days, staff check DIBCESS issue and escalate.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0037" source="DB_DCF" target="R136_E0019"><data key="edge_relationship_id">R136_R0037</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">supports_follow_up_for</data><data key="edge_target_entity_id">R136_E0019</data><data key="edge_operational_context">CDR Development Worksheet places five-day tickle in DCF.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0038" source="R136_E0022" target="APP_STATUTORY_BENEFIT_CONT"><data key="edge_relationship_id">R136_R0038</data><data key="edge_source_entity_id">R136_E0022</data><data key="edge_relationship_type">delays_recovery_in</data><data key="edge_target_entity_id">APP_STATUTORY_BENEFIT_CONT</data><data key="edge_operational_context">Statutory benefit continuation payments are not debt before final cessation decision and end of appeals; DMS use not inferred; only repayment governance applies.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0039" source="R136_E0023" target="R136_E0022"><data key="edge_relationship_id">R136_R0039</data><data key="edge_source_entity_id">R136_E0023</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">R136_E0022</data><data key="edge_operational_context">Early recovery may not start without requisite notice, and response within 30 days requires collection hold.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0040" source="R136_E0024" target="R136_E0023"><data key="edge_relationship_id">R136_R0040</data><data key="edge_source_entity_id">R136_E0024</data><data key="edge_relationship_type">requires_correction_of</data><data key="edge_target_entity_id">R136_E0023</data><data key="edge_operational_context">Defective or missing overpayment notice requires new notice and repayment of improperly withheld sums.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0041" source="APP_DMS" target="R136_E0023"><data key="edge_relationship_id">R136_R0041</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">records_contact_about</data><data key="edge_target_entity_id">R136_E0023</data><data key="edge_operational_context">DMS Remarks records oral first notice and discussion about liability.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R136_R0042" source="R136_E0025" target="EX_ISVER"><data key="edge_relationship_id">R136_R0042</data><data key="edge_source_entity_id">R136_E0025</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">EX_ISVER</data><data key="edge_operational_context">DOS passport identity verification uses applicant name, SSN, DOB, sex and other information; exchange is outgoing SSA verification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence-specific documented operational relationship. Do not generalize to automatic address changes or broader production synchronization.</data></edge><edge id="R137_R0001" source="APP_ECBSV" target="R137_E0001"><data key="edge_relationship_id">R137_R0001</data><data key="edge_source_entity_id">APP_ECBSV</data><data key="edge_relationship_type">requires_external_oidc_configuration</data><data key="edge_target_entity_id">R137_E0001</data><data key="edge_operational_context">Permitted entities must configure OpenID Connect/OAuth 2.0 to access eCBSV Verification API.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0002" source="R137_E0001" target="R137_E0002"><data key="edge_relationship_id">R137_R0002</data><data key="edge_source_entity_id">R137_E0001</data><data key="edge_relationship_type">carries_end_user_permission_assertions</data><data key="edge_target_entity_id">R137_E0002</data><data key="edge_operational_context">SSA directs permitted entities to manage end-user permissions in OIDC assertion attributes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0003" source="SVC_ECBSV_API" target="R137_E0006"><data key="edge_relationship_id">R137_R0003</data><data key="edge_source_entity_id">SVC_ECBSV_API</data><data key="edge_relationship_type">uses_documented_external_security_concepts</data><data key="edge_target_entity_id">R137_E0006</data><data key="edge_operational_context">SSA technical information identifies OIDC/OAuth2 and JSON REST/JWT/JWE concepts for the eCBSV external API.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0004" source="ENV_ECBSV_ETE" target="R137_E0003"><data key="edge_relationship_id">R137_R0004</data><data key="edge_source_entity_id">ENV_ECBSV_ETE</data><data key="edge_relationship_type">returns_test_client_identifier</data><data key="edge_target_entity_id">R137_E0003</data><data key="edge_operational_context">Successful external test OIDC issuer registration yields ETE OAuth client ID.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0005" source="ENV_ECBSV_ETE" target="R137_E0004"><data key="edge_relationship_id">R137_R0005</data><data key="edge_source_entity_id">ENV_ECBSV_ETE</data><data key="edge_relationship_type">subject_to_load_testing_restriction</data><data key="edge_target_entity_id">R137_E0004</data><data key="edge_operational_context">The SSA test environment should not be used for high-volume performance testing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0006" source="SVC_ECBSV_API" target="R137_E0005"><data key="edge_relationship_id">R137_R0006</data><data key="edge_source_entity_id">SVC_ECBSV_API</data><data key="edge_relationship_type">returns_documented_match_and_death_payload</data><data key="edge_target_entity_id">R137_E0005</data><data key="edge_operational_context">eCBSV yes/no match result may include nonmatched field and SSA-recorded death indicator; no record update is stated.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0007" source="APP_ECBSV" target="R137_E0001"><data key="edge_relationship_id">R137_R0007</data><data key="edge_source_entity_id">APP_ECBSV</data><data key="edge_relationship_type">enforces_authentication_for</data><data key="edge_target_entity_id">R137_E0001</data><data key="edge_operational_context">SSA states eCBSV verification is unavailable without successful authentication/authorization.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0008" source="COMP_STC" target="R137_E0010"><data key="edge_relationship_id">R137_R0008</data><data key="edge_source_entity_id">COMP_STC</data><data key="edge_relationship_type">requires_data_flow_safeguard_agreement</data><data key="edge_target_entity_id">R137_E0010</data><data key="edge_operational_context">State STC use requires separately executed agreement governing interagency transfer and information safeguards.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0009" source="FORM_SSA157" target="R137_E0011"><data key="edge_relationship_id">R137_R0009</data><data key="edge_source_entity_id">FORM_SSA157</data><data key="edge_relationship_type">is_submitted_via</data><data key="edge_target_entity_id">R137_E0011</data><data key="edge_operational_context">State guidance instructs new data exchange applicants to complete SSA-157 through an online route.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0010" source="R137_E0008" target="R137_E0007"><data key="edge_relationship_id">R137_R0010</data><data key="edge_source_entity_id">R137_E0008</data><data key="edge_relationship_type">governs_federal_benefits_disclosures_from</data><data key="edge_target_entity_id">R137_E0007</data><data key="edge_operational_context">CMA plus IEA/F govern SSA data disclosure to federally funded state-administered programs.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0011" source="R137_E0009" target="R137_E0007"><data key="edge_relationship_id">R137_R0011</data><data key="edge_source_entity_id">R137_E0009</data><data key="edge_relationship_type">governs_state_funded_disclosures_from</data><data key="edge_target_entity_id">R137_E0007</data><data key="edge_operational_context">R-IEA required for state-funded state-administered programs.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0012" source="R137_E0010" target="COMP_STC"><data key="edge_relationship_id">R137_R0012</data><data key="edge_source_entity_id">R137_E0010</data><data key="edge_relationship_type">documents_authorized_interagency_transfer_by</data><data key="edge_target_entity_id">COMP_STC</data><data key="edge_operational_context">The STC agreement documents how an approved recipient receives data via transmission component.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0013" source="R137_E0011" target="FORM_SSA157"><data key="edge_relationship_id">R137_R0013</data><data key="edge_source_entity_id">R137_E0011</data><data key="edge_relationship_type">initiates_state_exchange_agreement_request_through</data><data key="edge_target_entity_id">FORM_SSA157</data><data key="edge_operational_context">Online SSA-157 is the data-exchange request form, not an authorized active data feed by itself.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0014" source="DATA_CSCRA_QUESTIONNAIRE" target="R137_E0012"><data key="edge_relationship_id">R137_R0014</data><data key="edge_source_entity_id">DATA_CSCRA_QUESTIONNAIRE</data><data key="edge_relationship_type">includes_foreign_control_topic</data><data key="edge_target_entity_id">R137_E0012</data><data key="edge_operational_context">SSA lists foreign ownership/control/influence as questionnaire risk category.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0015" source="DATA_CSCRA_QUESTIONNAIRE" target="R137_E0013"><data key="edge_relationship_id">R137_R0015</data><data key="edge_source_entity_id">DATA_CSCRA_QUESTIONNAIRE</data><data key="edge_relationship_type">includes_remote_support_and_labor_topic</data><data key="edge_target_entity_id">R137_E0013</data><data key="edge_operational_context">SSA lists overseas labor and remote service or support location categories.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0016" source="DATA_CSCRA_QUESTIONNAIRE" target="R137_E0014"><data key="edge_relationship_id">R137_R0016</data><data key="edge_source_entity_id">DATA_CSCRA_QUESTIONNAIRE</data><data key="edge_relationship_type">includes_counterfeit_and_imports_topic</data><data key="edge_target_entity_id">R137_E0014</data><data key="edge_operational_context">SSA lists counterfeit incident history and imports of products/parts.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0017" source="PROC_CSCRA" target="R137_E0015"><data key="edge_relationship_id">R137_R0017</data><data key="edge_source_entity_id">PROC_CSCRA</data><data key="edge_relationship_type">supports_preaward_eligibility_decision</data><data key="edge_target_entity_id">R137_E0015</data><data key="edge_operational_context">Preaward supply-chain assessment informs contractor eligibility and mitigation controls; not award evidence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0018" source="APP_TP_RISK_MGMT" target="R137_E0016"><data key="edge_relationship_id">R137_R0018</data><data key="edge_source_entity_id">APP_TP_RISK_MGMT</data><data key="edge_relationship_type">supports_postaward_tracking_control</data><data key="edge_target_entity_id">R137_E0016</data><data key="edge_operational_context">SSA tracks third-party relationships via Third-Party Risk Management system through contract lifecycle.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0019" source="INIT_CSCRM" target="R137_E0016"><data key="edge_relationship_id">R137_R0019</data><data key="edge_source_entity_id">INIT_CSCRM</data><data key="edge_relationship_type">encompasses</data><data key="edge_target_entity_id">R137_E0016</data><data key="edge_operational_context">CSCRM continuing program includes post-award tracking, onboarding and completion reviews.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0020" source="PLAT_TP_CYBER_RISK_MON" target="R137_E0015"><data key="edge_relationship_id">R137_R0020</data><data key="edge_source_entity_id">PLAT_TP_CYBER_RISK_MON</data><data key="edge_relationship_type">supports_preaward_assessment</data><data key="edge_target_entity_id">R137_E0015</data><data key="edge_operational_context">SSA identifies third-party monitoring platform as specialized preaward due-diligence tool.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0021" source="ORG_IT_IRB" target="R137_E0017"><data key="edge_relationship_id">R137_R0021</data><data key="edge_source_entity_id">ORG_IT_IRB</data><data key="edge_relationship_type">subject_to_reported_operations_oversight_gap</data><data key="edge_target_entity_id">R137_E0017</data><data key="edge_operational_context">GAO 2025 says IT IRB did not have process to review O&amp;M, infrastructure and cybersecurity investments.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0022" source="ORG_IT_IRB" target="R137_E0019"><data key="edge_relationship_id">R137_R0022</data><data key="edge_source_entity_id">ORG_IT_IRB</data><data key="edge_relationship_type">needs_formal_operational_analyses</data><data key="edge_target_entity_id">R137_E0019</data><data key="edge_operational_context">GAO recommendation remains open in January 2026 status update; do not mark implemented.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0023" source="PLAT_ADDS" target="R137_E0018"><data key="edge_relationship_id">R137_R0023</data><data key="edge_source_entity_id">PLAT_ADDS</data><data key="edge_relationship_type">subject_to_investment_documentation_review</data><data key="edge_target_entity_id">R137_E0018</data><data key="edge_operational_context">GAO specifically assessed Analytics and Disability Decision Support Intelligent Medical Language Analysis Generation investment documentation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0024" source="APP_DCPS" target="R137_E0018"><data key="edge_relationship_id">R137_R0024</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">has_enhancement_investment_documentation_reviewed_in</data><data key="edge_target_entity_id">R137_E0018</data><data key="edge_operational_context">GAO identified Disability Case Processing System 2 Enhancements as selected investment, without establishing architecture of DCPS 2.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0025" source="APP_HACPS" target="R137_E0018"><data key="edge_relationship_id">R137_R0025</data><data key="edge_source_entity_id">APP_HACPS</data><data key="edge_relationship_type">has_case_processing_investment_documentation_reviewed_in</data><data key="edge_target_entity_id">R137_E0018</data><data key="edge_operational_context">GAO named Hearings and Appeals Case Processing System investment documentation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0026" source="R137_E0017" target="R137_E0019"><data key="edge_relationship_id">R137_R0026</data><data key="edge_source_entity_id">R137_E0017</data><data key="edge_relationship_type">was_reported_with</data><data key="edge_target_entity_id">R137_E0019</data><data key="edge_operational_context">GAO recommended oversight of O&amp;M after finding investment board lacked processes for broad operations portfolio.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0027" source="R137_E0020" target="R137_E0021"><data key="edge_relationship_id">R137_R0027</data><data key="edge_source_entity_id">R137_E0020</data><data key="edge_relationship_type">uses_application_reporting_calendar</data><data key="edge_target_entity_id">R137_E0021</data><data key="edge_operational_context">Applications are weekly-tabulated; months can include four/five weeks and quarters twelve/fourteen weeks.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0028" source="R137_E0020" target="R137_E0022"><data key="edge_relationship_id">R137_R0028</data><data key="edge_source_entity_id">R137_E0020</data><data key="edge_relationship_type">has_noncohort_awards_ratio_caveat</data><data key="edge_target_entity_id">R137_E0022</data><data key="edge_operational_context">Same-period awards-to-applications proportion is not eventual application allowance rate.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0029" source="R137_E0020" target="R137_E0023"><data key="edge_relationship_id">R137_R0029</data><data key="edge_source_entity_id">R137_E0020</data><data key="edge_relationship_type">uses_reported_termination_rate_calculation</data><data key="edge_target_entity_id">R137_E0023</data><data key="edge_operational_context">OACT describes estimated termination rate using beginning entitled population and half-period awards.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0030" source="R137_E0020" target="R137_E0024"><data key="edge_relationship_id">R137_R0030</data><data key="edge_source_entity_id">R137_E0020</data><data key="edge_relationship_type">qualifies_award_measure_with</data><data key="edge_target_entity_id">R137_E0024</data><data key="edge_operational_context">OACT notes unedited awards can include duplicate cases, historically pre-2014.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0031" source="DOM_TITLE2" target="R137_E0020"><data key="edge_relationship_id">R137_R0031</data><data key="edge_source_entity_id">DOM_TITLE2</data><data key="edge_relationship_type">is_described_in_statistical_product</data><data key="edge_target_entity_id">R137_E0020</data><data key="edge_operational_context">OACT page covers disabled workers and excludes disabled child and disabled widow(er) claims from its application count.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0032" source="DATA_MONTHLY_STAT_SNAPSHOT" target="R137_E0020"><data key="edge_relationship_id">R137_R0032</data><data key="edge_source_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_relationship_type">has_distinct_measure_population_from</data><data key="edge_target_entity_id">R137_E0020</data><data key="edge_operational_context">OACT disability time series has disabled-worker only receipts/awards while monthly statistical snapshot reports broader OASDI/SSI populations; measures must not be combined as equivalent.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0033" source="SYS_SSR" target="R137_E0025"><data key="edge_relationship_id">R137_R0033</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">is_target_information_not_confirmed_physical_source_for_proposal</data><data key="edge_target_entity_id">R137_E0025</data><data key="edge_operational_context">SSAB recommends SSI case facts readable to recipients; does not specify how SSR data would be exposed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0034" source="R137_E0025" target="R137_E0027"><data key="edge_relationship_id">R137_R0034</data><data key="edge_source_entity_id">R137_E0025</data><data key="edge_relationship_type">responds_to_documented_gap</data><data key="edge_target_entity_id">R137_E0027</data><data key="edge_operational_context">An SSI record snapshot was recommended to address lack of visibility into case fact and change status.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0035" source="R137_E0026" target="R137_E0027"><data key="edge_relationship_id">R137_R0035</data><data key="edge_source_entity_id">R137_E0026</data><data key="edge_relationship_type">responds_to_documented_gap</data><data key="edge_target_entity_id">R137_E0027</data><data key="edge_operational_context">Proposed mobile reporting would address nonwage change reporting limitations; not established as deployed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0036" source="DOM_TITLE16" target="R137_E0026"><data key="edge_relationship_id">R137_R0036</data><data key="edge_source_entity_id">DOM_TITLE16</data><data key="edge_relationship_type">has_stakeholder_modernization_proposals</data><data key="edge_target_entity_id">R137_E0026</data><data key="edge_operational_context">SSAB recommendation for SSI mobile change reporting is advisory, not evidence of implementation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0037" source="APP_MYCOA" target="R137_E0028"><data key="edge_relationship_id">R137_R0037</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">produces_online_transaction_capture</data><data key="edge_target_entity_id">R137_E0028</data><data key="edge_operational_context">Beneficiary-submitted online changes are captured before documented MBR updates.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0038" source="R137_E0028" target="SYS_MBR"><data key="edge_relationship_id">R137_R0038</data><data key="edge_source_entity_id">R137_E0028</data><data key="edge_relationship_type">has_documented_program_record_update_destination</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA Open Data explicitly says eligible online change-of-address updates are sent to a database and updated to MBR.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0039" source="DATA_COA_INET" target="R137_E0028"><data key="edge_relationship_id">R137_R0039</data><data key="edge_source_entity_id">DATA_COA_INET</data><data key="edge_relationship_type">counts_online_transaction_capture</data><data key="edge_target_entity_id">R137_E0028</data><data key="edge_operational_context">Public volumes cover Internet submissions only, not changes made via FO, telephone or mail.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0040" source="APP_MYDD" target="R137_E0029"><data key="edge_relationship_id">R137_R0040</data><data key="edge_source_entity_id">APP_MYDD</data><data key="edge_relationship_type">produces_online_transaction_capture</data><data key="edge_target_entity_id">R137_E0029</data><data key="edge_operational_context">Eligible Title II beneficiaries enter direct deposit via my Social Security online service.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0041" source="R137_E0029" target="SYS_MBR"><data key="edge_relationship_id">R137_R0041</data><data key="edge_source_entity_id">R137_E0029</data><data key="edge_relationship_type">has_documented_program_record_update_destination</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Official SSA page documents MBR update for online direct deposit changes; does not extend to SSI or non-US mailing addresses.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0042" source="DATA_DD_INET" target="R137_E0029"><data key="edge_relationship_id">R137_R0042</data><data key="edge_source_entity_id">DATA_DD_INET</data><data key="edge_relationship_type">counts_online_transaction_capture</data><data key="edge_target_entity_id">R137_E0029</data><data key="edge_operational_context">The online direct deposit monthly count excludes telephone, field-office and mailed changes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0043" source="APP_SSI_CLAIMS_LOGICAL" target="R137_E0030"><data key="edge_relationship_id">R137_R0043</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">records_financial_institution_identity_not_beneficiary_residence</data><data key="edge_target_entity_id">R137_E0030</data><data key="edge_operational_context">SSI Claims FI Account page records bank name/address/account designation; not an update to SSI recipient residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0044" source="APP_EAFI" target="R137_E0030"><data key="edge_relationship_id">R137_R0044</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">documents_financial_institution_attributes_in</data><data key="edge_target_entity_id">R137_E0030</data><data key="edge_operational_context">Technician uses financial-account page to document FI and account data before SSI resource assessment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0045" source="APP_E4641" target="R137_E0032"><data key="edge_relationship_id">R137_R0045</data><data key="edge_source_entity_id">APP_E4641</data><data key="edge_relationship_type">allows_interest_request_selection</data><data key="edge_target_entity_id">R137_E0032</data><data key="edge_operational_context">POMS directs technicians to select Interest checkbox when requesting interest verification using e4641/eAFI.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0046" source="APP_EAFI" target="R137_E0032"><data key="edge_relationship_id">R137_R0046</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">allows_interest_request_selection</data><data key="edge_target_entity_id">R137_E0032</data><data key="edge_operational_context">POMS documents interest-selection procedure for electronic AFI verification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0047" source="R137_E0031" target="EX_AFI_FI"><data key="edge_relationship_id">R137_R0047</data><data key="edge_source_entity_id">R137_E0031</data><data key="edge_relationship_type">protects_private_banking_credentials_during</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Automated phone FI verification requires account holder to enter private credentials; no SSA collection of passwords or PINs.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0048" source="R137_E0030" target="R135_E0019"><data key="edge_relationship_id">R137_R0048</data><data key="edge_source_entity_id">R137_E0030</data><data key="edge_relationship_type">is_subject_to_resource_ownership_interpretation</data><data key="edge_target_entity_id">R135_E0019</data><data key="edge_operational_context">A documented bank/account address and balance is an investigative resource fact; countability depends on legal access/ownership.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0049" source="DATA_OACT_DEATH_PROB_2026" target="R137_E0033"><data key="edge_relationship_id">R137_R0049</data><data key="edge_source_entity_id">DATA_OACT_DEATH_PROB_2026</data><data key="edge_relationship_type">uses_historical_projection_boundary</data><data key="edge_target_entity_id">R137_E0033</data><data key="edge_operational_context">Published mortality probability files separate historical 1900-2023 and projected 2024-2100 under alternatives I/II/III.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0050" source="DATA_OACT_PERIOD_LIFE_2026" target="R137_E0033"><data key="edge_relationship_id">R137_R0050</data><data key="edge_source_entity_id">DATA_OACT_PERIOD_LIFE_2026</data><data key="edge_relationship_type">uses_historical_projection_boundary</data><data key="edge_target_entity_id">R137_E0033</data><data key="edge_operational_context">The 2026 period life table family publishes historical and three projected assumption scenarios.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0051" source="DATA_OACT_COHORT_LIFE_2026" target="R137_E0034"><data key="edge_relationship_id">R137_R0051</data><data key="edge_source_entity_id">DATA_OACT_COHORT_LIFE_2026</data><data key="edge_relationship_type">uses_birth_cohort_reference_rule</data><data key="edge_target_entity_id">R137_E0034</data><data key="edge_operational_context">2026 cohort life table family is organized by birth year, unlike calendar-year period tables.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0052" source="DATA_OACT_PERIOD_LIFE_2026" target="R137_E0034"><data key="edge_relationship_id">R137_R0052</data><data key="edge_source_entity_id">DATA_OACT_PERIOD_LIFE_2026</data><data key="edge_relationship_type">differs_semantically_from</data><data key="edge_target_entity_id">R137_E0034</data><data key="edge_operational_context">Period life tables reflect mortality for fixed calendar year rather than lifetime of birth cohort.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0053" source="DB_SSI_IRS_INTERFACE" target="R137_E0035"><data key="edge_relationship_id">R137_R0053</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">exposes_recent_two_years_for_alert_retrieval</data><data key="edge_target_entity_id">R137_E0035</data><data key="edge_operational_context">2017 revised IRS interface POMS describes recent two IRS data years available for alerts; no Numident or MBR address overwrite inferred.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0054" source="PORTAL_SUMS_MCAS_MI_CENTRAL" target="R137_E0035"><data key="edge_relationship_id">R137_R0054</data><data key="edge_source_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_relationship_type">queries_the_interface_window</data><data key="edge_target_entity_id">R137_E0035</data><data key="edge_operational_context">POMS says staff can retrieve alerts via MI Central housed-under number overnight; SSTNG offers immediate retrieval.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R137_R0055" source="WORK_SSI_IRS_5B_DIARY" target="R137_E0035"><data key="edge_relationship_id">R137_R0055</data><data key="edge_source_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_relationship_type">is_alert_control_not_address_update_for</data><data key="edge_target_entity_id">R137_E0035</data><data key="edge_operational_context">5B diary calls for income/resource development; it does not document an IRS-supplied address update.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Scope limited to cited public documentation. No unspecified physical interface or propagation asserted.</data></edge><edge id="R138_R0001" source="PROC_MEDICAL_FOLDER_SEARCH" target="R138_E0001"><data key="edge_relationship_id">R138_R0001</data><data key="edge_source_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_relationship_type">requires_cross_system_reconciliation</data><data key="edge_target_entity_id">R138_E0001</data><data key="edge_operational_context">Medical-folder detective work involves multiple independent queries, not a single universal folder index.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0002" source="R138_E0001" target="APP_CATS"><data key="edge_relationship_id">R138_R0002</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">APP_CATS</data><data key="edge_operational_context">POMS DI 13015.080 lists APP_CATS as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0003" source="R138_E0001" target="APP_DDSQ"><data key="edge_relationship_id">R138_R0003</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">APP_DDSQ</data><data key="edge_operational_context">POMS DI 13015.080 lists APP_DDSQ as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0004" source="R138_E0001" target="QRY_FACT"><data key="edge_relationship_id">R138_R0004</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">QRY_FACT</data><data key="edge_operational_context">POMS DI 13015.080 lists QRY_FACT as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0005" source="R138_E0001" target="QRY_OHAQ"><data key="edge_relationship_id">R138_R0005</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">QRY_OHAQ</data><data key="edge_operational_context">POMS DI 13015.080 lists QRY_OHAQ as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0006" source="R138_E0001" target="QRY_QRSL"><data key="edge_relationship_id">R138_R0006</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">QRY_QRSL</data><data key="edge_operational_context">POMS DI 13015.080 lists QRY_QRSL as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0007" source="R138_E0001" target="QRY_SSID"><data key="edge_relationship_id">R138_R0007</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">QRY_SSID</data><data key="edge_operational_context">POMS DI 13015.080 lists QRY_SSID as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0008" source="R138_E0001" target="APP_PCACS"><data key="edge_relationship_id">R138_R0008</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">POMS DI 13015.080 lists APP_PCACS as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0009" source="R138_E0001" target="QRY_OFFLINE_CCTL"><data key="edge_relationship_id">R138_R0009</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">QRY_OFFLINE_CCTL</data><data key="edge_operational_context">POMS DI 13015.080 lists QRY_OFFLINE_CCTL as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0010" source="R138_E0001" target="SYS_NUMIDENT"><data key="edge_relationship_id">R138_R0010</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reviews_query_or_record</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">POMS DI 13015.080 lists SYS_NUMIDENT as a possible medical-folder tracking lead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0011" source="QRY_OFFLINE_CCTL" target="R138_E0002"><data key="edge_relationship_id">R138_R0011</data><data key="edge_source_entity_id">QRY_OFFLINE_CCTL</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">R138_E0002</data><data key="edge_operational_context">The offline 8028/AR25 query displays up to six historical folder locations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0012" source="APP_SSI_FOLDERCTRL" target="R138_E0003"><data key="edge_relationship_id">R138_R0012</data><data key="edge_source_entity_id">APP_SSI_FOLDERCTRL</data><data key="edge_relationship_type">has_documented_limitation</data><data key="edge_target_entity_id">R138_E0003</data><data key="edge_operational_context">Multiple SSI records may share one CCTL line, while prior folder location is overlaid.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0013" source="APP_PCACS" target="R138_E0004"><data key="edge_relationship_id">R138_R0013</data><data key="edge_source_entity_id">APP_PCACS</data><data key="edge_relationship_type">has_documented_limitation</data><data key="edge_target_entity_id">R138_E0004</data><data key="edge_operational_context">PCACS location correction may retain an earlier movement date.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0014" source="R138_E0001" target="R138_E0002"><data key="edge_relationship_id">R138_R0014</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">reconciles</data><data key="edge_target_entity_id">R138_E0002</data><data key="edge_operational_context">Earlier folder location history can resolve misleading current location markers.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0015" source="R138_E0001" target="R138_E0003"><data key="edge_relationship_id">R138_R0015</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R138_E0003</data><data key="edge_operational_context">Technician must not assume a single CCTL field describes every earlier folder.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0016" source="R138_E0001" target="R138_E0004"><data key="edge_relationship_id">R138_R0016</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R138_E0004</data><data key="edge_operational_context">Location and location-date semantics differ when a case has not reached processing centers.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0017" source="R138_E0001" target="R138_E0005"><data key="edge_relationship_id">R138_R0017</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">consults_address_history</data><data key="edge_target_entity_id">R138_E0005</data><data key="edge_operational_context">POMS instructs staff to review address changes before searching other field offices.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0018" source="R138_E0005" target="SYS_MBR"><data key="edge_relationship_id">R138_R0018</data><data key="edge_source_entity_id">R138_E0005</data><data key="edge_relationship_type">examines_address_clue_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Medical-folder location search treats these fields as leads to office routing, not auto-posted residence updates.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0019" source="R138_E0005" target="QRY_SSID"><data key="edge_relationship_id">R138_R0019</data><data key="edge_source_entity_id">R138_E0005</data><data key="edge_relationship_type">examines_address_clue_in</data><data key="edge_target_entity_id">QRY_SSID</data><data key="edge_operational_context">Medical-folder location search treats these fields as leads to office routing, not auto-posted residence updates.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0020" source="R138_E0005" target="QRY_QRSL"><data key="edge_relationship_id">R138_R0020</data><data key="edge_source_entity_id">R138_E0005</data><data key="edge_relationship_type">examines_address_clue_in</data><data key="edge_target_entity_id">QRY_QRSL</data><data key="edge_operational_context">Medical-folder location search treats these fields as leads to office routing, not auto-posted residence updates.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0021" source="R138_E0001" target="R138_E0006"><data key="edge_relationship_id">R138_R0021</data><data key="edge_source_entity_id">R138_E0001</data><data key="edge_relationship_type">uses_cross_identifiers</data><data key="edge_target_entity_id">R138_E0006</data><data key="edge_operational_context">HUN/FUN and spouse/parent cross-references can identify a folder held under a different SSN.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0022" source="QRY_SSID" target="R138_E0006"><data key="edge_relationship_id">R138_R0022</data><data key="edge_source_entity_id">QRY_SSID</data><data key="edge_relationship_type">exposes_hun_fun_for_folder_search</data><data key="edge_target_entity_id">R138_E0006</data><data key="edge_operational_context">Current and earlier SSID query records can reveal HUN/FUN cross-references.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0023" source="R138_E0006" target="APP_SSI_FOLDERCTRL"><data key="edge_relationship_id">R138_R0023</data><data key="edge_source_entity_id">R138_E0006</data><data key="edge_relationship_type">can_explain_location_under</data><data key="edge_target_entity_id">APP_SSI_FOLDERCTRL</data><data key="edge_operational_context">SSICS is described as tracking HUN and may not retain the historical relationship as a single person record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0024" source="SYS_MBR" target="R138_E0007"><data key="edge_relationship_id">R138_R0024</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">may_disclose_address_to_irs_if_authorized</data><data key="edge_target_entity_id">R138_E0007</data><data key="edge_operational_context">MBR address is eligible for release for a valid IRS tax investigation when an applicable routine use permits it.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0025" source="ORG_IRS" target="R138_E0007"><data key="edge_relationship_id">R138_R0025</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">subject_to_mbr_disclosure_conditions</data><data key="edge_target_entity_id">R138_E0007</data><data key="edge_operational_context">IRS tax investigations require a written signed request and legally sufficient identification, purpose, and detail.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0026" source="ORG_IRS" target="R138_E0008"><data key="edge_relationship_id">R138_R0026</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">can_retrieve_fti_per_policy</data><data key="edge_target_entity_id">R138_E0008</data><data key="edge_operational_context">POMS describes retrieval of SSA-held IRS 1099, W-2, W-3 information over a 10-year lookback, not an address master sync.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0027" source="R138_E0008" target="DB_SSI_IRS_INTERFACE"><data key="edge_relationship_id">R138_R0027</data><data key="edge_source_entity_id">R138_E0008</data><data key="edge_relationship_type">not_equivalent_to</data><data key="edge_target_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_operational_context">The 10-year tax-info access window in disclosure policy is not the 2-most-recent-tax-years 5B SSI database query horizon.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0028" source="ORG_IRS" target="R138_E0010"><data key="edge_relationship_id">R138_R0028</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">forwards_deferred_vested_plan_information_for</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">IRS provides SSA with pension plan data for notices, not SSA retirement benefit records.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0029" source="R138_E0009" target="R138_E0010"><data key="edge_relationship_id">R138_R0029</data><data key="edge_source_entity_id">R138_E0009</data><data key="edge_relationship_type">provides_plan_identifiers_for</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">SSA uses the Form 8955-SSA-supplied plan number and EIN when issuing pension information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0030" source="R138_E0009" target="R138_E0012"><data key="edge_relationship_id">R138_R0030</data><data key="edge_source_entity_id">R138_E0009</data><data key="edge_relationship_type">forms_compound_identifier</data><data key="edge_target_entity_id">R138_E0012</data><data key="edge_operational_context">Three-digit plan number is concatenated with nine-digit EIN for 12-digit retrieval key.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0031" source="R138_E0010" target="R138_E0011"><data key="edge_relationship_id">R138_R0031</data><data key="edge_source_entity_id">R138_E0010</data><data key="edge_relationship_type">carries</data><data key="edge_target_entity_id">R138_E0011</data><data key="edge_operational_context">Notice contains plan administrator name and mailing address, not the beneficiary home address.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0032" source="R138_E0010" target="R138_E0012"><data key="edge_relationship_id">R138_R0032</data><data key="edge_source_entity_id">R138_E0010</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R138_E0012</data><data key="edge_operational_context">Plan number appears in beneficiary notice; separate from personal SSN.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0033" source="APP_ECO" target="R110_E050"><data key="edge_relationship_id">R138_R0033</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">applies_address_recency_gate</data><data key="edge_target_entity_id">R110_E050</data><data key="edge_operational_context">ECO uses contractor verification, then program address recency, and delayed 6-month recheck if needed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0034" source="R110_E050" target="DATA_AVC_DEBTOR_ADDR"><data key="edge_relationship_id">R138_R0034</data><data key="edge_source_entity_id">R110_E050</data><data key="edge_relationship_type">prefers</data><data key="edge_target_entity_id">DATA_AVC_DEBTOR_ADDR</data><data key="edge_operational_context">Verified contractor-delivered address takes precedence for mailing this particular notice.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0035" source="R110_E050" target="SYS_MBR"><data key="edge_relationship_id">R138_R0035</data><data key="edge_source_entity_id">R110_E050</data><data key="edge_relationship_type">fallback_reads</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR address may supply pre-offset notice only if updated in past year and no contractor-valid address is found.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0036" source="R110_E050" target="SYS_SSR"><data key="edge_relationship_id">R138_R0036</data><data key="edge_source_entity_id">R110_E050</data><data key="edge_relationship_type">fallback_reads</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR address may supply pre-offset notice only if updated in past year and no contractor-valid address is found.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0037" source="APP_ECO" target="R110_E049"><data key="edge_relationship_id">R138_R0037</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">must_defer_or_reopen_procedure</data><data key="edge_target_entity_id">R110_E049</data><data key="edge_operational_context">Returned unremedied TRO notices may require full new review opportunity, and suspend offset selection until debt re-established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0038" source="APP_ROAR" target="R110_E049"><data key="edge_relationship_id">R138_R0038</data><data key="edge_source_entity_id">APP_ROAR</data><data key="edge_relationship_type">supports_delete_reestablish_for</data><data key="edge_target_entity_id">R110_E049</data><data key="edge_operational_context">Debt is deleted by SMTC, verified next day, re-established by SMED using current establishment date.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0039" source="APP_ORS" target="R110_E049"><data key="edge_relationship_id">R138_R0039</data><data key="edge_source_entity_id">APP_ORS</data><data key="edge_relationship_type">retains_notices_used_in</data><data key="edge_target_entity_id">R110_E049</data><data key="edge_operational_context">POMS places ECO notice copies from November 2015 onward in On-line Retrieval System.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0040" source="DATA_OASDI_STATE_COUNTY_2025" target="R138_E0013"><data key="edge_relationship_id">R138_R0040</data><data key="edge_source_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_relationship_type">has_payee_geography_caveat</data><data key="edge_target_entity_id">R138_E0013</data><data key="edge_operational_context">Geographic data for beneficiaries with payees reflects payee location.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0041" source="DATA_OASDI_STATE_COUNTY_2025" target="R138_E0014"><data key="edge_relationship_id">R138_R0041</data><data key="edge_source_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_relationship_type">applies_disclosure_transformation</data><data key="edge_target_entity_id">R138_E0014</data><data key="edge_operational_context">County table totals and dollar amounts may differ from raw master-record amounts due to controlled rounding/reweighting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0042" source="SYS_MBR" target="DATA_OASDI_STATE_COUNTY_2025"><data key="edge_relationship_id">R138_R0042</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">feeds_aggregate_product</data><data key="edge_target_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_operational_context">2025 state/county tables are derived from MBR; no claim of direct public personal records.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0043" source="R138_E0016" target="R138_E0015"><data key="edge_relationship_id">R138_R0043</data><data key="edge_source_entity_id">R138_E0016</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R138_E0015</data><data key="edge_operational_context">Historical HTML table editions are assembled into public flattened JSON and CSV outputs after edits/corrections.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0044" source="DATA_OASDI_STATE_COUNTY_2025" target="R138_E0015"><data key="edge_relationship_id">R138_R0044</data><data key="edge_source_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_relationship_type">included_in</data><data key="edge_target_entity_id">R138_E0015</data><data key="edge_operational_context">2025 annual edition is included in flattened 1999-to-current aggregate release.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0045" source="R138_E0015" target="R138_E0018"><data key="edge_relationship_id">R138_R0045</data><data key="edge_source_entity_id">R138_E0015</data><data key="edge_relationship_type">has_variable_key_caveat</data><data key="edge_target_entity_id">R138_E0018</data><data key="edge_operational_context">Public beta schema may change; consumer should version its parser.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0046" source="R138_E0015" target="R138_E0017"><data key="edge_relationship_id">R138_R0046</data><data key="edge_source_entity_id">R138_E0015</data><data key="edge_relationship_type">normalizes_codes_by</data><data key="edge_target_entity_id">R138_E0017</data><data key="edge_operational_context">Pre-2008 ANSI code values null; numbers stored as strings to preserve zero-padding.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0047" source="R138_E0015" target="R138_E0019"><data key="edge_relationship_id">R138_R0047</data><data key="edge_source_entity_id">R138_E0015</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R138_E0019</data><data key="edge_operational_context">Official beta series supplies Table 1 CSV and JSON dataset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0048" source="R138_E0015" target="R138_E0020"><data key="edge_relationship_id">R138_R0048</data><data key="edge_source_entity_id">R138_E0015</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R138_E0020</data><data key="edge_operational_context">Official beta series supplies Table 2 CSV and JSON dataset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0049" source="R138_E0015" target="R138_E0021"><data key="edge_relationship_id">R138_R0049</data><data key="edge_source_entity_id">R138_E0015</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R138_E0021</data><data key="edge_operational_context">Official beta series supplies Table 3 CSV and JSON dataset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0050" source="R138_E0015" target="R138_E0022"><data key="edge_relationship_id">R138_R0050</data><data key="edge_source_entity_id">R138_E0015</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R138_E0022</data><data key="edge_operational_context">Official beta series supplies Table 4 CSV and JSON dataset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0051" source="R138_E0015" target="R138_E0023"><data key="edge_relationship_id">R138_R0051</data><data key="edge_source_entity_id">R138_E0015</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R138_E0023</data><data key="edge_operational_context">Official beta series supplies Table 5 CSV and JSON dataset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0052" source="DATA_SSI_STATE_COUNTY_2025" target="R138_E0024"><data key="edge_relationship_id">R138_R0052</data><data key="edge_source_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_relationship_type">excludes</data><data key="edge_target_entity_id">R138_E0024</data><data key="edge_operational_context">State-administered supplement amounts are not in these published SSI payment amounts.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0053" source="DATA_SSI_STATE_COUNTY_2025" target="R138_E0025"><data key="edge_relationship_id">R138_R0053</data><data key="edge_source_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_relationship_type">uses_disclosure_protection</data><data key="edge_target_entity_id">R138_E0025</data><data key="edge_operational_context">Suppressed county values are nevertheless included in state totals.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0054" source="SYS_SSR" target="DATA_SSI_STATE_COUNTY_2025"><data key="edge_relationship_id">R138_R0054</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">is_administrative_source_for</data><data key="edge_target_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_operational_context">State/county SSI publication derives from Supplemental Security Record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0055" source="DATA_SSI_STATE_COUNTY_2025" target="R138_E0026"><data key="edge_relationship_id">R138_R0055</data><data key="edge_source_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_relationship_type">included_in</data><data key="edge_target_entity_id">R138_E0026</data><data key="edge_operational_context">Current annual SSI state-county tables included in historical flattened products.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0056" source="R138_E0027" target="R138_E0026"><data key="edge_relationship_id">R138_R0056</data><data key="edge_source_entity_id">R138_E0027</data><data key="edge_relationship_type">regenerates</data><data key="edge_target_entity_id">R138_E0026</data><data key="edge_operational_context">Each annual update processes full corrected HTML archive rather than appending unalterable rows.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0057" source="R138_E0026" target="R138_E0028"><data key="edge_relationship_id">R138_R0057</data><data key="edge_source_entity_id">R138_E0026</data><data key="edge_relationship_type">excludes_table</data><data key="edge_target_entity_id">R138_E0028</data><data key="edge_operational_context">Table 4 lacks flattened format because historical layouts differ.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0058" source="R138_E0026" target="R138_E0029"><data key="edge_relationship_id">R138_R0058</data><data key="edge_source_entity_id">R138_E0026</data><data key="edge_relationship_type">normalizes_codes_and_suppression_by</data><data key="edge_target_entity_id">R138_E0029</data><data key="edge_operational_context">Publication clarifies JSON/CSV fields and suppression values.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0059" source="R138_E0026" target="R138_E0030"><data key="edge_relationship_id">R138_R0059</data><data key="edge_source_entity_id">R138_E0026</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R138_E0030</data><data key="edge_operational_context">Official SSI flat series supplies Table 1 JSON and CSV output.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0060" source="R138_E0026" target="R138_E0031"><data key="edge_relationship_id">R138_R0060</data><data key="edge_source_entity_id">R138_E0026</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R138_E0031</data><data key="edge_operational_context">Official SSI flat series supplies Table 2 JSON and CSV output.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0061" source="R138_E0026" target="R138_E0032"><data key="edge_relationship_id">R138_R0061</data><data key="edge_source_entity_id">R138_E0026</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R138_E0032</data><data key="edge_operational_context">Official SSI flat series supplies Table 3 JSON and CSV output.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0062" source="R138_E0033" target="SYS_MBR"><data key="edge_relationship_id">R138_R0062</data><data key="edge_source_entity_id">R138_E0033</data><data key="edge_relationship_type">samples_transactions_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Monthly random samples include current MBR payments and recently processed RSDI transactions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0063" source="R138_E0033" target="FORM_SSA93"><data key="edge_relationship_id">R138_R0063</data><data key="edge_source_entity_id">R138_E0033</data><data key="edge_relationship_type">may_include</data><data key="edge_target_entity_id">FORM_SSA93</data><data key="edge_operational_context">Quality Review uses SSA-93 to refer errors for corrective action (see subsequent POMS).</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0064" source="R138_E0034" target="R138_E0033"><data key="edge_relationship_id">R138_R0064</data><data key="edge_source_entity_id">R138_E0034</data><data key="edge_relationship_type">supports_authenticating_quality_reviewer</data><data key="edge_target_entity_id">R138_E0033</data><data key="edge_operational_context">Public can authenticate QR employee through FO/TSC and suspected fraud is routed to ARIS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0065" source="APP_SSA93_QR_WEB" target="R138_E0035"><data key="edge_relationship_id">R138_R0065</data><data key="edge_source_entity_id">APP_SSA93_QR_WEB</data><data key="edge_relationship_type">controls_deadline_and_extension</data><data key="edge_target_entity_id">R138_E0035</data><data key="edge_operational_context">Ninety-day closure deadline; approval/denial of extension requests is retained for audit.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0066" source="APP_SSA93_QR_WEB" target="R138_E0036"><data key="edge_relationship_id">R138_R0066</data><data key="edge_source_entity_id">APP_SSA93_QR_WEB</data><data key="edge_relationship_type">supports_rebuttals_within</data><data key="edge_target_entity_id">R138_E0036</data><data key="edge_operational_context">The SSA-93 web application sends rebuttal requests, rationale, and files to reviewers.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0067" source="APP_SSA93_QR_WEB" target="R138_E0037"><data key="edge_relationship_id">R138_R0067</data><data key="edge_source_entity_id">APP_SSA93_QR_WEB</data><data key="edge_relationship_type">flags_high_risk_review_for</data><data key="edge_target_entity_id">R138_E0037</data><data key="edge_operational_context">Closed corrections with high-risk indicators are centrally rechecked; reminders generated when incomplete.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0068" source="FORM_SSA93" target="R138_E0035"><data key="edge_relationship_id">R138_R0068</data><data key="edge_source_entity_id">FORM_SSA93</data><data key="edge_relationship_type">routes_corrections_through</data><data key="edge_target_entity_id">R138_E0035</data><data key="edge_operational_context">SSA-93 travels from QR to FO/PC with electronic folder/NDRED evidence references.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R138_R0069" source="DATA_USPS_NATIONAL_ZIP4" target="R138_E0038"><data key="edge_relationship_id">R138_R0069</data><data key="edge_source_entity_id">DATA_USPS_NATIONAL_ZIP4</data><data key="edge_relationship_type">supports_postal_address_standardization</data><data key="edge_target_entity_id">R138_E0038</data><data key="edge_operational_context">Postal addressing rules validate delivery line and last line city/state/ZIP, not recipient residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Supported only for the cited business process and observation date; no undocumented system synchronization inferred.</data></edge><edge id="R139_R0001" source="R139_E0001" target="APP_SSNAP"><data key="edge_relationship_id">R139_R0001</data><data key="edge_source_entity_id">R139_E0001</data><data key="edge_relationship_type">documents_responsibility_for_maintenance_of</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">2023 operating responsibility for software, not proof of current organization structure.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0002" source="R139_E0001" target="SYS_NUMIDENT"><data key="edge_relationship_id">R139_R0002</data><data key="edge_source_entity_id">R139_E0001</data><data key="edge_relationship_type">documents_responsibility_for_file_updates_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Responsibility to update files including Numident, not direct human modification of database.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0003" source="R139_E0002" target="SYS_NUMIDENT"><data key="edge_relationship_id">R139_R0003</data><data key="edge_source_entity_id">R139_E0002</data><data key="edge_relationship_type">documents_database_operations_responsibility_for</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">2023 documented division operations role.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0004" source="R139_E0003" target="SYS_NUMIDENT"><data key="edge_relationship_id">R139_R0004</data><data key="edge_source_entity_id">R139_E0003</data><data key="edge_relationship_type">posts_issuance_control_number_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Print/mailing control number is captured on Numident.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0005" source="R139_E0004" target="SYS_NUMIDENT"><data key="edge_relationship_id">R139_R0005</data><data key="edge_source_entity_id">R139_E0004</data><data key="edge_relationship_type">reconciles_discrepancies_between</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">PSC corrections reconcile Numident and beneficiary context.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0006" source="R139_E0004" target="SYS_MBR"><data key="edge_relationship_id">R139_R0006</data><data key="edge_source_entity_id">R139_E0004</data><data key="edge_relationship_type">consults_discrepant_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PSC handles discrepancy-induced card actions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0007" source="EX_EBE" target="R139_E0005"><data key="edge_relationship_id">R139_R0007</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">uses_pending_application_address_control</data><data key="edge_target_entity_id">R139_E0005</data><data key="edge_operational_context">Exception-resolution verifies card contact address rather than recipient residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0008" source="APP_SSNAP" target="R139_E0006"><data key="edge_relationship_id">R139_R0008</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">applies_pending_ebe_identity_match_rule</data><data key="edge_target_entity_id">R139_E0006</data><data key="edge_operational_context">Pending SSNAP match can use ARN and name/DOB variants.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0009" source="R139_E0006" target="SYS_NUMIDENT"><data key="edge_relationship_id">R139_R0009</data><data key="edge_source_entity_id">R139_E0006</data><data key="edge_relationship_type">references_identifying_record</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Existing Numident SSN and identifying data considered in EBE search and matching.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0010" source="R139_E0007" target="R139_E0008"><data key="edge_relationship_id">R139_R0010</data><data key="edge_source_entity_id">R139_E0007</data><data key="edge_relationship_type">is_relayed_for_manual_entry_by</data><data key="edge_target_entity_id">R139_E0008</data><data key="edge_operational_context">OIG to CO to RO sequence, as described in 2022 POMS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0011" source="R139_E0008" target="APP_ERPS"><data key="edge_relationship_id">R139_R0011</data><data key="edge_source_entity_id">R139_E0008</data><data key="edge_relationship_type">enters_conviction_indicators_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Staff entry documented; no API mechanism established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0012" source="APP_ERPS" target="R139_E0009"><data key="edge_relationship_id">R139_R0012</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">enforces_barred_conviction_control</data><data key="edge_target_entity_id">R139_E0009</data><data key="edge_operational_context">eRPS selection decision restricted for listed convictions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0013" source="R139_E0009" target="R139_E0007"><data key="edge_relationship_id">R139_R0013</data><data key="edge_source_entity_id">R139_E0009</data><data key="edge_relationship_type">is_based_on</data><data key="edge_target_entity_id">R139_E0007</data><data key="edge_operational_context">OIG-provided conviction listing informs a selection safeguard.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0014" source="APP_ERPS" target="R139_E0010"><data key="edge_relationship_id">R139_R0014</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">flags_death_discrepancy_with</data><data key="edge_target_entity_id">R139_E0010</data><data key="edge_operational_context">Mismatch involving Numident and program benefit records, not automatic synchronization.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0015" source="R139_E0010" target="SYS_NUMIDENT"><data key="edge_relationship_id">R139_R0015</data><data key="edge_source_entity_id">R139_E0010</data><data key="edge_relationship_type">compares_identity_death_record</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">NUMI death information in discrepancy assessment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0016" source="R139_E0010" target="SYS_MBR"><data key="edge_relationship_id">R139_R0016</data><data key="edge_source_entity_id">R139_E0010</data><data key="edge_relationship_type">compares_title_ii_death_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR death entry part of eRPS discrepancy test.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0017" source="R139_E0010" target="SYS_SSR"><data key="edge_relationship_id">R139_R0017</data><data key="edge_source_entity_id">R139_E0010</data><data key="edge_relationship_type">compares_title_xvi_death_record</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR death entry part of eRPS discrepancy test.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0018" source="APP_ERPS" target="R139_E0011"><data key="edge_relationship_id">R139_R0018</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">requires_identity_mismatch_resolution_using</data><data key="edge_target_entity_id">R139_E0011</data><data key="edge_operational_context">Client identity different from Numident requires investigation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0019" source="R139_E0011" target="SYS_NUMIDENT"><data key="edge_relationship_id">R139_R0019</data><data key="edge_source_entity_id">R139_E0011</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Use authoritative enumeration identity record to resolve mismatch.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0020" source="APP_ERPS" target="R139_E0012"><data key="edge_relationship_id">R139_R0020</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">can_create_followup_for</data><data key="edge_target_entity_id">R139_E0012</data><data key="edge_operational_context">Eligibility exception recorded with 180-day evidence control.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0021" source="APP_ERPS" target="R139_E0013"><data key="edge_relationship_id">R139_R0021</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">has_manual_vendor_failure_fallback</data><data key="edge_target_entity_id">R139_E0013</data><data key="edge_operational_context">2022 POMS identifies an integration failure path, not normal successful backend method.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0022" source="R139_E0013" target="SVC_LEXISNEXIS_ACCURINT"><data key="edge_relationship_id">R139_R0022</data><data key="edge_source_entity_id">R139_E0013</data><data key="edge_relationship_type">uses_external_manual_service</data><data key="edge_target_entity_id">SVC_LEXISNEXIS_ACCURINT</data><data key="edge_operational_context">Accurint accessed outside eRPS only when vendor connection fails.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0023" source="R139_E0013" target="R139_E0014"><data key="edge_relationship_id">R139_R0023</data><data key="edge_source_entity_id">R139_E0013</data><data key="edge_relationship_type">requires_manager_documentation</data><data key="edge_target_entity_id">R139_E0014</data><data key="edge_operational_context">Manager confirms out-of-system check in eRPS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0024" source="APP_EVIEW" target="R139_E0015"><data key="edge_relationship_id">R139_R0024</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">provides_claimant_pdf_export_workflow</data><data key="edge_target_entity_id">R139_E0015</data><data key="edge_operational_context">Send to mySSA from selected CEF PDF documents.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0025" source="R139_E0015" target="SVC_MYSSA_MESSAGE_CENTER"><data key="edge_relationship_id">R139_R0025</data><data key="edge_source_entity_id">R139_E0015</data><data key="edge_relationship_type">delivers_selected_documents_to</data><data key="edge_target_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_operational_context">Disclosed selected PDF goes to claimant mySSA account.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0026" source="APP_EVIEW" target="R139_E0016"><data key="edge_relationship_id">R139_R0026</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">offers_secure_email_export</data><data key="edge_target_entity_id">R139_E0016</data><data key="edge_operational_context">Password-protected eFolder PDF disclosure path.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0027" source="R139_E0015" target="R139_E0017"><data key="edge_relationship_id">R139_R0027</data><data key="edge_source_entity_id">R139_E0015</data><data key="edge_relationship_type">requires_audit_annotation</data><data key="edge_target_entity_id">R139_E0017</data><data key="edge_operational_context">eView message records channel/recipient/date.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0028" source="R139_E0016" target="R139_E0017"><data key="edge_relationship_id">R139_R0028</data><data key="edge_source_entity_id">R139_E0016</data><data key="edge_relationship_type">requires_audit_annotation</data><data key="edge_target_entity_id">R139_E0017</data><data key="edge_operational_context">eView message records secure email disclosure.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0029" source="R139_E0015" target="REPO_CEF"><data key="edge_relationship_id">R139_R0029</data><data key="edge_source_entity_id">R139_E0015</data><data key="edge_relationship_type">derives_selected_documents_from</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">CEF source contains documents; not automatic full-folder mirroring.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0030" source="APP_EVIEW" target="R139_E0018"><data key="edge_relationship_id">R139_R0030</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">applies_sensitive_release_filter</data><data key="edge_target_entity_id">R139_E0018</data><data key="edge_operational_context">Selected documents exclude those withheld by official access/disclosure rules.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0031" source="REPO_CEF" target="R139_E0019"><data key="edge_relationship_id">R139_R0031</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">may_contain_releasable_hearing_exhibits</data><data key="edge_target_entity_id">R139_E0019</data><data key="edge_operational_context">Official audio exhibits vs internal hearing notes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0032" source="R139_E0015" target="R139_E0018"><data key="edge_relationship_id">R139_R0032</data><data key="edge_source_entity_id">R139_E0015</data><data key="edge_relationship_type">is_subject_to</data><data key="edge_target_entity_id">R139_E0018</data><data key="edge_operational_context">mySSA folder export does not override disclosure rules.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0033" source="R139_E0020" target="R139_E0021"><data key="edge_relationship_id">R139_R0033</data><data key="edge_source_entity_id">R139_E0020</data><data key="edge_relationship_type">includes_cyber_logging_recommendation</data><data key="edge_target_entity_id">R139_E0021</data><data key="edge_operational_context">July 2025 CIO open recommendations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0034" source="R139_E0020" target="R139_E0022"><data key="edge_relationship_id">R139_R0034</data><data key="edge_source_entity_id">R139_E0020</data><data key="edge_relationship_type">includes_software_inventory_recommendation</data><data key="edge_target_entity_id">R139_E0022</data><data key="edge_operational_context">July 2025 CIO open recommendations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0035" source="R139_E0022" target="APP_SW_LICENSE_TRACKER"><data key="edge_relationship_id">R139_R0035</data><data key="edge_source_entity_id">R139_E0022</data><data key="edge_relationship_type">governs_license_accountability_context_for</data><data key="edge_target_entity_id">APP_SW_LICENSE_TRACKER</data><data key="edge_operational_context">This ties a governance goal to a known SSA license tool, not GAO assertion that this product itself fulfills the recommendation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0036" source="R139_E0023" target="R139_E0024"><data key="edge_relationship_id">R139_R0036</data><data key="edge_source_entity_id">R139_E0023</data><data key="edge_relationship_type">explicitly_subject_to</data><data key="edge_target_entity_id">R139_E0024</data><data key="edge_operational_context">Projection sensitivity documented in 2026 SSI Annual Report.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0037" source="REPORT_TRUSTEES_2026" target="R139_E0023"><data key="edge_relationship_id">R139_R0037</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">sets_oasdi_assumptions_affecting</data><data key="edge_target_entity_id">R139_E0023</data><data key="edge_operational_context">Uses intermediate assumptions and current-law scheduled benefits; not payable balance after insolvency.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0038" source="MODEL_OACT_LABOR_FORCE" target="R139_E0025"><data key="edge_relationship_id">R139_R0038</data><data key="edge_source_entity_id">MODEL_OACT_LABOR_FORCE</data><data key="edge_relationship_type">stratifies_by</data><data key="edge_target_entity_id">R139_E0025</data><data key="edge_operational_context">Explicit model dimensions from 2026 Trustees methods.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0039" source="MODEL_OACT_LABOR_FORCE" target="R139_E0026"><data key="edge_relationship_id">R139_R0039</data><data key="edge_source_entity_id">MODEL_OACT_LABOR_FORCE</data><data key="edge_relationship_type">uses_participation_assumptions_from</data><data key="edge_target_entity_id">R139_E0026</data><data key="edge_operational_context">Socioeconomic and demographic projection factors.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0040" source="R139_E0027" target="R139_E0028"><data key="edge_relationship_id">R139_R0040</data><data key="edge_source_entity_id">R139_E0027</data><data key="edge_relationship_type">has_corrected_publication_error</data><data key="edge_target_entity_id">R139_E0028</data><data key="edge_operational_context">Official April 2026 notice modifies statistical value in prior released edition.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0041" source="R139_E0027" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R139_R0041</data><data key="edge_source_entity_id">R139_E0027</data><data key="edge_relationship_type">historical_predecessor_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Publication-version relationship, not same source data.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0042" source="REPO_SSA_VENDOR" target="R139_E0029"><data key="edge_relationship_id">R139_R0042</data><data key="edge_source_entity_id">REPO_SSA_VENDOR</data><data key="edge_relationship_type">has_documented_retention_rule</data><data key="edge_target_entity_id">R139_E0029</data><data key="edge_operational_context">Approximate one-year repository data deletion, not email system retention assurance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0043" source="PROC_VENDOR_REPO_SUBMISSION" target="R139_E0030"><data key="edge_relationship_id">R139_R0043</data><data key="edge_source_entity_id">PROC_VENDOR_REPO_SUBMISSION</data><data key="edge_relationship_type">has_email_ingest_size_limit</data><data key="edge_target_entity_id">R139_E0030</data><data key="edge_operational_context">5MB attachment-inclusive intake policy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0044" source="REPO_SSA_VENDOR" target="R139_E0031"><data key="edge_relationship_id">R139_R0044</data><data key="edge_source_entity_id">REPO_SSA_VENDOR</data><data key="edge_relationship_type">allows_use_for_market_research</data><data key="edge_target_entity_id">R139_E0031</data><data key="edge_operational_context">Not a source-selection bidding list.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0045" source="DATA_HRS_DER" target="R139_E0032"><data key="edge_relationship_id">R139_R0045</data><data key="edge_source_entity_id">DATA_HRS_DER</data><data key="edge_relationship_type">has_april2026_release_attributes</data><data key="edge_target_entity_id">R139_E0032</data><data key="edge_operational_context">Restricted April 2026 MEF-derived data product, not live SSA feed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0046" source="DATA_HRS_DER" target="R139_E0033"><data key="edge_relationship_id">R139_R0046</data><data key="edge_source_entity_id">DATA_HRS_DER</data><data key="edge_relationship_type">has_incomplete_early_year_warning</data><data key="edge_target_entity_id">R139_E0033</data><data key="edge_operational_context">Do not treat 1978/1979 detailed employer earnings as complete.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0047" source="DATA_HRS_DER" target="R139_E0034"><data key="edge_relationship_id">R139_R0047</data><data key="edge_source_entity_id">DATA_HRS_DER</data><data key="edge_relationship_type">april2026_distributed_separately_from</data><data key="edge_target_entity_id">R139_E0034</data><data key="edge_operational_context">Weights file not contained in April 2026 detailed earnings download.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0048" source="APP_SERS" target="R139_E0035"><data key="edge_relationship_id">R139_R0048</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">requires_per_debtor_query_for</data><data key="edge_target_entity_id">R139_E0035</data><data key="edge_operational_context">Multi-beneficiary payments require separate debtor selections, even on shared earnings record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0049" source="APP_SERS" target="R139_E0036"><data key="edge_relationship_id">R139_R0049</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">has_exception_handling</data><data key="edge_target_entity_id">R139_E0036</data><data key="edge_operational_context">If web service fails, follow established legacy remittance paths.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R139_R0050" source="R139_E0036" target="APP_DMS"><data key="edge_relationship_id">R139_R0050</data><data key="edge_source_entity_id">R139_E0036</data><data key="edge_relationship_type">uses_manual_fallback</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Manual DMS path not proof of automated debt reconciliation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship asserted only for documented flow, role, and date; not an undocumented current backend integration.</data></edge><edge id="R140_R0001" source="APP_PERSON_INFO" target="R140_E0001"><data key="edge_relationship_id">R140_R0001</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">supplies_mail_zip_for</data><data key="edge_target_entity_id">R140_E0001</data><data key="edge_operational_context">Person Information supplies recorded mailing ZIP attribute for routing; current delivery/residence not guaranteed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0002" source="APP_UPLOAD_DOCUMENTS" target="R140_E0002"><data key="edge_relationship_id">R140_R0002</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">uses_routing_rule</data><data key="edge_target_entity_id">R140_E0002</data><data key="edge_operational_context">March 2025 customer-initiated forms routed based on PI ZIP.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0003" source="R140_E0002" target="R140_E0001"><data key="edge_relationship_id">R140_R0003</data><data key="edge_source_entity_id">R140_E0002</data><data key="edge_relationship_type">uses_field</data><data key="edge_target_entity_id">R140_E0001</data><data key="edge_operational_context">Routed to FO associated with PI mailing ZIP, not to an enterprise beneficiary account master.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0004" source="APP_UPLOAD_DOCUMENTS" target="R140_E0003"><data key="edge_relationship_id">R140_R0004</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">prompts_if_address_absent</data><data key="edge_target_entity_id">R140_E0003</data><data key="edge_operational_context">If PI address missing, requests mailing ZIP before submission.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0005" source="R140_E0003" target="R140_E0001"><data key="edge_relationship_id">R140_R0005</data><data key="edge_source_entity_id">R140_E0003</data><data key="edge_relationship_type">conditioned_on_missing</data><data key="edge_target_entity_id">R140_E0001</data><data key="edge_operational_context">ZIP solicitation is transactional; no verified change to PI established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0006" source="APP_UPLOAD_DOCUMENTS" target="R140_E0004"><data key="edge_relationship_id">R140_R0006</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R140_E0004</data><data key="edge_operational_context">Submitted documents enter WorkTrack intake process.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0007" source="R140_E0004" target="APP_WORKTRACK"><data key="edge_relationship_id">R140_R0007</data><data key="edge_source_entity_id">R140_E0004</data><data key="edge_relationship_type">is_managed_in</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">WorkTrack carries submitted work item to servicing FO before technician assignment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0008" source="APP_UPLOAD_DOCUMENTS" target="R140_E0005"><data key="edge_relationship_id">R140_R0008</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">has_date_scoped_eligibility</data><data key="edge_target_entity_id">R140_E0005</data><data key="edge_operational_context">2025-03-29 scope: forms-only customer initiation; subsequent releases not assessed by this source.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0009" source="APP_TED" target="R140_E0006"><data key="edge_relationship_id">R140_R0009</data><data key="edge_source_entity_id">APP_TED</data><data key="edge_relationship_type">controls_technician_requested</data><data key="edge_target_entity_id">R140_E0006</data><data key="edge_operational_context">Listed benefit and appeals forms are technician-initiated under March 2025 instructions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0010" source="APP_UPLOAD_DOCUMENTS" target="R140_E0006"><data key="edge_relationship_id">R140_R0010</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">has_technician_only_subset</data><data key="edge_target_entity_id">R140_E0006</data><data key="edge_operational_context">The 2025 customer self-service option excludes the listed forms.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0011" source="SVC_MYSSA_MESSAGE_CENTER" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R140_R0011</data><data key="edge_source_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_relationship_type">issues_customer_submission_receipt_for</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Successful customer-initiated submissions automatically generate a Message Center receipt.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0012" source="APP_ERPS" target="R140_E0007"><data key="edge_relationship_id">R140_R0012</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">automatically_propagates_within_application</data><data key="edge_target_entity_id">R140_E0007</data><data key="edge_operational_context">Explicit intra-eRPS note propagation only; not evidence of MBR or SSR synchronization.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0013" source="DATA_ERPS_BENE_CAPABILITY_NOTE" target="UI_ERPS_BENE_DETAILS"><data key="edge_relationship_id">R140_R0013</data><data key="edge_source_entity_id">DATA_ERPS_BENE_CAPABILITY_NOTE</data><data key="edge_relationship_type">is_displayed_under</data><data key="edge_target_entity_id">UI_ERPS_BENE_DETAILS</data><data key="edge_operational_context">A saved capability note is propagated to Beneficiary Details notes as documented in June 2026.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0014" source="R140_E0007" target="UI_ERPS_BENE_DETAILS"><data key="edge_relationship_id">R140_R0014</data><data key="edge_source_entity_id">R140_E0007</data><data key="edge_relationship_type">propagates_to</data><data key="edge_target_entity_id">UI_ERPS_BENE_DETAILS</data><data key="edge_operational_context">Application Summary capability note propagated to beneficiary notes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0015" source="APP_ERPS" target="R140_E0008"><data key="edge_relationship_id">R140_R0015</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">supports_no_new_application_route</data><data key="edge_target_entity_id">R140_E0008</data><data key="edge_operational_context">A prior eRPS beneficiary record can hold a capability determination despite no new payee application.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0016" source="R140_E0008" target="UI_ERPS_BENE_DETAILS"><data key="edge_relationship_id">R140_R0016</data><data key="edge_source_entity_id">R140_E0008</data><data key="edge_relationship_type">is_documented_on</data><data key="edge_target_entity_id">UI_ERPS_BENE_DETAILS</data><data key="edge_operational_context">Beneficiary Details note location required when no new application exists.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0017" source="R140_E0009" target="APP_MCS"><data key="edge_relationship_id">R140_R0017</data><data key="edge_source_entity_id">R140_E0009</data><data key="edge_relationship_type">uses_title_ii_record</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Title II and concurrent capability determination documented on MCS RPOC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0018" source="R140_E0009" target="APP_CCE"><data key="edge_relationship_id">R140_R0018</data><data key="edge_source_entity_id">R140_E0009</data><data key="edge_relationship_type">uses_title_xvi_record</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Title XVI-only capability decision documented on CCE Report of Contact.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0019" source="R140_E0009" target="R140_E0010"><data key="edge_relationship_id">R140_R0019</data><data key="edge_source_entity_id">R140_E0009</data><data key="edge_relationship_type">has_paper_fallback</data><data key="edge_target_entity_id">R140_E0010</data><data key="edge_operational_context">SSA-5002 retained electronically if no suitable Report of Contact established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0020" source="R140_E0010" target="FORM_SSA5002"><data key="edge_relationship_id">R140_R0020</data><data key="edge_source_entity_id">R140_E0010</data><data key="edge_relationship_type">uses_document</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">Paper SSA-5002 is used when MCS or CCE report unavailable.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0021" source="R140_E0010" target="REPO_NDRED"><data key="edge_relationship_id">R140_R0021</data><data key="edge_source_entity_id">R140_E0010</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Evidence Portal storage in NDRed when applicable.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0022" source="R140_E0010" target="APP_EVIEW"><data key="edge_relationship_id">R140_R0022</data><data key="edge_source_entity_id">R140_E0010</data><data key="edge_relationship_type">alternatively_stored_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">eView storage of fallback evidence document permitted.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0023" source="EX_PIE" target="R140_E0011"><data key="edge_relationship_id">R140_R0023</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">is_primary_evidence_under</data><data key="edge_target_entity_id">R140_E0011</data><data key="edge_operational_context">PIE is primary wage evidence, not evidence that all claims are automatically verified.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0024" source="EX_PIE" target="R140_E0012"><data key="edge_relationship_id">R140_R0024</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">conditionally_posts_to</data><data key="edge_target_entity_id">R140_E0012</data><data key="edge_operational_context">Auto post only where identifying information such as employer EIN matches.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0025" source="R140_E0012" target="APP_CCE"><data key="edge_relationship_id">R140_R0025</data><data key="edge_source_entity_id">R140_E0012</data><data key="edge_relationship_type">writes_wages_page_of</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Policy references SSI Claims system Wages page; CCE is SSI claims system, not a universal MEF update.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0026" source="R140_E0012" target="R140_E0013"><data key="edge_relationship_id">R140_R0026</data><data key="edge_source_entity_id">R140_E0012</data><data key="edge_relationship_type">is_subject_to</data><data key="edge_target_entity_id">R140_E0013</data><data key="edge_operational_context">Monthly updates generally before Goldberg-Kelly notice cutoff.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0027" source="R140_E0011" target="SVC_TWN"><data key="edge_relationship_id">R140_R0027</data><data key="edge_source_entity_id">R140_E0011</data><data key="edge_relationship_type">also_uses_approved_verifier</data><data key="edge_target_entity_id">SVC_TWN</data><data key="edge_operational_context">TWN provides wage data also supplied by current PIE payroll provider; historical TWN use where PIE period incomplete.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0028" source="R140_E0011" target="R140_E0014"><data key="edge_relationship_id">R140_R0028</data><data key="edge_source_entity_id">R140_E0011</data><data key="edge_relationship_type">classifies_as_secondary</data><data key="edge_target_entity_id">R140_E0014</data><data key="edge_operational_context">Query evidence from NDNH/MEF/state/iTOPSS requires documentation and monthly interpretation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0029" source="R140_E0014" target="SYS_MEF"><data key="edge_relationship_id">R140_R0029</data><data key="edge_source_entity_id">R140_E0014</data><data key="edge_relationship_type">includes_official_earnings_record</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">MEF/W-2 secondary when monthly primary wage evidence unavailable.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0030" source="R140_E0014" target="EX_PIE"><data key="edge_relationship_id">R140_R0030</data><data key="edge_source_entity_id">R140_E0014</data><data key="edge_relationship_type">does_not_replace</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">PIE is listed above these secondary sources in the procedure.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0031" source="R140_E0015" target="APP_CCE"><data key="edge_relationship_id">R140_R0031</data><data key="edge_source_entity_id">R140_E0015</data><data key="edge_relationship_type">restricts_personal_data_disclosure_from</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Employees cannot submit SSI claimant PII to non-approved wage verifier sites.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0032" source="R140_E0016" target="SYS_SSR"><data key="edge_relationship_id">R140_R0032</data><data key="edge_source_entity_id">R140_E0016</data><data key="edge_relationship_type">is_reflected_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Wage evidence status and verification codes are on SSR.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0033" source="ORG_CMS" target="R140_E0017"><data key="edge_relationship_id">R140_R0033</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">reinstates_plans_after</data><data key="edge_target_entity_id">R140_E0017</data><data key="edge_operational_context">CMS restores Part C/D plan enrollment after SSA provides corrected records/referral.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0034" source="R140_E0017" target="R140_E0018"><data key="edge_relationship_id">R140_R0034</data><data key="edge_source_entity_id">R140_E0017</data><data key="edge_relationship_type">requires_prerequisite</data><data key="edge_target_entity_id">R140_E0018</data><data key="edge_operational_context">SSA record and Part A/B or Title II restoration precedes CMS reinstatement request.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0035" source="R140_E0018" target="SYS_MBR"><data key="edge_relationship_id">R140_R0035</data><data key="edge_source_entity_id">R140_E0018</data><data key="edge_relationship_type">involves_master_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Reinstatement case needs authoritative SSA death/benefit record correction; no universal auto update asserted.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0036" source="R140_E0017" target="APP_MAPS"><data key="edge_relationship_id">R140_R0036</data><data key="edge_source_entity_id">R140_E0017</data><data key="edge_relationship_type">uses_investigation_tool</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">MAPS and MBR can be queried to confirm recent Part C/D information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0037" source="APP_MAPS" target="R140_E0019"><data key="edge_relationship_id">R140_R0037</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_scope_limitation</data><data key="edge_target_entity_id">R140_E0019</data><data key="edge_operational_context">Some Part D coverage is invisible to MAPS in defined non-LIS/non-withholding cases.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0038" source="R140_E0017" target="APP_DIPS"><data key="edge_relationship_id">R140_R0038</data><data key="edge_source_entity_id">R140_E0017</data><data key="edge_relationship_type">may_require_death_record_correction</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">Death record correction is an SSA prerequisite; particular direct-input action depends on case.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0039" source="R140_E0017" target="R140_E0020"><data key="edge_relationship_id">R140_R0039</data><data key="edge_source_entity_id">R140_E0017</data><data key="edge_relationship_type">may_require_urgent</data><data key="edge_target_entity_id">R140_E0020</data><data key="edge_operational_context">Priority when essential medications not accessible.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0040" source="R140_E0020" target="R140_E0021"><data key="edge_relationship_id">R140_R0040</data><data key="edge_source_entity_id">R140_E0020</data><data key="edge_relationship_type">is_submitted_on</data><data key="edge_target_entity_id">R140_E0021</data><data key="edge_operational_context">Referral captures number of days of medication available.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0041" source="R140_E0017" target="R140_E0022"><data key="edge_relationship_id">R140_R0041</data><data key="edge_source_entity_id">R140_E0017</data><data key="edge_relationship_type">is_governed_by</data><data key="edge_target_entity_id">R140_E0022</data><data key="edge_operational_context">Authorization is role-specific.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0042" source="R140_E0021" target="ORG_CMS"><data key="edge_relationship_id">R140_R0042</data><data key="edge_source_entity_id">R140_E0021</data><data key="edge_relationship_type">is_sent_for_action_to</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS coordinates prioritization with MA and PDP companies and responds by email.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0043" source="R140_E0023" target="APP_POS"><data key="edge_relationship_id">R140_R0043</data><data key="edge_source_entity_id">R140_E0023</data><data key="edge_relationship_type">determines_mbr_correction_via</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Direct update in POS considered before manual CMS-2178-U2 referrals.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0044" source="R140_E0023" target="SYS_MBR"><data key="edge_relationship_id">R140_R0044</data><data key="edge_source_entity_id">R140_E0023</data><data key="edge_relationship_type">separates_update_targets</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR and HI master may differ; refer to PC if SSA record wrong and direct input unsuccessful.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0045" source="R140_E0023" target="ORG_CMS"><data key="edge_relationship_id">R140_R0045</data><data key="edge_source_entity_id">R140_E0023</data><data key="edge_relationship_type">otherwise_routes_cms_only_to</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">HI-only discrepancy goes to CMS via email with form CMS-2178-U2.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0046" source="R140_E0023" target="R140_E0024"><data key="edge_relationship_id">R140_R0046</data><data key="edge_source_entity_id">R140_E0023</data><data key="edge_relationship_type">has_followup_rule</data><data key="edge_target_entity_id">R140_E0024</data><data key="edge_operational_context">30 working day controls and 90 calendar day escalation for unresolved problems.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0047" source="DB_SSI_IRS_INTERFACE" target="R140_E0025"><data key="edge_relationship_id">R140_R0047</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">contains_tax_match_role_data</data><data key="edge_target_entity_id">R140_E0025</data><data key="edge_operational_context">Role-specific payer/payee/taxpayer naming; no assumption that reported address is current residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0048" source="DB_SSI_IRS_INTERFACE" target="R140_E0026"><data key="edge_relationship_id">R140_R0048</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">has_restricted_data_classification</data><data key="edge_target_entity_id">R140_E0026</data><data key="edge_operational_context">Tax-data safeguard applies to alert content after development.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0049" source="R140_E0025" target="SYS_MBR"><data key="edge_relationship_id">R140_R0049</data><data key="edge_source_entity_id">R140_E0025</data><data key="edge_relationship_type">is_not_an_automatic_change_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">An alert is an investigative lead, not verified MBR residence information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0050" source="R140_E0026" target="SYS_SSR"><data key="edge_relationship_id">R140_R0050</data><data key="edge_source_entity_id">R140_E0026</data><data key="edge_relationship_type">does_not_authorize_update_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">IRS alert requires development; authorized data access alone does not prove SSR update.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0051" source="R140_E0027" target="SYS_SSI_EARN_ALERT"><data key="edge_relationship_id">R140_R0051</data><data key="edge_source_entity_id">R140_E0027</data><data key="edge_relationship_type">reviews_controls_of</data><data key="edge_target_entity_id">SYS_SSI_EARN_ALERT</data><data key="edge_operational_context">OIG evaluated resolution of earnings alert work, not verification that each alert represents misconduct.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0052" source="R140_E0027" target="R140_E0028"><data key="edge_relationship_id">R140_R0052</data><data key="edge_source_entity_id">R140_E0027</data><data key="edge_relationship_type">documents_failure_modes</data><data key="edge_target_entity_id">R140_E0028</data><data key="edge_operational_context">63 unresolved and 17 inadequately developed from sampled 100.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0053" source="R140_E0027" target="R140_E0029"><data key="edge_relationship_id">R140_R0053</data><data key="edge_source_entity_id">R140_E0027</data><data key="edge_relationship_type">estimates_recovery_limitations</data><data key="edge_target_entity_id">R140_E0029</data><data key="edge_operational_context">Statistical extrapolation includes administrative finality effects; not actual booked recoveries.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0054" source="R140_E0028" target="SYS_SSR"><data key="edge_relationship_id">R140_R0054</data><data key="edge_source_entity_id">R140_E0028</data><data key="edge_relationship_type">is_related_to_income_record_verification</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Alert development requires correctly posting wages affecting SSI entitlement/payment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0055" source="DATA_SSI_AR_IVA1_POP" target="R140_E0030"><data key="edge_relationship_id">R140_R0055</data><data key="edge_source_entity_id">DATA_SSI_AR_IVA1_POP</data><data key="edge_relationship_type">uses_observation_date_basis</data><data key="edge_target_entity_id">R140_E0030</data><data key="edge_operational_context">Table IV.A1 is July 1 population point estimate; not start- or end-year.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0056" source="DATA_SSI_AR_IVA2_FBR" target="R140_E0031"><data key="edge_relationship_id">R140_R0056</data><data key="edge_source_entity_id">DATA_SSI_AR_IVA2_FBR</data><data key="edge_relationship_type">follows_adjustment_assumptions</data><data key="edge_target_entity_id">R140_E0031</data><data key="edge_operational_context">SSI FBR January COLA on Trustees intermediate projection basis.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0057" source="REPORT_SSI_ANNUAL_2026" target="R140_E0031"><data key="edge_relationship_id">R140_R0057</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">publishes_statistical_assumption</data><data key="edge_target_entity_id">R140_E0031</data><data key="edge_operational_context">Projected policy rates are not observed values.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0058" source="SVC_GRANTSOLUTIONS" target="R140_E0032"><data key="edge_relationship_id">R140_R0058</data><data key="edge_source_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_relationship_type">delivers_award_notification_for</data><data key="edge_target_entity_id">R140_E0032</data><data key="edge_operational_context">Official SSA grants workflow uses GrantSolutions for electronic award notices, not evidence of SSA-hosted database.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R140_R0059" source="SVC_GRANTS_GOV" target="R140_E0032"><data key="edge_relationship_id">R140_R0059</data><data key="edge_source_entity_id">SVC_GRANTS_GOV</data><data key="edge_relationship_type">accepts_competitive_applications_prior_to</data><data key="edge_target_entity_id">R140_E0032</data><data key="edge_operational_context">Grants.gov is application intake and GrantSolutions subsequent award notification under public instruction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Documented association, not proof of automatic integration unless directly stated.</data></edge><edge id="R141_R0001" source="APP_UPLOAD_DOCUMENTS" target="R130_E008"><data key="edge_relationship_id">R141_R0001</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">appends_to_submitted_pdf</data><data key="edge_target_entity_id">R130_E008</data><data key="edge_operational_context">Electronic signature data page accompanies signed PDF after submission.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0002" source="APP_UPLOAD_DOCUMENTS" target="R141_E003"><data key="edge_relationship_id">R141_R0002</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">uses_signature_control</data><data key="edge_target_entity_id">R141_E003</data><data key="edge_operational_context">Authenticated customer checks required electronic signature box and clicks Submit.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0003" source="R141_E003" target="R130_E008"><data key="edge_relationship_id">R141_R0003</data><data key="edge_source_entity_id">R141_E003</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R130_E008</data><data key="edge_operational_context">Electronic signature page is appended to PDF as evidence of signature acceptance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0004" source="APP_UPLOAD_DOCUMENTS" target="R141_E002"><data key="edge_relationship_id">R141_R0004</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">requires_technician_process</data><data key="edge_target_entity_id">R141_E002</data><data key="edge_operational_context">Form signed online still processed as a paper application.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0005" source="R141_E002" target="APP_MCS"><data key="edge_relationship_id">R141_R0005</data><data key="edge_source_entity_id">R141_E002</data><data key="edge_relationship_type">requires_manual_entry_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Technician reviews submitted form and loads benefit application into MCS, not automatic upload-to-master posting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0006" source="R141_E002" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R141_R0006</data><data key="edge_source_entity_id">R141_E002</data><data key="edge_relationship_type">requires_manual_entry_in</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Technician enters benefit application in CCE when appropriate; no automatic intake synchronization presumed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0007" source="R141_E002" target="R141_E004"><data key="edge_relationship_id">R141_R0007</data><data key="edge_source_entity_id">R141_E002</data><data key="edge_relationship_type">uses_signature_method_note</data><data key="edge_target_entity_id">R141_E004</data><data key="edge_operational_context">ATTEST issue can represent Upload Documents method only with accurate remarks.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0008" source="R141_E004" target="UI_MCS_DW01"><data key="edge_relationship_id">R141_R0008</data><data key="edge_source_entity_id">R141_E004</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">UI_MCS_DW01</data><data key="edge_operational_context">ATTEST appears on DW01 and technician annotates true method.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0009" source="R141_E004" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R141_R0009</data><data key="edge_source_entity_id">R141_E004</data><data key="edge_relationship_type">documents_true_method_for</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Remark upload docs distinguishes signer channel from actual worker attestation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0010" source="R141_E005" target="R141_E006"><data key="edge_relationship_id">R141_R0010</data><data key="edge_source_entity_id">R141_E005</data><data key="edge_relationship_type">accepted_as_evidence_for</data><data key="edge_target_entity_id">R141_E006</data><data key="edge_operational_context">CPAS date, time and signer name are reviewed for signature acceptance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0011" source="R141_E006" target="R141_E004"><data key="edge_relationship_id">R141_R0011</data><data key="edge_source_entity_id">R141_E006</data><data key="edge_relationship_type">records_method_on</data><data key="edge_target_entity_id">R141_E004</data><data key="edge_operational_context">CPAS must be remarked as CPAS even when ATTEST issue propagated automatically.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0012" source="R141_E006" target="APP_MCS"><data key="edge_relationship_id">R141_R0012</data><data key="edge_source_entity_id">R141_E006</data><data key="edge_relationship_type">loads_case_to</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">CPAS benefit forms manually entered into MCS where applicable.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0013" source="R141_E006" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R141_R0013</data><data key="edge_source_entity_id">R141_E006</data><data key="edge_relationship_type">loads_case_to</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">CPAS benefit forms manually entered into CCE where applicable.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0014" source="APP_EDCS" target="R141_E007"><data key="edge_relationship_id">R141_R0014</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_conditional_case_creation</data><data key="edge_target_entity_id">R141_E007</data><data key="edge_operational_context">EDCS allows manual Title XVI claims where CCE/MSSICS exclusion applies.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0015" source="R141_E007" target="R141_E008"><data key="edge_relationship_id">R141_R0015</data><data key="edge_source_entity_id">R141_E007</data><data key="edge_relationship_type">collects_information_via</data><data key="edge_target_entity_id">R141_E008</data><data key="edge_operational_context">Manually Created T16 Information screen captures required case details.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0016" source="R141_E007" target="R141_E011"><data key="edge_relationship_id">R141_R0016</data><data key="edge_source_entity_id">R141_E007</data><data key="edge_relationship_type">records_exclusion_provenance_using</data><data key="edge_target_entity_id">R141_E011</data><data key="edge_operational_context">Reason dropdown records why claim could not enter EDCS electronically.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0017" source="R141_E007" target="R141_E009"><data key="edge_relationship_id">R141_R0017</data><data key="edge_source_entity_id">R141_E007</data><data key="edge_relationship_type">prohibited_for</data><data key="edge_target_entity_id">R141_E009</data><data key="edge_operational_context">Manual Title XVI is prohibited for CDR initial/appeal and age-18 redetermination CDR.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0018" source="R141_E010" target="R141_E007"><data key="edge_relationship_id">R141_R0018</data><data key="edge_source_entity_id">R141_E010</data><data key="edge_relationship_type">uses_case_entry_path</data><data key="edge_target_entity_id">R141_E007</data><data key="edge_operational_context">Concurrent Title XVI allowance and Title II denial requires manual T16 for certain ALJ hearings.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0019" source="R141_E012" target="REPO_CEF"><data key="edge_relationship_id">R141_R0019</data><data key="edge_source_entity_id">R141_E012</data><data key="edge_relationship_type">conditions_official_folder_status_for</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Where EDCS exclusion results in partial-electronic folder, paper remains official.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0020" source="APP_EDCS" target="R141_E012"><data key="edge_relationship_id">R141_R0020</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_hybrid_case_record_rule</data><data key="edge_target_entity_id">R141_E012</data><data key="edge_operational_context">EDCS permits electronic development even where official record is paper.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0021" source="UTIL_EDCS_COPY_FROM_PRIOR" target="R141_E013"><data key="edge_relationship_id">R141_R0021</data><data key="edge_source_entity_id">UTIL_EDCS_COPY_FROM_PRIOR</data><data key="edge_relationship_type">can_propagate</data><data key="edge_target_entity_id">R141_E013</data><data key="edge_operational_context">Selected medical-source contact details copy from closed prior EDCS case.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0022" source="R141_E014" target="R141_E013"><data key="edge_relationship_id">R141_R0022</data><data key="edge_source_entity_id">R141_E014</data><data key="edge_relationship_type">validates_stale_attributes_from</data><data key="edge_target_entity_id">R141_E013</data><data key="edge_operational_context">Address and contact details require review when carrying forward.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0023" source="UTIL_EDCS_COPY_FROM_PRIOR" target="R141_E015"><data key="edge_relationship_id">R141_R0023</data><data key="edge_source_entity_id">UTIL_EDCS_COPY_FROM_PRIOR</data><data key="edge_relationship_type">preserves_original_as</data><data key="edge_target_entity_id">R141_E015</data><data key="edge_operational_context">Prior EDCS record remains intact and available for subsequent copying.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0024" source="R141_E015" target="R141_E013"><data key="edge_relationship_id">R141_R0024</data><data key="edge_source_entity_id">R141_E015</data><data key="edge_relationship_type">applies_to_copy_of</data><data key="edge_target_entity_id">R141_E013</data><data key="edge_operational_context">Copied source details can be updated in new case but old source record remains.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0025" source="R141_E024" target="R141_E013"><data key="edge_relationship_id">R141_R0025</data><data key="edge_source_entity_id">R141_E024</data><data key="edge_relationship_type">qualifies_meaning_of</data><data key="edge_target_entity_id">R141_E013</data><data key="edge_operational_context">EDCS medical-source mailing address is not the claimants residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0026" source="R141_E024" target="R141_E014"><data key="edge_relationship_id">R141_R0026</data><data key="edge_source_entity_id">R141_E024</data><data key="edge_relationship_type">constrains_reuse_process</data><data key="edge_target_entity_id">R141_E014</data><data key="edge_operational_context">Review source contact address rather than treating as verified person location.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC364; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0027" source="APP_ECO" target="R141_E016"><data key="edge_relationship_id">R141_R0027</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">implements_conditional_address_retry</data><data key="edge_target_entity_id">R141_E016</data><data key="edge_operational_context">Lack of AVC address and stale MBR/SSR data triggers later AVC query.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC220; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0028" source="R141_E016" target="SVC_AVC"><data key="edge_relationship_id">R141_R0028</data><data key="edge_source_entity_id">R141_E016</data><data key="edge_relationship_type">rechecks_service</data><data key="edge_target_entity_id">SVC_AVC</data><data key="edge_operational_context">Next address lookup occurs approximately six months later under conditions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC220; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0029" source="R141_E016" target="SYS_MBR"><data key="edge_relationship_id">R141_R0029</data><data key="edge_source_entity_id">R141_E016</data><data key="edge_relationship_type">assesses_recency_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II master address updated within last year is permitted fallback.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC220; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0030" source="R141_E016" target="SYS_SSR"><data key="edge_relationship_id">R141_R0030</data><data key="edge_source_entity_id">R141_E016</data><data key="edge_relationship_type">assesses_recency_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI master address updated within last year is permitted fallback.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC220; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0031" source="APP_ECO" target="R141_E017"><data key="edge_relationship_id">R141_R0031</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">observes_address_request_boundary</data><data key="edge_target_entity_id">R141_E017</data><data key="edge_operational_context">Automated debt address request separate from DMS manual address search.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC220; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0032" source="R141_E017" target="APP_DMS"><data key="edge_relationship_id">R141_R0032</data><data key="edge_source_entity_id">R141_E017</data><data key="edge_relationship_type">distinguishes</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Automated AVC workflow and DMS requests are independent per POMS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC220; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0033" source="R141_E018" target="R141_E021"><data key="edge_relationship_id">R141_R0033</data><data key="edge_source_entity_id">R141_E018</data><data key="edge_relationship_type">governs_signature_on</data><data key="edge_target_entity_id">R141_E021</data><data key="edge_operational_context">Eligible couple signs in separate recipient and spouse spaces.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source R141_S001; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0034" source="R141_E019" target="R141_E021"><data key="edge_relationship_id">R141_R0034</data><data key="edge_source_entity_id">R141_E019</data><data key="edge_relationship_type">governs_signature_on</data><data key="edge_target_entity_id">R141_E021</data><data key="edge_operational_context">Witness rules for recipient making signature by mark.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source R141_S001; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0035" source="R141_E020" target="R141_E021"><data key="edge_relationship_id">R141_R0035</data><data key="edge_source_entity_id">R141_E020</data><data key="edge_relationship_type">governs_signature_on</data><data key="edge_target_entity_id">R141_E021</data><data key="edge_operational_context">Payee signature on behalf of incapable recipient subject to exceptions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source R141_S001; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0036" source="R141_E021" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R141_R0036</data><data key="edge_source_entity_id">R141_E021</data><data key="edge_relationship_type">generated_as_printout_by</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">SSA-8203-BK is SSI Claims redetermination printout.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source R141_S001; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0037" source="R141_E021" target="FORM_SSA8203BK"><data key="edge_relationship_id">R141_R0037</data><data key="edge_source_entity_id">R141_E021</data><data key="edge_relationship_type">implements_form_structure_for</data><data key="edge_target_entity_id">FORM_SSA8203BK</data><data key="edge_operational_context">Signature layout corresponds to SSA-8203-BK.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source R141_S001; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0038" source="APP_ICLAIM" target="R141_E022"><data key="edge_relationship_id">R141_R0038</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">enforces_authenticated_case_handling</data><data key="edge_target_entity_id">R141_E022</data><data key="edge_operational_context">Unverified identity requires contact; verified first party not recontacted solely for identity.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0039" source="APP_ICLAIM" target="R141_E023"><data key="edge_relationship_id">R141_R0039</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">retains_submitted_snapshot_as</data><data key="edge_target_entity_id">R141_E023</data><data key="edge_operational_context">After downloaded to MCS, original online application summary posts to ORS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0040" source="R141_E023" target="APP_ORS"><data key="edge_relationship_id">R141_R0040</data><data key="edge_source_entity_id">R141_E023</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">ORS stores copy of summary as submitted online after MCS download.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R141_R0041" source="APP_MCS" target="R141_E023"><data key="edge_relationship_id">R141_R0041</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">receives_claim_information_from</data><data key="edge_target_entity_id">R141_E023</data><data key="edge_operational_context">Submitted original source precedes employee adjudication and may differ.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source SRC_R38_003; conditional relationship, no assumed universal update path.</data></edge><edge id="R142_R0001" source="FORM_SSA11BK" target="R142_E001"><data key="edge_relationship_id">R142_R0001</data><data key="edge_source_entity_id">FORM_SSA11BK</data><data key="edge_relationship_type">requires_followup_interview_as_lead</data><data key="edge_target_entity_id">R142_E001</data><data key="edge_operational_context">SSA-11 submitted by mail, fax or drop box is not by itself an approved payee appointment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0002" source="R142_E001" target="APP_ERPS"><data key="edge_relationship_id">R142_R0002</data><data key="edge_source_entity_id">R142_E001</data><data key="edge_relationship_type">requires_case_interview_record</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Technician must interview applicant, verify applicant and enter information into eRPS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0003" source="R142_E001" target="DATA_ERPS_REP_PAYEE_APPLICANT_NOTE"><data key="edge_relationship_id">R142_R0003</data><data key="edge_source_entity_id">R142_E001</data><data key="edge_relationship_type">is_documented_on</data><data key="edge_target_entity_id">DATA_ERPS_REP_PAYEE_APPLICANT_NOTE</data><data key="edge_operational_context">Document receipt of SSA-11 as a lead in eRPS note type.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0004" source="R142_E002" target="SYS_NUMIDENT"><data key="edge_relationship_id">R142_R0004</data><data key="edge_source_entity_id">R142_E002</data><data key="edge_relationship_type">uses_authoritative_ssn_identity_record</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Remote individual identity is confirmed against Numident information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0005" source="R142_E002" target="UI_ERPS_SSA11_INTRO"><data key="edge_relationship_id">R142_R0005</data><data key="edge_source_entity_id">R142_E002</data><data key="edge_relationship_type">records_interview_method_on</data><data key="edge_target_entity_id">UI_ERPS_SSA11_INTRO</data><data key="edge_operational_context">Record by-phone or by-video on eRPS application introduction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0006" source="R142_E002" target="APP_ERPS"><data key="edge_relationship_id">R142_R0006</data><data key="edge_source_entity_id">R142_E002</data><data key="edge_relationship_type">supports_payee_appointment_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Eligible remote interview provides required verified applicant identity for eRPS selection path.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0007" source="R142_E003" target="APP_ERPS"><data key="edge_relationship_id">R142_R0007</data><data key="edge_source_entity_id">R142_E003</data><data key="edge_relationship_type">records_organizational_details_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Verify organizational name, EIN, address and staff role before appointment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0008" source="R142_E003" target="DATA_ERPS_REP_PAYEE_APPLICANT_NOTE"><data key="edge_relationship_id">R142_R0008</data><data key="edge_source_entity_id">R142_E003</data><data key="edge_relationship_type">records_human_agent_roles_in</data><data key="edge_target_entity_id">DATA_ERPS_REP_PAYEE_APPLICANT_NOTE</data><data key="edge_operational_context">Document organizational employee name/title and funds manager in eRPS note.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0009" source="R142_E003" target="DATA_ERPS_CONTACT_ADDRESS"><data key="edge_relationship_id">R142_R0009</data><data key="edge_source_entity_id">R142_E003</data><data key="edge_relationship_type">distinguishes_business_contact_from</data><data key="edge_target_entity_id">DATA_ERPS_CONTACT_ADDRESS</data><data key="edge_operational_context">Organizational payee business address is not established as beneficiary residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0010" source="R142_E004" target="R142_E002"><data key="edge_relationship_id">R142_R0010</data><data key="edge_source_entity_id">R142_E004</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R142_E002</data><data key="edge_operational_context">Numident-confirmed telephone or approved video identity is allowable only under exceptions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0011" source="R142_E004" target="R142_E009"><data key="edge_relationship_id">R142_R0011</data><data key="edge_source_entity_id">R142_E004</data><data key="edge_relationship_type">requires_face_to_face_for</data><data key="edge_target_entity_id">R142_E009</data><data key="edge_operational_context">U.S. resident payee applicant without SSN requires face-to-face interview even where no eRPS record is established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0012" source="R142_E005" target="PROC_ERPS_CRIMINAL_BG"><data key="edge_relationship_id">R142_R0012</data><data key="edge_source_entity_id">R142_E005</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">PROC_ERPS_CRIMINAL_BG</data><data key="edge_operational_context">Eligible applicants must consent before eRPS criminal background check.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0013" source="R142_E005" target="DATA_ERPS_REP_PAYEE_APPLICANT_NOTE"><data key="edge_relationship_id">R142_R0013</data><data key="edge_source_entity_id">R142_E005</data><data key="edge_relationship_type">records_decision_in</data><data key="edge_target_entity_id">DATA_ERPS_REP_PAYEE_APPLICANT_NOTE</data><data key="edge_operational_context">Document refused screening and nonselection rationale in eRPS note.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0014" source="R142_E005" target="UI_ERPS_BG_PERMISSION"><data key="edge_relationship_id">R142_R0014</data><data key="edge_source_entity_id">R142_E005</data><data key="edge_relationship_type">uses_permission_screen</data><data key="edge_target_entity_id">UI_ERPS_BG_PERMISSION</data><data key="edge_operational_context">Permission for Background Check eRPS screen precedes criminal history request.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0015" source="R142_E006" target="PROC_ERPS_CRIMINAL_BG"><data key="edge_relationship_id">R142_R0015</data><data key="edge_source_entity_id">R142_E006</data><data key="edge_relationship_type">exempts_from</data><data key="edge_target_entity_id">PROC_ERPS_CRIMINAL_BG</data><data key="edge_operational_context">Named custodial relatives and guardians must not be subject to screening request under the rule.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0016" source="R142_E007" target="APP_PUPS"><data key="edge_relationship_id">R142_R0016</data><data key="edge_source_entity_id">R142_E007</data><data key="edge_relationship_type">qualifies_interpretation_of</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Prisoner history alone cannot identify statutory barred offense.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0017" source="R142_E007" target="APP_ERPS"><data key="edge_relationship_id">R142_R0017</data><data key="edge_source_entity_id">R142_E007</data><data key="edge_relationship_type">requires_crime_detail_development_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Workers review background results and document statutory bar separately.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0018" source="R142_E008" target="APP_ERPS"><data key="edge_relationship_id">R142_R0018</data><data key="edge_source_entity_id">R142_E008</data><data key="edge_relationship_type">records_incomplete_status_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Non-select Incomplete if applicant leaves before attesting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0019" source="R142_E008" target="DATA_ERPS_REP_PAYEE_APPLICANT_NOTE"><data key="edge_relationship_id">R142_R0019</data><data key="edge_source_entity_id">R142_E008</data><data key="edge_relationship_type">documents_interview_in</data><data key="edge_target_entity_id">DATA_ERPS_REP_PAYEE_APPLICANT_NOTE</data><data key="edge_operational_context">Documents interview circumstances and any background findings.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0020" source="R142_E009" target="FORM_SSA5002"><data key="edge_relationship_id">R142_R0020</data><data key="edge_source_entity_id">R142_E009</data><data key="edge_relationship_type">creates_form</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">SSA-5002 Report of Contact documents the result where no eRPS record is created.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0021" source="R142_E009" target="APP_EVIEW"><data key="edge_relationship_id">R142_R0021</data><data key="edge_source_entity_id">R142_E009</data><data key="edge_relationship_type">can_retain_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Document may be filed in eView.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0022" source="R142_E009" target="REPO_NDRED"><data key="edge_relationship_id">R142_R0022</data><data key="edge_source_entity_id">R142_E009</data><data key="edge_relationship_type">can_retain_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Document may be retained in non-disability evidentiary repository.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0023" source="R142_E010" target="DATA_ERPS_REP_PAYEE_APPLICANT_NOTE"><data key="edge_relationship_id">R142_R0023</data><data key="edge_source_entity_id">R142_E010</data><data key="edge_relationship_type">stored_as</data><data key="edge_target_entity_id">DATA_ERPS_REP_PAYEE_APPLICANT_NOTE</data><data key="edge_operational_context">eRPS note stores interview reason, date and suitability determinations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R131_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0024" source="R142_E011" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R142_R0024</data><data key="edge_source_entity_id">R142_E011</data><data key="edge_relationship_type">governs_fo_redeterminations_in</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">FO redetermination event triggers request for financial-institution contact permission.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0025" source="R142_E012" target="R142_E013"><data key="edge_relationship_id">R142_R0025</data><data key="edge_source_entity_id">R142_E012</data><data key="edge_relationship_type">used_as_lead_by</data><data key="edge_target_entity_id">R142_E013</data><data key="edge_operational_context">IRS informational alert may lead to asset development but is not conclusive resource verification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0026" source="R142_E013" target="SYS_SSR"><data key="edge_relationship_id">R142_R0026</data><data key="edge_source_entity_id">R142_E013</data><data key="edge_relationship_type">triggered_by_direct_deposit_indicator_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR direct-deposit indicator triggers financial-account resource inquiry.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0027" source="R142_E013" target="SYS_MBR"><data key="edge_relationship_id">R142_R0027</data><data key="edge_source_entity_id">R142_E013</data><data key="edge_relationship_type">also_triggered_by_direct_deposit_indicator_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR direct-deposit indicator triggers separate eligibility/resource inquiry.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0028" source="R142_E013" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">R142_R0028</data><data key="edge_source_entity_id">R142_E013</data><data key="edge_relationship_type">documents_verified_data_in</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">CCE Financial Accounts captures the relevant direct deposit account and its resource status.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0029" source="R142_E014" target="R142_E013"><data key="edge_relationship_id">R142_R0029</data><data key="edge_source_entity_id">R142_E014</data><data key="edge_relationship_type">constrains_resource_valuation_for</data><data key="edge_target_entity_id">R142_E013</data><data key="edge_operational_context">Liquid-resource evaluation uses bank evidence for first-of-month balance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0030" source="R142_E015" target="R142_E013"><data key="edge_relationship_id">R142_R0030</data><data key="edge_source_entity_id">R142_E015</data><data key="edge_relationship_type">collected_for</data><data key="edge_target_entity_id">R142_E013</data><data key="edge_operational_context">Bank/company address identifies a financial institution during asset inquiry.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0031" source="R142_E015" target="SYS_SSR"><data key="edge_relationship_id">R142_R0031</data><data key="edge_source_entity_id">R142_E015</data><data key="edge_relationship_type">not_proof_of_beneficiary_address_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Account-owning bank address is not verified recipient residential address and does not imply SSR address change.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0032" source="R142_E016" target="R142_E014"><data key="edge_relationship_id">R142_R0032</data><data key="edge_source_entity_id">R142_E016</data><data key="edge_relationship_type">adjusts</data><data key="edge_target_entity_id">R142_E014</data><data key="edge_operational_context">Advance SSI payment should not be counted as first-of-month resources for the ensuing month merely due to early delivery.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0033" source="R142_E012" target="SYS_SSR"><data key="edge_relationship_id">R142_R0033</data><data key="edge_source_entity_id">R142_E012</data><data key="edge_relationship_type">does_not_automatically_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">IRS informational resource alert requires development; no auto-update of beneficiary program address established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC_R100_005; no unstated automatic synchronization.</data></edge><edge id="R142_R0034" source="DB_REP_DISQUAL_SOR" target="R142_E017"><data key="edge_relationship_id">R142_R0034</data><data key="edge_source_entity_id">DB_REP_DISQUAL_SOR</data><data key="edge_relationship_type">maintains_representative_contact_attributes</data><data key="edge_target_entity_id">R142_E017</data><data key="edge_operational_context">Records include representative home/business address, contact numbers, email and ID.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC445; no unstated automatic synchronization.</data></edge><edge id="R142_R0035" source="DB_REP_DISQUAL_SOR" target="R142_E018"><data key="edge_relationship_id">R142_R0035</data><data key="edge_source_entity_id">DB_REP_DISQUAL_SOR</data><data key="edge_relationship_type">maintains_professional_evidence</data><data key="edge_target_entity_id">R142_E018</data><data key="edge_operational_context">Records include bar standing and investigation information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC445; no unstated automatic synchronization.</data></edge><edge id="R142_R0036" source="R142_E017" target="DB_REP_DISQUAL_SOR"><data key="edge_relationship_id">R142_R0036</data><data key="edge_source_entity_id">R142_E017</data><data key="edge_relationship_type">applies_to_disqualified_rep_record_in</data><data key="edge_target_entity_id">DB_REP_DISQUAL_SOR</data><data key="edge_operational_context">These addresses identify a representative, not beneficiary residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC445; no unstated automatic synchronization.</data></edge><edge id="R142_R0037" source="R142_E018" target="APP_REP_CONDUCT_CLAIMS"><data key="edge_relationship_id">R142_R0037</data><data key="edge_source_entity_id">R142_E018</data><data key="edge_relationship_type">is_recorded_in</data><data key="edge_target_entity_id">APP_REP_CONDUCT_CLAIMS</data><data key="edge_operational_context">2021 PIA expressly identifies Representative Conduct Claims as a repository for sanctioned representative information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: SRC445; no unstated automatic synchronization.</data></edge><edge id="R142_R0038" source="DATA_AWI_SERIES" target="R142_E019"><data key="edge_relationship_id">R142_R0038</data><data key="edge_source_entity_id">DATA_AWI_SERIES</data><data key="edge_relationship_type">publishes_2024_factor_used_for</data><data key="edge_target_entity_id">R142_E019</data><data key="edge_operational_context">2024 AWI is 69,846.57 and governs 2026 eligibility-year past-earnings wage indexing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S003; no unstated automatic synchronization.</data></edge><edge id="R142_R0039" source="R142_E019" target="R142_E022"><data key="edge_relationship_id">R142_R0039</data><data key="edge_source_entity_id">R142_E019</data><data key="edge_relationship_type">feeds_calculation_of</data><data key="edge_target_entity_id">R142_E022</data><data key="edge_operational_context">Historical covered earnings are indexed before AIME highest-years computation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S002; no unstated automatic synchronization.</data></edge><edge id="R142_R0040" source="R142_E022" target="R142_E020"><data key="edge_relationship_id">R142_R0040</data><data key="edge_source_entity_id">R142_E022</data><data key="edge_relationship_type">yields_inputs_to</data><data key="edge_target_entity_id">R142_E020</data><data key="edge_operational_context">PIA formula applies to computed AIME, subject to yearly bend-point table.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S002; no unstated automatic synchronization.</data></edge><edge id="R142_R0041" source="R142_E020" target="R126_E012"><data key="edge_relationship_id">R142_R0041</data><data key="edge_source_entity_id">R142_E020</data><data key="edge_relationship_type">supports_disclosed_rule_for</data><data key="edge_target_entity_id">R126_E012</data><data key="edge_operational_context">2026 public calculator may use wage-indexed PIA formula parameters; this is a calculation-rule relationship, not established code deployment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S002; no unstated automatic synchronization.</data></edge><edge id="R142_R0042" source="R142_E021" target="R142_E022"><data key="edge_relationship_id">R142_R0042</data><data key="edge_source_entity_id">R142_E021</data><data key="edge_relationship_type">requires_user_provided_earnings_input_for</data><data key="edge_target_entity_id">R142_E022</data><data key="edge_operational_context">Online calculator documentation requires yearly covered earnings entry; same official benefit-method principles.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Validated direct policy/published data: R127_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0043" source="R127_E001" target="SYS_MEF"><data key="edge_relationship_id">R142_R0043</data><data key="edge_source_entity_id">R127_E001</data><data key="edge_relationship_type">does_not_query_personal_earnings_in</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Quick Calculator expressly states it does not access personal earnings record and estimates it from user input.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R127_S001; no unstated automatic synchronization.</data></edge><edge id="R142_R0044" source="SVC_I1020" target="R142_E023"><data key="edge_relationship_id">R142_R0044</data><data key="edge_source_entity_id">SVC_I1020</data><data key="edge_relationship_type">may_create_ssi_protective_filing_effect</data><data key="edge_target_entity_id">R142_E023</data><data key="edge_operational_context">Submission of Extra Help application provides SSI protective-filing rights.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S004; no unstated automatic synchronization.</data></edge><edge id="R142_R0045" source="R142_E023" target="EX_MSP_STATE_REFERRAL"><data key="edge_relationship_id">R142_R0045</data><data key="edge_source_entity_id">R142_E023</data><data key="edge_relationship_type">can_trigger_state_referral_via</data><data key="edge_target_entity_id">EX_MSP_STATE_REFERRAL</data><data key="edge_operational_context">Extra Help application information generally sent to state to initiate MSP application unless applicant opts out.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S004; no unstated automatic synchronization.</data></edge><edge id="R142_R0046" source="R142_E024" target="ORG_CMS"><data key="edge_relationship_id">R142_R0046</data><data key="edge_source_entity_id">R142_E024</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS selects Part D drug-plan enrollment for certain Extra Help approved nonenrollees.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S004; no unstated automatic synchronization.</data></edge><edge id="R142_R0047" source="PROC_EXTRA_HELP" target="R142_E024"><data key="edge_relationship_id">R142_R0047</data><data key="edge_source_entity_id">PROC_EXTRA_HELP</data><data key="edge_relationship_type">can_result_in_conditional_enrollment</data><data key="edge_target_entity_id">R142_E024</data><data key="edge_operational_context">Application approval does not itself guarantee plan enrollment; CMS handles plan selection where applicable.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S004; no unstated automatic synchronization.</data></edge><edge id="R142_R0048" source="R142_E025" target="PROC_EXTRA_HELP"><data key="edge_relationship_id">R142_R0048</data><data key="edge_source_entity_id">R142_E025</data><data key="edge_relationship_type">prompts_new_application_in</data><data key="edge_target_entity_id">PROC_EXTRA_HELP</data><data key="edge_operational_context">Lost-deemed-status beneficiaries may reapply for subsidy with future-year effective date.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S004; no unstated automatic synchronization.</data></edge><edge id="R142_R0049" source="R142_E025" target="ORG_CMS"><data key="edge_relationship_id">R142_R0049</data><data key="edge_source_entity_id">R142_E025</data><data key="edge_relationship_type">communicated_by</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS advises beneficiaries of deemed-status loss.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated direct policy/published data: R142_S004; no unstated automatic synchronization.</data></edge><edge id="R143_R0001" source="R143_E0001" target="R143_E0002"><data key="edge_relationship_id">R143_R0001</data><data key="edge_source_entity_id">R143_E0001</data><data key="edge_relationship_type">authorizes_with_consent</data><data key="edge_target_entity_id">R143_E0002</data><data key="edge_operational_context">An SSA-581 authorization, with valid consent, supports release of SSA-1826 itemized earnings to authorized requester.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0002" source="R143_E0005" target="R143_E0001"><data key="edge_relationship_id">R143_R0002</data><data key="edge_source_entity_id">R143_E0005</data><data key="edge_relationship_type">limits_validity_of</data><data key="edge_target_entity_id">R143_E0001</data><data key="edge_operational_context">SSA must receive the signed consent within 120 days of the individual signature under the cited IRS regulation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0003" source="R143_E0003" target="FORM_SSA1235"><data key="edge_relationship_id">R143_R0003</data><data key="edge_source_entity_id">R143_E0003</data><data key="edge_relationship_type">requires_signed_agreement_form</data><data key="edge_target_entity_id">FORM_SSA1235</data><data key="edge_operational_context">Reimbursable agreement uses SSA-1235 and a memorandum of agreement.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0004" source="R143_E0004" target="R143_E0003"><data key="edge_relationship_id">R143_R0004</data><data key="edge_source_entity_id">R143_E0004</data><data key="edge_relationship_type">reviews_reimbursable_agreement_requests</data><data key="edge_target_entity_id">R143_E0003</data><data key="edge_operational_context">Earnings Operations Support reviews written company-letterhead requests and negotiates agreements.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0005" source="R143_E0009" target="R143_E0001"><data key="edge_relationship_id">R143_R0005</data><data key="edge_source_entity_id">R143_E0009</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R143_E0001</data><data key="edge_operational_context">Each earnings disclosure requires an SSA-581 with appropriate consent or authority of person consenting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0006" source="R143_E0009" target="R143_E0003"><data key="edge_relationship_id">R143_R0006</data><data key="edge_source_entity_id">R143_E0009</data><data key="edge_relationship_type">operates_under</data><data key="edge_target_entity_id">R143_E0003</data><data key="edge_operational_context">Pension plan or legal organization may use a reimbursable agreement to obtain itemized earnings.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0007" source="R143_E0003" target="R143_E0007"><data key="edge_relationship_id">R143_R0007</data><data key="edge_source_entity_id">R143_E0003</data><data key="edge_relationship_type">enforces_fee_reconciliation</data><data key="edge_target_entity_id">R143_E0007</data><data key="edge_operational_context">Estimated costs paid in advance, quarterly accounting, refund or bill after fiscal-year reconciliation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0008" source="R143_E0002" target="R143_E0006"><data key="edge_relationship_id">R143_R0008</data><data key="edge_source_entity_id">R143_E0002</data><data key="edge_relationship_type">contains_reporting_employer_address</data><data key="edge_target_entity_id">R143_E0006</data><data key="edge_operational_context">SSA-1826 identifies employers and their addresses, not necessarily the wage earner current residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0009" source="R143_E0009" target="R143_E0008"><data key="edge_relationship_id">R143_R0009</data><data key="edge_source_entity_id">R143_E0009</data><data key="edge_relationship_type">provides_organization_address_for_intake</data><data key="edge_target_entity_id">R143_E0008</data><data key="edge_operational_context">Agreement request provides EIN and organizational and representative addresses.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0010" source="R143_E0003" target="R143_E0002"><data key="edge_relationship_id">R143_R0010</data><data key="edge_source_entity_id">R143_E0003</data><data key="edge_relationship_type">governs_release_of</data><data key="edge_target_entity_id">R143_E0002</data><data key="edge_operational_context">Itemized earnings made available to consenting third-party participants under reimbursable agreement.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S001. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0012" source="R143_E0010" target="R143_E0011"><data key="edge_relationship_id">R143_R0012</data><data key="edge_source_entity_id">R143_E0010</data><data key="edge_relationship_type">usage_observed_in</data><data key="edge_target_entity_id">R143_E0011</data><data key="edge_operational_context">Vendor monitors SSA calls to interpretation service for count, requested language, and duration.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0013" source="R143_E0011" target="R143_E0012"><data key="edge_relationship_id">R143_R0013</data><data key="edge_source_entity_id">R143_E0011</data><data key="edge_relationship_type">transmitted_in</data><data key="edge_target_entity_id">R143_E0012</data><data key="edge_operational_context">Vendor forwards usage information to SSA monthly.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0014" source="R143_E0012" target="R143_E0013"><data key="edge_relationship_id">R143_R0014</data><data key="edge_source_entity_id">R143_E0012</data><data key="edge_relationship_type">supports_annual_publication_of</data><data key="edge_target_entity_id">R143_E0013</data><data key="edge_operational_context">Official dataset is based on contracted vendor usage reporting; publication is annual by language.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0015" source="R143_E0013" target="R143_E0014"><data key="edge_relationship_id">R143_R0015</data><data key="edge_source_entity_id">R143_E0013</data><data key="edge_relationship_type">applies_small_cell_marking</data><data key="edge_target_entity_id">R143_E0014</data><data key="edge_operational_context">Counts fewer than three calls per language are marked by an asterisk.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0016" source="ORG_SSA_OAG" target="R143_E0010"><data key="edge_relationship_id">R143_R0016</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">contracts_for_service</data><data key="edge_target_entity_id">R143_E0010</data><data key="edge_operational_context">SSA identifies TIS as a contract awarded and administered by OAG.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0017" source="R143_E0015" target="DATA_DDS_STATE_MONTHLY_WORKLOAD"><data key="edge_relationship_id">R143_R0017</data><data key="edge_source_entity_id">R143_E0015</data><data key="edge_relationship_type">provides_operational_date_mapping_for</data><data key="edge_target_entity_id">DATA_DDS_STATE_MONTHLY_WORKLOAD</data><data key="edge_operational_context">SSA_DATES1 gives mapping of SSA week ending dates to SSA month, quarter and fiscal/calendar reporting periods.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S003. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0018" source="DATA_DDS_STATE_MONTHLY_WORKLOAD" target="R143_E0021"><data key="edge_relationship_id">R143_R0018</data><data key="edge_source_entity_id">DATA_DDS_STATE_MONTHLY_WORKLOAD</data><data key="edge_relationship_type">has_published_expanded_distribution</data><data key="edge_target_entity_id">R143_E0021</data><data key="edge_operational_context">Existing monthly public DDS workload dataset is distributed in 71-element CSV/XLS publication.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0019" source="R143_E0021" target="R143_E0016"><data key="edge_relationship_id">R143_R0019</data><data key="edge_source_entity_id">R143_E0021</data><data key="edge_relationship_type">uses_adjudicating_agency_geography_not_home_address</data><data key="edge_target_entity_id">R143_E0016</data><data key="edge_operational_context">State refers to DDS conducting determination, which may differ from claimant residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0020" source="R143_E0017" target="DB_DIODS"><data key="edge_relationship_id">R143_R0020</data><data key="edge_source_entity_id">R143_E0017</data><data key="edge_relationship_type">creates_workload_data_in</data><data key="edge_target_entity_id">DB_DIODS</data><data key="edge_operational_context">Electronic DDS referral and outcome transaction flow to SSA supports DIODS authoritative DDS workload store.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0021" source="DB_DIODS" target="R143_E0021"><data key="edge_relationship_id">R143_R0021</data><data key="edge_source_entity_id">DB_DIODS</data><data key="edge_relationship_type">underlies_public_product</data><data key="edge_target_entity_id">R143_E0021</data><data key="edge_operational_context">DIODS is identified by SSA as definitive workload data store for state agency disability claims.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0022" source="DB_DIODS" target="R143_E0018"><data key="edge_relationship_id">R143_R0022</data><data key="edge_source_entity_id">DB_DIODS</data><data key="edge_relationship_type">has_non_recomputed_period_summaries</data><data key="edge_target_entity_id">R143_E0018</data><data key="edge_operational_context">Historical aggregates remain stored and not recalculated after later row corrections; longer overlapping summaries contain corrected values.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0023" source="R143_E0018" target="R143_E0021"><data key="edge_relationship_id">R143_R0023</data><data key="edge_source_entity_id">R143_E0018</data><data key="edge_relationship_type">requires_nonadditive_time_series_caution_for</data><data key="edge_target_entity_id">R143_E0021</data><data key="edge_operational_context">Monthly totals need not equal quarterly/annual summaries due to later record corrections; overlapping longer series can be more accurate.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0024" source="R143_E0019" target="R143_E0015"><data key="edge_relationship_id">R143_R0024</data><data key="edge_source_entity_id">R143_E0019</data><data key="edge_relationship_type">can_be_converted_by</data><data key="edge_target_entity_id">R143_E0015</data><data key="edge_operational_context">Calendar conversion table maps four- or five-week operational month dates for correct comparison.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0025" source="R143_E0021" target="R143_E0020"><data key="edge_relationship_id">R143_R0025</data><data key="edge_source_entity_id">R143_E0021</data><data key="edge_relationship_type">implements_concurrent_case_single_count</data><data key="edge_target_entity_id">R143_E0020</data><data key="edge_operational_context">Concurrent cases generally counted once in all initial/reconsideration/CDR totals; program breakouts presented separately.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0026" source="R143_E0021" target="R143_E0022"><data key="edge_relationship_id">R143_R0026</data><data key="edge_source_entity_id">R143_E0021</data><data key="edge_relationship_type">uses_federal_workload_code</data><data key="edge_target_entity_id">R143_E0022</data><data key="edge_operational_context">FE code aggregates federal components not one geographic state.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0027" source="R143_E0021" target="R143_E0023"><data key="edge_relationship_id">R143_R0027</data><data key="edge_source_entity_id">R143_E0021</data><data key="edge_relationship_type">has_prototype_discontinuity_warning</data><data key="edge_target_entity_id">R143_E0023</data><data key="edge_operational_context">Reconsideration counts not directly comparable to initial cohort counts in prototype states.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0028" source="R143_E0021" target="R143_E0024"><data key="edge_relationship_id">R143_R0028</data><data key="edge_source_entity_id">R143_E0021</data><data key="edge_relationship_type">published_by_file_replacement</data><data key="edge_target_entity_id">R143_E0024</data><data key="edge_operational_context">Updated file at same URL may replace earlier download, with changed historical data and no public prior file.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0029" source="R143_E0021" target="R143_E0019"><data key="edge_relationship_id">R143_R0029</data><data key="edge_source_entity_id">R143_E0021</data><data key="edge_relationship_type">uses_operational_month_definition</data><data key="edge_target_entity_id">R143_E0019</data><data key="edge_operational_context">SSA workload months are four or five weeks ending on last Friday, unlike calendar months.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R55_002. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0030" source="DATA_OACT_TR2026_SINGLE_YEAR" target="R143_E0025"><data key="edge_relationship_id">R143_R0030</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_annual_income_rate_components</data><data key="edge_target_entity_id">R143_E0025</data><data key="edge_operational_context">Table index identifies IV.B2 as Components of Annual Income Rates for 1970–2100.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R81_004. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0031" source="DATA_OACT_TR2026_SINGLE_YEAR" target="R143_E0026"><data key="edge_relationship_id">R143_R0031</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_fertility_mortality_assumptions</data><data key="edge_target_entity_id">R143_E0026</data><data key="edge_operational_context">Table index identifies V.A1 as Fertility and Mortality Assumptions for 1940–2100.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R81_004. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0032" source="R143_E0025" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R143_R0032</data><data key="edge_source_entity_id">R143_E0025</data><data key="edge_relationship_type">is_consistent_with_assumptions_in</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Single-year supplemental actuarial table is consistent with the 2026 OASDI Trustees Report.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R81_004. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0033" source="R143_E0026" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R143_R0033</data><data key="edge_source_entity_id">R143_E0026</data><data key="edge_relationship_type">is_consistent_with_assumptions_in</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Single-year supplemental actuarial table is consistent with the 2026 OASDI Trustees Report.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R81_004. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0034" source="APP_IMRC" target="R143_E0027"><data key="edge_relationship_id">R143_R0034</data><data key="edge_source_entity_id">APP_IMRC</data><data key="edge_relationship_type">requires_updated_address_development_if_moved</data><data key="edge_target_entity_id">R143_E0027</data><data key="edge_operational_context">Online Medicare replacement card guidance says changed address must be reported before replacement is processed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R31_006. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0035" source="APP_IMRC" target="DB_ESERVICE_ODS"><data key="edge_relationship_id">R143_R0035</data><data key="edge_source_entity_id">APP_IMRC</data><data key="edge_relationship_type">captures_usage_to</data><data key="edge_target_entity_id">DB_ESERVICE_ODS</data><data key="edge_operational_context">SSA Open Data documents night-time movement of internet application activity counts into Electronic Services ODS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R31_006. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0036" source="DB_ESERVICE_ODS" target="DATA_IMRC_APPLICATION_VOLUMES"><data key="edge_relationship_id">R143_R0036</data><data key="edge_source_entity_id">DB_ESERVICE_ODS</data><data key="edge_relationship_type">feeds_public_usage_warehouse_for</data><data key="edge_target_entity_id">DATA_IMRC_APPLICATION_VOLUMES</data><data key="edge_operational_context">SSA Open Data reports movement from Electronic Services ODS to a data warehouse on the following day.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R31_006. Public documentation supports only the stated flow or rule.</data></edge><edge id="R143_R0037" source="APP_FIVR" target="R143_E0028"><data key="edge_relationship_id">R143_R0037</data><data key="edge_source_entity_id">APP_FIVR</data><data key="edge_relationship_type">limited_to_administrative_payments</data><data key="edge_target_entity_id">R143_E0028</data><data key="edge_operational_context">FIVR is an administrative vendor-payment query, not a Title II, Title XVI or retirement/disability benefit ledger.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R143_S004. Public documentation supports only the stated flow or rule.</data></edge><edge id="R144_R0001" source="SYS_MBR" target="R144_E0001"><data key="edge_relationship_id">R144_R0001</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_program_beneficiary_context_for</data><data key="edge_target_entity_id">R144_E0001</data><data key="edge_operational_context">Title II change-of-address must be evaluated with existing benefit/tax status, not treated as immigration status proof.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S001. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0002" source="R144_E0004" target="R144_E0001"><data key="edge_relationship_id">R144_R0002</data><data key="edge_source_entity_id">R144_E0004</data><data key="edge_relationship_type">governs_conditional_development_of</data><data key="edge_target_entity_id">R144_E0001</data><data key="edge_operational_context">POMS conditions domestic-to-foreign development on AWSC and planned duration.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S001. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0003" source="R144_E0002" target="R144_E0001"><data key="edge_relationship_id">R144_R0003</data><data key="edge_source_entity_id">R144_E0002</data><data key="edge_relationship_type">limits_inference_from</data><data key="edge_target_entity_id">R144_E0001</data><data key="edge_operational_context">An address change alone does not establish citizenship, immigration or NRA withholding tax status.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S001. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0004" source="R144_E0001" target="R144_E0003"><data key="edge_relationship_id">R144_R0004</data><data key="edge_source_entity_id">R144_E0001</data><data key="edge_relationship_type">may_require_documentation_in</data><data key="edge_target_entity_id">R144_E0003</data><data key="edge_operational_context">Tax-status development evidence is forwarded to processing center claims folder.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S001. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0005" source="FORM_R96_SSA21" target="R144_E0003"><data key="edge_relationship_id">R144_R0005</data><data key="edge_source_entity_id">FORM_R96_SSA21</data><data key="edge_relationship_type">may_be_needed_for</data><data key="edge_target_entity_id">R144_E0003</data><data key="edge_operational_context">SSA-21 may be required for other alien-tax development circumstances per GN 05010.090 summary chart.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S001. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0006" source="APP_MCS" target="R144_E0005"><data key="edge_relationship_id">R144_R0006</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">implements</data><data key="edge_target_entity_id">R144_E0005</data><data key="edge_operational_context">MCS triggers and manages AFNB 2025-2026 claims through Earnings Computation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0007" source="R144_E0007" target="R144_E0008"><data key="edge_relationship_id">R144_R0007</data><data key="edge_source_entity_id">R144_E0007</data><data key="edge_relationship_type">generates_system_receipt_for</data><data key="edge_target_entity_id">R144_E0008</data><data key="edge_operational_context">DAPP approval automatically receipts ADVFIL on DW01.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0008" source="R144_E0007" target="R144_E0005"><data key="edge_relationship_id">R144_R0008</data><data key="edge_source_entity_id">R144_E0007</data><data key="edge_relationship_type">supports_trigger_of</data><data key="edge_target_entity_id">R144_E0005</data><data key="edge_operational_context">DAPP is used during AFNB claim triggering.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0009" source="R144_E0005" target="R144_E0009"><data key="edge_relationship_id">R144_R0009</data><data key="edge_source_entity_id">R144_E0005</data><data key="edge_relationship_type">uses_control</data><data key="edge_target_entity_id">R144_E0009</data><data key="edge_operational_context">EC tickle dates must remain unchanged for system-operated AFNB batches.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0010" source="R144_E0005" target="R144_E0011"><data key="edge_relationship_id">R144_R0010</data><data key="edge_source_entity_id">R144_E0005</data><data key="edge_relationship_type">subject_to_bendpoint_availability</data><data key="edge_target_entity_id">R144_E0011</data><data key="edge_operational_context">Processing depends on 2026 EC bendpoints and MBR BRI update timing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0011" source="R144_E0010" target="R144_E0005"><data key="edge_relationship_id">R144_R0011</data><data key="edge_source_entity_id">R144_E0010</data><data key="edge_relationship_type">controls_exception_date_for</data><data key="edge_target_entity_id">R144_E0005</data><data key="edge_operational_context">FDDS material date can change in specified AFNB hold cases.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0012" source="R144_E0010" target="R144_E0006"><data key="edge_relationship_id">R144_R0012</data><data key="edge_source_entity_id">R144_E0010</data><data key="edge_relationship_type">prohibits_date_override_for</data><data key="edge_target_entity_id">R144_E0006</data><data key="edge_operational_context">Material file date must not be changed in non-AFNB Future MOE claims.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0013" source="R144_E0006" target="R144_E0012"><data key="edge_relationship_id">R144_R0013</data><data key="edge_source_entity_id">R144_E0006</data><data key="edge_relationship_type">coordinates</data><data key="edge_target_entity_id">R144_E0012</data><data key="edge_operational_context">Future MOE AI is used after the other benefit account becomes established in specified dual-entitlement cases.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0014" source="R144_E0012" target="SYS_MBR"><data key="edge_relationship_id">R144_R0014</data><data key="edge_source_entity_id">R144_E0012</data><data key="edge_relationship_type">requires_existing_record_sequence_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Dual-entitlement processing depends on MBR establishment and COLA adjustment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0015" source="APP_MCS" target="R144_E0006"><data key="edge_relationship_id">R144_R0015</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R144_E0006</data><data key="edge_operational_context">MCS Future MOE auto-initiate is a documented scheduled processing pathway.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0016" source="R144_E0005" target="R144_E0013"><data key="edge_relationship_id">R144_R0016</data><data key="edge_source_entity_id">R144_E0005</data><data key="edge_relationship_type">subject_to_reporting_limitation</data><data key="edge_target_entity_id">R144_E0013</data><data key="edge_operational_context">Automated processing-time calculation omits application-to-trigger wait interval.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0017" source="R144_E0006" target="R144_E0014"><data key="edge_relationship_id">R144_R0017</data><data key="edge_source_entity_id">R144_E0006</data><data key="edge_relationship_type">may_require_manual_exception</data><data key="edge_target_entity_id">R144_E0014</data><data key="edge_operational_context">EC cannot process all family-maximum scenarios; A101 manual processing may be necessary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0018" source="R144_E0014" target="SYS_MBR"><data key="edge_relationship_id">R144_R0018</data><data key="edge_source_entity_id">R144_E0014</data><data key="edge_relationship_type">corrects_claim_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">A101 is a manual fallback for certain EC-limited claims, not universal automated posting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0019" source="R144_E0011" target="SYS_MBR"><data key="edge_relationship_id">R144_R0019</data><data key="edge_source_entity_id">R144_E0011</data><data key="edge_relationship_type">conditions_future_entitlement_updates_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">BRI values must update on MBR before affected EC claims can process.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0020" source="APP_MACADE" target="R144_E0011"><data key="edge_relationship_id">R144_R0020</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">has_year_end_input_restrictions_due_to</data><data key="edge_target_entity_id">R144_E0011</data><data key="edge_operational_context">POMS limits MACADE input of future PIA and family-maximum rates before the appropriate operational month.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0021" source="APP_MCS" target="R144_E0013"><data key="edge_relationship_id">R144_R0021</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">produces_processing_time_metric_with</data><data key="edge_target_entity_id">R144_E0013</data><data key="edge_operational_context">The operational AFNB case-time measure is not end-to-end time from application.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S002. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0022" source="PROC_IDD" target="R144_E0015"><data key="edge_relationship_id">R144_R0022</data><data key="edge_source_entity_id">PROC_IDD</data><data key="edge_relationship_type">has_country_specific_process</data><data key="edge_target_entity_id">R144_E0015</data><data key="edge_operational_context">Czech IDD has documented operational controls within Title II international direct deposit.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0023" source="R144_E0015" target="R144_E0016"><data key="edge_relationship_id">R144_R0023</data><data key="edge_source_entity_id">R144_E0015</data><data key="edge_relationship_type">uses_form</data><data key="edge_target_entity_id">R144_E0016</data><data key="edge_operational_context">SSA-1199-OP13 is the Czech IDD customer enrollment form.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R89_005. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0024" source="R144_E0016" target="FORM_SSA1199_FAMILY"><data key="edge_relationship_id">R144_R0024</data><data key="edge_source_entity_id">R144_E0016</data><data key="edge_relationship_type">is_one_member_of</data><data key="edge_target_entity_id">FORM_SSA1199_FAMILY</data><data key="edge_operational_context">SSA publicly lists Czech Republic form among country-specific SSA-1199 forms.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R89_005. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0025" source="R144_E0015" target="R144_E0017"><data key="edge_relationship_id">R144_R0025</data><data key="edge_source_entity_id">R144_E0015</data><data key="edge_relationship_type">transforms_IBAN_to_coding</data><data key="edge_target_entity_id">R144_E0017</data><data key="edge_operational_context">SSA derives an RTN and DAN from the 24-character Czech IBAN; not equivalent to storing the IBAN as a native MBR field.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0026" source="R144_E0017" target="SYS_MBR"><data key="edge_relationship_id">R144_R0026</data><data key="edge_source_entity_id">R144_E0017</data><data key="edge_relationship_type">codes_direct_deposit_fields_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR domestic-layout deposit fields also carry Czech-specific IDD routing fields.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0027" source="R144_E0015" target="R144_E0018"><data key="edge_relationship_id">R144_R0027</data><data key="edge_source_entity_id">R144_E0015</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R144_E0018</data><data key="edge_operational_context">Two separately documented data-entry actions are necessary for current Czech IDD processing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0028" source="APP_MCS" target="R144_E0018"><data key="edge_relationship_id">R144_R0028</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">may_record_bank_data_for</data><data key="edge_target_entity_id">R144_E0018</data><data key="edge_operational_context">MCS is among the SSA systems that may establish or change Czech IDD bank information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0029" source="APP_MACADE" target="R144_E0018"><data key="edge_relationship_id">R144_R0029</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">may_record_bank_data_for</data><data key="edge_target_entity_id">R144_E0018</data><data key="edge_operational_context">MACADE may establish or change Czech IDD bank information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0030" source="APP_POS" target="R144_E0018"><data key="edge_relationship_id">R144_R0030</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">may_record_bank_data_for</data><data key="edge_target_entity_id">R144_E0018</data><data key="edge_operational_context">POS may process Czech IDD postentitlement account changes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0031" source="R144_E0018" target="SVC_ITS_GOV"><data key="edge_relationship_id">R144_R0031</data><data key="edge_source_entity_id">R144_E0018</data><data key="edge_relationship_type">separately_requires_Treasury_entry_in</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Separate ITS.gov data entry must occur on same business day as SSA system bank update.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0032" source="R144_E0015" target="R144_E0019"><data key="edge_relationship_id">R144_R0032</data><data key="edge_source_entity_id">R144_E0015</data><data key="edge_relationship_type">has_local_financial_intermediary</data><data key="edge_target_entity_id">R144_E0019</data><data key="edge_operational_context">POMS identifies Czech local FI and intermediary without naming a specific processing vendor.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0033" source="ORG_FRBKC" target="R144_E0015"><data key="edge_relationship_id">R144_R0033</data><data key="edge_source_entity_id">ORG_FRBKC</data><data key="edge_relationship_type">routes_international_payment_for</data><data key="edge_target_entity_id">R144_E0015</data><data key="edge_operational_context">FRB Kansas City routes IDD payments to Czech processing bank for local credit.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0034" source="R144_E0020" target="SYS_MBR"><data key="edge_relationship_id">R144_R0034</data><data key="edge_source_entity_id">R144_E0020</data><data key="edge_relationship_type">checks_address_coding_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR PCOC=8 foreign residence code is a prerequisite for noninitial Czech IDD changes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0035" source="R144_E0018" target="R144_E0020"><data key="edge_relationship_id">R144_R0035</data><data key="edge_source_entity_id">R144_E0018</data><data key="edge_relationship_type">conditioned_on</data><data key="edge_target_entity_id">R144_E0020</data><data key="edge_operational_context">Foreign-beneficiary address precondition must be met for specified updates.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0036" source="DATA_ITS_BENEFICIARY_ADDRESS" target="DATA_ITS_BANK_ADDRESS"><data key="edge_relationship_id">R144_R0036</data><data key="edge_source_entity_id">DATA_ITS_BENEFICIARY_ADDRESS</data><data key="edge_relationship_type">is_separate_from</data><data key="edge_target_entity_id">DATA_ITS_BANK_ADDRESS</data><data key="edge_operational_context">Treasury ITS.gov requires beneficiary and financial-institution addresses as separate attributes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0037" source="R144_E0015" target="R144_E0021"><data key="edge_relationship_id">R144_R0037</data><data key="edge_source_entity_id">R144_E0015</data><data key="edge_relationship_type">requires_separate_address_fields</data><data key="edge_target_entity_id">R144_E0021</data><data key="edge_operational_context">ITS.gov requires bank address and beneficiary address, with no validated master-record address overwrite.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0038" source="R144_E0021" target="DATA_ITS_BENEFICIARY_ADDRESS"><data key="edge_relationship_id">R144_R0038</data><data key="edge_source_entity_id">R144_E0021</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">DATA_ITS_BENEFICIARY_ADDRESS</data><data key="edge_operational_context">Beneficiary address field is specifically populated during ITS.gov enrollment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0039" source="R144_E0021" target="DATA_ITS_BANK_ADDRESS"><data key="edge_relationship_id">R144_R0039</data><data key="edge_source_entity_id">R144_E0021</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">DATA_ITS_BANK_ADDRESS</data><data key="edge_operational_context">Bank address field identifies FI and does not establish beneficiary residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0040" source="R144_E0015" target="R144_E0022"><data key="edge_relationship_id">R144_R0040</data><data key="edge_source_entity_id">R144_E0015</data><data key="edge_relationship_type">has_exception_control</data><data key="edge_target_entity_id">R144_E0022</data><data key="edge_operational_context">Inadequate forms can be routed from DIO to servicing FBU for manual follow-up.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0041" source="R144_E0018" target="R144_E0023"><data key="edge_relationship_id">R144_R0041</data><data key="edge_source_entity_id">R144_E0018</data><data key="edge_relationship_type">can_produce_exception</data><data key="edge_target_entity_id">R144_E0023</data><data key="edge_operational_context">Incomplete ITS.gov entries can produce FRB Kansas City rejection and funds return.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0042" source="ORG_FRBKC" target="R144_E0023"><data key="edge_relationship_id">R144_R0042</data><data key="edge_source_entity_id">ORG_FRBKC</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">R144_E0023</data><data key="edge_operational_context">FRBKC relies on complete ITS.gov bank data to avoid rejection.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S003. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0043" source="R144_E0024" target="PROC_IDD"><data key="edge_relationship_id">R144_R0043</data><data key="edge_source_entity_id">R144_E0024</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">IDD eligibility ends when beneficiary resumes residence in the U.S., per SSA forms guidance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R89_005. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0044" source="R144_E0016" target="R144_E0024"><data key="edge_relationship_id">R144_R0044</data><data key="edge_source_entity_id">R144_E0016</data><data key="edge_relationship_type">requires_eligible_foreign_account_under</data><data key="edge_target_entity_id">R144_E0024</data><data key="edge_operational_context">Country-specific form is for qualifying Title II recipients residing outside the U.S.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: SRC_R89_005. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0045" source="R144_E0025" target="R144_E0026"><data key="edge_relationship_id">R144_R0045</data><data key="edge_source_entity_id">R144_E0025</data><data key="edge_relationship_type">uses_external_non_census_dataset</data><data key="edge_target_entity_id">R144_E0026</data><data key="edge_operational_context">Representative-firm data are not an SSA administrative census.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S004. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0046" source="R144_E0026" target="R144_E0027"><data key="edge_relationship_id">R144_R0046</data><data key="edge_source_entity_id">R144_E0026</data><data key="edge_relationship_type">supports_statistic</data><data key="edge_target_entity_id">R144_E0027</data><data key="edge_operational_context">Observed median 20 versus 77 days and about five percent beyond 300 days apply to the studied dataset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S004. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0047" source="R144_E0025" target="R144_E0028"><data key="edge_relationship_id">R144_R0047</data><data key="edge_source_entity_id">R144_E0025</data><data key="edge_relationship_type">recommends</data><data key="edge_target_entity_id">R144_E0028</data><data key="edge_operational_context">SSAB recommends interest on delayed past-due benefits, not implemented action in source.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S004. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0048" source="R144_E0029" target="R144_E0030"><data key="edge_relationship_id">R144_R0048</data><data key="edge_source_entity_id">R144_E0029</data><data key="edge_relationship_type">analyzes</data><data key="edge_target_entity_id">R144_E0030</data><data key="edge_operational_context">Analysis is based on self-reported HRS health limitation and benefit participation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S005. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0049" source="R144_E0030" target="PROG_HRS"><data key="edge_relationship_id">R144_R0049</data><data key="edge_source_entity_id">R144_E0030</data><data key="edge_relationship_type">subset_of</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">HRS is the self-report research source; this report does not establish an SSA administrative-data linkage.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S005. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0050" source="R144_E0029" target="R144_E0031"><data key="edge_relationship_id">R144_R0050</data><data key="edge_source_entity_id">R144_E0029</data><data key="edge_relationship_type">recommends</data><data key="edge_target_entity_id">R144_E0031</data><data key="edge_operational_context">2025 outreach and cross-program automation is a proposal, not a deployed SSA system.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S005. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0051" source="R144_E0032" target="PROC_SSA_PURCHASE_CARD"><data key="edge_relationship_id">R144_R0051</data><data key="edge_source_entity_id">R144_E0032</data><data key="edge_relationship_type">assesses</data><data key="edge_target_entity_id">PROC_SSA_PURCHASE_CARD</data><data key="edge_operational_context">OIG evaluated SSA purchase card spending and risk in FY2025.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S006. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0052" source="R144_E0032" target="R144_E0033"><data key="edge_relationship_id">R144_R0052</data><data key="edge_source_entity_id">R144_E0032</data><data key="edge_relationship_type">assesses</data><data key="edge_target_entity_id">R144_E0033</data><data key="edge_operational_context">OIG assessed travel and centrally billed accounts separately from purchase cards.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S006. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0053" source="R144_E0032" target="R144_E0034"><data key="edge_relationship_id">R144_R0053</data><data key="edge_source_entity_id">R144_E0032</data><data key="edge_relationship_type">documents_reporting_gap</data><data key="edge_target_entity_id">R144_E0034</data><data key="edge_operational_context">Required FY2025 violation reports were filed in March 2026 rather than during FY2025.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S006. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0054" source="R144_E0036" target="PROC_SSA_PURCHASE_CARD"><data key="edge_relationship_id">R144_R0054</data><data key="edge_source_entity_id">R144_E0036</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_SSA_PURCHASE_CARD</data><data key="edge_operational_context">SSA charge-card management plans establish safeguard and internal-control requirements.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S006. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0055" source="R144_E0036" target="R144_E0033"><data key="edge_relationship_id">R144_R0055</data><data key="edge_source_entity_id">R144_E0036</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R144_E0033</data><data key="edge_operational_context">SSA travel and central-billing cards are within charge-card program control plans.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S006. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0056" source="R144_E0035" target="R144_E0033"><data key="edge_relationship_id">R144_R0056</data><data key="edge_source_entity_id">R144_E0035</data><data key="edge_relationship_type">temporarily_restricted</data><data key="edge_target_entity_id">R144_E0033</data><data key="edge_operational_context">OIG describes temporary $1 transaction limit imposed on travel cards under February 2025 measures.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S006. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0057" source="R144_E0035" target="PROC_SSA_PURCHASE_CARD"><data key="edge_relationship_id">R144_R0057</data><data key="edge_source_entity_id">R144_E0035</data><data key="edge_relationship_type">temporarily_restricted</data><data key="edge_target_entity_id">PROC_SSA_PURCHASE_CARD</data><data key="edge_operational_context">OIG describes temporary $1 transaction limit imposed on purchase cards.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S006. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R144_R0058" source="R144_E0032" target="R144_E0035"><data key="edge_relationship_id">R144_R0058</data><data key="edge_source_entity_id">R144_E0032</data><data key="edge_relationship_type">documents</data><data key="edge_target_entity_id">R144_E0035</data><data key="edge_operational_context">OIG describes the historical February 2025 charge card transaction freeze response.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source: R144_S006. Explicitly scoped, not a claim of automatic updates or physical architecture.</data></edge><edge id="R145_R0001" source="APP_SSNAP" target="R145_E0001"><data key="edge_relationship_id">R145_R0001</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">records_document_metadata_in</data><data key="edge_target_entity_id">R145_E0001</data><data key="edge_operational_context">SSNAP Summary Evidence Submitted captures foreign passport attributes with the documented primary DHS proof of identity.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0002" source="R145_E0004" target="R145_E0001"><data key="edge_relationship_id">R145_R0002</data><data key="edge_source_entity_id">R145_E0004</data><data key="edge_relationship_type">requires_documentation_in</data><data key="edge_target_entity_id">R145_E0001</data><data key="edge_operational_context">When the foreign passport accompanies a DHS identity document, required passport identifying metadata is entered in SSNAP Summary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0003" source="R145_E0002" target="APP_SSNAP"><data key="edge_relationship_id">R145_R0003</data><data key="edge_source_entity_id">R145_E0002</data><data key="edge_relationship_type">governs_identity_proof_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">State identification carrying NOT FOR FEDERAL IDENTIFICATION may qualify as primary identity evidence for SSNAP enumeration processing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0004" source="R145_E0003" target="APP_SSNAP"><data key="edge_relationship_id">R145_R0004</data><data key="edge_source_entity_id">R145_E0003</data><data key="edge_relationship_type">controls_identity_document_priority_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Age-based evidence priorities and third-level exceptions govern SSNAP SSN application review.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0005" source="R145_E0004" target="APP_SSNAP"><data key="edge_relationship_id">R145_R0005</data><data key="edge_source_entity_id">R145_E0004</data><data key="edge_relationship_type">establishes_alien_primary_identity_evidence_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">DHS lawful-alien documents plus a foreign passport serve as specified primary identity evidence; conditional exceptions apply.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0006" source="R145_E0001" target="UI_SSNAP_SUMMARY"><data key="edge_relationship_id">R145_R0006</data><data key="edge_source_entity_id">R145_E0001</data><data key="edge_relationship_type">displayed_on</data><data key="edge_target_entity_id">UI_SSNAP_SUMMARY</data><data key="edge_operational_context">POMS explicitly names the Evidence Submitted field on SSNAP Summary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0007" source="R145_E0005" target="ORG_SSA_CENTRAL_PROCESSING"><data key="edge_relationship_id">R145_R0007</data><data key="edge_source_entity_id">R145_E0005</data><data key="edge_relationship_type">governed_by_custodian</data><data key="edge_target_entity_id">ORG_SSA_CENTRAL_PROCESSING</data><data key="edge_operational_context">POMS names Central Processing as holder of concurrent-case Title II paper folders.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0008" source="R145_E0006" target="R110_E002"><data key="edge_relationship_id">R145_R0008</data><data key="edge_source_entity_id">R145_E0006</data><data key="edge_relationship_type">governed_by_custodian</data><data key="edge_target_entity_id">R110_E002</data><data key="edge_operational_context">POMS identifies National Records Center as the Title XVI paper folder location.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0009" source="R145_E0005" target="REPO_PAPER_DISABILITY_FOLDER"><data key="edge_relationship_id">R145_R0009</data><data key="edge_source_entity_id">R145_E0005</data><data key="edge_relationship_type">defines_custody_for</data><data key="edge_target_entity_id">REPO_PAPER_DISABILITY_FOLDER</data><data key="edge_operational_context">Defines Title II component of split physical folder custody in concurrent claims.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0010" source="R145_E0006" target="REPO_PAPER_DISABILITY_FOLDER"><data key="edge_relationship_id">R145_R0010</data><data key="edge_source_entity_id">R145_E0006</data><data key="edge_relationship_type">defines_custody_for</data><data key="edge_target_entity_id">REPO_PAPER_DISABILITY_FOLDER</data><data key="edge_operational_context">Defines Title XVI component of split physical folder custody in concurrent claims.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0011" source="R145_E0007" target="REPO_PAPER_DISABILITY_FOLDER"><data key="edge_relationship_id">R145_R0011</data><data key="edge_source_entity_id">R145_E0007</data><data key="edge_relationship_type">requires_paper_evidence_transferred_from</data><data key="edge_target_entity_id">REPO_PAPER_DISABILITY_FOLDER</data><data key="edge_operational_context">Electronic case referral does not eliminate associated paper folder transfer to DDS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0012" source="R145_E0007" target="APP_EDCS"><data key="edge_relationship_id">R145_R0012</data><data key="edge_source_entity_id">R145_E0007</data><data key="edge_relationship_type">applies_alongside_electronic_case_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">eCDR folder transfer includes EDCS electronic information and any associated physical folders.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0013" source="R145_E0008" target="APP_EVIEW"><data key="edge_relationship_id">R145_R0013</data><data key="edge_source_entity_id">R145_E0008</data><data key="edge_relationship_type">uses_electronic_case_review_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">The DDS examiner reviews eView Case Data, Case Documents, and Alerts &amp; Messages tabs for concurrent eCDR.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0014" source="R145_E0009" target="REPO_PAPER_DISABILITY_FOLDER"><data key="edge_relationship_id">R145_R0014</data><data key="edge_source_entity_id">R145_E0009</data><data key="edge_relationship_type">limits_retrieval_of</data><data key="edge_target_entity_id">REPO_PAPER_DISABILITY_FOLDER</data><data key="edge_operational_context">The Title XVI paper folder need not always be obtained based solely on an SSI2 query.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0015" source="R145_E0008" target="APP_EDCS"><data key="edge_relationship_id">R145_R0015</data><data key="edge_source_entity_id">R145_E0008</data><data key="edge_relationship_type">coordinates_decision_with</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Cross-title CDR determinations require reconciliation of unresolved entitlement information prior to processing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0016" source="R145_E0010" target="APP_DDSQ"><data key="edge_relationship_id">R145_R0016</data><data key="edge_source_entity_id">R145_E0010</data><data key="edge_relationship_type">requires_cross_check_of</data><data key="edge_target_entity_id">APP_DDSQ</data><data key="edge_operational_context">DDSQ is not necessarily the latest adjudicative disposition after DQR revisions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0017" source="R145_E0010" target="PROC_DQR_QUALITY_REVIEW"><data key="edge_relationship_id">R145_R0017</data><data key="edge_source_entity_id">R145_E0010</data><data key="edge_relationship_type">requires_final_decision_evidence_from</data><data key="edge_target_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_operational_context">DQR procedural changes can differ from DDSQ data; verify final SSA-831. This represents a review process, not a system interface.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0018" source="R145_E0011" target="APP_EDCS"><data key="edge_relationship_id">R145_R0018</data><data key="edge_source_entity_id">R145_E0011</data><data key="edge_relationship_type">controls_assistance_requests_from</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Field office tracks requests conveyed by EDCS AI/AR or other documented channels and responds or supplies status within 14 days.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0019" source="R145_E0012" target="DATA_NDDSS_SO"><data key="edge_relationship_id">R145_R0019</data><data key="edge_source_entity_id">R145_E0012</data><data key="edge_relationship_type">defines_code_values_for</data><data key="edge_target_entity_id">DATA_NDDSS_SO</data><data key="edge_operational_context">Documented four values control whether case movement, decisional, all, or no NDDSS elements transmit.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0020" source="R145_E0012" target="APP_DDSQ"><data key="edge_relationship_id">R145_R0020</data><data key="edge_source_entity_id">R145_E0012</data><data key="edge_relationship_type">constrains_data_available_through</data><data key="edge_target_entity_id">APP_DDSQ</data><data key="edge_operational_context">An override flag can intentionally suppress case movement or decisional data from SSA systems.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0021" source="R145_E0013" target="APP_MYSSA"><data key="edge_relationship_id">R145_R0021</data><data key="edge_source_entity_id">R145_E0013</data><data key="edge_relationship_type">delivered_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Online access via my Social Security provides print, save, replacement request options and preference settings.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0022" source="R145_E0014" target="R145_E0013"><data key="edge_relationship_id">R145_R0022</data><data key="edge_source_entity_id">R145_E0014</data><data key="edge_relationship_type">sets_historical_access_window_for</data><data key="edge_target_entity_id">R145_E0013</data><data key="edge_operational_context">Current plus five preceding benefit tax years, not an underlying database retention guarantee.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0023" source="R145_E0015" target="R145_E0013"><data key="edge_relationship_id">R145_R0023</data><data key="edge_source_entity_id">R145_E0015</data><data key="edge_relationship_type">governs_notice_distribution_of</data><data key="edge_target_entity_id">R145_E0013</data><data key="edge_operational_context">Representative payee receives mailed tax statements regardless of beneficiary online preference.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0024" source="R145_E0016" target="R145_E0013"><data key="edge_relationship_id">R145_R0024</data><data key="edge_source_entity_id">R145_E0016</data><data key="edge_relationship_type">governs_undeliverable_mail_of</data><data key="edge_target_entity_id">R145_E0013</data><data key="edge_operational_context">Undeliverable form is disposed securely; no investigation or address-master update required.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0025" source="R145_E0017" target="R145_E0013"><data key="edge_relationship_id">R145_R0025</data><data key="edge_source_entity_id">R145_E0017</data><data key="edge_relationship_type">generates_corrected_output_for</data><data key="edge_target_entity_id">R145_E0013</data><data key="edge_operational_context">Automated Central Office statement correction and NCC print route; alternate manual replacement forms documented.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0026" source="R145_E0018" target="R145_E0013"><data key="edge_relationship_id">R145_R0026</data><data key="edge_source_entity_id">R145_E0018</data><data key="edge_relationship_type">conditions_postal_delivery_of</data><data key="edge_target_entity_id">R145_E0013</data><data key="edge_operational_context">Delivery suppressed for countries subject to USPS international suspension or sanctions.)</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0027" source="R145_E0014" target="SVC_MYSSA_MESSAGE_CENTER"><data key="edge_relationship_id">R145_R0027</data><data key="edge_source_entity_id">R145_E0014</data><data key="edge_relationship_type">provides_digital_access_through</data><data key="edge_target_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_operational_context">mySSA Message Center preferences govern digital/paper notification; six-year tax form access occurs in mySSA.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0028" source="R145_E0019" target="SYS_MEF"><data key="edge_relationship_id">R145_R0028</data><data key="edge_source_entity_id">R145_E0019</data><data key="edge_relationship_type">changes_governance_of</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">A claimant-provided tax document becomes IRC-controlled return information when used to create or amend the official earnings record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0029" source="R145_E0020" target="ORG_IRS"><data key="edge_relationship_id">R145_R0029</data><data key="edge_source_entity_id">R145_E0020</data><data key="edge_relationship_type">governs_tax_information_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SSA may use/disclose federal tax return information only with statutory or IRS authorization; source and authorized purpose matter.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0030" source="R145_E0021" target="SYS_MEF"><data key="edge_relationship_id">R145_R0030</data><data key="edge_source_entity_id">R145_E0021</data><data key="edge_relationship_type">addresses_identity_mismatches_associated_with</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Employer W-2 reporting can produce names/SSNs that do not match SSA records, prompting employer EDCOR notices; DECOR mailing suspended.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0031" source="R145_E0022" target="R145_E0023"><data key="edge_relationship_id">R145_R0031</data><data key="edge_source_entity_id">R145_E0022</data><data key="edge_relationship_type">publishes_statistical_table</data><data key="edge_target_entity_id">R145_E0023</data><data key="edge_operational_context">The 2026 SSA Fast Facts publication includes the 1970 and 2025 insured-status sex comparison.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0032" source="R145_E0023" target="R145_E0024"><data key="edge_relationship_id">R145_R0032</data><data key="edge_source_entity_id">R145_E0023</data><data key="edge_relationship_type">uses_population_denominator_definition</data><data key="edge_target_entity_id">R145_E0024</data><data key="edge_operational_context">Chartbook statistical denominator is Social Security area population and is subject to revisions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0033" source="R145_E0022" target="DATA_OACT_INSURED_WORKERS_STATUS"><data key="edge_relationship_id">R145_R0033</data><data key="edge_source_entity_id">R145_E0022</data><data key="edge_relationship_type">corroborates_oact_domain_data</data><data key="edge_target_entity_id">DATA_OACT_INSURED_WORKERS_STATUS</data><data key="edge_operational_context">Published SSA Actuarial Services insured-status statistics form an annual public reporting product.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0034" source="R145_E0024" target="DATA_OACT_SOCSEC_AREA_INSURED"><data key="edge_relationship_id">R145_R0034</data><data key="edge_source_entity_id">R145_E0024</data><data key="edge_relationship_type">qualifies_insured_population_statistics_in</data><data key="edge_target_entity_id">DATA_OACT_SOCSEC_AREA_INSURED</data><data key="edge_operational_context">Population denominators include defined non-mainland groups and outside-U.S. populations; not a simple resident geographic count.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0035" source="R145_E0025" target="SYS_MBR"><data key="edge_relationship_id">R145_R0035</data><data key="edge_source_entity_id">R145_E0025</data><data key="edge_relationship_type">qualifies_prior_award_evidence_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">A prior payment record can establish only the insured-status criteria underlying that earlier payment; not every subsequent benefit test.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0036" source="R145_E0026" target="SYS_MEF"><data key="edge_relationship_id">R145_R0036</data><data key="edge_source_entity_id">R145_E0026</data><data key="edge_relationship_type">requires_current_master_validation_against</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">SSA guidance calls for checking the earnings record with DEQY after processing rather than assuming transaction screens equal the master.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0037" source="R145_E0027" target="APP_MCS"><data key="edge_relationship_id">R145_R0037</data><data key="edge_source_entity_id">R145_E0027</data><data key="edge_relationship_type">requires_representative_data_validation_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">SSA appointment procedures require technician checks for active representation in title II claims processing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0038" source="R145_E0027" target="APP_MSSICS"><data key="edge_relationship_id">R145_R0038</data><data key="edge_source_entity_id">R145_E0027</data><data key="edge_relationship_type">requires_representative_data_validation_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">For applicable SSI claims, representation must be correctly recorded in the SSI claim environment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R145_R0039" source="R145_E0027" target="APP_EDCS"><data key="edge_relationship_id">R145_R0039</data><data key="edge_source_entity_id">R145_E0027</data><data key="edge_relationship_type">requires_representative_data_validation_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">For applicable disability cases, representative flags must be checked or corrected in EDCS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0001" source="R146_E0001" target="R146_E0002"><data key="edge_relationship_id">R146_R0001</data><data key="edge_source_entity_id">R146_E0001</data><data key="edge_relationship_type">forwards_irs_pension_participant_data_to</data><data key="edge_target_entity_id">R146_E0002</data><data key="edge_operational_context">Electronic 8955-SSA filing passes from IRS to SSA ERISA records; specific format/transport not documented.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0002" source="R146_E0004" target="R146_E0002"><data key="edge_relationship_id">R146_R0002</data><data key="edge_source_entity_id">R146_E0004</data><data key="edge_relationship_type">historically_transferred_pension_reports_to</data><data key="edge_target_entity_id">R146_E0002</data><data key="edge_operational_context">DOL EFAST was used for historical Form 5500 Schedule SSA transfers, retired as an intake path after transition.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0003" source="ORG_WBDOC" target="R146_E0005"><data key="edge_relationship_id">R146_R0003</data><data key="edge_source_entity_id">ORG_WBDOC</data><data key="edge_relationship_type">processes_paper_fallout_for</data><data key="edge_target_entity_id">R146_E0005</data><data key="edge_operational_context">Wilkes-Barre handles paper IRS 8955-SSA scanning and historic EFAST fallout.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0004" source="R146_E0005" target="R146_E0002"><data key="edge_relationship_id">R146_R0004</data><data key="edge_source_entity_id">R146_E0005</data><data key="edge_relationship_type">supplies_scanned_pension_info_to</data><data key="edge_target_entity_id">R146_E0002</data><data key="edge_operational_context">Paper ERISA participant reporting was keyed/scanned into electronic files.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0005" source="ORG_IRS" target="R146_E0001"><data key="edge_relationship_id">R146_R0005</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">uses_pension_electronic_filing_channel</data><data key="edge_target_entity_id">R146_E0001</data><data key="edge_operational_context">IRS receives 8955-SSA through FIRE, then transmits IRS data to SSA.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0006" source="R146_E0003" target="R138_E0010"><data key="edge_relationship_id">R146_R0006</data><data key="edge_source_entity_id">R146_E0003</data><data key="edge_relationship_type">indexes_paper_irs_pension_images_for</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">Paper-source 12-digit notice cases have AIRS images available on inquiry.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0007" source="R146_E0006" target="R146_E0003"><data key="edge_relationship_id">R146_R0007</data><data key="edge_source_entity_id">R146_E0006</data><data key="edge_relationship_type">identifies_paper_image_custody_in</data><data key="edge_target_entity_id">R146_E0003</data><data key="edge_operational_context">AIRS retains images for paper IRS pension reports indexed using twelve-digit DCN.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0008" source="R146_E0007" target="R146_E0001"><data key="edge_relationship_id">R146_R0008</data><data key="edge_source_entity_id">R146_E0007</data><data key="edge_relationship_type">indicates_upstream_irs_channel</data><data key="edge_target_entity_id">R146_E0001</data><data key="edge_operational_context">The 14-digit SSA DCN identifies IRS FIRE electronical submission of Form 8955-SSA.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0009" source="R146_E0007" target="R146_E0009"><data key="edge_relationship_id">R146_R0009</data><data key="edge_source_entity_id">R146_E0007</data><data key="edge_relationship_type">invokes_disclosure_limitation</data><data key="edge_target_entity_id">R146_E0009</data><data key="edge_operational_context">Electronic source report has no additional stored image for inquirer.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0010" source="R146_E0008" target="APP_IRON"><data key="edge_relationship_id">R146_R0010</data><data key="edge_source_entity_id">R146_E0008</data><data key="edge_relationship_type">locates_pre_2008_microfilm_records_in</data><data key="edge_target_entity_id">APP_IRON</data><data key="edge_operational_context">M-prefixed DCNs link to microfilmed historical ERISA pension data in IRON.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0011" source="R146_E0006" target="R138_E0010"><data key="edge_relationship_id">R146_R0011</data><data key="edge_source_entity_id">R146_E0006</data><data key="edge_relationship_type">indexes_erisa_notice</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">DCN in the SSA-L99-C1 for paper-source notice and associated image.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0012" source="R146_E0007" target="R138_E0010"><data key="edge_relationship_id">R146_R0012</data><data key="edge_source_entity_id">R146_E0007</data><data key="edge_relationship_type">indexes_erisa_notice</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">DCN in the SSA-L99-C1 for electronic-source case without archived image.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0013" source="R146_E0008" target="R138_E0010"><data key="edge_relationship_id">R146_R0013</data><data key="edge_source_entity_id">R146_E0008</data><data key="edge_relationship_type">indexes_erisa_notice</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">M-prefixed control number distinguishes historical source.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0014" source="R146_E0010" target="R138_E0011"><data key="edge_relationship_id">R146_R0014</data><data key="edge_source_entity_id">R146_E0010</data><data key="edge_relationship_type">qualifies_plan_administrator_address</data><data key="edge_target_entity_id">R138_E0011</data><data key="edge_operational_context">The IRS-reported plan address can be outdated and must not be assigned to the named pension participant.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0015" source="R146_E0010" target="R138_E0010"><data key="edge_relationship_id">R146_R0015</data><data key="edge_source_entity_id">R146_E0010</data><data key="edge_relationship_type">is_printed_on</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">SSA-L99-C1 includes plan address carried from earlier tax reporting year.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0016" source="ORG_IRS" target="R146_E0010"><data key="edge_relationship_id">R146_R0016</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">supplies_third_party_address_observation</data><data key="edge_target_entity_id">R146_E0010</data><data key="edge_operational_context">Plan administrator reports mailing address to IRS; SSA receives it through ERISA pension reporting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0017" source="R146_E0011" target="R146_E0002"><data key="edge_relationship_id">R146_R0017</data><data key="edge_source_entity_id">R146_E0011</data><data key="edge_relationship_type">queries_pension_participant_database</data><data key="edge_target_entity_id">R146_E0002</data><data key="edge_operational_context">Claim/Medicare applications trigger lookup against ERISA plan participant data maintained by SSA.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0018" source="R146_E0011" target="R138_E0010"><data key="edge_relationship_id">R146_R0018</data><data key="edge_source_entity_id">R146_E0011</data><data key="edge_relationship_type">produces_potential_pension_notice</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">SSA mails monthly Potential Private Retirement Benefit Information notice when matching data exists.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0020" source="R146_E0012" target="APP_MAPS"><data key="edge_relationship_id">R146_R0020</data><data key="edge_source_entity_id">R146_E0012</data><data key="edge_relationship_type">triggers_manual_entry_in</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">Employees enter copies in MAPS rather than sending photocopies to scanner.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0021" source="R146_E0012" target="DATA_SSA1020_OCR"><data key="edge_relationship_id">R146_R0021</data><data key="edge_source_entity_id">R146_E0012</data><data key="edge_relationship_type">affects_intake_document</data><data key="edge_target_entity_id">DATA_SSA1020_OCR</data><data key="edge_operational_context">Only original scannable form is accepted by WBDOC imaging process.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0022" source="R146_E0013" target="ORG_WBDOC"><data key="edge_relationship_id">R146_R0022</data><data key="edge_source_entity_id">R146_E0013</data><data key="edge_relationship_type">routes_exception_to</data><data key="edge_target_entity_id">ORG_WBDOC</data><data key="edge_operational_context">Paper resource-question self-screening exception is handled at WBDOC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0023" source="R146_E0014" target="APP_MAPS"><data key="edge_relationship_id">R146_R0023</data><data key="edge_source_entity_id">R146_E0014</data><data key="edge_relationship_type">requires_print_step_in</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">MAPS printing is an operational prerequisite to stored copy retrieval under cited POMS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0024" source="R146_E0014" target="R146_E0015"><data key="edge_relationship_id">R146_R0024</data><data key="edge_source_entity_id">R146_E0014</data><data key="edge_relationship_type">causes_document_availability_in</data><data key="edge_target_entity_id">R146_E0015</data><data key="edge_operational_context">SSA advises always print MAPS application so it will appear in ORS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0025" source="R146_E0015" target="APP_MAPS"><data key="edge_relationship_id">R146_R0025</data><data key="edge_source_entity_id">R146_E0015</data><data key="edge_relationship_type">retains_accessible_map_application_from</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">SSA describes the specific application document retrieval route; physical retention schedule undocumented.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0026" source="R146_E0016" target="APP_MAPS"><data key="edge_relationship_id">R146_R0026</data><data key="edge_source_entity_id">R146_E0016</data><data key="edge_relationship_type">changes_spouse_identity_encoding_in</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">Do not add unenumerated spouse as separate MAPS entry when enumeration unavailable; adjust household/income treatment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0028" source="R146_E0016" target="UI_MAPS_APPLICANT_INFO"><data key="edge_relationship_id">R146_R0028</data><data key="edge_source_entity_id">R146_E0016</data><data key="edge_relationship_type">affects_applicant_spouse_information_in</data><data key="edge_target_entity_id">UI_MAPS_APPLICANT_INFO</data><data key="edge_operational_context">Household resources/income treatment differs when spouse is not enumerated.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0029" source="R146_E0017" target="UI_MAPS_DEV_WORKSHEET"><data key="edge_relationship_id">R146_R0029</data><data key="edge_source_entity_id">R146_E0017</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">UI_MAPS_DEV_WORKSHEET</data><data key="edge_operational_context">Technician initials/ATTEST entry reflect proxy signature for in-person and telephone MAPS claims.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0030" source="R146_E0017" target="SVC_I1020"><data key="edge_relationship_id">R146_R0030</data><data key="edge_source_entity_id">R146_E0017</data><data key="edge_relationship_type">contrasts_internet_signature_from</data><data key="edge_target_entity_id">SVC_I1020</data><data key="edge_operational_context">i1020 uses customer electronic click-and-sign, distinct from employee MAPS attestation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0031" source="R146_E0017" target="R146_E0014"><data key="edge_relationship_id">R146_R0031</data><data key="edge_source_entity_id">R146_E0017</data><data key="edge_relationship_type">must_support_retrieval_using</data><data key="edge_target_entity_id">R146_E0014</data><data key="edge_operational_context">POMS makes printing the MAPS application mandatory for Online Retrieval storage.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0032" source="R146_E0018" target="APP_RASR"><data key="edge_relationship_id">R146_R0032</data><data key="edge_source_entity_id">R146_E0018</data><data key="edge_relationship_type">maintained_within</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">IDPE list appears in RASR with EIN, claim SSN, status, dates, outstanding amounts.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0033" source="R146_E0019" target="R146_E0018"><data key="edge_relationship_id">R146_R0033</data><data key="edge_source_entity_id">R146_E0019</data><data key="edge_relationship_type">reviews_and_updates</data><data key="edge_target_entity_id">R146_E0018</data><data key="edge_operational_context">Coordinator verifies fee liabilities, controls eligibility and updates list for remittances.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0034" source="R146_E0020" target="R146_E0019"><data key="edge_relationship_id">R146_R0034</data><data key="edge_source_entity_id">R146_E0020</data><data key="edge_relationship_type">triggers_manager_review_by</data><data key="edge_target_entity_id">R146_E0019</data><data key="edge_operational_context">Referral after both 30-day responses exhausted and approval documented.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0035" source="R146_E0021" target="APP_DMS"><data key="edge_relationship_id">R146_R0035</data><data key="edge_source_entity_id">R146_E0021</data><data key="edge_relationship_type">records_debt_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Title II individual excess payment is entered in DMS, with separate manual Title XVI controls.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0036" source="R146_E0022" target="APP_RASR"><data key="edge_relationship_id">R146_R0036</data><data key="edge_source_entity_id">R146_E0022</data><data key="edge_relationship_type">is_part_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Individual ROC per appointment in RASR rather than entity-only document.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0037" source="R146_E0020" target="R146_E0022"><data key="edge_relationship_id">R146_R0037</data><data key="edge_source_entity_id">R146_E0020</data><data key="edge_relationship_type">uses_documented_report_screen</data><data key="edge_target_entity_id">R146_E0022</data><data key="edge_operational_context">RASR includes EIN, Rep IDs, past due benefits, fee authorization and claimant impact.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0038" source="R146_E0018" target="APP_RASR"><data key="edge_relationship_id">R146_R0038</data><data key="edge_source_entity_id">R146_E0018</data><data key="edge_relationship_type">identifies_organization_by_ein_and_claimant_ssn</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">IDPE row relates entity EIN to claimant SSN for each unresolved fee issue.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0039" source="R146_E0023" target="APP_DPS"><data key="edge_relationship_id">R146_R0039</data><data key="edge_source_entity_id">R146_E0023</data><data key="edge_relationship_type">may_be_created_using</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Collection letter may be authored in DPS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0040" source="R146_E0023" target="APP_AURORA"><data key="edge_relationship_id">R146_R0040</data><data key="edge_source_entity_id">R146_E0023</data><data key="edge_relationship_type">may_be_created_using</data><data key="edge_target_entity_id">APP_AURORA</data><data key="edge_operational_context">Collection letter may be authored in Aurora.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0041" source="R146_E0024" target="APP_DPS"><data key="edge_relationship_id">R146_R0041</data><data key="edge_source_entity_id">R146_E0024</data><data key="edge_relationship_type">may_be_created_using</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Final entity collection letter available through DPS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0042" source="R146_E0024" target="APP_AURORA"><data key="edge_relationship_id">R146_R0042</data><data key="edge_source_entity_id">R146_E0024</data><data key="edge_relationship_type">may_be_created_using</data><data key="edge_target_entity_id">APP_AURORA</data><data key="edge_operational_context">Final entity collection letter available through Aurora.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0043" source="R146_E0020" target="R146_E0023"><data key="edge_relationship_id">R146_R0043</data><data key="edge_source_entity_id">R146_E0020</data><data key="edge_relationship_type">initial_notice</data><data key="edge_target_entity_id">R146_E0023</data><data key="edge_operational_context">First 30-day recovery control begins with MAO104.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0044" source="R146_E0020" target="R146_E0024"><data key="edge_relationship_id">R146_R0044</data><data key="edge_source_entity_id">R146_E0020</data><data key="edge_relationship_type">final_notice</data><data key="edge_target_entity_id">R146_E0024</data><data key="edge_operational_context">Second 30-day control begins with MAO105.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0045" source="R146_E0018" target="R146_E0025"><data key="edge_relationship_id">R146_R0045</data><data key="edge_source_entity_id">R146_E0018</data><data key="edge_relationship_type">generates_status_notification</data><data key="edge_target_entity_id">R146_E0025</data><data key="edge_operational_context">RASR sends IDPE determination notice once new entry established subject to repeat suppression.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0046" source="R146_E0026" target="APP_DMS"><data key="edge_relationship_id">R146_R0046</data><data key="edge_source_entity_id">R146_E0026</data><data key="edge_relationship_type">requires_conditional_reconciliation_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">When remittance fails to post automatically to DMS, technician checks and corrects manually.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0047" source="R146_E0026" target="DB_PHUS"><data key="edge_relationship_id">R146_R0047</data><data key="edge_source_entity_id">R146_E0026</data><data key="edge_relationship_type">requires_conditional_reconciliation_in</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">PHUS payment history needs correction when normal automatic posting missing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0048" source="R146_E0027" target="WORK_SSI_IRS_5B_DIARY"><data key="edge_relationship_id">R146_R0048</data><data key="edge_source_entity_id">R146_E0027</data><data key="edge_relationship_type">determines_diary_trigger_in</data><data key="edge_target_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_operational_context">System screens incoming IRS amounts by program-size thresholds and prior alert tolerance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0049" source="R146_E0027" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R146_R0049</data><data key="edge_source_entity_id">R146_E0027</data><data key="edge_relationship_type">applies_to_irs_reported_input_via</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">1099 resource/income categories provide triggers, not verified countable-income determinations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0050" source="R146_E0028" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R146_R0050</data><data key="edge_source_entity_id">R146_E0028</data><data key="edge_relationship_type">controls_release_of</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">Three batch windows and selected cohorts described in SI 02310.045.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0051" source="R146_E0028" target="WORK_SSI_IRS_5B_DIARY"><data key="edge_relationship_id">R146_R0051</data><data key="edge_source_entity_id">R146_E0028</data><data key="edge_relationship_type">posts_work_issue_to</data><data key="edge_target_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_operational_context">Qualifying records produce SSR 5B diary subject to thresholds.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0052" source="WORK_SSI_IRS_5B_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R146_R0052</data><data key="edge_source_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_relationship_type">flags_followup_work_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR diaries require further development; they do not modify verified income/resource automatically.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0053" source="R146_E0029" target="APP_PCACS"><data key="edge_relationship_id">R146_R0053</data><data key="edge_source_entity_id">R146_E0029</data><data key="edge_relationship_type">requires_workload_receipt_confirmation_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">Reviews require PCACS or Evidence Portal confirmation of controlling issue.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0054" source="R146_E0029" target="APP_DMS"><data key="edge_relationship_id">R146_R0054</data><data key="edge_source_entity_id">R146_E0029</data><data key="edge_relationship_type">has_processing_center_debt_record_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Mid-Atlantic processing center DMS follows appeals for FSO.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0055" source="R146_E0030" target="APP_PCACS"><data key="edge_relationship_id">R146_R0055</data><data key="edge_source_entity_id">R146_E0030</data><data key="edge_relationship_type">verifies_evidence_workload_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">Staff query PCACS to confirm paperless case before destroying retained FO copy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0056" source="R146_E0030" target="R146_E0029"><data key="edge_relationship_id">R146_R0056</data><data key="edge_source_entity_id">R146_E0030</data><data key="edge_relationship_type">controls_appeal_document_custody_for</data><data key="edge_target_entity_id">R146_E0029</data><data key="edge_operational_context">FO retention is temporary and separate from official appeal folder.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0057" source="R146_E0031" target="APP_TED"><data key="edge_relationship_id">R146_R0057</data><data key="edge_source_entity_id">R146_E0031</data><data key="edge_relationship_type">processed_in</data><data key="edge_target_entity_id">APP_TED</data><data key="edge_operational_context">TED technician selects verified one-time address using stored account email as optional starting value.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0058" source="R146_E0031" target="APP_MYSSA"><data key="edge_relationship_id">R146_R0058</data><data key="edge_source_entity_id">R146_E0031</data><data key="edge_relationship_type">may_reference_but_does_not_necessarily_change</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">My Social Security account email may be shown, but separate recipient email permitted.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0059" source="R146_E0032" target="APP_TED"><data key="edge_relationship_id">R146_R0059</data><data key="edge_source_entity_id">R146_E0032</data><data key="edge_relationship_type">controls_tasks_created_in</data><data key="edge_target_entity_id">APP_TED</data><data key="edge_operational_context">Unanswered technician task closes after 30 days under 2024 instruction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0060" source="R146_E0033" target="APP_WORKTRACK"><data key="edge_relationship_id">R146_R0060</data><data key="edge_source_entity_id">R146_E0033</data><data key="edge_relationship_type">describes_batch_import_in</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">WorkTrack upload is a different function from customer eSignature/Upload Documents.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0061" source="R146_E0034" target="APP_WORKTRACK"><data key="edge_relationship_id">R146_R0061</data><data key="edge_source_entity_id">R146_E0034</data><data key="edge_relationship_type">feeds_signed_document_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">SSA-827 webform PDF available in WorkTrack after digital submission.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0063" source="R146_E0035" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R146_R0063</data><data key="edge_source_entity_id">R146_E0035</data><data key="edge_relationship_type">qualifies_publication_status_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Tables from 2026 supplement are subject to updates until edition complete.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0064" source="R146_E0036" target="SYS_MBR"><data key="edge_relationship_id">R146_R0064</data><data key="edge_source_entity_id">R146_E0036</data><data key="edge_relationship_type">derives_cross_program_statistics_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">OASDI side is full-population MBR rather than a random sampling frame.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0065" source="R146_E0036" target="SYS_SSR"><data key="edge_relationship_id">R146_R0065</data><data key="edge_source_entity_id">R146_E0036</data><data key="edge_relationship_type">derives_cross_program_statistics_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI side is full-population SSR and concurrent count de-duplicates OASDI.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0066" source="R146_E0036" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R146_R0066</data><data key="edge_source_entity_id">R146_E0036</data><data key="edge_relationship_type">qualifies_counts_in</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">Primary and secondary benefit entitlement not counted twice.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R146_R0067" source="R146_E0037" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R146_R0067</data><data key="edge_source_entity_id">R146_E0037</data><data key="edge_relationship_type">qualifies_ssi_payment_amount_statistics_in</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">Retroactive amounts included in aggregate total but excluded from reported average monthly benefit.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0001" source="APP_CPMS" target="R147_E0001"><data key="edge_relationship_id">R147_R0001</data><data key="edge_source_entity_id">APP_CPMS</data><data key="edge_relationship_type">historical_case_microdata_feeds</data><data key="edge_target_entity_id">R147_E0001</data><data key="edge_operational_context">OHO supplies year-end pending case microdata from CPMS; source explicitly relates to FY2005-2017 historical series, not 2026 operation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0002" source="ORG_OHO" target="R147_E0001"><data key="edge_relationship_id">R147_R0002</data><data key="edge_source_entity_id">ORG_OHO</data><data key="edge_relationship_type">provided_historical_case_microdata_for</data><data key="edge_target_entity_id">R147_E0001</data><data key="edge_operational_context">OHO provided CPMS microdata used in the published historical year-end pending-claimants CSV.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0003" source="PORTAL_SSA_OPEN_DATA" target="R147_E0001"><data key="edge_relationship_id">R147_R0003</data><data key="edge_source_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_relationship_type">publishes_historical_pending_claimant_csv</data><data key="edge_target_entity_id">R147_E0001</data><data key="edge_operational_context">Public CSV from June 1, 2018, catalog US-GOV-SSA-2372.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0004" source="R147_E0001" target="R147_E0002"><data key="edge_relationship_id">R147_R0004</data><data key="edge_source_entity_id">R147_E0001</data><data key="edge_relationship_type">requires_survivorship_count_interpretation</data><data key="edge_target_entity_id">R147_E0002</data><data key="edge_operational_context">End-year Total includes some deceased claimants whose cases stay open; Total Alive is separate.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0005" source="R147_E0001" target="R147_E0003"><data key="edge_relationship_id">R147_R0005</data><data key="edge_source_entity_id">R147_E0001</data><data key="edge_relationship_type">has_partial_2009_reporting_period</data><data key="edge_target_entity_id">R147_E0003</data><data key="edge_operational_context">FY2009 coverage is April through September only.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0006" source="R147_E0001" target="R147_E0006"><data key="edge_relationship_id">R147_R0006</data><data key="edge_source_entity_id">R147_E0001</data><data key="edge_relationship_type">uses_administrative_week_ended_fiscal_year</data><data key="edge_target_entity_id">R147_E0006</data><data key="edge_operational_context">Fiscal-year workload reports follow weekly cutoff conventions, occasionally 53 weeks.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0007" source="PORTAL_SSA_OPEN_DATA" target="R147_E0004"><data key="edge_relationship_id">R147_R0007</data><data key="edge_source_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_relationship_type">publishes_seven_historical_actuarial_csv_tables</data><data key="edge_target_entity_id">R147_E0004</data><data key="edge_operational_context">Seven CSV files corresponding to Actuarial Note 159 tables 1-7.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0008" source="R147_E0004" target="R147_E0005"><data key="edge_relationship_id">R147_R0008</data><data key="edge_source_entity_id">R147_E0004</data><data key="edge_relationship_type">requires_age_sex_adjusted_context</data><data key="edge_target_entity_id">R147_E0005</data><data key="edge_operational_context">Age-sex adjusted mortality risk and analysis of pending ALJ population, not raw death count alone.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0009" source="R147_E0004" target="R147_E0001"><data key="edge_relationship_id">R147_R0009</data><data key="edge_source_entity_id">R147_E0004</data><data key="edge_relationship_type">complements_claimant_population_denominator_series</data><data key="edge_target_entity_id">R147_E0001</data><data key="edge_operational_context">Seven-table mortality datasets complement the separate OHO end-of-FY pending-claimant dataset; do not imply individual record linkage in publicly released data.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R147_R0010" source="R147_E0004" target="R114_E030"><data key="edge_relationship_id">R147_R0010</data><data key="edge_source_entity_id">R147_E0004</data><data key="edge_relationship_type">provides_context_for_death_counts</data><data key="edge_target_entity_id">R114_E030</data><data key="edge_operational_context">Actuarial Note 159 provides machine-readable mortality tables supplementing the separate deaths-while-pending public CSV.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0011" source="REPORT_TRUSTEES_2026" target="R147_E0007"><data key="edge_relationship_id">R147_R0011</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">contains_vi_h1_oasi_disabled_beneficiary_table</data><data key="edge_target_entity_id">R147_E0007</data><data key="edge_operational_context">Published 2026 report includes VI.H1 historical 1960-2025 and estimated 2026-2035 scheduled benefit payment series.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0012" source="REPORT_TRUSTEES_2026" target="R147_E0008"><data key="edge_relationship_id">R147_R0012</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">contains_vi_h2_oasi_di_allocation_table</data><data key="edge_target_entity_id">R147_E0008</data><data key="edge_operational_context">Published 2026 report includes VI.H2 disability-related benefit payments by DI and OASI trust fund.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0013" source="R147_E0007" target="R147_E0009"><data key="edge_relationship_id">R147_R0013</data><data key="edge_source_entity_id">R147_E0007</data><data key="edge_relationship_type">applies_disability_specific_oasi_population_rule</data><data key="edge_target_entity_id">R147_E0009</data><data key="edge_operational_context">2025 OASI disabled-related beneficiary total excludes otherwise age-entitled disabled widows/widowers aged 60+.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0014" source="R147_E0008" target="R147_E0009"><data key="edge_relationship_id">R147_R0014</data><data key="edge_source_entity_id">R147_E0008</data><data key="edge_relationship_type">counts_oasi_disability_without_conflating_di_fund</data><data key="edge_target_entity_id">R147_E0009</data><data key="edge_operational_context">OASI disability-related payments are not paid by the DI Trust Fund and must be separately accounted for.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0015" source="R147_E0007" target="R147_E0010"><data key="edge_relationship_id">R147_R0015</data><data key="edge_source_entity_id">R147_E0007</data><data key="edge_relationship_type">normalizes_jan2021_calendar_payment_timing</data><data key="edge_target_entity_id">R147_E0010</data><data key="edge_operational_context">Earlier December 31 2020 physical disbursement treated as regularly scheduled Jan 3 2021 benefit for consistent calendar-year accounting.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0016" source="R147_E0008" target="R147_E0010"><data key="edge_relationship_id">R147_R0016</data><data key="edge_source_entity_id">R147_E0008</data><data key="edge_relationship_type">uses_normalized_calendar_disbursement_convention</data><data key="edge_target_entity_id">R147_E0010</data><data key="edge_operational_context">Source explicitly documents 2020-2021 payment date reclassification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0017" source="R147_E0007" target="R147_E0011"><data key="edge_relationship_id">R147_R0017</data><data key="edge_source_entity_id">R147_E0007</data><data key="edge_relationship_type">distinguishes_realized_history_from_intermediate_projection</data><data key="edge_target_entity_id">R147_E0011</data><data key="edge_operational_context">2026–2035 estimates not observed payments.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0018" source="R147_E0008" target="R147_E0011"><data key="edge_relationship_id">R147_R0018</data><data key="edge_source_entity_id">R147_E0008</data><data key="edge_relationship_type">uses_intermediate_assumption_estimates_2026_to_2035</data><data key="edge_target_entity_id">R147_E0011</data><data key="edge_operational_context">2026 OASI forecast $17.530 billion; actual may differ.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0019" source="R147_E0012" target="R147_E0013"><data key="edge_relationship_id">R147_R0019</data><data key="edge_source_entity_id">R147_E0012</data><data key="edge_relationship_type">publishes_quarterly_new_court_case_workload_xml</data><data key="edge_target_entity_id">R147_E0013</data><data key="edge_operational_context">OARO Appeals Council publishes NCC FY2026 receipts, dispositions and pending counts covering Sep 27 2025 to Jun 26 2026.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0020" source="R147_E0012" target="R147_E0014"><data key="edge_relationship_id">R147_R0020</data><data key="edge_source_entity_id">R147_E0012</data><data key="edge_relationship_type">publishes_quarterly_court_remand_workload_xml</data><data key="edge_target_entity_id">R147_E0014</data><data key="edge_operational_context">OARO Appeals Council publishes CR FY2026 receipts, dispositions and pending counts covering Sep 27 2025 to Jun 26 2026.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0021" source="R147_E0012" target="R147_E0015"><data key="edge_relationship_id">R147_R0021</data><data key="edge_source_entity_id">R147_E0012</data><data key="edge_relationship_type">prepares_administrative_records_for_new_court_suits</data><data key="edge_target_entity_id">R147_E0015</data><data key="edge_operational_context">Appeals Council sends certified administrative case records to federal court following new civil lawsuits.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0022" source="R147_E0013" target="R147_E0015"><data key="edge_relationship_id">R147_R0022</data><data key="edge_source_entity_id">R147_E0013</data><data key="edge_relationship_type">reflects_record_preparation_dispositions</data><data key="edge_target_entity_id">R147_E0015</data><data key="edge_operational_context">NCC disposition may include preparation of certified court record, AC-requested ALJ remand or another action.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0023" source="R147_E0014" target="R147_E0012"><data key="edge_relationship_id">R147_R0023</data><data key="edge_source_entity_id">R147_E0014</data><data key="edge_relationship_type">court_returned_cases_reviewed_by</data><data key="edge_target_entity_id">R147_E0012</data><data key="edge_operational_context">Courts return remanded cases to SSA Appeals Council for further administrative action.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0024" source="R147_E0012" target="R147_E0016"><data key="edge_relationship_id">R147_R0024</data><data key="edge_source_entity_id">R147_E0012</data><data key="edge_relationship_type">publishes_longitudinal_court_filing_and_remand_counts</data><data key="edge_target_entity_id">R147_E0016</data><data key="edge_operational_context">Public XML with fiscal-year filing and court-remand counts from 2010 through 2025.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0025" source="R147_E0016" target="R147_E0017"><data key="edge_relationship_id">R147_R0025</data><data key="edge_source_entity_id">R147_E0016</data><data key="edge_relationship_type">must_not_infer_filing_cohort_remand_rate</data><data key="edge_target_entity_id">R147_E0017</data><data key="edge_operational_context">Same-year remands may originate from lawsuits filed prior years; ratio not longitudinal cohort success.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0026" source="R147_E0012" target="R147_E0018"><data key="edge_relationship_id">R147_R0026</data><data key="edge_source_entity_id">R147_E0012</data><data key="edge_relationship_type">publishes_annual_ac_remand_share_series</data><data key="edge_target_entity_id">R147_E0018</data><data key="edge_operational_context">AC remands 15.54 percent of FY2025 AC requests-for-review dispositions; do not conflate with court remands.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0027" source="R147_E0018" target="R147_E0019"><data key="edge_relationship_id">R147_R0027</data><data key="edge_source_entity_id">R147_E0018</data><data key="edge_relationship_type">has_52_53_week_reporting_variants</data><data key="edge_target_entity_id">R147_E0019</data><data key="edge_operational_context">SSA publishes separate 52/53-week variants for FY2016 and FY2022.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0028" source="R147_E0016" target="R147_E0019"><data key="edge_relationship_id">R147_R0028</data><data key="edge_source_entity_id">R147_E0016</data><data key="edge_relationship_type">uses_52_53_week_fy_variants</data><data key="edge_target_entity_id">R147_E0019</data><data key="edge_operational_context">Annual court series includes 52/53-week FY2016/2022 variants.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0029" source="R147_E0013" target="R147_E0016"><data key="edge_relationship_id">R147_R0029</data><data key="edge_source_entity_id">R147_E0013</data><data key="edge_relationship_type">current_quarterly_counterpart_of_historical_annual_series</data><data key="edge_target_entity_id">R147_E0016</data><data key="edge_operational_context">FY2026 NCC reporting complements historical FY2010-2025 annual new court filing series; coverage and definitions differ.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0030" source="R147_E0014" target="R147_E0016"><data key="edge_relationship_id">R147_R0030</data><data key="edge_source_entity_id">R147_E0014</data><data key="edge_relationship_type">current_quarterly_remands_counterpart_of_historical_series</data><data key="edge_target_entity_id">R147_E0016</data><data key="edge_operational_context">FY2026 remand workload distinct from annual returns in public time series.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0031" source="DATA_AC_RR_PUBLIC" target="R147_E0018"><data key="edge_relationship_id">R147_R0031</data><data key="edge_source_entity_id">DATA_AC_RR_PUBLIC</data><data key="edge_relationship_type">review_disposition_history_published_as_remand_share</data><data key="edge_target_entity_id">R147_E0018</data><data key="edge_operational_context">Appeals Council review dispositions provide denominator for annual AC remand-share statistics.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R147_R0032" source="APP_CPMS" target="R147_E0004"><data key="edge_relationship_id">R147_R0032</data><data key="edge_source_entity_id">APP_CPMS</data><data key="edge_relationship_type">historically_supported_alj_mortality_analysis</data><data key="edge_target_entity_id">R147_E0004</data><data key="edge_operational_context">Actuarial mortality analyses concern OHO CPMS pending-claimant population in years 2006-2017, not a new production CPMS interface.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R147_R0033" source="R147_E0001" target="R114_E030"><data key="edge_relationship_id">R147_R0033</data><data key="edge_source_entity_id">R147_E0001</data><data key="edge_relationship_type">paired_historical_alj_population_and_death_measures</data><data key="edge_target_entity_id">R114_E030</data><data key="edge_operational_context">Published separately as datasets supporting Actuarial Note 159; do not infer individual-level linkage of public CSVs.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R148_R0001" source="DB_ARPS_MI" target="R148_E0001"><data key="edge_relationship_id">R148_R0001</data><data key="edge_source_entity_id">DB_ARPS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0001</data><data key="edge_operational_context">AC requests for review, receipts, dispositions and certain court-case metrics</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0002" source="DB_ARPS_MI" target="R148_E0002"><data key="edge_relationship_id">R148_R0002</data><data key="edge_source_entity_id">DB_ARPS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0002</data><data key="edge_operational_context">New court cases, court remands, and related adjusted receipt/disposition counts</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0003" source="DB_CPMS_MI" target="R148_E0003"><data key="edge_relationship_id">R148_R0003</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0003</data><data key="edge_operational_context">Hearing office workload, average processing time, dispositions, and reporting period fields</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0004" source="DB_ARPS_MI" target="R148_E0004"><data key="edge_relationship_id">R148_R0004</data><data key="edge_source_entity_id">DB_ARPS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0004</data><data key="edge_operational_context">Remand and grant-review reporting in the public data dictionary</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0005" source="DB_CPMS_MI" target="R148_E0005"><data key="edge_relationship_id">R148_R0005</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0005</data><data key="edge_operational_context">ALJ names and favorable, partially favorable and unfavorable disposition counts</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0006" source="DB_CPMS_MI" target="R148_E0006"><data key="edge_relationship_id">R148_R0006</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0006</data><data key="edge_operational_context">Counts of pending cases in electronic and paper formats</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0007" source="DB_CPMS_MI" target="R148_E0007"><data key="edge_relationship_id">R148_R0007</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0007</data><data key="edge_operational_context">Owning hearing office name shown in public hearing-office reports</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0008" source="DB_CPMS_MI" target="R148_E0008"><data key="edge_relationship_id">R148_R0008</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0008</data><data key="edge_operational_context">In-person hearings count in published data dictionary</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0009" source="DB_CPMS_MI" target="R148_E0009"><data key="edge_relationship_id">R148_R0009</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0009</data><data key="edge_operational_context">Video teleconference hearings count in published data dictionary</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0010" source="DB_CPMS_MI" target="R148_E0010"><data key="edge_relationship_id">R148_R0010</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0010</data><data key="edge_operational_context">Video hearing opt-out data source</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0011" source="DB_ARPS_MI" target="R148_E0011"><data key="edge_relationship_id">R148_R0011</data><data key="edge_source_entity_id">DB_ARPS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0011</data><data key="edge_operational_context">Remand reason information in public hearings dictionary</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0012" source="DB_ARPS_MI" target="R148_E0012"><data key="edge_relationship_id">R148_R0012</data><data key="edge_source_entity_id">DB_ARPS_MI</data><data key="edge_relationship_type">named_as_mi_table_source_in_public_dictionary</data><data key="edge_target_entity_id">R148_E0012</data><data key="edge_operational_context">Remand reason category source used for top ten remand reports</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0013" source="R148_E0003" target="R148_E0013"><data key="edge_relationship_id">R148_R0013</data><data key="edge_source_entity_id">R148_E0003</data><data key="edge_relationship_type">documented_mi_source_of_published_field</data><data key="edge_target_entity_id">R148_E0013</data><data key="edge_operational_context">SMALLINT NOT NULL; calendar days from hearing request date to disposition date; not days of employee processing time</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0014" source="R148_E0001" target="R148_E0014"><data key="edge_relationship_id">R148_R0014</data><data key="edge_source_entity_id">R148_E0001</data><data key="edge_relationship_type">documented_mi_source_of_published_field</data><data key="edge_target_entity_id">R148_E0014</data><data key="edge_operational_context">INTEGER NOT NULL; adjusted receipts, not necessarily gross new receipts</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0015" source="R148_E0003" target="R148_E0015"><data key="edge_relationship_id">R148_R0015</data><data key="edge_source_entity_id">R148_E0003</data><data key="edge_relationship_type">documented_mi_source_of_published_field</data><data key="edge_target_entity_id">R148_E0015</data><data key="edge_operational_context">INTEGER NOT NULL; excludes cases in CLSD status</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0016" source="R148_E0006" target="R148_E0016"><data key="edge_relationship_id">R148_R0016</data><data key="edge_source_entity_id">R148_E0006</data><data key="edge_relationship_type">documented_mi_source_of_published_field</data><data key="edge_target_entity_id">R148_E0016</data><data key="edge_operational_context">INTEGER NOT NULL; electronic-format cases pending at end of period</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0017" source="R148_E0006" target="R148_E0017"><data key="edge_relationship_id">R148_R0017</data><data key="edge_source_entity_id">R148_E0006</data><data key="edge_relationship_type">documented_mi_source_of_published_field</data><data key="edge_target_entity_id">R148_E0017</data><data key="edge_operational_context">INTEGER NOT NULL; paper-format cases pending at end of period</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0018" source="R148_E0003" target="R148_E0018"><data key="edge_relationship_id">R148_R0018</data><data key="edge_source_entity_id">R148_E0003</data><data key="edge_relationship_type">documented_mi_source_of_published_field</data><data key="edge_target_entity_id">R148_E0018</data><data key="edge_operational_context">INTEGER NOT NULL; judge-wide total can differ from office-specific judge disposition count</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0019" source="R148_E0003" target="R148_E0019"><data key="edge_relationship_id">R148_R0019</data><data key="edge_source_entity_id">R148_E0003</data><data key="edge_relationship_type">documented_mi_source_of_published_field</data><data key="edge_target_entity_id">R148_E0019</data><data key="edge_operational_context">DECIMAL(5,2) NOT NULL; mean per-day dispositions, not judge-specific work time</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0020" source="R148_E0012" target="R148_E0020"><data key="edge_relationship_id">R148_R0020</data><data key="edge_source_entity_id">R148_E0012</data><data key="edge_relationship_type">documented_mi_source_of_published_field</data><data key="edge_target_entity_id">R148_E0020</data><data key="edge_operational_context">CHAR (MULTIPLE) NOT NULL; remand reason category in AC and federal-court reports</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0021" source="R148_E0013" target="R148_E0021"><data key="edge_relationship_id">R148_R0021</data><data key="edge_source_entity_id">R148_E0013</data><data key="edge_relationship_type">defined_by_measurement_rule</data><data key="edge_target_entity_id">R148_E0021</data><data key="edge_operational_context">SSA public data dictionary explicitly defines the hearing-request-date to disposition-date interval.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0022" source="DATA_OHO_WORKLOAD_PUBLIC" target="R148_E0013"><data key="edge_relationship_id">R148_R0022</data><data key="edge_source_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_relationship_type">reports_processing_time_using</data><data key="edge_target_entity_id">R148_E0013</data><data key="edge_operational_context">Published hearing-office workload is linked in SSA dictionary to DSPN_AVGPT, not end-to-end claim processing time.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0023" source="DATA_OHO_WORKLOAD_PUBLIC" target="R148_E0014"><data key="edge_relationship_id">R148_R0023</data><data key="edge_source_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_relationship_type">reports_adjusted_receipts_using</data><data key="edge_target_entity_id">R148_E0014</data><data key="edge_operational_context">Receipts may reflect adjusted office work transfers; not a gross intake measure.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0024" source="DATA_OHO_WORKLOAD_PUBLIC" target="R148_E0015"><data key="edge_relationship_id">R148_R0024</data><data key="edge_source_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_relationship_type">reports_pending_at_period_end_using</data><data key="edge_target_entity_id">R148_E0015</data><data key="edge_operational_context">Pending means not closed (CLSD) at end of report period.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0025" source="DATA_OHO_WORKLOAD_PUBLIC" target="R148_E0022"><data key="edge_relationship_id">R148_R0025</data><data key="edge_source_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_relationship_type">related_public_office_processing_time_ranking</data><data key="edge_target_entity_id">R148_E0022</data><data key="edge_operational_context">Both public FY2026 OHO outputs describe hearing-office workload and processing-time statistics through the reported cutoff.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0026" source="R148_E0022" target="R148_E0013"><data key="edge_relationship_id">R148_R0026</data><data key="edge_source_entity_id">R148_E0022</data><data key="edge_relationship_type">uses_statistical_measure</data><data key="edge_target_entity_id">R148_E0013</data><data key="edge_operational_context">Dictionary maps the mean calendar-day processing-time measure to this ranking report.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0027" source="R148_E0023" target="R148_E0019"><data key="edge_relationship_id">R148_R0027</data><data key="edge_source_entity_id">R148_E0023</data><data key="edge_relationship_type">reports_dispositions_per_day_using</data><data key="edge_target_entity_id">R148_E0019</data><data key="edge_operational_context">SSA dictionary maps the daily average ALJ disposition count to the ranking report.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0028" source="APP_ERPS" target="R148_E0024"><data key="edge_relationship_id">R148_R0028</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">codes_certain_businesses_as_individual_payees</data><data key="edge_target_entity_id">R148_E0024</data><data key="edge_operational_context">eRPS classification depends on legal entity form and contact partner, not EIN presence alone.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0029" source="DATA_ERPS_INDIVIDUAL_ID" target="R148_E0024"><data key="edge_relationship_id">R148_R0029</data><data key="edge_source_entity_id">DATA_ERPS_INDIVIDUAL_ID</data><data key="edge_relationship_type">identifies_sole_proprietorship_or_partnership_under_owner_ssn</data><data key="edge_target_entity_id">R148_E0024</data><data key="edge_operational_context">Owner or contact general partner SSN is the identifier for relevant business types.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0030" source="APP_ERPS" target="R148_E0025"><data key="edge_relationship_id">R148_R0030</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">applies_single_identifier_for_joint_guardians</data><data key="edge_target_entity_id">R148_E0025</data><data key="edge_operational_context">Second guardian is represented by annotation, not by second primary case key.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0031" source="UI_ERPS_PAYMENT_LEGEND" target="R148_E0025"><data key="edge_relationship_id">R148_R0031</data><data key="edge_source_entity_id">UI_ERPS_PAYMENT_LEGEND</data><data key="edge_relationship_type">records_court_ordered_joint_guardian_legend</data><data key="edge_target_entity_id">R148_E0025</data><data key="edge_operational_context">For joint guardians, display payment legend preference as in court order.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0032" source="DATA_ERPS_ORG_ID" target="R148_E0026"><data key="edge_relationship_id">R148_R0032</data><data key="edge_source_entity_id">DATA_ERPS_ORG_ID</data><data key="edge_relationship_type">uses_physical_business_location_zip_not_beneficiary_address</data><data key="edge_target_entity_id">R148_E0026</data><data key="edge_operational_context">The organization location ZIP is an identifier component, not residence or mailing address of each beneficiary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0033" source="APP_ERPS" target="R148_E0026"><data key="edge_relationship_id">R148_R0033</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">documented_organization_identifier_composition</data><data key="edge_target_entity_id">R148_E0026</data><data key="edge_operational_context">eRPS uses a ZIP-based organization ID despite documentation of verified EIN.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0034" source="APP_IMAIN" target="R148_E0027"><data key="edge_relationship_id">R148_R0034</data><data key="edge_source_entity_id">APP_IMAIN</data><data key="edge_relationship_type">claims_entry_point_for</data><data key="edge_target_entity_id">R148_E0027</data><data key="edge_operational_context">Claims verification through I-Main, not proof of direct update to Numident.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0035" source="APP_SSNAP" target="R148_E0027"><data key="edge_relationship_id">R148_R0035</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">enumeration_entry_point_for</data><data key="edge_target_entity_id">R148_E0027</data><data key="edge_operational_context">SSNAP is the separately documented SAVE entry route for enumeration.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0036" source="R148_E0027" target="SVC_SAVE"><data key="edge_relationship_id">R148_R0036</data><data key="edge_source_entity_id">R148_E0027</data><data key="edge_relationship_type">queries_external_immigration_status_service</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">SAVE supplies immigration/document verification, not program eligibility determinations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0037" source="DATA_SAVE_QUERY_RESPONSE" target="R148_E0028"><data key="edge_relationship_id">R148_R0037</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">filed_as_claims_documentation_through</data><data key="edge_target_entity_id">R148_E0028</data><data key="edge_operational_context">The documented response printout and document copies support claim evidence, not physical custody of original immigration document.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0038" source="APP_EVIEW" target="R148_E0028"><data key="edge_relationship_id">R148_R0038</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">permitted_retrieval_of_documented_claims_verification</data><data key="edge_target_entity_id">R148_E0028</data><data key="edge_operational_context">SSA instructions name eView as an electronic folder example; no live inter-system synchronization inferred.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0039" source="DATA_PI_ARN" target="R148_E0028"><data key="edge_relationship_id">R148_R0039</data><data key="edge_source_entity_id">DATA_PI_ARN</data><data key="edge_relationship_type">is_claims_entered_dhs_document_identifier_under</data><data key="edge_target_entity_id">R148_E0028</data><data key="edge_operational_context">When a DHS document contains an Alien Registration Number, claims instructions call for entry in Person Information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0040" source="SVC_SAVE" target="R148_E0029"><data key="edge_relationship_id">R148_R0040</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">unconfirmed_online_status_requires_additional_evidence_before_action</data><data key="edge_target_entity_id">R148_E0029</data><data key="edge_operational_context">Online response is evidence for development and does not itself decide lawful-presence entitlement.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0041" source="FORM_G845" target="R148_E0029"><data key="edge_relationship_id">R148_R0041</data><data key="edge_source_entity_id">FORM_G845</data><data key="edge_relationship_type">used_for_secondary_verification_after</data><data key="edge_target_entity_id">R148_E0029</data><data key="edge_operational_context">Form G-845 and supplement may be required when SAVE response does not resolve status.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0042" source="SVC_SAVE" target="R148_E0030"><data key="edge_relationship_id">R148_R0042</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">supports_category_specific_lawful_presence_reverification</data><data key="edge_target_entity_id">R148_E0030</data><data key="edge_operational_context">2026 lawful presence evidence table establishes varying recheck conditions by status and document.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0043" source="APP_ERPS" target="R148_E0031"><data key="edge_relationship_id">R148_R0043</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">tracks_fiduciary_relationship_for</data><data key="edge_target_entity_id">R148_E0031</data><data key="edge_operational_context">eRPS Relationship Details notes hold ABLE title reflecting beneficiary ownership and payee fiduciary role.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0044" source="UI_ERPS_RELATIONSHIP_DETAILS" target="R148_E0031"><data key="edge_relationship_id">R148_R0044</data><data key="edge_source_entity_id">UI_ERPS_RELATIONSHIP_DETAILS</data><data key="edge_relationship_type">records_able_account_fiduciary_title_under</data><data key="edge_target_entity_id">R148_E0031</data><data key="edge_operational_context">POMS calls for note of ABLE account title in Relationship Details tab.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0045" source="R148_E0031" target="R148_E0032"><data key="edge_relationship_id">R148_R0045</data><data key="edge_source_entity_id">R148_E0031</data><data key="edge_relationship_type">signature_authority_loss_triggers</data><data key="edge_target_entity_id">R148_E0032</data><data key="edge_operational_context">ABLE designated beneficiary may replace the signatory, removing the payee ability to manage account or use it for direct deposit.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0046" source="UI_ERPS_BENE_DETAILS" target="R148_E0032"><data key="edge_relationship_id">R148_R0046</data><data key="edge_source_entity_id">UI_ERPS_BENE_DETAILS</data><data key="edge_relationship_type">captures_follow_up_report_of_contact_for</data><data key="edge_target_entity_id">R148_E0032</data><data key="edge_operational_context">POMS calls for Report of Contact in eRPS Beneficiary Details and potentially new payee evaluation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0047" source="APP_ERPS" target="R148_E0033"><data key="edge_relationship_id">R148_R0047</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">representative_accounting_guidance_is_separate_from</data><data key="edge_target_entity_id">R148_E0033</data><data key="edge_operational_context">Guidance concerns payee records and use of funds, not established eRPS bank transaction import.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0048" source="R148_E0031" target="R148_E0034"><data key="edge_relationship_id">R148_R0048</data><data key="edge_source_entity_id">R148_E0031</data><data key="edge_relationship_type">change_of_payee_requires_special_funds_disposition</data><data key="edge_target_entity_id">R148_E0034</data><data key="edge_operational_context">SSA distinguishes transferring account control from withdrawing funds and re-depositing under annual ABLE contribution rules.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0049" source="SYS_MBR" target="R148_E0035"><data key="edge_relationship_id">R148_R0049</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">full_population_source_for_representative_payee_statistical_table</data><data key="edge_target_entity_id">R148_E0035</data><data key="edge_operational_context">Table 5.L1 explicitly sourced to MBR 100 percent data; counts use beneficiary types, not organization ZIP location.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0050" source="R148_E0035" target="APP_ERPS"><data key="edge_relationship_id">R148_R0050</data><data key="edge_source_entity_id">R148_E0035</data><data key="edge_relationship_type">counts_payees_as_associated_beneficiaries_not_unique_payees</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Table counts beneficiary records with payees; it is not a census of payee organizations and does not establish eRPS as statistical source.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0051" source="R148_E0018" target="R148_E0036"><data key="edge_relationship_id">R148_R0051</data><data key="edge_source_entity_id">R148_E0018</data><data key="edge_relationship_type">subject_to_cross_office_reporting_rule</data><data key="edge_target_entity_id">R148_E0036</data><data key="edge_operational_context">Judge-level office counts cannot simply be equated with an individual ALJ total across all locations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R148_R0052" source="R148_E0023" target="R148_E0036"><data key="edge_relationship_id">R148_R0052</data><data key="edge_source_entity_id">R148_E0023</data><data key="edge_relationship_type">needs_location_and_workday_caveat</data><data key="edge_target_entity_id">R148_E0036</data><data key="edge_operational_context">Ranking is office-based and only reflects available fiscal YTD; not a nationwide single-judge productivity ranking.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented source relationship; no undocumented deployment, synchronization or storage mechanism asserted.</data></edge><edge id="R149_R0001" source="SYS_MBR" target="R149_E0001"><data key="edge_relationship_id">R149_R0001</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">can_contain</data><data key="edge_target_entity_id">R149_E0001</data><data key="edge_operational_context">Field-office in-person-only safety marker may appear on Master Beneficiary Record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0002" source="SYS_SSR" target="R149_E0001"><data key="edge_relationship_id">R149_R0002</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">can_contain</data><data key="edge_target_entity_id">R149_E0001</data><data key="edge_operational_context">Field-office in-person-only safety marker may appear on Supplemental Security Record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0003" source="R149_E0001" target="R149_E0002"><data key="edge_relationship_id">R149_R0003</data><data key="edge_source_entity_id">R149_E0001</data><data key="edge_relationship_type">requires_documented_consent</data><data key="edge_target_entity_id">R149_E0002</data><data key="edge_operational_context">In-person-only handling requires beneficiary-signed request or qualifying field-office determination with signed documentation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0004" source="R149_E0002" target="REPO_NDRED"><data key="edge_relationship_id">R149_R0004</data><data key="edge_source_entity_id">R149_E0002</data><data key="edge_relationship_type">scanned_as_evidence_into</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Field offices scan the signed in-person-only request to NDRed when appropriate.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0005" source="R149_E0002" target="REPO_EF"><data key="edge_relationship_id">R149_R0005</data><data key="edge_source_entity_id">R149_E0002</data><data key="edge_relationship_type">may_be_scanned_as_evidence_into</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">SSA allows eView as the appropriate record location for signed in-person-only contact evidence; this entity represents the existing electronic folder family, not a new folder.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0006" source="R149_E0001" target="R149_E0003"><data key="edge_relationship_id">R149_R0006</data><data key="edge_source_entity_id">R149_E0001</data><data key="edge_relationship_type">enforces_no_telephone_or_mail_disclosure</data><data key="edge_target_entity_id">R149_E0003</data><data key="edge_operational_context">Telephone contact may not produce disclosure, mail to address of record, or a record change while protected in-person-only flag applies.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0007" source="R149_E0001" target="R149_E0004"><data key="edge_relationship_id">R149_R0007</data><data key="edge_source_entity_id">R149_E0001</data><data key="edge_relationship_type">prohibits_password_field_workaround</data><data key="edge_target_entity_id">R149_E0004</data><data key="edge_operational_context">MBR/SSR special messages no longer support customer-chosen passwords or phrases.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0008" source="R149_E0001" target="R149_E0005"><data key="edge_relationship_id">R149_R0008</data><data key="edge_source_entity_id">R149_E0001</data><data key="edge_relationship_type">subject_to_routine_use_and_electronic_service_exceptions</data><data key="edge_target_entity_id">R149_E0005</data><data key="edge_operational_context">Routine uses authorized under Privacy Act and independently authenticated online/IVR services are not categorically prohibited by the in-person flag.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0009" source="R149_E0006" target="R149_E0007"><data key="edge_relationship_id">R149_R0009</data><data key="edge_source_entity_id">R149_E0006</data><data key="edge_relationship_type">limits_scope_through</data><data key="edge_target_entity_id">R149_E0007</data><data key="edge_operational_context">SSA directs staff to request only material needed to satisfy the pending-hearing access request.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0010" source="R149_E0006" target="R149_E0008"><data key="edge_relationship_id">R149_R0010</data><data key="edge_source_entity_id">R149_E0006</data><data key="edge_relationship_type">may_provide</data><data key="edge_target_entity_id">R149_E0008</data><data key="edge_operational_context">Claimants and representatives can receive copies of hearing audio on compact disc.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0011" source="R149_E0006" target="R149_E0009"><data key="edge_relationship_id">R149_R0011</data><data key="edge_source_entity_id">R149_E0006</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R149_E0009</data><data key="edge_operational_context">Claimants can request hearing evidence, but transcript preparation is normally conditional on ALJ case need.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0012" source="R149_E0008" target="R149_E0009"><data key="edge_relationship_id">R149_R0012</data><data key="edge_source_entity_id">R149_E0008</data><data key="edge_relationship_type">does_not_imply</data><data key="edge_target_entity_id">R149_E0009</data><data key="edge_operational_context">A recorded hearing does not itself establish an automatically generated transcript.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0013" source="R149_E0006" target="REPO_EF"><data key="edge_relationship_id">R149_R0013</data><data key="edge_source_entity_id">R149_E0006</data><data key="edge_relationship_type">draws_from</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Policy permits hearing unit to transmit electronic copies of needed folder material for access requests.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0014" source="R149_E0010" target="R149_E0011"><data key="edge_relationship_id">R149_R0014</data><data key="edge_source_entity_id">R149_E0010</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R149_E0011</data><data key="edge_operational_context">OACT index identifies actuarial note 2026.6 published July 2026.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0015" source="R149_E0010" target="R149_E0012"><data key="edge_relationship_id">R149_R0015</data><data key="edge_source_entity_id">R149_E0010</data><data key="edge_relationship_type">has_publication_immutability_guidance</data><data key="edge_target_entity_id">R149_E0012</data><data key="edge_operational_context">OACT warns actuarial notes are historical artifacts and generally not revised.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0016" source="R149_E0011" target="R149_E0012"><data key="edge_relationship_id">R149_R0016</data><data key="edge_source_entity_id">R149_E0011</data><data key="edge_relationship_type">subject_to_pdf_distribution_policy</data><data key="edge_target_entity_id">R149_E0012</data><data key="edge_operational_context">OACT says updated actuarial notes are distributed in PDF format; no inference about model software or internal data store.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0017" source="R149_E0013" target="EX_SASRO"><data key="edge_relationship_id">R149_R0017</data><data key="edge_source_entity_id">R149_E0013</data><data key="edge_relationship_type">governs_single_electronic_state_record_queries</data><data key="edge_target_entity_id">EX_SASRO</data><data key="edge_operational_context">SASRO IEA authorizes specific one-off state queries for SSA program tasks; individual master file field/update outcomes are not enumerated in general policy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0018" source="R149_E0013" target="SYS_MBR"><data key="edge_relationship_id">R149_R0018</data><data key="edge_source_entity_id">R149_E0013</data><data key="edge_relationship_type">does_not_independently_establish_address_auto_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Generic SSA-file updating purpose in SASRO IEA does not establish automated MBR address synchronization.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0019" source="R149_E0013" target="SYS_SSR"><data key="edge_relationship_id">R149_R0019</data><data key="edge_source_entity_id">R149_E0013</data><data key="edge_relationship_type">does_not_independently_establish_address_auto_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Generic state-record query permission does not establish automated SSR address synchronization.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0020" source="R149_E0014" target="SYS_MBR"><data key="edge_relationship_id">R149_R0020</data><data key="edge_source_entity_id">R149_E0014</data><data key="edge_relationship_type">supports_program_processing_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">State foster-care changes support representative-payee choices for minor SSA beneficiaries; no direct MBR field update asserted.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0021" source="R149_E0015" target="EX_STATE_ABLE_MONTHLY"><data key="edge_relationship_id">R149_R0021</data><data key="edge_source_entity_id">R149_E0015</data><data key="edge_relationship_type">governs_state_reporting_through</data><data key="edge_target_entity_id">EX_STATE_ABLE_MONTHLY</data><data key="edge_operational_context">ABLE IEA category covers statement/account balance information for SSI resources; cadence depends on implemented agreement.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0022" source="R149_E0016" target="ORG_STATE_DMV"><data key="edge_relationship_id">R149_R0022</data><data key="edge_source_entity_id">R149_E0016</data><data key="edge_relationship_type">provides_partial_ssn_and_death_verification_for</data><data key="edge_target_entity_id">ORG_STATE_DMV</data><data key="edge_operational_context">For voter applicant without qualifying driver license, state MVA may request name DOB last-four SSN match and death flag.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0023" source="R149_E0017" target="PLAT_ICON_HUB"><data key="edge_relationship_id">R149_R0023</data><data key="edge_source_entity_id">R149_E0017</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PLAT_ICON_HUB</data><data key="edge_operational_context">Interstate Benefit Inquiry IEA allows SSA to use ICON as a state unemployment and wages query channel.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0024" source="R149_E0018" target="ORG_STATE_DMV"><data key="edge_relationship_id">R149_R0024</data><data key="edge_source_entity_id">R149_E0018</data><data key="edge_relationship_type">sends_overnight_batch_verification_to</data><data key="edge_target_entity_id">ORG_STATE_DMV</data><data key="edge_operational_context">MVA IEA names overnight SSN verification support for driver licensing and state identification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0025" source="R149_E0019" target="ORG_AAMVA"><data key="edge_relationship_id">R149_R0025</data><data key="edge_source_entity_id">R149_E0019</data><data key="edge_relationship_type">connects_via</data><data key="edge_target_entity_id">ORG_AAMVA</data><data key="edge_operational_context">AAMVA supplies state SSN verification connectivity billing and help desk under SSOLV agreements.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0026" source="R149_E0019" target="ORG_STATE_DMV"><data key="edge_relationship_id">R149_R0026</data><data key="edge_source_entity_id">R149_E0019</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_STATE_DMV</data><data key="edge_operational_context">AAMVA-linked SSA SSOLV supports eligible state motor vehicle agencies.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0027" source="R149_E0020" target="R149_E0021"><data key="edge_relationship_id">R149_R0027</data><data key="edge_source_entity_id">R149_E0020</data><data key="edge_relationship_type">must_undergo</data><data key="edge_target_entity_id">R149_E0021</data><data key="edge_operational_context">OIS must carry out a security compliance review of STC once every three years.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0028" source="R149_E0020" target="ORG_STATE_DMV"><data key="edge_relationship_id">R149_R0028</data><data key="edge_source_entity_id">R149_E0020</data><data key="edge_relationship_type">acts_as_conduit_for</data><data key="edge_target_entity_id">ORG_STATE_DMV</data><data key="edge_operational_context">The defined state transmission component transfers only specifically approved data to the specified state recipient agencies; DMV used as existing class for state-agency example, not universal recipient.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0029" source="R149_E0022" target="R149_E0024"><data key="edge_relationship_id">R149_R0029</data><data key="edge_source_entity_id">R149_E0022</data><data key="edge_relationship_type">requires_periodic</data><data key="edge_target_entity_id">R149_E0024</data><data key="edge_operational_context">IEA-F state-administered program agreement must be accompanied by updated compliance certification each 30 months.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0030" source="R149_E0023" target="R149_E0024"><data key="edge_relationship_id">R149_R0030</data><data key="edge_source_entity_id">R149_E0023</data><data key="edge_relationship_type">requires_periodic</data><data key="edge_target_entity_id">R149_E0024</data><data key="edge_operational_context">IEA-S state-administered program agreement must be accompanied by updated compliance certification each 30 months.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0031" source="R149_E0025" target="R149_E0022"><data key="edge_relationship_id">R149_R0031</data><data key="edge_source_entity_id">R149_E0025</data><data key="edge_relationship_type">separates_research_data_from_program_matching</data><data key="edge_target_entity_id">R149_E0022</data><data key="edge_operational_context">Research MOU/MOA uses differ from IEA-F federally funded state benefit eligibility matching arrangements.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0032" source="PROC_SSA_GRANT_APPLICATION" target="R149_E0026"><data key="edge_relationship_id">R149_R0032</data><data key="edge_source_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="edge_relationship_type">routes_competitive_apps_through</data><data key="edge_target_entity_id">R149_E0026</data><data key="edge_operational_context">Competitive grant reviewers conduct external expert peer reviews after verifying registration and application completeness.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0033" source="PROC_SSA_GRANT_APPLICATION" target="R149_E0027"><data key="edge_relationship_id">R149_R0033</data><data key="edge_source_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R149_E0027</data><data key="edge_operational_context">Applicant must provide budget justification and a calculation-based detail worksheet.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0034" source="PROC_SSA_GRANT_APPLICATION" target="R149_E0028"><data key="edge_relationship_id">R149_R0034</data><data key="edge_source_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="edge_relationship_type">continuation_review_requires</data><data key="edge_target_entity_id">R149_E0028</data><data key="edge_operational_context">Continuation grants have prior-year program and SF-425 financial submission checks.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0035" source="R149_E0028" target="FORM_SF425"><data key="edge_relationship_id">R149_R0035</data><data key="edge_source_entity_id">R149_E0028</data><data key="edge_relationship_type">checks_reporting_document</data><data key="edge_target_entity_id">FORM_SF425</data><data key="edge_operational_context">Grants officer checks prior-year SF-425 before applicable continuation award.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R149_R0036" source="R149_E0027" target="SVC_GRANTS_GOV"><data key="edge_relationship_id">R149_R0036</data><data key="edge_source_entity_id">R149_E0027</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SVC_GRANTS_GOV</data><data key="edge_operational_context">Competitive grant submission uses Grants.gov; budget material belongs to application package, not claimed automatic cross-system transfer.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Published policy describes relationship or control; avoid inference beyond source.</data></edge><edge id="R150_R0001" source="SYS_NUMIDENT" target="R150_E0001"><data key="edge_relationship_id">R150_R0001</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">correction_triggers_employee_update</data><data key="edge_target_entity_id">R150_E0001</data><data key="edge_operational_context">SSA directs an employee to update program records after a qualifying Numident sex-code correction; no automatic update claimed.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0002" source="R150_E0001" target="SYS_MBR"><data key="edge_relationship_id">R150_R0002</data><data key="edge_source_entity_id">R150_E0001</data><data key="edge_relationship_type">requires_program_record_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Employee must apply consistent sex-code designation to relevant program record following a Numident correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0003" source="R150_E0001" target="SYS_SSR"><data key="edge_relationship_id">R150_R0003</data><data key="edge_source_entity_id">R150_E0001</data><data key="edge_relationship_type">requires_program_record_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Employee must apply consistent sex-code designation to relevant program record following a Numident correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0004" source="R150_E0001" target="APP_RPS"><data key="edge_relationship_id">R150_R0004</data><data key="edge_source_entity_id">R150_E0001</data><data key="edge_relationship_type">requires_program_record_update</data><data key="edge_target_entity_id">APP_RPS</data><data key="edge_operational_context">Employee must apply consistent sex-code designation to relevant program record following a Numident correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0005" source="SYS_NUMIDENT" target="R150_E0002"><data key="edge_relationship_id">R150_R0005</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">parent_name_correction_triggers_review</data><data key="edge_target_entity_id">R150_E0002</data><data key="edge_operational_context">A change to a child parent name in Numident prompts review of beneficiary/payee attributes if applicable.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0006" source="R150_E0002" target="SYS_MBR"><data key="edge_relationship_id">R150_R0006</data><data key="edge_source_entity_id">R150_E0002</data><data key="edge_relationship_type">requires_conditional_review_not_auto_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Review potentially affected program record and initiate an update only if factually and procedurally necessary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0007" source="R150_E0002" target="SYS_SSR"><data key="edge_relationship_id">R150_R0007</data><data key="edge_source_entity_id">R150_E0002</data><data key="edge_relationship_type">requires_conditional_review_not_auto_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Review potentially affected program record and initiate an update only if factually and procedurally necessary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0008" source="R150_E0002" target="APP_RPS"><data key="edge_relationship_id">R150_R0008</data><data key="edge_source_entity_id">R150_E0002</data><data key="edge_relationship_type">requires_conditional_review_not_auto_update</data><data key="edge_target_entity_id">APP_RPS</data><data key="edge_operational_context">Review potentially affected program record and initiate an update only if factually and procedurally necessary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0009" source="APP_SSNAP" target="R150_E0003"><data key="edge_relationship_id">R150_R0009</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">records_numident_change_evidence</data><data key="edge_target_entity_id">R150_E0003</data><data key="edge_operational_context">SSNAP remarks include details of supporting identity/evidence documents not otherwise captured.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0010" source="APP_MAPS" target="R150_E0004"><data key="edge_relationship_id">R150_R0010</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">receives_tax_interest_not_account_balance</data><data key="edge_target_entity_id">R150_E0004</data><data key="edge_operational_context">IRS 1099-INT/1099-DIV transfer is an income observation, not a direct bank-balance verification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0011" source="R150_E0004" target="R150_E0005"><data key="edge_relationship_id">R150_R0011</data><data key="edge_source_entity_id">R150_E0004</data><data key="edge_relationship_type">inputs_balance_estimation</data><data key="edge_target_entity_id">R150_E0005</data><data key="edge_operational_context">SSA computes an approximate account balance from matched account interest amounts.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0012" source="R150_E0005" target="R150_E0006"><data key="edge_relationship_id">R150_R0012</data><data key="edge_source_entity_id">R150_E0005</data><data key="edge_relationship_type">comparison_input</data><data key="edge_target_entity_id">R150_E0006</data><data key="edge_operational_context">Derived agency estimated resources compared with applicant resource allegations for verification routing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0013" source="R150_E0007" target="R150_E0006"><data key="edge_relationship_id">R150_R0013</data><data key="edge_source_entity_id">R150_E0007</data><data key="edge_relationship_type">comparison_input</data><data key="edge_target_entity_id">R150_E0006</data><data key="edge_operational_context">Applicant-reported resource values form the separate application side of tolerance comparison.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0014" source="R150_E0006" target="R150_E0008"><data key="edge_relationship_id">R150_R0014</data><data key="edge_source_entity_id">R150_E0006</data><data key="edge_relationship_type">conditionally_triggers</data><data key="edge_target_entity_id">R150_E0008</data><data key="edge_operational_context">MAPS sends cases for verification when applicant and agency resource figures meet discrepancy criteria.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0015" source="R150_E0008" target="R150_E0009"><data key="edge_relationship_id">R150_R0015</data><data key="edge_source_entity_id">R150_E0008</data><data key="edge_relationship_type">uses_source_disambiguation</data><data key="edge_target_entity_id">R150_E0009</data><data key="edge_operational_context">Technician retrieves underlying source through Medicare query rather than relying on aggregate balance label.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0016" source="R150_E0008" target="UI_MAPS_DWRC"><data key="edge_relationship_id">R150_R0016</data><data key="edge_source_entity_id">R150_E0008</data><data key="edge_relationship_type">documents_verification</data><data key="edge_target_entity_id">UI_MAPS_DWRC</data><data key="edge_operational_context">MAPS report of contact records outreach, resource evidence and decisions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0017" source="R150_E0008" target="R150_E0010"><data key="edge_relationship_id">R150_R0017</data><data key="edge_source_entity_id">R150_E0008</data><data key="edge_relationship_type">completes</data><data key="edge_target_entity_id">R150_E0010</data><data key="edge_operational_context">Unresolved discrepancies follow documented action rather than automatic IRS-source bank-balance acceptance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0018" source="R150_E0010" target="APP_MAPS"><data key="edge_relationship_id">R150_R0018</data><data key="edge_source_entity_id">R150_E0010</data><data key="edge_relationship_type">implemented_in</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">Documented MAPS selection and submit-to-subsidy workflow.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0019" source="EX_CMA1305_IRS_PARTD" target="R150_E0004"><data key="edge_relationship_id">R150_R0019</data><data key="edge_source_entity_id">EX_CMA1305_IRS_PARTD</data><data key="edge_relationship_type">supplies_irs_income_comparison_observation</data><data key="edge_target_entity_id">R150_E0004</data><data key="edge_operational_context">IRS information is used by Medicare Extra Help verification, subject to matching agreements and rules.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R150_R0020" source="PROC_CPAS" target="R150_E0011"><data key="edge_relationship_id">R150_R0020</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">requires_submitter_capability</data><data key="edge_target_entity_id">R150_E0011</data><data key="edge_operational_context">Commercial signatures require submitter-capable audit evidence separate from signing page submitted with application.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0021" source="R150_E0011" target="R150_E0012"><data key="edge_relationship_id">R150_R0021</data><data key="edge_source_entity_id">R150_E0011</data><data key="edge_relationship_type">subject_to_submitter_retention</data><data key="edge_target_entity_id">R150_E0012</data><data key="edge_operational_context">Retention clock begins at SSA submission date; no assertion SSA retains the submitter archive.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0022" source="PROC_CPAS" target="R150_E0013"><data key="edge_relationship_id">R150_R0022</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">requires_per_form_submitted_certificate_when_needed</data><data key="edge_target_entity_id">R150_E0013</data><data key="edge_operational_context">Each applicable form in a bundle needs its own appended certification page.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0023" source="PROC_CPAS" target="R150_E0014"><data key="edge_relationship_id">R150_R0023</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">requires_original_trail_before_fraud_referral</data><data key="edge_target_entity_id">R150_E0014</data><data key="edge_operational_context">Original digital certificate requested from submitter prior to suspected-issue referral.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0024" source="APP_RASR" target="R150_E0015"><data key="edge_relationship_id">R150_R0024</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">has_creation_only_cpas_coding</data><data key="edge_target_entity_id">R150_E0015</data><data key="edge_operational_context">RASR only displays CPAS coding checkbox for initial appointment entry.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0025" source="R150_E0015" target="APP_MCS"><data key="edge_relationship_id">R150_R0025</data><data key="edge_source_entity_id">R150_E0015</data><data key="edge_relationship_type">manual_remark_fallback</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS development worksheet DW01 can record CPAS when RASR coding cannot be amended.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0026" source="APP_DCPS" target="R150_E0016"><data key="edge_relationship_id">R150_R0026</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">automatically_sets_status_in_dde</data><data key="edge_target_entity_id">R150_E0016</data><data key="edge_operational_context">On DHU transfer DCPS designates applied medical assessments Advisory on Disability Determination Explanation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0027" source="R150_E0016" target="STRUCT_DDE"><data key="edge_relationship_id">R150_R0027</data><data key="edge_source_entity_id">R150_E0016</data><data key="edge_relationship_type">reflected_in</data><data key="edge_target_entity_id">STRUCT_DDE</data><data key="edge_operational_context">DDE reflects downstream consultative assessment advisory rather than final favorable determination.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0028" source="REPO_CEF" target="R150_E0017"><data key="edge_relationship_id">R150_R0028</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">requires_unmodifiable_evidence_exception</data><data key="edge_target_entity_id">R150_E0017</data><data key="edge_operational_context">Previously imaged assessment PDF remains unchanged; annotation must be on eView Notes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0029" source="R150_E0017" target="APP_EVIEW"><data key="edge_relationship_id">R150_R0029</data><data key="edge_source_entity_id">R150_E0017</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">eView Details/Notes annotate Advisory on immutable document.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0030" source="R150_E0019" target="APP_DCPS"><data key="edge_relationship_id">R150_R0030</data><data key="edge_source_entity_id">R150_E0019</data><data key="edge_relationship_type">routes_nonfavorable_cessation_to</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DDS case in DCPS designated for DHU review; update case control destination.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R150_R0031" source="R150_E0019" target="R150_E0018"><data key="edge_relationship_id">R150_R0031</data><data key="edge_source_entity_id">R150_E0019</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R150_E0018</data><data key="edge_operational_context">SSA-887 evidence summary accompanies pre-hearing cessation for hearing review.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0032" source="R150_E0019" target="FORM_SSA408"><data key="edge_relationship_id">R150_R0032</data><data key="edge_source_entity_id">R150_E0019</data><data key="edge_relationship_type">routes_paper_folder_with</data><data key="edge_target_entity_id">FORM_SSA408</data><data key="edge_operational_context">Physical folder transmission uses SSA-408 route slip and applicable destination code.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0033" source="APP_EDCS" target="R150_E0020"><data key="edge_relationship_id">R150_R0033</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">causes_cross_case_cal_message</data><data key="edge_target_entity_id">R150_E0020</data><data key="edge_operational_context">EDCS transfer of subsequent CAL new claim causes AC message in eView when earlier AC proceeding exists.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0034" source="R150_E0020" target="APP_EVIEW"><data key="edge_relationship_id">R150_R0034</data><data key="edge_source_entity_id">R150_E0020</data><data key="edge_relationship_type">delivered_through</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">eView message names related same-SSN case, qualifying condition or CAL removal event.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0035" source="APP_CAL_SELECTION" target="R150_E0021"><data key="edge_relationship_id">R150_R0035</data><data key="edge_source_entity_id">APP_CAL_SELECTION</data><data key="edge_relationship_type">establishes_appeals_priority</data><data key="edge_target_entity_id">R150_E0021</data><data key="edge_operational_context">CAL designation preserves priority at any subsequent appeal after claim denial.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0036" source="R150_E0021" target="APP_EVIEW"><data key="edge_relationship_id">R150_R0036</data><data key="edge_source_entity_id">R150_E0021</data><data key="edge_relationship_type">visible_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">CAL:Y flag on eView electronic-folder header identifies case.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0037" source="APP_EDCS" target="R150_E0022"><data key="edge_relationship_id">R150_R0037</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">triggers_initial_claim_tickler</data><data key="edge_target_entity_id">R150_E0022</data><data key="edge_operational_context">Action item after transfer prompts employee to log CAL issue and monitor 20-day tickle.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0038" source="R150_E0022" target="APP_MCS"><data key="edge_relationship_id">R150_R0038</data><data key="edge_source_entity_id">R150_E0022</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS DW01 issue control tracks CAL development, not a person master attribute.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0039" source="R150_E0022" target="APP_CCE"><data key="edge_relationship_id">R150_R0039</data><data key="edge_source_entity_id">R150_E0022</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">CCE development worksheet also supports CAL issue control.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0040" source="R150_E0023" target="REPO_CEF"><data key="edge_relationship_id">R150_R0040</data><data key="edge_source_entity_id">R150_E0023</data><data key="edge_relationship_type">evidence_held_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Electronic claims retain copies of WC/PDB proof in EF to support future benefit-offset reviews.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0041" source="R150_E0023" target="R150_E0024"><data key="edge_relationship_id">R150_R0041</data><data key="edge_source_entity_id">R150_E0023</data><data key="edge_relationship_type">dual_copies_required_when_pc_action</data><data key="edge_target_entity_id">R150_E0024</data><data key="edge_operational_context">WC/PDB proof may require two routed copies, one EF and one PC Paperless.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0042" source="R150_E0024" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">R150_R0042</data><data key="edge_source_entity_id">R150_E0024</data><data key="edge_relationship_type">copy_destination</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">Processing center Paperless copy supplied for PC benefit-offset action.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0043" source="R150_E0024" target="REPO_CEF"><data key="edge_relationship_id">R150_R0043</data><data key="edge_source_entity_id">R150_E0024</data><data key="edge_relationship_type">copy_destination</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Electronic disability case receives independent WC/PDB proof copy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0044" source="APP_PAPERLESS_PSC" target="R150_E0025"><data key="edge_relationship_id">R150_R0044</data><data key="edge_source_entity_id">APP_PAPERLESS_PSC</data><data key="edge_relationship_type">fo_read_access_not_available</data><data key="edge_target_entity_id">R150_E0025</data><data key="edge_operational_context">POMS explicitly limits FO access to PC Paperless; cannot assume shared enterprise search.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0045" source="APP_EDCS" target="R150_E0026"><data key="edge_relationship_id">R150_R0045</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">supports_ac_evidence_follow_up</data><data key="edge_target_entity_id">R150_E0026</data><data key="edge_operational_context">Appeals Council evidence update- after-transfer process includes explicit staff follow-up and escalation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0046" source="R118_E013" target="R150_E0026"><data key="edge_relationship_id">R150_R0046</data><data key="edge_source_entity_id">R118_E013</data><data key="edge_relationship_type">governed_by_followup</data><data key="edge_target_entity_id">R150_E0026</data><data key="edge_operational_context">AC UAT alert requires timeliness control once sent.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0047" source="R150_E0027" target="APP_EVIEW"><data key="edge_relationship_id">R150_R0047</data><data key="edge_source_entity_id">R150_E0027</data><data key="edge_relationship_type">governs_evidence_intake_for</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Use case-stage and protective filing rule before placing later evidence in electronic appeals evidence context.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R150_R0048" source="SVC_E1696" target="R150_E0028"><data key="edge_relationship_id">R150_R0048</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">excludes_supporting_attachments</data><data key="edge_target_entity_id">R150_E0028</data><data key="edge_operational_context">e1696 online appointment path does not receive other attachments through the same submission portal.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0049" source="APP_RASR" target="R150_E0029"><data key="edge_relationship_id">R150_R0049</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">separates_appointment_from_fee_assignment</data><data key="edge_target_entity_id">R150_E0029</data><data key="edge_operational_context">Appointment recognition and fee-assignment authorization require separate decision processing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0050" source="REPO_SSA_VENDOR" target="R150_E0030"><data key="edge_relationship_id">R150_R0050</data><data key="edge_source_entity_id">REPO_SSA_VENDOR</data><data key="edge_relationship_type">applies_temporary_statement_retention</data><data key="edge_target_entity_id">R150_E0030</data><data key="edge_operational_context">OAG vendor capability files are time-limited market-research records, not indefinitely maintained contract history.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0051" source="PROC_VENDOR_REPO_SUBMISSION" target="R150_E0030"><data key="edge_relationship_id">R150_R0051</data><data key="edge_source_entity_id">PROC_VENDOR_REPO_SUBMISSION</data><data key="edge_relationship_type">subject_to_repository_retention</data><data key="edge_target_entity_id">R150_E0030</data><data key="edge_operational_context">Vendor may refile after approximate one-year deletion interval.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R150_R0052" source="R150_E0031" target="REPO_CEF"><data key="edge_relationship_id">R150_R0052</data><data key="edge_source_entity_id">R150_E0031</data><data key="edge_relationship_type">conditional_electronic_archive</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Representatives copies accompanying certified electronic record follow electronic copy/retrieval procedure.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R150_R0053" source="R150_E0031" target="APP_EP"><data key="edge_relationship_id">R150_R0053</data><data key="edge_source_entity_id">R150_E0031</data><data key="edge_relationship_type">conditional_remote_folder_copy</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">When another component holds paper folder, Evidence Portal may support communication copy transmission.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R151_R001" source="R151_E001" target="SYS_NUMIDENT"><data key="edge_relationship_id">R151_R001</data><data key="edge_source_entity_id">R151_E001</data><data key="edge_relationship_type">updates_conditionally</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">2024 policy permits correction to deceased person Numident when identity/relationship proof and source evidence support the claim.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R002" source="R151_E001" target="R151_E002"><data key="edge_relationship_id">R151_R002</data><data key="edge_source_entity_id">R151_E001</data><data key="edge_relationship_type">requires_verification_of</data><data key="edge_target_entity_id">R151_E002</data><data key="edge_operational_context">Field office obtains the requestor identification and relationship to the deceased numberholder.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R003" source="R151_E001" target="UI_SSNAP_ADDITIONAL_INFO"><data key="edge_relationship_id">R151_R003</data><data key="edge_source_entity_id">R151_E001</data><data key="edge_relationship_type">performed_through</data><data key="edge_target_entity_id">UI_SSNAP_ADDITIONAL_INFO</data><data key="edge_operational_context">SSNAP Additional Info is used to suppress card issuance for deceased correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R004" source="R151_E003" target="R151_E001"><data key="edge_relationship_id">R151_R004</data><data key="edge_source_entity_id">R151_E003</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R151_E001</data><data key="edge_operational_context">Deceased correction application requires affirmative suppress-card indication.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R005" source="R151_E004" target="APP_DIPS"><data key="edge_relationship_id">R151_R005</data><data key="edge_source_entity_id">R151_E004</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">DIPS receives death input when death is missing on Numident.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R006" source="R151_E004" target="SYS_NUMIDENT"><data key="edge_relationship_id">R151_R006</data><data key="edge_source_entity_id">R151_E004</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">POMS says add death through DIPS if Numident lacks death information; death certificate is required.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R007" source="R151_E001" target="R151_E004"><data key="edge_relationship_id">R151_R007</data><data key="edge_source_entity_id">R151_E001</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">R151_E004</data><data key="edge_operational_context">When death information absent on Numident, death certificate and DIPS entry follow corrections.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R008" source="R151_E005" target="R151_E006"><data key="edge_relationship_id">R151_R008</data><data key="edge_source_entity_id">R151_E005</data><data key="edge_relationship_type">provides_corrected_information_via</data><data key="edge_target_entity_id">R151_E006</data><data key="edge_operational_context">WA L&amp;I sends amended SSA-1709 after a WC award is re-opened or corrected.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R009" source="R151_E006" target="R151_E008"><data key="edge_relationship_id">R151_R009</data><data key="edge_source_entity_id">R151_E006</data><data key="edge_relationship_type">supports_verification_for</data><data key="edge_target_entity_id">R151_E008</data><data key="edge_operational_context">SSA-1709 serves as a source of WC payments used by employees to determine offset; attorney fees require separate verification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R010" source="R151_E008" target="R151_E005"><data key="edge_relationship_id">R151_R010</data><data key="edge_source_entity_id">R151_E008</data><data key="edge_relationship_type">involves_external_agency</data><data key="edge_target_entity_id">R151_E005</data><data key="edge_operational_context">WA L&amp;I applies reverse offset based on SSA benefit notification, after its own notice to recipient.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R011" source="R151_E008" target="R151_E009"><data key="edge_relationship_id">R151_R011</data><data key="edge_source_entity_id">R151_E008</data><data key="edge_relationship_type">records_data_on</data><data key="edge_target_entity_id">R151_E009</data><data key="edge_operational_context">WA reverse-jurisdiction claims use MCS WPCL start-date and indication fields.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R012" source="R151_E009" target="APP_MCS"><data key="edge_relationship_id">R151_R012</data><data key="edge_source_entity_id">R151_E009</data><data key="edge_relationship_type">is_screen_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS WPCL screen requires initial reverse-offset start input and later correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R013" source="R151_E008" target="R151_E010"><data key="edge_relationship_id">R151_R013</data><data key="edge_source_entity_id">R151_E008</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">R151_E010</data><data key="edge_operational_context">FO diaries age-62 offset reimposition four months in advance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R014" source="R151_E010" target="UI_MCS_DECI"><data key="edge_relationship_id">R151_R014</data><data key="edge_source_entity_id">R151_E010</data><data key="edge_relationship_type">controlled_in</data><data key="edge_target_entity_id">UI_MCS_DECI</data><data key="edge_operational_context">042 diary is entered in MCS DECI and associated DIAR screen.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R015" source="R151_E008" target="R151_E011"><data key="edge_relationship_id">R151_R015</data><data key="edge_source_entity_id">R151_E008</data><data key="edge_relationship_type">excludes_auto_initiation_via</data><data key="edge_target_entity_id">R151_E011</data><data key="edge_operational_context">Do not use Non-Medical Completion/SPORT or Auto-Initiate in these MCS cases.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R016" source="R151_E011" target="APP_MCS"><data key="edge_relationship_id">R151_R016</data><data key="edge_source_entity_id">R151_E011</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Specific WA WC reverse-offset cases require conditional manual handling rather than auto-initiation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R017" source="R151_E008" target="R151_E012"><data key="edge_relationship_id">R151_R017</data><data key="edge_source_entity_id">R151_E008</data><data key="edge_relationship_type">may_use_fallback</data><data key="edge_target_entity_id">R151_E012</data><data key="edge_operational_context">Where MCS has processing limitation, employees use ICF WC/PDB WCCD screen.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R018" source="R151_E012" target="APP_ICF_T2"><data key="edge_relationship_id">R151_R018</data><data key="edge_source_entity_id">R151_E012</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ICF_T2</data><data key="edge_operational_context">ICF Title II WCCD route supports manual WA reverse-jurisdiction WC/PDB offset entry.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R019" source="R151_E008" target="R151_E007"><data key="edge_relationship_id">R151_R019</data><data key="edge_source_entity_id">R151_E008</data><data key="edge_relationship_type">produces_notice</data><data key="edge_target_entity_id">R151_E007</data><data key="edge_operational_context">SSA sends WA WC data sheet to state or self-insurer after adjudication and during age-62 offset resumption.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R020" source="R151_E007" target="R151_E005"><data key="edge_relationship_id">R151_R020</data><data key="edge_source_entity_id">R151_E007</data><data key="edge_relationship_type">delivered_to</data><data key="edge_target_entity_id">R151_E005</data><data key="edge_operational_context">SSA faxes/mails relevant benefit data sheet to WA L&amp;I; state uses it to determine offset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R021" source="R151_E007" target="REPO_EF"><data key="edge_relationship_id">R151_R021</data><data key="edge_source_entity_id">R151_E007</data><data key="edge_relationship_type">may_be_retained_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">SSA retains copy in electronic folder, NDRed, or Paperless, depending on record type.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R022" source="R151_E013" target="R151_E006"><data key="edge_relationship_id">R151_R022</data><data key="edge_source_entity_id">R151_E013</data><data key="edge_relationship_type">uses_amended</data><data key="edge_target_entity_id">R151_E006</data><data key="edge_operational_context">A revised WA WC Form SSA-1709 can trigger recalculation of previous offset; do not treat previous amount as final.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R023" source="R151_E013" target="R151_E008"><data key="edge_relationship_id">R151_R023</data><data key="edge_source_entity_id">R151_E013</data><data key="edge_relationship_type">changes_adjudication_in</data><data key="edge_target_entity_id">R151_E008</data><data key="edge_operational_context">Employee reworks WA WC offset with amended state payment information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R024" source="R151_E005" target="R151_E013"><data key="edge_relationship_id">R151_R024</data><data key="edge_source_entity_id">R151_E005</data><data key="edge_relationship_type">supplies_information_to</data><data key="edge_target_entity_id">R151_E013</data><data key="edge_operational_context">State amended SSA-1709 supports SSA correction; transport may be fax/mail; no automated state application integration established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R025" source="R151_E014" target="DB_IRS_IMF"><data key="edge_relationship_id">R151_R025</data><data key="edge_source_entity_id">R151_E014</data><data key="edge_relationship_type">retrieves_taxpayer_mailing_address_from</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">As of 2015, PEBES sends weekly unmatched names/SSNs to IRS IMF for statement-only mailing addresses.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Historical process; IRS address data use under 26 USC 6103(m)(7); never treat as proof of MBR/SSR/Numident update.</data></edge><edge id="R151_R026" source="R151_E014" target="APP_PEBES"><data key="edge_relationship_id">R151_R026</data><data key="edge_source_entity_id">R151_E014</data><data key="edge_relationship_type">supplies_statement_mailing_address_to</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">2015 policy describes batch IRS addresses returned to PEBES automatic Statement production.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R027" source="R151_E014" target="R151_E015"><data key="edge_relationship_id">R151_R027</data><data key="edge_source_entity_id">R151_E014</data><data key="edge_relationship_type">may_return</data><data key="edge_target_entity_id">R151_E015</data><data key="edge_operational_context">In 2015-revised POMS approximately 15 percent of IRS address requests returned no-match.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R028" source="R151_E014" target="R151_E016"><data key="edge_relationship_id">R151_R028</data><data key="edge_source_entity_id">R151_E014</data><data key="edge_relationship_type">subject_to_address_quality_caveat</data><data key="edge_target_entity_id">R151_E016</data><data key="edge_operational_context">2015 POMS warns batch IRS IMF address and IRS customer-service query address can differ.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R029" source="R151_E014" target="DB_SIPEBES_TERRITORY_ADDRESS"><data key="edge_relationship_id">R151_R029</data><data key="edge_source_entity_id">R151_E014</data><data key="edge_relationship_type">used_after_territorial_matching</data><data key="edge_target_entity_id">DB_SIPEBES_TERRITORY_ADDRESS</data><data key="edge_operational_context">SSA described territory-taxpayer matching as preceding weekly IRS IMF matching for unmatched SSN/name sets.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Historical sequencing; does not establish current 2026 cadence or present physical staging.</data></edge><edge id="R151_R030" source="R151_E016" target="DB_IRS_IMF"><data key="edge_relationship_id">R151_R030</data><data key="edge_source_entity_id">R151_E016</data><data key="edge_relationship_type">concerns</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">IRS online agent-view data may differ from SSA batch IMF address data in the 2015-revised description.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R031" source="SYS_SSR" target="R151_E017"><data key="edge_relationship_id">R151_R031</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R151_E017</data><data key="edge_operational_context">SSA 2026 Supplement Table 7.D1 identifies SSR 100% data for December 2025 SSI income.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R032" source="SYS_SSR" target="R151_E018"><data key="edge_relationship_id">R151_R032</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R151_E018</data><data key="edge_operational_context">SSA 2026 Supplement Table 7.D2 uses SSR administrative data on SSI beneficiaries with Social Security income by state/age.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R033" source="R151_E017" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R151_R033</data><data key="edge_source_entity_id">R151_E017</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Published within 2026 Annual Statistical Supplement, sectional release subject to revision.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R034" source="R151_E018" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R151_R034</data><data key="edge_source_entity_id">R151_E018</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Published within 2026 Annual Statistical Supplement, sectional release subject to revision.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R035" source="R151_E017" target="R151_E019"><data key="edge_relationship_id">R151_R035</data><data key="edge_source_entity_id">R151_E017</data><data key="edge_relationship_type">uses_denominator_rule</data><data key="edge_target_entity_id">R151_E019</data><data key="edge_operational_context">December 2025 full SSR population, not a sample; age/eligibility categories provided.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R036" source="R151_E018" target="R151_E019"><data key="edge_relationship_id">R151_R036</data><data key="edge_source_entity_id">R151_E018</data><data key="edge_relationship_type">uses_denominator_rule</data><data key="edge_target_entity_id">R151_E019</data><data key="edge_operational_context">State/age percentages compare SSI recipients with Social Security income within published category.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R037" source="R151_E020" target="R151_E021"><data key="edge_relationship_id">R151_R037</data><data key="edge_source_entity_id">R151_E020</data><data key="edge_relationship_type">describes_submission_process</data><data key="edge_target_entity_id">R151_E021</data><data key="edge_operational_context">WAV001 communicates waiver routes and conditions to beneficiary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Observed 2026-10-09; only documented business process, not inferred programmatic API, physical DB or automatic write.</data></edge><edge id="R151_R038" source="R151_E021" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R151_R038</data><data key="edge_source_entity_id">R151_E021</data><data key="edge_relationship_type">uses_evidence_form</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">The notice directs certain claimants to my Social Security Upload Documents for electronic SSA-632 submission.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Customer-facing instructions do not establish adjudication automation or waiver backend entry.</data></edge><edge id="R152_R001" source="R152_E001" target="SYS_NUMIDENT"><data key="edge_relationship_id">R152_R001</data><data key="edge_source_entity_id">R152_E001</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">The DOB field is part of Numident and changes on proper evidence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R002" source="R152_E002" target="SYS_MBR"><data key="edge_relationship_id">R152_R002</data><data key="edge_source_entity_id">R152_E002</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR DOB proof code can be used under specific policy conditions for a Numident correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R003" source="R152_E003" target="SYS_SSR"><data key="edge_relationship_id">R152_R003</data><data key="edge_source_entity_id">R152_E003</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR age proof codes are subject to separate SSI participation and category rules.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R004" source="R152_E004" target="R152_E002"><data key="edge_relationship_id">R152_R004</data><data key="edge_source_entity_id">R152_E004</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R152_E002</data><data key="edge_operational_context">MBR proof values A,B,C,F,P,Q and absent values have conditional acceptance rules.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R005" source="R152_E004" target="R152_E003"><data key="edge_relationship_id">R152_R005</data><data key="edge_source_entity_id">R152_E004</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R152_E003</data><data key="edge_operational_context">SSR proof values B,C,E,F,Q and missing values have conditional acceptance rules.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R006" source="R152_E004" target="R152_E001"><data key="edge_relationship_id">R152_R006</data><data key="edge_source_entity_id">R152_E004</data><data key="edge_relationship_type">may_correct</data><data key="edge_target_entity_id">R152_E001</data><data key="edge_operational_context">Supported benefit-record DOB can update Numident via applicable SSNAP special field-office processing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R007" source="R152_E005" target="SYS_MBR"><data key="edge_relationship_id">R152_R007</data><data key="edge_source_entity_id">R152_E005</data><data key="edge_relationship_type">limits_correction_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Administrative finality can prevent revision of MBR established DOB even when Numident identity DOB changes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R008" source="R152_E005" target="SYS_SSR"><data key="edge_relationship_id">R152_R008</data><data key="edge_source_entity_id">R152_E005</data><data key="edge_relationship_type">limits_correction_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Administrative finality can protect benefit determination on SSR separately from identity correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R009" source="R152_E007" target="R152_E008"><data key="edge_relationship_id">R152_R009</data><data key="edge_source_entity_id">R152_E007</data><data key="edge_relationship_type">compares_to</data><data key="edge_target_entity_id">R152_E008</data><data key="edge_operational_context">Paper SS-5 or microprint is checked against Numident to establish actual keying errors.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R010" source="R152_E007" target="PROC_NCP"><data key="edge_relationship_id">R152_R010</data><data key="edge_source_entity_id">R152_E007</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PROC_NCP</data><data key="edge_operational_context">Documented keying error handled with NCP; ordinary updated fact may require new iteration instead.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R011" source="R152_E006" target="ORG_STATE_BVS"><data key="edge_relationship_id">R152_R011</data><data key="edge_source_entity_id">R152_E006</data><data key="edge_relationship_type">verifies_with</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">State birth-record evidence can be verified before Numident DOB correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R012" source="R152_E006" target="R152_E009"><data key="edge_relationship_id">R152_R012</data><data key="edge_source_entity_id">R152_E006</data><data key="edge_relationship_type">records_proof_on</data><data key="edge_target_entity_id">R152_E009</data><data key="edge_operational_context">After confirmation that no birth certificate exists, document proof-of-age screen for alternative evidence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R013" source="R152_E007" target="R152_E001"><data key="edge_relationship_id">R152_R013</data><data key="edge_source_entity_id">R152_E007</data><data key="edge_relationship_type">supports_correction_of</data><data key="edge_target_entity_id">R152_E001</data><data key="edge_operational_context">Correcting Numident DOB requires identity and age evidence unless verified keying error.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R014" source="R152_E011" target="FORM_SSA821BK"><data key="edge_relationship_id">R152_R014</data><data key="edge_source_entity_id">R152_E011</data><data key="edge_relationship_type">revises</data><data key="edge_target_entity_id">FORM_SSA821BK</data><data key="edge_operational_context">Form SSA-821-BK redesigned September 2025 for employee work activity documentation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S002. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R015" source="R152_E011" target="R152_E010"><data key="edge_relationship_id">R152_R015</data><data key="edge_source_entity_id">R152_E011</data><data key="edge_relationship_type">made_available_via</data><data key="edge_target_entity_id">R152_E010</data><data key="edge_operational_context">SSA identifies inForms as route to revised SSA-821-BK as of September 2025.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S002. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R016" source="R152_E011" target="APP_UNIFORMS"><data key="edge_relationship_id">R152_R016</data><data key="edge_source_entity_id">R152_E011</data><data key="edge_relationship_type">planned_availability_via</data><data key="edge_target_entity_id">APP_UNIFORMS</data><data key="edge_operational_context">2025 EM said the form would be available in UniForms December 2025; actual release not independently verified.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence R152_S002. Prospective date reported in September 2025, not validated independent 2026 deployment.</data></edge><edge id="R152_R017" source="R152_E011" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R152_R017</data><data key="edge_source_entity_id">R152_E011</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Redesigned form aligns with Upload Documents lack of prefilled fields; does not imply automatic adjudication.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S002. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R018" source="R152_E012" target="FORM_SSA821BK"><data key="edge_relationship_id">R152_R018</data><data key="edge_source_entity_id">R152_E012</data><data key="edge_relationship_type">modifies</data><data key="edge_target_entity_id">FORM_SSA821BK</data><data key="edge_operational_context">Removes historical prefilled IRS earnings table in favor of current earnings development.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S002. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R019" source="R152_E013" target="FORM_SSA821BK"><data key="edge_relationship_id">R152_R019</data><data key="edge_source_entity_id">R152_E013</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">FORM_SSA821BK</data><data key="edge_operational_context">Form records receipt of pay stubs without retaining previous embedded pay-stub table.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S002. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R020" source="R152_E014" target="FORM_SSA821BK"><data key="edge_relationship_id">R152_R020</data><data key="edge_source_entity_id">R152_E014</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">FORM_SSA821BK</data><data key="edge_operational_context">Reason work ended supports possible unsuccessful-work-attempt investigation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S002. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R021" source="R152_E015" target="FORM_SSA821BK"><data key="edge_relationship_id">R152_R021</data><data key="edge_source_entity_id">R152_E015</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">FORM_SSA821BK</data><data key="edge_operational_context">Form asks about accommodation providers other than employer and disability-related work incentives.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S002. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R022" source="R152_E016" target="FORM_SSA820BK"><data key="edge_relationship_id">R152_R022</data><data key="edge_source_entity_id">R152_E016</data><data key="edge_relationship_type">revises</data><data key="edge_target_entity_id">FORM_SSA820BK</data><data key="edge_operational_context">February 2026 instruction issued redesigned self-employment work report.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S003. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R023" source="R152_E016" target="R152_E010"><data key="edge_relationship_id">R152_R023</data><data key="edge_source_entity_id">R152_E016</data><data key="edge_relationship_type">made_available_via</data><data key="edge_target_entity_id">R152_E010</data><data key="edge_operational_context">New SSA-820-BK available via inForms in February 2026.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S003. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R024" source="R152_E016" target="APP_EWORK"><data key="edge_relationship_id">R152_R024</data><data key="edge_source_entity_id">R152_E016</data><data key="edge_relationship_type">linked_from</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">February 2026 EM states the revised form is linked from eWork home page message board.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S003. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R025" source="R152_E016" target="APP_UNIFORMS"><data key="edge_relationship_id">R152_R025</data><data key="edge_source_entity_id">R152_E016</data><data key="edge_relationship_type">planned_availability_via</data><data key="edge_target_entity_id">APP_UNIFORMS</data><data key="edge_operational_context">February 2026 EM said UniForms availability would begin in July; independent release status not established.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence R152_S003. Prospective form channel, not verified implementation event.</data></edge><edge id="R152_R026" source="R152_E016" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R152_R026</data><data key="edge_source_entity_id">R152_E016</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Redesigned self-employment form supports Upload Documents workflow without prefilled electronic inputs.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S003. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R027" source="R152_E017" target="FORM_SSA820BK"><data key="edge_relationship_id">R152_R027</data><data key="edge_source_entity_id">R152_E017</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">FORM_SSA820BK</data><data key="edge_operational_context">Self-employment form asks about new gig-work categories.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S003. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R028" source="R152_E018" target="FORM_SSA820BK"><data key="edge_relationship_id">R152_R028</data><data key="edge_source_entity_id">R152_E018</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">FORM_SSA820BK</data><data key="edge_operational_context">Form collects forward-looking earnings estimates in lieu of an embedded historical monthly table.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence R152_S003. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R029" source="R152_E019" target="APP_EWORK"><data key="edge_relationship_id">R152_R029</data><data key="edge_source_entity_id">R152_E019</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">Work Review Summary is an eWork display for review of employment records.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R030" source="R152_E020" target="APP_EWORK"><data key="edge_relationship_id">R152_R030</data><data key="edge_source_entity_id">R152_E020</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">POMS explicitly identifies eWork pay-stub table.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R031" source="R152_E021" target="APP_EWORK"><data key="edge_relationship_id">R152_R031</data><data key="edge_source_entity_id">R152_E021</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">eWork Earnings Details page displays monthly earnings by source.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R032" source="R152_E022" target="R152_E019"><data key="edge_relationship_id">R152_R032</data><data key="edge_source_entity_id">R152_E022</data><data key="edge_relationship_type">writes_employer_entry_to</data><data key="edge_target_entity_id">R152_E019</data><data key="edge_operational_context">New PDP-sourced EIN absent from eWork employer list is added to Work Review Summary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R033" source="EX_PIE" target="R152_E020"><data key="edge_relationship_id">R152_R033</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">supplies_payroll_data_to</data><data key="edge_target_entity_id">R152_E020</data><data key="edge_operational_context">PIE/PDP earnings propagate to eWork pay-stub table with PDP source code.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R034" source="R152_E023" target="R152_E020"><data key="edge_relationship_id">R152_R034</data><data key="edge_source_entity_id">R152_E023</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R152_E020</data><data key="edge_operational_context">eWork source precedence for overlapping pay stubs: PDP then employee-posted then myWR then ENI.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R035" source="R152_E021" target="R152_E020"><data key="edge_relationship_id">R152_R035</data><data key="edge_source_entity_id">R152_E021</data><data key="edge_relationship_type">records_monthly_earnings_from</data><data key="edge_target_entity_id">R152_E020</data><data key="edge_operational_context">eWork converts pay periods into monthly earnings totals and assigns verified-by source codes.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R036" source="R152_E024" target="R152_E025"><data key="edge_relationship_id">R152_R036</data><data key="edge_source_entity_id">R152_E024</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R152_E025</data><data key="edge_operational_context">Post-entitlement policy attempts to determine when money was earned; paid-month fallback subject to due process.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R037" source="R152_E026" target="DB_WEI_REPO"><data key="edge_relationship_id">R152_R037</data><data key="edge_source_entity_id">R152_E026</data><data key="edge_relationship_type">uses_as_evidence</data><data key="edge_target_entity_id">DB_WEI_REPO</data><data key="edge_operational_context">Initial claims may use readily available PDP or payroll data from WEI with approval/authorization.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R038" source="R152_E025" target="DB_WEI_REPO"><data key="edge_relationship_id">R152_R038</data><data key="edge_source_entity_id">R152_E025</data><data key="edge_relationship_type">uses_as_evidence</data><data key="edge_target_entity_id">DB_WEI_REPO</data><data key="edge_operational_context">Post-entitlement review prioritizes POMS-identified payroll provider wage data before other sources.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R039" source="R152_E027" target="UI_CWP"><data key="edge_relationship_id">R152_R039</data><data key="edge_source_entity_id">R152_E027</data><data key="edge_relationship_type">accessed_using</data><data key="edge_target_entity_id">UI_CWP</data><data key="edge_operational_context">Ticket-to-Work wage stubs from iTOPSS visible through EDCS Consolidated Wage Page.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R040" source="R152_E027" target="R152_E025"><data key="edge_relationship_id">R152_R040</data><data key="edge_source_entity_id">R152_E027</data><data key="edge_relationship_type">supplies_wage_evidence_to</data><data key="edge_target_entity_id">R152_E025</data><data key="edge_operational_context">iTOPSS wages may supplement eWork work CDR monthly wages where pay dates available.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R041" source="R152_E028" target="R152_E025"><data key="edge_relationship_id">R152_R041</data><data key="edge_source_entity_id">R152_E028</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">R152_E025</data><data key="edge_operational_context">Employer SSA-L725 inquiry last resort when other post-entitlement source options exhausted.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R042" source="R152_E029" target="R152_E028"><data key="edge_relationship_id">R152_R042</data><data key="edge_source_entity_id">R152_E029</data><data key="edge_relationship_type">controls_followup_for</data><data key="edge_target_entity_id">R152_E028</data><data key="edge_operational_context">Field office 15-day and processing-center 35-day follow-up periods apply to employer request.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R043" source="R152_E023" target="EX_PIE"><data key="edge_relationship_id">R152_R043</data><data key="edge_source_entity_id">R152_E023</data><data key="edge_relationship_type">prioritizes</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">Payroll data providers take first priority over manual/social/user work reports for overlapping same-employer wage observations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R044" source="R152_E026" target="FORM_SSA821BK"><data key="edge_relationship_id">R152_R044</data><data key="edge_source_entity_id">R152_E026</data><data key="edge_relationship_type">receives_claimant_report_from</data><data key="edge_target_entity_id">FORM_SSA821BK</data><data key="edge_operational_context">SSA-821-BK work allegation assists income timing and significant disability onset discrepancies.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R045" source="R152_E025" target="FORM_SSA821BK"><data key="edge_relationship_id">R152_R045</data><data key="edge_source_entity_id">R152_E025</data><data key="edge_relationship_type">receives_claimant_report_from</data><data key="edge_target_entity_id">FORM_SSA821BK</data><data key="edge_operational_context">SSA-821-BK supports work CDR investigation when needed; not required for clearly non-SGA work.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC160. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R046" source="R152_E032" target="R152_E030"><data key="edge_relationship_id">R152_R046</data><data key="edge_source_entity_id">R152_E032</data><data key="edge_relationship_type">prioritizes</data><data key="edge_target_entity_id">R152_E030</data><data key="edge_operational_context">CWHS county residence attribution first uses self-employment associated address for workers with Schedule SE.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R66_005. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R047" source="R152_E032" target="R152_E031"><data key="edge_relationship_id">R152_R047</data><data key="edge_source_entity_id">R152_E032</data><data key="edge_relationship_type">falls_back_to</data><data key="edge_target_entity_id">R152_E031</data><data key="edge_operational_context">Without Schedule SE, use W-2 residence for highest Medicare-taxable-wage report.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R66_005. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R048" source="R152_E032" target="REPORT_EARN_EMP_2023"><data key="edge_relationship_id">R152_R048</data><data key="edge_source_entity_id">R152_E032</data><data key="edge_relationship_type">used_in</data><data key="edge_target_entity_id">REPORT_EARN_EMP_2023</data><data key="edge_operational_context">2023 state/county earnings report assigns multi-area worker to one geographic residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R66_005. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R049" source="R152_E033" target="REPORT_EARN_EMP_2023"><data key="edge_relationship_id">R152_R049</data><data key="edge_source_entity_id">R152_E033</data><data key="edge_relationship_type">classification_in</data><data key="edge_target_entity_id">REPORT_EARN_EMP_2023</data><data key="edge_operational_context">Report uses Unknown county when residence has no county code.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R66_005. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R050" source="R152_E034" target="REPORT_EARN_EMP_2023"><data key="edge_relationship_id">R152_R050</data><data key="edge_source_entity_id">R152_E034</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">REPORT_EARN_EMP_2023</data><data key="edge_operational_context">Suppressed county cells still contribute to state totals.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R66_005. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R051" source="R152_E035" target="REPORT_EARN_EMP_2023"><data key="edge_relationship_id">R152_R051</data><data key="edge_source_entity_id">R152_E035</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">REPORT_EARN_EMP_2023</data><data key="edge_operational_context">One-percent sample inflated to population estimates, subject to sampling variability.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R66_005. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R052" source="DATA_CWHS" target="R152_E035"><data key="edge_relationship_id">R152_R052</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">sample_source_for</data><data key="edge_target_entity_id">R152_E035</data><data key="edge_operational_context">CWHS 1% sample is underlying statistical sample rather than a person-level census.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R66_005. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R053" source="R152_E036" target="R123_E010"><data key="edge_relationship_id">R152_R053</data><data key="edge_source_entity_id">R152_E036</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">R123_E010</data><data key="edge_operational_context">Annual SSI V.F1 table cannot be interpreted as a complete census of participation in all public programs.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R123_001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R054" source="SYS_SSR" target="R123_E010"><data key="edge_relationship_id">R152_R054</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_complete_current_participation_extract_for</data><data key="edge_target_entity_id">R123_E010</data><data key="edge_operational_context">2026 SSI Report draws current program participation from 100% SSR extract for December 2025.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R123_001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R055" source="SYS_SSR" target="R123_E010"><data key="edge_relationship_id">R152_R055</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_sampled_prior_participation_extract_for</data><data key="edge_target_entity_id">R123_E010</data><data key="edge_operational_context">Prior TANF/AFDC and Interim Assistance participation is summarized from 10% SSR extract.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC_R123_001. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R056" source="R152_E037" target="DATA_EVVE_DEATH_INDICATION"><data key="edge_relationship_id">R152_R056</data><data key="edge_source_entity_id">R152_E037</data><data key="edge_relationship_type">triggered_by</data><data key="edge_target_entity_id">DATA_EVVE_DEATH_INDICATION</data><data key="edge_operational_context">Possible death discrepancy relative to Numident/MBR/SSR requires manual identity-data verification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC401. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R057" source="R152_E037" target="SYS_NUMIDENT"><data key="edge_relationship_id">R152_R057</data><data key="edge_source_entity_id">R152_E037</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Vital record and Numident death-status disagreement must be resolved before assuming death or fraud.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC401. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R058" source="R152_E038" target="SVC_EVVE"><data key="edge_relationship_id">R152_R058</data><data key="edge_source_entity_id">R152_E038</data><data key="edge_relationship_type">returned_by</data><data key="edge_target_entity_id">SVC_EVVE</data><data key="edge_operational_context">EVVE reports source record modification but does not disclose modified attributes in the alert.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC401. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R059" source="R152_E037" target="APP_SSNAP"><data key="edge_relationship_id">R152_R059</data><data key="edge_source_entity_id">R152_E037</data><data key="edge_relationship_type">may_require_further_development_through</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Enumeration identity evidence requires fraud/no-match follow-up where source record disagrees.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence SRC401. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R060" source="R152_E039" target="PROC_IRS_3857_RESOLUTION"><data key="edge_relationship_id">R152_R060</data><data key="edge_source_entity_id">R152_E039</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_operational_context">Initial correspondence to taxpayers, employers and post office followed by 30 working-day diary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC137. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R061" source="R152_E040" target="R152_E039"><data key="edge_relationship_id">R152_R061</data><data key="edge_source_entity_id">R152_E040</data><data key="edge_relationship_type">follows</data><data key="edge_target_entity_id">R152_E039</data><data key="edge_operational_context">Additional 15-workday diary after unsuccessful 30-day response, with renewed employer/USPS follow-up.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC137. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R062" source="R152_E041" target="APP_ICOR"><data key="edge_relationship_id">R152_R062</data><data key="edge_source_entity_id">R152_E041</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">APP_ICOR</data><data key="edge_operational_context">SSA POMS requires recording date/actions/staff identifier in ICOR ERMK remark.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC137. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R152_R063" source="PROC_IRS_3857_RESOLUTION" target="R152_E041"><data key="edge_relationship_id">R152_R063</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">documents_external_contact_in</data><data key="edge_target_entity_id">R152_E041</data><data key="edge_operational_context">Case contact history with taxpayers, employers, USPS documented in ICOR ERMK.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence SRC137. No unspecified automatic updates or physical persistence inferred.</data></edge><edge id="R153_R001" source="R153_E003" target="R153_E001"><data key="edge_relationship_id">R153_R001</data><data key="edge_source_entity_id">R153_E003</data><data key="edge_relationship_type">supports_collection_at</data><data key="edge_target_entity_id">R153_E001</data><data key="edge_operational_context">CMS-500 coupon accompanies regular Medicare premium payment to CMS MPCC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R002" source="R153_E004" target="R153_E003"><data key="edge_relationship_id">R153_R002</data><data key="edge_source_entity_id">R153_E004</data><data key="edge_relationship_type">spanish_language_version_of</data><data key="edge_target_entity_id">R153_E003</data><data key="edge_operational_context">POMS explicitly identifies CMS-500A as Spanish version of CMS-500.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R003" source="R153_E002" target="R153_E003"><data key="edge_relationship_id">R153_R003</data><data key="edge_source_entity_id">R153_E002</data><data key="edge_relationship_type">generates_billing_information_for</data><data key="edge_target_entity_id">R153_E003</data><data key="edge_operational_context">Electronic billing normally supplies CMS-500, with manual PSC preparation if DBS cannot produce bill.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R004" source="R153_E006" target="R153_E003"><data key="edge_relationship_id">R153_R004</data><data key="edge_source_entity_id">R153_E006</data><data key="edge_relationship_type">uses_billing_coupon</data><data key="edge_target_entity_id">R153_E003</data><data key="edge_operational_context">Regular monthly/quarterly Medicare premium routed with preprinted or manually prepared CMS-500.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R005" source="R153_E006" target="R153_E001"><data key="edge_relationship_id">R153_R005</data><data key="edge_source_entity_id">R153_E006</data><data key="edge_relationship_type">routed_to</data><data key="edge_target_entity_id">R153_E001</data><data key="edge_operational_context">Regular CMS-managed premium payments received at field office go to MPCC, not MATPSC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R006" source="R153_E006" target="REPORT_DMS_FODRL"><data key="edge_relationship_id">R153_R006</data><data key="edge_source_entity_id">R153_E006</data><data key="edge_relationship_type">reported_on</data><data key="edge_target_entity_id">REPORT_DMS_FODRL</data><data key="edge_operational_context">DMS records regular CMS lockbox premium receipts on FO Daily Receipt Listing (FODRL).</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R007" source="R153_E006" target="APP_SERS"><data key="edge_relationship_id">R153_R007</data><data key="edge_source_entity_id">R153_E006</data><data key="edge_relationship_type">is_excluded_from</data><data key="edge_target_entity_id">APP_SERS</data><data key="edge_operational_context">Regular Medicare premium remittances excluded from SERS processing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R008" source="R153_E008" target="R153_E006"><data key="edge_relationship_id">R153_R008</data><data key="edge_source_entity_id">R153_E008</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">R153_E006</data><data key="edge_operational_context">Use DMS/eFOR trust-fund N and reason H for CMS lockbox regular premium remittances.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R009" source="R153_E008" target="R153_E005"><data key="edge_relationship_id">R153_R009</data><data key="edge_source_entity_id">R153_E008</data><data key="edge_relationship_type">entered_through</data><data key="edge_target_entity_id">R153_E005</data><data key="edge_operational_context">POMS names eFOR system as a remittance entry pathway for Medicare code N/H.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R010" source="R153_E008" target="APP_DMS"><data key="edge_relationship_id">R153_R010</data><data key="edge_source_entity_id">R153_E008</data><data key="edge_relationship_type">entered_through</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS names DMS as a remittance entry pathway for Medicare code N/H.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R011" source="R153_E007" target="R153_E009"><data key="edge_relationship_id">R153_R011</data><data key="edge_source_entity_id">R153_E007</data><data key="edge_relationship_type">recorded_with</data><data key="edge_target_entity_id">R153_E009</data><data key="edge_operational_context">Retroactive Medicare installment remittances use trust-fund O and reason P in DMS or eFOR.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R012" source="R153_E009" target="R153_E005"><data key="edge_relationship_id">R153_R012</data><data key="edge_source_entity_id">R153_E009</data><data key="edge_relationship_type">entered_through</data><data key="edge_target_entity_id">R153_E005</data><data key="edge_operational_context">POMS names eFOR for premium installment remittance code O/P.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R013" source="R153_E009" target="APP_DMS"><data key="edge_relationship_id">R153_R013</data><data key="edge_source_entity_id">R153_E009</data><data key="edge_relationship_type">entered_through</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS names DMS for premium installment remittance code O/P.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R014" source="R153_E007" target="APP_SERS"><data key="edge_relationship_id">R153_R014</data><data key="edge_source_entity_id">R153_E007</data><data key="edge_relationship_type">is_excluded_from</data><data key="edge_target_entity_id">APP_SERS</data><data key="edge_operational_context">Retroactive Medicare premium remittances use DMS/eFOR and manual forwarding, not SERS.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R015" source="R153_E007" target="FAC_MATPSC"><data key="edge_relationship_id">R153_R015</data><data key="edge_source_entity_id">R153_E007</data><data key="edge_relationship_type">generally_handled_by</data><data key="edge_target_entity_id">FAC_MATPSC</data><data key="edge_operational_context">2026 POMS says retroactive installment and lump-sum premium cases handled by MATPSC; identify conflict with older GN 02403.020 FORT report instructions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001. 2026 treatment only; old 2007 source differs on using FORT for installments.</data></edge><edge id="R153_R016" source="R153_E010" target="R153_E001"><data key="edge_relationship_id">R153_R016</data><data key="edge_source_entity_id">R153_E010</data><data key="edge_relationship_type">sends_entire_payment_to</data><data key="edge_target_entity_id">R153_E001</data><data key="edge_operational_context">When one payment covers monthly and lump-sum retroactive premium, full payment goes to MPCC and PSC is told.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R017" source="R153_E011" target="R153_E006"><data key="edge_relationship_id">R153_R017</data><data key="edge_source_entity_id">R153_E011</data><data key="edge_relationship_type">limits_receipt_into</data><data key="edge_target_entity_id">R153_E006</data><data key="edge_operational_context">Do not accept Medicare premiums before HI/SMI award prepared because MPCC lacks corresponding beneficiary record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R018" source="R153_E012" target="R153_E006"><data key="edge_relationship_id">R153_R018</data><data key="edge_source_entity_id">R153_E012</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R153_E006</data><data key="edge_operational_context">Do not deposit CMS premium into Social Security trust funds; erroneous posting may initiate IPAC and delay payment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R019" source="R153_E013" target="APP_DMS"><data key="edge_relationship_id">R153_R019</data><data key="edge_source_entity_id">R153_E013</data><data key="edge_relationship_type">produced_by</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">DMS produces forwarding instruction sheet indicating destination for remittances.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R020" source="R153_E014" target="R153_E006"><data key="edge_relationship_id">R153_R020</data><data key="edge_source_entity_id">R153_E014</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">R153_E006</data><data key="edge_operational_context">SSA FO and telephone cannot receive Medicare premium credit-card payments under this policy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R021" source="R153_E005" target="R153_E006"><data key="edge_relationship_id">R153_R021</data><data key="edge_source_entity_id">R153_E005</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R153_E006</data><data key="edge_operational_context">2026 SSA POMS directs Medicare premium entry via eFOR and issuance of automated receipt.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R022" source="R153_E005" target="R153_E007"><data key="edge_relationship_id">R153_R022</data><data key="edge_source_entity_id">R153_E005</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R153_E007</data><data key="edge_operational_context">2026 SSA POMS names eFOR as one system used for coding premium installment remittances.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R023" source="R153_E006" target="R153_E007"><data key="edge_relationship_id">R153_R023</data><data key="edge_source_entity_id">R153_E006</data><data key="edge_relationship_type">is_distinct_from</data><data key="edge_target_entity_id">R153_E007</data><data key="edge_operational_context">Current Medicare premiums route to CMS lockbox; retroactive premiums use PSC handling except documented mixed exception.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S001.</data></edge><edge id="R153_R024" source="ORG_STATE_BVS" target="R153_E015"><data key="edge_relationship_id">R153_R024</data><data key="edge_source_entity_id">ORG_STATE_BVS</data><data key="edge_relationship_type">submits_number_for</data><data key="edge_target_entity_id">R153_E015</data><data key="edge_operational_context">Participating state BVS submits an SSN to SSA electronically under agreement for verification before EDR.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S003.</data></edge><edge id="R153_R025" source="R153_E015" target="SYS_NUMIDENT"><data key="edge_relationship_id">R153_R025</data><data key="edge_source_entity_id">R153_E015</data><data key="edge_relationship_type">relies_on</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Source describes SSA SSN verification for state BVS. Numident is authoritative SSN record, but exact verification application and lookup implementation not stated.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Source R153_S003. Logical identity role only; no direct technical data flow into Numident asserted.</data></edge><edge id="R153_R026" source="R153_E015" target="R153_E016"><data key="edge_relationship_id">R153_R026</data><data key="edge_source_entity_id">R153_E015</data><data key="edge_relationship_type">precedes</data><data key="edge_target_entity_id">R153_E016</data><data key="edge_operational_context">State obtains SSN verification first, then submits death report tied to verified SSN.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S003.</data></edge><edge id="R153_R027" source="R153_E016" target="ORG_STATE_BVS"><data key="edge_relationship_id">R153_R027</data><data key="edge_source_entity_id">R153_E016</data><data key="edge_relationship_type">returns_death_report_from</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">State BVS returns EDR death record with verified SSN to SSA.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S003.</data></edge><edge id="R153_R028" source="R153_E016" target="EX_IEDR"><data key="edge_relationship_id">R153_R028</data><data key="edge_source_entity_id">R153_E016</data><data key="edge_relationship_type">related_to</data><data key="edge_target_entity_id">EX_IEDR</data><data key="edge_operational_context">Existing internet EDR exchange represents state death reporting; source documents front-end verification stage, not transport.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Source R153_S003.</data></edge><edge id="R153_R029" source="R153_E017" target="ORG_STATE_BVS"><data key="edge_relationship_id">R153_R029</data><data key="edge_source_entity_id">R153_E017</data><data key="edge_relationship_type">authorized_for</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">SSA may disclose to State BVS under applicable SORN routine uses to acquire age/marriage evidence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S003.</data></edge><edge id="R153_R030" source="R153_E017" target="SYS_NUMIDENT"><data key="edge_relationship_id">R153_R030</data><data key="edge_source_entity_id">R153_E017</data><data key="edge_relationship_type">can_use_authorized_records_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA POMS identifies SORN 60-0058 as one possible record source for state vital records disclosures.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S003.</data></edge><edge id="R153_R031" source="R153_E017" target="SYS_MBR"><data key="edge_relationship_id">R153_R031</data><data key="edge_source_entity_id">R153_E017</data><data key="edge_relationship_type">can_use_authorized_records_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA POMS identifies SORN 60-0090 as one possible record source for state vital records disclosures.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S003.</data></edge><edge id="R153_R032" source="R153_E017" target="SYS_SSR"><data key="edge_relationship_id">R153_R032</data><data key="edge_source_entity_id">R153_E017</data><data key="edge_relationship_type">can_use_authorized_records_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA POMS identifies SORN 60-0103 as one possible record source for state vital records disclosures.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S003.</data></edge><edge id="R153_R033" source="R153_E018" target="ORG_SSA_OAG"><data key="edge_relationship_id">R153_R033</data><data key="edge_source_entity_id">R153_E018</data><data key="edge_relationship_type">documents_procurement_of</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">GAO aggregated annual SSA IT contract obligations while evaluating OAG contracting workforce; numbers do not establish a named technology deployment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S002.</data></edge><edge id="R153_R034" source="R153_E019" target="ORG_SSA_OAG"><data key="edge_relationship_id">R153_R034</data><data key="edge_source_entity_id">R153_E019</data><data key="edge_relationship_type">implemented_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">GAO reports senior procurement executive addressed IT contracting officer workload assessment using contract complexity and quantity by April 2026.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S002.</data></edge><edge id="R153_R035" source="R153_E020" target="ORG_SSA_OAG"><data key="edge_relationship_id">R153_R035</data><data key="edge_source_entity_id">R153_E020</data><data key="edge_relationship_type">implemented_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">GAO recommendation 2 closed after FY2026 training plan and mandatory IT acquisition training.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S002.</data></edge><edge id="R153_R036" source="R153_E022" target="R153_E020"><data key="edge_relationship_id">R153_R036</data><data key="edge_source_entity_id">R153_E022</data><data key="edge_relationship_type">addressed_by</data><data key="edge_target_entity_id">R153_E020</data><data key="edge_operational_context">2025 GAO finding of 2019 training-plan staleness is mitigated by FY2026 mandatory training plan according to later recommendation status.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S002.</data></edge><edge id="R153_R037" source="R153_E019" target="R153_E021"><data key="edge_relationship_id">R153_R037</data><data key="edge_source_entity_id">R153_E019</data><data key="edge_relationship_type">is_contrasted_with</data><data key="edge_target_entity_id">R153_E021</data><data key="edge_operational_context">GAO acquisition officer workload recommendation closed in April 2026; contracting officer representative workload recommendation remains open.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source R153_S002.</data></edge><edge id="R153_R038" source="DATA_USPS_NATIONAL_ZIP4" target="DATA_OASDI_STATE_COUNTY_2025"><data key="edge_relationship_id">R153_R038</data><data key="edge_source_entity_id">DATA_USPS_NATIONAL_ZIP4</data><data key="edge_relationship_type">contributes_county_reference_to</data><data key="edge_target_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_operational_context">2025 OASDI county statistical geography assigns county using USPS national 9-digit ZIP+4; postal delivery geography is not necessarily beneficiary residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R61_005.</data></edge><edge id="R153_R039" source="R138_E0013" target="DATA_OASDI_STATE_COUNTY_2025"><data key="edge_relationship_id">R153_R039</data><data key="edge_source_entity_id">R138_E0013</data><data key="edge_relationship_type">limits_inference_from</data><data key="edge_target_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_operational_context">For cases with representative payees, published beneficiary state/county is payee geography; cannot infer individual claimant congressional district.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R61_005.</data></edge><edge id="R153_R040" source="R138_E0025" target="DATA_SSI_STATE_COUNTY_2025"><data key="edge_relationship_id">R153_R040</data><data key="edge_source_entity_id">R138_E0025</data><data key="edge_relationship_type">limits_inference_from</data><data key="edge_target_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_operational_context">SSI reported county values may be suppressed and reported rounded county dollars may not add to independent state dollar totals.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R61_006.</data></edge><edge id="R154_R0001" source="APP_SERS" target="R154_E001"><data key="edge_relationship_id">R154_R0001</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">provides_screen</data><data key="edge_target_entity_id">R154_E001</data><data key="edge_operational_context">Order Tracker is within SERS Orders tab and exposes electronic remittance list and scanned item images.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0002" source="R154_E001" target="R154_E002"><data key="edge_relationship_id">R154_R0002</data><data key="edge_source_entity_id">R154_E001</data><data key="edge_relationship_type">supports_supervisor_control</data><data key="edge_target_entity_id">R154_E002</data><data key="edge_operational_context">Daily Order Tracker listing reconciled by supervisor to FO remittance check log.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0003" source="R154_E002" target="REPORT_DMS_FODRL"><data key="edge_relationship_id">R154_R0003</data><data key="edge_source_entity_id">R154_E002</data><data key="edge_relationship_type">separately_reconciles</data><data key="edge_target_entity_id">REPORT_DMS_FODRL</data><data key="edge_operational_context">FODRL applies to non-SERS DMS entries, not SERS; supervisors reconcile each route separately.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0004" source="R154_E002" target="APP_DMS"><data key="edge_relationship_id">R154_R0004</data><data key="edge_source_entity_id">R154_E002</data><data key="edge_relationship_type">reconciles_separate_route</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Non-SERS receipts use DMS FORT, CCFORT and FODRL reconciliation.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0005" source="APP_SERS" target="R154_E003"><data key="edge_relationship_id">R154_R0005</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">governs_physical_originals_under</data><data key="edge_target_entity_id">R154_E003</data><data key="edge_operational_context">SERS paper items secured for five days after scan and non-negotiable marking, then shredded.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0006" source="R154_E003" target="R154_E006"><data key="edge_relationship_id">R154_R0006</data><data key="edge_source_entity_id">R154_E003</data><data key="edge_relationship_type">enforces_nonduplicative_routing</data><data key="edge_target_entity_id">R154_E006</data><data key="edge_operational_context">SERS checks do not go to MATPSC for redundant physical processing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0007" source="APP_SERS" target="R154_E006"><data key="edge_relationship_id">R154_R0007</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">applies_double_mail_prevention</data><data key="edge_target_entity_id">R154_E006</data><data key="edge_operational_context">DMS versus SERS boundaries determine physical mailing to MATPSC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0008" source="R154_E001" target="R154_E004"><data key="edge_relationship_id">R154_R0008</data><data key="edge_source_entity_id">R154_E001</data><data key="edge_relationship_type">supports_incorrect_order_flag</data><data key="edge_target_entity_id">R154_E004</data><data key="edge_operational_context">Submit/Update Incorrect Order entry precedes documented MDW corrections.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0009" source="R154_E005" target="R154_E004"><data key="edge_relationship_id">R154_R0009</data><data key="edge_source_entity_id">R154_E005</data><data key="edge_relationship_type">requires_manual_flag_and_correction</data><data key="edge_target_entity_id">R154_E004</data><data key="edge_operational_context">Wrong scanned instrument can result in duplicate apparent credit pending manual correction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0010" source="R154_E005" target="R154_E001"><data key="edge_relationship_id">R154_R0010</data><data key="edge_source_entity_id">R154_E005</data><data key="edge_relationship_type">is_handled_using</data><data key="edge_target_entity_id">R154_E001</data><data key="edge_operational_context">SERS Order Tracker records flagged incorrect scan and later corrective action.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0011" source="STORE_SERS_PROGRAMMATIC" target="R154_E006"><data key="edge_relationship_id">R154_R0011</data><data key="edge_source_entity_id">STORE_SERS_PROGRAMMATIC</data><data key="edge_relationship_type">subject_to_no_duplicate_mail_rule</data><data key="edge_target_entity_id">R154_E006</data><data key="edge_operational_context">Programmatic scanned remittances are not physically forwarded to MATPSC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0012" source="STORE_SERS_CONSERVED" target="R154_E006"><data key="edge_relationship_id">R154_R0012</data><data key="edge_source_entity_id">STORE_SERS_CONSERVED</data><data key="edge_relationship_type">subject_to_no_duplicate_mail_rule</data><data key="edge_target_entity_id">R154_E006</data><data key="edge_operational_context">Conserved funds SERS scanned remittances follow same no-duplicate-forwarding protection.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC223; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0013" source="SVC_TOP" target="R154_E007"><data key="edge_relationship_id">R154_R0013</data><data key="edge_source_entity_id">SVC_TOP</data><data key="edge_relationship_type">matches_debtors_using</data><data key="edge_target_entity_id">R154_E007</data><data key="edge_operational_context">Treasury certified disbursement matching uses TIN/BOAN plus name control, not matching by postal address.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC219; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0014" source="APP_ECO" target="R154_E009"><data key="edge_relationship_id">R154_R0014</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">pre_offset_notifies_through</data><data key="edge_target_entity_id">R154_E009</data><data key="edge_operational_context">ECO emits advance 60-day notices before qualifying external referral.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC219; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0015" source="SVC_TOP" target="R154_E008"><data key="edge_relationship_id">R154_R0015</data><data key="edge_source_entity_id">SVC_TOP</data><data key="edge_relationship_type">separates_legal_participation_roles</data><data key="edge_target_entity_id">R154_E008</data><data key="edge_operational_context">SSA acts in Treasury TOP as payment and creditor agency, but inter-SSA cross-program recovery is internally administered.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC219; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0016" source="R154_E008" target="APP_ECO"><data key="edge_relationship_id">R154_R0016</data><data key="edge_source_entity_id">R154_E008</data><data key="edge_relationship_type">uses_internal_debt_management</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">ECO identifies outside debts for Treasury; internal benefit-to-benefit recovery follows separate SSA process.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Validated by SRC219; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0017" source="SVC_E1696" target="R154_E010"><data key="edge_relationship_id">R154_R0017</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">uses_two_party_signature_routing</data><data key="edge_target_entity_id">R154_E010</data><data key="edge_operational_context">Representative signs first and claimant signs second; no partial submission to SSA.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC001; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0018" source="R154_E010" target="TECH_ADOBE_SIGN"><data key="edge_relationship_id">R154_R0018</data><data key="edge_source_entity_id">R154_E010</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_ADOBE_SIGN</data><data key="edge_operational_context">Public web portal explicitly states Adobe Sign intermediary and confirmation emails.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC001; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0019" source="SVC_E1696" target="R154_E011"><data key="edge_relationship_id">R154_R0019</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">enforces_time_to_completion</data><data key="edge_target_entity_id">R154_E011</data><data key="edge_operational_context">Fifteen-calendar-day expiry for pending two-signer form.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC001; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0020" source="SVC_E1696" target="R154_E012"><data key="edge_relationship_id">R154_R0020</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">deletes_unsubmitted_session_data_under</data><data key="edge_target_entity_id">R154_E012</data><data key="edge_operational_context">After 60 minutes without activity web session expires and entered data are deleted; complete archived forms not covered.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC001; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0021" source="R154_E010" target="R154_E013"><data key="edge_relationship_id">R154_R0021</data><data key="edge_source_entity_id">R154_E010</data><data key="edge_relationship_type">routes_using_transaction_specific_contacts</data><data key="edge_target_entity_id">R154_E013</data><data key="edge_operational_context">Separate claimant and representative email fields control signing invitation delivery; no MBR/SSR mailing update inferred.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC001; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0022" source="R154_E010" target="R154_E014"><data key="edge_relationship_id">R154_R0022</data><data key="edge_source_entity_id">R154_E010</data><data key="edge_relationship_type">authenticates_using</data><data key="edge_target_entity_id">R154_E014</data><data key="edge_operational_context">Representative creates shared access password that cannot be reset and should be transmitted via different channel.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC001; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0023" source="R154_E011" target="R154_E015"><data key="edge_relationship_id">R154_R0023</data><data key="edge_source_entity_id">R154_E011</data><data key="edge_relationship_type">terminates_pending_reminders_for</data><data key="edge_target_entity_id">R154_E015</data><data key="edge_operational_context">Daily e-signature reminders continue until completion or expiry.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC001; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0024" source="SVC_E1696" target="R154_E015"><data key="edge_relationship_id">R154_R0024</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">provides_submission_and_processing_notices</data><data key="edge_target_entity_id">R154_E015</data><data key="edge_operational_context">Signed electronic form delivery is followed by postal processing notification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC001; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0025" source="APP_RASR" target="R154_E010"><data key="edge_relationship_id">R154_R0025</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">receives_only_completed_e1696_appointment_process</data><data key="edge_target_entity_id">R154_E010</data><data key="edge_operational_context">The RASR appointment relationship depends on completed claimant and representative signing; SSA processing follows submission.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Validated by SRC409; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0026" source="R109_E024" target="R154_E016"><data key="edge_relationship_id">R154_R0026</data><data key="edge_source_entity_id">R109_E024</data><data key="edge_relationship_type">delegates_redemption_without_ownership_through</data><data key="edge_target_entity_id">R154_E016</data><data key="edge_operational_context">TreasuryDirect With signer may have operational redemption authority without legal ownership until owner death.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0027" source="R109_E024" target="R154_E017"><data key="edge_relationship_id">R154_R0027</data><data key="edge_source_entity_id">R109_E024</data><data key="edge_relationship_type">uses_inaccessible_electronic_gift_rule</data><data key="edge_target_entity_id">R154_E017</data><data key="edge_operational_context">Electronic gift held by purchaser may not be accessible to registered recipient for SSI.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0028" source="R109_E024" target="R154_E018"><data key="edge_relationship_id">R154_R0028</data><data key="edge_source_entity_id">R109_E024</data><data key="edge_relationship_type">assigns_electronic_bond_issue_identifiers</data><data key="edge_target_entity_id">R154_E018</data><data key="edge_operational_context">Book-entry bonds use issue-confirmation IDs rather than paper bond serials.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0029" source="R109_E025" target="R154_E019"><data key="edge_relationship_id">R154_R0029</data><data key="edge_source_entity_id">R109_E025</data><data key="edge_relationship_type">supplies_owner_produced_evidence_for</data><data key="edge_target_entity_id">R154_E019</data><data key="edge_operational_context">TreasuryDirect Current Holdings statement is claimant-supplied evidence used to document value on SSA EVID.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0030" source="R154_E019" target="APP_EVID"><data key="edge_relationship_id">R154_R0030</data><data key="edge_source_entity_id">R154_E019</data><data key="edge_relationship_type">is_entered_into</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Technician records confirmation number and current bond value in SSA evidence system.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0031" source="R154_E019" target="R154_E018"><data key="edge_relationship_id">R154_R0031</data><data key="edge_source_entity_id">R154_E019</data><data key="edge_relationship_type">may_use</data><data key="edge_target_entity_id">R154_E018</data><data key="edge_operational_context">EVID records issue confirmation number for electronic bond, serial number for paper bond.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0032" source="SYS_SSR" target="R154_E020"><data key="edge_relationship_id">R154_R0032</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">maintains_non_mssics_bond_resource_attributes</data><data key="edge_target_entity_id">R154_E020</data><data key="edge_operational_context">SSR remarks include bond series, value, date and RE21 in non-MSSICS cases.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0033" source="R154_E020" target="R154_E021"><data key="edge_relationship_id">R154_R0033</data><data key="edge_source_entity_id">R154_E020</data><data key="edge_relationship_type">involves_resource_owner_identification_rule</data><data key="edge_target_entity_id">R154_E021</data><data key="edge_operational_context">Paper bond displayed SSN does not itself establish legal ownership.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0034" source="ALERT_SSI_SAVINGS_SECURITY" target="R154_E021"><data key="edge_relationship_id">R154_R0034</data><data key="edge_source_entity_id">ALERT_SSI_SAVINGS_SECURITY</data><data key="edge_relationship_type">requires_owner_verification_based_on</data><data key="edge_target_entity_id">R154_E021</data><data key="edge_operational_context">Matched SSN in Treasury alert is an investigative lead; check registered name before accepting ownership.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R62_015; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0035" source="UI_MSSICS_DSAB" target="R154_E017"><data key="edge_relationship_id">R154_R0035</data><data key="edge_source_entity_id">UI_MSSICS_DSAB</data><data key="edge_relationship_type">distinguishes_owner_access_from_allegation</data><data key="edge_target_entity_id">R154_E017</data><data key="edge_operational_context">For inaccessible electronic gift bond, determine access and document ownership/access status.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by SRC_R107_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0036" source="APP_IRMAA" target="R154_E022"><data key="edge_relationship_id">R154_R0036</data><data key="edge_source_entity_id">APP_IRMAA</data><data key="edge_relationship_type">supports_corrected_irs_data_processing</data><data key="edge_target_entity_id">R154_E022</data><data key="edge_operational_context">Revised IRS data enter IRMAA new initial determination only with prescribed proof.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC003; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0037" source="R154_E022" target="UI_IRMAA_PYTY"><data key="edge_relationship_id">R154_R0037</data><data key="edge_source_entity_id">R154_E022</data><data key="edge_relationship_type">uses_tax_year_selection</data><data key="edge_target_entity_id">UI_IRMAA_PYTY</data><data key="edge_operational_context">PYTY selects New Tax Data to use corrected tax-year evidence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC003; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0038" source="R154_E022" target="UI_IRMAA_IRMA"><data key="edge_relationship_id">R154_R0038</data><data key="edge_source_entity_id">R154_E022</data><data key="edge_relationship_type">records_income_tax_attributes</data><data key="edge_target_entity_id">UI_IRMAA_IRMA</data><data key="edge_operational_context">IRMA marks source as IRS Tax Correction Data and proof as proven or pending.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC003; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0039" source="R154_E022" target="APP_EVID"><data key="edge_relationship_id">R154_R0039</data><data key="edge_source_entity_id">R154_E022</data><data key="edge_relationship_type">records_correction_evidence_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">IRS correction letter/transcript and return proof documented using EVID WAGES evidence category.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC003; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0040" source="R154_E022" target="R154_E023"><data key="edge_relationship_id">R154_R0040</data><data key="edge_source_entity_id">R154_E022</data><data key="edge_relationship_type">requires_specific_identity_fraud_proof_when_applicable</data><data key="edge_target_entity_id">R154_E023</data><data key="edge_operational_context">Identity-theft claim needs IRS TRDBV transcript or qualifying TDS Letter 3538; no automatic identity master correction asserted.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC003; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0041" source="R154_E022" target="R154_E024"><data key="edge_relationship_id">R154_R0041</data><data key="edge_source_entity_id">R154_E022</data><data key="edge_relationship_type">permits_specific_transcription_error_exception</data><data key="edge_target_entity_id">R154_E024</data><data key="edge_operational_context">Obvious TEI transcription error may use signed return only absent investigation or protest.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC003; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0042" source="R154_E024" target="UI_IRMAA_IRMA"><data key="edge_relationship_id">R154_R0042</data><data key="edge_source_entity_id">R154_E024</data><data key="edge_relationship_type">used_in</data><data key="edge_target_entity_id">UI_IRMAA_IRMA</data><data key="edge_operational_context">IRMA screen marks corrected TEI as IRS Tax Correction Data with proof.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC003; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0043" source="ORG_SSA_OAG" target="R154_E025"><data key="edge_relationship_id">R154_R0043</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">enforces_contracting_authority_rules</data><data key="edge_target_entity_id">R154_E025</data><data key="edge_operational_context">Only delegated contracting officer or authorized micro-purchaser can create binding instrument.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC002; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0044" source="R154_E025" target="R154_E026"><data key="edge_relationship_id">R154_R0044</data><data key="edge_source_entity_id">R154_E025</data><data key="edge_relationship_type">may_be_cured_only_through</data><data key="edge_target_entity_id">R154_E026</data><data key="edge_operational_context">Unauthorized commitment not binding absent discretionary compliant ratification.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC002; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0045" source="R154_E025" target="R154_E027"><data key="edge_relationship_id">R154_R0045</data><data key="edge_source_entity_id">R154_E025</data><data key="edge_relationship_type">is_subject_to_delegated_spending_rules</data><data key="edge_target_entity_id">R154_E027</data><data key="edge_operational_context">OAG public notice lists limits; source undated, current controlling limits should be validated.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">Validated by R154_SRC002; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R154_R0046" source="PROC_T2_SSI_ADDR_RECENCY" target="SYS_SSR"><data key="edge_relationship_id">R154_R0046</data><data key="edge_source_entity_id">PROC_T2_SSI_ADDR_RECENCY</data><data key="edge_relationship_type">requires_separate_program_update_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title II address development can require independent field-office SSI Claims System action to correct SSR rather than an automatic MBR-to-SSR flow.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">4</data><data key="edge_notes">Validated by SRC_R47_010; does not imply unstated database, transport, persistence, automated propagation or vendor deployment.</data></edge><edge id="R155_R0001" source="APP_ERPS" target="R155_E0001"><data key="edge_relationship_id">R155_R0001</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">initiates_title_ii_nightly_address_propagation</data><data key="edge_target_entity_id">R155_E0001</data><data key="edge_operational_context">Individual payee Title II address entry is transmitted to MBR the night following eRPS input.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0002" source="R155_E0001" target="SYS_MBR"><data key="edge_relationship_id">R155_R0002</data><data key="edge_source_entity_id">R155_E0001</data><data key="edge_relationship_type">nightly_posts_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Individual payee change of address; next-night MBR update; no universal live synchronization claim.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0003" source="APP_ERPS" target="R155_E0002"><data key="edge_relationship_id">R155_R0003</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">requires_separate_title_xvi_address_entry</data><data key="edge_target_entity_id">R155_E0002</data><data key="edge_operational_context">Individual payee Title XVI change requires additional MSSICS input.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0004" source="R155_E0002" target="APP_MSSICS"><data key="edge_relationship_id">R155_R0004</data><data key="edge_source_entity_id">R155_E0002</data><data key="edge_relationship_type">requires_operator_entry_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">eRPS does not send individual-payee COA to SSR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0005" source="R155_E0002" target="SYS_SSR"><data key="edge_relationship_id">R155_R0005</data><data key="edge_source_entity_id">R155_E0002</data><data key="edge_relationship_type">results_in_program_record_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">After operator builds SSR from MSSICS, Title XVI record reflects COA.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0006" source="APP_ERPS" target="R155_E0003"><data key="edge_relationship_id">R155_R0006</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">supports_institutional_payee_address_path</data><data key="edge_target_entity_id">R155_E0003</data><data key="edge_operational_context">Institutional payees correctly registered in eRPS are an explicit exception.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0007" source="R155_E0003" target="SYS_MBR"><data key="edge_relationship_id">R155_R0007</data><data key="edge_source_entity_id">R155_E0003</data><data key="edge_relationship_type">automatically_updates_title_ii</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Institution address input propagates across associated Title II cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0008" source="R155_E0003" target="SYS_SSR"><data key="edge_relationship_id">R155_R0008</data><data key="edge_source_entity_id">R155_E0003</data><data key="edge_relationship_type">automatically_updates_title_xvi</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Institution address input propagates across associated Title XVI cases; not individual payees.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0009" source="APP_ERPS" target="R155_E0004"><data key="edge_relationship_id">R155_R0009</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">triggers_custody_residence_review</data><data key="edge_target_entity_id">R155_E0004</data><data key="edge_operational_context">Collect actual residence of payee and beneficiaries and verify custody when mailing address changes.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0010" source="R155_E0005" target="APP_ERPS"><data key="edge_relationship_id">R155_R0010</data><data key="edge_source_entity_id">R155_E0005</data><data key="edge_relationship_type">requires_parallel_record_action_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">MACADE processing-center address input does not replace eRPS update.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0011" source="R155_E0004" target="R155_E0002"><data key="edge_relationship_id">R155_R0011</data><data key="edge_source_entity_id">R155_E0004</data><data key="edge_relationship_type">operationally_informs</data><data key="edge_target_entity_id">R155_E0002</data><data key="edge_operational_context">Payee mailing change and beneficiary residence/custody must be evaluated separately.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0012" source="APP_MAPS" target="R155_E0006"><data key="edge_relationship_id">R155_R0012</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_manual_correction_screen</data><data key="edge_target_entity_id">R155_E0006</data><data key="edge_operational_context">MCOR visible in the MAPS Development Worksheet.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0013" source="APP_MAPS" target="R155_E0007"><data key="edge_relationship_id">R155_R0013</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_report_date_editor</data><data key="edge_target_entity_id">R155_E0007</data><data key="edge_operational_context">DEDS supports manual-correction effective-date edits.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0014" source="UI_MAPS_DEV_WORKSHEET" target="R155_E0006"><data key="edge_relationship_id">R155_R0014</data><data key="edge_source_entity_id">UI_MAPS_DEV_WORKSHEET</data><data key="edge_relationship_type">launches</data><data key="edge_target_entity_id">R155_E0006</data><data key="edge_operational_context">After determination, technician chooses Manual Correction on DWMP.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0015" source="R155_E0006" target="R155_E0008"><data key="edge_relationship_id">R155_R0015</data><data key="edge_source_entity_id">R155_E0006</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">R155_E0008</data><data key="edge_operational_context">Creates new correction application following specified error conditions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0016" source="R155_E0008" target="R155_E0009"><data key="edge_relationship_id">R155_R0016</data><data key="edge_source_entity_id">R155_E0008</data><data key="edge_relationship_type">triggers_identity_field_propagation_exception</data><data key="edge_target_entity_id">R155_E0009</data><data key="edge_operational_context">When corrected SSN, some prior application data do not propagate.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0017" source="R155_E0008" target="R155_E0010"><data key="edge_relationship_id">R155_R0017</data><data key="edge_source_entity_id">R155_E0008</data><data key="edge_relationship_type">initiates_new_external_tax_inquiry</data><data key="edge_target_entity_id">R155_E0010</data><data key="edge_operational_context">MAPS re-requests IRS data when correction treated as new application.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0018" source="R155_E0010" target="ORG_IRS"><data key="edge_relationship_id">R155_R0018</data><data key="edge_source_entity_id">R155_E0010</data><data key="edge_relationship_type">requests_information_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">No specific IRS file/transport or address-master update established by POMS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0019" source="R155_E0008" target="R155_E0011"><data key="edge_relationship_id">R155_R0019</data><data key="edge_source_entity_id">R155_E0008</data><data key="edge_relationship_type">subject_to_one_action_daily</data><data key="edge_target_entity_id">R155_E0011</data><data key="edge_operational_context">One manual correction per SSN per day.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0020" source="R155_E0008" target="R155_E0012"><data key="edge_relationship_id">R155_R0020</data><data key="edge_source_entity_id">R155_E0008</data><data key="edge_relationship_type">subject_to_technician_error_window</data><data key="edge_target_entity_id">R155_E0012</data><data key="edge_operational_context">Initial determination or hearing decision error correction within 60 days.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0021" source="R155_E0008" target="R155_E0013"><data key="edge_relationship_id">R155_R0021</data><data key="edge_source_entity_id">R155_E0008</data><data key="edge_relationship_type">creates_pending_subsidy_redetermination</data><data key="edge_target_entity_id">R155_E0013</data><data key="edge_operational_context">New pending application sent to subsidy determination, potentially new verification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0022" source="R155_E0013" target="PROC_MAPS_VERIFICATION"><data key="edge_relationship_id">R155_R0022</data><data key="edge_source_entity_id">R155_E0013</data><data key="edge_relationship_type">uses_verification_procedure</data><data key="edge_target_entity_id">PROC_MAPS_VERIFICATION</data><data key="edge_operational_context">Reprocessing may create agency discrepancy verification issues.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0023" source="R155_E0006" target="R155_E0007"><data key="edge_relationship_id">R155_R0023</data><data key="edge_source_entity_id">R155_E0006</data><data key="edge_relationship_type">uses_report_date_screen</data><data key="edge_target_entity_id">R155_E0007</data><data key="edge_operational_context">Manual corrections can require Report Date adjustment to preserve entitlement effective date.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0024" source="IFACE_SSI_DIRECT_SSR" target="R155_E0014"><data key="edge_relationship_id">R155_R0024</data><data key="edge_source_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_relationship_type">offers_disposition_screen</data><data key="edge_target_entity_id">R155_E0014</data><data key="edge_operational_context">UOPD selects SSI debt disposition; underlying SSR is record of decision.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0025" source="R155_E0014" target="SYS_SSR"><data key="edge_relationship_id">R155_R0025</data><data key="edge_source_entity_id">R155_E0014</data><data key="edge_relationship_type">records_dispositions_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Overpayment final dispositions are documented on SSR for any amount.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0026" source="R155_E0014" target="R155_E0015"><data key="edge_relationship_id">R155_R0026</data><data key="edge_source_entity_id">R155_E0014</data><data key="edge_relationship_type">enforces_noncollection_review_above_2000</data><data key="edge_target_entity_id">R155_E0015</data><data key="edge_operational_context">Two PIN review for amounts &gt;2000 and &lt;5000; not a blanket rule for collect decisions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0027" source="R155_E0014" target="R155_E0016"><data key="edge_relationship_id">R155_R0027</data><data key="edge_source_entity_id">R155_E0014</data><data key="edge_relationship_type">enforces_management_concurrence_at_5000</data><data key="edge_target_entity_id">R155_E0016</data><data key="edge_operational_context">Noncollect &gt;=5000 requires FO management concurrence; fraud has additional conditions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0028" source="R155_E0017" target="REPO_NDRED"><data key="edge_relationship_id">R155_R0028</data><data key="edge_source_entity_id">R155_E0017</data><data key="edge_relationship_type">uploads_to</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Non-MSSICS noncollection rationale from SSA-5002 via Evidence Portal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0029" source="SYS_SSR" target="R155_E0018"><data key="edge_relationship_id">R155_R0029</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">auto_recalculates_jurisdiction_after_address_entry</data><data key="edge_target_entity_id">R155_E0018</data><data key="edge_operational_context">In Puerto Rico and USVI residence case, posting new address automatically posts DIS FO code on SSR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0030" source="R155_E0018" target="APP_MSSICS"><data key="edge_relationship_id">R155_R0030</data><data key="edge_source_entity_id">R155_E0018</data><data key="edge_relationship_type">requires_case_transfer_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Transfer to Downtown Manhattan FO 109; specific documented administrative routing, not generic postal logic.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0031" source="R155_E0019" target="SYS_MBR"><data key="edge_relationship_id">R155_R0031</data><data key="edge_source_entity_id">R155_E0019</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">After correction of Ticket eligibility coding, query two workdays later.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0032" source="R155_E0019" target="SYS_SSR"><data key="edge_relationship_id">R155_R0032</data><data key="edge_source_entity_id">R155_E0019</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">After correction of Ticket eligibility coding, query two workdays later.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0033" source="R155_E0019" target="DB_DCF"><data key="edge_relationship_id">R155_R0033</data><data key="edge_source_entity_id">R155_E0019</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">After correction of Ticket eligibility coding, query two workdays later.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0034" source="R155_E0019" target="R155_E0020"><data key="edge_relationship_id">R155_R0034</data><data key="edge_source_entity_id">R155_E0019</data><data key="edge_relationship_type">presents_results_through</data><data key="edge_target_entity_id">R155_E0020</data><data key="edge_operational_context">General Ticket Query displays whether selection date has appeared.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0035" source="APP_POS" target="R155_E0021"><data key="edge_relationship_id">R155_R0035</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">corrects_residence_geographic_code_for</data><data key="edge_target_entity_id">R155_E0021</data><data key="edge_operational_context">When payee mailing and beneficiary residence differ, fix state/county on beneficiary record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0036" source="R155_E0021" target="DATA_MBR_RESIDENCE_SCC"><data key="edge_relationship_id">R155_R0036</data><data key="edge_source_entity_id">R155_E0021</data><data key="edge_relationship_type">records_residence_code_on</data><data key="edge_target_entity_id">DATA_MBR_RESIDENCE_SCC</data><data key="edge_operational_context">Title II actual residence SCC, independent of payee mailing location.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0037" source="R155_E0022" target="DB_DCF"><data key="edge_relationship_id">R155_R0037</data><data key="edge_source_entity_id">R155_E0022</data><data key="edge_relationship_type">reconciles_medical_determination_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">PC can input DDSQ favorable CDR data when DCF stale; SSI may post via SSR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0038" source="R155_E0022" target="SYS_SSR"><data key="edge_relationship_id">R155_R0038</data><data key="edge_source_entity_id">R155_E0022</data><data key="edge_relationship_type">may_trigger_update_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI DDSQ CDR information can be posted to SSR and then DCF updates automatically.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0039" source="DATA_OAG_HQ_AWARDS" target="R155_E0023"><data key="edge_relationship_id">R155_R0039</data><data key="edge_source_entity_id">DATA_OAG_HQ_AWARDS</data><data key="edge_relationship_type">exposes_csv_download</data><data key="edge_target_entity_id">R155_E0023</data><data key="edge_operational_context">OAG 2023 posted award listing export; excludes award modifications and BPA call orders.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Historical 2023 listing date, not 2026 award confirmation.</data></edge><edge id="R155_R0040" source="DATA_OAG_HQ_AWARDS" target="R155_E0024"><data key="edge_relationship_id">R155_R0040</data><data key="edge_source_entity_id">DATA_OAG_HQ_AWARDS</data><data key="edge_relationship_type">exposes_xml_download</data><data key="edge_target_entity_id">R155_E0024</data><data key="edge_operational_context">OAG 2023 posted award listing export; excludes award modifications and BPA call orders.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Historical 2023 listing date, not 2026 award confirmation.</data></edge><edge id="R155_R0041" source="DATA_OAG_HQ_AWARDS" target="R155_E0025"><data key="edge_relationship_id">R155_R0041</data><data key="edge_source_entity_id">DATA_OAG_HQ_AWARDS</data><data key="edge_relationship_type">exposes_json_download</data><data key="edge_target_entity_id">R155_E0025</data><data key="edge_operational_context">OAG 2023 posted award listing export; excludes award modifications and BPA call orders.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Historical 2023 listing date, not 2026 award confirmation.</data></edge><edge id="R155_R0042" source="SYS_MBR" target="R155_E0026"><data key="edge_relationship_id">R155_R0042</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_statistical_product</data><data key="edge_target_entity_id">R155_E0026</data><data key="edge_operational_context">100% MBR population, December 2025 withheld retired-worker awards.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0043" source="SYS_MBR" target="R155_E0027"><data key="edge_relationship_id">R155_R0043</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_statistical_product</data><data key="edge_target_entity_id">R155_E0027</data><data key="edge_operational_context">100% MBR population, December 2025 all-beneficiary withheld reasons.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0044" source="R155_E0027" target="R155_E0028"><data key="edge_relationship_id">R155_R0044</data><data key="edge_source_entity_id">R155_E0027</data><data key="edge_relationship_type">reports_address_quality_category</data><data key="edge_target_entity_id">R155_E0028</data><data key="edge_operational_context">162,312 benefits withheld for address unknown (not 162,312 distinct persons).</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0045" source="SVC_SAM" target="R155_E0029"><data key="edge_relationship_id">R155_R0045</data><data key="edge_source_entity_id">SVC_SAM</data><data key="edge_relationship_type">supplies_auto_vendor_financial_change</data><data key="edge_target_entity_id">R155_E0029</data><data key="edge_operational_context">SSA vendor direct deposit page says SAM financial changes automatically update SSA database.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0046" source="R155_E0029" target="DB_VENDOR_PAYMENT_UNNAMED"><data key="edge_relationship_id">R155_R0046</data><data key="edge_source_entity_id">R155_E0029</data><data key="edge_relationship_type">targets_unnamed_administrative_vendor_database</data><data key="edge_target_entity_id">DB_VENDOR_PAYMENT_UNNAMED</data><data key="edge_operational_context">Exact physical database, transport, latency not specified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R155_R0047" source="APP_EDCS" target="R155_E0030"><data key="edge_relationship_id">R155_R0047</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">has_excluded_case_visibility_boundary</data><data key="edge_target_entity_id">R155_E0030</data><data key="edge_operational_context">An excluded appeal not in EDCS cannot be tracked there, may be visible only in MI Central.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R155_R0048" source="R155_E0030" target="R124_E004"><data key="edge_relationship_id">R155_R0048</data><data key="edge_source_entity_id">R155_E0030</data><data key="edge_relationship_type">has_conditional_tracking_in</data><data key="edge_target_entity_id">R124_E004</data><data key="edge_operational_context">CDR reconsideration excluded from electronic EDCS processing, except specific Title II hearing-tickle cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R156_R0001" source="APP_PER_TDR_MODELS" target="R156_E0002"><data key="edge_relationship_id">R156_R0001</data><data key="edge_source_entity_id">APP_PER_TDR_MODELS</data><data key="edge_relationship_type">selects</data><data key="edge_target_entity_id">R156_E0002</data><data key="edge_operational_context">Predictive model randomly selects high-error-risk favorable Title II and adult Title XVI determinations for statutory pre-effectuation review.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0002" source="APP_PER_TDR_MODELS" target="R156_E0003"><data key="edge_relationship_id">R156_R0002</data><data key="edge_source_entity_id">APP_PER_TDR_MODELS</data><data key="edge_relationship_type">selects</data><data key="edge_target_entity_id">R156_E0003</data><data key="edge_operational_context">Model selects discretionary targeted denied cases; corrections controlled but TDR finding not charged against QA performance accuracy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0003" source="PROC_DQR_QUALITY_REVIEW" target="R156_E0001"><data key="edge_relationship_id">R156_R0003</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">draws_sample_from</data><data key="edge_target_entity_id">R156_E0001</data><data key="edge_operational_context">DQR QA results feed state adjudicating-component performance accuracy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0004" source="PROC_PER_DISABILITY_REVIEW" target="R156_E0002"><data key="edge_relationship_id">R156_R0004</data><data key="edge_source_entity_id">PROC_PER_DISABILITY_REVIEW</data><data key="edge_relationship_type">uses_sample</data><data key="edge_target_entity_id">R156_E0002</data><data key="edge_operational_context">Pre-effectuation quality controls before favorable award is effected.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0005" source="PROC_DQR_QUALITY_REVIEW" target="R156_E0003"><data key="edge_relationship_id">R156_R0005</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">uses_sample</data><data key="edge_target_entity_id">R156_E0003</data><data key="edge_operational_context">Discretionary targeted-denial reviews identify deficiency-prone cases.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0006" source="APP_QRCPS" target="R156_E0004"><data key="edge_relationship_id">R156_R0006</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0004</data><data key="edge_operational_context">Excluded review cases coded in DQR case processing before routing to field office.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0007" source="APP_QRCPS" target="R156_E0005"><data key="edge_relationship_id">R156_R0007</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0005</data><data key="edge_operational_context">Reviewer classifies potentially determination-reversing deficiency.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0008" source="APP_QRCPS" target="R156_E0006"><data key="edge_relationship_id">R156_R0008</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0006</data><data key="edge_operational_context">Reviewer records deficiency affecting disability period.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0009" source="APP_QRCPS" target="R156_E0007"><data key="edge_relationship_id">R156_R0009</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0007</data><data key="edge_operational_context">Reviewer records procedural technical corrective actions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0010" source="APP_QRCPS" target="R156_E0008"><data key="edge_relationship_id">R156_R0010</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R156_E0008</data><data key="edge_operational_context">QRCPS creates Request for Case Action; reviewer adds rationale and action instructions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0011" source="APP_QRCPS" target="R156_E0009"><data key="edge_relationship_id">R156_R0011</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">propagates_fields_into</data><data key="edge_target_entity_id">R156_E0009</data><data key="edge_operational_context">Populates SSN, claimant name, claim type/level, adjudicating component.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0012" source="R156_E0009" target="R156_E0008"><data key="edge_relationship_id">R156_R0012</data><data key="edge_source_entity_id">R156_E0009</data><data key="edge_relationship_type">included_in</data><data key="edge_target_entity_id">R156_E0008</data><data key="edge_operational_context">Customer identity and claim fields are embedded in transactional document, not consolidated identity repository.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0013" source="R156_E0008" target="APP_EVIEW"><data key="edge_relationship_id">R156_R0013</data><data key="edge_source_entity_id">R156_E0008</data><data key="edge_relationship_type">accessible_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">All disability components may view uploaded request in certified electronic folder.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0014" source="APP_QRCPS" target="R156_E0010"><data key="edge_relationship_id">R156_R0014</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R156_E0010</data><data key="edge_operational_context">FO Assistance Request function enables work activity development.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0015" source="APP_QRCPS" target="R156_E0011"><data key="edge_relationship_id">R156_R0015</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">propagates_fields_into</data><data key="edge_target_entity_id">R156_E0011</data><data key="edge_operational_context">SSA-1774-U5 request auto-populates header/sections from quality case data; onset narrative entered manually.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0016" source="R156_E0011" target="FORM_SSA1774"><data key="edge_relationship_id">R156_R0016</data><data key="edge_source_entity_id">R156_E0011</data><data key="edge_relationship_type">included_in</data><data key="edge_target_entity_id">FORM_SSA1774</data><data key="edge_operational_context">Auto-populated SSA-1774 header includes deficiency classification; human enters allegation/onset information.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0017" source="R156_E0012" target="FORM_SSA1774"><data key="edge_relationship_id">R156_R0017</data><data key="edge_source_entity_id">R156_E0012</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA1774</data><data key="edge_operational_context">DQR group I and II review deficiency returns via corrective-action request.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0018" source="APP_QRCPS" target="R156_E0012"><data key="edge_relationship_id">R156_R0018</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">R156_E0012</data><data key="edge_operational_context">Quality review controlled returns and re-reviews corrected case record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0019" source="APP_QRCPS" target="R156_E0013"><data key="edge_relationship_id">R156_R0019</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0013</data><data key="edge_operational_context">Final probability-of-reversal disposition belongs to reviewer, not medical contractor.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0020" source="APP_QRCPS" target="R156_E0014"><data key="edge_relationship_id">R156_R0020</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">R156_E0014</data><data key="edge_operational_context">Substitution-of-judgment rationale recorded as quality case note.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0021" source="APP_QRCPS" target="R156_E0015"><data key="edge_relationship_id">R156_R0021</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R156_E0015</data><data key="edge_operational_context">Reviewer may assume adjudicative jurisdiction and amend determination.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0022" source="R156_E0015" target="R156_E0016"><data key="edge_relationship_id">R156_R0022</data><data key="edge_source_entity_id">R156_E0015</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R156_E0016</data><data key="edge_operational_context">Original determination retained in eFolder and annotated Do Not Process.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0023" source="R156_E0015" target="R156_E0017"><data key="edge_relationship_id">R156_R0023</data><data key="edge_source_entity_id">R156_E0015</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R156_E0017</data><data key="edge_operational_context">Superseded notice annotated Do Not Release.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0024" source="R156_E0016" target="APP_EVIEW"><data key="edge_relationship_id">R156_R0024</data><data key="edge_source_entity_id">R156_E0016</data><data key="edge_relationship_type">accessible_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Certified electronic folder retains original determination for audit trail.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0025" source="R156_E0017" target="APP_EVIEW"><data key="edge_relationship_id">R156_R0025</data><data key="edge_source_entity_id">R156_E0017</data><data key="edge_relationship_type">accessible_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Certified folder retains original unapproved notice with release restriction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0026" source="APP_EVIEW" target="R156_E0018"><data key="edge_relationship_id">R156_R0026</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">R156_E0018</data><data key="edge_operational_context">eView Alerts and Messages shows Update After Transfer; Case Data shows ROC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0027" source="PROC_DQR_QUALITY_REVIEW" target="R156_E0019"><data key="edge_relationship_id">R156_R0027</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R156_E0019</data><data key="edge_operational_context">Post-clearance material may change corrective action without revising adjudicating-component attribution at earlier clearance.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0028" source="PROC_DQR_QUALITY_REVIEW" target="R156_E0020"><data key="edge_relationship_id">R156_R0028</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">enforces</data><data key="edge_target_entity_id">R156_E0020</data><data key="edge_operational_context">Query-use restrictions govern work-history evidence, preventing independent query acquisition absent qualifying conditions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0029" source="R156_E0020" target="QRY_SEQY"><data key="edge_relationship_id">R156_R0029</data><data key="edge_source_entity_id">R156_E0020</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">QRY_SEQY</data><data key="edge_operational_context">DQR may rely on SEQY only within reference/presence conditions and exceptions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0030" source="R156_E0020" target="QRY_DEQY"><data key="edge_relationship_id">R156_R0030</data><data key="edge_source_entity_id">R156_E0020</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">DQR may rely on DEQY only within reference/presence conditions and exceptions.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0031" source="APP_QRCPS" target="R156_E0022"><data key="edge_relationship_id">R156_R0031</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0022</data><data key="edge_operational_context">Grace period field on QA Initial Allowance tab for applicable group I.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0032" source="R156_E0021" target="R156_E0022"><data key="edge_relationship_id">R156_R0032</data><data key="edge_source_entity_id">R156_E0021</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R156_E0022</data><data key="edge_operational_context">Qualifying group I deficiency coded informational only in first two full calendar months after new policy.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0033" source="APP_QRCPS" target="R156_E0023"><data key="edge_relationship_id">R156_R0033</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R156_E0023</data><data key="edge_operational_context">Weekly deficiency report captures only regulation-basis-code TCA subset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0034" source="PROC_DQR_QUALITY_REVIEW" target="R156_E0024"><data key="edge_relationship_id">R156_R0034</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">has_reporting_limit</data><data key="edge_target_entity_id">R156_E0024</data><data key="edge_operational_context">Concurrent split sample reviewed for both claims but quality-review sample metadata counted only for sampled claim.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0035" source="R156_E0025" target="R156_E0006"><data key="edge_relationship_id">R156_R0035</data><data key="edge_source_entity_id">R156_E0025</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R156_E0006</data><data key="edge_operational_context">Group II category 73/81/82/83 controlled return requires 60-day follow-up if unresolved.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0036" source="APP_RECOOP" target="R156_E0026"><data key="edge_relationship_id">R156_R0036</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">identifies_cases_by</data><data key="edge_target_entity_id">R156_E0026</data><data key="edge_operational_context">ARC code identifies cases controlled by RECOOP including installment and suspension categories.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0037" source="APP_RECOOP" target="R156_E0027"><data key="edge_relationship_id">R156_R0037</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R156_E0027</data><data key="edge_operational_context">Monthly bill issued 20 days before payment due date.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0038" source="APP_RECOOP" target="R156_E0028"><data key="edge_relationship_id">R156_R0038</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R156_E0028</data><data key="edge_operational_context">Alerts go to Debtor Contact Section; source says not to field offices.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0039" source="APP_MSSICS" target="R156_E0029"><data key="edge_relationship_id">R156_R0039</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R156_E0029</data><data key="edge_operational_context">Existing terminated SSI record debt brought forward when new eligibility reestablished.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0040" source="APP_MSSICS" target="R156_E0030"><data key="edge_relationship_id">R156_R0040</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">R156_E0030</data><data key="edge_operational_context">UOMN menu has RECONCILIATION selection for terminated-SSR overpayment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0041" source="APP_MSSICS" target="R156_E0031"><data key="edge_relationship_id">R156_R0041</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">R156_E0031</data><data key="edge_operational_context">UOMA records manually computed overpayment brought forward.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0042" source="R156_E0029" target="R156_E0030"><data key="edge_relationship_id">R156_R0042</data><data key="edge_source_entity_id">R156_E0029</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R156_E0030</data><data key="edge_operational_context">Employee selects UOMN RECONCILIATION.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0043" source="R156_E0029" target="R156_E0031"><data key="edge_relationship_id">R156_R0043</data><data key="edge_source_entity_id">R156_E0029</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R156_E0031</data><data key="edge_operational_context">Manually transfer debt onto reestablished SSI record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0044" source="R156_E0029" target="R156_E0032"><data key="edge_relationship_id">R156_R0044</data><data key="edge_source_entity_id">R156_E0029</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R156_E0032</data><data key="edge_operational_context">Q TAC closes old record overpayment after transfer.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0045" source="R156_E0029" target="R156_E0033"><data key="edge_relationship_id">R156_R0045</data><data key="edge_source_entity_id">R156_E0029</data><data key="edge_relationship_type">conditioned_by</data><data key="edge_target_entity_id">R156_E0033</data><data key="edge_operational_context">B1 overdue installment flag affects transfer timing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0046" source="APP_MSSICS" target="R156_E0037"><data key="edge_relationship_id">R156_R0046</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">R156_E0037</data><data key="edge_operational_context">UOPD RECOVER BY INSTALLMENTS generates G TAC.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0047" source="SYS_SSR" target="R156_E0037"><data key="edge_relationship_id">R156_R0047</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0037</data><data key="edge_operational_context">G TAC housed in SSR OPDD overpayment decision segment.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0048" source="SYS_SSR" target="R156_E0032"><data key="edge_relationship_id">R156_R0048</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0032</data><data key="edge_operational_context">Q TAC bring-forward records debt close-out on prior record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0049" source="SYS_SSR" target="R156_E0033"><data key="edge_relationship_id">R156_R0049</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0033</data><data key="edge_operational_context">B1 overpayment overdue installment diary.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0050" source="APP_RECOOP" target="R156_E0034"><data key="edge_relationship_id">R156_R0050</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">selects_debts_for</data><data key="edge_target_entity_id">R156_E0034</data><data key="edge_operational_context">Automated CPR selects qualifying RECOOP-controlled SSI debts; manual K TAC required for unselected qualifying debts.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0051" source="APP_MSSICS" target="R156_E0034"><data key="edge_relationship_id">R156_R0051</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">R156_E0034</data><data key="edge_operational_context">Employee adds manual K TAC to SSI SSR through UOPD for CPR.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0052" source="SYS_SSR" target="R156_E0034"><data key="edge_relationship_id">R156_R0052</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0034</data><data key="edge_operational_context">Cross-program recovery authorizing TAC on SSI record.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0053" source="SYS_SSR" target="R156_E0035"><data key="edge_relationship_id">R156_R0053</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R156_E0035</data><data key="edge_operational_context">B8 diary generated when SSI resumes current pay and automatic CPR cannot continue.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0054" source="R156_E0036" target="SYS_SSR"><data key="edge_relationship_id">R156_R0054</data><data key="edge_source_entity_id">R156_E0036</data><data key="edge_relationship_type">reconciles</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">450S batch may reconcile terminated and reestablished SSI debts in documented exception situations.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0055" source="APP_ROAR" target="R156_E0034"><data key="edge_relationship_id">R156_R0055</data><data key="edge_source_entity_id">APP_ROAR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R156_E0034</data><data key="edge_operational_context">Official reduction notice flows in ROAR after manual K TAC transaction.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0056" source="APP_RECOOP" target="R156_E0038"><data key="edge_relationship_id">R156_R0056</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R156_E0038</data><data key="edge_operational_context">Residence of debtor in foreign country or Puerto Rico/USVI changes debt-control routing.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0057" source="UI_SSI_FI_ACCOUNT" target="R156_E0039"><data key="edge_relationship_id">R156_R0057</data><data key="edge_source_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_relationship_type">captures</data><data key="edge_target_entity_id">R156_E0039</data><data key="edge_operational_context">FI name and FI business address documented on financial-account metadata; does not identify beneficiary residence.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0058" source="APP_EAFI" target="R156_E0039"><data key="edge_relationship_id">R156_R0058</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">verifies_accounts_referenced_by</data><data key="edge_target_entity_id">R156_E0039</data><data key="edge_operational_context">AFI account verification contacts named financial institution; no address master update inferred.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0059" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="R156_E0040"><data key="edge_relationship_id">R156_R0059</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">develops</data><data key="edge_target_entity_id">R156_E0040</data><data key="edge_operational_context">Informational IRS alert used as development lead, not verified asset.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0060" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="R156_E0041"><data key="edge_relationship_id">R156_R0060</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">develops</data><data key="edge_target_entity_id">R156_E0041</data><data key="edge_operational_context">Controlled IRS alert subject to mandatory development procedures.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R156_R0061" source="APP_SSI_CLAIMS_LOGICAL" target="R156_E0041"><data key="edge_relationship_id">R156_R0061</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R156_E0041</data><data key="edge_operational_context">Controlled IRS source alert informs SSI RZ verification; information is not master-address update.</data><data key="edge_observed_as_of">2026-10-09</data><data key="edge_confidence">5</data><data key="edge_notes">SSA documented policy relationship; implementation technology not independently verified.</data></edge><edge id="R157_REL_0001" source="R157_DATA_BK_COURT_NOTICE" target="ORG_SSA_OGC"><data key="edge_relationship_id">R157_REL_0001</data><data key="edge_source_entity_id">R157_DATA_BK_COURT_NOTICE</data><data key="edge_relationship_type">routed_to</data><data key="edge_target_entity_id">ORG_SSA_OGC</data><data key="edge_operational_context">Court bankruptcy notices primarily to OGC electronic process; other contact forwarded to OGC.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0002" source="ORG_SSA_OGC" target="R157_PROC_BK_STAY"><data key="edge_relationship_id">R157_REL_0002</data><data key="edge_source_entity_id">ORG_SSA_OGC</data><data key="edge_relationship_type">directs_collection_stay</data><data key="edge_target_entity_id">R157_PROC_BK_STAY</data><data key="edge_operational_context">OGC notice triggers stay of prepetition debt collection.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0003" source="R157_PROC_BK_STAY" target="R157_DATA_BK_PREPETITION"><data key="edge_relationship_id">R157_REL_0003</data><data key="edge_source_entity_id">R157_PROC_BK_STAY</data><data key="edge_relationship_type">classifies_using</data><data key="edge_target_entity_id">R157_DATA_BK_PREPETITION</data><data key="edge_operational_context">Underlying benefit month compared to petition date.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0004" source="R157_PROC_BK_STAY" target="R157_CTRL_BK_MBR_MESSAGE"><data key="edge_relationship_id">R157_REL_0004</data><data key="edge_source_entity_id">R157_PROC_BK_STAY</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R157_CTRL_BK_MBR_MESSAGE</data><data key="edge_operational_context">Title II special MBR message required.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0005" source="R157_CTRL_BK_MBR_MESSAGE" target="SYS_MBR"><data key="edge_relationship_id">R157_REL_0005</data><data key="edge_source_entity_id">R157_CTRL_BK_MBR_MESSAGE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR special message by BIC.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0006" source="R157_CTRL_BK_WAIVER_HOLD" target="R157_PROC_BK_STAY"><data key="edge_relationship_id">R157_REL_0006</data><data key="edge_source_entity_id">R157_CTRL_BK_WAIVER_HOLD</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R157_PROC_BK_STAY</data><data key="edge_operational_context">Waiver processing held in pending bankruptcy unless OGC says otherwise.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0007" source="R157_PROC_BK_PREF_REFUND" target="R157_PROC_BK_IPAC"><data key="edge_relationship_id">R157_REL_0007</data><data key="edge_source_entity_id">R157_PROC_BK_PREF_REFUND</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R157_PROC_BK_IPAC</data><data key="edge_operational_context">OGC-directed preference refund paid through IPAC, funded from administrative expenses.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0008" source="R157_PROC_BK_IPAC" target="R157_DATA_BK_IPAC_ID"><data key="edge_relationship_id">R157_REL_0008</data><data key="edge_source_entity_id">R157_PROC_BK_IPAC</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R157_DATA_BK_IPAC_ID</data><data key="edge_operational_context">Office of Finance returns reference identifier.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0009" source="R157_PROC_BK_IPAC" target="R157_DATA_BK_TRUSTEE_MAIL"><data key="edge_relationship_id">R157_REL_0009</data><data key="edge_source_entity_id">R157_PROC_BK_IPAC</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R157_DATA_BK_TRUSTEE_MAIL</data><data key="edge_operational_context">Bankruptcy trustee refund routing address among remittance metadata.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0010" source="R157_PROC_BK_PREF_REFUND" target="R157_DATA_BK_DMS_REMARKS"><data key="edge_relationship_id">R157_REL_0010</data><data key="edge_source_entity_id">R157_PROC_BK_PREF_REFUND</data><data key="edge_relationship_type">documents_in</data><data key="edge_target_entity_id">R157_DATA_BK_DMS_REMARKS</data><data key="edge_operational_context">Refund/debt restoration documented in DMS remarks.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0011" source="R157_DATA_BK_DMS_REMARKS" target="APP_DMS"><data key="edge_relationship_id">R157_REL_0011</data><data key="edge_source_entity_id">R157_DATA_BK_DMS_REMARKS</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">DMS remarks screen audit trail.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0012" source="R157_PROC_BK_STAY" target="R157_RULE_BK_JOINT"><data key="edge_relationship_id">R157_REL_0012</data><data key="edge_source_entity_id">R157_PROC_BK_STAY</data><data key="edge_relationship_type">constrained_by</data><data key="edge_target_entity_id">R157_RULE_BK_JOINT</data><data key="edge_operational_context">Stay applies to filing debtor rather than all jointly liable parties.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0013" source="R157_RULE_BK_JOINT" target="APP_RPS"><data key="edge_relationship_id">R157_REL_0013</data><data key="edge_source_entity_id">R157_RULE_BK_JOINT</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_RPS</data><data key="edge_operational_context">Representative payee status alone does not transfer debtor-specific bankruptcy protection.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0014" source="R157_DATA_BK_COURT_NOTICE" target="R157_CTRL_BK_WAIVER_HOLD"><data key="edge_relationship_id">R157_REL_0014</data><data key="edge_source_entity_id">R157_DATA_BK_COURT_NOTICE</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R157_CTRL_BK_WAIVER_HOLD</data><data key="edge_operational_context">Bankruptcy notice calls for waiver decision hold.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0015" source="R157_DATA_BK_PREPETITION" target="R157_PROC_BK_PREF_REFUND"><data key="edge_relationship_id">R157_REL_0015</data><data key="edge_source_entity_id">R157_DATA_BK_PREPETITION</data><data key="edge_relationship_type">conditions</data><data key="edge_target_entity_id">R157_PROC_BK_PREF_REFUND</data><data key="edge_operational_context">Refund concerns payments for covered prepetition liability.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0016" source="R157_UI_EDCS_CDRI" target="APP_EDCS"><data key="edge_relationship_id">R157_REL_0016</data><data key="edge_source_entity_id">R157_UI_EDCS_CDRI</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">CDR appeal screens in EDCS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0017" source="R157_UI_EDCS_CDRI" target="R157_CTRL_ECDR_DCF_CDRI"><data key="edge_relationship_id">R157_REL_0017</data><data key="edge_source_entity_id">R157_UI_EDCS_CDRI</data><data key="edge_relationship_type">automatically_updates</data><data key="edge_target_entity_id">R157_CTRL_ECDR_DCF_CDRI</data><data key="edge_operational_context">After transfer, DCF CDRI screen records appeal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0018" source="R157_CTRL_ECDR_DCF_CDRI" target="DB_DCF"><data key="edge_relationship_id">R157_REL_0018</data><data key="edge_source_entity_id">R157_CTRL_ECDR_DCF_CDRI</data><data key="edge_relationship_type">posts_to</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Automatic transfer update limited to appeal, not initial CDR movement.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0019" source="R157_CTRL_ECDR_MAINFRAME_PRECHECK" target="R157_UI_EDCS_CDRI"><data key="edge_relationship_id">R157_REL_0019</data><data key="edge_source_entity_id">R157_CTRL_ECDR_MAINFRAME_PRECHECK</data><data key="edge_relationship_type">precedes</data><data key="edge_target_entity_id">R157_UI_EDCS_CDRI</data><data key="edge_operational_context">FO checks and updates mainframe contact/payee data before transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0020" source="R157_CTRL_ECDR_MAINFRAME_PRECHECK" target="SYS_MBR"><data key="edge_relationship_id">R157_REL_0020</data><data key="edge_source_entity_id">R157_CTRL_ECDR_MAINFRAME_PRECHECK</data><data key="edge_relationship_type">verifies</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Relevant Title II mainframe claimant fields checked.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0021" source="R157_CTRL_ECDR_MAINFRAME_PRECHECK" target="SYS_SSR"><data key="edge_relationship_id">R157_REL_0021</data><data key="edge_source_entity_id">R157_CTRL_ECDR_MAINFRAME_PRECHECK</data><data key="edge_relationship_type">verifies</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Applicable SSI claimant details checked; not blanket synchronization.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0022" source="R157_CTRL_ECDR_5D" target="SYS_MBR"><data key="edge_relationship_id">R157_REL_0022</data><data key="edge_source_entity_id">R157_CTRL_ECDR_5D</data><data key="edge_relationship_type">verifies_record_posting</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Five-day follow-up and manual correction if automatic posting absent.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0023" source="R157_CTRL_ECDR_5D" target="SYS_SSR"><data key="edge_relationship_id">R157_REL_0023</data><data key="edge_source_entity_id">R157_CTRL_ECDR_5D</data><data key="edge_relationship_type">verifies_record_posting</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Five-day follow-up for Title XVI and concurrent decisions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0024" source="R157_PROC_ECDR_CPD_PAPER" target="R157_UI_EDCS_CDRI"><data key="edge_relationship_id">R157_REL_0024</data><data key="edge_source_entity_id">R157_PROC_ECDR_CPD_PAPER</data><data key="edge_relationship_type">accompanies</data><data key="edge_target_entity_id">R157_UI_EDCS_CDRI</data><data key="edge_operational_context">Paper CPD accompanies concurrent electronic appeal transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0025" source="R157_PROC_ECDR_CPD_PAPER" target="ORG_DDS"><data key="edge_relationship_id">R157_REL_0025</data><data key="edge_source_entity_id">R157_PROC_ECDR_CPD_PAPER</data><data key="edge_relationship_type">delivered_to</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Paper prior-CPD folders to DDS alongside EDCS transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0026" source="APP_MSSICS" target="R157_UI_EDCS_CDRI"><data key="edge_relationship_id">R157_REL_0026</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">precedes</data><data key="edge_target_entity_id">R157_UI_EDCS_CDRI</data><data key="edge_operational_context">For Title XVI or concurrent, SSR cessation appeal/SBC fields updated before EDCS case.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0027" source="R157_UI_EDCS_CDRI" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0027</data><data key="edge_source_entity_id">R157_UI_EDCS_CDRI</data><data key="edge_relationship_type">files_documents_to</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Appeal forms and SBC evidence filed in CEF.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0028" source="R157_PROC_SSNAP_NAME_CORR" target="SYS_NUMIDENT"><data key="edge_relationship_id">R157_REL_0028</data><data key="edge_source_entity_id">R157_PROC_SSNAP_NAME_CORR</data><data key="edge_relationship_type">updates_identity_display_on</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Conditional card legal-name correction vs documented legal name-change event.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0029" source="R157_PROC_SSNAP_NAME_CORR" target="APP_SSNAP"><data key="edge_relationship_id">R157_REL_0029</data><data key="edge_source_entity_id">R157_PROC_SSNAP_NAME_CORR</data><data key="edge_relationship_type">performed_using</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">POMS directs name fields through SSNAP workflow.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0030" source="R157_PROC_SSNAP_NAME_CORR" target="R157_DATA_NUMIDENT_NL2"><data key="edge_relationship_id">R157_REL_0030</data><data key="edge_source_entity_id">R157_PROC_SSNAP_NAME_CORR</data><data key="edge_relationship_type">may_use</data><data key="edge_target_entity_id">R157_DATA_NUMIDENT_NL2</data><data key="edge_operational_context">Prior NL2 conditional legal-name evidence for U.S.-born applicant.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0031" source="R157_DATA_NUMIDENT_NL2" target="SYS_NUMIDENT"><data key="edge_relationship_id">R157_REL_0031</data><data key="edge_source_entity_id">R157_DATA_NUMIDENT_NL2</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Historical NL2 entry on prior Numident.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0032" source="R157_PROC_DMV_NAMESSN" target="R157_PROC_SSNAP_NAME_CORR"><data key="edge_relationship_id">R157_REL_0032</data><data key="edge_source_entity_id">R157_PROC_DMV_NAMESSN</data><data key="edge_relationship_type">may_prompt</data><data key="edge_target_entity_id">R157_PROC_SSNAP_NAME_CORR</data><data key="edge_operational_context">Failed DMV electronic name/SSN verification or state card-name requirements may initiate correction; not automatic.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0033" source="R157_PROC_DMV_NAMESSN" target="SYS_NUMIDENT"><data key="edge_relationship_id">R157_REL_0033</data><data key="edge_source_entity_id">R157_PROC_DMV_NAMESSN</data><data key="edge_relationship_type">does_not_assert_address_update_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">No documented DMV address propagation from this instruction.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0034" source="R157_DOC_DMA_0190" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0034</data><data key="edge_source_entity_id">R157_DOC_DMA_0190</data><data key="edge_relationship_type">indexed_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DMA document type 0190 designates CEF section and intended evidence classification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0035" source="R157_DOC_DMA_1080" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0035</data><data key="edge_source_entity_id">R157_DOC_DMA_1080</data><data key="edge_relationship_type">indexed_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DMA document type 1080 designates CEF section and intended evidence classification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0036" source="R157_DOC_DMA_0050" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0036</data><data key="edge_source_entity_id">R157_DOC_DMA_0050</data><data key="edge_relationship_type">indexed_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DMA document type 0050 designates CEF section and intended evidence classification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0037" source="R157_DOC_DMA_3157" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0037</data><data key="edge_source_entity_id">R157_DOC_DMA_3157</data><data key="edge_relationship_type">indexed_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DMA document type 3157 designates CEF section and intended evidence classification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0038" source="R157_DOC_DMA_3158" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0038</data><data key="edge_source_entity_id">R157_DOC_DMA_3158</data><data key="edge_relationship_type">indexed_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DMA document type 3158 designates CEF section and intended evidence classification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0039" source="R157_DOC_DMA_0185" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0039</data><data key="edge_source_entity_id">R157_DOC_DMA_0185</data><data key="edge_relationship_type">indexed_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DMA document type 0185 designates CEF section and intended evidence classification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0040" source="R157_DOC_DMA_0180" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0040</data><data key="edge_source_entity_id">R157_DOC_DMA_0180</data><data key="edge_relationship_type">indexed_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DMA document type 0180 designates CEF section and intended evidence classification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0041" source="R157_DOC_DMA_5032" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0041</data><data key="edge_source_entity_id">R157_DOC_DMA_5032</data><data key="edge_relationship_type">indexed_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DMA document type 5032 designates CEF section and intended evidence classification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0042" source="R157_DOC_DMA_3157" target="REPO_CEF"><data key="edge_relationship_id">R157_REL_0042</data><data key="edge_source_entity_id">R157_DOC_DMA_3157</data><data key="edge_relationship_type">requires_medical_document_content</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">School records with IQ/medical content in Section F; unlike nonmedical 3158.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0043" source="R157_DATA_OSDBU_SUBDIR" target="R157_CON_ITSSC_LOCKHEED"><data key="edge_relationship_id">R157_REL_0043</data><data key="edge_source_entity_id">R157_DATA_OSDBU_SUBDIR</data><data key="edge_relationship_type">historically_lists</data><data key="edge_target_entity_id">R157_CON_ITSSC_LOCKHEED</data><data key="edge_operational_context">Public directory lists historical contract number; no current contract status.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0044" source="R157_CON_ITSSC_LOCKHEED" target="R157_ORG_LOCKHEED"><data key="edge_relationship_id">R157_REL_0044</data><data key="edge_source_entity_id">R157_CON_ITSSC_LOCKHEED</data><data key="edge_relationship_type">historically_lists_prime</data><data key="edge_target_entity_id">R157_ORG_LOCKHEED</data><data key="edge_operational_context">SSA subcontracting directory prime listed for this ITSSC contract number; not specific technology use.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0045" source="R157_ORG_LOCKHEED" target="R157_DATA_OSDBU_SUBDIR"><data key="edge_relationship_id">R157_REL_0045</data><data key="edge_source_entity_id">R157_ORG_LOCKHEED</data><data key="edge_relationship_type">appears_in</data><data key="edge_target_entity_id">R157_DATA_OSDBU_SUBDIR</data><data key="edge_operational_context">Historical prime contractor shown in public directory.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0046" source="R157_DATA_OSDBU_SUBDIR" target="R157_CON_ITSSC_NORTHROP"><data key="edge_relationship_id">R157_REL_0046</data><data key="edge_source_entity_id">R157_DATA_OSDBU_SUBDIR</data><data key="edge_relationship_type">historically_lists</data><data key="edge_target_entity_id">R157_CON_ITSSC_NORTHROP</data><data key="edge_operational_context">Public directory lists historical contract number; no current contract status.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0047" source="R157_CON_ITSSC_NORTHROP" target="R157_ORG_NORTHROP"><data key="edge_relationship_id">R157_REL_0047</data><data key="edge_source_entity_id">R157_CON_ITSSC_NORTHROP</data><data key="edge_relationship_type">historically_lists_prime</data><data key="edge_target_entity_id">R157_ORG_NORTHROP</data><data key="edge_operational_context">SSA subcontracting directory prime listed for this ITSSC contract number; not specific technology use.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0048" source="R157_ORG_NORTHROP" target="R157_DATA_OSDBU_SUBDIR"><data key="edge_relationship_id">R157_REL_0048</data><data key="edge_source_entity_id">R157_ORG_NORTHROP</data><data key="edge_relationship_type">appears_in</data><data key="edge_target_entity_id">R157_DATA_OSDBU_SUBDIR</data><data key="edge_operational_context">Historical prime contractor shown in public directory.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0049" source="R157_DATA_OSDBU_SUBDIR" target="R157_CON_ITSSC_CGI"><data key="edge_relationship_id">R157_REL_0049</data><data key="edge_source_entity_id">R157_DATA_OSDBU_SUBDIR</data><data key="edge_relationship_type">historically_lists</data><data key="edge_target_entity_id">R157_CON_ITSSC_CGI</data><data key="edge_operational_context">Public directory lists historical contract number; no current contract status.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0050" source="R157_CON_ITSSC_CGI" target="R157_ORG_CGI"><data key="edge_relationship_id">R157_REL_0050</data><data key="edge_source_entity_id">R157_CON_ITSSC_CGI</data><data key="edge_relationship_type">historically_lists_prime</data><data key="edge_target_entity_id">R157_ORG_CGI</data><data key="edge_operational_context">SSA subcontracting directory prime listed for this ITSSC contract number; not specific technology use.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0051" source="R157_ORG_CGI" target="R157_DATA_OSDBU_SUBDIR"><data key="edge_relationship_id">R157_REL_0051</data><data key="edge_source_entity_id">R157_ORG_CGI</data><data key="edge_relationship_type">appears_in</data><data key="edge_target_entity_id">R157_DATA_OSDBU_SUBDIR</data><data key="edge_operational_context">Historical prime contractor shown in public directory.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0052" source="R157_SVC_SSI_SIMPLIFIED_2025" target="R157_RULE_SSI_COHORT_2025"><data key="edge_relationship_id">R157_REL_0052</data><data key="edge_source_entity_id">R157_SVC_SSI_SIMPLIFIED_2025</data><data key="edge_relationship_type">has_eligibility_boundary</data><data key="edge_target_entity_id">R157_RULE_SSI_COHORT_2025</data><data key="edge_operational_context">Documented access cohort as of June 2025.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R157_REL_0053" source="R157_CTRL_PIE_3MO_NOTICE" target="EX_PIE"><data key="edge_relationship_id">R157_REL_0053</data><data key="edge_source_entity_id">R157_CTRL_PIE_3MO_NOTICE</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">Three-month nonreceipt rule for reduced-reporting restoration.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0054" source="R157_CTRL_PIE_AUTH_APPEAL" target="DB_WEI_REPO"><data key="edge_relationship_id">R157_REL_0054</data><data key="edge_source_entity_id">R157_CTRL_PIE_AUTH_APPEAL</data><data key="edge_relationship_type">conditions</data><data key="edge_target_entity_id">DB_WEI_REPO</data><data key="edge_operational_context">Authorized prior-month wages accumulate only while effective authorization exists.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0055" source="R157_CTRL_PIE_AUTH_APPEAL" target="DATA_SSA8240"><data key="edge_relationship_id">R157_REL_0055</data><data key="edge_source_entity_id">R157_CTRL_PIE_AUTH_APPEAL</data><data key="edge_relationship_type">affects</data><data key="edge_target_entity_id">DATA_SSA8240</data><data key="edge_operational_context">Renewed SSA-8240 / WEIA can be needed after late appeal expiry.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0056" source="R157_CTRL_PIE_FORCE_DUE" target="SYS_SSR"><data key="edge_relationship_id">R157_REL_0056</data><data key="edge_source_entity_id">R157_CTRL_PIE_FORCE_DUE</data><data key="edge_relationship_type">blocks_auto_post_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Certain SSI cases require employee development rather than automatic post.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0057" source="R157_CTRL_PIE_FORCE_DUE" target="WORK_PIE_EE_DIARY"><data key="edge_relationship_id">R157_REL_0057</data><data key="edge_source_entity_id">R157_CTRL_PIE_FORCE_DUE</data><data key="edge_relationship_type">generates_review_in</data><data key="edge_target_entity_id">WORK_PIE_EE_DIARY</data><data key="edge_operational_context">Pending unmatched/force-due wage creates EE diary in relevant cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R157_REL_0058" source="R157_CTRL_PIE_3MO_NOTICE" target="WORK_PIE_EE_DIARY"><data key="edge_relationship_id">R157_REL_0058</data><data key="edge_source_entity_id">R157_CTRL_PIE_3MO_NOTICE</data><data key="edge_relationship_type">does_not_replace</data><data key="edge_target_entity_id">WORK_PIE_EE_DIARY</data><data key="edge_operational_context">Notice rules and EE exception-work control are separate.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R158_R0001" source="R158_E0001" target="ORG_DDS"><data key="edge_relationship_id">R158_R0001</data><data key="edge_source_entity_id">R158_E0001</data><data key="edge_relationship_type">budgets_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0002" source="R158_E0002" target="ORG_DDS"><data key="edge_relationship_id">R158_R0002</data><data key="edge_source_entity_id">R158_E0002</data><data key="edge_relationship_type">reports_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0003" source="R158_E0003" target="ORG_DDS"><data key="edge_relationship_id">R158_R0003</data><data key="edge_source_entity_id">R158_E0003</data><data key="edge_relationship_type">classifies_cost_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0004" source="R158_E0004" target="ORG_DDS"><data key="edge_relationship_id">R158_R0004</data><data key="edge_source_entity_id">R158_E0004</data><data key="edge_relationship_type">classifies_cost_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0005" source="R158_E0005" target="ORG_DDS"><data key="edge_relationship_id">R158_R0005</data><data key="edge_source_entity_id">R158_E0005</data><data key="edge_relationship_type">classifies_cost_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0006" source="R158_E0006" target="ORG_DDS"><data key="edge_relationship_id">R158_R0006</data><data key="edge_source_entity_id">R158_E0006</data><data key="edge_relationship_type">classifies_cost_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0007" source="R158_E0007" target="ORG_DDS"><data key="edge_relationship_id">R158_R0007</data><data key="edge_source_entity_id">R158_E0007</data><data key="edge_relationship_type">requires_review_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0008" source="R158_E0008" target="ORG_DDS"><data key="edge_relationship_id">R158_R0008</data><data key="edge_source_entity_id">R158_E0008</data><data key="edge_relationship_type">governs_budget_timing_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0009" source="R158_E0009" target="ORG_DDS"><data key="edge_relationship_id">R158_R0009</data><data key="edge_source_entity_id">R158_E0009</data><data key="edge_relationship_type">requires_security_approval_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0010" source="R158_E0010" target="ORG_DDS"><data key="edge_relationship_id">R158_R0010</data><data key="edge_source_entity_id">R158_E0010</data><data key="edge_relationship_type">defines_design_control_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0011" source="R158_E0011" target="ORG_DDS"><data key="edge_relationship_id">R158_R0011</data><data key="edge_source_entity_id">R158_E0011</data><data key="edge_relationship_type">requires_backup_policy_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0012" source="R158_E0012" target="ORG_DDS"><data key="edge_relationship_id">R158_R0012</data><data key="edge_source_entity_id">R158_E0012</data><data key="edge_relationship_type">governs_access_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0013" source="R158_E0013" target="ORG_DDS"><data key="edge_relationship_id">R158_R0013</data><data key="edge_source_entity_id">R158_E0013</data><data key="edge_relationship_type">defines_abuse_security_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0014" source="R158_E0019" target="ORG_DDS"><data key="edge_relationship_id">R158_R0014</data><data key="edge_source_entity_id">R158_E0019</data><data key="edge_relationship_type">receives_complaint_in</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0015" source="R158_E0020" target="ORG_DDS"><data key="edge_relationship_id">R158_R0015</data><data key="edge_source_entity_id">R158_E0020</data><data key="edge_relationship_type">investigates_complaints_in</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0016" source="R158_E0021" target="ORG_DDS"><data key="edge_relationship_id">R158_R0016</data><data key="edge_source_entity_id">R158_E0021</data><data key="edge_relationship_type">classifies_allegations_in</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Policy-based DDS budget/security/complaint-control relationship.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0017" source="R158_E0001" target="R158_E0002"><data key="edge_relationship_id">R158_R0017</data><data key="edge_source_entity_id">R158_E0001</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R158_E0002</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0018" source="R158_E0001" target="R158_E0003"><data key="edge_relationship_id">R158_R0018</data><data key="edge_source_entity_id">R158_E0001</data><data key="edge_relationship_type">categorizes</data><data key="edge_target_entity_id">R158_E0003</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0019" source="R158_E0001" target="R158_E0004"><data key="edge_relationship_id">R158_R0019</data><data key="edge_source_entity_id">R158_E0001</data><data key="edge_relationship_type">categorizes</data><data key="edge_target_entity_id">R158_E0004</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0020" source="R158_E0001" target="R158_E0005"><data key="edge_relationship_id">R158_R0020</data><data key="edge_source_entity_id">R158_E0001</data><data key="edge_relationship_type">categorizes</data><data key="edge_target_entity_id">R158_E0005</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0021" source="R158_E0001" target="R158_E0006"><data key="edge_relationship_id">R158_R0021</data><data key="edge_source_entity_id">R158_E0001</data><data key="edge_relationship_type">categorizes</data><data key="edge_target_entity_id">R158_E0006</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0022" source="R158_E0007" target="R158_E0005"><data key="edge_relationship_id">R158_R0022</data><data key="edge_source_entity_id">R158_E0007</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">R158_E0005</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0023" source="R158_E0008" target="R158_E0001"><data key="edge_relationship_id">R158_R0023</data><data key="edge_source_entity_id">R158_E0008</data><data key="edge_relationship_type">supports_planning_in</data><data key="edge_target_entity_id">R158_E0001</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0024" source="R158_E0009" target="R158_E0010"><data key="edge_relationship_id">R158_R0024</data><data key="edge_source_entity_id">R158_E0009</data><data key="edge_relationship_type">reviews</data><data key="edge_target_entity_id">R158_E0010</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0025" source="R158_E0010" target="R158_E0011"><data key="edge_relationship_id">R158_R0025</data><data key="edge_source_entity_id">R158_E0010</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R158_E0011</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0026" source="R158_E0010" target="R158_E0012"><data key="edge_relationship_id">R158_R0026</data><data key="edge_source_entity_id">R158_E0010</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R158_E0012</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0027" source="R158_E0020" target="R158_E0019"><data key="edge_relationship_id">R158_R0027</data><data key="edge_source_entity_id">R158_E0020</data><data key="edge_relationship_type">processes_input_from</data><data key="edge_target_entity_id">R158_E0019</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0028" source="R158_E0020" target="R158_E0021"><data key="edge_relationship_id">R158_R0028</data><data key="edge_source_entity_id">R158_E0020</data><data key="edge_relationship_type">classifies</data><data key="edge_target_entity_id">R158_E0021</data><data key="edge_operational_context">Documented relationship among related policy controls; no claim of physical data transfer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0029" source="R158_E0014" target="DATA_SSI_AR_IVC1_FED_PAYMENTS"><data key="edge_relationship_id">R158_R0029</data><data key="edge_source_entity_id">R158_E0014</data><data key="edge_relationship_type">is_measurement_method_for</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC1_FED_PAYMENTS</data><data key="edge_operational_context">OACT 2026 SSI IV.C method; publication lineage, not physical application or SQL extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0030" source="R158_E0015" target="DATA_SSI_AR_IVC1_FED_PAYMENTS"><data key="edge_relationship_id">R158_R0030</data><data key="edge_source_entity_id">R158_E0015</data><data key="edge_relationship_type">is_a_comparative_reporting_basis_for</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC1_FED_PAYMENTS</data><data key="edge_operational_context">OACT 2026 SSI IV.C method; publication lineage, not physical application or SQL extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0031" source="R158_E0016" target="DATA_SSI_AR_IVC1_FED_PAYMENTS"><data key="edge_relationship_id">R158_R0031</data><data key="edge_source_entity_id">R158_E0016</data><data key="edge_relationship_type">reconciles_federal_budget_treatment_for</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC1_FED_PAYMENTS</data><data key="edge_operational_context">OACT 2026 SSI IV.C method; publication lineage, not physical application or SQL extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0032" source="R158_E0017" target="DATA_SSI_AR_IVC2_FY_FED_PAY"><data key="edge_relationship_id">R158_R0032</data><data key="edge_source_entity_id">R158_E0017</data><data key="edge_relationship_type">explains_fiscal_year_effects_in</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC2_FY_FED_PAY</data><data key="edge_operational_context">OACT 2026 SSI IV.C method; publication lineage, not physical application or SQL extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0033" source="R158_E0018" target="DATA_SSI_AR_IVC1_FED_PAYMENTS"><data key="edge_relationship_id">R158_R0033</data><data key="edge_source_entity_id">R158_E0018</data><data key="edge_relationship_type">underlies_projection_in</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC1_FED_PAYMENTS</data><data key="edge_operational_context">OACT 2026 SSI IV.C method; publication lineage, not physical application or SQL extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0034" source="R158_E0014" target="REPORT_SSI_ANNUAL_2026"><data key="edge_relationship_id">R158_R0034</data><data key="edge_source_entity_id">R158_E0014</data><data key="edge_relationship_type">documented_by</data><data key="edge_target_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_operational_context">OACT 2026 SSI IV.C method; publication lineage, not physical application or SQL extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0035" source="R158_E0016" target="REPORT_SSI_ANNUAL_2026"><data key="edge_relationship_id">R158_R0035</data><data key="edge_source_entity_id">R158_E0016</data><data key="edge_relationship_type">documented_by</data><data key="edge_target_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_operational_context">OACT 2026 SSI IV.C method; publication lineage, not physical application or SQL extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0036" source="R158_E0018" target="REPORT_SSI_ANNUAL_2026"><data key="edge_relationship_id">R158_R0036</data><data key="edge_source_entity_id">R158_E0018</data><data key="edge_relationship_type">documented_by</data><data key="edge_target_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_operational_context">OACT 2026 SSI IV.C method; publication lineage, not physical application or SQL extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0037" source="R158_E0014" target="R158_E0015"><data key="edge_relationship_id">R158_R0037</data><data key="edge_source_entity_id">R158_E0014</data><data key="edge_relationship_type">contrasts_reporting_basis_with</data><data key="edge_target_entity_id">R158_E0015</data><data key="edge_operational_context">Separate actual-payment reporting basis and Statistical Supplement due-month reporting with recovery treatment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0038" source="R158_E0014" target="R158_E0017"><data key="edge_relationship_id">R158_R0038</data><data key="edge_source_entity_id">R158_E0014</data><data key="edge_relationship_type">is_affected_by</data><data key="edge_target_entity_id">R158_E0017</data><data key="edge_operational_context">Separate actual-payment reporting basis and Statistical Supplement due-month reporting with recovery treatment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0039" source="R158_E0016" target="R158_E0015"><data key="edge_relationship_id">R158_R0039</data><data key="edge_source_entity_id">R158_E0016</data><data key="edge_relationship_type">requires_reconciliation_between</data><data key="edge_target_entity_id">R158_E0015</data><data key="edge_operational_context">Separate actual-payment reporting basis and Statistical Supplement due-month reporting with recovery treatment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0040" source="R158_E0020" target="PROC_DDS_CE_OVERSIGHT"><data key="edge_relationship_id">R158_R0040</data><data key="edge_source_entity_id">R158_E0020</data><data key="edge_relationship_type">is_part_of</data><data key="edge_target_entity_id">PROC_DDS_CE_OVERSIGHT</data><data key="edge_operational_context">Complaints investigated by DDS as part of CE provider oversight.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0041" source="R158_E0021" target="DATA_CE_PROVIDER_OVERSIGHT"><data key="edge_relationship_id">R158_R0041</data><data key="edge_source_entity_id">R158_E0021</data><data key="edge_relationship_type">categorized_within</data><data key="edge_target_entity_id">DATA_CE_PROVIDER_OVERSIGHT</data><data key="edge_operational_context">Potential source for provider oversight, without inferring actual database posting.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0042" source="R158_E0022" target="APP_EDCS"><data key="edge_relationship_id">R158_R0042</data><data key="edge_source_entity_id">R158_E0022</data><data key="edge_relationship_type">transfer_event_triggers_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS transfer triggers new mainframe data propagation to EDCS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0043" source="R158_E0022" target="PROC_EDCS_MAINFRAME_PROPAGATION"><data key="edge_relationship_id">R158_R0043</data><data key="edge_source_entity_id">R158_E0022</data><data key="edge_relationship_type">specializes</data><data key="edge_target_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_operational_context">Transfer-time repropagation of data from MCS, MSSICS and RPS as available.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0044" source="R158_E0023" target="APP_MCS"><data key="edge_relationship_id">R158_R0044</data><data key="edge_source_entity_id">R158_E0023</data><data key="edge_relationship_type">alerts_when_cannot_access</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">On transfer, EDCS alerts CR if system inaccessible; alternative to cancel or proceed.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0045" source="R158_E0023" target="APP_MSSICS"><data key="edge_relationship_id">R158_R0045</data><data key="edge_source_entity_id">R158_E0023</data><data key="edge_relationship_type">alerts_when_cannot_access</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">On transfer, EDCS alerts CR if system inaccessible; alternative to cancel or proceed.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0046" source="R158_E0023" target="APP_EDCS"><data key="edge_relationship_id">R158_R0046</data><data key="edge_source_entity_id">R158_E0023</data><data key="edge_relationship_type">is_control_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS case transfer policy; route and HIT preconditions, not all cases necessarily trigger HIT.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0047" source="R158_E0024" target="APP_EDCS"><data key="edge_relationship_id">R158_R0047</data><data key="edge_source_entity_id">R158_E0024</data><data key="edge_relationship_type">blocks_receipt_processing_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS case transfer policy; route and HIT preconditions, not all cases necessarily trigger HIT.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0048" source="R158_E0025" target="APP_EDCS"><data key="edge_relationship_id">R158_R0048</data><data key="edge_source_entity_id">R158_E0025</data><data key="edge_relationship_type">is_routing_rule_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS case transfer policy; route and HIT preconditions, not all cases necessarily trigger HIT.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0049" source="R158_E0026" target="APP_MEGAHIT"><data key="edge_relationship_id">R158_R0049</data><data key="edge_source_entity_id">R158_E0026</data><data key="edge_relationship_type">requires_authorization_for</data><data key="edge_target_entity_id">APP_MEGAHIT</data><data key="edge_operational_context">EDCS case transfer policy; route and HIT preconditions, not all cases necessarily trigger HIT.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0050" source="R158_E0026" target="DATA_HIT_REQUEST"><data key="edge_relationship_id">R158_R0050</data><data key="edge_source_entity_id">R158_E0026</data><data key="edge_relationship_type">precondition_for</data><data key="edge_target_entity_id">DATA_HIT_REQUEST</data><data key="edge_operational_context">EDCS case transfer policy; route and HIT preconditions, not all cases necessarily trigger HIT.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0051" source="R158_E0024" target="R158_E0022"><data key="edge_relationship_id">R158_R0051</data><data key="edge_source_entity_id">R158_E0024</data><data key="edge_relationship_type">prerequisite_for</data><data key="edge_target_entity_id">R158_E0022</data><data key="edge_operational_context">Jurisdiction transfer must occur for case electronic processing at DDS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0052" source="R158_E0025" target="R158_E0024"><data key="edge_relationship_id">R158_R0052</data><data key="edge_source_entity_id">R158_E0025</data><data key="edge_relationship_type">requires_transfer_rule_from</data><data key="edge_target_entity_id">R158_E0024</data><data key="edge_operational_context">Physical paper material route varies if CEF exclusion or prior paper folder.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0053" source="R158_E0027" target="R128_E043"><data key="edge_relationship_id">R158_R0053</data><data key="edge_source_entity_id">R158_E0027</data><data key="edge_relationship_type">is_provenance_caution_for</data><data key="edge_target_entity_id">R128_E043</data><data key="edge_operational_context">IRS and MEF alert fields can identify payer record payee, not automatically an SSI recipient address; independent verification must be classified separately.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0054" source="R158_E0027" target="DOM_PERSON_CUSTOMER_RECORD"><data key="edge_relationship_id">R158_R0054</data><data key="edge_source_entity_id">R158_E0027</data><data key="edge_relationship_type">warns_against_person_identity_inference_for</data><data key="edge_target_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="edge_operational_context">IRS and MEF alert fields can identify payer record payee, not automatically an SSI recipient address; independent verification must be classified separately.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0055" source="R158_E0028" target="R128_E043"><data key="edge_relationship_id">R158_R0055</data><data key="edge_source_entity_id">R158_E0028</data><data key="edge_relationship_type">qualifies_verification_of</data><data key="edge_target_entity_id">R128_E043</data><data key="edge_operational_context">IRS and MEF alert fields can identify payer record payee, not automatically an SSI recipient address; independent verification must be classified separately.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R158_R0056" source="R158_E0028" target="R158_E0027"><data key="edge_relationship_id">R158_R0056</data><data key="edge_source_entity_id">R158_E0028</data><data key="edge_relationship_type">can_follow_independent_verification_of</data><data key="edge_target_entity_id">R158_E0027</data><data key="edge_operational_context">POMS distinguishes tax data and prior/independently verified SSA data; no automatic master update.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Directional policy, data production, or business-process relationship only; no transport/physical persistence or live deployment inferred.</data></edge><edge id="R159_R001" source="R159_E001" target="APP_RASR"><data key="edge_relationship_id">R159_R001</data><data key="edge_source_entity_id">R159_E001</data><data key="edge_relationship_type">limits_authority_from</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">SSA appointment permits representation but does not authorize claimant mailing-address or direct-deposit edits.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R002" source="R159_E001" target="DOM_PERSON_CUSTOMER_RECORD"><data key="edge_relationship_id">R159_R002</data><data key="edge_source_entity_id">R159_E001</data><data key="edge_relationship_type">protects_person_attributes_of</data><data key="edge_target_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="edge_operational_context">Representative permissions are not permission to alter logical person records or beneficiary attributes.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R003" source="R159_E002" target="APP_RASR"><data key="edge_relationship_id">R159_R003</data><data key="edge_source_entity_id">R159_E002</data><data key="edge_relationship_type">constrains_delegation_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Designated associates handle limited administrative tasks; legally significant actions remain representative duties.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R004" source="R159_E003" target="APP_RASR"><data key="edge_relationship_id">R159_R004</data><data key="edge_source_entity_id">R159_E003</data><data key="edge_relationship_type">checks_active_appointment_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Verify valid appointment in RASR before disclosing records by telephone.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R005" source="R159_E004" target="SYS_NUMIDENT"><data key="edge_relationship_id">R159_R005</data><data key="edge_source_entity_id">R159_E004</data><data key="edge_relationship_type">triggered_by_numident_flag_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SPIN code 6 on Numident triggers in-person-only disclosure to representative or associate.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R006" source="R159_E004" target="R159_E003"><data key="edge_relationship_id">R159_R006</data><data key="edge_source_entity_id">R159_E004</data><data key="edge_relationship_type">overrides_telephone_disclosure_under</data><data key="edge_target_entity_id">R159_E003</data><data key="edge_operational_context">Numident SPIN code 6 bars telephonic representative disclosure despite otherwise valid appointment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R007" source="R159_E005" target="APP_RASR"><data key="edge_relationship_id">R159_R007</data><data key="edge_source_entity_id">R159_E005</data><data key="edge_relationship_type">recorded_temporarily_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Auxiliary fee-only temporary appointment is created and ended in RASR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R008" source="R159_E006" target="APP_RASR"><data key="edge_relationship_id">R159_R008</data><data key="edge_source_entity_id">R159_E006</data><data key="edge_relationship_type">limits_default_related_beneficiary_scope_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Auxiliary claimant may independently appoint or opt out of default primary representative notices.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R009" source="R159_E007" target="APP_RASR"><data key="edge_relationship_id">R159_R009</data><data key="edge_source_entity_id">R159_E007</data><data key="edge_relationship_type">restricts_claim_file_disclosure_from</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Court representation alone permits only limited fee-related information without separate SSA appointment or consent.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R010" source="R159_E008" target="APP_MCS"><data key="edge_relationship_id">R159_R010</data><data key="edge_source_entity_id">R159_E008</data><data key="edge_relationship_type">restricts_external_distribution_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Administrative MBR/other screen query output is not ordinarily furnished to representatives; provide underlying information suitably.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R011" source="R159_E003" target="R159_E004"><data key="edge_relationship_id">R159_R011</data><data key="edge_source_entity_id">R159_E003</data><data key="edge_relationship_type">subject_to_special_protection</data><data key="edge_target_entity_id">R159_E004</data><data key="edge_operational_context">SPIN 6 requires in-person verification instead of phone/mail/fax disclosure.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R012" source="R159_E009" target="APP_MSSICS"><data key="edge_relationship_id">R159_R012</data><data key="edge_source_entity_id">R159_E009</data><data key="edge_relationship_type">is_screen_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">DGEN screen created during gerontology redetermination or limited issue interview.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R013" source="R159_E009" target="R120_E012"><data key="edge_relationship_id">R159_R013</data><data key="edge_source_entity_id">R159_E009</data><data key="edge_relationship_type">documents_interview_for</data><data key="edge_target_entity_id">R120_E012</data><data key="edge_operational_context">MSSICS DGEN development documents gerontology KC diary work.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R014" source="R159_E010" target="R120_E012"><data key="edge_relationship_id">R159_R014</data><data key="edge_source_entity_id">R159_E010</data><data key="edge_relationship_type">makes_diary_available_for</data><data key="edge_target_entity_id">R120_E012</data><data key="edge_operational_context">CHINET SSI Diary Workload Control Application displays KC diary.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R015" source="APP_SSTNG" target="R120_E012"><data key="edge_relationship_id">R159_R015</data><data key="edge_source_entity_id">APP_SSTNG</data><data key="edge_relationship_type">makes_gerontology_diary_available_for</data><data key="edge_target_entity_id">R120_E012</data><data key="edge_operational_context">SSTNG supports retrieval of KC gerontology diary and appointment letters.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R016" source="R159_E011" target="R120_E012"><data key="edge_relationship_id">R159_R016</data><data key="edge_source_entity_id">R159_E011</data><data key="edge_relationship_type">determines_selection_of</data><data key="edge_target_entity_id">R120_E012</data><data key="edge_operational_context">KC selection is age at least 90, SSI-only current pay and 3 or more years with no SSR activity.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R017" source="R159_E011" target="SYS_SSR"><data key="edge_relationship_id">R159_R017</data><data key="edge_source_entity_id">R159_E011</data><data key="edge_relationship_type">checks_prior_activity_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">KC qualifying inactivity measured by SSR transactions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R018" source="R159_E012" target="R159_E009"><data key="edge_relationship_id">R159_R018</data><data key="edge_source_entity_id">R159_E012</data><data key="edge_relationship_type">interview_development_documented_on</data><data key="edge_target_entity_id">R159_E009</data><data key="edge_operational_context">DGEN screen records gerontology beneficiary identity/liveness interview.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R019" source="R159_E012" target="SYS_NUMIDENT"><data key="edge_relationship_id">R159_R019</data><data key="edge_source_entity_id">R159_E012</data><data key="edge_relationship_type">compares_beneficiary_identification_with</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Employee reviews Numident and SSR for identity/DOB anomalies ahead of gerontology interview.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R020" source="R159_E013" target="R159_E030"><data key="edge_relationship_id">R159_R020</data><data key="edge_source_entity_id">R159_E013</data><data key="edge_relationship_type">governs_address_search_outcome_of</data><data key="edge_target_entity_id">R159_E030</data><data key="edge_operational_context">Gerontology whereabouts unknown vs failed appointment leads to separate S06/N20 actions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R021" source="R159_E013" target="PROC_SSI_WU_S06"><data key="edge_relationship_id">R159_R021</data><data key="edge_source_entity_id">R159_E013</data><data key="edge_relationship_type">specializes_existing_suspension_procedure</data><data key="edge_target_entity_id">PROC_SSI_WU_S06</data><data key="edge_operational_context">KC case S06 where recipient cannot be located after contact development.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R022" source="R159_E014" target="APP_EVID"><data key="edge_relationship_id">R159_R022</data><data key="edge_source_entity_id">R159_E014</data><data key="edge_relationship_type">requires_death_proof_recorded_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">EVID required to support verified SSI death update, with limited Numident proof exceptions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R023" source="R159_E014" target="SYS_SSR"><data key="edge_relationship_id">R159_R023</data><data key="edge_source_entity_id">R159_E014</data><data key="edge_relationship_type">applies_to_verification_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR death entry without evidence may not establish verified proof.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R024" source="R159_E015" target="SYS_SSR"><data key="edge_relationship_id">R159_R024</data><data key="edge_source_entity_id">R159_E015</data><data key="edge_relationship_type">clears_diary_using_direct_update_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Non-MSSICS gerontology limited issue diary cleared using direct SSR update (UDIA).</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R025" source="R159_E015" target="FORM_SSA1719B"><data key="edge_relationship_id">R159_R025</data><data key="edge_source_entity_id">R159_E015</data><data key="edge_relationship_type">uses_input_form</data><data key="edge_target_entity_id">FORM_SSA1719B</data><data key="edge_operational_context">Non-MSSICS gerontology processing includes SSA-1719B.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R026" source="R159_E028" target="APP_ARIS"><data key="edge_relationship_id">R159_R026</data><data key="edge_source_entity_id">R159_E028</data><data key="edge_relationship_type">uses_referral_application</data><data key="edge_target_entity_id">APP_ARIS</data><data key="edge_operational_context">Suspected death fraud referral made via ARIS with KC Gerontology LI notation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R027" source="R159_E028" target="ORG_SSA_OIG"><data key="edge_relationship_id">R159_R027</data><data key="edge_source_entity_id">R159_E028</data><data key="edge_relationship_type">refers_suspected_fraud_to</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">Gerontology alert after suspected recipient death may require OIG referral.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R028" source="R159_E029" target="R159_E012"><data key="edge_relationship_id">R159_R028</data><data key="edge_source_entity_id">R159_E029</data><data key="edge_relationship_type">protects_disclosure_in</data><data key="edge_target_entity_id">R159_E012</data><data key="edge_operational_context">Helper may assist only with beneficiary permission; is not an appointed representative by virtue of helping.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R029" source="R159_E030" target="FORM_SSA_L502"><data key="edge_relationship_id">R159_R029</data><data key="edge_source_entity_id">R159_E030</data><data key="edge_relationship_type">requests_reachability_through</data><data key="edge_target_entity_id">FORM_SSA_L502</data><data key="edge_operational_context">Telephone appointment letters support gerontology recipient contact.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R030" source="R159_E030" target="FORM_SSA_L501"><data key="edge_relationship_id">R159_R030</data><data key="edge_source_entity_id">R159_E030</data><data key="edge_relationship_type">may_send_home_visit_notice</data><data key="edge_target_entity_id">FORM_SSA_L501</data><data key="edge_operational_context">Home-visit letter is used if telephone identity or contact inadequate.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R031" source="R159_E030" target="PROC_SSI_WU_S06"><data key="edge_relationship_id">R159_R031</data><data key="edge_source_entity_id">R159_E030</data><data key="edge_relationship_type">uses_existing_address_location_process</data><data key="edge_target_entity_id">PROC_SSI_WU_S06</data><data key="edge_operational_context">Undeliverable gerontology notice triggers standard address-location procedures, not automatic master updates.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R032" source="R159_E030" target="SYS_SSR"><data key="edge_relationship_id">R159_R032</data><data key="edge_source_entity_id">R159_E030</data><data key="edge_relationship_type">collects_external_leads_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Address observation from third-party sources requires investigation before program record change.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R033" source="R159_E012" target="R159_E009"><data key="edge_relationship_id">R159_R033</data><data key="edge_source_entity_id">R159_E012</data><data key="edge_relationship_type">requires_completion_of</data><data key="edge_target_entity_id">R159_E009</data><data key="edge_operational_context">DGEN development completeness controls closure of gerontology limited issue.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R034" source="R159_E016" target="DB_DCF"><data key="edge_relationship_id">R159_R034</data><data key="edge_source_entity_id">R159_E016</data><data key="edge_relationship_type">loads_workload_into</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Office of Systems loads age-18 redetermination cases and related CDR alerts in DCF.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R035" source="R159_E016" target="APP_DCFS"><data key="edge_relationship_id">R159_R035</data><data key="edge_source_entity_id">R159_E016</data><data key="edge_relationship_type">creates_age18_worklist_in</data><data key="edge_target_entity_id">APP_DCFS</data><data key="edge_operational_context">DCF FO pending medical CDR list receives age-18 alerts.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R036" source="R159_E017" target="DB_DCF"><data key="edge_relationship_id">R159_R036</data><data key="edge_source_entity_id">R159_E017</data><data key="edge_relationship_type">classifies_cdr_events_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Type 4 CDR age 18/DDS direct-release category stored in DCF.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R037" source="R159_E018" target="APP_DCFS"><data key="edge_relationship_id">R159_R037</data><data key="edge_source_entity_id">R159_E018</data><data key="edge_relationship_type">screens_age18_nonmedical_cases_in</data><data key="edge_target_entity_id">APP_DCFS</data><data key="edge_operational_context">Event 5 SSR/MBR condition permits FO to screen age-18 case for nonmedical rules.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R038" source="R159_E018" target="SYS_SSR"><data key="edge_relationship_id">R159_R038</data><data key="edge_source_entity_id">R159_E018</data><data key="edge_relationship_type">checks_program_record_conditions_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Screenout requires applicable SSI record conditions rather than presumed need for another full review.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R039" source="R159_E019" target="APP_SSTNG"><data key="edge_relationship_id">R159_R039</data><data key="edge_source_entity_id">R159_E019</data><data key="edge_relationship_type">is_coordinated_using</data><data key="edge_target_entity_id">APP_SSTNG</data><data key="edge_operational_context">Age-18 RZ and medical redetermination interview coordinated using SSTNG when both show pending.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R040" source="R159_E019" target="WORK_SSI_KB_DIARY"><data key="edge_relationship_id">R159_R040</data><data key="edge_source_entity_id">R159_E019</data><data key="edge_relationship_type">triggered_by</data><data key="edge_target_entity_id">WORK_SSI_KB_DIARY</data><data key="edge_operational_context">KB age-18 diary requires DDS medical redetermination; selected no earlier than two months before 18.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R041" source="R159_E020" target="SYS_SSR"><data key="edge_relationship_id">R159_R041</data><data key="edge_source_entity_id">R159_E020</data><data key="edge_relationship_type">checks_type_of_master_record_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Employee checks TMR DC-to-DI and prior determination dates for adult disability criteria.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R042" source="R159_E020" target="R159_E018"><data key="edge_relationship_id">R159_R042</data><data key="edge_source_entity_id">R159_E020</data><data key="edge_relationship_type">supports_review_of</data><data key="edge_target_entity_id">R159_E018</data><data key="edge_operational_context">Prior adult criteria determination can change age-18 review work requirements.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R043" source="R159_E019" target="R159_E016"><data key="edge_relationship_id">R159_R043</data><data key="edge_source_entity_id">R159_E019</data><data key="edge_relationship_type">uses_disability_worklist_from</data><data key="edge_target_entity_id">R159_E016</data><data key="edge_operational_context">Age-18 medical interview planning coordinated with loaded DCF work items.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R044" source="R159_E021" target="APP_RASR"><data key="edge_relationship_id">R159_R044</data><data key="edge_source_entity_id">R159_E021</data><data key="edge_relationship_type">notice_output_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">RASR produces RSR103 under the notice rule applicable to appointment/revocation/withdrawal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R045" source="R159_E022" target="APP_RASR"><data key="edge_relationship_id">R159_R045</data><data key="edge_source_entity_id">R159_E022</data><data key="edge_relationship_type">notice_output_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">RASR produces RSR104 under the notice rule applicable to appointment/revocation/withdrawal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R046" source="R159_E023" target="APP_RASR"><data key="edge_relationship_id">R159_R046</data><data key="edge_source_entity_id">R159_E023</data><data key="edge_relationship_type">notice_output_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">RASR produces RSR106 under the notice rule applicable to appointment/revocation/withdrawal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R047" source="R159_E024" target="APP_RASR"><data key="edge_relationship_id">R159_R047</data><data key="edge_source_entity_id">R159_E024</data><data key="edge_relationship_type">notice_output_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">RASR produces RSR107 under the notice rule applicable to appointment/revocation/withdrawal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R048" source="R159_E025" target="APP_RASR"><data key="edge_relationship_id">R159_R048</data><data key="edge_source_entity_id">R159_E025</data><data key="edge_relationship_type">notice_output_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">RASR produces RSR108 under the notice rule applicable to appointment/revocation/withdrawal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R049" source="R159_E026" target="APP_RASR"><data key="edge_relationship_id">R159_R049</data><data key="edge_source_entity_id">R159_E026</data><data key="edge_relationship_type">notice_output_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">RASR produces RSR119 under the notice rule applicable to appointment/revocation/withdrawal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R050" source="R159_E021" target="R159_E003"><data key="edge_relationship_id">R159_R050</data><data key="edge_source_entity_id">R159_E021</data><data key="edge_relationship_type">sent_to_appointed_representative</data><data key="edge_target_entity_id">R159_E003</data><data key="edge_operational_context">RSR103 goes to the appointed representative, subject to appointment validity checks.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R051" source="R159_E022" target="APP_RASR"><data key="edge_relationship_id">R159_R051</data><data key="edge_source_entity_id">R159_E022</data><data key="edge_relationship_type">sent_to_claimant_with_appointment_information</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">RSR104 goes to claimant documenting appointment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R052" source="R159_E023" target="R159_E003"><data key="edge_relationship_id">R159_R052</data><data key="edge_source_entity_id">R159_E023</data><data key="edge_relationship_type">notifies_termination_of_representative_access</data><data key="edge_target_entity_id">R159_E003</data><data key="edge_operational_context">Revocation terminates representative access to claimant information.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R053" source="R159_E025" target="APP_RASR"><data key="edge_relationship_id">R159_R053</data><data key="edge_source_entity_id">R159_E025</data><data key="edge_relationship_type">describes_replacement_principal_representative_for</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">RSR108 identifies new principal representative after another representative withdraws.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R054" source="R159_E026" target="R159_E021"><data key="edge_relationship_id">R159_R054</data><data key="edge_source_entity_id">R159_E026</data><data key="edge_relationship_type">documents_direct_fee_assignment_distinct_from</data><data key="edge_target_entity_id">R159_E021</data><data key="edge_operational_context">RSR119 supports assignment of fee payment to entity, unlike ordinary appointment notice.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R055" source="R159_E027" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R159_R055</data><data key="edge_source_entity_id">R159_E027</data><data key="edge_relationship_type">constrains_submission_through</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Upload Documents does not accept original or certified documents electronically.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R056" source="R159_E027" target="DOM_PERSON_CUSTOMER_RECORD"><data key="edge_relationship_id">R159_R056</data><data key="edge_source_entity_id">R159_E027</data><data key="edge_relationship_type">applies_to_evidence_submission_not_identity_synchronization</data><data key="edge_target_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="edge_operational_context">No automatic update of Person or another authoritative record from upload capability is established.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R057" source="R159_E009" target="SYS_SSR"><data key="edge_relationship_id">R159_R057</data><data key="edge_source_entity_id">R159_E009</data><data key="edge_relationship_type">requires_completed_posteligibility_record_build_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">MSSICS DGEN completion allows building SSR and closing limited issue.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R159_R058" source="R159_E029" target="R159_E012"><data key="edge_relationship_id">R159_R058</data><data key="edge_source_entity_id">R159_E029</data><data key="edge_relationship_type">supports_assistance_for</data><data key="edge_target_entity_id">R159_E012</data><data key="edge_operational_context">Helper presence is controlled by consent at interview, not appointed representative authority.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes documented policy/workflow, not undocumented infrastructure or database synchronization.</data></edge><edge id="R160_R0001" source="SYS_MBR" target="R160_E0001"><data key="edge_relationship_id">R160_R0001</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">death_posting_triggers</data><data key="edge_target_entity_id">R160_E0001</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0002" source="R160_E0001" target="APP_RECOOP"><data key="edge_relationship_id">R160_R0002</data><data key="edge_source_entity_id">R160_E0001</data><data key="edge_relationship_type">stops_billing_in</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0003" source="R160_E0001" target="R160_E0002"><data key="edge_relationship_id">R160_R0003</data><data key="edge_source_entity_id">R160_E0001</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R160_E0002</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0004" source="R160_E0002" target="APP_RECOOP"><data key="edge_relationship_id">R160_R0004</data><data key="edge_source_entity_id">R160_E0002</data><data key="edge_relationship_type">is_produced_by</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0005" source="SYS_SSR" target="R160_E0003"><data key="edge_relationship_id">R160_R0005</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">death_posting_triggers</data><data key="edge_target_entity_id">R160_E0003</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0006" source="R160_E0003" target="APP_RECOOP"><data key="edge_relationship_id">R160_R0006</data><data key="edge_source_entity_id">R160_E0003</data><data key="edge_relationship_type">removes_debt_from</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0007" source="R160_E0004" target="SYS_SSR"><data key="edge_relationship_id">R160_R0007</data><data key="edge_source_entity_id">R160_E0004</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0008" source="R160_E0004" target="APP_RECOOP"><data key="edge_relationship_id">R160_R0008</data><data key="edge_source_entity_id">R160_E0004</data><data key="edge_relationship_type">controls_debt_action_in</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R160_R0009" source="R160_E0005" target="APP_DMS"><data key="edge_relationship_id">R160_R0009</data><data key="edge_source_entity_id">R160_E0005</data><data key="edge_relationship_type">is_screen_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0010" source="R160_E0006" target="APP_DMS"><data key="edge_relationship_id">R160_R0010</data><data key="edge_source_entity_id">R160_E0006</data><data key="edge_relationship_type">is_screen_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0011" source="R160_E0008" target="R160_E0009"><data key="edge_relationship_id">R160_R0011</data><data key="edge_source_entity_id">R160_E0008</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">R160_E0009</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0012" source="R160_E0008" target="FORM_SSA1724F4"><data key="edge_relationship_id">R160_R0012</data><data key="edge_source_entity_id">R160_E0008</data><data key="edge_relationship_type">can_use</data><data key="edge_target_entity_id">FORM_SSA1724F4</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0013" source="R160_E0008" target="SYS_MBR"><data key="edge_relationship_id">R160_R0013</data><data key="edge_source_entity_id">R160_E0008</data><data key="edge_relationship_type">requires_assessment_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Physical direct MBR read interface not established by POMS.</data></edge><edge id="R160_R0014" source="R160_E0010" target="R160_E0011"><data key="edge_relationship_id">R160_R0014</data><data key="edge_source_entity_id">R160_E0010</data><data key="edge_relationship_type">requires_unpaid_share_hold</data><data key="edge_target_entity_id">R160_E0011</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0015" source="R160_E0011" target="DATA_MBR_SPA_LINE"><data key="edge_relationship_id">R160_R0015</data><data key="edge_source_entity_id">R160_E0011</data><data key="edge_relationship_type">retains_unpaid_balance_in</data><data key="edge_target_entity_id">DATA_MBR_SPA_LINE</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0016" source="R160_E0011" target="SYS_MBR"><data key="edge_relationship_id">R160_R0016</data><data key="edge_source_entity_id">R160_E0011</data><data key="edge_relationship_type">documents_reason_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0017" source="R160_E0012" target="DATA_MBR_SPA_LINE"><data key="edge_relationship_id">R160_R0017</data><data key="edge_source_entity_id">R160_E0012</data><data key="edge_relationship_type">retains_unissued_payment_in</data><data key="edge_target_entity_id">DATA_MBR_SPA_LINE</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0018" source="R160_E0012" target="SYS_MBR"><data key="edge_relationship_id">R160_R0018</data><data key="edge_source_entity_id">R160_E0012</data><data key="edge_relationship_type">annotates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0019" source="R160_E0013" target="FORM_SSA1724F4"><data key="edge_relationship_id">R160_R0019</data><data key="edge_source_entity_id">R160_E0013</data><data key="edge_relationship_type">receives</data><data key="edge_target_entity_id">FORM_SSA1724F4</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0020" source="R160_E0013" target="R160_E0014"><data key="edge_relationship_id">R160_R0020</data><data key="edge_source_entity_id">R160_E0013</data><data key="edge_relationship_type">applies</data><data key="edge_target_entity_id">R160_E0014</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0021" source="R160_E0013" target="DATA_MBR_SPA_LINE"><data key="edge_relationship_id">R160_R0021</data><data key="edge_source_entity_id">R160_E0013</data><data key="edge_relationship_type">holds_unclaimed_balance_in</data><data key="edge_target_entity_id">DATA_MBR_SPA_LINE</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0022" source="R160_E0015" target="R160_E0016"><data key="edge_relationship_id">R160_R0022</data><data key="edge_source_entity_id">R160_E0015</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R160_E0016</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0023" source="R160_E0015" target="DATA_MBR_SPA_LINE"><data key="edge_relationship_id">R160_R0023</data><data key="edge_source_entity_id">R160_E0015</data><data key="edge_relationship_type">holds_barred_recipient_share_in</data><data key="edge_target_entity_id">DATA_MBR_SPA_LINE</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0024" source="SYS_MBR" target="DATA_MBR_SPA_LINE"><data key="edge_relationship_id">R160_R0024</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">retains_foreign_unissued_underpayment_as</data><data key="edge_target_entity_id">DATA_MBR_SPA_LINE</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0025" source="R160_E0017" target="DATA_MBR_SPA_LINE"><data key="edge_relationship_id">R160_R0025</data><data key="edge_source_entity_id">R160_E0017</data><data key="edge_relationship_type">holds_unverified_share_in</data><data key="edge_target_entity_id">DATA_MBR_SPA_LINE</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0026" source="R160_E0018" target="R160_E0019"><data key="edge_relationship_id">R160_R0026</data><data key="edge_source_entity_id">R160_E0018</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R160_E0019</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0027" source="R160_E0020" target="R160_E0021"><data key="edge_relationship_id">R160_R0027</data><data key="edge_source_entity_id">R160_E0020</data><data key="edge_relationship_type">requires_when_payer_unverified</data><data key="edge_target_entity_id">R160_E0021</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0028" source="R160_E0020" target="FORM_SSA1724F4"><data key="edge_relationship_id">R160_R0028</data><data key="edge_source_entity_id">R160_E0020</data><data key="edge_relationship_type">may_use</data><data key="edge_target_entity_id">FORM_SSA1724F4</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0029" source="R160_E0020" target="FORM_SSA795"><data key="edge_relationship_id">R160_R0029</data><data key="edge_source_entity_id">R160_E0020</data><data key="edge_relationship_type">may_use</data><data key="edge_target_entity_id">FORM_SSA795</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0030" source="APP_T2R" target="R160_E0022"><data key="edge_relationship_id">R160_R0030</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">produces_premium_refund_alert</data><data key="edge_target_entity_id">R160_E0022</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0031" source="ORG_CMS" target="R160_E0023"><data key="edge_relationship_id">R160_R0031</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">handles</data><data key="edge_target_entity_id">R160_E0023</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0032" source="PROC_STATE_BUYIN" target="R160_E0022"><data key="edge_relationship_id">R160_R0032</data><data key="edge_source_entity_id">PROC_STATE_BUYIN</data><data key="edge_relationship_type">may_create_premium_refund_condition_for</data><data key="edge_target_entity_id">R160_E0022</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">No automated mechanism or interface is specified.</data></edge><edge id="R160_R0033" source="R160_E0025" target="R160_E0024"><data key="edge_relationship_id">R160_R0033</data><data key="edge_source_entity_id">R160_E0025</data><data key="edge_relationship_type">documented_by</data><data key="edge_target_entity_id">R160_E0024</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0034" source="ORG_CMS" target="R160_E0025"><data key="edge_relationship_id">R160_R0034</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">funding_source_for</data><data key="edge_target_entity_id">R160_E0025</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R160_R0035" source="APP_SPS" target="R160_E0025"><data key="edge_relationship_id">R160_R0035</data><data key="edge_source_entity_id">APP_SPS</data><data key="edge_relationship_type">requires_associated_manual_funding</data><data key="edge_target_entity_id">R160_E0025</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0036" source="APP_MCS" target="R160_E0026"><data key="edge_relationship_id">R160_R0036</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">has_propagation_precedence_set_by</data><data key="edge_target_entity_id">R160_E0026</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0037" source="R160_E0026" target="APP_EDCS"><data key="edge_relationship_id">R160_R0037</data><data key="edge_source_entity_id">R160_E0026</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0038" source="SYS_ICDB" target="APP_EDCS"><data key="edge_relationship_id">R160_R0038</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">is_listed_as_source_for</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0039" source="R160_E0027" target="APP_EDCS"><data key="edge_relationship_id">R160_R0039</data><data key="edge_source_entity_id">R160_E0027</data><data key="edge_relationship_type">controls_intake_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0040" source="R160_E0027" target="APP_EVIEW"><data key="edge_relationship_id">R160_R0040</data><data key="edge_source_entity_id">R160_E0027</data><data key="edge_relationship_type">records_nonpropagation_reason_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0041" source="R160_E0028" target="APP_EDCS"><data key="edge_relationship_id">R160_R0041</data><data key="edge_source_entity_id">R160_E0028</data><data key="edge_relationship_type">controls_field_values_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0042" source="R160_E0029" target="DATA_ROC"><data key="edge_relationship_id">R160_R0042</data><data key="edge_source_entity_id">R160_E0029</data><data key="edge_relationship_type">produces_snapshot_in</data><data key="edge_target_entity_id">DATA_ROC</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0043" source="R160_E0029" target="APP_EDCS"><data key="edge_relationship_id">R160_R0043</data><data key="edge_source_entity_id">R160_E0029</data><data key="edge_relationship_type">occurs_during</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0044" source="R160_E0028" target="R160_E0029"><data key="edge_relationship_id">R160_R0044</data><data key="edge_source_entity_id">R160_E0028</data><data key="edge_relationship_type">requires_preoverlap_snapshot</data><data key="edge_target_entity_id">R160_E0029</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0045" source="R160_E0030" target="APP_MCS"><data key="edge_relationship_id">R160_R0045</data><data key="edge_source_entity_id">R160_E0030</data><data key="edge_relationship_type">requires_correction_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0046" source="R160_E0030" target="APP_MSSICS"><data key="edge_relationship_id">R160_R0046</data><data key="edge_source_entity_id">R160_E0030</data><data key="edge_relationship_type">requires_correction_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0047" source="R160_E0030" target="APP_EDCS"><data key="edge_relationship_id">R160_R0047</data><data key="edge_source_entity_id">R160_E0030</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0048" source="R160_E0031" target="APP_EDCS"><data key="edge_relationship_id">R160_R0048</data><data key="edge_source_entity_id">R160_E0031</data><data key="edge_relationship_type">blocks_case_creation_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0049" source="R160_E0031" target="APP_MCS"><data key="edge_relationship_id">R160_R0049</data><data key="edge_source_entity_id">R160_E0031</data><data key="edge_relationship_type">requires_resolving_claim_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0050" source="R160_E0032" target="APP_EDCS"><data key="edge_relationship_id">R160_R0050</data><data key="edge_source_entity_id">R160_E0032</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R160_R0051" source="APP_EDCS" target="SYS_MBR"><data key="edge_relationship_id">R160_R0051</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">transfer_of_T2_CDR_appeal_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">No transport or physical DB synchronization mechanism asserted.</data></edge><edge id="R160_R0052" source="APP_EDCS" target="DB_DCF"><data key="edge_relationship_id">R160_R0052</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">transfer_of_T2_CDR_appeal_updates</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context" /><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R161_R0001" source="R161_E0001" target="APP_SS5_REPRINTS"><data key="edge_relationship_id">R161_R0001</data><data key="edge_source_entity_id">R161_E0001</data><data key="edge_relationship_type">uses_prior_ss5_microprint</data><data key="edge_target_entity_id">APP_SS5_REPRINTS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0002" source="R161_E0001" target="SYS_NUMIDENT"><data key="edge_relationship_id">R161_R0002</data><data key="edge_source_entity_id">R161_E0001</data><data key="edge_relationship_type">investigates_last_record_iteration</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0003" source="APP_PEBES" target="R161_E0002"><data key="edge_relationship_id">R161_R0003</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">applies_address_availability_selection</data><data key="edge_target_entity_id">R161_E0002</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0004" source="ORG_IRS" target="R161_E0003"><data key="edge_relationship_id">R161_R0004</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">must_satisfy_before_tax_information_request</data><data key="edge_target_entity_id">R161_E0003</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0005" source="R161_E0003" target="SYS_MBR"><data key="edge_relationship_id">R161_R0005</data><data key="edge_source_entity_id">R161_E0003</data><data key="edge_relationship_type">permits_limited_address_and_payment_disclosure</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0006" source="ORG_IRS" target="R161_E0004"><data key="edge_relationship_id">R161_R0006</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">may_conduct_authorized_tax_safeguard_audit</data><data key="edge_target_entity_id">R161_E0004</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0007" source="DATA_IRS_TOP_WEEKLY_TAX_DEBT_FILE" target="R161_E0005"><data key="edge_relationship_id">R161_R0007</data><data key="edge_source_entity_id">DATA_IRS_TOP_WEEKLY_TAX_DEBT_FILE</data><data key="edge_relationship_type">includes_match_notification_indicator</data><data key="edge_target_entity_id">R161_E0005</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0008" source="R161_E0005" target="DB_NID3"><data key="edge_relationship_id">R161_R0008</data><data key="edge_source_entity_id">R161_E0005</data><data key="edge_relationship_type">applies_to_treasury_delinq_debtor_records</data><data key="edge_target_entity_id">DB_NID3</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0009" source="DATA_FPLP_PAYMENT_RECORD" target="DATA_FPLP_BYPASS_CODE"><data key="edge_relationship_id">R161_R0009</data><data key="edge_source_entity_id">DATA_FPLP_PAYMENT_RECORD</data><data key="edge_relationship_type">carries_payment_levy_exclusion_code</data><data key="edge_target_entity_id">DATA_FPLP_BYPASS_CODE</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0010" source="ORG_IRS" target="R161_E0006"><data key="edge_relationship_id">R161_R0010</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">transmits_levy_notice_image</data><data key="edge_target_entity_id">R161_E0006</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0011" source="R161_E0006" target="APP_ORS"><data key="edge_relationship_id">R161_R0011</data><data key="edge_source_entity_id">R161_E0006</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0012" source="R161_E0006" target="R161_E0007"><data key="edge_relationship_id">R161_R0012</data><data key="edge_source_entity_id">R161_E0006</data><data key="edge_relationship_type">is_governed_by</data><data key="edge_target_entity_id">R161_E0007</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0013" source="PROC_FPLP" target="R161_E0008"><data key="edge_relationship_id">R161_R0013</data><data key="edge_source_entity_id">PROC_FPLP</data><data key="edge_relationship_type">supports_nonentitlement_reversals</data><data key="edge_target_entity_id">R161_E0008</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0014" source="R161_E0008" target="ORG_BFS"><data key="edge_relationship_id">R161_R0014</data><data key="edge_source_entity_id">R161_E0008</data><data key="edge_relationship_type">instructs_treasury_levy_reversal</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0015" source="REPO_CEF" target="R161_E0009"><data key="edge_relationship_id">R161_R0015</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">is_required_for_virtual_federal_review</data><data key="edge_target_entity_id">R161_E0009</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0016" source="R161_E0009" target="APP_QRCPS"><data key="edge_relationship_id">R161_R0016</data><data key="edge_source_entity_id">R161_E0009</data><data key="edge_relationship_type">review_results_recorded_in</data><data key="edge_target_entity_id">APP_QRCPS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0017" source="APP_QRCPS" target="R161_E0010"><data key="edge_relationship_id">R161_R0017</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">transmits_review_data_to_central_office</data><data key="edge_target_entity_id">R161_E0010</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0018" source="R161_E0010" target="R161_E0011"><data key="edge_relationship_id">R161_R0018</data><data key="edge_source_entity_id">R161_E0010</data><data key="edge_relationship_type">supports_production_of</data><data key="edge_target_entity_id">R161_E0011</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0019" source="R161_E0012" target="APP_DCPS"><data key="edge_relationship_id">R161_R0019</data><data key="edge_source_entity_id">R161_E0012</data><data key="edge_relationship_type">requires_case_closure_in</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0020" source="R161_E0012" target="APP_EVIEW"><data key="edge_relationship_id">R161_R0020</data><data key="edge_source_entity_id">R161_E0012</data><data key="edge_relationship_type">requires_case_closure_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0021" source="R161_E0012" target="APP_NDDSS"><data key="edge_relationship_id">R161_R0021</data><data key="edge_source_entity_id">R161_E0012</data><data key="edge_relationship_type">requires_case_closure_in</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0022" source="R161_E0012" target="R161_E0013"><data key="edge_relationship_id">R161_R0022</data><data key="edge_source_entity_id">R161_E0012</data><data key="edge_relationship_type">applies_following_completion</data><data key="edge_target_entity_id">R161_E0013</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0023" source="R161_E0013" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R161_R0023</data><data key="edge_source_entity_id">R161_E0013</data><data key="edge_relationship_type">routable_to_originating_office</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R161_R0024" source="R161_E0013" target="R110_E002"><data key="edge_relationship_id">R161_R0024</data><data key="edge_source_entity_id">R161_E0013</data><data key="edge_relationship_type">routable_to_national_records_center</data><data key="edge_target_entity_id">R110_E002</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R162_R0001" source="R162_E0002" target="R162_E0001"><data key="edge_relationship_id">R162_R0001</data><data key="edge_source_entity_id">R162_E0002</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R162_E0001</data><data key="edge_operational_context">The Title II PSC workflow prepares a court-usable certified payment extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0002" source="R162_E0003" target="R162_E0001"><data key="edge_relationship_id">R162_R0002</data><data key="edge_source_entity_id">R162_E0003</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R162_E0001</data><data key="edge_operational_context">The Title XVI regional-office workflow prepares a certified SSI payment extract.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0003" source="R162_E0001" target="R162_E0004"><data key="edge_relationship_id">R162_R0003</data><data key="edge_source_entity_id">R162_E0001</data><data key="edge_relationship_type">requires_certification</data><data key="edge_target_entity_id">R162_E0004</data><data key="edge_operational_context">CPE packet includes authorization for certification (Swear Statement).</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0004" source="R162_E0001" target="R162_E0005"><data key="edge_relationship_id">R162_R0004</data><data key="edge_source_entity_id">R162_E0001</data><data key="edge_relationship_type">accompanied_by</data><data key="edge_target_entity_id">R162_E0005</data><data key="edge_operational_context">CPE packet requires accompanying cover memorandum.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0005" source="R162_E0001" target="R162_E0006"><data key="edge_relationship_id">R162_R0005</data><data key="edge_source_entity_id">R162_E0001</data><data key="edge_relationship_type">constrained_by</data><data key="edge_target_entity_id">R162_E0006</data><data key="edge_operational_context">Only negotiated checks appear; returned checks are specifically excluded.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0006" source="R162_E0001" target="R162_E0007"><data key="edge_relationship_id">R162_R0006</data><data key="edge_source_entity_id">R162_E0001</data><data key="edge_relationship_type">can_include_institution_metadata</data><data key="edge_target_entity_id">R162_E0007</data><data key="edge_operational_context">Relevant bank name and address are listed when a financial institution is involved.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0007" source="R162_E0001" target="R162_E0008"><data key="edge_relationship_id">R162_R0007</data><data key="edge_source_entity_id">R162_E0001</data><data key="edge_relationship_type">documents_payee_transition_with</data><data key="edge_target_entity_id">R162_E0008</data><data key="edge_operational_context">Extract describes representative-payee change dates when applicable.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0008" source="R162_E0009" target="R162_E0001"><data key="edge_relationship_id">R162_R0008</data><data key="edge_source_entity_id">R162_E0009</data><data key="edge_relationship_type">routes_requests_for</data><data key="edge_target_entity_id">R162_E0001</data><data key="edge_operational_context">OIG CPE requests use CASI flag and regional PSC CASI function.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0009" source="ORG_SSA_OIG" target="R162_E0009"><data key="edge_relationship_id">R162_R0009</data><data key="edge_source_entity_id">ORG_SSA_OIG</data><data key="edge_relationship_type">requests</data><data key="edge_target_entity_id">R162_E0009</data><data key="edge_operational_context">OIG seeks extracts for fraud investigations through CASI route.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0010" source="R162_E0002" target="R162_E0010"><data key="edge_relationship_id">R162_R0010</data><data key="edge_source_entity_id">R162_E0002</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R162_E0010</data><data key="edge_operational_context">Priority CPE processing target applies to payment extracts.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0011" source="R162_E0003" target="R162_E0010"><data key="edge_relationship_id">R162_R0011</data><data key="edge_source_entity_id">R162_E0003</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R162_E0010</data><data key="edge_operational_context">Priority CPE processing target applies to payment extracts.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0012" source="PROC_SYSTEM_INFO_AS_PROOF" target="R162_E0013"><data key="edge_relationship_id">R162_R0012</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">requires_proven_factor_or_proof_code</data><data key="edge_target_entity_id">R162_E0013</data><data key="edge_operational_context">GN 01010.038 limits prior data reuse to factors proven in paid entitlement or coded evidence.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0013" source="R162_E0013" target="SYS_MBR"><data key="edge_relationship_id">R162_R0013</data><data key="edge_source_entity_id">R162_E0013</data><data key="edge_relationship_type">can_use_evidence_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR proven entitlement or proof coding supports conditional reuse.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0014" source="R162_E0013" target="SYS_SSR"><data key="edge_relationship_id">R162_R0014</data><data key="edge_source_entity_id">R162_E0013</data><data key="edge_relationship_type">can_use_evidence_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR proven entitlement or proof coding supports conditional reuse.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0015" source="R162_E0013" target="SYS_NUMIDENT"><data key="edge_relationship_id">R162_R0015</data><data key="edge_source_entity_id">R162_E0013</data><data key="edge_relationship_type">can_use_evidence_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Numident may provide applicable proof information subject to specific policy.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0016" source="R162_E0013" target="APP_DRAMS"><data key="edge_relationship_id">R162_R0016</data><data key="edge_source_entity_id">R162_E0013</data><data key="edge_relationship_type">can_use_evidence_from</data><data key="edge_target_entity_id">APP_DRAMS</data><data key="edge_operational_context">Disability/Railroad/Alien/Military-Service query may supply acceptable evidence subject to policy.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0017" source="R162_E0013" target="R162_E0011"><data key="edge_relationship_id">R162_R0017</data><data key="edge_source_entity_id">R162_E0013</data><data key="edge_relationship_type">requires_new_earnings_proof_when</data><data key="edge_target_entity_id">R162_E0011</data><data key="edge_operational_context">Prior entitlement for BIC E, C or G insufficient to establish fully insured status.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0018" source="R162_E0012" target="UI_MCS_EARN"><data key="edge_relationship_id">R162_R0018</data><data key="edge_source_entity_id">R162_E0012</data><data key="edge_relationship_type">checks_data_from</data><data key="edge_target_entity_id">UI_MCS_EARN</data><data key="edge_operational_context">Review MCS EARN computation-year values for agreement with DEQY.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0019" source="R162_E0012" target="UI_MCS_ECOR"><data key="edge_relationship_id">R162_R0019</data><data key="edge_source_entity_id">R162_E0012</data><data key="edge_relationship_type">checks_data_from</data><data key="edge_target_entity_id">UI_MCS_ECOR</data><data key="edge_operational_context">Review MCS ECOR computation-year values for agreement with DEQY.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0020" source="R162_E0012" target="QRY_DEQY"><data key="edge_relationship_id">R162_R0020</data><data key="edge_source_entity_id">R162_E0012</data><data key="edge_relationship_type">validates_using</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">DEQY used to confirm that source screen values reached MEF.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0021" source="R162_E0012" target="SYS_MEF"><data key="edge_relationship_id">R162_R0021</data><data key="edge_source_entity_id">R162_E0012</data><data key="edge_relationship_type">verifies_update_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">MEF update is confirmed by comparison, not assumed.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0022" source="R162_E0012" target="APP_ICOR"><data key="edge_relationship_id">R162_R0022</data><data key="edge_source_entity_id">R162_E0012</data><data key="edge_relationship_type">requires_correction_through_if_needed</data><data key="edge_target_entity_id">APP_ICOR</data><data key="edge_operational_context">POMS directs necessary corrective action such as ICOR when MEF not updated.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0023" source="APP_REACT" target="R162_E0014"><data key="edge_relationship_id">R162_R0023</data><data key="edge_source_entity_id">APP_REACT</data><data key="edge_relationship_type">generates_notice_for</data><data key="edge_target_entity_id">R162_E0014</data><data key="edge_operational_context">LP notice returned to PSC supports repayment decision; REACT generally produces Title II notice file.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0024" source="R162_E0014" target="R162_E0015"><data key="edge_relationship_id">R162_R0024</data><data key="edge_source_entity_id">R162_E0014</data><data key="edge_relationship_type">requires_completion_of</data><data key="edge_target_entity_id">R162_E0015</data><data key="edge_operational_context">Incomplete notice cannot support repayment until applicable defects resolved.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0025" source="R162_E0015" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">R162_R0025</data><data key="edge_source_entity_id">R162_E0015</data><data key="edge_relationship_type">can_file_unresolved_in</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">When neither signature nor check selection is on notice, PC files in Paperless and takes no repayment action.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0026" source="R162_E0014" target="DB_PHUS"><data key="edge_relationship_id">R162_R0026</data><data key="edge_source_entity_id">R162_E0014</data><data key="edge_relationship_type">requires_eligibility_status_check_with</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">PC uses payment history to respond to inquiry; not automatic repaying.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0027" source="R162_E0016" target="SYS_SSR"><data key="edge_relationship_id">R162_R0027</data><data key="edge_source_entity_id">R162_E0016</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI direct-contact LP policy unlike Title II mailed notice.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0028" source="SVC_PRIVACY_RECORD_ACCESS" target="R162_E0017"><data key="edge_relationship_id">R162_R0028</data><data key="edge_source_entity_id">SVC_PRIVACY_RECORD_ACCESS</data><data key="edge_relationship_type">subject_to_recordholder_age_gate</data><data key="edge_target_entity_id">R162_E0017</data><data key="edge_operational_context">SSA web access gate states record holder, age 18+, identity verified; third-party requester not supported in this channel.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0029" source="SVC_PRIVACY_RECORD_ACCESS" target="R162_E0018"><data key="edge_relationship_id">R162_R0029</data><data key="edge_source_entity_id">SVC_PRIVACY_RECORD_ACCESS</data><data key="edge_relationship_type">limited_to_record_scope</data><data key="edge_target_entity_id">R162_E0018</data><data key="edge_operational_context">Public access form lists four SORNs and specified record types.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0030" source="R162_E0018" target="SYS_MBR"><data key="edge_relationship_id">R162_R0030</data><data key="edge_source_entity_id">R162_E0018</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR 60-0090 records eligible for electronic privacy request under list.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0031" source="R162_E0018" target="SYS_SSR"><data key="edge_relationship_id">R162_R0031</data><data key="edge_source_entity_id">R162_E0018</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI/SVB 60-0103 records eligible for electronic privacy request under list.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0032" source="R162_E0018" target="DB_EDIB_CLAIM_FILE"><data key="edge_relationship_id">R162_R0032</data><data key="edge_source_entity_id">R162_E0018</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_operational_context">eDIB 60-0320 records eligible for electronic privacy request under list.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0033" source="R162_E0020" target="SVC_ASAP"><data key="edge_relationship_id">R162_R0033</data><data key="edge_source_entity_id">R162_E0020</data><data key="edge_relationship_type">implemented_using</data><data key="edge_target_entity_id">SVC_ASAP</data><data key="edge_operational_context">Grants FAQ says SSA award recipients establish electronic payment accounts via ASAP.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0034" source="R162_E0019" target="R162_E0020"><data key="edge_relationship_id">R162_R0034</data><data key="edge_source_entity_id">R162_E0019</data><data key="edge_relationship_type">interim_manual_request_for</data><data key="edge_target_entity_id">R162_E0020</data><data key="edge_operational_context">SF-270 may be emailed to SSA financial analyst as interim mechanism.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0035" source="R162_E0021" target="SVC_GRANTSOLUTIONS"><data key="edge_relationship_id">R162_R0035</data><data key="edge_source_entity_id">R162_E0021</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_operational_context">OAG application guidance specifies GrantSolutions for continuation grants.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R162_R0036" source="R162_E0022" target="SVC_GRANTS_GOV"><data key="edge_relationship_id">R162_R0036</data><data key="edge_source_entity_id">R162_E0022</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_GRANTS_GOV</data><data key="edge_operational_context">OAG application guidance specifies Grants.gov for competitive discretionary applications.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented administrative relationship; no undocumented physical deployment, transport or synchronization implied.</data></edge><edge id="R163_R0001" source="ORG_DDS" target="R163_E001"><data key="edge_relationship_id">R163_R0001</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R163_E001</data><data key="edge_operational_context">DDS decisional-data entry has specific enumerated exclusions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0002" source="R163_E001" target="R163_E002"><data key="edge_relationship_id">R163_R0002</data><data key="edge_source_entity_id">R163_E001</data><data key="edge_relationship_type">has_title_ii_exception</data><data key="edge_target_entity_id">R163_E002</data><data key="edge_operational_context">Title II enumerates prisoner, TWP, MQGE, totalization, CDR 301 and EPE exclusions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0003" source="R163_E001" target="R163_E003"><data key="edge_relationship_id">R163_R0003</data><data key="edge_source_entity_id">R163_E001</data><data key="edge_relationship_type">has_title_xvi_exception</data><data key="edge_target_entity_id">R163_E003</data><data key="edge_operational_context">Title XVI enumerates systems-limitation, reconsideration-reversal and favorable-reopening exclusions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0004" source="ORG_DDS" target="R163_E004"><data key="edge_relationship_id">R163_R0004</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">required_to_record</data><data key="edge_target_entity_id">R163_E004</data><data key="edge_operational_context">DDS must report intake and clearance of cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0005" source="R163_E004" target="APP_NDDSS"><data key="edge_relationship_id">R163_R0005</data><data key="edge_source_entity_id">R163_E004</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_operational_context">DDS enters case movement data and NDDSS provides inquiry of case-control status; technical transfer is not specified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0006" source="R163_E001" target="R163_E004"><data key="edge_relationship_id">R163_R0006</data><data key="edge_source_entity_id">R163_E001</data><data key="edge_relationship_type">restricts</data><data key="edge_target_entity_id">R163_E004</data><data key="edge_operational_context">DDS decision-data entry restrictions do not abolish required case movement reporting.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0007" source="ORG_DDS" target="R163_E005"><data key="edge_relationship_id">R163_R0007</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">R163_E005</data><data key="edge_operational_context">DDS must locate claimant or request FO assistance when whereabouts become unknown.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0008" source="R163_E005" target="R163_E007"><data key="edge_relationship_id">R163_R0008</data><data key="edge_source_entity_id">R163_E005</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R163_E007</data><data key="edge_operational_context">USPS address search may use a 15-day SSA-L2001 response window.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0009" source="R163_E007" target="FORM_SSA_L2001"><data key="edge_relationship_id">R163_R0009</data><data key="edge_source_entity_id">R163_E007</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA_L2001</data><data key="edge_operational_context">DDS sends SSA-L2001 to postmaster; retrieved address is a lead, not an automatic master-record update.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0010" source="R163_E005" target="R163_E008"><data key="edge_relationship_id">R163_R0010</data><data key="edge_source_entity_id">R163_E005</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R163_E008</data><data key="edge_operational_context">DDS may initiate DCPS FO assistance request, retaining jurisdiction.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0011" source="R163_E008" target="APP_DCPS"><data key="edge_relationship_id">R163_R0011</data><data key="edge_source_entity_id">R163_E008</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DCPS carries DDS-to-FO assistance requests and follow-up controls.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0012" source="R163_E005" target="R163_E006"><data key="edge_relationship_id">R163_R0012</data><data key="edge_source_entity_id">R163_E005</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R163_E006</data><data key="edge_operational_context">Appointed representative addresses cannot directly change DCPS except stated guardianship/parent exceptions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0013" source="R163_E006" target="APP_DCPS"><data key="edge_relationship_id">R163_R0013</data><data key="edge_source_entity_id">R163_E006</data><data key="edge_relationship_type">restricts_updates_to</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Unconfirmed AR-provided contact information cannot automatically modify claimant contact information in DCPS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0014" source="R163_E005" target="R163_E010"><data key="edge_relationship_id">R163_R0014</data><data key="edge_source_entity_id">R163_E005</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R163_E010</data><data key="edge_operational_context">DDS cannot deny solely due to unknown whereabouts.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0015" source="R163_E010" target="R163_E009"><data key="edge_relationship_id">R163_R0015</data><data key="edge_source_entity_id">R163_E010</data><data key="edge_relationship_type">documents_using</data><data key="edge_target_entity_id">R163_E009</data><data key="edge_operational_context">Whereabouts unknown determination must show last-known address on SSA-831 and rationale in explanation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0016" source="APP_IAPPT" target="R163_E011"><data key="edge_relationship_id">R163_R0016</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R163_E011</data><data key="edge_operational_context">iAppt UNVER data is stored in eLAS pending SSN/other attribute verification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0017" source="R163_E011" target="WORK_ELAS_UNVER"><data key="edge_relationship_id">R163_R0017</data><data key="edge_source_entity_id">R163_E011</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">WORK_ELAS_UNVER</data><data key="edge_operational_context">UNVER on eLAS WKSH records nonverified internet data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0018" source="R163_E011" target="FUNC_ELAS_VERIFY_PI"><data key="edge_relationship_id">R163_R0018</data><data key="edge_source_entity_id">R163_E011</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FUNC_ELAS_VERIFY_PI</data><data key="edge_operational_context">Verify PI receipts UNVER following verification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0019" source="R163_E011" target="SYS_ICDB"><data key="edge_relationship_id">R163_R0019</data><data key="edge_source_entity_id">R163_E011</data><data key="edge_relationship_type">conditionally_promotes_to</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">Verified eLAS appointment information can enter CLIENT only following verification and issue receipt.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0020" source="R163_E011" target="SYS_NUMIDENT"><data key="edge_relationship_id">R163_R0020</data><data key="edge_source_entity_id">R163_E011</data><data key="edge_relationship_type">does_not_automatically_update</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">iAppt data is not automatically used to correct Numident.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0021" source="R163_E011" target="APP_PERSON_INFO"><data key="edge_relationship_id">R163_R0021</data><data key="edge_source_entity_id">R163_E011</data><data key="edge_relationship_type">does_not_automatically_update</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">iAppt data is not automatically used to correct Person Information.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0022" source="APP_ELAS" target="R163_E012"><data key="edge_relationship_id">R163_R0022</data><data key="edge_source_entity_id">APP_ELAS</data><data key="edge_relationship_type">enforces</data><data key="edge_target_entity_id">R163_E012</data><data key="edge_operational_context">eLAS suppresses iAppt confirmation notices until UNVER resolution.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0023" source="R163_E012" target="WORK_ELAS_UNVER"><data key="edge_relationship_id">R163_R0023</data><data key="edge_source_entity_id">R163_E012</data><data key="edge_relationship_type">depends_on</data><data key="edge_target_entity_id">WORK_ELAS_UNVER</data><data key="edge_operational_context">Suppression is linked to pending UNVER, which must be resolved before manual notice.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0024" source="R163_E013" target="APP_ELAS"><data key="edge_relationship_id">R163_R0024</data><data key="edge_source_entity_id">R163_E013</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">eLAS fifth calendar is reserved for online iAppt use.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0025" source="APP_IAPPT" target="R163_E013"><data key="edge_relationship_id">R163_R0025</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R163_E013</data><data key="edge_operational_context">iAppt queries slots allocated to fifth eLAS calendar.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0026" source="APP_IAPPT" target="R163_E014"><data key="edge_relationship_id">R163_R0026</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R163_E014</data><data key="edge_operational_context">ASL language selection triggers FO mailbox and fallback Area Director Office notice.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0027" source="R163_E014" target="UI_ELAS_RMRK"><data key="edge_relationship_id">R163_R0027</data><data key="edge_source_entity_id">R163_E014</data><data key="edge_relationship_type">records_on</data><data key="edge_target_entity_id">UI_ELAS_RMRK</data><data key="edge_operational_context">ASL and language preferences generate designated eLAS remark.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0028" source="APP_IAPPT" target="R163_E015"><data key="edge_relationship_id">R163_R0028</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R163_E015</data><data key="edge_operational_context">Successful scheduling displays online confirmation with protective-filing closeout dates.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0029" source="R163_E015" target="APP_ELAS"><data key="edge_relationship_id">R163_R0029</data><data key="edge_source_entity_id">R163_E015</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">iAppt creates protective filing and appointment data in eLAS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0030" source="R163_E016" target="APP_CCE"><data key="edge_relationship_id">R163_R0030</data><data key="edge_source_entity_id">R163_E016</data><data key="edge_relationship_type">documents_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Special pandemic assistance allegations documented on CCE Report of Contact.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0031" source="R163_E016" target="FORM_SSA5002"><data key="edge_relationship_id">R163_R0031</data><data key="edge_source_entity_id">R163_E016</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">Alternative recorded pandemic assistance evidence used SSA-5002.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0032" source="R163_E016" target="APP_EP"><data key="edge_relationship_id">R163_R0032</data><data key="edge_source_entity_id">R163_E016</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">SSA-5002 uploads entered electronic folder using Evidence Portal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0033" source="R163_E017" target="R163_E016"><data key="edge_relationship_id">R163_R0033</data><data key="edge_source_entity_id">R163_E017</data><data key="edge_relationship_type">supersedes_for_new_development</data><data key="edge_target_entity_id">R163_E016</data><data key="edge_operational_context">2026-08-21 ends routine special inquiry/documentation for new development, preserves historical case treatment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0034" source="R163_E018" target="R163_E016"><data key="edge_relationship_id">R163_R0034</data><data key="edge_source_entity_id">R163_E018</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">R163_E016</data><data key="edge_operational_context">Prior procedures warn that incorrect CCE Disaster Assistance posting may change deeming allocations.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0035" source="R163_E019" target="R163_E016"><data key="edge_relationship_id">R163_R0035</data><data key="edge_source_entity_id">R163_E019</data><data key="edge_relationship_type">reference_for</data><data key="edge_target_entity_id">R163_E016</data><data key="edge_operational_context">State/territory pandemic unemployment end dates inform earlier income exclusions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0036" source="R163_E020" target="APP_SSI_COMPUTE"><data key="edge_relationship_id">R163_R0036</data><data key="edge_source_entity_id">R163_E020</data><data key="edge_relationship_type">changed</data><data key="edge_target_entity_id">APP_SSI_COMPUTE</data><data key="edge_operational_context">August 2021 SSI Computations software handled covered pandemic unemployment exclusions automatically.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0037" source="R163_E020" target="APP_CCE"><data key="edge_relationship_id">R163_R0037</data><data key="edge_source_entity_id">R163_E020</data><data key="edge_relationship_type">changed</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">POMS associates August 2021 auto-exclusion change with CCE and SSI Computations.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0038" source="APP_EAFI" target="R163_E021"><data key="edge_relationship_id">R163_R0038</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R163_E021</data><data key="edge_operational_context">AFI negative/geo search and look-back govern account verification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0039" source="R163_E021" target="UI_SSI_FI_ACCOUNT"><data key="edge_relationship_id">R163_R0039</data><data key="edge_source_entity_id">R163_E021</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_operational_context">Verified SSI financial balances are documented on financial account resource page where permitted.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0040" source="R163_E022" target="R163_E021"><data key="edge_relationship_id">R163_R0040</data><data key="edge_source_entity_id">R163_E022</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R163_E021</data><data key="edge_operational_context">Alternative evidence is allowed but does not always replace required AFI negative search/verification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0041" source="R163_E022" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R163_R0041</data><data key="edge_source_entity_id">R163_E022</data><data key="edge_relationship_type">supports_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Uploaded bank statements or transaction-image files can satisfy completeness requirements.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0042" source="R163_E023" target="UI_SSI_FI_ACCOUNT"><data key="edge_relationship_id">R163_R0042</data><data key="edge_source_entity_id">R163_E023</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_operational_context">Legal entitlement to withdraw funds affects SSI resource-countability evaluation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0043" source="R163_E023" target="DATA_FI_BANK_STATEMENT_EVIDENCE"><data key="edge_relationship_id">R163_R0043</data><data key="edge_source_entity_id">R163_E023</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_FI_BANK_STATEMENT_EVIDENCE</data><data key="edge_operational_context">Complete bank account statements are one accepted form of ownership and balance evidence.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0044" source="R163_E024" target="FORM_SS5"><data key="edge_relationship_id">R163_R0044</data><data key="edge_source_entity_id">R163_E024</data><data key="edge_relationship_type">related_form_in_family</data><data key="edge_target_entity_id">FORM_SS5</data><data key="edge_operational_context">SSA Forms displays original SS-5 and outside-US SS-5-FS as separate card application forms; no shared electronic workflow is inferred.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0045" source="R163_E026" target="REPORT_SSI_ANNUAL_2026"><data key="edge_relationship_id">R163_R0045</data><data key="edge_source_entity_id">R163_E026</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_operational_context">OACT publication list links the July 22, 2026 annual SSI report.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R163_R0046" source="ORG_SSA_OCACT" target="R163_E026"><data key="edge_relationship_id">R163_R0046</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R163_E026</data><data key="edge_operational_context">Office of the Chief Actuary publishes actuarial-publications index.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS or SSA page documents the operational rule. Does not imply undocumented interface, data retention, hosting, or automatic updates.</data></edge><edge id="R164_R0001" source="APP_RASR" target="R164_E001"><data key="edge_relationship_id">R164_R0001</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">supports_eligibility_reconciliation</data><data key="edge_target_entity_id">R164_E001</data><data key="edge_operational_context">Field office reviews appointment and waiver information in RASR before effectuation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.1. Operational rule/publication relationship only.</data></edge><edge id="R164_R0002" source="SYS_SSR" target="R164_E009"><data key="edge_relationship_id">R164_R0002</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R164_E009</data><data key="edge_operational_context">SSR reflects principal representative identity and direct payment eligibility.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.1. Operational rule/publication relationship only.</data></edge><edge id="R164_R0003" source="R164_E001" target="SYS_SSR"><data key="edge_relationship_id">R164_R0003</data><data key="edge_source_entity_id">R164_E001</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Field office reconciles SSR with electronic/paper folder and RASR before effectuation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.1. Operational rule/publication relationship only.</data></edge><edge id="R164_R0004" source="R164_E001" target="R164_E002"><data key="edge_relationship_id">R164_R0004</data><data key="edge_source_entity_id">R164_E001</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">R164_E002</data><data key="edge_operational_context">For non-attorney direct pay eligibility, staff check RASR EDPNA query as of effectuation date.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.2. Operational rule/publication relationship only.</data></edge><edge id="R164_R0005" source="R164_E002" target="APP_RASR"><data key="edge_relationship_id">R164_R0005</data><data key="edge_source_entity_id">R164_E002</data><data key="edge_relationship_type">is_query_within</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">EDPNA Query is documented in RASR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.2.b. Operational rule/publication relationship only.</data></edge><edge id="R164_R0006" source="R164_E001" target="R164_E003"><data key="edge_relationship_id">R164_R0006</data><data key="edge_source_entity_id">R164_E001</data><data key="edge_relationship_type">uses_screen</data><data key="edge_target_entity_id">R164_E003</data><data key="edge_operational_context">For absent representative on SSR, use UMEN along with UATH and UFEE.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.1. Operational rule/publication relationship only.</data></edge><edge id="R164_R0007" source="R164_E001" target="UI_MSSICS_UATH"><data key="edge_relationship_id">R164_R0007</data><data key="edge_source_entity_id">R164_E001</data><data key="edge_relationship_type">uses_screen</data><data key="edge_target_entity_id">UI_MSSICS_UATH</data><data key="edge_operational_context">Representative authorization data entered through UATH.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.1. Operational rule/publication relationship only.</data></edge><edge id="R164_R0008" source="R164_E001" target="UI_MSSICS_UFEE"><data key="edge_relationship_id">R164_R0008</data><data key="edge_source_entity_id">R164_E001</data><data key="edge_relationship_type">uses_screen</data><data key="edge_target_entity_id">UI_MSSICS_UFEE</data><data key="edge_operational_context">Fee eligibility/waiver data entered through UFEE.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.1. Operational rule/publication relationship only.</data></edge><edge id="R164_R0009" source="R164_E003" target="SYS_SSR"><data key="edge_relationship_id">R164_R0009</data><data key="edge_source_entity_id">R164_E003</data><data key="edge_relationship_type">supports_program_update_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">UMEN screen is specified for representative record coding to SSR. No transport claim.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.1. Operational rule/publication relationship only.</data></edge><edge id="R164_R0010" source="R164_E010" target="R164_E004"><data key="edge_relationship_id">R164_R0010</data><data key="edge_source_entity_id">R164_E010</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">R164_E004</data><data key="edge_operational_context">Prior OPDD collection decisions require removal and later reposting in qualifying cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.4.b,C.4.d. Operational rule/publication relationship only.</data></edge><edge id="R164_R0011" source="R164_E004" target="SYS_SSR"><data key="edge_relationship_id">R164_R0011</data><data key="edge_source_entity_id">R164_E004</data><data key="edge_relationship_type">is_segment_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">OPDD is described as segment of existing SSR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.4.b. Operational rule/publication relationship only.</data></edge><edge id="R164_R0012" source="R164_E010" target="R164_E007"><data key="edge_relationship_id">R164_R0012</data><data key="edge_source_entity_id">R164_E010</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">R164_E007</data><data key="edge_operational_context">Deleting prior OPDD collection decision establishes diary to repost.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.4.b,C.4.d. Operational rule/publication relationship only.</data></edge><edge id="R164_R0013" source="R164_E010" target="R164_E005"><data key="edge_relationship_id">R164_R0013</data><data key="edge_source_entity_id">R164_E010</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">R164_E005</data><data key="edge_operational_context">Fee petition followup diary by resolution/court context.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.4,C.7. Operational rule/publication relationship only.</data></edge><edge id="R164_R0014" source="R164_E010" target="R164_E006"><data key="edge_relationship_id">R164_R0014</data><data key="edge_source_entity_id">R164_E010</data><data key="edge_relationship_type">may_generate</data><data key="edge_target_entity_id">R164_E006</data><data key="edge_operational_context">IAR underpayment review at $5,000 or more triggers I9 alert requiring OTP reimbursement, with qualifying conditions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.4.c. Operational rule/publication relationship only.</data></edge><edge id="R164_R0015" source="R164_E010" target="PROC_AOTP"><data key="edge_relationship_id">R164_R0015</data><data key="edge_source_entity_id">R164_E010</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PROC_AOTP</data><data key="edge_operational_context">A-OTP used for State IAR reimbursement and claimant underpayment release.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.4. Operational rule/publication relationship only.</data></edge><edge id="R164_R0016" source="R164_E010" target="DATA_SSI_U_TAC"><data key="edge_relationship_id">R164_R0016</data><data key="edge_source_entity_id">R164_E010</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_SSI_U_TAC</data><data key="edge_operational_context">U TAC manually withholds past-due SSI amounts in prescribed fee/IAR cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.4. Operational rule/publication relationship only.</data></edge><edge id="R164_R0017" source="R164_E010" target="R164_E008"><data key="edge_relationship_id">R164_R0017</data><data key="edge_source_entity_id">R164_E010</data><data key="edge_relationship_type">enforces</data><data key="edge_target_entity_id">R164_E008</data><data key="edge_operational_context">Privacy limits govern fee notices and former representative information.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, B,C.5-C.6. Operational rule/publication relationship only.</data></edge><edge id="R164_R0018" source="R164_E001" target="R164_E010"><data key="edge_relationship_id">R164_R0018</data><data key="edge_source_entity_id">R164_E001</data><data key="edge_relationship_type">may_precede</data><data key="edge_target_entity_id">R164_E010</data><data key="edge_operational_context">Direct payment eligibility and appointment status are resolved before fee withholding.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S001, C.1,C.4. Operational rule/publication relationship only.</data></edge><edge id="R164_R0019" source="R164_E011" target="R164_E012"><data key="edge_relationship_id">R164_R0019</data><data key="edge_source_entity_id">R164_E011</data><data key="edge_relationship_type">requires_when_applicable</data><data key="edge_target_entity_id">R164_E012</data><data key="edge_operational_context">Prior claim folders generally requested before reopening; exceptions specified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S002, B.2. Operational rule/publication relationship only.</data></edge><edge id="R164_R0020" source="R164_E011" target="ORG_DDS"><data key="edge_relationship_id">R164_R0020</data><data key="edge_source_entity_id">R164_E011</data><data key="edge_relationship_type">authorizes_by_level</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">DDS may reopen same/lower-level final disability determinations within policy.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S002, B.3.a. Operational rule/publication relationship only.</data></edge><edge id="R164_R0021" source="R164_E011" target="ORG_DHU"><data key="edge_relationship_id">R164_R0021</data><data key="edge_source_entity_id">R164_E011</data><data key="edge_relationship_type">authorizes_by_level</data><data key="edge_target_entity_id">ORG_DHU</data><data key="edge_operational_context">DHU has specified medical reconsideration reopening jurisdiction; cannot reopen ALJ/AC decisions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S002, B.3.b. Operational rule/publication relationship only.</data></edge><edge id="R164_R0022" source="R164_E011" target="R164_E013"><data key="edge_relationship_id">R164_R0022</data><data key="edge_source_entity_id">R164_E011</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R164_E013</data><data key="edge_operational_context">Medical improvement review standard applies to defined adverse medical revisions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S002, B.4. Operational rule/publication relationship only.</data></edge><edge id="R164_R0023" source="R164_E011" target="R164_E014"><data key="edge_relationship_id">R164_R0023</data><data key="edge_source_entity_id">R164_E011</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R164_E014</data><data key="edge_operational_context">Reopening revisions include documented due process and notice actions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S002, D.1-D.3. Operational rule/publication relationship only.</data></edge><edge id="R164_R0024" source="R164_E016" target="R164_E015"><data key="edge_relationship_id">R164_R0024</data><data key="edge_source_entity_id">R164_E016</data><data key="edge_relationship_type">may_be_documented_on</data><data key="edge_target_entity_id">R164_E015</data><data key="edge_operational_context">Denial of reopening request may be documented on SSA-553.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S002, D.4. Operational rule/publication relationship only.</data></edge><edge id="R164_R0025" source="R164_E016" target="R164_E011"><data key="edge_relationship_id">R164_R0025</data><data key="edge_source_entity_id">R164_E016</data><data key="edge_relationship_type">follows</data><data key="edge_target_entity_id">R164_E011</data><data key="edge_operational_context">No-appeal-rights reopening denial follows applicable administrative finality policy.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S002, D.4. Operational rule/publication relationship only.</data></edge><edge id="R164_R0026" source="R164_E017" target="DATA_OACT_TRUST_FUND_FINANCIAL"><data key="edge_relationship_id">R164_R0026</data><data key="edge_source_entity_id">R164_E017</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_operational_context">OASI short-range table is a publicly accessible statistical product in Trustees report, not transactional accounting store.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S003, IV.A1. Operational rule/publication relationship only.</data></edge><edge id="R164_R0027" source="R164_E018" target="DATA_OACT_TRUST_FUND_FINANCIAL"><data key="edge_relationship_id">R164_R0027</data><data key="edge_source_entity_id">R164_E018</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_operational_context">DI short-range table reflects projections in Trustees report and historic data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S003, IV.A2. Operational rule/publication relationship only.</data></edge><edge id="R164_R0028" source="R164_E019" target="DATA_OACT_TRUST_FUND_FINANCIAL"><data key="edge_relationship_id">R164_R0028</data><data key="edge_source_entity_id">R164_E019</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_operational_context">Combined OASDI table presents hypothetical combined short-range position.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S003, IV.A3. Operational rule/publication relationship only.</data></edge><edge id="R164_R0029" source="R164_E020" target="R164_E017"><data key="edge_relationship_id">R164_R0029</data><data key="edge_source_entity_id">R164_E020</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R164_E017</data><data key="edge_operational_context">Short-range adequacy standard considered for OASI projected ratios.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S003, IV.A. Operational rule/publication relationship only.</data></edge><edge id="R164_R0030" source="R164_E020" target="R164_E018"><data key="edge_relationship_id">R164_R0030</data><data key="edge_source_entity_id">R164_E020</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R164_E018</data><data key="edge_operational_context">Short-range adequacy standard considered for DI projected ratios.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S003, IV.A. Operational rule/publication relationship only.</data></edge><edge id="R164_R0031" source="R164_E020" target="R164_E019"><data key="edge_relationship_id">R164_R0031</data><data key="edge_source_entity_id">R164_E020</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">R164_E019</data><data key="edge_operational_context">Combined ratio and reserves also evaluated under intermediate assumptions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R164_S003, IV.A. Operational rule/publication relationship only.</data></edge><edge id="R165_R0001" source="R165_E001" target="R165_E002"><data key="edge_relationship_id">R165_R0001</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">uses_evidence</data><data key="edge_target_entity_id">R165_E002</data><data key="edge_operational_context">A properly attributed electronic writing may evidence written acknowledgment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section B-C. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0002" source="R165_E001" target="R165_E003"><data key="edge_relationship_id">R165_R0002</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">uses_mcs_screen</data><data key="edge_target_entity_id">R165_E003</data><data key="edge_operational_context">MCS DEPC qualifies conditionally with NH application on APPL or RMKS proof.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section C.5. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0003" source="R165_E003" target="APP_MCS"><data key="edge_relationship_id">R165_R0003</data><data key="edge_source_entity_id">R165_E003</data><data key="edge_relationship_type">is_screen_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Dependent-children screen in Modernized Claims System.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section C.5. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0004" source="R165_E001" target="R165_E004"><data key="edge_relationship_id">R165_R0004</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">may_use_appointment_evidence</data><data key="edge_target_entity_id">R165_E004</data><data key="edge_operational_context">eLAS appointment shows NH initiated contact and named identifiable child.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section G. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0005" source="R165_E004" target="APP_ELAS"><data key="edge_relationship_id">R165_R0005</data><data key="edge_source_entity_id">R165_E004</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Appointment scheduling record can protect acknowledgment date.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section G. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0006" source="R165_E001" target="R165_E005"><data key="edge_relationship_id">R165_R0006</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R165_E005</data><data key="edge_operational_context">Acknowledgment date determines effective parent-child relationship absent earlier evidence.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section F. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0007" source="R165_E001" target="R165_E006"><data key="edge_relationship_id">R165_R0007</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">requires_conflict_review</data><data key="edge_target_entity_id">R165_E006</data><data key="edge_operational_context">Conflicting parentage evidence must be resolved.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section D-E. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0008" source="R165_E006" target="ORG_SSA_OGC"><data key="edge_relationship_id">R165_R0008</data><data key="edge_source_entity_id">R165_E006</data><data key="edge_relationship_type">may_request_legal_opinion_from</data><data key="edge_target_entity_id">ORG_SSA_OGC</data><data key="edge_operational_context">Unresolved biological relationship may require an SSA legal opinion.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section E. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0009" source="R165_E001" target="R165_E007"><data key="edge_relationship_id">R165_R0009</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">accepts_claimant_provided_tax_return_as</data><data key="edge_target_entity_id">R165_E007</data><data key="edge_operational_context">NH tax return naming child as dependent may serve as evidence.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section C.4. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0010" source="R165_E007" target="R165_E009"><data key="edge_relationship_id">R165_R0010</data><data key="edge_source_entity_id">R165_E007</data><data key="edge_relationship_type">subject_to_supply_restriction</data><data key="edge_target_entity_id">R165_E009</data><data key="edge_operational_context">IRS/state tax office does not provide return copy directly to SSA for this evidence workflow.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section C.4. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0011" source="ORG_IRS" target="R165_E007"><data key="edge_relationship_id">R165_R0011</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">does_not_routinely_send_tax_copy_for</data><data key="edge_target_entity_id">R165_E007</data><data key="edge_operational_context">Policy says IRS does not furnish tax-return copies to SSA under this specific written-acknowledgment evidence pathway.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section C.4. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0012" source="R165_E001" target="R165_E008"><data key="edge_relationship_id">R165_R0012</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">can_reference</data><data key="edge_target_entity_id">R165_E008</data><data key="edge_operational_context">Form SSA-2519 suggests sources of child-relationship proof.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section C. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0013" source="R165_E001" target="DATA_NUMIDENT_EAB_PARENTAGE"><data key="edge_relationship_id">R165_R0013</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">can_use_eab_attribute</data><data key="edge_target_entity_id">DATA_NUMIDENT_EAB_PARENTAGE</data><data key="edge_operational_context">EAB Numident parentage data may support child relationship under conditions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section D. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0014" source="R165_E001" target="UI_MCS_RPOC"><data key="edge_relationship_id">R165_R0014</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">documents_review_in</data><data key="edge_target_entity_id">UI_MCS_RPOC</data><data key="edge_operational_context">MCS RPOC documents proof and adjudication when MCS screen used.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section C.5. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0015" source="R165_E006" target="DATA_NUMIDENT_EAB_PARENTAGE"><data key="edge_relationship_id">R165_R0015</data><data key="edge_source_entity_id">R165_E006</data><data key="edge_relationship_type">compares_parentage_on</data><data key="edge_target_entity_id">DATA_NUMIDENT_EAB_PARENTAGE</data><data key="edge_operational_context">EAB and birth-certificate parentage contradictions can trigger further development.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section E. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0016" source="R165_E001" target="R165_E013"><data key="edge_relationship_id">R165_R0016</data><data key="edge_source_entity_id">R165_E001</data><data key="edge_relationship_type">applies_later_iteration_check</data><data key="edge_target_entity_id">R165_E013</data><data key="edge_operational_context">EAB parent-name field is reviewed against subsequent Numident iterations.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S001 section D. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0017" source="R165_E010" target="R165_E011"><data key="edge_relationship_id">R165_R0017</data><data key="edge_source_entity_id">R165_E010</data><data key="edge_relationship_type">uses_policy_matrix</data><data key="edge_target_entity_id">R165_E011</data><data key="edge_operational_context">Jurisdiction and date of state law determine whether presumption is available.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section B.1. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0018" source="R165_E010" target="R165_E012"><data key="edge_relationship_id">R165_R0018</data><data key="edge_source_entity_id">R165_E010</data><data key="edge_relationship_type">can_use_parent_informant_signature</data><data key="edge_target_entity_id">R165_E012</data><data key="edge_operational_context">Signed informant name plus parent name on full birth certificate may establish acknowledgment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section A.1.a. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0019" source="R165_E010" target="DATA_NUMIDENT_EAB_PARENTAGE"><data key="edge_relationship_id">R165_R0019</data><data key="edge_source_entity_id">R165_E010</data><data key="edge_relationship_type">queries_parentage_evidence</data><data key="edge_target_entity_id">DATA_NUMIDENT_EAB_PARENTAGE</data><data key="edge_operational_context">Source of EAB parent name is state vital-record registration.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section A.2. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0020" source="R165_E010" target="R165_E013"><data key="edge_relationship_id">R165_R0020</data><data key="edge_source_entity_id">R165_E010</data><data key="edge_relationship_type">requires_non_supersession_rule</data><data key="edge_target_entity_id">R165_E013</data><data key="edge_operational_context">Later Numident iterations must not identify different parent under corresponding field.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section A.2. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0021" source="R165_E011" target="R165_E010"><data key="edge_relationship_id">R165_R0021</data><data key="edge_source_entity_id">R165_E011</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R165_E010</data><data key="edge_operational_context">Presumption requires state law consent or court order when paternal name entered.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section B. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0022" source="ORG_STATE_BVS" target="EX_EAB"><data key="edge_relationship_id">R165_R0022</data><data key="edge_source_entity_id">ORG_STATE_BVS</data><data key="edge_relationship_type">provides_birth_registration_data_via</data><data key="edge_target_entity_id">EX_EAB</data><data key="edge_operational_context">State vital data including parent names transferred through Enumeration at Birth.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section A.2. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0023" source="R165_E010" target="R165_E001"><data key="edge_relationship_id">R165_R0023</data><data key="edge_source_entity_id">R165_E010</data><data key="edge_relationship_type">may_establish</data><data key="edge_target_entity_id">R165_E001</data><data key="edge_operational_context">EAB parentage evidence may satisfy federal written-acknowledgment path if conditions hold.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section A. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0024" source="R165_E011" target="ORG_SSA_OGC"><data key="edge_relationship_id">R165_R0024</data><data key="edge_source_entity_id">R165_E011</data><data key="edge_relationship_type">may_require_legal_opinion_from</data><data key="edge_target_entity_id">ORG_SSA_OGC</data><data key="edge_operational_context">When State rule or date cannot be determined, request legal opinion.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section B.2. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0025" source="R165_E013" target="SYS_NUMIDENT"><data key="edge_relationship_id">R165_R0025</data><data key="edge_source_entity_id">R165_E013</data><data key="edge_relationship_type">examines_record_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">EAB FMC=6, MNA/FNA and subsequent iterations require review.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R56_011 section A.2. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0026" source="R165_E016" target="R165_E014"><data key="edge_relationship_id">R165_R0026</data><data key="edge_source_entity_id">R165_E016</data><data key="edge_relationship_type">accepts_certified_evidence_via</data><data key="edge_target_entity_id">R165_E014</data><data key="edge_operational_context">Certified decree or support order as evidence of biological parentage.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S002 section B-C. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0027" source="R165_E016" target="R165_E015"><data key="edge_relationship_id">R165_R0027</data><data key="edge_source_entity_id">R165_E016</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R165_E015</data><data key="edge_operational_context">Post-death orders are excluded from the specific federal section 216(h)(3) court pathway.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S002 section A. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0028" source="R165_E014" target="REPO_NDRED"><data key="edge_relationship_id">R165_R0028</data><data key="edge_source_entity_id">R165_E014</data><data key="edge_relationship_type">files_into</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Certified court order is faxed into NDRed using Evidence Portal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S002 section C.1. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0029" source="R165_E014" target="APP_EP"><data key="edge_relationship_id">R165_R0029</data><data key="edge_source_entity_id">R165_E014</data><data key="edge_relationship_type">uses_portal</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Evidence Portal supports transmission of certified court parentage evidence.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S002 section C.1. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0030" source="R165_E016" target="R165_E010"><data key="edge_relationship_id">R165_R0030</data><data key="edge_source_entity_id">R165_E016</data><data key="edge_relationship_type">may_use_eab_presumption</data><data key="edge_target_entity_id">R165_E010</data><data key="edge_operational_context">Qualifying EAB Numident or birth certificate may evidence court determination.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S002 section C.2. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0031" source="R165_E016" target="ORG_SSA_OGC"><data key="edge_relationship_id">R165_R0031</data><data key="edge_source_entity_id">R165_E016</data><data key="edge_relationship_type">may_request_interpretation_from</data><data key="edge_target_entity_id">ORG_SSA_OGC</data><data key="edge_operational_context">Questionable state order or legal ambiguity may require OGC opinion.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S002 section B. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0032" source="R165_E016" target="R165_E001"><data key="edge_relationship_id">R165_R0032</data><data key="edge_source_entity_id">R165_E016</data><data key="edge_relationship_type">supports_determination</data><data key="edge_target_entity_id">R165_E001</data><data key="edge_operational_context">Court-order pathway is an alternative 216(h)(3) parent-child relationship evidentiary basis.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S002 section A-C. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0033" source="APP_TPS_BUYIN" target="R165_E017"><data key="edge_relationship_id">R165_R0033</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">enforces_identity_matching_gate</data><data key="edge_target_entity_id">R165_E017</data><data key="edge_operational_context">State buy-in accretion requires match to Health Insurance Master before Third-Party Master entry.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section B. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0034" source="R165_E017" target="R120_E001"><data key="edge_relationship_id">R165_R0034</data><data key="edge_source_entity_id">R165_E017</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">R120_E001</data><data key="edge_operational_context">Claim number and identifying attributes are matched to Health Insurance Master.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section B. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0035" source="R165_E017" target="R127_E022"><data key="edge_relationship_id">R165_R0035</data><data key="edge_source_entity_id">R165_E017</data><data key="edge_relationship_type">precedes_write_to</data><data key="edge_target_entity_id">R127_E022</data><data key="edge_operational_context">CMS only accretes state action to Third-Party Master after HI identity match.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section B. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0036" source="R165_E018" target="ORG_CMS"><data key="edge_relationship_id">R165_R0036</data><data key="edge_source_entity_id">R165_E018</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS supplies monthly SSI accretion informational alerts to alert States.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section A. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0037" source="R165_E018" target="ORG_STATES"><data key="edge_relationship_id">R165_R0037</data><data key="edge_source_entity_id">R165_E018</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Alert States use SSI accretion alerts to identify buy-in prospects.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section A. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0038" source="R165_E019" target="ORG_CMS"><data key="edge_relationship_id">R165_R0038</data><data key="edge_source_entity_id">R165_E019</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS creates monthly SSI deletion alerts when SSI ends and buy-in is active.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section C. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0039" source="R165_E019" target="ORG_STATES"><data key="edge_relationship_id">R165_R0039</data><data key="edge_source_entity_id">R165_E019</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Alert State receives deletion alert for buy-in consideration.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section C. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0040" source="APP_TPS_BUYIN" target="R165_E020"><data key="edge_relationship_id">R165_R0040</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">produces_transaction_response</data><data key="edge_target_entity_id">R165_E020</data><data key="edge_operational_context">Third-Party System provides accept/reject/interim response.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section E. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0041" source="R165_E020" target="ORG_STATES"><data key="edge_relationship_id">R165_R0041</data><data key="edge_source_entity_id">R165_E020</data><data key="edge_relationship_type">returned_to</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">State receives transaction disposition for submitted action.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section E. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0042" source="R165_E020" target="R165_E027"><data key="edge_relationship_id">R165_R0042</data><data key="edge_source_entity_id">R165_E020</data><data key="edge_relationship_type">can_enter</data><data key="edge_target_entity_id">R165_E027</data><data key="edge_operational_context">Interim response may trigger investigation and paper fallback.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section E. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0043" source="APP_TPS_BUYIN" target="R165_E021"><data key="edge_relationship_id">R165_R0043</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">enforces_retroactive_limit</data><data key="edge_target_entity_id">R165_E021</data><data key="edge_operational_context">System limits retroactive State deletion to two months from month received.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section D. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0044" source="APP_TPS_BUYIN" target="R165_E022"><data key="edge_relationship_id">R165_R0044</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">adjusts_dates_under</data><data key="edge_target_entity_id">R165_E022</data><data key="edge_operational_context">System adjusts premature State buy-in start to Medicare entitlement date.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section F. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0045" source="R165_E022" target="R120_E001"><data key="edge_relationship_id">R165_R0045</data><data key="edge_source_entity_id">R165_E022</data><data key="edge_relationship_type">references_master_record</data><data key="edge_target_entity_id">R120_E001</data><data key="edge_operational_context">System compares requested State buy-in effective date to HI Medicare entitlement.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section F. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0046" source="R165_E027" target="ORG_STATES"><data key="edge_relationship_id">R165_R0046</data><data key="edge_source_entity_id">R165_E027</data><data key="edge_relationship_type">may_produce_paper_disposition_to</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Some exceptional State transactions receive paper explanation instead of electronic response.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source R165_S003 section E. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0047" source="R165_E023" target="DATA_SAVE_QUERY_RESPONSE"><data key="edge_relationship_id">R165_R0047</data><data key="edge_source_entity_id">R165_E023</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_operational_context">Only single-character name difference with no other mismatches can be tolerated.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R119_001 section C.5.b. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0048" source="R165_E024" target="DATA_SAVE_QUERY_RESPONSE"><data key="edge_relationship_id">R165_R0048</data><data key="edge_source_entity_id">R165_E024</data><data key="edge_relationship_type">constrains_display_of</data><data key="edge_target_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_operational_context">SSA SAVE screen does not display middle name or initial.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R119_001 section C.5.b. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0049" source="R165_E025" target="DATA_SAVE_QUERY_RESPONSE"><data key="edge_relationship_id">R165_R0049</data><data key="edge_source_entity_id">R165_E025</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_operational_context">An SSN-only mismatch among otherwise matching fields does not require further action on that difference.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R119_001 section C.5.b. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0050" source="R165_E026" target="FORM_G845"><data key="edge_relationship_id">R165_R0050</data><data key="edge_source_entity_id">R165_E026</data><data key="edge_relationship_type">requires_manual_verification_form</data><data key="edge_target_entity_id">FORM_G845</data><data key="edge_operational_context">Suspected fraudulent DHS document follows manual form verification; do not rely on online SAVE.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R119_001 section C.3. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0051" source="R165_E026" target="SVC_SAVE"><data key="edge_relationship_id">R165_R0051</data><data key="edge_source_entity_id">R165_E026</data><data key="edge_relationship_type">precludes_using_online_result_as_proof</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">Suspected document fraud disallows SAVE query response as verification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R119_001 section C.3-C.4. No implementation details beyond cited evidence inferred.</data></edge><edge id="R165_R0052" source="R165_E026" target="ORG_SSA_OIG"><data key="edge_relationship_id">R165_R0052</data><data key="edge_source_entity_id">R165_E026</data><data key="edge_relationship_type">may_refer_suspected_fraud_to</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">Suspected fraud documentation may be forwarded for investigation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Primary source SRC_R119_001 section C.3. No implementation details beyond cited evidence inferred.</data></edge><edge id="R166_R0001" source="R166_E001" target="APP_EDCS"><data key="edge_relationship_id">R166_R0001</data><data key="edge_source_entity_id">R166_E001</data><data key="edge_relationship_type">form_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Electronic 3367 captured inside EDCS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0002" source="R166_E002" target="R166_E001"><data key="edge_relationship_id">R166_R0002</data><data key="edge_source_entity_id">R166_E002</data><data key="edge_relationship_type">substitutes_when_excluded_from</data><data key="edge_target_entity_id">R166_E001</data><data key="edge_operational_context">Paper 3367 used for EDCS-excluded cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0003" source="R166_E005" target="R166_E001"><data key="edge_relationship_id">R166_R0003</data><data key="edge_source_entity_id">R166_E005</data><data key="edge_relationship_type">requires_completion_of</data><data key="edge_target_entity_id">R166_E001</data><data key="edge_operational_context">Electronic 3367 completed before FO transfer for electronic cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0004" source="R166_E005" target="R166_E002"><data key="edge_relationship_id">R166_R0004</data><data key="edge_source_entity_id">R166_E005</data><data key="edge_relationship_type">allows_paper_exclusion_form</data><data key="edge_target_entity_id">R166_E002</data><data key="edge_operational_context">Paper path for exclusions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0005" source="R166_E001" target="R166_E003"><data key="edge_relationship_id">R166_R0005</data><data key="edge_source_entity_id">R166_E001</data><data key="edge_relationship_type">captures</data><data key="edge_target_entity_id">R166_E003</data><data key="edge_operational_context">3367 contains alleged onset information.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0006" source="R166_E001" target="R166_E004"><data key="edge_relationship_id">R166_R0006</data><data key="edge_source_entity_id">R166_E001</data><data key="edge_relationship_type">captures</data><data key="edge_target_entity_id">R166_E004</data><data key="edge_operational_context">3367 contains potential onset information.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0007" source="R166_E003" target="APP_MCS"><data key="edge_relationship_id">R166_R0007</data><data key="edge_source_entity_id">R166_E003</data><data key="edge_relationship_type">propagates_from</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">When a Title II MCS claim exists, alleged onset originates with MCS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0008" source="R166_E003" target="APP_MSSICS"><data key="edge_relationship_id">R166_R0008</data><data key="edge_source_entity_id">R166_E003</data><data key="edge_relationship_type">propagates_from</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">When SSI MSSICS claim exists, alleged onset originates with MSSICS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0009" source="R166_E006" target="APP_MCS"><data key="edge_relationship_id">R166_R0009</data><data key="edge_source_entity_id">R166_E006</data><data key="edge_relationship_type">corrects_at_source</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Correct MCS before repropagating AOD when applicable.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0010" source="R166_E006" target="APP_MSSICS"><data key="edge_relationship_id">R166_R0010</data><data key="edge_source_entity_id">R166_E006</data><data key="edge_relationship_type">corrects_at_source</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Correct MSSICS before repropagating AOD when applicable.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0011" source="R166_E006" target="APP_EDCS"><data key="edge_relationship_id">R166_R0011</data><data key="edge_source_entity_id">R166_E006</data><data key="edge_relationship_type">repropagates_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">After updating originating record, repropagate into EDCS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0012" source="R166_E007" target="ORG_DDS"><data key="edge_relationship_id">R166_R0012</data><data key="edge_source_entity_id">R166_E007</data><data key="edge_relationship_type">notifies</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">DDS notified through UAT after transfer; no unsupported delivery technology inferred.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0013" source="R166_E007" target="R166_E003"><data key="edge_relationship_id">R166_R0013</data><data key="edge_source_entity_id">R166_E007</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R166_E003</data><data key="edge_operational_context">Post transfer AOD change control.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0014" source="R166_E008" target="R166_E004"><data key="edge_relationship_id">R166_R0014</data><data key="edge_source_entity_id">R166_E008</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R166_E004</data><data key="edge_operational_context">Level-by-level Title II POD requirements.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0015" source="R166_E009" target="R166_E004"><data key="edge_relationship_id">R166_R0015</data><data key="edge_source_entity_id">R166_E009</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R166_E004</data><data key="edge_operational_context">Title XVI conditional POD requirement.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0016" source="R166_E010" target="R166_E001"><data key="edge_relationship_id">R166_R0016</data><data key="edge_source_entity_id">R166_E010</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">R166_E001</data><data key="edge_operational_context">NH and claimant may differ on an auxiliary benefit claim.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section preamble / A.1.a-c; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0017" source="R166_E011" target="R166_E001"><data key="edge_relationship_id">R166_R0017</data><data key="edge_source_entity_id">R166_E011</data><data key="edge_relationship_type">populates</data><data key="edge_target_entity_id">R166_E001</data><data key="edge_operational_context">Prior CEF filing information automatically appears when EDCS establishes new initial CEF.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section A.1.b / A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0018" source="R166_E011" target="REPO_CEF"><data key="edge_relationship_id">R166_R0018</data><data key="edge_source_entity_id">R166_E011</data><data key="edge_relationship_type">reuses_history_from</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Source is previous certified folder filing history; does not make CEF the only identity source.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section A.1.b / A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0019" source="R166_E012" target="R166_E001"><data key="edge_relationship_id">R166_R0019</data><data key="edge_source_entity_id">R166_E012</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">R166_E001</data><data key="edge_operational_context">Prior claim decision metadata recorded on 3367.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section A.1.b / A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0020" source="R166_E012" target="R166_E010"><data key="edge_relationship_id">R166_R0020</data><data key="edge_source_entity_id">R166_E012</data><data key="edge_relationship_type">captures_number_holder_history</data><data key="edge_target_entity_id">R166_E010</data><data key="edge_operational_context">Prior claim SSNs are tracked separately from present claim identity; no automatic identity merge.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section A.1.b / A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0021" source="R166_E013" target="ORG_DDS"><data key="edge_relationship_id">R166_R0021</data><data key="edge_source_entity_id">R166_E013</data><data key="edge_relationship_type">alerts</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">FO informs DDS of prior period terminated for failure to cooperate.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section A.1.b / A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0022" source="R166_E013" target="R166_E001"><data key="edge_relationship_id">R166_R0022</data><data key="edge_source_entity_id">R166_E013</data><data key="edge_relationship_type">documents_on</data><data key="edge_target_entity_id">R166_E001</data><data key="edge_operational_context">Prior termination flag belongs in 3367 case remarks.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section A.1.b / A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0023" source="R166_E014" target="R166_E003"><data key="edge_relationship_id">R166_R0023</data><data key="edge_source_entity_id">R166_E014</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">R166_E003</data><data key="edge_operational_context">Resolve competing alleged onset dates before onward development.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section A.1.b / A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0024" source="R166_E014" target="R166_E001"><data key="edge_relationship_id">R166_R0024</data><data key="edge_source_entity_id">R166_E014</data><data key="edge_relationship_type">documented_on</data><data key="edge_target_entity_id">R166_E001</data><data key="edge_operational_context">Reconciliation explanation entered in remarks.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S001 section A.1.b / A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0025" source="R166_E015" target="APP_EDCS"><data key="edge_relationship_id">R166_R0025</data><data key="edge_source_entity_id">R166_E015</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS prior filing page.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Authoritative source R166_S003 section A.1-A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0026" source="R166_E015" target="R166_E012"><data key="edge_relationship_id">R166_R0026</data><data key="edge_source_entity_id">R166_E015</data><data key="edge_relationship_type">captures</data><data key="edge_target_entity_id">R166_E012</data><data key="edge_operational_context">Prior claim metadata entered through EDCS page.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Authoritative source R166_S003 section A.1-A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0027" source="R166_E016" target="APP_EDCS"><data key="edge_relationship_id">R166_R0027</data><data key="edge_source_entity_id">R166_E016</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS onset page.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Authoritative source R166_S003 section A.1-A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0028" source="R166_E016" target="R166_E004"><data key="edge_relationship_id">R166_R0028</data><data key="edge_source_entity_id">R166_E016</data><data key="edge_relationship_type">captures</data><data key="edge_target_entity_id">R166_E004</data><data key="edge_operational_context">POD and reason entered on onset page.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Authoritative source R166_S003 section A.1-A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0029" source="R166_E016" target="R166_E003"><data key="edge_relationship_id">R166_R0029</data><data key="edge_source_entity_id">R166_E016</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">R166_E003</data><data key="edge_operational_context">AOD displayed on onset page.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Authoritative source R166_S003 section A.1-A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0030" source="R166_E017" target="APP_EDCS"><data key="edge_relationship_id">R166_R0030</data><data key="edge_source_entity_id">R166_E017</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS presumptive SSI page.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Authoritative source R166_S003 section A.1-A.3; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0031" source="R166_E018" target="PROC_FEE_AGREEMENT_ADMIN_REVIEW"><data key="edge_relationship_id">R166_R0031</data><data key="edge_source_entity_id">R166_E018</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_operational_context">ILQR responsible for favorable hearings/AC cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0032" source="R166_E019" target="APP_EVIEW"><data key="edge_relationship_id">R166_R0032</data><data key="edge_source_entity_id">R166_E019</data><data key="edge_relationship_type">uses_electronic_folder</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Upload administrative-review request to B section of eView when eView exists.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0033" source="R166_E019" target="APP_ENM"><data key="edge_relationship_id">R166_R0033</data><data key="edge_source_entity_id">R166_E019</data><data key="edge_relationship_type">uses_nonmedical_folder</data><data key="edge_target_entity_id">APP_ENM</data><data key="edge_operational_context">May use ENM B section if eView record absent and ENM exists.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0034" source="R166_E020" target="APP_EVIEW"><data key="edge_relationship_id">R166_R0034</data><data key="edge_source_entity_id">R166_E020</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Notice of review placed in eView section B for electronic record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0035" source="R166_E021" target="R166_E020"><data key="edge_relationship_id">R166_R0035</data><data key="edge_source_entity_id">R166_E021</data><data key="edge_relationship_type">governs_disclosure_of</data><data key="edge_target_entity_id">R166_E020</data><data key="edge_operational_context">Limit copies to third parties: redact protected address and identifying information.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0036" source="R166_E021" target="DATA_MBR_MAILING_ADDRESS"><data key="edge_relationship_id">R166_R0036</data><data key="edge_source_entity_id">R166_E021</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DATA_MBR_MAILING_ADDRESS</data><data key="edge_operational_context">Mailing addresses of claimant/auxiliary are PII; this is disclosure control, not automated MBR lookup.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0037" source="R166_E022" target="R166_E020"><data key="edge_relationship_id">R166_R0037</data><data key="edge_source_entity_id">R166_E022</data><data key="edge_relationship_type">triggered_by</data><data key="edge_target_entity_id">R166_E020</data><data key="edge_operational_context">HALLEX says decision upload to eView triggers alert.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0038" source="R166_E022" target="APP_EDCS"><data key="edge_relationship_id">R166_R0038</data><data key="edge_source_entity_id">R166_E022</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS implicated in documented alert to FO/PC; implementation mechanism unverified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0039" source="R166_E022" target="APP_EP"><data key="edge_relationship_id">R166_R0039</data><data key="edge_source_entity_id">R166_E022</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">EP implicated in documented notification; physical messaging mechanism unverified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0040" source="R166_E023" target="R166_E020"><data key="edge_relationship_id">R166_R0040</data><data key="edge_source_entity_id">R166_E023</data><data key="edge_relationship_type">fallback_for</data><data key="edge_target_entity_id">R166_E020</data><data key="edge_operational_context">Use PC mailbox and paper-file path when eView upload unavailable.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0041" source="R166_E024" target="PROC_FEE_AGREEMENT_ADMIN_REVIEW"><data key="edge_relationship_id">R166_R0041</data><data key="edge_source_entity_id">R166_E024</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_operational_context">Work diary and evidence comment windows.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source R166_S002 section A / C / D / F; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0042" source="R166_E025" target="REPO_NDRED"><data key="edge_relationship_id">R166_R0042</data><data key="edge_source_entity_id">R166_E025</data><data key="edge_relationship_type">may_be_stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Store capability medical evidence under beneficiary claim number; EP may perform upload.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0043" source="R166_E025" target="APP_EVIEW"><data key="edge_relationship_id">R166_R0043</data><data key="edge_source_entity_id">R166_E025</data><data key="edge_relationship_type">may_be_stored_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Alternatively evidence in eView under BOAN; exact record location differs by route.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0044" source="R166_E025" target="APP_EP"><data key="edge_relationship_id">R166_R0044</data><data key="edge_source_entity_id">R166_E025</data><data key="edge_relationship_type">uploaded_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Evidence Portal used to place capability evidence into NDRed/eView.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0045" source="R166_E025" target="APP_ERPS"><data key="edge_relationship_id">R166_R0045</data><data key="edge_source_entity_id">R166_E025</data><data key="edge_relationship_type">pertains_to</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">eRPS case documentation may reference where evidence is stored; not proof eRPS stores medical source files.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0046" source="R166_E026" target="APP_ERPS"><data key="edge_relationship_id">R166_R0046</data><data key="edge_source_entity_id">R166_E026</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Use eRPS Beneficiary Details RPOC if a payee application/case exists.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0047" source="R166_E026" target="R166_E025"><data key="edge_relationship_id">R166_R0047</data><data key="edge_source_entity_id">R166_E026</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R166_E025</data><data key="edge_operational_context">Authenticity questions require medical-source contact.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0048" source="R166_E027" target="R166_E025"><data key="edge_relationship_id">R166_R0048</data><data key="edge_source_entity_id">R166_E027</data><data key="edge_relationship_type">considers</data><data key="edge_target_entity_id">R166_E025</data><data key="edge_operational_context">FO assesses medical plus lay evidence, DDS opinions do not themselves decide payee capability.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0049" source="R166_E027" target="ORG_DDS"><data key="edge_relationship_id">R166_R0049</data><data key="edge_source_entity_id">R166_E027</data><data key="edge_relationship_type">receives_opinion_from</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">DDS may give evidence opinion on specified disability determination forms.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0050" source="R166_E028" target="R166_E025"><data key="edge_relationship_id">R166_R0050</data><data key="edge_source_entity_id">R166_E028</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R166_E025</data><data key="edge_operational_context">Recency conditions apply to medical-evidence development.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC006 section A.2 / A.5 / A.8; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0051" source="R166_E029" target="APP_EVIEW"><data key="edge_relationship_id">R166_R0051</data><data key="edge_source_entity_id">R166_E029</data><data key="edge_relationship_type">operates_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">eView case selection supports number holder and claimant SSN.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC018 section A / B; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0052" source="R166_E029" target="R166_E010"><data key="edge_relationship_id">R166_R0052</data><data key="edge_source_entity_id">R166_E029</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R166_E010</data><data key="edge_operational_context">Claimant identity and NH identity handled separately in auxiliary cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC018 section A / B; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0053" source="R166_E030" target="APP_EVIEW"><data key="edge_relationship_id">R166_R0053</data><data key="edge_source_entity_id">R166_E030</data><data key="edge_relationship_type">operates_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Unique EDCS folder number selects specific disability case.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC018 section A / B; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R166_R0054" source="R166_E030" target="REPO_CEF"><data key="edge_relationship_id">R166_R0054</data><data key="edge_source_entity_id">R166_E030</data><data key="edge_relationship_type">references</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Search opens case folder record by unique key. No physical-index technology asserted.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authoritative source SRC018 section A / B; observed 2026-10-10. Direction is evidence-backed, not a claim about undocumented transport, persistence, or synchronization.</data></edge><edge id="R167_R0001" source="R167_E001" target="APP_MCS"><data key="edge_relationship_id">R167_R0001</data><data key="edge_source_entity_id">R167_E001</data><data key="edge_relationship_type">requires_manual_adjudication_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">IEDS is MCS earnings-computation exception; manual route required.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.6. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0002" source="R167_E001" target="WF_A101"><data key="edge_relationship_id">R167_R0002</data><data key="edge_source_entity_id">R167_E001</data><data key="edge_relationship_type">uses_manual_transaction</data><data key="edge_target_entity_id">WF_A101</data><data key="edge_operational_context">A101 process used for IEDS adjudication.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.6. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0003" source="R167_E002" target="APP_EP"><data key="edge_relationship_id">R167_R0003</data><data key="edge_source_entity_id">R167_E002</data><data key="edge_relationship_type">submitted_through</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">SSA-1 unsigned number holder information faxed through Evidence Portal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.2. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0004" source="R167_E002" target="REPO_NDRED"><data key="edge_relationship_id">R167_R0004</data><data key="edge_source_entity_id">R167_E002</data><data key="edge_relationship_type">preserves_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Original SSA-1 intake evidence held in NDRed; paper discarded after verifying electronic receipt.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.2. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0005" source="R167_E003" target="R167_E004"><data key="edge_relationship_id">R167_R0005</data><data key="edge_source_entity_id">R167_E003</data><data key="edge_relationship_type">restricts_disclosure_during</data><data key="edge_target_entity_id">R167_E004</data><data key="edge_operational_context">Neither former spouse whereabouts may be disclosed to the other party while investigating address leads.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.4. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0006" source="R167_E004" target="R167_E008"><data key="edge_relationship_id">R167_R0006</data><data key="edge_source_entity_id">R167_E004</data><data key="edge_relationship_type">supports_identity_development</data><data key="edge_target_entity_id">R167_E008</data><data key="edge_operational_context">Employer may be contacted for nonfiling number holder address only if worked there within previous five years.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.4.b. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0007" source="R167_E005" target="APP_ICERS"><data key="edge_relationship_id">R167_R0007</data><data key="edge_source_entity_id">R167_E005</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">APP_ICERS</data><data key="edge_operational_context">ICERS certified E/R determines insured status and PIA.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.5. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0008" source="R167_E006" target="APP_MCS"><data key="edge_relationship_id">R167_R0008</data><data key="edge_source_entity_id">R167_E006</data><data key="edge_relationship_type">processed_using</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Allowed IEDS claim entered through MCS auxiliary-claim process.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.6. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0009" source="R167_E006" target="WF_A101"><data key="edge_relationship_id">R167_R0009</data><data key="edge_source_entity_id">R167_E006</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">WF_A101</data><data key="edge_operational_context">A101 manually effects DOFA decision and records special remarks.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.6. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0010" source="R167_E006" target="APP_MADCAP"><data key="edge_relationship_id">R167_R0010</data><data key="edge_source_entity_id">R167_E006</data><data key="edge_relationship_type">routed_for_manual_processing</data><data key="edge_target_entity_id">APP_MADCAP</data><data key="edge_operational_context">A101 remarks instruct payment center MADCAP processing.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.6. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0011" source="R167_E006" target="R167_E001"><data key="edge_relationship_id">R167_R0011</data><data key="edge_source_entity_id">R167_E006</data><data key="edge_relationship_type">implements</data><data key="edge_target_entity_id">R167_E001</data><data key="edge_operational_context">Special IEDS MCS earnings-computation exclusion is handled through manual A101/MADCAP.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.6. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0012" source="R167_E007" target="R167_E006"><data key="edge_relationship_id">R167_R0012</data><data key="edge_source_entity_id">R167_E007</data><data key="edge_relationship_type">is_exception_after</data><data key="edge_target_entity_id">R167_E006</data><data key="edge_operational_context">Nonfiling number holder death can cause manual conversion from IEDS to surviving divorced spouse payment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.5.f. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0013" source="R167_E008" target="R167_E002"><data key="edge_relationship_id">R167_R0013</data><data key="edge_source_entity_id">R167_E008</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R167_E002</data><data key="edge_operational_context">Number holder SSN, age, or material disability evidence developed for IEDS claim.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.1-B.4. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0014" source="R167_E008" target="R167_E005"><data key="edge_relationship_id">R167_R0014</data><data key="edge_source_entity_id">R167_E008</data><data key="edge_relationship_type">may_rely_on</data><data key="edge_target_entity_id">R167_E005</data><data key="edge_operational_context">NH earnings and certified record needed for insured-status determination.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S001 section B.5. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0015" source="R167_E009" target="SYS_SSR"><data key="edge_relationship_id">R167_R0015</data><data key="edge_source_entity_id">R167_E009</data><data key="edge_relationship_type">posts_or_updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">VA/SSR interface can post qualifying veteran, survivor, and dependent VA benefits to SSR in posteligibility.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0016" source="R167_E009" target="R167_E010"><data key="edge_relationship_id">R167_R0016</data><data key="edge_source_entity_id">R167_E009</data><data key="edge_relationship_type">records_provenance_using</data><data key="edge_target_entity_id">R167_E010</data><data key="edge_operational_context">SSR unearned-income verification codes 2, 3 or 4 signal VA/SSR interface posting.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0017" source="R167_E010" target="SYS_SSR"><data key="edge_relationship_id">R167_R0017</data><data key="edge_source_entity_id">R167_E010</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Verification indicator follows VA claim number in SSR unearned income record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0018" source="R167_E011" target="R167_E009"><data key="edge_relationship_id">R167_R0018</data><data key="edge_source_entity_id">R167_E011</data><data key="edge_relationship_type">governs_processing_of</data><data key="edge_target_entity_id">R167_E009</data><data key="edge_operational_context">Dependent attribution governs VA/SSR interface eligible portions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section C/E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0019" source="R167_E012" target="SYS_SSR"><data key="edge_relationship_id">R167_R0019</data><data key="edge_source_entity_id">R167_E012</data><data key="edge_relationship_type">updates_when_interface_missing</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Field office manually inputs VA income only if VA/SSR interface has not posted requisite payment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E/F. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0020" source="R167_E012" target="R167_E009"><data key="edge_relationship_id">R167_R0020</data><data key="edge_source_entity_id">R167_E012</data><data key="edge_relationship_type">is_exception_to</data><data key="edge_target_entity_id">R167_E009</data><data key="edge_operational_context">Automatic SSA VA/SSR interface posting not guaranteed for all dependent portions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E/F. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0021" source="R167_E012" target="R167_E013"><data key="edge_relationship_id">R167_R0021</data><data key="edge_source_entity_id">R167_E012</data><data key="edge_relationship_type">documents_via</data><data key="edge_target_entity_id">R167_E013</data><data key="edge_operational_context">SSI pending cases use Veterans Affairs Payment page for manual inputs.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section F. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0022" source="R167_E013" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R167_R0022</data><data key="edge_source_entity_id">R167_E013</data><data key="edge_relationship_type">is_interface_of</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Veterans Affairs Payment page in SSI claims system.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section F. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0023" source="R167_E014" target="SYS_SSR"><data key="edge_relationship_id">R167_R0023</data><data key="edge_source_entity_id">R167_E014</data><data key="edge_relationship_type">encoded_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">PCOC D follows claim number for certain manual dependent VA entries.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section F.2/F.3. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0024" source="R167_E015" target="R167_E011"><data key="edge_relationship_id">R167_R0024</data><data key="edge_source_entity_id">R167_E015</data><data key="edge_relationship_type">requests_income_verification_for</data><data key="edge_target_entity_id">R167_E011</data><data key="edge_operational_context">SSA-L1103-U3 verifies applicable VA income for all months under review.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section D/E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0025" source="R167_E016" target="R167_E011"><data key="edge_relationship_id">R167_R0025</data><data key="edge_source_entity_id">R167_E016</data><data key="edge_relationship_type">limits_new_apportionment_under</data><data key="edge_target_entity_id">R167_E011</data><data key="edge_operational_context">VA no longer generally awards new needs-based apportionments after 2026-02-09; narrow exceptions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section B.2. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0026" source="R167_E017" target="SYS_SSR"><data key="edge_relationship_id">R167_R0026</data><data key="edge_source_entity_id">R167_E017</data><data key="edge_relationship_type">excludes_unapportioned_income_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Absent dependent VA portion without direct apportionment should not be recorded as that dependent SSI VA income.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E/F. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0027" source="R167_E017" target="R167_E021"><data key="edge_relationship_id">R167_R0027</data><data key="edge_source_entity_id">R167_E017</data><data key="edge_relationship_type">is_qualified_by</data><data key="edge_target_entity_id">R167_E021</data><data key="edge_operational_context">Residence and VA direct payment determine applicable income attribution.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E/F. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0028" source="R167_E018" target="SYS_SSR"><data key="edge_relationship_id">R167_R0028</data><data key="edge_source_entity_id">R167_E018</data><data key="edge_relationship_type">requires_review_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Resolve SSR VA income interface alerts, diaries and rejects.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0029" source="R167_E018" target="R167_E009"><data key="edge_relationship_id">R167_R0029</data><data key="edge_source_entity_id">R167_E018</data><data key="edge_relationship_type">tracks_exception_of</data><data key="edge_target_entity_id">R167_E009</data><data key="edge_operational_context">VA interface missing post or rejection requires manual investigation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0030" source="R167_E019" target="SYS_SSR"><data key="edge_relationship_id">R167_R0030</data><data key="edge_source_entity_id">R167_E019</data><data key="edge_relationship_type">reviews_record_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Missing January dependent VA COLA prompts verification.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0031" source="R167_E019" target="R167_E015"><data key="edge_relationship_id">R167_R0031</data><data key="edge_source_entity_id">R167_E019</data><data key="edge_relationship_type">may_invoke</data><data key="edge_target_entity_id">R167_E015</data><data key="edge_operational_context">Missing VA COLA information verified using SSA-L1103-U3.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0032" source="R167_E020" target="SYS_SSR"><data key="edge_relationship_id">R167_R0032</data><data key="edge_source_entity_id">R167_E020</data><data key="edge_relationship_type">coded_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Need-based and non-need based VA income posted with separate SSI unearned income types C/E.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section F. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0033" source="R167_E020" target="R167_E014"><data key="edge_relationship_id">R167_R0033</data><data key="edge_source_entity_id">R167_E020</data><data key="edge_relationship_type">may_use</data><data key="edge_target_entity_id">R167_E014</data><data key="edge_operational_context">Dependent SSI VA type C/E entries include PCOC D.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section F.2/F.3. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0034" source="R167_E021" target="R167_E017"><data key="edge_relationship_id">R167_R0034</data><data key="edge_source_entity_id">R167_E021</data><data key="edge_relationship_type">determines</data><data key="edge_target_entity_id">R167_E017</data><data key="edge_operational_context">Absent dependent and direct VA apportionment controls whether SSI counts VA augmented portion.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S003 section E/F. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0035" source="R167_E022" target="APP_TPPS"><data key="edge_relationship_id">R167_R0035</data><data key="edge_source_entity_id">R167_E022</data><data key="edge_relationship_type">issues_through</data><data key="edge_target_entity_id">APP_TPPS</data><data key="edge_operational_context">Field office EAP/IP issued through TPPS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section A. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0036" source="R167_E022" target="PAY_USDC"><data key="edge_relationship_id">R167_R0036</data><data key="edge_source_entity_id">R167_E022</data><data key="edge_relationship_type">uses_payment_instrument</data><data key="edge_target_entity_id">PAY_USDC</data><data key="edge_operational_context">US Debit Card is issuance instrument effective 2026-02-09.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section A. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0037" source="R167_E023" target="ORG_DDS"><data key="edge_relationship_id">R167_R0037</data><data key="edge_source_entity_id">R167_E023</data><data key="edge_relationship_type">may_require_presumptive_development_by</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">For emergency where FO cannot establish PD/PB, DDS may develop presumptive finding.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section B.1.a. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0038" source="R167_E024" target="R167_E023"><data key="edge_relationship_id">R167_R0038</data><data key="edge_source_entity_id">R167_E024</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R167_E023</data><data key="edge_operational_context">Recovery terms follow emergency advance against future SSI payments.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section B.1.d. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0039" source="R167_E025" target="SYS_MBR"><data key="edge_relationship_id">R167_R0039</data><data key="edge_source_entity_id">R167_E025</data><data key="edge_relationship_type">requires_benefit_calculation_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Concurrent Title II/IP allocation considers Title II amount after windfall offset, not raw unadjusted amount.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section B.2.c. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0040" source="R167_E025" target="SYS_SSR"><data key="edge_relationship_id">R167_R0040</data><data key="edge_source_entity_id">R167_E025</data><data key="edge_relationship_type">requires_benefit_calculation_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Concurrent program allocation considers Title XVI eligible amount after windfall offset.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section B.2.c. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0041" source="R167_E026" target="APP_TPPS"><data key="edge_relationship_id">R167_R0041</data><data key="edge_source_entity_id">R167_E026</data><data key="edge_relationship_type">constrains_initial_claim_payment_in</data><data key="edge_target_entity_id">APP_TPPS</data><data key="edge_operational_context">SSI IP cannot be issued for initial claim without valid SSN; use EAP when criteria allow.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section B.2.b. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0042" source="R167_E027" target="R167_E025"><data key="edge_relationship_id">R167_R0042</data><data key="edge_source_entity_id">R167_E027</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R167_E025</data><data key="edge_operational_context">Title XVI IP amounts are recovered from first following regular SSI payment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section B.2.e. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0043" source="R167_E028" target="R167_E025"><data key="edge_relationship_id">R167_R0043</data><data key="edge_source_entity_id">R167_E028</data><data key="edge_relationship_type">caps</data><data key="edge_target_entity_id">R167_E025</data><data key="edge_operational_context">IP limit $2,000 Title XVI only, $5,000 concurrent benefits.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S002 section B.2/C. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0044" source="R167_E029" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R167_R0044</data><data key="edge_source_entity_id">R167_E029</data><data key="edge_relationship_type">published_as_section_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">2026 Annual Statistical Supplement section 5.J1.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S004 section Table 5.J1. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0045" source="R167_E030" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R167_R0045</data><data key="edge_source_entity_id">R167_E030</data><data key="edge_relationship_type">published_as_section_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">2026 Annual Statistical Supplement section 5.J2.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S004 section Table 5.J2. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0046" source="R167_E029" target="SYS_MBR"><data key="edge_relationship_id">R167_R0046</data><data key="edge_source_entity_id">R167_E029</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Statistical 2025 benefit estimates are sourced to 100 percent MBR data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S004 section Table 5.J1. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0047" source="R167_E030" target="SYS_MBR"><data key="edge_relationship_id">R167_R0047</data><data key="edge_source_entity_id">R167_E030</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">December 2025 OASDI beneficiary counts use 100 percent MBR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S004 section Table 5.J2. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0048" source="R167_E031" target="R167_E029"><data key="edge_relationship_id">R167_R0048</data><data key="edge_source_entity_id">R167_E031</data><data key="edge_relationship_type">is_caveat_on</data><data key="edge_target_entity_id">R167_E029</data><data key="edge_operational_context">5.J1 excludes lump-sum death and does not deduct unnegotiated checks.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S004 section Table 5.J1. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0049" source="R167_E032" target="R167_E029"><data key="edge_relationship_id">R167_R0049</data><data key="edge_source_entity_id">R167_E032</data><data key="edge_relationship_type">contributes_provenance_to</data><data key="edge_target_entity_id">R167_E029</data><data key="edge_operational_context">USPS geographic data and MBR source credited for 5.J1 aggregate state tables.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S004 section Table 5.J1. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0050" source="R167_E032" target="ORG_USPS"><data key="edge_relationship_id">R167_R0050</data><data key="edge_source_entity_id">R167_E032</data><data key="edge_relationship_type">uses_geographic_reference_from</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">2026 5.J source credits USPS geographic reference data, without identifying particular USPS ZIP+4 or other file.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S004 section Table 5.J1. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R167_R0051" source="R167_E032" target="SYS_MBR"><data key="edge_relationship_id">R167_R0051</data><data key="edge_source_entity_id">R167_E032</data><data key="edge_relationship_type">uses_master_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Table references MBR 100-percent beneficiary data for state geography, not a direct master-address update.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R167_S004 section Table 5.J1. Verified 2026-10-10; edge describes administrative/published relationship only.</data></edge><edge id="R168_R0001" source="R168_E001" target="R168_E002"><data key="edge_relationship_id">R168_R0001</data><data key="edge_source_entity_id">R168_E001</data><data key="edge_relationship_type">provides_ssn_name_control_updates_for</data><data key="edge_target_entity_id">R168_E002</data><data key="edge_operational_context">IRS internal taxpayer name-control validation</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Transport described historically as tapes, current transport unverified.</data></edge><edge id="R168_R0002" source="R168_E001" target="DB_IRS_NAP_DM1"><data key="edge_relationship_id">R168_R0002</data><data key="edge_source_entity_id">R168_E001</data><data key="edge_relationship_type">received_into_existing_tax_validation_environment</data><data key="edge_target_entity_id">DB_IRS_NAP_DM1</data><data key="edge_operational_context">SSA -&gt; IRS DM-1 matching</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Existing catalog NAP-DM1 name requires reconciliation.</data></edge><edge id="R168_R0003" source="DB_IRS_NAP_DM1" target="R168_E002"><data key="edge_relationship_id">R168_R0003</data><data key="edge_source_entity_id">DB_IRS_NAP_DM1</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R168_E002</data><data key="edge_operational_context">IRS name-control verification</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0004" source="R168_E002" target="R168_E003"><data key="edge_relationship_id">R168_R0004</data><data key="edge_source_entity_id">R168_E002</data><data key="edge_relationship_type">classifies_tax_transactions_into</data><data key="edge_target_entity_id">R168_E003</data><data key="edge_operational_context">IRS IMF processing</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0005" source="R168_E003" target="DB_IRS_IMF"><data key="edge_relationship_id">R168_R0005</data><data key="edge_source_entity_id">R168_E003</data><data key="edge_relationship_type">logical_segment_of</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">IRS account validity</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0006" source="R168_E004" target="DB_IRS_NAP_DM1"><data key="edge_relationship_id">R168_R0006</data><data key="edge_source_entity_id">R168_E004</data><data key="edge_relationship_type">includes_existing_dm1_reference</data><data key="edge_target_entity_id">DB_IRS_NAP_DM1</data><data key="edge_operational_context">IRS taxpayer validation sources</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Existing combined canonical name DB_IRS_NAP_DM1 requires future reconciliation.</data></edge><edge id="R168_R0007" source="R168_E004" target="DB_IRS_IMF"><data key="edge_relationship_id">R168_R0007</data><data key="edge_source_entity_id">R168_E004</data><data key="edge_relationship_type">supplies_taxpayer_entity_information_to</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">IRS IMF taxpayer records</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0008" source="R168_E002" target="R168_E010"><data key="edge_relationship_id">R168_R0008</data><data key="edge_source_entity_id">R168_E002</data><data key="edge_relationship_type">applies_name_control_rules_from</data><data key="edge_target_entity_id">R168_E010</data><data key="edge_operational_context">IRS processing</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0009" source="R168_E010" target="R168_E003"><data key="edge_relationship_id">R168_R0009</data><data key="edge_source_entity_id">R168_E010</data><data key="edge_relationship_type">governs_tin_name_matching_to</data><data key="edge_target_entity_id">R168_E003</data><data key="edge_operational_context">IRS IMF segment selection</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0010" source="R168_E005" target="R168_E006"><data key="edge_relationship_id">R168_R0010</data><data key="edge_source_entity_id">R168_E005</data><data key="edge_relationship_type">enters</data><data key="edge_target_entity_id">R168_E006</data><data key="edge_operational_context">IRS Statement-related address requests</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0011" source="R168_E006" target="R168_E029"><data key="edge_relationship_id">R168_R0011</data><data key="edge_source_entity_id">R168_E006</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R168_E029</data><data key="edge_operational_context">IRS active-account screening</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0012" source="R168_E006" target="DB_IRS_IMF"><data key="edge_relationship_id">R168_R0012</data><data key="edge_source_entity_id">R168_E006</data><data key="edge_relationship_type">may_update_active_account_address_in</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">IRS tax account address update</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">No SSA MBR SSR Numident update asserted.</data></edge><edge id="R168_R0013" source="R168_E005" target="R168_E007"><data key="edge_relationship_id">R168_R0013</data><data key="edge_source_entity_id">R168_E005</data><data key="edge_relationship_type">may_be_archived_in</data><data key="edge_target_entity_id">R168_E007</data><data key="edge_operational_context">IRS entity-case document handling</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0014" source="R168_E030" target="R168_E007"><data key="edge_relationship_id">R168_R0014</data><data key="edge_source_entity_id">R168_E030</data><data key="edge_relationship_type">limits_retention_in</data><data key="edge_target_entity_id">R168_E007</data><data key="edge_operational_context">IRS address request records</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0015" source="R168_E008" target="DB_IRS_IMF"><data key="edge_relationship_id">R168_R0015</data><data key="edge_source_entity_id">R168_E008</data><data key="edge_relationship_type">submits_primary_taxpayer_address_update_to</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">IRS address maintenance</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0016" source="R168_E008" target="R168_E009"><data key="edge_relationship_id">R168_R0016</data><data key="edge_source_entity_id">R168_E008</data><data key="edge_relationship_type">can_invoke</data><data key="edge_target_entity_id">R168_E009</data><data key="edge_operational_context">IRS spouse address handling</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0017" source="R168_E009" target="DB_IRS_IMF"><data key="edge_relationship_id">R168_R0017</data><data key="edge_source_entity_id">R168_E009</data><data key="edge_relationship_type">conditionally_updates_secondary_address_in</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">IRS joint filers only</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0018" source="R168_E006" target="APP_PEBES"><data key="edge_relationship_id">R168_R0018</data><data key="edge_source_entity_id">R168_E006</data><data key="edge_relationship_type">relates_to_statement_address_flow_in</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">Purpose-limited Statement address usage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Context link only, do not equate address update with PEBES database refresh.</data></edge><edge id="R168_R0019" source="R168_E011" target="SYS_SSR"><data key="edge_relationship_id">R168_R0019</data><data key="edge_source_entity_id">R168_E011</data><data key="edge_relationship_type">is_verification_state_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI monthly wages</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0020" source="R168_E011" target="UI_SSI_WAGES_PAGE"><data key="edge_relationship_id">R168_R0020</data><data key="edge_source_entity_id">R168_E011</data><data key="edge_relationship_type">applies_to_wage_entry_in</data><data key="edge_target_entity_id">UI_SSI_WAGES_PAGE</data><data key="edge_operational_context">SSI wage reporting</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0021" source="R168_E012" target="EX_IBIQ"><data key="edge_relationship_id">R168_R0021</data><data key="edge_source_entity_id">R168_E012</data><data key="edge_relationship_type">governs_evidence_from</data><data key="edge_target_entity_id">EX_IBIQ</data><data key="edge_operational_context">State wage query development</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0022" source="R168_E012" target="DB_NDNH"><data key="edge_relationship_id">R168_R0022</data><data key="edge_source_entity_id">R168_E012</data><data key="edge_relationship_type">governs_evidence_from</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">NDNH wage query development</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0023" source="R168_E012" target="EX_SASRO"><data key="edge_relationship_id">R168_R0023</data><data key="edge_source_entity_id">R168_E012</data><data key="edge_relationship_type">governs_evidence_from</data><data key="edge_target_entity_id">EX_SASRO</data><data key="edge_operational_context">State records wage development</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0024" source="R168_E012" target="APP_ITOPSS"><data key="edge_relationship_id">R168_R0024</data><data key="edge_source_entity_id">R168_E012</data><data key="edge_relationship_type">governs_evidence_from</data><data key="edge_target_entity_id">APP_ITOPSS</data><data key="edge_operational_context">Ticket work wage query development</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0025" source="R168_E013" target="APP_EP"><data key="edge_relationship_id">R168_R0025</data><data key="edge_source_entity_id">R168_E013</data><data key="edge_relationship_type">restricts_query_printout_intake_at</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Restricted wage query evidence</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0026" source="R168_E013" target="DB_NDNH"><data key="edge_relationship_id">R168_R0026</data><data key="edge_source_entity_id">R168_E013</data><data key="edge_relationship_type">applies_to_queries_from</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">Restricted OCSE query data</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0027" source="R168_E014" target="SYS_SSR"><data key="edge_relationship_id">R168_R0027</data><data key="edge_source_entity_id">R168_E014</data><data key="edge_relationship_type">computes_monthly_wages_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI resource and income processing</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0028" source="R168_E014" target="SYS_MEF"><data key="edge_relationship_id">R168_R0028</data><data key="edge_source_entity_id">R168_E014</data><data key="edge_relationship_type">may_use_annual_total_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Secondary MEF data source</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0029" source="R168_E015" target="FORM_SSA5002"><data key="edge_relationship_id">R168_R0029</data><data key="edge_source_entity_id">R168_E015</data><data key="edge_relationship_type">documented_using</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">SSI wages evidence development</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0030" source="R168_E015" target="APP_EP"><data key="edge_relationship_id">R168_R0030</data><data key="edge_source_entity_id">R168_E015</data><data key="edge_relationship_type">may_store_corresponding_evidence_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">SSI wages evidence retention</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0031" source="R168_E016" target="APP_SSIMWV"><data key="edge_relationship_id">R168_R0031</data><data key="edge_source_entity_id">R168_E016</data><data key="edge_relationship_type">processed_using</data><data key="edge_target_entity_id">APP_SSIMWV</data><data key="edge_operational_context">SSI wage reporting receipts</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0032" source="R168_E016" target="APP_ORS"><data key="edge_relationship_id">R168_R0032</data><data key="edge_source_entity_id">R168_E016</data><data key="edge_relationship_type">receipt_archived_by</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Electronic receipt archive</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0033" source="R168_E016" target="APP_EP"><data key="edge_relationship_id">R168_R0033</data><data key="edge_source_entity_id">R168_E016</data><data key="edge_relationship_type">alternative_evidence_storage_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Wage evidence collection</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0034" source="SYS_SSR" target="R168_E017"><data key="edge_relationship_id">R168_R0034</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains_recurring_bank_account_attribute</data><data key="edge_target_entity_id">R168_E017</data><data key="edge_operational_context">SSI DRDP recurring deposits</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0035" source="R168_E018" target="R168_E017"><data key="edge_relationship_id">R168_R0035</data><data key="edge_source_entity_id">R168_E018</data><data key="edge_relationship_type">compares_dedicated_account_against</data><data key="edge_target_entity_id">R168_E017</data><data key="edge_operational_context">A-OTP processing</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0036" source="R168_E018" target="PROC_AOTP"><data key="edge_relationship_id">R168_R0036</data><data key="edge_source_entity_id">R168_E018</data><data key="edge_relationship_type">rejects_conflicting_attempt_in</data><data key="edge_target_entity_id">PROC_AOTP</data><data key="edge_operational_context">SSI dedicated underpayments</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0037" source="R168_E020" target="R168_E019"><data key="edge_relationship_id">R168_R0037</data><data key="edge_source_entity_id">R168_E020</data><data key="edge_relationship_type">launches</data><data key="edge_target_entity_id">R168_E019</data><data key="edge_operational_context">Direct SSR Update menu navigation</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0038" source="R168_E019" target="PROC_AOTP"><data key="edge_relationship_id">R168_R0038</data><data key="edge_source_entity_id">R168_E019</data><data key="edge_relationship_type">submits_payment_through</data><data key="edge_target_entity_id">PROC_AOTP</data><data key="edge_operational_context">Dedicated account disbursement</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0039" source="R168_E019" target="R168_E017"><data key="edge_relationship_id">R168_R0039</data><data key="edge_source_entity_id">R168_E019</data><data key="edge_relationship_type">does_not_change_regular_deposit_data_in</data><data key="edge_target_entity_id">R168_E017</data><data key="edge_operational_context">Recurring vs dedicated separation</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0040" source="R168_E021" target="R168_E019"><data key="edge_relationship_id">R168_R0040</data><data key="edge_source_entity_id">R168_E021</data><data key="edge_relationship_type">alerts_office_about_required_separate_payment_in</data><data key="edge_target_entity_id">R168_E019</data><data key="edge_operational_context">SSI work management</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Indirect operational process relation, not software integration.</data></edge><edge id="R168_R0041" source="R168_E022" target="PROC_SSI_IAR_UNDERPAYMENT_HOLD"><data key="edge_relationship_id">R168_R0041</data><data key="edge_source_entity_id">R168_E022</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_SSI_IAR_UNDERPAYMENT_HOLD</data><data key="edge_operational_context">Title XVI underpayment sequence</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0042" source="R168_E022" target="PROC_AOTP"><data key="edge_relationship_id">R168_R0042</data><data key="edge_source_entity_id">R168_E022</data><data key="edge_relationship_type">precedes_dedicated_account_payment_via</data><data key="edge_target_entity_id">PROC_AOTP</data><data key="edge_operational_context">SSI payment scheduling</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0043" source="R168_E023" target="PROC_OACT_MORTALITY_PROJ"><data key="edge_relationship_id">R168_R0043</data><data key="edge_source_entity_id">R168_E023</data><data key="edge_relationship_type">statistical_input_to</data><data key="edge_target_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_operational_context">2026 Trustee mortality assumptions</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0044" source="ORG_NCHS" target="R168_E023"><data key="edge_relationship_id">R168_R0044</data><data key="edge_source_entity_id">ORG_NCHS</data><data key="edge_relationship_type">publishes_statistical_source_used_by</data><data key="edge_target_entity_id">R168_E023</data><data key="edge_operational_context">Mortality data publication</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0045" source="R168_E024" target="PROC_OACT_MORTALITY_PROJ"><data key="edge_relationship_id">R168_R0045</data><data key="edge_source_entity_id">R168_E024</data><data key="edge_relationship_type">statistical_input_to</data><data key="edge_target_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_operational_context">2026 Trustee age-65-plus mortality method</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0046" source="ORG_CMS" target="R168_E024"><data key="edge_relationship_id">R168_R0046</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">is_agency_associated_with</data><data key="edge_target_entity_id">R168_E024</data><data key="edge_operational_context">Medicare program source</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R168_R0047" source="ORG_CENSUS" target="R168_E025"><data key="edge_relationship_id">R168_R0047</data><data key="edge_source_entity_id">ORG_CENSUS</data><data key="edge_relationship_type">publishes_input_represented_by</data><data key="edge_target_entity_id">R168_E025</data><data key="edge_operational_context">Trustees Census population baseline</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0048" source="R168_E025" target="MODEL_OACT_POPULATION"><data key="edge_relationship_id">R168_R0048</data><data key="edge_source_entity_id">R168_E025</data><data key="edge_relationship_type">statistical_input_to</data><data key="edge_target_entity_id">MODEL_OACT_POPULATION</data><data key="edge_operational_context">Actuarial demographic projections</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0049" source="ORG_DHS" target="R168_E026"><data key="edge_relationship_id">R168_R0049</data><data key="edge_source_entity_id">ORG_DHS</data><data key="edge_relationship_type">publishes_data_source_for</data><data key="edge_target_entity_id">R168_E026</data><data key="edge_operational_context">2026 Trustees immigration assumptions</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0050" source="R168_E026" target="PROC_OACT_IMMIGRATION_PROJ"><data key="edge_relationship_id">R168_R0050</data><data key="edge_source_entity_id">R168_E026</data><data key="edge_relationship_type">supports_assumption_revision_for</data><data key="edge_target_entity_id">PROC_OACT_IMMIGRATION_PROJ</data><data key="edge_operational_context">2026 immigration projection</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0051" source="R168_E027" target="PROC_OACT_MORTALITY_PROJ"><data key="edge_relationship_id">R168_R0051</data><data key="edge_source_entity_id">R168_E027</data><data key="edge_relationship_type">governs_historical_series_in</data><data key="edge_target_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_operational_context">2026 mortality regression procedure</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0052" source="R168_E027" target="R168_E023"><data key="edge_relationship_id">R168_R0052</data><data key="edge_source_entity_id">R168_E027</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R168_E023</data><data key="edge_operational_context">NCHS mortality historical regression inputs</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R168_R0053" source="R168_E028" target="MODEL_OACT_LABOR_FORCE"><data key="edge_relationship_id">R168_R0053</data><data key="edge_source_entity_id">R168_E028</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">MODEL_OACT_LABOR_FORCE</data><data key="edge_operational_context">2026 75+ workforce calibration</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R169_R0001" source="ORG_RRB" target="R169_E0001"><data key="edge_relationship_id">R169_R0001</data><data key="edge_source_entity_id">ORG_RRB</data><data key="edge_relationship_type">refers_disability_application</data><data key="edge_target_entity_id">R169_E0001</data><data key="edge_operational_context">RRB sends nonvested railroad worker disability claim to SSA FO when service threshold not met.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0002" source="R169_E0001" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R169_R0002</data><data key="edge_source_entity_id">R169_E0001</data><data key="edge_relationship_type">routed_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">SSA field office handles RRB nonvested disability referral.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0003" source="ORG_RRB" target="R169_E0002"><data key="edge_relationship_id">R169_R0003</data><data key="edge_source_entity_id">ORG_RRB</data><data key="edge_relationship_type">makes_qualifying_joint_freeze_determination</data><data key="edge_target_entity_id">R169_E0002</data><data key="edge_operational_context">RRB produces joint freeze decision when possible RSDI entitlement exists.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0004" source="R169_E0002" target="R169_E0003"><data key="edge_relationship_id">R169_R0004</data><data key="edge_source_entity_id">R169_E0002</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">R169_E0003</data><data key="edge_operational_context">Two decision copies of SSA-831 sent to DCR Branch 2A.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0005" source="R169_E0003" target="ORG_DCR"><data key="edge_relationship_id">R169_R0005</data><data key="edge_source_entity_id">R169_E0003</data><data key="edge_relationship_type">received_by</data><data key="edge_target_entity_id">ORG_DCR</data><data key="edge_operational_context">DCR Branch 2A receives decision copies.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0006" source="R169_E0003" target="APP_PPC"><data key="edge_relationship_id">R169_R0006</data><data key="edge_source_entity_id">R169_E0003</data><data key="edge_relationship_type">one_copy_scanned_into</data><data key="edge_target_entity_id">APP_PPC</data><data key="edge_operational_context">One SSA-831 copy enters DCR PPC paperless system, not an asserted automated source interface.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0007" source="R169_E0003" target="R169_E0004"><data key="edge_relationship_id">R169_R0007</data><data key="edge_source_entity_id">R169_E0003</data><data key="edge_relationship_type">other_copy_used_as</data><data key="edge_target_entity_id">R169_E0004</data><data key="edge_operational_context">Second determination copy used for statistical and coding activities.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0008" source="R169_E0002" target="R169_E0005"><data key="edge_relationship_id">R169_R0008</data><data key="edge_source_entity_id">R169_E0002</data><data key="edge_relationship_type">may_generate_unfiled_claims_lead</data><data key="edge_target_entity_id">R169_E0005</data><data key="edge_operational_context">DCR flags potential DIB entitlement when no DIB claim filed.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0009" source="R169_E0005" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R169_R0009</data><data key="edge_source_entity_id">R169_E0005</data><data key="edge_relationship_type">forwarded_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">Servicing FO contacts number holder and explores new application.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0010" source="R169_E0005" target="R169_E0006"><data key="edge_relationship_id">R169_R0010</data><data key="edge_source_entity_id">R169_E0005</data><data key="edge_relationship_type">triggers_eligibility_screen</data><data key="edge_target_entity_id">R169_E0006</data><data key="edge_operational_context">Referral also instructs FO to screen SSI eligibility.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0011" source="APP_SSI_CLAIMS_LOGICAL" target="R169_E0007"><data key="edge_relationship_id">R169_R0011</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">requires_prequery_identity_statement</data><data key="edge_target_entity_id">R169_E0007</data><data key="edge_operational_context">NHRP request requires own allegations, Privacy Act notice, and open claim event.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0012" source="R169_E0007" target="R169_E0008"><data key="edge_relationship_id">R169_R0012</data><data key="edge_source_entity_id">R169_E0007</data><data key="edge_relationship_type">governs_requests_on</data><data key="edge_target_entity_id">R169_E0008</data><data key="edge_operational_context">Each claimant, recipient or qualified deemor answers own real-property questions before request.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0013" source="APP_CCE" target="R169_E0008"><data key="edge_relationship_id">R169_R0013</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">navigates_to</data><data key="edge_target_entity_id">R169_E0008</data><data key="edge_operational_context">CCE Claims Actions page links to NHRP request selection for the associated SSI claim.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0014" source="APP_NHRP" target="R169_E0008"><data key="edge_relationship_id">R169_R0014</data><data key="edge_source_entity_id">APP_NHRP</data><data key="edge_relationship_type">surfaces_requests_through</data><data key="edge_target_entity_id">R169_E0008</data><data key="edge_operational_context">NHRP electronic search is integrated in SSI Claims system; request response typically seconds.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0015" source="SVC_LEXISNEXIS_ACCURINT" target="R169_E0010"><data key="edge_relationship_id">R169_R0015</data><data key="edge_source_entity_id">SVC_LEXISNEXIS_ACCURINT</data><data key="edge_relationship_type">provides_third_party_leads_to</data><data key="edge_target_entity_id">R169_E0010</data><data key="edge_operational_context">Search result is a third-party report subject to independent review; it is not an authoritative ownership determination.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0016" source="R169_E0008" target="R169_E0010"><data key="edge_relationship_id">R169_R0016</data><data key="edge_source_entity_id">R169_E0008</data><data key="edge_relationship_type">generates_candidate_property_information</data><data key="edge_target_entity_id">R169_E0010</data><data key="edge_operational_context">NHRP result includes action required and pending candidate properties.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0017" source="R169_E0010" target="R169_E0009"><data key="edge_relationship_id">R169_R0017</data><data key="edge_source_entity_id">R169_E0010</data><data key="edge_relationship_type">presented_for_review_on</data><data key="edge_target_entity_id">R169_E0009</data><data key="edge_operational_context">Pending Real Properties candidate is evaluated before acceptance or rejection.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0018" source="R169_E0009" target="R169_E0011"><data key="edge_relationship_id">R169_R0018</data><data key="edge_source_entity_id">R169_E0009</data><data key="edge_relationship_type">requires_disposition_under</data><data key="edge_target_entity_id">R169_E0011</data><data key="edge_operational_context">Add, Update, Reject, or Decide Later based on evidence; unresolved property prevents closeout.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0019" source="R169_E0009" target="R169_E0012"><data key="edge_relationship_id">R169_R0019</data><data key="edge_source_entity_id">R169_E0009</data><data key="edge_relationship_type">exposes_prior_address_comparison</data><data key="edge_target_entity_id">R169_E0012</data><data key="edge_operational_context">Prior rejected property addresses are recognized when address exactly matches for this SSN.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Property address, not current beneficiary mailing/residential address.</data></edge><edge id="R169_R0020" source="R169_E0013" target="R169_E0008"><data key="edge_relationship_id">R169_R0020</data><data key="edge_source_entity_id">R169_E0013</data><data key="edge_relationship_type">requires_search_via</data><data key="edge_target_entity_id">R169_E0008</data><data key="edge_operational_context">Only specified SSI claim/reopening/redetermination events require integrated electronic NHRP search.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0021" source="R169_E0010" target="R169_E0011"><data key="edge_relationship_id">R169_R0021</data><data key="edge_source_entity_id">R169_E0010</data><data key="edge_relationship_type">subject_to_independent_verification</data><data key="edge_target_entity_id">R169_E0011</data><data key="edge_operational_context">Third-party search result must not be used alone to infer resource ownership or value.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R50_007; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0022" source="PROC_ANOMALOUS_WAGE_REVIEW" target="R169_E0014"><data key="edge_relationship_id">R169_R0022</data><data key="edge_source_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="edge_relationship_type">may_hold_without_posting</data><data key="edge_target_entity_id">R169_E0014</data><data key="edge_operational_context">Suspect W-2 data not posted while SSA investigates anomaly.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Unposted pending investigation; no queue implementation specified.</data></edge><edge id="R169_R0023" source="R169_E0014" target="APP_EWR"><data key="edge_relationship_id">R169_R0023</data><data key="edge_source_entity_id">R169_E0014</data><data key="edge_relationship_type">safeguards</data><data key="edge_target_entity_id">APP_EWR</data><data key="edge_operational_context">Wage-report submission processing can be held when accuracy is in doubt.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0024" source="DOC_WAGE_INVESTIGATIVE_NOTICE" target="R169_E0015"><data key="edge_relationship_id">R169_R0024</data><data key="edge_source_entity_id">DOC_WAGE_INVESTIGATIVE_NOTICE</data><data key="edge_relationship_type">controls_initial_response_by</data><data key="edge_target_entity_id">R169_E0015</data><data key="edge_operational_context">First investigative notice identifies WFID, EIN and tax year; first response and extension periods.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0025" source="DATA_WFID" target="R169_E0014"><data key="edge_relationship_id">R169_R0025</data><data key="edge_source_entity_id">DATA_WFID</data><data key="edge_relationship_type">identifies_held_reports_in</data><data key="edge_target_entity_id">R169_E0014</data><data key="edge_operational_context">Investigative notices identify affected submissions by Wage File Identifier.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0026" source="R169_E0015" target="R169_E0016"><data key="edge_relationship_id">R169_R0026</data><data key="edge_source_entity_id">R169_E0015</data><data key="edge_relationship_type">may_escalate_to</data><data key="edge_target_entity_id">R169_E0016</data><data key="edge_operational_context">SSA sends second investigative notice when first corrective response does not resolve anomalies.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0027" source="R169_E0016" target="R169_E0014"><data key="edge_relationship_id">R169_R0027</data><data key="edge_source_entity_id">R169_E0016</data><data key="edge_relationship_type">may_end_in_rejection_of</data><data key="edge_target_entity_id">R169_E0014</data><data key="edge_operational_context">SSA may reject suspect report after unresolved second investigative notice.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0028" source="PROC_ANOMALOUS_WAGE_REVIEW" target="R169_E0017"><data key="edge_relationship_id">R169_R0028</data><data key="edge_source_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="edge_relationship_type">applies_account_affiliation_control</data><data key="edge_target_entity_id">R169_E0017</data><data key="edge_operational_context">Noncompliant submitter suspension may extend to related accounts by filer/EIN/contact.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0029" source="R169_E0017" target="R169_E0020"><data key="edge_relationship_id">R169_R0029</data><data key="edge_source_entity_id">R169_E0017</data><data key="edge_relationship_type">distinguishes_access_impacts_through</data><data key="edge_target_entity_id">R169_E0020</data><data key="edge_operational_context">Suspension of filing and BSO credential deactivation impose different access consequences.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0030" source="PLAT_BSO" target="R169_E0020"><data key="edge_relationship_id">R169_R0030</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">subject_to_submission_and_credential_controls</data><data key="edge_target_entity_id">R169_E0020</data><data key="edge_operational_context">BSO permissions and credential controls described in POMS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0031" source="R169_E0018" target="R169_E0017"><data key="edge_relationship_id">R169_R0031</data><data key="edge_source_entity_id">R169_E0018</data><data key="edge_relationship_type">reviews_suspension_under</data><data key="edge_target_entity_id">R169_E0017</data><data key="edge_operational_context">Wage service access suspension appeal, ten-day submitter and 30-day SSA clocks.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0032" source="PROC_ANOMALOUS_WAGE_REVIEW" target="R169_E0019"><data key="edge_relationship_id">R169_R0032</data><data key="edge_source_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="edge_relationship_type">requires_supporting_document_review</data><data key="edge_target_entity_id">R169_E0019</data><data key="edge_operational_context">SSA validates employer/tax support before processing anomalous wage reports.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0033" source="R169_E0019" target="R169_E0014"><data key="edge_relationship_id">R169_R0033</data><data key="edge_source_entity_id">R169_E0019</data><data key="edge_relationship_type">may_release_held_wage_report</data><data key="edge_target_entity_id">R169_E0014</data><data key="edge_operational_context">Verified legitimate reports can be released from anomalous hold.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0034" source="R169_E0017" target="DATA_SUSPENDED_3P_SUBMITTERS"><data key="edge_relationship_id">R169_R0034</data><data key="edge_source_entity_id">R169_E0017</data><data key="edge_relationship_type">may_affect</data><data key="edge_target_entity_id">DATA_SUSPENDED_3P_SUBMITTERS</data><data key="edge_operational_context">SSA may notify affected parties or publish names of final suspended third-party submitters.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC133; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0035" source="R169_E0021" target="R169_E0022"><data key="edge_relationship_id">R169_R0035</data><data key="edge_source_entity_id">R169_E0021</data><data key="edge_relationship_type">required_before</data><data key="edge_target_entity_id">R169_E0022</data><data key="edge_operational_context">Title II erroneous payment suspension/termination follows notice, response and any reopening conditions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0036" source="R169_E0021" target="R169_E0023"><data key="edge_relationship_id">R169_R0036</data><data key="edge_source_entity_id">R169_E0021</data><data key="edge_relationship_type">required_before</data><data key="edge_target_entity_id">R169_E0023</data><data key="edge_operational_context">SSI adverse correction requires Goldberg Kelly due-process notice and manual exception handling.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0037" source="R169_E0022" target="APP_MDW_AI"><data key="edge_relationship_id">R169_R0037</data><data key="edge_source_entity_id">R169_E0022</data><data key="edge_relationship_type">initiated_with</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">High-priority MDW to PC for Title II S9 to T9 termination or appropriate code.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; MDW is workflow request, does not itself guarantee PC changed the MBR.</data></edge><edge id="R169_R0038" source="R169_E0022" target="SYS_MBR"><data key="edge_relationship_id">R169_R0038</data><data key="edge_source_entity_id">R169_E0022</data><data key="edge_relationship_type">targets_payment_state_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Authorized Title II post-entitlement suspense/termination after correction.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0039" source="R169_E0023" target="SYS_SSR"><data key="edge_relationship_id">R169_R0039</data><data key="edge_source_entity_id">R169_E0023</data><data key="edge_relationship_type">targets_payment_status_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Manual Title XVI SSI record nonpayment status and explanatory special message.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0040" source="PROC_MANUAL_FSTOP" target="R169_E0024"><data key="edge_relationship_id">R169_R0040</data><data key="edge_source_entity_id">PROC_MANUAL_FSTOP</data><data key="edge_relationship_type">may_support</data><data key="edge_target_entity_id">R169_E0024</data><data key="edge_operational_context">SSI wrong-bank-account scenario calls for F-stop and record notes.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0041" source="R169_E0024" target="APP_DMS"><data key="edge_relationship_id">R169_R0041</data><data key="edge_source_entity_id">R169_E0024</data><data key="edge_relationship_type">may_create_debtor_case_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Non-returned wrong-recipient payment may require non-entitled debtor DMS case.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0042" source="R169_E0024" target="APP_NED"><data key="edge_relationship_id">R169_R0042</data><data key="edge_source_entity_id">R169_E0024</data><data key="edge_relationship_type">uses_non_entitled_debtor_function</data><data key="edge_target_entity_id">APP_NED</data><data key="edge_operational_context">DMS NED record for some non-claimant payment recovery circumstances.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0043" source="R169_E0024" target="APP_MDW_AI"><data key="edge_relationship_id">R169_R0043</data><data key="edge_source_entity_id">R169_E0024</data><data key="edge_relationship_type">requires_processing_center_referral</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">Title II priority MDW escalates to PC evaluation of recovery/stop action.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0044" source="R169_E0025" target="APP_DCPS"><data key="edge_relationship_id">R169_R0044</data><data key="edge_source_entity_id">R169_E0025</data><data key="edge_relationship_type">routes_medical_review_through</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Medical CDR goes to DDS if reopening barred; this is business workflow not direct system interface.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0045" source="R169_E0026" target="R169_E0021"><data key="edge_relationship_id">R169_R0045</data><data key="edge_source_entity_id">R169_E0026</data><data key="edge_relationship_type">governs_notice_for</data><data key="edge_target_entity_id">R169_E0021</data><data key="edge_operational_context">Different adverse determination types generally require their own appeal-right explanations.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0046" source="R169_E0021" target="R169_E0024"><data key="edge_relationship_id">R169_R0046</data><data key="edge_source_entity_id">R169_E0021</data><data key="edge_relationship_type">precedes_debt_assessment_if_applicable</data><data key="edge_target_entity_id">R169_E0024</data><data key="edge_operational_context">Error finding, due process, correction and debt evaluation are separate decisions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source R169_S002; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0047" source="REPO_CEF" target="R169_E0027"><data key="edge_relationship_id">R169_R0047</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">must_be_accessible_before</data><data key="edge_target_entity_id">R169_E0027</data><data key="edge_operational_context">Locally imaged paper document verified visible in CEF before local destruction.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC408; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0048" source="R169_E0027" target="APP_DCPS"><data key="edge_relationship_id">R169_R0048</data><data key="edge_source_entity_id">R169_E0027</data><data key="edge_relationship_type">governs_local_document_handling_for</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DDS scan then confirm image before disposal; DCPS is DDS case processing context, not scanning mechanism.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source SRC408; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0049" source="R169_E0028" target="REPO_CEF"><data key="edge_relationship_id">R169_R0049</data><data key="edge_source_entity_id">R169_E0028</data><data key="edge_relationship_type">stores_interpretation_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Original films returned; associated interpretation report scanned into case evidence.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC408; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0050" source="ORG_SSA_FIELD_OFFICES" target="R169_E0029"><data key="edge_relationship_id">R169_R0050</data><data key="edge_source_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_relationship_type">may_fax_critical_case_evidence_using</data><data key="edge_target_entity_id">R169_E0029</data><data key="edge_operational_context">FO direct CEF fax permitted for TERI, QDD, CAL, PD and special critical cases.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC408; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0051" source="R169_E0029" target="REPO_CEF"><data key="edge_relationship_id">R169_R0051</data><data key="edge_source_entity_id">R169_E0029</data><data key="edge_relationship_type">indexes_received_evidence_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Scanned/faxed medical evidence enters claim electronic folder using barcode controls.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC408; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0052" source="R169_E0029" target="APP_EDCS"><data key="edge_relationship_id">R169_R0052</data><data key="edge_source_entity_id">R169_E0029</data><data key="edge_relationship_type">annotates_route_with</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS routing form marked that scanned/faxed documents follow.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC408; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0053" source="PROC_CAP" target="R169_E0030"><data key="edge_relationship_id">R169_R0053</data><data key="edge_source_entity_id">PROC_CAP</data><data key="edge_relationship_type">has_standard_model</data><data key="edge_target_entity_id">R169_E0030</data><data key="edge_operational_context">Standard CAP joint SSI-SNAP intake through SSA for participating jurisdictions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R89_001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0054" source="PROC_CAP" target="R169_E0031"><data key="edge_relationship_id">R169_R0054</data><data key="edge_source_entity_id">PROC_CAP</data><data key="edge_relationship_type">has_modified_model</data><data key="edge_target_entity_id">R169_E0031</data><data key="edge_operational_context">Modified CAP state-led outreach from existing SDX feeds.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R89_001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0055" source="ORG_SSA_FIELD_OFFICES" target="R169_E0030"><data key="edge_relationship_id">R169_R0055</data><data key="edge_source_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_relationship_type">performs_standard_cap_intake</data><data key="edge_target_entity_id">R169_E0030</data><data key="edge_operational_context">SSA service delivery for Standard CAP, not necessarily any automated SNAP eligibility adjudication.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R89_001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0056" source="EX_SDX" target="R169_E0031"><data key="edge_relationship_id">R169_R0056</data><data key="edge_source_entity_id">EX_SDX</data><data key="edge_relationship_type">supports_state_snap_outreach_for</data><data key="edge_target_entity_id">R169_E0031</data><data key="edge_operational_context">Modified CAP partners leverage already supplied SDX SSI data to identify potential SNAP participants.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R89_001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0057" source="R169_E0030" target="R169_E0032"><data key="edge_relationship_id">R169_R0057</data><data key="edge_source_entity_id">R169_E0030</data><data key="edge_relationship_type">subject_to_state_specific_criteria</data><data key="edge_target_entity_id">R169_E0032</data><data key="edge_operational_context">Standard CAP participation and application criteria are state-program-specific.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R89_001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0058" source="R169_E0031" target="R169_E0032"><data key="edge_relationship_id">R169_R0058</data><data key="edge_source_entity_id">R169_E0031</data><data key="edge_relationship_type">subject_to_state_specific_criteria</data><data key="edge_target_entity_id">R169_E0032</data><data key="edge_operational_context">Modified CAP participation and application criteria are state-program-specific.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R89_001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0059" source="ORG_USDA_FNS" target="PROC_CAP"><data key="edge_relationship_id">R169_R0059</data><data key="edge_source_entity_id">ORG_USDA_FNS</data><data key="edge_relationship_type">federal_program_partner_for</data><data key="edge_target_entity_id">PROC_CAP</data><data key="edge_operational_context">SSA, States and FNS CAP partnership described in current POMS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC_R89_001; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0060" source="R169_E0033" target="APP_RASR"><data key="edge_relationship_id">R169_R0060</data><data key="edge_source_entity_id">R169_E0033</data><data key="edge_relationship_type">requires_case_specific_representation_reconciliation_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Consolidated proceedings retain valid appointments across old and new claims; RASR case key limitation requires case-specific handling.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC409; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0061" source="R169_E0033" target="R127_E018"><data key="edge_relationship_id">R169_R0061</data><data key="edge_source_entity_id">R169_E0033</data><data key="edge_relationship_type">requires_claimant_principal_selection</data><data key="edge_target_entity_id">R127_E018</data><data key="edge_operational_context">Principal representative chosen by claimant, most recent temporarily if unreachable.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC409; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0062" source="R169_E0034" target="SVC_E1696"><data key="edge_relationship_id">R169_R0062</data><data key="edge_source_entity_id">R169_E0034</data><data key="edge_relationship_type">applies_to_new_claim_representative_form</data><data key="edge_target_entity_id">SVC_E1696</data><data key="edge_operational_context">A separate SSA-1696 is required for appointment on subsequent claim.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC409; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0063" source="R169_E0034" target="APP_RASR"><data key="edge_relationship_id">R169_R0063</data><data key="edge_source_entity_id">R169_E0034</data><data key="edge_relationship_type">prevents_automatic_rep_import_by</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Prior case representative is not automatically appointed on subsequent application.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC409; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0064" source="R169_E0035" target="APP_RASR"><data key="edge_relationship_id">R169_R0064</data><data key="edge_source_entity_id">R169_E0035</data><data key="edge_relationship_type">controls_invalid_form_processing_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Invalid SSA-1696 not accepted and destroyed per policy; absence of representation not proof of physical form retention.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC409; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R169_R0065" source="R169_E0035" target="SVC_E1696"><data key="edge_relationship_id">R169_R0065</data><data key="edge_source_entity_id">R169_E0035</data><data key="edge_relationship_type">requires_identification_of</data><data key="edge_target_entity_id">SVC_E1696</data><data key="edge_operational_context">Missing party identifiers or signature triggers rejection and permitted notice/disposal process.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source SRC409; Administrative/policy relationship only, not a claim about a particular automated interface.</data></edge><edge id="R170_REL0001" source="R170_E006" target="R170_E001"><data key="edge_relationship_id">R170_REL0001</data><data key="edge_source_entity_id">R170_E006</data><data key="edge_relationship_type">proposed_consolidation_of</data><data key="edge_target_entity_id">R170_E001</data><data key="edge_operational_context">Historical NGTP procurement combined HTS into new unified telephony requirement.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Historical NGTP procurement combined HTS into new unified telephony requirement.</data></edge><edge id="R170_REL0002" source="R170_E006" target="R170_E002"><data key="edge_relationship_id">R170_REL0002</data><data key="edge_source_entity_id">R170_E006</data><data key="edge_relationship_type">proposed_consolidation_of</data><data key="edge_target_entity_id">R170_E002</data><data key="edge_operational_context">Historical NGTP procurement combined TSRP agency field office telephone and fax systems.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Historical NGTP procurement combined TSRP agency field office telephone and fax systems.</data></edge><edge id="R170_REL0003" source="R170_E006" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R170_REL0003</data><data key="edge_source_entity_id">R170_E006</data><data key="edge_relationship_type">proposed_consolidation_of</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">Historical NGTP procurement combined National 800 Number platform into the proposed solution.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Historical NGTP procurement combined National 800 Number platform into the proposed solution.</data></edge><edge id="R170_REL0004" source="R170_E006" target="PLAT_NGTP"><data key="edge_relationship_id">R170_REL0004</data><data key="edge_source_entity_id">R170_E006</data><data key="edge_relationship_type">defined_requirements_for</data><data key="edge_target_entity_id">PLAT_NGTP</data><data key="edge_operational_context">GAO identifies original RFP number, issue date, intended NGTP unified communications features.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">GAO identifies original RFP number, issue date, intended NGTP unified communications features.</data></edge><edge id="R170_REL0005" source="NET_SSANET" target="PLAT_NGTP"><data key="edge_relationship_id">R170_REL0005</data><data key="edge_source_entity_id">NET_SSANET</data><data key="edge_relationship_type">was_planned_network_foundation_for</data><data key="edge_target_entity_id">PLAT_NGTP</data><data key="edge_operational_context">2018 NGTP solicitation described SSANet as government-furnished enterprise network foundation; this is a 2020 sourcing of 2018 design, not a current d</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">2018 NGTP solicitation described SSANet as government-furnished enterprise network foundation; this is a 2020 sourcing of 2018 design, not a current deployment claim.</data></edge><edge id="R170_REL0006" source="R170_E004" target="ORG_VERIZON"><data key="edge_relationship_id">R170_REL0006</data><data key="edge_source_entity_id">R170_E004</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_VERIZON</data><data key="edge_operational_context">Separate 2019 GSA EIS network task order to Verizon, not the NGTP system development award.</data><data key="edge_observed_as_of">2019-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Separate 2019 GSA EIS network task order to Verizon, not the NGTP system development award.</data></edge><edge id="R170_REL0007" source="R170_E005" target="R170_E003"><data key="edge_relationship_id">R170_REL0007</data><data key="edge_source_entity_id">R170_E005</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">R170_E003</data><data key="edge_operational_context">CenturyLink held the second 2019 EIS SSANet network-support task order.</data><data key="edge_observed_as_of">2019-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">CenturyLink held the second 2019 EIS SSANet network-support task order.</data></edge><edge id="R170_REL0008" source="R170_E004" target="NET_SSANET"><data key="edge_relationship_id">R170_REL0008</data><data key="edge_source_entity_id">R170_E004</data><data key="edge_relationship_type">supported</data><data key="edge_target_entity_id">NET_SSANET</data><data key="edge_operational_context">Verizon 2019 enterprise network support task order; historical.</data><data key="edge_observed_as_of">2019-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Verizon 2019 enterprise network support task order; historical.</data></edge><edge id="R170_REL0009" source="R170_E005" target="NET_SSANET"><data key="edge_relationship_id">R170_REL0009</data><data key="edge_source_entity_id">R170_E005</data><data key="edge_relationship_type">supported</data><data key="edge_target_entity_id">NET_SSANET</data><data key="edge_operational_context">CenturyLink 2019 enterprise network support task order; historical.</data><data key="edge_observed_as_of">2019-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">CenturyLink 2019 enterprise network support task order; historical.</data></edge><edge id="R170_REL0010" source="R170_E004" target="VEH_GSA_EIS"><data key="edge_relationship_id">R170_REL0010</data><data key="edge_source_entity_id">R170_E004</data><data key="edge_relationship_type">issued_under</data><data key="edge_target_entity_id">VEH_GSA_EIS</data><data key="edge_operational_context">2019 task order sourced under GSA Enterprise Infrastructure Solutions IDIQ.</data><data key="edge_observed_as_of">2019-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">2019 task order sourced under GSA Enterprise Infrastructure Solutions IDIQ.</data></edge><edge id="R170_REL0011" source="R170_E005" target="VEH_GSA_EIS"><data key="edge_relationship_id">R170_REL0011</data><data key="edge_source_entity_id">R170_E005</data><data key="edge_relationship_type">issued_under</data><data key="edge_target_entity_id">VEH_GSA_EIS</data><data key="edge_operational_context">2019 task order sourced under GSA Enterprise Infrastructure Solutions IDIQ.</data><data key="edge_observed_as_of">2019-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">2019 task order sourced under GSA Enterprise Infrastructure Solutions IDIQ.</data></edge><edge id="R170_REL0012" source="R170_E008" target="R170_E006"><data key="edge_relationship_id">R170_REL0012</data><data key="edge_source_entity_id">R170_E008</data><data key="edge_relationship_type">requirement_in</data><data key="edge_target_entity_id">R170_E006</data><data key="edge_operational_context">Continuous systems engineering and WAN fault advice explicitly required by NGTP solicitation.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Continuous systems engineering and WAN fault advice explicitly required by NGTP solicitation.</data></edge><edge id="R170_REL0013" source="R170_E008" target="NET_SSANET"><data key="edge_relationship_id">R170_REL0013</data><data key="edge_source_entity_id">R170_E008</data><data key="edge_relationship_type">required_assessment_of</data><data key="edge_target_entity_id">NET_SSANET</data><data key="edge_operational_context">NGTP contractor obligated to assess agency-provided WAN network quality in support of NGTP; not evidence of direct operational control.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">NGTP contractor obligated to assess agency-provided WAN network quality in support of NGTP; not evidence of direct operational control.</data></edge><edge id="R170_REL0014" source="R170_E007" target="R170_E004"><data key="edge_relationship_id">R170_REL0014</data><data key="edge_source_entity_id">R170_E007</data><data key="edge_relationship_type">concerned_oversight_of</data><data key="edge_target_entity_id">R170_E004</data><data key="edge_operational_context">GAO found potential impaired objectivity when Verizon NGTP contractor would advise on the SSANet provided under its separate task order.</data><data key="edge_observed_as_of">2020-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">GAO found potential impaired objectivity when Verizon NGTP contractor would advise on the SSANet provided under its separate task order.</data></edge><edge id="R170_REL0015" source="R170_E007" target="CON_NGTP_VERIZON"><data key="edge_relationship_id">R170_REL0015</data><data key="edge_source_entity_id">R170_E007</data><data key="edge_relationship_type">related_to_contract</data><data key="edge_target_entity_id">CON_NGTP_VERIZON</data><data key="edge_operational_context">GAO sustained 2020 award protest on OCI assessment, not on source-code or platform fault.</data><data key="edge_observed_as_of">2020-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">GAO sustained 2020 award protest on OCI assessment, not on source-code or platform fault.</data></edge><edge id="R170_REL0016" source="R170_E009" target="R170_E006"><data key="edge_relationship_id">R170_REL0016</data><data key="edge_source_entity_id">R170_E009</data><data key="edge_relationship_type">evaluated_in</data><data key="edge_target_entity_id">R170_E006</data><data key="edge_operational_context">Section 508 compliance was the first-phase procurement evaluation gate.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Section 508 compliance was the first-phase procurement evaluation gate.</data></edge><edge id="R170_REL0017" source="R170_E010" target="R170_E001"><data key="edge_relationship_id">R170_REL0017</data><data key="edge_source_entity_id">R170_E010</data><data key="edge_relationship_type">documents_legacy_usage_of</data><data key="edge_target_entity_id">R170_E001</data><data key="edge_operational_context">Solicitation cites annual HTS service volume &gt;14 million calls.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Solicitation cites annual HTS service volume &gt;14 million calls.</data></edge><edge id="R170_REL0018" source="R170_E010" target="R170_E002"><data key="edge_relationship_id">R170_REL0018</data><data key="edge_source_entity_id">R170_E010</data><data key="edge_relationship_type">documents_legacy_usage_of</data><data key="edge_target_entity_id">R170_E002</data><data key="edge_operational_context">Solicitation cites TSRP annual &gt;90 million calls and &gt;30 million faxes.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Solicitation cites TSRP annual &gt;90 million calls and &gt;30 million faxes.</data></edge><edge id="R170_REL0019" source="R170_E010" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R170_REL0019</data><data key="edge_source_entity_id">R170_E010</data><data key="edge_relationship_type">documents_legacy_usage_of</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">Solicitation cites N8NN annual &gt;80 million calls.</data><data key="edge_observed_as_of">2018-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Solicitation cites N8NN annual &gt;80 million calls.</data></edge><edge id="R170_REL0020" source="ORG_ATT" target="R170_E007"><data key="edge_relationship_id">R170_REL0020</data><data key="edge_source_entity_id">ORG_ATT</data><data key="edge_relationship_type">filed_protest_related_to</data><data key="edge_target_entity_id">R170_E007</data><data key="edge_operational_context">AT&amp;T 2020 protest resulted in GAO decision sustaining the organizational conflict of interest challenge.</data><data key="edge_observed_as_of">2020-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">AT&amp;T 2020 protest resulted in GAO decision sustaining the organizational conflict of interest challenge.</data></edge><edge id="R170_REL0021" source="R170_E011" target="SVC_DNP"><data key="edge_relationship_id">R170_REL0021</data><data key="edge_source_entity_id">R170_E011</data><data key="edge_relationship_type">supplies_extended_death_coverage_to</data><data key="edge_target_entity_id">SVC_DNP</data><data key="edge_operational_context">Pilot expands DNP access to the full SSA Death Master File including state-supplied reports; pilot boundary and permitted uses apply.</data><data key="edge_observed_as_of">2026-02-12</data><data key="edge_confidence">5</data><data key="edge_notes">Pilot expands DNP access to the full SSA Death Master File including state-supplied reports; pilot boundary and permitted uses apply.</data></edge><edge id="R170_REL0022" source="DATA_DMF" target="R170_E011"><data key="edge_relationship_id">R170_REL0022</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">was_made_available_under</data><data key="edge_target_entity_id">R170_E011</data><data key="edge_operational_context">Three-year Treasury pilot uses full DMF rather than limited public version.</data><data key="edge_observed_as_of">2026-02-12</data><data key="edge_confidence">5</data><data key="edge_notes">Three-year Treasury pilot uses full DMF rather than limited public version.</data></edge><edge id="R170_REL0023" source="R170_E012" target="DATA_DMF"><data key="edge_relationship_id">R170_REL0023</data><data key="edge_source_entity_id">R170_E012</data><data key="edge_relationship_type">governs_acquisition_of</data><data key="edge_target_entity_id">DATA_DMF</data><data key="edge_operational_context">SSA uses state death-record agreements as an input to broader SSA death data holdings; state-provided portion only, not all DMF content.</data><data key="edge_observed_as_of">2026-02-12</data><data key="edge_confidence">4</data><data key="edge_notes">SSA uses state death-record agreements as an input to broader SSA death data holdings; state-provided portion only, not all DMF content.</data></edge><edge id="R170_REL0024" source="R170_E013" target="R170_E012"><data key="edge_relationship_id">R170_REL0024</data><data key="edge_source_entity_id">R170_E013</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R170_E012</data><data key="edge_operational_context">SSA allocates costs for contracted state death records across agencies under cost-sharing obligations.</data><data key="edge_observed_as_of">2026-02-12</data><data key="edge_confidence">5</data><data key="edge_notes">SSA allocates costs for contracted state death records across agencies under cost-sharing obligations.</data></edge><edge id="R170_REL0025" source="R170_E013" target="R170_E011"><data key="edge_relationship_id">R170_REL0025</data><data key="edge_source_entity_id">R170_E013</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R170_E011</data><data key="edge_operational_context">GAO examined how SSA allocates shared state death-record costs when Treasury and other agencies use the full death file.</data><data key="edge_observed_as_of">2026-02-12</data><data key="edge_confidence">4</data><data key="edge_notes">GAO examined how SSA allocates shared state death-record costs when Treasury and other agencies use the full death file.</data></edge><edge id="R170_REL0026" source="R170_E014" target="R170_E011"><data key="edge_relationship_id">R170_REL0026</data><data key="edge_source_entity_id">R170_E014</data><data key="edge_relationship_type">reports_benefits_of</data><data key="edge_target_entity_id">R170_E011</data><data key="edge_operational_context">Treasury first-year 2024 pilot benefit figures, not independently audited SSA benefits.</data><data key="edge_observed_as_of">2026-02-12</data><data key="edge_confidence">5</data><data key="edge_notes">Treasury first-year 2024 pilot benefit figures, not independently audited SSA benefits.</data></edge><edge id="R170_REL0027" source="R170_E015" target="R170_E013"><data key="edge_relationship_id">R170_REL0027</data><data key="edge_source_entity_id">R170_E015</data><data key="edge_relationship_type">recommends_changes_to</data><data key="edge_target_entity_id">R170_E013</data><data key="edge_operational_context">GAO recommended revising SSA multiagency cost allocation using relevant source-data costs.</data><data key="edge_observed_as_of">2026-02-12</data><data key="edge_confidence">5</data><data key="edge_notes">GAO recommended revising SSA multiagency cost allocation using relevant source-data costs.</data></edge><edge id="R170_REL0028" source="R170_E015" target="R170_E012"><data key="edge_relationship_id">R170_REL0028</data><data key="edge_source_entity_id">R170_E015</data><data key="edge_relationship_type">recommends_changes_to</data><data key="edge_target_entity_id">R170_E012</data><data key="edge_operational_context">GAO recommended documenting statute-authorized costs and examining renegotiation of state death data fee schedules.</data><data key="edge_observed_as_of">2026-02-12</data><data key="edge_confidence">5</data><data key="edge_notes">GAO recommended documenting statute-authorized costs and examining renegotiation of state death data fee schedules.</data></edge><edge id="R170_REL0029" source="R170_E016" target="APP_WORKTRACK"><data key="edge_relationship_id">R170_REL0029</data><data key="edge_source_entity_id">R170_E016</data><data key="edge_relationship_type">refers_documents_using</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">DDS faxes new or updated SSA-1696 into WorkTrack for FO processing; manual referral with AR documented.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">DDS faxes new or updated SSA-1696 into WorkTrack for FO processing; manual referral with AR documented.</data></edge><edge id="R170_REL0030" source="R170_E016" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R170_REL0030</data><data key="edge_source_entity_id">R170_E016</data><data key="edge_relationship_type">refers_processing_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">DDS cannot adjudicate representative appointment; FO reviews and processes appointment.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">DDS cannot adjudicate representative appointment; FO reviews and processes appointment.</data></edge><edge id="R170_REL0031" source="R170_E017" target="APP_RASR"><data key="edge_relationship_id">R170_REL0031</data><data key="edge_source_entity_id">R170_E017</data><data key="edge_relationship_type">propagates_authorization_from</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">FO confirms representative appointment in RASR before EDCS propagation.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">FO confirms representative appointment in RASR before EDCS propagation.</data></edge><edge id="R170_REL0032" source="R170_E017" target="APP_EDCS"><data key="edge_relationship_id">R170_REL0032</data><data key="edge_source_entity_id">R170_E017</data><data key="edge_relationship_type">propagates_authorization_into</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">POMS expressly states FO ensures RASR appointment information propagates to EDCS.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">POMS expressly states FO ensures RASR appointment information propagates to EDCS.</data></edge><edge id="R170_REL0033" source="APP_RASR" target="APP_EDCS"><data key="edge_relationship_id">R170_REL0033</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">propagates_appointment_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">POMS DI 31001.001B.1 FO ensures RASR representative appointment information propagates to EDCS.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">POMS DI 31001.001B.1 FO ensures RASR representative appointment information propagates to EDCS.</data></edge><edge id="R170_REL0034" source="APP_EDCS" target="APP_DCPS"><data key="edge_relationship_id">R170_REL0034</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">creates_representation_uat_for</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">EDCS flags produce Update After Transfer to DCPS when representative appointment flags must update.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">EDCS flags produce Update After Transfer to DCPS when representative appointment flags must update.</data></edge><edge id="R170_REL0035" source="R170_E018" target="APP_DCPS"><data key="edge_relationship_id">R170_REL0035</data><data key="edge_source_entity_id">R170_E018</data><data key="edge_relationship_type">prevents_unverified_update_of</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DDS cannot change contact data provided only by representative before independent claimant verification.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">DDS cannot change contact data provided only by representative before independent claimant verification.</data></edge><edge id="R170_REL0036" source="R170_E019" target="APP_DCPS"><data key="edge_relationship_id">R170_REL0036</data><data key="edge_source_entity_id">R170_E019</data><data key="edge_relationship_type">updates_claimant_contact_in</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DDS updates case-development contact after independent claimant verification.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">DDS updates case-development contact after independent claimant verification.</data></edge><edge id="R170_REL0037" source="R170_E019" target="APP_MCS"><data key="edge_relationship_id">R170_REL0037</data><data key="edge_source_entity_id">R170_E019</data><data key="edge_relationship_type">requests_fo_update_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">DDS sends assistance request for FO correction of claimant contact in MCS where relevant.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">DDS sends assistance request for FO correction of claimant contact in MCS where relevant.</data></edge><edge id="R170_REL0038" source="R170_E019" target="APP_MSSICS"><data key="edge_relationship_id">R170_REL0038</data><data key="edge_source_entity_id">R170_E019</data><data key="edge_relationship_type">requests_fo_update_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">DDS sends assistance request for FO correction of claimant contact in MSSICS where relevant.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">DDS sends assistance request for FO correction of claimant contact in MSSICS where relevant.</data></edge><edge id="R170_REL0039" source="R170_E020" target="APP_DCPS"><data key="edge_relationship_id">R170_REL0039</data><data key="edge_source_entity_id">R170_E020</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DDS prepares ROC identifying unappointed caller name, telephone and address; contact data belongs to caller.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">DDS prepares ROC identifying unappointed caller name, telephone and address; contact data belongs to caller.</data></edge><edge id="R170_REL0040" source="R170_E021" target="APP_ARIS"><data key="edge_relationship_id">R170_REL0040</data><data key="edge_source_entity_id">R170_E021</data><data key="edge_relationship_type">can_produce_oig_referral_via</data><data key="edge_target_entity_id">APP_ARIS</data><data key="edge_operational_context">Suspected criminal misconduct or similar fault triggers OIG referral through ARIS if conditions are met.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">Suspected criminal misconduct or similar fault triggers OIG referral through ARIS if conditions are met.</data></edge><edge id="R170_REL0041" source="R170_E022" target="REPO_EF"><data key="edge_relationship_id">R170_REL0041</data><data key="edge_source_entity_id">R170_E022</data><data key="edge_relationship_type">documents_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Signed representative revocation/withdrawal is scanned into section B of electronic case folder; eView can display the record.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">4</data><data key="edge_notes">Signed representative revocation/withdrawal is scanned into section B of electronic case folder; eView can display the record.</data></edge><edge id="R170_REL0042" source="R170_E022" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R170_REL0042</data><data key="edge_source_entity_id">R170_E022</data><data key="edge_relationship_type">requires_field_office_processing_by</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">FO processes withdrawal and removes representation flag where appropriate.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes">FO processes withdrawal and removes representation flag where appropriate.</data></edge><edge id="R170_REL0043" source="R170_E023" target="APP_ELAS"><data key="edge_relationship_id">R170_REL0043</data><data key="edge_source_entity_id">R170_E023</data><data key="edge_relationship_type">requires_review_of</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Review existing lead records by SSN and program before establishing duplicate protective date.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">Review existing lead records by SSN and program before establishing duplicate protective date.</data></edge><edge id="R170_REL0044" source="R170_E023" target="APP_WORKTRACK"><data key="edge_relationship_id">R170_REL0044</data><data key="edge_source_entity_id">R170_E023</data><data key="edge_relationship_type">requires_review_of</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">WorkTrack is among cross-channel sources staff inspect for existing protective writing.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">WorkTrack is among cross-channel sources staff inspect for existing protective writing.</data></edge><edge id="R170_REL0045" source="R170_E023" target="APP_ICLAIM"><data key="edge_relationship_id">R170_REL0045</data><data key="edge_source_entity_id">R170_E023</data><data key="edge_relationship_type">requires_review_of</data><data key="edge_target_entity_id">APP_ICLAIM</data><data key="edge_operational_context">Partial/previous Internet claim records checked before new protective filing.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">Partial/previous Internet claim records checked before new protective filing.</data></edge><edge id="R170_REL0046" source="R170_E023" target="APP_TED"><data key="edge_relationship_id">R170_REL0046</data><data key="edge_source_entity_id">R170_E023</data><data key="edge_relationship_type">requires_review_of</data><data key="edge_target_entity_id">APP_TED</data><data key="edge_operational_context">TED is a work source that staff may inspect for an earlier protective-filing event.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">TED is a work source that staff may inspect for an earlier protective-filing event.</data></edge><edge id="R170_REL0047" source="R170_E024" target="APP_ICLAIM"><data key="edge_relationship_id">R170_REL0047</data><data key="edge_source_entity_id">R170_E024</data><data key="edge_relationship_type">controls_effective_filing_of</data><data key="edge_target_entity_id">APP_ICLAIM</data><data key="edge_operational_context">Earliest unexpired partial iClaim record determines protected filing date under conditional signing/closeout rule.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">Earliest unexpired partial iClaim record determines protected filing date under conditional signing/closeout rule.</data></edge><edge id="R170_REL0048" source="R170_E025" target="APP_ICLAIM"><data key="edge_relationship_id">R170_REL0048</data><data key="edge_source_entity_id">R170_E025</data><data key="edge_relationship_type">lacks_intent_capture_in</data><data key="edge_target_entity_id">APP_ICLAIM</data><data key="edge_operational_context">iClaim does not collect auxiliary filing intent. Employees must develop it separately; no iClaim data-entry capability is inferred.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">4</data><data key="edge_notes">iClaim does not collect auxiliary filing intent. Employees must develop it separately; no iClaim data-entry capability is inferred.</data></edge><edge id="R170_REL0049" source="R170_E026" target="APP_ELAS"><data key="edge_relationship_id">R170_REL0049</data><data key="edge_source_entity_id">R170_E026</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Separate eLAS unscheduled lead per qualifying child or spouse identified with intent.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">Separate eLAS unscheduled lead per qualifying child or spouse identified with intent.</data></edge><edge id="R170_REL0050" source="R170_E027" target="R170_E023"><data key="edge_relationship_id">R170_REL0050</data><data key="edge_source_entity_id">R170_E027</data><data key="edge_relationship_type">temporarily_documents</data><data key="edge_target_entity_id">R170_E023</data><data key="edge_operational_context">SSA-2514 used during scheduling outage; date reentered and paper form then destroyed.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-2514 used during scheduling outage; date reentered and paper form then destroyed.</data></edge><edge id="R170_REL0051" source="R170_E028" target="APP_EP"><data key="edge_relationship_id">R170_REL0051</data><data key="edge_source_entity_id">R170_E028</data><data key="edge_relationship_type">stores_document_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Signed protective writing and mailed DPS closeout notice retained in Evidence Portal.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">Signed protective writing and mailed DPS closeout notice retained in Evidence Portal.</data></edge><edge id="R170_REL0052" source="R170_E028" target="APP_DPS"><data key="edge_relationship_id">R170_REL0052</data><data key="edge_source_entity_id">R170_E028</data><data key="edge_relationship_type">uses_closeout_notices_from</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">DPS generates manual closeout after two failed contact attempts for signed mailed written intent.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">DPS generates manual closeout after two failed contact attempts for signed mailed written intent.</data></edge><edge id="R170_REL0053" source="R170_E029" target="APP_WORKTRACK"><data key="edge_relationship_id">R170_REL0053</data><data key="edge_source_entity_id">R170_E029</data><data key="edge_relationship_type">stored_as_status_in</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">Evidence received before claim is held in WorkTrack with Future Appointment reason.</data><data key="edge_observed_as_of">2026-08-26</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence received before claim is held in WorkTrack with Future Appointment reason.</data></edge><edge id="R170_REL0054" source="R170_E030" target="APP_TED"><data key="edge_relationship_id">R170_REL0054</data><data key="edge_source_entity_id">R170_E030</data><data key="edge_relationship_type">entered_in</data><data key="edge_target_entity_id">APP_TED</data><data key="edge_operational_context">Technicians select completion and exception states during WLM TED wrap-up.</data><data key="edge_observed_as_of">2026-08-26</data><data key="edge_confidence">5</data><data key="edge_notes">Technicians select completion and exception states during WLM TED wrap-up.</data></edge><edge id="R170_REL0055" source="R170_E030" target="APP_WLM"><data key="edge_relationship_id">R170_REL0055</data><data key="edge_source_entity_id">R170_E030</data><data key="edge_relationship_type">describes_queue_outcomes_for</data><data key="edge_target_entity_id">APP_WLM</data><data key="edge_operational_context">Documented WLM completed, canceled, no-show, unresolved-incomplete and pending-requeued categories.</data><data key="edge_observed_as_of">2026-08-26</data><data key="edge_confidence">5</data><data key="edge_notes">Documented WLM completed, canceled, no-show, unresolved-incomplete and pending-requeued categories.</data></edge><edge id="R170_REL0056" source="R170_E031" target="APP_WLM"><data key="edge_relationship_id">R170_REL0056</data><data key="edge_source_entity_id">R170_E031</data><data key="edge_relationship_type">available_during</data><data key="edge_target_entity_id">APP_WLM</data><data key="edge_operational_context">WLM field-office limited rollout accepts nonoriginal proof via video with employee review.</data><data key="edge_observed_as_of">2026-08-26</data><data key="edge_confidence">5</data><data key="edge_notes">WLM field-office limited rollout accepts nonoriginal proof via video with employee review.</data></edge><edge id="R170_REL0057" source="R170_E032" target="APP_WLM"><data key="edge_relationship_id">R170_REL0057</data><data key="edge_source_entity_id">R170_E032</data><data key="edge_relationship_type">limits_rerouting_in</data><data key="edge_target_entity_id">APP_WLM</data><data key="edge_operational_context">Geographic area alone cannot justify return-to-queue under Keep What You Take limited rollout.</data><data key="edge_observed_as_of">2026-08-26</data><data key="edge_confidence">5</data><data key="edge_notes">Geographic area alone cannot justify return-to-queue under Keep What You Take limited rollout.</data></edge><edge id="R170_REL0058" source="R170_E032" target="PROC_KEEP_WHAT_YOU_TAKE"><data key="edge_relationship_id">R170_REL0058</data><data key="edge_source_entity_id">R170_E032</data><data key="edge_relationship_type">implements</data><data key="edge_target_entity_id">PROC_KEEP_WHAT_YOU_TAKE</data><data key="edge_operational_context">Workload return restrictions enforce cross-jurisdiction claim ownership under limited rollout.</data><data key="edge_observed_as_of">2026-08-26</data><data key="edge_confidence">5</data><data key="edge_notes">Workload return restrictions enforce cross-jurisdiction claim ownership under limited rollout.</data></edge><edge id="R170_REL0059" source="R170_E033" target="ORG_SSA_OAG"><data key="edge_relationship_id">R170_REL0059</data><data key="edge_source_entity_id">R170_E033</data><data key="edge_relationship_type">published_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">SSA small-business utilization office publishes public procurement category targets; oversight organizational relationship only.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">SSA small-business utilization office publishes public procurement category targets; oversight organizational relationship only.</data></edge><edge id="R171_REL0001" source="R171_E001" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0001</data><data key="edge_source_entity_id">R171_E001</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0002" source="R171_E001" target="SYS_MBR"><data key="edge_relationship_id">R171_REL0002</data><data key="edge_source_entity_id">R171_E001</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Table expressly cites Master Beneficiary Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Master Beneficiary Record, 100 percent data.</data></edge><edge id="R171_REL0003" source="R171_E002" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0003</data><data key="edge_source_entity_id">R171_E002</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0004" source="R171_E002" target="SYS_MBR"><data key="edge_relationship_id">R171_REL0004</data><data key="edge_source_entity_id">R171_E002</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Table expressly cites Master Beneficiary Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Master Beneficiary Record, 100 percent data.</data></edge><edge id="R171_REL0005" source="R171_E003" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0005</data><data key="edge_source_entity_id">R171_E003</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0006" source="R171_E003" target="SYS_MBR"><data key="edge_relationship_id">R171_REL0006</data><data key="edge_source_entity_id">R171_E003</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Table expressly cites Master Beneficiary Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Master Beneficiary Record, 100 percent data.</data></edge><edge id="R171_REL0007" source="R171_E004" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0007</data><data key="edge_source_entity_id">R171_E004</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0008" source="R171_E004" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0008</data><data key="edge_source_entity_id">R171_E004</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Table expressly cites Supplemental Security Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Supplemental Security Record, 100 percent data.</data></edge><edge id="R171_REL0009" source="R171_E005" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0009</data><data key="edge_source_entity_id">R171_E005</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0010" source="R171_E005" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0010</data><data key="edge_source_entity_id">R171_E005</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Table expressly cites Supplemental Security Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Supplemental Security Record, 100 percent data.</data></edge><edge id="R171_REL0011" source="R171_E006" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0011</data><data key="edge_source_entity_id">R171_E006</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0012" source="R171_E006" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0012</data><data key="edge_source_entity_id">R171_E006</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Table expressly cites Supplemental Security Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Supplemental Security Record, 100 percent data.</data></edge><edge id="R171_REL0013" source="R171_E007" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0013</data><data key="edge_source_entity_id">R171_E007</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0014" source="R171_E007" target="SYS_MBR"><data key="edge_relationship_id">R171_REL0014</data><data key="edge_source_entity_id">R171_E007</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Table expressly cites Master Beneficiary Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Master Beneficiary Record, 100 percent data.</data></edge><edge id="R171_REL0015" source="R171_E007" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0015</data><data key="edge_source_entity_id">R171_E007</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Table expressly cites Supplemental Security Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Supplemental Security Record, 100 percent data.</data></edge><edge id="R171_REL0016" source="R171_E007" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0016</data><data key="edge_source_entity_id">R171_E007</data><data key="edge_relationship_type">includes_cross_program_unduplicated_counts</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Publication combines published OASDI and SSI beneficiary categories and removes overlaps; not proof of shared physical person repository.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Publication combines published OASDI and SSI beneficiary categories and removes overlaps; not proof of shared physical person repository.</data></edge><edge id="R171_REL0017" source="R171_E008" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0017</data><data key="edge_source_entity_id">R171_E008</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0018" source="R171_E008" target="SYS_MBR"><data key="edge_relationship_id">R171_REL0018</data><data key="edge_source_entity_id">R171_E008</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Table expressly cites Master Beneficiary Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Master Beneficiary Record, 100 percent data.</data></edge><edge id="R171_REL0019" source="R171_E008" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0019</data><data key="edge_source_entity_id">R171_E008</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Table expressly cites Supplemental Security Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Supplemental Security Record, 100 percent data.</data></edge><edge id="R171_REL0020" source="R171_E008" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0020</data><data key="edge_source_entity_id">R171_E008</data><data key="edge_relationship_type">includes_cross_program_unduplicated_counts</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Publication combines published OASDI and SSI beneficiary categories and removes overlaps; not proof of shared physical person repository.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Publication combines published OASDI and SSI beneficiary categories and removes overlaps; not proof of shared physical person repository.</data></edge><edge id="R171_REL0021" source="R171_E009" target="REPORT_FAST_FACTS_2026"><data key="edge_relationship_id">R171_REL0021</data><data key="edge_source_entity_id">R171_E009</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_operational_context">Official October 2026 Fast Facts publication includes named dataset/table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official October 2026 Fast Facts publication includes named dataset/table.</data></edge><edge id="R171_REL0022" source="R171_E009" target="SYS_MBR"><data key="edge_relationship_id">R171_REL0022</data><data key="edge_source_entity_id">R171_E009</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Table expressly cites Master Beneficiary Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Master Beneficiary Record, 100 percent data.</data></edge><edge id="R171_REL0023" source="R171_E009" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0023</data><data key="edge_source_entity_id">R171_E009</data><data key="edge_relationship_type">reports_statistics_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Table expressly cites Supplemental Security Record, 100 percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table expressly cites Supplemental Security Record, 100 percent data.</data></edge><edge id="R171_REL0024" source="R171_E009" target="SYS_SSR"><data key="edge_relationship_id">R171_REL0024</data><data key="edge_source_entity_id">R171_E009</data><data key="edge_relationship_type">includes_cross_program_unduplicated_counts</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Publication combines published OASDI and SSI beneficiary categories and removes overlaps; not proof of shared physical person repository.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Publication combines published OASDI and SSI beneficiary categories and removes overlaps; not proof of shared physical person repository.</data></edge><edge id="R171_REL0025" source="R171_E011" target="R171_E014"><data key="edge_relationship_id">R171_REL0025</data><data key="edge_source_entity_id">R171_E011</data><data key="edge_relationship_type">sourced_from</data><data key="edge_target_entity_id">R171_E014</data><data key="edge_operational_context">Office-of-public-service database supplies 2016 agency office counts.</data><data key="edge_observed_as_of">2017</data><data key="edge_confidence">5</data><data key="edge_notes">Office-of-public-service database supplies 2016 agency office counts.</data></edge><edge id="R171_REL0026" source="R171_E011" target="R171_E015"><data key="edge_relationship_id">R171_REL0026</data><data key="edge_source_entity_id">R171_E011</data><data key="edge_relationship_type">sourced_from</data><data key="edge_target_entity_id">R171_E015</data><data key="edge_operational_context">ODAR Case Control System supplies historical hearings office organizational data.</data><data key="edge_observed_as_of">2017</data><data key="edge_confidence">5</data><data key="edge_notes">ODAR Case Control System supplies historical hearings office organizational data.</data></edge><edge id="R171_REL0027" source="R171_E012" target="R171_E016"><data key="edge_relationship_id">R171_REL0027</data><data key="edge_source_entity_id">R171_E012</data><data key="edge_relationship_type">sourced_from</data><data key="edge_target_entity_id">R171_E016</data><data key="edge_operational_context">HR Management Information System supplies Sept 2016 employee groupings.</data><data key="edge_observed_as_of">2017</data><data key="edge_confidence">5</data><data key="edge_notes">HR Management Information System supplies Sept 2016 employee groupings.</data></edge><edge id="R171_REL0028" source="R171_E013" target="R171_E017"><data key="edge_relationship_id">R171_REL0028</data><data key="edge_source_entity_id">R171_E013</data><data key="edge_relationship_type">sourced_from</data><data key="edge_target_entity_id">R171_E017</data><data key="edge_operational_context">SSA Payroll Reports supply work-year series.</data><data key="edge_observed_as_of">2017</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Payroll Reports supply work-year series.</data></edge><edge id="R171_REL0029" source="R171_E011" target="R171_E010"><data key="edge_relationship_id">R171_REL0029</data><data key="edge_source_entity_id">R171_E011</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">R171_E010</data><data key="edge_operational_context">SSA Annual Statistical Supplement 2017 Table 2.F published historic reporting.</data><data key="edge_observed_as_of">2017</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Annual Statistical Supplement 2017 Table 2.F published historic reporting.</data></edge><edge id="R171_REL0030" source="R171_E012" target="R171_E010"><data key="edge_relationship_id">R171_REL0030</data><data key="edge_source_entity_id">R171_E012</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">R171_E010</data><data key="edge_operational_context">SSA Annual Statistical Supplement 2017 Table 2.F published historic reporting.</data><data key="edge_observed_as_of">2017</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Annual Statistical Supplement 2017 Table 2.F published historic reporting.</data></edge><edge id="R171_REL0031" source="R171_E013" target="R171_E010"><data key="edge_relationship_id">R171_REL0031</data><data key="edge_source_entity_id">R171_E013</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">R171_E010</data><data key="edge_operational_context">SSA Annual Statistical Supplement 2017 Table 2.F published historic reporting.</data><data key="edge_observed_as_of">2017</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Annual Statistical Supplement 2017 Table 2.F published historic reporting.</data></edge><edge id="R171_REL0032" source="R171_E018" target="R171_E019"><data key="edge_relationship_id">R171_REL0032</data><data key="edge_source_entity_id">R171_E018</data><data key="edge_relationship_type">derived_in_research_project</data><data key="edge_target_entity_id">R171_E019</data><data key="edge_operational_context">Official SSA public-use catalog attributes office listing compilation to named DRC research project.</data><data key="edge_observed_as_of">2017-06</data><data key="edge_confidence">5</data><data key="edge_notes">Official SSA public-use catalog attributes office listing compilation to named DRC research project.</data></edge><edge id="R171_REL0033" source="R171_E018" target="R171_E011"><data key="edge_relationship_id">R171_REL0033</data><data key="edge_source_entity_id">R171_E018</data><data key="edge_relationship_type">historical_geographic_companion_to</data><data key="edge_target_entity_id">R171_E011</data><data key="edge_operational_context">2016 office listing and 2016 office-count table cover historical agency footprint; the official sources do not establish exact identical underlying source or one-to-one reconciliation.</data><data key="edge_observed_as_of">2017-06</data><data key="edge_confidence">4</data><data key="edge_notes">Conceptual comparison only, not asserted automated pipeline.</data></edge><edge id="R172_REL0001" source="EX_HRS_LINKAGE" target="R172_E001"><data key="edge_relationship_id">R172_REL0001</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R172_E001</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">HRS respondent consent/matching arrangement subject to stated prospective permission and data-refresh rules.</data></edge><edge id="R172_REL0002" source="EX_HRS_LINKAGE" target="R172_E002"><data key="edge_relationship_id">R172_REL0002</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R172_E002</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">HRS respondent consent/matching arrangement subject to stated prospective permission and data-refresh rules.</data></edge><edge id="R172_REL0003" source="EX_HRS_LINKAGE" target="R172_E003"><data key="edge_relationship_id">R172_REL0003</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R172_E003</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">HRS respondent consent/matching arrangement subject to stated prospective permission and data-refresh rules.</data></edge><edge id="R172_REL0004" source="EX_HRS_LINKAGE" target="R172_E004"><data key="edge_relationship_id">R172_REL0004</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">historically_changed_by</data><data key="edge_target_entity_id">R172_E004</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">HRS respondent consent/matching arrangement subject to stated prospective permission and data-refresh rules.</data></edge><edge id="R172_REL0005" source="DATA_HRS_CYBF" target="R172_E002"><data key="edge_relationship_id">R172_REL0005</data><data key="edge_source_entity_id">DATA_HRS_CYBF</data><data key="edge_relationship_type">subject_to_consented_future_update_window</data><data key="edge_target_entity_id">R172_E002</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Benefits product receives administrative updates only under valid prospective permission.</data></edge><edge id="R172_REL0006" source="DATA_HRS_CYBF" target="R172_E003"><data key="edge_relationship_id">R172_REL0006</data><data key="edge_source_entity_id">DATA_HRS_CYBF</data><data key="edge_relationship_type">uses_prior_observation_if_no_new_consent</data><data key="edge_target_entity_id">R172_E003</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Published historical records can persist in derived research product when recent permission/data are unavailable.</data></edge><edge id="R172_REL0007" source="DATA_HRS_SER" target="R172_E001"><data key="edge_relationship_id">R172_REL0007</data><data key="edge_source_entity_id">DATA_HRS_SER</data><data key="edge_relationship_type">limited_by_consent_window</data><data key="edge_target_entity_id">R172_E001</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">HRS earnings release follows the earnings prospective permission range. Research product coverage years are not consent duration.</data></edge><edge id="R172_REL0008" source="R172_E005" target="R172_E006"><data key="edge_relationship_id">R172_REL0008</data><data key="edge_source_entity_id">R172_E005</data><data key="edge_relationship_type">available_as_csv</data><data key="edge_target_entity_id">R172_E006</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official SSA dataset description specifically identifies R172_E006 and its role.</data></edge><edge id="R172_REL0009" source="R172_E005" target="R172_E007"><data key="edge_relationship_id">R172_REL0009</data><data key="edge_source_entity_id">R172_E005</data><data key="edge_relationship_type">available_as_xlsx</data><data key="edge_target_entity_id">R172_E007</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official SSA dataset description specifically identifies R172_E007 and its role.</data></edge><edge id="R172_REL0010" source="R172_E005" target="R172_E008"><data key="edge_relationship_id">R172_REL0010</data><data key="edge_source_entity_id">R172_E005</data><data key="edge_relationship_type">uses_receiving_office_geography</data><data key="edge_target_entity_id">R172_E008</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official SSA dataset description specifically identifies R172_E008 and its role.</data></edge><edge id="R172_REL0011" source="R172_E005" target="R172_E009"><data key="edge_relationship_id">R172_REL0011</data><data key="edge_source_entity_id">R172_E005</data><data key="edge_relationship_type">follows_overlap_counting_rule</data><data key="edge_target_entity_id">R172_E009</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official SSA dataset description specifically identifies R172_E009 and its role.</data></edge><edge id="R172_REL0012" source="R172_E005" target="R172_E010"><data key="edge_relationship_id">R172_REL0012</data><data key="edge_source_entity_id">R172_E005</data><data key="edge_relationship_type">computes_percentage_using</data><data key="edge_target_entity_id">R172_E010</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official SSA dataset description specifically identifies R172_E010 and its role.</data></edge><edge id="R172_REL0013" source="APP_QDD_MODEL" target="R172_E005"><data key="edge_relationship_id">R172_REL0013</data><data key="edge_source_entity_id">APP_QDD_MODEL</data><data key="edge_relationship_type">contributes_flagged_cases_to</data><data key="edge_target_entity_id">R172_E005</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">QDD model identifies cases for fast-track reporting; publicly published statistics are aggregate not model-level outputs.</data></edge><edge id="R172_REL0014" source="APP_CAL_SELECTION" target="R172_E005"><data key="edge_relationship_id">R172_REL0014</data><data key="edge_source_entity_id">APP_CAL_SELECTION</data><data key="edge_relationship_type">contributes_flagged_cases_to</data><data key="edge_target_entity_id">R172_E005</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">CAL process identifies fast-track cases, with overlap counted only once when both CAL and QDD.</data></edge><edge id="R172_REL0015" source="ORG_DDS" target="R172_E005"><data key="edge_relationship_id">R172_REL0015</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">is_receiving_adjudicative_component_in</data><data key="edge_target_entity_id">R172_E005</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Dataset includes DDS, Extended Service Teams, and federal DDS-like sites; DDS location must not be confused with claimant residence.</data></edge><edge id="R172_REL0016" source="DB_SCDD" target="R172_E011"><data key="edge_relationship_id">R172_REL0016</data><data key="edge_source_entity_id">DB_SCDD</data><data key="edge_relationship_type">provides_aggregate_language_reporting_data_to</data><data key="edge_target_entity_id">R172_E011</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA explicitly identifies SCDD as the source of LEP reporting statistics.</data></edge><edge id="R172_REL0017" source="R172_E011" target="R172_E012"><data key="edge_relationship_id">R172_REL0017</data><data key="edge_source_entity_id">R172_E011</data><data key="edge_relationship_type">distributed_as</data><data key="edge_target_entity_id">R172_E012</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Published distribution is named Yrly.csv.</data></edge><edge id="R172_REL0018" source="R172_E011" target="R172_E013"><data key="edge_relationship_id">R172_REL0018</data><data key="edge_source_entity_id">R172_E011</data><data key="edge_relationship_type">has_documentation_conflict</data><data key="edge_target_entity_id">R172_E013</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Title/filename annual while paragraph says quarterly; metadata disputed and preserved.</data></edge><edge id="R172_REL0019" source="DB_SUMS_CLIENT_TABLES" target="R172_E011"><data key="edge_relationship_id">R172_REL0019</data><data key="edge_source_entity_id">DB_SUMS_CLIENT_TABLES</data><data key="edge_relationship_type">underpins_language_demographics_for</data><data key="edge_target_entity_id">R172_E011</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SCDD joins SUMS workload data with ICDB-origin demographic attributes housed in SUMS Client Tables; no direct technical API inferred.</data></edge><edge id="R172_REL0020" source="ORG_CENSUS" target="R172_E014"><data key="edge_relationship_id">R172_REL0020</data><data key="edge_source_entity_id">ORG_CENSUS</data><data key="edge_relationship_type">supplies_population_estimates_to</data><data key="edge_target_entity_id">R172_E014</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Census state age-specific estimated populations provide resident population denominator.</data></edge><edge id="R172_REL0021" source="R172_E014" target="DATA_SSA_DISABILITY_CLAIM_DATA"><data key="edge_relationship_id">R172_REL0021</data><data key="edge_source_entity_id">R172_E014</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DATA_SSA_DISABILITY_CLAIM_DATA</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Census population estimates are combined with disability claim activity in the published composite.</data></edge><edge id="R172_REL0022" source="R172_E015" target="DATA_SSA_DISABILITY_CLAIM_DATA"><data key="edge_relationship_id">R172_REL0022</data><data key="edge_source_entity_id">R172_E015</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DATA_SSA_DISABILITY_CLAIM_DATA</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Published SSA SSI and SSDI program recipient counts supply end-of-calendar-year numerator/eligibility measures.</data></edge><edge id="R172_REL0023" source="DB_DIODS" target="DATA_SSA_DISABILITY_CLAIM_DATA"><data key="edge_relationship_id">R172_REL0023</data><data key="edge_source_entity_id">DB_DIODS</data><data key="edge_relationship_type">supplies_state_adjudication_workload_to</data><data key="edge_target_entity_id">DATA_SSA_DISABILITY_CLAIM_DATA</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">DIODS receipts/determinations are the definitive operational workload origin in composite FY product.</data></edge><edge id="R172_REL0024" source="DATA_SSA_DISABILITY_CLAIM_DATA" target="R172_E016"><data key="edge_relationship_id">R172_REL0024</data><data key="edge_source_entity_id">DATA_SSA_DISABILITY_CLAIM_DATA</data><data key="edge_relationship_type">subject_to_two_stage_publication_refresh</data><data key="edge_target_entity_id">R172_E016</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Annual workload and later demographic/beneficiary refresh follow separate observed schedules.</data></edge><edge id="R172_REL0025" source="DATA_SSA_DISABILITY_CLAIM_DATA" target="R172_E017"><data key="edge_relationship_id">R172_REL0025</data><data key="edge_source_entity_id">DATA_SSA_DISABILITY_CLAIM_DATA</data><data key="edge_relationship_type">requires_geographic_warning</data><data key="edge_target_entity_id">R172_E017</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">DDS adjudicating state cannot be assumed to be the beneficiary residence state.</data></edge><edge id="R172_REL0026" source="DATA_SSA_DISABILITY_CLAIM_DATA" target="R172_E018"><data key="edge_relationship_id">R172_REL0026</data><data key="edge_source_entity_id">DATA_SSA_DISABILITY_CLAIM_DATA</data><data key="edge_relationship_type">applies_person_deduplication_rule</data><data key="edge_target_entity_id">R172_E018</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Person-level total avoids double-counting concurrent SSDI and SSI beneficiary figures.</data></edge><edge id="R172_REL0027" source="R172_E015" target="R172_E018"><data key="edge_relationship_id">R172_REL0027</data><data key="edge_source_entity_id">R172_E015</data><data key="edge_relationship_type">applies_concurrent_beneficiary_adjustment</data><data key="edge_target_entity_id">R172_E018</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Published beneficiary source counts are adjusted to make adult population figures unduplicated.</data></edge><edge id="R172_REL0028" source="PROC_SSI_RZ_ADDRESS_DEVELOPMENT" target="R172_E019"><data key="edge_relationship_id">R172_REL0028</data><data key="edge_source_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="edge_relationship_type">uses_conditional_ssr_comparison</data><data key="edge_target_entity_id">R172_E019</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Employees compare allegation with recorded SSR address and investigate unreported change or temporary absence when needed.</data></edge><edge id="R172_REL0029" source="SYS_SSR" target="R172_E019"><data key="edge_relationship_id">R172_REL0029</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_recorded_address_for</data><data key="edge_target_entity_id">R172_E019</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSR is consulted for whether current alleged residence address is already recorded.</data></edge><edge id="R172_REL0030" source="R172_E020" target="R172_E021"><data key="edge_relationship_id">R172_REL0030</data><data key="edge_source_entity_id">R172_E020</data><data key="edge_relationship_type">historically_includes</data><data key="edge_target_entity_id">R172_E021</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2015-01-01</data><data key="edge_confidence">4</data><data key="edge_notes">Archived NCHS documentation explicitly lists a MEF-derived QOC research extract.</data></edge><edge id="R172_REL0031" source="SYS_MBR" target="R172_E020"><data key="edge_relationship_id">R172_REL0031</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">was_documented_input_to</data><data key="edge_target_entity_id">R172_E020</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2015-01-01</data><data key="edge_confidence">4</data><data key="edge_notes">Archived NCHS record states linked historical SSA administrative data from this source; current exchange unverified.</data></edge><edge id="R172_REL0032" source="SYS_SSR" target="R172_E020"><data key="edge_relationship_id">R172_REL0032</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">was_documented_input_to</data><data key="edge_target_entity_id">R172_E020</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2015-01-01</data><data key="edge_confidence">4</data><data key="edge_notes">Archived NCHS record states linked historical SSA administrative data from this source; current exchange unverified.</data></edge><edge id="R172_REL0033" source="DB_PHUS" target="R172_E020"><data key="edge_relationship_id">R172_REL0033</data><data key="edge_source_entity_id">DB_PHUS</data><data key="edge_relationship_type">was_documented_input_to</data><data key="edge_target_entity_id">R172_E020</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2015-01-01</data><data key="edge_confidence">4</data><data key="edge_notes">Archived NCHS record states linked historical SSA administrative data from this source; current exchange unverified.</data></edge><edge id="R172_REL0034" source="SYS_MEF" target="R172_E021"><data key="edge_relationship_id">R172_REL0034</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">was_historical_source_for</data><data key="edge_target_entity_id">R172_E021</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2015-01-01</data><data key="edge_confidence">4</data><data key="edge_notes">Archival NCHS documented summarized quarters-of-coverage extract from MEF; current availability unconfirmed.</data></edge><edge id="R172_REL0035" source="R172_E020" target="R172_E022"><data key="edge_relationship_id">R172_REL0035</data><data key="edge_source_entity_id">R172_E020</data><data key="edge_relationship_type">historical_restricted_use_subject_to</data><data key="edge_target_entity_id">R172_E022</data><data key="edge_operational_context">documented_workflow</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">3</data><data key="edge_notes">Historical NCHS files had access controls; NCHS currently operates RDC for restricted linked data generally. Do not infer current specific file availability.</data></edge><edge id="R173_REL0001" source="ORG_DDS" target="R173_E001"><data key="edge_relationship_id">R173_REL0001</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">may_use_qualified_medical_decision_authority</data><data key="edge_target_entity_id">R173_E001</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Requires verified qualified disability examiners and documented MC recruitment efforts; not an unrestricted DDS power.</data></edge><edge id="R173_REL0002" source="R173_E001" target="R173_E002"><data key="edge_relationship_id">R173_REL0002</data><data key="edge_source_entity_id">R173_E001</data><data key="edge_relationship_type">applies_conditionally_to</data><data key="edge_target_entity_id">R173_E002</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Initial physical-only fully favorable adult onset/POD condition.</data></edge><edge id="R173_REL0003" source="R173_E001" target="R173_E003"><data key="edge_relationship_id">R173_REL0003</data><data key="edge_source_entity_id">R173_E001</data><data key="edge_relationship_type">requires_site_recruitment_documentation</data><data key="edge_target_entity_id">R173_E003</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Every reasonable effort within previous 18 months before authority assigned.</data></edge><edge id="R173_REL0004" source="R173_E001" target="R173_E004"><data key="edge_relationship_id">R173_REL0004</data><data key="edge_source_entity_id">R173_E001</data><data key="edge_relationship_type">requires_examiner_qualification_record</data><data key="edge_target_entity_id">R173_E004</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Includes 12 months training+practice threshold and supervisory approval.</data></edge><edge id="R173_REL0005" source="R173_E001" target="R173_E005"><data key="edge_relationship_id">R173_REL0005</data><data key="edge_source_entity_id">R173_E001</data><data key="edge_relationship_type">produces_signature_annotation</data><data key="edge_target_entity_id">R173_E005</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-831 blanks specific signature items and uses item-34 remark.</data></edge><edge id="R173_REL0006" source="R173_E005" target="R128_E007"><data key="edge_relationship_id">R173_REL0006</data><data key="edge_source_entity_id">R173_E005</data><data key="edge_relationship_type">applies_to_initial_disability_form</data><data key="edge_target_entity_id">R128_E007</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-831 initial determination file; does not infer physical repository.</data></edge><edge id="R173_REL0007" source="R173_E001" target="R173_E006"><data key="edge_relationship_id">R173_REL0007</data><data key="edge_source_entity_id">R173_E001</data><data key="edge_relationship_type">permits_qualified_examiner_medical_form_signature</data><data key="edge_target_entity_id">R173_E006</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-4734 physical RFC assessment.</data></edge><edge id="R173_REL0008" source="R173_E001" target="FORM_R105_SSA416"><data key="edge_relationship_id">R173_REL0008</data><data key="edge_source_entity_id">R173_E001</data><data key="edge_relationship_type">permits_signature_on_medical_evaluation</data><data key="edge_target_entity_id">FORM_R105_SSA416</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Page refers to SSA-416 as Medical Evaluation, while historical Atlas labels SSA-416 Case Analysis. Form-title discrepancy needs review.</data></edge><edge id="R173_REL0009" source="R173_E002" target="STRUCT_DDE"><data key="edge_relationship_id">R173_REL0009</data><data key="edge_source_entity_id">R173_E002</data><data key="edge_relationship_type">excludes_ineligible_signature_from</data><data key="edge_target_entity_id">STRUCT_DDE</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Do not use examiner authority in Disability Determination Explanation when case excluded.</data></edge><edge id="R173_REL0010" source="R173_E007" target="R173_E008"><data key="edge_relationship_id">R173_REL0010</data><data key="edge_source_entity_id">R173_E007</data><data key="edge_relationship_type">extends_qualifying_CDR_continuances</data><data key="edge_target_entity_id">R173_E008</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">No cessation cases; subject to main DEDA criteria.</data></edge><edge id="R173_REL0011" source="R173_E007" target="R173_E009"><data key="edge_relationship_id">R173_REL0011</data><data key="edge_source_entity_id">R173_E007</data><data key="edge_relationship_type">extends_qualifying_age18_cases</data><data key="edge_target_entity_id">R173_E009</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Full favorable physical-only adult redeterminations.</data></edge><edge id="R173_REL0012" source="R173_E007" target="R173_E010"><data key="edge_relationship_id">R173_REL0012</data><data key="edge_source_entity_id">R173_E007</data><data key="edge_relationship_type">extends_qualifying_EXR_cases</data><data key="edge_target_entity_id">R173_E010</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Related impairment and favorable EXR standards.</data></edge><edge id="R173_REL0013" source="R173_E007" target="R173_E011"><data key="edge_relationship_id">R173_REL0013</data><data key="edge_source_entity_id">R173_E007</data><data key="edge_relationship_type">requires_extension_form_annotation</data><data key="edge_target_entity_id">R173_E011</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">SSA-832/833 blank MC/PC fields and remarks.</data></edge><edge id="R173_REL0014" source="R173_E011" target="R128_E008"><data key="edge_relationship_id">R173_REL0014</data><data key="edge_source_entity_id">R173_E011</data><data key="edge_relationship_type">applies_to_CDR_decision_forms</data><data key="edge_target_entity_id">R128_E008</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">SSA-832/SSA-833 existing grouped administrative file.</data></edge><edge id="R173_REL0015" source="R173_E007" target="R173_E003"><data key="edge_relationship_id">R173_REL0015</data><data key="edge_source_entity_id">R173_E007</data><data key="edge_relationship_type">inherits_site_recruitment_control</data><data key="edge_target_entity_id">R173_E003</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Separate extension retains medical consultant recruitment prerequisite.</data></edge><edge id="R173_REL0016" source="R173_E007" target="R173_E004"><data key="edge_relationship_id">R173_REL0016</data><data key="edge_source_entity_id">R173_E007</data><data key="edge_relationship_type">inherits_qualified_examiner_gate</data><data key="edge_target_entity_id">R173_E004</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Additional conditions may apply to assisting adjudication sites.</data></edge><edge id="R173_REL0017" source="ORG_DDS" target="R173_E012"><data key="edge_relationship_id">R173_REL0017</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">observes_evidence_followup_rule</data><data key="edge_target_entity_id">R173_E012</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Initial 10 plus further 10 days absent good reason for more time.</data></edge><edge id="R173_REL0018" source="R173_E012" target="R173_E013"><data key="edge_relationship_id">R173_REL0018</data><data key="edge_source_entity_id">R173_E012</data><data key="edge_relationship_type">escalates_special_handling_to</data><data key="edge_target_entity_id">R173_E013</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Disability case special-handling exceptions.</data></edge><edge id="R173_REL0019" source="R173_E012" target="R173_E014"><data key="edge_relationship_id">R173_REL0019</data><data key="edge_source_entity_id">R173_E012</data><data key="edge_relationship_type">constrains_disclosure_via</data><data key="edge_target_entity_id">R173_E014</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Voice contact minimal necessary information; cannot disclose case identifiers in voicemail.</data></edge><edge id="R173_REL0020" source="R173_E014" target="FORM_SSA5002"><data key="edge_relationship_id">R173_REL0020</data><data key="edge_source_entity_id">R173_E014</data><data key="edge_relationship_type">documents_contact_in</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-5002 or DCPS case note alternative.</data></edge><edge id="R173_REL0021" source="R173_E014" target="APP_DCPS"><data key="edge_relationship_id">R173_REL0021</data><data key="edge_source_entity_id">R173_E014</data><data key="edge_relationship_type">documents_case_note_in</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Contact date, person, content recorded in DCPS case notes when used.</data></edge><edge id="R173_REL0022" source="R173_E012" target="STRUCT_CDW"><data key="edge_relationship_id">R173_REL0022</data><data key="edge_source_entity_id">R173_E012</data><data key="edge_relationship_type">requires_workflow_entry_in</data><data key="edge_target_entity_id">STRUCT_CDW</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Write to case development worksheet.</data></edge><edge id="R173_REL0023" source="R173_E013" target="STRUCT_DDE"><data key="edge_relationship_id">R173_REL0023</data><data key="edge_source_entity_id">R173_E013</data><data key="edge_relationship_type">requires_reasonable_medical_record_development</data><data key="edge_target_entity_id">STRUCT_DDE</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence-in-file decision uses sequential evaluation after independent medical history development; DDE connection is conceptual and not a technical interface.</data></edge><edge id="R173_REL0024" source="ORG_DDS" target="R173_E015"><data key="edge_relationship_id">R173_REL0024</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">issues_written_CE_notice_under</data><data key="edge_target_entity_id">R173_E015</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Provider contact/address in notice is NOT claimant address.</data></edge><edge id="R173_REL0025" source="R173_E015" target="DATA_CE_PROVIDER_ADDR"><data key="edge_relationship_id">R173_REL0025</data><data key="edge_source_entity_id">R173_E015</data><data key="edge_relationship_type">includes_medical_provider_address</data><data key="edge_target_entity_id">DATA_CE_PROVIDER_ADDR</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Address belongs to CE provider; not an update to claimant program records.</data></edge><edge id="R173_REL0026" source="R173_E015" target="R173_E016"><data key="edge_relationship_id">R173_REL0026</data><data key="edge_source_entity_id">R173_E015</data><data key="edge_relationship_type">requires_confirmation_followup</data><data key="edge_target_entity_id">R173_E016</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">When scheduled more than 10 days after written notice.</data></edge><edge id="R173_REL0027" source="R173_E015" target="R173_E017"><data key="edge_relationship_id">R173_REL0027</data><data key="edge_source_entity_id">R173_E015</data><data key="edge_relationship_type">may_use_short_notice_path</data><data key="edge_target_entity_id">R173_E017</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Ten days or less from written notice.</data></edge><edge id="R173_REL0028" source="R173_E015" target="R173_E018"><data key="edge_relationship_id">R173_REL0028</data><data key="edge_source_entity_id">R173_E015</data><data key="edge_relationship_type">supports_missed_CE_escalation</data><data key="edge_target_entity_id">R173_E018</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Records missed examination and good reason for reschedule.</data></edge><edge id="R173_REL0029" source="R173_E018" target="R173_E019"><data key="edge_relationship_id">R173_REL0029</data><data key="edge_source_entity_id">R173_E018</data><data key="edge_relationship_type">may_trigger_incarcerated_CE_consent</data><data key="edge_target_entity_id">R173_E019</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Staff presence in corrections facility triggers consent request; not automatic consent.</data></edge><edge id="R173_REL0030" source="R173_E016" target="APP_DCPS"><data key="edge_relationship_id">R173_REL0030</data><data key="edge_source_entity_id">R173_E016</data><data key="edge_relationship_type">documents_confirmation_in</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Document on case note and CDW or SSA-5002, unless written confirmation filed.</data></edge><edge id="R173_REL0031" source="R173_E018" target="STRUCT_CDW"><data key="edge_relationship_id">R173_REL0031</data><data key="edge_source_entity_id">R173_E018</data><data key="edge_relationship_type">requires_case_development_worklog</data><data key="edge_target_entity_id">STRUCT_CDW</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">DDS must write to worksheet; no particular database technology inferred.</data></edge><edge id="R173_REL0032" source="R173_E018" target="R173_E020"><data key="edge_relationship_id">R173_REL0032</data><data key="edge_source_entity_id">R173_E018</data><data key="edge_relationship_type">uses_special_handling_third_party_rule</data><data key="edge_target_entity_id">R173_E020</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Reasonable effort to involve third party in special-handling cases.</data></edge><edge id="R173_REL0033" source="R173_E013" target="R173_E020"><data key="edge_relationship_id">R173_REL0033</data><data key="edge_source_entity_id">R173_E013</data><data key="edge_relationship_type">depends_on_third_party_eligibility</data><data key="edge_target_entity_id">R173_E020</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Exception for minors with AR and other conditional criteria.</data></edge><edge id="R173_REL0034" source="R173_E020" target="R173_E021"><data key="edge_relationship_id">R173_REL0034</data><data key="edge_source_entity_id">R173_E020</data><data key="edge_relationship_type">obtains_claimant_nominated_contact</data><data key="edge_target_entity_id">R173_E021</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Third-party name/address/phone from claimant or recorded forms; not verified claimant address.</data></edge><edge id="R173_REL0035" source="R173_E021" target="R173_E022"><data key="edge_relationship_id">R173_REL0035</data><data key="edge_source_entity_id">R173_E021</data><data key="edge_relationship_type">subject_to_independent_lookup_restriction</data><data key="edge_target_entity_id">R173_E022</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Nonprofessional address/phone lookup restricted.</data></edge><edge id="R173_REL0036" source="R173_E020" target="R173_E023"><data key="edge_relationship_id">R173_REL0036</data><data key="edge_source_entity_id">R173_E020</data><data key="edge_relationship_type">triggers_contact_verification_and_followup</data><data key="edge_target_entity_id">R173_E023</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Identity checks, ten days and good reason extensions.</data></edge><edge id="R173_REL0037" source="R173_E023" target="APP_DCPS"><data key="edge_relationship_id">R173_REL0037</data><data key="edge_source_entity_id">R173_E023</data><data key="edge_relationship_type">documents_contacts_in</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-5002 or DCPS Case Note and CDW.</data></edge><edge id="R173_REL0038" source="R173_E023" target="STRUCT_CDW"><data key="edge_relationship_id">R173_REL0038</data><data key="edge_source_entity_id">R173_E023</data><data key="edge_relationship_type">requires_worksheet_entry</data><data key="edge_target_entity_id">STRUCT_CDW</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Specific case development logging obligation.</data></edge><edge id="R173_REL0039" source="R173_E021" target="SYS_MBR"><data key="edge_relationship_id">R173_REL0039</data><data key="edge_source_entity_id">R173_E021</data><data key="edge_relationship_type">is_not_verified_claimant_address_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Address is a third-party contact attribute; no evidence it updates MBR.</data></edge><edge id="R173_REL0040" source="R173_E021" target="SYS_SSR"><data key="edge_relationship_id">R173_REL0040</data><data key="edge_source_entity_id">R173_E021</data><data key="edge_relationship_type">is_not_verified_claimant_address_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Address is a third-party contact attribute; no evidence it updates SSR.</data></edge><edge id="R173_REL0041" source="APP_SSI_CLAIMS_LOGICAL" target="R173_E024"><data key="edge_relationship_id">R173_REL0041</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">guides_redetermination_insurance_development</data><data key="edge_target_entity_id">R173_E024</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Interview path and policy checks.</data></edge><edge id="R173_REL0042" source="FORM_SSA8203BK" target="R173_E024"><data key="edge_relationship_id">R173_REL0042</data><data key="edge_source_entity_id">FORM_SSA8203BK</data><data key="edge_relationship_type">collects_insurance_policy_allegations_for</data><data key="edge_target_entity_id">R173_E024</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Question 18 multiple owner/insured/provider/policy attributes.</data></edge><edge id="R173_REL0043" source="R173_E024" target="R173_E025"><data key="edge_relationship_id">R173_REL0043</data><data key="edge_source_entity_id">R173_E024</data><data key="edge_relationship_type">captures_insurer_organizational_address</data><data key="edge_target_entity_id">R173_E025</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Not claimant mailing/residential address.</data></edge><edge id="R173_REL0044" source="R173_E024" target="R173_E026"><data key="edge_relationship_id">R173_REL0044</data><data key="edge_source_entity_id">R173_E024</data><data key="edge_relationship_type">requires_lookback_value_development_for</data><data key="edge_target_entity_id">R173_E026</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence of cash out/lapse, records or insurer contact;  verification to date of event.</data></edge><edge id="R173_REL0045" source="R173_E026" target="R173_E025"><data key="edge_relationship_id">R173_REL0045</data><data key="edge_source_entity_id">R173_E026</data><data key="edge_relationship_type">can_require_insurer_contact_using</data><data key="edge_target_entity_id">R173_E025</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Only when claimant lacks documentation; no automated FI interface inferred.</data></edge><edge id="R173_REL0046" source="ORG_SSA_OCACT" target="R173_E027"><data key="edge_relationship_id">R173_REL0046</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes_historical_trust_fund_admin_expenses</data><data key="edge_target_entity_id">R173_E027</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Official public OACT statistics with data through calendar 2025.</data></edge><edge id="R173_REL0047" source="R173_E027" target="R173_E028"><data key="edge_relationship_id">R173_REL0047</data><data key="edge_source_entity_id">R173_E027</data><data key="edge_relationship_type">applies_cost_share_definition</data><data key="edge_target_entity_id">R173_E028</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Annual share of trust-fund total cost; avoids confusing with all SSA appropriations.</data></edge><edge id="R173_REL0048" source="R173_E027" target="DATA_OACT_TRUST_FUND_FINANCIAL"><data key="edge_relationship_id">R173_REL0048</data><data key="edge_source_entity_id">R173_E027</data><data key="edge_relationship_type">is_statistically_related_to_trust_fund_reporting</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_operational_context">documented_policy_or_statistical_lineage</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Common trust-fund financial domain, not confirmed technical feed or publication ETL.</data></edge><edge id="R174_REL0001" source="R174_E001" target="DB_DCF"><data key="edge_relationship_id">R174_REL0001</data><data key="edge_source_entity_id">R174_E001</data><data key="edge_relationship_type">records_title_ii_cdr_appeal_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">FO uses EEAI for Title II medical-CDR appeals excluded from EDCS; appeal request entered in DCF.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">FO uses EEAI for Title II medical-CDR appeals excluded from EDCS; appeal request entered in DCF.</data></edge><edge id="R174_REL0002" source="R174_E001" target="R174_E002"><data key="edge_relationship_id">R174_REL0002</data><data key="edge_source_entity_id">R174_E001</data><data key="edge_relationship_type">initiates_exception_workflow</data><data key="edge_target_entity_id">R174_E002</data><data key="edge_operational_context">EEAI is the documented entry route for the Title II CDR exclusion workflow.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">EEAI is the documented entry route for the Title II CDR exclusion workflow.</data></edge><edge id="R174_REL0003" source="R174_E002" target="DB_DCF"><data key="edge_relationship_id">R174_REL0003</data><data key="edge_source_entity_id">R174_E002</data><data key="edge_relationship_type">reads_or_receives_case_details_from</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">DCF passes appeal request and statutory benefit continuation information to T2R background program; no protocol claimed.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">DCF passes appeal request and statutory benefit continuation information to T2R background program; no protocol claimed.</data></edge><edge id="R174_REL0004" source="R174_E002" target="APP_T2R"><data key="edge_relationship_id">R174_REL0004</data><data key="edge_source_entity_id">R174_E002</data><data key="edge_relationship_type">processed_by</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">Title II Redesign background program consumes CDR appeal and SBC data from DCF.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Title II Redesign background program consumes CDR appeal and SBC data from DCF.</data></edge><edge id="R174_REL0005" source="R174_E002" target="SYS_MBR"><data key="edge_relationship_id">R174_REL0005</data><data key="edge_source_entity_id">R174_E002</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS explicitly states the T2R background program automatically updates MBR for Title II CDR exclusion reconsiderations.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly states the T2R background program automatically updates MBR for Title II CDR exclusion reconsiderations.</data></edge><edge id="R174_REL0006" source="R174_E003" target="APP_POS"><data key="edge_relationship_id">R174_REL0006</data><data key="edge_source_entity_id">R174_E003</data><data key="edge_relationship_type">requires_manual_posting_via</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">In excluded Title II CDR hearing appeal, a hearing reversal requires POS input to MBR unlike specified dispositions that post automatically.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">In excluded Title II CDR hearing appeal, a hearing reversal requires POS input to MBR unlike specified dispositions that post automatically.</data></edge><edge id="R174_REL0007" source="R174_E003" target="SYS_MBR"><data key="edge_relationship_id">R174_REL0007</data><data key="edge_source_entity_id">R174_E003</data><data key="edge_relationship_type">updates_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Manual POS input updates MBR for excluded CDR hearing reversal; automatic posting applies to other specified dispositions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Manual POS input updates MBR for excluded CDR hearing reversal; automatic posting applies to other specified dispositions.</data></edge><edge id="R174_REL0008" source="R174_E003" target="R174_E002"><data key="edge_relationship_id">R174_REL0008</data><data key="edge_source_entity_id">R174_E003</data><data key="edge_relationship_type">exception_from</data><data key="edge_target_entity_id">R174_E002</data><data key="edge_operational_context">Automated background-update route cannot be assumed for all CDR appeal outcome types.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Automated background-update route cannot be assumed for all CDR appeal outcome types.</data></edge><edge id="R174_REL0009" source="R174_E004" target="FORM_SSA789"><data key="edge_relationship_id">R174_REL0009</data><data key="edge_source_entity_id">R174_E004</data><data key="edge_relationship_type">resolves_missing_information_on</data><data key="edge_target_entity_id">FORM_SSA789</data><data key="edge_operational_context">FO develops incomplete claimant hearing or interpreter preference with a 15-day follow-up diary.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">FO develops incomplete claimant hearing or interpreter preference with a 15-day follow-up diary.</data></edge><edge id="R174_REL0010" source="R174_E004" target="ORG_DDS"><data key="edge_relationship_id">R174_REL0010</data><data key="edge_source_entity_id">R174_E004</data><data key="edge_relationship_type">supports_routing_to</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">After 15-day nonresponse, FO forwards the incomplete case for DDS resolution.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">After 15-day nonresponse, FO forwards the incomplete case for DDS resolution.</data></edge><edge id="R174_REL0011" source="R174_E002" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R174_REL0011</data><data key="edge_source_entity_id">R174_E002</data><data key="edge_relationship_type">tracked_in</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">Title II EDCS-excluded reconsideration appeal loaded in DCF becomes visible in MI Central; excluded ALJ hearing appeals do not.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Title II EDCS-excluded reconsideration appeal loaded in DCF becomes visible in MI Central; excluded ALJ hearing appeals do not.</data></edge><edge id="R174_REL0012" source="SYS_MBR" target="R174_E005"><data key="edge_relationship_id">R174_REL0012</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">primary_statistical_source_for</data><data key="edge_target_entity_id">R174_E005</data><data key="edge_operational_context">Annual Statistical Supplement 6.F reports MBR 100-percent data; statistical lineage only.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Annual Statistical Supplement 6.F reports MBR 100-percent data; statistical lineage only.</data></edge><edge id="R174_REL0013" source="R174_E005" target="R174_E006"><data key="edge_relationship_id">R174_REL0013</data><data key="edge_source_entity_id">R174_E005</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R174_E006</data><data key="edge_operational_context">Annual section 6.F publishes historical terminations table 6.F1.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Annual section 6.F publishes historical terminations table 6.F1.</data></edge><edge id="R174_REL0014" source="R174_E005" target="R174_E007"><data key="edge_relationship_id">R174_REL0014</data><data key="edge_source_entity_id">R174_E005</data><data key="edge_relationship_type">publishes_table</data><data key="edge_target_entity_id">R174_E007</data><data key="edge_operational_context">Annual section 6.F publishes 2025 reasons for terminations table 6.F2.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Annual section 6.F publishes 2025 reasons for terminations table 6.F2.</data></edge><edge id="R174_REL0015" source="R174_E007" target="R174_E008"><data key="edge_relationship_id">R174_REL0015</data><data key="edge_source_entity_id">R174_E007</data><data key="edge_relationship_type">applies_calendar_report_rule</data><data key="edge_target_entity_id">R174_E008</data><data key="edge_operational_context">Terminations counted by calendar year of recorded termination regardless of effective date.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Terminations counted by calendar year of recorded termination regardless of effective date.</data></edge><edge id="R174_REL0016" source="R174_E007" target="R174_E010"><data key="edge_relationship_id">R174_REL0016</data><data key="edge_source_entity_id">R174_E007</data><data key="edge_relationship_type">includes_statistical_breakdown</data><data key="edge_target_entity_id">R174_E010</data><data key="edge_operational_context">Table 6.F2 itemizes different disability cessation reason categories.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table 6.F2 itemizes different disability cessation reason categories.</data></edge><edge id="R174_REL0017" source="R174_E005" target="R174_E009"><data key="edge_relationship_id">R174_REL0017</data><data key="edge_source_entity_id">R174_E005</data><data key="edge_relationship_type">has_methodology_caveat</data><data key="edge_target_entity_id">R174_E009</data><data key="edge_operational_context">Published MBR termination series may differ from Actuarial Services series; no undocumented reconciliation method inferred.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Published MBR termination series may differ from Actuarial Services series; no undocumented reconciliation method inferred.</data></edge><edge id="R174_REL0018" source="SYS_MBR" target="R174_E010"><data key="edge_relationship_id">R174_REL0018</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_publication</data><data key="edge_target_entity_id">R174_E010</data><data key="edge_operational_context">Subgroup statistics from MBR; not proof of direct DDS-to-publication pipeline.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Subgroup statistics from MBR; not proof of direct DDS-to-publication pipeline.</data></edge><edge id="R174_REL0019" source="R174_E006" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R174_REL0019</data><data key="edge_source_entity_id">R174_E006</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">2026 annual edition includes 6.F1 as a published table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">2026 annual edition includes 6.F1 as a published table.</data></edge><edge id="R174_REL0020" source="SYS_MBR" target="R174_E011"><data key="edge_relationship_id">R174_REL0020</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_statistics_for</data><data key="edge_target_entity_id">R174_E011</data><data key="edge_operational_context">SSA identifies MBR as administrative source for the 2026 5.H family tables.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA identifies MBR as administrative source for the 2026 5.H family tables.</data></edge><edge id="R174_REL0021" source="R174_E011" target="R174_E012"><data key="edge_relationship_id">R174_REL0021</data><data key="edge_source_entity_id">R174_E011</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R174_E012</data><data key="edge_operational_context">Historical 5.H1 family series in 2026 section 5.H.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Historical 5.H1 family series in 2026 section 5.H.</data></edge><edge id="R174_REL0022" source="R174_E011" target="R174_E013"><data key="edge_relationship_id">R174_REL0022</data><data key="edge_source_entity_id">R174_E011</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R174_E013</data><data key="edge_operational_context">2025 5.H2 table distinguishes family units and beneficiaries.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">2025 5.H2 table distinguishes family units and beneficiaries.</data></edge><edge id="R174_REL0023" source="R174_E012" target="R174_E014"><data key="edge_relationship_id">R174_REL0023</data><data key="edge_source_entity_id">R174_E012</data><data key="edge_relationship_type">subject_to_historical_sample_rule</data><data key="edge_target_entity_id">R174_E014</data><data key="edge_operational_context">SSA explicitly supplies historical family sample rates 1945–1984, 1985–2005, and other years.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA explicitly supplies historical family sample rates 1945–1984, 1985–2005, and other years.</data></edge><edge id="R174_REL0024" source="R174_E013" target="R174_E015"><data key="edge_relationship_id">R174_REL0024</data><data key="edge_source_entity_id">R174_E013</data><data key="edge_relationship_type">applies_entitlement_reporting_rule</data><data key="edge_target_entity_id">R174_E015</data><data key="edge_operational_context">Dually entitled spouse benefit amount in 5.H2 is a difference between benefits.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Dually entitled spouse benefit amount in 5.H2 is a difference between benefits.</data></edge><edge id="R174_REL0025" source="R174_E011" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R174_REL0025</data><data key="edge_source_entity_id">R174_E011</data><data key="edge_relationship_type">section_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Section 5.H part of 2026 statistical supplement.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Section 5.H part of 2026 statistical supplement.</data></edge><edge id="R174_REL0026" source="R174_E013" target="R174_E011"><data key="edge_relationship_id">R174_REL0026</data><data key="edge_source_entity_id">R174_E013</data><data key="edge_relationship_type">counts_multiple_people_per_family</data><data key="edge_target_entity_id">R174_E011</data><data key="edge_operational_context">Family and individual counts appear as different columns; does not assert physical family master.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Family and individual counts appear as different columns; does not assert physical family master.</data></edge><edge id="R174_REL0027" source="SYS_MBR" target="R174_E016"><data key="edge_relationship_id">R174_REL0027</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">supplies_statistical_records_for</data><data key="edge_target_entity_id">R174_E016</data><data key="edge_operational_context">2026 totalization statistics use 100-percent MBR data; no assertion about external totalization transport.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">2026 totalization statistics use 100-percent MBR data; no assertion about external totalization transport.</data></edge><edge id="R174_REL0028" source="R174_E016" target="R174_E017"><data key="edge_relationship_id">R174_REL0028</data><data key="edge_source_entity_id">R174_E016</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R174_E017</data><data key="edge_operational_context">5.M1 selected-year and country-by-benefit publication table.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">5.M1 selected-year and country-by-benefit publication table.</data></edge><edge id="R174_REL0029" source="R174_E017" target="R174_E018"><data key="edge_relationship_id">R174_REL0029</data><data key="edge_source_entity_id">R174_E017</data><data key="edge_relationship_type">subject_to_geographic_attribution_constraint</data><data key="edge_target_entity_id">R174_E018</data><data key="edge_operational_context">Country labels refer to agreement groupings and do not prove an individuals current residence.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Country labels refer to agreement groupings and do not prove an individuals current residence.</data></edge><edge id="R174_REL0030" source="R174_E017" target="R174_E019"><data key="edge_relationship_id">R174_REL0030</data><data key="edge_source_entity_id">R174_E017</data><data key="edge_relationship_type">subject_to_disclosure_rule</data><data key="edge_target_entity_id">R174_E019</data><data key="edge_operational_context">SSA suppresses some cells to avoid disclosing information about individuals.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA suppresses some cells to avoid disclosing information about individuals.</data></edge><edge id="R174_REL0031" source="R174_E016" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R174_REL0031</data><data key="edge_source_entity_id">R174_E016</data><data key="edge_relationship_type">section_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Section 5.M appears in 2026 annual supplement.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Section 5.M appears in 2026 annual supplement.</data></edge><edge id="R174_REL0032" source="SYS_MBR" target="R174_E020"><data key="edge_relationship_id">R174_REL0032</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_publication</data><data key="edge_target_entity_id">R174_E020</data><data key="edge_operational_context">Table 6.E5 states MBR 100-percent data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table 6.E5 states MBR 100-percent data.</data></edge><edge id="R174_REL0033" source="R174_E020" target="R174_E021"><data key="edge_relationship_id">R174_REL0033</data><data key="edge_source_entity_id">R174_E020</data><data key="edge_relationship_type">reports_category</data><data key="edge_target_entity_id">R174_E021</data><data key="edge_operational_context">Address unknown is one of the enumerated reason-for-withholding categories; no actual new address observed.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Address unknown is one of the enumerated reason-for-withholding categories; no actual new address observed.</data></edge><edge id="R174_REL0034" source="R155_E0027" target="R174_E021"><data key="edge_relationship_id">R174_REL0034</data><data key="edge_source_entity_id">R155_E0027</data><data key="edge_relationship_type">includes_category_also_found_in</data><data key="edge_target_entity_id">R174_E021</data><data key="edge_operational_context">Published Table 6.E4 includes address unknown; table 6.E5 groups by basis of entitlement.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Published Table 6.E4 includes address unknown; table 6.E5 groups by basis of entitlement.</data></edge><edge id="R174_REL0035" source="R174_E020" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R174_REL0035</data><data key="edge_source_entity_id">R174_E020</data><data key="edge_relationship_type">section_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Table 6.E5 is part of statistical supplement 2026.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Table 6.E5 is part of statistical supplement 2026.</data></edge><edge id="R174_REL0036" source="R174_E022" target="R174_E023"><data key="edge_relationship_id">R174_REL0036</data><data key="edge_source_entity_id">R174_E022</data><data key="edge_relationship_type">routes_career_railroad_to</data><data key="edge_target_entity_id">R174_E023</data><data key="edge_operational_context">POMS CDR reconsideration folders for career railroad case route to Great Lakes Program Service Center.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">POMS CDR reconsideration folders for career railroad case route to Great Lakes Program Service Center.</data></edge><edge id="R174_REL0037" source="R174_E022" target="ORG_SSA_OEIO"><data key="edge_relationship_id">R174_REL0037</data><data key="edge_source_entity_id">R174_E022</data><data key="edge_relationship_type">routes_foreign_case_to</data><data key="edge_target_entity_id">ORG_SSA_OEIO</data><data key="edge_operational_context">Foreign medical CDR reconsideration folder directed to OEIO, not servicing DDS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Foreign medical CDR reconsideration folder directed to OEIO, not servicing DDS.</data></edge><edge id="R174_REL0038" source="FORM_SSA789" target="R174_E022"><data key="edge_relationship_id">R174_REL0038</data><data key="edge_source_entity_id">FORM_SSA789</data><data key="edge_relationship_type">supports_special_case_routing</data><data key="edge_target_entity_id">R174_E022</data><data key="edge_operational_context">FO documentation rules for career railroad and foreign CDR cases identify handling of form SSA-789.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">FO documentation rules for career railroad and foreign CDR cases identify handling of form SSA-789.</data></edge><edge id="R175_R0001" source="APP_ERPS" target="R175_E0007"><data key="edge_relationship_id">R175_R0001</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">supports_payee_name_matching_for</data><data key="edge_target_entity_id">R175_E0007</data><data key="edge_operational_context">Policy requires payee name on collective account match eRPS identity</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0002" source="R175_E0007" target="R175_E0001"><data key="edge_relationship_id">R175_R0002</data><data key="edge_source_entity_id">R175_E0007</data><data key="edge_relationship_type">verifies_name_on</data><data key="edge_target_entity_id">R175_E0001</data><data key="edge_operational_context">Cross-document match concerns externally titled account, not a new SSA address repository</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0003" source="R175_E0008" target="R175_E0007"><data key="edge_relationship_id">R175_R0003</data><data key="edge_source_entity_id">R175_E0008</data><data key="edge_relationship_type">constrains_payee_identity_for</data><data key="edge_target_entity_id">R175_E0007</data><data key="edge_operational_context">DBA or parent company name is not interchangeable with actual appointed payee</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0004" source="R175_E0009" target="R175_E0007"><data key="edge_relationship_id">R175_R0004</data><data key="edge_source_entity_id">R175_E0009</data><data key="edge_relationship_type">constrains_payee_identity_for</data><data key="edge_target_entity_id">R175_E0007</data><data key="edge_operational_context">Branch/subsidiary appointed payee is the account-holder name</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0005" source="R175_E0011" target="R175_E0001"><data key="edge_relationship_id">R175_R0005</data><data key="edge_source_entity_id">R175_E0011</data><data key="edge_relationship_type">governs_ownership_of</data><data key="edge_target_entity_id">R175_E0001</data><data key="edge_operational_context">Beneficiary is beneficial owner, payee holds fiduciary control</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0006" source="R175_E0002" target="R175_E0001"><data key="edge_relationship_id">R175_R0006</data><data key="edge_source_entity_id">R175_E0002</data><data key="edge_relationship_type">exception_to_standard_titling_of</data><data key="edge_target_entity_id">R175_E0001</data><data key="edge_operational_context">Only certain spouses or parents using personal checking under all criteria</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0007" source="R175_E0003" target="R175_E0002"><data key="edge_relationship_id">R175_R0007</data><data key="edge_source_entity_id">R175_E0003</data><data key="edge_relationship_type">limits_exception_of</data><data key="edge_target_entity_id">R175_E0002</data><data key="edge_operational_context">Personal savings accounts are expressly excluded</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0008" source="R175_E0013" target="R175_E0002"><data key="edge_relationship_id">R175_R0008</data><data key="edge_source_entity_id">R175_E0013</data><data key="edge_relationship_type">required_verification_for</data><data key="edge_target_entity_id">R175_E0002</data><data key="edge_operational_context">Confirm same household and current-expense use; no accumulation</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0009" source="R175_E0004" target="R175_E0005"><data key="edge_relationship_id">R175_R0009</data><data key="edge_source_entity_id">R175_E0004</data><data key="edge_relationship_type">passes_payments_to</data><data key="edge_target_entity_id">R175_E0005</data><data key="edge_operational_context">Government depository must promptly pass amounts to beneficiary-protected fiduciary sub-account</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0010" source="R175_E0012" target="R175_E0006"><data key="edge_relationship_id">R175_R0010</data><data key="edge_source_entity_id">R175_E0012</data><data key="edge_relationship_type">requires_beneficiary_level</data><data key="edge_target_entity_id">R175_E0006</data><data key="edge_operational_context">State childcare/foster care payee deposit and cost-of-care expenditures tracked by child</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0011" source="R175_E0012" target="R175_E0001"><data key="edge_relationship_id">R175_R0011</data><data key="edge_source_entity_id">R175_E0012</data><data key="edge_relationship_type">exception_to_standard_titling_of</data><data key="edge_target_entity_id">R175_E0001</data><data key="edge_operational_context">Government foster-care account exception conditional on protections</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0012" source="R175_E0010" target="R175_E0001"><data key="edge_relationship_id">R175_R0012</data><data key="edge_source_entity_id">R175_E0010</data><data key="edge_relationship_type">excludes_account_form_for</data><data key="edge_target_entity_id">R175_E0001</data><data key="edge_operational_context">Traditional trust does not qualify as collective payee account</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0013" source="APP_ERPS" target="R175_E0008"><data key="edge_relationship_id">R175_R0013</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">identifies_actual_payee_for</data><data key="edge_target_entity_id">R175_E0008</data><data key="edge_operational_context">eRPS payee identity governs the account title under DBA and parent examples</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0014" source="APP_ERPS" target="R175_E0009"><data key="edge_relationship_id">R175_R0014</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">identifies_actual_payee_for</data><data key="edge_target_entity_id">R175_E0009</data><data key="edge_operational_context">eRPS names the branch/subsidiary when it is appointed, not automatically the parent</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0015" source="DOM_REPPAYEE" target="R175_E0011"><data key="edge_relationship_id">R175_R0015</data><data key="edge_source_entity_id">DOM_REPPAYEE</data><data key="edge_relationship_type">governed_by_account_rule</data><data key="edge_target_entity_id">R175_E0011</data><data key="edge_operational_context">Person roles: beneficiary as owner, payee as fiduciary, not physical Person repository</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0016" source="APP_DCPS" target="R175_E0015"><data key="edge_relationship_id">R175_R0016</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">provides_interface</data><data key="edge_target_entity_id">R175_E0015</data><data key="edge_operational_context">DCPS hosts Evaluations and Assessments section</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0017" source="R175_E0015" target="R175_E0016"><data key="edge_relationship_id">R175_R0017</data><data key="edge_source_entity_id">R175_E0015</data><data key="edge_relationship_type">contained_in_page</data><data key="edge_target_entity_id">R175_E0016</data><data key="edge_operational_context">Medical evaluation section on Impairment Severity/Sign page</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0018" source="APP_DCPS" target="R175_E0016"><data key="edge_relationship_id">R175_R0018</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">provides_interface</data><data key="edge_target_entity_id">R175_E0016</data><data key="edge_operational_context">Page documented in medical evaluation POMS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0019" source="R175_E0015" target="R175_E0014"><data key="edge_relationship_id">R175_R0019</data><data key="edge_source_entity_id">R175_E0015</data><data key="edge_relationship_type">supports_form</data><data key="edge_target_entity_id">R175_E0014</data><data key="edge_operational_context">MA uses MA-416 in DCPS for electronic and paper case processing</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0020" source="R175_E0015" target="FORM_R105_SSA416"><data key="edge_relationship_id">R175_R0020</data><data key="edge_source_entity_id">R175_E0015</data><data key="edge_relationship_type">supports_form</data><data key="edge_target_entity_id">FORM_R105_SSA416</data><data key="edge_operational_context">SSA-416 medical evaluation on same DCPS page</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0021" source="FORM_R105_SSA416" target="R175_E0017"><data key="edge_relationship_id">R175_R0021</data><data key="edge_source_entity_id">FORM_R105_SSA416</data><data key="edge_relationship_type">has_attribute</data><data key="edge_target_entity_id">R175_E0017</data><data key="edge_operational_context">Evaluation period dropdown</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0022" source="FORM_R105_SSA416" target="R175_E0018"><data key="edge_relationship_id">R175_R0022</data><data key="edge_source_entity_id">FORM_R105_SSA416</data><data key="edge_relationship_type">has_attribute</data><data key="edge_target_entity_id">R175_E0018</data><data key="edge_operational_context">Medical finding subject fields</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0023" source="FORM_R105_SSA416" target="R175_E0019"><data key="edge_relationship_id">R175_R0023</data><data key="edge_source_entity_id">FORM_R105_SSA416</data><data key="edge_relationship_type">has_completion_control</data><data key="edge_target_entity_id">R175_E0019</data><data key="edge_operational_context">Statement reserved for complete medical findings</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0024" source="FORM_R105_SSA416" target="R175_E0020"><data key="edge_relationship_id">R175_R0024</data><data key="edge_source_entity_id">FORM_R105_SSA416</data><data key="edge_relationship_type">has_signature_metadata</data><data key="edge_target_entity_id">R175_E0020</data><data key="edge_operational_context">Electronic 416 sign-and-save populates signer specialty/date</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0025" source="R175_E0014" target="R175_E0020"><data key="edge_relationship_id">R175_R0025</data><data key="edge_source_entity_id">R175_E0014</data><data key="edge_relationship_type">has_signature_metadata</data><data key="edge_target_entity_id">R175_E0020</data><data key="edge_operational_context">Electronic MA-416 sign-and-save populates specialty/date</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0026" source="R175_E0014" target="R175_E0022"><data key="edge_relationship_id">R175_R0026</data><data key="edge_source_entity_id">R175_E0014</data><data key="edge_relationship_type">bounded_by</data><data key="edge_target_entity_id">R175_E0022</data><data key="edge_operational_context">Medical Advisor signed analysis must not be mistaken for medical portion signoff</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0027" source="APP_DCPS" target="R175_E0021"><data key="edge_relationship_id">R175_R0027</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">supports_assessment_revision</data><data key="edge_target_entity_id">R175_E0021</data><data key="edge_operational_context">Unsign revise re-sign signed assessment prior to closure</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0028" source="R175_E0023" target="REPO_CEF"><data key="edge_relationship_id">R175_R0028</data><data key="edge_source_entity_id">R175_E0023</data><data key="edge_relationship_type">places_scanned_document_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Paper medical assessment wet-signed by MC/PC scanned into CEF</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0029" source="R175_E0024" target="REPO_CEF"><data key="edge_relationship_id">R175_R0029</data><data key="edge_source_entity_id">R175_E0024</data><data key="edge_relationship_type">governs_scanned_medical_evidence_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Scanned tracing acceptable if gridlines and scale viewable</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0030" source="FORM_R105_SSA416" target="R175_E0025"><data key="edge_relationship_id">R175_R0030</data><data key="edge_source_entity_id">FORM_R105_SSA416</data><data key="edge_relationship_type">has_documented_name_variation</data><data key="edge_target_entity_id">R175_E0025</data><data key="edge_operational_context">Title Medical Evaluation and legacy Case Analysis wording</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R175_R0031" source="APP_DCPS" target="R175_E0014"><data key="edge_relationship_id">R175_R0031</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">captures_medical_advisor_evaluation</data><data key="edge_target_entity_id">R175_E0014</data><data key="edge_operational_context">MA signs MA-416 in DCPS; not a generic shared repository for all consultants</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0032" source="REPO_CEF" target="R175_E0021"><data key="edge_relationship_id">R175_R0032</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">provides_imaged_evidence_for</data><data key="edge_target_entity_id">R175_E0021</data><data key="edge_operational_context">MC and PC examine CEF and may need to revise signed assessment</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0033" source="APP_EVIEW" target="R175_E0026"><data key="edge_relationship_id">R175_R0033</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">enforces_request_type_limit</data><data key="edge_target_entity_id">R175_E0026</data><data key="edge_operational_context">Five request types for one DEQY invocation</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0034" source="QRY_DEQY" target="R175_E0027"><data key="edge_relationship_id">R175_R0034</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">exposes_query_option</data><data key="edge_target_entity_id">R175_E0027</data><data key="edge_operational_context">Request type 8 employer address</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0035" source="QRY_DEQY" target="R175_E0028"><data key="edge_relationship_id">R175_R0035</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">exposes_query_option</data><data key="edge_target_entity_id">R175_E0028</data><data key="edge_operational_context">Request type 9 last employer address</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0036" source="R175_E0027" target="R175_E0026"><data key="edge_relationship_id">R175_R0036</data><data key="edge_source_entity_id">R175_E0027</data><data key="edge_relationship_type">is_governed_by</data><data key="edge_target_entity_id">R175_E0026</data><data key="edge_operational_context">Employer address selection one of at most five query codes</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0037" source="R175_E0028" target="R175_E0026"><data key="edge_relationship_id">R175_R0037</data><data key="edge_source_entity_id">R175_E0028</data><data key="edge_relationship_type">is_governed_by</data><data key="edge_target_entity_id">R175_E0026</data><data key="edge_operational_context">Last-employer address selection one of at most five</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0038" source="APP_EVIEW" target="R175_E0029"><data key="edge_relationship_id">R175_R0038</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">supports_query_save_process</data><data key="edge_target_entity_id">R175_E0029</data><data key="edge_operational_context">eView query button saves to case e-folder</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0039" source="R175_E0029" target="REPO_EF"><data key="edge_relationship_id">R175_R0039</data><data key="edge_source_entity_id">R175_E0029</data><data key="edge_relationship_type">stores_case_query_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">eView saves return to the electronic folder case documents</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0040" source="QRY_DEQY" target="R175_E0029"><data key="edge_relationship_id">R175_R0040</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">uses_save_action</data><data key="edge_target_entity_id">R175_E0029</data><data key="edge_operational_context">DEQY can be saved to EF</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0041" source="QRY_SEQY" target="R175_E0029"><data key="edge_relationship_id">R175_R0041</data><data key="edge_source_entity_id">QRY_SEQY</data><data key="edge_relationship_type">uses_save_action</data><data key="edge_target_entity_id">R175_E0029</data><data key="edge_operational_context">SEQY can be saved to EF</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0042" source="APP_EVIEW" target="R175_E0030"><data key="edge_relationship_id">R175_R0042</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">governed_by_query_access_control</data><data key="edge_target_entity_id">R175_E0030</data><data key="edge_operational_context">User profiles restrict query functionality</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0043" source="TECH_PCOM" target="R175_E0031"><data key="edge_relationship_id">R175_R0043</data><data key="edge_source_entity_id">TECH_PCOM</data><data key="edge_relationship_type">exposes_query_route</data><data key="edge_target_entity_id">R175_E0031</data><data key="edge_operational_context">PCOM MFQM option 9</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0044" source="R175_E0031" target="QRY_DEQY"><data key="edge_relationship_id">R175_R0044</data><data key="edge_source_entity_id">R175_E0031</data><data key="edge_relationship_type">requests_query</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">MFQM code 9 invokes DEQY</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0045" source="QRY_DEQY" target="R175_E0032"><data key="edge_relationship_id">R175_R0045</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">has_vocational_evidence_limit</data><data key="edge_target_entity_id">R175_E0032</data><data key="edge_operational_context">Wage/employer facts do not establish job duties</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0046" source="QRY_SEQY" target="R175_E0032"><data key="edge_relationship_id">R175_R0046</data><data key="edge_source_entity_id">QRY_SEQY</data><data key="edge_relationship_type">has_vocational_evidence_limit</data><data key="edge_target_entity_id">R175_E0032</data><data key="edge_operational_context">Year and wage only do not establish work performed</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0047" source="SYS_MEF" target="R175_E0033"><data key="edge_relationship_id">R175_R0047</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">is_documented_source_for</data><data key="edge_target_entity_id">R175_E0033</data><data key="edge_operational_context">One of two documented DEQY extract sources</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0048" source="DB_EIF" target="R175_E0033"><data key="edge_relationship_id">R175_R0048</data><data key="edge_source_entity_id">DB_EIF</data><data key="edge_relationship_type">is_documented_source_for</data><data key="edge_target_entity_id">R175_E0033</data><data key="edge_operational_context">Employer Identification File contributes employer attributes</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0049" source="R175_E0033" target="QRY_DEQY"><data key="edge_relationship_id">R175_R0049</data><data key="edge_source_entity_id">R175_E0033</data><data key="edge_relationship_type">is_used_to_answer</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">DEQY printout displays data extracted from MEF and EIF</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0050" source="APP_DMS" target="R175_E0035"><data key="edge_relationship_id">R175_R0050</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">documents_repayment_contact_with</data><data key="edge_target_entity_id">R175_E0035</data><data key="edge_operational_context">DMS Remarks (RMKS) screen stores caller-conversation results</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0051" source="R175_E0035" target="UI_DMS_RMKS"><data key="edge_relationship_id">R175_R0051</data><data key="edge_source_entity_id">R175_E0035</data><data key="edge_relationship_type">is_entered_on</data><data key="edge_target_entity_id">UI_DMS_RMKS</data><data key="edge_operational_context">Policy specifies DMS RMKS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0052" source="APP_MSSICS" target="R175_E0036"><data key="edge_relationship_id">R175_R0052</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">supports_installment_recovery_decision</data><data key="edge_target_entity_id">R175_E0036</data><data key="edge_operational_context">Title XVI G TAC Recover by Installments through UOPD</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0053" source="R175_E0036" target="R155_E0014"><data key="edge_relationship_id">R175_R0053</data><data key="edge_source_entity_id">R175_E0036</data><data key="edge_relationship_type">is_entered_on</data><data key="edge_target_entity_id">R155_E0014</data><data key="edge_operational_context">Existing catalog contains UOPD decision screen</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0054" source="APP_DMS" target="R160_E0005"><data key="edge_relationship_id">R175_R0054</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">processes_titleii_installment_via</data><data key="edge_target_entity_id">R160_E0005</data><data key="edge_operational_context">Title II installment enters DRIN screen</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0055" source="R175_E0037" target="R175_E0036"><data key="edge_relationship_id">R175_R0055</data><data key="edge_source_entity_id">R175_E0037</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R175_E0036</data><data key="edge_operational_context">SSI installment negotiation order also applies Title II</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0056" source="R175_E0038" target="APP_DMS"><data key="edge_relationship_id">R175_R0056</data><data key="edge_source_entity_id">R175_E0038</data><data key="edge_relationship_type">applies_to_delinquent_debts_tracked_by</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Separate TOP/credit criteria and remittance default controls</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0057" source="APP_ECO" target="R175_E0038"><data key="edge_relationship_id">R175_R0057</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">is_subject_to_collection_condition</data><data key="edge_target_entity_id">R175_E0038</data><data key="edge_operational_context">External collection referrals contingent on debt and default/notice criteria</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0058" source="R175_E0034" target="R175_E0039"><data key="edge_relationship_id">R175_R0058</data><data key="edge_source_entity_id">R175_E0034</data><data key="edge_relationship_type">restricted_by</data><data key="edge_target_entity_id">R175_E0039</data><data key="edge_operational_context">Remittance-only post-office box not address for correspondence</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0059" source="R175_E0040" target="R175_E0037"><data key="edge_relationship_id">R175_R0059</data><data key="edge_source_entity_id">R175_E0040</data><data key="edge_relationship_type">escalates_to</data><data key="edge_target_entity_id">R175_E0037</data><data key="edge_operational_context">Beyond six months due date requires installments rather than delayed full refund</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0060" source="R175_E0041" target="R175_E0038"><data key="edge_relationship_id">R175_R0060</data><data key="edge_source_entity_id">R175_E0041</data><data key="edge_relationship_type">limits_collection_under</data><data key="edge_target_entity_id">R175_E0038</data><data key="edge_operational_context">TOP and credit reporting depend on due process and criteria</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R175_R0061" source="APP_DMS" target="R175_E0034"><data key="edge_relationship_id">R175_R0061</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">has_remittance_destination</data><data key="edge_target_entity_id">R175_E0034</data><data key="edge_operational_context">Payment P.O. box is administrative destination and not an individual address</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0001" source="R176_GAO_CROSSWALK" target="R176_GAO_SSA_BD"><data key="edge_relationship_id">R176_R0001</data><data key="edge_source_entity_id">R176_GAO_CROSSWALK</data><data key="edge_relationship_type">crosswalk_identifies_anonymized_system</data><data key="edge_target_entity_id">R176_GAO_SSA_BD</data><data key="edge_operational_context">GAO Table 10 matches SSA anonymous identifiers across 2019 and 2025; no specific functional system identification follows.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0002" source="R176_GAO_CROSSWALK" target="R176_GAO_SSA_BE"><data key="edge_relationship_id">R176_R0002</data><data key="edge_source_entity_id">R176_GAO_CROSSWALK</data><data key="edge_relationship_type">crosswalk_identifies_anonymized_system</data><data key="edge_target_entity_id">R176_GAO_SSA_BE</data><data key="edge_operational_context">GAO Table 10 matches SSA anonymous identifiers across 2019 and 2025; no specific functional system identification follows.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0003" source="R176_GAO_CROSSWALK" target="R176_GAO_SSA_BF"><data key="edge_relationship_id">R176_R0003</data><data key="edge_source_entity_id">R176_GAO_CROSSWALK</data><data key="edge_relationship_type">crosswalk_identifies_anonymized_system</data><data key="edge_target_entity_id">R176_GAO_SSA_BF</data><data key="edge_operational_context">GAO Table 10 matches SSA anonymous identifiers across 2019 and 2025; no specific functional system identification follows.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0004" source="APP_SSI_REDET" target="R176_RZ_NO_PAYMENT_UPDATE"><data key="edge_relationship_id">R176_R0004</data><data key="edge_source_entity_id">APP_SSI_REDET</data><data key="edge_relationship_type">requires_address_phone_update_even_if_no_payment_change</data><data key="edge_target_entity_id">R176_RZ_NO_PAYMENT_UPDATE</data><data key="edge_operational_context">Section B requires changed address/phone forwarded despite unchanged benefits.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0005" source="R176_RZ_NO_PAYMENT_UPDATE" target="SYS_SSR"><data key="edge_relationship_id">R176_R0005</data><data key="edge_source_entity_id">R176_RZ_NO_PAYMENT_UPDATE</data><data key="edge_relationship_type">updates_ssr_after_development</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR fields are updated through SSA-1719B or MSSICS BTS; not automatic on allegations alone.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0006" source="FORM_SSA1719B" target="R176_RZ_1719B_TRANSMIT"><data key="edge_relationship_id">R176_R0006</data><data key="edge_source_entity_id">FORM_SSA1719B</data><data key="edge_relationship_type">implements_redetermination_posteligibility_transmission</data><data key="edge_target_entity_id">R176_RZ_1719B_TRANSMIT</data><data key="edge_operational_context">Paper RZ data including CG or remarks and corrections transmitted using SSA-1719B.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0007" source="R176_RZ_1719B_TRANSMIT" target="SYS_SSR"><data key="edge_relationship_id">R176_R0007</data><data key="edge_source_entity_id">R176_RZ_1719B_TRANSMIT</data><data key="edge_relationship_type">transmits_confirmed_attributes_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA-1719B SSI data input route to SSR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0008" source="APP_MSSICS" target="R176_RZ_BTS_TRANSMIT"><data key="edge_relationship_id">R176_R0008</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">performs_build_transaction_ssr_redetermination</data><data key="edge_target_entity_id">R176_RZ_BTS_TRANSMIT</data><data key="edge_operational_context">MSSICS BTS records confirmed information changes in SSR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0009" source="R176_RZ_BTS_TRANSMIT" target="SYS_SSR"><data key="edge_relationship_id">R176_R0009</data><data key="edge_source_entity_id">R176_RZ_BTS_TRANSMIT</data><data key="edge_relationship_type">transmits_confirmed_attributes_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">MSSICS BTS record transmission to SSR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0010" source="APP_SSI_REDET" target="R176_RZ_VP_REJECT"><data key="edge_relationship_id">R176_R0010</data><data key="edge_source_entity_id">APP_SSI_REDET</data><data key="edge_relationship_type">subject_to_pending_priority_diary_reject</data><data key="edge_target_entity_id">R176_RZ_VP_REJECT</data><data key="edge_operational_context">Pending SSR priority diary triggers VP reject on RZ clearance.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0011" source="R176_RZ_VP_REJECT" target="SYS_SSR"><data key="edge_relationship_id">R176_R0011</data><data key="edge_source_entity_id">R176_RZ_VP_REJECT</data><data key="edge_relationship_type">requires_clearance_of_ssr_priority_diary</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Clear the outstanding priority diary before completing an RZ.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0012" source="FORM_SSA1719B" target="R176_RZ_RC_SUPPORT"><data key="edge_relationship_id">R176_R0012</data><data key="edge_source_entity_id">FORM_SSA1719B</data><data key="edge_relationship_type">requires_change_documentation</data><data key="edge_target_entity_id">R176_RZ_RC_SUPPORT</data><data key="edge_operational_context">Report of Contact supports amended item, date, reason, effect.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0013" source="APP_SSI_REDET" target="R176_RZ_RETRO_CONSOLIDATE"><data key="edge_relationship_id">R176_R0013</data><data key="edge_source_entity_id">APP_SSI_REDET</data><data key="edge_relationship_type">requires_retroactive_input_consolidation</data><data key="edge_target_entity_id">R176_RZ_RETRO_CONSOLIDATE</data><data key="edge_operational_context">Finish issue development before changes; avoid fragmented inputs.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0014" source="APP_SSI_REDET" target="R176_RZ_FINAL_COMPLETION"><data key="edge_relationship_id">R176_R0014</data><data key="edge_source_entity_id">APP_SSI_REDET</data><data key="edge_relationship_type">requires_final_redetermination_completion_entry</data><data key="edge_target_entity_id">R176_RZ_FINAL_COMPLETION</data><data key="edge_operational_context">Final transaction closes RZ via SSA-1719B or MSSICS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0015" source="R176_RZ_FINAL_COMPLETION" target="APP_MSSICS"><data key="edge_relationship_id">R176_R0015</data><data key="edge_source_entity_id">R176_RZ_FINAL_COMPLETION</data><data key="edge_relationship_type">may_be_sent_from</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Final SSI RZ closing event can be sent by MSSICS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0016" source="APP_SSI_REDET" target="R176_RZ_HOUSEHOLD_THIRD_PARTY"><data key="edge_relationship_id">R176_R0016</data><data key="edge_source_entity_id">APP_SSI_REDET</data><data key="edge_relationship_type">produces_other_recipient_third_party_lead</data><data key="edge_target_entity_id">R176_RZ_HOUSEHOLD_THIRD_PARTY</data><data key="edge_operational_context">Household member income or composition fact must be developed for different recipient.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0017" source="R176_RZ_HOUSEHOLD_THIRD_PARTY" target="SYS_SSR"><data key="edge_relationship_id">R176_R0017</data><data key="edge_source_entity_id">R176_RZ_HOUSEHOLD_THIRD_PARTY</data><data key="edge_relationship_type">requires_development_before_other_ssr_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">A third-party household report does not itself authorize automatic other-recipient SSR update.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0018" source="R176_RZ_WBDOC_FO" target="APP_MSSICS"><data key="edge_relationship_id">R176_R0018</data><data key="edge_source_entity_id">R176_RZ_WBDOC_FO</data><data key="edge_relationship_type">preferentially_processed_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">WBDOC electronic RZ referred to FO is preferentially completed in MSSICS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0019" source="APP_SSI_REDET" target="R176_RZ_WBDOC_FO"><data key="edge_relationship_id">R176_R0019</data><data key="edge_source_entity_id">APP_SSI_REDET</data><data key="edge_relationship_type">uses_wbdoc_to_field_office_route</data><data key="edge_target_entity_id">R176_RZ_WBDOC_FO</data><data key="edge_operational_context">RZ transfers WBDOC to servicing FO.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0020" source="APP_SSI_REDET" target="R176_RZ_FI_PERMISSION"><data key="edge_relationship_id">R176_R0020</data><data key="edge_source_entity_id">APP_SSI_REDET</data><data key="edge_relationship_type">requires_scope_based_financial_institution_permission</data><data key="edge_target_entity_id">R176_RZ_FI_PERMISSION</data><data key="edge_operational_context">FO RZ and WBDOC transfer permission required; WBDOC-completed RZ differs.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0021" source="R176_DOWR_MONTH" target="DATA_COA_INET"><data key="edge_relationship_id">R176_R0021</data><data key="edge_source_entity_id">R176_DOWR_MONTH</data><data key="edge_relationship_type">defines_monthly_reporting_period_for</data><data key="edge_target_entity_id">DATA_COA_INET</data><data key="edge_operational_context">SSA COA online-applications open data defines Month according to DOWR administrative monthly periods; not necessarily calendar months.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0022" source="R176_DOWR_MONTH" target="DATA_DOWR"><data key="edge_relationship_id">R176_R0022</data><data key="edge_source_entity_id">R176_DOWR_MONTH</data><data key="edge_relationship_type">governs_annual_office_reporting_periods_in</data><data key="edge_target_entity_id">DATA_DOWR</data><data key="edge_operational_context">SSA explicitly defines DOWR month in the COA dataset as an administratively set office-workload reporting interval.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0023" source="R176_DOWR_MONTH" target="DATA_DD_INET"><data key="edge_relationship_id">R176_R0023</data><data key="edge_source_entity_id">R176_DOWR_MONTH</data><data key="edge_relationship_type">defines_monthly_reporting_period_for</data><data key="edge_target_entity_id">DATA_DD_INET</data><data key="edge_operational_context">SSA direct-deposit online-applications dataset also reports by administratively set DOWR Month.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0024" source="R176_UAS459" target="R176_UAS_MYSSA_NOTE"><data key="edge_relationship_id">R176_R0024</data><data key="edge_source_entity_id">R176_UAS459</data><data key="edge_relationship_type">provides_survey_data_for</data><data key="edge_target_entity_id">R176_UAS_MYSSA_NOTE</data><data key="edge_operational_context">SSA 2026 note derives estimates from UAS 459 survey 2022-2024, not from SSA online application log data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0025" source="R176_UAS459" target="R176_UAS_MYSSA_SELFREPORT"><data key="edge_relationship_id">R176_R0025</data><data key="edge_source_entity_id">R176_UAS459</data><data key="edge_relationship_type">contains_self_report_measure</data><data key="edge_target_entity_id">R176_UAS_MYSSA_SELFREPORT</data><data key="edge_operational_context">UAS asks respondents about self-reported mySSA awareness, registration and willingness.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0026" source="R176_UAS_MYSSA_SELFREPORT" target="APP_MYSSA"><data key="edge_relationship_id">R176_R0026</data><data key="edge_source_entity_id">R176_UAS_MYSSA_SELFREPORT</data><data key="edge_relationship_type">evaluates_user_reported_engagement_with</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Respondent-reported portal enrollment does not prove any automated integration or data matching with SSA mySSA operational database.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0027" source="R176_UAS_MYSSA_NOTE" target="APP_MYSSA"><data key="edge_relationship_id">R176_R0027</data><data key="edge_source_entity_id">R176_UAS_MYSSA_NOTE</data><data key="edge_relationship_type">publishes_estimates_about</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Policy analysis of public awareness, not operational account traffic.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0028" source="R176_CPU" target="R176_PAYEE_REMOTE_WSU_CPU"><data key="edge_relationship_id">R176_R0028</data><data key="edge_source_entity_id">R176_CPU</data><data key="edge_relationship_type">supports_limited_remote_payee_interview_exception</data><data key="edge_target_entity_id">R176_PAYEE_REMOTE_WSU_CPU</data><data key="edge_operational_context">Special WSU/CPU custodial parent/spouse exception to in-person SSA-11 interview.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0029" source="ORG_WSU" target="R176_PAYEE_REMOTE_WSU_CPU"><data key="edge_relationship_id">R176_R0029</data><data key="edge_source_entity_id">ORG_WSU</data><data key="edge_relationship_type">supports_limited_remote_payee_interview_exception</data><data key="edge_target_entity_id">R176_PAYEE_REMOTE_WSU_CPU</data><data key="edge_operational_context">Workload Support Units covered for qualifying custodial parent or spouse.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0030" source="R176_PAYEE_REMOTE_WSU_CPU" target="APP_ERPS"><data key="edge_relationship_id">R176_R0030</data><data key="edge_source_entity_id">R176_PAYEE_REMOTE_WSU_CPU</data><data key="edge_relationship_type">is_recorded_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">eRPS applicant interview mode and proof-of-identity screens record qualifying telephone/video interviews; Numident identity verification when applicable.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0031" source="R176_PAYEE_APPLICANT_HAS_PAYEE" target="APP_ERPS"><data key="edge_relationship_id">R176_R0031</data><data key="edge_source_entity_id">R176_PAYEE_APPLICANT_HAS_PAYEE</data><data key="edge_relationship_type">requires_applicant_nonselection_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">No exceptions for applicant who currently has own representative payee; record non-selection in eRPS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R176_R0032" source="R176_PUPS_OFFENSE_LIMIT" target="APP_ERPS"><data key="edge_relationship_id">R176_R0032</data><data key="edge_source_entity_id">R176_PUPS_OFFENSE_LIMIT</data><data key="edge_relationship_type">limits_criminal_suitability_conclusions_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">PUPS alone provides incarceration dates not crime name, and staff develop offense before suitability decision.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R177_REL0001" source="SYS_SSR" target="DATA_DISABILITY_RESEARCH_FILE"><data key="edge_relationship_id">R177_REL0001</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">base_administrative_record_for</data><data key="edge_target_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_operational_context">2026 SSI report Title XVI Disability Research File SSR is base file</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">2026 SSI report Title XVI Disability Research File SSR is base file</data></edge><edge id="R177_REL0002" source="R177_SDR" target="DATA_DISABILITY_RESEARCH_FILE"><data key="edge_relationship_id">R177_REL0002</data><data key="edge_source_entity_id">R177_SDR</data><data key="edge_relationship_type">named_administrative_input_to</data><data key="edge_target_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_operational_context">SSI application/appeal longitudinal research file uses SDR records</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSI application/appeal longitudinal research file uses SDR records</data></edge><edge id="R177_REL0003" source="R128_E007" target="DATA_DISABILITY_RESEARCH_FILE"><data key="edge_relationship_id">R177_REL0003</data><data key="edge_source_entity_id">R128_E007</data><data key="edge_relationship_type">provides_initial_determination_transactions_for</data><data key="edge_target_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_operational_context">SSA-831 determination records matched to Title XVI longitudinal file</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-831 determination records matched to Title XVI longitudinal file</data></edge><edge id="R177_REL0004" source="R177_T16_DRF_SSN_INPUT" target="DATA_DISABILITY_RESEARCH_FILE"><data key="edge_relationship_id">R177_REL0004</data><data key="edge_source_entity_id">R177_T16_DRF_SSN_INPUT</data><data key="edge_relationship_type">named_identity_source_for</data><data key="edge_target_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_operational_context">SSN identification record data used for research-file matching; technical system not named</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSN identification record data used for research-file matching; technical system not named</data></edge><edge id="R177_REL0005" source="R177_T16_DRF_APPEAL_INPUT" target="DATA_DISABILITY_RESEARCH_FILE"><data key="edge_relationship_id">R177_REL0005</data><data key="edge_source_entity_id">R177_T16_DRF_APPEAL_INPUT</data><data key="edge_relationship_type">provides_appeal_records_for</data><data key="edge_target_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_operational_context">Hearing and Appeals Council information matched into SSI research cohort</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Hearing and Appeals Council information matched into SSI research cohort</data></edge><edge id="R177_REL0006" source="R177_T16_DRF_PRODUCTION" target="DATA_DISABILITY_RESEARCH_FILE"><data key="edge_relationship_id">R177_REL0006</data><data key="edge_source_entity_id">R177_T16_DRF_PRODUCTION</data><data key="edge_relationship_type">constructs_annually</data><data key="edge_target_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_operational_context">SSA Disability Policy performs 200-step annual construction in 2-4 months</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Disability Policy performs 200-step annual construction in 2-4 months</data></edge><edge id="R177_REL0007" source="R177_T16_DRF_PRODUCTION" target="R177_T16_DRF_COHORT"><data key="edge_relationship_id">R177_REL0007</data><data key="edge_source_entity_id">R177_T16_DRF_PRODUCTION</data><data key="edge_relationship_type">applies_filing_cohort_reconciliation</data><data key="edge_target_entity_id">R177_T16_DRF_COHORT</data><data key="edge_operational_context">Historical filing-date alignment across data with inconsistent filing-date availability</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Historical filing-date alignment across data with inconsistent filing-date availability</data></edge><edge id="R177_REL0008" source="R177_T16_DRF_COHORT" target="DATA_DISABILITY_RESEARCH_FILE"><data key="edge_relationship_id">R177_REL0008</data><data key="edge_source_entity_id">R177_T16_DRF_COHORT</data><data key="edge_relationship_type">governs_cohort_structure_of</data><data key="edge_target_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_operational_context">Recent three yearly cohorts from current source data; earlier updated over time</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Recent three yearly cohorts from current source data; earlier updated over time</data></edge><edge id="R177_REL0009" source="R177_T16_DRF_2025_EST" target="R177_OACT_SSI26_VC1"><data key="edge_relationship_id">R177_REL0009</data><data key="edge_source_entity_id">R177_T16_DRF_2025_EST</data><data key="edge_relationship_type">substitutes_provisionally_for_cohort_in</data><data key="edge_target_entity_id">R177_OACT_SSI26_VC1</data><data key="edge_operational_context">2025 adult application cohort uses estimates through January 2026</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">2025 adult application cohort uses estimates through January 2026</data></edge><edge id="R177_REL0010" source="R177_T16_DRF_2025_EST" target="R177_OACT_SSI26_VC2"><data key="edge_relationship_id">R177_REL0010</data><data key="edge_source_entity_id">R177_T16_DRF_2025_EST</data><data key="edge_relationship_type">substitutes_provisionally_for_cohort_in</data><data key="edge_target_entity_id">R177_OACT_SSI26_VC2</data><data key="edge_operational_context">2025 child application cohort uses estimates through January 2026</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">2025 child application cohort uses estimates through January 2026</data></edge><edge id="R177_REL0011" source="R177_T16_DRF_2025_EST" target="R177_T16_DRF_PERSON_CLAIM_BIAS"><data key="edge_relationship_id">R177_REL0011</data><data key="edge_source_entity_id">R177_T16_DRF_2025_EST</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R177_T16_DRF_PERSON_CLAIM_BIAS</data><data key="edge_operational_context">Claimant-based appeals source can undercount individual claim events</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Claimant-based appeals source can undercount individual claim events</data></edge><edge id="R177_REL0012" source="DATA_DISABILITY_RESEARCH_FILE" target="R177_OACT_SSI26_VC1"><data key="edge_relationship_id">R177_REL0012</data><data key="edge_source_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_relationship_type">supports_publication_of</data><data key="edge_target_entity_id">R177_OACT_SSI26_VC1</data><data key="edge_operational_context">Longitudinal research records underpin SSI adult applications-by-filing-year table</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Longitudinal research records underpin SSI adult applications-by-filing-year table</data></edge><edge id="R177_REL0013" source="DATA_DISABILITY_RESEARCH_FILE" target="R177_OACT_SSI26_VC2"><data key="edge_relationship_id">R177_REL0013</data><data key="edge_source_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_relationship_type">supports_publication_of</data><data key="edge_target_entity_id">R177_OACT_SSI26_VC2</data><data key="edge_operational_context">Longitudinal research records underpin SSI child applications-by-filing-year table</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Longitudinal research records underpin SSI child applications-by-filing-year table</data></edge><edge id="R177_REL0014" source="R177_T16_DRF_PRODUCTION" target="R177_SDR"><data key="edge_relationship_id">R177_REL0014</data><data key="edge_source_entity_id">R177_T16_DRF_PRODUCTION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R177_SDR</data><data key="edge_operational_context">Named source SDR; no asserted replication or hosting</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Named source SDR; no asserted replication or hosting</data></edge><edge id="R177_REL0015" source="R177_T16_DRF_PRODUCTION" target="SYS_SSR"><data key="edge_relationship_id">R177_REL0015</data><data key="edge_source_entity_id">R177_T16_DRF_PRODUCTION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Named source SSR is base of Title XVI disability research file</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Named source SSR is base of Title XVI disability research file</data></edge><edge id="R177_REL0016" source="R177_T16_DRF_PRODUCTION" target="R177_T16_DRF_APPEAL_INPUT"><data key="edge_relationship_id">R177_REL0016</data><data key="edge_source_entity_id">R177_T16_DRF_PRODUCTION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R177_T16_DRF_APPEAL_INPUT</data><data key="edge_operational_context">Named source: hearing and appeals council information</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Named source: hearing and appeals council information</data></edge><edge id="R177_REL0017" source="FORM_SS5" target="R177_SS5_PARENT_SSNS"><data key="edge_relationship_id">R177_REL0017</data><data key="edge_source_entity_id">FORM_SS5</data><data key="edge_relationship_type">collects_conditional</data><data key="edge_target_entity_id">R177_SS5_PARENT_SSNS</data><data key="edge_operational_context">Parent identifiers on child original/new SSN applications under age 18</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Parent identifiers on child original/new SSN applications under age 18</data></edge><edge id="R177_REL0018" source="R177_SS5_PARENT_SSNS" target="R177_SS5_PARENT_IRS_REPORT"><data key="edge_relationship_id">R177_REL0018</data><data key="edge_source_entity_id">R177_SS5_PARENT_SSNS</data><data key="edge_relationship_type">furnished_to</data><data key="edge_target_entity_id">R177_SS5_PARENT_IRS_REPORT</data><data key="edge_operational_context">Parent SSNs are reportable under PL105-34; transport not documented</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Parent SSNs are reportable under PL105-34; transport not documented</data></edge><edge id="R177_REL0019" source="R177_SS5_PARENT_IRS_REPORT" target="ORG_IRS"><data key="edge_relationship_id">R177_REL0019</data><data key="edge_source_entity_id">R177_SS5_PARENT_IRS_REPORT</data><data key="edge_relationship_type">has_authorized_recipient</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SSA supplies parents SSNs for applicable child SSN applications to IRS under statute</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA supplies parents SSNs for applicable child SSN applications to IRS under statute</data></edge><edge id="R177_REL0020" source="APP_SSNAP" target="R177_SS5_PARENT_VERIFY_GATE"><data key="edge_relationship_id">R177_REL0020</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">enforces_parent_match_rule</data><data key="edge_target_entity_id">R177_SS5_PARENT_VERIFY_GATE</data><data key="edge_operational_context">SSNAP compares parental SSN and NAA/NL2 in Numident</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSNAP compares parental SSN and NAA/NL2 in Numident</data></edge><edge id="R177_REL0021" source="R177_SS5_PARENT_VERIFY_GATE" target="SYS_NUMIDENT"><data key="edge_relationship_id">R177_REL0021</data><data key="edge_source_entity_id">R177_SS5_PARENT_VERIFY_GATE</data><data key="edge_relationship_type">checks_identity_fields_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">NAA or NL2 name in any parent Numident iteration</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">NAA or NL2 name in any parent Numident iteration</data></edge><edge id="R177_REL0022" source="R177_SS5_PARENT_VERIFY_GATE" target="R177_SS5_PARENT_SUSPECT"><data key="edge_relationship_id">R177_REL0022</data><data key="edge_source_entity_id">R177_SS5_PARENT_VERIFY_GATE</data><data key="edge_relationship_type">may_trigger</data><data key="edge_target_entity_id">R177_SS5_PARENT_SUSPECT</data><data key="edge_operational_context">Unresolved bad parental SSN verification produces suspect application status</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Unresolved bad parental SSN verification produces suspect application status</data></edge><edge id="R177_REL0023" source="R177_SS5_PARENT_SUSPECT" target="WORK_SSNAP_SUSPECT_HOLD"><data key="edge_relationship_id">R177_REL0023</data><data key="edge_source_entity_id">R177_SS5_PARENT_SUSPECT</data><data key="edge_relationship_type">uses_work_control</data><data key="edge_target_entity_id">WORK_SSNAP_SUSPECT_HOLD</data><data key="edge_operational_context">SSNAP suspect status after failed parent ID verification, file-level structure not asserted</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSNAP suspect status after failed parent ID verification, file-level structure not asserted</data></edge><edge id="R177_REL0024" source="APP_SSNAP" target="R177_SS5_PARENT_PRINT_HIDE"><data key="edge_relationship_id">R177_REL0024</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">applies_print_privacy_control</data><data key="edge_target_entity_id">R177_SS5_PARENT_PRINT_HIDE</data><data key="edge_operational_context">Hide SSN on printed application for identified nonapplicant parent</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Hide SSN on printed application for identified nonapplicant parent</data></edge><edge id="R177_REL0025" source="R177_SS5_PARENT_NO_SSN_EXCEPTION" target="UI_SSNAP_ADDITIONAL_INFO"><data key="edge_relationship_id">R177_REL0025</data><data key="edge_source_entity_id">R177_SS5_PARENT_NO_SSN_EXCEPTION</data><data key="edge_relationship_type">can_be_recorded_on</data><data key="edge_target_entity_id">UI_SSNAP_ADDITIONAL_INFO</data><data key="edge_operational_context">Policy exceptions entered with Unknown SSN or None field</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Policy exceptions entered with Unknown SSN or None field</data></edge><edge id="R177_REL0026" source="APP_SSNAP" target="R177_SS5_PARENT_NOTIFY_ASSIGNED"><data key="edge_relationship_id">R177_REL0026</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">can_generate</data><data key="edge_target_entity_id">R177_SS5_PARENT_NOTIFY_ASSIGNED</data><data key="edge_operational_context">Notify office when parents original SSN assigned first, before child application</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Notify office when parents original SSN assigned first, before child application</data></edge><edge id="R177_REL0027" source="R177_SS5_PARENT_ALPHIDENT" target="R177_SS5_PARENT_SSNS"><data key="edge_relationship_id">R177_REL0027</data><data key="edge_source_entity_id">R177_SS5_PARENT_ALPHIDENT</data><data key="edge_relationship_type">can_recover</data><data key="edge_target_entity_id">R177_SS5_PARENT_SSNS</data><data key="edge_operational_context">Find missing parent SSN through alphident; avoid disclosure to nonapplicant</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Find missing parent SSN through alphident; avoid disclosure to nonapplicant</data></edge><edge id="R177_REL0028" source="FORM_SSA795" target="R177_SS5_PARENT_795_SHRED"><data key="edge_relationship_id">R177_REL0028</data><data key="edge_source_entity_id">FORM_SSA795</data><data key="edge_relationship_type">can_document</data><data key="edge_target_entity_id">R177_SS5_PARENT_795_SHRED</data><data key="edge_operational_context">Paper parent SSN follow-up development; qualifying statement shredded after processing</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Paper parent SSN follow-up development; qualifying statement shredded after processing</data></edge><edge id="R177_REL0029" source="APP_SSNAP" target="R177_SS5_PARENT_NO_SSN_EXCEPTION"><data key="edge_relationship_id">R177_REL0029</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">uses_exception</data><data key="edge_target_entity_id">R177_SS5_PARENT_NO_SSN_EXCEPTION</data><data key="edge_operational_context">Recognized reasons for absent SSNs; not every missing SSN denies child number</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Recognized reasons for absent SSNs; not every missing SSN denies child number</data></edge><edge id="R177_REL0030" source="R177_SS5_PARENT_VERIFY_GATE" target="DATA_NUMIDENT_PARENT_NAME"><data key="edge_relationship_id">R177_REL0030</data><data key="edge_source_entity_id">R177_SS5_PARENT_VERIFY_GATE</data><data key="edge_relationship_type">may_require_correcting</data><data key="edge_target_entity_id">DATA_NUMIDENT_PARENT_NAME</data><data key="edge_operational_context">If submitted parent name correct but absent from NAA/NL2, documented Numident correction precedes child application</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">If submitted parent name correct but absent from NAA/NL2, documented Numident correction precedes child application</data></edge><edge id="R177_REL0031" source="APP_CPMS" target="R177_ALJ_FY26_AUG_XML"><data key="edge_relationship_id">R177_REL0031</data><data key="edge_source_entity_id">APP_CPMS</data><data key="edge_relationship_type">supplies_raw_admin_disposition_data_for</data><data key="edge_target_entity_id">R177_ALJ_FY26_AUG_XML</data><data key="edge_operational_context">2026 SSA public page explicitly names CPMS raw source</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">2026 SSA public page explicitly names CPMS raw source</data></edge><edge id="R177_REL0032" source="R177_ALJ_CPMS_RAW_LINEAGE" target="R177_ALJ_FY26_AUG_XML"><data key="edge_relationship_id">R177_REL0032</data><data key="edge_source_entity_id">R177_ALJ_CPMS_RAW_LINEAGE</data><data key="edge_relationship_type">explains</data><data key="edge_target_entity_id">R177_ALJ_FY26_AUG_XML</data><data key="edge_operational_context">Raw CPMS data are not the complete application population</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Raw CPMS data are not the complete application population</data></edge><edge id="R177_REL0033" source="R177_ALJ_FY26_AUG_XML" target="R177_ALJ_MULTIOFFICE_RULE"><data key="edge_relationship_id">R177_REL0033</data><data key="edge_source_entity_id">R177_ALJ_FY26_AUG_XML</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R177_ALJ_MULTIOFFICE_RULE</data><data key="edge_operational_context">ALJs work across hearing offices; disposition office not claimant domicile</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">ALJs work across hearing offices; disposition office not claimant domicile</data></edge><edge id="R177_REL0034" source="R177_ALJ_FY26_AUG_XML" target="R177_ALJ_WORKTIME_CAVEAT"><data key="edge_relationship_id">R177_REL0034</data><data key="edge_source_entity_id">R177_ALJ_FY26_AUG_XML</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R177_ALJ_WORKTIME_CAVEAT</data><data key="edge_operational_context">Unadjusted counts are not productivity estimates correcting for non-hearing assignments</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Unadjusted counts are not productivity estimates correcting for non-hearing assignments</data></edge><edge id="R177_REL0035" source="DATA_OHO_WORKLOAD_PUBLIC" target="R177_OHO_NET_RECEIPTS_RULE"><data key="edge_relationship_id">R177_REL0035</data><data key="edge_source_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R177_OHO_NET_RECEIPTS_RULE</data><data key="edge_operational_context">Negative receipt counts arise when transfers out exceed new receipts</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Negative receipt counts arise when transfers out exceed new receipts</data></edge><edge id="R177_REL0036" source="R177_ALJ_FY26_AUG_XML" target="APP_CPMS"><data key="edge_relationship_id">R177_REL0036</data><data key="edge_source_entity_id">R177_ALJ_FY26_AUG_XML</data><data key="edge_relationship_type">is_monthly_publication_snapshot_of</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">2025-09-27 to 2026-08-28 reporting period with XML download</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">2025-09-27 to 2026-08-28 reporting period with XML download</data></edge><edge id="R177_REL0037" source="ORG_USPS" target="R177_SSI_UNDELIV_MAIL_ADDRESS_LEAD"><data key="edge_relationship_id">R177_REL0037</data><data key="edge_source_entity_id">ORG_USPS</data><data key="edge_relationship_type">returns_undeliverable_notice_as_lead_for</data><data key="edge_target_entity_id">R177_SSI_UNDELIV_MAIL_ADDRESS_LEAD</data><data key="edge_operational_context">USPS returned correspondence begins FO address-development process</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">USPS returned correspondence begins FO address-development process</data></edge><edge id="R177_REL0038" source="R177_SSI_UNDELIV_MAIL_ADDRESS_LEAD" target="PROC_T16_UNDELIV_ADDRESS"><data key="edge_relationship_id">R177_REL0038</data><data key="edge_source_entity_id">R177_SSI_UNDELIV_MAIL_ADDRESS_LEAD</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_operational_context">FO must locate individual and develop whether mailing or residence changes</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">FO must locate individual and develop whether mailing or residence changes</data></edge><edge id="R177_REL0039" source="R177_SSI_UNDELIV_MAIL_ADDRESS_LEAD" target="DOC_SSI_UNDELIVERABLE_COVER_LETTER"><data key="edge_relationship_id">R177_REL0039</data><data key="edge_source_entity_id">R177_SSI_UNDELIV_MAIL_ADDRESS_LEAD</data><data key="edge_relationship_type">may_cause_reissue_with</data><data key="edge_target_entity_id">DOC_SSI_UNDELIVERABLE_COVER_LETTER</data><data key="edge_operational_context">Appeal-rights re-mailing can include undeliverable cover letter</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Appeal-rights re-mailing can include undeliverable cover letter</data></edge><edge id="R177_REL0040" source="R177_SSI_UNDELIV_APPEAL_SERVICE" target="DOC_SSI_UNDELIVERABLE_COVER_LETTER"><data key="edge_relationship_id">R177_REL0040</data><data key="edge_source_entity_id">R177_SSI_UNDELIV_APPEAL_SERVICE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DOC_SSI_UNDELIVERABLE_COVER_LETTER</data><data key="edge_operational_context">Specified appeal-response protection when notice returned and re-served</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Specified appeal-response protection when notice returned and re-served</data></edge><edge id="R177_REL0041" source="R177_SSI_RETURNED_DECEASED_NOTICE" target="PROC_T16_UNDELIV_ADDRESS"><data key="edge_relationship_id">R177_REL0041</data><data key="edge_source_entity_id">R177_SSI_RETURNED_DECEASED_NOTICE</data><data key="edge_relationship_type">is_triaged_separately_during</data><data key="edge_target_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_operational_context">Deceased marking follows separate death-report procedure; not confirmed death status</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Deceased marking follows separate death-report procedure; not confirmed death status</data></edge><edge id="R177_REL0042" source="R177_SSI_FO_RETURN_ADDRESS" target="PROC_T16_UNDELIV_ADDRESS"><data key="edge_relationship_id">R177_REL0042</data><data key="edge_source_entity_id">R177_SSI_FO_RETURN_ADDRESS</data><data key="edge_relationship_type">is_return_address_for</data><data key="edge_target_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_operational_context">SSI undeliverable notice returns to servicing FO rather than central office</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSI undeliverable notice returns to servicing FO rather than central office</data></edge><edge id="R178_REL0001" source="R178_E0001" target="R178_E0005"><data key="edge_relationship_id">R178_REL0001</data><data key="edge_source_entity_id">R178_E0001</data><data key="edge_relationship_type">produced</data><data key="edge_target_entity_id">R178_E0005</data><data key="edge_operational_context">2008 initiative recommendations were assessed obsolete in June 2011</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0002" source="R178_E0002" target="R178_E0003"><data key="edge_relationship_id">R178_REL0002</data><data key="edge_source_entity_id">R178_E0002</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R178_E0003</data><data key="edge_operational_context">September 2013 inventory identified exchange supporting systems and participating entities</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0003" source="R178_E0002" target="R178_E0004"><data key="edge_relationship_id">R178_REL0003</data><data key="edge_source_entity_id">R178_E0002</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R178_E0004</data><data key="edge_operational_context">September 2013 inventory supported workload and request-type reports</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0004" source="R178_E0006" target="R178_E0007"><data key="edge_relationship_id">R178_REL0004</data><data key="edge_source_entity_id">R178_E0006</data><data key="edge_relationship_type">preceded</data><data key="edge_target_entity_id">R178_E0007</data><data key="edge_operational_context">2007 plan predated 2015 enterprise architecture road map</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0005" source="R178_E0007" target="R178_E0009"><data key="edge_relationship_id">R178_REL0005</data><data key="edge_source_entity_id">R178_E0007</data><data key="edge_relationship_type">has_documented_gap</data><data key="edge_target_entity_id">R178_E0009</data><data key="edge_operational_context">2016 GAO follow-up found comprehensive gap analysis still missing</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0006" source="R178_E0010" target="R178_E0007"><data key="edge_relationship_id">R178_REL0006</data><data key="edge_source_entity_id">R178_E0010</data><data key="edge_relationship_type">recommended_for</data><data key="edge_target_entity_id">R178_E0007</data><data key="edge_operational_context">GAO sought SOA roadmap and formal enterprise gap analysis; proposal, not confirmed implemented architecture</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R178_REL0007" source="R178_E0011" target="R178_E0012"><data key="edge_relationship_id">R178_REL0007</data><data key="edge_source_entity_id">R178_E0011</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R178_E0012</data><data key="edge_operational_context">SSA investment review board approved projects undergo quality-assurance reviews</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0008" source="R178_E0012" target="R178_E0013"><data key="edge_relationship_id">R178_REL0008</data><data key="edge_source_entity_id">R178_E0012</data><data key="edge_relationship_type">enforces</data><data key="edge_target_entity_id">R178_E0013</data><data key="edge_operational_context">QA noncompliance leads to corrective action plan documentation within five business days</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0009" source="R178_E0012" target="R178_E0014"><data key="edge_relationship_id">R178_REL0009</data><data key="edge_source_entity_id">R178_E0012</data><data key="edge_relationship_type">reviewed</data><data key="edge_target_entity_id">R178_E0014</data><data key="edge_operational_context">GAO identified actual QA review for mandatory multifactor authentication project in 2016</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0010" source="R178_E0015" target="PROC_PIR"><data key="edge_relationship_id">R178_REL0010</data><data key="edge_source_entity_id">R178_E0015</data><data key="edge_relationship_type">instance_of</data><data key="edge_target_entity_id">PROC_PIR</data><data key="edge_operational_context">June 2016 mySSA 1099 review was a postimplementation review</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0011" source="R178_E0015" target="APP_MYSSA"><data key="edge_relationship_id">R178_REL0011</data><data key="edge_source_entity_id">R178_E0015</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Historical mySSA 1099 project review, not proof of its internal infrastructure</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0012" source="R178_E0016" target="R157_ORG_NORTHROP"><data key="edge_relationship_id">R178_REL0012</data><data key="edge_source_entity_id">R178_E0016</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">R157_ORG_NORTHROP</data><data key="edge_operational_context">Northrop Grumman awarded SS00-10-60082 September 10 2010</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0013" source="R178_E0016" target="R178_E0017"><data key="edge_relationship_id">R178_REL0013</data><data key="edge_source_entity_id">R178_E0016</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R178_E0017</data><data key="edge_operational_context">SSA 2010 contract includes firm-fixed-price and time-and-materials task orders</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0014" source="R178_E0018" target="R178_E0019"><data key="edge_relationship_id">R178_REL0014</data><data key="edge_source_entity_id">R178_E0018</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R178_E0019</data><data key="edge_operational_context">Service channel metrics use incompatible transaction/visit/call counting units</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0015" source="R178_E0018" target="R178_E0020"><data key="edge_relationship_id">R178_REL0015</data><data key="edge_source_entity_id">R178_E0018</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R178_E0020</data><data key="edge_operational_context">Historical online replacement SSN card channel metrics</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0016" source="R178_E0018" target="R178_E0021"><data key="edge_relationship_id">R178_REL0016</data><data key="edge_source_entity_id">R178_E0018</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R178_E0021</data><data key="edge_operational_context">Historical initial disability filing channel metrics</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0017" source="R178_E0018" target="DATA_N8NN_CALL_VOLUME_BUSY"><data key="edge_relationship_id">R178_REL0017</data><data key="edge_source_entity_id">R178_E0018</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">DATA_N8NN_CALL_VOLUME_BUSY</data><data key="edge_operational_context">SSAB cited SSA National 800 Number Call Volume and Agent Busy Rate data among source materials</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0018" source="R178_E0020" target="APP_ISSNRC"><data key="edge_relationship_id">R178_REL0018</data><data key="edge_source_entity_id">R178_E0020</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">APP_ISSNRC</data><data key="edge_operational_context">Historical 2016 introduction of internet SSN replacement card channel</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0019" source="R178_E0022" target="R178_E0023"><data key="edge_relationship_id">R178_REL0019</data><data key="edge_source_entity_id">R178_E0022</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R178_E0023</data><data key="edge_operational_context">Historic field-office count definition and reference-date changes</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0020" source="R178_E0022" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R178_REL0020</data><data key="edge_source_entity_id">R178_E0022</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">Counts are administrative historical office observations, not current live location status</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0021" source="R178_E0024" target="R178_E0025"><data key="edge_relationship_id">R178_REL0021</data><data key="edge_source_entity_id">R178_E0024</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R178_E0025</data><data key="edge_operational_context">New recipient table 3 covers any recipient paid during calendar year</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0022" source="R178_E0024" target="R178_E0026"><data key="edge_relationship_id">R178_REL0022</data><data key="edge_source_entity_id">R178_E0024</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R178_E0026</data><data key="edge_operational_context">Terminations Table 77 publication series restarted at 2006 due revised method</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0023" source="R178_E0027" target="R178_E0028"><data key="edge_relationship_id">R178_REL0023</data><data key="edge_source_entity_id">R178_E0027</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R178_E0028</data><data key="edge_operational_context">2009 report explains 100-percent file and award definition changes in its series</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0024" source="R178_E0027" target="R178_E0029"><data key="edge_relationship_id">R178_REL0024</data><data key="edge_source_entity_id">R178_E0027</data><data key="edge_relationship_type">excluded</data><data key="edge_target_entity_id">R178_E0029</data><data key="edge_operational_context">SIPP-based estimates removed due attrition and low linkage match rates</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0025" source="R178_E0030" target="R178_E0029"><data key="edge_relationship_id">R178_REL0025</data><data key="edge_source_entity_id">R178_E0030</data><data key="edge_relationship_type">responds_to</data><data key="edge_target_entity_id">R178_E0029</data><data key="edge_operational_context">ORES commissioned Census interviews to improve SIPP-based estimates following degraded sample/match quality</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0026" source="R178_E0030" target="ORG_SSA_ORES"><data key="edge_relationship_id">R178_REL0026</data><data key="edge_source_entity_id">R178_E0030</data><data key="edge_relationship_type">commissioned_by</data><data key="edge_target_entity_id">ORG_SSA_ORES</data><data key="edge_operational_context">SSA Office of Research Evaluation and Statistics contracted with Census Bureau</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0027" source="R178_E0030" target="ORG_CENSUS"><data key="edge_relationship_id">R178_REL0027</data><data key="edge_source_entity_id">R178_E0030</data><data key="edge_relationship_type">conducted_by</data><data key="edge_target_entity_id">ORG_CENSUS</data><data key="edge_operational_context">Census Bureau performed specialized SIPP-based interview for disability beneficiaries</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0028" source="R178_E0027" target="R178_E0031"><data key="edge_relationship_id">R178_REL0028</data><data key="edge_source_entity_id">R178_E0027</data><data key="edge_relationship_type">has_correction</data><data key="edge_target_entity_id">R178_E0031</data><data key="edge_operational_context">Table 25 corrected January 2010; Table 58 corrected May 2011</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0029" source="SYS_SSR" target="R178_E0032"><data key="edge_relationship_id">R178_REL0029</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">represented_in</data><data key="edge_target_entity_id">R178_E0032</data><data key="edge_operational_context">2008 Fast Facts identifies SSR Characteristic Record Extract statistical format</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0030" source="R178_E0032" target="R178_E0033"><data key="edge_relationship_id">R178_REL0030</data><data key="edge_source_entity_id">R178_E0032</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">R178_E0033</data><data key="edge_operational_context">2007 SSI/OASDI dual-program unduplicated estimate from MBR plus SSR CRE</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0031" source="SYS_MBR" target="R178_E0033"><data key="edge_relationship_id">R178_REL0031</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">R178_E0033</data><data key="edge_operational_context">2007 unduplicated beneficiary population combines MBR with SSI SSR CRE</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0032" source="R178_E0032" target="R178_E0034"><data key="edge_relationship_id">R178_REL0032</data><data key="edge_source_entity_id">R178_E0032</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R178_E0034</data><data key="edge_operational_context">Historical average SSI payment metric excludes retroactive payments</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0033" source="R178_E0035" target="R178_E0036"><data key="edge_relationship_id">R178_REL0033</data><data key="edge_source_entity_id">R178_E0035</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R178_E0036</data><data key="edge_operational_context">Publication duty ended after FY2011</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0034" source="R178_E0037" target="R178_E0038"><data key="edge_relationship_id">R178_REL0034</data><data key="edge_source_entity_id">R178_E0037</data><data key="edge_relationship_type">has_correction</data><data key="edge_target_entity_id">R178_E0038</data><data key="edge_operational_context">2011 edition web data corrected many years after publication</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0035" source="R178_E0039" target="R178_E0040"><data key="edge_relationship_id">R178_REL0035</data><data key="edge_source_entity_id">R178_E0039</data><data key="edge_relationship_type">distributes</data><data key="edge_target_entity_id">R178_E0040</data><data key="edge_operational_context">2012 SSAB chartbook provides companion spreadsheet of data used</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R178_REL0036" source="R178_E0033" target="R178_E0041"><data key="edge_relationship_id">R178_REL0036</data><data key="edge_source_entity_id">R178_E0033</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R178_E0041</data><data key="edge_operational_context">OASDI+SSI combined count avoids double counting dual recipients</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R179_REL0001" source="FAC_SSC" target="R179_E0001"><data key="edge_relationship_id">R179_REL0001</data><data key="edge_source_entity_id">FAC_SSC</data><data key="edge_relationship_type">hosted_historical_workload</data><data key="edge_target_entity_id">R179_E0001</data><data key="edge_operational_context">By May 2009 SSC maintained medical images for electronic disability folders; no assertion for current hosting.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0002" source="R179_E0001" target="DB_EDIB_CLAIM_FILE"><data key="edge_relationship_id">R179_REL0002</data><data key="edge_source_entity_id">R179_E0001</data><data key="edge_relationship_type">stores_historical_data_for</data><data key="edge_target_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_operational_context">The images were maintained for electronic disability folders; claim-file entity is logical crosswalk, exact physical tables unspecified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0003" source="FAC_SSC" target="R179_E0002"><data key="edge_relationship_id">R179_REL0003</data><data key="edge_source_entity_id">FAC_SSC</data><data key="edge_relationship_type">historically_provided</data><data key="edge_target_entity_id">R179_E0002</data><data key="edge_operational_context">Redundant SSC paths to field offices, Internet, and NCC in 2009.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0004" source="R179_E0002" target="FAC_NCC"><data key="edge_relationship_id">R179_REL0004</data><data key="edge_source_entity_id">R179_E0002</data><data key="edge_relationship_type">connected_to_historical</data><data key="edge_target_entity_id">FAC_NCC</data><data key="edge_operational_context">SSCs redundant communications connected to the NCC in 2009.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0005" source="FAC_NCC" target="R179_E0003"><data key="edge_relationship_id">R179_REL0005</data><data key="edge_source_entity_id">FAC_NCC</data><data key="edge_relationship_type">historical_disaster_recovery_fallback</data><data key="edge_target_entity_id">R179_E0003</data><data key="edge_operational_context">The commercial hot site represented a 7-day limited-capacity recovery of NCC critical workloads in 2009.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0006" source="FAC_SSC" target="R179_E0004"><data key="edge_relationship_id">R179_REL0006</data><data key="edge_source_entity_id">FAC_SSC</data><data key="edge_relationship_type">was_planned_to_support</data><data key="edge_target_entity_id">R179_E0004</data><data key="edge_operational_context">2009 forward-looking goal for SSC and NCC hourly synchronization and 24-hour recovery, not completed implementation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0007" source="R179_E0004" target="FAC_NCC"><data key="edge_relationship_id">R179_REL0007</data><data key="edge_source_entity_id">R179_E0004</data><data key="edge_relationship_type">planned_replication_with</data><data key="edge_target_entity_id">FAC_NCC</data><data key="edge_operational_context">Proposed hourly synchronization between centers by 2012, actual implementation unverified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0008" source="FAC_NSC" target="R179_E0005"><data key="edge_relationship_id">R179_REL0008</data><data key="edge_source_entity_id">FAC_NSC</data><data key="edge_relationship_type">planned_interoperability_control</data><data key="edge_target_entity_id">R179_E0005</data><data key="edge_operational_context">NSC migration site sought a location within 40 miles and under 100km distance to support dependent case-processing systems.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0009" source="R179_E0005" target="FAC_NCC"><data key="edge_relationship_id">R179_REL0009</data><data key="edge_source_entity_id">R179_E0005</data><data key="edge_relationship_type">governed_transition_from</data><data key="edge_target_entity_id">FAC_NCC</data><data key="edge_operational_context">Historical migration requirement, not proof of specific replicated database or current transport.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0010" source="FAC_SSC" target="R179_E0006"><data key="edge_relationship_id">R179_REL0010</data><data key="edge_source_entity_id">FAC_SSC</data><data key="edge_relationship_type">historically_demonstrated</data><data key="edge_target_entity_id">R179_E0006</data><data key="edge_operational_context">The OIG compared actual historical test recovery times in 2009 and 2010, distinct from 2009 planned one-day objective.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0011" source="R179_E0006" target="R179_E0004"><data key="edge_relationship_id">R179_REL0011</data><data key="edge_source_entity_id">R179_E0006</data><data key="edge_relationship_type">measured_against_planned_goal</data><data key="edge_target_entity_id">R179_E0004</data><data key="edge_operational_context">2010 tested recovery under five days did not demonstrate the 2012 one-day goal.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0012" source="R179_E0007" target="TECH_LINUX"><data key="edge_relationship_id">R179_REL0012</data><data key="edge_source_entity_id">R179_E0007</data><data key="edge_relationship_type">tested_technology</data><data key="edge_target_entity_id">TECH_LINUX</data><data key="edge_operational_context">2015 Linux pilot documented as historical report, not present-day coverage.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0013" source="R179_E0008" target="TECH_LINUX"><data key="edge_relationship_id">R179_REL0013</data><data key="edge_source_entity_id">R179_E0008</data><data key="edge_relationship_type">targeted_technology</data><data key="edge_target_entity_id">TECH_LINUX</data><data key="edge_operational_context">Linux was intended target platform in a reported middle-tier migration plan.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0014" source="R179_E0011" target="EX_EAB"><data key="edge_relationship_id">R179_REL0014</data><data key="edge_source_entity_id">R179_E0011</data><data key="edge_relationship_type">historically_governed</data><data key="edge_target_entity_id">EX_EAB</data><data key="edge_operational_context">Each participating jurisdiction furnished birth registration data under a per-record arrangement as described in 2011.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0015" source="R179_E0012" target="SYS_NUMIDENT"><data key="edge_relationship_id">R179_REL0015</data><data key="edge_source_entity_id">R179_E0012</data><data key="edge_relationship_type">can_affect_historical_status_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSN-holder record work classification could lag changed DHS authorization until an SSA-processed update; no automated DHS→Numident path established.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0016" source="R179_E0013" target="R179_E0012"><data key="edge_relationship_id">R179_REL0016</data><data key="edge_source_entity_id">R179_E0013</data><data key="edge_relationship_type">proposed_to_remediate</data><data key="edge_target_entity_id">R179_E0012</data><data key="edge_operational_context">Discussions about potential DHS feeds were exploratory in 2011 and do not confirm automatic update of Numident.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0017" source="R179_E0014" target="SYS_NUMIDENT"><data key="edge_relationship_id">R179_REL0017</data><data key="edge_source_entity_id">R179_E0014</data><data key="edge_relationship_type">historically_determined_part_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSN geographical numbering relationship before randomization; mailing location at application time is not a current residence.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0018" source="PLAT_EDIB" target="R179_E0015"><data key="edge_relationship_id">R179_REL0018</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">historically_included_component_or_control</data><data key="edge_target_entity_id">R179_E0015</data><data key="edge_operational_context">Net-new PIA control or activity; historical context, not current system-deployment assertion.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0019" source="PLAT_EDIB" target="R179_E0016"><data key="edge_relationship_id">R179_REL0019</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">historically_included_component_or_control</data><data key="edge_target_entity_id">R179_E0016</data><data key="edge_operational_context">Net-new PIA control or activity; historical context, not current system-deployment assertion.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0020" source="APP_CFRMS" target="R179_E0015"><data key="edge_relationship_id">R179_REL0020</data><data key="edge_source_entity_id">APP_CFRMS</data><data key="edge_relationship_type">managed_ssn_exclusion_control</data><data key="edge_target_entity_id">R179_E0015</data><data key="edge_operational_context">CFRMS supports file access/destruction and maintains SSN exclusion list as separate records-management control.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0021" source="DB_ARPS_MI" target="APP_ARPS"><data key="edge_relationship_id">R179_REL0021</data><data key="edge_source_entity_id">DB_ARPS_MI</data><data key="edge_relationship_type">reported_workloads_from</data><data key="edge_target_entity_id">APP_ARPS</data><data key="edge_operational_context">ARPS MI supports Appeals Council and court workload monitoring.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0022" source="DB_CPMS_MI" target="APP_CPMS"><data key="edge_relationship_id">R179_REL0022</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">reported_workloads_from</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">CPMS MI supports office/regional/national hearing workload reporting.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0023" source="R179_E0016" target="APP_NDDSS"><data key="edge_relationship_id">R179_REL0023</data><data key="edge_source_entity_id">R179_E0016</data><data key="edge_relationship_type">daily_source</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_operational_context">Disability Database System extracts initial and CDR cases daily from NDDS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0024" source="R179_E0016" target="DB_DISABILITY_DATABASE_SYSTEM"><data key="edge_relationship_id">R179_REL0024</data><data key="edge_source_entity_id">R179_E0016</data><data key="edge_relationship_type">provided_records_to</data><data key="edge_target_entity_id">DB_DISABILITY_DATABASE_SYSTEM</data><data key="edge_operational_context">Extract data feed into Disability Database System; weekly determinations from OHO and Wilkes-Barre described without exact source system.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0025" source="APP_FECS" target="DB_ERE_MI"><data key="edge_relationship_id">R179_REL0025</data><data key="edge_source_entity_id">APP_FECS</data><data key="edge_relationship_type">historically_supplied_medical_submission_counts_to</data><data key="edge_target_entity_id">DB_ERE_MI</data><data key="edge_operational_context">PIA says each DDS/OHO Front End Capture System server contributed counts to ERE MI.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0026" source="REPO_DMA_ECLIENT" target="DB_EDIB_CLAIM_FILE"><data key="edge_relationship_id">R179_REL0026</data><data key="edge_source_entity_id">REPO_DMA_ECLIENT</data><data key="edge_relationship_type">supported_historical_electronic_file</data><data key="edge_target_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_operational_context">eClient contains images and multimedia for eDIB cases; no claim it is current sole repository.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0027" source="PLAT_EDIB" target="DATA_EDIB_ADDR_CHANGE_REPORT"><data key="edge_relationship_id">R179_REL0027</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">historically_maintained_separate_address_reports</data><data key="edge_target_entity_id">DATA_EDIB_ADDR_CHANGE_REPORT</data><data key="edge_operational_context">The 2018 PIA mentions separate post-adjudicative address-report files; it does not establish automatic update to MBR, SSR or Numident.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0028" source="PLAT_EDIB" target="R179_E0017"><data key="edge_relationship_id">R179_REL0028</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">historically_collected_third_party_information</data><data key="edge_target_entity_id">R179_E0017</data><data key="edge_operational_context">The source identifies third-party IRS information in eDIB generally; whether addresses were included and whether persisted is unknown.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0029" source="R179_E0018" target="R179_E0019"><data key="edge_relationship_id">R179_REL0029</data><data key="edge_source_entity_id">R179_E0018</data><data key="edge_relationship_type">supplies_demographic_inputs_to</data><data key="edge_target_entity_id">R179_E0019</data><data key="edge_operational_context">2010 model graph demography→economics</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0030" source="R179_E0018" target="R179_E0020"><data key="edge_relationship_id">R179_REL0030</data><data key="edge_source_entity_id">R179_E0018</data><data key="edge_relationship_type">supplies_demographic_inputs_to</data><data key="edge_target_entity_id">R179_E0020</data><data key="edge_operational_context">2010 model graph demography→beneficiaries</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0031" source="R179_E0019" target="R179_E0020"><data key="edge_relationship_id">R179_REL0031</data><data key="edge_source_entity_id">R179_E0019</data><data key="edge_relationship_type">supplies_economic_inputs_to</data><data key="edge_target_entity_id">R179_E0020</data><data key="edge_operational_context">2010 model graph economics→beneficiaries</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0032" source="R179_E0018" target="R179_E0021"><data key="edge_relationship_id">R179_REL0032</data><data key="edge_source_entity_id">R179_E0018</data><data key="edge_relationship_type">supplies_demographic_inputs_to</data><data key="edge_target_entity_id">R179_E0021</data><data key="edge_operational_context">2010 model graph demography→trust fund</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0033" source="R179_E0019" target="R179_E0021"><data key="edge_relationship_id">R179_REL0033</data><data key="edge_source_entity_id">R179_E0019</data><data key="edge_relationship_type">supplies_economic_inputs_to</data><data key="edge_target_entity_id">R179_E0021</data><data key="edge_operational_context">2010 model graph economics→trust fund</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0034" source="R179_E0020" target="R179_E0021"><data key="edge_relationship_id">R179_REL0034</data><data key="edge_source_entity_id">R179_E0020</data><data key="edge_relationship_type">supplies_beneficiary_inputs_to</data><data key="edge_target_entity_id">R179_E0021</data><data key="edge_operational_context">2010 model graph beneficiaries→trust fund</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0035" source="R179_E0022" target="R179_E0018"><data key="edge_relationship_id">R179_REL0035</data><data key="edge_source_entity_id">R179_E0022</data><data key="edge_relationship_type">historically_provided_inputs_to</data><data key="edge_target_entity_id">R179_E0018</data><data key="edge_operational_context">Mortality probabilities estimated by demographic process</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0036" source="R179_E0023" target="R179_E0018"><data key="edge_relationship_id">R179_REL0036</data><data key="edge_source_entity_id">R179_E0023</data><data key="edge_relationship_type">historically_provided_inputs_to</data><data key="edge_target_entity_id">R179_E0018</data><data key="edge_operational_context">Birth rates estimated by demographic process</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0037" source="R179_E0025" target="R179_E0019"><data key="edge_relationship_id">R179_REL0037</data><data key="edge_source_entity_id">R179_E0025</data><data key="edge_relationship_type">historically_provided_inputs_to</data><data key="edge_target_entity_id">R179_E0019</data><data key="edge_operational_context">BLS employment input to economics model</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0038" source="R179_E0024" target="R179_E0019"><data key="edge_relationship_id">R179_REL0038</data><data key="edge_source_entity_id">R179_E0024</data><data key="edge_relationship_type">historically_provided_inputs_to</data><data key="edge_target_entity_id">R179_E0019</data><data key="edge_operational_context">BEA NIPA input to economics model</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0039" source="R179_E0018" target="R179_E0029"><data key="edge_relationship_id">R179_REL0039</data><data key="edge_source_entity_id">R179_E0018</data><data key="edge_relationship_type">produced_historical_output</data><data key="edge_target_entity_id">R179_E0029</data><data key="edge_operational_context">SSA-area population projection by age sex marital status</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0040" source="R179_E0027" target="R179_E0026"><data key="edge_relationship_id">R179_REL0040</data><data key="edge_source_entity_id">R179_E0027</data><data key="edge_relationship_type">provides_awards_sample_to</data><data key="edge_target_entity_id">R179_E0026</data><data key="edge_operational_context">Selected 225465 record MBR sample used by AWARDS</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0041" source="R179_E0028" target="R179_E0026"><data key="edge_relationship_id">R179_REL0041</data><data key="edge_source_entity_id">R179_E0028</data><data key="edge_relationship_type">provides_earnings_patterns_to</data><data key="edge_target_entity_id">R179_E0026</data><data key="edge_operational_context">CWHS information and MEF-posted covered earnings assist forecasting</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0042" source="R179_E0026" target="R179_E0030"><data key="edge_relationship_id">R179_REL0042</data><data key="edge_source_entity_id">R179_E0026</data><data key="edge_relationship_type">historically_produced</data><data key="edge_target_entity_id">R179_E0030</data><data key="edge_operational_context">Projected AIME distributions for new entitlement</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0043" source="R179_E0030" target="R179_E0021"><data key="edge_relationship_id">R179_REL0043</data><data key="edge_source_entity_id">R179_E0030</data><data key="edge_relationship_type">historically_inputs_benefit_projections</data><data key="edge_target_entity_id">R179_E0021</data><data key="edge_operational_context">Projected AIME distributions feed actuarial benefit payment calculations</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0044" source="R179_E0031" target="R179_E0021"><data key="edge_relationship_id">R179_REL0044</data><data key="edge_source_entity_id">R179_E0031</data><data key="edge_relationship_type">provides_railroad_interchange_data_to</data><data key="edge_target_entity_id">R179_E0021</data><data key="edge_operational_context">RRB input for trust fund railroad interchange</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0045" source="R179_E0032" target="R179_E0021"><data key="edge_relationship_id">R179_REL0045</data><data key="edge_source_entity_id">R179_E0032</data><data key="edge_relationship_type">provides_tax_benefit_input_to</data><data key="edge_target_entity_id">R179_E0021</data><data key="edge_operational_context">Treasury OTA tax on benefits assumptions</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0046" source="R179_E0021" target="R179_E0033"><data key="edge_relationship_id">R179_REL0046</data><data key="edge_source_entity_id">R179_E0021</data><data key="edge_relationship_type">historically_supported_publication</data><data key="edge_target_entity_id">R179_E0033</data><data key="edge_operational_context">Actuarial outputs underlie published long-range single-year tables</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0047" source="SYS_MBR" target="R179_E0027"><data key="edge_relationship_id">R179_REL0047</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provided_historical_awards_sample_to</data><data key="edge_target_entity_id">R179_E0027</data><data key="edge_operational_context">2010 OACT AWARDS explicitly describes newly entitled beneficiary 10% MBR sample of 225465.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0048" source="SYS_MEF" target="R179_E0027"><data key="edge_relationship_id">R179_REL0048</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">provided_historical_earnings_to</data><data key="edge_target_entity_id">R179_E0027</data><data key="edge_operational_context">Sample included historical worker taxable earnings; OACT describes MBR and MEF jointly, not single consolidated Person DB.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0049" source="R179_E0028" target="SYS_MEF"><data key="edge_relationship_id">R179_REL0049</data><data key="edge_source_entity_id">R179_E0028</data><data key="edge_relationship_type">historically_derives_earnings_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">MEF-posted earnings used with CWHS to project future distribution; nonposted suspense cannot be assumed posted.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0050" source="ORG_CMS" target="R179_E0022"><data key="edge_relationship_id">R179_REL0050</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">historically_provided_medicare_enrollment_for</data><data key="edge_target_entity_id">R179_E0022</data><data key="edge_operational_context">Mortality model used historical Medicare deaths and enrollment for mortality inputs.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0051" source="ORG_CENSUS" target="R179_E0022"><data key="edge_relationship_id">R179_REL0051</data><data key="edge_source_entity_id">ORG_CENSUS</data><data key="edge_relationship_type">historically_supported</data><data key="edge_target_entity_id">R179_E0022</data><data key="edge_operational_context">Mortality model uses resident population; Census source attribution is for population statistics rather than an address feed.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0052" source="ORG_BLS" target="R179_E0025"><data key="edge_relationship_id">R179_REL0052</data><data key="edge_source_entity_id">ORG_BLS</data><data key="edge_relationship_type">provided_historical_labor_data_to</data><data key="edge_target_entity_id">R179_E0025</data><data key="edge_operational_context">Official model documentation specifies BLS employment estimates for economics group.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0053" source="ORG_TREASURY" target="R179_E0032"><data key="edge_relationship_id">R179_REL0053</data><data key="edge_source_entity_id">ORG_TREASURY</data><data key="edge_relationship_type">historically_provided_tax_policy_inputs_to</data><data key="edge_target_entity_id">R179_E0032</data><data key="edge_operational_context">Treasury Office of Tax Analysis benefits-tax assumption family, distinct from agency payment instructions.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0054" source="R179_E0035" target="R179_E0034"><data key="edge_relationship_id">R179_REL0054</data><data key="edge_source_entity_id">R179_E0035</data><data key="edge_relationship_type">historically_blocked_unverified_changes_from</data><data key="edge_target_entity_id">R179_E0034</data><data key="edge_operational_context">Beneficiary requested block could prevent ACH auto-enrollment changes; record field and master system unspecified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0055" source="R179_E0036" target="R179_E0034"><data key="edge_relationship_id">R179_REL0055</data><data key="edge_source_entity_id">R179_E0036</data><data key="edge_relationship_type">historically_constrained</data><data key="edge_target_entity_id">R179_E0034</data><data key="edge_operational_context">2013 SSA identity verification controls applied to electronic direct-deposit changes, not necessarily every bank-origin ACH in same way.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0056" source="ORG_TREASURY" target="R179_E0037"><data key="edge_relationship_id">R179_REL0056</data><data key="edge_source_entity_id">ORG_TREASURY</data><data key="edge_relationship_type">historically_decided_exceptions_under</data><data key="edge_target_entity_id">R179_E0037</data><data key="edge_operational_context">Treasury was authority for waivers to electronic federal payments; SSA advised people to contact Treasury.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0057" source="R179_E0038" target="APP_EBB"><data key="edge_relationship_id">R179_REL0057</data><data key="edge_source_entity_id">R179_E0038</data><data key="edge_relationship_type">historically_piloted_application</data><data key="edge_target_entity_id">APP_EBB</data><data key="edge_operational_context">Three-office 2012 pilot for electronic bench book assisting ALJ analysis.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0058" source="APP_CPMS" target="R179_E0040"><data key="edge_relationship_id">R179_REL0058</data><data key="edge_source_entity_id">APP_CPMS</data><data key="edge_relationship_type">historically_automated_document_generation_through</data><data key="edge_target_entity_id">R179_E0040</data><data key="edge_operational_context">2012 testimony explicitly says Automated Noticing enabled CPMS to produce appropriate notices based on stored data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0059" source="R179_E0044" target="APP_CPMS"><data key="edge_relationship_id">R179_REL0059</data><data key="edge_source_entity_id">R179_E0044</data><data key="edge_relationship_type">historically_exposed_case_status_from</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Authorized appointed representatives received CPMS case status via self-service in 2012.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0060" source="R179_E0044" target="DB_EDIB_CLAIM_FILE"><data key="edge_relationship_id">R179_REL0060</data><data key="edge_source_entity_id">R179_E0044</data><data key="edge_relationship_type">historically_allowed_authorized_folder_access_to</data><data key="edge_target_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_operational_context">Authorized representative eFolder access documented in 2012; exact physical folder system linkage not specified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R179_REL0061" source="R179_E0043" target="R179_E0042"><data key="edge_relationship_id">R179_REL0061</data><data key="edge_source_entity_id">R179_E0043</data><data key="edge_relationship_type">historically_used_standardized_decision_templates</data><data key="edge_target_entity_id">R179_E0042</data><data key="edge_operational_context">2012 testimony documents common hearing office electronic process and FIT templates but does not detail a technical integration.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">3</data><data key="edge_notes">Documented historical relationship; no unspecified live transport, persistence, or update semantics.</data></edge><edge id="R180_REL0001" source="R180_E0002" target="R180_E0001"><data key="edge_relationship_id">R180_REL0001</data><data key="edge_source_entity_id">R180_E0002</data><data key="edge_relationship_type">supplies_address_correspondence_evidence_to</data><data key="edge_target_entity_id">R180_E0001</data><data key="edge_operational_context">IRS/SSA address observations supported Census respondent matching, not SSA program-record updates.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0002" source="SYS_NUMIDENT" target="R180_E0001"><data key="edge_relationship_id">R180_REL0002</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">supplies_application_identity_to</data><data key="edge_target_entity_id">R180_E0001</data><data key="edge_operational_context">Census uses Numident SSN application information to associate survey respondents with administrative identities.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0003" source="APP_EVS" target="R180_E0005"><data key="edge_relationship_id">R180_REL0003</data><data key="edge_source_entity_id">APP_EVS</data><data key="edge_relationship_type">historically_validates_ssn_names_for</data><data key="edge_target_entity_id">R180_E0005</data><data key="edge_operational_context">SSA Enumeration Verification System tested survey SSN, name, DOB, sex before extraction and linkage.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0004" source="R180_E0001" target="R180_E0003"><data key="edge_relationship_id">R180_REL0004</data><data key="edge_source_entity_id">R180_E0001</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R180_E0003</data><data key="edge_operational_context">Survey linkage proceeded only where the respondent did not opt out.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0005" source="R180_E0001" target="R180_E0004"><data key="edge_relationship_id">R180_REL0005</data><data key="edge_source_entity_id">R180_E0001</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R180_E0004</data><data key="edge_operational_context">Census substitutes survey identifiers for SSNs in the linked research record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0006" source="R180_E0005" target="R180_E0001"><data key="edge_relationship_id">R180_REL0006</data><data key="edge_source_entity_id">R180_E0005</data><data key="edge_relationship_type">provides_verified_data_for</data><data key="edge_target_entity_id">R180_E0001</data><data key="edge_operational_context">After matching/verification SSA extracts record for Census linkage; no physical transport asserted.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0007" source="ORG_CENSUS" target="R180_E0001"><data key="edge_relationship_id">R180_REL0007</data><data key="edge_source_entity_id">ORG_CENSUS</data><data key="edge_relationship_type">historically_performs</data><data key="edge_target_entity_id">R180_E0001</data><data key="edge_operational_context">Census described as conducting 2009 address-assisted identity matching.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0008" source="DATA_SIPP" target="R180_E0006"><data key="edge_relationship_id">R180_REL0008</data><data key="edge_source_entity_id">DATA_SIPP</data><data key="edge_relationship_type">serves_as_survey_input_to</data><data key="edge_target_entity_id">R180_E0006</data><data key="edge_operational_context">FEM uses linked SIPP data to simulate SSI rules.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0009" source="R180_E0006" target="SYS_SSR"><data key="edge_relationship_id">R180_REL0009</data><data key="edge_source_entity_id">R180_E0006</data><data key="edge_relationship_type">historically_models_benefit_rules_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">FEM models Title XVI eligibility/participation, not a program-record update.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0010" source="R180_E0007" target="ORG_CENSUS"><data key="edge_relationship_id">R180_REL0010</data><data key="edge_source_entity_id">R180_E0007</data><data key="edge_relationship_type">historically_uses_census_survey_input_from</data><data key="edge_target_entity_id">ORG_CENSUS</data><data key="edge_operational_context">MINT uses linked Census survey/SSA administrative data; exact individual survey source is not fixed in 2009 description.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0011" source="R180_E0005" target="R180_E0008"><data key="edge_relationship_id">R180_REL0011</data><data key="edge_source_entity_id">R180_E0005</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R180_E0008</data><data key="edge_operational_context">Title 13 and special Census approvals constrain access to matched data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0012" source="APP_HRS" target="R180_E0013"><data key="edge_relationship_id">R180_REL0012</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0013</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Agency Skills Inventory (ASI) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0013" source="APP_HRS" target="R180_E0014"><data key="edge_relationship_id">R180_REL0013</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0014</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Anti-Harassment and Hostile Work Environment Case Tracking System (AHWECTS) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0014" source="APP_HRS" target="R180_E0015"><data key="edge_relationship_id">R180_REL0014</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0015</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Employee Data (EEData) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0015" source="APP_HRS" target="R180_E0016"><data key="edge_relationship_id">R180_REL0015</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0016</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Equal Employment Opportunity Case Management System (EEOCMS) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0016" source="APP_HRS" target="R180_E0017"><data key="edge_relationship_id">R180_REL0016</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0017</data><data key="edge_operational_context">2017 HRS PIA explicitly lists SSA Human Resources Portal (2017) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0017" source="APP_HRS" target="R180_E0018"><data key="edge_relationship_id">R180_REL0017</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0018</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Labor Relations/Employee Relations Workload Management System (LR/ER-WMS) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0018" source="APP_HRS" target="R180_E0019"><data key="edge_relationship_id">R180_REL0018</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0019</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Minority Serving Institutions Reporting System (MSIRS) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0019" source="APP_HRS" target="R180_E0020"><data key="edge_relationship_id">R180_REL0019</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0020</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Official Union Time Tracking System (OUTTS) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0020" source="APP_HRS" target="R180_E0021"><data key="edge_relationship_id">R180_REL0020</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0021</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Performance Assessment and Communication System (PACS, HR) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0021" source="APP_HRS" target="R180_E0022"><data key="edge_relationship_id">R180_REL0021</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0022</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Payroll Operational Data Store (PayODS) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0022" source="APP_HRS" target="R180_E0023"><data key="edge_relationship_id">R180_REL0022</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0023</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Position Data Application (PDA) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0023" source="APP_HRS" target="R180_E0024"><data key="edge_relationship_id">R180_REL0023</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0024</data><data key="edge_operational_context">2017 HRS PIA explicitly lists SSA Learning Management System (2017) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0024" source="APP_HRS" target="R180_E0025"><data key="edge_relationship_id">R180_REL0024</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">included_component_in_2017_pia</data><data key="edge_target_entity_id">R180_E0025</data><data key="edge_operational_context">2017 HRS PIA explicitly lists Training Online Nomination System (TONS) as a subsystem.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0025" source="APP_HRS" target="R180_E0009"><data key="edge_relationship_id">R180_REL0025</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">historically_uses_external_payroll_processor</data><data key="edge_target_entity_id">R180_E0009</data><data key="edge_operational_context">2017 HRS PIA identifies DOI FPPS as SSA external personnel/payroll processor.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0026" source="R180_E0009" target="APP_HRS"><data key="edge_relationship_id">R180_REL0026</data><data key="edge_source_entity_id">R180_E0009</data><data key="edge_relationship_type">historically_delivered_personnel_actions_to</data><data key="edge_target_entity_id">APP_HRS</data><data key="edge_operational_context">2008 HRMIS PIA says FPPS personnel action records were delivered to SSA for HRMIS processing.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0027" source="R180_E0010" target="R180_E0009"><data key="edge_relationship_id">R180_REL0027</data><data key="edge_source_entity_id">R180_E0010</data><data key="edge_relationship_type">historically_operated</data><data key="edge_target_entity_id">R180_E0009</data><data key="edge_operational_context">DOI National Business Center processed SSA payroll/personnel actions under 2008 HRMIS PIA.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0028" source="APP_HRS" target="R180_E0011"><data key="edge_relationship_id">R180_REL0028</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">historically_contained</data><data key="edge_target_entity_id">R180_E0011</data><data key="edge_operational_context">2017 PIA lists HRODS as its HR operational database.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0029" source="R180_E0021" target="R180_E0011"><data key="edge_relationship_id">R180_REL0029</data><data key="edge_source_entity_id">R180_E0021</data><data key="edge_relationship_type">historically_updated</data><data key="edge_target_entity_id">R180_E0011</data><data key="edge_operational_context">2017 PIA explicitly states that HR PACS updates performance information to HRODS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0030" source="R180_E0012" target="APP_HRS"><data key="edge_relationship_id">R180_REL0030</data><data key="edge_source_entity_id">R180_E0012</data><data key="edge_relationship_type">historically_used_hr_personnel_data_from</data><data key="edge_target_entity_id">APP_HRS</data><data key="edge_operational_context">2008 PIA says MTAS used HRMIS employee personnel identifiers for time/attendance.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0031" source="R180_E0012" target="R180_E0009"><data key="edge_relationship_id">R180_REL0031</data><data key="edge_source_entity_id">R180_E0012</data><data key="edge_relationship_type">historically_transmitted_attendance_data_for_pay_to</data><data key="edge_target_entity_id">R180_E0009</data><data key="edge_operational_context">2008 PIA documents electronic MTAS interface to FPPS for payroll computation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0032" source="APP_HRS" target="R180_E0012"><data key="edge_relationship_id">R180_REL0032</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">historically_contained_time_and_attendance_subsystem</data><data key="edge_target_entity_id">R180_E0012</data><data key="edge_operational_context">2008 predecessor HRMIS boundary with same project identifier contained MTAS; 2017 HRS PIA does not list MTAS, so current relationship is not asserted.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0033" source="APP_HRS" target="R180_E0026"><data key="edge_relationship_id">R180_REL0033</data><data key="edge_source_entity_id">APP_HRS</data><data key="edge_relationship_type">stored_employee_contact_attribute</data><data key="edge_target_entity_id">R180_E0026</data><data key="edge_operational_context">2017 HRS PIA describes employee mailing address among personnel data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0034" source="R180_E0015" target="APP_HRS"><data key="edge_relationship_id">R180_REL0034</data><data key="edge_source_entity_id">R180_E0015</data><data key="edge_relationship_type">historically_enabled_employee_updates_to</data><data key="edge_target_entity_id">APP_HRS</data><data key="edge_operational_context">2017 PIA states EEData lets employees view and update HR records, not SSA beneficiary master records.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0035" source="R180_E0027" target="DOM_SVB"><data key="edge_relationship_id">R180_REL0035</data><data key="edge_source_entity_id">R180_E0027</data><data key="edge_relationship_type">historically_supported_program</data><data key="edge_target_entity_id">DOM_SVB</data><data key="edge_operational_context">SSIRMS boundary includes Title VIII special veterans benefits, as stated in FY07 PIA.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0036" source="R180_E0027" target="R180_E0028"><data key="edge_relationship_id">R180_REL0036</data><data key="edge_source_entity_id">R180_E0027</data><data key="edge_relationship_type">historically_maintained</data><data key="edge_target_entity_id">R180_E0028</data><data key="edge_operational_context">The FY07 application boundary had recipient address/person attributes; does not establish independent physical address store.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0037" source="R180_E0027" target="SYS_SSR"><data key="edge_relationship_id">R180_REL0037</data><data key="edge_source_entity_id">R180_E0027</data><data key="edge_relationship_type">historically_administered_data_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">PIA identifies SSI record maintenance; this is a business relationship not statement that SSIRMS=SSR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0038" source="APP_TITLE2_PIA" target="R123_E018"><data key="edge_relationship_id">R180_REL0038</data><data key="edge_source_entity_id">APP_TITLE2_PIA</data><data key="edge_relationship_type">historically_incorporated_cms_and_railroad_data_for_benefits</data><data key="edge_target_entity_id">R123_E018</data><data key="edge_operational_context">2007 PIA establishes receipt of CMS and RRB data within Title II eligibility processes, with 2017 service scope distinct.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0039" source="PROC_EDCS_MAINFRAME_PROPAGATION" target="R180_E0029"><data key="edge_relationship_id">R180_REL0039</data><data key="edge_source_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_relationship_type">uses_priority_rule</data><data key="edge_target_entity_id">R180_E0029</data><data key="edge_operational_context">POMS source precedence explicit: MCS first, then MSSICS/other available sources.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0040" source="R180_E0029" target="APP_MCS"><data key="edge_relationship_id">R180_REL0040</data><data key="edge_source_entity_id">R180_E0029</data><data key="edge_relationship_type">prioritizes_origin_system</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS case fields override alternative mainframe sources when available.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0041" source="R180_E0029" target="APP_MSSICS"><data key="edge_relationship_id">R180_REL0041</data><data key="edge_source_entity_id">R180_E0029</data><data key="edge_relationship_type">uses_fallback_origin_system</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">If no MCS claim, active MSSICS and other mainframe systems furnish EDCS claimant data.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0042" source="PROC_EDCS_MAINFRAME_PROPAGATION" target="R180_E0030"><data key="edge_relationship_id">R180_REL0042</data><data key="edge_source_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_relationship_type">subject_to_mainframe_vs_internet_overlay</data><data key="edge_target_entity_id">R180_E0030</data><data key="edge_operational_context">Mainframe data takes precedence over Internet reports at propagation even if source field empty.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0043" source="R180_E0031" target="APP_MCS"><data key="edge_relationship_id">R180_REL0043</data><data key="edge_source_entity_id">R180_E0031</data><data key="edge_relationship_type">requires_origination_update_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">To correct most propagated EDCS fields, first correct mainframe claimant data in MCS/MSSICS.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0044" source="R180_E0031" target="APP_MSSICS"><data key="edge_relationship_id">R180_REL0044</data><data key="edge_source_entity_id">R180_E0031</data><data key="edge_relationship_type">alternatively_corrects_origination_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Corrections can originate MSSICS when relevant Title XVI source.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0045" source="R180_E0031" target="APP_EDCS"><data key="edge_relationship_id">R180_REL0045</data><data key="edge_source_entity_id">R180_E0031</data><data key="edge_relationship_type">then_repropagates_into</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">After MCS/MSSICS update, reopen EDCS and trigger repropagation; no reverse EDCS master write assumed.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0046" source="R180_E0032" target="APP_EDCS"><data key="edge_relationship_id">R180_REL0046</data><data key="edge_source_entity_id">R180_E0032</data><data key="edge_relationship_type">requires_address_verification_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">When copying historic folder, staff must verify current address/telephone before relying on previous records.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0047" source="R180_E0033" target="APP_MCS"><data key="edge_relationship_id">R180_REL0047</data><data key="edge_source_entity_id">R180_E0033</data><data key="edge_relationship_type">uses_computation_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Insured status dates propagate only after MCS DIB Earnings Computation.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0048" source="R180_E0034" target="APP_EDCS"><data key="edge_relationship_id">R180_REL0048</data><data key="edge_source_entity_id">R180_E0034</data><data key="edge_relationship_type">blocks_creation_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Multiple DIB claims lead to propagation stop until MCS resolved.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0049" source="SYS_MEF" target="R180_E0035"><data key="edge_relationship_id">R180_REL0049</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">contains_historical_segment</data><data key="edge_target_entity_id">R180_E0035</data><data key="edge_operational_context">2009 SSA Bulletin identifies Detail and Summary MEF storage segments.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0050" source="SYS_MEF" target="R180_E0036"><data key="edge_relationship_id">R180_REL0050</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">contains_historical_segment</data><data key="edge_target_entity_id">R180_E0036</data><data key="edge_operational_context">2009 SSA Bulletin identifies Detail and Summary MEF storage segments.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0051" source="R180_E0035" target="R180_E0036"><data key="edge_relationship_id">R180_REL0051</data><data key="edge_source_entity_id">R180_E0035</data><data key="edge_relationship_type">historically_rolls_up_yearly_totals_to</data><data key="edge_target_entity_id">R180_E0036</data><data key="edge_operational_context">Detail posts lead to aggregated annual earnings and QCs in Summary Segment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0052" source="R180_E0037" target="SYS_NUMIDENT"><data key="edge_relationship_id">R180_REL0052</data><data key="edge_source_entity_id">R180_E0037</data><data key="edge_relationship_type">checks_person_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Name+SSN verification against Numident precedes posting to MEF.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0053" source="R180_E0037" target="R180_E0035"><data key="edge_relationship_id">R180_REL0053</data><data key="edge_source_entity_id">R180_E0037</data><data key="edge_relationship_type">allows_verified_posting_to</data><data key="edge_target_entity_id">R180_E0035</data><data key="edge_operational_context">Verified wage names and SSNs post to MEF Detail Segment.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0054" source="R180_E0037" target="DB_ESF"><data key="edge_relationship_id">R180_REL0054</data><data key="edge_source_entity_id">R180_E0037</data><data key="edge_relationship_type">routes_unmatched_earnings_to</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">Unmatched items go to Earnings Suspense File until resolved.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0055" source="R180_E0040" target="R180_E0035"><data key="edge_relationship_id">R180_REL0055</data><data key="edge_source_entity_id">R180_E0040</data><data key="edge_relationship_type">must_balance_before_earnings_posting_to</data><data key="edge_target_entity_id">R180_E0035</data><data key="edge_operational_context">Employer W-2 cumulative totals balanced against W-3 before posting.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0056" source="R180_E0041" target="R180_E0035"><data key="edge_relationship_id">R180_REL0056</data><data key="edge_source_entity_id">R180_E0041</data><data key="edge_relationship_type">appends_correction_records_in</data><data key="edge_target_entity_id">R180_E0035</data><data key="edge_operational_context">W-2c negative offset and corrected value are separate postings; do not delete prior record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0057" source="R180_E0038" target="R180_E0040"><data key="edge_relationship_id">R180_REL0057</data><data key="edge_source_entity_id">R180_E0038</data><data key="edge_relationship_type">is_employer_reported_attribute_for</data><data key="edge_target_entity_id">R180_E0040</data><data key="edge_operational_context">Employer W-2 includes employee address; no evidence it updates program master address fields.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0058" source="R180_E0039" target="R180_E0040"><data key="edge_relationship_id">R180_REL0058</data><data key="edge_source_entity_id">R180_E0039</data><data key="edge_relationship_type">is_employer_contact_attribute_for</data><data key="edge_target_entity_id">R180_E0040</data><data key="edge_operational_context">W-2 employer address separate from worker residential address.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0059" source="R180_E0042" target="SYS_MEF"><data key="edge_relationship_id">R180_REL0059</data><data key="edge_source_entity_id">R180_E0042</data><data key="edge_relationship_type">historically_derived_earnings_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">CWHS draws MEF earnings annually.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0060" source="R180_E0042" target="SYS_NUMIDENT"><data key="edge_relationship_id">R180_REL0060</data><data key="edge_source_entity_id">R180_E0042</data><data key="edge_relationship_type">historically_derived_person_demographics_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">CWHS derives sample demographic attributes from Numident.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0061" source="R180_E0042" target="SYS_MBR"><data key="edge_relationship_id">R180_REL0061</data><data key="edge_source_entity_id">R180_E0042</data><data key="edge_relationship_type">historically_derived_annual_benefits_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">CWHS combined annual benefit data from MBR.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0062" source="R180_E0042" target="R180_E0043"><data key="edge_relationship_id">R180_REL0062</data><data key="edge_source_entity_id">R180_E0042</data><data key="edge_relationship_type">historically_produced_research_file</data><data key="edge_target_entity_id">R180_E0043</data><data key="edge_operational_context">2009 SSA report describes CWHS family annual one-percent research files.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0063" source="R180_E0042" target="R180_E0044"><data key="edge_relationship_id">R180_REL0063</data><data key="edge_source_entity_id">R180_E0042</data><data key="edge_relationship_type">historically_produced_research_file</data><data key="edge_target_entity_id">R180_E0044</data><data key="edge_operational_context">2009 SSA report describes CWHS family annual one-percent research files.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0064" source="R180_E0042" target="R180_E0045"><data key="edge_relationship_id">R180_REL0064</data><data key="edge_source_entity_id">R180_E0042</data><data key="edge_relationship_type">historically_produced_research_file</data><data key="edge_target_entity_id">R180_E0045</data><data key="edge_operational_context">2009 SSA report describes CWHS family annual one-percent research files.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0065" source="R180_E0042" target="R180_E0046"><data key="edge_relationship_id">R180_REL0065</data><data key="edge_source_entity_id">R180_E0042</data><data key="edge_relationship_type">historically_produced_research_file</data><data key="edge_target_entity_id">R180_E0046</data><data key="edge_operational_context">2009 SSA report describes CWHS family annual one-percent research files.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0066" source="R180_E0046" target="R180_E0047"><data key="edge_relationship_id">R180_REL0066</data><data key="edge_source_entity_id">R180_E0046</data><data key="edge_relationship_type">included_extra_irs_provided_not_mef_persisted_fields</data><data key="edge_target_entity_id">R180_E0047</data><data key="edge_operational_context">IRS information in research snapshot includes geographic fields not retained in MEF; exact source IRS file not specified.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0067" source="R180_E0044" target="R180_E0047"><data key="edge_relationship_id">R180_REL0067</data><data key="edge_source_entity_id">R180_E0044</data><data key="edge_relationship_type">includes_geography_and_industry_metadata</data><data key="edge_target_entity_id">R180_E0047</data><data key="edge_operational_context">2009 research file includes county/state and industry classifications for worker and employer.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0068" source="APP_IAPPEALS" target="R180_E0048"><data key="edge_relationship_id">R180_REL0068</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R180_E0048</data><data key="edge_operational_context">PIA explicit restriction on re-disclosure of tax return information in internet appeals.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R180_REL0069" source="APP_IAPPEALS" target="SYS_NUMIDENT"><data key="edge_relationship_id">R180_REL0069</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">historically_used_ssn_application_data_for_verification</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">PIA states iAppeals linked newly collected authentication information with existing SSN application records; no master update.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Source describes a documented historical/administrative dependency; implementation details and current deployment not inferred.</data></edge><edge id="R181_REL0001" source="SYS_ICDB" target="R181_E001"><data key="edge_relationship_id">R181_REL0001</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">historically_has_documented_content_or_component</data><data key="edge_target_entity_id">R181_E001</data><data key="edge_operational_context">ICDB PIA specifies this shared-client record class or functional component.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0002" source="SYS_ICDB" target="R181_E002"><data key="edge_relationship_id">R181_REL0002</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">historically_has_documented_content_or_component</data><data key="edge_target_entity_id">R181_E002</data><data key="edge_operational_context">ICDB PIA specifies this shared-client record class or functional component.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0003" source="SYS_ICDB" target="R181_E003"><data key="edge_relationship_id">R181_REL0003</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">historically_has_documented_content_or_component</data><data key="edge_target_entity_id">R181_E003</data><data key="edge_operational_context">ICDB PIA specifies this shared-client record class or functional component.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0004" source="SYS_ICDB" target="R181_E004"><data key="edge_relationship_id">R181_REL0004</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">historically_has_documented_content_or_component</data><data key="edge_target_entity_id">R181_E004</data><data key="edge_operational_context">ICDB PIA specifies this shared-client record class or functional component.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0005" source="R181_E004" target="SYS_ICDB"><data key="edge_relationship_id">R181_REL0005</data><data key="edge_source_entity_id">R181_E004</data><data key="edge_relationship_type">historically_restricts_public_access_to</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">The 2007 ICDB environment is not publicly accessible and is subject to authorized-employee access.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0006" source="APP_CBSV" target="R181_E005"><data key="edge_relationship_id">R181_REL0006</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">2008_pia_describes_registration_in</data><data key="edge_target_entity_id">R181_E005</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0007" source="R181_E006" target="R181_E005"><data key="edge_relationship_id">R181_REL0007</data><data key="edge_source_entity_id">R181_E006</data><data key="edge_relationship_type">historically_authorized_cbs_verification_users_in</data><data key="edge_target_entity_id">R181_E005</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0008" source="APP_CBSV" target="R181_E007"><data key="edge_relationship_id">R181_REL0008</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">historical_pia_describes_activation_credential</data><data key="edge_target_entity_id">R181_E007</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0009" source="R181_E007" target="R181_E005"><data key="edge_relationship_id">R181_REL0009</data><data key="edge_source_entity_id">R181_E007</data><data key="edge_relationship_type">completed_access_activation_for</data><data key="edge_target_entity_id">R181_E005</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0010" source="APP_CBSV" target="R181_E008"><data key="edge_relationship_id">R181_REL0010</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">historical_pia_describes_planned_batch_submission</data><data key="edge_target_entity_id">R181_E008</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0011" source="APP_CBSV" target="R181_E009"><data key="edge_relationship_id">R181_REL0011</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">historical_pia_describes_planned_small_realtime_submission</data><data key="edge_target_entity_id">R181_E009</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0012" source="APP_CBSV" target="R181_E010"><data key="edge_relationship_id">R181_REL0012</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">historically_described_proposed_webservice</data><data key="edge_target_entity_id">R181_E010</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0013" source="APP_CBSV" target="R181_E011"><data key="edge_relationship_id">R181_REL0013</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">subject_to_requester_consent_retention</data><data key="edge_target_entity_id">R181_E011</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0014" source="APP_CBSV" target="R181_E012"><data key="edge_relationship_id">R181_REL0014</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">subject_to_consent_validity</data><data key="edge_target_entity_id">R181_E012</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0015" source="APP_CBSV" target="R181_E013"><data key="edge_relationship_id">R181_REL0015</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">subject_to_redisclosure_restriction</data><data key="edge_target_entity_id">R181_E013</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0016" source="R181_E005" target="PLAT_BSO"><data key="edge_relationship_id">R181_REL0016</data><data key="edge_source_entity_id">R181_E005</data><data key="edge_relationship_type">part_of_historical_requester_registration</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0017" source="R181_E008" target="PLAT_BSO"><data key="edge_relationship_id">R181_REL0017</data><data key="edge_source_entity_id">R181_E008</data><data key="edge_relationship_type">historical_pia_describes_access_via</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0018" source="R181_E009" target="PLAT_BSO"><data key="edge_relationship_id">R181_REL0018</data><data key="edge_source_entity_id">R181_E009</data><data key="edge_relationship_type">historical_pia_describes_access_via</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0019" source="R181_E007" target="ORG_USPS"><data key="edge_relationship_id">R181_REL0019</data><data key="edge_source_entity_id">R181_E007</data><data key="edge_relationship_type">historical_pia_describes_planned_postal_delivery</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">2008 CBSV PIA documents this registration, access, consent, or transmission rule. No current configuration or Numident write behavior is implied.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0020" source="APP_800_CLAIMS" target="R181_E014"><data key="edge_relationship_id">R181_REL0020</data><data key="edge_source_entity_id">APP_800_CLAIMS</data><data key="edge_relationship_type">2008_pia_describes_use_of_claim_confirmation</data><data key="edge_target_entity_id">R181_E014</data><data key="edge_operational_context">2008 National 800-Number Claims Status PIA expressly documents the identity check, claims lookup, mailing route or ephemeral storage; this is not a persistent identity record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0021" source="APP_800_CLAIMS" target="R181_E015"><data key="edge_relationship_id">R181_REL0021</data><data key="edge_source_entity_id">APP_800_CLAIMS</data><data key="edge_relationship_type">2008_pia_describes_identity_and_claim_lookup</data><data key="edge_target_entity_id">R181_E015</data><data key="edge_operational_context">2008 National 800-Number Claims Status PIA expressly documents the identity check, claims lookup, mailing route or ephemeral storage; this is not a persistent identity record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0022" source="R181_E015" target="SYS_NUMIDENT"><data key="edge_relationship_id">R181_REL0022</data><data key="edge_source_entity_id">R181_E015</data><data key="edge_relationship_type">2008_pia_describes_identification_lookup_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">2008 National 800-Number Claims Status PIA expressly documents the identity check, claims lookup, mailing route or ephemeral storage; this is not a persistent identity record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0023" source="R181_E015" target="DB_CLAIMS_FOLDERS_SYSTEM"><data key="edge_relationship_id">R181_REL0023</data><data key="edge_source_entity_id">R181_E015</data><data key="edge_relationship_type">2008_pia_describes_claim_lookup_against</data><data key="edge_target_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="edge_operational_context">2008 National 800-Number Claims Status PIA expressly documents the identity check, claims lookup, mailing route or ephemeral storage; this is not a persistent identity record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0024" source="APP_800_CLAIMS" target="R181_E016"><data key="edge_relationship_id">R181_REL0024</data><data key="edge_source_entity_id">APP_800_CLAIMS</data><data key="edge_relationship_type">2008_pia_describes_transient_session_input</data><data key="edge_target_entity_id">R181_E016</data><data key="edge_operational_context">2008 National 800-Number Claims Status PIA expressly documents the identity check, claims lookup, mailing route or ephemeral storage; this is not a persistent identity record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0025" source="R181_E017" target="ORG_USPS"><data key="edge_relationship_id">R181_REL0025</data><data key="edge_source_entity_id">R181_E017</data><data key="edge_relationship_type">2008_pia_describes_postal_confirmation</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">2008 National 800-Number Claims Status PIA expressly documents the identity check, claims lookup, mailing route or ephemeral storage; this is not a persistent identity record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0026" source="R181_E017" target="R181_E014"><data key="edge_relationship_id">R181_REL0026</data><data key="edge_source_entity_id">R181_E017</data><data key="edge_relationship_type">delivered</data><data key="edge_target_entity_id">R181_E014</data><data key="edge_operational_context">2008 National 800-Number Claims Status PIA expressly documents the identity check, claims lookup, mailing route or ephemeral storage; this is not a persistent identity record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0027" source="APP_800_CLAIMS" target="R181_E017"><data key="edge_relationship_id">R181_REL0027</data><data key="edge_source_entity_id">APP_800_CLAIMS</data><data key="edge_relationship_type">2008_pia_describes_phone_claim_confirmation</data><data key="edge_target_entity_id">R181_E017</data><data key="edge_operational_context">2008 National 800-Number Claims Status PIA expressly documents the identity check, claims lookup, mailing route or ephemeral storage; this is not a persistent identity record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0028" source="APP_ATS" target="R181_E018"><data key="edge_relationship_id">R181_REL0028</data><data key="edge_source_entity_id">APP_ATS</data><data key="edge_relationship_type">historically_collected_and_retained</data><data key="edge_target_entity_id">R181_E018</data><data key="edge_operational_context">2017 ATS PIA documents daily auditable event collection and lookup. Existing source systems are not assumed to expose direct external interfaces.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0029" source="APP_ATS" target="R181_E019"><data key="edge_relationship_id">R181_REL0029</data><data key="edge_source_entity_id">APP_ATS</data><data key="edge_relationship_type">historically_supported_authorized_lookup_by</data><data key="edge_target_entity_id">R181_E019</data><data key="edge_operational_context">2017 ATS PIA documents daily auditable event collection and lookup. Existing source systems are not assumed to expose direct external interfaces.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0030" source="R181_E019" target="R181_E018"><data key="edge_relationship_id">R181_REL0030</data><data key="edge_source_entity_id">R181_E019</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">R181_E018</data><data key="edge_operational_context">2017 ATS PIA documents daily auditable event collection and lookup. Existing source systems are not assumed to expose direct external interfaces.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0031" source="R181_E018" target="DB_PINFILE"><data key="edge_relationship_id">R181_REL0031</data><data key="edge_source_entity_id">R181_E018</data><data key="edge_relationship_type">contains_actor_identifier_from</data><data key="edge_target_entity_id">DB_PINFILE</data><data key="edge_operational_context">2017 ATS PIA documents daily auditable event collection and lookup. Existing source systems are not assumed to expose direct external interfaces.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0032" source="APP_CIRP" target="R181_E020"><data key="edge_relationship_id">R181_REL0032</data><data key="edge_source_entity_id">APP_CIRP</data><data key="edge_relationship_type">historically_identified_for_review</data><data key="edge_target_entity_id">R181_E020</data><data key="edge_operational_context">2007 CIRP PIA documents review of program transaction metadata and management of referrals; not a complete capture of each program record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0033" source="APP_CIRP" target="R181_E021"><data key="edge_relationship_id">R181_REL0033</data><data key="edge_source_entity_id">APP_CIRP</data><data key="edge_relationship_type">historically_provided_screen_to_review_and_dispose</data><data key="edge_target_entity_id">R181_E021</data><data key="edge_operational_context">2007 CIRP PIA documents review of program transaction metadata and management of referrals; not a complete capture of each program record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0034" source="R181_E021" target="R181_E020"><data key="edge_relationship_id">R181_REL0034</data><data key="edge_source_entity_id">R181_E021</data><data key="edge_relationship_type">processes</data><data key="edge_target_entity_id">R181_E020</data><data key="edge_operational_context">2007 CIRP PIA documents review of program transaction metadata and management of referrals; not a complete capture of each program record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0035" source="R181_E020" target="DB_PINFILE"><data key="edge_relationship_id">R181_REL0035</data><data key="edge_source_entity_id">R181_E020</data><data key="edge_relationship_type">identifies_employee_actions_by</data><data key="edge_target_entity_id">DB_PINFILE</data><data key="edge_operational_context">2007 CIRP PIA documents review of program transaction metadata and management of referrals; not a complete capture of each program record.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0036" source="APP_MENS" target="R181_E022"><data key="edge_relationship_id">R181_REL0036</data><data key="edge_source_entity_id">APP_MENS</data><data key="edge_relationship_type">2021_pia_documents_hosted_by</data><data key="edge_target_entity_id">R181_E022</data><data key="edge_operational_context">2021 MENS PIA provides direct evidence of hosted SaaS, named contractor and emergency-contact categories. No assertion that the same vendor remains contractor in 2026.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0037" source="APP_MENS" target="R181_E025"><data key="edge_relationship_id">R181_REL0037</data><data key="edge_source_entity_id">APP_MENS</data><data key="edge_relationship_type">historically_uses_hosted_service_boundary</data><data key="edge_target_entity_id">R181_E025</data><data key="edge_operational_context">2021 MENS PIA provides direct evidence of hosted SaaS, named contractor and emergency-contact categories. No assertion that the same vendor remains contractor in 2026.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0038" source="R181_E022" target="R181_E025"><data key="edge_relationship_id">R181_REL0038</data><data key="edge_source_entity_id">R181_E022</data><data key="edge_relationship_type">historically_hosted_under_segregation_commitment</data><data key="edge_target_entity_id">R181_E025</data><data key="edge_operational_context">2021 MENS PIA provides direct evidence of hosted SaaS, named contractor and emergency-contact categories. No assertion that the same vendor remains contractor in 2026.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0039" source="APP_MENS" target="R181_E023"><data key="edge_relationship_id">R181_REL0039</data><data key="edge_source_entity_id">APP_MENS</data><data key="edge_relationship_type">was_seeded_with</data><data key="edge_target_entity_id">R181_E023</data><data key="edge_operational_context">2021 MENS PIA provides direct evidence of hosted SaaS, named contractor and emergency-contact categories. No assertion that the same vendor remains contractor in 2026.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0040" source="R181_E023" target="R181_E022"><data key="edge_relationship_id">R181_REL0040</data><data key="edge_source_entity_id">R181_E023</data><data key="edge_relationship_type">historically_delivered_to_host</data><data key="edge_target_entity_id">R181_E022</data><data key="edge_operational_context">2021 MENS PIA provides direct evidence of hosted SaaS, named contractor and emergency-contact categories. No assertion that the same vendor remains contractor in 2026.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0041" source="APP_MENS" target="R181_E024"><data key="edge_relationship_id">R181_REL0041</data><data key="edge_source_entity_id">APP_MENS</data><data key="edge_relationship_type">allowed_eligible_users_to_maintain</data><data key="edge_target_entity_id">R181_E024</data><data key="edge_operational_context">2021 MENS PIA provides direct evidence of hosted SaaS, named contractor and emergency-contact categories. No assertion that the same vendor remains contractor in 2026.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0042" source="R181_E024" target="R181_E025"><data key="edge_relationship_id">R181_REL0042</data><data key="edge_source_entity_id">R181_E024</data><data key="edge_relationship_type">stored_under</data><data key="edge_target_entity_id">R181_E025</data><data key="edge_operational_context">2021 MENS PIA provides direct evidence of hosted SaaS, named contractor and emergency-contact categories. No assertion that the same vendor remains contractor in 2026.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0043" source="REPO_SSA_VENDOR" target="R181_E026"><data key="edge_relationship_id">R181_REL0043</data><data key="edge_source_entity_id">REPO_SSA_VENDOR</data><data key="edge_relationship_type">has_documented_ingestion_metadata_rule</data><data key="edge_target_entity_id">R181_E026</data><data key="edge_operational_context">SSA Vendor Repository March 2024 official PDF documents the email ingestion taxonomy and approximate retention/deletion rule; no inference about storage engine.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0044" source="REPO_SSA_VENDOR" target="R181_E027"><data key="edge_relationship_id">R181_REL0044</data><data key="edge_source_entity_id">REPO_SSA_VENDOR</data><data key="edge_relationship_type">has_documented_retention_deletion_rule</data><data key="edge_target_entity_id">R181_E027</data><data key="edge_operational_context">SSA Vendor Repository March 2024 official PDF documents the email ingestion taxonomy and approximate retention/deletion rule; no inference about storage engine.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0045" source="PROC_VENDOR_REPO_SUBMISSION" target="R181_E026"><data key="edge_relationship_id">R181_REL0045</data><data key="edge_source_entity_id">PROC_VENDOR_REPO_SUBMISSION</data><data key="edge_relationship_type">uses_documented_subject_taxonomy</data><data key="edge_target_entity_id">R181_E026</data><data key="edge_operational_context">SSA Vendor Repository March 2024 official PDF documents the email ingestion taxonomy and approximate retention/deletion rule; no inference about storage engine.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0046" source="R181_E028" target="R181_E029"><data key="edge_relationship_id">R181_REL0046</data><data key="edge_source_entity_id">R181_E028</data><data key="edge_relationship_type">publishes_vintage_specific_product</data><data key="edge_target_entity_id">R181_E029</data><data key="edge_operational_context">2014 OACT supplemental tables are vintage-specific historical projection publications, not updated 2026 projections or operational MBR records.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0047" source="R181_E028" target="R181_E030"><data key="edge_relationship_id">R181_REL0047</data><data key="edge_source_entity_id">R181_E028</data><data key="edge_relationship_type">publishes_vintage_specific_product</data><data key="edge_target_entity_id">R181_E030</data><data key="edge_operational_context">2014 OACT supplemental tables are vintage-specific historical projection publications, not updated 2026 projections or operational MBR records.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0048" source="PROC_DEBT_SKIPTRACE" target="R181_E031"><data key="edge_relationship_id">R181_REL0048</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">historically_mentions_without_implementation_detail</data><data key="edge_target_entity_id">R181_E031</data><data key="edge_operational_context">Skiptracing POMS says BOAN is mandatory for credit bureau contact and IRS Project 719; no source describes Project 719 actual record feeds.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">4</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0049" source="APP_EPECS" target="R181_E032"><data key="edge_relationship_id">R181_REL0049</data><data key="edge_source_entity_id">APP_EPECS</data><data key="edge_relationship_type">historically_processed_credential_applicant_address</data><data key="edge_target_entity_id">R181_E032</data><data key="edge_operational_context">2013 official SMACS PIA establishes PIV card credential holder data and LSAS facility access auditing; not beneficiary address and no current deployment inference.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0050" source="APP_PIV_CMS" target="R181_E032"><data key="edge_relationship_id">R181_REL0050</data><data key="edge_source_entity_id">APP_PIV_CMS</data><data key="edge_relationship_type">historically_processed_credential_holder_address</data><data key="edge_target_entity_id">R181_E032</data><data key="edge_operational_context">2013 official SMACS PIA establishes PIV card credential holder data and LSAS facility access auditing; not beneficiary address and no current deployment inference.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0051" source="APP_SAFE" target="R181_E032"><data key="edge_relationship_id">R181_REL0051</data><data key="edge_source_entity_id">APP_SAFE</data><data key="edge_relationship_type">historically_contained_physical_security_contact_data</data><data key="edge_target_entity_id">R181_E032</data><data key="edge_operational_context">2013 official SMACS PIA establishes PIV card credential holder data and LSAS facility access auditing; not beneficiary address and no current deployment inference.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0052" source="APP_PACS" target="APP_LSAS"><data key="edge_relationship_id">R181_REL0052</data><data key="edge_source_entity_id">APP_PACS</data><data key="edge_relationship_type">historically_implemented_using</data><data key="edge_target_entity_id">APP_LSAS</data><data key="edge_operational_context">2013 official SMACS PIA establishes PIV card credential holder data and LSAS facility access auditing; not beneficiary address and no current deployment inference.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R181_REL0053" source="APP_LSAS" target="R181_E033"><data key="edge_relationship_id">R181_REL0053</data><data key="edge_source_entity_id">APP_LSAS</data><data key="edge_relationship_type">historically_recorded_facility_entry_information</data><data key="edge_target_entity_id">R181_E033</data><data key="edge_operational_context">2013 official SMACS PIA establishes PIV card credential holder data and LSAS facility access auditing; not beneficiary address and no current deployment inference.</data><data key="edge_observed_as_of">2026-10-10</data><data key="edge_confidence">5</data><data key="edge_notes">Direct source documents historical administrative relationship; mechanism, storage and current deployment not assumed.</data></edge><edge id="R182_REL0001" source="R182_E001" target="SYS_MBR"><data key="edge_relationship_id">R182_REL0001</data><data key="edge_source_entity_id">R182_E001</data><data key="edge_relationship_type">historically_managed</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">OIG 2010 names this master-file group among MADAM-managed repositories before conversion.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0002" source="R182_E001" target="SYS_SSR"><data key="edge_relationship_id">R182_REL0002</data><data key="edge_source_entity_id">R182_E001</data><data key="edge_relationship_type">historically_managed</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">OIG 2010 names this master-file group among MADAM-managed repositories before conversion.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0003" source="R182_E001" target="SYS_MEF"><data key="edge_relationship_id">R182_REL0003</data><data key="edge_source_entity_id">R182_E001</data><data key="edge_relationship_type">historically_managed</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">OIG 2010 names this master-file group among MADAM-managed repositories before conversion.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0004" source="R182_E001" target="SYS_NUMIDENT"><data key="edge_relationship_id">R182_REL0004</data><data key="edge_source_entity_id">R182_E001</data><data key="edge_relationship_type">historically_managed</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG 2010 names this master-file group among MADAM-managed repositories before conversion.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0005" source="R182_E001" target="DB_ALPHIDENT"><data key="edge_relationship_id">R182_REL0005</data><data key="edge_source_entity_id">R182_E001</data><data key="edge_relationship_type">historically_managed</data><data key="edge_target_entity_id">DB_ALPHIDENT</data><data key="edge_operational_context">OIG 2010 names this master-file group among MADAM-managed repositories before conversion.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0006" source="R182_E004" target="R182_E005"><data key="edge_relationship_id">R182_REL0006</data><data key="edge_source_entity_id">R182_E004</data><data key="edge_relationship_type">historically_has_phase</data><data key="edge_target_entity_id">R182_E005</data><data key="edge_operational_context">Phase I migrates stored master files; not a statement that all four completed.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0007" source="R182_E004" target="R182_E006"><data key="edge_relationship_id">R182_REL0007</data><data key="edge_source_entity_id">R182_E004</data><data key="edge_relationship_type">planned_follow_on_phase</data><data key="edge_target_entity_id">R182_E006</data><data key="edge_operational_context">2010 planned Phase II to remove compatibility calls; implementation not established.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0008" source="R182_E004" target="R182_E007"><data key="edge_relationship_id">R182_REL0008</data><data key="edge_source_entity_id">R182_E004</data><data key="edge_relationship_type">planned_follow_on_phase</data><data key="edge_target_entity_id">R182_E007</data><data key="edge_operational_context">2010 planned Phase III direct access after further scope analysis.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0009" source="R182_E005" target="R182_E002"><data key="edge_relationship_id">R182_REL0009</data><data key="edge_source_entity_id">R182_E005</data><data key="edge_relationship_type">historically_used_compatibility_routing</data><data key="edge_target_entity_id">R182_E002</data><data key="edge_operational_context">Existing application calls entered compatibility interface in mixed MADAM/DB2 period.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0010" source="R182_E002" target="R182_E003"><data key="edge_relationship_id">R182_REL0010</data><data key="edge_source_entity_id">R182_E002</data><data key="edge_relationship_type">historically_dispatched_db2_calls_to</data><data key="edge_target_entity_id">R182_E003</data><data key="edge_operational_context">2010 OIG Appendix D identifies DB2 adapter calls after interface translation.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0011" source="R182_E003" target="TECH_DB2"><data key="edge_relationship_id">R182_REL0011</data><data key="edge_source_entity_id">R182_E003</data><data key="edge_relationship_type">historically_accessed</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">DB2 adapter mediates DB2 master-file operations, 2009 architecture.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0012" source="R182_E001" target="R182_E004"><data key="edge_relationship_id">R182_REL0012</data><data key="edge_source_entity_id">R182_E001</data><data key="edge_relationship_type">was_subject_of</data><data key="edge_target_entity_id">R182_E004</data><data key="edge_operational_context">OIG audit establishes conversion from MADAM to DB2.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0013" source="R182_E005" target="R182_E008"><data key="edge_relationship_id">R182_REL0013</data><data key="edge_source_entity_id">R182_E005</data><data key="edge_relationship_type">resulted_in_partial_state</data><data key="edge_target_entity_id">R182_E008</data><data key="edge_operational_context">November 2009 snapshot shows Numident/MEF converted, not MBR/SSR.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0014" source="SYS_NUMIDENT" target="TECH_DB2"><data key="edge_relationship_id">R182_REL0014</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">reported_as_in_db2_november_2009</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">As of November 2009, this master-file component had completed the DB2 conversion.</data><data key="edge_observed_as_of">2009-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0015" source="DB_ALPHIDENT" target="TECH_DB2"><data key="edge_relationship_id">R182_REL0015</data><data key="edge_source_entity_id">DB_ALPHIDENT</data><data key="edge_relationship_type">reported_as_in_db2_november_2009</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">As of November 2009, this master-file component had completed the DB2 conversion.</data><data key="edge_observed_as_of">2009-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0016" source="SYS_MEF" target="TECH_DB2"><data key="edge_relationship_id">R182_REL0016</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">reported_as_in_db2_november_2009</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">As of November 2009, this master-file component had completed the DB2 conversion.</data><data key="edge_observed_as_of">2009-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0017" source="SYS_MBR" target="R182_E001"><data key="edge_relationship_id">R182_REL0017</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">reported_as_in_madam_november_2009</data><data key="edge_target_entity_id">R182_E001</data><data key="edge_operational_context">MBR and SSR not converted as of November 2009; planned date is not proven outcome.</data><data key="edge_observed_as_of">2009-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0018" source="SYS_SSR" target="R182_E001"><data key="edge_relationship_id">R182_REL0018</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">reported_as_in_madam_november_2009</data><data key="edge_target_entity_id">R182_E001</data><data key="edge_operational_context">MBR and SSR not converted as of November 2009; planned date is not proven outcome.</data><data key="edge_observed_as_of">2009-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0019" source="R182_E006" target="R182_E010"><data key="edge_relationship_id">R182_REL0019</data><data key="edge_source_entity_id">R182_E006</data><data key="edge_relationship_type">must_address</data><data key="edge_target_entity_id">R182_E010</data><data key="edge_operational_context">Compressed legacy record and uncompressed DB2 representations require code handling.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0020" source="SYS_MBR" target="R182_E011"><data key="edge_relationship_id">R182_REL0020</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">historically_includes_cross_program_short_references</data><data key="edge_target_entity_id">R182_E011</data><data key="edge_operational_context">MBR contains short cross references to other program entitlement records.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0021" source="DB_ALPHIDENT" target="R182_E012"><data key="edge_relationship_id">R182_REL0021</data><data key="edge_source_entity_id">DB_ALPHIDENT</data><data key="edge_relationship_type">historically_supports_lookup</data><data key="edge_target_entity_id">R182_E012</data><data key="edge_operational_context">Alphident used to locate SSN from name plus DOB.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0022" source="R182_E005" target="R182_E009"><data key="edge_relationship_id">R182_REL0022</data><data key="edge_source_entity_id">R182_E005</data><data key="edge_relationship_type">uses_master_file_segment_layout</data><data key="edge_target_entity_id">R182_E009</data><data key="edge_operational_context">OIG Appendix C describes master-file segments and subsegments.</data><data key="edge_observed_as_of">2010-05-13</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0023" source="R182_E013" target="R182_E014"><data key="edge_relationship_id">R182_REL0023</data><data key="edge_source_entity_id">R182_E013</data><data key="edge_relationship_type">included_mainframe_access_repository</data><data key="edge_target_entity_id">R182_E014</data><data key="edge_operational_context">SSA identifies TOP SECRET as internal workforce access repository for 2008 infrastructure.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0024" source="FORM_SSA120" target="R182_E015"><data key="edge_relationship_id">R182_REL0024</data><data key="edge_source_entity_id">FORM_SSA120</data><data key="edge_relationship_type">authorized_request_for_historical_access</data><data key="edge_target_entity_id">R182_E015</data><data key="edge_operational_context">Form SSA-120 submitted by management for requested workforce system access.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0025" source="R182_E015" target="R182_E014"><data key="edge_relationship_id">R182_REL0025</data><data key="edge_source_entity_id">R182_E015</data><data key="edge_relationship_type">historically_provisioned_accounts_in</data><data key="edge_target_entity_id">R182_E014</data><data key="edge_operational_context">Authorized SSA-120 information was entered into TOP SECRET.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0026" source="R182_E014" target="R182_E016"><data key="edge_relationship_id">R182_REL0026</data><data key="edge_source_entity_id">R182_E014</data><data key="edge_relationship_type">historically_allocated</data><data key="edge_target_entity_id">R182_E016</data><data key="edge_operational_context">TOP SECRET employee and contractor accounts assigned unique PIN credentials.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0027" source="R182_E013" target="SYS_ICDB"><data key="edge_relationship_id">R182_REL0027</data><data key="edge_source_entity_id">R182_E013</data><data key="edge_relationship_type">historically_supported_ssa_gss_or_major_application</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">2008 PIA names this SSA GSS or major application as supported by EWANS infrastructure.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0028" source="R182_E013" target="APP_DACUS"><data key="edge_relationship_id">R182_REL0028</data><data key="edge_source_entity_id">R182_E013</data><data key="edge_relationship_type">historically_supported_ssa_gss_or_major_application</data><data key="edge_target_entity_id">APP_DACUS</data><data key="edge_operational_context">2008 PIA names this SSA GSS or major application as supported by EWANS infrastructure.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0029" source="R182_E013" target="APP_FALCON"><data key="edge_relationship_id">R182_REL0029</data><data key="edge_source_entity_id">R182_E013</data><data key="edge_relationship_type">historically_supported_ssa_gss_or_major_application</data><data key="edge_target_entity_id">APP_FALCON</data><data key="edge_operational_context">2008 PIA names this SSA GSS or major application as supported by EWANS infrastructure.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0030" source="R182_E013" target="APP_QAS"><data key="edge_relationship_id">R182_REL0030</data><data key="edge_source_entity_id">R182_E013</data><data key="edge_relationship_type">historically_supported_ssa_gss_or_major_application</data><data key="edge_target_entity_id">APP_QAS</data><data key="edge_operational_context">2008 PIA names this SSA GSS or major application as supported by EWANS infrastructure.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0031" source="R182_E013" target="APP_SSNEC"><data key="edge_relationship_id">R182_REL0031</data><data key="edge_source_entity_id">R182_E013</data><data key="edge_relationship_type">historically_supported_ssa_gss_or_major_application</data><data key="edge_target_entity_id">APP_SSNEC</data><data key="edge_operational_context">2008 PIA names this SSA GSS or major application as supported by EWANS infrastructure.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0032" source="R182_E013" target="SYS_MBR"><data key="edge_relationship_id">R182_REL0032</data><data key="edge_source_entity_id">R182_E013</data><data key="edge_relationship_type">historically_supported_program_access_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2008 PIA describes centralized platform for Title II and Title XVI major processing; support scope only, no storage inference.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">4</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0033" source="R182_E013" target="SYS_SSR"><data key="edge_relationship_id">R182_REL0033</data><data key="edge_source_entity_id">R182_E013</data><data key="edge_relationship_type">historically_supported_program_access_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2008 PIA describes centralized platform for Title II and Title XVI major processing; support scope only, no storage inference.</data><data key="edge_observed_as_of">2008-09-08</data><data key="edge_confidence">4</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0034" source="APP_800_VOICE" target="R182_E017"><data key="edge_relationship_id">R182_REL0034</data><data key="edge_source_entity_id">APP_800_VOICE</data><data key="edge_relationship_type">historically_implemented_one_time_collection</data><data key="edge_target_entity_id">R182_E017</data><data key="edge_operational_context">TVDC designed to reuse within-call authentication rather than repeated collection.</data><data key="edge_observed_as_of">2008-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0035" source="R182_E017" target="R182_E018"><data key="edge_relationship_id">R182_REL0035</data><data key="edge_source_entity_id">R182_E017</data><data key="edge_relationship_type">holds_in_transient_session</data><data key="edge_target_entity_id">R182_E018</data><data key="edge_operational_context">TVDC keeps caller data in encrypted, short-lived memory and deletes it at call end.</data><data key="edge_observed_as_of">2008-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0036" source="R182_E017" target="R182_E021"><data key="edge_relationship_id">R182_REL0036</data><data key="edge_source_entity_id">R182_E017</data><data key="edge_relationship_type">requires_customer_provided</data><data key="edge_target_entity_id">R182_E021</data><data key="edge_operational_context">TVDC lists possible identity fields used to authenticate callers.</data><data key="edge_observed_as_of">2008-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0037" source="R182_E017" target="R182_E019"><data key="edge_relationship_id">R182_REL0037</data><data key="edge_source_entity_id">R182_E017</data><data key="edge_relationship_type">conditionally_passes_data_to</data><data key="edge_target_entity_id">R182_E019</data><data key="edge_operational_context">Transfer to agent after caller choice or failed automated verification.</data><data key="edge_observed_as_of">2008-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0038" source="R182_E020" target="APP_800_VOICE"><data key="edge_relationship_id">R182_REL0038</data><data key="edge_source_entity_id">R182_E020</data><data key="edge_relationship_type">restricts_automated_access_via</data><data key="edge_target_entity_id">APP_800_VOICE</data><data key="edge_operational_context">PIA describes blocking automated and internet access, then referral to alternative channels.</data><data key="edge_observed_as_of">2008-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0039" source="APP_800_VOICE" target="R182_E017"><data key="edge_relationship_id">R182_REL0039</data><data key="edge_source_entity_id">APP_800_VOICE</data><data key="edge_relationship_type">historically_supported_transient_address_change_transaction</data><data key="edge_target_entity_id">R182_E017</data><data key="edge_operational_context">Change of address one of listed telephone actions; no automatic MBR/SSR update path established.</data><data key="edge_observed_as_of">2008-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0040" source="R182_E022" target="APP_DACUS"><data key="edge_relationship_id">R182_REL0040</data><data key="edge_source_entity_id">R182_E022</data><data key="edge_relationship_type">historically_input_to</data><data key="edge_target_entity_id">APP_DACUS</data><data key="edge_operational_context">State EDR death reports submitted into DACUS for comparison and processing.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0041" source="R182_E025" target="APP_DACUS"><data key="edge_relationship_id">R182_REL0041</data><data key="edge_source_entity_id">R182_E025</data><data key="edge_relationship_type">historically_input_to</data><data key="edge_target_entity_id">APP_DACUS</data><data key="edge_operational_context">2007 DACUS received nonstate internal death reports through Daily Update Data Exchange.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0042" source="APP_DACUS" target="SYS_MBR"><data key="edge_relationship_id">R182_REL0042</data><data key="edge_source_entity_id">APP_DACUS</data><data key="edge_relationship_type">historically_crosschecked</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Death reports compared to MBR payment and identity indicators to prevent postmortem benefits.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0043" source="APP_DACUS" target="SYS_SSR"><data key="edge_relationship_id">R182_REL0043</data><data key="edge_source_entity_id">APP_DACUS</data><data key="edge_relationship_type">historically_crosschecked</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Death reports compared to SSR eligibility/payment indicators.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0044" source="APP_DACUS" target="R182_E023"><data key="edge_relationship_id">R182_REL0044</data><data key="edge_source_entity_id">APP_DACUS</data><data key="edge_relationship_type">created_investigation_alert</data><data key="edge_target_entity_id">R182_E023</data><data key="edge_operational_context">Conflicting non-EDR reports generate field office investigative alert.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0045" source="R182_E022" target="SYS_MBR"><data key="edge_relationship_id">R182_REL0045</data><data key="edge_source_entity_id">R182_E022</data><data key="edge_relationship_type">historically_triggered_program_record_notifications</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2007 state EDR reports sent to MBR for conditional action; not evidence of no-review automatic write.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0046" source="R182_E022" target="SYS_SSR"><data key="edge_relationship_id">R182_REL0046</data><data key="edge_source_entity_id">R182_E022</data><data key="edge_relationship_type">historically_triggered_program_record_notifications</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2007 state EDR reports sent to SSR for conditional action; not evidence of no-review automatic write.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0047" source="R182_E024" target="APP_SSNEC"><data key="edge_relationship_id">R182_REL0047</data><data key="edge_source_entity_id">R182_E024</data><data key="edge_relationship_type">historically_routed_through</data><data key="edge_target_entity_id">APP_SSNEC</data><data key="edge_operational_context">Resolved DACUS death data sent to SSNEC for posting to Numident.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0048" source="APP_SSNEC" target="SYS_NUMIDENT"><data key="edge_relationship_id">R182_REL0048</data><data key="edge_source_entity_id">APP_SSNEC</data><data key="edge_relationship_type">posts_death_update_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Source explicitly describes SSNEC route to Numident when conflict resolved or absent.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0049" source="APP_DACUS" target="R182_E024"><data key="edge_relationship_id">R182_REL0049</data><data key="edge_source_entity_id">APP_DACUS</data><data key="edge_relationship_type">conditionally_processes_death_posting</data><data key="edge_target_entity_id">R182_E024</data><data key="edge_operational_context">Conditional death posting after no conflicts or conflict resolution.</data><data key="edge_observed_as_of">2007-09-28</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0050" source="APP_RACEETH" target="R182_E026"><data key="edge_relationship_id">R182_REL0050</data><data key="edge_source_entity_id">APP_RACEETH</data><data key="edge_relationship_type">subject_to_coverage_gap</data><data key="edge_target_entity_id">R182_E026</data><data key="edge_operational_context">RECS excludes EAB/EAE applicants from collection when partner processes omit race data.</data><data key="edge_observed_as_of">2009-11-18</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0051" source="APP_RACEETH" target="R182_E027"><data key="edge_relationship_id">R182_REL0051</data><data key="edge_source_entity_id">APP_RACEETH</data><data key="edge_relationship_type">uses_classification</data><data key="edge_target_entity_id">R182_E027</data><data key="edge_operational_context">2009 PIA states OMB revised race/ethnicity categories implemented or being introduced.</data><data key="edge_observed_as_of">2009-11-18</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0052" source="APP_RACEETH" target="R182_E028"><data key="edge_relationship_id">R182_REL0052</data><data key="edge_source_entity_id">APP_RACEETH</data><data key="edge_relationship_type">planned_historical_separation</data><data key="edge_target_entity_id">R182_E028</data><data key="edge_operational_context">Old race data to remain in historical SSN master after completed RECS transition; success unverified.</data><data key="edge_observed_as_of">2009-11-18</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0053" source="R182_E028" target="SYS_NUMIDENT"><data key="edge_relationship_id">R182_REL0053</data><data key="edge_source_entity_id">R182_E028</data><data key="edge_relationship_type">proposed_retained_legacy_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Historical race entries in SSN-holder system; not proof of any modern Numident race attribute.</data><data key="edge_observed_as_of">2009-11-18</data><data key="edge_confidence">4</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0054" source="APP_RACEETH" target="R182_E029"><data key="edge_relationship_id">R182_REL0054</data><data key="edge_source_entity_id">APP_RACEETH</data><data key="edge_relationship_type">limited_by_use_policy</data><data key="edge_target_entity_id">R182_E029</data><data key="edge_operational_context">RECS data for research and reporting, not benefits adjudication.</data><data key="edge_observed_as_of">2009-11-18</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0055" source="APP_SSNEC" target="R182_E030"><data key="edge_relationship_id">R182_REL0055</data><data key="edge_source_entity_id">APP_SSNEC</data><data key="edge_relationship_type">historically_recorded_application_fields</data><data key="edge_target_entity_id">R182_E030</data><data key="edge_operational_context">Original applications contain names of both parents, date/place of birth, gender and evidence description.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0056" source="APP_SSNEC" target="R182_E031"><data key="edge_relationship_id">R182_REL0056</data><data key="edge_source_entity_id">APP_SSNEC</data><data key="edge_relationship_type">historically_flagged_suspect_evidence</data><data key="edge_target_entity_id">R182_E031</data><data key="edge_operational_context">2007 SSNEC system contains suspected fraudulent support evidence and processing restrictions.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0057" source="APP_SSNEC" target="R182_E032"><data key="edge_relationship_id">R182_REL0057</data><data key="edge_source_entity_id">APP_SSNEC</data><data key="edge_relationship_type">historically_tracked_multiple_ssn_cross_references</data><data key="edge_target_entity_id">R182_E032</data><data key="edge_operational_context">Cross-reference indications for multiple issued SSNs associated with an individual.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0058" source="APP_FALCON" target="R182_E033"><data key="edge_relationship_id">R182_REL0058</data><data key="edge_source_entity_id">APP_FALCON</data><data key="edge_relationship_type">historically_provided</data><data key="edge_target_entity_id">R182_E033</data><data key="edge_operational_context">SSA processing centers used FALCON for manual bulk updates.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0059" source="R182_E033" target="R182_E034"><data key="edge_relationship_id">R182_REL0059</data><data key="edge_source_entity_id">R182_E033</data><data key="edge_relationship_type">passed_correction_inputs_to</data><data key="edge_target_entity_id">R182_E034</data><data key="edge_operational_context">Bulk data entry forwarded to program-specific payment systems for actual processing.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0060" source="APP_FALCON" target="R182_E035"><data key="edge_relationship_id">R182_REL0060</data><data key="edge_source_entity_id">APP_FALCON</data><data key="edge_relationship_type">historically_documented_unused_capability</data><data key="edge_target_entity_id">R182_E035</data><data key="edge_operational_context">2007 PIA states class-action processing possible but not used in recent years.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0061" source="APP_QAS" target="R182_E036"><data key="edge_relationship_id">R182_REL0061</data><data key="edge_source_entity_id">APP_QAS</data><data key="edge_relationship_type">historically_stored_review_copy_of</data><data key="edge_target_entity_id">R182_E036</data><data key="edge_operational_context">2018 QA data contains geographic residence data used for reviews; not a claimant address update.</data><data key="edge_observed_as_of">2018-12-17</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0062" source="APP_QAS" target="R182_E037"><data key="edge_relationship_id">R182_REL0062</data><data key="edge_source_entity_id">APP_QAS</data><data key="edge_relationship_type">historically_stored_review_copy_of</data><data key="edge_target_entity_id">R182_E037</data><data key="edge_operational_context">2018 QA system uses claim evidence and performance-error attributes in sampling context.</data><data key="edge_observed_as_of">2018-12-17</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0063" source="APP_DICARS_LEGACY" target="R182_E037"><data key="edge_relationship_id">R182_REL0063</data><data key="edge_source_entity_id">APP_DICARS_LEGACY</data><data key="edge_relationship_type">historically_used_sample_context</data><data key="edge_target_entity_id">R182_E037</data><data key="edge_operational_context">Legacy DICARS sample tracking; replaced later by QRCPS per existing catalog.</data><data key="edge_observed_as_of">2018-12-17</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0064" source="R182_E038" target="R182_E039"><data key="edge_relationship_id">R182_REL0064</data><data key="edge_source_entity_id">R182_E038</data><data key="edge_relationship_type">historically_published_supplement</data><data key="edge_target_entity_id">R182_E039</data><data key="edge_operational_context">2009 Trustees Report provides single-year supplement alongside main Trustees publication.</data><data key="edge_observed_as_of">2009-05-12</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R182_REL0065" source="R182_E038" target="R182_E040"><data key="edge_relationship_id">R182_REL0065</data><data key="edge_source_entity_id">R182_E038</data><data key="edge_relationship_type">projection_scenarios_based_on</data><data key="edge_target_entity_id">R182_E040</data><data key="edge_operational_context">2009 economic low/intermediate/high scenarios incorporate recession assumptions, not actual outcomes.</data><data key="edge_observed_as_of">2009-05-12</data><data key="edge_confidence">5</data><data key="edge_notes">Only stated source-supported historical functional dependency; update, deployment and technical mechanism not inferred.</data></edge><edge id="R183_REL0001" source="EX_SVES" target="R183_E002"><data key="edge_relationship_id">R183_REL0001</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">member_of_2009_batch_exchange_architecture</data><data key="edge_target_entity_id">R183_E002</data><data key="edge_operational_context">GAO identifies this system as operating in the 2009 batch exchange category.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0002" source="EX_BENDEX" target="R183_E002"><data key="edge_relationship_id">R183_REL0002</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">member_of_2009_batch_exchange_architecture</data><data key="edge_target_entity_id">R183_E002</data><data key="edge_operational_context">GAO identifies this system as operating in the 2009 batch exchange category.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0003" source="APP_EVS" target="R183_E002"><data key="edge_relationship_id">R183_REL0003</data><data key="edge_source_entity_id">APP_EVS</data><data key="edge_relationship_type">member_of_2009_batch_exchange_architecture</data><data key="edge_target_entity_id">R183_E002</data><data key="edge_operational_context">GAO identifies this system as operating in the 2009 batch exchange category.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0004" source="EX_SDX" target="R183_E002"><data key="edge_relationship_id">R183_REL0004</data><data key="edge_source_entity_id">EX_SDX</data><data key="edge_relationship_type">member_of_2009_batch_exchange_architecture</data><data key="edge_target_entity_id">R183_E002</data><data key="edge_operational_context">GAO identifies this system as operating in the 2009 batch exchange category.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0005" source="APP_PUPS" target="R183_E002"><data key="edge_relationship_id">R183_REL0005</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">member_of_2009_batch_exchange_architecture</data><data key="edge_target_entity_id">R183_E002</data><data key="edge_operational_context">GAO identifies this system as operating in the 2009 batch exchange category.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0006" source="EX_SOLQ" target="R183_E003"><data key="edge_relationship_id">R183_REL0006</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">member_of_2009_online_exchange_architecture</data><data key="edge_target_entity_id">R183_E003</data><data key="edge_operational_context">GAO identifies this application as one of the key online partner query services in 2009.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0007" source="EX_SSOLV" target="R183_E003"><data key="edge_relationship_id">R183_REL0007</data><data key="edge_source_entity_id">EX_SSOLV</data><data key="edge_relationship_type">member_of_2009_online_exchange_architecture</data><data key="edge_target_entity_id">R183_E003</data><data key="edge_operational_context">GAO identifies this application as one of the key online partner query services in 2009.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0008" source="EX_HAVV" target="R183_E003"><data key="edge_relationship_id">R183_REL0008</data><data key="edge_source_entity_id">EX_HAVV</data><data key="edge_relationship_type">member_of_2009_online_exchange_architecture</data><data key="edge_target_entity_id">R183_E003</data><data key="edge_operational_context">GAO identifies this application as one of the key online partner query services in 2009.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0009" source="EX_EVERIFY" target="R183_E003"><data key="edge_relationship_id">R183_REL0009</data><data key="edge_source_entity_id">EX_EVERIFY</data><data key="edge_relationship_type">member_of_2009_online_exchange_architecture</data><data key="edge_target_entity_id">R183_E003</data><data key="edge_operational_context">GAO identifies this application as one of the key online partner query services in 2009.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0010" source="EX_UIQ" target="R183_E003"><data key="edge_relationship_id">R183_REL0010</data><data key="edge_source_entity_id">EX_UIQ</data><data key="edge_relationship_type">member_of_2009_online_exchange_architecture</data><data key="edge_target_entity_id">R183_E003</data><data key="edge_operational_context">GAO identifies this application as one of the key online partner query services in 2009.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0011" source="R183_E005" target="R183_E002"><data key="edge_relationship_id">R183_REL0011</data><data key="edge_source_entity_id">R183_E005</data><data key="edge_relationship_type">member_of_2009_batch_exchange_architecture</data><data key="edge_target_entity_id">R183_E002</data><data key="edge_operational_context">Earnings System appears among the six batch services in the GAO 2009 table.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0012" source="R183_E005" target="SYS_MEF"><data key="edge_relationship_id">R183_REL0012</data><data key="edge_source_entity_id">R183_E005</data><data key="edge_relationship_type">documented_2009_read_source</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">2009 Earnings System reports wages and earnings verification using MEF.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0013" source="R183_E004" target="EX_SOLQ"><data key="edge_relationship_id">R183_REL0013</data><data key="edge_source_entity_id">R183_E004</data><data key="edge_relationship_type">federal_name_for_2009_service</data><data key="edge_target_entity_id">EX_SOLQ</data><data key="edge_operational_context">FOLQ is the federal designator for SOLQ, not an asserted separate technical application.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0014" source="R183_E004" target="EX_SVES"><data key="edge_relationship_id">R183_REL0014</data><data key="edge_source_entity_id">R183_E004</data><data key="edge_relationship_type">online_counterpart_of_2009_batch_exchange</data><data key="edge_target_entity_id">EX_SVES</data><data key="edge_operational_context">GAO identifies online SOLQ/FOLQ as analogous to batch SVES.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0015" source="R183_E002" target="R183_E001"><data key="edge_relationship_id">R183_REL0015</data><data key="edge_source_entity_id">R183_E002</data><data key="edge_relationship_type">component_of_historical_architecture</data><data key="edge_target_entity_id">R183_E001</data><data key="edge_operational_context">Six batch services form one class of the 2009 observed outgoing exchange architecture.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0016" source="R183_E003" target="R183_E001"><data key="edge_relationship_id">R183_REL0016</data><data key="edge_source_entity_id">R183_E003</data><data key="edge_relationship_type">component_of_historical_architecture</data><data key="edge_target_entity_id">R183_E001</data><data key="edge_operational_context">Five real-time services form another class of the 2009 observed outgoing exchange architecture.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0017" source="EX_SVES" target="SYS_NUMIDENT"><data key="edge_relationship_id">R183_REL0017</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">2009 SVES consulted Numident for SSN verification.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0018" source="EX_SVES" target="SYS_MBR"><data key="edge_relationship_id">R183_REL0018</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2009 SVES consulted MBR for Title II benefit information.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0019" source="EX_SVES" target="SYS_SSR"><data key="edge_relationship_id">R183_REL0019</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2009 SVES consulted SSR for SSI program information.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0020" source="EX_BENDEX" target="SYS_MBR"><data key="edge_relationship_id">R183_REL0020</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2009 BENDEX used MBR for RSDI benefit information.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0021" source="EX_BENDEX" target="SYS_MEF"><data key="edge_relationship_id">R183_REL0021</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">2009 BENDEX used MEF for prior-year earnings and employer information.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0022" source="EX_SDX" target="SYS_SSR"><data key="edge_relationship_id">R183_REL0022</data><data key="edge_source_entity_id">EX_SDX</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2009 SDX retrieved SSI recipient information from SSR.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0023" source="APP_EVS" target="SYS_NUMIDENT"><data key="edge_relationship_id">R183_REL0023</data><data key="edge_source_entity_id">APP_EVS</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">2009 EVS verified SSNs using Numident.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0024" source="EX_SSOLV" target="SYS_NUMIDENT"><data key="edge_relationship_id">R183_REL0024</data><data key="edge_source_entity_id">EX_SSOLV</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">2009 SSOLV used Numident for state DMV verification.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0025" source="EX_HAVV" target="SYS_NUMIDENT"><data key="edge_relationship_id">R183_REL0025</data><data key="edge_source_entity_id">EX_HAVV</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">2009 HAVV used Numident to verify four-digit SSNs for eligible voter registration.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0026" source="EX_EVERIFY" target="SYS_NUMIDENT"><data key="edge_relationship_id">R183_REL0026</data><data key="edge_source_entity_id">EX_EVERIFY</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">2009 E-Verify checked Numident SSN data for DHS employment eligibility workflows.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0027" source="EX_UIQ" target="SYS_MBR"><data key="edge_relationship_id">R183_REL0027</data><data key="edge_source_entity_id">EX_UIQ</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2009 UIQ retrieved RSDI benefits information for state unemployment agencies.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0028" source="EX_SOLQ" target="SYS_SSR"><data key="edge_relationship_id">R183_REL0028</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">2009_source_record_access</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2009 SOLQ/FOLQ retrieved SSI information from SSR.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0029" source="EX_SSOLV" target="R183_E006"><data key="edge_relationship_id">R183_REL0029</data><data key="edge_source_entity_id">EX_SSOLV</data><data key="edge_relationship_type">2009_exchange_sla_governed_by</data><data key="edge_target_entity_id">R183_E006</data><data key="edge_operational_context">2009 AAMVA SLA sets requested 3-second and 5-second response thresholds; not an actual response-time measurement.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0030" source="ORG_AAMVA" target="R183_E006"><data key="edge_relationship_id">R183_REL0030</data><data key="edge_source_entity_id">ORG_AAMVA</data><data key="edge_relationship_type">2009_partner_in_service_standard</data><data key="edge_target_entity_id">R183_E006</data><data key="edge_operational_context">AAMVA network is the partner named in the GAO-reported SSOLV SLA.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0031" source="ORG_VBA" target="R183_E007"><data key="edge_relationship_id">R183_REL0031</data><data key="edge_source_entity_id">ORG_VBA</data><data key="edge_relationship_type">2009_partner_in_service_standard</data><data key="edge_target_entity_id">R183_E007</data><data key="edge_operational_context">GAO reports Veterans Benefits Administration agreement 99 percent data-accuracy target.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0032" source="EX_EVERIFY" target="R183_E008"><data key="edge_relationship_id">R183_REL0032</data><data key="edge_source_entity_id">EX_EVERIFY</data><data key="edge_relationship_type">represented_in_historical_transaction_series</data><data key="edge_target_entity_id">R183_E008</data><data key="edge_operational_context">E-Verify transactions rose from about 3.3 million in FY2007 to 6.7 million in FY2008.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0033" source="EX_BENDEX" target="R183_E008"><data key="edge_relationship_id">R183_REL0033</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">historical_request_volume_recorded_by</data><data key="edge_target_entity_id">R183_E008</data><data key="edge_operational_context">GAO provides FY2007/FY2008 comparison; differing request definitions should be retained.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0034" source="EX_SDX" target="R183_E008"><data key="edge_relationship_id">R183_REL0034</data><data key="edge_source_entity_id">EX_SDX</data><data key="edge_relationship_type">historical_request_volume_recorded_by</data><data key="edge_target_entity_id">R183_E008</data><data key="edge_operational_context">GAO provides FY2007/FY2008 comparison; differing request definitions should be retained.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0035" source="EX_SSOLV" target="R183_E008"><data key="edge_relationship_id">R183_REL0035</data><data key="edge_source_entity_id">EX_SSOLV</data><data key="edge_relationship_type">historical_request_volume_recorded_by</data><data key="edge_target_entity_id">R183_E008</data><data key="edge_operational_context">GAO provides FY2007/FY2008 comparison; differing request definitions should be retained.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0036" source="EX_HAVV" target="R183_E008"><data key="edge_relationship_id">R183_REL0036</data><data key="edge_source_entity_id">EX_HAVV</data><data key="edge_relationship_type">historical_request_volume_recorded_by</data><data key="edge_target_entity_id">R183_E008</data><data key="edge_operational_context">GAO provides FY2007/FY2008 comparison; differing request definitions should be retained.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0037" source="EX_SOLQ" target="R183_E008"><data key="edge_relationship_id">R183_REL0037</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">historical_request_volume_recorded_by</data><data key="edge_target_entity_id">R183_E008</data><data key="edge_operational_context">GAO provides FY2007/FY2008 comparison; differing request definitions should be retained.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0038" source="APP_EVS" target="R183_E008"><data key="edge_relationship_id">R183_REL0038</data><data key="edge_source_entity_id">APP_EVS</data><data key="edge_relationship_type">historical_request_volume_recorded_by</data><data key="edge_target_entity_id">R183_E008</data><data key="edge_operational_context">GAO provides FY2007/FY2008 comparison; differing request definitions should be retained.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0039" source="R183_E001" target="R183_E009"><data key="edge_relationship_id">R183_REL0039</data><data key="edge_source_entity_id">R183_E001</data><data key="edge_relationship_type">service_incidents_recorded_by</data><data key="edge_target_entity_id">R183_E009</data><data key="edge_operational_context">GAO reported approximately 35 service-impacting incidents in the 14-month observational period.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0040" source="R183_E010" target="R183_E009"><data key="edge_relationship_id">R183_REL0040</data><data key="edge_source_entity_id">R183_E010</data><data key="edge_relationship_type">recorded_exchange_service_incidents</data><data key="edge_target_entity_id">R183_E009</data><data key="edge_operational_context">CAPRS tracked service interruptions recorded by GAO for the 2008-2009 observation window.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0041" source="R183_E011" target="EX_SSOLV"><data key="edge_relationship_id">R183_REL0041</data><data key="edge_source_entity_id">R183_E011</data><data key="edge_relationship_type">monitored_2009_exchange_service</data><data key="edge_target_entity_id">EX_SSOLV</data><data key="edge_operational_context">National operations centers watched SSOLV performance and handled service alerts.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0042" source="R183_E011" target="R183_E010"><data key="edge_relationship_id">R183_REL0042</data><data key="edge_source_entity_id">R183_E011</data><data key="edge_relationship_type">escalated_incidents_into</data><data key="edge_target_entity_id">R183_E010</data><data key="edge_operational_context">Incident owner and resolution updates were tracked through the change/asset/problem system.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0043" source="R183_E012" target="R183_E010"><data key="edge_relationship_id">R183_REL0043</data><data key="edge_source_entity_id">R183_E012</data><data key="edge_relationship_type">created_problem_tracking_in</data><data key="edge_target_entity_id">R183_E010</data><data key="edge_operational_context">National help desk incident management was supported by agency problem reporting process.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">4</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0044" source="R183_E013" target="EX_SSOLV"><data key="edge_relationship_id">R183_REL0044</data><data key="edge_source_entity_id">R183_E013</data><data key="edge_relationship_type">restored_2009_exchange_connection_for</data><data key="edge_target_entity_id">EX_SSOLV</data><data key="edge_operational_context">Historical 34-second failover applied to the AAMVA exchange connection, not all SSA services.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0045" source="R183_E011" target="R183_E013"><data key="edge_relationship_id">R183_REL0045</data><data key="edge_source_entity_id">R183_E011</data><data key="edge_relationship_type">responded_to_incident</data><data key="edge_target_entity_id">R183_E013</data><data key="edge_operational_context">GAO identifies SSA support response moving AAMVA connectivity to the backup connection.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0046" source="R183_E014" target="EX_EVERIFY"><data key="edge_relationship_id">R183_REL0046</data><data key="edge_source_entity_id">R183_E014</data><data key="edge_relationship_type">proposed_future_verification_read_layer_for</data><data key="edge_target_entity_id">EX_EVERIFY</data><data key="edge_operational_context">GAO describes proposed dedicated verification database, not a verified production database.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">4</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0047" source="R183_E015" target="R183_E001"><data key="edge_relationship_id">R183_REL0047</data><data key="edge_source_entity_id">R183_E015</data><data key="edge_relationship_type">proposed_partner_access_surface_for</data><data key="edge_target_entity_id">R183_E001</data><data key="edge_operational_context">2009 vision describes a planned menu-driven partner access portal, not a deployed frontend.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">4</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0048" source="R183_E016" target="R183_E001"><data key="edge_relationship_id">R183_REL0048</data><data key="edge_source_entity_id">R183_E016</data><data key="edge_relationship_type">identified_planning_gap_for</data><data key="edge_target_entity_id">R183_E001</data><data key="edge_operational_context">2009 GAO found missing workload forecasts and target architecture requirements for external exchange growth.</data><data key="edge_observed_as_of">2009-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0049" source="PROC_DEBT_SKIPTRACE" target="R183_E017"><data key="edge_relationship_id">R183_REL0049</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">used_external_observation</data><data key="edge_target_entity_id">R183_E017</data><data key="edge_operational_context">2008 debtor locator procedures call for credit bureau address query after no new address in SSA records.</data><data key="edge_observed_as_of">2008-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0050" source="R183_E017" target="R183_E018"><data key="edge_relationship_id">R183_REL0050</data><data key="edge_source_entity_id">R183_E017</data><data key="edge_relationship_type">requires_human_development_before_record_correction</data><data key="edge_target_entity_id">R183_E018</data><data key="edge_operational_context">A retrieved credit bureau address becomes basis for an employee-driven address update; no automatic bulk update established.</data><data key="edge_observed_as_of">2008-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0051" source="R183_E018" target="SYS_MBR"><data key="edge_relationship_id">R183_REL0051</data><data key="edge_source_entity_id">R183_E018</data><data key="edge_relationship_type">conditional_program_record_update_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2008 POMS directs MBR address change after debtor is located through credit bureau.</data><data key="edge_observed_as_of">2008-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0052" source="R183_E018" target="SYS_SSR"><data key="edge_relationship_id">R183_REL0052</data><data key="edge_source_entity_id">R183_E018</data><data key="edge_relationship_type">conditional_program_record_update_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2008 POMS directs SSR address change after debtor is located through credit bureau.</data><data key="edge_observed_as_of">2008-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0053" source="PROC_DEBT_SKIPTRACE" target="R183_E019"><data key="edge_relationship_id">R183_REL0053</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">documented_in_case_workflow_screen</data><data key="edge_target_entity_id">R183_E019</data><data key="edge_operational_context">RECOOP skiptrace activity is documented on DBST.</data><data key="edge_observed_as_of">2008-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0054" source="R183_E019" target="APP_DMS"><data key="edge_relationship_id">R183_REL0054</data><data key="edge_source_entity_id">R183_E019</data><data key="edge_relationship_type">supports_historical_overpayment_collection_workflow</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">DBST belongs to debt management / RECOOP collection environment, not a beneficiary master.</data><data key="edge_observed_as_of">2008-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0055" source="R183_E017" target="R183_E020"><data key="edge_relationship_id">R183_REL0055</data><data key="edge_source_entity_id">R183_E017</data><data key="edge_relationship_type">subject_to_purpose_restrictions</data><data key="edge_target_entity_id">R183_E020</data><data key="edge_operational_context">FCRA and SSA POMS limit access and require audit oversight; this is not a general-purpose address directory.</data><data key="edge_observed_as_of">2008-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0056" source="PROC_DEBT_SKIPTRACE" target="R183_E020"><data key="edge_relationship_id">R183_REL0056</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">enforced_credit_bureau_access_rules</data><data key="edge_target_entity_id">R183_E020</data><data key="edge_operational_context">Only eligible program-debt collection uses supported, with administrator access to audit traces.</data><data key="edge_observed_as_of">2008-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0057" source="R183_E021" target="SYS_MBR"><data key="edge_relationship_id">R183_REL0057</data><data key="edge_source_entity_id">R183_E021</data><data key="edge_relationship_type">codifies_mbr_payment_attribute</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Country-specific Bulgarian international account number representation on MBR.</data><data key="edge_observed_as_of">2023-10-18</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0058" source="R183_E022" target="SVC_ITS_GOV"><data key="edge_relationship_id">R183_REL0058</data><data key="edge_source_entity_id">R183_E022</data><data key="edge_relationship_type">requires_matching_payment_data_entry</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Staff must enter complete beneficiary and banking information into ITS.gov in the same business day.</data><data key="edge_observed_as_of">2023-10-18</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0059" source="R183_E022" target="APP_POS"><data key="edge_relationship_id">R183_REL0059</data><data key="edge_source_entity_id">R183_E022</data><data key="edge_relationship_type">requires_ssa_program_transaction</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">POS (or other SSA transaction route such as MCS/MACADE) performs direct deposit record updates.</data><data key="edge_observed_as_of">2023-10-18</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0060" source="R183_E023" target="SYS_MBR"><data key="edge_relationship_id">R183_REL0060</data><data key="edge_source_entity_id">R183_E023</data><data key="edge_relationship_type">limits_international_dd_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PCOC code 8 foreign address required before MBR accepts Bulgaria IDD bank coding.</data><data key="edge_observed_as_of">2023-10-18</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0061" source="R183_E023" target="R183_E022"><data key="edge_relationship_id">R183_REL0061</data><data key="edge_source_entity_id">R183_E023</data><data key="edge_relationship_type">preconditions</data><data key="edge_target_entity_id">R183_E022</data><data key="edge_operational_context">Country/address status must be verified before payment data updates.</data><data key="edge_observed_as_of">2023-10-18</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0062" source="R183_E024" target="SVC_ITS_GOV"><data key="edge_relationship_id">R183_REL0062</data><data key="edge_source_entity_id">R183_E024</data><data key="edge_relationship_type">can_result_from_incomplete_entry_into</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Treasury ITS.gov missing fields can trigger Federal Reserve Bank return.</data><data key="edge_observed_as_of">2023-10-18</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0063" source="R183_E022" target="R183_E024"><data key="edge_relationship_id">R183_REL0063</data><data key="edge_source_entity_id">R183_E022</data><data key="edge_relationship_type">must_prevent_exception</data><data key="edge_target_entity_id">R183_E024</data><data key="edge_operational_context">Same-day dual-system entry prevents payment rejections caused by incomplete data.</data><data key="edge_observed_as_of">2023-10-18</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0064" source="PROG_HRS" target="R183_E025"><data key="edge_relationship_id">R183_REL0064</data><data key="edge_source_entity_id">PROG_HRS</data><data key="edge_relationship_type">maintains_restricted_linkage_governance</data><data key="edge_target_entity_id">R183_E025</data><data key="edge_operational_context">HRS maintains restricted datasets linked to SSA administrative earnings and benefits, available through controlled research access.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0065" source="EX_HRS_LINKAGE" target="R183_E027"><data key="edge_relationship_id">R183_REL0065</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">requires_consent_condition</data><data key="edge_target_entity_id">R183_E027</data><data key="edge_operational_context">2009 SSA research note establishes respondent authorization for administrative linkage.</data><data key="edge_observed_as_of">2009</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0066" source="R183_E025" target="R183_E026"><data key="edge_relationship_id">R183_REL0066</data><data key="edge_source_entity_id">R183_E025</data><data key="edge_relationship_type">is_protected_by_release_transform</data><data key="edge_target_entity_id">R183_E026</data><data key="edge_operational_context">Rounding/top coding reduce reidentification risk in linked administrative research products.</data><data key="edge_observed_as_of">2009</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0067" source="R183_E025" target="R183_E028"><data key="edge_relationship_id">R183_REL0067</data><data key="edge_source_entity_id">R183_E025</data><data key="edge_relationship_type">geographically_limited_by</data><data key="edge_target_entity_id">R183_E028</data><data key="edge_operational_context">Linked SSA administrative data must not be accessed from outside US under HRS restrictions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0068" source="DATA_HRS_DER" target="R183_E025"><data key="edge_relationship_id">R183_REL0068</data><data key="edge_source_entity_id">DATA_HRS_DER</data><data key="edge_relationship_type">subject_to_linked_research_data_governance</data><data key="edge_target_entity_id">R183_E025</data><data key="edge_operational_context">Restricted HRS SSA administrative-file family: linkage, consent and researcher access controls apply.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0069" source="DATA_HRS_SER" target="R183_E025"><data key="edge_relationship_id">R183_REL0069</data><data key="edge_source_entity_id">DATA_HRS_SER</data><data key="edge_relationship_type">subject_to_linked_research_data_governance</data><data key="edge_target_entity_id">R183_E025</data><data key="edge_operational_context">Restricted HRS SSA administrative-file family: linkage, consent and researcher access controls apply.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0070" source="DATA_HRS_CYBF" target="R183_E025"><data key="edge_relationship_id">R183_REL0070</data><data key="edge_source_entity_id">DATA_HRS_CYBF</data><data key="edge_relationship_type">subject_to_linked_research_data_governance</data><data key="edge_target_entity_id">R183_E025</data><data key="edge_operational_context">Restricted HRS SSA administrative-file family: linkage, consent and researcher access controls apply.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0071" source="DATA_HRS_SSI" target="R183_E025"><data key="edge_relationship_id">R183_REL0071</data><data key="edge_source_entity_id">DATA_HRS_SSI</data><data key="edge_relationship_type">subject_to_linked_research_data_governance</data><data key="edge_target_entity_id">R183_E025</data><data key="edge_operational_context">Restricted HRS SSA administrative-file family: linkage, consent and researcher access controls apply.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0072" source="MODEL_OASDI_STOCHASTIC" target="R183_E029"><data key="edge_relationship_id">R183_REL0072</data><data key="edge_source_entity_id">MODEL_OASDI_STOCHASTIC</data><data key="edge_relationship_type">produced_historical_valuation</data><data key="edge_target_entity_id">R183_E029</data><data key="edge_operational_context">2014 Trustees model produces a probability distribution for trust fund ratios and depletion years, from the 2014 information set.</data><data key="edge_observed_as_of">2014</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0073" source="R183_E029" target="R183_E030"><data key="edge_relationship_id">R183_REL0073</data><data key="edge_source_entity_id">R183_E029</data><data key="edge_relationship_type">must_be_interpreted_using</data><data key="edge_target_entity_id">R183_E030</data><data key="edge_operational_context">Year-specific percentile summaries cannot be read as a coherent single projected trajectory.</data><data key="edge_observed_as_of">2014</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0074" source="R181_E028" target="R183_E029"><data key="edge_relationship_id">R183_REL0074</data><data key="edge_source_entity_id">R181_E028</data><data key="edge_relationship_type">includes_historical_stochastic_assessment</data><data key="edge_target_entity_id">R183_E029</data><data key="edge_operational_context">2014 Trustees reporting vintage includes stochastic estimate and supplemental annual tables.</data><data key="edge_observed_as_of">2014</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0075" source="R183_E031" target="R183_E033"><data key="edge_relationship_id">R183_REL0075</data><data key="edge_source_entity_id">R183_E031</data><data key="edge_relationship_type">applies_to_contracting_workstream</data><data key="edge_target_entity_id">R183_E033</data><data key="edge_operational_context">Acquisition 360 survey solicitation inclusion applies to qualifying IT awards.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0076" source="R183_E031" target="R183_E034"><data key="edge_relationship_id">R183_REL0076</data><data key="edge_source_entity_id">R183_E031</data><data key="edge_relationship_type">applies_to_contracting_workstream</data><data key="edge_target_entity_id">R183_E034</data><data key="edge_operational_context">Acquisition 360 survey inclusion applies to qualifying non-IT awards exceeding $10 million lifetime value.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R183_REL0077" source="R183_E032" target="R183_E034"><data key="edge_relationship_id">R183_REL0077</data><data key="edge_source_entity_id">R183_E032</data><data key="edge_relationship_type">belongs_to_program_contracts_workstream</data><data key="edge_target_entity_id">R183_E034</data><data key="edge_operational_context">OAG lists Medical Expert Services bundling notification; award details are not established here.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Documented for the stated observation period. Endpoint types and source do not establish deployment or automated updates outside described scope.</data></edge><edge id="R184_R001" source="SYS_MBR" target="R184_E001"><data key="edge_relationship_id">R184_R001</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_title_ii_eligibility_to</data><data key="edge_target_entity_id">R184_E001</data><data key="edge_operational_context">Historical Title II payment eligibility derived from MBR for interagency 2009 ERL matching.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R002" source="SYS_SSR" target="R184_E001"><data key="edge_relationship_id">R184_R002</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_title_xvi_eligibility_to</data><data key="edge_target_entity_id">R184_E001</data><data key="edge_operational_context">Historical Title XVI recipient eligibility input for interagency 2009 ERL matching.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R003" source="ORG_RRB" target="R184_E002"><data key="edge_relationship_id">R184_R003</data><data key="edge_source_entity_id">ORG_RRB</data><data key="edge_relationship_type">supplies_client_ssn_list_via</data><data key="edge_target_entity_id">R184_E002</data><data key="edge_operational_context">RRB provided client SSN information for 2009 ERL eligibility comparison.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R004" source="R184_E002" target="R184_E001"><data key="edge_relationship_id">R184_R004</data><data key="edge_source_entity_id">R184_E002</data><data key="edge_relationship_type">is_matched_against</data><data key="edge_target_entity_id">R184_E001</data><data key="edge_operational_context">RRB client-own-SSN eligibility comparison against Economic Recovery List, not Numident address modification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R005" source="R184_E003" target="R184_E001"><data key="edge_relationship_id">R184_R005</data><data key="edge_source_entity_id">R184_E003</data><data key="edge_relationship_type">matches_eligible_records_from</data><data key="edge_target_entity_id">R184_E001</data><data key="edge_operational_context">One-to-one statutory overlapping-beneficiary payment check against ERL in 2009.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R006" source="R184_E007" target="R184_E001"><data key="edge_relationship_id">R184_R006</data><data key="edge_source_entity_id">R184_E007</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">R184_E001</data><data key="edge_operational_context">SSA RRB response supplied eligibility matched against ERL.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R007" source="R184_E007" target="ORG_RRB"><data key="edge_relationship_id">R184_R007</data><data key="edge_source_entity_id">R184_E007</data><data key="edge_relationship_type">disclosed_to</data><data key="edge_target_entity_id">ORG_RRB</data><data key="edge_operational_context">Historical SSA-to-RRB ERL eligibility response, subject to limited-purpose disclosure.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R008" source="R184_E008" target="R184_E001"><data key="edge_relationship_id">R184_R008</data><data key="edge_source_entity_id">R184_E008</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">R184_E001</data><data key="edge_operational_context">SSA VBA response supplied eligibility matched against ERL.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R009" source="R184_E008" target="ORG_VBA"><data key="edge_relationship_id">R184_R009</data><data key="edge_source_entity_id">R184_E008</data><data key="edge_relationship_type">disclosed_to</data><data key="edge_target_entity_id">ORG_VBA</data><data key="edge_operational_context">Historical SSA-to-VBA one-time payment eligibility response.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R010" source="R184_E001" target="R184_E004"><data key="edge_relationship_id">R184_R010</data><data key="edge_source_entity_id">R184_E001</data><data key="edge_relationship_type">tracks_recovery_and_reclamation</data><data key="edge_target_entity_id">R184_E004</data><data key="edge_operational_context">Payment recovery/returned/nonreceipt/offset status for 2009 stimulus eligibility.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R011" source="R184_E001" target="R184_E005"><data key="edge_relationship_id">R184_R011</data><data key="edge_source_entity_id">R184_E001</data><data key="edge_relationship_type">can_hold_deceased_payee_estate_mailing_address</data><data key="edge_target_entity_id">R184_E005</data><data key="edge_operational_context">Executor estate mailing address for possible reissuance after beneficiary death, not beneficiary residence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R012" source="R184_E006" target="R184_E001"><data key="edge_relationship_id">R184_R012</data><data key="edge_source_entity_id">R184_E006</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">R184_E001</data><data key="edge_operational_context">Tax-credit eligibility information shared with IRS for limited 2009 Making Work Pay purpose.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R013" source="R184_E006" target="ORG_IRS"><data key="edge_relationship_id">R184_R013</data><data key="edge_source_entity_id">R184_E006</data><data key="edge_relationship_type">disclosed_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">2009 limited outgoing recovery payment information, distinct from IRS IMF/IRMF address inquiry.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R014" source="ORG_TREASURY" target="R184_E001"><data key="edge_relationship_id">R184_R014</data><data key="edge_source_entity_id">ORG_TREASURY</data><data key="edge_relationship_type">processes_2009_recovery_disbursement_using</data><data key="edge_target_entity_id">R184_E001</data><data key="edge_operational_context">Treasury payment responsibilities for one-time 2009 recovery payments are separately documented; no asserted direct technical interface.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R184_R015" source="R184_E012" target="R184_E010"><data key="edge_relationship_id">R184_R015</data><data key="edge_source_entity_id">R184_E012</data><data key="edge_relationship_type">supplied_telephony_events_to</data><data key="edge_target_entity_id">R184_E010</data><data key="edge_operational_context">2008 historical vendor-provided ACD network call event records used for web-based MI reporting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R016" source="R184_E012" target="R184_E016"><data key="edge_relationship_id">R184_R016</data><data key="edge_source_entity_id">R184_E012</data><data key="edge_relationship_type">collected_network_call_metadata</data><data key="edge_target_entity_id">R184_E016</data><data key="edge_operational_context">2008 ACD and VoIP routing metadata fields including hold, transfer and call duration.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R017" source="R184_E016" target="R184_E010"><data key="edge_relationship_id">R184_R017</data><data key="edge_source_entity_id">R184_E016</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">R184_E010</data><data key="edge_operational_context">Historical call detail management statistics and operational activity, three-year retention.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R018" source="R184_E009" target="R184_E013"><data key="edge_relationship_id">R184_R018</data><data key="edge_source_entity_id">R184_E009</data><data key="edge_relationship_type">supports_observation_assessment</data><data key="edge_target_entity_id">R184_E013</data><data key="edge_operational_context">Service observation recordings used to prepare employee quality assessments; routine calls auto-delete after 14 days.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R019" source="R184_E009" target="R184_E014"><data key="edge_relationship_id">R184_R019</data><data key="edge_source_entity_id">R184_E009</data><data key="edge_relationship_type">subject_to_60_day_exception</data><data key="edge_target_entity_id">R184_E014</data><data key="edge_operational_context">Unsatisfactory service calls were retained for a longer period under the published 2008 SORN.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R020" source="R184_E013" target="R184_E011"><data key="edge_relationship_id">R184_R020</data><data key="edge_source_entity_id">R184_E013</data><data key="edge_relationship_type">records_quality_observations_in</data><data key="edge_target_entity_id">R184_E011</data><data key="edge_operational_context">Historical quality scores/observations entered into dedicated service observation database.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R021" source="R184_E013" target="R184_E015"><data key="edge_relationship_id">R184_R021</data><data key="edge_source_entity_id">R184_E013</data><data key="edge_relationship_type">can_be_retained_in_personnel_case</data><data key="edge_target_entity_id">R184_E015</data><data key="edge_operational_context">Personnel actions and EEO matters involve separate retention exceptions, not blanket call retention.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R022" source="R184_E011" target="R184_E009"><data key="edge_relationship_id">R184_R022</data><data key="edge_source_entity_id">R184_E011</data><data key="edge_relationship_type">is_not_verified_caller_identity_repository</data><data key="edge_target_entity_id">R184_E009</data><data key="edge_operational_context">Service observation quality assessments are separate from transient caller authentication and voice recordings.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R023" source="R184_E010" target="SYS_MBR"><data key="edge_relationship_id">R184_R023</data><data key="edge_source_entity_id">R184_E010</data><data key="edge_relationship_type">does_not_establish_claimant_address_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Calling telephone numbers and call metadata are not evidence of claimant address or automated MBR update. This is an exclusion/negative finding.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R024" source="R184_E017" target="APP_BOND"><data key="edge_relationship_id">R184_R024</data><data key="edge_source_entity_id">R184_E017</data><data key="edge_relationship_type">managed_historical_demonstration</data><data key="edge_target_entity_id">APP_BOND</data><data key="edge_operational_context">SSA POMS identifies Abt as the outside BOND implementation contractor; project ended in 2024.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R025" source="R184_E017" target="APP_BODS"><data key="edge_relationship_id">R184_R025</data><data key="edge_source_entity_id">R184_E017</data><data key="edge_relationship_type">operated_historical_participant_repository</data><data key="edge_target_entity_id">APP_BODS</data><data key="edge_operational_context">Abt managed historical BOND operations and participant assignment data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R026" source="R184_E018" target="R184_E017"><data key="edge_relationship_id">R184_R026</data><data key="edge_source_entity_id">R184_E018</data><data key="edge_relationship_type">performed_subcontracted_outreach_for</data><data key="edge_target_entity_id">R184_E017</data><data key="edge_operational_context">Historical call-center services subcontracted by Abt for BOND (not current SSA 800-number contract).</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R027" source="APP_BODS" target="R184_E020"><data key="edge_relationship_id">R184_R027</data><data key="edge_source_entity_id">APP_BODS</data><data key="edge_relationship_type">produced_nightly_estimate_data</data><data key="edge_target_entity_id">R184_E020</data><data key="edge_operational_context">Historical nightly participant earnings estimate update process, separate from posted MEF actual earnings.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R028" source="R184_E020" target="APP_BSAS"><data key="edge_relationship_id">R184_R028</data><data key="edge_source_entity_id">R184_E020</data><data key="edge_relationship_type">fed_bond_processing_application</data><data key="edge_target_entity_id">APP_BSAS</data><data key="edge_operational_context">Estimated earnings entered BSAS for historical trial offset calculations.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R029" source="APP_BSAS" target="R184_E022"><data key="edge_relationship_id">R184_R029</data><data key="edge_source_entity_id">APP_BSAS</data><data key="edge_relationship_type">initiated_historical_offset</data><data key="edge_target_entity_id">R184_E022</data><data key="edge_operational_context">BSAS determined offset participation and generated transaction for Title II benefit posting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R030" source="R184_E022" target="APP_MADCAP"><data key="edge_relationship_id">R184_R030</data><data key="edge_source_entity_id">R184_E022</data><data key="edge_relationship_type">automatically_generated_MADCAP_action</data><data key="edge_target_entity_id">APP_MADCAP</data><data key="edge_operational_context">Historical BSAS created a MADCAP action that updated MBR for eligible automated BOND offset cases.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R031" source="R184_E022" target="SYS_MBR"><data key="edge_relationship_id">R184_R031</data><data key="edge_source_entity_id">R184_E022</data><data key="edge_relationship_type">conditionally_updated_title_ii_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Conditional BOND DEMO/offset field changes posted to MBR; applies only to concluded demonstration rules.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R032" source="APP_BSAS" target="R184_E019"><data key="edge_relationship_id">R184_R032</data><data key="edge_source_entity_id">APP_BSAS</data><data key="edge_relationship_type">generated_processing_limitation_alerts_via</data><data key="edge_target_entity_id">R184_E019</data><data key="edge_operational_context">Historical BSAS sent processing limitations through Processing Time Tracker loader.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R033" source="R184_E019" target="APP_PCACS"><data key="edge_relationship_id">R184_R033</data><data key="edge_source_entity_id">R184_E019</data><data key="edge_relationship_type">loaded_processing_alerts_into</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">PTT loader placed BOND processing limitation alert into PCACS as documented by POMS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R034" source="APP_PCACS" target="APP_MACADE"><data key="edge_relationship_id">R184_R034</data><data key="edge_source_entity_id">APP_PCACS</data><data key="edge_relationship_type">referred_bond_exceptions_for_manual_action_in</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">OCO centralized unit handled BOND processing limitations with manual MACADE changes rather than automatic MADCAP posting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R035" source="R184_E021" target="SYS_MEF"><data key="edge_relationship_id">R184_R035</data><data key="edge_source_entity_id">R184_E021</data><data key="edge_relationship_type">used_actual_posted_earnings_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">End-of-year BOND reconciliation relies on posted MEF historical wage totals, not financial institution balances.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R036" source="R184_E021" target="APP_BSAS"><data key="edge_relationship_id">R184_R036</data><data key="edge_source_entity_id">R184_E021</data><data key="edge_relationship_type">compared_estimates_recorded_in</data><data key="edge_target_entity_id">APP_BSAS</data><data key="edge_operational_context">Estimate-to-actual benefit offset reconciliation generally around August.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R037" source="R184_E021" target="R184_E022"><data key="edge_relationship_id">R184_R037</data><data key="edge_source_entity_id">R184_E021</data><data key="edge_relationship_type">could_trigger_adjustment_posting</data><data key="edge_target_entity_id">R184_E022</data><data key="edge_operational_context">Historical reconciliation led to possible underpayment/overpayment calculation and Title II changes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R038" source="R184_E017" target="R184_E023"><data key="edge_relationship_id">R184_R038</data><data key="edge_source_entity_id">R184_E017</data><data key="edge_relationship_type">issued_historical_participation_correspondence</data><data key="edge_target_entity_id">R184_E023</data><data key="edge_operational_context">BOND initial/end program letters prepared outside SSA ORS by contractor.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R039" source="APP_BOND" target="R184_E024"><data key="edge_relationship_id">R184_R039</data><data key="edge_source_entity_id">APP_BOND</data><data key="edge_relationship_type">used_site_assignment_and_foreign_travel_rule</data><data key="edge_target_entity_id">R184_E024</data><data key="edge_operational_context">Historical demonstration participation site eligibility and &gt;90-day foreign travel control.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R040" source="R184_E024" target="SYS_MBR"><data key="edge_relationship_id">R184_R040</data><data key="edge_source_entity_id">R184_E024</data><data key="edge_relationship_type">not_authoritative_master_residence_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Demonstration sampling site and participant travel do not establish current master-record address or automatic updates.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R041" source="APP_UMS_MCAS" target="R184_E025"><data key="edge_relationship_id">R184_R041</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">recorded_staff_time_session_events</data><data key="edge_target_entity_id">R184_E025</data><data key="edge_operational_context">Historical aggregate workforce time/session attributes used for management costing and capacity measurement.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R042" source="APP_UMS_MCAS" target="R184_E026"><data key="edge_relationship_id">R184_R042</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">could_collect_statistical_visitor_location_data</data><data key="edge_target_entity_id">R184_E026</data><data key="edge_operational_context">Limited visitor/claimant location/address attributes in management measurements are not verified residence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R043" source="APP_UMS_MCAS" target="R182_E014"><data key="edge_relationship_id">R184_R043</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">used_historical_mainframe_access_controls</data><data key="edge_target_entity_id">R182_E014</data><data key="edge_operational_context">2008 historical application access subject to TOP SECRET user authorization controls; no current deployment inferred.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R184_R044" source="ORG_AAMVA" target="R184_E027"><data key="edge_relationship_id">R184_R044</data><data key="edge_source_entity_id">ORG_AAMVA</data><data key="edge_relationship_type">awarded_listed_ssa_task_order</data><data key="edge_target_entity_id">R184_E027</data><data key="edge_operational_context">2022 SSA Office of Acquisition and Grants historical award listing, amounts not actual payments.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R045" source="ORG_AAMVA" target="R184_E028"><data key="edge_relationship_id">R184_R045</data><data key="edge_source_entity_id">ORG_AAMVA</data><data key="edge_relationship_type">awarded_later_listed_task_order</data><data key="edge_target_entity_id">R184_E028</data><data key="edge_operational_context">2023 SSA OAG historical award listing, separate from verification-service architecture claims.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R046" source="R184_E027" target="DATA_OAG_HQ_AWARDS"><data key="edge_relationship_id">R184_R046</data><data key="edge_source_entity_id">R184_E027</data><data key="edge_relationship_type">listed_in_official_award_inventory</data><data key="edge_target_entity_id">DATA_OAG_HQ_AWARDS</data><data key="edge_operational_context">OAG publicly identifies award number, award date and listed amount.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R047" source="R184_E028" target="DATA_OAG_HQ_AWARDS"><data key="edge_relationship_id">R184_R047</data><data key="edge_source_entity_id">R184_E028</data><data key="edge_relationship_type">listed_in_official_award_inventory</data><data key="edge_target_entity_id">DATA_OAG_HQ_AWARDS</data><data key="edge_operational_context">OAG publicly identifies historical task order, not live contracted operations.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R048" source="R184_E029" target="R184_E030"><data key="edge_relationship_id">R184_R048</data><data key="edge_source_entity_id">R184_E029</data><data key="edge_relationship_type">later_table_revision_documented_in</data><data key="edge_target_entity_id">R184_E030</data><data key="edge_operational_context">Official SSA page records correction history for previously released 2016 report table data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R049" source="R184_E030" target="SYS_MBR"><data key="edge_relationship_id">R184_R049</data><data key="edge_source_entity_id">R184_E030</data><data key="edge_relationship_type">changes_historical_publication_not_source_master</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Statistical correction changes publication vintage; does not establish alteration of MBR source records.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R184_R050" source="APP_VRRMS" target="APP_IDMS_DIS"><data key="edge_relationship_id">R184_R050</data><data key="edge_source_entity_id">APP_VRRMS</data><data key="edge_relationship_type">historically_no_direct_interface_to</data><data key="edge_target_entity_id">APP_IDMS_DIS</data><data key="edge_operational_context">Negative 2017 technical-interface evidence: VRRMS was described as disconnected from related SSA systems, not a discovered physical API.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R184_R051" source="R184_E031" target="APP_VRRMS"><data key="edge_relationship_id">R184_R051</data><data key="edge_source_entity_id">R184_E031</data><data key="edge_relationship_type">describes_external_system_independence_of</data><data key="edge_target_entity_id">APP_VRRMS</data><data key="edge_operational_context">PIA establishes constrained historical interface design.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R185_R001" source="R185_E001" target="R185_E006"><data key="edge_relationship_id">R185_R001</data><data key="edge_source_entity_id">R185_E001</data><data key="edge_relationship_type">had_obsolete_microfilm_representation</data><data key="edge_target_entity_id">R185_E006</data><data key="edge_operational_context">1978-2000 microfilm copy</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">5</data><data key="edge_notes">Specific microfilm no longer stored; electronic alternatives exist.</data></edge><edge id="R185_R002" source="R185_E001" target="R185_E002"><data key="edge_relationship_id">R185_R002</data><data key="edge_source_entity_id">R185_E001</data><data key="edge_relationship_type">can_be_queried_through</data><data key="edge_target_entity_id">R185_E002</data><data key="edge_operational_context">Historical source query</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">5</data><data key="edge_notes">Availability verified in 2022 policy only.</data></edge><edge id="R185_R003" source="R185_E002" target="R185_E003"><data key="edge_relationship_id">R185_R003</data><data key="edge_source_entity_id">R185_E002</data><data key="edge_relationship_type">provides_location_candidate_for</data><data key="edge_target_entity_id">R185_E003</data><data key="edge_operational_context">Earnings discrepancy correspondence address lead</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">4</data><data key="edge_notes">AWR and EAMATE historical employer reports, not guaranteed current address.</data></edge><edge id="R185_R004" source="PROC_AWR" target="R185_E003"><data key="edge_relationship_id">R185_R004</data><data key="edge_source_entity_id">PROC_AWR</data><data key="edge_relationship_type">may_supply</data><data key="edge_target_entity_id">R185_E003</data><data key="edge_operational_context">Historic annual wage evidence</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">5</data><data key="edge_notes">Does not replace SSA authoritative address.</data></edge><edge id="R185_R005" source="R185_E003" target="R185_E005"><data key="edge_relationship_id">R185_R005</data><data key="edge_source_entity_id">R185_E003</data><data key="edge_relationship_type">used_conditionally_by</data><data key="edge_target_entity_id">R185_E005</data><data key="edge_operational_context">Closeout only if current case-file address unavailable</data><data key="edge_observed_as_of">2021-11-08</data><data key="edge_confidence">5</data><data key="edge_notes">Historical mailing/address lead only.</data></edge><edge id="R185_R006" source="R185_E004" target="R185_E005"><data key="edge_relationship_id">R185_R006</data><data key="edge_source_entity_id">R185_E004</data><data key="edge_relationship_type">preferred_by</data><data key="edge_target_entity_id">R185_E005</data><data key="edge_operational_context">More recent ED file address first</data><data key="edge_observed_as_of">2021-11-08</data><data key="edge_confidence">5</data><data key="edge_notes">No proven master record change.</data></edge><edge id="R185_R007" source="R185_E005" target="R185_E008"><data key="edge_relationship_id">R185_R007</data><data key="edge_source_entity_id">R185_E005</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R185_E008</data><data key="edge_operational_context">Closure and fallback investigation</data><data key="edge_observed_as_of">2021-11-08</data><data key="edge_confidence">5</data><data key="edge_notes">No address available recorded in ED file when none located.</data></edge><edge id="R185_R008" source="R185_E008" target="R185_E007"><data key="edge_relationship_id">R185_R008</data><data key="edge_source_entity_id">R185_E008</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R185_E007</data><data key="edge_operational_context">Written further development in specified cases</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">5</data><data key="edge_notes">Telephone redevelopment preferred when appropriate.</data></edge><edge id="R185_R009" source="R185_E008" target="APP_ICOR"><data key="edge_relationship_id">R185_R009</data><data key="edge_source_entity_id">R185_E008</data><data key="edge_relationship_type">is_controlled_through</data><data key="edge_target_entity_id">APP_ICOR</data><data key="edge_operational_context">Earnings discrepancy case control</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">5</data><data key="edge_notes">Agency controls discrepancy cases in ICOR.</data></edge><edge id="R185_R010" source="R185_E008" target="R185_E003"><data key="edge_relationship_id">R185_R010</data><data key="edge_source_entity_id">R185_E008</data><data key="edge_relationship_type">investigates</data><data key="edge_target_entity_id">R185_E003</data><data key="edge_operational_context">Historical address as location lead</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">5</data><data key="edge_notes">Reinvestigate when relevant available address was missed.</data></edge><edge id="R185_R011" source="R185_E008" target="DB_GIR"><data key="edge_relationship_id">R185_R011</data><data key="edge_source_entity_id">R185_E008</data><data key="edge_relationship_type">uses_additional_query</data><data key="edge_target_entity_id">DB_GIR</data><data key="edge_operational_context">GIR electronic alternative for retired microfilm</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">5</data><data key="edge_notes">Use only if information can be retrieved.</data></edge><edge id="R185_R012" source="R185_E008" target="TECH_PCOM"><data key="edge_relationship_id">R185_R012</data><data key="edge_source_entity_id">R185_E008</data><data key="edge_relationship_type">uses_additional_query</data><data key="edge_target_entity_id">TECH_PCOM</data><data key="edge_operational_context">PCOM electronic alternative for retired microfilm</data><data key="edge_observed_as_of">2022-01-14</data><data key="edge_confidence">5</data><data key="edge_notes">Not asserted to be underlying database.</data></edge><edge id="R185_R013" source="R185_E009" target="SYS_MEF"><data key="edge_relationship_id">R185_R013</data><data key="edge_source_entity_id">R185_E009</data><data key="edge_relationship_type">supports_later_check_of</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Following October next calendar year</data><data key="edge_observed_as_of">2021-11-08</data><data key="edge_confidence">5</data><data key="edge_notes">Holding file for suspected continuing SSN misuse.</data></edge><edge id="R185_R014" source="R185_E011" target="R185_E010"><data key="edge_relationship_id">R185_R014</data><data key="edge_source_entity_id">R185_E011</data><data key="edge_relationship_type">searches</data><data key="edge_target_entity_id">R185_E010</data><data key="edge_operational_context">Historical 1937-1977 wage period</data><data key="edge_observed_as_of">2011-09-01</data><data key="edge_confidence">5</data><data key="edge_notes">Separate from scouting employer wage reports.</data></edge><edge id="R185_R015" source="R185_E011" target="SYS_MEF"><data key="edge_relationship_id">R185_R015</data><data key="edge_source_entity_id">R185_E011</data><data key="edge_relationship_type">posts_verified_earnings_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Validated historical earnings</data><data key="edge_observed_as_of">2011-09-01</data><data key="edge_confidence">5</data><data key="edge_notes">Conditional when microfilm detail is found.</data></edge><edge id="R185_R016" source="R185_E012" target="R185_E015"><data key="edge_relationship_id">R185_R016</data><data key="edge_source_entity_id">R185_E012</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">R185_E015</data><data key="edge_operational_context">Pre-1978 employer records</data><data key="edge_observed_as_of">2011-09-01</data><data key="edge_confidence">5</data><data key="edge_notes">Retained status unverified.</data></edge><edge id="R185_R017" source="R185_E012" target="SVC_ERQY"><data key="edge_relationship_id">R185_R017</data><data key="edge_source_entity_id">R185_E012</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">SVC_ERQY</data><data key="edge_operational_context">1978 onward employer report queries</data><data key="edge_observed_as_of">2011-09-01</data><data key="edge_confidence">5</data><data key="edge_notes">Employer EIN/name/address returned, no claimant address update implied.</data></edge><edge id="R185_R018" source="R185_E012" target="R185_E001"><data key="edge_relationship_id">R185_R018</data><data key="edge_source_entity_id">R185_E012</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">R185_E001</data><data key="edge_operational_context">Post-1977 employer reports</data><data key="edge_observed_as_of">2011-09-01</data><data key="edge_confidence">5</data><data key="edge_notes">Potential microfilm or electronic path, age variable.</data></edge><edge id="R185_R019" source="APP_ICOR" target="R185_E013"><data key="edge_relationship_id">R185_R019</data><data key="edge_source_entity_id">APP_ICOR</data><data key="edge_relationship_type">documents_reasoning_with</data><data key="edge_target_entity_id">R185_E013</data><data key="edge_operational_context">Earnings correction rationale</data><data key="edge_observed_as_of">2011-09-01</data><data key="edge_confidence">5</data><data key="edge_notes">EART records special circumstances.</data></edge><edge id="R185_R020" source="APP_ICOR" target="R185_E014"><data key="edge_relationship_id">R185_R020</data><data key="edge_source_entity_id">APP_ICOR</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R185_E014</data><data key="edge_operational_context">Evidence basis documentation vs copy retention</data><data key="edge_observed_as_of">2011-09-01</data><data key="edge_confidence">5</data><data key="edge_notes">Wage correction process only.</data></edge><edge id="R185_R021" source="R185_E014" target="R185_E013"><data key="edge_relationship_id">R185_R021</data><data key="edge_source_entity_id">R185_E014</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R185_E013</data><data key="edge_operational_context">EART documentation screen</data><data key="edge_observed_as_of">2011-09-01</data><data key="edge_confidence">5</data><data key="edge_notes">Does not establish general document destruction requirement.</data></edge><edge id="R185_R022" source="PROC_IRS_3857_RESOLUTION" target="R185_E016"><data key="edge_relationship_id">R185_R022</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">may_initiate</data><data key="edge_target_entity_id">R185_E016</data><data key="edge_operational_context">When current postal address needed</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes">Used for contacting taxpayers about SSN dispute.</data></edge><edge id="R185_R023" source="R185_E016" target="FORM_SSA_L2001"><data key="edge_relationship_id">R185_R023</data><data key="edge_source_entity_id">R185_E016</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA_L2001</data><data key="edge_operational_context">Post office address request</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes">No guarantee of USPS response.</data></edge><edge id="R185_R024" source="R185_E016" target="R185_E018"><data key="edge_relationship_id">R185_R024</data><data key="edge_source_entity_id">R185_E016</data><data key="edge_relationship_type">may_produce</data><data key="edge_target_entity_id">R185_E018</data><data key="edge_operational_context">Transient investigative address lead</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">4</data><data key="edge_notes">Storage unspecified.</data></edge><edge id="R185_R025" source="PROC_IRS_3857_RESOLUTION" target="R185_E017"><data key="edge_relationship_id">R185_R025</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">requires_evidence_before</data><data key="edge_target_entity_id">R185_E017</data><data key="edge_operational_context">Correct SSNs and earnings only on evidence</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes">Manual conditional clean-up.</data></edge><edge id="R185_R026" source="R185_E017" target="SYS_NUMIDENT"><data key="edge_relationship_id">R185_R026</data><data key="edge_source_entity_id">R185_E017</data><data key="edge_relationship_type">can_correct</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Incorrect identity cross-reference removal</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes">Not an IRS data-origin automatic update.</data></edge><edge id="R185_R027" source="R185_E019" target="SYS_NUMIDENT"><data key="edge_relationship_id">R185_R027</data><data key="edge_source_entity_id">R185_E019</data><data key="edge_relationship_type">requires_inspection_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Scrambled wages identity proof review</data><data key="edge_observed_as_of">2023-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">May also use original SS5 and employer records.</data></edge><edge id="R185_R028" source="R185_E019" target="R185_E020"><data key="edge_relationship_id">R185_R028</data><data key="edge_source_entity_id">R185_E019</data><data key="edge_relationship_type">precedes</data><data key="edge_target_entity_id">R185_E020</data><data key="edge_operational_context">Proof before transfer-to-suspense decisions</data><data key="edge_observed_as_of">2023-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Earnings ambiguity kept in suspense.</data></edge><edge id="R185_R029" source="R185_E020" target="DB_ESF"><data key="edge_relationship_id">R185_R029</data><data key="edge_source_entity_id">R185_E020</data><data key="edge_relationship_type">places_unattributed_wages_in</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">Move not delete unidentified earnings</data><data key="edge_observed_as_of">2023-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Historical earnings preservation.</data></edge><edge id="R185_R030" source="R185_E021" target="R185_E019"><data key="edge_relationship_id">R185_R030</data><data key="edge_source_entity_id">R185_E021</data><data key="edge_relationship_type">is_location_lead_for</data><data key="edge_target_entity_id">R185_E019</data><data key="edge_operational_context">Latest W-2 can be used to locate worker</data><data key="edge_observed_as_of">2023-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">W2 mailing address not verified residential address.</data></edge><edge id="R185_R031" source="R185_E022" target="APP_WLM"><data key="edge_relationship_id">R185_R031</data><data key="edge_source_entity_id">R185_E022</data><data key="edge_relationship_type">limited_rollout_of</data><data key="edge_target_entity_id">APP_WLM</data><data key="edge_operational_context">2026 domestic phone initial claims</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes">Not nationwide.</data></edge><edge id="R185_R032" source="R185_E022" target="APP_ASC"><data key="edge_relationship_id">R185_R032</data><data key="edge_source_entity_id">R185_E022</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ASC</data><data key="edge_operational_context">ASC appointment creation and WLM distribution</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes">WLM matches to employee skillsets/availability.</data></edge><edge id="R185_R033" source="R185_E022" target="R185_E023"><data key="edge_relationship_id">R185_R033</data><data key="edge_source_entity_id">R185_E022</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R185_E023</data><data key="edge_operational_context">Keep What You Take case ownership</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes">Geographic jurisdiction is not sole return reason.</data></edge><edge id="R185_R034" source="R185_E022" target="R185_E024"><data key="edge_relationship_id">R185_R034</data><data key="edge_source_entity_id">R185_E022</data><data key="edge_relationship_type">has_unresolved_scope_conflict</data><data key="edge_target_entity_id">R185_E024</data><data key="edge_operational_context">12 vs 14 jurisdiction mismatch</data><data key="edge_observed_as_of">2026-08-26</data><data key="edge_confidence">5</data><data key="edge_notes">Nevada and Tennessee in operative text but absent purpose list.</data></edge><edge id="R185_R035" source="APP_WLM" target="R185_E023"><data key="edge_relationship_id">R185_R035</data><data key="edge_source_entity_id">APP_WLM</data><data key="edge_relationship_type">implements_in_limited_rollout</data><data key="edge_target_entity_id">R185_E023</data><data key="edge_operational_context">Case remains with interviewing office</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes">Only named locations documented.</data></edge><edge id="R185_R036" source="R185_E025" target="APP_WORKTRACK"><data key="edge_relationship_id">R185_R036</data><data key="edge_source_entity_id">R185_E025</data><data key="edge_relationship_type">moves_documents_from</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">FO manually profiles DDS/hearings submissions</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes">Emergency message later expired; historical workflow.</data></edge><edge id="R185_R037" source="R185_E025" target="APP_EVIEW"><data key="edge_relationship_id">R185_R037</data><data key="edge_source_entity_id">R185_E025</data><data key="edge_relationship_type">moves_documents_to</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">DDS and Hearings case file workflow</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic document routing asserted.</data></edge><edge id="R185_R038" source="R185_E025" target="R185_E026"><data key="edge_relationship_id">R185_R038</data><data key="edge_source_entity_id">R185_E025</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">R185_E026</data><data key="edge_operational_context">Image quality and correct form type</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes">Verification of case pending in DDS or Hearings.</data></edge><edge id="R185_R039" source="R185_E027" target="APP_WORKTRACK"><data key="edge_relationship_id">R185_R039</data><data key="edge_source_entity_id">R185_E027</data><data key="edge_relationship_type">offers_document_disposition_of</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">Completion choices include NDRed eView Paperless</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes">Disposition status does not establish DDS action.</data></edge><edge id="R185_R040" source="R185_E026" target="R185_E027"><data key="edge_relationship_id">R185_R040</data><data key="edge_source_entity_id">R185_E026</data><data key="edge_relationship_type">gates</data><data key="edge_target_entity_id">R185_E027</data><data key="edge_operational_context">Before submission or routing</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes">Review before delivery.</data></edge><edge id="R185_R041" source="APP_SSI_NOTICES" target="R185_E028"><data key="edge_relationship_id">R185_R041</data><data key="edge_source_entity_id">APP_SSI_NOTICES</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R185_E028</data><data key="edge_operational_context">Separate phone-process input file 2021</data><data key="edge_observed_as_of">2021-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">Telephone service identity undetermined.</data></edge><edge id="R185_R042" source="APP_PAYMT" target="R185_E029"><data key="edge_relationship_id">R185_R042</data><data key="edge_source_entity_id">APP_PAYMT</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R185_E029</data><data key="edge_operational_context">Balance/verification and certification reports</data><data key="edge_observed_as_of">2021-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">Payment reports not benefit master.</data></edge><edge id="R185_R043" source="R185_E029" target="R185_E030"><data key="edge_relationship_id">R185_R043</data><data key="edge_source_entity_id">R185_E029</data><data key="edge_relationship_type">supplies</data><data key="edge_target_entity_id">R185_E030</data><data key="edge_operational_context">Certification review</data><data key="edge_observed_as_of">2021-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">Tool named; no specific deployment technology.</data></edge><edge id="R185_R044" source="APP_SSI_DAILY_EDITS" target="R185_E031"><data key="edge_relationship_id">R185_R044</data><data key="edge_source_entity_id">APP_SSI_DAILY_EDITS</data><data key="edge_relationship_type">implements</data><data key="edge_target_entity_id">R185_E031</data><data key="edge_operational_context">Rejected transactions routed to FOs</data><data key="edge_observed_as_of">2021-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">SSR transaction may remain unposted.</data></edge><edge id="R185_R045" source="APP_SSI_FINVERIFY" target="R185_E032"><data key="edge_relationship_id">R185_R045</data><data key="edge_source_entity_id">APP_SSI_FINVERIFY</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R185_E032</data><data key="edge_operational_context">Treasury-origin verification certification exceptions</data><data key="edge_observed_as_of">2021-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">No auto correction of SSR asserted.</data></edge><edge id="R186_R001" source="R186_E001" target="R186_E002"><data key="edge_relationship_id">R186_R001</data><data key="edge_source_entity_id">R186_E001</data><data key="edge_relationship_type">is_consulted_in</data><data key="edge_target_entity_id">R186_E002</data><data key="edge_operational_context">EOIR status may be verified on the ACIS website for SSI deemed-qualified alien development.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">EOIR status may be verified on the ACIS website for SSI deemed-qualified alien development.</data></edge><edge id="R186_R002" source="R186_E002" target="APP_EP"><data key="edge_relationship_id">R186_R002</data><data key="edge_source_entity_id">R186_E002</data><data key="edge_relationship_type">records_supporting_evidence_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">SSA stores EOIR documentation in Evidence Portal after status verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA stores EOIR documentation in Evidence Portal after status verification.</data></edge><edge id="R186_R003" source="R186_E003" target="APP_EP"><data key="edge_relationship_id">R186_R003</data><data key="edge_source_entity_id">R186_E003</data><data key="edge_relationship_type">is_stored_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">EOIR documents are scanned to SSA Evidence Portal; underlying physical storage is not disclosed.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">EOIR documents are scanned to SSA Evidence Portal; underlying physical storage is not disclosed.</data></edge><edge id="R186_R004" source="R186_E002" target="R186_E003"><data key="edge_relationship_id">R186_R004</data><data key="edge_source_entity_id">R186_E002</data><data key="edge_relationship_type">produces_evidence</data><data key="edge_target_entity_id">R186_E003</data><data key="edge_operational_context">EOIR verification supports the EOIR document evidence recorded for the claim.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">EOIR verification supports the EOIR document evidence recorded for the claim.</data></edge><edge id="R186_R005" source="R186_E004" target="R186_E005"><data key="edge_relationship_id">R186_R005</data><data key="edge_source_entity_id">R186_E004</data><data key="edge_relationship_type">documents_initial_award_in</data><data key="edge_target_entity_id">R186_E005</data><data key="edge_operational_context">Initial MSSICS SSI awards use alien status Z and battery-petition flag Y after verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Initial MSSICS SSI awards use alien status Z and battery-petition flag Y after verification.</data></edge><edge id="R186_R006" source="R186_E004" target="R186_E006"><data key="edge_relationship_id">R186_R006</data><data key="edge_source_entity_id">R186_E004</data><data key="edge_relationship_type">documents_initial_award_in</data><data key="edge_target_entity_id">R186_E006</data><data key="edge_operational_context">Non-MSSICS award path codes AR field and AQ exception code on SSR.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Non-MSSICS award path codes AR field and AQ exception code on SSR.</data></edge><edge id="R186_R007" source="R186_E005" target="APP_MSSICS"><data key="edge_relationship_id">R186_R007</data><data key="edge_source_entity_id">R186_E005</data><data key="edge_relationship_type">is_recorded_through</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">MSSICS records verified deemed-qualified-alien status using two designated status fields.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">MSSICS records verified deemed-qualified-alien status using two designated status fields.</data></edge><edge id="R186_R008" source="R186_E006" target="SYS_SSR"><data key="edge_relationship_id">R186_R008</data><data key="edge_source_entity_id">R186_E006</data><data key="edge_relationship_type">is_recorded_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR carries AR and AQ coding for non-MSSICS award processing.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSR carries AR and AQ coding for non-MSSICS award processing.</data></edge><edge id="R186_R009" source="R186_E007" target="R186_E005"><data key="edge_relationship_id">R186_R009</data><data key="edge_source_entity_id">R186_E007</data><data key="edge_relationship_type">compares_field_semantics</data><data key="edge_target_entity_id">R186_E005</data><data key="edge_operational_context">SSA warns that the MSSICS and SSR status representations differ.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA warns that the MSSICS and SSR status representations differ.</data></edge><edge id="R186_R010" source="R186_E007" target="R186_E006"><data key="edge_relationship_id">R186_R010</data><data key="edge_source_entity_id">R186_E007</data><data key="edge_relationship_type">compares_field_semantics</data><data key="edge_target_entity_id">R186_E006</data><data key="edge_operational_context">SSA warns that the SSR and MSSICS status representations differ.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA warns that the SSR and MSSICS status representations differ.</data></edge><edge id="R186_R011" source="SVC_SAVE" target="R186_E004"><data key="edge_relationship_id">R186_R011</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">supports_evidentiary_verification_for</data><data key="edge_target_entity_id">R186_E004</data><data key="edge_operational_context">Claimant immigration status is checked through DHS SAVE, but program eligibility is determined by SSA.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Claimant immigration status is checked through DHS SAVE, but program eligibility is determined by SSA.</data></edge><edge id="R186_R012" source="R186_E008" target="R186_E004"><data key="edge_relationship_id">R186_R012</data><data key="edge_source_entity_id">R186_E008</data><data key="edge_relationship_type">is_reviewed_for</data><data key="edge_target_entity_id">R186_E004</data><data key="edge_operational_context">Proof of separate residence is reviewed as a condition of battery-based SSI eligibility.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Proof of separate residence is reviewed as a condition of battery-based SSI eligibility.</data></edge><edge id="R186_R013" source="R186_E009" target="R186_E008"><data key="edge_relationship_id">R186_R013</data><data key="edge_source_entity_id">R186_E009</data><data key="edge_relationship_type">requests_evidence</data><data key="edge_target_entity_id">R186_E008</data><data key="edge_operational_context">The 30-day work diary tracks submission of evidence that residence is separate from batterer.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">The 30-day work diary tracks submission of evidence that residence is separate from batterer.</data></edge><edge id="R186_R014" source="R186_E009" target="R186_E004"><data key="edge_relationship_id">R186_R014</data><data key="edge_source_entity_id">R186_E009</data><data key="edge_relationship_type">controls_processing_of</data><data key="edge_target_entity_id">R186_E004</data><data key="edge_operational_context">Failure to provide required residence proof after the development period may cause denial.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Failure to provide required residence proof after the development period may cause denial.</data></edge><edge id="R186_R015" source="R186_E010" target="R186_E004"><data key="edge_relationship_id">R186_R015</data><data key="edge_source_entity_id">R186_E010</data><data key="edge_relationship_type">tracks_ongoing_eligibility_of</data><data key="edge_target_entity_id">R186_E004</data><data key="edge_operational_context">AT diary flags postentitlement SSI status based on battery.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">AT diary flags postentitlement SSI status based on battery.</data></edge><edge id="R186_R016" source="R186_E011" target="R186_E004"><data key="edge_relationship_id">R186_R016</data><data key="edge_source_entity_id">R186_E011</data><data key="edge_relationship_type">tracks_review_of</data><data key="edge_target_entity_id">R186_E004</data><data key="edge_operational_context">Prima facie determination has a 150-day review point.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Prima facie determination has a 150-day review point.</data></edge><edge id="R186_R017" source="R186_E012" target="R186_E004"><data key="edge_relationship_id">R186_R017</data><data key="edge_source_entity_id">R186_E012</data><data key="edge_relationship_type">tracks_ongoing_eligibility_of</data><data key="edge_target_entity_id">R186_E004</data><data key="edge_operational_context">Annual review includes DHS SAVE verification and separate-residence evaluation as relevant.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Annual review includes DHS SAVE verification and separate-residence evaluation as relevant.</data></edge><edge id="R186_R018" source="R186_E012" target="SVC_SAVE"><data key="edge_relationship_id">R186_R018</data><data key="edge_source_entity_id">R186_E012</data><data key="edge_relationship_type">uses_verification_service</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">Annual petition-based status reverification uses DHS SAVE and scanned documentation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Annual petition-based status reverification uses DHS SAVE and scanned documentation.</data></edge><edge id="R186_R019" source="R186_E013" target="SYS_SSR"><data key="edge_relationship_id">R186_R019</data><data key="edge_source_entity_id">R186_E013</data><data key="edge_relationship_type">updates_status_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">PR-9 input and SSR remarks record status changes; denial processed with 1719B.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">PR-9 input and SSR remarks record status changes; denial processed with 1719B.</data></edge><edge id="R186_R020" source="R186_E013" target="APP_MSSICS"><data key="edge_relationship_id">R186_R020</data><data key="edge_source_entity_id">R186_E013</data><data key="edge_relationship_type">addresses_code_limitation_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">SSA POMS labels this scenario a MSSICS limitation requiring PR-9 plus 1719B action.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA POMS labels this scenario a MSSICS limitation requiring PR-9 plus 1719B action.</data></edge><edge id="R186_R021" source="R186_E013" target="R186_E004"><data key="edge_relationship_id">R186_R021</data><data key="edge_source_entity_id">R186_E013</data><data key="edge_relationship_type">responds_to_change_in</data><data key="edge_target_entity_id">R186_E004</data><data key="edge_operational_context">Only after legal status or exception changes does SSA process corresponding record changes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Only after legal status or exception changes does SSA process corresponding record changes.</data></edge><edge id="R186_R022" source="R186_E014" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R186_R022</data><data key="edge_source_entity_id">R186_E014</data><data key="edge_relationship_type">classifies_alerts_from</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">Alert payer EIN is used to classify the interest transaction before development.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Alert payer EIN is used to classify the interest transaction before development.</data></edge><edge id="R186_R023" source="R186_E015" target="ORG_BFS"><data key="edge_relationship_id">R186_R023</data><data key="edge_source_entity_id">R186_E015</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">BFS securities verification is routed via specified parallel field office using SSA-562-UF.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">BFS securities verification is routed via specified parallel field office using SSA-562-UF.</data></edge><edge id="R186_R024" source="R186_E015" target="R186_E016"><data key="edge_relationship_id">R186_R024</data><data key="edge_source_entity_id">R186_E015</data><data key="edge_relationship_type">requires_control</data><data key="edge_target_entity_id">R186_E016</data><data key="edge_operational_context">Request requires SSA-8510 and protection of unrelated IRS alert entries.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Request requires SSA-8510 and protection of unrelated IRS alert entries.</data></edge><edge id="R186_R025" source="R186_E015" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R186_R025</data><data key="edge_source_entity_id">R186_E015</data><data key="edge_relationship_type">develops_information_for</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">BFS verification supplies development evidence for IRS 1099 security interest alerts.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">BFS verification supplies development evidence for IRS 1099 security interest alerts.</data></edge><edge id="R186_R026" source="R186_E016" target="FORM_SSA8510"><data key="edge_relationship_id">R186_R026</data><data key="edge_source_entity_id">R186_E016</data><data key="edge_relationship_type">uses_authorization_form</data><data key="edge_target_entity_id">FORM_SSA8510</data><data key="edge_operational_context">SSA-8510 signed consent enables specified third-party securities disclosure.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-8510 signed consent enables specified third-party securities disclosure.</data></edge><edge id="R186_R027" source="R186_E017" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R186_R027</data><data key="edge_source_entity_id">R186_E017</data><data key="edge_relationship_type">develops_discrepancies_for</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">An IRS agricultural subsidy alert triggers county-agency development as needed.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">An IRS agricultural subsidy alert triggers county-agency development as needed.</data></edge><edge id="R186_R028" source="R186_E018" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R186_R028</data><data key="edge_source_entity_id">R186_E018</data><data key="edge_relationship_type">governs_alerts_from</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">Refund-interest alerts from IRS are developed by evidence or claimant allegation rather than direct IRS contact.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Refund-interest alerts from IRS are developed by evidence or claimant allegation rather than direct IRS contact.</data></edge><edge id="R186_R029" source="APP_TPS_BUYIN" target="R186_E019"><data key="edge_relationship_id">R186_R029</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">produces_info_alert</data><data key="edge_target_entity_id">R186_E019</data><data key="edge_operational_context">CMS provides monthly SSI accretion alerts to alert States.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">CMS provides monthly SSI accretion alerts to alert States.</data></edge><edge id="R186_R030" source="APP_TPS_BUYIN" target="R186_E020"><data key="edge_relationship_id">R186_R030</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">produces_info_alert</data><data key="edge_target_entity_id">R186_E020</data><data key="edge_operational_context">CMS generates monthly SSI termination/deletion alerts conditioned on current buy-in enrollment.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">CMS generates monthly SSI termination/deletion alerts conditioned on current buy-in enrollment.</data></edge><edge id="R186_R031" source="R186_E021" target="R120_E001"><data key="edge_relationship_id">R186_R031</data><data key="edge_source_entity_id">R186_E021</data><data key="edge_relationship_type">validates_against</data><data key="edge_target_entity_id">R120_E001</data><data key="edge_operational_context">State accretion must match a CMS Health Insurance Master record before Third-Party Master posting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">State accretion must match a CMS Health Insurance Master record before Third-Party Master posting.</data></edge><edge id="R186_R032" source="R186_E021" target="R127_E022"><data key="edge_relationship_id">R186_R032</data><data key="edge_source_entity_id">R186_E021</data><data key="edge_relationship_type">gates_record_creation_on</data><data key="edge_target_entity_id">R127_E022</data><data key="edge_operational_context">Third-party record creation is conditional on HIM identity reconciliation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Third-party record creation is conditional on HIM identity reconciliation.</data></edge><edge id="R186_R033" source="EX_STATE_BUYIN" target="R186_E021"><data key="edge_relationship_id">R186_R033</data><data key="edge_source_entity_id">EX_STATE_BUYIN</data><data key="edge_relationship_type">uses_validation_rule</data><data key="edge_target_entity_id">R186_E021</data><data key="edge_operational_context">State accretion requests are screened against HIM matching fields.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">State accretion requests are screened against HIM matching fields.</data></edge><edge id="R186_R034" source="APP_TPS_BUYIN" target="R186_E022"><data key="edge_relationship_id">R186_R034</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">generates_responses</data><data key="edge_target_entity_id">R186_E022</data><data key="edge_operational_context">Third-Party System returns acknowledged, rejected or interim disposition for state actions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Third-Party System returns acknowledged, rejected or interim disposition for state actions.</data></edge><edge id="R186_R035" source="EX_STATE_BUYIN" target="R186_E022"><data key="edge_relationship_id">R186_R035</data><data key="edge_source_entity_id">EX_STATE_BUYIN</data><data key="edge_relationship_type">exposes_response_product</data><data key="edge_target_entity_id">R186_E022</data><data key="edge_operational_context">States receive CMS response to accretion/deletion action.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">States receive CMS response to accretion/deletion action.</data></edge><edge id="R186_R036" source="R186_E023" target="APP_TPS_BUYIN"><data key="edge_relationship_id">R186_R036</data><data key="edge_source_entity_id">R186_E023</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_TPS_BUYIN</data><data key="edge_operational_context">CMS adjusts buy-in date no earlier than Medicare entitlement date.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">CMS adjusts buy-in date no earlier than Medicare entitlement date.</data></edge><edge id="R186_R037" source="R186_E024" target="APP_TPS_BUYIN"><data key="edge_relationship_id">R186_R037</data><data key="edge_source_entity_id">R186_E024</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_TPS_BUYIN</data><data key="edge_operational_context">CMS limits effective deletion retroactivity to a two-month window.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">CMS limits effective deletion retroactivity to a two-month window.</data></edge><edge id="R186_R038" source="EX_STATE_BUYIN" target="R186_E025"><data key="edge_relationship_id">R186_R038</data><data key="edge_source_entity_id">EX_STATE_BUYIN</data><data key="edge_relationship_type">carries_deletion</data><data key="edge_target_entity_id">R186_E025</data><data key="edge_operational_context">SSA transmits death-based buy-in deletion through regular monthly data exchange to CMS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA transmits death-based buy-in deletion through regular monthly data exchange to CMS.</data></edge><edge id="R186_R039" source="R186_E025" target="APP_TPS_BUYIN"><data key="edge_relationship_id">R186_R039</data><data key="edge_source_entity_id">R186_E025</data><data key="edge_relationship_type">is_processed_by</data><data key="edge_target_entity_id">APP_TPS_BUYIN</data><data key="edge_operational_context">CMS Third-Party System deletes buy-in with effective month of death.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">CMS Third-Party System deletes buy-in with effective month of death.</data></edge><edge id="R186_R040" source="EX_STATE_BUYIN" target="R186_E026"><data key="edge_relationship_id">R186_R040</data><data key="edge_source_entity_id">EX_STATE_BUYIN</data><data key="edge_relationship_type">carries_deletion</data><data key="edge_target_entity_id">R186_E026</data><data key="edge_operational_context">SSA sends Medicare eligibility-loss deletion to CMS in monthly exchange.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA sends Medicare eligibility-loss deletion to CMS in monthly exchange.</data></edge><edge id="R186_R041" source="R186_E026" target="APP_TPS_BUYIN"><data key="edge_relationship_id">R186_R041</data><data key="edge_source_entity_id">R186_E026</data><data key="edge_relationship_type">is_processed_by</data><data key="edge_target_entity_id">APP_TPS_BUYIN</data><data key="edge_operational_context">CMS Third-Party System terminates buy-in in Medicare termination month/year.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">CMS Third-Party System terminates buy-in in Medicare termination month/year.</data></edge><edge id="R186_R042" source="SVC_E1696" target="R186_E027"><data key="edge_relationship_id">R186_R042</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">generates_document</data><data key="edge_target_entity_id">R186_E027</data><data key="edge_operational_context">Upon electronically signed form submission SSA creates Form SSA-1696-APP image.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Upon electronically signed form submission SSA creates Form SSA-1696-APP image.</data></edge><edge id="R186_R043" source="R186_E027" target="APP_WORKTRACK"><data key="edge_relationship_id">R186_R043</data><data key="edge_source_entity_id">R186_E027</data><data key="edge_relationship_type">is_received_in</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">Field office technician receives electronic image through WorkTrack.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Field office technician receives electronic image through WorkTrack.</data></edge><edge id="R186_R044" source="APP_800_EMPVER" target="R186_E028"><data key="edge_relationship_id">R186_R044</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">enforces_per_call_limit</data><data key="edge_target_entity_id">R186_E028</data><data key="edge_operational_context">TNEV speech recognition accepts up to ten employee SSNs in one call.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">TNEV speech recognition accepts up to ten employee SSNs in one call.</data></edge><edge id="R186_R045" source="APP_800_EMPVER" target="R186_E029"><data key="edge_relationship_id">R186_R045</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">requires_authentication_gate</data><data key="edge_target_entity_id">R186_E029</data><data key="edge_operational_context">Call prompts for IRES credentials with a single permitted attempt.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Call prompts for IRES credentials with a single permitted attempt.</data></edge><edge id="R186_R046" source="R186_E029" target="APP_IRES"><data key="edge_relationship_id">R186_R046</data><data key="edge_source_entity_id">R186_E029</data><data key="edge_relationship_type">authenticates_against</data><data key="edge_target_entity_id">APP_IRES</data><data key="edge_operational_context">User ID and self-selected password were issued by IRES access-control utility.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">User ID and self-selected password were issued by IRES access-control utility.</data></edge><edge id="R186_R047" source="R186_E030" target="APP_WEIA"><data key="edge_relationship_id">R186_R047</data><data key="edge_source_entity_id">R186_E030</data><data key="edge_relationship_type">governs_authorization_in</data><data key="edge_target_entity_id">APP_WEIA</data><data key="edge_operational_context">WEIA applicant signing authority relies on competence or legal parent/guardian status, not merely payee appointment.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">WEIA applicant signing authority relies on competence or legal parent/guardian status, not merely payee appointment.</data></edge><edge id="R186_R048" source="R186_E030" target="EX_PIE"><data key="edge_relationship_id">R186_R048</data><data key="edge_source_entity_id">R186_E030</data><data key="edge_relationship_type">governs_disclosure_for</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">PIE wage access requires properly authorized consent; payee status alone is insufficient.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">PIE wage access requires properly authorized consent; payee status alone is insufficient.</data></edge><edge id="R186_R049" source="R186_E031" target="APP_WEIA"><data key="edge_relationship_id">R186_R049</data><data key="edge_source_entity_id">R186_E031</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_WEIA</data><data key="edge_operational_context">Title II and Title XVI require separate program-based authorization decisions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Title II and Title XVI require separate program-based authorization decisions.</data></edge><edge id="R186_R050" source="R186_E032" target="APP_WEIA"><data key="edge_relationship_id">R186_R050</data><data key="edge_source_entity_id">R186_E032</data><data key="edge_relationship_type">is_recorded_in</data><data key="edge_target_entity_id">APP_WEIA</data><data key="edge_operational_context">SSA records WEIA revocation in authorization system.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA records WEIA revocation in authorization system.</data></edge><edge id="R186_R051" source="R186_E032" target="EX_PIE"><data key="edge_relationship_id">R186_R051</data><data key="edge_source_entity_id">R186_E032</data><data key="edge_relationship_type">terminates_information_permission_for</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">After SSA processes the revocation, PIE cannot use that person’s authorization.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">After SSA processes the revocation, PIE cannot use that person’s authorization.</data></edge><edge id="R186_R052" source="R186_E033" target="DATA_SSA8240"><data key="edge_relationship_id">R186_R052</data><data key="edge_source_entity_id">R186_E033</data><data key="edge_relationship_type">uses_authorization_form</data><data key="edge_target_entity_id">DATA_SSA8240</data><data key="edge_operational_context">Non-SSI-Claims-system authorization is collected on paper Form SSA-8240.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Non-SSI-Claims-system authorization is collected on paper Form SSA-8240.</data></edge><edge id="R186_R053" source="R186_E033" target="APP_EP"><data key="edge_relationship_id">R186_R053</data><data key="edge_source_entity_id">R186_E033</data><data key="edge_relationship_type">retains_paper_image_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">POMS directs paper SSA-8240 into Evidence Portal for non-SSI-system cases.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">POMS directs paper SSA-8240 into Evidence Portal for non-SSI-system cases.</data></edge><edge id="R186_R054" source="R186_E033" target="APP_WEIA"><data key="edge_relationship_id">R186_R054</data><data key="edge_source_entity_id">R186_E033</data><data key="edge_relationship_type">may_be_reentered_into</data><data key="edge_target_entity_id">APP_WEIA</data><data key="edge_operational_context">When seeded into SSI Claims, employee records earlier paper response in WEIA application.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">When seeded into SSI Claims, employee records earlier paper response in WEIA application.</data></edge><edge id="R186_R055" source="R186_E034" target="FORM_SSA8510"><data key="edge_relationship_id">R186_R055</data><data key="edge_source_entity_id">R186_E034</data><data key="edge_relationship_type">governs_third_party_disclosure_via</data><data key="edge_target_entity_id">FORM_SSA8510</data><data key="edge_operational_context">SSI third-party disclosure requires a wet signature for Form SSA-8510; not telephone attestation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSI third-party disclosure requires a wet signature for Form SSA-8510; not telephone attestation.</data></edge><edge id="R186_R056" source="R186_E034" target="DATA_SSA8240"><data key="edge_relationship_id">R186_R056</data><data key="edge_source_entity_id">R186_E034</data><data key="edge_relationship_type">is_not_substitute_for</data><data key="edge_target_entity_id">DATA_SSA8240</data><data key="edge_operational_context">SSA-8510 is not a valid wage and employment information authorization form for PIE.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-8510 is not a valid wage and employment information authorization form for PIE.</data></edge><edge id="R186_R057" source="R186_E035" target="ORG_DDS"><data key="edge_relationship_id">R186_R057</data><data key="edge_source_entity_id">R186_E035</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">DDS must assign reviewers independent of initial-level determinations.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">DDS must assign reviewers independent of initial-level determinations.</data></edge><edge id="R186_R058" source="R186_E035" target="R186_E036"><data key="edge_relationship_id">R186_R058</data><data key="edge_source_entity_id">R186_E035</data><data key="edge_relationship_type">requires_evidence_development</data><data key="edge_target_entity_id">R186_E036</data><data key="edge_operational_context">De novo review includes earlier evidence and new sources not adequately developed.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">De novo review includes earlier evidence and new sources not adequately developed.</data></edge><edge id="R186_R059" source="R186_E036" target="APP_ERE"><data key="edge_relationship_id">R186_R059</data><data key="edge_source_entity_id">R186_E036</data><data key="edge_relationship_type">may_request_records_via</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">SSA permits Electronic Records Express among means of requesting evidence quickly.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA permits Electronic Records Express among means of requesting evidence quickly.</data></edge><edge id="R186_R060" source="R186_E037" target="REPO_CEF"><data key="edge_relationship_id">R186_R060</data><data key="edge_source_entity_id">R186_E037</data><data key="edge_relationship_type">governs_case_evidence_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DDS must review/copy relevant prior paper and electronic folder evidence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">DDS must review/copy relevant prior paper and electronic folder evidence.</data></edge><edge id="R186_R061" source="R186_E037" target="ORG_DDS"><data key="edge_relationship_id">R186_R061</data><data key="edge_source_entity_id">R186_E037</data><data key="edge_relationship_type">supports_review_in</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">DDS reconsiders total record including earlier electronic and paper folders.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">DDS reconsiders total record including earlier electronic and paper folders.</data></edge><edge id="R186_R062" source="R186_E038" target="APP_DCPS"><data key="edge_relationship_id">R186_R062</data><data key="edge_source_entity_id">R186_E038</data><data key="edge_relationship_type">writes_case_note_in</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Functional changes may be recorded in DCPS case note instead of new SSA-3373 form.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Functional changes may be recorded in DCPS case note instead of new SSA-3373 form.</data></edge><edge id="R186_R063" source="R186_E038" target="STRUCT_DDE"><data key="edge_relationship_id">R186_R063</data><data key="edge_source_entity_id">R186_E038</data><data key="edge_relationship_type">writes_through_to</data><data key="edge_target_entity_id">STRUCT_DDE</data><data key="edge_operational_context">DDS functional change notes are written through to Disability Determination Explanation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">DDS functional change notes are written through to Disability Determination Explanation.</data></edge><edge id="R186_R064" source="R186_E039" target="APP_MSSICS"><data key="edge_relationship_id">R186_R064</data><data key="edge_source_entity_id">R186_E039</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">SSI case processing follows reasonable extension and third-party assistance requirements.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSI case processing follows reasonable extension and third-party assistance requirements.</data></edge><edge id="R186_R065" source="R186_E034" target="APP_WEIA"><data key="edge_relationship_id">R186_R065</data><data key="edge_source_entity_id">R186_E034</data><data key="edge_relationship_type">separates_wage_authorization_from</data><data key="edge_target_entity_id">APP_WEIA</data><data key="edge_operational_context">SSA-8510 is not wage authorization and is handled separately from WEIA.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-8510 is not wage authorization and is handled separately from WEIA.</data></edge><edge id="R187_R0001" source="APP_SSOARS" target="R187_E0001"><data key="edge_relationship_id">R187_R0001</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">R187_E0001</data><data key="edge_operational_context">SSA FY2025 identifies iStore as a component of SSOARS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0002" source="APP_SSOARS" target="R187_E0002"><data key="edge_relationship_id">R187_R0002</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">R187_E0002</data><data key="edge_operational_context">SSA FY2025 confirms its financial system includes SSO services.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0003" source="R187_E0002" target="R187_E0003"><data key="edge_relationship_id">R187_R0003</data><data key="edge_source_entity_id">R187_E0002</data><data key="edge_relationship_type">enforces</data><data key="edge_target_entity_id">R187_E0003</data><data key="edge_operational_context">FY2025 report specifically identifies MFA-compliant SSO for invoice approvals.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0004" source="R187_E0003" target="APP_SSOARS"><data key="edge_relationship_id">R187_R0004</data><data key="edge_source_entity_id">R187_E0003</data><data key="edge_relationship_type">controls_access_to</data><data key="edge_target_entity_id">APP_SSOARS</data><data key="edge_operational_context">MFA-compliant SSO governs the financial invoice-approval user workflow, not universal SSA authentication.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0005" source="APP_SSOARS" target="R187_E0004"><data key="edge_relationship_id">R187_R0005</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_reporting_component</data><data key="edge_target_entity_id">R187_E0004</data><data key="edge_operational_context">FY2024 financial system report describes implementation of a WebFOCUS reporting replacement.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0006" source="APP_SSOARS" target="R187_E0005"><data key="edge_relationship_id">R187_R0006</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">historically_included</data><data key="edge_target_entity_id">R187_E0005</data><data key="edge_operational_context">FY2024 report names BI Publisher as a legacy reporting component.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0007" source="R187_E0004" target="R187_E0005"><data key="edge_relationship_id">R187_R0007</data><data key="edge_source_entity_id">R187_E0004</data><data key="edge_relationship_type">intended_to_replace</data><data key="edge_target_entity_id">R187_E0005</data><data key="edge_operational_context">FY2024 WebFOCUS implementation was intended to replace BI Publisher.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0008" source="APP_SSOARS" target="R187_E0006"><data key="edge_relationship_id">R187_R0008</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">historically_included</data><data key="edge_target_entity_id">R187_E0006</data><data key="edge_operational_context">FY2024 names WebCenter as a reporting component.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0009" source="R187_E0004" target="R187_E0006"><data key="edge_relationship_id">R187_R0009</data><data key="edge_source_entity_id">R187_E0004</data><data key="edge_relationship_type">intended_to_replace</data><data key="edge_target_entity_id">R187_E0006</data><data key="edge_operational_context">FY2024 plans targeted replacement of WebCenter reporting with WebFOCUS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0010" source="APP_SSOARS" target="R187_E0007"><data key="edge_relationship_id">R187_R0010</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">historically_used</data><data key="edge_target_entity_id">R187_E0007</data><data key="edge_operational_context">Financial controls involved now-unsupported third-party Preventive Controls Governor software.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0011" source="APP_SSOARS" target="R187_E0008"><data key="edge_relationship_id">R187_R0011</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_documented_control</data><data key="edge_target_entity_id">R187_E0008</data><data key="edge_operational_context">Custom form/field validations operated as a SSOARS preventive control in FY2025.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0012" source="R187_E0008" target="R187_E0007"><data key="edge_relationship_id">R187_R0012</data><data key="edge_source_entity_id">R187_E0008</data><data key="edge_relationship_type">replaced</data><data key="edge_target_entity_id">R187_E0007</data><data key="edge_operational_context">FY2025 report explicitly states custom configurations replaced Preventive Controls Governor.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0013" source="APP_SSOARS" target="R187_E0009"><data key="edge_relationship_id">R187_R0013</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">R187_E0009</data><data key="edge_operational_context">FY2025 official report reports implementation of the replacement general-ledger upload.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0014" source="APP_SSOARS" target="R187_E0010"><data key="edge_relationship_id">R187_R0014</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">historically_used</data><data key="edge_target_entity_id">R187_E0010</data><data key="edge_operational_context">FY2025 report describes previous Oracle upload technology reliant on ActiveX.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0015" source="R187_E0009" target="R187_E0010"><data key="edge_relationship_id">R187_R0015</data><data key="edge_source_entity_id">R187_E0009</data><data key="edge_relationship_type">replaced</data><data key="edge_target_entity_id">R187_E0010</data><data key="edge_operational_context">General ledger upload solution replaced Oracle technology reliant on ActiveX.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0016" source="APP_SSOARS" target="R187_E0011"><data key="edge_relationship_id">R187_R0016</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">supports_reporting_under</data><data key="edge_target_entity_id">R187_E0011</data><data key="edge_operational_context">SSA financial system is an accounting source within agency DATA Act/USAspending data-quality workflow; this is governance reporting, not a direct API claim.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data></edge><edge id="R187_R0017" source="R187_E0012" target="R187_E0011"><data key="edge_relationship_id">R187_R0017</data><data key="edge_source_entity_id">R187_E0012</data><data key="edge_relationship_type">uses_standard</data><data key="edge_target_entity_id">R187_E0011</data><data key="edge_operational_context">SSA FY2025 discusses ongoing Governmentwide Spending Data Model and quality validation of DATA Act submissions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0018" source="R187_E0013" target="R187_E0012"><data key="edge_relationship_id">R187_R0018</data><data key="edge_source_entity_id">R187_E0013</data><data key="edge_relationship_type">subject_to_data_quality_plan</data><data key="edge_target_entity_id">R187_E0012</data><data key="edge_operational_context">FY2024 financial report explains missing external USAspending award linkage for FY2023 reported population.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0019" source="R187_E0014" target="R187_E0012"><data key="edge_relationship_id">R187_R0019</data><data key="edge_source_entity_id">R187_E0014</data><data key="edge_relationship_type">subject_to_data_quality_plan</data><data key="edge_target_entity_id">R187_E0012</data><data key="edge_operational_context">FY2024 financial report explains missing external USAspending award linkage for FY2024 reported population.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0020" source="R187_E0015" target="R187_E0012"><data key="edge_relationship_id">R187_R0020</data><data key="edge_source_entity_id">R187_E0015</data><data key="edge_relationship_type">subject_to_data_quality_plan</data><data key="edge_target_entity_id">R187_E0012</data><data key="edge_operational_context">FY2025 unlinked awards are discussed alongside DATA Act data-quality assurance and external publication limitations.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0021" source="R187_E0015" target="R187_E0016"><data key="edge_relationship_id">R187_R0021</data><data key="edge_source_entity_id">R187_E0015</data><data key="edge_relationship_type">has_external_linkage_limitation</data><data key="edge_target_entity_id">R187_E0016</data><data key="edge_operational_context">SSA identifies data matching limitations for 2,512 unlinked awards; should not naively assign those awards to congressional districts.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0022" source="R187_E0014" target="R187_E0016"><data key="edge_relationship_id">R187_R0022</data><data key="edge_source_entity_id">R187_E0014</data><data key="edge_relationship_type">has_external_linkage_limitation</data><data key="edge_target_entity_id">R187_E0016</data><data key="edge_operational_context">FY2024 AFR states 669 unlinked contract and assistance awards cannot link externally in USAspending due to reporting requirements.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0023" source="R187_E0013" target="R187_E0016"><data key="edge_relationship_id">R187_R0023</data><data key="edge_source_entity_id">R187_E0013</data><data key="edge_relationship_type">has_external_linkage_limitation</data><data key="edge_target_entity_id">R187_E0016</data><data key="edge_operational_context">FY2024 AFR reports 484 unlinked awards in FY2023; lack of external linkage is a reporting limitation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0024" source="R187_E0012" target="R187_E0017"><data key="edge_relationship_id">R187_R0024</data><data key="edge_source_entity_id">R187_E0012</data><data key="edge_relationship_type">validates</data><data key="edge_target_entity_id">R187_E0017</data><data key="edge_operational_context">SSA uses DATA Act quality controls and treasury account symbol obligation reconciliation in financial reporting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0025" source="R187_E0015" target="R187_E0016"><data key="edge_relationship_id">R187_R0025</data><data key="edge_source_entity_id">R187_E0015</data><data key="edge_relationship_type">submitted_to</data><data key="edge_target_entity_id">R187_E0016</data><data key="edge_operational_context">FY2025 SSA award submissions appear in USAspending with some external award linkages unavailable.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0026" source="R187_E0018" target="R187_E0019"><data key="edge_relationship_id">R187_R0026</data><data key="edge_source_entity_id">R187_E0018</data><data key="edge_relationship_type">cites_existing_catalog_capability</data><data key="edge_target_entity_id">R187_E0019</data><data key="edge_operational_context">The FY2025 financial report explicitly says the Analytics and Improvements inventory effort leverages existing tools and services such as Enterprise Data Catalog, without naming an implementation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0027" source="R187_E0020" target="R187_E0018"><data key="edge_relationship_id">R187_R0027</data><data key="edge_source_entity_id">R187_E0020</data><data key="edge_relationship_type">planned_to_centralize</data><data key="edge_target_entity_id">R187_E0018</data><data key="edge_operational_context">Two FY2025 inventory-governance initiatives share stated centralization goals; this relation is a governance dependency, not an asserted integrated technology interface.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">3</data></edge><edge id="R187_R0028" source="CAP_ENTERPRISE_LOGGING" target="R187_E0021"><data key="edge_relationship_id">R187_R0028</data><data key="edge_source_entity_id">CAP_ENTERPRISE_LOGGING</data><data key="edge_relationship_type">includes_onboarding</data><data key="edge_target_entity_id">R187_E0021</data><data key="edge_operational_context">FY2025 SSA report documents the enterprise logging Level 1 implementation progress.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0029" source="CAP_ENTERPRISE_LOGGING" target="R187_E0022"><data key="edge_relationship_id">R187_R0029</data><data key="edge_source_entity_id">CAP_ENTERPRISE_LOGGING</data><data key="edge_relationship_type">includes_onboarding</data><data key="edge_target_entity_id">R187_E0022</data><data key="edge_operational_context">FY2025 reports actively onboarding EL Level 2 systems.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0030" source="R187_E0020" target="R187_E0023"><data key="edge_relationship_id">R187_R0030</data><data key="edge_source_entity_id">R187_E0020</data><data key="edge_relationship_type">responds_to_governance_need</data><data key="edge_target_entity_id">R187_E0023</data><data key="edge_operational_context">FY2025 SSA report relates broader cyber governance improvement activity and annual audit findings, not an auditor-verified successful remediation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data></edge><edge id="R187_R0031" source="R187_E0024" target="R187_E0023"><data key="edge_relationship_id">R187_R0031</data><data key="edge_source_entity_id">R187_E0024</data><data key="edge_relationship_type">qualified_by</data><data key="edge_target_entity_id">R187_E0023</data><data key="edge_operational_context">Domain-specific incident-response rating cannot be used to characterize the overall FISMA program rating.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0032" source="APP_SSOARS" target="R187_E0025"><data key="edge_relationship_id">R187_R0032</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R187_E0025</data><data key="edge_operational_context">SSA says SSOARS patches recognized vulnerabilities on CISA KEV list.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0033" source="R187_E0030" target="R187_E0026"><data key="edge_relationship_id">R187_R0033</data><data key="edge_source_entity_id">R187_E0030</data><data key="edge_relationship_type">may_review</data><data key="edge_target_entity_id">R187_E0026</data><data key="edge_operational_context">Claimant may report wages under another SSN or an IRS-issued ITIN; intentional misuse cannot be presumed.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0034" source="R187_E0030" target="R187_E0028"><data key="edge_relationship_id">R187_R0034</data><data key="edge_source_entity_id">R187_E0030</data><data key="edge_relationship_type">routed_through</data><data key="edge_target_entity_id">R187_E0028</data><data key="edge_operational_context">Field offices send qualifying Title II reviews to Center for Program Support regional personnel.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0035" source="R187_E0028" target="R187_E0029"><data key="edge_relationship_id">R187_R0035</data><data key="edge_source_entity_id">R187_E0028</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">R187_E0029</data><data key="edge_operational_context">CPS sends the referral to regional counsel office.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0036" source="R187_E0029" target="R187_E0027"><data key="edge_relationship_id">R187_R0036</data><data key="edge_source_entity_id">R187_E0029</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">R187_E0027</data><data key="edge_operational_context">Regional counsel uses federal court records to determine whether there was a qualifying conviction.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0037" source="R187_E0030" target="R187_E0031"><data key="edge_relationship_id">R187_R0037</data><data key="edge_source_entity_id">R187_E0030</data><data key="edge_relationship_type">requires_followup</data><data key="edge_target_entity_id">R187_E0031</data><data key="edge_operational_context">Field office diaries case 15 days and follows up on missing disposition.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0038" source="R187_E0030" target="R187_E0032"><data key="edge_relationship_id">R187_R0038</data><data key="edge_source_entity_id">R187_E0030</data><data key="edge_relationship_type">carries_address_attributes</data><data key="edge_target_entity_id">R187_E0032</data><data key="edge_operational_context">Referral includes address of record plus other aliases and addresses used.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0039" source="R187_E0030" target="R187_E0033"><data key="edge_relationship_id">R187_R0039</data><data key="edge_source_entity_id">R187_E0030</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R187_E0033</data><data key="edge_operational_context">Separate intent-based OIG referral question; not every cross-SSN report constitutes intentional fraud.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0040" source="R187_E0030" target="SYS_MEF"><data key="edge_relationship_id">R187_R0040</data><data key="edge_source_entity_id">R187_E0030</data><data key="edge_relationship_type">uses_claims_record</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Review concerns asserted covered work and insured-status earnings; no automatic MEF correction established.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data></edge><edge id="R187_R0041" source="R187_E0030" target="SYS_NUMIDENT"><data key="edge_relationship_id">R187_R0041</data><data key="edge_source_entity_id">R187_E0030</data><data key="edge_relationship_type">uses_identity_record</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA evaluates claimant identity and assigned SSN as background to earnings disputes; not direct master update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data></edge><edge id="R187_R0042" source="R187_E0034" target="FORM_IRS4029"><data key="edge_relationship_id">R187_R0042</data><data key="edge_source_entity_id">R187_E0034</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">FORM_IRS4029</data><data key="edge_operational_context">SSA maintains processing status of religious exemption Form 4029 in its Religious Exemption database.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0043" source="PROC_IRS4029_RETURN" target="R187_E0034"><data key="edge_relationship_id">R187_R0043</data><data key="edge_source_entity_id">PROC_IRS4029_RETURN</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">R187_E0034</data><data key="edge_operational_context">Form 4029 return processing includes create/update of religious exemption database records.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0044" source="PROC_IRS4029_RETURN" target="R187_E0036"><data key="edge_relationship_id">R187_R0044</data><data key="edge_source_entity_id">PROC_IRS4029_RETURN</data><data key="edge_relationship_type">consults</data><data key="edge_target_entity_id">R187_E0036</data><data key="edge_operational_context">SSA communicates with IRS MWU as needed for approval and status.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0045" source="R187_E0035" target="FORM_R96_SSA1458"><data key="edge_relationship_id">R187_R0045</data><data key="edge_source_entity_id">R187_E0035</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">FORM_R96_SSA1458</data><data key="edge_operational_context">Form 1458 group verification uses religious group lookup data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0046" source="R187_E0036" target="PROC_IRS4029_RETURN"><data key="edge_relationship_id">R187_R0046</data><data key="edge_source_entity_id">R187_E0036</data><data key="edge_relationship_type">returns_approval_for</data><data key="edge_target_entity_id">PROC_IRS4029_RETURN</data><data key="edge_operational_context">IRS-approved Form 4029 arrives in SSA REU for SSN/DOB verification and later SSA-controlled processing.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0047" source="APP_ESCORR" target="R187_E0037"><data key="edge_relationship_id">R187_R0047</data><data key="edge_source_entity_id">APP_ESCORR</data><data key="edge_relationship_type">conditionally_posts</data><data key="edge_target_entity_id">R187_E0037</data><data key="edge_operational_context">SSA staff key Form 4029 exemption information into ESCORR; POMS directs Q-indicator posting after verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0048" source="R187_E0037" target="SYS_NUMIDENT"><data key="edge_relationship_id">R187_R0048</data><data key="edge_source_entity_id">R187_E0037</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Q/FICA is a coded Numident waiver indicator, not an address update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0049" source="R187_E0034" target="R187_E0038"><data key="edge_relationship_id">R187_R0049</data><data key="edge_source_entity_id">R187_E0034</data><data key="edge_relationship_type">collects_for_status_verification</data><data key="edge_target_entity_id">R187_E0038</data><data key="edge_operational_context">Religious exemption Form 4029 requester status authentication can include mailing address.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0050" source="PROC_IRS4029_RETURN" target="APP_PEBES"><data key="edge_relationship_id">R187_R0050</data><data key="edge_source_entity_id">PROC_IRS4029_RETURN</data><data key="edge_relationship_type">suppresses_statement_using</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">SSA POMS explicitly directs Statement suppression when processed IRS Form 4029 returns.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0051" source="R187_E0039" target="R187_E0040"><data key="edge_relationship_id">R187_R0051</data><data key="edge_source_entity_id">R187_E0039</data><data key="edge_relationship_type">supplements_not_replaces</data><data key="edge_target_entity_id">R187_E0040</data><data key="edge_operational_context">eMailer can supplement evidence development but cannot replace mandatory mailed statutory notice.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0052" source="R187_E0040" target="R187_E0041"><data key="edge_relationship_id">R187_R0052</data><data key="edge_source_entity_id">R187_E0040</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R187_E0041</data><data key="edge_operational_context">SSA policy requires properly stored electronic copies or alternate case file handling for SSI notices.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0053" source="R187_E0040" target="R187_E0043"><data key="edge_relationship_id">R187_R0053</data><data key="edge_source_entity_id">R187_E0040</data><data key="edge_relationship_type">involves_followup</data><data key="edge_target_entity_id">R187_E0043</data><data key="edge_operational_context">Recipient/contact development follows policy notices and response stages.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0054" source="R187_E0042" target="R187_E0040"><data key="edge_relationship_id">R187_R0054</data><data key="edge_source_entity_id">R187_E0042</data><data key="edge_relationship_type">triggers_review_of</data><data key="edge_target_entity_id">R187_E0040</data><data key="edge_operational_context">Returned/forwarded SSI correspondence requires additional location and appropriate contact development.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0055" source="R187_E0041" target="APP_ORS"><data key="edge_relationship_id">R187_R0055</data><data key="edge_source_entity_id">R187_E0041</data><data key="edge_relationship_type">uses_repository</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">ORS stores electronic notices generated through qualifying notice systems.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0056" source="R187_E0041" target="APP_DPS"><data key="edge_relationship_id">R187_R0056</data><data key="edge_source_entity_id">R187_E0041</data><data key="edge_relationship_type">may_receive_from</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">DPS-generated notices can be available through ORS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0057" source="R187_E0041" target="APP_SSTNG"><data key="edge_relationship_id">R187_R0057</data><data key="edge_source_entity_id">R187_E0041</data><data key="edge_relationship_type">may_receive_from</data><data key="edge_target_entity_id">APP_SSTNG</data><data key="edge_operational_context">SSTNG-generated correspondence can be available through ORS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0058" source="R187_E0042" target="SYS_SSR"><data key="edge_relationship_id">R187_R0058</data><data key="edge_source_entity_id">R187_E0042</data><data key="edge_relationship_type">does_not_automatically_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS requires address development rather than treating USPS forwarding as self-authenticating or an automatic SSI master update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0059" source="DB_SUMS_MCAS_RZLI_INTERFACE" target="R187_E0044"><data key="edge_relationship_id">R187_R0059</data><data key="edge_source_entity_id">DB_SUMS_MCAS_RZLI_INTERFACE</data><data key="edge_relationship_type">has_match_data_availability</data><data key="edge_target_entity_id">R187_E0044</data><data key="edge_operational_context">POMS says SSI/IRS alert interface data cover most recent two years and are accessible through MI Central/SSTNG.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data></edge><edge id="R187_R0060" source="WORK_SSI_IRS_5B_DIARY" target="R187_E0045"><data key="edge_relationship_id">R187_R0060</data><data key="edge_source_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_relationship_type">released_under_schedule</data><data key="edge_target_entity_id">R187_E0045</data><data key="edge_operational_context">The 5B workload diary follows SSA published fiscal-year schedule.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0061" source="WORK_SSI_IRS_5H_DIARY" target="R187_E0046"><data key="edge_relationship_id">R187_R0061</data><data key="edge_source_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_relationship_type">may_be_identified_using</data><data key="edge_target_entity_id">R187_E0046</data><data key="edge_operational_context">SSA 5H procedures instruct accessing PE ODS to identify records with pension alerts.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0062" source="R187_E0046" target="SYS_SSR"><data key="edge_relationship_id">R187_R0062</data><data key="edge_source_entity_id">R187_E0046</data><data key="edge_relationship_type">supports_identity_attribution_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">A 5H diary must be attributed to the correct SSI individual or deemor using SSR queries; no automatic IRS address update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data></edge><edge id="R187_R0063" source="WORK_SSI_IRS_5H_DIARY" target="R187_E0047"><data key="edge_relationship_id">R187_R0063</data><data key="edge_source_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_relationship_type">generated_under_match_rule</data><data key="edge_target_entity_id">R187_E0047</data><data key="edge_operational_context">POMS provides eligibility-date, income-type, and matching criteria for 5H alerts.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R187_R0064" source="R187_E0047" target="SYS_SSR"><data key="edge_relationship_id">R187_R0064</data><data key="edge_source_entity_id">R187_E0047</data><data key="edge_relationship_type">compares_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS requires comparison to SSI program recorded unearned income; observed difference starts development, not automatic eligibility termination.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data></edge><edge id="R188_R0001" source="R188_E0001" target="R188_E0002"><data key="edge_relationship_id">R188_R0001</data><data key="edge_source_entity_id">R188_E0001</data><data key="edge_relationship_type">is_extracted_by</data><data key="edge_target_entity_id">R188_E0002</data><data key="edge_operational_context">OEIS draws tax-form addresses separately for ORES/OACT geographic research.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0002" source="R188_E0002" target="R188_E0003"><data key="edge_relationship_id">R188_R0002</data><data key="edge_source_entity_id">R188_E0002</data><data key="edge_relationship_type">uses_geographic_coding_software</data><data key="edge_target_entity_id">R188_E0003</data><data key="edge_operational_context">SSA documents Finalist used during research-specific address-to-state/county coding.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0003" source="R188_E0003" target="R188_E0004"><data key="edge_relationship_id">R188_R0003</data><data key="edge_source_entity_id">R188_E0003</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R188_E0004</data><data key="edge_operational_context">Historical job-level state/county coding is derived from the extracted full tax-form address.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0004" source="R188_E0004" target="R188_E0005"><data key="edge_relationship_id">R188_R0004</data><data key="edge_source_entity_id">R188_E0004</data><data key="edge_relationship_type">historically_written_to</data><data key="edge_target_entity_id">R188_E0005</data><data key="edge_operational_context">2022 methodology describes tape files of geocoded geographic outputs before statistical assembly.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0005" source="R188_E0005" target="R188_E0006"><data key="edge_relationship_id">R188_R0005</data><data key="edge_source_entity_id">R188_E0005</data><data key="edge_relationship_type">supplies</data><data key="edge_target_entity_id">R188_E0006</data><data key="edge_operational_context">MGD process selects one code per worker using geographic coding results from tape.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0006" source="R188_E0004" target="R188_E0007"><data key="edge_relationship_id">R188_R0006</data><data key="edge_source_entity_id">R188_E0004</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R188_E0007</data><data key="edge_operational_context">Records with only one state/county code are treated as gold-standard for the county assignment step.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0007" source="R188_E0007" target="R188_E0008"><data key="edge_relationship_id">R188_R0007</data><data key="edge_source_entity_id">R188_E0007</data><data key="edge_relationship_type">supplies_frequency_distribution_to</data><data key="edge_target_entity_id">R188_E0008</data><data key="edge_operational_context">ZIP-derived frequencies among single-code workers support inference for geographic missing-code workers.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0008" source="R188_E0008" target="R188_E0006"><data key="edge_relationship_id">R188_R0008</data><data key="edge_source_entity_id">R188_E0008</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R188_E0006</data><data key="edge_operational_context">The documented imputation process helps choose one SCC for otherwise uncoded workers.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0009" source="SYS_NUMIDENT" target="R188_E0009"><data key="edge_relationship_id">R188_R0009</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">enriches_research_extract</data><data key="edge_target_entity_id">R188_E0009</data><data key="edge_operational_context">ORES looks up Numident to check SSN validity and add sex, birth and death attributes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0010" source="R188_E0009" target="R188_E0010"><data key="edge_relationship_id">R188_R0010</data><data key="edge_source_entity_id">R188_E0009</data><data key="edge_relationship_type">merged_into</data><data key="edge_target_entity_id">R188_E0010</data><data key="edge_operational_context">The geographic worker file is reunited with Numident-derived demographics in standalone tax-year MGD output.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0011" source="R188_E0006" target="R188_E0010"><data key="edge_relationship_id">R188_R0011</data><data key="edge_source_entity_id">R188_E0006</data><data key="edge_relationship_type">outputs_to</data><data key="edge_target_entity_id">R188_E0010</data><data key="edge_operational_context">MGD holds one selected state/county code per SSN for the sampled tax year.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0012" source="R188_E0012" target="R188_E0010"><data key="edge_relationship_id">R188_R0012</data><data key="edge_source_entity_id">R188_E0012</data><data key="edge_relationship_type">stored_with</data><data key="edge_target_entity_id">R188_E0010</data><data key="edge_operational_context">Output provides a method flag for the inferred geographic assignment.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0013" source="R188_E0017" target="R188_E0010"><data key="edge_relationship_id">R188_R0013</data><data key="edge_source_entity_id">R188_E0017</data><data key="edge_relationship_type">is_geographic_coding_standard_for</data><data key="edge_target_entity_id">R188_E0010</data><data key="edge_operational_context">New worker geography uses FIPS-compatible SCCs.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0014" source="R188_E0010" target="R188_E0011"><data key="edge_relationship_id">R188_R0014</data><data key="edge_source_entity_id">R188_E0010</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R188_E0011</data><data key="edge_operational_context">Annual production tracks input and assignment counts with 32 processing audit reports.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0015" source="R188_E0010" target="R188_E0013"><data key="edge_relationship_id">R188_R0015</data><data key="edge_source_entity_id">R188_E0010</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R188_E0013</data><data key="edge_operational_context">Tax forms processed in nonprimary years are excluded from original primary-year MGD file.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0016" source="R188_E0013" target="R188_E0014"><data key="edge_relationship_id">R188_R0016</data><data key="edge_source_entity_id">R188_E0013</data><data key="edge_relationship_type">has_address_time_uncertainty</data><data key="edge_target_entity_id">R188_E0014</data><data key="edge_operational_context">Late filing can make tax-form reported address temporally inconsistent with the analyzed earnings year.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0017" source="R188_E0010" target="R188_E0015"><data key="edge_relationship_id">R188_R0017</data><data key="edge_source_entity_id">R188_E0010</data><data key="edge_relationship_type">requires_caution_for</data><data key="edge_target_entity_id">R188_E0015</data><data key="edge_operational_context">Raw research source contains unmatched SSNs, unlike validated programmatic MEF posting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0018" source="R188_E0009" target="R188_E0015"><data key="edge_relationship_id">R188_R0018</data><data key="edge_source_entity_id">R188_E0009</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R188_E0015</data><data key="edge_operational_context">SSNs not found in Numident are flagged invalid and receive missing demographic fields.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0019" source="R188_E0010" target="R188_E0016"><data key="edge_relationship_id">R188_R0019</data><data key="edge_source_entity_id">R188_E0010</data><data key="edge_relationship_type">used_for</data><data key="edge_target_entity_id">R188_E0016</data><data key="edge_operational_context">Historical 2014–2021 tax-year MGD files underpin ORES preliminary estimates.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0020" source="ORG_SSA_ORES" target="R188_E0016"><data key="edge_relationship_id">R188_R0020</data><data key="edge_source_entity_id">ORG_SSA_ORES</data><data key="edge_relationship_type">produced</data><data key="edge_target_entity_id">R188_E0016</data><data key="edge_operational_context">SSA ORES research note presents 2014–2021 worker counts using historical MGD data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0021" source="R188_E0010" target="R188_E0020"><data key="edge_relationship_id">R188_R0021</data><data key="edge_source_entity_id">R188_E0010</data><data key="edge_relationship_type">has_absent_earnings_field_caveat</data><data key="edge_target_entity_id">R188_E0020</data><data key="edge_operational_context">The MGD output has geography/demographics but not the type or amount of taxable earnings.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0022" source="DATA_CWHS" target="R188_E0018"><data key="edge_relationship_id">R188_R0022</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">expanded_for_research_as</data><data key="edge_target_entity_id">R188_E0018</data><data key="edge_operational_context">ORES described developing ten-percent CWHS plus high-earner supplement for statistical estimates.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Planned research sampling configuration, not proof current replacement.</data></edge><edge id="R188_R0023" source="R188_E0018" target="R188_E0019"><data key="edge_relationship_id">R188_R0023</data><data key="edge_source_entity_id">R188_E0018</data><data key="edge_relationship_type">planned_to_support</data><data key="edge_target_entity_id">R188_E0019</data><data key="edge_operational_context">Larger sample planned to reduce statistical suppression in state/county annual earnings estimates.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R188_R0024" source="R188_E0010" target="R188_E0019"><data key="edge_relationship_id">R188_R0024</data><data key="edge_source_entity_id">R188_E0010</data><data key="edge_relationship_type">planned_to_support</data><data key="edge_target_entity_id">R188_E0019</data><data key="edge_operational_context">MGD geographic codes were proposed as one input to the new county earnings estimation process.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R188_R0025" source="R188_E0019" target="REPORT_EARN_EMP_SERIES"><data key="edge_relationship_id">R188_R0025</data><data key="edge_source_entity_id">R188_E0019</data><data key="edge_relationship_type">targeted_publication</data><data key="edge_target_entity_id">REPORT_EARN_EMP_SERIES</data><data key="edge_operational_context">ORES aims to improve county earnings tables by replacing original 1-percent sampling.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R188_R0026" source="SYS_MEF" target="R188_E0019"><data key="edge_relationship_id">R188_R0026</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">would_supply_earnings_to</data><data key="edge_target_entity_id">R188_E0019</data><data key="edge_operational_context">New methodology would require separate MEF-derived earnings information, not tax-form geography alone.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Proposed analytical lineage, not a proven production interface.</data></edge><edge id="R188_R0027" source="R177_SDR" target="R188_E0021"><data key="edge_relationship_id">R188_R0027</data><data key="edge_source_entity_id">R177_SDR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R188_E0021</data><data key="edge_operational_context">2022 SSA research identifies the Structured Data Repository among DASH component sources.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0028" source="DB_DIODS" target="R188_E0021"><data key="edge_relationship_id">R188_R0028</data><data key="edge_source_entity_id">DB_DIODS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R188_E0021</data><data key="edge_operational_context">SSA research identifies Disability Operational Data Store among DASH component sources.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0029" source="DATA_DMF" target="R188_E0021"><data key="edge_relationship_id">R188_R0029</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R188_E0021</data><data key="edge_operational_context">DASH receives death/survival information from Death Master File in described research pipeline.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0030" source="R188_E0021" target="R188_E0025"><data key="edge_relationship_id">R188_R0030</data><data key="edge_source_entity_id">R188_E0021</data><data key="edge_relationship_type">refreshes</data><data key="edge_target_entity_id">R188_E0025</data><data key="edge_operational_context">Daily-refreshed disability data support QDD cohort and DDS receipt measurements.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0031" source="R188_E0021" target="R188_E0022"><data key="edge_relationship_id">R188_R0031</data><data key="edge_source_entity_id">R188_E0021</data><data key="edge_relationship_type">joined_with</data><data key="edge_target_entity_id">R188_E0022</data><data key="edge_operational_context">Researchers merged disability longitudinal case data with MTIME processing dates.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0032" source="R188_E0022" target="R188_E0023"><data key="edge_relationship_id">R188_R0032</data><data key="edge_source_entity_id">R188_E0022</data><data key="edge_relationship_type">used_in</data><data key="edge_target_entity_id">R188_E0023</data><data key="edge_operational_context">MTIME provided timing/survival periods for historical QDD analysis.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0033" source="R188_E0021" target="R188_E0023"><data key="edge_relationship_id">R188_R0033</data><data key="edge_source_entity_id">R188_E0021</data><data key="edge_relationship_type">used_in</data><data key="edge_target_entity_id">R188_E0023</data><data key="edge_operational_context">DASH supplied longitudinal disability case and DDS processing data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0034" source="R188_E0023" target="R188_E0025"><data key="edge_relationship_id">R188_R0034</data><data key="edge_source_entity_id">R188_E0023</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R188_E0025</data><data key="edge_operational_context">Joined DASH/MTIME records created historical QDD cases and timing statistics.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0035" source="R188_E0021" target="R188_E0024"><data key="edge_relationship_id">R188_R0035</data><data key="edge_source_entity_id">R188_E0021</data><data key="edge_relationship_type">includes_research_unit</data><data key="edge_target_entity_id">R188_E0024</data><data key="edge_operational_context">Research reports distinguish single filing claims and consolidated disability cases.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0036" source="R188_E0022" target="R188_E0026"><data key="edge_relationship_id">R188_R0036</data><data key="edge_source_entity_id">R188_E0022</data><data key="edge_relationship_type">defined_by</data><data key="edge_target_entity_id">R188_E0026</data><data key="edge_operational_context">MTIME FY boundary is last Friday September-to-last-Friday September.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0037" source="APP_QDD_MODEL" target="R188_E0027"><data key="edge_relationship_id">R188_R0037</data><data key="edge_source_entity_id">APP_QDD_MODEL</data><data key="edge_relationship_type">historically_prioritized_cases_using</data><data key="edge_target_entity_id">R188_E0027</data><data key="edge_operational_context">QDD screening identifies cases for special assignment treatment; not a determination.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0038" source="R188_E0025" target="R188_E0027"><data key="edge_relationship_id">R188_R0038</data><data key="edge_source_entity_id">R188_E0025</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">R188_E0027</data><data key="edge_operational_context">QDD flag is studied separately from ultimate decision and processing time.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0039" source="APP_OIG_ICMS" target="R188_E0028"><data key="edge_relationship_id">R188_R0039</data><data key="edge_source_entity_id">APP_OIG_ICMS</data><data key="edge_relationship_type">produces_or_feeds</data><data key="edge_target_entity_id">R188_E0028</data><data key="edge_operational_context">ICMS data are pulled into standardized FBI incident reporting submissions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0040" source="R188_E0028" target="EX_OIG_NIBRS"><data key="edge_relationship_id">R188_R0040</data><data key="edge_source_entity_id">R188_E0028</data><data key="edge_relationship_type">transmitted_in</data><data key="edge_target_entity_id">EX_OIG_NIBRS</data><data key="edge_operational_context">2026 testimony describes NIBRS report data extracted from ICMS and sent automatically via the established exchange.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0041" source="R188_E0029" target="PROJ_OIG_ANALYTICS_PLATFORM"><data key="edge_relationship_id">R188_R0041</data><data key="edge_source_entity_id">R188_E0029</data><data key="edge_relationship_type">supports_development_of</data><data key="edge_target_entity_id">PROJ_OIG_ANALYTICS_PLATFORM</data><data key="edge_operational_context">Index files and requirements gathering were underway for internal extraction platform in FY2026.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0042" source="R188_E0031" target="APP_OIG_ICMS"><data key="edge_relationship_id">R188_R0042</data><data key="edge_source_entity_id">R188_E0031</data><data key="edge_relationship_type">reviewed_using</data><data key="edge_target_entity_id">APP_OIG_ICMS</data><data key="edge_operational_context">OIG implemented investigative case-management enhancements to review SSN-holder mismatch referrals.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0043" source="R188_E0030" target="ORG_SSA_OIG"><data key="edge_relationship_id">R188_R0043</data><data key="edge_source_entity_id">R188_E0030</data><data key="edge_relationship_type">belongs_to</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">OIG reports redesigning its fraud/imposter report intake web forms.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0044" source="R188_E0033" target="R188_E0032"><data key="edge_relationship_id">R188_R0044</data><data key="edge_source_entity_id">R188_E0033</data><data key="edge_relationship_type">governed_by_destruct_after_validation</data><data key="edge_target_entity_id">R188_E0032</data><data key="edge_operational_context">IRS tax alert personal data require safeguarding and destruction after use unless serving as disposition record.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R188_R0045" source="R188_E0033" target="SYS_SSR"><data key="edge_relationship_id">R188_R0045</data><data key="edge_source_entity_id">R188_E0033</data><data key="edge_relationship_type">is_not_an_automatic_update_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA policy treats IRS alert addresses as restricted tax information subject to investigation; no master address update described.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Negative inference control, not a demonstrated lack of every possible separate workflow.</data></edge><edge id="R189_R001" source="R189_E001" target="R189_E002"><data key="edge_relationship_id">R189_R001</data><data key="edge_source_entity_id">R189_E001</data><data key="edge_relationship_type">contains_documented_data_store</data><data key="edge_target_entity_id">R189_E002</data><data key="edge_operational_context">2012 NDDS/ASSP QA architecture</data><data key="edge_observed_as_of">2012-08-22</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly identifies QA database in ASSP.</data></edge><edge id="R189_R002" source="R189_E001" target="R189_E003"><data key="edge_relationship_id">R189_R002</data><data key="edge_source_entity_id">R189_E001</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">R189_E003</data><data key="edge_operational_context">2012 DDS federal sample selection</data><data key="edge_observed_as_of">2012-08-22</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly describes federal sample-selection capability.</data></edge><edge id="R189_R003" source="R189_E004" target="R189_E005"><data key="edge_relationship_id">R189_R003</data><data key="edge_source_entity_id">R189_E004</data><data key="edge_relationship_type">has_documented_exception_for</data><data key="edge_target_entity_id">R189_E005</data><data key="edge_operational_context">DDS system acquisitions</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit SSADARS exception to complete feasibility-review requirement.</data></edge><edge id="R189_R004" source="R189_E004" target="R189_E006"><data key="edge_relationship_id">R189_R004</data><data key="edge_source_entity_id">R189_E004</data><data key="edge_relationship_type">requires_security_review</data><data key="edge_target_entity_id">R189_E006</data><data key="edge_operational_context">DDS acquisition design controls</data><data key="edge_observed_as_of">2023-09-26</data><data key="edge_confidence">5</data><data key="edge_notes">Security study and regional ISO approval required for DDS system proposals.</data></edge><edge id="R189_R005" source="R189_E006" target="R189_E007"><data key="edge_relationship_id">R189_R005</data><data key="edge_source_entity_id">R189_E006</data><data key="edge_relationship_type">requires_continuity_control</data><data key="edge_target_entity_id">R189_E007</data><data key="edge_operational_context">DDS security and offsite backups</data><data key="edge_observed_as_of">2023-09-26</data><data key="edge_confidence">5</data><data key="edge_notes">DDS system security guidance expects offsite backup and recovery capability.</data></edge><edge id="R189_R006" source="R189_E008" target="SVC_E1696"><data key="edge_relationship_id">R189_R006</data><data key="edge_source_entity_id">R189_E008</data><data key="edge_relationship_type">controls_filing_validation_for</data><data key="edge_target_entity_id">SVC_E1696</data><data key="edge_operational_context">SSA-1696 form-version acceptance</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">New appointments require edition available at date established since December 9 2024.</data></edge><edge id="R189_R007" source="R189_E009" target="SVC_E1696"><data key="edge_relationship_id">R189_R007</data><data key="edge_source_entity_id">R189_E009</data><data key="edge_relationship_type">governs_updates_submitted_through</data><data key="edge_target_entity_id">SVC_E1696</data><data key="edge_operational_context">signed appointment updates</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Specific fields require one or both signers, as documented in 2026 revision.</data></edge><edge id="R189_R008" source="R189_E010" target="SVC_E1696"><data key="edge_relationship_id">R189_R008</data><data key="edge_source_entity_id">R189_E010</data><data key="edge_relationship_type">constrains_case_authorization_of</data><data key="edge_target_entity_id">SVC_E1696</data><data key="edge_operational_context">Title II and Title XVI appointment scoping</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Case-specific scope must not be extrapolated to other claims or programs.</data></edge><edge id="R189_R009" source="R189_E011" target="APP_RASR"><data key="edge_relationship_id">R189_R009</data><data key="edge_source_entity_id">R189_E011</data><data key="edge_relationship_type">triggers_separate_processing_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">partial success representative appointment</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">SSA instructs employees to process appointment notwithstanding failed fee assignment.</data></edge><edge id="R189_R010" source="R189_E012" target="APP_RASR"><data key="edge_relationship_id">R189_R010</data><data key="edge_source_entity_id">R189_E012</data><data key="edge_relationship_type">is_enforced_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">entity affiliation in RASR</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">SSA requires affiliation before fee-payment assignment, not as representative identity.</data></edge><edge id="R189_R011" source="R189_E011" target="SVC_E1696"><data key="edge_relationship_id">R189_R011</data><data key="edge_source_entity_id">R189_E011</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">SVC_E1696</data><data key="edge_operational_context">SSA-1696 fee assignment and appointment</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Failed assignment does not block valid appointment.</data></edge><edge id="R189_R012" source="R189_E014" target="EX_AFI_FI"><data key="edge_relationship_id">R189_R012</data><data key="edge_source_entity_id">R189_E014</data><data key="edge_relationship_type">uses_verification_exchange</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">SSI resource checking</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">AFI program uses account balance retrieval with consent and FI participation caveats.</data></edge><edge id="R189_R013" source="R189_E013" target="UI_SSI_FI_ACCOUNT"><data key="edge_relationship_id">R189_R013</data><data key="edge_source_entity_id">R189_E013</data><data key="edge_relationship_type">controls_resource_calculations_on</data><data key="edge_target_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_operational_context">SSI monthly account resources</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSI policy values balances as of first day of month, with exclusions and deductions.</data></edge><edge id="R189_R014" source="R189_E014" target="UI_SSI_FI_ACCOUNT"><data key="edge_relationship_id">R189_R014</data><data key="edge_source_entity_id">R189_E014</data><data key="edge_relationship_type">supports_documentation_on</data><data key="edge_target_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_operational_context">FI resource account development</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">FI verification populates resource development in SSI Claims UI; exact transport/persistence not inferred.</data></edge><edge id="R189_R015" source="R189_E015" target="UI_SSI_FI_PERMISSION"><data key="edge_relationship_id">R189_R015</data><data key="edge_source_entity_id">R189_E015</data><data key="edge_relationship_type">is_recorded_on</data><data key="edge_target_entity_id">UI_SSI_FI_PERMISSION</data><data key="edge_operational_context">financial permission attribute</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Permission persists in SSI Claims permission UI rather than inferred permanent bank/vendor store.</data></edge><edge id="R189_R016" source="R189_E016" target="EX_AFI_FI"><data key="edge_relationship_id">R189_R016</data><data key="edge_source_entity_id">R189_E016</data><data key="edge_relationship_type">applies_when_account_data_not_available_from</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">manual replacement for eAFI responses</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Manual/alternative proof may permit adjudication before AFI response; later FI data separately addressed.</data></edge><edge id="R189_R017" source="R189_E016" target="UI_SSI_FI_ACCOUNT"><data key="edge_relationship_id">R189_R017</data><data key="edge_source_entity_id">R189_E016</data><data key="edge_relationship_type">documents_evidence_on</data><data key="edge_target_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_operational_context">accepted SSI resource evidence</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Bank statements and FI records establish balances on FI account page.</data></edge><edge id="R189_R018" source="R189_E017" target="R189_E014"><data key="edge_relationship_id">R189_R018</data><data key="edge_source_entity_id">R189_E017</data><data key="edge_relationship_type">is_enforced_by</data><data key="edge_target_entity_id">R189_E014</data><data key="edge_operational_context">mandatory broad FI checks</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Negative lookups and past 25-month balance requests persist despite alternative verification.</data></edge><edge id="R189_R019" source="R189_E018" target="R189_E014"><data key="edge_relationship_id">R189_R019</data><data key="edge_source_entity_id">R189_E018</data><data key="edge_relationship_type">follows_late_response_from</data><data key="edge_target_entity_id">R189_E014</data><data key="edge_operational_context">AFI responses after eligibility action</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSA policy prescribes independent later processing when response arrives post-adjudication.</data></edge><edge id="R189_R020" source="R189_E019" target="UI_SSI_FI_ACCOUNT"><data key="edge_relationship_id">R189_R020</data><data key="edge_source_entity_id">R189_E019</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_operational_context">bank contact metadata for financial verification</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Bank institution address is FI metadata, not beneficiary address.</data></edge><edge id="R189_R021" source="R189_E020" target="R189_E014"><data key="edge_relationship_id">R189_R021</data><data key="edge_source_entity_id">R189_E020</data><data key="edge_relationship_type">restricts_manual_verification_under</data><data key="edge_target_entity_id">R189_E014</data><data key="edge_operational_context">FI telephone account lookups</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Protects account credential secrets; employee not permitted to collect claimant PIN.</data></edge><edge id="R189_R022" source="R189_E021" target="R189_E014"><data key="edge_relationship_id">R189_R022</data><data key="edge_source_entity_id">R189_E021</data><data key="edge_relationship_type">controls_exception_followup_for</data><data key="edge_target_entity_id">R189_E014</data><data key="edge_operational_context">Participating FI verification</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">AFI vendor handles participating FI contact, preventing duplication of direct technician inquiries.</data></edge><edge id="R189_R023" source="R189_E022" target="R189_E013"><data key="edge_relationship_id">R189_R023</data><data key="edge_source_entity_id">R189_E022</data><data key="edge_relationship_type">adjusts_account_valuation_under</data><data key="edge_target_entity_id">R189_E013</data><data key="edge_operational_context">SSI resource first-of-month values</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Early deposited benefit amounts and qualified tax refunds excluded when material, not blanket removal of all deposits.</data></edge><edge id="R189_R024" source="R189_E022" target="UI_SSI_FI_ACCOUNT"><data key="edge_relationship_id">R189_R024</data><data key="edge_source_entity_id">R189_E022</data><data key="edge_relationship_type">documented_on</data><data key="edge_target_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_operational_context">Excluded Amount resource interface</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">SSI Claims FI Account page specifies reason and amount for resource exclusion.</data></edge><edge id="R189_R025" source="R189_E023" target="R189_E024"><data key="edge_relationship_id">R189_R025</data><data key="edge_source_entity_id">R189_E023</data><data key="edge_relationship_type">produces_scenario_output</data><data key="edge_target_entity_id">R189_E024</data><data key="edge_operational_context">OACT single-year proposal projections</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Published proposal-specific annual table is modeled output, not observed trust fund data.</data></edge><edge id="R189_R026" source="R189_E025" target="R189_E026"><data key="edge_relationship_id">R189_R026</data><data key="edge_source_entity_id">R189_E025</data><data key="edge_relationship_type">produces_scenario_output</data><data key="edge_target_entity_id">R189_E026</data><data key="edge_operational_context">OACT trust fund investment scenario tables</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">OACT G1 modeled data series separate from actual trust-fund investment holdings.</data></edge><edge id="R189_R027" source="R189_E027" target="R189_E028"><data key="edge_relationship_id">R189_R027</data><data key="edge_source_entity_id">R189_E027</data><data key="edge_relationship_type">uses_methodological_caveat</data><data key="edge_target_entity_id">R189_E028</data><data key="edge_operational_context">disability processing time statistics</data><data key="edge_observed_as_of">2017-06-26</data><data key="edge_confidence">5</data><data key="edge_notes">Report notes pending cohort censoring and exclusion of claims denied before medical determination.</data></edge><edge id="R189_R028" source="R189_E029" target="EX_PIE"><data key="edge_relationship_id">R189_R028</data><data key="edge_source_entity_id">R189_E029</data><data key="edge_relationship_type">controls_start_of_reliance_on</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">payroll exchange opt-in</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Claimant must continue other wage reporting until SSA confirms PIE receipt.</data></edge><edge id="R190_R0001" source="R190_E001" target="R190_E002"><data key="edge_relationship_id">R190_R0001</data><data key="edge_source_entity_id">R190_E001</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R190_E002</data><data key="edge_operational_context">EPUF demographic component</data><data key="edge_observed_as_of">2011-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0002" source="R190_E001" target="R190_E003"><data key="edge_relationship_id">R190_R0002</data><data key="edge_source_entity_id">R190_E001</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R190_E003</data><data key="edge_operational_context">EPUF annual earnings component</data><data key="edge_observed_as_of">2011-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0003" source="R190_E001" target="SYS_MEF"><data key="edge_relationship_id">R190_R0003</data><data key="edge_source_entity_id">R190_E001</data><data key="edge_relationship_type">based_primarily_on</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">MEF summary segment administrative earnings values</data><data key="edge_observed_as_of">2011-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0004" source="R190_E001" target="R190_E006"><data key="edge_relationship_id">R190_R0004</data><data key="edge_source_entity_id">R190_E001</data><data key="edge_relationship_type">uses_sampling_method</data><data key="edge_target_entity_id">R190_E006</data><data key="edge_operational_context">1-percent SSN systematic sample</data><data key="edge_observed_as_of">2011-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0005" source="R190_E001" target="R190_E005"><data key="edge_relationship_id">R190_R0005</data><data key="edge_source_entity_id">R190_E001</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R190_E005</data><data key="edge_operational_context">research disclosure protections</data><data key="edge_observed_as_of">2011-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0006" source="R190_E002" target="R190_E004"><data key="edge_relationship_id">R190_R0006</data><data key="edge_source_entity_id">R190_E002</data><data key="edge_relationship_type">links_by_randomized_identifier</data><data key="edge_target_entity_id">R190_E004</data><data key="edge_operational_context">public subfile join field</data><data key="edge_observed_as_of">2011-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0007" source="R190_E003" target="R190_E004"><data key="edge_relationship_id">R190_R0007</data><data key="edge_source_entity_id">R190_E003</data><data key="edge_relationship_type">links_by_randomized_identifier</data><data key="edge_target_entity_id">R190_E004</data><data key="edge_operational_context">public subfile join field</data><data key="edge_observed_as_of">2011-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0008" source="R190_E002" target="R190_E006"><data key="edge_relationship_id">R190_R0008</data><data key="edge_source_entity_id">R190_E002</data><data key="edge_relationship_type">stores_aggregate_earnings_period</data><data key="edge_target_entity_id">R190_E006</data><data key="edge_operational_context">1937–1950 aggregate earnings in demographic subfile, method-defined</data><data key="edge_observed_as_of">2011-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0009" source="R190_E007" target="R190_E008"><data key="edge_relationship_id">R190_R0009</data><data key="edge_source_entity_id">R190_E007</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R190_E008</data><data key="edge_operational_context">state age output</data><data key="edge_observed_as_of">2013-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0010" source="R190_E007" target="R190_E009"><data key="edge_relationship_id">R190_R0010</data><data key="edge_source_entity_id">R190_E007</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R190_E009</data><data key="edge_operational_context">state eligibility output</data><data key="edge_observed_as_of">2013-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0011" source="R190_E007" target="R190_E010"><data key="edge_relationship_id">R190_R0011</data><data key="edge_source_entity_id">R190_E007</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R190_E010</data><data key="edge_operational_context">region diagnostic output</data><data key="edge_observed_as_of">2013-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0012" source="R190_E007" target="R190_E011"><data key="edge_relationship_id">R190_R0012</data><data key="edge_source_entity_id">R190_E007</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R190_E011</data><data key="edge_operational_context">Census-area diagnostic output</data><data key="edge_observed_as_of">2013-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0013" source="R190_E007" target="R190_E012"><data key="edge_relationship_id">R190_R0013</data><data key="edge_source_entity_id">R190_E007</data><data key="edge_relationship_type">applies</data><data key="edge_target_entity_id">R190_E012</data><data key="edge_operational_context">disclosure controls</data><data key="edge_observed_as_of">2013-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0014" source="R190_E009" target="R190_E012"><data key="edge_relationship_id">R190_R0014</data><data key="edge_source_entity_id">R190_E009</data><data key="edge_relationship_type">combines_eligibility_categories_under</data><data key="edge_target_entity_id">R190_E012</data><data key="edge_operational_context">blind and disabled reporting categories combined</data><data key="edge_observed_as_of">2013-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0015" source="R190_E010" target="R190_E012"><data key="edge_relationship_id">R190_R0015</data><data key="edge_source_entity_id">R190_E010</data><data key="edge_relationship_type">uses_geographic_aggregation_control</data><data key="edge_target_entity_id">R190_E012</data><data key="edge_operational_context">SSA regions versus state breakout</data><data key="edge_observed_as_of">2013-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0016" source="R190_E011" target="R190_E012"><data key="edge_relationship_id">R190_R0016</data><data key="edge_source_entity_id">R190_E011</data><data key="edge_relationship_type">uses_geographic_aggregation_control</data><data key="edge_target_entity_id">R190_E012</data><data key="edge_operational_context">Census Areas versus state breakout</data><data key="edge_observed_as_of">2013-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0017" source="R190_E013" target="R190_E014"><data key="edge_relationship_id">R190_R0017</data><data key="edge_source_entity_id">R190_E013</data><data key="edge_relationship_type">supplies_sample_to</data><data key="edge_target_entity_id">R190_E014</data><data key="edge_operational_context">SSA Ticket Research File study finder file</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0018" source="R190_E014" target="R190_E015"><data key="edge_relationship_id">R190_R0018</data><data key="edge_source_entity_id">R190_E014</data><data key="edge_relationship_type">provided_to_cms_for_sample_extraction</data><data key="edge_target_entity_id">R190_E015</data><data key="edge_operational_context">CMS selects Medicare enrollment records for sample</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0019" source="R190_E014" target="R190_E016"><data key="edge_relationship_id">R190_R0019</data><data key="edge_source_entity_id">R190_E014</data><data key="edge_relationship_type">provided_to_cms_for_sample_extraction</data><data key="edge_target_entity_id">R190_E016</data><data key="edge_operational_context">CMS selects Medicaid analytic records for sample</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0020" source="R190_E015" target="R190_E017"><data key="edge_relationship_id">R190_R0020</data><data key="edge_source_entity_id">R190_E015</data><data key="edge_relationship_type">contributes_research_data_to</data><data key="edge_target_entity_id">R190_E017</data><data key="edge_operational_context">CMS Medicare enrollment extract joined for research</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0021" source="R190_E016" target="R190_E017"><data key="edge_relationship_id">R190_R0021</data><data key="edge_source_entity_id">R190_E016</data><data key="edge_relationship_type">contributes_research_data_to</data><data key="edge_target_entity_id">R190_E017</data><data key="edge_operational_context">CMS Medicaid extract joined for research</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0022" source="R190_E014" target="R190_E017"><data key="edge_relationship_id">R190_R0022</data><data key="edge_source_entity_id">R190_E014</data><data key="edge_relationship_type">defines_cohort_for</data><data key="edge_target_entity_id">R190_E017</data><data key="edge_operational_context">SSNs and basic identifiers used in historical study join</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0023" source="R190_E017" target="R190_E018"><data key="edge_relationship_id">R190_R0023</data><data key="edge_source_entity_id">R190_E017</data><data key="edge_relationship_type">uses_observation_window</data><data key="edge_target_entity_id">R190_E018</data><data key="edge_operational_context">84-month person-time design</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R190_R0024" source="R190_E017" target="R190_E019"><data key="edge_relationship_id">R190_R0024</data><data key="edge_source_entity_id">R190_E017</data><data key="edge_relationship_type">applies_coverage_definition</data><data key="edge_target_entity_id">R190_E019</data><data key="edge_operational_context">Medicare Part A and full Medicaid only</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct official published documentation; historical workflow/data product; no claim of current physical architecture or automatic master-record update.</data></edge><edge id="R191_R0001" source="R152_E002" target="R191_E001"><data key="edge_relationship_id">R191_R0001</data><data key="edge_source_entity_id">R152_E002</data><data key="edge_relationship_type">permits_conditional_numident_correction</data><data key="edge_target_entity_id">R191_E001</data><data key="edge_operational_context">MBR proof codes B or C may support Numident DOB correction without new age evidence where POMS conditions hold.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0002" source="R191_E001" target="SYS_NUMIDENT"><data key="edge_relationship_id">R191_R0002</data><data key="edge_source_entity_id">R191_E001</data><data key="edge_relationship_type">authorizes_change_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Authorized correction affects Numident after identity and proof-code review; not generalized database replication.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0003" source="R152_E003" target="R191_E002"><data key="edge_relationship_id">R191_R0003</data><data key="edge_source_entity_id">R152_E003</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R191_E002</data><data key="edge_operational_context">An SSR Q age proof indicator requires full age development before Numident correction.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0004" source="R191_E002" target="SYS_NUMIDENT"><data key="edge_relationship_id">R191_R0004</data><data key="edge_source_entity_id">R191_E002</data><data key="edge_relationship_type">limits_evidence_use_for</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">No unconditional write from SSR DOB code Q into Numident.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0005" source="PROC_SSI_INTERSTATE_COA_STAGING" target="R191_E003"><data key="edge_relationship_id">R191_R0005</data><data key="edge_source_entity_id">PROC_SSI_INTERSTATE_COA_STAGING</data><data key="edge_relationship_type">applies</data><data key="edge_target_entity_id">R191_E003</data><data key="edge_operational_context">Interstate change may stage a mailing update while keeping previous residence state/county and payment codes pending investigation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0006" source="R191_E003" target="DATA_SSR_CMPH_SEGMENT"><data key="edge_relationship_id">R191_R0006</data><data key="edge_source_entity_id">R191_E003</data><data key="edge_relationship_type">preserves_prior_state_codes_on</data><data key="edge_target_entity_id">DATA_SSR_CMPH_SEGMENT</data><data key="edge_operational_context">When new residence has not been established, prior codes remain interim; follow-up is necessary.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0007" source="R191_E003" target="UI_MSSICS_DWO1"><data key="edge_relationship_id">R191_R0007</data><data key="edge_source_entity_id">R191_E003</data><data key="edge_relationship_type">may_generate_referral_in</data><data key="edge_target_entity_id">UI_MSSICS_DWO1</data><data key="edge_operational_context">After a move, the old field office may route an unresolved living-arrangement development issue to the new office using DWOI.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0008" source="FORM_SSA8203BK" target="R191_E004"><data key="edge_relationship_id">R191_R0008</data><data key="edge_source_entity_id">FORM_SSA8203BK</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">R191_E004</data><data key="edge_operational_context">Paper redetermination includes a separate claimant-residence prompt and documents mailing discrepancies in remarks.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0009" source="R191_E004" target="UI_SSI_LRES"><data key="edge_relationship_id">R191_R0009</data><data key="edge_source_entity_id">R191_E004</data><data key="edge_relationship_type">has_structured_residence_entry_in</data><data key="edge_target_entity_id">UI_SSI_LRES</data><data key="edge_operational_context">The SSI Claims system records residence in the Residence Address and Jurisdiction page.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0010" source="R191_E004" target="UI_SSI_APID"><data key="edge_relationship_id">R191_R0010</data><data key="edge_source_entity_id">R191_E004</data><data key="edge_relationship_type">has_structured_mailing_entry_in</data><data key="edge_target_entity_id">UI_SSI_APID</data><data key="edge_operational_context">The SSI Claims system records mailing address in Personal Information, General ID.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0011" source="PROC_SSI_WU_S06" target="R191_E005"><data key="edge_relationship_id">R191_R0011</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">includes_system_trigger</data><data key="edge_target_entity_id">R191_E005</data><data key="edge_operational_context">Address-related Treasury check return may initiate automated whereabouts-unknown S06 status.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0012" source="R191_E005" target="SYS_SSR"><data key="edge_relationship_id">R191_R0012</data><data key="edge_source_entity_id">R191_E005</data><data key="edge_relationship_type">changes_payment_status_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The automatic event relates to SSR S06 payment status, not to automatic updating of the residential address.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0013" source="PROC_SSI_WU_S06" target="R191_E006"><data key="edge_relationship_id">R191_R0013</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">applies</data><data key="edge_target_entity_id">R191_E006</data><data key="edge_operational_context">SSA separates required locate attempts from optional bank/SASRO leads.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0014" source="R191_E006" target="FORM_SSA_L2001"><data key="edge_relationship_id">R191_R0014</data><data key="edge_source_entity_id">R191_E006</data><data key="edge_relationship_type">uses_postal_inquiry</data><data key="edge_target_entity_id">FORM_SSA_L2001</data><data key="edge_operational_context">Required postal address inquiry, subject to documented exceptions; USPS response is only a location lead.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0015" source="R191_E006" target="EX_SASRO"><data key="edge_relationship_id">R191_R0015</data><data key="edge_source_entity_id">R191_E006</data><data key="edge_relationship_type">may_consult_state_address_leads_in</data><data key="edge_target_entity_id">EX_SASRO</data><data key="edge_operational_context">State welfare or food-stamp address differences require further development rather than automatic SSR posting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0016" source="R189_E005" target="R191_E007"><data key="edge_relationship_id">R191_R0016</data><data key="edge_source_entity_id">R189_E005</data><data key="edge_relationship_type">generates_or_exposes</data><data key="edge_target_entity_id">R191_E007</data><data key="edge_operational_context">SSADARS printout is identified as the place Spanish notice needs should be reflected.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0017" source="R191_E008" target="R191_E007"><data key="edge_relationship_id">R191_R0017</data><data key="edge_source_entity_id">R191_E008</data><data key="edge_relationship_type">waives_notice_requirement_from</data><data key="edge_target_entity_id">R191_E007</data><data key="edge_operational_context">Signed waiver and claims-folder evidence can override Spanish-notice default for qualifying beneficiaries.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0018" source="R191_E009" target="R191_E007"><data key="edge_relationship_id">R191_R0018</data><data key="edge_source_entity_id">R191_E009</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">R191_E007</data><data key="edge_operational_context">DHU reviews disability folder and SSA-derived language need signals; no automatic SSADARS feed is established.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R191_R0019" source="R191_E009" target="R191_E008"><data key="edge_relationship_id">R191_R0019</data><data key="edge_source_entity_id">R191_E009</data><data key="edge_relationship_type">may_be_waived_using</data><data key="edge_target_entity_id">R191_E008</data><data key="edge_operational_context">Appropriate beneficiary SSA-381-SP and documented waiver are required.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0020" source="R191_E010" target="R191_E011"><data key="edge_relationship_id">R191_R0020</data><data key="edge_source_entity_id">R191_E010</data><data key="edge_relationship_type">is_documented_at</data><data key="edge_target_entity_id">R191_E011</data><data key="edge_operational_context">Email memorandum and case note precede ordering; source does not identify a specific database or email transport architecture.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0021" source="R191_E012" target="R191_E010"><data key="edge_relationship_id">R191_R0021</data><data key="edge_source_entity_id">R191_E012</data><data key="edge_relationship_type">requires_rationale</data><data key="edge_target_entity_id">R191_E010</data><data key="edge_operational_context">An ALJ must document reasoning even when medical-expert evidence is required by authority or the cited equivalence condition.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0022" source="R191_E013" target="R191_E010"><data key="edge_relationship_id">R191_R0022</data><data key="edge_source_entity_id">R191_E013</data><data key="edge_relationship_type">requires_rationale</data><data key="edge_target_entity_id">R191_E010</data><data key="edge_operational_context">Discretionary ME requests require specified case-specific rationale.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0023" source="R191_E014" target="DATA_OACT_INSURED_WORKERS_STATUS"><data key="edge_relationship_id">R191_R0023</data><data key="edge_source_entity_id">R191_E014</data><data key="edge_relationship_type">redirects_publication_to</data><data key="edge_target_entity_id">DATA_OACT_INSURED_WORKERS_STATUS</data><data key="edge_operational_context">Supplement table 4.C1 insured-worker status is provided through the OACT data product rather than duplicated Supplement publication.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0024" source="DATA_OACT_INSURED_WORKERS_STATUS" target="R191_E015"><data key="edge_relationship_id">R191_R0024</data><data key="edge_source_entity_id">DATA_OACT_INSURED_WORKERS_STATUS</data><data key="edge_relationship_type">has_2026_vintage</data><data key="edge_target_entity_id">R191_E015</data><data key="edge_operational_context">Current insured-status publication shows 1940-2026 values and qualified 2026 Trustees/CWHS source provenance.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0025" source="R191_E015" target="DATA_CWHS"><data key="edge_relationship_id">R191_R0025</data><data key="edge_source_entity_id">R191_E015</data><data key="edge_relationship_type">sourced_partly_from</data><data key="edge_target_entity_id">DATA_CWHS</data><data key="edge_operational_context">OACT page explicitly says estimates are based in part on the 1% Continuous Work History Sample.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0026" source="R191_E015" target="R191_E016"><data key="edge_relationship_id">R191_R0026</data><data key="edge_source_entity_id">R191_E015</data><data key="edge_relationship_type">has_age_sex_companion_table</data><data key="edge_target_entity_id">R191_E016</data><data key="edge_operational_context">Separate insured worker age/sex statistical table.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0027" source="R191_E015" target="R191_E017"><data key="edge_relationship_id">R191_R0027</data><data key="edge_source_entity_id">R191_E015</data><data key="edge_relationship_type">has_disability_insured_age_sex_companion</data><data key="edge_target_entity_id">R191_E017</data><data key="edge_operational_context">Age/sex disability-insured counts differ from awards or payments.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0028" source="DATA_OACT_SOCSEC_AREA_INSURED" target="R191_E018"><data key="edge_relationship_id">R191_R0028</data><data key="edge_source_entity_id">DATA_OACT_SOCSEC_AREA_INSURED</data><data key="edge_relationship_type">has_publication_vintage</data><data key="edge_target_entity_id">R191_E018</data><data key="edge_operational_context">OACT population-denominator and insured-share table provides a separate statistical context for insured worker counts.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0029" source="R191_E015" target="R191_E018"><data key="edge_relationship_id">R191_R0029</data><data key="edge_source_entity_id">R191_E015</data><data key="edge_relationship_type">uses_population_denominator_from</data><data key="edge_target_entity_id">R191_E018</data><data key="edge_operational_context">Insured status ratios must use the Social Security area reference population rather than a simple residential census count.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0030" source="R191_E019" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R191_R0030</data><data key="edge_source_entity_id">R191_E019</data><data key="edge_relationship_type">supports_follow_up_in</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">An addressed change report initiates the policy-controlled SSI posteligibility development process; POMS does not identify automatic IRS-origin master updating.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R191_R0031" source="R191_E019" target="R191_E003"><data key="edge_relationship_id">R191_R0031</data><data key="edge_source_entity_id">R191_E019</data><data key="edge_relationship_type">triggers_development_under</data><data key="edge_target_entity_id">R191_E003</data><data key="edge_operational_context">SSI changes of residence can necessitate staged mailing and living-arrangement updates when interstate eligibility factors remain unresolved.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R191_R0032" source="UI_SSI_LRES" target="DATA_SSR_CMPH_SEGMENT"><data key="edge_relationship_id">R191_R0032</data><data key="edge_source_entity_id">UI_SSI_LRES</data><data key="edge_relationship_type">documents_residence_separately_in_2026</data><data key="edge_target_entity_id">DATA_SSR_CMPH_SEGMENT</data><data key="edge_operational_context">Correct residence state/county and living-arrangement inputs affect CMPH Medicaid and SSI computations rather than only postal delivery.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0033" source="R189_E005" target="R191_E009"><data key="edge_relationship_id">R191_R0033</data><data key="edge_source_entity_id">R189_E005</data><data key="edge_relationship_type">documented_in_2023_notice_policy</data><data key="edge_target_entity_id">R191_E009</data><data key="edge_operational_context">The SSADARS printout is named as disability hearing unit language-notice documentation, not a proven data-transfer protocol.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0034" source="R152_E002" target="SYS_NUMIDENT"><data key="edge_relationship_id">R191_R0034</data><data key="edge_source_entity_id">R152_E002</data><data key="edge_relationship_type">requires_code_specific_verification_before</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">MBR age proof codes have conditions; an MBR DOB does not unconditionally replace Numident DOB.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R191_R0035" source="R152_E003" target="SYS_NUMIDENT"><data key="edge_relationship_id">R191_R0035</data><data key="edge_source_entity_id">R152_E003</data><data key="edge_relationship_type">requires_code_specific_verification_before</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSR Q must undergo full age development; specific other codes have conditional acceptance.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R192_REL0001" source="DATA_CWHS" target="R192_E001"><data key="edge_relationship_id">R192_REL0001</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">provides_sample_for</data><data key="edge_target_entity_id">R192_E001</data><data key="edge_operational_context">CWHS one-percent sample underlies Table 4.B10.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0002" source="DATA_CWHS" target="R192_E002"><data key="edge_relationship_id">R192_REL0002</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">provides_sample_for</data><data key="edge_target_entity_id">R192_E002</data><data key="edge_operational_context">CWHS one-percent sample underlies Table 4.B12.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0003" source="R192_E003" target="R192_E005"><data key="edge_relationship_id">R192_REL0003</data><data key="edge_source_entity_id">R192_E003</data><data key="edge_relationship_type">provides_address_observation_to</data><data key="edge_target_entity_id">R192_E005</data><data key="edge_operational_context">End-of-year residence from electronically filed employer reports is the primary worker state attribution.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0004" source="R192_E004" target="R192_E005"><data key="edge_relationship_id">R192_REL0004</data><data key="edge_source_entity_id">R192_E004</data><data key="edge_relationship_type">provides_fallback_location_to</data><data key="edge_target_entity_id">R192_E005</data><data key="edge_operational_context">Paper wage-report employer location is used as a geographic proxy, not verified worker residence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0005" source="R192_E005" target="R192_E001"><data key="edge_relationship_id">R192_REL0005</data><data key="edge_source_entity_id">R192_E005</data><data key="edge_relationship_type">governs_state_assignment_for</data><data key="edge_target_entity_id">R192_E001</data><data key="edge_operational_context">State-level 2023 covered-worker table applies documented residence/employer fallback.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0006" source="R192_E005" target="R192_E002"><data key="edge_relationship_id">R192_REL0006</data><data key="edge_source_entity_id">R192_E005</data><data key="edge_relationship_type">governs_state_assignment_for</data><data key="edge_target_entity_id">R192_E002</data><data key="edge_operational_context">State-level 2023 HI-covered-worker table applies documented residence/employer fallback.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0007" source="R192_E006" target="REPORT_STAT_SUPP_SERIES"><data key="edge_relationship_id">R192_REL0007</data><data key="edge_source_entity_id">R192_E006</data><data key="edge_relationship_type">replaces_background_section_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_SERIES</data><data key="edge_operational_context">2026 standalone reference replaces the supplement’s through-2024 program description and legislative-history background.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0008" source="R192_E006" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R192_REL0008</data><data key="edge_source_entity_id">R192_E006</data><data key="edge_relationship_type">supports_interpretation_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Standalone OASDI reference is linked from the current statistical supplement.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0009" source="R192_E007" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R192_REL0009</data><data key="edge_source_entity_id">R192_E007</data><data key="edge_relationship_type">supports_interpretation_of</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Cross-publication glossary is linked from 2026 supplement.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0010" source="R192_E007" target="REPORT_SSI_ASR_2025"><data key="edge_relationship_id">R192_REL0010</data><data key="edge_source_entity_id">R192_E007</data><data key="edge_relationship_type">supports_interpretation_of</data><data key="edge_target_entity_id">REPORT_SSI_ASR_2025</data><data key="edge_operational_context">Glossary consolidates SSI annual statistical report terminology.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0011" source="R192_E008" target="R192_E007"><data key="edge_relationship_id">R192_REL0011</data><data key="edge_source_entity_id">R192_E008</data><data key="edge_relationship_type">applies_interpretive_scope_to</data><data key="edge_target_entity_id">R192_E007</data><data key="edge_operational_context">Statistical glossary definitions are program-tagged and subject to edition-specific notes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0012" source="R192_E009" target="R192_E006"><data key="edge_relationship_id">R192_REL0012</data><data key="edge_source_entity_id">R192_E009</data><data key="edge_relationship_type">limits_policy_authority_of</data><data key="edge_target_entity_id">R192_E006</data><data key="edge_operational_context">SSA explicitly disclaims OASDI publication reference as official program policy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0013" source="R192_E013" target="R192_E010"><data key="edge_relationship_id">R192_REL0013</data><data key="edge_source_entity_id">R192_E013</data><data key="edge_relationship_type">relates_year_offset_to</data><data key="edge_target_entity_id">R192_E010</data><data key="edge_operational_context">January 1 population corresponds to preceding December 31 population.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0014" source="R192_E013" target="R192_E012"><data key="edge_relationship_id">R192_REL0014</data><data key="edge_source_entity_id">R192_E013</data><data key="edge_relationship_type">relates_year_offset_to</data><data key="edge_target_entity_id">R192_E012</data><data key="edge_operational_context">December 31 population corresponds to following January 1 population.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0015" source="R192_E010" target="R192_E011"><data key="edge_relationship_id">R192_REL0015</data><data key="edge_source_entity_id">R192_E010</data><data key="edge_relationship_type">shares_assumption_vintage_with</data><data key="edge_target_entity_id">R192_E011</data><data key="edge_operational_context">Beginning and midyear exports use 2022 trustees intermediate assumptions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0016" source="R192_E011" target="R192_E012"><data key="edge_relationship_id">R192_REL0016</data><data key="edge_source_entity_id">R192_E011</data><data key="edge_relationship_type">shares_assumption_vintage_with</data><data key="edge_target_entity_id">R192_E012</data><data key="edge_operational_context">Midyear and year-end exports use 2022 trustees intermediate assumptions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0017" source="DATA_SSR_ACD" target="R192_E014"><data key="edge_relationship_id">R192_REL0017</data><data key="edge_source_entity_id">DATA_SSR_ACD</data><data key="edge_relationship_type">is_compared_under_rule</data><data key="edge_target_entity_id">R192_E014</data><data key="edge_operational_context">SSR ACD compared with MBR address last-updated for selecting more current Title II correspondence location.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0018" source="R192_E014" target="APP_POS"><data key="edge_relationship_id">R192_REL0018</data><data key="edge_source_entity_id">R192_E014</data><data key="edge_relationship_type">authorizes_conditional_manual_update_using</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Title II employee may enter the more-current SSI address into MBR via POS after comparing dates.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0019" source="R192_E015" target="APP_POS"><data key="edge_relationship_id">R192_REL0019</data><data key="edge_source_entity_id">R192_E015</data><data key="edge_relationship_type">initiates_controlled_update_using</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">FI/USPS supplied located address entered through POS by SSA employee.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0020" source="DATA_FI_LOCATE_MAIL_ADDR" target="R192_E015"><data key="edge_relationship_id">R192_REL0020</data><data key="edge_source_entity_id">DATA_FI_LOCATE_MAIL_ADDR</data><data key="edge_relationship_type">supports_update_rule</data><data key="edge_target_entity_id">R192_E015</data><data key="edge_operational_context">FI address lead supports POS entry under narrowly documented returned-mail circumstances.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0021" source="DATA_USPS_LOCATE_MAIL_ADDR" target="R192_E015"><data key="edge_relationship_id">R192_REL0021</data><data key="edge_source_entity_id">DATA_USPS_LOCATE_MAIL_ADDR</data><data key="edge_relationship_type">supports_update_rule</data><data key="edge_target_entity_id">R192_E015</data><data key="edge_operational_context">USPS address response supports POS entry under narrowly documented returned-mail circumstances.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0022" source="R192_E015" target="R192_E016"><data key="edge_relationship_id">R192_REL0022</data><data key="edge_source_entity_id">R192_E015</data><data key="edge_relationship_type">initiates_if_concurrent_mismatch</data><data key="edge_target_entity_id">R192_E016</data><data key="edge_operational_context">Where SSI and Title II addresses differ, PCS/TSC follow-up is separate from Title II POS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0023" source="R192_E016" target="APP_MDW_AI"><data key="edge_relationship_id">R192_REL0023</data><data key="edge_source_entity_id">R192_E016</data><data key="edge_relationship_type">uses_case_referral</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">PSC/TSC sends Request for Assistance or MDW to servicing FO.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0024" source="R192_E016" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R192_REL0024</data><data key="edge_source_entity_id">R192_E016</data><data key="edge_relationship_type">requests_update_via</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">SSI FO technician updates SSR through SSI Claims System.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0025" source="R192_E017" target="PROC_T2_UNDELIV_ADDRESS"><data key="edge_relationship_id">R192_REL0025</data><data key="edge_source_entity_id">R192_E017</data><data key="edge_relationship_type">governs_development_of</data><data key="edge_target_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_operational_context">Undeliverable due-process or required response notices trigger address development.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0026" source="R192_E018" target="REPO_NDRED"><data key="edge_relationship_id">R192_REL0026</data><data key="edge_source_entity_id">R192_E018</data><data key="edge_relationship_type">may_preserve_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Absent an ORS retained copy, returned notice is faxed into NDRed via Evidence Portal.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0027" source="R192_E019" target="SYS_MBR"><data key="edge_relationship_id">R192_REL0027</data><data key="edge_source_entity_id">R192_E019</data><data key="edge_relationship_type">directs_staff_to_review_and_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Upon Numident sex-field update, POMS directs follow-up on MBR.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0028" source="R192_E019" target="SYS_SSR"><data key="edge_relationship_id">R192_REL0028</data><data key="edge_source_entity_id">R192_E019</data><data key="edge_relationship_type">directs_staff_to_review_and_update</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Upon Numident sex-field update, POMS directs follow-up on SSR.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0029" source="R192_E020" target="SYS_MBR"><data key="edge_relationship_id">R192_REL0029</data><data key="edge_source_entity_id">R192_E020</data><data key="edge_relationship_type">requires_consistency_review_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Numident parent-name correction may require Title II beneficiary relationship review.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0030" source="R192_E020" target="SYS_SSR"><data key="edge_relationship_id">R192_REL0030</data><data key="edge_source_entity_id">R192_E020</data><data key="edge_relationship_type">requires_consistency_review_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Numident parent-name correction may require SSI record review.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0031" source="DATA_DISABILITY_RESEARCH_FILE" target="R192_E021"><data key="edge_relationship_id">R192_REL0031</data><data key="edge_source_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_relationship_type">aggregates_into</data><data key="edge_target_entity_id">R192_E021</data><data key="edge_operational_context">SSA identifies DRF annual application-file updates as Table 69 source.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0032" source="DATA_DISABILITY_RESEARCH_FILE" target="R192_E022"><data key="edge_relationship_id">R192_REL0032</data><data key="edge_source_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_relationship_type">aggregates_into</data><data key="edge_target_entity_id">R192_E022</data><data key="edge_operational_context">Annual DRF records underpin initial/recon/hearing SSI allowance tables.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0033" source="R192_E023" target="R192_E021"><data key="edge_relationship_id">R192_REL0033</data><data key="edge_source_entity_id">R192_E023</data><data key="edge_relationship_type">defines_calculation_for</data><data key="edge_target_entity_id">R192_E021</data><data key="edge_operational_context">Different numerator and denominator for allowance versus award; subsequent technical denials counted differently.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0034" source="R192_E024" target="R192_E021"><data key="edge_relationship_id">R192_REL0034</data><data key="edge_source_entity_id">R192_E024</data><data key="edge_relationship_type">qualifies_interpretation_of</data><data key="edge_target_entity_id">R192_E021</data><data key="edge_operational_context">Incomplete recent cohorts will be revised as pending claims reach final decision.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0035" source="R192_E025" target="R192_E022"><data key="edge_relationship_id">R192_REL0035</data><data key="edge_source_entity_id">R192_E025</data><data key="edge_relationship_type">alters_comparability_of</data><data key="edge_target_entity_id">R192_E022</data><data key="edge_operational_context">Prototype 10-state no-reconsideration regime affects level distribution until 2020.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0036" source="R192_E021" target="REPORT_SSI_ASR_2025"><data key="edge_relationship_id">R192_REL0036</data><data key="edge_source_entity_id">R192_E021</data><data key="edge_relationship_type">published_in</data><data key="edge_target_entity_id">REPORT_SSI_ASR_2025</data><data key="edge_operational_context">Table 69 published in the 2025 SSI annual statistical report.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0037" source="R192_E026" target="DATA_SSI_STATE_COUNTY_2025"><data key="edge_relationship_id">R192_REL0037</data><data key="edge_source_entity_id">R192_E026</data><data key="edge_relationship_type">governs_published_suppression_of</data><data key="edge_target_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_operational_context">Suppressed county cells contribute to state totals; public table is disclosure controlled.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0038" source="R192_E027" target="DATA_SSI_STATE_COUNTY_2025"><data key="edge_relationship_id">R192_REL0038</data><data key="edge_source_entity_id">R192_E027</data><data key="edge_relationship_type">governs_published_rounding_of</data><data key="edge_target_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_operational_context">State payment amount is unrounded sum, not necessarily sum of published rounded county figures.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R192_REL0039" source="SYS_SSR" target="DATA_SSI_STATE_COUNTY_2025"><data key="edge_relationship_id">R192_REL0039</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_aggregate_statistics_to</data><data key="edge_target_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_operational_context">Report uses SSR administrative records, not a separate physical residence authority.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as of cited source. Do not infer automatic updating, physical transport, current deployment, or retention beyond what source says.</data></edge><edge id="R193_R001" source="R193_E001" target="APP_CPMS"><data key="edge_relationship_id">R193_R001</data><data key="edge_source_entity_id">R193_E001</data><data key="edge_relationship_type">explicitly_documented_no_interface_with</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">2023 POMS DI 81001.035 CEF-copy document-location instructions</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Negative current interface finding limited to source observation; revalidate current state before using operationally.</data></edge><edge id="R193_R002" source="R193_E001" target="REPO_CEF"><data key="edge_relationship_id">R193_R002</data><data key="edge_source_entity_id">R193_E001</data><data key="edge_relationship_type">explicitly_documented_no_interface_with</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">2023 POMS DI 81001.035 CEF-copy document-location instructions</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Negative current interface finding limited to source observation; revalidate current state before using operationally.</data></edge><edge id="R193_R003" source="R193_E001" target="APP_ORS"><data key="edge_relationship_id">R193_R003</data><data key="edge_source_entity_id">R193_E001</data><data key="edge_relationship_type">explicitly_documented_no_interface_with</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">2023 POMS DI 81001.035 CEF-copy document-location instructions</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Negative current interface finding limited to source observation; revalidate current state before using operationally.</data></edge><edge id="R193_R004" source="R193_E002" target="APP_MCS"><data key="edge_relationship_id">R193_R004</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R005" source="R193_E002" target="APP_MSSICS"><data key="edge_relationship_id">R193_R005</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R006" source="R193_E002" target="APP_CCE"><data key="edge_relationship_id">R193_R006</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R007" source="R193_E002" target="SYS_MBR"><data key="edge_relationship_id">R193_R007</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R008" source="R193_E002" target="SYS_SSR"><data key="edge_relationship_id">R193_R008</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R009" source="R193_E002" target="DB_DCF"><data key="edge_relationship_id">R193_R009</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R010" source="R193_E002" target="APP_ERPS"><data key="edge_relationship_id">R193_R010</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R011" source="R193_E002" target="APP_EVIEW"><data key="edge_relationship_id">R193_R011</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R012" source="R193_E002" target="APP_ORS"><data key="edge_relationship_id">R193_R012</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R013" source="R193_E002" target="APP_CPMS"><data key="edge_relationship_id">R193_R013</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R014" source="R193_E002" target="APP_ARPS"><data key="edge_relationship_id">R193_R014</data><data key="edge_source_entity_id">R193_E002</data><data key="edge_relationship_type">manual_folder_location_check_includes</data><data key="edge_target_entity_id">APP_ARPS</data><data key="edge_operational_context">Employee consults named system/record to locate materials needed for official disability folder copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R015" source="R193_E003" target="REPO_CEF"><data key="edge_relationship_id">R193_R015</data><data key="edge_source_entity_id">R193_E003</data><data key="edge_relationship_type">excludes_from_disclosure_copy</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Temporary/current development documents not part of releasable official copy.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R016" source="R193_E004" target="REPO_CEF"><data key="edge_relationship_id">R193_R016</data><data key="edge_source_entity_id">R193_E004</data><data key="edge_relationship_type">requires_materialization_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Linked ORS/CPD evidence must be copied into current folder before media export.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R017" source="R193_E005" target="APP_EVIEW"><data key="edge_relationship_id">R193_R017</data><data key="edge_source_entity_id">R193_E005</data><data key="edge_relationship_type">excludes_metadata_from_export</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Messages/flags/annotations not automatically included in CD export of electronic images.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R018" source="APP_ORS" target="R193_E006"><data key="edge_relationship_id">R193_R018</data><data key="edge_source_entity_id">APP_ORS</data><data key="edge_relationship_type">supports_manual_import_into</data><data key="edge_target_entity_id">R193_E006</data><data key="edge_operational_context">ORS source documents can be imported selectively into CEF via eView.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R019" source="R193_E006" target="REPO_CEF"><data key="edge_relationship_id">R193_R019</data><data key="edge_source_entity_id">R193_E006</data><data key="edge_relationship_type">stages_selected_content_to</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Manual selection/import through eView before CD export.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R020" source="R193_E007" target="R193_E008"><data key="edge_relationship_id">R193_R020</data><data key="edge_source_entity_id">R193_E007</data><data key="edge_relationship_type">requires_indexed_barcode</data><data key="edge_target_entity_id">R193_E008</data><data key="edge_operational_context">Evidence request letter includes DMA indexing barcode and return address of contract scanning service.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R021" source="R193_E008" target="COMP_DMA"><data key="edge_relationship_id">R193_R021</data><data key="edge_source_entity_id">R193_E008</data><data key="edge_relationship_type">is_barcode_record_for</data><data key="edge_target_entity_id">COMP_DMA</data><data key="edge_operational_context">DMA links returned records to intended electronic disability folder with indexing.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R022" source="R193_E009" target="FORM_SSA3369BK"><data key="edge_relationship_id">R193_R022</data><data key="edge_source_entity_id">R193_E009</data><data key="edge_relationship_type">propagates_work_history_to</data><data key="edge_target_entity_id">FORM_SSA3369BK</data><data key="edge_operational_context">Work History segment SSA-3368 entered into EDCS populates SSA-3369 work history.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R023" source="APP_EDCS" target="R193_E009"><data key="edge_relationship_id">R193_R023</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">performs_documented_field_propagation</data><data key="edge_target_entity_id">R193_E009</data><data key="edge_operational_context">POMS DI 81020.020 explicit SSA-3368 to SSA-3369 transformation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R024" source="DATA_EFI_DOWNLOAD" target="R193_E010"><data key="edge_relationship_id">R193_R024</data><data key="edge_source_entity_id">DATA_EFI_DOWNLOAD</data><data key="edge_relationship_type">missing_rep_data_triggers_manual_process</data><data key="edge_target_entity_id">R193_E010</data><data key="edge_operational_context">Title XVI-only appointed rep missing from EFI download requires manual entry to DDS case system.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R025" source="R193_E010" target="APP_EDCS"><data key="edge_relationship_id">R193_R025</data><data key="edge_source_entity_id">R193_E010</data><data key="edge_relationship_type">requires_representation_verification_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Check Representative Involved flag and Form SSA-1696 before entering contact attributes manually.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R026" source="R193_E010" target="R193_E016"><data key="edge_relationship_id">R193_R026</data><data key="edge_source_entity_id">R193_E010</data><data key="edge_relationship_type">requires_manual_entry_of</data><data key="edge_target_entity_id">R193_E016</data><data key="edge_operational_context">Name, postal address, telephone and fax information.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R027" source="R193_E011" target="APP_EDCS"><data key="edge_relationship_id">R193_R027</data><data key="edge_source_entity_id">R193_E011</data><data key="edge_relationship_type">is_displayed_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS Action Page Request FO to add Client Contact</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R028" source="R193_E012" target="REPO_CEF"><data key="edge_relationship_id">R193_R028</data><data key="edge_source_entity_id">R193_E012</data><data key="edge_relationship_type">stored_in_documentation_section_of</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">HIT MER clinical information located in yellow section of EF.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R029" source="R193_E013" target="REPO_CEF"><data key="edge_relationship_id">R193_R029</data><data key="edge_source_entity_id">R193_E013</data><data key="edge_relationship_type">stored_in_documentation_section_of</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">HIT request/response/SSA-827 messages identified in blue section.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R030" source="R193_E014" target="R193_E012"><data key="edge_relationship_id">R193_R030</data><data key="edge_source_entity_id">R193_E014</data><data key="edge_relationship_type">constrains_document_content_in</data><data key="edge_target_entity_id">R193_E012</data><data key="edge_operational_context">HIT Standard Documents are narrative extracts; graphics/images in specified modalities are excluded.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R031" source="R193_E015" target="R193_E012"><data key="edge_relationship_id">R193_R031</data><data key="edge_source_entity_id">R193_E015</data><data key="edge_relationship_type">used_for_follow_up_of</data><data key="edge_target_entity_id">R193_E012</data><data key="edge_operational_context">Use HIT User Trigger for electronic followup when relevant to HIT MER, then ERE/traditional when needed.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R032" source="R193_E015" target="APP_ERE"><data key="edge_relationship_id">R193_R032</data><data key="edge_source_entity_id">R193_E015</data><data key="edge_relationship_type">may_use_electronic_records_express</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">ERE alternative where applicable; does not imply direct HIT-to-ERE API.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R033" source="DATA_EFI_DOWNLOAD" target="R193_E016"><data key="edge_relationship_id">R193_R033</data><data key="edge_source_entity_id">DATA_EFI_DOWNLOAD</data><data key="edge_relationship_type">contains_optional_rep_contact_attributes</data><data key="edge_target_entity_id">R193_E016</data><data key="edge_operational_context">Specific data attributes from EFI may be incomplete on Title XVI only cases.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R034" source="APP_EVIEW" target="R193_E017"><data key="edge_relationship_id">R193_R034</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">provides_unreceipted_barcode_query</data><data key="edge_target_entity_id">R193_E017</data><data key="edge_operational_context">Query lists only eView-created DMA barcode requests not yet receipted.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R035" source="R193_E018" target="R193_E017"><data key="edge_relationship_id">R193_R035</data><data key="edge_source_entity_id">R193_E018</data><data key="edge_relationship_type">limits_coverage_of</data><data key="edge_target_entity_id">R193_E017</data><data key="edge_operational_context">Query excludes DDS legacy, CPMS and ARPS generated barcodes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R036" source="APP_EVIEW" target="R193_E019"><data key="edge_relationship_id">R193_R036</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">records_bookmark_audit_attributes_in</data><data key="edge_target_entity_id">R193_E019</data><data key="edge_operational_context">Document bookmarks track associated page, user and dates.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R037" source="APP_EVIEW" target="R193_E020"><data key="edge_relationship_id">R193_R037</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">exposes_categorized_page_metadata_in</data><data key="edge_target_entity_id">R193_E020</data><data key="edge_operational_context">Category type e.g. Mental/Physical plus page/source/exhibit/indexing info.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R038" source="R193_E020" target="UI_DMA_VIEWER"><data key="edge_relationship_id">R193_R038</data><data key="edge_source_entity_id">R193_E020</data><data key="edge_relationship_type">opens_pages_in</data><data key="edge_target_entity_id">UI_DMA_VIEWER</data><data key="edge_operational_context">Categorized page hyperlinks open viewer to specific document pages.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R039" source="R193_E021" target="UI_EVIEW_CASE_DOCUMENTS"><data key="edge_relationship_id">R193_R039</data><data key="edge_source_entity_id">R193_E021</data><data key="edge_relationship_type">is_section_of</data><data key="edge_target_entity_id">UI_EVIEW_CASE_DOCUMENTS</data><data key="edge_operational_context">Private hearing file accessible only in hearing office with jurisdiction.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R040" source="APP_CCE" target="R193_E022"><data key="edge_relationship_id">R193_R040</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">guides_resource_redetermination_with</data><data key="edge_target_entity_id">R193_E022</data><data key="edge_operational_context">Current SSI Claims guided REDETERMINATION event path.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R041" source="R193_E023" target="R193_E022"><data key="edge_relationship_id">R193_R041</data><data key="edge_source_entity_id">R193_E023</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R193_E022</data><data key="edge_operational_context">Requires renewed permission to query financial institution during FO-initiated SSI RZ.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R042" source="R193_E024" target="R193_E022"><data key="edge_relationship_id">R193_R042</data><data key="edge_source_entity_id">R193_E024</data><data key="edge_relationship_type">is_followed_during</data><data key="edge_target_entity_id">R193_E022</data><data key="edge_operational_context">IRS controlled alerts developed as required; informational used as leads.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R043" source="R193_E025" target="R193_E022"><data key="edge_relationship_id">R193_R043</data><data key="edge_source_entity_id">R193_E025</data><data key="edge_relationship_type">is_recorded_for</data><data key="edge_target_entity_id">R193_E022</data><data key="edge_operational_context">Form SSA-8203-BK collecting bank/company address is organization address, not residence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R044" source="SYS_SSR" target="R193_E026"><data key="edge_relationship_id">R193_R044</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">direct_deposit_indicator_can_prompt</data><data key="edge_target_entity_id">R193_E026</data><data key="edge_operational_context">SSR direct-deposit indicator prompts account resource development.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R045" source="SYS_MBR" target="R193_E026"><data key="edge_relationship_id">R193_R045</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">direct_deposit_indicator_can_prompt</data><data key="edge_target_entity_id">R193_E026</data><data key="edge_operational_context">MBR direct-deposit indicator prompts account resource development.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R046" source="R193_E026" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">R193_R046</data><data key="edge_source_entity_id">R193_E026</data><data key="edge_relationship_type">requires_documentation_in</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">Use CCE Financial Accounts screen to record account used for direct deposit.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R047" source="R193_E027" target="R193_E022"><data key="edge_relationship_id">R193_R047</data><data key="edge_source_entity_id">R193_E027</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R193_E022</data><data key="edge_operational_context">Early payment adjustment at FOM resource count requires evidence and eligibility rules.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R048" source="R193_E028" target="SYS_MBR"><data key="edge_relationship_id">R193_R048</data><data key="edge_source_entity_id">R193_E028</data><data key="edge_relationship_type">recorded_as_attribute_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Representative Payee Type code as Individual or Organization.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R049" source="R193_E028" target="SYS_SSR"><data key="edge_relationship_id">R193_R049</data><data key="edge_source_entity_id">R193_E028</data><data key="edge_relationship_type">recorded_as_attribute_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Representative Payee Type code as Individual or Organization.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R050" source="R193_E028" target="APP_ERPS"><data key="edge_relationship_id">R193_R050</data><data key="edge_source_entity_id">R193_E028</data><data key="edge_relationship_type">recorded_as_attribute_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Representative Payee Type code as Individual or Organization.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R051" source="R193_E029" target="APP_ERPS"><data key="edge_relationship_id">R193_R051</data><data key="edge_source_entity_id">R193_E029</data><data key="edge_relationship_type">controls_ein_evidence_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Manager seeks IRS or state proof if EIN or incorporated status conflicts with EIF.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R052" source="R193_E030" target="SYS_MBR"><data key="edge_relationship_id">R193_R052</data><data key="edge_source_entity_id">R193_E030</data><data key="edge_relationship_type">statistical_input_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA monthly snapshot Table 1 is based on full-population MBR administrative counts.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R053" source="R193_E030" target="SYS_SSR"><data key="edge_relationship_id">R193_R053</data><data key="edge_source_entity_id">R193_E030</data><data key="edge_relationship_type">statistical_input_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA monthly snapshot Table 1 is based on full-population SSR administrative counts.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R193_R054" source="R193_E031" target="R193_E030"><data key="edge_relationship_id">R193_R054</data><data key="edge_source_entity_id">R193_E031</data><data key="edge_relationship_type">is_methodological_rule_for</data><data key="edge_target_entity_id">R193_E030</data><data key="edge_operational_context">Cross-program individuals are deduplicated; tables distinguish program-specific receipt.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R001" source="R196_E001" target="SYS_NUMIDENT"><data key="edge_relationship_id">R196_R001</data><data key="edge_source_entity_id">R196_E001</data><data key="edge_relationship_type">evaluates</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSPA first original SSN and work-authorization verification</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R002" source="R196_E002" target="SYS_NUMIDENT"><data key="edge_relationship_id">R196_R002</data><data key="edge_source_entity_id">R196_E002</data><data key="edge_relationship_type">attribute_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">earliest original Numident iteration; not every cycle date equals authoritative original assignment</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R003" source="R196_E003" target="SYS_NUMIDENT"><data key="edge_relationship_id">R196_R003</data><data key="edge_source_entity_id">R196_E003</data><data key="edge_relationship_type">attribute_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">historic work authorization coding used in insured-status development</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R004" source="R196_E001" target="R196_E002"><data key="edge_relationship_id">R196_R004</data><data key="edge_source_entity_id">R196_E001</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E002</data><data key="edge_operational_context">original properly assigned SSN issue date exception</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R005" source="R196_E001" target="R196_E003"><data key="edge_relationship_id">R196_R005</data><data key="edge_source_entity_id">R196_E001</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E003</data><data key="edge_operational_context">SSN work-purpose history</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R006" source="R196_E001" target="R196_E004"><data key="edge_relationship_id">R196_R006</data><data key="edge_source_entity_id">R196_E001</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E004</data><data key="edge_operational_context">wrong-number/scrambled/later-new-SSN original-issue-date exceptions</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R007" source="R196_E004" target="R196_E005"><data key="edge_relationship_id">R196_R007</data><data key="edge_source_entity_id">R196_E004</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R196_E005</data><data key="edge_operational_context">resolve identity and assignment conflicts before relying on SSN cycle date</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R008" source="R196_E005" target="APP_ICOR"><data key="edge_relationship_id">R196_R008</data><data key="edge_source_entity_id">R196_E005</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ICOR</data><data key="edge_operational_context">documented earnings attribution correction path</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R009" source="R196_E001" target="R196_E006"><data key="edge_relationship_id">R196_R009</data><data key="edge_source_entity_id">R196_E001</data><data key="edge_relationship_type">has_alternative</data><data key="edge_target_entity_id">R196_E006</data><data key="edge_operational_context">B-1/D-1/D-2 eligibility alternative to work SSN history</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R010" source="R196_E001" target="R196_E007"><data key="edge_relationship_id">R196_R010</data><data key="edge_source_entity_id">R196_E001</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R196_E007</data><data key="edge_operational_context">not-met case with SSN, special manual Title II disallowance processing</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R011" source="R196_E007" target="APP_MACADE"><data key="edge_relationship_id">R196_R011</data><data key="edge_source_entity_id">R196_E007</data><data key="edge_relationship_type">processed_via</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">manual transaction entry for special-case Title II disallowance</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R012" source="R196_E007" target="APP_MADCAP"><data key="edge_relationship_id">R196_R012</data><data key="edge_source_entity_id">R196_E007</data><data key="edge_relationship_type">processed_via</data><data key="edge_target_entity_id">APP_MADCAP</data><data key="edge_operational_context">manual disallowance processing system</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R013" source="R196_E007" target="APP_MCS"><data key="edge_relationship_id">R196_R013</data><data key="edge_source_entity_id">R196_E007</data><data key="edge_relationship_type">excludes</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS/EC excluded when Section 211 not met</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R014" source="R196_E007" target="R196_E008"><data key="edge_relationship_id">R196_R014</data><data key="edge_source_entity_id">R196_E007</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R196_E008</data><data key="edge_operational_context">manual disallowance notification</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R015" source="R196_E008" target="APP_DPS"><data key="edge_relationship_id">R196_R015</data><data key="edge_source_entity_id">R196_E008</data><data key="edge_relationship_type">generated_using</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">initial claim misc disallowance template</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R016" source="R196_E007" target="R196_E009"><data key="edge_relationship_id">R196_R016</data><data key="edge_source_entity_id">R196_E007</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E009</data><data key="edge_operational_context">code 292 Section 211 not met; 291 qualifying nonimmigrant award</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R017" source="R196_E001" target="R196_E010"><data key="edge_relationship_id">R196_R017</data><data key="edge_source_entity_id">R196_E001</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E010</data><data key="edge_operational_context">special indicator exception routed to region</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R196_R018" source="R196_E012" target="EX_EAE"><data key="edge_relationship_id">R196_R018</data><data key="edge_source_entity_id">R196_E012</data><data key="edge_relationship_type">limits</data><data key="edge_target_entity_id">EX_EAE</data><data key="edge_operational_context">EAE enrollment omits race/ethnicity indicators</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R019" source="R196_E012" target="DATA_NUMIDENT_EAB_PARENTAGE"><data key="edge_relationship_id">R196_R019</data><data key="edge_source_entity_id">R196_E012</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DATA_NUMIDENT_EAB_PARENTAGE</data><data key="edge_operational_context">EAB medical-only race information excluded from enumerated personal attributes</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R196_R020" source="R196_E013" target="R196_E014"><data key="edge_relationship_id">R196_R020</data><data key="edge_source_entity_id">R196_E013</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E014</data><data key="edge_operational_context">historical CPS/ASEC race and beneficiary characteristics</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R196_R021" source="R196_E013" target="R196_E015"><data key="edge_relationship_id">R196_R021</data><data key="edge_source_entity_id">R196_E013</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E015</data><data key="edge_operational_context">historical ACS race characteristics without SSA admin linkage</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R196_R022" source="R196_E013" target="DATA_SIPP"><data key="edge_relationship_id">R196_R022</data><data key="edge_source_entity_id">R196_E013</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_SIPP</data><data key="edge_operational_context">historical SIPP comparisons and linked administrative survey data</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R196_R023" source="R196_E013" target="PROG_HRS"><data key="edge_relationship_id">R196_R023</data><data key="edge_source_entity_id">R196_E013</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">historical HRS research linkage availability</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R196_R024" source="R196_E013" target="R196_E016"><data key="edge_relationship_id">R196_R024</data><data key="edge_source_entity_id">R196_E013</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E016</data><data key="edge_operational_context">demographic data-collection and category-change caveat</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R025" source="R196_E011" target="R196_E016"><data key="edge_relationship_id">R196_R025</data><data key="edge_source_entity_id">R196_E011</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E016</data><data key="edge_operational_context">self-selected volunteer race entries are incomplete longitudinally</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R026" source="R196_E017" target="R196_E023"><data key="edge_relationship_id">R196_R026</data><data key="edge_source_entity_id">R196_E017</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E023</data><data key="edge_operational_context">Year dimension and single ages 0-119 across gender-specific files</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R027" source="R196_E017" target="R196_E024"><data key="edge_relationship_id">R196_R027</data><data key="edge_source_entity_id">R196_E017</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E024</data><data key="edge_operational_context">Trustees intermediate assumption and 2024 publication vintage; historical observations vary by file</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R028" source="R196_E018" target="R196_E023"><data key="edge_relationship_id">R196_R028</data><data key="edge_source_entity_id">R196_E018</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E023</data><data key="edge_operational_context">Year dimension and single ages 0-119 across gender-specific files</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R029" source="R196_E018" target="R196_E024"><data key="edge_relationship_id">R196_R029</data><data key="edge_source_entity_id">R196_E018</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E024</data><data key="edge_operational_context">Trustees intermediate assumption and 2024 publication vintage; historical observations vary by file</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R030" source="R196_E019" target="R196_E023"><data key="edge_relationship_id">R196_R030</data><data key="edge_source_entity_id">R196_E019</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E023</data><data key="edge_operational_context">Year dimension and single ages 0-119 across gender-specific files</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R031" source="R196_E019" target="R196_E024"><data key="edge_relationship_id">R196_R031</data><data key="edge_source_entity_id">R196_E019</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E024</data><data key="edge_operational_context">Trustees intermediate assumption and 2024 publication vintage; historical observations vary by file</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R032" source="R196_E020" target="R196_E023"><data key="edge_relationship_id">R196_R032</data><data key="edge_source_entity_id">R196_E020</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E023</data><data key="edge_operational_context">Year dimension and single ages 0-119 across gender-specific files</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R033" source="R196_E020" target="R196_E024"><data key="edge_relationship_id">R196_R033</data><data key="edge_source_entity_id">R196_E020</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E024</data><data key="edge_operational_context">Trustees intermediate assumption and 2024 publication vintage; historical observations vary by file</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R034" source="R196_E021" target="R196_E023"><data key="edge_relationship_id">R196_R034</data><data key="edge_source_entity_id">R196_E021</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E023</data><data key="edge_operational_context">Year dimension and single ages 0-119 across gender-specific files</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R035" source="R196_E021" target="R196_E024"><data key="edge_relationship_id">R196_R035</data><data key="edge_source_entity_id">R196_E021</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E024</data><data key="edge_operational_context">Trustees intermediate assumption and 2024 publication vintage; historical observations vary by file</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R036" source="R196_E022" target="R196_E023"><data key="edge_relationship_id">R196_R036</data><data key="edge_source_entity_id">R196_E022</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E023</data><data key="edge_operational_context">Year dimension and single ages 0-119 across gender-specific files</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R037" source="R196_E022" target="R196_E024"><data key="edge_relationship_id">R196_R037</data><data key="edge_source_entity_id">R196_E022</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R196_E024</data><data key="edge_operational_context">Trustees intermediate assumption and 2024 publication vintage; historical observations vary by file</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R038" source="R196_E017" target="DATA_OACT_COHORT_LIFE_2026"><data key="edge_relationship_id">R196_R038</data><data key="edge_source_entity_id">R196_E017</data><data key="edge_relationship_type">has_vintage_comparator</data><data key="edge_target_entity_id">DATA_OACT_COHORT_LIFE_2026</data><data key="edge_operational_context">same statistical family; distinct 2024 and 2026 vintage</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R196_R039" source="R196_E019" target="DATA_OACT_PERIOD_LIFE_2026"><data key="edge_relationship_id">R196_R039</data><data key="edge_source_entity_id">R196_E019</data><data key="edge_relationship_type">has_vintage_comparator</data><data key="edge_target_entity_id">DATA_OACT_PERIOD_LIFE_2026</data><data key="edge_operational_context">same statistical family; distinct 2024 and 2026 vintage</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R196_R040" source="R196_E025" target="R196_E026"><data key="edge_relationship_id">R196_R040</data><data key="edge_source_entity_id">R196_E025</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R196_E026</data><data key="edge_operational_context">Linked HRS administrative covered earnings used for earnings before/after disability decision</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R041" source="R196_E026" target="SYS_MEF"><data key="edge_relationship_id">R196_R041</data><data key="edge_source_entity_id">R196_E026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">MEF earnings summarized for HRS consenting subjects</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R042" source="R196_E026" target="R196_E027"><data key="edge_relationship_id">R196_R042</data><data key="edge_source_entity_id">R196_E026</data><data key="edge_relationship_type">access_subject_to</data><data key="edge_target_entity_id">R196_E027</data><data key="edge_operational_context">consented respondents and restricted data analysis</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R043" source="R196_E025" target="PROG_HRS"><data key="edge_relationship_id">R196_R043</data><data key="edge_source_entity_id">R196_E025</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">HRS survey data and claimant decision dates</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R196_R044" source="R196_E028" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R196_R044</data><data key="edge_source_entity_id">R196_E028</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">2026 Supplement releases sections over June 2026-February 2027 expected schedule</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0001" source="EX_CMS_NURSING_1076" target="R197_E0001"><data key="edge_relationship_id">R197_R0001</data><data key="edge_source_entity_id">EX_CMS_NURSING_1076</data><data key="edge_relationship_type">sends_monthly_finder</data><data key="edge_target_entity_id">R197_E0001</data><data key="edge_operational_context">2026 CMA 1076 notice: SSA supplies CMS a monthly finder file drawn from SSI/SVB records (SORN 60-0103).</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0002" source="R197_E0001" target="DATA_CMS_LTC_MDS"><data key="edge_relationship_id">R197_R0002</data><data key="edge_source_entity_id">R197_E0001</data><data key="edge_relationship_type">matched_against</data><data key="edge_target_entity_id">DATA_CMS_LTC_MDS</data><data key="edge_operational_context">CMS compares monthly SSI/SVB finder against LTC/MDS facility admission/discharge source records (SORN 09-70-0528).</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0003" source="DATA_CMS_LTC_MDS" target="R197_E0002"><data key="edge_relationship_id">R197_R0003</data><data key="edge_source_entity_id">DATA_CMS_LTC_MDS</data><data key="edge_relationship_type">produces_match_response</data><data key="edge_target_entity_id">R197_E0002</data><data key="edge_operational_context">CMS submits a response file to SSA after matching SSA finder against its LTC/MDS records.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0004" source="R197_E0002" target="R197_E0004"><data key="edge_relationship_id">R197_R0004</data><data key="edge_source_entity_id">R197_E0002</data><data key="edge_relationship_type">supports_review_of</data><data key="edge_target_entity_id">R197_E0004</data><data key="edge_operational_context">Facility admissions/discharges inform review of SSI eligibility and potential SVB residence abroad.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0005" source="R197_E0003" target="R197_E0002"><data key="edge_relationship_id">R197_R0005</data><data key="edge_source_entity_id">R197_E0003</data><data key="edge_relationship_type">represents_match_subject_in</data><data key="edge_target_entity_id">R197_E0002</data><data key="edge_operational_context">The CMS response concerns nursing-facility admission and discharge observations.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0006" source="EX_CMS_NURSING_1076" target="R197_E0005"><data key="edge_relationship_id">R197_R0006</data><data key="edge_source_entity_id">EX_CMS_NURSING_1076</data><data key="edge_relationship_type">subject_to_effective_date_correction</data><data key="edge_target_entity_id">R197_E0005</data><data key="edge_operational_context">Original 2026-05-07 notice had erroneous 2025 year; 2026-06-22 correction specifies June 20, 2026.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0007" source="EX_CMS_NURSING_1076" target="R197_E0004"><data key="edge_relationship_id">R197_R0007</data><data key="edge_source_entity_id">EX_CMS_NURSING_1076</data><data key="edge_relationship_type">supports_residence_review</data><data key="edge_target_entity_id">R197_E0004</data><data key="edge_operational_context">CMS matched nursing facility data support examination of SVB beneficiaries no longer residing abroad; not direct residence master-record update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0008" source="EX_CMA1038_BFS_SAVINGS" target="R197_E0006"><data key="edge_relationship_id">R197_R0008</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">sends_finder</data><data key="edge_target_entity_id">R197_E0006</data><data key="edge_operational_context">2026 renewal notice: SSA sends SSN and name for roughly 10 million SSI applicant/recipient/deemor records.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0009" source="R197_E0006" target="EXT_BFS_US_SECURITIES_ACCESS"><data key="edge_relationship_id">R197_R0009</data><data key="edge_source_entity_id">R197_E0006</data><data key="edge_relationship_type">is_matched_with</data><data key="edge_target_entity_id">EXT_BFS_US_SECURITIES_ACCESS</data><data key="edge_operational_context">Treasury Fiscal Service compares SSA SSI SSN and name finder against United States Securities and Access ownership records.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0010" source="EX_CMA1038_BFS_SAVINGS" target="R197_E0007"><data key="edge_relationship_id">R197_R0010</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">receives_security_information_from</data><data key="edge_target_entity_id">R197_E0007</data><data key="edge_operational_context">Fiscal Service supplies matched security purchase and redemption details to SSA for SSI benefit eligibility verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0011" source="R197_E0007" target="R197_E0008"><data key="edge_relationship_id">R197_R0011</data><data key="edge_source_entity_id">R197_E0007</data><data key="edge_relationship_type">is_governed_by</data><data key="edge_target_entity_id">R197_E0008</data><data key="edge_operational_context">Returned savings securities information is for SSI financial verification of omitted or incorrect reporting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0012" source="EX_CMA1038_BFS_SAVINGS" target="DOM_TITLE16"><data key="edge_relationship_id">R197_R0012</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">2026 renewal describes SSI applicants, recipients and deemors; not Medicare Part D Extra Help.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0013" source="DATA_CMS_HIX" target="R197_E0009"><data key="edge_relationship_id">R197_R0013</data><data key="edge_source_entity_id">DATA_CMS_HIX</data><data key="edge_relationship_type">requests_verification_using</data><data key="edge_target_entity_id">R197_E0009</data><data key="edge_operational_context">CMS Qualified Health Plan and affordability-program consumers are checked with five required request fields.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0014" source="R197_E0009" target="EX_CMS_ACA_1097"><data key="edge_relationship_id">R197_R0014</data><data key="edge_source_entity_id">R197_E0009</data><data key="edge_relationship_type">is_processed_through</data><data key="edge_target_entity_id">EX_CMS_ACA_1097</data><data key="edge_operational_context">CMS request fields are used for SSA matching pursuant to CMA 1097; not physical cross-agency Person database.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0015" source="EX_CMS_ACA_1097" target="R197_E0010"><data key="edge_relationship_id">R197_R0015</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">conditionally_discloses</data><data key="edge_target_entity_id">R197_E0010</data><data key="edge_operational_context">SSA can return name, DOB, death/disability/incarceration, income, citizenship and SSN attestation, and coverage quarters as available.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0016" source="R197_E0010" target="R197_E0011"><data key="edge_relationship_id">R197_R0016</data><data key="edge_source_entity_id">R197_E0010</data><data key="edge_relationship_type">constrained_by</data><data key="edge_target_entity_id">R197_E0011</data><data key="edge_operational_context">Name/SSN match and available-data limitations in published CMS notice.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0017" source="EX_CMS_ACA_1097" target="DOM_TITLE2"><data key="edge_relationship_id">R197_R0017</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">CMS ACA affordability eligibility may use SSA Title II annual and monthly income verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0018" source="R197_E0013" target="R197_E0014"><data key="edge_relationship_id">R197_R0018</data><data key="edge_source_entity_id">R197_E0013</data><data key="edge_relationship_type">predecessor_of</data><data key="edge_target_entity_id">R197_E0014</data><data key="edge_operational_context">POMS DX 00101.010 identifies 2013 ODEPP and its ODEPPIN successor in October 2018.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0019" source="R197_E0014" target="R197_E0012"><data key="edge_relationship_id">R197_R0019</data><data key="edge_source_entity_id">R197_E0014</data><data key="edge_relationship_type">governance_function_transferred_to</data><data key="edge_target_entity_id">R197_E0012</data><data key="edge_operational_context">2025 merger with SSA Law and Policy, and 2026 placement of data exchanges under PPDX.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0020" source="R197_E0012" target="FORM_SSA157"><data key="edge_relationship_id">R197_R0020</data><data key="edge_source_entity_id">R197_E0012</data><data key="edge_relationship_type">requires_application_form</data><data key="edge_target_entity_id">FORM_SSA157</data><data key="edge_operational_context">External requesters use SSA-157 DXRF submitted to PPDX for new and expanded outgoing data exchanges.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0021" source="FORM_SSA157" target="R197_E0016"><data key="edge_relationship_id">R197_R0021</data><data key="edge_source_entity_id">FORM_SSA157</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">R197_E0016</data><data key="edge_operational_context">SSA-157 requires purpose, requested data, legal authority, volume, frequency, safeguards, prior exchange history.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0022" source="R197_E0012" target="R197_E0017"><data key="edge_relationship_id">R197_R0022</data><data key="edge_source_entity_id">R197_E0012</data><data key="edge_relationship_type">classifies_sharing_under</data><data key="edge_target_entity_id">R197_E0017</data><data key="edge_operational_context">Administrative payroll and manual transfers excluded from PPDX programmatic data-exchange definition.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0023" source="R197_E0012" target="R197_E0015"><data key="edge_relationship_id">R197_R0023</data><data key="edge_source_entity_id">R197_E0012</data><data key="edge_relationship_type">refers_agreement_type_to</data><data key="edge_target_entity_id">R197_E0015</data><data key="edge_operational_context">Designated SSA legal branches determine applicable agreement type for the exchange.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0024" source="R197_E0012" target="R197_E0018"><data key="edge_relationship_id">R197_R0024</data><data key="edge_source_entity_id">R197_E0012</data><data key="edge_relationship_type">defines_exchange_mode</data><data key="edge_target_entity_id">R197_E0018</data><data key="edge_operational_context">POMS identifies real-time query responses as generic permitted transmission pattern.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0025" source="R197_E0012" target="R197_E0019"><data key="edge_relationship_id">R197_R0025</data><data key="edge_source_entity_id">R197_E0012</data><data key="edge_relationship_type">defines_exchange_mode</data><data key="edge_target_entity_id">R197_E0019</data><data key="edge_operational_context">POMS identifies overnight high-volume batch sharing as generic pattern.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0026" source="R197_E0020" target="SYS_MEF"><data key="edge_relationship_id">R197_R0026</data><data key="edge_source_entity_id">R197_E0020</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Linked DER extract draws on SSA administrative detailed wage records; NOT evidence for modifying MEF.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0027" source="R197_E0020" target="R197_E0021"><data key="edge_relationship_id">R197_R0027</data><data key="edge_source_entity_id">R197_E0020</data><data key="edge_relationship_type">measures_survey_response</data><data key="edge_target_entity_id">R197_E0021</data><data key="edge_operational_context">2024 study compares Census CPS/ASEC WSAL_VAL to SSA DER Box 5 wages.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0028" source="R197_E0020" target="R197_E0022"><data key="edge_relationship_id">R197_R0028</data><data key="edge_source_entity_id">R197_E0020</data><data key="edge_relationship_type">measures_administrative_wage</data><data key="edge_target_entity_id">R197_E0022</data><data key="edge_operational_context">SSA Detailed Earnings Record comparison variable derived from W-2 Box 5.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0029" source="R197_E0020" target="R197_E0023"><data key="edge_relationship_id">R197_R0029</data><data key="edge_source_entity_id">R197_E0020</data><data key="edge_relationship_type">limited_by</data><data key="edge_target_entity_id">R197_E0023</data><data key="edge_operational_context">Research excludes self-employment reported via IRS Schedule SE.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0030" source="R197_E0020" target="R197_E0024"><data key="edge_relationship_id">R197_R0030</data><data key="edge_source_entity_id">R197_E0020</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R197_E0024</data><data key="edge_operational_context">Earnings difference metrics depend on survey nonresponse/imputation and wage definitions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0031" source="R197_E0025" target="R197_E0020"><data key="edge_relationship_id">R197_R0031</data><data key="edge_source_entity_id">R197_E0025</data><data key="edge_relationship_type">publishes_analysis_of</data><data key="edge_target_entity_id">R197_E0020</data><data key="edge_operational_context">2024 SSA Research and Statistics Note 2024-01 reports linked CPS and DER wage differences.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R197_R0032" source="R197_E0021" target="R197_E0022"><data key="edge_relationship_id">R197_R0032</data><data key="edge_source_entity_id">R197_E0021</data><data key="edge_relationship_type">compared_with</data><data key="edge_target_entity_id">R197_E0022</data><data key="edge_operational_context">CPS WSAL_VAL and DER W-2 Box 5 are different measures and should not be treated as identical administrative data elements.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0001" source="APP_EDCS" target="DB_DCF"><data key="edge_relationship_id">R198_R0001</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">automatically_posts_medical_cdr_appeal_to</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">EDCS transfer updates DCF on standard Title II medical CDR appeal pathway; excluded cases follow separate exception route.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0002" source="APP_EDCS" target="SYS_MBR"><data key="edge_relationship_id">R198_R0002</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">automatically_posts_medical_cdr_appeal_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">EDCS transfer updates MBR on standard Title II medical CDR appeal pathway; verify completion and exception handling.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0003" source="R198_E0001" target="SYS_MBR"><data key="edge_relationship_id">R198_R0003</data><data key="edge_source_entity_id">R198_E0001</data><data key="edge_relationship_type">governs_controlled_change_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Explicit automatic transfer is limited to documented Title II CDR appeal process.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0004" source="R198_E0006" target="SYS_SSR"><data key="edge_relationship_id">R198_R0004</data><data key="edge_source_entity_id">R198_E0006</data><data key="edge_relationship_type">documents_appeal_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">MSSICS initial appeal entry captures Title XVI CDR/SBC data on SSR before verification in EDCS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0005" source="R198_E0006" target="APP_EDCS"><data key="edge_relationship_id">R198_R0005</data><data key="edge_source_entity_id">R198_E0006</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Title XVI data entered in MSSICS should mirror in EDCS; user instructed to verify.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0006" source="R198_E0002" target="SYS_MBR"><data key="edge_relationship_id">R198_R0006</data><data key="edge_source_entity_id">R198_E0002</data><data key="edge_relationship_type">verifies_updates_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">FO five-day follow-up for MBR after medical CDR appeal determination.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0007" source="R198_E0002" target="SYS_SSR"><data key="edge_relationship_id">R198_R0007</data><data key="edge_source_entity_id">R198_E0002</data><data key="edge_relationship_type">verifies_updates_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">FO five-day follow-up for SSR in Title XVI and concurrent medical CDR appeals.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0008" source="R198_E0003" target="APP_EDCS"><data key="edge_relationship_id">R198_R0008</data><data key="edge_source_entity_id">R198_E0003</data><data key="edge_relationship_type">notifies_after_master_record_changes</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">FO makes applicable MBR, MSSICS and EDCS entries before sending a UAT to DDS/DHU; UAT is downstream notice, not new master-record source.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0009" source="R198_E0004" target="APP_EDCS"><data key="edge_relationship_id">R198_R0009</data><data key="edge_source_entity_id">R198_E0004</data><data key="edge_relationship_type">requires_manual_DHU_notification_after</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Hearing-site escalation uses case-transferred contact and manual DHU phone/email; no automatic office assignment established.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0010" source="R198_E0005" target="APP_PCACS"><data key="edge_relationship_id">R198_R0010</data><data key="edge_source_entity_id">R198_E0005</data><data key="edge_relationship_type">escalates_if_posting_exception_unaccounted_for</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">When neither DIBCESS in PCACS nor THIS exception exists, FO uses DCF Problem Report route.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0011" source="APP_PUPS" target="APP_T2R"><data key="edge_relationship_id">R198_R0011</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">creates_future_suspension_transaction_in</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">PUPS action SUSPEND BENEFITS creates T2R future due-process suspension transaction.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0012" source="APP_T2R" target="SYS_MBR"><data key="edge_relationship_id">R198_R0012</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">posts_prisoner_status_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">After 15/35-day due process T2R attempts LAF S7 and RFST PRISON/MENTAL/PREDTR on MBR.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0013" source="R198_E0007" target="SYS_MBR"><data key="edge_relationship_id">R198_R0013</data><data key="edge_source_entity_id">R198_E0007</data><data key="edge_relationship_type">gates_update_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">LAF S7 entry waits 15 or 35 days; ordinary input is not immediate SSI or Title II benefit discontinuance.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0014" source="SYS_MBR" target="APP_PUPS"><data key="edge_relationship_id">R198_R0014</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_suspension_feedback_to</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">MBR LAF S7 feedback closes PUPS prisoner record to suspension after successful processing.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0015" source="R198_E0009" target="APP_PCACS"><data key="edge_relationship_id">R198_R0015</data><data key="edge_source_entity_id">R198_E0009</data><data key="edge_relationship_type">creates_exception_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">PCACS PRISON/PRISUS action-control records identify T2R posting failures needing PC action.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0016" source="R198_E0010" target="APP_PUPS"><data key="edge_relationship_id">R198_R0016</data><data key="edge_source_entity_id">R198_E0010</data><data key="edge_relationship_type">escalates_manual_MBR_suspension_for</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">When exception path fails, use 2790-FAX processing-center manual suspension with PUPS *PENDING retained.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0017" source="R198_E0011" target="APP_PUPS"><data key="edge_relationship_id">R198_R0017</data><data key="edge_source_entity_id">R198_E0011</data><data key="edge_relationship_type">reports_admission_and_transfer_data_to</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Federal BOP sends monthly new inmate and transfer reporting for PUPS computer matching.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0018" source="R198_E0012" target="APP_IRCS"><data key="edge_relationship_id">R198_R0018</data><data key="edge_source_entity_id">R198_E0012</data><data key="edge_relationship_type">maps_BOP_incoming_code_via</data><data key="edge_target_entity_id">APP_IRCS</data><data key="edge_operational_context">PUPS three-digit BOP source facility code converted to six-digit code on IRCS, facility name shown on actionable alert.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0019" source="R198_E0013" target="APP_PUPS"><data key="edge_relationship_id">R198_R0019</data><data key="edge_source_entity_id">R198_E0013</data><data key="edge_relationship_type">controls_identity_verification_on</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Questionable EVS codes trigger additional verification; otherwise valid V/L are not routinely redeveloped.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0020" source="R198_E0014" target="APP_PUPS"><data key="edge_relationship_id">R198_R0020</data><data key="edge_source_entity_id">R198_E0014</data><data key="edge_relationship_type">qualifies_location_data_in</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Custody facility and transfer destinations are not beneficiary residence or mailing address.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0021" source="R198_E0015" target="APP_PUPS"><data key="edge_relationship_id">R198_R0021</data><data key="edge_source_entity_id">R198_E0015</data><data key="edge_relationship_type">constrains_inmate_event_data_in</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Monthly BOP report lacks release date; no automated discharge date should be inferred.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0022" source="R198_E0017" target="QRY_DEQY"><data key="edge_relationship_id">R198_R0022</data><data key="edge_source_entity_id">R198_E0017</data><data key="edge_relationship_type">uses_payer_EIN_to_query</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">DEQY is specified payer identifier lookup when IRS alert payer name/address is blank or improbable.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0023" source="R198_E0016" target="QRY_DEQY"><data key="edge_relationship_id">R198_R0023</data><data key="edge_source_entity_id">R198_E0016</data><data key="edge_relationship_type">uses_EIN_resolution_via</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">DEQY checks possible same-digit EIN and SSN identity confusion from IRS alert payee details.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0024" source="R198_E0018" target="DB_BFS_SAVINGS_SECURITY_REG"><data key="edge_relationship_id">R198_R0024</data><data key="edge_source_entity_id">R198_E0018</data><data key="edge_relationship_type">historical_index_component_of</data><data key="edge_target_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="edge_operational_context">Historical Treasury bond registration indexing by owner name/address of original purchase, no assertion of active 2026 same physical storage.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0025" source="R198_E0019" target="DB_BFS_SAVINGS_SECURITY_REG"><data key="edge_relationship_id">R198_R0025</data><data key="edge_source_entity_id">R198_E0019</data><data key="edge_relationship_type">historical_index_component_of</data><data key="edge_target_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="edge_operational_context">Registration by SSN applies for later bonds; it is not universal identifier resolution for older issues.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0026" source="R198_E0020" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R198_R0026</data><data key="edge_source_entity_id">R198_E0020</data><data key="edge_relationship_type">uses_IRS_taxpayer_alert_under</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">Farm Subsidy external verification based on tax alert; county payer verification rather than assumed farm ownership.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0027" source="DB_BFS_SAVINGS_SECURITY_REG" target="SYS_SSR"><data key="edge_relationship_id">R198_R0027</data><data key="edge_source_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="edge_relationship_type">matched_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI records for eligible recipients and deemors are compared against BFS savings securities file; claims restricted to match described in Sept 2026 POMS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0028" source="R198_E0021" target="WORK_SSI_SB_DIARY"><data key="edge_relationship_id">R198_R0028</data><data key="edge_source_entity_id">R198_E0021</data><data key="edge_relationship_type">attribute_on</data><data key="edge_target_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_operational_context">SB alert includes possible book account number and separate value return-date, not current account balance without verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0029" source="R198_E0022" target="WORK_SSI_SB_DIARY"><data key="edge_relationship_id">R198_R0029</data><data key="edge_source_entity_id">R198_E0022</data><data key="edge_relationship_type">suppresses_repeated_alerts_on</data><data key="edge_target_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_operational_context">Aggregate redemption amount &gt;= $1,000 with two-previous-match suppression.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0030" source="R198_E0023" target="WORK_SSI_SB_DIARY"><data key="edge_relationship_id">R198_R0030</data><data key="edge_source_entity_id">R198_E0023</data><data key="edge_relationship_type">controls_owner_validation_for</data><data key="edge_target_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_operational_context">Holder name, not merely associated SSN, controls security ownership review.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0031" source="R198_E0024" target="SYS_SSR"><data key="edge_relationship_id">R198_R0031</data><data key="edge_source_entity_id">R198_E0024</data><data key="edge_relationship_type">updates_verified_resource_status_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Employee completes DSAB and builds SSR or direct SSR transaction for non-MSSICS; not BFS direct authoritative write.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0032" source="R198_E0025" target="WORK_SSI_E2_DIARY"><data key="edge_relationship_id">R198_R0032</data><data key="edge_source_entity_id">R198_E0025</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">WORK_SSI_E2_DIARY</data><data key="edge_operational_context">Automatic annual COLA run creates E2 workload on SSR subject to stated LA/payment criteria.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0033" source="R198_E0026" target="SYS_SSR"><data key="edge_relationship_id">R198_R0033</data><data key="edge_source_entity_id">R198_E0026</data><data key="edge_relationship_type">uses_state_attribute_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSR residence-state condition gates historical Sept 2024 rule; no external address ingestion follows from this edit.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0034" source="R198_E0027" target="APP_MSSICS"><data key="edge_relationship_id">R198_R0034</data><data key="edge_source_entity_id">R198_E0027</data><data key="edge_relationship_type">validates_living_arrangements_on</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">MSSICS Living Arrangement Change and close-event edits enforce specified LA creation dates.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0035" source="R198_E0028" target="SYS_SSR"><data key="edge_relationship_id">R198_R0035</data><data key="edge_source_entity_id">R198_E0028</data><data key="edge_relationship_type">affects_subsidy_amount_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI rental subsidy calculation changes payment based on verified rent and PMV/CMRV; staff-directed update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0036" source="R198_E0029" target="SYS_SSR"><data key="edge_relationship_id">R198_R0036</data><data key="edge_source_entity_id">R198_E0029</data><data key="edge_relationship_type">posts_cross_reference_into</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSIDPP field office confirmed same person before cross-referencing M1 and T20 status changes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0037" source="R198_E0030" target="APP_MSSICS"><data key="edge_relationship_id">R198_R0037</data><data key="edge_source_entity_id">R198_E0030</data><data key="edge_relationship_type">controls_pending_file_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Unarchived MSSICS pending file requires MANCLR before incorrect duplicate record is terminated T50.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0038" source="PROC_SSIDPP" target="SYS_NUMIDENT"><data key="edge_relationship_id">R198_R0038</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">uses_identification_records_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Annual duplicate SSI project uses Numident and SSID documents; matching name and month/year of birth alone only selects cases for review.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0039" source="R198_E0031" target="SYS_MEF"><data key="edge_relationship_id">R198_R0039</data><data key="edge_source_entity_id">R198_E0031</data><data key="edge_relationship_type">compares_yearly_earnings_on</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">K6/K7 diary based on MEF annual wage or Schedule SE comparison to SSR wage reporting; specified thresholds and suppression.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0040" source="R198_E0031" target="SYS_SSR"><data key="edge_relationship_id">R198_R0040</data><data key="edge_source_entity_id">R198_E0031</data><data key="edge_relationship_type">compares_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">MEF-to-SSR internal earnings match identifies discrepancy; SSA says CMPPA does not apply to this entirely internal match.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0041" source="R198_E0032" target="QRY_DEQY"><data key="edge_relationship_id">R198_R0041</data><data key="edge_source_entity_id">R198_E0032</data><data key="edge_relationship_type">retrieves_employer_location_using</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">DEQY lists employer name/address as earnings source, not address-update instruction for SSI.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0042" source="R198_E0033" target="R198_E0034"><data key="edge_relationship_id">R198_R0042</data><data key="edge_source_entity_id">R198_E0033</data><data key="edge_relationship_type">supports_request_for</data><data key="edge_target_entity_id">R198_E0034</data><data key="edge_operational_context">Authorized 26 USC 6103(l)(1)(A) SSA request can result in IRS account/return transcript, subject to purpose and signed template.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0043" source="R198_E0033" target="SYS_NUMIDENT"><data key="edge_relationship_id">R198_R0043</data><data key="edge_source_entity_id">R198_E0033</data><data key="edge_relationship_type">contains_taxpayer_correspondence_attribute_but_does_not_update</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Request template includes taxpayer address as identification/request data; no permitted Numident update path established.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0044" source="R198_E0034" target="SYS_MEF"><data key="edge_relationship_id">R198_R0044</data><data key="edge_source_entity_id">R198_E0034</data><data key="edge_relationship_type">supports_evidence_for</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">IRS tax return transcript can support earnings correction investigation; no automatic MEF write established by document.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R198_R0045" source="R198_E0036" target="EX_SASRO"><data key="edge_relationship_id">R198_R0045</data><data key="edge_source_entity_id">R198_E0036</data><data key="edge_relationship_type">governs_state_query_via</data><data key="edge_target_entity_id">EX_SASRO</data><data key="edge_operational_context">Single-query state IEA permits legally authorized uses under Titles II and XVI but no inferred mechanical Numident, SSR or MBR write.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0046" source="R198_E0037" target="ORG_SSA_OAG"><data key="edge_relationship_id">R198_R0046</data><data key="edge_source_entity_id">R198_E0037</data><data key="edge_relationship_type">issued_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">January 2026 security/privacy procurement document made public on OAG acquisition security page.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R198_R0047" source="R198_E0037" target="INIT_CSCRM"><data key="edge_relationship_id">R198_R0047</data><data key="edge_source_entity_id">R198_E0037</data><data key="edge_relationship_type">governance_context_for</data><data key="edge_target_entity_id">INIT_CSCRM</data><data key="edge_operational_context">Agency CSCRM pre-award assessment and post-award monitoring are documented in parallel; exact document-to-platform interface not established.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R199_R0001" source="DB_INTERNET_REPORT" target="R199_E0001"><data key="edge_relationship_id">R199_R0001</data><data key="edge_source_entity_id">DB_INTERNET_REPORT</data><data key="edge_relationship_type">contains_logical_component</data><data key="edge_target_entity_id">R199_E0001</data><data key="edge_operational_context">2014 POMS identifies editable active report file, without underlying physical schema.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0002" source="DB_INTERNET_REPORT" target="R199_E0002"><data key="edge_relationship_id">R199_R0002</data><data key="edge_source_entity_id">DB_INTERNET_REPORT</data><data key="edge_relationship_type">contains_logical_component</data><data key="edge_target_entity_id">R199_E0002</data><data key="edge_operational_context">2014 POMS identifies separate inactive long-term storage; physical implementation unspecified.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0003" source="R199_E0001" target="R199_E0002"><data key="edge_relationship_id">R199_R0003</data><data key="edge_source_entity_id">R199_E0001</data><data key="edge_relationship_type">moves_records_to</data><data key="edge_target_entity_id">R199_E0002</data><data key="edge_operational_context">Archive process moves report out of editable active set.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0004" source="R199_E0003" target="R199_E0002"><data key="edge_relationship_id">R199_R0004</data><data key="edge_source_entity_id">R199_E0003</data><data key="edge_relationship_type">moves_to</data><data key="edge_target_entity_id">R199_E0002</data><data key="edge_operational_context">Archive triggered by filing-period, time-based and WMI-list conditions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0005" source="R199_E0004" target="APP_I3441"><data key="edge_relationship_id">R199_R0005</data><data key="edge_source_entity_id">R199_E0004</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_I3441</data><data key="edge_operational_context">90 days after i3441 started per 2014 instructions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0006" source="R199_E0005" target="APP_I3368"><data key="edge_relationship_id">R199_R0006</data><data key="edge_source_entity_id">R199_E0005</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_I3368</data><data key="edge_operational_context">30 days after protective filing expiration per 2014 instructions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0007" source="R199_E0005" target="APP_I3820"><data key="edge_relationship_id">R199_R0007</data><data key="edge_source_entity_id">R199_E0005</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_I3820</data><data key="edge_operational_context">Same 30-days-after-protective-period rule for i3820.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0008" source="R199_E0006" target="R199_E0002"><data key="edge_relationship_id">R199_R0008</data><data key="edge_source_entity_id">R199_E0006</data><data key="edge_relationship_type">purges_records_from</data><data key="edge_target_entity_id">R199_E0002</data><data key="edge_operational_context">2014 instructions require purge after 120 days in inactive archive, subject to other purge triggers.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0009" source="R199_E0007" target="APP_EDCS"><data key="edge_relationship_id">R199_R0009</data><data key="edge_source_entity_id">R199_E0007</data><data key="edge_relationship_type">blocks_transfer_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Archived IDR inaccessible to EDCS propagation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0010" source="R199_E0007" target="R199_E0002"><data key="edge_relationship_id">R199_R0010</data><data key="edge_source_entity_id">R199_E0007</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R199_E0002</data><data key="edge_operational_context">FO can query/print archive while EDCS cannot propagate it.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0011" source="R199_E0008" target="DB_INTERNET_REPORT"><data key="edge_relationship_id">R199_R0011</data><data key="edge_source_entity_id">R199_E0008</data><data key="edge_relationship_type">groups_records_within</data><data key="edge_target_entity_id">DB_INTERNET_REPORT</data><data key="edge_operational_context">Sets of reports sharing SSN, form and protective filing date are archived or purged together.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0012" source="R199_E0009" target="R199_E0001"><data key="edge_relationship_id">R199_R0012</data><data key="edge_source_entity_id">R199_E0009</data><data key="edge_relationship_type">controls_edit_access_to</data><data key="edge_target_entity_id">R199_E0001</data><data key="edge_operational_context">Unsubmitted editable partial has randomly generated secret reentry number; SSA cannot retrieve forgotten number.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0013" source="R199_E0010" target="R199_E0001"><data key="edge_relationship_id">R199_R0013</data><data key="edge_source_entity_id">R199_E0010</data><data key="edge_relationship_type">locks_record_in</data><data key="edge_target_entity_id">R199_E0001</data><data key="edge_operational_context">Final submit locks user-editable record before EDCS propagation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0014" source="R199_E0011" target="APP_I3368"><data key="edge_relationship_id">R199_R0014</data><data key="edge_source_entity_id">R199_E0011</data><data key="edge_relationship_type">is_collected_by</data><data key="edge_target_entity_id">APP_I3368</data><data key="edge_operational_context">Illustrative IDR provider required fields: first/last name and city/state, not full address.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0015" source="R199_E0012" target="APP_IQF"><data key="edge_relationship_id">R199_R0015</data><data key="edge_source_entity_id">R199_E0012</data><data key="edge_relationship_type">available_through</data><data key="edge_target_entity_id">APP_IQF</data><data key="edge_operational_context">FO may query/print archived IDR until purge, but cannot reactivate for EDCS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0016" source="R199_E0012" target="R199_E0002"><data key="edge_relationship_id">R199_R0016</data><data key="edge_source_entity_id">R199_E0012</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">R199_E0002</data><data key="edge_operational_context">Historical archive lookup capability, no automatic EDCS repopulation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0017" source="R199_E0013" target="APP_IWMI"><data key="edge_relationship_id">R199_R0017</data><data key="edge_source_entity_id">R199_E0013</data><data key="edge_relationship_type">limits</data><data key="edge_target_entity_id">APP_IWMI</data><data key="edge_operational_context">2017 policy states WMI list lacks automatic follow-up.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0018" source="R199_E0014" target="DB_INTERNET_REPORT"><data key="edge_relationship_id">R199_R0018</data><data key="edge_source_entity_id">R199_E0014</data><data key="edge_relationship_type">controls_purge_for</data><data key="edge_target_entity_id">DB_INTERNET_REPORT</data><data key="edge_operational_context">Y marks report for delayed purge and prevents EDCS import.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0019" source="R199_E0015" target="R199_E0014"><data key="edge_relationship_id">R199_R0019</data><data key="edge_source_entity_id">R199_E0015</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R199_E0014</data><data key="edge_operational_context">2017 policy requires removal of mistakenly set Y within seven days.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0020" source="R199_E0016" target="APP_IWMI"><data key="edge_relationship_id">R199_R0020</data><data key="edge_source_entity_id">R199_E0016</data><data key="edge_relationship_type">produced_by</data><data key="edge_target_entity_id">APP_IWMI</data><data key="edge_operational_context">Submission becomes visible on iWMI SSN listing next day under published procedure.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0021" source="R199_E0016" target="APP_I3368"><data key="edge_relationship_id">R199_R0021</data><data key="edge_source_entity_id">R199_E0016</data><data key="edge_relationship_type">identifies</data><data key="edge_target_entity_id">APP_I3368</data><data key="edge_operational_context">Listing may show adult disability report submissions; not an eligibility adjudication.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0022" source="R199_E0017" target="APP_EDCS"><data key="edge_relationship_id">R199_R0022</data><data key="edge_source_entity_id">R199_E0017</data><data key="edge_relationship_type">blocks_propagation_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Preexisting pending DDS case blocks ordinary i3368 import in specified cases.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0023" source="R199_E0018" target="APP_EDCS"><data key="edge_relationship_id">R199_R0023</data><data key="edge_source_entity_id">R199_E0018</data><data key="edge_relationship_type">updates_information_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Compare internet printout to EDCS 3368, document changes by UAT.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0024" source="R199_E0019" target="APP_EDCS"><data key="edge_relationship_id">R199_R0024</data><data key="edge_source_entity_id">R199_E0019</data><data key="edge_relationship_type">manually_transcribes_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">When partial cannot be submitted, FO prints via internet query and transcribes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0025" source="R199_E0019" target="APP_IQF"><data key="edge_relationship_id">R199_R0025</data><data key="edge_source_entity_id">R199_E0019</data><data key="edge_relationship_type">retrieves_partial_from</data><data key="edge_target_entity_id">APP_IQF</data><data key="edge_operational_context">FO internet query accesses printout of partial when normal submit impossible.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0026" source="R199_E0020" target="APP_I3368"><data key="edge_relationship_id">R199_R0026</data><data key="edge_source_entity_id">R199_E0020</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_I3368</data><data key="edge_operational_context">As of Jan 25 2014 i3368 submission requires preceding iClaim.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0027" source="R199_E0020" target="APP_ICLAIM"><data key="edge_relationship_id">R199_R0027</data><data key="edge_source_entity_id">R199_E0020</data><data key="edge_relationship_type">requires_prior_submission_of</data><data key="edge_target_entity_id">APP_ICLAIM</data><data key="edge_operational_context">Submit iClaim before i3368 under 2014+ procedure.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0028" source="R199_E0021" target="APP_MCS"><data key="edge_relationship_id">R199_R0028</data><data key="edge_source_entity_id">R199_E0021</data><data key="edge_relationship_type">requires_claim_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">For Title II i3368 case, MCS claim established before ordinary EDCS creation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0029" source="R199_E0021" target="APP_MSSICS"><data key="edge_relationship_id">R199_R0029</data><data key="edge_source_entity_id">R199_E0021</data><data key="edge_relationship_type">also_allows_claim_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Existing Title XVI MSSICS case supports EDCS intake.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0030" source="R199_E0021" target="APP_EDCS"><data key="edge_relationship_id">R199_R0030</data><data key="edge_source_entity_id">R199_E0021</data><data key="edge_relationship_type">precedes</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Claims system established prior to ordinary EDCS creation and i3368 propagation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0031" source="R199_E0022" target="SYS_MEF"><data key="edge_relationship_id">R199_R0031</data><data key="edge_source_entity_id">R199_E0022</data><data key="edge_relationship_type">corrects_attribution_in</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Documented corrections may transfer wrong-person or wrong-year earnings after normal time limit.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0032" source="R199_E0023" target="DB_ESF"><data key="edge_relationship_id">R199_R0032</data><data key="edge_source_entity_id">R199_E0023</data><data key="edge_relationship_type">transfers_unidentified_wages_to</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">Unidentified workers wages are moved to suspense file by ICOR procedure.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0033" source="R199_E0024" target="SYS_MEF"><data key="edge_relationship_id">R199_R0033</data><data key="edge_source_entity_id">R199_E0024</data><data key="edge_relationship_type">corrects_attribution_in</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Reallocation of existing SEI cannot invent additional reported SEI amount.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0034" source="R199_E0025" target="APP_ICOR"><data key="edge_relationship_id">R199_R0034</data><data key="edge_source_entity_id">R199_E0025</data><data key="edge_relationship_type">performed_using</data><data key="edge_target_entity_id">APP_ICOR</data><data key="edge_operational_context">POMS directs appropriate ICOR action to fix wrong-period/person earnings.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0035" source="R199_E0025" target="DB_ESF"><data key="edge_relationship_id">R199_R0035</data><data key="edge_source_entity_id">R199_E0025</data><data key="edge_relationship_type">moves_wages_to_or_from</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">ICOR may move wage credit into or out of suspense if required.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0036" source="R199_E0026" target="APP_EWORK"><data key="edge_relationship_id">R199_R0036</data><data key="edge_source_entity_id">R199_E0026</data><data key="edge_relationship_type">historically_implemented_by</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">BOND-specific eWork participation notice logic, not currently applicable.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0037" source="R199_E0027" target="DB_DCF"><data key="edge_relationship_id">R199_R0037</data><data key="edge_source_entity_id">R199_E0027</data><data key="edge_relationship_type">historically_read_date_from</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">BOND work review starting the month after demonstration stop date.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0038" source="R199_E0028" target="APP_BOND"><data key="edge_relationship_id">R199_R0038</data><data key="edge_source_entity_id">R199_E0028</data><data key="edge_relationship_type">independent_of_historical</data><data key="edge_target_entity_id">APP_BOND</data><data key="edge_operational_context">Concurrent Title XVI reporting continued under FO standards.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0039" source="R199_E0028" target="SYS_SSR"><data key="edge_relationship_id">R199_R0039</data><data key="edge_source_entity_id">R199_E0028</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Normal SSI changes remained allowed for BOND participants.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R199_R0040" source="R199_E0029" target="APP_BOND"><data key="edge_relationship_id">R199_R0040</data><data key="edge_source_entity_id">R199_E0029</data><data key="edge_relationship_type">historical_status_of</data><data key="edge_target_entity_id">APP_BOND</data><data key="edge_operational_context">Public POMS labels BOND obsolete and closes L5R.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence is date-scoped; no unproven current deployment or transport implied.</data></edge><edge id="R200_R0001" source="APP_SSNAP" target="R200_E001"><data key="edge_relationship_id">R200_R0001</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">R200_E001</data><data key="edge_operational_context">SSNAP submits initial SAVE verification and processes response in the same application path.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0002" source="R200_E001" target="SVC_SAVE"><data key="edge_relationship_id">R200_R0002</data><data key="edge_source_entity_id">R200_E001</data><data key="edge_relationship_type">uses_verification_service</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">SAVE initial verification responds within SSNAP application workflow.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0003" source="R200_E002" target="APP_SSNAP"><data key="edge_relationship_id">R200_R0003</data><data key="edge_source_entity_id">R200_E002</data><data key="edge_relationship_type">has_manual_intake_gate</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Additional SAVE response is electronic but must be pulled into SSNAP by FO action; it does not auto-propagate.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0004" source="R200_E003" target="APP_SSNAP"><data key="edge_relationship_id">R200_R0004</data><data key="edge_source_entity_id">R200_E003</data><data key="edge_relationship_type">has_manual_intake_gate</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Third-level responses are obtained from SSNAP list and manually imported into application.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0005" source="R200_E004" target="APP_SSNAP"><data key="edge_relationship_id">R200_R0005</data><data key="edge_source_entity_id">R200_E004</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Critical A-number and I-94 selection differs between initial and additional SAVE requests.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0006" source="R200_E005" target="APP_SSNAP"><data key="edge_relationship_id">R200_R0006</data><data key="edge_source_entity_id">R200_E005</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Unverified SAVE returns place or keep SSN application in suspect status.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0007" source="R200_E005" target="SYS_NUMIDENT"><data key="edge_relationship_id">R200_R0007</data><data key="edge_source_entity_id">R200_E005</data><data key="edge_relationship_type">contributes_evidence_for</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Successful verified application determines CIT/PRA Numident field values; the procedure does not state an unconditional direct SAVE-to-Numident write.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0008" source="R200_E006" target="APP_SSNAP"><data key="edge_relationship_id">R200_R0008</data><data key="edge_source_entity_id">R200_E006</data><data key="edge_relationship_type">is_legacy_ui_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Residual WRAPS screen is not evidence of a currently operating WRAPS fax verification exchange.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0009" source="R200_E007" target="R200_E006"><data key="edge_relationship_id">R200_R0009</data><data key="edge_source_entity_id">R200_E007</data><data key="edge_relationship_type">circumvents_legacy</data><data key="edge_target_entity_id">R200_E006</data><data key="edge_operational_context">Manual path bypasses discontinued WRAPS fax feature to request SAVE additional verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0010" source="R200_E007" target="SVC_SAVE"><data key="edge_relationship_id">R200_R0010</data><data key="edge_source_entity_id">R200_E007</data><data key="edge_relationship_type">submits_to</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">Workaround submits electronic SAVE additional verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0011" source="R200_E008" target="APP_SSNAP"><data key="edge_relationship_id">R200_R0011</data><data key="edge_source_entity_id">R200_E008</data><data key="edge_relationship_type">is_evidence_input_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Combined CBP I-94 and DOS boarding letter accepted as specified refugee SSN-card documentation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0012" source="PROC_RETAP" target="R200_E009"><data key="edge_relationship_id">R200_R0012</data><data key="edge_source_entity_id">PROC_RETAP</data><data key="edge_relationship_type">implements</data><data key="edge_target_entity_id">R200_E009</data><data key="edge_operational_context">Established RETAP operation selects impending Medicare entitlement cases monthly.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0013" source="R200_E009" target="SYS_MBR"><data key="edge_relationship_id">R200_R0013</data><data key="edge_source_entity_id">R200_E009</data><data key="edge_relationship_type">posts_conditional_entitlement_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">RETAP establishes Medicare HI and SMI on MBR for specified domestic jurisdictions; partial abroad/PR exception.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0014" source="R200_E010" target="PROC_RETAP"><data key="edge_relationship_id">R200_R0014</data><data key="edge_source_entity_id">R200_E010</data><data key="edge_relationship_type">restricts</data><data key="edge_target_entity_id">PROC_RETAP</data><data key="edge_operational_context">Puerto Rico and foreign residence change SMI automatic enrollment behavior.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0015" source="R200_E009" target="R200_E011"><data key="edge_relationship_id">R200_R0015</data><data key="edge_source_entity_id">R200_E009</data><data key="edge_relationship_type">produces_downstream_notification_for</data><data key="edge_target_entity_id">R200_E011</data><data key="edge_operational_context">SSA provides entitlement information to CMS for domestic initial enrollment notices.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0016" source="R200_E011" target="ORG_CMS"><data key="edge_relationship_id">R200_R0016</data><data key="edge_source_entity_id">R200_E011</data><data key="edge_relationship_type">fulfilled_by</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS mails entitlement packages and cards after SSA eligibility data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0017" source="R200_E012" target="SYS_MBR"><data key="edge_relationship_id">R200_R0017</data><data key="edge_source_entity_id">R200_E012</data><data key="edge_relationship_type">changes_program_enrollment_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SMI refusal is recorded through SSA processing; CMS issues revised Medicare card.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0018" source="R200_E012" target="ORG_CMS"><data key="edge_relationship_id">R200_R0018</data><data key="edge_source_entity_id">R200_E012</data><data key="edge_relationship_type">requires_downstream_action_by</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS issues revised Medicare card showing HI entitlement only.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0019" source="R200_E013" target="APP_PPC"><data key="edge_relationship_id">R200_R0019</data><data key="edge_source_entity_id">R200_E013</data><data key="edge_relationship_type">routed_to</data><data key="edge_target_entity_id">APP_PPC</data><data key="edge_operational_context">SSA-409 paperless fax alerts PC of actionable evidence and enables proper TOEL coding.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0020" source="R200_E013" target="APP_EVIEW"><data key="edge_relationship_id">R200_R0020</data><data key="edge_source_entity_id">R200_E013</data><data key="edge_relationship_type">notifies_action_stored_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">SSA-409 tells PC the actionable supporting material was filed in eView.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0021" source="R200_E014" target="APP_EVIEW"><data key="edge_relationship_id">R200_R0021</data><data key="edge_source_entity_id">R200_E014</data><data key="edge_relationship_type">documents_missing_auto_alert_from</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Document image arrival alone does not initiate PC work; independent notice required.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0022" source="R200_E014" target="R200_E013"><data key="edge_relationship_id">R200_R0022</data><data key="edge_source_entity_id">R200_E014</data><data key="edge_relationship_type">requires_form</data><data key="edge_target_entity_id">R200_E013</data><data key="edge_operational_context">Manual SSA-409 fax to PPC is mandatory for PC action.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0023" source="R200_E015" target="APP_EDCS"><data key="edge_relationship_id">R200_R0023</data><data key="edge_source_entity_id">R200_E015</data><data key="edge_relationship_type">authoritative_when_electronic</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS entry serves as official disability report in regular electronic cases.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0024" source="R200_E015" target="REPO_MDF"><data key="edge_relationship_id">R200_R0024</data><data key="edge_source_entity_id">R200_E015</data><data key="edge_relationship_type">exception_document_stored_in</data><data key="edge_target_entity_id">REPO_MDF</data><data key="edge_operational_context">EDCS exclusions require retaining paper disability report in modular disability folder.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0025" source="R200_E016" target="APP_EVIEW"><data key="edge_relationship_id">R200_R0025</data><data key="edge_source_entity_id">R200_E016</data><data key="edge_relationship_type">governs_document_indexing_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Document folder indexes use NH SSN or disabled auxiliary BOAN according to benefit role.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0026" source="R200_E017" target="APP_EVIEW"><data key="edge_relationship_id">R200_R0026</data><data key="edge_source_entity_id">R200_E017</data><data key="edge_relationship_type">writes_evidence_to</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Regional DMA fax converts barcoded evidence into eView; employee verifies image pages.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0027" source="R200_E018" target="APP_QRCPS"><data key="edge_relationship_id">R200_R0027</data><data key="edge_source_entity_id">R200_E018</data><data key="edge_relationship_type">managed_in</data><data key="edge_target_entity_id">APP_QRCPS</data><data key="edge_operational_context">DQR management assigns MAQR task to qualified reviewers in QRCPS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0028" source="R200_E019" target="APP_QRCPS"><data key="edge_relationship_id">R200_R0028</data><data key="edge_source_entity_id">R200_E019</data><data key="edge_relationship_type">routed_through</data><data key="edge_target_entity_id">APP_QRCPS</data><data key="edge_operational_context">Medical referral generated through quality-review case processing system.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0029" source="R200_E020" target="APP_EVIEW"><data key="edge_relationship_id">R200_R0029</data><data key="edge_source_entity_id">R200_E020</data><data key="edge_relationship_type">posts_documents_to</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Final MC/PC forms uploaded to eView; earlier determinations maintained in audit trail.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0030" source="R200_E020" target="PROC_DQR_QUALITY_REVIEW"><data key="edge_relationship_id">R200_R0030</data><data key="edge_source_entity_id">R200_E020</data><data key="edge_relationship_type">supports_process</data><data key="edge_target_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_operational_context">DQR FQR checks MC/PC documentation and preserves original assessments.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0031" source="R200_E021" target="PROC_IDD"><data key="edge_relationship_id">R200_R0031</data><data key="edge_source_entity_id">R200_E021</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">International deposit destination may differ from country of foreign residence; separate legal-use and address types.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0032" source="R200_E022" target="PROC_IDD"><data key="edge_relationship_id">R200_R0032</data><data key="edge_source_entity_id">R200_E022</data><data key="edge_relationship_type">is_precondition_of</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">Foreign residence and stored foreign address are prerequisites; domestic relocation ends arrangement.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0033" source="R200_E023" target="FORM_SSA1199_FAMILY"><data key="edge_relationship_id">R200_R0033</data><data key="edge_source_entity_id">R200_E023</data><data key="edge_relationship_type">requires_identity_check_for</data><data key="edge_target_entity_id">FORM_SSA1199_FAMILY</data><data key="edge_operational_context">Mailed SSA-1199 enrollment requests require prior beneficiary identity verification.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0034" source="R200_E023" target="PROC_IDD"><data key="edge_relationship_id">R200_R0034</data><data key="edge_source_entity_id">R200_E023</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">Identity check required before modifying beneficiary IDD bank information.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0035" source="R200_E024" target="SYS_MBR"><data key="edge_relationship_id">R200_R0035</data><data key="edge_source_entity_id">R200_E024</data><data key="edge_relationship_type">compares_updated_address_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Treasury returned mail prompts check for MBR newer address; this is lookup, not Treasury authoritative address write.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0036" source="R200_E024" target="SYS_SSR"><data key="edge_relationship_id">R200_R0036</data><data key="edge_source_entity_id">R200_E024</data><data key="edge_relationship_type">compares_updated_address_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Treasury returned mail prompts check for SSR newer address; SSA develops/updates only through separate authorized action.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0037" source="R200_E025" target="SVC_TCIS"><data key="edge_relationship_id">R200_R0037</data><data key="edge_source_entity_id">R200_E025</data><data key="edge_relationship_type">retrieved_from</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">TCIS claim form can be printed by SSA employee, with Direct Express exception.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0038" source="R200_E026" target="APP_DMS"><data key="edge_relationship_id">R200_R0038</data><data key="edge_source_entity_id">R200_E026</data><data key="edge_relationship_type">updates_debt_with</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">PC manually posts returned-payment credit using DMS RRRE.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0039" source="R200_E026" target="SYS_MBR"><data key="edge_relationship_id">R200_R0039</data><data key="edge_source_entity_id">R200_E026</data><data key="edge_relationship_type">adds_note_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PC posts required special MBR message documenting returned fraud redirected-payment credit.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0040" source="R200_E027" target="SYS_SSR"><data key="edge_relationship_id">R200_R0040</data><data key="edge_source_entity_id">R200_E027</data><data key="edge_relationship_type">posts_recovered_credit_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA OBASA credits reflected in OPRR or PMTH based on partial/full returned payment.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0041" source="R200_E028" target="SYS_MBR"><data key="edge_relationship_id">R200_R0041</data><data key="edge_source_entity_id">R200_E028</data><data key="edge_relationship_type">corrects_benefit_statement_using</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PC issues corrected SSA-1099 based on actual recipient payment after unauthorized redirection; source does not detail underlying data store.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0042" source="R200_E029" target="SYS_MBR"><data key="edge_relationship_id">R200_R0042</data><data key="edge_source_entity_id">R200_E029</data><data key="edge_relationship_type">stages_online_change_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Online direct deposit changes are sent to a database then updated to MBR; intermediary remains unnamed in source.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R200_R0043" source="APP_MYDD" target="R200_E029"><data key="edge_relationship_id">R200_R0043</data><data key="edge_source_entity_id">APP_MYDD</data><data key="edge_relationship_type">uses_posting_process</data><data key="edge_target_entity_id">R200_E029</data><data key="edge_operational_context">SSA Open Data describes online transaction capture and subsequent MBR posting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Date-scoped authoritative policy; not proof of unspecified automatic updates.</data></edge><edge id="R201_REL001" source="R201_E001" target="APP_SSI_RZ_MODEL"><data key="edge_relationship_id">R201_REL001</data><data key="edge_source_entity_id">R201_E001</data><data key="edge_relationship_type">modifies_2026_claims_rule_for</data><data key="edge_target_entity_id">APP_SSI_RZ_MODEL</data><data key="edge_operational_context">Title II protective filing from SSI redetermination</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">New rule effective 2026-04-27; earlier redeterminations use archived policy.</data></edge><edge id="R201_REL002" source="APP_IAPPT" target="APP_MCS"><data key="edge_relationship_id">R201_REL002</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">auto_propagates_protective_date_to</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">iAppt scheduling/protective filing</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Specific filing-date movement with required verification; separate from person data.</data></edge><edge id="R201_REL003" source="APP_IAPPT" target="APP_CCE"><data key="edge_relationship_id">R201_REL003</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">auto_propagates_protective_date_to</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">iAppt scheduling/protective filing</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">POMS describes automatic movement to MCS or CCE, according to claim context.</data></edge><edge id="R201_REL004" source="R201_E002" target="APP_IAPPT"><data key="edge_relationship_id">R201_REL004</data><data key="edge_source_entity_id">R201_E002</data><data key="edge_relationship_type">governs_auto_propagation_from</data><data key="edge_target_entity_id">APP_IAPPT</data><data key="edge_operational_context">iAppt protective filing date cross-system processing</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Employee must check filing date.</data></edge><edge id="R201_REL005" source="R201_E003" target="SYS_MBR"><data key="edge_relationship_id">R201_REL005</data><data key="edge_source_entity_id">R201_E003</data><data key="edge_relationship_type">governs_filing_date_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II protective filing displayed as MBR filing date</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Does not change independent claim receipt date.</data></edge><edge id="R201_REL006" source="R201_E004" target="APP_MSSICS"><data key="edge_relationship_id">R201_REL006</data><data key="edge_source_entity_id">R201_E004</data><data key="edge_relationship_type">governs_ssi_receipt_entry_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">SSI age-65 special system exception</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Exception applies in specifically described cases; review full POMS for predicate.</data></edge><edge id="R201_REL007" source="R201_E005" target="APP_MCS"><data key="edge_relationship_id">R201_REL007</data><data key="edge_source_entity_id">R201_E005</data><data key="edge_relationship_type">controls_claim_receipt_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">iClaim receipt date vs MCS case establishment date</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">IMNU submission is actual receipt when valid electronically signed claim.</data></edge><edge id="R201_REL008" source="UI_RASR_ROC" target="APP_MCS"><data key="edge_relationship_id">R201_REL008</data><data key="edge_source_entity_id">UI_RASR_ROC</data><data key="edge_relationship_type">requires_separate_documentation_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Representative direct claimant contact: RPOC</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">RASR contact does not auto-populate MCS.</data></edge><edge id="R201_REL009" source="UI_RASR_ROC" target="APP_CCE"><data key="edge_relationship_id">R201_REL009</data><data key="edge_source_entity_id">UI_RASR_ROC</data><data key="edge_relationship_type">requires_separate_documentation_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Representative direct claimant contact: DROC</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">RASR contact does not auto-populate CCE.</data></edge><edge id="R201_REL010" source="R201_E006" target="UI_RASR_ROC"><data key="edge_relationship_id">R201_REL010</data><data key="edge_source_entity_id">R201_E006</data><data key="edge_relationship_type">requires_contact_documentation_in</data><data key="edge_target_entity_id">UI_RASR_ROC</data><data key="edge_operational_context">Represented-claimant exception documentation</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">RASR contact record additionally required.</data></edge><edge id="R201_REL011" source="R201_E007" target="APP_MCS"><data key="edge_relationship_id">R201_REL011</data><data key="edge_source_entity_id">R201_E007</data><data key="edge_relationship_type">is_manual_entry_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Represented-claimant RPOC</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic update from RASR.</data></edge><edge id="R201_REL012" source="R201_E008" target="APP_CCE"><data key="edge_relationship_id">R201_REL012</data><data key="edge_source_entity_id">R201_E008</data><data key="edge_relationship_type">is_manual_entry_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Represented-claimant DROC</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic update from RASR.</data></edge><edge id="R201_REL013" source="R201_E009" target="R201_E027"><data key="edge_relationship_id">R201_REL013</data><data key="edge_source_entity_id">R201_E009</data><data key="edge_relationship_type">documented_on</data><data key="edge_target_entity_id">R201_E027</data><data key="edge_operational_context">Nonblind and later blind onset dates</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Distinct SSI and Title II notation; see POMS for fields.</data></edge><edge id="R201_REL014" source="R201_E010" target="UI_MCS_DICL"><data key="edge_relationship_id">R201_REL014</data><data key="edge_source_entity_id">R201_E010</data><data key="edge_relationship_type">is_exception_to_data_propagation_in</data><data key="edge_target_entity_id">UI_MCS_DICL</data><data key="edge_operational_context">Later blind onset not propagated when nonblind earlier</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Employees review SSA-831; not evidence of lost medical onset.</data></edge><edge id="R201_REL015" source="R201_E010" target="APP_MSSICS"><data key="edge_relationship_id">R201_REL015</data><data key="edge_source_entity_id">R201_E010</data><data key="edge_relationship_type">is_exception_to_data_propagation_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Title XVI blind onset clearance</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Later onset need not propagate to SSI clearance.</data></edge><edge id="R201_REL016" source="R201_E011" target="UI_MCS_DICL"><data key="edge_relationship_id">R201_REL016</data><data key="edge_source_entity_id">R201_E011</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">UI_MCS_DICL</data><data key="edge_operational_context">Title II adjusted statutory blind onset date</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">ABOD can propagate where applicable.</data></edge><edge id="R201_REL017" source="R201_E012" target="SYS_SSR"><data key="edge_relationship_id">R201_REL017</data><data key="edge_source_entity_id">R201_E012</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSI blind classification conversion</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">TMR and recipient ID fields may update; manual follow-up on failure.</data></edge><edge id="R201_REL018" source="R201_E013" target="R201_E027"><data key="edge_relationship_id">R201_REL018</data><data key="edge_source_entity_id">R201_E013</data><data key="edge_relationship_type">applies_historically_to</data><data key="edge_target_entity_id">R201_E027</data><data key="edge_operational_context">Pre-2012 statutory blind coding</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">2012-12-01 diagnosis code 3694 policy discontinuity.</data></edge><edge id="R201_REL019" source="R201_E014" target="SVC_ITS_GOV"><data key="edge_relationship_id">R201_REL019</data><data key="edge_source_entity_id">R201_E014</data><data key="edge_relationship_type">requires_separate_transaction_in</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Lithuania IDD Treasury enrollment</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Same-day dual entry requirement, not automated integration.</data></edge><edge id="R201_REL020" source="R201_E014" target="SYS_MBR"><data key="edge_relationship_id">R201_REL020</data><data key="edge_source_entity_id">R201_E014</data><data key="edge_relationship_type">uses_mbr_bank_fields_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Lithuania IDD bank coding</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA master-record direct deposit fields used.</data></edge><edge id="R201_REL021" source="R201_E014" target="ORG_TREASURY"><data key="edge_relationship_id">R201_REL021</data><data key="edge_source_entity_id">R201_E014</data><data key="edge_relationship_type">routes_payment_through</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">International payment clearing and enrollment</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Treasury ITS.gov and Federal Reserve Bank of Kansas City cited as distinct roles.</data></edge><edge id="R201_REL022" source="R201_E015" target="SVC_ITS_GOV"><data key="edge_relationship_id">R201_REL022</data><data key="edge_source_entity_id">R201_E015</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Lithuania bank-enrollment beneficiary address</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">LT/Town/Name address notation; no automatic residence update inferred.</data></edge><edge id="R201_REL023" source="R201_E016" target="R201_E017"><data key="edge_relationship_id">R201_REL023</data><data key="edge_source_entity_id">R201_E016</data><data key="edge_relationship_type">used_to_derive</data><data key="edge_target_entity_id">R201_E017</data><data key="edge_operational_context">Lithuania IBAN and RTN programming</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Published procedural transformation; exact parsing fields not fully specified.</data></edge><edge id="R201_REL024" source="R201_E016" target="R201_E018"><data key="edge_relationship_id">R201_REL024</data><data key="edge_source_entity_id">R201_E016</data><data key="edge_relationship_type">used_to_derive</data><data key="edge_target_entity_id">R201_E018</data><data key="edge_operational_context">Lithuania IBAN and DAN coding</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Account transformation documented, but 20 vs 21 vs H+11 characters inconsistent.</data></edge><edge id="R201_REL025" source="R201_E017" target="SYS_MBR"><data key="edge_relationship_id">R201_REL025</data><data key="edge_source_entity_id">R201_E017</data><data key="edge_relationship_type">stored_in_mbr_direct_deposit_fields_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Lithuania RTN and MBR beneficiary deposit record</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">66 multi-country prefix.</data></edge><edge id="R201_REL026" source="R201_E018" target="SYS_MBR"><data key="edge_relationship_id">R201_REL026</data><data key="edge_source_entity_id">R201_E018</data><data key="edge_relationship_type">stored_in_mbr_direct_deposit_fields_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Lithuania account number with H prefix</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Precise account-length algorithm unresolved in published text.</data></edge><edge id="R201_REL027" source="R201_E019" target="R201_E014"><data key="edge_relationship_id">R201_REL027</data><data key="edge_source_entity_id">R201_E019</data><data key="edge_relationship_type">provides_country_specific_intake_to</data><data key="edge_target_entity_id">R201_E014</data><data key="edge_operational_context">Lithuania SSA-1199 form alternative</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Mail, phone, or fax also possible.</data></edge><edge id="R201_REL028" source="R201_E020" target="R201_E014"><data key="edge_relationship_id">R201_REL028</data><data key="edge_source_entity_id">R201_E020</data><data key="edge_relationship_type">flags_conflict_in</data><data key="edge_target_entity_id">R201_E014</data><data key="edge_operational_context">Lithuania IDD Euro validation branch</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Published STOP on Euro account contradicts Euro requirement.</data></edge><edge id="R201_REL029" source="R201_E021" target="SVC_ITS_GOV"><data key="edge_relationship_id">R201_REL029</data><data key="edge_source_entity_id">R201_E021</data><data key="edge_relationship_type">captured_by</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Treasury bank-routing enrollment details</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Distinct bank metadata, not beneficiary address.</data></edge><edge id="R201_REL030" source="R201_E022" target="APP_RASR"><data key="edge_relationship_id">R201_REL030</data><data key="edge_source_entity_id">R201_E022</data><data key="edge_relationship_type">governs_notice_suppression_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">IDPE notices for already-ineligible entity</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">New records must be resolved even without new auto notice.</data></edge><edge id="R201_REL031" source="R201_E023" target="APP_RASR"><data key="edge_relationship_id">R201_REL031</data><data key="edge_source_entity_id">R201_E023</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">IDPE incident keyed by EIN and claimant SSN</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Per fee occurrence; separate from claimant eligibility master.</data></edge><edge id="R201_REL032" source="R201_E024" target="APP_MYSSA"><data key="edge_relationship_id">R201_REL032</data><data key="edge_source_entity_id">R201_E024</data><data key="edge_relationship_type">delivers_benefit_verification_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Historical my Social Security BEVE to address of record</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Published POMS does not identify the source database for the address.</data></edge><edge id="R201_REL033" source="R201_E025" target="APP_EDCS"><data key="edge_relationship_id">R201_REL033</data><data key="edge_source_entity_id">R201_E025</data><data key="edge_relationship_type">requires_transfer_of_paper_folder_alongside</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Concurrent medical CDR supporting documents</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Electronic folder may coexist with external paper folder.</data></edge><edge id="R201_REL034" source="R201_E026" target="APP_EAFI"><data key="edge_relationship_id">R201_REL034</data><data key="edge_source_entity_id">R201_E026</data><data key="edge_relationship_type">governs_electronic_verification_using</data><data key="edge_target_entity_id">APP_EAFI</data><data key="edge_operational_context">2026 SSI allowances resource verification</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Applies even with no alleged accounts; follow applicable timing/permission rules.</data></edge><edge id="R202_REL001" source="R202_E001" target="R202_E002"><data key="edge_relationship_id">R202_REL001</data><data key="edge_source_entity_id">R202_E001</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">R202_E002</data><data key="edge_operational_context">State DCF maintains ACCESS; SSA field offices have permitted inquiry-only access, not database replication.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">State DCF maintains ACCESS; SSA field offices have permitted inquiry-only access, not database replication.</data></edge><edge id="R202_REL002" source="EX_SASRO" target="R202_E002"><data key="edge_relationship_id">R202_REL002</data><data key="edge_source_entity_id">EX_SASRO</data><data key="edge_relationship_type">supports_authorized_state_record_query_of</data><data key="edge_target_entity_id">R202_E002</data><data key="edge_operational_context">Vermont DCF online SASRO arrangement provides limited inquiry-only ACCESS access.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Vermont DCF online SASRO arrangement provides limited inquiry-only ACCESS access.</data></edge><edge id="R202_REL003" source="R202_E002" target="R202_E003"><data key="edge_relationship_id">R202_REL003</data><data key="edge_source_entity_id">R202_E002</data><data key="edge_relationship_type">supplies_custodial_verification_of</data><data key="edge_target_entity_id">R202_E003</data><data key="edge_operational_context">Certain state-origin public assistance and child-support benefits may be used as custodian records with specified exceptions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Certain state-origin public assistance and child-support benefits may be used as custodian records with specified exceptions.</data></edge><edge id="R202_REL004" source="R202_E002" target="R202_E004"><data key="edge_relationship_id">R202_REL004</data><data key="edge_source_entity_id">R202_E002</data><data key="edge_relationship_type">exposes_unverified_collateral</data><data key="edge_target_entity_id">R202_E004</data><data key="edge_operational_context">Reported recipient addresses and telephone numbers from Vermont DCF are collateral leads requiring development.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Reported recipient addresses and telephone numbers from Vermont DCF are collateral leads requiring development.</data></edge><edge id="R202_REL005" source="R202_E005" target="R202_E004"><data key="edge_relationship_id">R202_REL005</data><data key="edge_source_entity_id">R202_E005</data><data key="edge_relationship_type">requires_independent_verification_of</data><data key="edge_target_entity_id">R202_E004</data><data key="edge_operational_context">State DCF recipient address must not be presumed verified or automatically posted to MBR or SSR.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">State DCF recipient address must not be presumed verified or automatically posted to MBR or SSR.</data></edge><edge id="R202_REL006" source="R202_E005" target="R202_E003"><data key="edge_relationship_id">R202_REL006</data><data key="edge_source_entity_id">R202_E005</data><data key="edge_relationship_type">permits_custodial_evidence_from</data><data key="edge_target_entity_id">R202_E003</data><data key="edge_operational_context">Some custodial benefit data may be used directly subject to the POMS qualifications.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Some custodial benefit data may be used directly subject to the POMS qualifications.</data></edge><edge id="R202_REL007" source="R202_E006" target="R202_E007"><data key="edge_relationship_id">R202_REL007</data><data key="edge_source_entity_id">R202_E006</data><data key="edge_relationship_type">operates</data><data key="edge_target_entity_id">R202_E007</data><data key="edge_operational_context">Connecticut DSS EMS is a state-owned eligibility system, not an SSA authoritative repository.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Connecticut DSS EMS is a state-owned eligibility system, not an SSA authoritative repository.</data></edge><edge id="R202_REL008" source="EX_SASRO" target="R202_E009"><data key="edge_relationship_id">R202_REL008</data><data key="edge_source_entity_id">EX_SASRO</data><data key="edge_relationship_type">historically_accesses_state_ems_via</data><data key="edge_target_entity_id">R202_E009</data><data key="edge_operational_context">Connecticut regional SASRO operates through the CTHS SSA Main Menu route.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Connecticut regional SASRO operates through the CTHS SSA Main Menu route.</data></edge><edge id="R202_REL009" source="R202_E009" target="R202_E007"><data key="edge_relationship_id">R202_REL009</data><data key="edge_source_entity_id">R202_E009</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">R202_E007</data><data key="edge_operational_context">Authorized SSA personnel receive inquiry access after state credential authentication.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Authorized SSA personnel receive inquiry access after state credential authentication.</data></edge><edge id="R202_REL010" source="R202_E007" target="R202_E008"><data key="edge_relationship_id">R202_REL010</data><data key="edge_source_entity_id">R202_E007</data><data key="edge_relationship_type">presents_verified_state_unemployment_from</data><data key="edge_target_entity_id">R202_E008</data><data key="edge_operational_context">Under the specific Connecticut agreement, DOL-origin unemployment benefits available through EMS can be accepted as verified.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Under the specific Connecticut agreement, DOL-origin unemployment benefits available through EMS can be accepted as verified.</data></edge><edge id="R202_REL011" source="R202_E010" target="R202_E007"><data key="edge_relationship_id">R202_REL011</data><data key="edge_source_entity_id">R202_E010</data><data key="edge_relationship_type">governs_custodial_vs_collateral_use_of</data><data key="edge_target_entity_id">R202_E007</data><data key="edge_operational_context">SSA staff must document source, screen and access date when using state online evidence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA staff must document source, screen and access date when using state online evidence.</data></edge><edge id="R202_REL012" source="ORG_EMPLOYMENT_NETWORKS" target="R202_E011"><data key="edge_relationship_id">R202_REL012</data><data key="edge_source_entity_id">ORG_EMPLOYMENT_NETWORKS</data><data key="edge_relationship_type">submits_ticket_user_earnings_to</data><data key="edge_target_entity_id">R202_E011</data><data key="edge_operational_context">Employment Network earnings statements reach SSA Ticket Program Manager for administrative posting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Employment Network earnings statements reach SSA Ticket Program Manager for administrative posting.</data></edge><edge id="R202_REL013" source="R202_E011" target="R202_E012"><data key="edge_relationship_id">R202_REL013</data><data key="edge_source_entity_id">R202_E011</data><data key="edge_relationship_type">posts_ticket_wages_into</data><data key="edge_target_entity_id">R202_E012</data><data key="edge_operational_context">TPM contractor receives participant earnings and enters them into iTOPSS; not equivalent to adjudicated earnings.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">TPM contractor receives participant earnings and enters them into iTOPSS; not equivalent to adjudicated earnings.</data></edge><edge id="R202_REL014" source="R202_E012" target="R202_E013"><data key="edge_relationship_id">R202_REL014</data><data key="edge_source_entity_id">R202_E012</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">R202_E013</data><data key="edge_operational_context">iTOPSS holds Ticket participant wage reports from provider submissions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">iTOPSS holds Ticket participant wage reports from provider submissions.</data></edge><edge id="R202_REL015" source="R202_E012" target="R202_E014"><data key="edge_relationship_id">R202_REL015</data><data key="edge_source_entity_id">R202_E012</data><data key="edge_relationship_type">updates_disability_control_file_via</data><data key="edge_target_entity_id">R202_E014</data><data key="edge_operational_context">POMS explicitly states overnight batch updates DCF from iTOPSS.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly states overnight batch updates DCF from iTOPSS.</data></edge><edge id="R202_REL016" source="R202_E014" target="DB_DCF"><data key="edge_relationship_id">R202_REL016</data><data key="edge_source_entity_id">R202_E014</data><data key="edge_relationship_type">posts_participant_wage_data_to</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">iTOPSS overnight batch posts wage information to DCF; FO retains earnings verification responsibilities.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">iTOPSS overnight batch posts wage information to DCF; FO retains earnings verification responsibilities.</data></edge><edge id="R202_REL017" source="UI_CWP" target="R202_E012"><data key="edge_relationship_id">R202_REL017</data><data key="edge_source_entity_id">UI_CWP</data><data key="edge_relationship_type">exposes_ticket_wage_data_from</data><data key="edge_target_entity_id">R202_E012</data><data key="edge_operational_context">EDCS Consolidated Wage Page displays iTOPSS-derived pay-stub information.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">EDCS Consolidated Wage Page displays iTOPSS-derived pay-stub information.</data></edge><edge id="R202_REL018" source="R202_E015" target="R202_E013"><data key="edge_relationship_id">R202_REL018</data><data key="edge_source_entity_id">R202_E015</data><data key="edge_relationship_type">provides_inquiry_access_to</data><data key="edge_target_entity_id">R202_E013</data><data key="edge_operational_context">QERN inquiry is a documented wage information source under SSI evidence ranking.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">QERN inquiry is a documented wage information source under SSI evidence ranking.</data></edge><edge id="R202_REL019" source="R202_E016" target="R202_E013"><data key="edge_relationship_id">R202_REL019</data><data key="edge_source_entity_id">R202_E016</data><data key="edge_relationship_type">governs_provisional_use_of</data><data key="edge_target_entity_id">R202_E013</data><data key="edge_operational_context">Worker agreement and documentation required before using third-party iTOPSS wage information as SSI evidence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Worker agreement and documentation required before using third-party iTOPSS wage information as SSI evidence.</data></edge><edge id="R202_REL020" source="TECH_IDMS" target="R202_E012"><data key="edge_relationship_id">R202_REL020</data><data key="edge_source_entity_id">TECH_IDMS</data><data key="edge_relationship_type">included_itopss_subsystem</data><data key="edge_target_entity_id">R202_E012</data><data key="edge_operational_context">2017 SSA PIA names ITOPSS as a component of IDMS; historical grouping, not proof of same current security boundary.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">2017 SSA PIA names ITOPSS as a component of IDMS; historical grouping, not proof of same current security boundary.</data></edge><edge id="R202_REL021" source="R202_E012" target="R202_E015"><data key="edge_relationship_id">R202_REL021</data><data key="edge_source_entity_id">R202_E012</data><data key="edge_relationship_type">supports_wage_view_through</data><data key="edge_target_entity_id">R202_E015</data><data key="edge_operational_context">iTOPSS wage reports are accessible in QERN; specific interface protocol not publicly established.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">iTOPSS wage reports are accessible in QERN; specific interface protocol not publicly established.</data></edge><edge id="R202_REL022" source="FORM_IRS4029" target="R202_E017"><data key="edge_relationship_id">R202_REL022</data><data key="edge_source_entity_id">FORM_IRS4029</data><data key="edge_relationship_type">is_scanned_to</data><data key="edge_target_entity_id">R202_E017</data><data key="edge_operational_context">SSA Religious Exemption Unit scans original processed IRS Form 4029 into GIR after IRS response.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA Religious Exemption Unit scans original processed IRS Form 4029 into GIR after IRS response.</data></edge><edge id="R202_REL023" source="FORM_IRS4361" target="R202_E017"><data key="edge_relationship_id">R202_REL023</data><data key="edge_source_entity_id">FORM_IRS4361</data><data key="edge_relationship_type">is_scanned_to</data><data key="edge_target_entity_id">R202_E017</data><data key="edge_operational_context">IRS Form 4361 receipts are scanned to GIR after verification and processing.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">IRS Form 4361 receipts are scanned to GIR after verification and processing.</data></edge><edge id="R202_REL024" source="R202_E017" target="R202_E019"><data key="edge_relationship_id">R202_REL024</data><data key="edge_source_entity_id">R202_E017</data><data key="edge_relationship_type">stores_document_copies_of</data><data key="edge_target_entity_id">R202_E019</data><data key="edge_operational_context">GIR stores electronic copies of historical and recent religious exemption forms 4029/4361.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">GIR stores electronic copies of historical and recent religious exemption forms 4029/4361.</data></edge><edge id="R202_REL025" source="R202_E018" target="SYS_NUMIDENT"><data key="edge_relationship_id">R202_REL025</data><data key="edge_source_entity_id">R202_E018</data><data key="edge_relationship_type">posts_religious_waiver_indicator_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">REU keys ESCORR inputs to apply the Q/FICA marker to Numident from approved Form 4029; specific transaction details not inferred.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">REU keys ESCORR inputs to apply the Q/FICA marker to Numident from approved Form 4029; specific transaction details not inferred.</data></edge><edge id="R202_REL026" source="R202_E020" target="R187_E0034"><data key="edge_relationship_id">R202_REL026</data><data key="edge_source_entity_id">R202_E020</data><data key="edge_relationship_type">marks_processed_form_as_scanned_in</data><data key="edge_target_entity_id">R187_E0034</data><data key="edge_operational_context">Form 4361 workflow records scan status in Religious Exemption database.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Form 4361 workflow records scan status in Religious Exemption database.</data></edge><edge id="R202_REL027" source="R202_E020" target="R202_E017"><data key="edge_relationship_id">R202_REL027</data><data key="edge_source_entity_id">R202_E020</data><data key="edge_relationship_type">records_exemption_in</data><data key="edge_target_entity_id">R202_E017</data><data key="edge_operational_context">Received Form 4361 scanned into GIR and tracked separately from Numident indicators.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Received Form 4361 scanned into GIR and tracked separately from Numident indicators.</data></edge><edge id="R202_REL028" source="APP_MAPS" target="R202_E021"><data key="edge_relationship_id">R202_REL028</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">records_applicant_correspondence_address_subject_to</data><data key="edge_target_entity_id">R202_E021</data><data key="edge_operational_context">The MAPS mailing address serves correspondence; address changes require program-specific master-record procedure rather than automatic MAPS-to-MBR/SSR linkage.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">The MAPS mailing address serves correspondence; address changes require program-specific master-record procedure rather than automatic MAPS-to-MBR/SSR linkage.</data></edge><edge id="R202_REL029" source="R202_E021" target="APP_POS"><data key="edge_relationship_id">R202_REL029</data><data key="edge_source_entity_id">R202_E021</data><data key="edge_relationship_type">routes_title_ii_address_changes_through</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">When timely SSA-1020 change appears, staff apply POS Title II procedures for MBR update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">When timely SSA-1020 change appears, staff apply POS Title II procedures for MBR update.</data></edge><edge id="R202_REL030" source="R202_E021" target="APP_MSSICS"><data key="edge_relationship_id">R202_REL030</data><data key="edge_source_entity_id">R202_E021</data><data key="edge_relationship_type">routes_title_xvi_address_changes_through</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">If SSI claimant Extra Help submission indicates change, staff follow SSI system procedures; does not establish automatic update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">If SSI claimant Extra Help submission indicates change, staff follow SSI system procedures; does not establish automatic update.</data></edge><edge id="R202_REL031" source="R202_E022" target="APP_MAPS"><data key="edge_relationship_id">R202_REL031</data><data key="edge_source_entity_id">R202_E022</data><data key="edge_relationship_type">informs_earnings_development_on</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">OCSE prior wage information helps identify and resolve differences from claimant-alleged reduced wages.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">OCSE prior wage information helps identify and resolve differences from claimant-alleged reduced wages.</data></edge><edge id="R202_REL032" source="REPORT_SSI_ANNUAL_2026" target="R202_E023"><data key="edge_relationship_id">R202_REL032</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">includes_financial_section</data><data key="edge_target_entity_id">R202_E023</data><data key="edge_operational_context">SSI 2026 annual program report includes administrative and beneficiary service cost section IV.E.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSI 2026 annual program report includes administrative and beneficiary service cost section IV.E.</data></edge><edge id="R202_REL033" source="R202_E023" target="R202_E024"><data key="edge_relationship_id">R202_REL033</data><data key="edge_source_entity_id">R202_E023</data><data key="edge_relationship_type">documents_integrated_funding_allocation</data><data key="edge_target_entity_id">R202_E024</data><data key="edge_operational_context">OACT annual publication distinguishes historical expenses from 2026 projections and year-end cost true-up.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">OACT annual publication distinguishes historical expenses from 2026 projections and year-end cost true-up.</data></edge><edge id="R202_REL034" source="R202_E024" target="DATA_OACT_TRUST_FUND_FINANCIAL"><data key="edge_relationship_id">R202_REL034</data><data key="edge_source_entity_id">R202_E024</data><data key="edge_relationship_type">allocates_costs_between</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_operational_context">Trust fund / general fund accounting costs are allocated; does not imply the publication directly drives fund postings.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Trust fund / general fund accounting costs are allocated; does not imply the publication directly drives fund postings.</data></edge><edge id="R202_REL035" source="PORTAL_SSA_OPEN_DATA" target="R202_E025"><data key="edge_relationship_id">R202_REL035</data><data key="edge_source_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R202_E025</data><data key="edge_operational_context">Published CSV distribution and reporting period are directly documented; survey collection system not asserted.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Published CSV distribution and reporting period are directly documented; survey collection system not asserted.</data></edge><edge id="R202_REL036" source="PORTAL_SSA_OPEN_DATA" target="R202_E026"><data key="edge_relationship_id">R202_REL036</data><data key="edge_source_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R202_E026</data><data key="edge_operational_context">Published disability/hearing satisfaction series is a separate CSV with its own temporal coverage.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Published disability/hearing satisfaction series is a separate CSV with its own temporal coverage.</data></edge><edge id="R202_REL037" source="R202_E028" target="R202_E027"><data key="edge_relationship_id">R202_REL037</data><data key="edge_source_entity_id">R202_E028</data><data key="edge_relationship_type">participates_in</data><data key="edge_target_entity_id">R202_E027</data><data key="edge_operational_context">SSA OIG investigative/analyst participation in DOJ fraud coordination; not proof of bulk data sharing or a new SSA enterprise architecture component.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA OIG investigative/analyst participation in DOJ fraud coordination; not proof of bulk data sharing or a new SSA enterprise architecture component.</data></edge><edge id="R202_REL038" source="FORM_SSA827" target="R202_E029"><data key="edge_relationship_id">R202_REL038</data><data key="edge_source_entity_id">FORM_SSA827</data><data key="edge_relationship_type">is_indexed_under</data><data key="edge_target_entity_id">R202_E029</data><data key="edge_operational_context">Pen-and-ink SSA-827 uses barcode document type 1050 for imaging into certified electronic folder.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Pen-and-ink SSA-827 uses barcode document type 1050 for imaging into certified electronic folder.</data></edge><edge id="R202_REL039" source="R202_E029" target="APP_EVIEW"><data key="edge_relationship_id">R202_REL039</data><data key="edge_source_entity_id">R202_E029</data><data key="edge_relationship_type">must_be_verified_visible_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Field office checks scanned SSA-827 readable image in eView before case transfer.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Field office checks scanned SSA-827 readable image in eView before case transfer.</data></edge><edge id="R202_REL040" source="R202_E030" target="APP_EVIEW"><data key="edge_relationship_id">R202_REL040</data><data key="edge_source_entity_id">R202_E030</data><data key="edge_relationship_type">requires_document_imaging_review_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Manual signed paper-form processing requires readable image; electronically signed form automatically files without duplicate scanning.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Manual signed paper-form processing requires readable image; electronically signed form automatically files without duplicate scanning.</data></edge><edge id="R203_R001" source="APP_RASR" target="R203_E001"><data key="edge_relationship_id">R203_R001</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">stores_business_contact_attribute</data><data key="edge_target_entity_id">R203_E001</data><data key="edge_operational_context">SSA GN 03913.010A establishes representative name, business address and affiliations as centrally stored in RASR.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA GN 03913.010A establishes representative name, business address and affiliations as centrally stored in RASR.</data></edge><edge id="R203_R002" source="SYS_NUMIDENT" target="R203_E002"><data key="edge_relationship_id">R203_R002</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">must_be_updated_before</data><data key="edge_target_entity_id">R203_E002</data><data key="edge_operational_context">POMS GN 03913.010D: Numident updated first, followed by SSA-1699 registration form.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">POMS GN 03913.010D: Numident updated first, followed by SSA-1699 registration form.</data></edge><edge id="R203_R003" source="R203_E002" target="APP_RASR"><data key="edge_relationship_id">R203_R003</data><data key="edge_source_entity_id">R203_E002</data><data key="edge_relationship_type">controls_change_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">DEBS updates RASR after a representative files a new SSA-1699; source does not establish automatic Numident push.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">DEBS updates RASR after a representative files a new SSA-1699; source does not establish automatic Numident push.</data></edge><edge id="R203_R004" source="FORM_R96_SSA1699" target="R203_E002"><data key="edge_relationship_id">R203_R004</data><data key="edge_source_entity_id">FORM_R96_SSA1699</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R203_E002</data><data key="edge_operational_context">SSA-1699 refiled after a Numident name change to update representative registration.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-1699 refiled after a Numident name change to update representative registration.</data></edge><edge id="R203_R005" source="APP_RASR" target="R203_E003"><data key="edge_relationship_id">R203_R005</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">conditionally_updates</data><data key="edge_target_entity_id">R203_E003</data><data key="edge_operational_context">GN 03913.010C.2 documents RASR automatic pending-claim affiliation update after DEBS processing.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">GN 03913.010C.2 documents RASR automatic pending-claim affiliation update after DEBS processing.</data></edge><edge id="R203_R006" source="APP_RASR" target="R203_E004"><data key="edge_relationship_id">R203_R006</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">applies_affiliation_control</data><data key="edge_target_entity_id">R203_E004</data><data key="edge_operational_context">GN 03913.010C.1: changed EIN treated as new affiliation; manual claim form is required.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">GN 03913.010C.1: changed EIN treated as new affiliation; manual claim form is required.</data></edge><edge id="R203_R007" source="R203_E005" target="APP_RASR"><data key="edge_relationship_id">R203_R007</data><data key="edge_source_entity_id">R203_E005</data><data key="edge_relationship_type">updates_registration_through</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">SSA GN 03913.010F: executor information updated in deceased representative RASR record; not a new representative appointment.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SSA GN 03913.010F: executor information updated in deceased representative RASR record; not a new representative appointment.</data></edge><edge id="R203_R008" source="APP_RASR" target="R203_E006"><data key="edge_relationship_id">R203_R008</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">determines_fee_reporting_context</data><data key="edge_target_entity_id">R203_E006</data><data key="edge_operational_context">GN 03913.010E differentiates individual/entity 1099 categories and narrowly permitted corrections.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">GN 03913.010E differentiates individual/entity 1099 categories and narrowly permitted corrections.</data></edge><edge id="R203_R009" source="APP_ERPS" target="R113_E015"><data key="edge_relationship_id">R203_R009</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">is_reconciled_against</data><data key="edge_target_entity_id">R113_E015</data><data key="edge_operational_context">POMS GN 00504.101B.2 requires comparing eRPS list to payee-supplied list.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">POMS GN 00504.101B.2 requires comparing eRPS list to payee-supplied list.</data></edge><edge id="R203_R010" source="R203_E007" target="APP_ERPS"><data key="edge_relationship_id">R203_R010</data><data key="edge_source_entity_id">R203_E007</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">GN 00504.101B.9 states terminating in eRPS is insufficient for current MBR/SSR payee; separate field office action required.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">GN 00504.101B.9 states terminating in eRPS is insufficient for current MBR/SSR payee; separate field office action required.</data></edge><edge id="R203_R011" source="R203_E007" target="SYS_MBR"><data key="edge_relationship_id">R203_R011</data><data key="edge_source_entity_id">R203_E007</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">GN 00504.101B.9 states terminating in eRPS is insufficient for current MBR/SSR payee; separate field office action required.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">GN 00504.101B.9 states terminating in eRPS is insufficient for current MBR/SSR payee; separate field office action required.</data></edge><edge id="R203_R012" source="R203_E007" target="SYS_SSR"><data key="edge_relationship_id">R203_R012</data><data key="edge_source_entity_id">R203_E007</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">GN 00504.101B.9 states terminating in eRPS is insufficient for current MBR/SSR payee; separate field office action required.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">GN 00504.101B.9 states terminating in eRPS is insufficient for current MBR/SSR payee; separate field office action required.</data></edge><edge id="R203_R013" source="SYS_MBR" target="R203_E008"><data key="edge_relationship_id">R203_R013</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">has_missing_ssi_disposition_exchange_to</data><data key="edge_target_entity_id">R203_E008</data><data key="edge_operational_context">MBR/SSR interface does not send Title XVI debt-disposition record; distinct from supported SSR-to-ROAR exchange.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">MBR/SSR interface does not send Title XVI debt-disposition record; distinct from supported SSR-to-ROAR exchange.</data></edge><edge id="R203_R014" source="R203_E008" target="SYS_SSR"><data key="edge_relationship_id">R203_R014</data><data key="edge_source_entity_id">R203_E008</data><data key="edge_relationship_type">affects</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The missing disposition is a specifically documented MBR-to-SSR cross-program recovery transaction.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">The missing disposition is a specifically documented MBR-to-SSR cross-program recovery transaction.</data></edge><edge id="R203_R015" source="SYS_MBR" target="R203_E009"><data key="edge_relationship_id">R203_R015</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R203_E009</data><data key="edge_operational_context">SI 02220.020E.1: MBR generates PC alert when benefits defer, terminate, or suspend during CPR.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SI 02220.020E.1: MBR generates PC alert when benefits defer, terminate, or suspend during CPR.</data></edge><edge id="R203_R016" source="SYS_SSR" target="R203_E010"><data key="edge_relationship_id">R203_R016</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">may_generate</data><data key="edge_target_entity_id">R203_E010</data><data key="edge_operational_context">SI 02220.020E.3 describes B8 diary control for return to SSI C01 current payment during CPR.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SI 02220.020E.3 describes B8 diary control for return to SSI C01 current payment during CPR.</data></edge><edge id="R203_R017" source="UI_DMS_DROA" target="R203_E011"><data key="edge_relationship_id">R203_R017</data><data key="edge_source_entity_id">UI_DMS_DROA</data><data key="edge_relationship_type">supports_manual_adjustment_in</data><data key="edge_target_entity_id">R203_E011</data><data key="edge_operational_context">SI 02220.020E.2 directs DMS DROA for withholding rate changes; K TAC may not agree.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">SI 02220.020E.2 directs DMS DROA for withholding rate changes; K TAC may not agree.</data></edge><edge id="R203_R018" source="R203_E011" target="APP_ROAR"><data key="edge_relationship_id">R203_R018</data><data key="edge_source_entity_id">R203_E011</data><data key="edge_relationship_type">requires_rate_confirmation_in</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">ROAR must be queried for actual withholding rate because K TAC can remain inaccurate.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">ROAR must be queried for actual withholding rate because K TAC can remain inaccurate.</data></edge><edge id="R203_R019" source="APP_ERPS" target="R203_E012"><data key="edge_relationship_id">R203_R019</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">supports_exception_workflow_for</data><data key="edge_target_entity_id">R203_E012</data><data key="edge_operational_context">POMS GN 00502.302C.4: foreign payee DPS notice and tickle for criminal-history development.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">POMS GN 00502.302C.4: foreign payee DPS notice and tickle for criminal-history development.</data></edge><edge id="R203_R020" source="PROC_NCP" target="R203_E013"><data key="edge_relationship_id">R203_R020</data><data key="edge_source_entity_id">PROC_NCP</data><data key="edge_relationship_type">requires_origin_evidence_for</data><data key="edge_target_entity_id">R203_E013</data><data key="edge_operational_context">RM 10212.200A.1: EAB keying error corrected using NCP only with partner documentation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">RM 10212.200A.1: EAB keying error corrected using NCP only with partner documentation.</data></edge><edge id="R203_R021" source="R168_E001" target="R203_E014"><data key="edge_relationship_id">R203_R021</data><data key="edge_source_entity_id">R168_E001</data><data key="edge_relationship_type">supplies_indicator_for</data><data key="edge_target_entity_id">R203_E014</data><data key="edge_operational_context">IRM 3.13.5.16: SSA weekly update data appear as NEW SSA N/C on IRS CC INOLES.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">IRM 3.13.5.16: SSA weekly update data appear as NEW SSA N/C on IRS CC INOLES.</data></edge><edge id="R203_R022" source="R203_E014" target="DB_IRS_IMF"><data key="edge_relationship_id">R203_R022</data><data key="edge_source_entity_id">R203_E014</data><data key="edge_relationship_type">supports_temporary_validation_in</data><data key="edge_target_entity_id">DB_IRS_IMF</data><data key="edge_operational_context">Indicator avoids certain invalid-name-control notices/refund delays until quarterly DM-1 merge.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Indicator avoids certain invalid-name-control notices/refund delays until quarterly DM-1 merge.</data></edge><edge id="R203_R023" source="DB_IRS_NAP_DM1" target="R203_E015"><data key="edge_relationship_id">R203_R023</data><data key="edge_source_entity_id">DB_IRS_NAP_DM1</data><data key="edge_relationship_type">performs_quarterly_validation</data><data key="edge_target_entity_id">R203_E015</data><data key="edge_operational_context">IRM 3.13.5.16: DM-1 quarterly merges update IMF valid/invalid taxpayer account processing.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">IRM 3.13.5.16: DM-1 quarterly merges update IMF valid/invalid taxpayer account processing.</data></edge><edge id="R203_R024" source="R203_E015" target="R203_E014"><data key="edge_relationship_id">R203_R024</data><data key="edge_source_entity_id">R203_E015</data><data key="edge_relationship_type">reconciles_indicator</data><data key="edge_target_entity_id">R203_E014</data><data key="edge_operational_context">NEW SSA N/C indicator cleared following successful/unsuccessful DM-1 quarterly validation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">NEW SSA N/C indicator cleared following successful/unsuccessful DM-1 quarterly validation.</data></edge><edge id="R203_R025" source="DB_DCF" target="R203_E016"><data key="edge_relationship_id">R203_R025</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">historically_triggers</data><data key="edge_target_entity_id">R203_E016</data><data key="edge_operational_context">DI 40525.001B.3 (2007): transfer input in DCF triggers MBR resumption.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">DI 40525.001B.3 (2007): transfer input in DCF triggers MBR resumption.</data></edge><edge id="R203_R026" source="R203_E016" target="SYS_MBR"><data key="edge_relationship_id">R203_R026</data><data key="edge_source_entity_id">R203_E016</data><data key="edge_relationship_type">historically_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Historical system-integrated benefit resumption conditional on CDR cooperation; manual exception if automated action fails.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Historical system-integrated benefit resumption conditional on CDR cooperation; manual exception if automated action fails.</data></edge><edge id="R203_R027" source="REPORT_STAT_SUPP_SERIES" target="R203_E017"><data key="edge_relationship_id">R203_R027</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_SERIES</data><data key="edge_relationship_type">documents_product_boundary</data><data key="edge_target_entity_id">R203_E017</data><data key="edge_operational_context">OACT statistical catalog distinguishes tables in the Annual Statistical Supplement from data products published separately; some tables are prepublication.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">OACT statistical catalog distinguishes tables in the Annual Statistical Supplement from data products published separately; some tables are prepublication.</data></edge><edge id="R203_R028" source="R203_E017" target="R203_E018"><data key="edge_relationship_id">R203_R028</data><data key="edge_source_entity_id">R203_E017</data><data key="edge_relationship_type">classifies_publication_of</data><data key="edge_target_entity_id">R203_E018</data><data key="edge_operational_context">OACT statistical index explicitly lists disabled worker beneficiary data with charts under non-Supplement products.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">OACT statistical index explicitly lists disabled worker beneficiary data with charts under non-Supplement products.</data></edge><edge id="R204_R0001" source="R204_E001" target="SYS_MBR"><data key="edge_relationship_id">R204_R0001</data><data key="edge_source_entity_id">R204_E001</data><data key="edge_relationship_type">identifies_affected_cases_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Office of Systems annotates MBR cases selected using addresses in designated disaster-area ZIP codes.</data><data key="edge_observed_as_of">2010-06-14</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0002" source="R204_E001" target="SYS_SSR"><data key="edge_relationship_id">R204_R0002</data><data key="edge_source_entity_id">R204_E001</data><data key="edge_relationship_type">identifies_affected_cases_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Office of Systems annotates affected SSR cases; terminated Title XVI records are excluded from the described CG display.</data><data key="edge_observed_as_of">2010-06-14</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0003" source="R204_E001" target="R204_E002"><data key="edge_relationship_id">R204_R0003</data><data key="edge_source_entity_id">R204_E001</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R204_E002</data><data key="edge_operational_context">MBR special messages identify the affected beneficiary identification codes; later-created MBRs require staff follow-up.</data><data key="edge_observed_as_of">2010-06-14</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0004" source="R204_E001" target="R204_E003"><data key="edge_relationship_id">R204_R0004</data><data key="edge_source_entity_id">R204_E001</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R204_E003</data><data key="edge_operational_context">SSR CG tagging includes an explicit manual remedy for missed displaced recipients.</data><data key="edge_observed_as_of">2010-06-14</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0005" source="R204_E002" target="SYS_MBR"><data key="edge_relationship_id">R204_R0005</data><data key="edge_source_entity_id">R204_E002</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The disaster special message is retained in MBR and must not be deleted or replaced.</data><data key="edge_observed_as_of">2010-06-14</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0006" source="R204_E003" target="SYS_SSR"><data key="edge_relationship_id">R204_R0006</data><data key="edge_source_entity_id">R204_E003</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The disaster CG code is retained in SSR; missed-case addition is a field-office action.</data><data key="edge_observed_as_of">2010-06-14</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0007" source="R204_E004" target="APP_PPC"><data key="edge_relationship_id">R204_R0007</data><data key="edge_source_entity_id">R204_E004</data><data key="edge_relationship_type">stored_in_before_forwarding</data><data key="edge_target_entity_id">APP_PPC</data><data key="edge_operational_context">BET stores the Italian claim packet in DIO PPC before forwarding to Italy.</data><data key="edge_observed_as_of">2022-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0008" source="APP_PPC" target="R204_E005"><data key="edge_relationship_id">R204_R0008</data><data key="edge_source_entity_id">APP_PPC</data><data key="edge_relationship_type">automatically_generates</data><data key="edge_target_entity_id">R204_E005</data><data key="edge_operational_context">The system generates the notice; the BET sends it to the applicant.</data><data key="edge_observed_as_of">2022-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0009" source="APP_EP" target="APP_PPC"><data key="edge_relationship_id">R204_R0009</data><data key="edge_source_entity_id">APP_EP</data><data key="edge_relationship_type">provides_claim_forwarding_status_access_to</data><data key="edge_target_entity_id">APP_PPC</data><data key="edge_operational_context">Field offices can check PPC through Evidence Portal for Italian claim forwarding status.</data><data key="edge_observed_as_of">2022-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0010" source="R204_E006" target="APP_PPC"><data key="edge_relationship_id">R204_R0010</data><data key="edge_source_entity_id">R204_E006</data><data key="edge_relationship_type">limits_status_interpretation_of</data><data key="edge_target_entity_id">APP_PPC</data><data key="edge_operational_context">PPC forwarding information does not establish subsequent Italian adjudication status.</data><data key="edge_observed_as_of">2022-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0011" source="R137_E0007" target="R204_E007"><data key="edge_relationship_id">R204_R0011</data><data key="edge_source_entity_id">R137_E0007</data><data key="edge_relationship_type">awards_procurement_instrument</data><data key="edge_target_entity_id">R204_E007</data><data key="edge_operational_context">Awarding agency code 028 identifies SSA in the reviewed transaction.</data><data key="edge_observed_as_of">2009-02-26</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0012" source="R204_E007" target="ORG_IBM"><data key="edge_relationship_id">R204_R0012</data><data key="edge_source_entity_id">R204_E007</data><data key="edge_relationship_type">names_procurement_recipient</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">The transaction names INTERNATIONAL BUSINESS MACHINE as recipient; UEI VV9KH3L99VE3.</data><data key="edge_observed_as_of">2009-02-26</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0013" source="R137_E0007" target="R204_E008"><data key="edge_relationship_id">R204_R0013</data><data key="edge_source_entity_id">R137_E0007</data><data key="edge_relationship_type">awards_procurement_instrument</data><data key="edge_target_entity_id">R204_E008</data><data key="edge_operational_context">Awarding agency code 028 identifies SSA in the reviewed transaction.</data><data key="edge_observed_as_of">2013-08-19</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0014" source="R204_E008" target="ORG_IBM"><data key="edge_relationship_id">R204_R0014</data><data key="edge_source_entity_id">R204_E008</data><data key="edge_relationship_type">names_procurement_recipient</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">The transaction names INTERNATIONAL BUSINESS MACHINE as recipient; UEI VV9KH3L99VE3.</data><data key="edge_observed_as_of">2013-08-19</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0015" source="R137_E0007" target="R204_E009"><data key="edge_relationship_id">R204_R0015</data><data key="edge_source_entity_id">R137_E0007</data><data key="edge_relationship_type">awards_procurement_instrument</data><data key="edge_target_entity_id">R204_E009</data><data key="edge_operational_context">Awarding agency code 028 identifies SSA in the reviewed transaction.</data><data key="edge_observed_as_of">2014-07-14</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0016" source="R204_E009" target="R204_E012"><data key="edge_relationship_id">R204_R0016</data><data key="edge_source_entity_id">R204_E009</data><data key="edge_relationship_type">names_procurement_recipient</data><data key="edge_target_entity_id">R204_E012</data><data key="edge_operational_context">The transaction names SOLUTIONS ENGINEERING CORP as recipient; UEI LCGCHS5JKU39.</data><data key="edge_observed_as_of">2014-07-14</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0017" source="R204_E009" target="TECH_ABINITIO"><data key="edge_relationship_id">R204_R0017</data><data key="edge_source_entity_id">R204_E009</data><data key="edge_relationship_type">procurement_description_names</data><data key="edge_target_entity_id">TECH_ABINITIO</data><data key="edge_operational_context">The BPA description explicitly names Ab Initio extract, transform and load software, maintenance, consulting, and training. It does not link a specific SSA application to a deployment.</data><data key="edge_observed_as_of">2014-07-14</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0018" source="R137_E0007" target="R204_E010"><data key="edge_relationship_id">R204_R0018</data><data key="edge_source_entity_id">R137_E0007</data><data key="edge_relationship_type">awards_procurement_instrument</data><data key="edge_target_entity_id">R204_E010</data><data key="edge_operational_context">Awarding agency code 028 identifies SSA in the reviewed transaction.</data><data key="edge_observed_as_of">2015-07-16</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0019" source="R204_E010" target="R204_E013"><data key="edge_relationship_id">R204_R0019</data><data key="edge_source_entity_id">R204_E010</data><data key="edge_relationship_type">names_procurement_recipient</data><data key="edge_target_entity_id">R204_E013</data><data key="edge_operational_context">The transaction names NETCON, INC as recipient; UEI MK7CB66VH219.</data><data key="edge_observed_as_of">2015-07-16</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0020" source="R137_E0007" target="R204_E011"><data key="edge_relationship_id">R204_R0020</data><data key="edge_source_entity_id">R137_E0007</data><data key="edge_relationship_type">awards_procurement_instrument</data><data key="edge_target_entity_id">R204_E011</data><data key="edge_operational_context">Awarding agency code 028 identifies SSA in the reviewed transaction.</data><data key="edge_observed_as_of">2008-06-27</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R204_R0021" source="R204_E011" target="R204_E014"><data key="edge_relationship_id">R204_R0021</data><data key="edge_source_entity_id">R204_E011</data><data key="edge_relationship_type">names_procurement_recipient</data><data key="edge_target_entity_id">R204_E014</data><data key="edge_operational_context">The transaction names SPECTRUM SYSTEMS, INC. as recipient; UEI ZRJRWK5KJP36.</data><data key="edge_observed_as_of">2008-06-27</data><data key="edge_confidence">4</data><data key="edge_notes">No inferred deployment, hosting, protocol, or automatic master-record synchronization.</data></edge><edge id="R205_R0001" source="R205_E001" target="APP_EDCS"><data key="edge_relationship_id">R205_R0001</data><data key="edge_source_entity_id">R205_E001</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Post-transfer eCDR contact changes require manual entry.</data><data key="edge_observed_as_of">2019-11-25</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0002" source="R205_E001" target="SYS_MBR"><data key="edge_relationship_id">R205_R0002</data><data key="edge_source_entity_id">R205_E001</data><data key="edge_relationship_type">does_not_repropagate_contact_changes_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">General eCDR post-transfer note expressly excludes MBR repropagation.</data><data key="edge_observed_as_of">2019-11-25</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0003" source="R205_E001" target="SYS_SSR"><data key="edge_relationship_id">R205_R0003</data><data key="edge_source_entity_id">R205_E001</data><data key="edge_relationship_type">does_not_repropagate_contact_changes_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">General eCDR post-transfer note expressly excludes SSR repropagation.</data><data key="edge_observed_as_of">2019-11-25</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0004" source="R205_E002" target="APP_EDCS"><data key="edge_relationship_id">R205_R0004</data><data key="edge_source_entity_id">R205_E002</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Age-18 transferred EDCS record does not update from later MSSICS corrections.</data><data key="edge_observed_as_of">2016-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0005" source="R205_E002" target="FORM_SSA5002"><data key="edge_relationship_id">R205_R0005</data><data key="edge_source_entity_id">R205_E002</data><data key="edge_relationship_type">requires_change_document</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">Age-18 changes require a message and SSA-5002 narrative.</data><data key="edge_observed_as_of">2016-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0006" source="R205_E002" target="UTIL_EDCS_UAT"><data key="edge_relationship_id">R205_R0006</data><data key="edge_source_entity_id">R205_E002</data><data key="edge_relationship_type">excludes_for_scoped_case</data><data key="edge_target_entity_id">UTIL_EDCS_UAT</data><data key="edge_operational_context">Age-18 reminder says UAT is unavailable; preserve scope and differing general eCDR wording.</data><data key="edge_observed_as_of">2016-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0007" source="R205_E003" target="APP_EDCS"><data key="edge_relationship_id">R205_R0007</data><data key="edge_source_entity_id">R205_E003</data><data key="edge_relationship_type">requires_separate_correction_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Correct inaccurate eCDR client information in EDCS.</data><data key="edge_observed_as_of">2019-11-25</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0008" source="R205_E003" target="SYS_MBR"><data key="edge_relationship_id">R205_R0008</data><data key="edge_source_entity_id">R205_E003</data><data key="edge_relationship_type">requires_separate_correction_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Correct the corresponding Title II master record as applicable.</data><data key="edge_observed_as_of">2019-11-25</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0009" source="R205_E003" target="SYS_SSR"><data key="edge_relationship_id">R205_R0009</data><data key="edge_source_entity_id">R205_E003</data><data key="edge_relationship_type">requires_separate_correction_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Correct the corresponding Title XVI master record as applicable.</data><data key="edge_observed_as_of">2019-11-25</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0010" source="R205_E004" target="APP_EDCS"><data key="edge_relationship_id">R205_R0010</data><data key="edge_source_entity_id">R205_E004</data><data key="edge_relationship_type">governs_client_identification_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">With a payee, enter claimant residence in Client Identification.</data><data key="edge_observed_as_of">2019-11-25</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0011" source="R205_E005" target="APP_EDCS"><data key="edge_relationship_id">R205_R0011</data><data key="edge_source_entity_id">R205_E005</data><data key="edge_relationship_type">gates_transfer_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Verify adult SSR TMR before age-18 transfer.</data><data key="edge_observed_as_of">2016-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0012" source="R205_E005" target="SYS_SSR"><data key="edge_relationship_id">R205_R0012</data><data key="edge_source_entity_id">R205_E005</data><data key="edge_relationship_type">depends_on_record_state_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Verify SSR TMR change using next-day SSID.</data><data key="edge_observed_as_of">2016-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0013" source="R205_E005" target="R117_E009"><data key="edge_relationship_id">R205_R0013</data><data key="edge_source_entity_id">R205_E005</data><data key="edge_relationship_type">requires_prior_conversion</data><data key="edge_target_entity_id">R117_E009</data><data key="edge_operational_context">Reuse existing age-18 TMR conversion concept; add explicit EDCS transfer gate.</data><data key="edge_observed_as_of">2016-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0014" source="R205_E006" target="APP_EDCS"><data key="edge_relationship_id">R205_R0014</data><data key="edge_source_entity_id">R205_E006</data><data key="edge_relationship_type">generated_field_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Generated CPD is case-creation date minus 12 months in this scoped workflow.</data><data key="edge_observed_as_of">2016-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0015" source="R205_E007" target="APP_EDCS"><data key="edge_relationship_id">R205_R0015</data><data key="edge_source_entity_id">R205_E007</data><data key="edge_relationship_type">requires_manual_entry_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Capability development yes response is manually entered, then displayed in SSA-3367.</data><data key="edge_observed_as_of">2016-03-02</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0016" source="R205_E008" target="R205_E010"><data key="edge_relationship_id">R205_R0016</data><data key="edge_source_entity_id">R205_E008</data><data key="edge_relationship_type">enforced_at</data><data key="edge_target_entity_id">R205_E010</data><data key="edge_operational_context">Always Mandatory for Transfer edits on Collect Edits cannot be overridden.</data><data key="edge_observed_as_of">2008-01-24</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0017" source="R205_E009" target="R205_E010"><data key="edge_relationship_id">R205_R0017</data><data key="edge_source_entity_id">R205_E009</data><data key="edge_relationship_type">override_control_on</data><data key="edge_target_entity_id">R205_E010</data><data key="edge_operational_context">Supervisory own-PIN override applies only to Mandatory for Transfer edits.</data><data key="edge_observed_as_of">2008-01-24</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0018" source="R205_E010" target="APP_EDCS"><data key="edge_relationship_id">R205_R0018</data><data key="edge_source_entity_id">R205_E010</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Collect Edits identifies incomplete or inconsistent fields for correction.</data><data key="edge_observed_as_of">2008-01-24</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0019" source="R205_E011" target="APP_SSI_DOD_INTERFACE"><data key="edge_relationship_id">R205_R0019</data><data key="edge_source_entity_id">R205_E011</data><data key="edge_relationship_type">constrains_interface</data><data key="edge_target_entity_id">APP_SSI_DOD_INTERFACE</data><data key="edge_operational_context">DoD benefit information is not posted electronically by this interface procedure.</data><data key="edge_observed_as_of">2013-12-16</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0020" source="R205_E011" target="SYS_SSR"><data key="edge_relationship_id">R205_R0020</data><data key="edge_source_entity_id">R205_E011</data><data key="edge_relationship_type">requires_manual_changes_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Employees manually post developed DoD benefit changes to SSR.</data><data key="edge_observed_as_of">2013-12-16</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0021" source="R205_E012" target="APP_SSI_DOD_INTERFACE"><data key="edge_relationship_id">R205_R0021</data><data key="edge_source_entity_id">R205_E012</data><data key="edge_relationship_type">governs_alerts_from</data><data key="edge_target_entity_id">APP_SSI_DOD_INTERFACE</data><data key="edge_operational_context">Matching Type-L income can still generate a no-action alert.</data><data key="edge_observed_as_of">2013-12-16</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R205_R0022" source="R205_E013" target="APP_SSI_DOD_INTERFACE"><data key="edge_relationship_id">R205_R0022</data><data key="edge_source_entity_id">R205_E013</data><data key="edge_relationship_type">routes_alerts_from</data><data key="edge_target_entity_id">APP_SSI_DOD_INTERFACE</data><data key="edge_operational_context">Published historical route uses field printers and a named MISF facility. Acronym alone is insufficient to join to the separate Storage Facility entity.</data><data key="edge_observed_as_of">2013-12-16</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0001" source="R206_E001" target="APP_ICF_T2"><data key="edge_relationship_id">R206_R0001</data><data key="edge_source_entity_id">R206_E001</data><data key="edge_relationship_type">function_of</data><data key="edge_target_entity_id">APP_ICF_T2</data><data key="edge_operational_context">Function 31 is the pre-adjudicate WC/PDB calculation mode.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0002" source="R206_E001" target="SYS_MBR"><data key="edge_relationship_id">R206_R0002</data><data key="edge_source_entity_id">R206_E001</data><data key="edge_relationship_type">does_not_modify</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">A function-31 calculation does not itself change the beneficiary record.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0003" source="R206_E002" target="APP_ICF_T2"><data key="edge_relationship_id">R206_R0003</data><data key="edge_source_entity_id">R206_E002</data><data key="edge_relationship_type">governs_input_from</data><data key="edge_target_entity_id">APP_ICF_T2</data><data key="edge_operational_context">Function 32 passes input data rather than calculation authority.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0004" source="R206_E002" target="APP_T2R"><data key="edge_relationship_id">R206_R0004</data><data key="edge_source_entity_id">R206_E002</data><data key="edge_relationship_type">requires_recomputation_by</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">T2R performs its own offset calculation.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0005" source="R206_E002" target="SYS_MBR"><data key="edge_relationship_id">R206_R0005</data><data key="edge_source_entity_id">R206_E002</data><data key="edge_relationship_type">uses_master_data_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The documented T2R computation uses MBR and unspecified T2 Shared data.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0006" source="R206_E003" target="APP_ICF_T2"><data key="edge_relationship_id">R206_R0006</data><data key="edge_source_entity_id">R206_E003</data><data key="edge_relationship_type">function_of</data><data key="edge_target_entity_id">APP_ICF_T2</data><data key="edge_operational_context">OREO is ICF function 34.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0007" source="R206_E003" target="APP_MACADE"><data key="edge_relationship_id">R206_R0007</data><data key="edge_source_entity_id">R206_E003</data><data key="edge_relationship_type">provides_data_for_staff_action_in</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">BA/BTE propagates completed OREO information into MACADE.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0008" source="R206_E003" target="APP_T2R"><data key="edge_relationship_id">R206_R0008</data><data key="edge_source_entity_id">R206_E003</data><data key="edge_relationship_type">does_not_post_through</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">OREO does not use T2R to post its MBR changes.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0009" source="R206_E004" target="APP_ICF_T2"><data key="edge_relationship_id">R206_R0009</data><data key="edge_source_entity_id">R206_E004</data><data key="edge_relationship_type">constrains_retention_in</data><data key="edge_target_entity_id">APP_ICF_T2</data><data key="edge_operational_context">The documented pre-adjudicate record has a single-record 18-month availability boundary.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0010" source="R206_E005" target="APP_ORS"><data key="edge_relationship_id">R206_R0010</data><data key="edge_source_entity_id">R206_E005</data><data key="edge_relationship_type">stores_datasheets_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Adjudicated datasheets become available in ORS after the documented transmission/propagation trigger.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0011" source="R206_E005" target="APP_T2R"><data key="edge_relationship_id">R206_R0011</data><data key="edge_source_entity_id">R206_E005</data><data key="edge_relationship_type">triggered_by_data_transmission_to</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">T2R transmission is one documented storage trigger.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0012" source="R206_E005" target="APP_MACADE"><data key="edge_relationship_id">R206_R0012</data><data key="edge_source_entity_id">R206_E005</data><data key="edge_relationship_type">triggered_by_data_propagation_to</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">MACADE propagation is the other documented storage trigger.</data><data key="edge_observed_as_of">2017-01-26</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0013" source="R206_E006" target="APP_T2R"><data key="edge_relationship_id">R206_R0013</data><data key="edge_source_entity_id">R206_E006</data><data key="edge_relationship_type">constrains_notice_generation_in</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">WCEP ENB notice data is ignored by T2R.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0014" source="R206_E006" target="R206_E003"><data key="edge_relationship_id">R206_R0014</data><data key="edge_source_entity_id">R206_E006</data><data key="edge_relationship_type">requires_alternative_route</data><data key="edge_target_entity_id">R206_E003</data><data key="edge_operational_context">Policy directs OREO to ensure T2R notice generation/release is avoided.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0015" source="R206_E007" target="R206_E003"><data key="edge_relationship_id">R206_R0015</data><data key="edge_source_entity_id">R206_E007</data><data key="edge_relationship_type">propagates_offset_rates_to</data><data key="edge_target_entity_id">R206_E003</data><data key="edge_operational_context">The e2455 tool supplies calculated offset rates to OREO.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0016" source="R206_E008" target="REPO_NDRED"><data key="edge_relationship_id">R206_R0016</data><data key="edge_source_entity_id">R206_E008</data><data key="edge_relationship_type">requires_document_copy_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Protected-rate datasheet is faxed into NDRed.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0017" source="R206_E008" target="APP_PPC"><data key="edge_relationship_id">R206_R0017</data><data key="edge_source_entity_id">R206_E008</data><data key="edge_relationship_type">requires_pc_copy_in</data><data key="edge_target_entity_id">APP_PPC</data><data key="edge_operational_context">Processing centers additionally scan the datasheet into PPC.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0018" source="R206_E008" target="SYS_MBR"><data key="edge_relationship_id">R206_R0018</data><data key="edge_source_entity_id">R206_E008</data><data key="edge_relationship_type">requires_special_message_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR Special Message identifies protected months and the NDRed datasheet.</data><data key="edge_observed_as_of">2015-11-30</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0019" source="R206_E009" target="DATA_EVIEW_CASE_DATA"><data key="edge_relationship_id">R206_R0019</data><data key="edge_source_entity_id">R206_E009</data><data key="edge_relationship_type">view_semantics_of</data><data key="edge_target_entity_id">DATA_EVIEW_CASE_DATA</data><data key="edge_operational_context">Forms view uses successful-transfer state, distinct from later Case Data updates.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0020" source="R206_E010" target="R201_E027"><data key="edge_relationship_id">R206_R0020</data><data key="edge_source_entity_id">R206_E010</data><data key="edge_relationship_type">governs_use_of</data><data key="edge_target_entity_id">R201_E027</data><data key="edge_operational_context">Latest imaged SSA-831 governs the instructed action where multiple versions exist.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0021" source="R206_E010" target="UI_EVIEW_CASE_DOCUMENTS"><data key="edge_relationship_id">R206_R0021</data><data key="edge_source_entity_id">R206_E010</data><data key="edge_relationship_type">selects_image_from</data><data key="edge_target_entity_id">UI_EVIEW_CASE_DOCUMENTS</data><data key="edge_operational_context">The relevant image is in Section A of Case Documents.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0022" source="R206_E010" target="DATA_EVIEW_CASE_DATA"><data key="edge_relationship_id">R206_R0022</data><data key="edge_source_entity_id">R206_E010</data><data key="edge_relationship_type">distinguishes_formatted_copy_in</data><data key="edge_target_entity_id">DATA_EVIEW_CASE_DATA</data><data key="edge_operational_context">Formatted Case Data is a distinct representation of SSA-831.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0023" source="R206_E011" target="DATA_ROC"><data key="edge_relationship_id">R206_R0023</data><data key="edge_source_entity_id">R206_E011</data><data key="edge_relationship_type">constrains_interpretation_of</data><data key="edge_target_entity_id">DATA_ROC</data><data key="edge_operational_context">A ROC is a whole-record snapshot, not a ready-made field-level diff.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0024" source="R206_E012" target="DATA_ROC"><data key="edge_relationship_id">R206_R0024</data><data key="edge_source_entity_id">R206_E012</data><data key="edge_relationship_type">constrains_retention_of</data><data key="edge_target_entity_id">DATA_ROC</data><data key="edge_operational_context">Associated ROC history is removed when the EDCS case is deleted.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0025" source="R206_E012" target="APP_EDCS"><data key="edge_relationship_id">R206_R0025</data><data key="edge_source_entity_id">R206_E012</data><data key="edge_relationship_type">triggered_by_case_deletion_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Deletion of the EDCS case removes the entire record including ROC.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0026" source="R206_E013" target="APP_EVIEW"><data key="edge_relationship_id">R206_R0026</data><data key="edge_source_entity_id">R206_E013</data><data key="edge_relationship_type">displayed_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Case Information exposes report type and reason for failed IDR propagation.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R206_R0027" source="R206_E013" target="APP_EDCS"><data key="edge_relationship_id">R206_R0027</data><data key="edge_source_entity_id">R206_E013</data><data key="edge_relationship_type">reports_failed_propagation_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">The visible annotation distinguishes an existing Internet report from one successfully imported into EDCS.</data><data key="edge_observed_as_of">2013-01-10</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped published policy; not an independently observed live production flow.</data></edge><edge id="R21_REL001" source="APP_SMACS" target="APP_EPECS"><data key="edge_relationship_id">R21_REL001</data><data key="edge_source_entity_id">APP_SMACS</data><data key="edge_relationship_type">has_subsystem</data><data key="edge_target_entity_id">APP_EPECS</data><data key="edge_operational_context">Subsystem architecture documented by the SMACS PIA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes">Parent SMACS remains in the current PIA catalog; subsystem current implementation is not independently confirmed.</data></edge><edge id="R21_REL002" source="APP_SMACS" target="APP_PIV_CMS"><data key="edge_relationship_id">R21_REL002</data><data key="edge_source_entity_id">APP_SMACS</data><data key="edge_relationship_type">has_subsystem</data><data key="edge_target_entity_id">APP_PIV_CMS</data><data key="edge_operational_context">Subsystem architecture documented by the SMACS PIA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes">Parent SMACS remains in the current PIA catalog; subsystem current implementation is not independently confirmed.</data></edge><edge id="R21_REL003" source="APP_SMACS" target="APP_PACS"><data key="edge_relationship_id">R21_REL003</data><data key="edge_source_entity_id">APP_SMACS</data><data key="edge_relationship_type">has_subsystem</data><data key="edge_target_entity_id">APP_PACS</data><data key="edge_operational_context">Subsystem architecture documented by the SMACS PIA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes">Parent SMACS remains in the current PIA catalog; subsystem current implementation is not independently confirmed.</data></edge><edge id="R21_REL004" source="APP_SMACS" target="APP_SAFE"><data key="edge_relationship_id">R21_REL004</data><data key="edge_source_entity_id">APP_SMACS</data><data key="edge_relationship_type">has_subsystem</data><data key="edge_target_entity_id">APP_SAFE</data><data key="edge_operational_context">Subsystem architecture documented by the SMACS PIA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes">Parent SMACS remains in the current PIA catalog; subsystem current implementation is not independently confirmed.</data></edge><edge id="R21_REL005" source="APP_PACS" target="APP_LSAS"><data key="edge_relationship_id">R21_REL005</data><data key="edge_source_entity_id">APP_PACS</data><data key="edge_relationship_type">implemented_using</data><data key="edge_target_entity_id">APP_LSAS</data><data key="edge_operational_context">PACS documented as implemented across many sites using LSAS.</data><data key="edge_observed_as_of">2013-09-30</data><data key="edge_confidence">4</data><data key="edge_notes">Historical implementation detail; current product/version/coverage unconfirmed.</data></edge><edge id="R21_REL006" source="APP_SAFE" target="APP_AIRS"><data key="edge_relationship_id">R21_REL006</data><data key="edge_source_entity_id">APP_SAFE</data><data key="edge_relationship_type">has_module</data><data key="edge_target_entity_id">APP_AIRS</data><data key="edge_operational_context">SAFE module documented in the SMACS PIA.</data><data key="edge_observed_as_of">2013-09-30</data><data key="edge_confidence">4</data><data key="edge_notes">Current module implementation not independently confirmed.</data></edge><edge id="R21_REL007" source="APP_SAFE" target="APP_CARS_SECURITY"><data key="edge_relationship_id">R21_REL007</data><data key="edge_source_entity_id">APP_SAFE</data><data key="edge_relationship_type">has_module</data><data key="edge_target_entity_id">APP_CARS_SECURITY</data><data key="edge_operational_context">SAFE module documented in the SMACS PIA.</data><data key="edge_observed_as_of">2013-09-30</data><data key="edge_confidence">4</data><data key="edge_notes">Current module implementation not independently confirmed.</data></edge><edge id="R21_REL008" source="APP_SAFE" target="APP_PAM_PHYSICAL"><data key="edge_relationship_id">R21_REL008</data><data key="edge_source_entity_id">APP_SAFE</data><data key="edge_relationship_type">has_module</data><data key="edge_target_entity_id">APP_PAM_PHYSICAL</data><data key="edge_operational_context">SAFE module documented in the SMACS PIA.</data><data key="edge_observed_as_of">2013-09-30</data><data key="edge_confidence">4</data><data key="edge_notes">Current module implementation not independently confirmed.</data></edge><edge id="R21_REL009" source="APP_SAFE" target="APP_PIV_CMS"><data key="edge_relationship_id">R21_REL009</data><data key="edge_source_entity_id">APP_SAFE</data><data key="edge_relationship_type">interfaces_with</data><data key="edge_target_entity_id">APP_PIV_CMS</data><data key="edge_operational_context">SAFE collects individual data indirectly through its interface with the Card Management System.</data><data key="edge_observed_as_of">2013-09-30</data><data key="edge_confidence">5</data><data key="edge_notes">Direct interface explicitly stated in the PIA.</data></edge><edge id="R21_REL010" source="APP_EPECS" target="APP_PIV"><data key="edge_relationship_id">R21_REL010</data><data key="edge_source_entity_id">APP_EPECS</data><data key="edge_relationship_type">supports_credential_lifecycle_for</data><data key="edge_target_entity_id">APP_PIV</data><data key="edge_operational_context">EPECS creates and maintains credential records through the PIV lifecycle and supports identity proofing.</data><data key="edge_observed_as_of">2013-09-30</data><data key="edge_confidence">5</data><data key="edge_notes">Functional relationship; not a claim about current protocol.</data></edge><edge id="R21_REL011" source="APP_PIV_CMS" target="APP_PIV"><data key="edge_relationship_id">R21_REL011</data><data key="edge_source_entity_id">APP_PIV_CMS</data><data key="edge_relationship_type">supports_credential_issuance_for</data><data key="edge_target_entity_id">APP_PIV</data><data key="edge_operational_context">CMS manages PIV credential issuance, production, and PKI.</data><data key="edge_observed_as_of">2013-09-30</data><data key="edge_confidence">5</data><data key="edge_notes">Functional relationship; not a claim about current protocol.</data></edge><edge id="R21_REL012" source="ORG_SSA_OIG" target="APP_TEAMMATE_OIG"><data key="edge_relationship_id">R21_REL012</data><data key="edge_source_entity_id">ORG_SSA_OIG</data><data key="edge_relationship_type">operates_or_sponsors</data><data key="edge_target_entity_id">APP_TEAMMATE_OIG</data><data key="edge_operational_context">OIG system/data modernization capability.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Authority/ownership is explicit in SSA/OIG material.</data></edge><edge id="R21_REL013" source="ORG_SSA_OIG" target="DB_OIG_AUTH_DATA_SOURCE"><data key="edge_relationship_id">R21_REL013</data><data key="edge_source_entity_id">ORG_SSA_OIG</data><data key="edge_relationship_type">operates_or_sponsors</data><data key="edge_target_entity_id">DB_OIG_AUTH_DATA_SOURCE</data><data key="edge_operational_context">OIG system/data modernization capability.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authority/ownership is explicit in SSA/OIG material.</data></edge><edge id="R21_REL014" source="ORG_SSA_OIG" target="PROJ_OIG_ANALYTICS_PLATFORM"><data key="edge_relationship_id">R21_REL014</data><data key="edge_source_entity_id">ORG_SSA_OIG</data><data key="edge_relationship_type">operates_or_sponsors</data><data key="edge_target_entity_id">PROJ_OIG_ANALYTICS_PLATFORM</data><data key="edge_operational_context">OIG system/data modernization capability.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes">Authority/ownership is explicit in SSA/OIG material.</data></edge><edge id="R21_REL015" source="APP_SSBS_PHONE" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R21_REL015</data><data key="edge_source_entity_id">APP_SSBS_PHONE</data><data key="edge_relationship_type">part_of_service</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">Automated telephone tax-statement replacement application operates through the National 800 Number automated telephone service.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Current service availability corroborated by SSA public guidance.</data></edge><edge id="R21_REL016" source="APP_SSBS_PHONE" target="SYS_NUMIDENT"><data key="edge_relationship_id">R21_REL016</data><data key="edge_source_entity_id">APP_SSBS_PHONE</data><data key="edge_relationship_type">authenticates_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">PIA says name, SSN and DOB are matched against the Master Files of SSN Holders and SSN Applications.</data><data key="edge_observed_as_of">2007-07-20</data><data key="edge_confidence">5</data><data key="edge_notes">Mapped to Atlas Numident entity; no retained telephone-input data is claimed.</data></edge><edge id="R21_REL017" source="DB_EDPNA_FEE_1099" target="PROC_REP_FEE_TAX_REPORTING"><data key="edge_relationship_id">R21_REL017</data><data key="edge_source_entity_id">DB_EDPNA_FEE_1099</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_REP_FEE_TAX_REPORTING</data><data key="edge_operational_context">The Attorney/EDPNA file was created to facilitate representative fee information-return reporting.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Function is current; exact present storage implementation unconfirmed.</data></edge><edge id="R21_REL018" source="PROC_REP_FEE_TAX_REPORTING" target="ORG_IRS"><data key="edge_relationship_id">R21_REL018</data><data key="edge_source_entity_id">PROC_REP_FEE_TAX_REPORTING</data><data key="edge_relationship_type">reports_information_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SSA issues Forms 1099-MISC/1099-NEC for qualifying direct representative fee payments under IRS reporting rules.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Business reporting relationship, not an assertion of a particular file-transfer protocol.</data></edge><edge id="R21_REL019" source="APP_OPWIZ" target="TECH_PCOM"><data key="edge_relationship_id">R21_REL019</data><data key="edge_source_entity_id">APP_OPWIZ</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">TECH_PCOM</data><data key="edge_operational_context">POMS locates OPWIZ on the PCOM OQA toolbar.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Current operational access path.</data></edge><edge id="R21_REL020" source="APP_OPWIZ" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R21_REL020</data><data key="edge_source_entity_id">APP_OPWIZ</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">POMS lists OPWIZ as a source used for written Title II overpayment explanations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Decision-support relationship.</data></edge><edge id="R21_REL021" source="IFACE_QROP" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R21_REL021</data><data key="edge_source_entity_id">IFACE_QROP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">POMS lists QROP as an online source FO/TSC staff may use to explain overpayments.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Query-use relationship; underlying data path not inferred.</data></edge><edge id="R21_REL022" source="IFACE_DRPF" target="APP_DMS"><data key="edge_relationship_id">R21_REL022</data><data key="edge_source_entity_id">IFACE_DRPF</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS identifies the protest/stop-recovery screen within Debt Management System workflow.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">UI membership is explicit in policy references.</data></edge><edge id="R21_REL023" source="IFACE_DRPT" target="APP_DMS"><data key="edge_relationship_id">R21_REL023</data><data key="edge_source_entity_id">IFACE_DRPT</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS identifies the protest/stop-recovery screen within Debt Management System workflow.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">UI membership is explicit in policy references.</data></edge><edge id="R21_REL024" source="IFACE_DRPR" target="APP_DMS"><data key="edge_relationship_id">R21_REL024</data><data key="edge_source_entity_id">IFACE_DRPR</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS identifies the protest/stop-recovery screen within Debt Management System workflow.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">UI membership is explicit in policy references.</data></edge><edge id="R21_REL025" source="SYS_MBR" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R21_REL025</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_record_for</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">POMS identifies this record/query as a source for explaining the overpayment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Operational information source; no API inference.</data></edge><edge id="R21_REL026" source="APP_ROAR" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R21_REL026</data><data key="edge_source_entity_id">APP_ROAR</data><data key="edge_relationship_type">provides_record_for</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">POMS identifies this record/query as a source for explaining the overpayment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Operational information source; no API inference.</data></edge><edge id="R21_REL027" source="DB_PHUS" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R21_REL027</data><data key="edge_source_entity_id">DB_PHUS</data><data key="edge_relationship_type">provides_record_for</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">POMS identifies this record/query as a source for explaining the overpayment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Operational information source; no API inference.</data></edge><edge id="R21_REL028" source="APP_ORS" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R21_REL028</data><data key="edge_source_entity_id">APP_ORS</data><data key="edge_relationship_type">provides_notice_history_for</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">POMS directs processing-center staff to check ORS for notices previously sent about the overpayment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Operational lookup relationship.</data></edge><edge id="R21_REL029" source="APP_PAPERLESS_PSC" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R21_REL029</data><data key="edge_source_entity_id">APP_PAPERLESS_PSC</data><data key="edge_relationship_type">provides_documentation_for</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">POMS permits use of documentation in Paperless when preparing the explanation.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Operational document-source relationship.</data></edge><edge id="R21_REL030" source="APP_DMS" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R21_REL030</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">DMS is used to stop recovery, record remarks, and resume collection in the explanation workflow.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Business workflow relationship, not a statement of system-to-system protocol.</data></edge><edge id="R21_REL031" source="CON_CLOUD_CO1_2021" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R21_REL031</data><data key="edge_source_entity_id">CON_CLOUD_CO1_2021</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">OIG Table 1 identifies the call order under Cloud BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Contractual hierarchy only.</data></edge><edge id="R21_REL032" source="CON_CLOUD_CO2_2022" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R21_REL032</data><data key="edge_source_entity_id">CON_CLOUD_CO2_2022</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">OIG Table 1 identifies the call order under Cloud BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Contractual hierarchy only.</data></edge><edge id="R21_REL033" source="CON_CLOUD_CO3_2023" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R21_REL033</data><data key="edge_source_entity_id">CON_CLOUD_CO3_2023</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">OIG Table 1 identifies the call order under Cloud BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Contractual hierarchy only.</data></edge><edge id="R21_REL034" source="CON_CLOUD_CO4_2024" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R21_REL034</data><data key="edge_source_entity_id">CON_CLOUD_CO4_2024</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">OIG Table 1 identifies the call order under Cloud BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Contractual hierarchy only.</data></edge><edge id="R21_REL035" source="CON_CLOUD_CO6_2025" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R21_REL035</data><data key="edge_source_entity_id">CON_CLOUD_CO6_2025</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">OIG Table 1 identifies the call order under Cloud BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Contractual hierarchy only.</data></edge><edge id="R21_REL036" source="CON_CLOUD_CO7_2026" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R21_REL036</data><data key="edge_source_entity_id">CON_CLOUD_CO7_2026</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">OIG Table 1 identifies the call order under Cloud BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Contractual hierarchy only.</data></edge><edge id="R21_REL037" source="CON_CLOUD_CO8_2026" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R21_REL037</data><data key="edge_source_entity_id">CON_CLOUD_CO8_2026</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">OIG Table 1 identifies the call order under Cloud BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Contractual hierarchy only.</data></edge><edge id="R21_REL038" source="CON_CLOUD_CO8_2026" target="TECH_DW_MGMT_PRODUCT_2026"><data key="edge_relationship_id">R21_REL038</data><data key="edge_source_entity_id">CON_CLOUD_CO8_2026</data><data key="edge_relationship_type">procures</data><data key="edge_target_entity_id">TECH_DW_MGMT_PRODUCT_2026</data><data key="edge_operational_context">OIG describes Call Order 8 as procuring a data-warehouse management product that can process and analyze data.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Product name and deployment architecture are not public.</data></edge><edge id="R21_REL039" source="TECH_AWS_CLOUDWATCH" target="ORG_AWS"><data key="edge_relationship_id">R21_REL039</data><data key="edge_source_entity_id">TECH_AWS_CLOUDWATCH</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_AWS</data><data key="edge_operational_context">CloudWatch is an AWS service and OIG reports SSA uses it to monitor resources.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes">No inference about account topology or monitored resource list.</data></edge><edge id="R21_REL040" source="APP_AWS_WLM_ATTEMPT" target="ORG_AWS"><data key="edge_relationship_id">R21_REL040</data><data key="edge_source_entity_id">APP_AWS_WLM_ATTEMPT</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_AWS</data><data key="edge_operational_context">OIG describes the attempted workforce-management solution as AWS functionality used alongside Amazon Connect.</data><data key="edge_observed_as_of">2025-07-31</data><data key="edge_confidence">5</data><data key="edge_notes">Historical attempted solution.</data></edge><edge id="R21_REL041" source="APP_AWS_WLM_ATTEMPT" target="SVC_AMAZON_CONNECT"><data key="edge_relationship_id">R21_REL041</data><data key="edge_source_entity_id">APP_AWS_WLM_ATTEMPT</data><data key="edge_relationship_type">attempted_companion_for</data><data key="edge_target_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_operational_context">SSA attempted the solution when it began using AWS Connect for telephone services.</data><data key="edge_observed_as_of">2025-07-31</data><data key="edge_confidence">5</data><data key="edge_notes">Does not imply a stable production integration.</data></edge><edge id="R21_REL042" source="APP_CONTACT_CENTER_WFM" target="APP_AWS_WLM_ATTEMPT"><data key="edge_relationship_id">R21_REL042</data><data key="edge_source_entity_id">APP_CONTACT_CENTER_WFM</data><data key="edge_relationship_type">replaced</data><data key="edge_target_entity_id">APP_AWS_WLM_ATTEMPT</data><data key="edge_operational_context">OIG reports SSA purchased replacement cloud workforce-management software after the AWS solution failed to meet needs.</data><data key="edge_observed_as_of">2025-07-31</data><data key="edge_confidence">5</data><data key="edge_notes">Replacement product name is not publicly identified.</data></edge><edge id="R21_REL043" source="APP_CONTACT_CENTER_WFM" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R21_REL043</data><data key="edge_source_entity_id">APP_CONTACT_CENTER_WFM</data><data key="edge_relationship_type">procured_under</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">OIG states SSA purchased the replacement workforce-management software using the same cloud BPA.</data><data key="edge_observed_as_of">2025-07-31</data><data key="edge_confidence">5</data><data key="edge_notes">No separate call-order number is identified in the report section.</data></edge><edge id="R21_REL044" source="APP_CONTACT_CENTER_WFM" target="SVC_AMAZON_CONNECT"><data key="edge_relationship_id">R21_REL044</data><data key="edge_source_entity_id">APP_CONTACT_CENTER_WFM</data><data key="edge_relationship_type">supports_operations_for</data><data key="edge_target_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_operational_context">Replacement software supports workforce optimization, scheduling, forecasting, monitoring, and reporting for SSA telephone operations after AWS Connect deployment.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">4</data><data key="edge_notes">Functional coexistence is documented; a direct technical interface/API is not established.</data></edge><edge id="R21_REL045" source="APP_CYBER_RISK_MGMT_TOOL" target="PROC_ENTERPRISE_CYBER_RISK"><data key="edge_relationship_id">R21_REL045</data><data key="edge_source_entity_id">APP_CYBER_RISK_MGMT_TOOL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_ENTERPRISE_CYBER_RISK</data><data key="edge_operational_context">OIG says previously siloed processes were aligned into a centralized Risk Management Tool launched in FY2026.</data><data key="edge_observed_as_of">2026-07-31</data><data key="edge_confidence">5</data><data key="edge_notes">Migration/refinement remained ongoing.</data></edge><edge id="R21_REL046" source="PROJ_NUMIDENT_VERIFY_CONSOLIDATION" target="SYS_NUMIDENT"><data key="edge_relationship_id">R21_REL046</data><data key="edge_source_entity_id">PROJ_NUMIDENT_VERIFY_CONSOLIDATION</data><data key="edge_relationship_type">centers_on_reference_data</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG reports SSA plans to consolidate several systems that verify incoming data against Numident into a centralized platform.</data><data key="edge_observed_as_of">2026-09-03</data><data key="edge_confidence">4</data><data key="edge_notes">Does not identify the systems, interface design, or future platform product.</data></edge><edge id="R21_REL047" source="PROJ_NUMIDENT_VERIFY_CONSOLIDATION" target="DOM_SSNV"><data key="edge_relationship_id">R21_REL047</data><data key="edge_source_entity_id">PROJ_NUMIDENT_VERIFY_CONSOLIDATION</data><data key="edge_relationship_type">modernizes</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Planned consolidation addresses Numident-based SSN/identity verification data matching.</data><data key="edge_observed_as_of">2026-09-03</data><data key="edge_confidence">4</data><data key="edge_notes">Domain-level modernization relationship; no deployed architecture inferred.</data></edge><edge id="R21_REL048" source="PROC_PBX_RFI_2025" target="SVC_AMAZON_CONNECT"><data key="edge_relationship_id">R21_REL048</data><data key="edge_source_entity_id">PROC_PBX_RFI_2025</data><data key="edge_relationship_type">seeks_complement_to</data><data key="edge_target_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_operational_context">RFI sought COTS IP PBX capabilities for field offices because Amazon Connect did not provide all needed back-office functions.</data><data key="edge_observed_as_of">2025-02-26</data><data key="edge_confidence">5</data><data key="edge_notes">Procurement intent only; no award or deployed integration is inferred.</data></edge><edge id="R22_REL001" source="APP_MCS" target="DB_TITLE2_ODS"><data key="edge_relationship_id">R22_REL001</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">feeds_nightly</data><data key="edge_target_entity_id">DB_TITLE2_ODS</data><data key="edge_operational_context">SSA downloads MCS data nightly to the Title II ODS for initial-claims management information.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL002" source="APP_UMS_MCAS" target="DB_SCDD"><data key="edge_relationship_id">R22_REL002</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">supplies_workload_data_to</data><data key="edge_target_entity_id">DB_SCDD</data><data key="edge_operational_context">SCDD is populated by associating SUMS workload data with client demographics.</data><data key="edge_observed_as_of">2026-03-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL003" source="SYS_ICDB" target="DB_SUMS_CLIENT_TABLES"><data key="edge_relationship_id">R22_REL003</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">sources_demographics_for</data><data key="edge_target_entity_id">DB_SUMS_CLIENT_TABLES</data><data key="edge_operational_context">SSA Open Data states demographics in SUMS client tables are sourced by the Integrated Client Database.</data><data key="edge_observed_as_of">2026-03-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL004" source="DB_SUMS_CLIENT_TABLES" target="DB_SCDD"><data key="edge_relationship_id">R22_REL004</data><data key="edge_source_entity_id">DB_SUMS_CLIENT_TABLES</data><data key="edge_relationship_type">feeds_demographics_to</data><data key="edge_target_entity_id">DB_SCDD</data><data key="edge_operational_context">SCDD combines demographics housed in SUMS client tables with SUMS workload data.</data><data key="edge_observed_as_of">2026-03-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL005" source="APP_EMAC" target="PROC_PUBLIC_INQUIRY_CORR"><data key="edge_relationship_id">R22_REL005</data><data key="edge_source_entity_id">APP_EMAC</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_PUBLIC_INQUIRY_CORR</data><data key="edge_operational_context">EMAC tracks, manages, assigns, and processes correspondence through completed response.</data><data key="edge_observed_as_of">2025-07-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL006" source="APP_OPICS" target="PROC_PUBLIC_INQUIRY_CORR"><data key="edge_relationship_id">R22_REL006</data><data key="edge_source_entity_id">APP_OPICS</data><data key="edge_relationship_type">records_timing_for</data><data key="edge_target_entity_id">PROC_PUBLIC_INQUIRY_CORR</data><data key="edge_operational_context">SSA measures inquiry processing time from entry into the OPICS record system to completion.</data><data key="edge_observed_as_of">2025-07-14</data><data key="edge_confidence">4</data><data key="edge_notes">Public source names OPICS but does not disclose architecture or acronym expansion.</data></edge><edge id="R22_REL007" source="DB_REP_DISQUAL_SOR" target="PLAT_SHAREPOINT"><data key="edge_relationship_id">R22_REL007</data><data key="edge_source_entity_id">DB_REP_DISQUAL_SOR</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">PLAT_SHAREPOINT</data><data key="edge_operational_context">SSA states representative-conduct information is maintained in agency repositories such as SharePoint.</data><data key="edge_observed_as_of">2021-04-14</data><data key="edge_confidence">5</data><data key="edge_notes">This establishes repository use for this data only, not enterprise SharePoint topology.</data></edge><edge id="R22_REL008" source="DB_REP_DISQUAL_SOR" target="APP_REP_CONDUCT_CLAIMS"><data key="edge_relationship_id">R22_REL008</data><data key="edge_source_entity_id">DB_REP_DISQUAL_SOR</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">APP_REP_CONDUCT_CLAIMS</data><data key="edge_operational_context">SSA states representative-conduct information is maintained in the Representative Conduct Claims application.</data><data key="edge_observed_as_of">2021-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL009" source="EX_CMA1003_DOL_BLC" target="ORG_DOL"><data key="edge_relationship_id">R22_REL009</data><data key="edge_source_entity_id">EX_CMA1003_DOL_BLC</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_DOL</data><data key="edge_operational_context">Active SSA computer matching program CMA 1003 with ORG_DOL.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL010" source="EX_CMA1004_DOD_RET" target="ORG_DMDC"><data key="edge_relationship_id">R22_REL010</data><data key="edge_source_entity_id">EX_CMA1004_DOD_RET</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_DMDC</data><data key="edge_operational_context">Active SSA computer matching program CMA 1004 with ORG_DMDC.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL011" source="EX_CMA1006_RRB_CHICO" target="ORG_RRB"><data key="edge_relationship_id">R22_REL011</data><data key="edge_source_entity_id">EX_CMA1006_RRB_CHICO</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_RRB</data><data key="edge_operational_context">Active SSA computer matching program CMA 1006 / CHICO with ORG_RRB.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL012" source="EX_CMA1007_RRB_WAGE_BEN" target="ORG_RRB"><data key="edge_relationship_id">R22_REL012</data><data key="edge_source_entity_id">EX_CMA1007_RRB_WAGE_BEN</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_RRB</data><data key="edge_operational_context">Active SSA computer matching program CMA 1007 with ORG_RRB.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL013" source="EX_CMA1010_DHS_NONCIT" target="ORG_DHS"><data key="edge_relationship_id">R22_REL013</data><data key="edge_source_entity_id">EX_CMA1010_DHS_NONCIT</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_DHS</data><data key="edge_operational_context">Active SSA computer matching program CMA 1010 with ORG_DHS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL014" source="EX_CMA1012_CNCS_SSN" target="ORG_CNCS"><data key="edge_relationship_id">R22_REL014</data><data key="edge_source_entity_id">EX_CMA1012_CNCS_SSN</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_CNCS</data><data key="edge_operational_context">Active SSA computer matching program CMA 1012 with ORG_CNCS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL015" source="EX_CMA1015_DOL_BLB" target="ORG_DOL"><data key="edge_relationship_id">R22_REL015</data><data key="edge_source_entity_id">EX_CMA1015_DOL_BLB</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_DOL</data><data key="edge_operational_context">Active SSA computer matching program CMA 1015 with ORG_DOL.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL016" source="EX_CMA1016_IRS_DISFLA" target="ORG_IRS"><data key="edge_relationship_id">R22_REL016</data><data key="edge_source_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Active SSA computer matching program CMA 1016 / DISFLA with ORG_IRS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL017" source="EX_CMA1030_VA_INCOME_DEP" target="ORG_VBA"><data key="edge_relationship_id">R22_REL017</data><data key="edge_source_entity_id">EX_CMA1030_VA_INCOME_DEP</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_VBA</data><data key="edge_operational_context">Active SSA computer matching program CMA 1030 with ORG_VBA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL018" source="EX_CMA1038_BFS_SAVINGS" target="ORG_BFS"><data key="edge_relationship_id">R22_REL018</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Active SSA computer matching program CMA 1038 with ORG_BFS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL019" source="EX_CMA1050_VA_EARNINGS" target="ORG_VBA"><data key="edge_relationship_id">R22_REL019</data><data key="edge_source_entity_id">EX_CMA1050_VA_EARNINGS</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_VBA</data><data key="edge_operational_context">Active SSA computer matching program CMA 1050 with ORG_VBA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL020" source="EX_CMA1051_ED_SSN_CIT" target="ORG_ED"><data key="edge_relationship_id">R22_REL020</data><data key="edge_source_entity_id">EX_CMA1051_ED_SSN_CIT</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_ED</data><data key="edge_operational_context">Active SSA computer matching program CMA 1051 with ORG_ED.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL021" source="EX_CMA1052_VHA_EARNINGS" target="ORG_VHA"><data key="edge_relationship_id">R22_REL021</data><data key="edge_source_entity_id">EX_CMA1052_VHA_EARNINGS</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_VHA</data><data key="edge_operational_context">Active SSA computer matching program CMA 1052 with ORG_VHA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL022" source="EX_CMA1061_HUD_INCOME" target="ORG_HUD"><data key="edge_relationship_id">R22_REL022</data><data key="edge_source_entity_id">EX_CMA1061_HUD_INCOME</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_HUD</data><data key="edge_operational_context">Active SSA computer matching program CMA 1061 with ORG_HUD.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL023" source="EX_CMA1071_OPM_BENEFIT" target="ORG_OPM"><data key="edge_relationship_id">R22_REL023</data><data key="edge_source_entity_id">EX_CMA1071_OPM_BENEFIT</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_OPM</data><data key="edge_operational_context">Active SSA computer matching program CMA 1071 with ORG_OPM.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL024" source="EX_CMA1100_ED_MINE" target="ORG_ED"><data key="edge_relationship_id">R22_REL024</data><data key="edge_source_entity_id">EX_CMA1100_ED_MINE</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_ED</data><data key="edge_operational_context">Active SSA computer matching program CMA 1100 / MINE with ORG_ED.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL025" source="EX_CMA1304_BFS_PARTD" target="ORG_BFS"><data key="edge_relationship_id">R22_REL025</data><data key="edge_source_entity_id">EX_CMA1304_BFS_PARTD</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Active SSA computer matching program CMA 1304 with ORG_BFS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL026" source="EX_CMA1305_IRS_PARTD" target="ORG_IRS"><data key="edge_relationship_id">R22_REL026</data><data key="edge_source_entity_id">EX_CMA1305_IRS_PARTD</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Active SSA computer matching program CMA 1305 with ORG_IRS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL027" source="EX_CMA1306_OCSE_PARTD" target="ORG_OCSE"><data key="edge_relationship_id">R22_REL027</data><data key="edge_source_entity_id">EX_CMA1306_OCSE_PARTD</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">Active SSA computer matching program CMA 1306 with ORG_OCSE.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL028" source="EX_CMA1307_OPM_PARTD" target="ORG_OPM"><data key="edge_relationship_id">R22_REL028</data><data key="edge_source_entity_id">EX_CMA1307_OPM_PARTD</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_OPM</data><data key="edge_operational_context">Active SSA computer matching program CMA 1307 with ORG_OPM.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL029" source="EX_CMA1308_RRB_PARTD" target="ORG_RRB"><data key="edge_relationship_id">R22_REL029</data><data key="edge_source_entity_id">EX_CMA1308_RRB_PARTD</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_RRB</data><data key="edge_operational_context">Active SSA computer matching program CMA 1308 with ORG_RRB.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL030" source="EX_CMA1310_IRS_PREMIUM" target="ORG_IRS"><data key="edge_relationship_id">R22_REL030</data><data key="edge_source_entity_id">EX_CMA1310_IRS_PREMIUM</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Active SSA computer matching program CMA 1310 with ORG_IRS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL031" source="EX_CMA1012_CNCS_SSN" target="SYS_NUMIDENT"><data key="edge_relationship_id">R22_REL031</data><data key="edge_source_entity_id">EX_CMA1012_CNCS_SSN</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">CMA 1012 uses SSA Enumeration System records to verify SSN/name/DOB and return recorded citizenship/death indicators.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Atlas links the Enumeration System record source to Numident; the agreement does not name a separate physical verification platform.</data></edge><edge id="R22_REL032" source="EX_CMA1050_VA_EARNINGS" target="SYS_NUMIDENT"><data key="edge_relationship_id">R22_REL032</data><data key="edge_source_entity_id">EX_CMA1050_VA_EARNINGS</data><data key="edge_relationship_type">verifies_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">CMA 1050 verifies VA-provided SSNs using SSA Enumeration System records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL033" source="EX_CMA1050_VA_EARNINGS" target="SYS_MEF"><data key="edge_relationship_id">R22_REL033</data><data key="edge_source_entity_id">EX_CMA1050_VA_EARNINGS</data><data key="edge_relationship_type">discloses_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">CMA 1050 discloses matched earnings data from the Earnings Recording and Self-Employment Income System / Master Earnings File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL034" source="EX_CMA1304_BFS_PARTD" target="DB_MDB"><data key="edge_relationship_id">R22_REL034</data><data key="edge_source_entity_id">EX_CMA1304_BFS_PARTD</data><data key="edge_relationship_type">sends_finder_data_from</data><data key="edge_target_entity_id">DB_MDB</data><data key="edge_operational_context">CMA 1304 states SSA extracts SSNs for the Fiscal Service finder file from the Medicare Database File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R22_REL035" source="EX_CMA1304_BFS_PARTD" target="EXT_BFS_US_SECURITIES_ACCESS"><data key="edge_relationship_id">R22_REL035</data><data key="edge_source_entity_id">EX_CMA1304_BFS_PARTD</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">EXT_BFS_US_SECURITIES_ACCESS</data><data key="edge_operational_context">Fiscal Service matches SSA finder-file SSNs against United States Securities and Access records and returns savings-security ownership data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL001" source="QRY_EARQ_LEGACY" target="TECH_PCOM"><data key="edge_relationship_id">R23_REL001</data><data key="edge_source_entity_id">QRY_EARQ_LEGACY</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">TECH_PCOM</data><data key="edge_operational_context">SSA describes the legacy EARQ system as the PCOM display/application used to develop earnings alerts.</data><data key="edge_observed_as_of">2026-07-14</data><data key="edge_confidence">5</data><data key="edge_notes">Interim instructions explicitly direct continued use of legacy PCOM EARQ.</data></edge><edge id="R23_REL002" source="API_EARQ" target="APP_CCE"><data key="edge_relationship_id">R23_REL002</data><data key="edge_source_entity_id">API_EARQ</data><data key="edge_relationship_type">flags_claims_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">The EARQ API flags CCE retirement claims with earnings alerts that require manual development/resolution.</data><data key="edge_observed_as_of">2026-07-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL003" source="PROC_RIB_STP" target="API_EARQ"><data key="edge_relationship_id">R23_REL003</data><data key="edge_source_entity_id">PROC_RIB_STP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">API_EARQ</data><data key="edge_operational_context">SSA says the new EARQ API was introduced as part of retirement iClaim straight-through processing.</data><data key="edge_observed_as_of">2026-07-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL004" source="PROC_RIB_STP" target="APP_ICLAIM"><data key="edge_relationship_id">R23_REL004</data><data key="edge_source_entity_id">PROC_RIB_STP</data><data key="edge_relationship_type">processes</data><data key="edge_target_entity_id">APP_ICLAIM</data><data key="edge_operational_context">The STP process applies to retirement insurance benefit iClaims; an EARQ makes a claim ineligible for straight-through processing.</data><data key="edge_observed_as_of">2026-07-14</data><data key="edge_confidence">5</data><data key="edge_notes">This is a process relationship, not a claim that all iClaims use STP.</data></edge><edge id="R23_REL005" source="APP_EQS" target="QRY_EARQ_LEGACY"><data key="edge_relationship_id">R23_REL005</data><data key="edge_source_entity_id">APP_EQS</data><data key="edge_relationship_type">modernized_parallel_to</data><data key="edge_target_entity_id">QRY_EARQ_LEGACY</data><data key="edge_operational_context">SSA contrasts the new web EQS with the legacy PCOM EARQ system; interim instructions kept the legacy path in use because their alert logic differed.</data><data key="edge_observed_as_of">2026-07-14</data><data key="edge_confidence">5</data><data key="edge_notes">Do not infer formal retirement/replacement completion.</data></edge><edge id="R23_REL006" source="SYS_SSI_EARN_ALERT" target="SYS_SSR"><data key="edge_relationship_id">R23_REL006</data><data key="edge_source_entity_id">SYS_SSI_EARN_ALERT</data><data key="edge_relationship_type">posts_diaries_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS says wage discrepancies generate field-office alerts and S2 diaries posted to the Supplemental Security Record.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL007" source="SYS_SSI_EARN_ALERT" target="EX_OCSE_SSI_WAGE_ALERT"><data key="edge_relationship_id">R23_REL007</data><data key="edge_source_entity_id">SYS_SSI_EARN_ALERT</data><data key="edge_relationship_type">uses_exchange_output_from</data><data key="edge_target_entity_id">EX_OCSE_SSI_WAGE_ALERT</data><data key="edge_operational_context">The SSI earnings-alert workflow uses the OCSE wage matching operation already represented as the OCSE State Wage Alerts exchange product.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship reflects documented business/data flow, not an asserted API.</data></edge><edge id="R23_REL008" source="UI_NAT_SSI_ALERT" target="SYS_SSI_EARN_ALERT"><data key="edge_relationship_id">R23_REL008</data><data key="edge_source_entity_id">UI_NAT_SSI_ALERT</data><data key="edge_relationship_type">provides_replacement_alerts_for</data><data key="edge_target_entity_id">SYS_SSI_EARN_ALERT</data><data key="edge_operational_context">POMS directs field offices to the National SSI Alert System Page to obtain replacement alerts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL009" source="UI_DSWM" target="SYS_SSR"><data key="edge_relationship_id">R23_REL009</data><data key="edge_source_entity_id">UI_DSWM</data><data key="edge_relationship_type">builds_update_transaction_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says the SSI Claims system DSWM screen is completed to clear the diary and build the transaction to SSR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL010" source="QRY_DEQY" target="SYS_SSI_EARN_ALERT"><data key="edge_relationship_id">R23_REL010</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">supports_resolution_of</data><data key="edge_target_entity_id">SYS_SSI_EARN_ALERT</data><data key="edge_operational_context">POMS requires a DEQY when working S2 wage alerts during March through September and directs comparison of employers/wages against SSI records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Operational support relationship; DEQY is not modeled as the alert engine.</data></edge><edge id="R23_REL011" source="APP_AMP" target="APP_ICLAIM"><data key="edge_relationship_id">R23_REL011</data><data key="edge_source_entity_id">APP_AMP</data><data key="edge_relationship_type">previously_processed</data><data key="edge_target_entity_id">APP_ICLAIM</data><data key="edge_operational_context">Before TAA, Medicare-only internet claims were processed via AMP or routed to technicians through MCS.</data><data key="edge_observed_as_of">2026-01-30</data><data key="edge_confidence">5</data><data key="edge_notes">Specific to Medicare-only iClaims.</data></edge><edge id="R23_REL012" source="PROC_TAA_MEDICARE" target="APP_ICLAIM"><data key="edge_relationship_id">R23_REL012</data><data key="edge_source_entity_id">PROC_TAA_MEDICARE</data><data key="edge_relationship_type">processes</data><data key="edge_target_entity_id">APP_ICLAIM</data><data key="edge_operational_context">TAA identifies standard Medicare-only iClaims and can process qualifying applications to completion.</data><data key="edge_observed_as_of">2026-01-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL013" source="PROC_TAA_MEDICARE" target="APP_CCE"><data key="edge_relationship_id">R23_REL013</data><data key="edge_source_entity_id">PROC_TAA_MEDICARE</data><data key="edge_relationship_type">executes_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Qualifying standard Medicare-only iClaims are processed to completion without technician intervention in CCE.</data><data key="edge_observed_as_of">2026-01-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL014" source="PROC_TAA_MEDICARE" target="SYS_MBR"><data key="edge_relationship_id">R23_REL014</data><data key="edge_source_entity_id">PROC_TAA_MEDICARE</data><data key="edge_relationship_type">establishes</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA states that after TAA adjudicates a standard Medicare-only iClaim to completion, CCE establishes the MBR.</data><data key="edge_observed_as_of">2026-01-30</data><data key="edge_confidence">5</data><data key="edge_notes">Modeled at process level; does not infer direct database connectivity from TAA itself.</data></edge><edge id="R23_REL015" source="PROC_TAA_MEDICARE" target="APP_ORS"><data key="edge_relationship_id">R23_REL015</data><data key="edge_source_entity_id">PROC_TAA_MEDICARE</data><data key="edge_relationship_type">stores_outputs_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">After successful TAA processing, the Notice of Award and a copy of the internet application are stored in ORS.</data><data key="edge_observed_as_of">2026-01-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL016" source="PROC_TAA_MEDICARE" target="APP_MCS"><data key="edge_relationship_id">R23_REL016</data><data key="edge_source_entity_id">PROC_TAA_MEDICARE</data><data key="edge_relationship_type">routes_exceptions_to</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Claims that cannot be processed through TAA/CCE may be routed to technicians and imported into MCS under documented exception paths.</data><data key="edge_observed_as_of">2026-01-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL017" source="APP_WAC" target="PROC_TAA_MEDICARE"><data key="edge_relationship_id">R23_REL017</data><data key="edge_source_entity_id">APP_WAC</data><data key="edge_relationship_type">lists_actionable_work_for</data><data key="edge_target_entity_id">PROC_TAA_MEDICARE</data><data key="edge_operational_context">TAA claims requiring technician action appear in WAC pending/internet-claim locations for assignment and review.</data><data key="edge_observed_as_of">2026-01-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL018" source="QRY_HIQR" target="PROC_TAA_MEDICARE"><data key="edge_relationship_id">R23_REL018</data><data key="edge_source_entity_id">QRY_HIQR</data><data key="edge_relationship_type">verifies_outputs_of</data><data key="edge_target_entity_id">PROC_TAA_MEDICARE</data><data key="edge_operational_context">Technicians may use HIQR to verify Medicare start dates, billing information, and card issuance after TAA processing.</data><data key="edge_observed_as_of">2026-01-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL019" source="APP_DALLAS_APPEALS" target="APP_CCE"><data key="edge_relationship_id">R23_REL019</data><data key="edge_source_entity_id">APP_DALLAS_APPEALS</data><data key="edge_relationship_type">hands_off_payment_continuation_to</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Technicians continue Banana for SSI non-medical PE reconsiderations and then initiate Goldberg-Kelly payment continuation in SSI CCE from the Banana End of Process screen.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL020" source="APP_DALLAS_APPEALS" target="APP_CCE"><data key="edge_relationship_id">R23_REL020</data><data key="edge_source_entity_id">APP_DALLAS_APPEALS</data><data key="edge_relationship_type">establishes_development_tickle_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Banana establishes a tickle on the SSI CCE Development Worksheet to control later removal of Goldberg-Kelly protected payment level.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL021" source="APP_MCS" target="APP_PERSON_INFO"><data key="edge_relationship_id">R23_REL021</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">stores_citizenship_data_in</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Beginning June 27, 2021, citizenship data collected on the MCS CLCZ screen is stored and maintained in Person Information.</data><data key="edge_observed_as_of">2026-09-27</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL022" source="APP_PERSON_INFO" target="DB_T2_SHARED_PERSON"><data key="edge_relationship_id">R23_REL022</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">superseded_citizenship_storage_in</data><data key="edge_target_entity_id">DB_T2_SHARED_PERSON</data><data key="edge_operational_context">SSA moved Title II citizenship storage from T2 Shared to Person Information effective June 27, 2021.</data><data key="edge_observed_as_of">2026-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Scope is citizenship data, not all T2 Shared person data.</data></edge><edge id="R23_REL023" source="APP_PERSON_INFO" target="APP_CCE"><data key="edge_relationship_id">R23_REL023</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">integrated_with</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">SSA described Person Information as fully integrated with SSI claims processing in CCE.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Detail from a 2022 instruction retained through 2026-09-27; post-retention topology not independently revalidated.</data></edge><edge id="R23_REL024" source="APP_PERSON_INFO" target="APP_ERPS"><data key="edge_relationship_id">R23_REL024</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">integrated_with</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">SSA described Person Information as fully integrated with eRPS.</data><data key="edge_observed_as_of">2026-09-27</data><data key="edge_confidence">4</data><data key="edge_notes">Detail from a 2022 instruction retained through 2026-09-27; post-retention topology not independently revalidated.</data></edge><edge id="R23_REL025" source="APP_PERSON_INFO" target="APP_IMAIN"><data key="edge_relationship_id">R23_REL025</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_IMAIN</data><data key="edge_operational_context">SSA instructed technicians to select Person Information from iMain for query/edit work.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL026" source="APP_MACADE" target="APP_PERSON_INFO"><data key="edge_relationship_id">R23_REL026</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">pulls_citizenship_data_from</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">For post-entitlement citizenship updates, a MACADE action pulls information from the PI update to the MBR.</data><data key="edge_observed_as_of">2026-09-27</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R23_REL027" source="APP_POS" target="APP_PERSON_INFO"><data key="edge_relationship_id">R23_REL027</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">pulls_citizenship_data_from</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">For post-entitlement citizenship updates, a POS action pulls information from the PI update to the MBR.</data><data key="edge_observed_as_of">2026-09-27</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R23_REL028" source="APP_RASR" target="APP_MCS"><data key="edge_relationship_id">R23_REL028</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">propagates_representative_data_to</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Current POMS says representative information entered in RASR propagates into MCS for applicable claims.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL029" source="APP_RASR" target="APP_MSSICS"><data key="edge_relationship_id">R23_REL029</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">propagates_representative_data_to</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS says representative information entered in RASR propagates into MSSICS for applicable claims.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL030" source="APP_RASR" target="APP_EDCS"><data key="edge_relationship_id">R23_REL030</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">propagates_representative_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Current POMS says representative information entered in RASR propagates into EDCS for applicable claims.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R23_REL031" source="SVC_E1696" target="APP_RASR"><data key="edge_relationship_id">R23_REL031</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">processed_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Current representative-appointment POMS directs staff to enter/process appointment information in RASR after receipt of the current SSA-1696/e1696.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">This models the appointment-processing path; e1696 submission transport itself is not inferred.</data></edge><edge id="R27_REL001" source="COMP_ERPS_WM" target="APP_ERPS"><data key="edge_relationship_id">R27_REL001</data><data key="edge_source_entity_id">COMP_ERPS_WM</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">POMS identifies Workload Management as an eRPS capability for criminal-information workload handling.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL002" source="PROC_ERPS_CRIMINAL_BG" target="APP_ERPS"><data key="edge_relationship_id">R27_REL002</data><data key="edge_source_entity_id">PROC_ERPS_CRIMINAL_BG</data><data key="edge_relationship_type">implemented_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">POMS identifies the criminal background check as occurring through eRPS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL003" source="PROC_ERPS_CRIMINAL_BG" target="DATA_ERPS_CRIM_WORK"><data key="edge_relationship_id">R27_REL003</data><data key="edge_source_entity_id">PROC_ERPS_CRIMINAL_BG</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_ERPS_CRIM_WORK</data><data key="edge_operational_context">Specified criminal-information issue types can be generated from the eRPS criminal background check.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL004" source="DATA_ERPS_CRIM_WORK" target="COMP_ERPS_WM"><data key="edge_relationship_id">R27_REL004</data><data key="edge_source_entity_id">DATA_ERPS_CRIM_WORK</data><data key="edge_relationship_type">managed_in</data><data key="edge_target_entity_id">COMP_ERPS_WM</data><data key="edge_operational_context">Field offices receive and process the specified criminal-information work issues in eRPS Workload Management.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL005" source="DATA_ERPS_CRIM_WORK" target="APP_WAC"><data key="edge_relationship_id">R27_REL005</data><data key="edge_source_entity_id">DATA_ERPS_CRIM_WORK</data><data key="edge_relationship_type">also_available_in</data><data key="edge_target_entity_id">APP_WAC</data><data key="edge_operational_context">POMS states the criminal-information work issues are also available in WAC.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL006" source="APP_MYRPA" target="DOM_REPPAYEE"><data key="edge_relationship_id">R27_REL006</data><data key="edge_source_entity_id">APP_MYRPA</data><data key="edge_relationship_type">supports_reporting_for</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">Current POMS identifies myRPA as an electronic filing option for representative-payee accounting reports.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL007" source="UI_MCS_DW01" target="APP_MCS"><data key="edge_relationship_id">R27_REL007</data><data key="edge_source_entity_id">UI_MCS_DW01</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS explicitly identifies DW01 as the MCS Development Worksheet screen.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL008" source="UI_MCS_DW01" target="ORG_WSU"><data key="edge_relationship_id">R27_REL008</data><data key="edge_source_entity_id">UI_MCS_DW01</data><data key="edge_relationship_type">identifies_assignment_to</data><data key="edge_target_entity_id">ORG_WSU</data><data key="edge_operational_context">The MCS DW01 screen identifies the assigned WSU in the documented claims workflow.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL009" source="UI_MCS_DW03" target="APP_MCS"><data key="edge_relationship_id">R27_REL009</data><data key="edge_source_entity_id">UI_MCS_DW03</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS identifies DW03 as an MCS screen used in the WSU routing workflow.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Screen purpose is documented; the screen code is not expanded in public policy.</data></edge><edge id="R27_REL010" source="APP_DOORS" target="ORG_WSU"><data key="edge_relationship_id">R27_REL010</data><data key="edge_source_entity_id">APP_DOORS</data><data key="edge_relationship_type">provides_contact_routing_for</data><data key="edge_target_entity_id">ORG_WSU</data><data key="edge_operational_context">POMS directs staff to DOORS for WSU address, telephone, and email information.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL011" source="APP_DOORS" target="APP_PCACS"><data key="edge_relationship_id">R27_REL011</data><data key="edge_source_entity_id">APP_DOORS</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">In documented exception workflows, staff use PCACS and consult DOORS for servicing module contact information.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Workflow co-use only; no direct system-to-system interface is inferred.</data></edge><edge id="R27_REL012" source="QRY_WMHH" target="ORG_WSU"><data key="edge_relationship_id">R27_REL012</data><data key="edge_source_entity_id">QRY_WMHH</data><data key="edge_relationship_type">supports_case_movement_review_for</data><data key="edge_target_entity_id">ORG_WSU</data><data key="edge_operational_context">POMS directs staff to review WMHH for recent case movement when determining routing/jurisdiction.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">No hosting or underlying WMS architecture is inferred.</data></edge><edge id="R27_REL013" source="UI_PEPP" target="APP_POS"><data key="edge_relationship_id">R27_REL013</data><data key="edge_source_entity_id">UI_PEPP</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Current POMS identifies PEPP as the Provisional Payment screen in Title II POS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL014" source="APP_POS" target="PROC_T2_EXR_PROVISIONAL"><data key="edge_relationship_id">R27_REL014</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_T2_EXR_PROVISIONAL</data><data key="edge_operational_context">Current POMS directs staff to begin eligible EXR provisional benefits via POS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL015" source="UI_PEPP" target="PROC_T2_EXR_PROVISIONAL"><data key="edge_relationship_id">R27_REL015</data><data key="edge_source_entity_id">UI_PEPP</data><data key="edge_relationship_type">input_for</data><data key="edge_target_entity_id">PROC_T2_EXR_PROVISIONAL</data><data key="edge_operational_context">Staff enter provisional-payment information on the PEPP screen to initiate the process.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL016" source="PROC_T2_EXR_PROVISIONAL" target="SYS_MBR"><data key="edge_relationship_id">R27_REL016</data><data key="edge_source_entity_id">PROC_T2_EXR_PROVISIONAL</data><data key="edge_relationship_type">updates_or_is_monitored_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS instructs staff to monitor the MBR for the provisional-benefit update after POS input.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Operational outcome is documented; a direct POS-to-MBR technical interface is not asserted.</data></edge><edge id="R27_REL017" source="APP_MYCOA" target="APP_MYSSA"><data key="edge_relationship_id">R27_REL017</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">POMS describes access to myCOA from the Contact link in My Profile within my Social Security.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL018" source="APP_MYCOA" target="APP_T2R"><data key="edge_relationship_id">R27_REL018</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">processed_by</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">POMS states Title II Redesign processes address/telephone inputs from myCOA and POS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL019" source="APP_MYCOA" target="SYS_MBR"><data key="edge_relationship_id">R27_REL019</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">posts_updates_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS states permitted Title II myCOA changes post to the MBR through existing batch processing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL020" source="APP_MYCOA" target="SYS_SSR"><data key="edge_relationship_id">R27_REL020</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">posts_limited_updates_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS states permitted Title XVI/concurrent telephone changes can post to the SSR; Title XVI address changes are not enabled through myCOA.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Scope is deliberately limited to documented telephone-change eligibility.</data></edge><edge id="R27_REL021" source="UI_APWA" target="APP_WEIA"><data key="edge_relationship_id">R27_REL021</data><data key="edge_source_entity_id">UI_APWA</data><data key="edge_relationship_type">access_point_for</data><data key="edge_target_entity_id">APP_WEIA</data><data key="edge_operational_context">POMS identifies the Application Programmatic Wage Authorization page as one access route to WEIA.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL022" source="EX_CMA1005_OPM_CIVIL" target="ORG_OPM"><data key="edge_relationship_id">R27_REL022</data><data key="edge_source_entity_id">EX_CMA1005_OPM_CIVIL</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_OPM</data><data key="edge_operational_context">OPM discloses civil-service pension/payment data to SSA under CMA 1005.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL023" source="EX_CMA1005_OPM_CIVIL" target="DOM_TITLE16"><data key="edge_relationship_id">R27_REL023</data><data key="edge_source_entity_id">EX_CMA1005_OPM_CIVIL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">CMA 1005 supports verification of SSI eligibility/payment information using OPM pension data.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL024" source="EX_CMA1005_OPM_CIVIL" target="DOM_SVB"><data key="edge_relationship_id">R27_REL024</data><data key="edge_source_entity_id">EX_CMA1005_OPM_CIVIL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SVB</data><data key="edge_operational_context">CMA 1005 supports verification of SVB eligibility/payment information using OPM pension data.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL025" source="EX_CMA1045_OPM_EARN" target="ORG_OPM"><data key="edge_relationship_id">R27_REL025</data><data key="edge_source_entity_id">EX_CMA1045_OPM_EARN</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_OPM</data><data key="edge_operational_context">SSA discloses wage and self-employment income to OPM under CMA 1045 for covered earnings-limit determinations.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL026" source="EX_CMA6000_STATE_LEVEL" target="ORG_STATES"><data key="edge_relationship_id">R27_REL026</data><data key="edge_source_entity_id">EX_CMA6000_STATE_LEVEL</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">CMA 6000 is the active state-level model matching program.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL027" source="EX_CMA6003_STATE_AGENCY" target="ORG_STATES"><data key="edge_relationship_id">R27_REL027</data><data key="edge_source_entity_id">EX_CMA6003_STATE_AGENCY</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">CMA 6003 is the active state-agency model matching program.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL028" source="EX_CMA6004_TRIBAL" target="ORG_TRIBAL_ENTITIES"><data key="edge_relationship_id">R27_REL028</data><data key="edge_source_entity_id">EX_CMA6004_TRIBAL</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_TRIBAL_ENTITIES</data><data key="edge_operational_context">CMA 6004 is the active tribal-entity model matching program.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R27_REL029" source="EX_CMA6000_STATE_LEVEL" target="SYS_NUMIDENT"><data key="edge_relationship_id">R27_REL029</data><data key="edge_source_entity_id">EX_CMA6000_STATE_LEVEL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Agreement lists SORN 60-0058, Master Files of SSN Holders and SSN Applications, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure; no physical transport path is inferred.</data></edge><edge id="R27_REL030" source="EX_CMA6000_STATE_LEVEL" target="SYS_MEF"><data key="edge_relationship_id">R27_REL030</data><data key="edge_source_entity_id">EX_CMA6000_STATE_LEVEL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Agreement lists SORN 60-0059, Earnings Recording and Self-Employment Income System, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Atlas maps SORN 60-0059 to the MEF/earnings domain with confidence 4; physical implementation is not inferred.</data></edge><edge id="R27_REL031" source="EX_CMA6000_STATE_LEVEL" target="SYS_MBR"><data key="edge_relationship_id">R27_REL031</data><data key="edge_source_entity_id">EX_CMA6000_STATE_LEVEL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Agreement lists SORN 60-0090, Master Beneficiary Record, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only.</data></edge><edge id="R27_REL032" source="EX_CMA6000_STATE_LEVEL" target="SYS_SSR"><data key="edge_relationship_id">R27_REL032</data><data key="edge_source_entity_id">EX_CMA6000_STATE_LEVEL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Agreement lists SORN 60-0103, Supplemental Security Income Record and Special Veterans Benefits, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only.</data></edge><edge id="R27_REL033" source="EX_CMA6000_STATE_LEVEL" target="APP_PUPS"><data key="edge_relationship_id">R27_REL033</data><data key="edge_source_entity_id">EX_CMA6000_STATE_LEVEL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Agreement lists SORN 60-0269, Prisoner Update Processing System, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only.</data></edge><edge id="R27_REL034" source="EX_CMA6000_STATE_LEVEL" target="DB_MDB"><data key="edge_relationship_id">R27_REL034</data><data key="edge_source_entity_id">EX_CMA6000_STATE_LEVEL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">DB_MDB</data><data key="edge_operational_context">Agreement lists SORN 60-0321, Medicare Database File, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only.</data></edge><edge id="R27_REL035" source="EX_CMA6003_STATE_AGENCY" target="SYS_NUMIDENT"><data key="edge_relationship_id">R27_REL035</data><data key="edge_source_entity_id">EX_CMA6003_STATE_AGENCY</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Agreement lists SORN 60-0058, Master Files of SSN Holders and SSN Applications, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure; no physical transport path is inferred.</data></edge><edge id="R27_REL036" source="EX_CMA6003_STATE_AGENCY" target="SYS_MEF"><data key="edge_relationship_id">R27_REL036</data><data key="edge_source_entity_id">EX_CMA6003_STATE_AGENCY</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Agreement lists SORN 60-0059, Earnings Recording and Self-Employment Income System, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Atlas maps SORN 60-0059 to the MEF/earnings domain with confidence 4; physical implementation is not inferred.</data></edge><edge id="R27_REL037" source="EX_CMA6003_STATE_AGENCY" target="SYS_MBR"><data key="edge_relationship_id">R27_REL037</data><data key="edge_source_entity_id">EX_CMA6003_STATE_AGENCY</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Agreement lists SORN 60-0090, Master Beneficiary Record, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only.</data></edge><edge id="R27_REL038" source="EX_CMA6003_STATE_AGENCY" target="SYS_SSR"><data key="edge_relationship_id">R27_REL038</data><data key="edge_source_entity_id">EX_CMA6003_STATE_AGENCY</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Agreement lists SORN 60-0103, Supplemental Security Income Record and Special Veterans Benefits, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only.</data></edge><edge id="R27_REL039" source="EX_CMA6003_STATE_AGENCY" target="APP_PUPS"><data key="edge_relationship_id">R27_REL039</data><data key="edge_source_entity_id">EX_CMA6003_STATE_AGENCY</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Agreement lists SORN 60-0269, Prisoner Update Processing System, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only.</data></edge><edge id="R27_REL040" source="EX_CMA6003_STATE_AGENCY" target="DB_MDB"><data key="edge_relationship_id">R27_REL040</data><data key="edge_source_entity_id">EX_CMA6003_STATE_AGENCY</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">DB_MDB</data><data key="edge_operational_context">Agreement lists SORN 60-0321, Medicare Database File, among records available for the match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only.</data></edge><edge id="R27_REL041" source="EX_CMA6004_TRIBAL" target="SYS_NUMIDENT"><data key="edge_relationship_id">R27_REL041</data><data key="edge_source_entity_id">EX_CMA6004_TRIBAL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Agreement lists SORN 60-0058.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only; no physical transport path is inferred.</data></edge><edge id="R27_REL042" source="EX_CMA6004_TRIBAL" target="SYS_MBR"><data key="edge_relationship_id">R27_REL042</data><data key="edge_source_entity_id">EX_CMA6004_TRIBAL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Agreement lists SORN 60-0090.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only; no physical transport path is inferred.</data></edge><edge id="R27_REL043" source="EX_CMA6004_TRIBAL" target="SYS_SSR"><data key="edge_relationship_id">R27_REL043</data><data key="edge_source_entity_id">EX_CMA6004_TRIBAL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Agreement lists SORN 60-0103.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only; no physical transport path is inferred.</data></edge><edge id="R27_REL044" source="EX_CMA6004_TRIBAL" target="APP_PUPS"><data key="edge_relationship_id">R27_REL044</data><data key="edge_source_entity_id">EX_CMA6004_TRIBAL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Agreement lists SORN 60-0269.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only; no physical transport path is inferred.</data></edge><edge id="R27_REL045" source="EX_CMA6004_TRIBAL" target="DB_MDB"><data key="edge_relationship_id">R27_REL045</data><data key="edge_source_entity_id">EX_CMA6004_TRIBAL</data><data key="edge_relationship_type">discloses_records_from</data><data key="edge_target_entity_id">DB_MDB</data><data key="edge_operational_context">Agreement lists SORN 60-0321.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical records disclosure only; no physical transport path is inferred.</data></edge><edge id="R28_REL001" source="INT_UPLOAD_DOCS_START" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R28_REL001</data><data key="edge_source_entity_id">INT_UPLOAD_DOCS_START</data><data key="edge_relationship_type">entry_point_for</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms links route representative electronically submittable forms through /eSubmit/upload-documents-ui/start with target and type parameters.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Observed URL-level interface only; no backend API topology inferred.</data></edge><edge id="R28_REL002" source="APP_UPLOAD_DOCUMENTS" target="CAP_UPLOAD_WEBFORM_MODE"><data key="edge_relationship_id">R28_REL002</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">supports_mode</data><data key="edge_target_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="edge_operational_context">EM-25024 and current Forms links distinguish Complete Online webforms from PDF upload.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL003" source="APP_UPLOAD_DOCUMENTS" target="CAP_UPLOAD_EVIDENCE_MODE"><data key="edge_relationship_id">R28_REL003</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">supports_mode</data><data key="edge_target_entity_id">CAP_UPLOAD_EVIDENCE_MODE</data><data key="edge_operational_context">EM-25037 documents customer-initiated submission of selected evidence through Upload Documents.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL004" source="PROC_UPLOAD_CREDENTIAL_STEPUP" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R28_REL004</data><data key="edge_source_entity_id">PROC_UPLOAD_CREDENTIAL_STEPUP</data><data key="edge_relationship_type">implemented_by</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Sensitive forms can require advanced credentials before the customer continues submission in Upload Documents.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL005" source="APP_UPLOAD_DOCUMENTS" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">R28_REL005</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">authenticates_via</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">Customer-initiated access authenticates through Login.gov before returning to Upload Documents.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL006" source="APP_UPLOAD_DOCUMENTS" target="SVC_IDME"><data key="edge_relationship_id">R28_REL006</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">authenticates_via</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">Customer-initiated access authenticates through ID.me before returning to Upload Documents.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL007" source="APP_UPLOAD_DOCUMENTS" target="APP_PERSON_INFO"><data key="edge_relationship_id">R28_REL007</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">uses_routing_data_from</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">SSA routes a successful customer submission to the field office associated with the mailing-address ZIP code in Person Information.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Operational routing dependency; transport between applications is not inferred.</data></edge><edge id="R28_REL008" source="APP_UPLOAD_DOCUMENTS" target="SVC_MYSSA_MESSAGE_CENTER"><data key="edge_relationship_id">R28_REL008</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">sends_receipts_to</data><data key="edge_target_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_operational_context">Customer-initiated submissions automatically generate a receipt in the my Social Security Message Center.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL009" source="SVC_MYSSA_MESSAGE_CENTER" target="APP_MYSSA"><data key="edge_relationship_id">R28_REL009</data><data key="edge_source_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA describes Message Center as a my Social Security feature for customer notices and receipts.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL010" source="SVC_MYSSA_HEARING_NOTICES" target="SVC_MYSSA_MESSAGE_CENTER"><data key="edge_relationship_id">R28_REL010</data><data key="edge_source_entity_id">SVC_MYSSA_HEARING_NOTICES</data><data key="edge_relationship_type">delivered_via</data><data key="edge_target_entity_id">SVC_MYSSA_MESSAGE_CENTER</data><data key="edge_operational_context">SSA says proffer letters and hearing-related notices are available securely in the my Social Security Message Center.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL011" source="SVC_MYSSA_ADJ_FORMS" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R28_REL011</data><data key="edge_source_entity_id">SVC_MYSSA_ADJ_FORMS</data><data key="edge_relationship_type">implemented_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current Forms links for HA-4631, HA-4632, and HA-4633 resolve to the shared Upload Documents /eSubmit entry point.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">This links the existing digital-service capability to its observed public intake application; no downstream hearings-system interface is inferred.</data></edge><edge id="R28_REL012" source="SVC_MYSSA_ADJ_FORMS" target="INT_UPLOAD_DOCS_START"><data key="edge_relationship_id">R28_REL012</data><data key="edge_source_entity_id">SVC_MYSSA_ADJ_FORMS</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">INT_UPLOAD_DOCS_START</data><data key="edge_operational_context">HA-4631/4632/4633 Complete Online links carry target=&lt;form&gt; and type=completeOnline through the shared endpoint.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL013" source="APP_IRPP" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R28_REL013</data><data key="edge_source_entity_id">APP_IRPP</data><data key="edge_relationship_type">launches</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Representative-payee Upload Documents access is available from my Social Security representative-payee services; current SSA-552 links include ref=rpp.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">The public ref=rpp parameter corroborates representative-payee routing; it is not treated as a backend interface specification.</data></edge><edge id="R28_REL014" source="APP_I454" target="APP_MYSSA"><data key="edge_relationship_id">R28_REL014</data><data key="edge_source_entity_id">APP_I454</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">POMS says the i454 link appears on the eligible beneficiary or recipient mySSA landing page.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL015" source="APP_WAC" target="COMP_CDR_DEV_TOOLBOX"><data key="edge_relationship_id">R28_REL015</data><data key="edge_source_entity_id">APP_WAC</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">COMP_CDR_DEV_TOOLBOX</data><data key="edge_operational_context">Field offices initiate the medical CDR in WAC using the CDR Development Toolbox.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL016" source="APP_WAC" target="APP_I454"><data key="edge_relationship_id">R28_REL016</data><data key="edge_source_entity_id">APP_WAC</data><data key="edge_relationship_type">enables_online_cdr_for</data><data key="edge_target_entity_id">APP_I454</data><data key="edge_operational_context">After the FO initiates the CDR in WAC and required DCF state is set, the i454 link can appear for eligible users.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow dependency only; no software call is inferred.</data></edge><edge id="R28_REL017" source="DB_DCF" target="APP_I454"><data key="edge_relationship_id">R28_REL017</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">gates_availability_of</data><data key="edge_target_entity_id">APP_I454</data><data key="edge_operational_context">POMS states the i454 link appears after the CDR is initiated in WAC and the DCF field has been initiated.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical workflow state dependency; no physical interface is asserted.</data></edge><edge id="R28_REL018" source="APP_I454" target="APP_WAC"><data key="edge_relationship_id">R28_REL018</data><data key="edge_source_entity_id">APP_I454</data><data key="edge_relationship_type">generates_submission_alert_in</data><data key="edge_target_entity_id">APP_WAC</data><data key="edge_operational_context">Submitted i454 cases appear with a submission date in the WAC DCF Pending Medical CDR listing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL019" source="APP_I454" target="APP_EDCS"><data key="edge_relationship_id">R28_REL019</data><data key="edge_source_entity_id">APP_I454</data><data key="edge_relationship_type">propagates_submission_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">After the FO establishes the CDR in EDCS and selects the submitted case from WAC, keyed i454 data propagate into EDCS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL020" source="APP_EAUTH827" target="APP_EDCS"><data key="edge_relationship_id">R28_REL020</data><data key="edge_source_entity_id">APP_EAUTH827</data><data key="edge_relationship_type">used_within</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Current POMS directs staff to the SSA-827 eAuthorization screen in EDCS for attestation.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL021" source="APP_EAUTH827" target="APP_EVIEW"><data key="edge_relationship_id">R28_REL021</data><data key="edge_source_entity_id">APP_EAUTH827</data><data key="edge_relationship_type">used_within</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Current POMS directs staff to the SSA-827 eAuthorization screen in eView for attestation.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL022" source="APP_EAUTH827" target="REPO_EF"><data key="edge_relationship_id">R28_REL022</data><data key="edge_source_entity_id">APP_EAUTH827</data><data key="edge_relationship_type">stores_signed_authorization_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Current POMS says the system automatically adds the signed SSA-827 to the electronic folder.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL023" source="APP_UNIFORMS" target="REPO_MDF"><data key="edge_relationship_id">R28_REL023</data><data key="edge_source_entity_id">APP_UNIFORMS</data><data key="edge_relationship_type">paper_fallback_to</data><data key="edge_target_entity_id">REPO_MDF</data><data key="edge_operational_context">When the official disability folder is the paper MDF, POMS directs staff to print the UniForm and file it in that folder.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL024" source="CAP_UPLOAD_EVIDENCE_MODE" target="APP_WORKTRACK"><data key="edge_relationship_id">R28_REL024</data><data key="edge_source_entity_id">CAP_UPLOAD_EVIDENCE_MODE</data><data key="edge_relationship_type">routes_submission_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">EM-25037 says all documents submitted through Upload Documents are received by the field office through WorkTrack.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R28_REL025" source="CAP_UPLOAD_WEBFORM_MODE" target="APP_WORKTRACK"><data key="edge_relationship_id">R28_REL025</data><data key="edge_source_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="edge_relationship_type">routes_submission_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">EM-25024 says documents submitted through Upload Documents, including customer-initiated webforms, come into the field office through WorkTrack.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL001" source="APP_ARS" target="REPO_EF"><data key="edge_relationship_id">R29_REL001</data><data key="edge_source_entity_id">APP_ARS</data><data key="edge_relationship_type">provides_realtime_access_to</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Current ARS lets appointed representatives view and download claimant eFolder documents in real time.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL002" source="APP_ARS" target="REPO_EF"><data key="edge_relationship_id">R29_REL002</data><data key="edge_source_entity_id">APP_ARS</data><data key="edge_relationship_type">uploads_evidence_to</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Current ARS lets appointed representatives upload medical evidence and other documents directly into a claimant eFolder.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL003" source="APP_APPOINTED_REP" target="DB_APPOINTED_REP"><data key="edge_relationship_id">R29_REL003</data><data key="edge_source_entity_id">APP_APPOINTED_REP</data><data key="edge_relationship_type">stores_representative_information_in</data><data key="edge_target_entity_id">DB_APPOINTED_REP</data><data key="edge_operational_context">The 2010 Appointed Representatives PIA says information collected for the project is maintained in the Appointed Representative database.</data><data key="edge_observed_as_of">2010-02-04</data><data key="edge_confidence">4</data><data key="edge_notes">Historical implementation relationship retained with current-boundary caution; no equivalence to RASR is inferred.</data></edge><edge id="R29_REL004" source="SVC_E1693" target="TECH_ADOBE_SIGN"><data key="edge_relationship_id">R29_REL004</data><data key="edge_source_entity_id">SVC_E1693</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_ADOBE_SIGN</data><data key="edge_operational_context">Current e1693 instructions identify adobesign@adobesign.com as the service sending access and completion links.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL005" source="SVC_E1696" target="TECH_ADOBE_SIGN"><data key="edge_relationship_id">R29_REL005</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_ADOBE_SIGN</data><data key="edge_operational_context">Current POMS explicitly refers to the e1696 and e1693 AdobeSign portals.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Technology use is portal-specific; no enterprise contract scope inferred.</data></edge><edge id="R29_REL006" source="SVC_E1693" target="PROC_REP_FEE_AGREEMENT"><data key="edge_relationship_id">R29_REL006</data><data key="edge_source_entity_id">SVC_E1693</data><data key="edge_relationship_type">submits_fee_agreement_for</data><data key="edge_target_entity_id">PROC_REP_FEE_AGREEMENT</data><data key="edge_operational_context">Current SSA representation/POMS pages identify e1693 as the electronic SSA-1693 fee-agreement submission method.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL007" source="SVC_E1693" target="APP_WORKTRACK"><data key="edge_relationship_id">R29_REL007</data><data key="edge_source_entity_id">SVC_E1693</data><data key="edge_relationship_type">historically_routes_submission_image_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">2021 implementation instructions say completed online SSA-1693 images were electronically routed to the claimant local field office online work queue and identify WorkTrack for processing.</data><data key="edge_observed_as_of">2021-11-12</data><data key="edge_confidence">4</data><data key="edge_notes">Historical implementation evidence only; the current downstream route was not independently revalidated in Run 29.</data></edge><edge id="R29_REL008" source="PROC_CPAS" target="APP_RASR"><data key="edge_relationship_id">R29_REL008</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">records_signature_indicator_in</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Current POMS requires staff processing a CPAS-signed SSA-1696 to code the CPAS checkbox in RASR.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL009" source="PROC_CPAS" target="UI_MCS_DW01"><data key="edge_relationship_id">R29_REL009</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">records_issue_on</data><data key="edge_target_entity_id">UI_MCS_DW01</data><data key="edge_operational_context">Current POMS directs staff to add/document the CPAS issue on the MCS DW01 screen for applicable initial-claim forms and when RASR coding was missed.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL010" source="PROC_CPAS" target="APP_CCE"><data key="edge_relationship_id">R29_REL010</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">records_initial_claim_issue_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Current POMS directs field-office staff to add the CPAS issue on the Development Worksheet in CCE SSI for applicable initial claims.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">The specific CCE worksheet implementation is not separately modeled.</data></edge><edge id="R29_REL011" source="PROC_CPAS" target="REPO_EF"><data key="edge_relationship_id">R29_REL011</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">stores_postentitlement_document_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">For applicable post-entitlement CPAS cases, current POMS directs staff to establish an SSA-5002 and store it in the electronic folder associated with the claim.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL012" source="PROC_CPAS" target="APP_EP"><data key="edge_relationship_id">R29_REL012</data><data key="edge_source_entity_id">PROC_CPAS</data><data key="edge_relationship_type">stores_paper_folder_document_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">For paper-folder CPAS cases, current POMS directs staff to store the documentation in Evidence Portal.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL013" source="APP_IAPPEALS" target="FORM_I561"><data key="edge_relationship_id">R29_REL013</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">FORM_I561</data><data key="edge_operational_context">Current POMS lists i561 as the iAppeals Request for Reconsideration component.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL014" source="APP_IAPPEALS" target="FORM_I501"><data key="edge_relationship_id">R29_REL014</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">FORM_I501</data><data key="edge_operational_context">Current POMS lists i501 as the iAppeals Request for Hearing by Administrative Law Judge component.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL015" source="APP_IAPPEALS" target="FORM_I520"><data key="edge_relationship_id">R29_REL015</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">FORM_I520</data><data key="edge_operational_context">Current POMS says i520 is available in iAppeals for Appeals Council review.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL016" source="APP_IAPPEALS" target="APP_IWMI"><data key="edge_relationship_id">R29_REL016</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">queues_requests_in</data><data key="edge_target_entity_id">APP_IWMI</data><data key="edge_operational_context">Current POMS says iAppeals adds submitted appeal requests to the Internet Disability WMI and technicians work them from the WMI listing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL017" source="APP_IAPPEALS" target="APP_MCS"><data key="edge_relationship_id">R29_REL017</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">propagates_title_ii_appeal_data_to</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Current POMS says most i561/i501 information propagates to MCS when technicians import Title II iAppeals requests.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL018" source="APP_IAPPEALS" target="APP_MSSICS"><data key="edge_relationship_id">R29_REL018</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">opens_title_xvi_appeal_event_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Title XVI POMS says an iAppeals submission automatically opens an MSSICS appeal event and most i561/i501 data propagates to MSSICS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Source section has an older revision date but remains effective to Present.</data></edge><edge id="R29_REL019" source="APP_IAPPEALS" target="APP_EDCS"><data key="edge_relationship_id">R29_REL019</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">transfers_appeal_via</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Current Title II and continuing Title XVI POMS instruct technicians to use EDCS to transfer iAppeals requests to DDS or the servicing hearing office.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL020" source="APP_IAPPEALS" target="APP_ORS"><data key="edge_relationship_id">R29_REL020</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">stores_title_ii_request_copy_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Current Title II iAppeals POMS directs staff to mail a copy after loading the appeal request into ORS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL021" source="APP_ICLAIM" target="APP_IAPPT"><data key="edge_relationship_id">R29_REL021</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">launches_after_failed_verification</data><data key="edge_target_entity_id">APP_IAPPT</data><data key="edge_operational_context">Current POMS says iClaim is the only iAppt entry point; after two failed verification checks in one session, eligible claimants are offered appointment scheduling.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL022" source="APP_ICLAIM" target="APP_IAPPT"><data key="edge_relationship_id">R29_REL022</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">propagates_identity_data_to</data><data key="edge_target_entity_id">APP_IAPPT</data><data key="edge_operational_context">Current POMS says claimant SSN, name, date of birth, and sex propagate from iClaim to iAppt.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL023" source="APP_IAPPT" target="APP_ELAS"><data key="edge_relationship_id">R29_REL023</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">transmits_appointment_data_to</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Current POMS says iAppt transmits collected About You data to eLAS and establishes the appointment/protective filing there.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL024" source="APP_ELAS" target="APP_IAPPT"><data key="edge_relationship_id">R29_REL024</data><data key="edge_source_entity_id">APP_ELAS</data><data key="edge_relationship_type">provides_dedicated_appointment_calendar_to</data><data key="edge_target_entity_id">APP_IAPPT</data><data key="edge_operational_context">Current POMS says a fifth eLAS calendar screen is for iAppt use only and supplies available field-office appointments.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R29_REL025" source="APP_IAPPT" target="SYS_ICDB"><data key="edge_relationship_id">R29_REL025</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">isolates_unverified_data_from</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">Current POMS says iAppt-created unverified data remains isolated from CLIENT/ICDB until staff verifies and receipts the UNVER issue.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit data-boundary relationship; does not imply a separate physical staging database.</data></edge><edge id="R29_REL026" source="APP_ICLAIM" target="UI_IMNU"><data key="edge_relationship_id">R29_REL026</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">records_submission_completion_date_on</data><data key="edge_target_entity_id">UI_IMNU</data><data key="edge_operational_context">Current POMS says an electronically signed first-party iClaim submission date is the complete date on the Internet Menu (IMNU).</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL001" source="APP_INFORM" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">R30_REL001</data><data key="edge_source_entity_id">APP_INFORM</data><data key="edge_relationship_type">supports_telephone_form_completion_for</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">Current waiver instructions direct technicians taking an SSA-632-BK by telephone to open Inform and complete the form.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Manual business workflow; no application-to-application API is asserted.</data></edge><edge id="R30_REL002" source="APP_INFORM" target="APP_WORKTRACK"><data key="edge_relationship_id">R30_REL002</data><data key="edge_source_entity_id">APP_INFORM</data><data key="edge_relationship_type">produces_pdf_for_manual_batch_upload_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">Waiver instructions say staff save the completed inForm SSA-632-BK as PDF and upload it into WorkTrack 2.0 using Upload a Batch.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">This is a human-mediated file handoff, not an inferred system interface.</data></edge><edge id="R30_REL003" source="APP_UPLOAD_DOCUMENTS" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">R30_REL003</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">accepts_public_submission_for</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">Current SSA waiver and forms instructions allow SSA-632-BK submission through Upload Documents.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Public digital intake path.</data></edge><edge id="R30_REL004" source="APP_WAIVER_DECISION_TREE" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">R30_REL004</data><data key="edge_source_entity_id">APP_WAIVER_DECISION_TREE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">SSA directs staff to the interactive Waiver Decision Tree for selecting waiver provisions and processing steps.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL005" source="UI_DMS_DRAD" target="APP_DMS"><data key="edge_relationship_id">R30_REL005</data><data key="edge_source_entity_id">UI_DMS_DRAD</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Current POMS identifies DRAD as a DMS Fact/Amount Appeal Disposition screen.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL006" source="UI_DMS_DRAD" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">R30_REL006</data><data key="edge_source_entity_id">UI_DMS_DRAD</data><data key="edge_relationship_type">records_title_ii_disposition_for</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">Current Title II waiver/reconsideration instructions use DRAD to input specified dismissals, approvals and denials.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL007" source="UI_DMS_DMFS" target="APP_DMS"><data key="edge_relationship_id">R30_REL007</data><data key="edge_source_entity_id">UI_DMS_DMFS</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Waiver instructions place the WMS Debt Management Function Selection screen in the DMS jurisdiction-transfer workflow.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">UI association only; physical WMS/DMS architecture is not inferred.</data></edge><edge id="R30_REL008" source="UI_DMS_DMFS" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">R30_REL008</data><data key="edge_source_entity_id">UI_DMS_DMFS</data><data key="edge_relationship_type">routes_jurisdiction_for</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">Current waiver basics instruct FOs to transfer waiver jurisdiction to the processing center using DMFS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL009" source="UI_SSR_UOWV" target="SYS_SSR"><data key="edge_relationship_id">R30_REL009</data><data key="edge_source_entity_id">UI_SSR_UOWV</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS says Title XVI waiver dismissal input is made through UOWV in Direct SSR Update.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL010" source="UI_SSR_UOWV" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">R30_REL010</data><data key="edge_source_entity_id">UI_SSR_UOWV</data><data key="edge_relationship_type">records_title_xvi_disposition_for</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">Current Title XVI waiver procedures use UOWV to record the waiver decision/dismissal.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL011" source="UI_DMS_DRDY" target="APP_DMS"><data key="edge_relationship_id">R30_REL011</data><data key="edge_source_entity_id">UI_DMS_DRDY</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS explicitly calls DRDY the ROAR Diary Processing screen in DMS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL012" source="UI_DMS_DRDY" target="APP_ROAR"><data key="edge_relationship_id">R30_REL012</data><data key="edge_source_entity_id">UI_DMS_DRDY</data><data key="edge_relationship_type">establishes_diary_for</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">POMS directs technicians to establish a 90-day ROAR diary via DRDY in DMS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL013" source="APP_ECOMPS" target="APP_ICF_T16"><data key="edge_relationship_id">R30_REL013</data><data key="edge_source_entity_id">APP_ECOMPS</data><data key="edge_relationship_type">alternative_computation_path_to</data><data key="edge_target_entity_id">APP_ICF_T16</data><data key="edge_operational_context">Current SSI policy directs technicians to use eComps or Interactive Comps for future SSI monthly benefit estimates.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Functional alternative, not a technical integration.</data></edge><edge id="R30_REL014" source="PROC_WAGE_SCOUTING" target="SYS_MEF"><data key="edge_relationship_id">R30_REL014</data><data key="edge_source_entity_id">PROC_WAGE_SCOUTING</data><data key="edge_relationship_type">uses_earnings_context_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Scouting procedures use MEF/DEQY context and employer wage reports to investigate earnings discrepancies.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Business-use relationship only.</data></edge><edge id="R30_REL015" source="PROC_WAGE_SCOUTING" target="SVC_ERQY"><data key="edge_relationship_id">R30_REL015</data><data key="edge_source_entity_id">PROC_WAGE_SCOUTING</data><data key="edge_relationship_type">used_to_resolve_alerts_from</data><data key="edge_target_entity_id">SVC_ERQY</data><data key="edge_operational_context">Current POMS instructs staff to request Wage Scouting (EWSR) when certain EARQ/ERQY duplicate-posting alerts require development.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL016" source="ARCH_SUMS" target="DB_SUMS_ENUM_ODS"><data key="edge_relationship_id">R30_REL016</data><data key="edge_source_entity_id">ARCH_SUMS</data><data key="edge_relationship_type">has_data_store</data><data key="edge_target_entity_id">DB_SUMS_ENUM_ODS</data><data key="edge_operational_context">SSA Open Data explicitly identifies a SUMS Enumeration Operational Data Store used for enumeration processing-time reporting.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Name and source support SUMS membership; no lower-level physical topology inferred.</data></edge><edge id="R30_REL017" source="DB_SUMS_ENUM_ODS" target="DOM_ENUMERATION"><data key="edge_relationship_id">R30_REL017</data><data key="edge_source_entity_id">DB_SUMS_ENUM_ODS</data><data key="edge_relationship_type">provides_management_reporting_for</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">SSA extracts enumeration processing-time data from the SUMS Enumeration ODS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL018" source="ARCH_SUMS" target="DB_SUMS_COUNTS_DW"><data key="edge_relationship_id">R30_REL018</data><data key="edge_source_entity_id">ARCH_SUMS</data><data key="edge_relationship_type">has_data_warehouse</data><data key="edge_target_entity_id">DB_SUMS_COUNTS_DW</data><data key="edge_operational_context">Current SSA Open Data names the Social Security Unified Measurement System (SUMS) Counts Data Warehouse.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL019" source="DB_MEDICARE_ODS" target="DB_SUMS_COUNTS_DW"><data key="edge_relationship_id">R30_REL019</data><data key="edge_source_entity_id">DB_MEDICARE_ODS</data><data key="edge_relationship_type">feeds_daily_workload_data_to</data><data key="edge_target_entity_id">DB_SUMS_COUNTS_DW</data><data key="edge_operational_context">SSA says the Extra Help dataset source warehouse is updated daily with current SUMS workload data from the Medicare Operational Data Store.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL020" source="DB_SUMS_COUNTS_DW" target="PROC_EXTRA_HELP"><data key="edge_relationship_id">R30_REL020</data><data key="edge_source_entity_id">DB_SUMS_COUNTS_DW</data><data key="edge_relationship_type">provides_reporting_data_for</data><data key="edge_target_entity_id">PROC_EXTRA_HELP</data><data key="edge_operational_context">SSA identifies SUMS Counts Data Warehouse as the source for its public Extra Help decisions dataset.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL021" source="DB_MEDICARE_ODS" target="PROC_EXTRA_HELP"><data key="edge_relationship_id">R30_REL021</data><data key="edge_source_entity_id">DB_MEDICARE_ODS</data><data key="edge_relationship_type">provides_workload_data_for</data><data key="edge_target_entity_id">PROC_EXTRA_HELP</data><data key="edge_operational_context">The current Extra Help dataset documentation says Medicare ODS supplies the workload data used to update the source warehouse.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Reporting relationship only; no MAPS/i1020 physical interface inferred.</data></edge><edge id="R30_REL022" source="QRY_HEAR" target="APP_EVIEW"><data key="edge_relationship_id">R30_REL022</data><data key="edge_source_entity_id">QRY_HEAR</data><data key="edge_relationship_type">accessed_within</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Post-CPMS instructions locate the HEAR query in the Queries link on eView Case Documents.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL023" source="QRY_HEAR" target="APP_CPMS"><data key="edge_relationship_id">R30_REL023</data><data key="edge_source_entity_id">QRY_HEAR</data><data key="edge_relationship_type">used_as_post_retirement_status_lookup_for</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">After CPMS retirement, SSA directs field staff to HEAR for medical hearing status information.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Replacement of a lookup function, not a database migration claim.</data></edge><edge id="R30_REL024" source="APP_WEBALJ" target="APP_CPMS"><data key="edge_relationship_id">R30_REL024</data><data key="edge_source_entity_id">APP_WEBALJ</data><data key="edge_relationship_type">new_case_feed_depended_on</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">SSA says WebALJ cannot receive new cases until it can successfully pull data without CPMS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Historical/broken dependency documented by the retirement EM.</data></edge><edge id="R30_REL025" source="APP_EDCS" target="APP_WEBALJ"><data key="edge_relationship_id">R30_REL025</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">provides_post_cpms_workaround_for</data><data key="edge_target_entity_id">APP_WEBALJ</data><data key="edge_operational_context">After WebALJ stopped receiving new cases, SSA told staff to identify SSI ALJ reversals from EDCS action-item listings.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL026" source="APP_WAC" target="APP_WEBALJ"><data key="edge_relationship_id">R30_REL026</data><data key="edge_source_entity_id">APP_WAC</data><data key="edge_relationship_type">provides_post_cpms_workaround_for</data><data key="edge_target_entity_id">APP_WEBALJ</data><data key="edge_operational_context">The same SSI ALJ-reversal workaround can be found through WAC action-item listings.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL027" source="APP_ARPS" target="APP_CPMS"><data key="edge_relationship_id">R30_REL027</data><data key="edge_source_entity_id">APP_ARPS</data><data key="edge_relationship_type">provides_post_cpms_status_lookup_for</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Post-retirement instructions direct staff to ARPS for Appeals Council and Federal Court pending/closed case status.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL028" source="APP_ENM" target="APP_CPMS"><data key="edge_relationship_id">R30_REL028</data><data key="edge_source_entity_id">APP_ENM</data><data key="edge_relationship_type">provides_post_cpms_nonmedical_lookup_for</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Post-retirement instructions direct staff to ENM queries for non-medical hearing information.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL029" source="APP_EVIEW" target="APP_CPMS"><data key="edge_relationship_id">R30_REL029</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">provides_post_cpms_decision_lookup_for</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Post-retirement instructions direct staff to eView Case Data for medical decision data at all appeal levels.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL030" source="APP_EP" target="APP_CPMS"><data key="edge_relationship_id">R30_REL030</data><data key="edge_source_entity_id">APP_EP</data><data key="edge_relationship_type">stores_post_cpms_nonmedical_decisions_for</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Post-retirement instructions state Appeals Council and Court non-medical decision documentation will be stored in Evidence Portal.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Functional replacement relationship only.</data></edge><edge id="R30_REL031" source="EX_EAE" target="DATA_ENUM_FEEDBACK_EM"><data key="edge_relationship_id">R30_REL031</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">generates_exception_message</data><data key="edge_target_entity_id">DATA_ENUM_FEEDBACK_EM</data><data key="edge_operational_context">EAE records with certain exceptions receive an Enumeration Feedback Message and Investigate status.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL032" source="DATA_ENUM_FEEDBACK_EM" target="APP_SSNAP"><data key="edge_relationship_id">R30_REL032</data><data key="edge_source_entity_id">DATA_ENUM_FEEDBACK_EM</data><data key="edge_relationship_type">associated_with_pending_application_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">EAE exception records remain pending and are worked through SSNAP.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL033" source="DATA_ENUM_FEEDBACK_EM" target="REPORT_ENUM_MI_LISTING"><data key="edge_relationship_id">R30_REL033</data><data key="edge_source_entity_id">DATA_ENUM_FEEDBACK_EM</data><data key="edge_relationship_type">excluded_from</data><data key="edge_target_entity_id">REPORT_ENUM_MI_LISTING</data><data key="edge_operational_context">Current EAE POMS explicitly says the Investigate application message is not listed on the Enumeration MI listing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Negative relationship is directly stated by policy.</data></edge><edge id="R30_REL034" source="EX_EBE" target="DATA_ENUM_FEEDBACK_EM3"><data key="edge_relationship_id">R30_REL034</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">generates_exception_message</data><data key="edge_target_entity_id">DATA_ENUM_FEEDBACK_EM3</data><data key="edge_operational_context">EBE applications that cannot auto-process can generate EM3 and remain in Investigate status.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL035" source="DATA_ENUM_FEEDBACK_EM3" target="APP_SSNAP"><data key="edge_relationship_id">R30_REL035</data><data key="edge_source_entity_id">DATA_ENUM_FEEDBACK_EM3</data><data key="edge_relationship_type">associated_with_pending_application_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">EBE EM3 exception work remains pending in SSNAP for resolution.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL036" source="DATA_ENUM_FEEDBACK_EM3" target="REPORT_ENUM_MI_LISTING"><data key="edge_relationship_id">R30_REL036</data><data key="edge_source_entity_id">DATA_ENUM_FEEDBACK_EM3</data><data key="edge_relationship_type">listed_on</data><data key="edge_target_entity_id">REPORT_ENUM_MI_LISTING</data><data key="edge_operational_context">Current EBE POMS explicitly says EM3 Investigate applications are listed on the Enumeration MI listing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R30_REL037" source="PROC_CASEWARE_IDEA_2024" target="TECH_CASEWARE_IDEA_NLS"><data key="edge_relationship_id">R30_REL037</data><data key="edge_source_entity_id">PROC_CASEWARE_IDEA_2024</data><data key="edge_relationship_type">renews_subscription_for</data><data key="edge_target_entity_id">TECH_CASEWARE_IDEA_NLS</data><data key="edge_operational_context">SAM.gov describes the solicitation as renewal of the prior concurrent-license Caseware IDEA NLS subscription.</data><data key="edge_observed_as_of">2024-01-25</data><data key="edge_confidence">5</data><data key="edge_notes">Procurement relationship only; no 2026 use inferred.</data></edge><edge id="R31REL001" source="DB_APPOINTED_REP_MI_ODS" target="APP_APPOINTED_REP"><data key="edge_relationship_id">R31REL001</data><data key="edge_source_entity_id">DB_APPOINTED_REP_MI_ODS</data><data key="edge_relationship_type">provides_management_reporting_for</data><data key="edge_target_entity_id">APP_APPOINTED_REP</data><data key="edge_operational_context">The data store contains appointed-representative information used for reporting; this is a logical scope link to the Appointed Representatives service family, not a claimed physical interface.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">No RASR/AARPS transport or physical feed is inferred.</data></edge><edge id="R31REL002" source="DB_APPOINTED_REP_1099" target="APP_APPOINTED_REP"><data key="edge_relationship_id">R31REL002</data><data key="edge_source_entity_id">DB_APPOINTED_REP_1099</data><data key="edge_relationship_type">contains_data_supporting</data><data key="edge_target_entity_id">APP_APPOINTED_REP</data><data key="edge_operational_context">SSA says the data store contains information for the Appointed Representative Suite, including appointment, 1099 issuance, and representative-claimant relationship data.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Logical product-family relationship only.</data></edge><edge id="R31REL003" source="DB_AUTHORIZED_REP" target="APP_APPOINTED_REP"><data key="edge_relationship_id">R31REL003</data><data key="edge_source_entity_id">DB_AUTHORIZED_REP</data><data key="edge_relationship_type">contains_post_entitlement_representative_data_for</data><data key="edge_target_entity_id">APP_APPOINTED_REP</data><data key="edge_operational_context">SSA inventories the asset as appointed-representative data collected after a post-entitlement action.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Catalog does not identify source application or transport.</data></edge><edge id="R31REL004" source="DB_LOCAL_MI_ODS" target="DOM_E_SERVICES"><data key="edge_relationship_id">R31REL004</data><data key="edge_source_entity_id">DB_LOCAL_MI_ODS</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">DOM_E_SERVICES</data><data key="edge_operational_context">SSA describes the asset as local management information for the Electronic Services application.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical reporting relationship; no physical source feed inferred.</data></edge><edge id="R31REL005" source="DB_SUMS_CDR_ODS" target="ARCH_SUMS"><data key="edge_relationship_id">R31REL005</data><data key="edge_source_entity_id">DB_SUMS_CDR_ODS</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">ARCH_SUMS</data><data key="edge_operational_context">The authoritative inventory explicitly names the data store as part of the SSA Unified Measurement System (SUMS).</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">This identifies architectural membership, not a specific interface.</data></edge><edge id="R31REL006" source="APP_IMRC" target="DB_ESERVICE_ODS"><data key="edge_relationship_id">R31REL006</data><data key="edge_source_entity_id">APP_IMRC</data><data key="edge_relationship_type">transactions_stored_nightly_in</data><data key="edge_target_entity_id">DB_ESERVICE_ODS</data><data key="edge_operational_context">SSA says Online Medicare Replacement Card front-end transactions are stored nightly in Electronic Services ODS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">SSA says data move to an unnamed Data Warehouse the next day; Atlas does not map that warehouse without a named target.</data></edge><edge id="R31REL007" source="ORG_TREASURY" target="EX_DAS_TREASURY"><data key="edge_relationship_id">R31REL007</data><data key="edge_source_entity_id">ORG_TREASURY</data><data key="edge_relationship_type">sends_status_transmission</data><data key="edge_target_entity_id">EX_DAS_TREASURY</data><data key="edge_operational_context">POMS defines Daily Advice of Status as an electronic transmission from Treasury reporting stop-code and payment/check status.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Transport technology is not specified.</data></edge><edge id="R31REL008" source="DATA_TREASURY_PROCESS_MSG" target="DB_PHUS"><data key="edge_relationship_id">R31REL008</data><data key="edge_source_entity_id">DATA_TREASURY_PROCESS_MSG</data><data key="edge_relationship_type">posts_to_for_title_ii</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">POMS says Treasury process messages/disposition codes post to PHUS for Title II cases.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct policy-stated destination.</data></edge><edge id="R31REL009" source="DATA_TREASURY_PROCESS_MSG" target="APP_UPTQ"><data key="edge_relationship_id">R31REL009</data><data key="edge_source_entity_id">DATA_TREASURY_PROCESS_MSG</data><data key="edge_relationship_type">posts_to_for_title_xvi</data><data key="edge_target_entity_id">APP_UPTQ</data><data key="edge_operational_context">POMS says Treasury process messages/disposition codes post to Treasury Status Query (UPTQ) for Title XVI cases.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct policy-stated destination.</data></edge><edge id="R31REL010" source="CON_CREOAL_SSOARS_SERS" target="ORG_CREOAL"><data key="edge_relationship_id">R31REL010</data><data key="edge_source_entity_id">CON_CREOAL_SSOARS_SERS</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_CREOAL</data><data key="edge_operational_context">USAspending identifies CREOAL Consulting LLC as recipient of SSA task order 28321323FDX030012.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Current federal award record.</data></edge><edge id="R31REL011" source="CON_CREOAL_SSOARS_SERS" target="APP_SSOARS"><data key="edge_relationship_id">R31REL011</data><data key="edge_source_entity_id">CON_CREOAL_SSOARS_SERS</data><data key="edge_relationship_type">supports_database_and_operating_system_services_for</data><data key="edge_target_entity_id">APP_SSOARS</data><data key="edge_operational_context">Award description explicitly covers application database administration and operating system services for SSOARS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Contract support relationship, not application architecture.</data></edge><edge id="R31REL012" source="CON_CREOAL_SSOARS_SERS" target="APP_SERS"><data key="edge_relationship_id">R31REL012</data><data key="edge_source_entity_id">CON_CREOAL_SSOARS_SERS</data><data key="edge_relationship_type">supports_database_and_operating_system_services_for</data><data key="edge_target_entity_id">APP_SERS</data><data key="edge_operational_context">Award description explicitly covers application database administration and operating system services for SERS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Contract support relationship, not application architecture.</data></edge><edge id="R32REL001" source="DB_HR_ODS_CORE" target="DB_HR_ODS"><data key="edge_relationship_id">R32REL001</data><data key="edge_source_entity_id">DB_HR_ODS_CORE</data><data key="edge_relationship_type">subset_of</data><data key="edge_target_entity_id">DB_HR_ODS</data><data key="edge_operational_context">SSA inventory states the Core Services asset contains a very small subset of Human Resources ODS data.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical/data-scope relationship only; no replication mechanism is inferred.</data></edge><edge id="R32REL002" source="DB_HR_ODS_CORE" target="SVC_SEODR"><data key="edge_relationship_id">R32REL002</data><data key="edge_source_entity_id">DB_HR_ODS_CORE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SVC_SEODR</data><data key="edge_operational_context">SSA inventory explicitly states the HR ODS Core Services data supports the SEODR Core Services function.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No API, protocol, or physical interface is inferred.</data></edge><edge id="R32REL003" source="PROC_CDR_MAILER" target="DATA_SSA455"><data key="edge_relationship_id">R32REL003</data><data key="edge_source_entity_id">PROC_CDR_MAILER</data><data key="edge_relationship_type">uses_form</data><data key="edge_target_entity_id">DATA_SSA455</data><data key="edge_operational_context">POMS identifies SSA-455 and SSA-455-OCR-SM as the forms used by the CDR mailer process.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Business-process relationship.</data></edge><edge id="R32REL004" source="DATA_SSA455" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R32REL004</data><data key="edge_source_entity_id">DATA_SSA455</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms catalog routes SSA-455 Complete Online Form and Upload PDF actions to the shared eSubmit/Upload Documents path.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Shared digital intake channel; no form-specific backend is inferred.</data></edge><edge id="R32REL005" source="DATA_SSA455" target="APP_INFORM"><data key="edge_relationship_id">R32REL005</data><data key="edge_source_entity_id">DATA_SSA455</data><data key="edge_relationship_type">available_in</data><data key="edge_target_entity_id">APP_INFORM</data><data key="edge_operational_context">EM-23054 REV states the latest SSA-455 is available in the inForm Library.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Current form-library availability.</data></edge><edge id="R32REL006" source="DATA_SSA455" target="ORG_WBDOC"><data key="edge_relationship_id">R32REL006</data><data key="edge_source_entity_id">DATA_SSA455</data><data key="edge_relationship_type">scannable_variant_returned_to</data><data key="edge_target_entity_id">ORG_WBDOC</data><data key="edge_operational_context">EM-23054 REV states recipients return the SSA-455-OCR-SM scannable mailer to the Wilkes-Barre Direct Operations Center.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Applies to the SSA-455-OCR-SM variant, not every SSA-455 submission channel.</data></edge><edge id="R32REL007" source="PROC_CDR_MAILER" target="DB_DCF"><data key="edge_relationship_id">R32REL007</data><data key="edge_source_entity_id">PROC_CDR_MAILER</data><data key="edge_relationship_type">updates_controls_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">POMS states CDR mailer processing establishes and updates Disability Control File controls and records decision outcomes.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Policy-level process relationship; no current middleware or transport is inferred.</data></edge><edge id="R32REL008" source="APP_ICLAIM" target="APP_I3368"><data key="edge_relationship_id">R32REL008</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">propagates_selected_data_to</data><data key="edge_target_entity_id">APP_I3368</data><data key="edge_operational_context">Current POMS states that after iClaim submission the system starts i3368 and some iClaim information propagates to i3368.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Separate applications remain modeled separately; transport is not specified.</data></edge><edge id="R32REL009" source="APP_I3368" target="APP_EAUTH827"><data key="edge_relationship_id">R32REL009</data><data key="edge_source_entity_id">APP_I3368</data><data key="edge_relationship_type">uses_eauthorization</data><data key="edge_target_entity_id">APP_EAUTH827</data><data key="edge_operational_context">Current POMS states i3368 offers eAuthorization and can submit an electronic SSA-827 with the i3368.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Functional linkage only; the source does not expose internal API implementation.</data></edge><edge id="R32REL010" source="APP_ASC" target="APP_ELAS"><data key="edge_relationship_id">R32REL010</data><data key="edge_source_entity_id">APP_ASC</data><data key="edge_relationship_type">stores_protective_filing_receipt_in</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Current ASC rollout guidance states protective filing and closeout receipt dates are stored in eLAS as appropriate.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Current field-operations relationship; no integration protocol is inferred.</data></edge><edge id="R32REL011" source="DB_PNICS" target="ORG_FBI"><data key="edge_relationship_id">R32REL011</data><data key="edge_source_entity_id">DB_PNICS</data><data key="edge_relationship_type">shares_information_with</data><data key="edge_target_entity_id">ORG_FBI</data><data key="edge_operational_context">Current SSA enterprise inventory states information in PNICS is shared with the FBI and added to the FBI database.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">External data-sharing relationship. Receiving FBI database and transmission mechanism are not named.</data></edge><edge id="R33REL001" source="DB_SRF" target="APP_EDCS"><data key="edge_relationship_id">R33REL001</data><data key="edge_source_entity_id">DB_SRF</data><data key="edge_relationship_type">component_data_store_of</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">POMS states EDCS contains the Source Reference File database used to locate disability information sources.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical containment; physical database engine/topology is not identified.</data></edge><edge id="R33REL002" source="APP_EDCS" target="APP_EFORMS"><data key="edge_relationship_id">R33REL002</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">links_to</data><data key="edge_target_entity_id">APP_EFORMS</data><data key="edge_operational_context">POMS states EDCS contains an internal link to the eForms program for disability-case forms not available directly in EDCS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No integration protocol is inferred.</data></edge><edge id="R33REL003" source="APP_EFORMS" target="REPO_CEF"><data key="edge_relationship_id">R33REL003</data><data key="edge_source_entity_id">APP_EFORMS</data><data key="edge_relationship_type">stores_completed_form_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">eForms instructions allow users to send a completed eForm to the Certified Electronic Folder using the EF button.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow relationship only; underlying transport is not stated.</data></edge><edge id="R33REL004" source="APP_EDCS" target="UI_DMA_VIEWER"><data key="edge_relationship_id">R33REL004</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">launches</data><data key="edge_target_entity_id">UI_DMA_VIEWER</data><data key="edge_operational_context">In the iAppeals document workflow, EDCS document links/open actions launch the DMA Viewer for review.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Context is the documented Internet/iAppeals document-review path; not generalized to every EDCS function.</data></edge><edge id="R33REL005" source="APP_EVIEW" target="UI_DMA_VIEWER"><data key="edge_relationship_id">R33REL005</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">opens_documents_with</data><data key="edge_target_entity_id">UI_DMA_VIEWER</data><data key="edge_operational_context">POMS documents electronic-folder document viewing through DMA Viewer in the retained disability evidence workflow.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Current architecture boundary between eView and DMA Viewer is not otherwise exposed; relationship is limited to documented user behavior.</data></edge><edge id="R33REL006" source="UTIL_EDCS_UAT" target="APP_EDCS"><data key="edge_relationship_id">R33REL006</data><data key="edge_source_entity_id">UTIL_EDCS_UAT</data><data key="edge_relationship_type">utility_within</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">UAT is accessed from an EDCS disability case via Transfer/Updates.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No separate deployment boundary is inferred.</data></edge><edge id="R33REL007" source="APP_MCS" target="UTIL_EDCS_UAT"><data key="edge_relationship_id">R33REL007</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">provides_post_transfer_updates_to</data><data key="edge_target_entity_id">UTIL_EDCS_UAT</data><data key="edge_operational_context">UAT propagates selected MCS changes into EDCS after case transfer.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical data propagation; protocol is not stated.</data></edge><edge id="R33REL008" source="APP_MSSICS" target="UTIL_EDCS_UAT"><data key="edge_relationship_id">R33REL008</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">provides_post_transfer_updates_to</data><data key="edge_target_entity_id">UTIL_EDCS_UAT</data><data key="edge_operational_context">UAT propagates selected MSSICS changes into EDCS after case transfer.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical data propagation; protocol is not stated.</data></edge><edge id="R33REL009" source="APP_CCE" target="UTIL_EDCS_UAT"><data key="edge_relationship_id">R33REL009</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">provides_post_transfer_updates_to</data><data key="edge_target_entity_id">UTIL_EDCS_UAT</data><data key="edge_operational_context">UAT procedures explicitly include selected Consolidated Claims Experience changes among post-transfer updates.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical data propagation; protocol is not stated.</data></edge><edge id="R33REL010" source="UTIL_EDCS_UAT" target="APP_EDCS"><data key="edge_relationship_id">R33REL010</data><data key="edge_source_entity_id">UTIL_EDCS_UAT</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">UAT repropagates selected post-transfer data and claim changes into EDCS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No direct database write/API assumption is made.</data></edge><edge id="R33REL011" source="UTIL_EDCS_UAT" target="DATA_ROC"><data key="edge_relationship_id">R33REL011</data><data key="edge_source_entity_id">UTIL_EDCS_UAT</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">DATA_ROC</data><data key="edge_operational_context">POMS states EDCS produces a Record of Change for the first UAT action.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Subsequent UAT actions do not produce additional ROCs per the cited POMS.</data></edge><edge id="R33REL012" source="DATA_ROC" target="APP_EVIEW"><data key="edge_relationship_id">R33REL012</data><data key="edge_source_entity_id">DATA_ROC</data><data key="edge_relationship_type">displayed_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Current quality-review POMS and EDCS case-data guidance identify Record of Change information in the electronic-folder/eView case-data workflow.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Presentation/storage internals are not inferred.</data></edge><edge id="R33REL013" source="UI_EDCS_ACTIONS" target="APP_EDCS"><data key="edge_relationship_id">R33REL013</data><data key="edge_source_entity_id">UI_EDCS_ACTIONS</data><data key="edge_relationship_type">page_within</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">POMS identifies the EDCS Actions Page as the first page presented after opening EDCS each day and as the AR/AI work surface.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R33REL014" source="UI_EDCS_ACTIONS" target="APP_EFI"><data key="edge_relationship_id">R33REL014</data><data key="edge_source_entity_id">UI_EDCS_ACTIONS</data><data key="edge_relationship_type">sends_accepted_requests_through</data><data key="edge_target_entity_id">APP_EFI</data><data key="edge_operational_context">Current POMS states an accepted AR enters Transaction in Progress when sent to EFI and becomes Pending after EFI processing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">This establishes active functional use of EFI but not its internal middleware topology.</data></edge><edge id="R33REL015" source="APP_EDCS" target="DATA_EFI_DOWNLOAD"><data key="edge_relationship_id">R33REL015</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_EFI_DOWNLOAD</data><data key="edge_operational_context">POMS states EDCS creates an EFI Download for each claim.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No file format or transport protocol is inferred.</data></edge><edge id="R33REL016" source="DATA_EFI_DOWNLOAD" target="ORG_DDS"><data key="edge_relationship_id">R33REL016</data><data key="edge_source_entity_id">DATA_EFI_DOWNLOAD</data><data key="edge_relationship_type">received_by</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">DDS procedures state DDS expects an EFI Download for claims on the EDCS Routing Form and uses it for receipt processing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Organization-level receipt relationship; receiving DDS case-processing system may vary by state and is not inferred.</data></edge><edge id="R33REL017" source="CAP_UPLOAD_CONVERSATIONAL" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R33REL017</data><data key="edge_source_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_relationship_type">feature_of</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">EM-26029 states the first conversational forms are launched within Upload Documents.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Mode/feature relationship, not a separate backend application.</data></edge><edge id="R33REL018" source="APP_UPLOAD_DOCUMENTS" target="DATA_SSA8240"><data key="edge_relationship_id">R33REL018</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">accepts_public_submission_for</data><data key="edge_target_entity_id">DATA_SSA8240</data><data key="edge_operational_context">Current Forms catalog provides electronic SSA-8240 completion/upload through the shared Upload Documents path.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Channel relationship only; downstream case-system integration is not inferred.</data></edge><edge id="R33REL019" source="DATA_SSA8240" target="APP_WEIA"><data key="edge_relationship_id">R33REL019</data><data key="edge_source_entity_id">DATA_SSA8240</data><data key="edge_relationship_type">processed_by</data><data key="edge_target_entity_id">APP_WEIA</data><data key="edge_operational_context">POMS states returned paper SSA-8240/authorization responses are recorded in the WEIA application and that SSA-8240 or WEIA pages are the authorized means of obtaining WEIA.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Business/workflow relationship; form image storage is separate.</data></edge><edge id="R33REL020" source="DATA_SSA8240" target="EX_PIE"><data key="edge_relationship_id">R33REL020</data><data key="edge_source_entity_id">DATA_SSA8240</data><data key="edge_relationship_type">authorizes_data_access_for</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">POMS states individuals provide WEIA on SSA-8240 and SSA uses that authorization to obtain payroll-provider information through PIE.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Legal/business authorization prerequisite, not a technical interface from the form artifact to PIE.</data></edge><edge id="R33REL021" source="APP_UPLOAD_DOCUMENTS" target="DATA_SSA552"><data key="edge_relationship_id">R33REL021</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">accepts_public_submission_for</data><data key="edge_target_entity_id">DATA_SSA552</data><data key="edge_operational_context">POMS states individual payees with my Social Security can complete and submit SSA-552 through Upload Documents.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R33REL022" source="DATA_SSA552" target="REPO_NDRED"><data key="edge_relationship_id">R33REL022</data><data key="edge_source_entity_id">DATA_SSA552</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">POMS directs the field office to store a completed SSA-552 in NDRed via Evidence Portal.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Repository relationship; Evidence Portal is the documented ingestion path.</data></edge><edge id="R33REL023" source="DATA_SSA552" target="APP_WORKTRACK"><data key="edge_relationship_id">R33REL023</data><data key="edge_source_entity_id">DATA_SSA552</data><data key="edge_relationship_type">routes_submission_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">POMS states SSA-552 submitted through Upload Documents is electronically routed to WorkTrack for the requesting technician or jurisdictional field office.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No message format/API is inferred.</data></edge><edge id="R33REL024" source="UI_DMS_DRCD" target="APP_DMS"><data key="edge_relationship_id">R33REL024</data><data key="edge_source_entity_id">UI_DMS_DRCD</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Current POMS identifies DRCD as the DMS Record Compromise Decision screen.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R33REL025" source="UI_DMS_DRCW" target="APP_DMS"><data key="edge_relationship_id">R33REL025</data><data key="edge_source_entity_id">UI_DMS_DRCW</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Current POMS identifies DRCW as the DMS Review Compromise Approval screen.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R33REL026" source="UI_DMS_RMKS" target="APP_DMS"><data key="edge_relationship_id">R33REL026</data><data key="edge_source_entity_id">UI_DMS_RMKS</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Current POMS explicitly calls RMKS the DMS REMARKS screen.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R33REL027" source="UI_DMS_DRCW" target="UI_DMS_DRCD"><data key="edge_relationship_id">R33REL027</data><data key="edge_source_entity_id">UI_DMS_DRCW</data><data key="edge_relationship_type">reviews_decisions_from</data><data key="edge_target_entity_id">UI_DMS_DRCD</data><data key="edge_operational_context">Compromises over $2,000 require second-level review in DRCW after the decision is entered in DRCD.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow sequence; no separate transaction bus is inferred.</data></edge><edge id="R33REL028" source="UI_DMS_DRCD" target="APP_ROAR"><data key="edge_relationship_id">R33REL028</data><data key="edge_source_entity_id">UI_DMS_DRCD</data><data key="edge_relationship_type">causes_writeoff_posting_to</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">POMS states input to DRCD/DRCW generates TC53 to post the write-off amount to ROAR and set a processing-center diary.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Effect is documented; the intermediate TC53 transaction is not separately modeled in this run.</data></edge><edge id="R33REL029" source="CON_OSEP_GIS_2025" target="ORG_ARDENT_CLOUD"><data key="edge_relationship_id">R33REL029</data><data key="edge_source_entity_id">CON_OSEP_GIS_2025</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_ARDENT_CLOUD</data><data key="edge_operational_context">USAspending identifies Ardent Cloud, LLC as recipient of SSA BPA Call 28321325FA0010051.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R34REL001" source="EX_HRS_LINKAGE" target="PROG_HRS"><data key="edge_relationship_id">R34REL001</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">The linkage supplies consented SSA administrative records for HRS restricted-data research use.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data></edge><edge id="R34REL002" source="EX_HRS_LINKAGE" target="SYS_NUMIDENT"><data key="edge_relationship_id">R34REL002</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">validates_identifying_information_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">HRS sends properly completed consent information to SSA; SSA first validates respondent identifying information against Numident before earnings/benefit matching.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data><data key="edge_notes">HRS guide explicitly says Numident match results themselves are not returned to HRS.</data></edge><edge id="R34REL003" source="SYS_MEF" target="DATA_HRS_SER"><data key="edge_relationship_id">R34REL003</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">source_for_research_extract</data><data key="edge_target_entity_id">DATA_HRS_SER</data><data key="edge_operational_context">HRS guide explicitly states SER is derived from SSA Master Earnings File.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL004" source="SYS_MEF" target="DATA_HRS_DER"><data key="edge_relationship_id">R34REL004</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">source_for_research_extract</data><data key="edge_target_entity_id">DATA_HRS_DER</data><data key="edge_operational_context">HRS guide explicitly states DER is derived from SSA Master Earnings File.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL005" source="SYS_MBR" target="DATA_HRS_CYBF"><data key="edge_relationship_id">R34REL005</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_research_extract</data><data key="edge_target_entity_id">DATA_HRS_CYBF</data><data key="edge_operational_context">HRS CYBF sections A-F draw benefit information from the Master Beneficiary Record.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL006" source="DB_PHUS" target="DATA_HRS_CYBF"><data key="edge_relationship_id">R34REL006</data><data key="edge_source_entity_id">DB_PHUS</data><data key="edge_relationship_type">source_for_research_extract</data><data key="edge_target_entity_id">DATA_HRS_CYBF</data><data key="edge_operational_context">HRS CYBF section G draws payment information from PHUS.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL007" source="SYS_SSR" target="DATA_HRS_SSI"><data key="edge_relationship_id">R34REL007</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for_research_extract</data><data key="edge_target_entity_id">DATA_HRS_SSI</data><data key="edge_operational_context">HRS guide states the HRS SSI file is derived from the Supplemental Security Record.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL008" source="DATA_HRS_SER" target="PROG_HRS"><data key="edge_relationship_id">R34REL008</data><data key="edge_source_entity_id">DATA_HRS_SER</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">SSA-linked restricted data product made available through the HRS data program for consented matched respondents.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL009" source="DATA_HRS_DER" target="PROG_HRS"><data key="edge_relationship_id">R34REL009</data><data key="edge_source_entity_id">DATA_HRS_DER</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">SSA-linked restricted data product made available through the HRS data program for consented matched respondents.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL010" source="DATA_HRS_FORM831" target="PROG_HRS"><data key="edge_relationship_id">R34REL010</data><data key="edge_source_entity_id">DATA_HRS_FORM831</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">SSA-linked restricted data product made available through the HRS data program for consented matched respondents.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL011" source="DATA_HRS_CYBF" target="PROG_HRS"><data key="edge_relationship_id">R34REL011</data><data key="edge_source_entity_id">DATA_HRS_CYBF</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">SSA-linked restricted data product made available through the HRS data program for consented matched respondents.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL012" source="DATA_HRS_SSI" target="PROG_HRS"><data key="edge_relationship_id">R34REL012</data><data key="edge_source_entity_id">DATA_HRS_SSI</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">SSA-linked restricted data product made available through the HRS data program for consented matched respondents.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL013" source="DATA_DAF" target="PROG_HRS"><data key="edge_relationship_id">R34REL013</data><data key="edge_source_entity_id">DATA_DAF</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">PROG_HRS</data><data key="edge_operational_context">HRS documentation lists the Disability Analysis File among SSA-linked restricted data products available to HRS users.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data><data key="edge_notes">Does not change the Atlas lifecycle status of the production DAF.</data></edge><edge id="R34REL014" source="EX_HRS_LINKAGE" target="DATA_HRS_SER"><data key="edge_relationship_id">R34REL014</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">produces_or_updates_research_extract</data><data key="edge_target_entity_id">DATA_HRS_SER</data><data key="edge_operational_context">SSA/HRS linkage cycle returns or updates the matched administrative records permitted by respondent consent.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">4</data><data key="edge_notes">Logical exchange relationship only; transport/file-transfer mechanism is not asserted.</data></edge><edge id="R34REL015" source="EX_HRS_LINKAGE" target="DATA_HRS_DER"><data key="edge_relationship_id">R34REL015</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">produces_or_updates_research_extract</data><data key="edge_target_entity_id">DATA_HRS_DER</data><data key="edge_operational_context">SSA/HRS linkage cycle returns or updates the matched administrative records permitted by respondent consent.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">4</data><data key="edge_notes">Logical exchange relationship only; transport/file-transfer mechanism is not asserted.</data></edge><edge id="R34REL016" source="EX_HRS_LINKAGE" target="DATA_HRS_FORM831"><data key="edge_relationship_id">R34REL016</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">produces_or_updates_research_extract</data><data key="edge_target_entity_id">DATA_HRS_FORM831</data><data key="edge_operational_context">SSA/HRS linkage cycle returns or updates the matched administrative records permitted by respondent consent.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">4</data><data key="edge_notes">Logical exchange relationship only; transport/file-transfer mechanism is not asserted.</data></edge><edge id="R34REL017" source="EX_HRS_LINKAGE" target="DATA_HRS_CYBF"><data key="edge_relationship_id">R34REL017</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">produces_or_updates_research_extract</data><data key="edge_target_entity_id">DATA_HRS_CYBF</data><data key="edge_operational_context">SSA/HRS linkage cycle returns or updates the matched administrative records permitted by respondent consent.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">4</data><data key="edge_notes">Logical exchange relationship only; transport/file-transfer mechanism is not asserted.</data></edge><edge id="R34REL018" source="EX_HRS_LINKAGE" target="DATA_HRS_SSI"><data key="edge_relationship_id">R34REL018</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">produces_or_updates_research_extract</data><data key="edge_target_entity_id">DATA_HRS_SSI</data><data key="edge_operational_context">SSA/HRS linkage cycle returns or updates the matched administrative records permitted by respondent consent.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">4</data><data key="edge_notes">Logical exchange relationship only; transport/file-transfer mechanism is not asserted.</data></edge><edge id="R34REL019" source="DATA_HRS_FORM831" target="DOM_TITLE2"><data key="edge_relationship_id">R34REL019</data><data key="edge_source_entity_id">DATA_HRS_FORM831</data><data key="edge_relationship_type">covers_program_domain</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Form 831 respondent records include medically reviewed SSDI applications.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL020" source="DATA_HRS_FORM831" target="DOM_TITLE16"><data key="edge_relationship_id">R34REL020</data><data key="edge_source_entity_id">DATA_HRS_FORM831</data><data key="edge_relationship_type">covers_program_domain</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Form 831 respondent records include medically reviewed SSI applications.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data></edge><edge id="R34REL021" source="INIT_STAT_PUB_MOD" target="PLAT_SHAREPOINT"><data key="edge_relationship_id">R34REL021</data><data key="edge_source_entity_id">INIT_STAT_PUB_MOD</data><data key="edge_relationship_type">uses_for_statistical_task_migration</data><data key="edge_target_entity_id">PLAT_SHAREPOINT</data><data key="edge_operational_context">FY2025 work upgraded, tested, and migrated OASDI, SSI, and earnings-related statistical-publication tasks with SharePoint.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL022" source="INIT_STAT_PUB_MOD" target="PLAT_EBI"><data key="edge_relationship_id">R34REL022</data><data key="edge_source_entity_id">INIT_STAT_PUB_MOD</data><data key="edge_relationship_type">uses_enhanced_tools_from</data><data key="edge_target_entity_id">PLAT_EBI</data><data key="edge_operational_context">FY2027 plan calls for enhanced EBI tools to support statistics production and ad hoc research extracts.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL023" source="INIT_STAT_PUB_MOD" target="DOM_TITLE2"><data key="edge_relationship_id">R34REL023</data><data key="edge_source_entity_id">INIT_STAT_PUB_MOD</data><data key="edge_relationship_type">modernizes_statistical_publication_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Budget describes OASDI statistical-publication modernization; Title II is the Atlas program-domain representation for OASDI benefit data.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Domain-level mapping, not an application interface.</data></edge><edge id="R34REL024" source="INIT_STAT_PUB_MOD" target="DOM_TITLE16"><data key="edge_relationship_id">R34REL024</data><data key="edge_source_entity_id">INIT_STAT_PUB_MOD</data><data key="edge_relationship_type">modernizes_statistical_publication_for</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Budget explicitly describes SSI statistical publication and data-input modernization.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL025" source="INIT_STAT_PUB_MOD" target="DOM_EARNINGS"><data key="edge_relationship_id">R34REL025</data><data key="edge_source_entity_id">INIT_STAT_PUB_MOD</data><data key="edge_relationship_type">modernizes_statistical_publication_for</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Budget explicitly describes earnings-related statistical publication tasks in the modernization effort.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL026" source="UI_DMS_RFOR" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">R34REL026</data><data key="edge_source_entity_id">UI_DMS_RFOR</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">Current POMS identifies this screen within field-office DMS remittance processing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL027" source="UI_DMS_RCFR" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">R34REL027</data><data key="edge_source_entity_id">UI_DMS_RCFR</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">Current POMS identifies this screen within field-office DMS remittance processing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL028" source="UI_DMS_RMCR" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">R34REL028</data><data key="edge_source_entity_id">UI_DMS_RMCR</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">Current POMS identifies this screen within field-office DMS remittance processing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL029" source="UI_DMS_RCRD" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">R34REL029</data><data key="edge_source_entity_id">UI_DMS_RCRD</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">Current POMS identifies this screen within field-office DMS remittance processing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL030" source="APP_DMS_REMITTANCE" target="REPORT_DMS_FORT"><data key="edge_relationship_id">R34REL030</data><data key="edge_source_entity_id">APP_DMS_REMITTANCE</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">REPORT_DMS_FORT</data><data key="edge_operational_context">Current POMS states DMS generates this remittance-control output/artifact.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL031" source="APP_DMS_REMITTANCE" target="REPORT_DMS_CCFORT"><data key="edge_relationship_id">R34REL031</data><data key="edge_source_entity_id">APP_DMS_REMITTANCE</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">REPORT_DMS_CCFORT</data><data key="edge_operational_context">Current POMS states DMS generates this remittance-control output/artifact.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL032" source="APP_DMS_REMITTANCE" target="REPORT_DMS_FODRL"><data key="edge_relationship_id">R34REL032</data><data key="edge_source_entity_id">APP_DMS_REMITTANCE</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">REPORT_DMS_FODRL</data><data key="edge_operational_context">Current POMS states DMS generates this remittance-control output/artifact.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL033" source="APP_DMS_REMITTANCE" target="DATA_DMS_FO_COUPON"><data key="edge_relationship_id">R34REL033</data><data key="edge_source_entity_id">APP_DMS_REMITTANCE</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_DMS_FO_COUPON</data><data key="edge_operational_context">Current POMS states DMS generates this remittance-control output/artifact.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL034" source="DATA_DMS_FO_COUPON" target="FAC_MATPSC"><data key="edge_relationship_id">R34REL034</data><data key="edge_source_entity_id">DATA_DMS_FO_COUPON</data><data key="edge_relationship_type">processed_at</data><data key="edge_target_entity_id">FAC_MATPSC</data><data key="edge_operational_context">MATPSC uses coupon/scan-line information to process and credit remittances.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL035" source="REPORT_DMS_FORT" target="FAC_MATPSC"><data key="edge_relationship_id">R34REL035</data><data key="edge_source_entity_id">REPORT_DMS_FORT</data><data key="edge_relationship_type">accompanies_remittances_to</data><data key="edge_target_entity_id">FAC_MATPSC</data><data key="edge_operational_context">FORT accompanies check/money-order remittances forwarded from field offices to MATPSC.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL036" source="REPORT_DMS_CCFORT" target="FAC_MATPSC"><data key="edge_relationship_id">R34REL036</data><data key="edge_source_entity_id">REPORT_DMS_CCFORT</data><data key="edge_relationship_type">accompanies_remittances_to</data><data key="edge_target_entity_id">FAC_MATPSC</data><data key="edge_operational_context">CCFORT is the end-of-day transmittal for debit/credit-card remittance transactions in the DMS field-office process; MATPSC is the national remittance processing site.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">The exact handling of card transaction settlement is not inferred.</data></edge><edge id="R34REL037" source="FAC_MATPSC" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">R34REL037</data><data key="edge_source_entity_id">FAC_MATPSC</data><data key="edge_relationship_type">national_processing_site_for</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">POMS identifies MATPSC as SSA national remittance processing site for programmatic debt payments forwarded by field offices/debtors.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R34REL038" source="APP_SERS" target="FAC_MATPSC"><data key="edge_relationship_id">R34REL038</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">reduces_physical_forwarding_to</data><data key="edge_target_entity_id">FAC_MATPSC</data><data key="edge_operational_context">POMS states SERS electronically processes eligible check/money-order programmatic remittances and eliminates the need for field offices to send all such eligible remittances to MATPSC.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Applies only to SERS-eligible remittance categories; not all remittances.</data></edge><edge id="R34REL039" source="ORG_TREASURY" target="DATA_TREASURY_CDN"><data key="edge_relationship_id">R34REL039</data><data key="edge_source_entity_id">ORG_TREASURY</data><data key="edge_relationship_type">sends_electronic_check_claim_status</data><data key="edge_target_entity_id">DATA_TREASURY_CDN</data><data key="edge_operational_context">POMS states SSI Systems receive an electronic file containing Claims Disposition Notices from Treasury.</data><data key="edge_observed_as_of">2025-01-27</data><data key="edge_confidence">5</data></edge><edge id="R34REL040" source="DATA_TREASURY_CDN" target="DATA_SSR_PMTH"><data key="edge_relationship_id">R34REL040</data><data key="edge_source_entity_id">DATA_TREASURY_CDN</data><data key="edge_relationship_type">posts_forgery_indicator_to</data><data key="edge_target_entity_id">DATA_SSR_PMTH</data><data key="edge_operational_context">The CDN file posts a forgery indicator in the SSR PMTH segment/display.</data><data key="edge_observed_as_of">2025-01-27</data><data key="edge_confidence">5</data></edge><edge id="R34REL041" source="DATA_SSR_PMTH" target="SYS_SSR"><data key="edge_relationship_id">R34REL041</data><data key="edge_source_entity_id">DATA_SSR_PMTH</data><data key="edge_relationship_type">segment_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS identifies PMTH as payment history on the Supplemental Security Record.</data><data key="edge_observed_as_of">2025-01-27</data><data key="edge_confidence">5</data></edge><edge id="R34REL042" source="UI_SSI_UPMR" target="DATA_SSR_PMTH"><data key="edge_relationship_id">R34REL042</data><data key="edge_source_entity_id">UI_SSI_UPMR</data><data key="edge_relationship_type">examines_payment_history_in</data><data key="edge_target_entity_id">DATA_SSR_PMTH</data><data key="edge_operational_context">SSI system examines PMTH Column F on the current SSR and displays a possible double-check-negotiation alert on UPMR.</data><data key="edge_observed_as_of">2025-01-27</data><data key="edge_confidence">5</data></edge><edge id="R34REL043" source="CON_SERVICENOW_BPA_2025" target="ORG_CARAHSOFT"><data key="edge_relationship_id">R34REL043</data><data key="edge_source_entity_id">CON_SERVICENOW_BPA_2025</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_CARAHSOFT</data><data key="edge_operational_context">FPDS identifies Carahsoft Technology Corp. as legal business name/awardee for SSA BPA 28321325A00040016.</data><data key="edge_observed_as_of">2026-02-11</data><data key="edge_confidence">5</data></edge><edge id="R34REL044" source="CON_SERVICENOW_BPA_2025" target="ORG_SERVICENOW"><data key="edge_relationship_id">R34REL044</data><data key="edge_source_entity_id">CON_SERVICENOW_BPA_2025</data><data key="edge_relationship_type">procures_software_from</data><data key="edge_target_entity_id">ORG_SERVICENOW</data><data key="edge_operational_context">FPDS requirement description explicitly states FSS BPA for ServiceNow software.</data><data key="edge_observed_as_of">2026-02-11</data><data key="edge_confidence">5</data><data key="edge_notes">Carahsoft is the contractual awardee/reseller; this relation records the named software provider, not a direct SSA-ServiceNow award.</data></edge><edge id="R34REL045" source="CON_SERVICENOW_BPA_2025" target="CON_SERVICENOW_BPA_2019"><data key="edge_relationship_id">R34REL045</data><data key="edge_source_entity_id">CON_SERVICENOW_BPA_2025</data><data key="edge_relationship_type">succeeds</data><data key="edge_target_entity_id">CON_SERVICENOW_BPA_2019</data><data key="edge_operational_context">FPDS requirement description names 28321319A00040024 as the previous BPA.</data><data key="edge_observed_as_of">2026-02-11</data><data key="edge_confidence">5</data></edge><edge id="R35REL001" source="DATA_E4962" target="APP_TDCP"><data key="edge_relationship_id">R35REL001</data><data key="edge_source_entity_id">DATA_E4962</data><data key="edge_relationship_type">completed_in</data><data key="edge_target_entity_id">APP_TDCP</data><data key="edge_operational_context">The e4962 is completed in TDCP to establish and maintain Totalization claims and foreign-agency assistance-request records.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL002" source="APP_TDCP" target="DB_TDCP"><data key="edge_relationship_id">R35REL002</data><data key="edge_source_entity_id">APP_TDCP</data><data key="edge_relationship_type">stores_completed_forms_in</data><data key="edge_target_entity_id">DB_TDCP</data><data key="edge_operational_context">TDCP retains electronic copies of completed forms in its database for three years.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL003" source="APP_TDCP" target="DATA_E2960"><data key="edge_relationship_id">R35REL003</data><data key="edge_source_entity_id">APP_TDCP</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_E2960</data><data key="edge_operational_context">TDCP was enhanced to automatically generate country-specific electronic SSA-2960 forms.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL004" source="APP_TDCP" target="DOM_TITLE2"><data key="edge_relationship_id">R35REL004</data><data key="edge_source_entity_id">APP_TDCP</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">TDCP is SSA's management-information source for the Totalization workload within international Title II processing.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL005" source="APP_TDCP" target="EX_US_ROMANIA_TOTALIZATION"><data key="edge_relationship_id">R35REL005</data><data key="edge_source_entity_id">APP_TDCP</data><data key="edge_relationship_type">supports_exchange</data><data key="edge_target_entity_id">EX_US_ROMANIA_TOTALIZATION</data><data key="edge_operational_context">Current Romania instructions require SSA staff to complete the e2960 USA/RO 3 via TDCP for claims and liaison requests.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL006" source="EX_US_ROMANIA_TOTALIZATION" target="ORG_ROMANIA_NHPP"><data key="edge_relationship_id">R35REL006</data><data key="edge_source_entity_id">EX_US_ROMANIA_TOTALIZATION</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_ROMANIA_NHPP</data><data key="edge_operational_context">The exchange transmits claims/material, requests information from, and responds to the Romanian National House of Public Pensions.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL007" source="EX_US_ROMANIA_TOTALIZATION" target="DATA_E2960"><data key="edge_relationship_id">R35REL007</data><data key="edge_source_entity_id">EX_US_ROMANIA_TOTALIZATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_E2960</data><data key="edge_operational_context">The U.S.-Romania exchange uses the SSA e2960 USA/RO 3 transmittal/request/certification form.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL008" source="APP_MCS" target="SYS_MBR"><data key="edge_relationship_id">R35REL008</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">generates_totalization_codes_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For U.S. Totalization claims, totalization codes are systems-generated from entries on MCS screens and posted to the MBR.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL009" source="SCR_MCS_TOTL" target="APP_MCS"><data key="edge_relationship_id">R35REL009</data><data key="edge_source_entity_id">SCR_MCS_TOTL</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">TOTALIZATION (TOTL) is documented as a Modernized Claims System screen used in applicable foreign-benefit claims.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL010" source="SCR_MCS_TOTL" target="DATA_US_TOTALIZATION_ER"><data key="edge_relationship_id">R35REL010</data><data key="edge_source_entity_id">SCR_MCS_TOTL</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_US_TOTALIZATION_ER</data><data key="edge_operational_context">Completing the MCS TOTALIZATION screen in concurrent U.S./foreign claims generates an earnings record for the foreign country.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL011" source="APP_ICER" target="DATA_US_TOTALIZATION_ER"><data key="edge_relationship_id">R35REL011</data><data key="edge_source_entity_id">APP_ICER</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_US_TOTALIZATION_ER</data><data key="edge_operational_context">For foreign-benefits-only claims that are MCS exclusions, technicians request an ICERS record for the foreign claims package.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL012" source="DATA_US_TOTALIZATION_ER" target="EX_US_ROMANIA_TOTALIZATION"><data key="edge_relationship_id">R35REL012</data><data key="edge_source_entity_id">DATA_US_TOTALIZATION_ER</data><data key="edge_relationship_type">included_in</data><data key="edge_target_entity_id">EX_US_ROMANIA_TOTALIZATION</data><data key="edge_operational_context">A U.S. totalization earnings/coverage record can be included in the claims package sent to the Romanian liaison agency.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL013" source="DATA_US_TOTALIZATION_ER" target="DATA_E2960"><data key="edge_relationship_id">R35REL013</data><data key="edge_source_entity_id">DATA_US_TOTALIZATION_ER</data><data key="edge_relationship_type">transmitted_with</data><data key="edge_target_entity_id">DATA_E2960</data><data key="edge_operational_context">Romania claim packages use e2960 and can include the U.S. earnings/coverage record as supporting material.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL014" source="APP_ISNO" target="APP_MCS"><data key="edge_relationship_id">R35REL014</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">appears_as_minipath_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">iSNO automatically appears as a mini-path from MCS when the Special Notice Option question is answered affirmatively.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL015" source="APP_ISNO" target="APP_MSSICS"><data key="edge_relationship_id">R35REL015</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">appears_as_minipath_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">iSNO automatically appears as a mini-path from MSSICS when the Special Notice Option question is answered affirmatively.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL016" source="APP_ISNO" target="APP_RPS"><data key="edge_relationship_id">R35REL016</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">appears_as_minipath_in</data><data key="edge_target_entity_id">APP_RPS</data><data key="edge_operational_context">iSNO automatically appears as a mini-path from RPS when the Special Notice Option question is answered affirmatively.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL017" source="APP_ISNO" target="APP_CHIP"><data key="edge_relationship_id">R35REL017</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">accessible_from</data><data key="edge_target_entity_id">APP_CHIP</data><data key="edge_operational_context">SSA employees can access iSNO through CHIP.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL018" source="APP_ISNO" target="APP_ARPS"><data key="edge_relationship_id">R35REL018</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">accessible_from</data><data key="edge_target_entity_id">APP_ARPS</data><data key="edge_operational_context">SSA employees can access iSNO through ARPS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL019" source="APP_ISNO" target="SYS_MBR"><data key="edge_relationship_id">R35REL019</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">authenticates_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">iSNO authentication checks identifying information against the MBR.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL020" source="APP_ISNO" target="SYS_SSR"><data key="edge_relationship_id">R35REL020</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">authenticates_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">iSNO authentication checks identifying information against the SSR.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL021" source="APP_ISNO" target="SYS_NUMIDENT"><data key="edge_relationship_id">R35REL021</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">authenticates_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">iSNO authentication checks identifying information against the Numident.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL022" source="APP_ISNO" target="PROC_SNO"><data key="edge_relationship_id">R35REL022</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">implements</data><data key="edge_target_entity_id">PROC_SNO</data><data key="edge_operational_context">iSNO records and queries a person's requested Special Notice Option.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL023" source="APP_IACCOMMODATE" target="APP_PERSON_INFO"><data key="edge_relationship_id">R35REL023</data><data key="edge_source_entity_id">APP_IACCOMMODATE</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current POMS says iAccommodate is found on IMAIN under Person Information (Identity, Contact, Accommodation).</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL024" source="SVC_TCIS" target="DATA_TREASURY_CHECK_CLAIMS_PACKAGE"><data key="edge_relationship_id">R35REL024</data><data key="edge_source_entity_id">SVC_TCIS</data><data key="edge_relationship_type">makes_available</data><data key="edge_target_entity_id">DATA_TREASURY_CHECK_CLAIMS_PACKAGE</data><data key="edge_operational_context">Treasury check claims packages are made available to SSA through TCIS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL025" source="DATA_TREASURY_CHECK_CLAIMS_PACKAGE" target="FORM_FS1133"><data key="edge_relationship_id">R35REL025</data><data key="edge_source_entity_id">DATA_TREASURY_CHECK_CLAIMS_PACKAGE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">FORM_FS1133</data><data key="edge_operational_context">Treasury check claims packages include FS-1133/FMS-1133.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL026" source="DATA_TREASURY_CHECK_CLAIMS_PACKAGE" target="FORM_FMS3858"><data key="edge_relationship_id">R35REL026</data><data key="edge_source_entity_id">DATA_TREASURY_CHECK_CLAIMS_PACKAGE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">FORM_FMS3858</data><data key="edge_operational_context">Treasury check claims packages include FMS-3858 Claims Document.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL027" source="ORG_TREASURY" target="DATA_TREASURY_CHECK_CLAIMS_PACKAGE"><data key="edge_relationship_id">R35REL027</data><data key="edge_source_entity_id">ORG_TREASURY</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_TREASURY_CHECK_CLAIMS_PACKAGE</data><data key="edge_operational_context">Treasury generates the claims package when SSA enters specified permanent stops on missing checks.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL028" source="FORM_FS1133" target="APP_EP"><data key="edge_relationship_id">R35REL028</data><data key="edge_source_entity_id">FORM_FS1133</data><data key="edge_relationship_type">scanned_into</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">FO, TSC or PC staff scan all pages of the completed FMS/FS-1133 into Evidence Portal before forwarding the package to Treasury.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL029" source="FORM_FS1133" target="ORG_TREASURY"><data key="edge_relationship_id">R35REL029</data><data key="edge_source_entity_id">FORM_FS1133</data><data key="edge_relationship_type">returned_to</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Completed FS-1133 claims packages are forwarded to Treasury for review.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL030" source="PROC_BSO_AUTHORIZATION" target="PLAT_BSO"><data key="edge_relationship_id">R35REL030</data><data key="edge_source_entity_id">PROC_BSO_AUTHORIZATION</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">SSA describes the planned updated authorization process as part of Business Services Online.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL031" source="DATA_EMPLOYER_SIGNATURE_PIN" target="PROC_BSO_AUTHORIZATION"><data key="edge_relationship_id">R35REL031</data><data key="edge_source_entity_id">DATA_EMPLOYER_SIGNATURE_PIN</data><data key="edge_relationship_type">issued_through</data><data key="edge_target_entity_id">PROC_BSO_AUTHORIZATION</data><data key="edge_operational_context">The planned Employer Signature PIN will be available through the updated BSO authorization system/process.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R35REL032" source="DATA_EMPLOYER_SIGNATURE_PIN" target="PLAT_BSO"><data key="edge_relationship_id">R35REL032</data><data key="edge_source_entity_id">DATA_EMPLOYER_SIGNATURE_PIN</data><data key="edge_relationship_type">authorizes_wage_submission_through</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">Organizations may opt to use the planned PIN to electronically sign wage reports submitted through BSO.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R36REL001" source="EX_EAB" target="PROC_AUTO_ENUM_SCREEN"><data key="edge_relationship_id">R36REL001</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">processed_by</data><data key="edge_target_entity_id">PROC_AUTO_ENUM_SCREEN</data><data key="edge_operational_context">OIG identifies parent requests for newborn SSNs during hospital birth registration as program information submitted through the Automated Enumeration Screening Process.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical processing relationship; transport and software boundary are not disclosed.</data></edge><edge id="R36REL002" source="ORG_DHS" target="PROC_AUTO_ENUM_SCREEN"><data key="edge_relationship_id">R36REL002</data><data key="edge_source_entity_id">ORG_DHS</data><data key="edge_relationship_type">submits_ssn_application_data_to</data><data key="edge_target_entity_id">PROC_AUTO_ENUM_SCREEN</data><data key="edge_operational_context">OIG identifies DHS applications for new and replacement SSNs as program information submitted through the Automated Enumeration Screening Process.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Does not identify the DHS source system or protocol.</data></edge><edge id="R36REL003" source="PROC_AUTO_ENUM_SCREEN" target="SYS_NUMIDENT"><data key="edge_relationship_id">R36REL003</data><data key="edge_source_entity_id">PROC_AUTO_ENUM_SCREEN</data><data key="edge_relationship_type">verifies_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG classifies the Automated Enumeration Screening Process as a Numident verification system.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Exact match fields/tolerances and implementation are not inferred.</data></edge><edge id="R36REL004" source="PROC_AWR" target="APP_SSN_NAME_VALID"><data key="edge_relationship_id">R36REL004</data><data key="edge_source_entity_id">PROC_AWR</data><data key="edge_relationship_type">feeds_wage_reports_to</data><data key="edge_target_entity_id">APP_SSN_NAME_VALID</data><data key="edge_operational_context">OIG Appendix A identifies employers wages as program information processed by the Social Security Number Name Validation System.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Annual Wage Reporting is used as the Atlas business-process endpoint for employer wage reports; no direct API is inferred.</data></edge><edge id="R36REL005" source="ORG_IRS" target="APP_SSN_NAME_VALID"><data key="edge_relationship_id">R36REL005</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">provides_self_employment_income_to</data><data key="edge_target_entity_id">APP_SSN_NAME_VALID</data><data key="edge_operational_context">OIG Appendix A identifies IRS self-employment income as program information processed by the Social Security Number Name Validation System.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Transmission mechanism is not identified.</data></edge><edge id="R36REL006" source="APP_SSN_NAME_VALID" target="SYS_NUMIDENT"><data key="edge_relationship_id">R36REL006</data><data key="edge_source_entity_id">APP_SSN_NAME_VALID</data><data key="edge_relationship_type">verifies_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG classifies SSN Name Validation as a Numident verification system for earnings reports.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Matching criteria vary from other Numident verification systems.</data></edge><edge id="R36REL007" source="APP_SSN_NAME_VALID" target="DB_ESF"><data key="edge_relationship_id">R36REL007</data><data key="edge_source_entity_id">APP_SSN_NAME_VALID</data><data key="edge_relationship_type">routes_unmatched_wages_to</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">When earnings reports do not match the Numident, the SSN Name Validation System places wage information in the Earnings Suspense File.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented by OIG.</data></edge><edge id="R36REL008" source="DB_ESF" target="APP_SSN_NAME_VALID"><data key="edge_relationship_id">R36REL008</data><data key="edge_source_entity_id">DB_ESF</data><data key="edge_relationship_type">reprocessed_through</data><data key="edge_target_entity_id">APP_SSN_NAME_VALID</data><data key="edge_operational_context">SSA later re-submits wage reports in the Earnings Suspense File through the SSN Name Validation System to test whether later Numident name changes allow a match.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Cadence is not specified.</data></edge><edge id="R36REL009" source="PROC_ENH_WAGE_VERIFY" target="DB_ESF"><data key="edge_relationship_id">R36REL009</data><data key="edge_source_entity_id">PROC_ENH_WAGE_VERIFY</data><data key="edge_relationship_type">analyzes_unmatched_wages_from</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">The enhanced wage verification program applies additional criteria to wage reports the SSN Name Validation System did not match; OIG describes annual analysis of wages from three years earlier.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Business-process relationship; implementation technology is unknown.</data></edge><edge id="R36REL010" source="PROC_ENH_WAGE_VERIFY" target="SYS_NUMIDENT"><data key="edge_relationship_id">R36REL010</data><data key="edge_source_entity_id">PROC_ENH_WAGE_VERIFY</data><data key="edge_relationship_type">verifies_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG describes enhanced wage verification as applying additional matching criteria to wage reports not matched to the Numident.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">The report does not identify this as a separately deployed application.</data></edge><edge id="R36REL011" source="PROC_ENH_WAGE_VERIFY" target="SYS_MEF"><data key="edge_relationship_id">R36REL011</data><data key="edge_source_entity_id">PROC_ENH_WAGE_VERIFY</data><data key="edge_relationship_type">posts_matched_wages_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">OIG states the enhanced wage verification program posts matched wage reports to the Master Earnings File.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented business/data result.</data></edge><edge id="R36REL012" source="ORG_STATE_BVS" target="EXT_STATE_EBR"><data key="edge_relationship_id">R36REL012</data><data key="edge_source_entity_id">ORG_STATE_BVS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">EXT_STATE_EBR</data><data key="edge_operational_context">OIG states facility staff or licensed midwives enter newborn information into the state Electronic Birth Registration system and each state Bureau of Vital Statistics receives and registers the birth information.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Represents the state-system family, not a single national application.</data></edge><edge id="R36REL013" source="EXT_STATE_EBR" target="EX_EAB"><data key="edge_relationship_id">R36REL013</data><data key="edge_source_entity_id">EXT_STATE_EBR</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">EX_EAB</data><data key="edge_operational_context">State electronic birth-registration data is the source of newborn information transmitted under the Enumeration at Birth program.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No common state technology stack or protocol is inferred.</data></edge><edge id="R36REL014" source="EX_EAB" target="FAC_NCC"><data key="edge_relationship_id">R36REL014</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">received_at</data><data key="edge_target_entity_id">FAC_NCC</data><data key="edge_operational_context">September 2026 OIG states the state transmits child birth information to SSA's National Computer Center through secure electronic interfaces.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">The current OIG terminology conflicts with older evidence that the National Support Center replaced the aging NCC facility; this relation records the 2026 source wording without asserting the physical hosting boundary.</data></edge><edge id="R36REL015" source="SVC_DNP" target="ORG_BFS"><data key="edge_relationship_id">R36REL015</data><data key="edge_source_entity_id">SVC_DNP</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Treasury Bureau of the Fiscal Service publishes and operates Do Not Pay payment-integrity services.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">External Treasury shared service.</data></edge><edge id="R36REL016" source="SVC_DNP" target="SVC_DNP_CONNECT"><data key="edge_relationship_id">R36REL016</data><data key="edge_source_entity_id">SVC_DNP</data><data key="edge_relationship_type">has_product</data><data key="edge_target_entity_id">SVC_DNP_CONNECT</data><data key="edge_operational_context">Treasury lists Do Not Pay Connect as a secure API product for direct system-to-system access.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R36REL017" source="SVC_DNP" target="SVC_DNP_WEB"><data key="edge_relationship_id">R36REL017</data><data key="edge_source_entity_id">SVC_DNP</data><data key="edge_relationship_type">has_product</data><data key="edge_target_entity_id">SVC_DNP_WEB</data><data key="edge_operational_context">Treasury lists the Do Not Pay Web Portal as an on-demand web access product.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R36REL018" source="SVC_DNP" target="SVC_TREASURY_PAYMENT_VERIFICATION"><data key="edge_relationship_id">R36REL018</data><data key="edge_source_entity_id">SVC_DNP</data><data key="edge_relationship_type">has_product</data><data key="edge_target_entity_id">SVC_TREASURY_PAYMENT_VERIFICATION</data><data key="edge_operational_context">Treasury documents Payment Verification within the Do Not Pay product suite for automatic screening of Treasury disbursements.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R36REL019" source="SVC_DNP" target="SVC_PARIS"><data key="edge_relationship_id">R36REL019</data><data key="edge_source_entity_id">SVC_DNP</data><data key="edge_relationship_type">provides_technical_service_for</data><data key="edge_target_entity_id">SVC_PARIS</data><data key="edge_operational_context">Treasury states Do Not Pay serves as the technical service provider for PARIS, which is administered by HHS Administration for Children and Families.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">PARIS is not treated as Treasury-owned merely because DNP supplies technical service.</data></edge><edge id="R36REL020" source="DATA_DMF" target="SVC_DNP_CONNECT"><data key="edge_relationship_id">R36REL020</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">available_via</data><data key="edge_target_entity_id">SVC_DNP_CONNECT</data><data key="edge_operational_context">Treasury lists SSA Death Master File Full as available through Do Not Pay Connect.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R36REL021" source="DATA_DMF" target="SVC_DNP_WEB"><data key="edge_relationship_id">R36REL021</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">available_via</data><data key="edge_target_entity_id">SVC_DNP_WEB</data><data key="edge_operational_context">Treasury lists SSA Death Master File Full as available through the Do Not Pay Web Portal.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R36REL022" source="DATA_DMF" target="SVC_TREASURY_PAYMENT_VERIFICATION"><data key="edge_relationship_id">R36REL022</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">available_via</data><data key="edge_target_entity_id">SVC_TREASURY_PAYMENT_VERIFICATION</data><data key="edge_operational_context">Treasury lists SSA Death Master File Full as available through Payment Verification.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R36REL023" source="DATA_DMF" target="SVC_PARIS"><data key="edge_relationship_id">R36REL023</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">available_via</data><data key="edge_target_entity_id">SVC_PARIS</data><data key="edge_operational_context">Treasury lists SSA Death Master File Full as available through PARIS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data></edge><edge id="R36REL024" source="SYS_NUMIDENT" target="SVC_TREASURY_PAYMENT_VERIFICATION"><data key="edge_relationship_id">R36REL024</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">available_via_select_programs</data><data key="edge_target_entity_id">SVC_TREASURY_PAYMENT_VERIFICATION</data><data key="edge_operational_context">Treasury lists Numident as available through Payment Verification for select programs.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">The specific programs are not identified on the public page.</data></edge><edge id="R36REL025" source="SYS_NUMIDENT" target="SVC_DNP_CONNECT"><data key="edge_relationship_id">R36REL025</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">planned_for</data><data key="edge_target_entity_id">SVC_DNP_CONNECT</data><data key="edge_operational_context">Treasury lists Numident availability in Do Not Pay Connect as coming soon for select programs.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Future-state relationship only; not modeled as a deployed API exchange.</data></edge><edge id="R36REL026" source="SYS_NUMIDENT" target="SVC_PARIS"><data key="edge_relationship_id">R36REL026</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">product_availability_listed_in</data><data key="edge_target_entity_id">SVC_PARIS</data><data key="edge_operational_context">Treasury lists Numident in PARIS product availability while separately marking state agency usage as coming soon through PARIS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Does not assert that state agencies currently receive Numident through PARIS.</data></edge><edge id="R36REL027" source="DATA_SSA_INCARCERATION_DNP" target="SVC_DNP_CONNECT"><data key="edge_relationship_id">R36REL027</data><data key="edge_source_entity_id">DATA_SSA_INCARCERATION_DNP</data><data key="edge_relationship_type">planned_for</data><data key="edge_target_entity_id">SVC_DNP_CONNECT</data><data key="edge_operational_context">Treasury lists SSA Incarceration Data for Do Not Pay Connect while marking federal and state usage as coming soon.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Future-state availability only.</data></edge><edge id="R36REL028" source="FORM_SSA1372" target="SYS_MBR"><data key="edge_relationship_id">R36REL028</data><data key="edge_source_entity_id">FORM_SSA1372</data><data key="edge_relationship_type">eligibility_information_reflected_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">OIG matched school-attendance information on Form SSA-1372 or other school records to school-attendance information in the Master Beneficiary Record; termination dates in MBR drive student-benefit periods.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">This does not establish an automated form-to-MBR interface.</data></edge><edge id="R36REL029" source="FORM_SSA1372" target="APP_EP"><data key="edge_relationship_id">R36REL029</data><data key="edge_source_entity_id">FORM_SSA1372</data><data key="edge_relationship_type">retention_evidence_reviewed_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">OIG queried Evidence Portal, along with MBR, to determine whether SSA retained adequate supporting documentation for student benefit payments.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Evidence that EP is used to evaluate retention; not proof that every SSA-1372 is always stored there.</data></edge><edge id="R36REL030" source="PROC_SSI_UNDERPAY_PREPAY_REVIEW" target="SYS_SSR"><data key="edge_relationship_id">R36REL030</data><data key="edge_source_entity_id">PROC_SSI_UNDERPAY_PREPAY_REVIEW</data><data key="edge_relationship_type">reviews_underpayments_recorded_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">OIG describes SSI underpayments as changes/pending amounts on the Supplemental Security Record and requires secondary review before large underpayments are released.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">The report documents business processing, not a separate review application.</data></edge><edge id="R36REL031" source="PROC_SSI_UNDERPAY_PREPAY_REVIEW" target="DATA_SSI_UNDERPAY_CTRL_LOG"><data key="edge_relationship_id">R36REL031</data><data key="edge_source_entity_id">PROC_SSI_UNDERPAY_PREPAY_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_SSI_UNDERPAY_CTRL_LOG</data><data key="edge_operational_context">SSA employees must manually track large underpayments in the SSI Underpayment Control Log while conducting required pre-payment review.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Manual work-control relationship.</data></edge><edge id="R36REL032" source="DATA_SSI_UNDERPAY_CTRL_LOG" target="SYS_SSR"><data key="edge_relationship_id">R36REL032</data><data key="edge_source_entity_id">DATA_SSI_UNDERPAY_CTRL_LOG</data><data key="edge_relationship_type">tracks_large_underpayments_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">OIG identifies large underpayments pending on the SSR and states employees manually track those requiring pre-payment review in the SSI Underpayment Control Log.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No implementation technology for the log is inferred.</data></edge><edge id="R37REL001" source="COMP_STC" target="TECH_MFT"><data key="edge_relationship_id">R37REL001</data><data key="edge_source_entity_id">COMP_STC</data><data key="edge_relationship_type">includes_software_component</data><data key="edge_target_entity_id">TECH_MFT</data><data key="edge_operational_context">SSA describes the State Transmission Component as including an MFT software license/configuration used for state data transfers.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Physical server topology and product version are not disclosed.</data></edge><edge id="R37REL002" source="COMP_STC" target="TECH_STC_VPN"><data key="edge_relationship_id">R37REL002</data><data key="edge_source_entity_id">COMP_STC</data><data key="edge_relationship_type">includes_secure_network_component</data><data key="edge_target_entity_id">TECH_STC_VPN</data><data key="edge_operational_context">SSA describes the STC as comprising the direct VPN connection plus MFT software configuration.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Specific VPN technology is not disclosed.</data></edge><edge id="R37REL003" source="TECH_MFT" target="ORG_TIBCO"><data key="edge_relationship_id">R37REL003</data><data key="edge_source_entity_id">TECH_MFT</data><data key="edge_relationship_type">developed_and_supported_by</data><data key="edge_target_entity_id">ORG_TIBCO</data><data key="edge_operational_context">SSA identifies TIBCO as the developer/support provider and licensor of MFT.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Current contract vehicle is not established by the cited source.</data></edge><edge id="R37REL004" source="EX_EAB" target="TECH_MFT"><data key="edge_relationship_id">R37REL004</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">transmitted_via</data><data key="edge_target_entity_id">TECH_MFT</data><data key="edge_operational_context">SSA EAB technical guidance identifies MFT as one of the two EAB file-transmission options used by participating state vital-records agencies.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Transmission choice depends on state/jurisdiction technical capabilities.</data></edge><edge id="R37REL005" source="EX_EAB" target="APP_GSO"><data key="edge_relationship_id">R37REL005</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">transmitted_via</data><data key="edge_target_entity_id">APP_GSO</data><data key="edge_operational_context">SSA EAB technical guidance identifies Government Services Online as the alternative EAB transmission option to MFT.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">The guide describes PC-to-mainframe/mainframe-to-PC transmission over the secure GSO exchange; no further internal topology is inferred.</data></edge><edge id="R37REL006" source="PORTAL_SSA_DIGITAL_LIBRARY" target="SVC_JD_POWER_VALUES"><data key="edge_relationship_id">R37REL006</data><data key="edge_source_entity_id">PORTAL_SSA_DIGITAL_LIBRARY</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">SVC_JD_POWER_VALUES</data><data key="edge_operational_context">POMS instructs non-SSI Claims system users to reach J.D. Power Values Online from the SSA Digital Library Electronic Resources Site.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Access-control and federation details are not public.</data></edge><edge id="R37REL007" source="APP_SSI_CLAIMS_LOGICAL" target="SVC_JD_POWER_VALUES"><data key="edge_relationship_id">R37REL007</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">links_to</data><data key="edge_target_entity_id">SVC_JD_POWER_VALUES</data><data key="edge_operational_context">POMS says users in the SSI Claims system select a link on the Vehicle page to access J.D. Power Values Online.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical user-interface relationship; no API or data integration is asserted.</data></edge><edge id="R37REL008" source="APP_I3368PRO" target="APP_I3368"><data key="edge_relationship_id">R37REL008</data><data key="edge_source_entity_id">APP_I3368PRO</data><data key="edge_relationship_type">professional_variant_of</data><data key="edge_target_entity_id">APP_I3368</data><data key="edge_operational_context">POMS and SSA Developers Support describe i3368PRO as the professional-user version of the adult Internet disability report.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Backend reuse is not inferred beyond the documented product family relationship.</data></edge><edge id="R37REL009" source="ORG_INSIDER_THREAT_RESILIENCY" target="ORG_SECURITY_RESILIENCY"><data key="edge_relationship_id">R37REL009</data><data key="edge_source_entity_id">ORG_INSIDER_THREAT_RESILIENCY</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">ORG_SECURITY_RESILIENCY</data><data key="edge_operational_context">OIG identifies the Office of Insider Threat and Resiliency within the Office of Security and Resiliency.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R37REL010" source="PROC_INSIDER_THREAT_PROGRAM" target="ORG_INSIDER_THREAT_RESILIENCY"><data key="edge_relationship_id">R37REL010</data><data key="edge_source_entity_id">PROC_INSIDER_THREAT_PROGRAM</data><data key="edge_relationship_type">managed_by</data><data key="edge_target_entity_id">ORG_INSIDER_THREAT_RESILIENCY</data><data key="edge_operational_context">OIG reviewed the Office of Insider Threat and Resiliency as the principal entity responsible for SSA’s Insider Threat Program.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes">Sensitive operational details are excluded from the public report.</data></edge><edge id="R37REL011" source="ALERT_REENTITLED_OVERPAYMENT" target="PROC_CONTINGENT_LIABILITY_RECOVERY"><data key="edge_relationship_id">R37REL011</data><data key="edge_source_entity_id">ALERT_REENTITLED_OVERPAYMENT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_CONTINGENT_LIABILITY_RECOVERY</data><data key="edge_operational_context">The annual alert notifies employees when OASDI benefits on a separate record may be withheld to recover an overpayment.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R37REL012" source="ALERT_CONTINGENT_LIABLE_OVERPAYMENT" target="PROC_CONTINGENT_LIABILITY_RECOVERY"><data key="edge_relationship_id">R37REL012</data><data key="edge_source_entity_id">ALERT_CONTINGENT_LIABLE_OVERPAYMENT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_CONTINGENT_LIABILITY_RECOVERY</data><data key="edge_operational_context">The annual alert notifies employees when a same-household contingently liable beneficiary may be subject to benefit withholding.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R37REL013" source="APP_ECO" target="PROC_CONTINGENT_LIABILITY_RECOVERY"><data key="edge_relationship_id">R37REL013</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">supports_external_collection_phase_of</data><data key="edge_target_entity_id">PROC_CONTINGENT_LIABILITY_RECOVERY</data><data key="edge_operational_context">OIG documents ECO selecting qualifying delinquent overpayments and referring eligible debts for Treasury tax-refund offset after notice and waiting-period requirements.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes">Does not imply ECO generates the annual contingent-liability alerts.</data></edge><edge id="R37REL014" source="SVC_TOP" target="PROC_CONTINGENT_LIABILITY_RECOVERY"><data key="edge_relationship_id">R37REL014</data><data key="edge_source_entity_id">SVC_TOP</data><data key="edge_relationship_type">supports_external_collection_phase_of</data><data key="edge_target_entity_id">PROC_CONTINGENT_LIABILITY_RECOVERY</data><data key="edge_operational_context">OIG documents Treasury Offset Program tax-refund offsets as an external collection path for delinquent SSA overpayments.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R37REL015" source="QRY_COLLECTION" target="PROC_CONTINGENT_LIABILITY_RECOVERY"><data key="edge_relationship_id">R37REL015</data><data key="edge_source_entity_id">QRY_COLLECTION</data><data key="edge_relationship_type">supports_case_review_for</data><data key="edge_target_entity_id">PROC_CONTINGENT_LIABILITY_RECOVERY</data><data key="edge_operational_context">OIG used Collection Query alongside MBR, ROAR, PHUS, SSR, and Evidence Portal when reviewing overpayment/TOP cases.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">4</data><data key="edge_notes">The public report does not establish the query’s backend or direct system interfaces.</data></edge><edge id="R38REL001" source="ORG_IT_IRB" target="PROC_CPIC"><data key="edge_relationship_id">R38REL001</data><data key="edge_source_entity_id">ORG_IT_IRB</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_CPIC</data><data key="edge_operational_context">OIG states the IT IRB governs SSA’s IT investment and management process.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL002" source="PROC_CPIC" target="APP_IT_INVESTMENT_MGMT_TOOL"><data key="edge_relationship_id">R38REL002</data><data key="edge_source_entity_id">PROC_CPIC</data><data key="edge_relationship_type">uses_portfolio_data_from</data><data key="edge_target_entity_id">APP_IT_INVESTMENT_MGMT_TOOL</data><data key="edge_operational_context">OIG describes SSA’s Investment Management Tool as the source/tracker for investment and risk information used in investment-management controls.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">No product integration or technical interface is inferred.</data></edge><edge id="R38REL003" source="APP_IT_INVESTMENT_MGMT_TOOL" target="PROJ_BI_TOOL_MIGRATION"><data key="edge_relationship_id">R38REL003</data><data key="edge_source_entity_id">APP_IT_INVESTMENT_MGMT_TOOL</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">PROJ_BI_TOOL_MIGRATION</data><data key="edge_operational_context">OIG used SSA investment-management data for this sampled discontinued investment.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL004" source="APP_IT_INVESTMENT_MGMT_TOOL" target="PROJ_ESERVICES_ENTERPRISE_API"><data key="edge_relationship_id">R38REL004</data><data key="edge_source_entity_id">APP_IT_INVESTMENT_MGMT_TOOL</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">PROJ_ESERVICES_ENTERPRISE_API</data><data key="edge_operational_context">OIG used SSA investment-management data for this sampled discontinued investment.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL005" source="APP_IT_INVESTMENT_MGMT_TOOL" target="PROJ_DMP"><data key="edge_relationship_id">R38REL005</data><data key="edge_source_entity_id">APP_IT_INVESTMENT_MGMT_TOOL</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">PROJ_DMP</data><data key="edge_operational_context">OIG used SSA investment-management data for this sampled investment and reports DMP was placed on hold in FY2026.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL006" source="APP_IT_INVESTMENT_MGMT_TOOL" target="PROJ_RCIRP"><data key="edge_relationship_id">R38REL006</data><data key="edge_source_entity_id">APP_IT_INVESTMENT_MGMT_TOOL</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">PROJ_RCIRP</data><data key="edge_operational_context">OIG used SSA investment-management data for this sampled discontinued investment.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL007" source="ORG_IT_IRB" target="PROJ_BI_TOOL_MIGRATION"><data key="edge_relationship_id">R38REL007</data><data key="edge_source_entity_id">ORG_IT_IRB</data><data key="edge_relationship_type">makes_funding_decisions_for</data><data key="edge_target_entity_id">PROJ_BI_TOOL_MIGRATION</data><data key="edge_operational_context">OIG reviewed relevant IT IRB decision records for sampled investments; IT IRB votes on which investments to fund.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Does not assert the exact meeting/date at which cancellation occurred.</data></edge><edge id="R38REL008" source="ORG_IT_IRB" target="PROJ_ESERVICES_ENTERPRISE_API"><data key="edge_relationship_id">R38REL008</data><data key="edge_source_entity_id">ORG_IT_IRB</data><data key="edge_relationship_type">makes_funding_decisions_for</data><data key="edge_target_entity_id">PROJ_ESERVICES_ENTERPRISE_API</data><data key="edge_operational_context">OIG reviewed relevant IT IRB decision records for sampled investments; IT IRB votes on which investments to fund.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Does not assert the exact meeting/date at which cancellation occurred.</data></edge><edge id="R38REL009" source="ORG_IT_IRB" target="PROJ_DMP"><data key="edge_relationship_id">R38REL009</data><data key="edge_source_entity_id">ORG_IT_IRB</data><data key="edge_relationship_type">makes_funding_decisions_for</data><data key="edge_target_entity_id">PROJ_DMP</data><data key="edge_operational_context">OIG states investments the IT IRB does not fund may be placed on hold; DMP was placed on hold in FY2026.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Public report does not quote the exact DMP IRB vote record.</data></edge><edge id="R38REL010" source="ORG_IT_IRB" target="PROJ_RCIRP"><data key="edge_relationship_id">R38REL010</data><data key="edge_source_entity_id">ORG_IT_IRB</data><data key="edge_relationship_type">defunded_except_contractor_support</data><data key="edge_target_entity_id">PROJ_RCIRP</data><data key="edge_operational_context">OIG states the IT IRB voted to defund rCIRP except for contractor support in FY2022.</data><data key="edge_observed_as_of">2022</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL011" source="PROJ_RCIRP" target="APP_CIRP"><data key="edge_relationship_id">R38REL011</data><data key="edge_source_entity_id">PROJ_RCIRP</data><data key="edge_relationship_type">reengineering_project_for</data><data key="edge_target_entity_id">APP_CIRP</data><data key="edge_operational_context">The investment name is Re-engineered Comprehensive Integrity Review Process and OIG says it ran in parallel with the legacy process before SSA reverted to that process.</data><data key="edge_observed_as_of">2022</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is process lineage, not a claimed software interface or exact codebase replacement.</data></edge><edge id="R38REL012" source="PORTAL_SUMS_MCAS_MI_CENTRAL" target="APP_UMS_MCAS"><data key="edge_relationship_id">R38REL012</data><data key="edge_source_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current POMS explicitly calls the portal SUMS/MCAS MI Central.</data><data key="edge_observed_as_of">2026-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL013" source="DB_SUMS_MCAS_RZLI_INTERFACE" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R38REL013</data><data key="edge_source_entity_id">DB_SUMS_MCAS_RZLI_INTERFACE</data><data key="edge_relationship_type">provides_alert_data_to</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">POMS says alert data are available on an interface database and retrievable through SUMS/MCAS MI Central.</data><data key="edge_observed_as_of">2026-07</data><data key="edge_confidence">5</data><data key="edge_notes">Database product and transport mechanism are not disclosed.</data></edge><edge id="R38REL014" source="UI_SUMS_MCAS_SSN_IRS_SSID_QUERY" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R38REL014</data><data key="edge_source_entity_id">UI_SUMS_MCAS_SSN_IRS_SSID_QUERY</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">POMS identifies the SSN/IRS/SSID Query Screen under the Workload Listing section of SUMS/MCAS MI Central.</data><data key="edge_observed_as_of">2026-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL015" source="UI_SUMS_MCAS_SSN_IRS_SSID_QUERY" target="DB_SUMS_MCAS_RZLI_INTERFACE"><data key="edge_relationship_id">R38REL015</data><data key="edge_source_entity_id">UI_SUMS_MCAS_SSN_IRS_SSID_QUERY</data><data key="edge_relationship_type">retrieves_alert_data_from</data><data key="edge_target_entity_id">DB_SUMS_MCAS_RZLI_INTERFACE</data><data key="edge_operational_context">POMS says alert data in the interface database are retrievable through this query screen.</data><data key="edge_observed_as_of">2026-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL016" source="APP_STATUTORY_BENEFIT_CONT" target="SYS_SSR"><data key="edge_relationship_id">R38REL016</data><data key="edge_source_entity_id">APP_STATUTORY_BENEFIT_CONT</data><data key="edge_relationship_type">controls_payment_continuation_cases_reflected_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says many N07/N08 payment-continuation cases are controlled via Statutory Benefit Continuation software and are in payment status C01; a K1 diary is on the SSR.</data><data key="edge_observed_as_of">2026-07</data><data key="edge_confidence">4</data><data key="edge_notes">Logical case-control relationship; no direct database interface is asserted.</data></edge><edge id="R38REL017" source="UI_ERPS_RPST" target="APP_ERPS"><data key="edge_relationship_id">R38REL017</data><data key="edge_source_entity_id">UI_ERPS_RPST</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies the RPST screen as part of the Representative Payee System/eRPS workflow.</data><data key="edge_observed_as_of">2026-07-15</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL018" source="ORG_DNB" target="UI_ERPS_RPST"><data key="edge_relationship_id">R38REL018</data><data key="edge_source_entity_id">ORG_DNB</data><data key="edge_relationship_type">provides_credit_information_for_decision_recorded_in</data><data key="edge_target_entity_id">UI_ERPS_RPST</data><data key="edge_operational_context">SSA obtains D&amp;B credit information for new nongovernmental fee-for-service payee applicants and directs staff to record the resulting suitability determination in RPST.</data><data key="edge_observed_as_of">2026-07-15</data><data key="edge_confidence">5</data><data key="edge_notes">Human-mediated review; not a direct D&amp;B-to-eRPS interface assertion.</data></edge><edge id="R38REL019" source="CAP_CLICK_SIGN" target="APP_ICLAIM"><data key="edge_relationship_id">R38REL019</data><data key="edge_source_entity_id">CAP_CLICK_SIGN</data><data key="edge_relationship_type">implemented_in</data><data key="edge_target_entity_id">APP_ICLAIM</data><data key="edge_operational_context">Current POMS describes Click-and-Sign as the electronic signing method at the conclusion of eligible iClaim applications.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL020" source="APP_ICLAIM" target="APP_MYSSA"><data key="edge_relationship_id">R38REL020</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">authenticates_first_party_claimants_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Current POMS says first-party iClaim users are routed to mySSA for authentication and identity verification.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL021" source="CAP_CLICK_SIGN" target="APP_MCS"><data key="edge_relationship_id">R38REL021</data><data key="edge_source_entity_id">CAP_CLICK_SIGN</data><data key="edge_relationship_type">records_internet_signature_marker_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS says the word Internet propagates to the appropriate MCS application/DW01 and the ATTEST issue is receipted for click-and-sign claims.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record propagation; no transport technology is inferred.</data></edge><edge id="R38REL022" source="APP_ICLAIM" target="APP_ORS"><data key="edge_relationship_id">R38REL022</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">stores_submitted_application_summary_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">POMS says after online application data are downloaded into MCS, ORS is automatically updated with a copy of the submitted Internet application summary.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes">The intermediate implementation is not public.</data></edge><edge id="R38REL023" source="ORG_SEWP_SOLUTIONS" target="CONTRACT_SEWP_NNG15SC19B"><data key="edge_relationship_id">R38REL023</data><data key="edge_source_entity_id">ORG_SEWP_SOLUTIONS</data><data key="edge_relationship_type">holds</data><data key="edge_target_entity_id">CONTRACT_SEWP_NNG15SC19B</data><data key="edge_operational_context">USAspending identifies SEWP Solutions LLC as the recipient of IDV NNG15SC19B.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL024" source="CONTRACT_SSA_28321326FDX030016" target="CONTRACT_SEWP_NNG15SC19B"><data key="edge_relationship_id">R38REL024</data><data key="edge_source_entity_id">CONTRACT_SSA_28321326FDX030016</data><data key="edge_relationship_type">issued_under</data><data key="edge_target_entity_id">CONTRACT_SEWP_NNG15SC19B</data><data key="edge_operational_context">USAspending lists the SSA delivery order among orders under NNG15SC19B.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL025" source="CONTRACT_SSA_28321324FDX030088" target="CONTRACT_SEWP_NNG15SC19B"><data key="edge_relationship_id">R38REL025</data><data key="edge_source_entity_id">CONTRACT_SSA_28321324FDX030088</data><data key="edge_relationship_type">issued_under</data><data key="edge_target_entity_id">CONTRACT_SEWP_NNG15SC19B</data><data key="edge_operational_context">USAspending lists the SSA delivery order among orders under NNG15SC19B.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL026" source="CONTRACT_SSA_28321326FDX030016" target="TECH_IBM_SUPER_SERVER"><data key="edge_relationship_id">R38REL026</data><data key="edge_source_entity_id">CONTRACT_SSA_28321326FDX030016</data><data key="edge_relationship_type">procures</data><data key="edge_target_entity_id">TECH_IBM_SUPER_SERVER</data><data key="edge_operational_context">The 2026 SSA order description is for IBM Super Server appliances.</data><data key="edge_observed_as_of">2026-02-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL027" source="TECH_IBM_SUPER_SERVER" target="FAC_SSC"><data key="edge_relationship_id">R38REL027</data><data key="edge_source_entity_id">TECH_IBM_SUPER_SERVER</data><data key="edge_relationship_type">supports_facility</data><data key="edge_target_entity_id">FAC_SSC</data><data key="edge_operational_context">Award description says the IBM Super Server appliances support the Second Support Center.</data><data key="edge_observed_as_of">2026-02-09</data><data key="edge_confidence">5</data><data key="edge_notes">Exact rack, network, and application topology are not public.</data></edge><edge id="R38REL028" source="TECH_IBM_SUPER_SERVER" target="FAC_NSC"><data key="edge_relationship_id">R38REL028</data><data key="edge_source_entity_id">TECH_IBM_SUPER_SERVER</data><data key="edge_relationship_type">supports_facility</data><data key="edge_target_entity_id">FAC_NSC</data><data key="edge_operational_context">Award description says the IBM Super Server appliances support the National Support Center.</data><data key="edge_observed_as_of">2026-02-09</data><data key="edge_confidence">5</data><data key="edge_notes">Exact rack, network, and application topology are not public.</data></edge><edge id="R38REL029" source="TECH_IBM_SUPER_SERVER" target="ORG_IBM"><data key="edge_relationship_id">R38REL029</data><data key="edge_source_entity_id">TECH_IBM_SUPER_SERVER</data><data key="edge_relationship_type">manufactured_by</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">Award description identifies the appliances as IBM servers.</data><data key="edge_observed_as_of">2026-02-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL030" source="CONTRACT_SSA_28321324FDX030088" target="TECH_IBM_POWER10"><data key="edge_relationship_id">R38REL030</data><data key="edge_source_entity_id">CONTRACT_SSA_28321324FDX030088</data><data key="edge_relationship_type">procures</data><data key="edge_target_entity_id">TECH_IBM_POWER10</data><data key="edge_operational_context">The 2024 SSA order description says it procures IBM Power10 at SSC.</data><data key="edge_observed_as_of">2024-04-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL031" source="TECH_IBM_POWER10" target="FAC_SSC"><data key="edge_relationship_id">R38REL031</data><data key="edge_source_entity_id">TECH_IBM_POWER10</data><data key="edge_relationship_type">procured_for</data><data key="edge_target_entity_id">FAC_SSC</data><data key="edge_operational_context">USAspending order description explicitly places the Power10 procurement at the Second Support Center.</data><data key="edge_observed_as_of">2024-04-11</data><data key="edge_confidence">5</data><data key="edge_notes">Procurement intent does not establish exact installation date.</data></edge><edge id="R38REL032" source="TECH_IBM_POWER10" target="TECH_IBM_POWER8"><data key="edge_relationship_id">R38REL032</data><data key="edge_source_entity_id">TECH_IBM_POWER10</data><data key="edge_relationship_type">upgrades</data><data key="edge_target_entity_id">TECH_IBM_POWER8</data><data key="edge_operational_context">USAspending states the Power10 was procured to upgrade the existing IBM Power8.</data><data key="edge_observed_as_of">2024-04-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL033" source="TECH_IBM_POWER10" target="ORG_IBM"><data key="edge_relationship_id">R38REL033</data><data key="edge_source_entity_id">TECH_IBM_POWER10</data><data key="edge_relationship_type">manufactured_by</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">Award description identifies the product as IBM Power10.</data><data key="edge_observed_as_of">2024-04-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R38REL034" source="TECH_IBM_POWER8" target="ORG_IBM"><data key="edge_relationship_id">R38REL034</data><data key="edge_source_entity_id">TECH_IBM_POWER8</data><data key="edge_relationship_type">manufactured_by</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">Award description identifies the existing upgrade target as IBM Power8.</data><data key="edge_observed_as_of">2024-04-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R39REL001" source="APP_SOLQ" target="EX_SOLQ"><data key="edge_relationship_id">R39REL001</data><data key="edge_source_entity_id">APP_SOLQ</data><data key="edge_relationship_type">mainframe_variant_of</data><data key="edge_target_entity_id">EX_SOLQ</data><data key="edge_operational_context">Current POMS distinguishes SOLQ as an online exchange typically used with States in a mainframe, while SOLQ-I is web-based.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical implementation relationship only; no specific mainframe platform or transport protocol is inferred.</data></edge><edge id="R39REL002" source="EX_MEDICARE1144" target="ORG_STATES"><data key="edge_relationship_id">R39REL002</data><data key="edge_source_entity_id">EX_MEDICARE1144</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Medicare 1144 provides approved State agencies lists for administration of the Section 1144 outreach program.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Partner scope includes approved State agencies; current outreach POMS specifically refers to State Medicaid agencies for annual lists.</data></edge><edge id="R39REL003" source="EX_MEDICARE1144" target="DOM_MEDICARE"><data key="edge_relationship_id">R39REL003</data><data key="edge_source_entity_id">EX_MEDICARE1144</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">Batch exchange provides candidate information for Medicare cost-sharing, transitional assistance, and low-income subsidy outreach.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Data-domain relationship; no schema or file layout inferred.</data></edge><edge id="R39REL004" source="PROC_MSP_OUTREACH" target="EX_MEDICARE1144"><data key="edge_relationship_id">R39REL004</data><data key="edge_source_entity_id">PROC_MSP_OUTREACH</data><data key="edge_relationship_type">shares_state_lists_via</data><data key="edge_target_entity_id">EX_MEDICARE1144</data><data key="edge_operational_context">SSA annually identifies potential MSP/Extra Help eligibles and electronically shares State lists; separate POMS identifies Medicare 1144 as the batch system for this outreach program.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Cross-source logical mapping. Exact internal file name, staging repository, and transmission cadence beyond the annual outreach process are not established.</data></edge><edge id="R39REL005" source="SVC_PRIVACY_RECORD_ACCESS" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R39REL005</data><data key="edge_source_entity_id">SVC_PRIVACY_RECORD_ACCESS</data><data key="edge_relationship_type">uses_submission_channel</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current Forms catalog routes SSA-2288-OP1 to the shared eSubmit/Upload Documents completeOnline start path.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Channel relationship; does not identify downstream workflow or repository.</data></edge><edge id="R39REL006" source="SVC_PRIVACY_RECORD_ACCESS" target="DB_CLAIMS_FOLDERS_SYSTEM"><data key="edge_relationship_id">R39REL006</data><data key="edge_source_entity_id">SVC_PRIVACY_RECORD_ACCESS</data><data key="edge_relationship_type">provides_record_access_for</data><data key="edge_target_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="edge_operational_context">SSA electronic-access page identifies Claims Folders System (60-0089) among systems whose eligible records may be requested electronically.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Business/data-scope relationship; no technical retrieval interface is inferred.</data></edge><edge id="R39REL007" source="SVC_PRIVACY_RECORD_ACCESS" target="SYS_MBR"><data key="edge_relationship_id">R39REL007</data><data key="edge_source_entity_id">SVC_PRIVACY_RECORD_ACCESS</data><data key="edge_relationship_type">provides_record_access_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA electronic-access page identifies Master Beneficiary Record (60-0090) among systems whose eligible records may be requested electronically.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Business/data-scope relationship; no technical retrieval interface is inferred.</data></edge><edge id="R39REL008" source="SVC_PRIVACY_RECORD_ACCESS" target="SYS_SSR"><data key="edge_relationship_id">R39REL008</data><data key="edge_source_entity_id">SVC_PRIVACY_RECORD_ACCESS</data><data key="edge_relationship_type">provides_record_access_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA electronic-access page identifies Supplemental Security Income Record and Special Veterans Benefits (60-0103) among systems whose eligible records may be requested electronically.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Business/data-scope relationship; no technical retrieval interface is inferred.</data></edge><edge id="R39REL009" source="SVC_PRIVACY_RECORD_ACCESS" target="DB_EDIB_CLAIM_FILE"><data key="edge_relationship_id">R39REL009</data><data key="edge_source_entity_id">SVC_PRIVACY_RECORD_ACCESS</data><data key="edge_relationship_type">provides_record_access_for</data><data key="edge_target_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_operational_context">SSA electronic-access page identifies Electronic Disability (eDIB) Claim File (60-0320) among systems whose eligible records may be requested electronically.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Business/data-scope relationship; no technical retrieval interface is inferred.</data></edge><edge id="R39REL010" source="SVC_PRIVACY_CONSENT" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R39REL010</data><data key="edge_source_entity_id">SVC_PRIVACY_CONSENT</data><data key="edge_relationship_type">uses_submission_channel</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current Forms catalog routes SSA-3288-OP1 to the shared eSubmit/Upload Documents completeOnline start path.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Channel relationship; no downstream workflow or repository is inferred.</data></edge><edge id="R39REL011" source="SVC_PRIVACY_CONSENT" target="DOM_SSNV"><data key="edge_relationship_id">R39REL011</data><data key="edge_source_entity_id">SVC_PRIVACY_CONSENT</data><data key="edge_relationship_type">supports_disclosure_of</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">SSA electronic-consent page lists verification of Social Security number among records eligible for electronic consent.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Data-scope relationship, not a direct system interface.</data></edge><edge id="R39REL012" source="SVC_PRIVACY_CONSENT" target="DOM_TITLE2"><data key="edge_relationship_id">R39REL012</data><data key="edge_source_entity_id">SVC_PRIVACY_CONSENT</data><data key="edge_relationship_type">supports_disclosure_of</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">SSA electronic-consent page permits consent for benefit/payment amount and benefit-related records.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Logical Title II data-scope mapping; public page does not name a specific source system for this consent service.</data></edge><edge id="R39REL013" source="SVC_PRIVACY_CONSENT" target="DOM_TITLE16"><data key="edge_relationship_id">R39REL013</data><data key="edge_source_entity_id">SVC_PRIVACY_CONSENT</data><data key="edge_relationship_type">supports_disclosure_of</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">SSA electronic-consent page permits consent for benefit/payment amount and benefit-related records.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Logical Title XVI data-scope mapping; public page does not name a specific source system for this consent service.</data></edge><edge id="R39REL014" source="SVC_PRIVACY_CONSENT" target="DOM_MEDICARE"><data key="edge_relationship_id">R39REL014</data><data key="edge_source_entity_id">SVC_PRIVACY_CONSENT</data><data key="edge_relationship_type">supports_disclosure_of</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">SSA electronic-consent page explicitly lists Medicare entitlement among records eligible for electronic consent.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Data-scope relationship, not a direct system interface.</data></edge><edge id="R39REL015" source="SVC_PRIVACY_CONSENT" target="DB_CLAIMS_FOLDERS_SYSTEM"><data key="edge_relationship_id">R39REL015</data><data key="edge_source_entity_id">SVC_PRIVACY_CONSENT</data><data key="edge_relationship_type">supports_disclosure_of</data><data key="edge_target_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="edge_operational_context">SSA electronic-consent page explicitly lists medical records from claims folders among eligible records.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">Logical record-scope relationship. The page does not name SORN 60-0089 on the consent page itself, so no technical source-system path is inferred.</data></edge><edge id="R39REL016" source="PROG_HRS" target="DATA_HRS_CONSENT_HISTORY"><data key="edge_relationship_id">R39REL016</data><data key="edge_source_entity_id">PROG_HRS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_HRS_CONSENT_HISTORY</data><data key="edge_operational_context">HRS produces derivative products from the linked administrative-data program, including the Cross-Wave Permissions Consent History.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data><data key="edge_notes">HRS-side research data product, not an SSA operational file.</data></edge><edge id="R39REL017" source="DATA_HRS_CONSENT_HISTORY" target="EX_HRS_LINKAGE"><data key="edge_relationship_id">R39REL017</data><data key="edge_source_entity_id">DATA_HRS_CONSENT_HISTORY</data><data key="edge_relationship_type">tracks_status_for</data><data key="edge_target_entity_id">EX_HRS_LINKAGE</data><data key="edge_operational_context">The file tracks respondent consent, transmission of properly completed consent to SSA, and whether respondents ultimately matched to SSA earnings and/or benefit files.</data><data key="edge_observed_as_of">2024-05-24</data><data key="edge_confidence">5</data><data key="edge_notes">Does not reveal SSA transfer protocol or internal match implementation.</data></edge><edge id="R39REL018" source="DB_IDMS" target="APP_PIV"><data key="edge_relationship_id">R39REL018</data><data key="edge_source_entity_id">DB_IDMS</data><data key="edge_relationship_type">historically_supported_records_for</data><data key="edge_target_entity_id">APP_PIV</data><data key="edge_operational_context">2012 PIV PIA says Identity Management System 60-0361 covers information related to issuing and maintaining PIV credentials and verifying/authenticating access to Federal resources.</data><data key="edge_observed_as_of">2012-08-01</data><data key="edge_confidence">5</data><data key="edge_notes">Historical relationship only. Current SORN catalog confirms IDMS still exists, but current PIV/IDMS implementation details are not inferred from the 2012 PIA.</data></edge><edge id="R40REL001" source="EX_CMA1038_BFS_SAVINGS" target="SYS_SSR"><data key="edge_relationship_id">R40REL001</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">posts_alert_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS says savings-security match alerts are posted to the Supplemental Security Record.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL002" source="EX_CMA1038_BFS_SAVINGS" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R40REL002</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">sets_work_control_in</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">Current POMS says match alerts are set on PE ODS after posting to SSR.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No internal transport or batch implementation inferred.</data></edge><edge id="R40REL003" source="DB_SSI_PE_ODS" target="ALERT_SSI_SAVINGS_SECURITY"><data key="edge_relationship_id">R40REL003</data><data key="edge_source_entity_id">DB_SSI_PE_ODS</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">ALERT_SSI_SAVINGS_SECURITY</data><data key="edge_operational_context">Current POMS says the system generates an SB alert controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL004" source="ALERT_SSI_SAVINGS_SECURITY" target="SYS_SSR"><data key="edge_relationship_id">R40REL004</data><data key="edge_source_entity_id">ALERT_SSI_SAVINGS_SECURITY</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The current POMS alert example and procedures identify the SSI/Savings Security Interface Alert with SSR record context.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Work-control relationship; not a separate physical database assertion.</data></edge><edge id="R40REL005" source="UI_MSSICS_DSAB" target="APP_MSSICS"><data key="edge_relationship_id">R40REL005</data><data key="edge_source_entity_id">UI_MSSICS_DSAB</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS identifies DSAB as an MSSICS Savings Bond Interface Development screen.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL006" source="UI_MSSICS_DSAB" target="ALERT_SSI_SAVINGS_SECURITY"><data key="edge_relationship_id">R40REL006</data><data key="edge_source_entity_id">UI_MSSICS_DSAB</data><data key="edge_relationship_type">documents_resolution_of</data><data key="edge_target_entity_id">ALERT_SSI_SAVINGS_SECURITY</data><data key="edge_operational_context">Current POMS directs staff to document savings-security verification results and clear the diary on DSAB.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL007" source="UI_MSSICS_DSAB" target="SYS_SSR"><data key="edge_relationship_id">R40REL007</data><data key="edge_source_entity_id">UI_MSSICS_DSAB</data><data key="edge_relationship_type">builds_transaction_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS says completing DSAB can build the transaction to the SSR.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Logical transaction relationship; no message format or middleware inferred.</data></edge><edge id="R40REL008" source="PROC_SSI_ABAP" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R40REL008</data><data key="edge_source_entity_id">PROC_SSI_ABAP</data><data key="edge_relationship_type">uses_preferred_system</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current POMS states an abbreviated SSI application can be taken using the SSI Claims System and identifies it as the preferred claims-taking method.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL009" source="PROC_SSI_ABAP" target="APP_MSSICS"><data key="edge_relationship_id">R40REL009</data><data key="edge_source_entity_id">PROC_SSI_ABAP</data><data key="edge_relationship_type">supported_by</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS provides MSSICS systems-input references for abbreviated applications.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">POMS also uses the broader logical term SSI Claims System; this relationship does not assert that all current SSI Claims System paths are MSSICS.</data></edge><edge id="R40REL010" source="DB_SSI_PE_ODS" target="WORK_SSI_CRITICAL_BDAY"><data key="edge_relationship_id">R40REL010</data><data key="edge_source_entity_id">DB_SSI_PE_ODS</data><data key="edge_relationship_type">selects_work_for</data><data key="edge_target_entity_id">WORK_SSI_CRITICAL_BDAY</data><data key="edge_operational_context">Current POMS says PE ODS selects a record with a KB diary as a scheduled age-18 redetermination in the month the recipient attains age 18.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship is specific to the documented KB critical-birthday path.</data></edge><edge id="R40REL011" source="WORK_SSI_CRITICAL_BDAY" target="SYS_SSR"><data key="edge_relationship_id">R40REL011</data><data key="edge_source_entity_id">WORK_SSI_CRITICAL_BDAY</data><data key="edge_relationship_type">drives_actions_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Critical-birthday diaries are set on SSI records in current payment status and drive post-entitlement review actions.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">4</data><data key="edge_notes">POMS describes the master-record and diary behavior but does not name the generating program.</data></edge><edge id="R40REL012" source="CON_DRN_2026" target="ORG_STERLING_COMPUTERS"><data key="edge_relationship_id">R40REL012</data><data key="edge_source_entity_id">CON_DRN_2026</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_STERLING_COMPUTERS</data><data key="edge_operational_context">USAspending identifies Sterling Computers Corporation as the recipient under the SEWP V IDV used for the SSA order.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL013" source="CON_DRN_2026" target="CONTRACT_SEWP_NNG15SC20B"><data key="edge_relationship_id">R40REL013</data><data key="edge_source_entity_id">CON_DRN_2026</data><data key="edge_relationship_type">placed_under</data><data key="edge_target_entity_id">CONTRACT_SEWP_NNG15SC20B</data><data key="edge_operational_context">USAspending lists SSA order 28321326FDX030037 under IDV NNG15SC20B.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL014" source="ORG_STERLING_COMPUTERS" target="CONTRACT_SEWP_NNG15SC20B"><data key="edge_relationship_id">R40REL014</data><data key="edge_source_entity_id">ORG_STERLING_COMPUTERS</data><data key="edge_relationship_type">holds</data><data key="edge_target_entity_id">CONTRACT_SEWP_NNG15SC20B</data><data key="edge_operational_context">USAspending identifies Sterling Computers Corporation as the IDV recipient.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL015" source="CON_DRN_2026" target="TECH_DRN"><data key="edge_relationship_id">R40REL015</data><data key="edge_source_entity_id">CON_DRN_2026</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">TECH_DRN</data><data key="edge_operational_context">The SSA delivery-order description expressly states the Data Replication Network requirement.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R40REL016" source="TECH_DRN" target="TECH_MAINFRAME"><data key="edge_relationship_id">R40REL016</data><data key="edge_source_entity_id">TECH_DRN</data><data key="edge_relationship_type">replicates_data_for</data><data key="edge_target_entity_id">TECH_MAINFRAME</data><data key="edge_operational_context">USAspending describes DRN as providing resilient, real-time replication of mainframe data.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No specific mainframe application or storage target inferred.</data></edge><edge id="R40REL017" source="TECH_DRN" target="TECH_MAINFRAME"><data key="edge_relationship_id">R40REL017</data><data key="edge_source_entity_id">TECH_DRN</data><data key="edge_relationship_type">supports_disaster_recovery_for</data><data key="edge_target_entity_id">TECH_MAINFRAME</data><data key="edge_operational_context">USAspending says the DRN supports disaster recovery for SSA mainframe data across geographically dispersed data centers.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">No named facility endpoint inferred.</data></edge><edge id="R41REL001" source="ENV_ECBSV_ETE" target="SVC_ECBSV_API"><data key="edge_relationship_id">R41REL001</data><data key="edge_source_entity_id">ENV_ECBSV_ETE</data><data key="edge_relationship_type">test_environment_for</data><data key="edge_target_entity_id">SVC_ECBSV_API</data><data key="edge_operational_context">SSA provides ETE so clients in development can perform interface testing against the eCBSV verification service.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No production hosting equivalence is inferred.</data></edge><edge id="R41REL002" source="ENV_ECBSV_ETE" target="TECH_OIDC"><data key="edge_relationship_id">R41REL002</data><data key="edge_source_entity_id">ENV_ECBSV_ETE</data><data key="edge_relationship_type">uses_authentication_technology</data><data key="edge_target_entity_id">TECH_OIDC</data><data key="edge_operational_context">ETE registration requires the client test environment OIDC issuer URL.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R41REL003" source="ENV_ECBSV_ETE" target="TECH_OAUTH2"><data key="edge_relationship_id">R41REL003</data><data key="edge_source_entity_id">ENV_ECBSV_ETE</data><data key="edge_relationship_type">uses_authorization_technology</data><data key="edge_target_entity_id">TECH_OAUTH2</data><data key="edge_operational_context">Successful ETE registration returns an ETE OAuth Client ID.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R41REL004" source="ORG_DEISB" target="ORG_DIIAS"><data key="edge_relationship_id">R41REL004</data><data key="edge_source_entity_id">ORG_DEISB</data><data key="edge_relationship_type">organizational_unit_within</data><data key="edge_target_entity_id">ORG_DIIAS</data><data key="edge_operational_context">Current POMS names the Office of Hardware Engineering, Division of Internet/Intranet Application Services, Data Exchange Infrastructure Support Branch.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Organizational containment only; no additional hierarchy is inferred.</data></edge><edge id="R41REL005" source="ORG_DEISB" target="PROC_DX_SOFTWARE_LICENSE_GRANT"><data key="edge_relationship_id">R41REL005</data><data key="edge_source_entity_id">ORG_DEISB</data><data key="edge_relationship_type">administers</data><data key="edge_target_entity_id">PROC_DX_SOFTWARE_LICENSE_GRANT</data><data key="edge_operational_context">Current POMS assigns DEISB the decision and issuance role for Data Exchange Software License Grants.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R41REL006" source="PROC_DX_SOFTWARE_LICENSE_GRANT" target="TECH_FTMS"><data key="edge_relationship_id">R41REL006</data><data key="edge_source_entity_id">PROC_DX_SOFTWARE_LICENSE_GRANT</data><data key="edge_relationship_type">enables_interface_to</data><data key="edge_target_entity_id">TECH_FTMS</data><data key="edge_operational_context">External entities receiving applicable data-exchange software licenses use them for communication with SSA; current policy requires capability to interface with FTMS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Business/technical enablement relationship; no particular software product is inferred.</data></edge><edge id="R41REL007" source="EX_DTA" target="DB_DTA_PIN_FILE"><data key="edge_relationship_id">R41REL007</data><data key="edge_source_entity_id">EX_DTA</data><data key="edge_relationship_type">uses_access_control_store</data><data key="edge_target_entity_id">DB_DTA_PIN_FILE</data><data key="edge_operational_context">Current DTA policy says OIS assigns approved users PINs and attaches employee PII to the PIN to capture all transactions under that PIN.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R41REL008" source="EXT_CYBERSCOPE" target="ORG_DHS"><data key="edge_relationship_id">R41REL008</data><data key="edge_source_entity_id">EXT_CYBERSCOPE</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_DHS</data><data key="edge_operational_context">FY2026 OIG identifies CyberScope as the Department of Homeland Security tool used for FISMA metric reporting.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R41REL009" source="APP_FOIAXPRESS_PAL" target="DB_FOIA_PRIVACY_REQUEST_APPEAL"><data key="edge_relationship_id">R41REL009</data><data key="edge_source_entity_id">APP_FOIAXPRESS_PAL</data><data key="edge_relationship_type">provides_public_submission_for</data><data key="edge_target_entity_id">DB_FOIA_PRIVACY_REQUEST_APPEAL</data><data key="edge_operational_context">Current PAL accepts FOIA requests; SORN 60-0340 is SSA's logical record system for FOIA and Privacy Act request/appeal records.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Cross-source logical relationship only; no direct PAL-to-database API or persistence mechanism is inferred.</data></edge><edge id="R41REL010" source="APP_FOIAXPRESS_PAL" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">R41REL010</data><data key="edge_source_entity_id">APP_FOIAXPRESS_PAL</data><data key="edge_relationship_type">supports_authentication_via</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">Current PAL offers Login.gov sign-in for registered requesters.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R41REL011" source="APP_FOIAXPRESS_PAL" target="SVC_IDME"><data key="edge_relationship_id">R41REL011</data><data key="edge_source_entity_id">APP_FOIAXPRESS_PAL</data><data key="edge_relationship_type">supports_authentication_via</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">Current PAL offers ID.me sign-in for registered requesters.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R41REL012" source="APP_FOIAONLINE" target="DB_FOIA_PRIVACY_REQUEST_APPEAL"><data key="edge_relationship_id">R41REL012</data><data key="edge_source_entity_id">APP_FOIAONLINE</data><data key="edge_relationship_type">described_as_processing_records_for</data><data key="edge_target_entity_id">DB_FOIA_PRIVACY_REQUEST_APPEAL</data><data key="edge_operational_context">SSA's current FOIA About page says all FOIA requests are captured in FOIAonline; the logical SORN record system covers FOIA/Privacy Act requests and appeals.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Documentation conflict preserved: current Request/Reports pages identify FOIAXpress/PAL. No current physical system-of-record conclusion is drawn.</data></edge><edge id="R42REL001" source="APP_FTD" target="EXT_DHS_ADIS"><data key="edge_relationship_id">R42REL001</data><data key="edge_source_entity_id">APP_FTD</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">EXT_DHS_ADIS</data><data key="edge_operational_context">Current POMS says FTD creates direct query access to DHS ADIS to obtain foreign-travel information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Does not imply an API protocol or network implementation.</data></edge><edge id="R42REL002" source="APP_FTD" target="APP_CCE"><data key="edge_relationship_id">R42REL002</data><data key="edge_source_entity_id">APP_FTD</data><data key="edge_relationship_type">available_within</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Current POMS says FTD is a query feature available on the SSI Claims Actions page within CCE.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Application embedding/integration only; no service boundary inferred.</data></edge><edge id="R42REL003" source="EX_FTD_ADIS_QUERY" target="EXT_DHS_ADIS"><data key="edge_relationship_id">R42REL003</data><data key="edge_source_entity_id">EX_FTD_ADIS_QUERY</data><data key="edge_relationship_type">source_repository</data><data key="edge_target_entity_id">EXT_DHS_ADIS</data><data key="edge_operational_context">The exchange obtains travel information from DHS ADIS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R42REL004" source="EX_FTD_ADIS_QUERY" target="APP_FTD"><data key="edge_relationship_id">R42REL004</data><data key="edge_source_entity_id">EX_FTD_ADIS_QUERY</data><data key="edge_relationship_type">delivers_to</data><data key="edge_target_entity_id">APP_FTD</data><data key="edge_operational_context">The direct-query exchange supplies foreign-travel information displayed through FTD.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R42REL005" source="EX_FTD_ADIS_QUERY" target="ORG_DHS"><data key="edge_relationship_id">R42REL005</data><data key="edge_source_entity_id">EX_FTD_ADIS_QUERY</data><data key="edge_relationship_type">external_partner</data><data key="edge_target_entity_id">ORG_DHS</data><data key="edge_operational_context">SSA POMS identifies DHS as the maintainer of ADIS and exchange partner for FTD.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R42REL006" source="APP_FTD" target="APP_SSI_REDET"><data key="edge_relationship_id">R42REL006</data><data key="edge_source_entity_id">APP_FTD</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_SSI_REDET</data><data key="edge_operational_context">FTD was initially used for SSI redeterminations and remains available for specified redetermination workloads.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS expands use beyond the original noncitizen redetermination scope.</data></edge><edge id="R42REL007" source="INIT_SSI_IMPROVEMENT" target="EX_PIE"><data key="edge_relationship_id">R42REL007</data><data key="edge_source_entity_id">INIT_SSI_IMPROVEMENT</data><data key="edge_relationship_type">includes_modernization_of</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">SSA lists full-scale PIE implementation among SSI Improvement Team accomplishments.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Program/initiative relationship, not a technical interface.</data></edge><edge id="R42REL008" source="INIT_SSI_IMPROVEMENT" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R42REL008</data><data key="edge_source_entity_id">INIT_SSI_IMPROVEMENT</data><data key="edge_relationship_type">promotes_use_of</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA identifies digital communication through Upload Documents as an SSI improvement.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No new Upload Documents architecture inferred.</data></edge><edge id="R42REL009" source="INIT_SSI_IMPROVEMENT" target="APP_FTD"><data key="edge_relationship_id">R42REL009</data><data key="edge_source_entity_id">INIT_SSI_IMPROVEMENT</data><data key="edge_relationship_type">drives_expansion_of</data><data key="edge_target_entity_id">APP_FTD</data><data key="edge_operational_context">FY2027 budget material states the SSI Improvement office improved the digital footprint through expansion of Foreign Travel Data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Program modernization relationship.</data></edge><edge id="R42REL010" source="CON_MONGODB_2026" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R42REL010</data><data key="edge_source_entity_id">CON_MONGODB_2026</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">Award data identifies 28321326FA0010219 as a call under BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Secondary federal-award data mirror.</data></edge><edge id="R42REL011" source="CON_MONGODB_2026" target="ORG_FOUR_POINTS"><data key="edge_relationship_id">R42REL011</data><data key="edge_source_entity_id">CON_MONGODB_2026</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_FOUR_POINTS</data><data key="edge_operational_context">Federal-award data mirrors identify Four Points as the awardee.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R42REL012" source="CON_MONGODB_2026" target="TECH_MONGODB"><data key="edge_relationship_id">R42REL012</data><data key="edge_source_entity_id">CON_MONGODB_2026</data><data key="edge_relationship_type">procures</data><data key="edge_target_entity_id">TECH_MONGODB</data><data key="edge_operational_context">Government description reproduced by award mirrors says "Call Order for Mongodb".</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Procurement does not prove production deployment.</data></edge><edge id="R42REL013" source="CON_CALL_BRANDING_2026" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">R42REL013</data><data key="edge_source_entity_id">CON_CALL_BRANDING_2026</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">Award data identifies 28321326FA0010070 as a call under BPA 28321321A00040003.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R42REL014" source="CON_CALL_BRANDING_2026" target="ORG_FOUR_POINTS"><data key="edge_relationship_id">R42REL014</data><data key="edge_source_entity_id">CON_CALL_BRANDING_2026</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_FOUR_POINTS</data><data key="edge_operational_context">Federal-award data mirrors identify Four Points as awardee.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R42REL015" source="CON_CALL_BRANDING_2026" target="SVC_OUTBOUND_CALL_TRUST"><data key="edge_relationship_id">R42REL015</data><data key="edge_source_entity_id">CON_CALL_BRANDING_2026</data><data key="edge_relationship_type">procures</data><data key="edge_target_entity_id">SVC_OUTBOUND_CALL_TRUST</data><data key="edge_operational_context">Government award description says the call order procures TransUnion outbound-call spoof-proofing and call-branding capability.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Procurement does not prove production deployment.</data></edge><edge id="R42REL016" source="SVC_OUTBOUND_CALL_TRUST" target="ORG_TRANSUNION"><data key="edge_relationship_id">R42REL016</data><data key="edge_source_entity_id">SVC_OUTBOUND_CALL_TRUST</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_TRANSUNION</data><data key="edge_operational_context">The government award description explicitly names TransUnion as the procured call-trust provider.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">No separate direct SSA-TransUnion prime-contract relationship is inferred; Four Points is the BPA-call awardee.</data></edge><edge id="R43REL001" source="UI_ERPS_SSA11_INTRO" target="APP_ERPS"><data key="edge_relationship_id">R43REL001</data><data key="edge_source_entity_id">UI_ERPS_SSA11_INTRO</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies the SSA-11 Application-Introduction screen as part of the eRPS application path.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL002" source="UI_ERPS_APPLICANT_ID" target="APP_ERPS"><data key="edge_relationship_id">R43REL002</data><data key="edge_source_entity_id">UI_ERPS_APPLICANT_ID</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies the Proof of Applicant's Identity screen as part of the eRPS application path.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL003" source="UI_ERPS_BG_PERMISSION" target="APP_ERPS"><data key="edge_relationship_id">R43REL003</data><data key="edge_source_entity_id">UI_ERPS_BG_PERMISSION</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies the Permission for Background Check screen in eRPS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL004" source="UI_ERPS_BG_RESULTS" target="APP_ERPS"><data key="edge_relationship_id">R43REL004</data><data key="edge_source_entity_id">UI_ERPS_BG_RESULTS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies the Background Check Results screen in the eRPS criminal-background workflow.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL005" source="UI_ERPS_MAKE_NOTE" target="APP_ERPS"><data key="edge_relationship_id">R43REL005</data><data key="edge_source_entity_id">UI_ERPS_MAKE_NOTE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS directs staff to the Make Note screen in eRPS for representative-payee applicant notes.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL006" source="UI_ERPS_SELECTION_DECISION" target="APP_ERPS"><data key="edge_relationship_id">R43REL006</data><data key="edge_source_entity_id">UI_ERPS_SELECTION_DECISION</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS directs staff to the Rep Payee Selection-Decision screen during eRPS application disposition.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL007" source="UI_ERPS_PRISONER_INFO" target="APP_ERPS"><data key="edge_relationship_id">R43REL007</data><data key="edge_source_entity_id">UI_ERPS_PRISONER_INFO</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies the Prisoner Information screen in the eRPS suitability workflow.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL008" source="UI_ERPS_FUGITIVE_FELON" target="APP_ERPS"><data key="edge_relationship_id">R43REL008</data><data key="edge_source_entity_id">UI_ERPS_FUGITIVE_FELON</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies the Fugitive Felon Information screen in the eRPS suitability workflow.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL009" source="UI_ERPS_APPLICANT_ID" target="SYS_NUMIDENT"><data key="edge_relationship_id">R43REL009</data><data key="edge_source_entity_id">UI_ERPS_APPLICANT_ID</data><data key="edge_relationship_type">verifies_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">For telephone and approved video interviews, current POMS directs staff to record ID verified via NUMI on this screen after confirming Numident information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Business/user-interface relationship; no separate API or service call is inferred.</data></edge><edge id="R43REL010" source="UI_ERPS_BG_PERMISSION" target="PROC_ERPS_CRIMINAL_BG"><data key="edge_relationship_id">R43REL010</data><data key="edge_source_entity_id">UI_ERPS_BG_PERMISSION</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_ERPS_CRIMINAL_BG</data><data key="edge_operational_context">Current POMS says the criminal background check is not conducted until permission is recorded on this screen.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL011" source="UI_ERPS_BG_RESULTS" target="PROC_ERPS_CRIMINAL_BG"><data key="edge_relationship_id">R43REL011</data><data key="edge_source_entity_id">UI_ERPS_BG_RESULTS</data><data key="edge_relationship_type">presents_results_of</data><data key="edge_target_entity_id">PROC_ERPS_CRIMINAL_BG</data><data key="edge_operational_context">Current POMS directs staff to discuss and verify criminal information displayed on the Background Check Results screen.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL012" source="UI_ERPS_PRISONER_INFO" target="APP_PUPS"><data key="edge_relationship_id">R43REL012</data><data key="edge_source_entity_id">UI_ERPS_PRISONER_INFO</data><data key="edge_relationship_type">presents_record_from</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Current POMS refers to a PUPS record on the eRPS Prisoner Information screen.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No underlying data-transfer mechanism is inferred.</data></edge><edge id="R43REL013" source="UI_ERPS_SELECTION_DECISION" target="PROC_ERPS_CRIMINAL_BG"><data key="edge_relationship_id">R43REL013</data><data key="edge_source_entity_id">UI_ERPS_SELECTION_DECISION</data><data key="edge_relationship_type">records_outcome_after</data><data key="edge_target_entity_id">PROC_ERPS_CRIMINAL_BG</data><data key="edge_operational_context">Current POMS directs staff to non-select an applicant on this screen when background information establishes a barred crime.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL014" source="SVC_EFAX" target="APP_RASR"><data key="edge_relationship_id">R43REL014</data><data key="edge_source_entity_id">SVC_EFAX</data><data key="edge_relationship_type">supports_representation_form_intake_for</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Current POMS lists Electronic Fax as an accepted SSA-1696 filing route; filed appointments are then processed under RASR procedures.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This is a business-intake path, not evidence of a direct eFax-to-RASR technical integration.</data></edge><edge id="R43REL015" source="UI_RASR_ROC" target="APP_RASR"><data key="edge_relationship_id">R43REL015</data><data key="edge_source_entity_id">UI_RASR_ROC</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">Current POMS directs technicians to annotate a Report of Contact screen in RASR for representation intent and withdrawal documentation.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL016" source="SYS_ECMS" target="DOM_IT_CONFIG_ASSET"><data key="edge_relationship_id">R43REL016</data><data key="edge_source_entity_id">SYS_ECMS</data><data key="edge_relationship_type">authoritative_repository_for</data><data key="edge_target_entity_id">DOM_IT_CONFIG_ASSET</data><data key="edge_operational_context">SSA Open Data describes ECMS as the authoritative repository for characteristics, authorized configurations, and relationships of key IT components/assets.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL017" source="APP_CIP" target="SYS_MBR"><data key="edge_relationship_id">R43REL017</data><data key="edge_source_entity_id">APP_CIP</data><data key="edge_relationship_type">supports_post_entitlement_pia_recomputation_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS directs FO/PSC staff to process specified post-entitlement PIA recomputations in the Change in PIA web application; the resulting Title II benefit record context is the MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Business-record context only. The source does not establish a direct CIP-to-MBR interface or update mechanism.</data></edge><edge id="R43REL018" source="UI_MONET_SMS1" target="APP_MONET"><data key="edge_relationship_id">R43REL018</data><data key="edge_source_entity_id">UI_MONET_SMS1</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MONET</data><data key="edge_operational_context">Current POMS identifies SMS1 as the Special Message Data screen in MONET.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL019" source="UI_MONET_SMS1" target="SYS_MBR"><data key="edge_relationship_id">R43REL019</data><data key="edge_source_entity_id">UI_MONET_SMS1</data><data key="edge_relationship_type">posts_special_message_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS directs staff to use the MONET SMS1 screen to add a Special Message to the MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL020" source="APP_TPPS" target="DATA_USDC_INVENTORY_LOG"><data key="edge_relationship_id">R43REL020</data><data key="edge_source_entity_id">APP_TPPS</data><data key="edge_relationship_type">provides_template_for</data><data key="edge_target_entity_id">DATA_USDC_INVENTORY_LOG</data><data key="edge_operational_context">Current POMS states the required U.S. Debit Card Inventory Log template can be accessed on the TPPS website.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL021" source="DATA_USDC_INVENTORY_LOG" target="PAY_USDC"><data key="edge_relationship_id">R43REL021</data><data key="edge_source_entity_id">DATA_USDC_INVENTORY_LOG</data><data key="edge_relationship_type">tracks_disbursement_of</data><data key="edge_target_entity_id">PAY_USDC</data><data key="edge_operational_context">Current POMS says field offices use the inventory log to track U.S. Debit Card receipt and disbursement.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R43REL022" source="CON_ORACLE_MAINT_2026" target="ORG_EMERGENT_LLC"><data key="edge_relationship_id">R43REL022</data><data key="edge_source_entity_id">CON_ORACLE_MAINT_2026</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_EMERGENT_LLC</data><data key="edge_operational_context">Federal award data identifies Emergent, LLC as recipient of delivery order 28321326FDX030114.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R43REL023" source="CON_ORACLE_MAINT_2026" target="TECH_ORACLE_DATABASE"><data key="edge_relationship_id">R43REL023</data><data key="edge_source_entity_id">CON_ORACLE_MAINT_2026</data><data key="edge_relationship_type">includes_maintenance_for</data><data key="edge_target_entity_id">TECH_ORACLE_DATABASE</data><data key="edge_operational_context">The government award description explicitly includes Oracle Database software maintenance.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">No application dependency is inferred.</data></edge><edge id="R43REL024" source="CON_ORACLE_MAINT_2026" target="TECH_ORACLE_MIDDLEWARE"><data key="edge_relationship_id">R43REL024</data><data key="edge_source_entity_id">CON_ORACLE_MAINT_2026</data><data key="edge_relationship_type">includes_maintenance_for</data><data key="edge_target_entity_id">TECH_ORACLE_MIDDLEWARE</data><data key="edge_operational_context">The government award description explicitly includes Oracle Middleware software maintenance.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">No product/version or application dependency is inferred.</data></edge><edge id="R43REL025" source="CON_ORACLE_MAINT_2026" target="APP_SERS"><data key="edge_relationship_id">R43REL025</data><data key="edge_source_entity_id">CON_ORACLE_MAINT_2026</data><data key="edge_relationship_type">includes_maintenance_for</data><data key="edge_target_entity_id">APP_SERS</data><data key="edge_operational_context">The government award description explicitly includes SERS software maintenance.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The award does not establish that SERS uses Oracle Database or Oracle Middleware.</data></edge><edge id="R43REL026" source="CON_ORACLE_MAINT_2026" target="APP_SSOARS"><data key="edge_relationship_id">R43REL026</data><data key="edge_source_entity_id">CON_ORACLE_MAINT_2026</data><data key="edge_relationship_type">includes_maintenance_for</data><data key="edge_target_entity_id">APP_SSOARS</data><data key="edge_operational_context">The government award description explicitly includes SSOARS software maintenance.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The award does not establish that SSOARS uses Oracle Database or Oracle Middleware.</data></edge><edge id="R43REL027" source="CON_SONATYPE_NEXUS_2026" target="ORG_ACCESSAGILITY"><data key="edge_relationship_id">R43REL027</data><data key="edge_source_entity_id">CON_SONATYPE_NEXUS_2026</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_ACCESSAGILITY</data><data key="edge_operational_context">Federal award data identifies AccessAgility LLC as recipient of delivery order 28321326FDX030022.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R43REL028" source="CON_SONATYPE_NEXUS_2026" target="TECH_SONATYPE_NEXUS"><data key="edge_relationship_id">R43REL028</data><data key="edge_source_entity_id">CON_SONATYPE_NEXUS_2026</data><data key="edge_relationship_type">renews_software_for</data><data key="edge_target_entity_id">TECH_SONATYPE_NEXUS</data><data key="edge_operational_context">The government award description states the order is an annual renewal of Sonatype Nexus Repository software.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Deployment location, version, and pipeline consumers are not inferred.</data></edge><edge id="R43REL029" source="CON_MITRE_NETWORK_ASSESS_2026" target="ORG_MITRE"><data key="edge_relationship_id">R43REL029</data><data key="edge_source_entity_id">CON_MITRE_NETWORK_ASSESS_2026</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_MITRE</data><data key="edge_operational_context">Federal award data identifies MITRE as recipient of delivery order 28321326FDX030085.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R43REL030" source="CON_MITRE_NETWORK_ASSESS_2026" target="PROJ_NETWORK_ASSESS_2026"><data key="edge_relationship_id">R43REL030</data><data key="edge_source_entity_id">CON_MITRE_NETWORK_ASSESS_2026</data><data key="edge_relationship_type">funds</data><data key="edge_target_entity_id">PROJ_NETWORK_ASSESS_2026</data><data key="edge_operational_context">The government award description defines the delivery order as an independent assessment of SSA network infrastructure and future-state recommendations.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R44REL001" source="ORG_SSA_OITA" target="ORG_SSA_OAG"><data key="edge_relationship_id">R44REL001</data><data key="edge_source_entity_id">ORG_SSA_OITA</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">Current OAG page identifies OITA as an OAG office responsible for IT products and related services.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL002" source="APP_SSASY" target="ORG_SSA_OAG"><data key="edge_relationship_id">R44REL002</data><data key="edge_source_entity_id">APP_SSASY</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">SSA states that OAG operates Social Security's Streamlined Acquisition System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL003" source="DB_VENDOR_INFO_REPO" target="ORG_SSA_OAG"><data key="edge_relationship_id">R44REL003</data><data key="edge_source_entity_id">DB_VENDOR_INFO_REPO</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">OAG publishes and administers the vendor repository instructions for SSA market research.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Repository is available SSA-wide; this does not imply OAG is the only consumer.</data></edge><edge id="R44REL004" source="INIT_CSCRM" target="PROC_CSCRA"><data key="edge_relationship_id">R44REL004</data><data key="edge_source_entity_id">INIT_CSCRM</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PROC_CSCRA</data><data key="edge_operational_context">SSA's CSCRM program requires a cybersecurity supply-chain risk assessment before contract award.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL005" source="PROC_CSCRA" target="DATA_CSCRA_QUESTIONNAIRE"><data key="edge_relationship_id">R44REL005</data><data key="edge_source_entity_id">PROC_CSCRA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_CSCRA_QUESTIONNAIRE</data><data key="edge_operational_context">The CSCRA process collects relevant third-party information through the CSCRA Questionnaire.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL006" source="PROC_CSCRA" target="PLAT_TP_CYBER_RISK_MON"><data key="edge_relationship_id">R44REL006</data><data key="edge_source_entity_id">PROC_CSCRA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PLAT_TP_CYBER_RISK_MON</data><data key="edge_operational_context">OAG says CSCRA due diligence uses specialized tools such as the agency's Third-Party Cyber Risk Monitoring platform.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL007" source="APP_TP_RISK_MGMT" target="INIT_CSCRM"><data key="edge_relationship_id">R44REL007</data><data key="edge_source_entity_id">APP_TP_RISK_MGMT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">INIT_CSCRM</data><data key="edge_operational_context">OAG says all third-party relationships are reviewed and tracked using the Third-Party Risk Management system during CSCRM monitoring.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL008" source="PLAT_TP_CYBER_RISK_MON" target="INIT_CSCRM"><data key="edge_relationship_id">R44REL008</data><data key="edge_source_entity_id">PLAT_TP_CYBER_RISK_MON</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">INIT_CSCRM</data><data key="edge_operational_context">January 2026 requirements call for pre-award assessment through the Government-selected Cyber Risk Monitoring platform and continuous risk monitoring.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL009" source="SVC_CPARS" target="ORG_SSA_OAG"><data key="edge_relationship_id">R44REL009</data><data key="edge_source_entity_id">SVC_CPARS</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">SSA OAG documents agency use of CPARS for contractor past-performance evaluations within the acquisition function.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The source states SSA-wide use; OAG is the principal procurement office, but it does not enumerate every internal CPARS user.</data></edge><edge id="R44REL010" source="SVC_GRANTS_GOV" target="ORG_SSA_OAG"><data key="edge_relationship_id">R44REL010</data><data key="edge_source_entity_id">SVC_GRANTS_GOV</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">OAG directs competitive discretionary grant applicants to submit through Grants.gov.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL011" source="SVC_GRANTSOLUTIONS" target="ORG_SSA_OAG"><data key="edge_relationship_id">R44REL011</data><data key="edge_source_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">OAG directs continuation grant applications through GrantSolutions and uses it for award notifications.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL012" source="SVC_ASAP" target="ORG_SSA_OAG"><data key="edge_relationship_id">R44REL012</data><data key="edge_source_entity_id">SVC_ASAP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">OAG requires SSA grant recipients to establish electronic payment accounts with ASAP.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL013" source="DATA_OAG_HQ_AWARDS" target="ORG_SSA_OAG"><data key="edge_relationship_id">R44REL013</data><data key="edge_source_entity_id">DATA_OAG_HQ_AWARDS</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">The public dataset page identifies OAG as the contracting office producing the headquarters award listing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL014" source="UI_SSI_PERSON_STATEMENT" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R44REL014</data><data key="edge_source_entity_id">UI_SSI_PERSON_STATEMENT</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current POMS explicitly identifies the Person Statement screen in the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL015" source="UI_SSI_FI_PERMISSION" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R44REL015</data><data key="edge_source_entity_id">UI_SSI_FI_PERMISSION</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current POMS says financial permission is recorded on the Financial Institutions Permission page in the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL016" source="UI_SSI_FI_ACCOUNT" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R44REL016</data><data key="edge_source_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current POMS repeatedly refers to the Financial Institution Account page in the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL017" source="UI_SSI_FI_ACCOUNT" target="APP_CCE"><data key="edge_relationship_id">R44REL017</data><data key="edge_source_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Current POMS explicitly says direct-deposit financial accounts can be recorded on the Financial Institution Account page in CCE.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This does not assert that CCE and the logical SSI Claims System are physically identical.</data></edge><edge id="R44REL018" source="UI_SSI_STATE_LOCAL_TRIBAL" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R44REL018</data><data key="edge_source_entity_id">UI_SSI_STATE_LOCAL_TRIBAL</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current POMS identifies the Other State, Local, or Tribal Assistance page in the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL019" source="UI_SSI_FI_PERMISSION" target="EX_AFI_FI"><data key="edge_relationship_id">R44REL019</data><data key="edge_source_entity_id">UI_SSI_FI_PERMISSION</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">Current POMS requires financial permission before financial account balance verification and records that permission in the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL020" source="UI_SSI_FI_ACCOUNT" target="DATA_FI_BALANCE_HISTORY"><data key="edge_relationship_id">R44REL020</data><data key="edge_source_entity_id">UI_SSI_FI_ACCOUNT</data><data key="edge_relationship_type">records_in</data><data key="edge_target_entity_id">DATA_FI_BALANCE_HISTORY</data><data key="edge_operational_context">Current POMS uses returned financial-account balance information to verify and document account balances on the Financial Institution Account page.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Models documented use of balance data on the page; it does not assert physical database storage in the UI.</data></edge><edge id="R44REL021" source="UI_ERPS_BENE_DETAILS" target="APP_ERPS"><data key="edge_relationship_id">R44REL021</data><data key="edge_source_entity_id">UI_ERPS_BENE_DETAILS</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies Beneficiary Details as an eRPS screen.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL022" source="UI_MCS_RPOC" target="APP_MCS"><data key="edge_relationship_id">R44REL022</data><data key="edge_source_entity_id">UI_MCS_RPOC</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Current POMS directs Title II/concurrent capability determinations to the MCS Report of Contact (RPOC).</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL023" source="UI_CCE_ROC" target="APP_CCE"><data key="edge_relationship_id">R44REL023</data><data key="edge_source_entity_id">UI_CCE_ROC</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Current POMS directs Title XVI-only capability determinations to the CCE Report of Contact page.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R44REL024" source="UI_ERPS_BENE_DETAILS" target="APP_ERPS"><data key="edge_relationship_id">R44REL024</data><data key="edge_source_entity_id">UI_ERPS_BENE_DETAILS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">POMS states capability determination notes remain associated with the beneficiary's eRPS record through Beneficiary Details.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R45REL001" source="DATA_CWHS" target="SYS_MEF"><data key="edge_relationship_id">R45REL001</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">SSA historical documentation says CWHS earnings and employment information is derived from the Master Earnings File.</data><data key="edge_observed_as_of">2009</data><data key="edge_confidence">5</data><data key="edge_notes">Historical lineage evidence; no assumption is made that extraction implementation details remain unchanged.</data></edge><edge id="R45REL002" source="DATA_CWHS" target="SYS_NUMIDENT"><data key="edge_relationship_id">R45REL002</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA historical documentation says CWHS demographic information is derived from Numident.</data><data key="edge_observed_as_of">2009</data><data key="edge_confidence">5</data><data key="edge_notes">Historical lineage evidence; no assumption is made that extraction implementation details remain unchanged.</data></edge><edge id="R45REL003" source="DATA_CWHS" target="SYS_MBR"><data key="edge_relationship_id">R45REL003</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA historical documentation says CWHS annual benefit data is derived from the Master Beneficiary Record.</data><data key="edge_observed_as_of">2009</data><data key="edge_confidence">5</data><data key="edge_notes">Historical lineage evidence; no assumption is made that extraction implementation details remain unchanged.</data></edge><edge id="R45REL004" source="DATA_CWHS" target="MODEL_OACT_FI_SR"><data key="edge_relationship_id">R45REL004</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">input_to</data><data key="edge_target_entity_id">MODEL_OACT_FI_SR</data><data key="edge_operational_context">The 2026 Trustees Report says the short-range fully insured model extrapolates historical trends using CWHS coverage and quarters-of-coverage information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R45REL005" source="MODEL_OACT_FI_SR" target="MODEL_OACT_FI_LR"><data key="edge_relationship_id">R45REL005</data><data key="edge_source_entity_id">MODEL_OACT_FI_SR</data><data key="edge_relationship_type">calibrates</data><data key="edge_target_entity_id">MODEL_OACT_FI_LR</data><data key="edge_operational_context">The 2026 Trustees Report says long-range model parameters are selected so simulated fully insured percentages are consistent with estimates from the short-range model.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R45REL006" source="MODEL_OACT_FI_SR" target="ORG_SSA_OCACT"><data key="edge_relationship_id">R45REL006</data><data key="edge_source_entity_id">MODEL_OACT_FI_SR</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_OCACT</data><data key="edge_operational_context">The Office of the Chief Actuary documents use of the short-range model in current OASDI actuarial methods.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R45REL007" source="MODEL_OACT_FI_LR" target="ORG_SSA_OCACT"><data key="edge_relationship_id">R45REL007</data><data key="edge_source_entity_id">MODEL_OACT_FI_LR</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_OCACT</data><data key="edge_operational_context">The Office of the Chief Actuary documents use of the long-range model in current OASDI actuarial methods.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R45REL008" source="DATA_SIPP" target="ORG_CENSUS"><data key="edge_relationship_id">R45REL008</data><data key="edge_source_entity_id">DATA_SIPP</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_CENSUS</data><data key="edge_operational_context">SSA identifies SIPP as a Census Bureau survey used in MINT8.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R45REL009" source="DATA_SIPP" target="MODEL_MINT8"><data key="edge_relationship_id">R45REL009</data><data key="edge_source_entity_id">DATA_SIPP</data><data key="edge_relationship_type">input_to</data><data key="edge_target_entity_id">MODEL_MINT8</data><data key="edge_operational_context">SSA says MINT8 is built from Social Security administrative records matched to SIPP.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Does not identify the specific SSA record systems in the current methodology page.</data></edge><edge id="R45REL010" source="MODEL_MINT8" target="ORG_SSA_ORES"><data key="edge_relationship_id">R45REL010</data><data key="edge_source_entity_id">MODEL_MINT8</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_ORES</data><data key="edge_operational_context">SSA ORES publishes the MINT overview and uses MINT for research projections of future retirement conditions and policy effects.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R45REL011" source="SVC_RCC" target="SVC_AMAZON_CONNECT"><data key="edge_relationship_id">R45REL011</data><data key="edge_source_entity_id">SVC_RCC</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_operational_context">SSA states RCC expansion and automated routing were made possible by transitioning the service to the Amazon Web Services Connect platform.</data><data key="edge_observed_as_of">2024-12-19</data><data key="edge_confidence">5</data><data key="edge_notes">The relationship is current-service architecture evidence; no lower-level API, hosting account, or routing implementation is inferred.</data></edge><edge id="R45REL012" source="ORG_SSA_CENTRAL_PROCESSING" target="ORG_WSU"><data key="edge_relationship_id">R45REL012</data><data key="edge_source_entity_id">ORG_SSA_CENTRAL_PROCESSING</data><data key="edge_relationship_type">manages</data><data key="edge_target_entity_id">ORG_WSU</data><data key="edge_operational_context">SSA states Central Processing now manages Workload Support Units as part of the 2026 processing-center realignment.</data><data key="edge_observed_as_of">2026-07-08</data><data key="edge_confidence">5</data></edge><edge id="R46REL001" source="APP_TAX_LEVY_NOTICE" target="DB_TAX_LEVY_NOTICE_DB2"><data key="edge_relationship_id">R46REL001</data><data key="edge_source_entity_id">APP_TAX_LEVY_NOTICE</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">DB_TAX_LEVY_NOTICE_DB2</data><data key="edge_operational_context">Tax Levy notice generation uses information from the Tax Levy DB2 database.</data><data key="edge_observed_as_of">2006-05-16</data><data key="edge_confidence">5</data><data key="edge_notes">Architecture detail is from the 2006 POMS description; the current POMS chapter confirms the Tax Levy Notice System remains referenced but does not republish the implementation detail.</data></edge><edge id="R46REL002" source="APP_TAX_LEVY_NOTICE" target="SYS_MBR"><data key="edge_relationship_id">R46REL002</data><data key="edge_source_entity_id">APP_TAX_LEVY_NOTICE</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Tax Levy notice generation uses Master Beneficiary Record data.</data><data key="edge_observed_as_of">2006-05-16</data><data key="edge_confidence">5</data><data key="edge_notes">Architecture detail is explicitly documented in the 2006 POMS description; no inference is made about current transport or query mechanism.</data></edge><edge id="R46REL003" source="DB_TAX_LEVY_NOTICE_DB2" target="TECH_DB2"><data key="edge_relationship_id">R46REL003</data><data key="edge_source_entity_id">DB_TAX_LEVY_NOTICE_DB2</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">The Tax Levy notice data store is explicitly identified as a DB2 database.</data><data key="edge_observed_as_of">2006-05-16</data><data key="edge_confidence">5</data><data key="edge_notes">Technology identification is explicit; version, hosting, schema, and current deployment are not disclosed.</data></edge><edge id="R46REL004" source="APP_TAX_LEVY_NOTICE" target="APP_AURORA"><data key="edge_relationship_id">R46REL004</data><data key="edge_source_entity_id">APP_TAX_LEVY_NOTICE</data><data key="edge_relationship_type">manual_notice_fallback_uses</data><data key="edge_target_entity_id">APP_AURORA</data><data key="edge_operational_context">When the Tax Levy Notice System cannot determine a manual notice, PSC staff prepare it via AURORA or exhibit notices.</data><data key="edge_observed_as_of">2006-05-16</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly states there is no AURORA interface for Tax Levy system notices; this is a human/manual fallback relationship, not a system interface.</data></edge><edge id="R46REL005" source="APP_TAX_LEVY_NOTICE" target="ORG_IRS"><data key="edge_relationship_id">R46REL005</data><data key="edge_source_entity_id">APP_TAX_LEVY_NOTICE</data><data key="edge_relationship_type">notifies</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Tax Levy Notice System provides notices to the beneficiary and the Internal Revenue Service about levy withholding.</data><data key="edge_observed_as_of">2006-05-16</data><data key="edge_confidence">5</data><data key="edge_notes">Notification is explicit in POMS. Delivery mechanism is not stated in the cited architecture description.</data></edge><edge id="R46REL006" source="APP_GARNISH_NOTICE" target="APP_ICP"><data key="edge_relationship_id">R46REL006</data><data key="edge_source_entity_id">APP_GARNISH_NOTICE</data><data key="edge_relationship_type">manual_notice_fallback_uses</data><data key="edge_target_entity_id">APP_ICP</data><data key="edge_operational_context">Current POMS directs PSC staff to prepare a manual Garnishment notice through ICP when the automated system cannot determine the notice type.</data><data key="edge_observed_as_of">2026-08-14</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly states there is no ICP interface for Garnishment system notices; modeled as manual fallback, not machine-to-machine integration.</data></edge><edge id="R46REL007" source="APP_CCM" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">R46REL007</data><data key="edge_source_entity_id">APP_CCM</data><data key="edge_relationship_type">loads_bad_notice_pdf_into</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">For Garnishment systems-bad notices, CCM automatically loads the bad notice into Paperless as a PDF for user review.</data><data key="edge_observed_as_of">2020-08-31</data><data key="edge_confidence">5</data><data key="edge_notes">Documented as effective summer 2020 in POMS. Current production status beyond the current POMS page is not independently inferred.</data></edge><edge id="R46REL008" source="APP_MADCAP" target="APP_MADCAP_NOTICE_PRINT"><data key="edge_relationship_id">R46REL008</data><data key="edge_source_entity_id">APP_MADCAP</data><data key="edge_relationship_type">uses_notice_print_program</data><data key="edge_target_entity_id">APP_MADCAP_NOTICE_PRINT</data><data key="edge_operational_context">Current POMS identifies a MADCAP Beneficiary Notice Print Program for Title II notices.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">5</data><data key="edge_notes">Logical relationship only; no separate physical deployment or runtime boundary is inferred.</data></edge><edge id="R46REL009" source="MODEL_OASDI_STOCHASTIC" target="MODEL_OASDI_SCENARIO"><data key="edge_relationship_id">R46REL009</data><data key="edge_source_entity_id">MODEL_OASDI_STOCHASTIC</data><data key="edge_relationship_type">supplements</data><data key="edge_target_entity_id">MODEL_OASDI_SCENARIO</data><data key="edge_operational_context">The stochastic projections supplement traditional scenario-based methods used to illustrate uncertainty in OASDI projections.</data><data key="edge_observed_as_of">2026-06-09</data><data key="edge_confidence">5</data><data key="edge_notes">Both models are explicitly described in the 2026 Trustees Report methodology.</data></edge><edge id="R46REL010" source="SYS_MBR" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R46REL010</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement identifies the Master Beneficiary Record as the source for multiple OASDI tables.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current publication lineage; table-specific sampling notes are preserved in evidence.</data></edge><edge id="R46REL011" source="SYS_SSR" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R46REL011</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement identifies the Supplemental Security Record as the source for SSI tables.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current publication lineage using 100-percent SSR data for the cited tables.</data></edge><edge id="R46REL012" source="APP_INFORM" target="DATA_SSA8102"><data key="edge_relationship_id">R46REL012</data><data key="edge_source_entity_id">APP_INFORM</data><data key="edge_relationship_type">provides_template_for</data><data key="edge_target_entity_id">DATA_SSA8102</data><data key="edge_operational_context">Current payment POMS says the SSA-8102 template is located in the inForm Library.</data><data key="edge_observed_as_of">2026-09-18</data><data key="edge_confidence">5</data><data key="edge_notes">Validated for both Title XVI emergency/immediate-payment and Title II immediate-payment workflows.</data></edge><edge id="R46REL013" source="DATA_SSA8102" target="APP_EP"><data key="edge_relationship_id">R46REL013</data><data key="edge_source_entity_id">DATA_SSA8102</data><data key="edge_relationship_type">uploaded_to</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Current POMS directs technicians to upload the File copy of SSA-8102 using the Evidence Portal after payment release.</data><data key="edge_observed_as_of">2026-09-18</data><data key="edge_confidence">5</data><data key="edge_notes">Title XVI instructions say upload to Evidence Portal; Title II instructions say upload to the Claims Folder using Evidence Portal.</data></edge><edge id="R46REL014" source="APP_SSNAP" target="EXT_WRAPS"><data key="edge_relationship_id">R46REL014</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">retains_legacy_workflow_for</data><data key="edge_target_entity_id">EXT_WRAPS</data><data key="edge_operational_context">Although SSA no longer uses WRAPS fax verification, WRAPS questions and workaround functionality may still appear in the SSNAP path until removed.</data><data key="edge_observed_as_of">2025-02-07</data><data key="edge_confidence">5</data><data key="edge_notes">Residual UI/workflow is explicit in current POMS; no active SSNAP-to-WRAPS system interface is inferred.</data></edge><edge id="R47_REL001" source="DB_IRS_IMF" target="APP_PEBES"><data key="edge_relationship_id">R47_REL001</data><data key="edge_source_entity_id">DB_IRS_IMF</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">Most automatic Social Security Statement mailing addresses are requested from the IRS taxpayer IMF by SSN. PEBES procures those addresses for Statement production.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic update from IRS IMF to Numident, MBR, or SSR is documented by this flow.</data></edge><edge id="R47_REL002" source="SYS_MEF" target="APP_PEBES"><data key="edge_relationship_id">R47_REL002</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">PEBES uses MEF earnings information to prepare year-by-year earnings, credits, and benefit estimates.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL003" source="APP_PEBES" target="APP_CCM"><data key="edge_relationship_id">R47_REL003</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">APP_CCM</data><data key="edge_operational_context">PEBES transmits compiled Social Security Statement information to CCM for downstream presentation/printing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL004" source="APP_PEBES" target="DB_STATEMENT_HISTORY"><data key="edge_relationship_id">R47_REL004</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DB_STATEMENT_HISTORY</data><data key="edge_operational_context">Statement processing is tracked in the Statement History File; current POMS identifies both as components of the Statement production environment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Current POMS does not publish a write-interface specification; modeled as processing-history support rather than a physical transport.</data></edge><edge id="R47_REL005" source="API_STATEMENT" target="APP_CCM"><data key="edge_relationship_id">R47_REL005</data><data key="edge_source_entity_id">API_STATEMENT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_CCM</data><data key="edge_operational_context">SSA describes the Statement API as generating the online Statement PDF through CCM using information from back-end systems.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL006" source="APP_PEBES_ONLINE" target="APP_PEBES"><data key="edge_relationship_id">R47_REL006</data><data key="edge_source_entity_id">APP_PEBES_ONLINE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">PEBES Online provides internal query access to benefit estimates associated with the PEBES/Statement processing domain.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Exact backend call/interface is not public.</data></edge><edge id="R47_REL007" source="APP_PEBES" target="SERVICE_SSA_PMF"><data key="edge_relationship_id">R47_REL007</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SERVICE_SSA_PMF</data><data key="edge_operational_context">On-request Social Security Statements produced in the PEBES/Statement process are printed and mailed by the SSA Print/Mail Facility.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Source establishes operational responsibility, not a direct system-to-system interface.</data></edge><edge id="R47_REL008" source="DB_IRS_IMF" target="DB_STATEMENT_HISTORY"><data key="edge_relationship_id">R47_REL008</data><data key="edge_source_entity_id">DB_IRS_IMF</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DB_STATEMENT_HISTORY</data><data key="edge_operational_context">Historical SIPEBES architecture stored IRS-sourced mailing address information in the History File, including the address/source used for mailings.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical relationship established in 1994. Current POMS confirms the Statement History File still exists but does not re-document this address field.</data></edge><edge id="R47_REL009" source="DB_SIPEBES_TERRITORY_ADDRESS" target="DB_STATEMENT_HISTORY"><data key="edge_relationship_id">R47_REL009</data><data key="edge_source_entity_id">DB_SIPEBES_TERRITORY_ADDRESS</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DB_STATEMENT_HISTORY</data><data key="edge_operational_context">Historical SIPEBES architecture transferred the address used for a territorial PEBES mailing into the History File after mailing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical relationship; current physical implementation is unconfirmed.</data></edge><edge id="R47_REL010" source="DB_IRS_IRMF" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R47_REL010</data><data key="edge_source_entity_id">DB_IRS_IRMF</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">Current CMA 1016 states IRS matches SSA Title XVI finder data against IRMF and returns unearned-income information including payee/payer address fields.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">CMA 1016 is effective January 1, 2026 through July 1, 2027; this resolves the prior currency uncertainty about IRMF as the current source file.</data></edge><edge id="R47_REL011" source="EX_SSI_IRS_1099" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R47_REL011</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">Current POMS computer-match chart identifies PE ODS as the data source for IRS 5B match alerts.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This does not establish that PE ODS, the generic RZ/LI Interface Database, and the SUMS Title XVI PEODS are the same physical store.</data></edge><edge id="R47_REL012" source="DB_SSI_PE_ODS" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R47_REL012</data><data key="edge_source_entity_id">DB_SSI_PE_ODS</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">IRS 5B alert data is retrievable through RZ/LI MI Central; the computer-match chart identifies PE ODS as the IRS data source.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL013" source="DB_SSI_PE_ODS" target="APP_SSTNG"><data key="edge_relationship_id">R47_REL013</data><data key="edge_source_entity_id">DB_SSI_PE_ODS</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_SSTNG</data><data key="edge_operational_context">The same IRS match data can be retrieved immediately through SSTNG; POMS identifies PE ODS as the IRS match data source.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL014" source="EX_SSI_IRS_1099" target="SYS_SSR"><data key="edge_relationship_id">R47_REL014</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">When IRS match tolerances are exceeded, the SSI system posts a 5B diary to the SSR for development.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">The diary is a workload/control indicator, not evidence that unverified IRS address/income data automatically becomes an SSR program fact.</data></edge><edge id="R47_REL015" source="UI_MSSICS_DIRS" target="APP_MSSICS"><data key="edge_relationship_id">R47_REL015</data><data key="edge_source_entity_id">UI_MSSICS_DIRS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">DIRS is identified by POMS as the MSSICS IRS Interface Development path for 5B diaries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL016" source="UI_MSSICS_DIRS" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R47_REL016</data><data key="edge_source_entity_id">UI_MSSICS_DIRS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">DIRS supports documentation and development of SSI IRS 5B interface alerts.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Confirmed data is separately input as SSA program data; the IRS alert remains tax data subject to safeguards.</data></edge><edge id="R47_REL017" source="ORG_USPS" target="DB_USPS_NCOA"><data key="edge_relationship_id">R47_REL017</data><data key="edge_source_entity_id">ORG_USPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DB_USPS_NCOA</data><data key="edge_operational_context">USPS is the source/maintainer of NCOA move data used in SSA matching.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL018" source="DB_USPS_NCOA" target="PROC_NCOA_TITLEII"><data key="edge_relationship_id">R47_REL018</data><data key="edge_source_entity_id">DB_USPS_NCOA</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">PROC_NCOA_TITLEII</data><data key="edge_operational_context">SSA matches Title II address records against USPS NCOA data through a licensed vendor.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL019" source="PROC_NCOA_TITLEII" target="APP_T2R"><data key="edge_relationship_id">R47_REL019</data><data key="edge_source_entity_id">PROC_NCOA_TITLEII</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">Eligible NCOA changes are automatically updated by Title II Redesign when no intervening address change exists.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL020" source="PROC_NCOA_TITLEII" target="SYS_MBR"><data key="edge_relationship_id">R47_REL020</data><data key="edge_source_entity_id">PROC_NCOA_TITLEII</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">NCOA processing conditionally changes Title II mailing addresses on the MBR and records NCOA ZIP flags.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly limits this NCOA process to Title II.</data></edge><edge id="R47_REL021" source="ORG_USPS" target="PROC_MASS_COA_USPS"><data key="edge_relationship_id">R47_REL021</data><data key="edge_source_entity_id">ORG_USPS</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">PROC_MASS_COA_USPS</data><data key="edge_operational_context">USPS reports mass postal changes such as ZIP, city, street, route, or box changes that require SSA action.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL022" source="PROC_MASS_COA_USPS" target="SYS_MBR"><data key="edge_relationship_id">R47_REL022</data><data key="edge_source_entity_id">PROC_MASS_COA_USPS</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Mass postal changes are applied to affected Title II master records.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed process description is older POMS; current physical implementation not inferred.</data></edge><edge id="R47_REL023" source="PROC_MASS_COA_USPS" target="SYS_SSR"><data key="edge_relationship_id">R47_REL023</data><data key="edge_source_entity_id">PROC_MASS_COA_USPS</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Mass postal changes are applied to affected SSI master records, including ZIP-related updates.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed process description is older POMS; current physical implementation not inferred.</data></edge><edge id="R47_REL024" source="DB_ZIP_CODE_MASTER" target="APP_ZIP4_SOFTWARE"><data key="edge_relationship_id">R47_REL024</data><data key="edge_source_entity_id">DB_ZIP_CODE_MASTER</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">APP_ZIP4_SOFTWARE</data><data key="edge_operational_context">SSA describes the ZIP Code Master File as the USPS-based reference file used by ZIP +4 Software.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed implementation description is from 2011.</data></edge><edge id="R47_REL025" source="APP_ZIP4_SOFTWARE" target="SYS_MBR"><data key="edge_relationship_id">R47_REL025</data><data key="edge_source_entity_id">APP_ZIP4_SOFTWARE</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">ZIP maintenance annotates ZIP+4 and delivery-point data to the MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed implementation description is from 2011.</data></edge><edge id="R47_REL026" source="APP_ZIP4_SOFTWARE" target="SYS_SSR"><data key="edge_relationship_id">R47_REL026</data><data key="edge_source_entity_id">APP_ZIP4_SOFTWARE</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">ZIP maintenance annotates ZIP+4 and delivery-point data to the SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed implementation description is from 2011.</data></edge><edge id="R47_REL027" source="APP_DOORS" target="ORG_USPS"><data key="edge_relationship_id">R47_REL027</data><data key="edge_source_entity_id">APP_DOORS</data><data key="edge_relationship_type">interfaces_with</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">POMS documents valid ZIP changes conveyed through an interface between DOORS and a USPS database.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The exact USPS database and transport are not identified.</data></edge><edge id="R47_REL028" source="SYS_MBR" target="PROC_T2_UNDELIV_ADDRESS"><data key="edge_relationship_id">R47_REL028</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_operational_context">Title II undeliverable-mail development first queries the MBR for a current address and records address-development efforts on MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL029" source="SYS_SSR" target="PROC_T2_UNDELIV_ADDRESS"><data key="edge_relationship_id">R47_REL029</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_operational_context">When indicated, technicians query SSR and can treat a later-dated SSI address as more current for Title II address development.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL030" source="PROC_T2_UNDELIV_ADDRESS" target="APP_POS"><data key="edge_relationship_id">R47_REL030</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">A new address developed from SSR, financial institution, USPS, or beneficiary contact is input to the Title II record through POS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL031" source="PROC_T2_UNDELIV_ADDRESS" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R47_REL031</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">For concurrent beneficiaries, if the developed address differs from SSR, the field office updates the new address through the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL032" source="ORG_USPS" target="PROC_T2_UNDELIV_ADDRESS"><data key="edge_relationship_id">R47_REL032</data><data key="edge_source_entity_id">ORG_USPS</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_operational_context">USPS can furnish a current address in Title II undeliverable-mail development through the SSA-L2001 request path.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL033" source="SYS_MBR" target="APP_PEBES"><data key="edge_relationship_id">R47_REL033</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">For people receiving Medicare benefits, SSA uses the mailing address stored on MBR for automatic Social Security Statements.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R47_REL034" source="DB_SIPEBES_TERRITORY_ADDRESS" target="APP_PEBES"><data key="edge_relationship_id">R47_REL034</data><data key="edge_source_entity_id">DB_SIPEBES_TERRITORY_ADDRESS</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">Territorial taxpayer address data supports Statement mailing for eligible residents of Puerto Rico and U.S. territories where federal-return addresses are unavailable.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Current POMS confirms territorial revenue-agency files as an address source; current physical use of the historical Territory Address System is not separately confirmed.</data></edge><edge id="R47_REL035" source="EX_SSI_IRS_1099" target="EX_CMA1016_IRS_DISFLA"><data key="edge_relationship_id">R47_REL035</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">corresponds_to</data><data key="edge_target_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_operational_context">The POMS-described SSI/IRS 1099 interface and current CMA 1016 DIFSLA match share the same Title XVI finder-file / IRS unearned-income IRMF pattern; modeled as corresponding program representations pending hardening/consolidation.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Retain both historical Atlas entities for continuity; current evidence strongly indicates they represent the same matching-program family, but labels and prior scope descriptions differ.</data></edge><edge id="R48_REL001" source="PROC_T2_DIRECT_COA" target="UI_POS_PEAD"><data key="edge_relationship_id">R48_REL001</data><data key="edge_source_entity_id">PROC_T2_DIRECT_COA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_POS_PEAD</data><data key="edge_operational_context">Direct Title II COA policy points technicians to the PEAD screen for the COA action.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed direct-input policy is older but remains in the current COA subchapter.</data></edge><edge id="R48_REL002" source="PROC_T2_DIRECT_COA" target="APP_T2R"><data key="edge_relationship_id">R48_REL002</data><data key="edge_source_entity_id">PROC_T2_DIRECT_COA</data><data key="edge_relationship_type">processed_by</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">Direct COA policy references the Address Change/Name Correction process via Title II Redesign.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Current POMS uses T2R terminology even though the old T2R PIA is listed as retired/obsolete; physical system boundary remains uncertain.</data></edge><edge id="R48_REL003" source="PROC_T2_DIRECT_COA" target="SYS_MBR"><data key="edge_relationship_id">R48_REL003</data><data key="edge_source_entity_id">PROC_T2_DIRECT_COA</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II direct COA processing updates the Master Beneficiary Record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL004" source="PROC_T2_DIRECT_COA" target="SYS_SSR"><data key="edge_relationship_id">R48_REL004</data><data key="edge_source_entity_id">PROC_T2_DIRECT_COA</data><data key="edge_relationship_type">may_require_separate_update_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">For dual SSI/RSDI cases, POMS requires a separate input to SSR when an SSI address change is necessary.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">A single transaction does not change both MBR and SSR in the documented SSI procedure.</data></edge><edge id="R48_REL005" source="UI_POS_PEAD" target="APP_POS"><data key="edge_relationship_id">R48_REL005</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">POMS identifies PEAD as the Post Entitlement System Address/Direct Deposit/Phone screen.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL006" source="UI_POS_PEAD" target="SYS_MBR"><data key="edge_relationship_id">R48_REL006</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PEAD is the current POS path for Title II post-entitlement address/direct-deposit/phone changes reflected in Title II records.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Business input relationship; exact database transaction mechanism is not public.</data></edge><edge id="R48_REL007" source="UI_POS_PEAF" target="APP_POS"><data key="edge_relationship_id">R48_REL007</data><data key="edge_source_entity_id">UI_POS_PEAF</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">POMS identifies PEAF as the future POS Address/Direct Deposit/Phone path.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL008" source="UI_POS_PEAF" target="SYS_MBR"><data key="edge_relationship_id">R48_REL008</data><data key="edge_source_entity_id">UI_POS_PEAF</data><data key="edge_relationship_type">schedules_future_changes_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PEAF is used for future payment address/direct-deposit/telephone changes up to three months ahead.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">POMS establishes future Title II processing but not the internal pending-transaction store.</data></edge><edge id="R48_REL009" source="UI_POS_PEAD" target="UI_POS_PELF"><data key="edge_relationship_id">R48_REL009</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">can_invoke</data><data key="edge_target_entity_id">UI_POS_PELF</data><data key="edge_operational_context">A domestic-to-foreign PEAD path can include PELF Alien Tax Update.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL010" source="UI_POS_PEAD" target="UI_POS_NUSC"><data key="edge_relationship_id">R48_REL010</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">can_invoke</data><data key="edge_target_entity_id">UI_POS_NUSC</data><data key="edge_operational_context">A domestic-to-foreign PEAD path can include NUSC Non-U.S. Citizen Coding.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL011" source="UI_POS_PEAD" target="UI_POS_LEUS"><data key="edge_relationship_id">R48_REL011</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">can_invoke</data><data key="edge_target_entity_id">UI_POS_LEUS</data><data key="edge_operational_context">A domestic-to-foreign PEAD path can include LEUS to annotate the date the beneficiary left the United States.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL012" source="DATA_SSR_AD" target="SYS_SSR"><data key="edge_relationship_id">R48_REL012</data><data key="edge_source_entity_id">DATA_SSR_AD</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS explicitly defines AD as an address field on the Supplemental Security Record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL013" source="DATA_SSR_RA" target="SYS_SSR"><data key="edge_relationship_id">R48_REL013</data><data key="edge_source_entity_id">DATA_SSR_RA</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS explicitly defines RA as a residence/address field on the Supplemental Security Record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL014" source="UI_SSI_APID" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R48_REL014</data><data key="edge_source_entity_id">UI_SSI_APID</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current redetermination policy identifies APID under the General ID tab in the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL015" source="UI_SSI_APID" target="DATA_SSR_AD"><data key="edge_relationship_id">R48_REL015</data><data key="edge_source_entity_id">UI_SSI_APID</data><data key="edge_relationship_type">documents</data><data key="edge_target_entity_id">DATA_SSR_AD</data><data key="edge_operational_context">Current SSI Claims System guidance uses APID to document the mailing address; SSR policy identifies AD as the mailing-address field.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Logical documentation lineage; no direct screen-to-field technical mapping is asserted beyond policy semantics.</data></edge><edge id="R48_REL016" source="UI_SSI_LRES" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R48_REL016</data><data key="edge_source_entity_id">UI_SSI_LRES</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current redetermination policy identifies LRES under the Living Arrangements tab in the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL017" source="UI_SSI_LRES" target="DATA_SSR_RA"><data key="edge_relationship_id">R48_REL017</data><data key="edge_source_entity_id">UI_SSI_LRES</data><data key="edge_relationship_type">documents</data><data key="edge_target_entity_id">DATA_SSR_RA</data><data key="edge_operational_context">Current SSI Claims System guidance uses LRES to document residence; SSR policy identifies RA as the residence/address field.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Logical documentation lineage; field semantics can vary for representative-payee cases.</data></edge><edge id="R48_REL018" source="UI_MSSICS_ADDR" target="APP_MSSICS"><data key="edge_relationship_id">R48_REL018</data><data key="edge_source_entity_id">UI_MSSICS_ADDR</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS references MSOM MSSICS 008.005 Mailing/Payment Address (ADDR).</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL019" source="EXT_MA_DTA_CONNECT" target="EX_SASRO"><data key="edge_relationship_id">R48_REL019</data><data key="edge_source_entity_id">EXT_MA_DTA_CONNECT</data><data key="edge_relationship_type">implements_state_access_under</data><data key="edge_target_entity_id">EX_SASRO</data><data key="edge_operational_context">Massachusetts DTA Connect is the online state-record access implementation used under the SASRO agreement.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL020" source="EXT_MA_DTA_CONNECT" target="SYS_MA_BEACON"><data key="edge_relationship_id">R48_REL020</data><data key="edge_source_entity_id">EXT_MA_DTA_CONNECT</data><data key="edge_relationship_type">provides_inquiry_access_to</data><data key="edge_target_entity_id">SYS_MA_BEACON</data><data key="edge_operational_context">SSA employees obtain inquiry-only access to Massachusetts DTA BEACON records through DTA Connect.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R48_REL021" source="EXT_MA_DTA_CONNECT" target="DOM_TITLE16"><data key="edge_relationship_id">R48_REL021</data><data key="edge_source_entity_id">EXT_MA_DTA_CONNECT</data><data key="edge_relationship_type">provides_collateral_address_evidence_for</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">DTA recipient addresses and phone numbers can assist SSI interviews/redeterminations but are collateral data and must be verified with other sources.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This relationship does not treat State address data as automatically verified or automatically posted to an SSA master record.</data></edge><edge id="R48_REL022" source="EXT_MA_DTA_CONNECT" target="APP_MCS"><data key="edge_relationship_id">R48_REL022</data><data key="edge_source_entity_id">EXT_MA_DTA_CONNECT</data><data key="edge_relationship_type">can_be_documented_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS says online SASRO verifications may be documented for MCS and other SSA systems with audit-trail details.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Does not imply an automated DTA Connect-to-MCS interface.</data></edge><edge id="R48_REL023" source="EXT_MA_DTA_CONNECT" target="APP_CCE"><data key="edge_relationship_id">R48_REL023</data><data key="edge_source_entity_id">EXT_MA_DTA_CONNECT</data><data key="edge_relationship_type">can_be_documented_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">POMS says online SASRO verifications may be documented for CCE and other SSA systems with audit-trail details.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Does not imply an automated DTA Connect-to-CCE interface.</data></edge><edge id="R48_REL024" source="DATA_SSNEC_APP_MAIL_ADDR" target="APP_SSNEC"><data key="edge_relationship_id">R48_REL024</data><data key="edge_source_entity_id">DATA_SSNEC_APP_MAIL_ADDR</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">APP_SSNEC</data><data key="edge_operational_context">SSNEC PIA describes SSN application mailing addresses among information maintained in the SSNEC environment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Broader address scope is from 2007 PIA; current 60-0058 explicitly names mailing addresses for suspect/fraud applications.</data></edge><edge id="R48_REL025" source="APP_SSNEC" target="SYS_NUMIDENT"><data key="edge_relationship_id">R48_REL025</data><data key="edge_source_entity_id">APP_SSNEC</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSNEC establishes and corrects SSN application/identity records in the enumeration environment covered by 60-0058; current SORN says the system ensures enumeration-related information is accurate in other SSA systems.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is logical/functional; no undocumented physical database interface is asserted.</data></edge><edge id="R49_REL001" source="APP_PERSON_INFO" target="DOM_PERSON_CUSTOMER_RECORD"><data key="edge_relationship_id">R49_REL001</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">implements_enterprise_authoritative_record_for</data><data key="edge_target_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="edge_operational_context">FY2025 budget positions PI as SSA’s Customer Record database and enterprise-level authoritative source for customer-related Identity, Death, Citizenship, Contact, Marriage, and Accommodation information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Logical enterprise record relationship; does not imply all program data is physically centralized in PI.</data></edge><edge id="R49_REL002" source="APP_PERSON_INFO" target="SYS_NUMIDENT"><data key="edge_relationship_id">R49_REL002</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">provides_query_access_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS instructs employees to use Person Information via IMAIN to access the Numident query for official death information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL003" source="DATA_PI_ARN" target="APP_PERSON_INFO"><data key="edge_relationship_id">R49_REL003</data><data key="edge_source_entity_id">DATA_PI_ARN</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current claims policy directs staff to enter the Alien Registration Number (A-Number/ARN) in Person Information when present on immigration evidence.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL004" source="DATA_PI_ARN" target="SVC_SAVE"><data key="edge_relationship_id">R49_REL004</data><data key="edge_source_entity_id">DATA_PI_ARN</data><data key="edge_relationship_type">used_as_query_identifier_for</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">SSA uses the A-Number as an identifier to query online SAVE when verifying immigration status.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL005" source="APP_IAPPT" target="APP_PERSON_INFO"><data key="edge_relationship_id">R49_REL005</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">does_not_automatically_update</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current iAppt policy states unverified internet data does not automatically correct Person Information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Negative boundary is explicit and important for provenance.</data></edge><edge id="R49_REL006" source="APP_IAPPT" target="SYS_NUMIDENT"><data key="edge_relationship_id">R49_REL006</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">does_not_automatically_update</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current iAppt policy states unverified internet data does not automatically correct the Numident.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Negative boundary is explicit and important for provenance.</data></edge><edge id="R49_REL007" source="PROJ_NUMIDENT_VERIFY_CONSOLIDATION" target="APP_CENTRAL_DATA_EXCHANGE_UNNAMED"><data key="edge_relationship_id">R49_REL007</data><data key="edge_source_entity_id">PROJ_NUMIDENT_VERIFY_CONSOLIDATION</data><data key="edge_relationship_type">expands_existing_centralized_application</data><data key="edge_target_entity_id">APP_CENTRAL_DATA_EXCHANGE_UNNAMED</data><data key="edge_operational_context">OIG says SSA already combined several data-exchange systems into a centralized application in FY2026 and plans to incorporate some Numident-verification systems into that application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL008" source="APP_CENTRAL_DATA_EXCHANGE_UNNAMED" target="DOM_SSNV"><data key="edge_relationship_id">R49_REL008</data><data key="edge_source_entity_id">APP_CENTRAL_DATA_EXCHANGE_UNNAMED</data><data key="edge_relationship_type">planned_to_incorporate_some</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">OIG says SSA plans to incorporate some Numident verification systems into the centralized application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Specific verification systems are not named.</data></edge><edge id="R49_REL009" source="PROC_RP_COA" target="APP_ERPS"><data key="edge_relationship_id">R49_REL009</data><data key="edge_source_entity_id">PROC_RP_COA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Representative-payee address changes are recorded through eRPS, with program-specific follow-on behavior.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL010" source="APP_ERPS" target="SYS_MBR"><data key="edge_relationship_id">R49_REL010</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">automatically_updates_individual_payee_address_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For Title II individual payees, POMS says eRPS COA input is automatically sent to the MBR the night following the change.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL011" source="APP_ERPS" target="SYS_SSR"><data key="edge_relationship_id">R49_REL011</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">requires_manual_companion_update_for_individual_payee_address_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">For Title XVI individual payees, staff first record the change in eRPS and then use MSSICS to build the SSR because eRPS does not send the address change to the SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL012" source="PROC_RP_COA" target="APP_MSSICS"><data key="edge_relationship_id">R49_REL012</data><data key="edge_source_entity_id">PROC_RP_COA</data><data key="edge_relationship_type">uses_for_title_xvi_individual_payee</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Title XVI individual-payee COA requires MSSICS action after eRPS to build/update the SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL013" source="APP_ERPS" target="SYS_MBR"><data key="edge_relationship_id">R49_REL013</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">automatically_updates_institutional_payee_address_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For institutional payees, POMS says eRPS COA automatically updates associated Title II records correctly established on eRPS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL014" source="APP_ERPS" target="SYS_SSR"><data key="edge_relationship_id">R49_REL014</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">automatically_updates_institutional_payee_address_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">For institutional payees, POMS says eRPS COA automatically updates associated Title XVI records correctly established on eRPS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL015" source="APP_MACADE" target="APP_ERPS"><data key="edge_relationship_id">R49_REL015</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">requires_separate_representative_payee_address_update_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">A MACADE COA input requires a separate eRPS input to update the representative-payee database.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL016" source="PROC_RP_COA" target="APP_POS"><data key="edge_relationship_id">R49_REL016</data><data key="edge_source_entity_id">PROC_RP_COA</data><data key="edge_relationship_type">uses_for_documented_exceptions</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Specified representative-payee COA exceptions, including payment-cycle cutoff and domestic/foreign changes, require POS plus eRPS input.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL017" source="PROC_SSI_WU_S06" target="SYS_SSR"><data key="edge_relationship_id">R49_REL017</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Locate efforts require checking SSR for telephone/address and later for current COA/payment status before suspension.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL018" source="PROC_SSI_WU_S06" target="SYS_MBR"><data key="edge_relationship_id">R49_REL018</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Locate efforts require checking MBR, when applicable, for telephone/address and current COA/payment status.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL019" source="PROC_SSI_WU_S06" target="FORM_SSA_L2001"><data key="edge_relationship_id">R49_REL019</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA_L2001</data><data key="edge_operational_context">POMS directs the field office to send SSA-L2001 to the Postal Service for a current address.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL020" source="FORM_SSA_L2001" target="ORG_USPS"><data key="edge_relationship_id">R49_REL020</data><data key="edge_source_entity_id">FORM_SSA_L2001</data><data key="edge_relationship_type">requests_current_address_from</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">SSA-L2001 is sent to the Postal Service during whereabouts-unknown development.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL021" source="PROC_SSI_WU_S06" target="APP_DPS"><data key="edge_relationship_id">R49_REL021</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">uses_for_financial_institution_locate_letter</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">When direct deposit is involved, staff can select a bank locate letter in DPS to request a current address from the financial institution.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL022" source="PROC_SSI_WU_S06" target="EX_SASRO"><data key="edge_relationship_id">R49_REL022</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">uses_as_optional_address_lead</data><data key="edge_target_entity_id">EX_SASRO</data><data key="edge_operational_context">SASRO state records may reveal a different address and trigger further development.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">POMS treats the state record as a lead; no automatic master-record update is inferred.</data></edge><edge id="R49_REL023" source="PROC_SSI_WU_S06" target="FORM_SSA5002"><data key="edge_relationship_id">R49_REL023</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">documents_development_in</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">When unable to locate the recipient, field office documents all locate efforts on SSA-5002 or equivalent.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL024" source="PROC_SSI_WU_S06" target="IFACE_SSI_DIRECT_SSR"><data key="edge_relationship_id">R49_REL024</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">may_suspend_via</data><data key="edge_target_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_operational_context">POMS permits S06 suspension through Direct SSR Update in MSSICS in specified returned-check/whereabouts-unknown processing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL025" source="PROC_SSI_WU_S06" target="SYS_SSR"><data key="edge_relationship_id">R49_REL025</data><data key="edge_source_entity_id">PROC_SSI_WU_S06</data><data key="edge_relationship_type">updates_payment_status_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Successful S06 input changes the SSI record to whereabouts-unknown suspension status.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL026" source="PROC_T16_UNDELIV_ADDRESS" target="PROC_SSI_WU_S06"><data key="edge_relationship_id">R49_REL026</data><data key="edge_source_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_relationship_type">invokes_when_location_efforts_fail</data><data key="edge_target_entity_id">PROC_SSI_WU_S06</data><data key="edge_operational_context">Current Title XVI undeliverable-notice policy directs field offices to the whereabouts-unknown/S06 instructions when locate efforts fail.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL027" source="PROC_T16_UNDELIV_ADDRESS" target="SYS_SSR"><data key="edge_relationship_id">R49_REL027</data><data key="edge_source_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_relationship_type">corrects_address_when_verified</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">When a new address is found, field office inputs the COA and develops related living-arrangement changes as appropriate.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">POMS says input COA “into the system” but this relationship is kept at SSR program-record level without asserting a specific physical transaction path.</data></edge><edge id="R49_REL028" source="PROC_UNKNOWN_ADDRESS_CLAIM" target="SYS_MEF"><data key="edge_relationship_id">R49_REL028</data><data key="edge_source_entity_id">PROC_UNKNOWN_ADDRESS_CLAIM</data><data key="edge_relationship_type">queries_for_location_leads</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Current Title II policy explicitly says query MEF for leads when claimant whereabouts become unknown.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">MEF is a lead source; this does not make MEF an authoritative current-address store.</data></edge><edge id="R49_REL029" source="PROC_UNKNOWN_ADDRESS_CLAIM" target="SYS_SSR"><data key="edge_relationship_id">R49_REL029</data><data key="edge_source_entity_id">PROC_UNKNOWN_ADDRESS_CLAIM</data><data key="edge_relationship_type">queries_for_location_leads</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current Title II policy explicitly says query SSR for leads when claimant whereabouts become unknown.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">SSR is a program record and may provide a lead; validity must be developed in context.</data></edge><edge id="R49_REL030" source="PROC_UNKNOWN_ADDRESS_CLAIM" target="UI_MCS_ADDR"><data key="edge_relationship_id">R49_REL030</data><data key="edge_source_entity_id">PROC_UNKNOWN_ADDRESS_CLAIM</data><data key="edge_relationship_type">records_last_known_address_in</data><data key="edge_target_entity_id">UI_MCS_ADDR</data><data key="edge_operational_context">Current procedure says show the number holder’s last-known address on MCS ADDR when immediate claim processing is necessary.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL031" source="PROC_UNKNOWN_ADDRESS_CLAIM" target="UI_MCS_RPOC"><data key="edge_relationship_id">R49_REL031</data><data key="edge_source_entity_id">PROC_UNKNOWN_ADDRESS_CLAIM</data><data key="edge_relationship_type">documents_development_in</data><data key="edge_target_entity_id">UI_MCS_RPOC</data><data key="edge_operational_context">Current procedure uses MCS RPOC to document locate steps and responses supporting the conclusion that address is unknown.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL032" source="PROC_UNKNOWN_ADDRESS_CLAIM" target="UI_MCS_DECI"><data key="edge_relationship_id">R49_REL032</data><data key="edge_source_entity_id">PROC_UNKNOWN_ADDRESS_CLAIM</data><data key="edge_relationship_type">establishes_control_diary_in</data><data key="edge_target_entity_id">UI_MCS_DECI</data><data key="edge_operational_context">Current procedure establishes a diary to control address development on the MCS DECI screen.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL033" source="PROC_UNKNOWN_ADDRESS_CLAIM" target="SYS_MBR"><data key="edge_relationship_id">R49_REL033</data><data key="edge_source_entity_id">PROC_UNKNOWN_ADDRESS_CLAIM</data><data key="edge_relationship_type">results_in_address_unknown_suspense_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Proper Address Unknown coding causes MBR to update the claim to suspense status S-6.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL034" source="UI_MCS_ADDR" target="APP_MCS"><data key="edge_relationship_id">R49_REL034</data><data key="edge_source_entity_id">UI_MCS_ADDR</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">ADDR is a Modernized Claims System screen used in current unknown-address claim processing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL035" source="UI_MCS_DECI" target="APP_MCS"><data key="edge_relationship_id">R49_REL035</data><data key="edge_source_entity_id">UI_MCS_DECI</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">DECI is a Modernized Claims System screen used to control address-development diaries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL036" source="PROC_UNKNOWN_ADDRESS_CLAIM" target="WF_A101"><data key="edge_relationship_id">R49_REL036</data><data key="edge_source_entity_id">PROC_UNKNOWN_ADDRESS_CLAIM</data><data key="edge_relationship_type">may_fallback_to_manual_processing_via</data><data key="edge_target_entity_id">WF_A101</data><data key="edge_operational_context">When MCS Earnings Computation cannot be used, current procedure allows manual claim processing through A101.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL037" source="PROC_FO_ADDRESS_AS_MAILING" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R49_REL037</data><data key="edge_source_entity_id">PROC_FO_ADDRESS_AS_MAILING</data><data key="edge_relationship_type">uses_office_address_from</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">Under management approval, a field-office street/mailing address can be used as the claimant’s mailing address as a last resort.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL038" source="PROC_FO_ADDRESS_AS_MAILING" target="SYS_MBR"><data key="edge_relationship_id">R49_REL038</data><data key="edge_source_entity_id">PROC_FO_ADDRESS_AS_MAILING</data><data key="edge_relationship_type">may_supply_mailing_address_for</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The policy applies to Title II claimants/beneficiaries; the Atlas records the FO address as a controlled program mailing-address value rather than residence evidence.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The cited section describes the operational policy but does not identify the exact Title II input transaction for every scenario.</data></edge><edge id="R49_REL039" source="PROC_FO_ADDRESS_AS_MAILING" target="SYS_SSR"><data key="edge_relationship_id">R49_REL039</data><data key="edge_source_entity_id">PROC_FO_ADDRESS_AS_MAILING</data><data key="edge_relationship_type">may_supply_mailing_address_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The policy applies to Title XVI claimants/recipients; the FO address can be used as controlled mailing address when alternatives are unavailable.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The cited section describes the operational policy but does not identify the exact Title XVI input transaction for every scenario.</data></edge><edge id="R49_REL040" source="PROC_FO_ADDRESS_AS_MAILING" target="FORM_SSA795"><data key="edge_relationship_id">R49_REL040</data><data key="edge_source_entity_id">PROC_FO_ADDRESS_AS_MAILING</data><data key="edge_relationship_type">documents_authorization_with</data><data key="edge_target_entity_id">FORM_SSA795</data><data key="edge_operational_context">Field-office management obtains and stores signed SSA-795 from the claimant documenting understanding of the FO-address arrangement, subject to stated exceptions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL041" source="FORM_SSA795" target="REPO_EF"><data key="edge_relationship_id">R49_REL041</data><data key="edge_source_entity_id">FORM_SSA795</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">POMS requires the signed SSA-795 for the FO-address workflow to be stored in the electronic folder.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">POMS says electronic folder generically; Atlas does not force it into CEF when the policy does not specify CEF.</data></edge><edge id="R49_REL042" source="UTIL_EDCS_UAT" target="DATA_EVIEW_CASE_DATA"><data key="edge_relationship_id">R49_REL042</data><data key="edge_source_entity_id">UTIL_EDCS_UAT</data><data key="edge_relationship_type">publishes_limited_post_transfer_updates_to</data><data key="edge_target_entity_id">DATA_EVIEW_CASE_DATA</data><data key="edge_operational_context">UAT repropagates limited MCS/MSSICS changes including claimant address; POMS says those updates appear under eView Case Data rather than in disability reports.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL043" source="DATA_EVIEW_CASE_DATA" target="APP_EVIEW"><data key="edge_relationship_id">R49_REL043</data><data key="edge_source_entity_id">DATA_EVIEW_CASE_DATA</data><data key="edge_relationship_type">displayed_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">The Case Data Tab is an eView display for limited data updated after transfer.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL044" source="UTIL_EDCS_UAT" target="FORM_SSA5002"><data key="edge_relationship_id">R49_REL044</data><data key="edge_source_entity_id">UTIL_EDCS_UAT</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">UAT Other Updates can create an SSA-5002 Report of Contact for new or changed generic information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL045" source="FORM_SSA5002" target="REPO_CEF"><data key="edge_relationship_id">R49_REL045</data><data key="edge_source_entity_id">FORM_SSA5002</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">An SSA-5002 created through EDCS UAT is added to the Certified Electronic Folder.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL046" source="UTIL_EDCS_UAT" target="DATA_EDCS_UAT_ALERT"><data key="edge_relationship_id">R49_REL046</data><data key="edge_source_entity_id">UTIL_EDCS_UAT</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_EDCS_UAT_ALERT</data><data key="edge_operational_context">EDCS UAT determines the office holding jurisdiction and notifies it of post-transfer updates; current move policy explicitly calls the address-change notification a UAT Alert.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL047" source="DATA_EDCS_UAT_ALERT" target="ORG_DDS"><data key="edge_relationship_id">R49_REL047</data><data key="edge_source_entity_id">DATA_EDCS_UAT_ALERT</data><data key="edge_relationship_type">notifies</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">When a claimant moves, the field office notifies DDS of the address change in EDCS via a UAT Alert.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R49_REL048" source="DATA_EDCS_UAT_ALERT" target="APP_EVIEW"><data key="edge_relationship_id">R49_REL048</data><data key="edge_source_entity_id">DATA_EDCS_UAT_ALERT</data><data key="edge_relationship_type">associated_case_update_visible_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Address updates propagated through UAT are reflected in eView Case Data for the electronic disability case.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Alert transport itself is not asserted to be stored in eView.</data></edge><edge id="R50_REL001" source="UI_PI_ON_RECORD" target="APP_PERSON_INFO"><data key="edge_relationship_id">R50_REL001</data><data key="edge_source_entity_id">UI_PI_ON_RECORD</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current CCE evidence policy references Person Information on Record (MS 08401.003).</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL002" source="UI_PI_IDENTITY_INFO" target="APP_PERSON_INFO"><data key="edge_relationship_id">R50_REL002</data><data key="edge_source_entity_id">UI_PI_IDENTITY_INFO</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current CCE evidence policy uses the Person Information Identity Information screen for birthplace and birthdate proof information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL003" source="UI_PI_CITIZENSHIP_INFO" target="APP_PERSON_INFO"><data key="edge_relationship_id">R50_REL003</data><data key="edge_source_entity_id">UI_PI_CITIZENSHIP_INFO</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current CCE evidence policy uses the Person Information Citizenship Information screen for citizenship status/proof.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL004" source="DATA_PI_DEATH_SOURCE_NOTIFICATION" target="APP_PERSON_INFO"><data key="edge_relationship_id">R50_REL004</data><data key="edge_source_entity_id">DATA_PI_DEATH_SOURCE_NOTIFICATION</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current policy documents SOURCE OF NOTIFICATION on the Person Information on Record page.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL005" source="DATA_PI_DEATH_SOURCE_NOTIFICATION" target="SYS_MBR"><data key="edge_relationship_id">R50_REL005</data><data key="edge_source_entity_id">DATA_PI_DEATH_SOURCE_NOTIFICATION</data><data key="edge_relationship_type">can_identify_source</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current policy documents SOURCE OF NOTIFICATION value 3 as MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Provenance code relationship; not a claim that MBR is the only death source.</data></edge><edge id="R50_REL006" source="DATA_PI_DEATH_SOURCE_NOTIFICATION" target="ORG_TREASURY"><data key="edge_relationship_id">R50_REL006</data><data key="edge_source_entity_id">DATA_PI_DEATH_SOURCE_NOTIFICATION</data><data key="edge_relationship_type">can_identify_source</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Current policy documents SOURCE OF NOTIFICATION value 4 as Treasury.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Provenance code relationship; not a claim of the physical death-reporting interface.</data></edge><edge id="R50_REL007" source="DB_ONLINE_EVS" target="SYS_NUMIDENT"><data key="edge_relationship_id">R50_REL007</data><data key="edge_source_entity_id">DB_ONLINE_EVS</data><data key="edge_relationship_type">supports_verification_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA Data.gov describes the database as serving several SSN verification systems that verify SSNs against Numident.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL008" source="DB_ONLINE_EVS" target="DOM_SSNV"><data key="edge_relationship_id">R50_REL008</data><data key="edge_source_entity_id">DB_ONLINE_EVS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">SSA catalog classifies this database as supporting SSN verification workloads.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL009" source="ORG_DHS" target="IFACE_CIS2_ENUM_SSA"><data key="edge_relationship_id">R50_REL009</data><data key="edge_source_entity_id">ORG_DHS</data><data key="edge_relationship_type">provides_enumeration_data_via</data><data key="edge_target_entity_id">IFACE_CIS2_ENUM_SSA</data><data key="edge_operational_context">DHS catalog identifies CIS2 Enumeration File - SSA as an outgoing interface providing enumeration data to SSA.</data><data key="edge_observed_as_of">2026-02-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL010" source="IFACE_CIS2_ENUM_SSA" target="DOM_ENUMERATION"><data key="edge_relationship_id">R50_REL010</data><data key="edge_source_entity_id">IFACE_CIS2_ENUM_SSA</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">DHS says the interface provides enumeration data to SSA’s SSN Enumeration system.</data><data key="edge_observed_as_of">2026-02-05</data><data key="edge_confidence">5</data><data key="edge_notes">Exact receiving SSA application is not named in the current partner inventory, so the relationship terminates at the validated Enumeration domain.</data></edge><edge id="R50_REL011" source="APP_ACDV" target="ORG_CREDIT_REPOSITORIES"><data key="edge_relationship_id">R50_REL011</data><data key="edge_source_entity_id">APP_ACDV</data><data key="edge_relationship_type">links_with</data><data key="edge_target_entity_id">ORG_CREDIT_REPOSITORIES</data><data key="edge_operational_context">Current Title II and Title XVI POMS say ACDV links credit bureaus and SSA for consumer debt disputes.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL012" source="APP_ACDV" target="SYS_MBR"><data key="edge_relationship_id">R50_REL012</data><data key="edge_source_entity_id">APP_ACDV</data><data key="edge_relationship_type">verifies_title_ii_debt_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II dispute processing verifies the fact or amount of debt on MBR or ROAR or both.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL013" source="APP_ACDV" target="APP_ROAR"><data key="edge_relationship_id">R50_REL013</data><data key="edge_source_entity_id">APP_ACDV</data><data key="edge_relationship_type">verifies_title_ii_debt_against</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">Title II dispute processing verifies the fact or amount of debt on MBR or ROAR or both.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL014" source="APP_ACDV" target="SYS_SSR"><data key="edge_relationship_id">R50_REL014</data><data key="edge_source_entity_id">APP_ACDV</data><data key="edge_relationship_type">verifies_title_xvi_debt_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI dispute processing verifies the fact or amount of debt on SSR.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL015" source="APP_ACDV" target="ORG_NEPSC"><data key="edge_relationship_id">R50_REL015</data><data key="edge_source_entity_id">APP_ACDV</data><data key="edge_relationship_type">handled_by</data><data key="edge_target_entity_id">ORG_NEPSC</data><data key="edge_operational_context">Current POMS identifies NEPSC as handling the ACDV process.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL016" source="PROC_DEBT_SKIPTRACE" target="ORG_CREDIT_REPOSITORIES"><data key="edge_relationship_id">R50_REL016</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">uses_address_lead_from</data><data key="edge_target_entity_id">ORG_CREDIT_REPOSITORIES</data><data key="edge_operational_context">Published skiptracing procedure directs staff to request an online address from a credit bureau when no new address is available.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes">Procedure revision is old but retained in current subchapter.</data></edge><edge id="R50_REL017" source="PROC_DEBT_SKIPTRACE" target="SYS_MBR"><data key="edge_relationship_id">R50_REL017</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">checks_address_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Published procedure checks MBR/SSR/RECOOP for recent address changes.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R50_REL018" source="PROC_DEBT_SKIPTRACE" target="SYS_SSR"><data key="edge_relationship_id">R50_REL018</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">checks_address_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Published procedure checks MBR/SSR/RECOOP for recent address changes.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R50_REL019" source="PROC_DEBT_SKIPTRACE" target="SYS_MEF"><data key="edge_relationship_id">R50_REL019</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">checks_employer_leads_in</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Published skiptracing resource list identifies MEF for employer leads.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R50_REL020" source="PROC_DEBT_SKIPTRACE" target="ORG_STATE_DMV"><data key="edge_relationship_id">R50_REL020</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">uses_location_lead_from</data><data key="edge_target_entity_id">ORG_STATE_DMV</data><data key="edge_operational_context">Published skiptracing resource list identifies Departments of Motor Vehicles.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes">No automated interface is established.</data></edge><edge id="R50_REL021" source="PROC_DEBT_SKIPTRACE" target="ORG_USPS"><data key="edge_relationship_id">R50_REL021</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">uses_location_lead_from</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">Published skiptracing resource list identifies the Post Office.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes">No automated interface is established by this source.</data></edge><edge id="R50_REL022" source="PROC_DEBT_SKIPTRACE" target="SYS_MBR"><data key="edge_relationship_id">R50_REL022</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">updates_address_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">If a new address is obtained from the credit bureau, published procedure directs staff to update MBR/SSR and RECOOP when appropriate.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes">Controlled debt-collection procedure; not automatic credit-bureau-to-MBR propagation.</data></edge><edge id="R50_REL023" source="PROC_DEBT_SKIPTRACE" target="SYS_SSR"><data key="edge_relationship_id">R50_REL023</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">updates_address_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">If a new address is obtained from the credit bureau, published procedure directs staff to update MBR/SSR and RECOOP when appropriate.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes">Controlled debt-collection procedure; not automatic credit-bureau-to-SSR propagation.</data></edge><edge id="R50_REL024" source="PROC_DEBT_SKIPTRACE" target="APP_RECOOP"><data key="edge_relationship_id">R50_REL024</data><data key="edge_source_entity_id">PROC_DEBT_SKIPTRACE</data><data key="edge_relationship_type">updates_address_in</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context">If a new address is obtained from the credit bureau, published procedure directs staff to update MBR/SSR and RECOOP when appropriate.</data><data key="edge_observed_as_of">2025-11-20</data><data key="edge_confidence">4</data><data key="edge_notes">Controlled debt-collection procedure.</data></edge><edge id="R50_REL025" source="APP_NHRP" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R50_REL025</data><data key="edge_source_entity_id">APP_NHRP</data><data key="edge_relationship_type">integrated_with</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current POMS says the electronic NHRP search process is integrated in the SSI Claims system (MSSICS/SSI claim).</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Logical SSI Claims boundary retained; the public source does not resolve the full CCE/MSSICS physical mapping.</data></edge><edge id="R50_REL026" source="APP_NHRP" target="SVC_LEXISNEXIS_ACCURINT"><data key="edge_relationship_id">R50_REL026</data><data key="edge_source_entity_id">APP_NHRP</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SVC_LEXISNEXIS_ACCURINT</data><data key="edge_operational_context">Current POMS says the NHRP electronic search process uses a LexisNexis|Accurint database.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL027" source="SVC_LEXISNEXIS_ACCURINT" target="APP_NHRP"><data key="edge_relationship_id">R50_REL027</data><data key="edge_source_entity_id">SVC_LEXISNEXIS_ACCURINT</data><data key="edge_relationship_type">provides_unverified_property_leads_to</data><data key="edge_target_entity_id">APP_NHRP</data><data key="edge_operational_context">SSA treats Accurint results as third-party reports used as leads and requiring additional verification.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Do not treat Accurint result as authoritative ownership/address proof.</data></edge><edge id="R50_REL028" source="APP_FIVR" target="ORG_DAPS"><data key="edge_relationship_id">R50_REL028</data><data key="edge_source_entity_id">APP_FIVR</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_DAPS</data><data key="edge_operational_context">Current SSA Vendor Payment Center guidance directs vendor payment inquiries to DAPS and identifies FIVR as its automated self-service telephone channel.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R50_REL029" source="ORG_DAPS" target="SVC_TREASURY_IPP"><data key="edge_relationship_id">R50_REL029</data><data key="edge_source_entity_id">ORG_DAPS</data><data key="edge_relationship_type">directs_vendors_to</data><data key="edge_target_entity_id">SVC_TREASURY_IPP</data><data key="edge_operational_context">Current SSA Vendor Payment Center page directs vendors to Treasury IPP to view payment history and remittance details.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No SSA-side interface mechanism is inferred.</data></edge><edge id="R50_REL030" source="SVC_SAM" target="DB_VENDOR_PAYMENT_UNNAMED"><data key="edge_relationship_id">R50_REL030</data><data key="edge_source_entity_id">SVC_SAM</data><data key="edge_relationship_type">automatically_updates</data><data key="edge_target_entity_id">DB_VENDOR_PAYMENT_UNNAMED</data><data key="edge_operational_context">SSA vendor direct-deposit guidance says changes completed through SAM automatically update SSA’s database.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Database remains unnamed; do not merge with another SSA payment/accounting repository without evidence.</data></edge><edge id="R51_REL001" source="APP_ELAS" target="SYS_ICDB"><data key="edge_relationship_id">R51_REL001</data><data key="edge_source_entity_id">APP_ELAS</data><data key="edge_relationship_type">verified_appointment_data_becomes_part_of</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">Current iAppointments POMS says selecting Verify PI in eLAS after verification allows previously isolated iAppt data to become part of CLIENT/ICDB.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit current POMS path; does not state that eLAS directly corrects Person Information or Numident.</data></edge><edge id="R51_REL002" source="SYS_ICDB" target="DATA_CLIENT_LANGUAGE_PREF"><data key="edge_relationship_id">R51_REL002</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">historically_documented_to_include_attribute</data><data key="edge_target_entity_id">DATA_CLIENT_LANGUAGE_PREF</data><data key="edge_operational_context">2007 ICDB PIA explicitly lists language preference for written and spoken communication as Client Data; current 2026 inventory separately catalogs a CLIENT-tagged language-preference asset.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">This establishes historical ICDB inclusion plus current CLIENT-domain continuity, but does not prove the present physical storage/extract topology of US-GOV-SSA-568.</data></edge><edge id="R51_REL003" source="APP_CSRQ" target="UTIL_GUNSCHIP"><data key="edge_relationship_id">R51_REL003</data><data key="edge_source_entity_id">APP_CSRQ</data><data key="edge_relationship_type">uses_numident_utility</data><data key="edge_target_entity_id">UTIL_GUNSCHIP</data><data key="edge_operational_context">Current SSA inventory names CSRQ among applications that use the GUNSCHIP/GUNPUC03 utility family to retrieve Numident data.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Inventory names the application and utility family collectively; it does not state that every listed application calls both utilities in every transaction.</data></edge><edge id="R51_REL004" source="APP_CSRQ" target="UTIL_GUNPUC03"><data key="edge_relationship_id">R51_REL004</data><data key="edge_source_entity_id">APP_CSRQ</data><data key="edge_relationship_type">uses_numident_utility</data><data key="edge_target_entity_id">UTIL_GUNPUC03</data><data key="edge_operational_context">Current SSA inventory names CSRQ among applications that use the GUNSCHIP/GUNPUC03 utility family to retrieve Numident data.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Inventory names the application and utility family collectively; it does not state that every listed application calls both utilities in every transaction.</data></edge><edge id="R51_REL005" source="SVC_FPLS" target="EX_FPLS_DRLIF"><data key="edge_relationship_id">R51_REL005</data><data key="edge_source_entity_id">SVC_FPLS</data><data key="edge_relationship_type">contains_exchange</data><data key="edge_target_entity_id">EX_FPLS_DRLIF</data><data key="edge_operational_context">SSA inventory explicitly says FPLS contains the DRLIF exchange.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL006" source="SVC_FPLS" target="EX_FPLS_ESKARI"><data key="edge_relationship_id">R51_REL006</data><data key="edge_source_entity_id">SVC_FPLS</data><data key="edge_relationship_type">contains_exchange</data><data key="edge_target_entity_id">EX_FPLS_ESKARI</data><data key="edge_operational_context">SSA inventory explicitly says FPLS contains the ESKARI exchange.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL007" source="ORG_OCSE" target="EX_FPLS_DRLIF"><data key="edge_relationship_id">R51_REL007</data><data key="edge_source_entity_id">ORG_OCSE</data><data key="edge_relationship_type">submits_known_ssn_finder_file_to</data><data key="edge_target_entity_id">EX_FPLS_DRLIF</data><data key="edge_operational_context">OCSE submits a known-SSN finder file daily for DRLIF processing.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL008" source="ORG_OCSE" target="EX_FPLS_ESKARI"><data key="edge_relationship_id">R51_REL008</data><data key="edge_source_entity_id">ORG_OCSE</data><data key="edge_relationship_type">submits_unknown_ssn_finder_file_to</data><data key="edge_target_entity_id">EX_FPLS_ESKARI</data><data key="edge_operational_context">OCSE submits unknown-SSN finder records daily for ESKARI processing.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL009" source="EX_FPLS_ESKARI" target="EX_FPLS_DRLIF"><data key="edge_relationship_id">R51_REL009</data><data key="edge_source_entity_id">EX_FPLS_ESKARI</data><data key="edge_relationship_type">feeds_identified_ssns_to</data><data key="edge_target_entity_id">EX_FPLS_DRLIF</data><data key="edge_operational_context">SSA inventory says SSNs identified through ESKARI are recycled into DRLIF for normal processing.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL010" source="EX_FPLS_DRLIF" target="ORG_OCSE"><data key="edge_relationship_id">R51_REL010</data><data key="edge_source_entity_id">EX_FPLS_DRLIF</data><data key="edge_relationship_type">returns_employer_addresses_and_wages_to</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">DRLIF identifies employer address information for up to ten recent employers over four years and wage amounts for child-support locate use.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">The catalog record does not name the internal SSA repositories used to produce these response fields.</data></edge><edge id="R51_REL011" source="DATA_BEPUF_2020" target="DATA_BEPUF2020_BENEFITS"><data key="edge_relationship_id">R51_REL011</data><data key="edge_source_entity_id">DATA_BEPUF_2020</data><data key="edge_relationship_type">contains_subfile</data><data key="edge_target_entity_id">DATA_BEPUF2020_BENEFITS</data><data key="edge_operational_context">BEPUF 2020 documentation identifies a Benefits Subfile as one of the published files.</data><data key="edge_observed_as_of">2026-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL012" source="DATA_BEPUF_2020" target="DATA_BEPUF2020_EARNINGS"><data key="edge_relationship_id">R51_REL012</data><data key="edge_source_entity_id">DATA_BEPUF_2020</data><data key="edge_relationship_type">contains_subfile</data><data key="edge_target_entity_id">DATA_BEPUF2020_EARNINGS</data><data key="edge_operational_context">BEPUF 2020 documentation identifies an Earnings Subfile as one of the published files.</data><data key="edge_observed_as_of">2026-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL013" source="DATA_BEPUF2020_BENEFITS" target="DATA_BEPUF2020_EARNINGS"><data key="edge_relationship_id">R51_REL013</data><data key="edge_source_entity_id">DATA_BEPUF2020_BENEFITS</data><data key="edge_relationship_type">record_linked_by_synthetic_id_to</data><data key="edge_target_entity_id">DATA_BEPUF2020_EARNINGS</data><data key="edge_operational_context">SSA states the two subfiles are linked at record level by a synthetic beneficiary identifier.</data><data key="edge_observed_as_of">2026-04</data><data key="edge_confidence">5</data><data key="edge_notes">SSA cautions that the earnings-to-monthly-benefit relationship is statistically modeled, not a program-rule computation for an individual record.</data></edge><edge id="R51_REL014" source="SYS_MBR" target="DATA_OACT_OASDI_BEN_STATS"><data key="edge_relationship_id">R51_REL014</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_publication</data><data key="edge_target_entity_id">DATA_OACT_OASDI_BEN_STATS</data><data key="edge_operational_context">OACT explicitly states the beneficiary-statistics table provides unedited data from MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL015" source="SYS_MBR" target="DATA_OASDI_ZIP_2024"><data key="edge_relationship_id">R51_REL015</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_publication</data><data key="edge_target_entity_id">DATA_OASDI_ZIP_2024</data><data key="edge_operational_context">SSA states the ZIP publication statistics are derived from MBR, the principal administrative file of Social Security beneficiaries.</data><data key="edge_observed_as_of">2026-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL016" source="APP_DOORS" target="DATA_OASDI_ZIP_2024"><data key="edge_relationship_id">R51_REL016</data><data key="edge_source_entity_id">APP_DOORS</data><data key="edge_relationship_type">associates_field_office_data_for</data><data key="edge_target_entity_id">DATA_OASDI_ZIP_2024</data><data key="edge_operational_context">SSA says DOORS is used to associate field-office data with ZIP Codes for this publication.</data><data key="edge_observed_as_of">2026-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R51_REL017" source="ORG_USPS" target="DATA_OASDI_ZIP_2024"><data key="edge_relationship_id">R51_REL017</data><data key="edge_source_entity_id">ORG_USPS</data><data key="edge_relationship_type">provides_geographic_data_for</data><data key="edge_target_entity_id">DATA_OASDI_ZIP_2024</data><data key="edge_operational_context">SSA identifies USPS geographic data as a source for the ZIP publication.</data><data key="edge_observed_as_of">2026-03</data><data key="edge_confidence">5</data><data key="edge_notes">This is publication geography input, not evidence of an individual-address master-record update.</data></edge><edge id="R51_REL018" source="DB_FINANCE_IVR" target="APP_FIVR"><data key="edge_relationship_id">R51_REL018</data><data key="edge_source_entity_id">DB_FINANCE_IVR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_FIVR</data><data key="edge_operational_context">The current SSA inventory describes the Finance IVR database as storing information that supports phone access to vendor invoice/payment status reports through an IVR capability.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Closes the previously unmapped relationship between the database asset and FIVR application; backend source systems feeding the database remain undocumented.</data></edge><edge id="R52_REL001" source="UI_PI_CONTACT" target="APP_PERSON_INFO"><data key="edge_relationship_id">R52_REL001</data><data key="edge_source_entity_id">UI_PI_CONTACT</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current POMS references Person Information Contact Information as the contact/address UI.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">MS 08401.005.</data></edge><edge id="R52_REL002" source="UI_PI_MARRIAGE" target="APP_PERSON_INFO"><data key="edge_relationship_id">R52_REL002</data><data key="edge_source_entity_id">UI_PI_MARRIAGE</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current SSI policy references Person Information Marriage Information Details.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">MS 08401.008.</data></edge><edge id="R52_REL003" source="UI_PI_DISCREPANCY" target="APP_PERSON_INFO"><data key="edge_relationship_id">R52_REL003</data><data key="edge_source_entity_id">UI_PI_DISCREPANCY</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Retained Title II citizenship instructions use the Person Information discrepancy screen to resolve conflicts.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">MS 08401.004.</data></edge><edge id="R52_REL004" source="PROC_DUAL_COA" target="SYS_MBR"><data key="edge_relationship_id">R52_REL004</data><data key="edge_source_entity_id">PROC_DUAL_COA</data><data key="edge_relationship_type">requires_separate_input_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Dual SSI/RSDI change-of-address processing requires an MBR input separate from the SSR input.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS GN 02605.035.</data></edge><edge id="R52_REL005" source="PROC_DUAL_COA" target="SYS_SSR"><data key="edge_relationship_id">R52_REL005</data><data key="edge_source_entity_id">PROC_DUAL_COA</data><data key="edge_relationship_type">requires_separate_input_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Dual SSI/RSDI change-of-address processing requires an SSR input separate from the MBR input.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS GN 02605.035.</data></edge><edge id="R52_REL006" source="PROC_DUAL_COA" target="UI_PI_CONTACT"><data key="edge_relationship_id">R52_REL006</data><data key="edge_source_entity_id">PROC_DUAL_COA</data><data key="edge_relationship_type">references_contact_information_in</data><data key="edge_target_entity_id">UI_PI_CONTACT</data><data key="edge_operational_context">The current dual-case COA policy includes Person Information Contact Information among its technical references.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Reference establishes workflow relevance but does not prove PI performs either MBR or SSR write.</data></edge><edge id="R52_REL007" source="REPO_EMR" target="DOM_DB_RECORD_METADATA"><data key="edge_relationship_id">R52_REL007</data><data key="edge_source_entity_id">REPO_EMR</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DOM_DB_RECORD_METADATA</data><data key="edge_operational_context">EMR stores physical and logical information about relational databases and record structures.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Current Federal Data Catalog.</data></edge><edge id="R52_REL008" source="UTIL_ESVC_CONTROL_TRACK" target="DOM_E_SERVICES"><data key="edge_relationship_id">R52_REL008</data><data key="edge_source_entity_id">UTIL_ESVC_CONTROL_TRACK</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_E_SERVICES</data><data key="edge_operational_context">Utility assigns and maintains confirmation numbers for tracking information-exchange artifacts in the eServices/IECA context.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Current Federal Data Catalog.</data></edge><edge id="R52_REL009" source="DB_ERE_MI_USAGE" target="APP_ERE"><data key="edge_relationship_id">R52_REL009</data><data key="edge_source_entity_id">DB_ERE_MI_USAGE</data><data key="edge_relationship_type">reports_on_evidence_collected_through</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">The usage-reporting store provides MI on evidence collected electronically through the ERE website.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Current Federal Data Catalog.</data></edge><edge id="R52_REL010" source="DB_ERE_MI_USAGE" target="PLAT_EDIB"><data key="edge_relationship_id">R52_REL010</data><data key="edge_source_entity_id">DB_ERE_MI_USAGE</data><data key="edge_relationship_type">tracks_evidence_prepared_for</data><data key="edge_target_entity_id">PLAT_EDIB</data><data key="edge_operational_context">The usage-reporting store tracks ERE evidence prepared for transition to the eDIB system.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Current Federal Data Catalog.</data></edge><edge id="R52_REL011" source="APP_MYDD" target="APP_MYSSA"><data key="edge_relationship_id">R52_REL011</data><data key="edge_source_entity_id">APP_MYDD</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA states people receiving Social Security benefits can use my Social Security to start or update direct deposit online.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current SSA Open Data.</data></edge><edge id="R52_REL012" source="APP_MYDD" target="SYS_MBR"><data key="edge_relationship_id">R52_REL012</data><data key="edge_source_entity_id">APP_MYDD</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA states internet direct-deposit changes are sent to a database and updated to the MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Unnamed intermediate database is deliberately not equated to a known SSA store.</data></edge><edge id="R52_REL013" source="DATA_DD_INET" target="APP_MYDD"><data key="edge_relationship_id">R52_REL013</data><data key="edge_source_entity_id">DATA_DD_INET</data><data key="edge_relationship_type">measures_transactions_from</data><data key="edge_target_entity_id">APP_MYDD</data><data key="edge_operational_context">Public dataset counts Internet Direct Deposit applications.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes">Current SSA Open Data.</data></edge><edge id="R52_REL014" source="DATA_COA_INET" target="APP_MYCOA"><data key="edge_relationship_id">R52_REL014</data><data key="edge_source_entity_id">DATA_COA_INET</data><data key="edge_relationship_type">measures_transactions_from</data><data key="edge_target_entity_id">APP_MYCOA</data><data key="edge_operational_context">Public dataset counts Internet Change of Address transactions.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes">Current SSA Open Data.</data></edge><edge id="R52_REL015" source="DATA_COA_INET" target="SYS_MBR"><data key="edge_relationship_id">R52_REL015</data><data key="edge_source_entity_id">DATA_COA_INET</data><data key="edge_relationship_type">documents_update_destination</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Dataset documentation states eligible online address changes are updated to MBR.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes">The unnamed intermediate database is not modeled as a known repository.</data></edge><edge id="R52_REL016" source="DATA_MONTHLY_STAT_SNAPSHOT" target="SYS_MBR"><data key="edge_relationship_id">R52_REL016</data><data key="edge_source_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">August 2026 Monthly Statistical Snapshot identifies MBR 100-percent data as the source for Social Security counts/benefits.</data><data key="edge_observed_as_of">2026-09</data><data key="edge_confidence">5</data><data key="edge_notes">Current statistical publication.</data></edge><edge id="R52_REL017" source="DATA_MONTHLY_STAT_SNAPSHOT" target="SYS_SSR"><data key="edge_relationship_id">R52_REL017</data><data key="edge_source_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">August 2026 Monthly Statistical Snapshot identifies SSR 100-percent data as the source for SSI counts/payments.</data><data key="edge_observed_as_of">2026-09</data><data key="edge_confidence">5</data><data key="edge_notes">Current statistical publication.</data></edge><edge id="R52_REL018" source="DATA_FO_CONTACT" target="APP_DOORS"><data key="edge_relationship_id">R52_REL018</data><data key="edge_source_entity_id">DATA_FO_CONTACT</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">APP_DOORS</data><data key="edge_operational_context">SSA states Office of Operations updates DOORS information and that regularly updated information underpins Office Locator.</data><data key="edge_observed_as_of">2026-03-09</data><data key="edge_confidence">5</data><data key="edge_notes">Current SSA Open Data.</data></edge><edge id="R52_REL019" source="DATA_FO_CONTACT" target="SVC_OFFICE_LOCATOR"><data key="edge_relationship_id">R52_REL019</data><data key="edge_source_entity_id">DATA_FO_CONTACT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SVC_OFFICE_LOCATOR</data><data key="edge_operational_context">SSA says the regularly updated field-office information underpins the Social Security Office Locator.</data><data key="edge_observed_as_of">2026-03-09</data><data key="edge_confidence">5</data><data key="edge_notes">Current SSA Open Data.</data></edge><edge id="R52_REL020" source="DATA_RS_CONTACT" target="DATA_FO_CONTACT"><data key="edge_relationship_id">R52_REL020</data><data key="edge_source_entity_id">DATA_RS_CONTACT</data><data key="edge_relationship_type">published_with</data><data key="edge_target_entity_id">DATA_FO_CONTACT</data><data key="edge_operational_context">SSA publishes resident-station and field-office location datasets together for application developers.</data><data key="edge_observed_as_of">2026-03-09</data><data key="edge_confidence">5</data><data key="edge_notes">No physical shared database is inferred.</data></edge><edge id="R53_REL001" source="DB_PERSON_STORE" target="DOM_PERSON_CUSTOMER_RECORD"><data key="edge_relationship_id">R53_REL001</data><data key="edge_source_entity_id">DB_PERSON_STORE</data><data key="edge_relationship_type">physical_data_store_for</data><data key="edge_target_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="edge_operational_context">Current Federal Data Catalog explicitly describes Person as a person-centric data store holding information about SSA customers.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This does not establish that DB_PERSON_STORE is the exact physical backing database of APP_PERSON_INFO.</data></edge><edge id="R53_REL002" source="DB_SUMS_CLIENT_TABLES" target="SYS_ICDB"><data key="edge_relationship_id">R53_REL002</data><data key="edge_source_entity_id">DB_SUMS_CLIENT_TABLES</data><data key="edge_relationship_type">subset_of_client_data_housed_in</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">Federal Data Catalog states Sums Client is a subset of Client data housed in the Integrated Client Database (ICDB).</data><data key="edge_observed_as_of">2026-05-01</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current containment statement; physical table/schema details remain unpublished.</data></edge><edge id="R53_REL003" source="APP_ECO" target="DB_ECO_DATA"><data key="edge_relationship_id">R53_REL003</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">uses_named_data_store</data><data key="edge_target_entity_id">DB_ECO_DATA</data><data key="edge_operational_context">SSA catalogs an External Collection Operation Data File that contains the data needed to maintain delinquent SSA debts; its name and ECO keywords align with the operational ECO subsystem.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship is supported by exact named asset alignment plus existing current POMS coverage of ECO debt maintenance; DBMS/transport are not inferred.</data></edge><edge id="R53_REL004" source="APP_ROAR" target="DB_ROAR_MASTER"><data key="edge_relationship_id">R53_REL004</data><data key="edge_source_entity_id">APP_ROAR</data><data key="edge_relationship_type">uses_named_master_data_store</data><data key="edge_target_entity_id">DB_ROAR_MASTER</data><data key="edge_operational_context">SSA catalogs the Recovery of Overpayments Accounting Reporting Master with ROAR keywords and detailed overpayment accounting/recovery history.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes">Physical DBMS/hosting are not public.</data></edge><edge id="R53_REL005" source="DB_SSI_WAGE_REPORT_HISTORY" target="APP_SSITWR"><data key="edge_relationship_id">R53_REL005</data><data key="edge_source_entity_id">DB_SSI_WAGE_REPORT_HISTORY</data><data key="edge_relationship_type">contains_reporting_history_from</data><data key="edge_target_entity_id">APP_SSITWR</data><data key="edge_operational_context">Catalog describes person-level history of telephone wage reports; SSITWR is the mapped SSA telephone wage-reporting application.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">The public catalog does not document the exact interface or write path.</data></edge><edge id="R53_REL006" source="DB_SSI_WAGE_REPORT_HISTORY" target="APP_SSAMWR"><data key="edge_relationship_id">R53_REL006</data><data key="edge_source_entity_id">DB_SSI_WAGE_REPORT_HISTORY</data><data key="edge_relationship_type">contains_reporting_history_from</data><data key="edge_target_entity_id">APP_SSAMWR</data><data key="edge_operational_context">Catalog describes person-level history of mobile wage reports; SSAMWR is the mapped SSA mobile wage-reporting application.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">The public catalog does not document the exact interface or write path.</data></edge><edge id="R53_REL007" source="DATA_OHO_LOCATION" target="SVC_OHO_LOCATOR"><data key="edge_relationship_id">R53_REL007</data><data key="edge_source_entity_id">DATA_OHO_LOCATION</data><data key="edge_relationship_type">distributed_via</data><data key="edge_target_entity_id">SVC_OHO_LOCATOR</data><data key="edge_operational_context">The Federal Data Catalog lists the OHO Hearing Office Locator HTML page as a distribution of the hearing-office location dataset.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Exact backend production pipeline is not inferred.</data></edge><edge id="R53_REL008" source="APP_FFAP" target="SYS_SSR"><data key="edge_relationship_id">R53_REL008</data><data key="edge_source_entity_id">APP_FFAP</data><data key="edge_relationship_type">posts_suspension_status_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current FFAP POMS states fully or partially automated cases post an N25 period to the SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Transaction is identified in POMS as F02 / Unit FFAP.</data></edge><edge id="R53_REL009" source="APP_FFAP" target="APP_ORS"><data key="edge_relationship_id">R53_REL009</data><data key="edge_source_entity_id">APP_FFAP</data><data key="edge_relationship_type">stores_or_exposes_notice_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Current FFAP POMS states the appropriate automated notice is sent and is available in the Online Retrieval System (ORS).</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R53_REL010" source="APP_FFSCF" target="SYS_MBR"><data key="edge_relationship_id">R53_REL010</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">updates_title_ii_fugitive_data_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current FFSCF POMS states Title II suspension processing establishes or updates FUGITIVE data on the MBR and that FFSCF can be updated from MBR warrant updates.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This is a bidirectional operational relationship at the business-data level; transport is not inferred.</data></edge><edge id="R53_REL011" source="REPORT_FAST_FACTS_2026" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R53_REL011</data><data key="edge_source_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_relationship_type">summarizes_statistics_from</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Fast Facts &amp; Figures 2026 states that most statistics come from the Annual Statistical Supplement.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R53_REL012" source="REPORT_FAST_FACTS_2026" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R53_REL012</data><data key="edge_source_entity_id">REPORT_FAST_FACTS_2026</data><data key="edge_relationship_type">uses_trust_fund_data_from</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Fast Facts &amp; Figures 2026 states trust-fund operations data come from the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL001" source="DB_BORG_CED" target="DOM_PERSON_CUSTOMER_RECORD"><data key="edge_relationship_id">R54_REL001</data><data key="edge_source_entity_id">DB_BORG_CED</data><data key="edge_relationship_type">implements_person_centered_model_for</data><data key="edge_target_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="edge_operational_context">BORG was explicitly designed as a consolidated relational database centered on person rather than program silos.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical person-centered implementation; no current-store continuity is inferred.</data></edge><edge id="R54_REL002" source="DB_BORG_CED" target="DATA_PCLNT_2016"><data key="edge_relationship_id">R54_REL002</data><data key="edge_source_entity_id">DB_BORG_CED</data><data key="edge_relationship_type">loads_person_subject_from</data><data key="edge_target_entity_id">DATA_PCLNT_2016</data><data key="edge_operational_context">BORG Phase 1 Person subject area included Client (PCLNT) data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL003" source="DB_BORG_CED" target="DATA_PACOMM_2016"><data key="edge_relationship_id">R54_REL003</data><data key="edge_source_entity_id">DB_BORG_CED</data><data key="edge_relationship_type">loads_person_subject_from</data><data key="edge_target_entity_id">DATA_PACOMM_2016</data><data key="edge_operational_context">BORG Phase 1 Person subject area included iAccommodate (PACOMM) data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL004" source="DB_BORG_CED" target="SYS_NUMIDENT"><data key="edge_relationship_id">R54_REL004</data><data key="edge_source_entity_id">DB_BORG_CED</data><data key="edge_relationship_type">loads_person_subject_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">BORG Phase 1 Person subject area included Numident (PNUMI) data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">PNUMI is captured as a documented alias of Numident.</data></edge><edge id="R54_REL005" source="DB_BORG_CED" target="DATA_WOUNDED_WARRIOR_2016"><data key="edge_relationship_id">R54_REL005</data><data key="edge_source_entity_id">DB_BORG_CED</data><data key="edge_relationship_type">loads_person_subject_from</data><data key="edge_target_entity_id">DATA_WOUNDED_WARRIOR_2016</data><data key="edge_operational_context">BORG Phase 1 Person subject area included Wounded Warrior data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL006" source="DB_BORG_CED" target="DATA_CLIENT_LANGUAGE_PREF"><data key="edge_relationship_id">R54_REL006</data><data key="edge_source_entity_id">DB_BORG_CED</data><data key="edge_relationship_type">loads_person_subject_from</data><data key="edge_target_entity_id">DATA_CLIENT_LANGUAGE_PREF</data><data key="edge_operational_context">BORG Phase 1 Person subject area included Language Preferences data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical loading relationship does not establish current physical topology of the language-preference asset.</data></edge><edge id="R54_REL007" source="DB_BORG_CED" target="SYS_MEF"><data key="edge_relationship_id">R54_REL007</data><data key="edge_source_entity_id">DB_BORG_CED</data><data key="edge_relationship_type">loads_earnings_subject_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">BORG Phase 2 Earnings subject area contained data from the Master Earnings File (PMEF).</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">PMEF is captured as a documented alias of MEF.</data></edge><edge id="R54_REL008" source="APP_CET_SUITE_2016" target="DB_BORG_CED"><data key="edge_relationship_id">R54_REL008</data><data key="edge_source_entity_id">APP_CET_SUITE_2016</data><data key="edge_relationship_type">planned_key_consumer_of</data><data key="edge_target_entity_id">DB_BORG_CED</data><data key="edge_operational_context">SSA identified the Customer Engagement Tools Application Suite as a future key target consumer of BORG.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This is a planned 2016 consumer relationship, not proof of later production use.</data></edge><edge id="R54_REL009" source="PLAT_ACI_2016" target="DB_BORG_CED"><data key="edge_relationship_id">R54_REL009</data><data key="edge_source_entity_id">PLAT_ACI_2016</data><data key="edge_relationship_type">provisions_resources_for</data><data key="edge_target_entity_id">DB_BORG_CED</data><data key="edge_operational_context">SSA planned to use ACI compute, storage, and network resources to support BORG CED.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL010" source="PLAT_ACI_2016" target="PLAT_MDE"><data key="edge_relationship_id">R54_REL010</data><data key="edge_source_entity_id">PLAT_ACI_2016</data><data key="edge_relationship_type">provisions_resources_for</data><data key="edge_target_entity_id">PLAT_MDE</data><data key="edge_operational_context">SSA planned to use ACI resources to support the Modern Development Environment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL011" source="PLAT_ACI_2016" target="DW_EDW_2016"><data key="edge_relationship_id">R54_REL011</data><data key="edge_source_entity_id">PLAT_ACI_2016</data><data key="edge_relationship_type">provisions_resources_for</data><data key="edge_target_entity_id">DW_EDW_2016</data><data key="edge_operational_context">SSA planned to use ACI resources to support the Enterprise Data Warehouse.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL012" source="PLAT_ACI_2016" target="ORG_AWS"><data key="edge_relationship_id">R54_REL012</data><data key="edge_source_entity_id">PLAT_ACI_2016</data><data key="edge_relationship_type">uses_cloud_provider</data><data key="edge_target_entity_id">ORG_AWS</data><data key="edge_operational_context">SSA stated the ACI pilot would use Amazon Web Services for cloud capability.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical provider relationship for the 2016 pilot.</data></edge><edge id="R54_REL013" source="DW_EDW_2016" target="TECH_EMC_GREENPLUM_2016"><data key="edge_relationship_id">R54_REL013</data><data key="edge_source_entity_id">DW_EDW_2016</data><data key="edge_relationship_type">implemented_with</data><data key="edge_target_entity_id">TECH_EMC_GREENPLUM_2016</data><data key="edge_operational_context">SSA stated the new EDW database would be built using EMC Greenplum.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL014" source="TECH_INFORMATICA_ETL_2016" target="LAKE_HADOOP_2016"><data key="edge_relationship_id">R54_REL014</data><data key="edge_source_entity_id">TECH_INFORMATICA_ETL_2016</data><data key="edge_relationship_type">extracts_from</data><data key="edge_target_entity_id">LAKE_HADOOP_2016</data><data key="edge_operational_context">SSA stated Informatica ETL would pull data from its Hadoop data lake.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL015" source="TECH_INFORMATICA_ETL_2016" target="DW_EDW_2016"><data key="edge_relationship_id">R54_REL015</data><data key="edge_source_entity_id">TECH_INFORMATICA_ETL_2016</data><data key="edge_relationship_type">loads_into</data><data key="edge_target_entity_id">DW_EDW_2016</data><data key="edge_operational_context">SSA stated Informatica ETL would pull Hadoop data into the new EDW.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL016" source="LAKE_HADOOP_2016" target="TECH_APACHE_HADOOP"><data key="edge_relationship_id">R54_REL016</data><data key="edge_source_entity_id">LAKE_HADOOP_2016</data><data key="edge_relationship_type">implemented_with</data><data key="edge_target_entity_id">TECH_APACHE_HADOOP</data><data key="edge_operational_context">The documented data lake is explicitly described as a Hadoop data lake; SSA separately describes Apache Hadoop as the open-source framework used in its Big Data architecture.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL017" source="DW_BI_ORACLE_2016" target="TECH_ABINITIO"><data key="edge_relationship_id">R54_REL017</data><data key="edge_source_entity_id">DW_BI_ORACLE_2016</data><data key="edge_relationship_type">uses_ingestion_technology</data><data key="edge_target_entity_id">TECH_ABINITIO</data><data key="edge_operational_context">SSA stated Ab Initio brought data into the existing BI data warehouse.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL018" source="DW_BI_ORACLE_2016" target="TECH_PLSQL"><data key="edge_relationship_id">R54_REL018</data><data key="edge_source_entity_id">DW_BI_ORACLE_2016</data><data key="edge_relationship_type">uses_ingestion_technology</data><data key="edge_target_entity_id">TECH_PLSQL</data><data key="edge_operational_context">SSA stated custom-coded PL/SQL brought data into the existing BI data warehouse.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL019" source="DW_BI_ORACLE_2016" target="TECH_ORACLE_DATABASE"><data key="edge_relationship_id">R54_REL019</data><data key="edge_source_entity_id">DW_BI_ORACLE_2016</data><data key="edge_relationship_type">uses_database_technology</data><data key="edge_target_entity_id">TECH_ORACLE_DATABASE</data><data key="edge_operational_context">SSA described the existing BI warehouse as an Oracle database exceeding 12 TB.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical relationship; current Oracle procurement does not prove continuity of this warehouse.</data></edge><edge id="R54_REL020" source="ARCH_BI_ODS_2016" target="TECH_DB2"><data key="edge_relationship_id">R54_REL020</data><data key="edge_source_entity_id">ARCH_BI_ODS_2016</data><data key="edge_relationship_type">implemented_primarily_with</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">SSA stated BI operational data-store detail data was primarily stored in DB2.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Architecture-layer relationship, not a claim of one single ODS database.</data></edge><edge id="R54_REL021" source="ARCH_IWS_LAN" target="NET_SSANET"><data key="edge_relationship_id">R54_REL021</data><data key="edge_source_entity_id">ARCH_IWS_LAN</data><data key="edge_relationship_type">bridges_to</data><data key="edge_target_entity_id">NET_SSANET</data><data key="edge_operational_context">OTA documented a bridge connecting each field-office LAN to SSANet.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL022" source="ARCH_IWS_LAN" target="TECH_TOKEN_RING"><data key="edge_relationship_id">R54_REL022</data><data key="edge_source_entity_id">ARCH_IWS_LAN</data><data key="edge_relationship_type">uses_lan_technology</data><data key="edge_target_entity_id">TECH_TOKEN_RING</data><data key="edge_operational_context">SSA selected token-ring LAN technology for IWS/LAN.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL023" source="ARCH_IWS_LAN" target="TECH_IBM_MAINFRAME_1994"><data key="edge_relationship_id">R54_REL023</data><data key="edge_source_entity_id">ARCH_IWS_LAN</data><data key="edge_relationship_type">retains_backend_role_for</data><data key="edge_target_entity_id">TECH_IBM_MAINFRAME_1994</data><data key="edge_operational_context">IWS/LAN replaced dumb terminals with PCs while retaining a central mainframe/backend role.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No claim is made that the mainframe technology remained unchanged after 1994.</data></edge><edge id="R54_REL024" source="NET_SSANET" target="TECH_IBM_MAINFRAME_1994"><data key="edge_relationship_id">R54_REL024</data><data key="edge_source_entity_id">NET_SSANET</data><data key="edge_relationship_type">connects_to</data><data key="edge_target_entity_id">TECH_IBM_MAINFRAME_1994</data><data key="edge_operational_context">SSANet connected field-office and teleservice terminals to the Baltimore mainframes.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL025" source="NET_SSANET" target="TECH_IBM_SNA"><data key="edge_relationship_id">R54_REL025</data><data key="edge_source_entity_id">NET_SSANET</data><data key="edge_relationship_type">uses_network_protocol</data><data key="edge_target_entity_id">TECH_IBM_SNA</data><data key="edge_operational_context">OTA states the SSA network used IBM Systems Network Architecture protocols.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL026" source="TECH_IBM_MAINFRAME_1994" target="FAC_NCC"><data key="edge_relationship_id">R54_REL026</data><data key="edge_source_entity_id">TECH_IBM_MAINFRAME_1994</data><data key="edge_relationship_type">located_at</data><data key="edge_target_entity_id">FAC_NCC</data><data key="edge_operational_context">OTA places the mainframes at the National Computer Center at SSA headquarters in Baltimore.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical physical-location relationship.</data></edge><edge id="R54_REL027" source="TECH_IBM_MAINFRAME_1994" target="TECH_COBOL"><data key="edge_relationship_id">R54_REL027</data><data key="edge_source_entity_id">TECH_IBM_MAINFRAME_1994</data><data key="edge_relationship_type">uses_programming_language</data><data key="edge_target_entity_id">TECH_COBOL</data><data key="edge_operational_context">OTA states SSA software in the mainframe environment was written in COBOL or CICS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">CICS is represented separately as a transaction-processing technology despite OTA wording calling both languages.</data></edge><edge id="R54_REL028" source="TECH_IBM_MAINFRAME_1994" target="TECH_CICS"><data key="edge_relationship_id">R54_REL028</data><data key="edge_source_entity_id">TECH_IBM_MAINFRAME_1994</data><data key="edge_relationship_type">uses_transaction_processing_technology</data><data key="edge_target_entity_id">TECH_CICS</data><data key="edge_operational_context">OTA documents CICS as part of SSA software in the IBM mainframe environment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL029" source="ENV_SYSTEM_ZERO" target="ARCH_IWS_LAN"><data key="edge_relationship_id">R54_REL029</data><data key="edge_source_entity_id">ENV_SYSTEM_ZERO</data><data key="edge_relationship_type">testbed_for</data><data key="edge_target_entity_id">ARCH_IWS_LAN</data><data key="edge_operational_context">System Zero at NCC was used to experiment with IWS/LAN technology before pilot-field deployment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL030" source="ENV_SYSTEM_ZERO" target="FAC_NCC"><data key="edge_relationship_id">R54_REL030</data><data key="edge_source_entity_id">ENV_SYSTEM_ZERO</data><data key="edge_relationship_type">located_at</data><data key="edge_target_entity_id">FAC_NCC</data><data key="edge_operational_context">OTA states the System Zero test system was installed at the National Computer Center.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL031" source="SYS_MDS_1994" target="ARCH_IWS_LAN"><data key="edge_relationship_id">R54_REL031</data><data key="edge_source_entity_id">SYS_MDS_1994</data><data key="edge_relationship_type">developed_for</data><data key="edge_target_entity_id">ARCH_IWS_LAN</data><data key="edge_operational_context">OTA states MDS software was written specifically for IWS/LAN and no mainframe version was planned.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL032" source="SYS_MDS_1994" target="ORG_DDS"><data key="edge_relationship_id">R54_REL032</data><data key="edge_source_entity_id">SYS_MDS_1994</data><data key="edge_relationship_type">electronically_transmits_cases_to</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">MDS was designed to replace mailed disability files with electronic transmission to state disability offices and electronic support for evidence/adjudication.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL033" source="ARCH_PROGRAM_SILO_1994" target="DOM_PERSON_CUSTOMER_RECORD"><data key="edge_relationship_id">R54_REL033</data><data key="edge_source_entity_id">ARCH_PROGRAM_SILO_1994</data><data key="edge_relationship_type">prevents_whole_person_view_of</data><data key="edge_target_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="edge_operational_context">OTA documented separate databases for each SSA program as preventing a whole-person view of clients.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical architectural constraint; not a claim that every 1994 database is individually known.</data></edge><edge id="R54_REL034" source="INIT_SYSTEMS_MODERNIZATION_PLAN_1980S" target="TECH_IBM_MAINFRAME_1994"><data key="edge_relationship_id">R54_REL034</data><data key="edge_source_entity_id">INIT_SYSTEMS_MODERNIZATION_PLAN_1980S</data><data key="edge_relationship_type">modernized</data><data key="edge_target_entity_id">TECH_IBM_MAINFRAME_1994</data><data key="edge_operational_context">OTA says the mid-1980s Systems Modernization Plan modernized the mainframe computers and storage hardware.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R54_REL035" source="DATA_PACOMM_2016" target="APP_IACCOMMODATE"><data key="edge_relationship_id">R54_REL035</data><data key="edge_source_entity_id">DATA_PACOMM_2016</data><data key="edge_relationship_type">application_context</data><data key="edge_target_entity_id">APP_IACCOMMODATE</data><data key="edge_operational_context">The strategic plan explicitly names the BORG source as iAccommodate (PACOMM).</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship captures application/data context only; it does not infer a specific extract interface.</data></edge><edge id="R55_REL001" source="APP_IACCOMMODATE" target="DATA_PI_ACCOMMODATION_INFO"><data key="edge_relationship_id">R55_REL001</data><data key="edge_source_entity_id">APP_IACCOMMODATE</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">DATA_PI_ACCOMMODATION_INFO</data><data key="edge_operational_context">iAccommodate records accommodations SSA provides and routes non-standard requests within the Person Information environment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Data-domain relationship; does not assert physical table placement.</data></edge><edge id="R55_REL002" source="DATA_PI_ACCOMMODATION_INFO" target="APP_PERSON_INFO"><data key="edge_relationship_id">R55_REL002</data><data key="edge_source_entity_id">DATA_PI_ACCOMMODATION_INFO</data><data key="edge_relationship_type">presented_within</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current POMS locates iAccommodate on IMAIN under Person Information (Identity, Contact, Accommodation).</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Presentation/application boundary; no underlying database topology inferred.</data></edge><edge id="R55_REL003" source="APP_IACCOMMODATE" target="SYS_NUMIDENT"><data key="edge_relationship_id">R55_REL003</data><data key="edge_source_entity_id">APP_IACCOMMODATE</data><data key="edge_relationship_type">checks_recording_eligibility_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS says the intranet application must not be used to record accommodations for people without SSNs or people with a date of death on Numident.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This restriction applies to the iAccommodate recording workflow only; it does not establish a universal Person Information rule.</data></edge><edge id="R55_REL004" source="EX_SSI_IRS_1099" target="WORK_SSI_IRS_5B_DIARY"><data key="edge_relationship_id">R55_REL004</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">creates_work_control</data><data key="edge_target_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_operational_context">The SSI IRS match generates 5B diary work items for matched information requiring review.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Underlying matched IRS data require development; diary creation is not a verified-income posting.</data></edge><edge id="R55_REL005" source="WORK_SSI_IRS_5B_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R55_REL005</data><data key="edge_source_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS states that controlled 5B alerts/diaries are posted to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Work-control posting only.</data></edge><edge id="R55_REL006" source="DB_SSI_PE_ODS" target="WORK_SSI_IRS_5B_DIARY"><data key="edge_relationship_id">R55_REL006</data><data key="edge_source_entity_id">DB_SSI_PE_ODS</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_operational_context">Current POMS maps IRS 5B alert workload into the SSI post-entitlement operational-data-store workflow.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Physical implementation beyond the published PE ODS boundary is not inferred.</data></edge><edge id="R55_REL007" source="PROC_SSI_IRS_PENSION_MATCH" target="SYS_SSR"><data key="edge_relationship_id">R55_REL007</data><data key="edge_source_entity_id">PROC_SSI_IRS_PENSION_MATCH</data><data key="edge_relationship_type">compares_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The pension interface compares SSNs and reported pension amounts with eligible individuals/deemors and unearned-income information on SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R55_REL008" source="PROC_SSI_IRS_PENSION_MATCH" target="WORK_SSI_IRS_5H_DIARY"><data key="edge_relationship_id">R55_REL008</data><data key="edge_source_entity_id">PROC_SSI_IRS_PENSION_MATCH</data><data key="edge_relationship_type">creates_work_control</data><data key="edge_target_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_operational_context">Records meeting published pension-match criteria receive a 5H diary.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R55_REL009" source="WORK_SSI_IRS_5H_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R55_REL009</data><data key="edge_source_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS explicitly states that the system posts the 5H diary to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">The diary is a work-control indicator; underlying tax data remain subject to development.</data></edge><edge id="R55_REL010" source="DB_SSI_PE_ODS" target="WORK_SSI_IRS_5H_DIARY"><data key="edge_relationship_id">R55_REL010</data><data key="edge_source_entity_id">DB_SSI_PE_ODS</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_operational_context">POMS instructs technicians to identify records containing 5H diaries through PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R55_REL011" source="WORK_SSI_IRS_5H_DIARY" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R55_REL011</data><data key="edge_source_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_relationship_type">retrieved_via</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">POMS directs users to replacement 5B/5H alerts through MI Central RZ/LI SSN Query and the IRS query.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R55_REL012" source="DB_IRS_IMF" target="DATA_IRS_STATEMENT_MAIL_ADDR"><data key="edge_relationship_id">R55_REL012</data><data key="edge_source_entity_id">DB_IRS_IMF</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_IRS_STATEMENT_MAIL_ADDR</data><data key="edge_operational_context">For most automatic Statement recipients, SSA requests taxpayer mailing addresses from the IRS Individual Master File.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Controlled tax-data use; no master-record overwrite inferred.</data></edge><edge id="R55_REL013" source="DATA_IRS_STATEMENT_MAIL_ADDR" target="APP_PEBES"><data key="edge_relationship_id">R55_REL013</data><data key="edge_source_entity_id">DATA_IRS_STATEMENT_MAIL_ADDR</data><data key="edge_relationship_type">consumed_by</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">PEBES procures and uses IRS addresses to produce and mail automatic Social Security Statements.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Statement production use only as documented.</data></edge><edge id="R55_REL014" source="DB_SUMS_ENUM_ODS" target="DATA_ENUM_PROCESSING_TIME"><data key="edge_relationship_id">R55_REL014</data><data key="edge_source_entity_id">DB_SUMS_ENUM_ODS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_ENUM_PROCESSING_TIME</data><data key="edge_operational_context">SSA says the public enumeration processing-time dataset is extracted from the SUMS Enumeration ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R55_REL015" source="DB_T2_ODS" target="DATA_RSI_APPLICATION_VOLUMES"><data key="edge_relationship_id">R55_REL015</data><data key="edge_source_entity_id">DB_T2_ODS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_RSI_APPLICATION_VOLUMES</data><data key="edge_operational_context">SSA downloads MCS data nightly to the Title II ODS and uses batch aggregation for the public national application volumes.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R55_REL016" source="DATA_DOWR" target="DATA_RSI_APPLICATION_VOLUMES"><data key="edge_relationship_id">R55_REL016</data><data key="edge_source_entity_id">DATA_DOWR</data><data key="edge_relationship_type">provides_reporting_dates_for</data><data key="edge_target_entity_id">DATA_RSI_APPLICATION_VOLUMES</data><data key="edge_operational_context">SSA uses DOWR receipt/reporting dates in the public RSI application dataset.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R55_REL017" source="DB_ESERVICE_ODS" target="DATA_IMRC_APPLICATION_VOLUMES"><data key="edge_relationship_id">R55_REL017</data><data key="edge_source_entity_id">DB_ESERVICE_ODS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_IMRC_APPLICATION_VOLUMES</data><data key="edge_operational_context">Internet Medicare Replacement Card front-end transaction counts are stored nightly in Electronic Services ODS and support the public volume dataset.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">The following-day Data Warehouse target remains unnamed in public documentation.</data></edge><edge id="R55_REL018" source="APP_IMRC" target="DATA_IMRC_APPLICATION_VOLUMES"><data key="edge_relationship_id">R55_REL018</data><data key="edge_source_entity_id">APP_IMRC</data><data key="edge_relationship_type">generates_activity_for</data><data key="edge_target_entity_id">DATA_IMRC_APPLICATION_VOLUMES</data><data key="edge_operational_context">The public monthly dataset counts front-end activity from the Online Medicare Replacement Card application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R55_REL019" source="DB_CSR_ODS" target="DATA_FO_VISITORS_AVG"><data key="edge_relationship_id">R55_REL019</data><data key="edge_source_entity_id">DB_CSR_ODS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_FO_VISITORS_AVG</data><data key="edge_operational_context">SSA derives field-office visitor counts through the CSR ODS process used since FY2009.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Published product is aggregate even though name/SSN enter the intake process.</data></edge><edge id="R55_REL020" source="DB_DIODS" target="DATA_DDS_STATE_MONTHLY_WORKLOAD"><data key="edge_relationship_id">R55_REL020</data><data key="edge_source_entity_id">DB_DIODS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_DDS_STATE_MONTHLY_WORKLOAD</data><data key="edge_operational_context">Current SSA documentation states the public disability workload dataset is based on DIODS case and summary data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R56_REL001" source="SVC_EREWS" target="APP_ERE"><data key="edge_relationship_id">R56_REL001</data><data key="edge_source_entity_id">SVC_EREWS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">EREWS is the machine-to-machine web-service channel within the Electronic Records Express family for high-volume electronic evidence submission.</data><data key="edge_observed_as_of">2007-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">Historical technical relationship from SSA developer documentation; current EREWS deployment status remains unconfirmed.</data></edge><edge id="R56_REL002" source="SVC_EREWS" target="TECH_SOAP"><data key="edge_relationship_id">R56_REL002</data><data key="edge_source_entity_id">SVC_EREWS</data><data key="edge_relationship_type">uses_protocol</data><data key="edge_target_entity_id">TECH_SOAP</data><data key="edge_operational_context">EREWS submitBulk and ping operations are exposed through SOAP messages.</data><data key="edge_observed_as_of">2007-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">Historical EREWS implementation.</data></edge><edge id="R56_REL003" source="SVC_EREWS" target="TECH_WSDL"><data key="edge_relationship_id">R56_REL003</data><data key="edge_source_entity_id">SVC_EREWS</data><data key="edge_relationship_type">described_by</data><data key="edge_target_entity_id">TECH_WSDL</data><data key="edge_operational_context">SSA published a WSDL defining the EREWS service, operations and SOAP binding.</data><data key="edge_observed_as_of">2007-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">Historical EREWS implementation.</data></edge><edge id="R56_REL004" source="SVC_EREWS" target="TECH_HTTPS_SSL"><data key="edge_relationship_id">R56_REL004</data><data key="edge_source_entity_id">SVC_EREWS</data><data key="edge_relationship_type">secured_by</data><data key="edge_target_entity_id">TECH_HTTPS_SSL</data><data key="edge_operational_context">SSA required EREWS clients to use HTTPS/SSL for confidentiality of medical information in transit.</data><data key="edge_observed_as_of">2007-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">Historical implementation terminology.</data></edge><edge id="R56_REL005" source="SVC_EREWS" target="TECH_WS_SECURITY"><data key="edge_relationship_id">R56_REL005</data><data key="edge_source_entity_id">SVC_EREWS</data><data key="edge_relationship_type">secured_by</data><data key="edge_target_entity_id">TECH_WS_SECURITY</data><data key="edge_operational_context">SSA documented WS-Security UsernameToken authentication/security headers for EREWS.</data><data key="edge_observed_as_of">2007-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">Historical EREWS implementation.</data></edge><edge id="R56_REL006" source="SVC_EREWS" target="TECH_APACHE_AXIS_14"><data key="edge_relationship_id">R56_REL006</data><data key="edge_source_entity_id">SVC_EREWS</data><data key="edge_relationship_type">reference_client_uses</data><data key="edge_target_entity_id">TECH_APACHE_AXIS_14</data><data key="edge_operational_context">SSA’s Java client reference stack used Apache Axis 1.4 and related libraries.</data><data key="edge_observed_as_of">2007-07-02</data><data key="edge_confidence">5</data><data key="edge_notes">Reference-client relationship only.</data></edge><edge id="R56_REL007" source="APP_SSNVS" target="FMT_SSNVS_FIXED130"><data key="edge_relationship_id">R56_REL007</data><data key="edge_source_entity_id">APP_SSNVS</data><data key="edge_relationship_type">accepts_batch_format</data><data key="edge_target_entity_id">FMT_SSNVS_FIXED130</data><data key="edge_operational_context">Current SSNVS batch upload accepts fixed-width 130-character records; SSA allows files up to 250,000 name/SSN requests.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current employer technical guidance.</data></edge><edge id="R56_REL008" source="SVC_EWRWS" target="FMT_EFW2"><data key="edge_relationship_id">R56_REL008</data><data key="edge_source_entity_id">SVC_EWRWS</data><data key="edge_relationship_type">accepts</data><data key="edge_target_entity_id">FMT_EFW2</data><data key="edge_operational_context">Current EWRWS page states the web service submits wage reports in the EFW2 format.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current service remains available to existing consolidators; SSA is not accepting new users/consolidators.</data></edge><edge id="R56_REL009" source="EX_SOLQ" target="DATA_SOLQ_T2_RESPONSE"><data key="edge_relationship_id">R56_REL009</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">returns_structure</data><data key="edge_target_entity_id">DATA_SOLQ_T2_RESPONSE</data><data key="edge_operational_context">SOLQ/SOLQ-I can return a Type 2 Title II response appended to the identity/verification response.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Record-layout relationship.</data></edge><edge id="R56_REL010" source="EX_SOLQ" target="DATA_SOLQ_T16_RESPONSE"><data key="edge_relationship_id">R56_REL010</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">returns_structure</data><data key="edge_target_entity_id">DATA_SOLQ_T16_RESPONSE</data><data key="edge_operational_context">SOLQ/SOLQ-I can return a Type 3 Title XVI response appended to the identity/verification response.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Record-layout relationship.</data></edge><edge id="R56_REL011" source="DATA_SOLQ_T2_RESPONSE" target="SYS_MBR"><data key="edge_relationship_id">R56_REL011</data><data key="edge_source_entity_id">DATA_SOLQ_T2_RESPONSE</data><data key="edge_relationship_type">contains_mbr_derived_fields</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The Type 2 record layout explicitly identifies fields such as LAF and dual-entitlement information as reflecting the Master Beneficiary Record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Does not claim every field in the response is sourced exclusively from MBR.</data></edge><edge id="R56_REL012" source="DATA_SOLQ_T16_RESPONSE" target="SYS_SSR"><data key="edge_relationship_id">R56_REL012</data><data key="edge_source_entity_id">DATA_SOLQ_T16_RESPONSE</data><data key="edge_relationship_type">contains_ssr_master_fields</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The Type 3 record layout explicitly says payee ZIP+4 can be present on the SSR master file and residence ZIP+4 can be present on the SSI master file.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Supports SSR/SSI-master provenance for the documented address fields without implying any update from SOLQ back into SSR.</data></edge><edge id="R56_REL013" source="EX_IEDR" target="SYS_NUMIDENT"><data key="edge_relationship_id">R56_REL013</data><data key="edge_source_entity_id">EX_IEDR</data><data key="edge_relationship_type">posts_death_data_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS treats Numident death data based on an EDR report as preferred evidence of death, establishing that EDR-derived death information is represented on Numident.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">The source does not expose the internal transaction/staging mechanism.</data></edge><edge id="R56_REL014" source="EX_IEDR" target="DOM_SSNV"><data key="edge_relationship_id">R56_REL014</data><data key="edge_source_entity_id">EX_IEDR</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">SSA Data Exchange describes I-EDR as allowing state vital-statistics agencies to verify decedent Social Security numbers before/while submitting death reports.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Verification source is SSA records; this relationship does not infer a specific internal verification application.</data></edge><edge id="R56_REL015" source="SYS_SSR" target="DATA_SSI_MONTHLY_STATS"><data key="edge_relationship_id">R56_REL015</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_SSI_MONTHLY_STATS</data><data key="edge_operational_context">SSA states the July 2026 SSI Monthly Statistics table uses Supplemental Security Record 100 percent data.</data><data key="edge_observed_as_of">2026-07</data><data key="edge_confidence">5</data><data key="edge_notes">Establishes publication lineage from SSR. No ETL or intermediate data-store mechanism is asserted.</data></edge><edge id="R56_REL016" source="PROC_NUMIDENT_CROSS_RECORD_UPDATE" target="SYS_NUMIDENT"><data key="edge_relationship_id">R56_REL016</data><data key="edge_source_entity_id">PROC_NUMIDENT_CROSS_RECORD_UPDATE</data><data key="edge_relationship_type">follows_update_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Process is triggered after specified Numident attribute updates under current SSNAP/Numident maintenance policy.</data><data key="edge_observed_as_of">2026-06-05</data><data key="edge_confidence">5</data><data key="edge_notes">Does not imply every Numident field change requires the same downstream actions.</data></edge><edge id="R56_REL017" source="PROC_NUMIDENT_CROSS_RECORD_UPDATE" target="SYS_MBR"><data key="edge_relationship_id">R56_REL017</data><data key="edge_source_entity_id">PROC_NUMIDENT_CROSS_RECORD_UPDATE</data><data key="edge_relationship_type">requires_separate_update_or_review_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS requires MBR update after a Numident sex-code change and review/action when a parent's name is changed for relevant individuals.</data><data key="edge_observed_as_of">2026-06-05</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit staff-directed cross-record action; not automatic propagation.</data></edge><edge id="R56_REL018" source="PROC_NUMIDENT_CROSS_RECORD_UPDATE" target="SYS_SSR"><data key="edge_relationship_id">R56_REL018</data><data key="edge_source_entity_id">PROC_NUMIDENT_CROSS_RECORD_UPDATE</data><data key="edge_relationship_type">requires_separate_update_or_review_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS requires SSR update after a Numident sex-code change and review/action when a parent's name is changed for relevant individuals.</data><data key="edge_observed_as_of">2026-06-05</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit staff-directed cross-record action; not automatic propagation.</data></edge><edge id="R56_REL019" source="PROC_NUMIDENT_CROSS_RECORD_UPDATE" target="APP_RPS"><data key="edge_relationship_id">R56_REL019</data><data key="edge_source_entity_id">PROC_NUMIDENT_CROSS_RECORD_UPDATE</data><data key="edge_relationship_type">requires_separate_update_or_review_of</data><data key="edge_target_entity_id">APP_RPS</data><data key="edge_operational_context">Current POMS requires RPS update after a Numident sex-code change and review/action when a parent's name is changed for a representative payee.</data><data key="edge_observed_as_of">2026-06-05</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit staff-directed cross-record action; RPS is the policy term, distinct from later eRPS unless separately established.</data></edge><edge id="R56_REL020" source="EX_EAB" target="SYS_NUMIDENT"><data key="edge_relationship_id">R56_REL020</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">transmits_parent_identity_attributes_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">State birth-registration data transmitted through Enumeration at Birth include parents' names, which can appear in the EAB Numident mother-name-at-birth or father-name-at-birth fields.</data><data key="edge_observed_as_of">2026-06-11</data><data key="edge_confidence">5</data><data key="edge_notes">Establishes provenance of specific person/parent attributes from state vital-statistics data through EAB. It does not imply state data update other SSA master records.</data></edge><edge id="R56_REL021" source="APP_UPLOAD_DOCUMENTS" target="APP_MCS"><data key="edge_relationship_id">R56_REL021</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">requires_manual_claims_entry_into</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Current POMS says technicians process electronically submitted benefit applications as paper applications and load them into MCS when applicable.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit manual/technician bridge. This is not modeled as an automated Upload Documents-to-MCS interface.</data></edge><edge id="R56_REL022" source="APP_UPLOAD_DOCUMENTS" target="APP_CCE"><data key="edge_relationship_id">R56_REL022</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">requires_manual_claims_entry_into</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Current POMS says technicians process electronically submitted benefit applications as paper applications and load them into CCE when applicable.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit manual/technician bridge. This is not modeled as an automated Upload Documents-to-CCE interface.</data></edge><edge id="R56_REL023" source="SVC_EWRWS" target="TECH_SOAP"><data key="edge_relationship_id">R56_REL023</data><data key="edge_source_entity_id">SVC_EWRWS</data><data key="edge_relationship_type">uses_protocol</data><data key="edge_target_entity_id">TECH_SOAP</data><data key="edge_operational_context">Current EWRWS Terms of Service states that the requesting party's software sends a SOAP message.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current service evidence, separate from the historical EREWS SOAP evidence.</data></edge><edge id="R56_REL024" source="SVC_EWRWS" target="TECH_HTTPS_SSL"><data key="edge_relationship_id">R56_REL024</data><data key="edge_source_entity_id">SVC_EWRWS</data><data key="edge_relationship_type">secured_by</data><data key="edge_target_entity_id">TECH_HTTPS_SSL</data><data key="edge_operational_context">Current EWRWS Terms of Service says communication with requesting-party software is secured using HTTPS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Entity name retains HTTPS/SSL because it was introduced for historical EREWS; current EWRWS evidence explicitly supports HTTPS, not a specific TLS/SSL version.</data></edge><edge id="R56_REL025" source="SVC_EWRWS" target="TECH_X509"><data key="edge_relationship_id">R56_REL025</data><data key="edge_source_entity_id">SVC_EWRWS</data><data key="edge_relationship_type">requires_digital_certificate</data><data key="edge_target_entity_id">TECH_X509</data><data key="edge_operational_context">Current EWRWS Terms of Service requires the SOAP message to include an X.509 digital certificate issued by a trusted CA.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R56_REL026" source="SVC_EWRWS" target="APP_IRES"><data key="edge_relationship_id">R56_REL026</data><data key="edge_source_entity_id">SVC_EWRWS</data><data key="edge_relationship_type">authenticates_via</data><data key="edge_target_entity_id">APP_IRES</data><data key="edge_operational_context">Current EWRWS Terms of Service requires the authorized representative to register with IRES within BSO and hold EWRWS access.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Residual current EWRWS dependency. Other BSO services have migrated to Login.gov/ID.me; no general BSO-to-IRES current dependency is asserted.</data></edge><edge id="R56_REL027" source="APP_IRES" target="PLAT_BSO"><data key="edge_relationship_id">R56_REL027</data><data key="edge_source_entity_id">APP_IRES</data><data key="edge_relationship_type">associated_with</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">Current EWRWS Terms of Service describes IRES as a registration utility of Business Services Online; historical SSA documentation also identifies IRES as the BSO registration application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship is limited to registration/access-control context and does not assert IRES remains the authentication path for all BSO services.</data></edge><edge id="R56_REL028" source="DB_IRES_MI" target="APP_IRES"><data key="edge_relationship_id">R56_REL028</data><data key="edge_source_entity_id">DB_IRES_MI</data><data key="edge_relationship_type">management_information_for</data><data key="edge_target_entity_id">APP_IRES</data><data key="edge_operational_context">The current SSA inventory identifies Integrated Registration Service management information supporting registration of organizations to SSA internet applications.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">4</data><data key="edge_notes">Logical association from naming and inventory purpose; physical database linkage or implementation is not publicly specified.</data></edge><edge id="R56_REL029" source="APP_ERPS" target="DATA_ERPS_INDIVIDUAL_ID"><data key="edge_relationship_id">R56_REL029</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">identifies_individual_payee_by</data><data key="edge_target_entity_id">DATA_ERPS_INDIVIDUAL_ID</data><data key="edge_operational_context">Current eRPS policy uses a verified SSN as the unique numeric identifier for an individual applicant/payee.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data><data key="edge_notes">Identifier semantics are specific to individual payees; organizations use a separate Organization ID.</data></edge><edge id="R56_REL030" source="DATA_ERPS_INDIVIDUAL_ID" target="SYS_NUMIDENT"><data key="edge_relationship_id">R56_REL030</data><data key="edge_source_entity_id">DATA_ERPS_INDIVIDUAL_ID</data><data key="edge_relationship_type">verified_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current eRPS applicant-identification workflow verifies individual SSN identity against SSA Numident/NUMI information before using the SSN as the payee identifier.</data><data key="edge_observed_as_of">2026-09-16</data><data key="edge_confidence">5</data><data key="edge_notes">Combines current identifier policy with current applicant-interview policy; no separate physical API/protocol is inferred.</data></edge><edge id="R56_REL031" source="APP_ERPS" target="DATA_ERPS_CONTACT_ADDRESS"><data key="edge_relationship_id">R56_REL031</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">stores_contact_address</data><data key="edge_target_entity_id">DATA_ERPS_CONTACT_ADDRESS</data><data key="edge_operational_context">eRPS records applicant/payee address and phone information; policy permits a substitute organization address/phone or P.O. Box in specified privacy circumstances.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">The stored contact address therefore is not necessarily a verified personal residence address.</data></edge><edge id="R57_REL001" source="DATA_BSO_IRS_EMPLOYER_ADDRESS" target="ORG_IRS"><data key="edge_relationship_id">R57_REL001</data><data key="edge_source_entity_id">DATA_BSO_IRS_EMPLOYER_ADDRESS</data><data key="edge_relationship_type">sourced_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SSA BSO registration guidance states the activation code is mailed to the employer address on file with IRS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Controlled-purpose employer authorization address; no SSA master-address overwrite is inferred.</data></edge><edge id="R57_REL002" source="PLAT_BSO" target="DATA_BSO_IRS_EMPLOYER_ADDRESS"><data key="edge_relationship_id">R57_REL002</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">uses_activation_address</data><data key="edge_target_entity_id">DATA_BSO_IRS_EMPLOYER_ADDRESS</data><data key="edge_operational_context">BSO employer-suite activation uses the IRS-registered employer address as the mailing destination.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This is address use for authorization, not a person/residence update path.</data></edge><edge id="R57_REL003" source="PLAT_BSO" target="DATA_BSO_ACTIVATION_CODE"><data key="edge_relationship_id">R57_REL003</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">issues</data><data key="edge_target_entity_id">DATA_BSO_ACTIVATION_CODE</data><data key="edge_operational_context">After employer services are requested, SSA issues an activation code that the user later enters in BSO.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Code is separate from Login.gov/ID.me personal identity proofing.</data></edge><edge id="R57_REL004" source="DATA_BSO_ACTIVATION_CODE" target="ORG_USPS"><data key="edge_relationship_id">R57_REL004</data><data key="edge_source_entity_id">DATA_BSO_ACTIVATION_CODE</data><data key="edge_relationship_type">delivered_via</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">SSA SSNVS/BSO guidance says the activation code is sent through USPS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Physical-mail delivery control.</data></edge><edge id="R57_REL005" source="DATA_BSO_ACTIVATION_CODE" target="DATA_BSO_IRS_EMPLOYER_ADDRESS"><data key="edge_relationship_id">R57_REL005</data><data key="edge_source_entity_id">DATA_BSO_ACTIVATION_CODE</data><data key="edge_relationship_type">mailed_to</data><data key="edge_target_entity_id">DATA_BSO_IRS_EMPLOYER_ADDRESS</data><data key="edge_operational_context">Activation code is mailed to the employer address registered with IRS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No persistence beyond the documented authorization workflow is inferred.</data></edge><edge id="R57_REL006" source="APP_SSNVS" target="DATA_BSO_ACTIVATION_CODE"><data key="edge_relationship_id">R57_REL006</data><data key="edge_source_entity_id">APP_SSNVS</data><data key="edge_relationship_type">requires_service_activation_via</data><data key="edge_target_entity_id">DATA_BSO_ACTIVATION_CODE</data><data key="edge_operational_context">New users or users adding SSNVS receive a mailed activation code before access is enabled.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Authentication still uses the current BSO credential path; this relationship captures service authorization.</data></edge><edge id="R57_REL007" source="PROC_ANOMALOUS_WAGE_REVIEW" target="PLAT_BSO"><data key="edge_relationship_id">R57_REL007</data><data key="edge_source_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="edge_relationship_type">governs_submissions_through</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">Current POMS applies anomalous-wage controls to SSA electronic wage-reporting services and BSO credentials.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Covers hold/investigation/suspension actions; does not imply all BSO services are wage reporting.</data></edge><edge id="R57_REL008" source="PROC_ANOMALOUS_WAGE_REVIEW" target="SVC_EWRWS"><data key="edge_relationship_id">R57_REL008</data><data key="edge_source_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="edge_relationship_type">governs_submissions_through</data><data key="edge_target_entity_id">SVC_EWRWS</data><data key="edge_operational_context">Current POMS explicitly includes EWRWS among electronic wage-reporting services subject to misuse/anomaly controls.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Applies to wage-report submissions, not unrelated web-service traffic.</data></edge><edge id="R57_REL009" source="DOC_WAGE_INVESTIGATIVE_NOTICE" target="PROC_ANOMALOUS_WAGE_REVIEW"><data key="edge_relationship_id">R57_REL009</data><data key="edge_source_entity_id">DOC_WAGE_INVESTIGATIVE_NOTICE</data><data key="edge_relationship_type">produced_by</data><data key="edge_target_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="edge_operational_context">SSA sends an Investigative Notice when anomalous wage reports warrant submitter action.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Notice provides required actions and deadline.</data></edge><edge id="R57_REL010" source="DOC_WAGE_INVESTIGATIVE_NOTICE" target="DATA_WFID"><data key="edge_relationship_id">R57_REL010</data><data key="edge_source_entity_id">DOC_WAGE_INVESTIGATIVE_NOTICE</data><data key="edge_relationship_type">references</data><data key="edge_target_entity_id">DATA_WFID</data><data key="edge_operational_context">Investigative Notice lists suspect wage reports by WFID along with EIN and tax year.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">WFID is modeled as submission identifier only.</data></edge><edge id="R57_REL011" source="PROC_ANOMALOUS_WAGE_REVIEW" target="APP_ARIS"><data key="edge_relationship_id">R57_REL011</data><data key="edge_source_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="edge_relationship_type">may_refer_suspected_fraud_to</data><data key="edge_target_entity_id">APP_ARIS</data><data key="edge_operational_context">Current POMS directs suspected fraud referrals to OIG through ARIS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Conditional referral, not an automatic path for every anomaly.</data></edge><edge id="R57_REL012" source="DATA_SUSPENDED_3P_SUBMITTERS" target="PROC_ANOMALOUS_WAGE_REVIEW"><data key="edge_relationship_id">R57_REL012</data><data key="edge_source_entity_id">DATA_SUSPENDED_3P_SUBMITTERS</data><data key="edge_relationship_type">published_from</data><data key="edge_target_entity_id">PROC_ANOMALOUS_WAGE_REVIEW</data><data key="edge_operational_context">SSA may publish a third-party submitter name on the Suspended Third-Party Submitters page after applicable suspension/deactivation action.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current page is empty; publication is conditional.</data></edge><edge id="R57_REL013" source="DATA_SUSPENDED_3P_SUBMITTERS" target="PLAT_BSO"><data key="edge_relationship_id">R57_REL013</data><data key="edge_source_entity_id">DATA_SUSPENDED_3P_SUBMITTERS</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">The public suspended-submitter page is part of the employer/BSO wage-reporting service surface.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Public control surface; underlying enforcement repository is not identified.</data></edge><edge id="R57_REL014" source="EX_PIE" target="WORK_PIE_EE_DIARY"><data key="edge_relationship_id">R57_REL014</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">creates_when_auto_post_fails</data><data key="edge_target_entity_id">WORK_PIE_EE_DIARY</data><data key="edge_operational_context">PIE creates an EE diary when wage/employment information cannot automatically post to the SSI record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit POMS work-control behavior.</data></edge><edge id="R57_REL015" source="APP_CCE" target="UI_PDP_PENDING_WAGE"><data key="edge_relationship_id">R57_REL015</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">UI_PDP_PENDING_WAGE</data><data key="edge_operational_context">SSI Claims/CCE may create a PDP Pending Wage page when PIE information cannot match to an existing Wages page.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS identifies CCE as the SSI Claims system in this workflow.</data></edge><edge id="R57_REL016" source="APP_CCE" target="UI_PDP_PENDING_WAGE_REPORT"><data key="edge_relationship_id">R57_REL016</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">UI_PDP_PENDING_WAGE_REPORT</data><data key="edge_operational_context">SSI Claims/CCE may create a PDP Pending Wage Report page for matched information requiring manual processing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Common examples include force-due or manual-deeming conditions.</data></edge><edge id="R57_REL017" source="UI_PDP_PENDING_WAGE" target="WORK_PIE_EE_DIARY"><data key="edge_relationship_id">R57_REL017</data><data key="edge_source_entity_id">UI_PDP_PENDING_WAGE</data><data key="edge_relationship_type">adds_work_control</data><data key="edge_target_entity_id">WORK_PIE_EE_DIARY</data><data key="edge_operational_context">Presence of the pending wage page adds the EE diary to the SSI record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">All pending pages must be resolved before the EE diary and associated LI/RZ can clear.</data></edge><edge id="R57_REL018" source="UI_PDP_PENDING_WAGE_REPORT" target="WORK_PIE_EE_DIARY"><data key="edge_relationship_id">R57_REL018</data><data key="edge_source_entity_id">UI_PDP_PENDING_WAGE_REPORT</data><data key="edge_relationship_type">adds_work_control</data><data key="edge_target_entity_id">WORK_PIE_EE_DIARY</data><data key="edge_operational_context">Presence of the pending wage report page adds the EE diary to the SSI record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Manual review is required before wages apply to SSR.</data></edge><edge id="R57_REL019" source="UI_PDP_PENDING_WAGE_REPORT" target="SYS_SSR"><data key="edge_relationship_id">R57_REL019</data><data key="edge_source_entity_id">UI_PDP_PENDING_WAGE_REPORT</data><data key="edge_relationship_type">delays_posting_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS states wages on the PDP Pending Wage Report page have not been applied to SSR and require technician action.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This is explicit negative/queue-state evidence, not an automatic posting path.</data></edge><edge id="R57_REL020" source="EX_PIE" target="UI_SSI_WAGES_PAGE"><data key="edge_relationship_id">R57_REL020</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">updates_on_successful_match</data><data key="edge_target_entity_id">UI_SSI_WAGES_PAGE</data><data key="edge_operational_context">When PDP EIN matches an SSI Claims Wages page, wage information received through PIE automatically updates that page.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Successful-match path only.</data></edge><edge id="R57_REL021" source="UI_SSI_WAGES_PAGE" target="SYS_SSR"><data key="edge_relationship_id">R57_REL021</data><data key="edge_source_entity_id">UI_SSI_WAGES_PAGE</data><data key="edge_relationship_type">submits_qualifying_wages_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">After a successful PIE match, qualifying wages are submitted to SSR before the Goldberg-Kelly cutoff.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS documents the automated SSI posting path.</data></edge><edge id="R57_REL022" source="APP_CCE" target="UI_SSI_WAGES_PAGE"><data key="edge_relationship_id">R57_REL022</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">UI_SSI_WAGES_PAGE</data><data key="edge_operational_context">Current PIE POMS describes Wages pages as part of the SSI Claims system/CCE processing environment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Logical UI containment only; underlying storage is not inferred.</data></edge><edge id="R57_REL023" source="APP_MCS" target="UI_MCS_CADR"><data key="edge_relationship_id">R57_REL023</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">UI_MCS_CADR</data><data key="edge_operational_context">RSDI claims use the CADR screen to enter claimant mailing address.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS reference.</data></edge><edge id="R57_REL024" source="UI_MCS_CADR" target="UI_MCS_ADDR"><data key="edge_relationship_id">R57_REL024</data><data key="edge_source_entity_id">UI_MCS_CADR</data><data key="edge_relationship_type">propagates_mailing_address_to</data><data key="edge_target_entity_id">UI_MCS_ADDR</data><data key="edge_operational_context">Current POMS explicitly states the mailing address entered on CADR propagates to ADDR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Within-MCS screen propagation; no MBR posting behavior is inferred from this statement alone.</data></edge><edge id="R57_REL025" source="EX_EBE" target="DATA_EBE_USCIS_MAILING_ADDRESS"><data key="edge_relationship_id">R57_REL025</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">carries</data><data key="edge_target_entity_id">DATA_EBE_USCIS_MAILING_ADDRESS</data><data key="edge_operational_context">USCIS electronically transmits EBE enumeration data and SSA mails the card to the address supplied on the USCIS application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Address is channel-specific enumeration/card-delivery data.</data></edge><edge id="R57_REL026" source="DATA_EBE_USCIS_MAILING_ADDRESS" target="ORG_USCIS"><data key="edge_relationship_id">R57_REL026</data><data key="edge_source_entity_id">DATA_EBE_USCIS_MAILING_ADDRESS</data><data key="edge_relationship_type">originates_from</data><data key="edge_target_entity_id">ORG_USCIS</data><data key="edge_operational_context">Applicant supplies the mailing address on the USCIS application that feeds EBE.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Do not infer that USCIS is authoritative for the person’s broader SSA mailing/residence address.</data></edge><edge id="R57_REL027" source="APP_SSNEC" target="DATA_SSN_CARD_PRINT_FILE"><data key="edge_relationship_id">R57_REL027</data><data key="edge_source_entity_id">APP_SSNEC</data><data key="edge_relationship_type">establishes</data><data key="edge_target_entity_id">DATA_SSN_CARD_PRINT_FILE</data><data key="edge_operational_context">SSNEC PIA states the system establishes the file from which Social Security cards are printed.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Historical component architecture; current physical implementation not independently verified.</data></edge><edge id="R57_REL028" source="APP_SSNEC" target="DATA_SSNEC_APP_MAIL_ADDR"><data key="edge_relationship_id">R57_REL028</data><data key="edge_source_entity_id">APP_SSNEC</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_SSNEC_APP_MAIL_ADDR</data><data key="edge_operational_context">SSNEC PIA states the system contains mailing addresses of individuals who filed SSN applications.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Application-address evidence is time-scoped; do not equate this automatically with a current Numident address field.</data></edge><edge id="R57_REL029" source="APP_RSDI_ACCT" target="SYS_MBR"><data key="edge_relationship_id">R57_REL029</data><data key="edge_source_entity_id">APP_RSDI_ACCT</data><data key="edge_relationship_type">uses_title_ii_payment_data_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">RSDI-ACCT uses Title II benefit payment data covered by MBR and accumulates totals used to ensure MBR integrity.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Historical detailed architecture within a system still listed in the current PIA catalog.</data></edge><edge id="R57_REL030" source="APP_RSDI_ACCT" target="DB_MDB"><data key="edge_relationship_id">R57_REL030</data><data key="edge_source_entity_id">APP_RSDI_ACCT</data><data key="edge_relationship_type">uses_medicare_premium_data_from</data><data key="edge_target_entity_id">DB_MDB</data><data key="edge_operational_context">RSDI-ACCT processes Medicare premium data covered by the Medicare Database SORN.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Historical detailed architecture; exact current interface mechanism not inferred.</data></edge><edge id="R57_REL031" source="APP_RSDI_ACCT" target="DATA_RSDI_ACCOUNTING_TOTALS"><data key="edge_relationship_id">R57_REL031</data><data key="edge_source_entity_id">APP_RSDI_ACCT</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_RSDI_ACCOUNTING_TOTALS</data><data key="edge_operational_context">RSDI-ACCT accumulates accounting-control, payment-certification, trust-fund and statistical totals.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Data-product/function relationship.</data></edge><edge id="R57_REL032" source="DATA_RSDI_ACCOUNTING_TOTALS" target="SYS_MBR"><data key="edge_relationship_id">R57_REL032</data><data key="edge_source_entity_id">DATA_RSDI_ACCOUNTING_TOTALS</data><data key="edge_relationship_type">used_to_validate</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA states accounting totals are used to ensure MBR integrity and benefit-payment accuracy.</data><data key="edge_observed_as_of">2007-09-27</data><data key="edge_confidence">5</data><data key="edge_notes">Validation/accounting relationship; not a claim that totals are written into MBR.</data></edge><edge id="R57_REL033" source="APP_IDMS_DIS" target="DB_DCF"><data key="edge_relationship_id">R57_REL033</data><data key="edge_source_entity_id">APP_IDMS_DIS</data><data key="edge_relationship_type">uses_master_file</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">2017 PIA states IDMS uses DCF as its master file/master repository.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Current catalog still lists IDMS; exact 2026 component topology is not inferred.</data></edge><edge id="R57_REL034" source="APP_DCFS" target="APP_IDMS_DIS"><data key="edge_relationship_id">R57_REL034</data><data key="edge_source_entity_id">APP_DCFS</data><data key="edge_relationship_type">subsystem_of</data><data key="edge_target_entity_id">APP_IDMS_DIS</data><data key="edge_operational_context">2017 PIA lists DCFS as an IDMS subsystem.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Historical/current-catalog parent relationship.</data></edge><edge id="R57_REL035" source="APP_DCFS" target="DB_DCF"><data key="edge_relationship_id">R57_REL035</data><data key="edge_source_entity_id">APP_DCFS</data><data key="edge_relationship_type">uses_master_repository</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">DCFS functions are represented by the DCF master repository for disability decision and post-entitlement data.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Distinguishes system wrapper from file/repository.</data></edge><edge id="R57_REL036" source="DB_DCF" target="SYS_MEF"><data key="edge_relationship_id">R57_REL036</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">reads_and_updates_according_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">2017 IDMS PIA explicitly states DCF reads and updates according to MEF.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Interface/transport and direction of individual field writes are not public; wording mirrors source.</data></edge><edge id="R57_REL037" source="DB_DCF" target="SYS_SSR"><data key="edge_relationship_id">R57_REL037</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">reads_and_updates_according_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2017 IDMS PIA explicitly states DCF reads and updates according to SSR.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Do not infer unrestricted write access or current transport details.</data></edge><edge id="R57_REL038" source="DB_DCF" target="SYS_MBR"><data key="edge_relationship_id">R57_REL038</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">reads_and_updates_according_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2017 IDMS PIA explicitly states DCF reads and updates according to MBR.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Do not infer unrestricted write access or current transport details.</data></edge><edge id="R57_REL039" source="SVC_EN_PORTAL" target="APP_ITOPSS"><data key="edge_relationship_id">R57_REL039</data><data key="edge_source_entity_id">SVC_EN_PORTAL</data><data key="edge_relationship_type">secure_web_interface_for</data><data key="edge_target_entity_id">APP_ITOPSS</data><data key="edge_operational_context">2017 PIA says EN and State VR users conduct Ticket to Work business through the secure EN Portal in the iTOPSS subsystem.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Historical portal boundary; current implementation/name unverified.</data></edge><edge id="R57_REL040" source="APP_BSAS" target="APP_IDMS_DIS"><data key="edge_relationship_id">R57_REL040</data><data key="edge_source_entity_id">APP_BSAS</data><data key="edge_relationship_type">subsystem_of</data><data key="edge_target_entity_id">APP_IDMS_DIS</data><data key="edge_operational_context">2011 BOND PIA and 2017 IDMS PIA place BSAS within IDMS.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">BSAS later became obsolete after BOND ended.</data></edge><edge id="R57_REL041" source="SVC_BWS" target="APP_IDMS_DIS"><data key="edge_relationship_id">R57_REL041</data><data key="edge_source_entity_id">SVC_BWS</data><data key="edge_relationship_type">subsystem_of</data><data key="edge_target_entity_id">APP_IDMS_DIS</data><data key="edge_operational_context">BOND Web Services is documented as an IDMS subsystem.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Historical project relationship.</data></edge><edge id="R57_REL042" source="APP_BODS" target="SVC_BWS"><data key="edge_relationship_id">R57_REL042</data><data key="edge_source_entity_id">APP_BODS</data><data key="edge_relationship_type">sends_data_via</data><data key="edge_target_entity_id">SVC_BWS</data><data key="edge_operational_context">BODS generated study/earnings data for one-way transfer through BWS.</data><data key="edge_observed_as_of">2011-01-19</data><data key="edge_confidence">5</data><data key="edge_notes">Historical BOND architecture.</data></edge><edge id="R57_REL043" source="SVC_BWS" target="APP_BSAS"><data key="edge_relationship_id">R57_REL043</data><data key="edge_source_entity_id">SVC_BWS</data><data key="edge_relationship_type">transfers_one_way_to</data><data key="edge_target_entity_id">APP_BSAS</data><data key="edge_operational_context">BWS provided the one-way data exchange from BODS to BSAS.</data><data key="edge_observed_as_of">2011-01-19</data><data key="edge_confidence">5</data><data key="edge_notes">Historical BOND architecture.</data></edge><edge id="R57_REL044" source="APP_BSAS" target="APP_MACADE"><data key="edge_relationship_id">R57_REL044</data><data key="edge_source_entity_id">APP_BSAS</data><data key="edge_relationship_type">feeds_processing_to</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">IDMS PIA says BWS/BSAS data supported MACADE batch automated processing and manual alerts/exceptions.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">5</data><data key="edge_notes">Historical BOND processing path; does not imply current operation.</data></edge><edge id="R57_REL045" source="APP_BDCS" target="APP_BODS"><data key="edge_relationship_id">R57_REL045</data><data key="edge_source_entity_id">APP_BDCS</data><data key="edge_relationship_type">provides_participant_data_to</data><data key="edge_target_entity_id">APP_BODS</data><data key="edge_operational_context">2017 IDMS PIA describes BODS storing information from BDCS for contractor analysis/reporting.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">4</data><data key="edge_notes">PIA table has wording inconsistency between BDCS/BODS rows; relationship is retained with reduced confidence and a conflict note.</data></edge><edge id="R57_REL046" source="APP_BODS" target="APP_IDMS_DIS"><data key="edge_relationship_id">R57_REL046</data><data key="edge_source_entity_id">APP_BODS</data><data key="edge_relationship_type">historically_externally_hosted_relative_to</data><data key="edge_target_entity_id">APP_IDMS_DIS</data><data key="edge_operational_context">2011 BOND PIA states BODS was housed outside SSA firewalls while BWS and BSAS were inside.</data><data key="edge_observed_as_of">2011-01-19</data><data key="edge_confidence">5</data><data key="edge_notes">Hosting is historical and project-specific; no current hosting inference.</data></edge><edge id="R57_REL047" source="APP_ETO" target="APP_ITOPSS"><data key="edge_relationship_id">R57_REL047</data><data key="edge_source_entity_id">APP_ETO</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_ITOPSS</data><data key="edge_operational_context">2017 PIA lists ETO as a TTW-supporting case-management application alongside IDMS ticket operations.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">4</data><data key="edge_notes">Logical program support relationship; exact integration mechanism not documented.</data></edge><edge id="R57_REL048" source="APP_BPS" target="APP_BSAS"><data key="edge_relationship_id">R57_REL048</data><data key="edge_source_entity_id">APP_BPS</data><data key="edge_relationship_type">analyzes_program_data_for</data><data key="edge_target_entity_id">APP_BSAS</data><data key="edge_operational_context">BPS analyzed SSA/RSA/DOL information for BOND evaluation; modeled as part of the same demonstration ecosystem, not as a direct technical interface.</data><data key="edge_observed_as_of">2017-02-13</data><data key="edge_confidence">3</data><data key="edge_notes">No direct BPS-to-BSAS transport is documented; relationship is analytical/ecosystem only.</data></edge><edge id="R57_REL049" source="SYS_MBR" target="DATA_MBR_MONTHLY_AWARD_ACTION_FILE"><data key="edge_relationship_id">R57_REL049</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">creates_monthly_award_action_file</data><data key="edge_target_entity_id">DATA_MBR_MONTHLY_AWARD_ACTION_FILE</data><data key="edge_operational_context">SSA methodology states that each month, when MBR is updated, a record/file of award actions is created.</data><data key="edge_observed_as_of">2026-03</data><data key="edge_confidence">5</data><data key="edge_notes">Statistical-production lineage; underlying ETL/tooling not identified.</data></edge><edge id="R57_REL050" source="DATA_MBR_MONTHLY_AWARD_ACTION_FILE" target="DATA_OASDI_ANNUAL_AWARD_FILE"><data key="edge_relationship_id">R57_REL050</data><data key="edge_source_entity_id">DATA_MBR_MONTHLY_AWARD_ACTION_FILE</data><data key="edge_relationship_type">combined_into</data><data key="edge_target_entity_id">DATA_OASDI_ANNUAL_AWARD_FILE</data><data key="edge_operational_context">Twelve monthly MBR award-action files are combined to produce the annual file.</data><data key="edge_observed_as_of">2026-03</data><data key="edge_confidence">5</data><data key="edge_notes">Documented 100-percent award-data production path.</data></edge><edge id="R57_REL051" source="DATA_OASDI_ANNUAL_AWARD_FILE" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R57_REL051</data><data key="edge_source_entity_id">DATA_OASDI_ANNUAL_AWARD_FILE</data><data key="edge_relationship_type">used_to_prepare_award_statistics_for</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Annual 100-percent award file is the documented production source for Supplement award statistics; 2026 Supplement remains in staged release.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Methodology is documented in the 2025 edition completed in 2026; relationship to 2026 publication family is highly plausible but exact 2026 Appendix B text is not yet published, so confidence is reduced.</data></edge><edge id="R58_REL001" source="APP_TCVQ" target="APP_DXQM"><data key="edge_relationship_id">R58_REL001</data><data key="edge_source_entity_id">APP_TCVQ</data><data key="edge_relationship_type">located_on</data><data key="edge_target_entity_id">APP_DXQM</data><data key="edge_operational_context">SSA current catalog says field offices request returned-check SSN information through TCVQ located on DXQM.</data><data key="edge_observed_as_of">2026-08-06</data><data key="edge_confidence">5</data><data key="edge_notes">No hosting or database technology is inferred.</data></edge><edge id="R58_REL002" source="APP_PAYMT" target="DATA_SSI_PAYMENT_FILES"><data key="edge_relationship_id">R58_REL002</data><data key="edge_source_entity_id">APP_PAYMT</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_SSI_PAYMENT_FILES</data><data key="edge_operational_context">Existing validated PAYMT architecture describes production of SSI payment files; the current Federal Data Catalog independently catalogs SSI Payment Files as files sent to Treasury.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship joins a previously validated PAYMT function to the newly cataloged current data asset; physical file format/staging is unresolved.</data></edge><edge id="R58_REL003" source="DATA_SSI_PAYMENT_FILES" target="ORG_TREASURY"><data key="edge_relationship_id">R58_REL003</data><data key="edge_source_entity_id">DATA_SSI_PAYMENT_FILES</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Current Federal Data Catalog explicitly states the SSI Payment Files are sent to the Department of Treasury to pay SSI recipients.</data><data key="edge_observed_as_of">2026-08-05</data><data key="edge_confidence">5</data><data key="edge_notes">Transport and cadence not disclosed by this source.</data></edge><edge id="R58_REL004" source="PROC_OHO_VE_BPA" target="SVC_FEDCONNECT"><data key="edge_relationship_id">R58_REL004</data><data key="edge_source_entity_id">PROC_OHO_VE_BPA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_FEDCONNECT</data><data key="edge_operational_context">SSA says that when a VE BPA solicitation is active, all interested vendors must register and apply through FedConnect.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">SSA says there is no active VE BPA solicitation at observation time.</data></edge><edge id="R58_REL005" source="PROC_OHO_VE_BPA" target="ORG_OHO"><data key="edge_relationship_id">R58_REL005</data><data key="edge_source_entity_id">PROC_OHO_VE_BPA</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">SSA describes VEs as providing services under BPA arrangements for the Office of Hearings Operations.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Process relationship; not a contract award claim.</data></edge><edge id="R58_REL006" source="PROC_AWI_CALC" target="DATA_AWI_RAW_WAGE"><data key="edge_relationship_id">R58_REL006</data><data key="edge_source_entity_id">PROC_AWI_CALC</data><data key="edge_relationship_type">consumes</data><data key="edge_target_entity_id">DATA_AWI_RAW_WAGE</data><data key="edge_operational_context">OACT says the change in latest raw average wage over the prior year is applied in calculating the next AWI.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Formula-level lineage only.</data></edge><edge id="R58_REL007" source="PROC_AWI_CALC" target="DATA_AWI_SERIES"><data key="edge_relationship_id">R58_REL007</data><data key="edge_source_entity_id">PROC_AWI_CALC</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_AWI_SERIES</data><data key="edge_operational_context">OACT publishes the national AWI series and states the calculation used to produce each next index value.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Production platform not disclosed.</data></edge><edge id="R58_REL008" source="SYS_MEF" target="PROC_AWI_CALC"><data key="edge_relationship_id">R58_REL008</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">provides_wage_basis_for</data><data key="edge_target_entity_id">PROC_AWI_CALC</data><data key="edge_operational_context">SSA historical earnings documentation says the MEF Detail Segment retains IRS-taxable wages from W-2 records and that this wage field is used in calculating the national average wage.</data><data key="edge_observed_as_of">2009-10</data><data key="edge_confidence">4</data><data key="edge_notes">Strong historical lineage; does not establish the exact current OACT extraction job, interface, or platform.</data></edge><edge id="R58_REL009" source="DATA_CAR" target="APP_EVIEW"><data key="edge_relationship_id">R58_REL009</data><data key="edge_source_entity_id">DATA_CAR</data><data key="edge_relationship_type">available_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">HALLEX says the court legal assistant informs OGC that the completed CAR is available in eView.</data><data key="edge_observed_as_of">2023-06-26</data><data key="edge_confidence">5</data><data key="edge_notes">Represents availability, not a claim that eView is the sole storage repository.</data></edge><edge id="R58_REL010" source="PROC_CAR_USAO_ROUTING" target="APP_EVIEW"><data key="edge_relationship_id">R58_REL010</data><data key="edge_source_entity_id">PROC_CAR_USAO_ROUTING</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Electronic CAR routing begins with the completed record available in eView.</data><data key="edge_observed_as_of">2023-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL011" source="PROC_CAR_USAO_ROUTING" target="SVC_USAFX"><data key="edge_relationship_id">R58_REL011</data><data key="edge_source_entity_id">PROC_CAR_USAO_ROUTING</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_USAFX</data><data key="edge_operational_context">HALLEX directs upload of the completed CAR and segments, when appropriate, to USAfx.</data><data key="edge_observed_as_of">2023-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL012" source="PROC_CAR_USAO_ROUTING" target="APP_ARPS"><data key="edge_relationship_id">R58_REL012</data><data key="edge_source_entity_id">PROC_CAR_USAO_ROUTING</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ARPS</data><data key="edge_operational_context">HALLEX directs staff to complete the case-analysis section, close to-do items/diaries, enter CAR page count/routing information, and close the case in ARPS as part of CAR routing.</data><data key="edge_observed_as_of">2023-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL013" source="SVC_USAFX" target="ORG_USAO"><data key="edge_relationship_id">R58_REL013</data><data key="edge_source_entity_id">SVC_USAFX</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">ORG_USAO</data><data key="edge_operational_context">HALLEX identifies USAfx as the upload channel used when routing the CAR to the United States Attorney's Office for federal-court filing.</data><data key="edge_observed_as_of">2023-06-26</data><data key="edge_confidence">5</data><data key="edge_notes">Ownership and downstream court-filing mechanics are not disclosed.</data></edge><edge id="R58_REL014" source="PROC_OHO_ADDRESS_VERIFY" target="APP_HACPS"><data key="edge_relationship_id">R58_REL014</data><data key="edge_source_entity_id">PROC_OHO_ADDRESS_VERIFY</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">APP_HACPS</data><data key="edge_operational_context">Current HALLEX requires OHO staff to check HACPS for updated claimant address information before specified notices/contact actions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL015" source="PROC_OHO_ADDRESS_VERIFY" target="QRY_FACT"><data key="edge_relationship_id">R58_REL015</data><data key="edge_source_entity_id">PROC_OHO_ADDRESS_VERIFY</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">QRY_FACT</data><data key="edge_operational_context">Current HALLEX requires the MBR Full Account Query (FACT) for Title II address verification.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">FACT is treated as query access to MBR, not an independent address master.</data></edge><edge id="R58_REL016" source="PROC_OHO_ADDRESS_VERIFY" target="QRY_SSID"><data key="edge_relationship_id">R58_REL016</data><data key="edge_source_entity_id">PROC_OHO_ADDRESS_VERIFY</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">QRY_SSID</data><data key="edge_operational_context">Current HALLEX requires SSID for Title XVI address verification.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">SSID is treated as a query/display, not the authoritative repository itself.</data></edge><edge id="R58_REL017" source="PROC_OHO_ADDRESS_VERIFY" target="APP_MDW_AI"><data key="edge_relationship_id">R58_REL017</data><data key="edge_source_entity_id">PROC_OHO_ADDRESS_VERIFY</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">Current HALLEX requires MDW for either title when checking for updated address/contact information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL018" source="PROC_OHO_ADDRESS_VERIFY" target="APP_PUPS"><data key="edge_relationship_id">R58_REL018</data><data key="edge_source_entity_id">PROC_OHO_ADDRESS_VERIFY</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Current HALLEX includes PUPS among queries staff must check for updated address/contact information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This does not make PUPS an address master.</data></edge><edge id="R58_REL019" source="PROC_OHO_ADDRESS_VERIFY" target="APP_ORS"><data key="edge_relationship_id">R58_REL019</data><data key="edge_source_entity_id">PROC_OHO_ADDRESS_VERIFY</data><data key="edge_relationship_type">may_check</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">HALLEX notes updated address/contact information may also be found in medical evidence or the Online Retrieval System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">ORS is an additional source, not a master-record update path.</data></edge><edge id="R58_REL020" source="APP_QCHECK" target="APP_MDW_AI"><data key="edge_relationship_id">R58_REL020</data><data key="edge_source_entity_id">APP_QCHECK</data><data key="edge_relationship_type">includes_query</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">HALLEX states QCHECK includes MDW.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Runtime implementation requires later technical corroboration.</data></edge><edge id="R58_REL021" source="APP_QCHECK" target="QRY_FACT"><data key="edge_relationship_id">R58_REL021</data><data key="edge_source_entity_id">APP_QCHECK</data><data key="edge_relationship_type">includes_query</data><data key="edge_target_entity_id">QRY_FACT</data><data key="edge_operational_context">HALLEX states QCHECK includes FACT.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL022" source="APP_QCHECK" target="QRY_SSID"><data key="edge_relationship_id">R58_REL022</data><data key="edge_source_entity_id">APP_QCHECK</data><data key="edge_relationship_type">includes_query</data><data key="edge_target_entity_id">QRY_SSID</data><data key="edge_operational_context">HALLEX states QCHECK includes SSID.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL023" source="PROC_T2_UNDELIV_ADDRESS" target="FORM_E3759"><data key="edge_relationship_id">R58_REL023</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_E3759</data><data key="edge_operational_context">Current Title II whereabouts/undeliverable-mail procedures direct FO/PC staff to send E3759 or an equivalent DPS locate letter to the beneficiary financial institution when direct deposit exists and the beneficiary cannot be located.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL024" source="FORM_E3759" target="ORG_BENEFICIARY_FI"><data key="edge_relationship_id">R58_REL024</data><data key="edge_source_entity_id">FORM_E3759</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_operational_context">E3759 is addressed to the financial institution where the beneficiary receives direct deposit and requests the current mailing address.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL025" source="ORG_BENEFICIARY_FI" target="DATA_FI_BENEFICIARY_ADDRESS"><data key="edge_relationship_id">R58_REL025</data><data key="edge_source_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_FI_BENEFICIARY_ADDRESS</data><data key="edge_operational_context">POMS permits a financial institution to provide beneficiary address information to SSA for this Title II locate purpose under the cited RFPA exception.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This is address-development data, not SSI AFI account-verification data.</data></edge><edge id="R58_REL026" source="DATA_FI_BENEFICIARY_ADDRESS" target="APP_POS"><data key="edge_relationship_id">R58_REL026</data><data key="edge_source_entity_id">DATA_FI_BENEFICIARY_ADDRESS</data><data key="edge_relationship_type">entered_via</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Existing current Title II address-development policy states a new address obtained from a financial institution can be input through POS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Manual/authorized post-entitlement action; no automatic FI-to-MBR write is inferred.</data></edge><edge id="R58_REL027" source="DATA_TITLEII_ZIP_FLAG" target="SYS_MBR"><data key="edge_relationship_id">R58_REL027</data><data key="edge_source_entity_id">DATA_TITLEII_ZIP_FLAG</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS defines the Title II ZIP Code Flag as a status/control field on the Title II record and states P indicates the MBR address changed from USPS NCOA information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Policy page dates to 2011; field semantics are preserved without inferring implementation technology.</data></edge><edge id="R58_REL028" source="DATA_TITLEII_ZIP_FLAG_DATE" target="SYS_MBR"><data key="edge_relationship_id">R58_REL028</data><data key="edge_source_entity_id">DATA_TITLEII_ZIP_FLAG_DATE</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS states the ZIP Code Flag Date is the month/year the flag applies to the MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL029" source="PROC_NCOA_TITLEII" target="DATA_TITLEII_ZIP_FLAG"><data key="edge_relationship_id">R58_REL029</data><data key="edge_source_entity_id">PROC_NCOA_TITLEII</data><data key="edge_relationship_type">sets</data><data key="edge_target_entity_id">DATA_TITLEII_ZIP_FLAG</data><data key="edge_operational_context">POMS states NCOA processing automatically generates ZIP flags L, P, and X to represent processing status.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL030" source="DATA_ZDPC" target="APP_ZIP4_SOFTWARE"><data key="edge_relationship_id">R58_REL030</data><data key="edge_source_entity_id">DATA_ZDPC</data><data key="edge_relationship_type">generated_by</data><data key="edge_target_entity_id">APP_ZIP4_SOFTWARE</data><data key="edge_operational_context">SSA ZIP-maintenance policy states the ZDPC is determined by ZIP+4 Software.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Existing ZIP+4 software entity is retained; no vendor/product version is inferred.</data></edge><edge id="R58_REL031" source="DATA_ZDPC" target="SYS_MBR"><data key="edge_relationship_id">R58_REL031</data><data key="edge_source_entity_id">DATA_ZDPC</data><data key="edge_relationship_type">annotated_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA policy states the ZIP Maintenance Operation automatically generates and annotates ZDPC to the MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL032" source="DATA_ZDPC" target="SYS_SSR"><data key="edge_relationship_id">R58_REL032</data><data key="edge_source_entity_id">DATA_ZDPC</data><data key="edge_relationship_type">annotated_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA policy states the ZIP Maintenance Operation automatically generates and annotates ZDPC to the SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R58_REL033" source="APP_CHIP" target="UTIL_GUNSCHIP"><data key="edge_relationship_id">R58_REL033</data><data key="edge_source_entity_id">APP_CHIP</data><data key="edge_relationship_type">uses_numident_utility</data><data key="edge_target_entity_id">UTIL_GUNSCHIP</data><data key="edge_operational_context">Current September 29, 2026 SSA inventory names CHIP among applications using the GUNSCHIP/GUNPUC03 utility family to obtain Numident data.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Inventory names the utility family collectively; it does not prove CHIP calls both utilities in every transaction.</data></edge><edge id="R58_REL034" source="APP_CHIP" target="UTIL_GUNPUC03"><data key="edge_relationship_id">R58_REL034</data><data key="edge_source_entity_id">APP_CHIP</data><data key="edge_relationship_type">uses_numident_utility</data><data key="edge_target_entity_id">UTIL_GUNPUC03</data><data key="edge_operational_context">Current September 29, 2026 SSA inventory names CHIP among applications using the GUNSCHIP/GUNPUC03 utility family to obtain Numident data.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Inventory names the utility family collectively; it does not prove CHIP calls both utilities in every transaction.</data></edge><edge id="R58_REL035" source="APP_PEBES" target="UTIL_GUNSCHIP"><data key="edge_relationship_id">R58_REL035</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">uses_numident_utility</data><data key="edge_target_entity_id">UTIL_GUNSCHIP</data><data key="edge_operational_context">Current September 29, 2026 SSA inventory names PEBES among applications using the GUNSCHIP/GUNPUC03 utility family to obtain Numident data.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Inventory names the utility family collectively; it does not prove PEBES calls both utilities in every transaction.</data></edge><edge id="R58_REL036" source="APP_PEBES" target="UTIL_GUNPUC03"><data key="edge_relationship_id">R58_REL036</data><data key="edge_source_entity_id">APP_PEBES</data><data key="edge_relationship_type">uses_numident_utility</data><data key="edge_target_entity_id">UTIL_GUNPUC03</data><data key="edge_operational_context">Current September 29, 2026 SSA inventory names PEBES among applications using the GUNSCHIP/GUNPUC03 utility family to obtain Numident data.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Inventory names the utility family collectively; it does not prove PEBES calls both utilities in every transaction.</data></edge><edge id="R59_REL001" source="EX_EAB" target="DATA_NUMIDENT_EAB_PARENTAGE"><data key="edge_relationship_id">R59_REL001</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">populates</data><data key="edge_target_entity_id">DATA_NUMIDENT_EAB_PARENTAGE</data><data key="edge_operational_context">State vital-statistics birth-registration data, including parent names, are transmitted to SSA through EAB and represented on an EAB Numident iteration.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL002" source="DATA_NUMIDENT_EAB_PARENTAGE" target="SYS_NUMIDENT"><data key="edge_relationship_id">R59_REL002</data><data key="edge_source_entity_id">DATA_NUMIDENT_EAB_PARENTAGE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS identifies FMC=6 and MNA/FNA values on the child’s EAB Numident iteration.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL003" source="ORG_BENEFICIARY_FI" target="DATA_DIRECT_DEPOSIT_NOC"><data key="edge_relationship_id">R59_REL003</data><data key="edge_source_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_DIRECT_DEPOSIT_NOC</data><data key="edge_operational_context">The beneficiary financial institution uses a NOC to send routing/account changes to SSA.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL004" source="DATA_DIRECT_DEPOSIT_NOC" target="TECH_ACH"><data key="edge_relationship_id">R59_REL004</data><data key="edge_source_entity_id">DATA_DIRECT_DEPOSIT_NOC</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">TECH_ACH</data><data key="edge_operational_context">Financial institutions transmit NOCs to SSA electronically through ACH.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL005" source="DATA_DIRECT_DEPOSIT_NOC" target="SYS_MBR"><data key="edge_relationship_id">R59_REL005</data><data key="edge_source_entity_id">DATA_DIRECT_DEPOSIT_NOC</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS says NOC information appears on the Title II record; MBR is the Atlas canonical Title II master-record endpoint. The source does not name MBR in this specific NOC sentence.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R59_REL006" source="DATA_DIRECT_DEPOSIT_NOC" target="SYS_SSR"><data key="edge_relationship_id">R59_REL006</data><data key="edge_source_entity_id">DATA_DIRECT_DEPOSIT_NOC</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says NOC information appears on the Title XVI record; SSR is the Atlas canonical Title XVI master-record endpoint. The source does not name SSR in this specific NOC sentence.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R59_REL007" source="DATA_DIRECT_DEPOSIT_PRENOTE" target="ORG_BENEFICIARY_FI"><data key="edge_relationship_id">R59_REL007</data><data key="edge_source_entity_id">DATA_DIRECT_DEPOSIT_PRENOTE</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_operational_context">Active POMS defines Prenote as notice that SSA will soon begin sending payments to the account; no internal generating system is established.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R59_REL008" source="DATA_DNE" target="ORG_FRBR"><data key="edge_relationship_id">R59_REL008</data><data key="edge_source_entity_id">DATA_DNE</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">ORG_FRBR</data><data key="edge_operational_context">SSA POMS states DNE is sent through the Richmond Federal Reserve Bank.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL009" source="DATA_DNE" target="TECH_ACH"><data key="edge_relationship_id">R59_REL009</data><data key="edge_source_entity_id">DATA_DNE</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">TECH_ACH</data><data key="edge_operational_context">RFRB passes DNE information through ACH to the U.S. financial institution.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL010" source="DATA_DNE" target="ORG_BENEFICIARY_FI"><data key="edge_relationship_id">R59_REL010</data><data key="edge_source_entity_id">DATA_DNE</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_operational_context">DNE is sent to the financial institution receiving the beneficiary/recipient direct deposit.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL011" source="SYS_MBR" target="DATA_DNE"><data key="edge_relationship_id">R59_REL011</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">triggers_generation_of</data><data key="edge_target_entity_id">DATA_DNE</data><data key="edge_operational_context">Automated DNE processing begins when verified death is posted/termination appears on the Title II record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R59_REL012" source="SYS_SSR" target="DATA_DNE"><data key="edge_relationship_id">R59_REL012</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">triggers_generation_of</data><data key="edge_target_entity_id">DATA_DNE</data><data key="edge_operational_context">Automated DNE processing begins when verified death is posted/termination appears on the Title XVI record.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R59_REL013" source="DATA_DNE" target="PROC_EFT_RECLAMATION"><data key="edge_relationship_id">R59_REL013</data><data key="edge_source_entity_id">DATA_DNE</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_EFT_RECLAMATION</data><data key="edge_operational_context">DNE issuance starts the timing sequence leading to automated reclamation requests when payments are not returned.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL014" source="PROC_EFT_RECLAMATION" target="DATA_ESTOP_SF1184"><data key="edge_relationship_id">R59_REL014</data><data key="edge_source_entity_id">PROC_EFT_RECLAMATION</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_ESTOP_SF1184</data><data key="edge_operational_context">Automated reclamation processing sends an E-stop/SF-1184 request for outstanding post-death EFT payments.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL015" source="DATA_ESTOP_SF1184" target="ORG_TREASURY"><data key="edge_relationship_id">R59_REL015</data><data key="edge_source_entity_id">DATA_ESTOP_SF1184</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">SSA sends the automated E-stop reclamation request to Treasury.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL016" source="PROC_EFT_RECLAMATION" target="DB_PHUS"><data key="edge_relationship_id">R59_REL016</data><data key="edge_source_entity_id">PROC_EFT_RECLAMATION</data><data key="edge_relationship_type">records_status_in</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">For Title II, POMS states PHUS shows E-stop information sent to Treasury and related payment/reclamation history.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL017" source="PROC_CORRESPONDENT_BANKING" target="DB_RTND"><data key="edge_relationship_id">R59_REL017</data><data key="edge_source_entity_id">PROC_CORRESPONDENT_BANKING</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DB_RTND</data><data key="edge_operational_context">Correspondent-banking policy directs staff to the RTND screen for the U.S. financial institution routing number.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL018" source="PROC_CORRESPONDENT_BANKING" target="EX_ENR"><data key="edge_relationship_id">R59_REL018</data><data key="edge_source_entity_id">PROC_CORRESPONDENT_BANKING</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">EX_ENR</data><data key="edge_operational_context">A U.S. FI may directly input correspondent-banking enrollment information through Auto Enrollment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL019" source="EX_ENR" target="SYS_MBR"><data key="edge_relationship_id">R59_REL019</data><data key="edge_source_entity_id">EX_ENR</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Correspondent-banking POMS explicitly states the U.S. FI can directly input information to MBR through Auto Enrollment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL020" source="DATA_DSI_EOL_QA" target="PROC_DQR_QUALITY_REVIEW"><data key="edge_relationship_id">R59_REL020</data><data key="edge_source_entity_id">DATA_DSI_EOL_QA</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_operational_context">The cataloged dataset contains sampled disability cases for end-of-line quality-assurance reviews. Mapping to the Atlas DQR process is functional rather than proof of a specific QRCPS physical interface.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R59_REL021" source="FORM_SSA1774" target="PROC_DQR_QUALITY_REVIEW"><data key="edge_relationship_id">R59_REL021</data><data key="edge_source_entity_id">FORM_SSA1774</data><data key="edge_relationship_type">used_within</data><data key="edge_target_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_operational_context">DQR completes the Request for Corrective Action to return specified deficiencies to the adjudicating component.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL022" source="APP_QRCPS" target="FORM_SSA1774"><data key="edge_relationship_id">R59_REL022</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">FORM_SSA1774</data><data key="edge_operational_context">Current POMS says DQR case-processing information electronically propagates most SSA-1774-U5 sections; QRCPS is the currently validated DQR case-processing system.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R59_REL023" source="SYS_SSR" target="REPORT_SSI_ASR_2025"><data key="edge_relationship_id">R59_REL023</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">REPORT_SSI_ASR_2025</data><data key="edge_operational_context">SSI applications tables identify SSR as the 100-percent administrative data source.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL024" source="SYS_MBR" target="REPORT_SSI_ASR_2025"><data key="edge_relationship_id">R59_REL024</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">REPORT_SSI_ASR_2025</data><data key="edge_operational_context">Combined Social Security/SSI recipient tables identify MBR together with SSR as 100-percent administrative data sources.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL025" source="DATA_DISABILITY_RESEARCH_FILE" target="REPORT_SSI_ASR_2025"><data key="edge_relationship_id">R59_REL025</data><data key="edge_source_entity_id">DATA_DISABILITY_RESEARCH_FILE</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">REPORT_SSI_ASR_2025</data><data key="edge_operational_context">The disability-application outcome section is derived from the Disability Research File.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL026" source="DB_DIODS" target="DATA_SSA_DISABILITY_CLAIM_DATA"><data key="edge_relationship_id">R59_REL026</data><data key="edge_source_entity_id">DB_DIODS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_SSA_DISABILITY_CLAIM_DATA</data><data key="edge_operational_context">SSA states the disability claim receipt, determination, and favorable determination data in this public product come entirely from DIODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL027" source="SYS_MBR" target="REPORT_DI_ASR_2024"><data key="edge_relationship_id">R59_REL027</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">REPORT_DI_ASR_2024</data><data key="edge_operational_context">Current-beneficiary tables and award tables from 2012 onward use MBR 100-percent data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL028" source="DATA_AWARD_TERMINATION_TRANSACTION" target="REPORT_DI_ASR_2024"><data key="edge_relationship_id">R59_REL028</data><data key="edge_source_entity_id">DATA_AWARD_TERMINATION_TRANSACTION</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">REPORT_DI_ASR_2024</data><data key="edge_operational_context">Historical disability award/termination tables use the Annual Award and Termination Transaction file for documented years during 2000-2011.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL029" source="REPORT_STAT_SUPP_2026" target="ORG_SSA_OCACT"><data key="edge_relationship_id">R59_REL029</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">redirects_section_to</data><data key="edge_target_entity_id">ORG_SSA_OCACT</data><data key="edge_operational_context">The 2026 Supplement discontinues section 4.A Trust Funds because those tables are already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R59_REL030" source="REPORT_STAT_SUPP_2026" target="ORG_SSA_OCACT"><data key="edge_relationship_id">R59_REL030</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">redirects_section_to</data><data key="edge_target_entity_id">ORG_SSA_OCACT</data><data key="edge_operational_context">The 2026 Supplement discontinues section 4.C Insured Workers because those tables are already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL001" source="DB_NIDD" target="APP_SSNAP"><data key="edge_relationship_id">R60_REL001</data><data key="edge_source_entity_id">DB_NIDD</data><data key="edge_relationship_type">reference_used_by</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Current POMS directs enumeration employees to review NIDD when an identity document is absent from the standard Enumeration System dropdown.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">NIDD is modeled as reference data; no direct runtime API is inferred.</data></edge><edge id="R60_REL002" source="DB_NIDD" target="APP_SSNAP"><data key="edge_relationship_id">R60_REL002</data><data key="edge_source_entity_id">DB_NIDD</data><data key="edge_relationship_type">can_populate_document_options_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Current POMS states regional coordinators use the NIDD User Guide to load acceptable identity documents into SSNAP.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL003" source="SVC_DOCUTECTOR" target="APP_DVW"><data key="edge_relationship_id">R60_REL003</data><data key="edge_source_entity_id">SVC_DOCUTECTOR</data><data key="edge_relationship_type">reference_available_through</data><data key="edge_target_entity_id">APP_DVW</data><data key="edge_operational_context">Current POMS identifies Docutector as a visual-standard resource available through SSA document-verification resources/DVW.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL004" source="DB_NIDD" target="APP_DVW"><data key="edge_relationship_id">R60_REL004</data><data key="edge_source_entity_id">DB_NIDD</data><data key="edge_relationship_type">reference_available_through</data><data key="edge_target_entity_id">APP_DVW</data><data key="edge_operational_context">Current POMS identifies NIDD among document-verification resources accessible through the Document Verification Website.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL005" source="APP_DVW" target="APP_SSNAP"><data key="edge_relationship_id">R60_REL005</data><data key="edge_source_entity_id">APP_DVW</data><data key="edge_relationship_type">supports_document_authenticity_review_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Enumeration staff use DVW visual-reference resources while reviewing evidence submitted for SSN-card processing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow support relationship only; no automated write-back to SSNAP is inferred.</data></edge><edge id="R60_REL006" source="DATA_DISALLOWED_APP_FILE" target="APP_SSNAP"><data key="edge_relationship_id">R60_REL006</data><data key="edge_source_entity_id">DATA_DISALLOWED_APP_FILE</data><data key="edge_relationship_type">consulted_during_identity_assessment_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">POMS identifies an applicant record on the Disallowed Application File as an indicator that identity may be questionable during SSN evidence review.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The source establishes policy use but not whether the check is automated inside SSNAP or performed through a separate query.</data></edge><edge id="R60_REL007" source="WORK_SSNAP_SUSPECT_HOLD" target="APP_SSNAP"><data key="edge_relationship_id">R60_REL007</data><data key="edge_source_entity_id">WORK_SSNAP_SUSPECT_HOLD</data><data key="edge_relationship_type">holds_pending_applications_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Suspect evidence is entered into SSNAP and may remain in Suspect Status while verification with the issuing agency is completed.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL008" source="PROC_SSNAP_OTSP" target="APP_SSNAP"><data key="edge_relationship_id">R60_REL008</data><data key="edge_source_entity_id">PROC_SSNAP_OTSP</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">OTSP is an SSNAP/Enumeration System option for exception evidence processing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL009" source="PROC_SSNAP_OTSP" target="DB_NIDD"><data key="edge_relationship_id">R60_REL009</data><data key="edge_source_entity_id">PROC_SSNAP_OTSP</data><data key="edge_relationship_type">used_with_reference_to</data><data key="edge_target_entity_id">DB_NIDD</data><data key="edge_operational_context">When a document is absent from the normal SSNAP dropdown, policy uses NIDD review and may direct selection of OTSP.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Does not imply every OTSP case originates in NIDD.</data></edge><edge id="R60_REL010" source="DATA_DIFSLA_FINDER" target="EX_CMA1016_IRS_DISFLA"><data key="edge_relationship_id">R60_REL010</data><data key="edge_source_entity_id">DATA_DIFSLA_FINDER</data><data key="edge_relationship_type">input_to</data><data key="edge_target_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_operational_context">SSA supplies the CMA 1016 DIFSLA finder/tickler file containing SSN and name control for requested individuals.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL011" source="DATA_DIFSLA_FINDER" target="DB_IRS_NAP_DM1"><data key="edge_relationship_id">R60_REL011</data><data key="edge_source_entity_id">DATA_DIFSLA_FINDER</data><data key="edge_relationship_type">validated_against</data><data key="edge_target_entity_id">DB_IRS_NAP_DM1</data><data key="edge_operational_context">IRS initially validates all SSA SSNs and name controls in the finder data against NAP-DM1.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL012" source="DATA_DIFSLA_FINDER" target="DB_IRS_IRMF"><data key="edge_relationship_id">R60_REL012</data><data key="edge_source_entity_id">DATA_DIFSLA_FINDER</data><data key="edge_relationship_type">matched_against</data><data key="edge_target_entity_id">DB_IRS_IRMF</data><data key="edge_operational_context">After identifier validation, IRS matches the SSA finder information against IRMF through DIFSLA.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL013" source="DB_IRS_IRMF" target="DATA_DIFSLA_RESPONSE"><data key="edge_relationship_id">R60_REL013</data><data key="edge_source_entity_id">DB_IRS_IRMF</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_DIFSLA_RESPONSE</data><data key="edge_operational_context">CMA 1016 states IRS extracts and discloses unearned-income return information from IRMF in response to SSA-identified individuals.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL014" source="DATA_DIFSLA_RESPONSE" target="EX_CMA1016_IRS_DISFLA"><data key="edge_relationship_id">R60_REL014</data><data key="edge_source_entity_id">DATA_DIFSLA_RESPONSE</data><data key="edge_relationship_type">response_for</data><data key="edge_target_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_operational_context">IRS provides response records under CMA 1016/DIFSLA for the individuals identified by SSA.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL015" source="DATA_DIFSLA_RESPONSE" target="DATA_DIFSLA_PAYEE_ADDRESS"><data key="edge_relationship_id">R60_REL015</data><data key="edge_source_entity_id">DATA_DIFSLA_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_DIFSLA_PAYEE_ADDRESS</data><data key="edge_operational_context">The DIFSLA response includes payee name and mailing address.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL016" source="DATA_DIFSLA_RESPONSE" target="DATA_DIFSLA_PAYER_ADDRESS"><data key="edge_relationship_id">R60_REL016</data><data key="edge_source_entity_id">DATA_DIFSLA_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_DIFSLA_PAYER_ADDRESS</data><data key="edge_operational_context">The DIFSLA response includes payer name and address.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL017" source="EX_CMA1016_IRS_DISFLA" target="DB_IRS_IRMF"><data key="edge_relationship_id">R60_REL017</data><data key="edge_source_entity_id">EX_CMA1016_IRS_DISFLA</data><data key="edge_relationship_type">uses_source</data><data key="edge_target_entity_id">DB_IRS_IRMF</data><data key="edge_operational_context">The current signed agreement explicitly identifies IRMF as the IRS system matched through DIFSLA.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL018" source="APP_FAS" target="APP_FAS_SMS"><data key="edge_relationship_id">R60_REL018</data><data key="edge_source_entity_id">APP_FAS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_FAS_SMS</data><data key="edge_operational_context">The Functional Assessment Study uses computerized adaptive testing through the Calibration Study Management System.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL019" source="APP_FAS_SMS" target="APP_FAS_QDS"><data key="edge_relationship_id">R60_REL019</data><data key="edge_source_entity_id">APP_FAS_SMS</data><data key="edge_relationship_type">includes_module</data><data key="edge_target_entity_id">APP_FAS_QDS</data><data key="edge_operational_context">The current PIA describes QDS as one of two discrete SMS modules.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL020" source="ORG_WESTAT" target="APP_FAS_SMS"><data key="edge_relationship_id">R60_REL020</data><data key="edge_source_entity_id">ORG_WESTAT</data><data key="edge_relationship_type">built_and_hosts</data><data key="edge_target_entity_id">APP_FAS_SMS</data><data key="edge_operational_context">The PIA states Westat built the CAT Calibration SMS and houses it.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL021" source="ORG_BU_HDRI" target="ORG_WESTAT"><data key="edge_relationship_id">R60_REL021</data><data key="edge_source_entity_id">ORG_BU_HDRI</data><data key="edge_relationship_type">subcontracts_data_collection_to</data><data key="edge_target_entity_id">ORG_WESTAT</data><data key="edge_operational_context">The PIA states BU-HDRI subcontracted with Westat to assist with study data collection.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL022" source="ORG_NIH_CRC_RMD" target="ORG_BU_HDRI"><data key="edge_relationship_id">R60_REL022</data><data key="edge_source_entity_id">ORG_NIH_CRC_RMD</data><data key="edge_relationship_type">subcontracts_research_work_to</data><data key="edge_target_entity_id">ORG_BU_HDRI</data><data key="edge_operational_context">The PIA states NIH CRC/RMD subcontracted with BU-HDRI to develop CAT instruments and questions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL023" source="ORG_NIH_CRC_RMD" target="APP_FAS"><data key="edge_relationship_id">R60_REL023</data><data key="edge_source_entity_id">ORG_NIH_CRC_RMD</data><data key="edge_relationship_type">conducts</data><data key="edge_target_entity_id">APP_FAS</data><data key="edge_operational_context">The PIA identifies NIH CRC/RMD as conducting the Functional Assessment Study sponsored by SSA ODP.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL024" source="APP_FAS" target="ORG_WESTAT"><data key="edge_relationship_id">R60_REL024</data><data key="edge_source_entity_id">APP_FAS</data><data key="edge_relationship_type">provides_claimant_pii_to</data><data key="edge_target_entity_id">ORG_WESTAT</data><data key="edge_operational_context">Through NIH CRC/RMD and BU-HDRI, SSA ODP provides Westat claims-related PII including name, age, sex, address, SSN, email address, and impairment allegations.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This is study-scoped data sharing; no general SSA-to-Westat feed is inferred.</data></edge><edge id="R60_REL025" source="APP_800_EMPVER" target="APP_IRES"><data key="edge_relationship_id">R60_REL025</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">authenticates_via</data><data key="edge_target_entity_id">APP_IRES</data><data key="edge_operational_context">The current TNEV PIA states the automated telephone application uses IRES user ID and password credentials to authenticate users.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Potential transition conflict retained: current BSO web access uses Login.gov/ID.me while this current-listed TNEV PIA still documents IRES.</data></edge><edge id="R60_REL026" source="MODEL_OACT_BEN_SR" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R60_REL026</data><data key="edge_source_entity_id">MODEL_OACT_BEN_SR</data><data key="edge_relationship_type">supports_projection_in</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">The 2026 Trustees Report says Actuarial Services uses a short-range model for the first 10 years of beneficiary projections.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R60_REL027" source="MODEL_OACT_BEN_LR" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R60_REL027</data><data key="edge_source_entity_id">MODEL_OACT_BEN_LR</data><data key="edge_relationship_type">supports_projection_in</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">The 2026 Trustees Report says Actuarial Services uses a separate long-range beneficiary model after the first 10 years.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL001" source="SURVEY_NBS_1982" target="DATA_NBDS"><data key="edge_relationship_id">R61_REL001</data><data key="edge_source_entity_id">SURVEY_NBS_1982</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_NBDS</data><data key="edge_operational_context">SSA identifies the 1982 national New Beneficiary Survey as the initial survey basis for NBDS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL002" source="SURVEY_NBF_1991" target="DATA_NBDS"><data key="edge_relationship_id">R61_REL002</data><data key="edge_source_entity_id">SURVEY_NBF_1991</data><data key="edge_relationship_type">expands</data><data key="edge_target_entity_id">DATA_NBDS</data><data key="edge_operational_context">SSA says the 1991 New Beneficiary Follow-up expanded NBDS with a second round of interviews and updated longitudinal measures.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL003" source="DATA_NBDS_ADMIN_PUF" target="DATA_NBDS"><data key="edge_relationship_id">R61_REL003</data><data key="edge_source_entity_id">DATA_NBDS_ADMIN_PUF</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">DATA_NBDS</data><data key="edge_operational_context">SSA publishes public-use administrative-data files for NBDS respondents and spouses as part of the NBDS data resource.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL004" source="DATA_NBDS_PUF" target="DATA_NBDS"><data key="edge_relationship_id">R61_REL004</data><data key="edge_source_entity_id">DATA_NBDS_PUF</data><data key="edge_relationship_type">publishes_from</data><data key="edge_target_entity_id">DATA_NBDS</data><data key="edge_operational_context">The Federal Data Catalog describes the public-use files as releases from NBDS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL005" source="DATA_NBDS_ADMIN_PUF" target="DATA_NBDS_PUF"><data key="edge_relationship_id">R61_REL005</data><data key="edge_source_entity_id">DATA_NBDS_ADMIN_PUF</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">DATA_NBDS_PUF</data><data key="edge_operational_context">The SSA NBDS landing page includes public-use administrative data as a component of the released NBDS public-use files.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL006" source="ORG_OHO" target="DATA_OHO_AVG_WAIT_MONTHLY"><data key="edge_relationship_id">R61_REL006</data><data key="edge_source_entity_id">ORG_OHO</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_OHO_AVG_WAIT_MONTHLY</data><data key="edge_operational_context">OHO publishes the monthly Average Wait Time Until Hearing Held report for its hearing offices and national hearing centers.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL007" source="ORG_OHO" target="DATA_OHO_AVG_WAIT_HIST"><data key="edge_relationship_id">R61_REL007</data><data key="edge_source_entity_id">ORG_OHO</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_OHO_AVG_WAIT_HIST</data><data key="edge_operational_context">SSA Open Data identifies the historical national hearing-held processing-time series as an appeals-operation dataset.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL008" source="DATA_OHO_AVG_WAIT_MONTHLY" target="DATA_OHO_AVG_WAIT_HIST"><data key="edge_relationship_id">R61_REL008</data><data key="edge_source_entity_id">DATA_OHO_AVG_WAIT_MONTHLY</data><data key="edge_relationship_type">extends_historical_reporting_after</data><data key="edge_target_entity_id">DATA_OHO_AVG_WAIT_HIST</data><data key="edge_operational_context">SSA states the separate monthly office dataset provides more current data beginning September 2010, while the historical annual dataset covers FY1989-2009.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship describes publication continuity only, not a shared physical production pipeline.</data></edge><edge id="R61_REL009" source="DATA_OASDI_STATE_COUNTY_2025" target="SYS_MBR"><data key="edge_relationship_id">R61_REL009</data><data key="edge_source_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA states that the OASDI state-and-county statistics are derived from the Master Beneficiary Record, the principal administrative file of Social Security beneficiaries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL010" source="DATA_USPS_NATIONAL_ZIP4" target="ORG_USPS"><data key="edge_relationship_id">R61_REL010</data><data key="edge_source_entity_id">DATA_USPS_NATIONAL_ZIP4</data><data key="edge_relationship_type">produced_by</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">SSA identifies the national ZIP+4 file used in this publication as produced by the U.S. Postal Service.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL011" source="PROC_OASDI_STATE_COUNTY_ASSIGN" target="SYS_MBR"><data key="edge_relationship_id">R61_REL011</data><data key="edge_source_entity_id">PROC_OASDI_STATE_COUNTY_ASSIGN</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The publication method begins with MBR beneficiary/payee address data for state/county designation.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL012" source="PROC_OASDI_STATE_COUNTY_ASSIGN" target="DATA_USPS_NATIONAL_ZIP4"><data key="edge_relationship_id">R61_REL012</data><data key="edge_source_entity_id">PROC_OASDI_STATE_COUNTY_ASSIGN</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_USPS_NATIONAL_ZIP4</data><data key="edge_operational_context">SSA uses the USPS national ZIP+4 file to improve county assignment where ZIP Code areas cross county boundaries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL013" source="PROC_OASDI_STATE_COUNTY_ASSIGN" target="DOM_REPPAYEE"><data key="edge_relationship_id">R61_REL013</data><data key="edge_source_entity_id">PROC_OASDI_STATE_COUNTY_ASSIGN</data><data key="edge_relationship_type">uses_representative_payee_location_for_payee_cases</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">SSA states that when a beneficiary has a representative payee, the publication assigns state and county based on the representative payee, not the beneficiary.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL014" source="PROC_OASDI_STATE_COUNTY_ASSIGN" target="DATA_OASDI_STATE_COUNTY_2025"><data key="edge_relationship_id">R61_REL014</data><data key="edge_source_entity_id">PROC_OASDI_STATE_COUNTY_ASSIGN</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_operational_context">The documented geographic-assignment method supports the 2025 state-and-county publication.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL015" source="DATA_SSI_STATE_COUNTY_2025" target="SYS_SSR"><data key="edge_relationship_id">R61_REL015</data><data key="edge_source_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA states that the SSI state-and-county statistics are drawn from the Supplemental Security Record, the principal administrative data file for SSI.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL016" source="FORM_SSA89" target="APP_ECBSV"><data key="edge_relationship_id">R61_REL016</data><data key="edge_source_entity_id">FORM_SSA89</data><data key="edge_relationship_type">authorizes_disclosure_through</data><data key="edge_target_entity_id">APP_ECBSV</data><data key="edge_operational_context">SSA eCBSV guidance accepts Form SSA-89 as written consent authorizing disclosure of SSN verification results to permitted entities/financial institutions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL017" source="FORM_SSA89" target="APP_CBSV"><data key="edge_relationship_id">R61_REL017</data><data key="edge_source_entity_id">FORM_SSA89</data><data key="edge_relationship_type">used_for_consent_in</data><data key="edge_target_entity_id">APP_CBSV</data><data key="edge_operational_context">SSA CBSV enrollment instructions include a current copy of Form SSA-89 in the user agreement package.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL018" source="PROC_SSA_DNP_REVISED_SCHEDULE" target="SVC_DNP"><data key="edge_relationship_id">R61_REL018</data><data key="edge_source_entity_id">PROC_SSA_DNP_REVISED_SCHEDULE</data><data key="edge_relationship_type">coordinated_with</data><data key="edge_target_entity_id">SVC_DNP</data><data key="edge_operational_context">Treasury states Do Not Pay participated with SSA and Federal Disbursement Services in the revised recurring-payment schedule.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL019" source="PROC_SSA_DNP_REVISED_SCHEDULE" target="ORG_FDS"><data key="edge_relationship_id">R61_REL019</data><data key="edge_source_entity_id">PROC_SSA_DNP_REVISED_SCHEDULE</data><data key="edge_relationship_type">coordinated_with</data><data key="edge_target_entity_id">ORG_FDS</data><data key="edge_operational_context">Treasury states Federal Disbursement Services participated with Do Not Pay and SSA in the revised schedule.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL020" source="ORG_FDS" target="ORG_TREASURY"><data key="edge_relationship_id">R61_REL020</data><data key="edge_source_entity_id">ORG_FDS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Federal Disbursement Services is identified on a Bureau of the Fiscal Service page within the Department of the Treasury context.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Organizational hierarchy recorded at Treasury level; no lower-level org-chart claims are inferred.</data></edge><edge id="R61_REL021" source="ORG_SSA_OAG" target="SVC_SAM_GOV"><data key="edge_relationship_id">R61_REL021</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">requires_applicant_registration_via</data><data key="edge_target_entity_id">SVC_SAM_GOV</data><data key="edge_operational_context">SSA OAG instructs grant applicants to register or update their registration on SAM.gov.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL022" source="ORG_SSA_OAG" target="SVC_GRANTS_GOV"><data key="edge_relationship_id">R61_REL022</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">routes_competitive_grant_applications_via</data><data key="edge_target_entity_id">SVC_GRANTS_GOV</data><data key="edge_operational_context">SSA OAG instructs applicants for competitive discretionary grants to submit through Grants.gov.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL023" source="ORG_SSA_OAG" target="SVC_GRANTSOLUTIONS"><data key="edge_relationship_id">R61_REL023</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">routes_continuation_grant_applications_via</data><data key="edge_target_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_operational_context">SSA OAG instructs applicants for continuation grants to submit through GrantSolutions when stipulated in the announcement.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL024" source="NETWORK_TEFCA" target="USECASE_TEFCA_GBD"><data key="edge_relationship_id">R61_REL024</data><data key="edge_source_entity_id">NETWORK_TEFCA</data><data key="edge_relationship_type">supports_use_case</data><data key="edge_target_entity_id">USECASE_TEFCA_GBD</data><data key="edge_operational_context">SSA says selecting eHealth Exchange as its QHIN strengthens SSA’s Government Benefits Determination use case under TEFCA.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL025" source="ORG_EHEALTH_EXCHANGE" target="USECASE_TEFCA_GBD"><data key="edge_relationship_id">R61_REL025</data><data key="edge_source_entity_id">ORG_EHEALTH_EXCHANGE</data><data key="edge_relationship_type">qhin_supports</data><data key="edge_target_entity_id">USECASE_TEFCA_GBD</data><data key="edge_operational_context">SSA selected eHealth Exchange as its QHIN for TEFCA testing in support of disability medical-evidence exchange and the Government Benefits Determination use case.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R61_REL026" source="APP_DIPS" target="SYS_NUMIDENT"><data key="edge_relationship_id">R61_REL026</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">verifies_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG describes DIPS as verifying state death reports before death information is recorded to Numident; the underlying audit identifies Numident matching as one rejection-check category.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This relationship supplements the existing DIPS -&gt; Numident update relationship; it does not imply every verification check is a direct Numident query.</data></edge><edge id="R61_REL027" source="EX_IEDR" target="APP_DIPS"><data key="edge_relationship_id">R61_REL027</data><data key="edge_source_entity_id">EX_IEDR</data><data key="edge_relationship_type">processed_through</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">OIG documents DIPS as the verification system for state death reports before accepted death information is posted to SSA records.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">I-EDR is one documented state vital-statistics submission channel; OIG discusses state death reports generally, so confidence is below maximum for channel-specific routing.</data></edge><edge id="R62_REL001" source="DB_ACT_TOR" target="APP_ACT"><data key="edge_relationship_id">R62_REL001</data><data key="edge_source_entity_id">DB_ACT_TOR</data><data key="edge_relationship_type">reports_for</data><data key="edge_target_entity_id">APP_ACT</data><data key="edge_operational_context">Catalog describes this as the tactical/operational reporting data store for ACT.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL002" source="DB_EMAC2" target="PROC_PUBLIC_INQUIRY_CORR"><data key="edge_relationship_id">R62_REL002</data><data key="edge_source_entity_id">DB_EMAC2</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_PUBLIC_INQUIRY_CORR</data><data key="edge_operational_context">EMAC 2 provides a production data-store environment for control/tracking of high-priority correspondence in the Office of Public Inquiries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL003" source="DB_OPI_CORRESP_CONTROL" target="PROC_PUBLIC_INQUIRY_CORR"><data key="edge_relationship_id">R62_REL003</data><data key="edge_source_entity_id">DB_OPI_CORRESP_CONTROL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_PUBLIC_INQUIRY_CORR</data><data key="edge_operational_context">OPI Correspondence Control System provides a production data-store environment for control/tracking of high-priority OPI correspondence.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL004" source="DB_CONTROL_TRACK_WS" target="UTIL_ESVC_CONTROL_TRACK"><data key="edge_relationship_id">R62_REL004</data><data key="edge_source_entity_id">DB_CONTROL_TRACK_WS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">UTIL_ESVC_CONTROL_TRACK</data><data key="edge_operational_context">Catalog says the data asset stores submission control numbers and status inserts to support eServices Control And Tracking.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL005" source="SVC_CONTROL_TRACK_WS_MI" target="UTIL_ESVC_CONTROL_TRACK"><data key="edge_relationship_id">R62_REL005</data><data key="edge_source_entity_id">SVC_CONTROL_TRACK_WS_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">UTIL_ESVC_CONTROL_TRACK</data><data key="edge_operational_context">Catalog describes a web service that processes application requests for control-number submissions and status inserts in the same eServices control/tracking function.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R62_REL006" source="PROC_SSIDPP" target="SYS_SSR"><data key="edge_relationship_id">R62_REL006</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">identifies_duplicate_records_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSIDPP selects and resolves duplicate SSI records to prevent duplicate payments and maintain SSR integrity.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL007" source="PROC_SSIDPP" target="SYS_NUMIDENT"><data key="edge_relationship_id">R62_REL007</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Case material includes Numident data for affected SSNs.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL008" source="PROC_SSIDPP" target="QRY_SSID"><data key="edge_relationship_id">R62_REL008</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">QRY_SSID</data><data key="edge_operational_context">Case material includes Supplemental Security Income Displays for affected records.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL009" source="PROC_SSIDPP" target="DATA_SSIDPP_CASE_CONTROL"><data key="edge_relationship_id">R62_REL009</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">produces_or_uses</data><data key="edge_target_entity_id">DATA_SSIDPP_CASE_CONTROL</data><data key="edge_operational_context">Case material includes case control sheets for both SSNs affected.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL010" source="DATA_SSR_M1" target="SYS_SSR"><data key="edge_relationship_id">R62_REL010</data><data key="edge_source_entity_id">DATA_SSR_M1</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current duplicate-record procedure directs cross-reference SSN entries into the SSR M1 field.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL011" source="DATA_SSR_MA" target="SYS_SSR"><data key="edge_relationship_id">R62_REL011</data><data key="edge_source_entity_id">DATA_SSR_MA</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current duplicate-record procedure uses the SSR MA field when the duplicate SSN was also issued through enumeration.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL012" source="PROC_SSIDPP" target="DATA_SSR_M1"><data key="edge_relationship_id">R62_REL012</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">writes_identity_cross_reference_to</data><data key="edge_target_entity_id">DATA_SSR_M1</data><data key="edge_operational_context">For duplicate records belonging to the same person, staff put the correct SSN on the terminated record and wrong SSN on the correct record in M1.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL013" source="PROC_SSIDPP" target="DATA_SSR_MA"><data key="edge_relationship_id">R62_REL013</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">conditionally_writes_enumeration_cross_reference_to</data><data key="edge_target_entity_id">DATA_SSR_MA</data><data key="edge_operational_context">If the terminated-record SSN was also issued to the individual through enumeration, POMS directs input to MA as well as M1.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL014" source="PROC_SSIDPP" target="DOM_PROGRAM_DEBT"><data key="edge_relationship_id">R62_REL014</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">may_trigger</data><data key="edge_target_entity_id">DOM_PROGRAM_DEBT</data><data key="edge_operational_context">The project explicitly identifies resulting overpayments for development when duplicate payments occurred.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL015" source="PROC_SSIDPP" target="APP_MSSICS"><data key="edge_relationship_id">R62_REL015</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">may_use</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">For duplicate/no-payment records with an unarchived MSSICS pending file, staff clear the pending file before T50 termination.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL016" source="WORK_SSI_E2_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R62_REL016</data><data key="edge_source_entity_id">WORK_SSI_E2_DIARY</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Annual systems COLA sets an E2 diary on the SSR when documented rental-subsidy/payment-status criteria are met.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL017" source="DATA_SSI_RENTAL_SUBSIDY_AMOUNT" target="WORK_SSI_E2_DIARY"><data key="edge_relationship_id">R62_REL017</data><data key="edge_source_entity_id">DATA_SSI_RENTAL_SUBSIDY_AMOUNT</data><data key="edge_relationship_type">used_to_set</data><data key="edge_target_entity_id">WORK_SSI_E2_DIARY</data><data key="edge_operational_context">An E2 diary is set when the rental subsidy amount is greater than zero for the most recent living-arrangement period and other criteria are met.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL018" source="WORK_SSI_E2_DIARY" target="DATA_SSI_CMRV"><data key="edge_relationship_id">R62_REL018</data><data key="edge_source_entity_id">WORK_SSI_E2_DIARY</data><data key="edge_relationship_type">triggers_development_of</data><data key="edge_target_entity_id">DATA_SSI_CMRV</data><data key="edge_operational_context">E2 processing requires verification/update of rental amount and current market rental value for the relevant living-arrangement period.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL019" source="IFACE_SSI_DIRECT_SSR" target="UI_SSI_UDIA"><data key="edge_relationship_id">R62_REL019</data><data key="edge_source_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_SSI_UDIA</data><data key="edge_operational_context">POMS directs staff to clear an E2 diary via the UDIA screen in Direct SSR Update when specified development attempts fail.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL020" source="UI_SSI_UDIA" target="WORK_SSI_E2_DIARY"><data key="edge_relationship_id">R62_REL020</data><data key="edge_source_entity_id">UI_SSI_UDIA</data><data key="edge_relationship_type">clears</data><data key="edge_target_entity_id">WORK_SSI_E2_DIARY</data><data key="edge_operational_context">UDIA is the documented Direct SSR Update screen used to clear the E2 diary in the stated condition.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL021" source="WORK_SSI_E2_DIARY" target="UI_SSI_LRES"><data key="edge_relationship_id">R62_REL021</data><data key="edge_source_entity_id">WORK_SSI_E2_DIARY</data><data key="edge_relationship_type">uses_residence_context_from</data><data key="edge_target_entity_id">UI_SSI_LRES</data><data key="edge_operational_context">Rental-subsidy edits use the address state on the Residence Address and Jurisdiction page as part of the documented processing context.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R62_REL022" source="PROC_SSI_RESIDENCY_DETERMINATION" target="UI_SSI_LRES"><data key="edge_relationship_id">R62_REL022</data><data key="edge_source_entity_id">PROC_SSI_RESIDENCY_DETERMINATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_SSI_LRES</data><data key="edge_operational_context">SSI residence determination relies on Residence Address and Jurisdiction information and policy-directed supporting evidence when needed.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL023" source="APP_MSSICS" target="DATA_SSI_RES_STATE_COUNTY"><data key="edge_relationship_id">R62_REL023</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">prefills</data><data key="edge_target_entity_id">DATA_SSI_RES_STATE_COUNTY</data><data key="edge_operational_context">MSSICS/LRES can prefill state and county codes based on alleged residence and residence ZIP code.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL024" source="DATA_SSI_RES_STATE_COUNTY" target="SYS_SSR"><data key="edge_relationship_id">R62_REL024</data><data key="edge_source_entity_id">DATA_SSI_RES_STATE_COUNTY</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Policy directs staff to enter/correct state and county of residence on the SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL025" source="PROC_SSI_RESIDENCY_DETERMINATION" target="DATA_SSI_RES_STATE_COUNTY"><data key="edge_relationship_id">R62_REL025</data><data key="edge_source_entity_id">PROC_SSI_RESIDENCY_DETERMINATION</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_SSI_RES_STATE_COUNTY</data><data key="edge_operational_context">Staff must overwrite incorrect prefilled state/county codes based on actual residence determination.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL026" source="UI_SSI_LRES" target="DATA_SSI_RES_STATE_COUNTY"><data key="edge_relationship_id">R62_REL026</data><data key="edge_source_entity_id">UI_SSI_LRES</data><data key="edge_relationship_type">stores_or_displays</data><data key="edge_target_entity_id">DATA_SSI_RES_STATE_COUNTY</data><data key="edge_operational_context">LRES entries drive the state/county prefill from residence ZIP; resulting codes must be checked and corrected.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R62_REL027" source="DATA_SSI_RENTAL_SUBSIDY_AMOUNT" target="UI_SSI_HOME_RENT"><data key="edge_relationship_id">R62_REL027</data><data key="edge_source_entity_id">DATA_SSI_RENTAL_SUBSIDY_AMOUNT</data><data key="edge_relationship_type">displayed_or_evaluated_on</data><data key="edge_target_entity_id">UI_SSI_HOME_RENT</data><data key="edge_operational_context">Current E2 rental-subsidy edits explicitly evaluate the rental subsidy amount on the Home Ownership and Rental Liability page.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL028" source="WORK_SSI_E2_DIARY" target="UI_SSI_HOME_RENT"><data key="edge_relationship_id">R62_REL028</data><data key="edge_source_entity_id">WORK_SSI_E2_DIARY</data><data key="edge_relationship_type">uses_rental_context_from</data><data key="edge_target_entity_id">UI_SSI_HOME_RENT</data><data key="edge_operational_context">Current E2 edit logic evaluates rental subsidy amount from the Home Ownership and Rental Liability page when determining required living-arrangement actions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL029" source="DATA_LAWFUL_PRESENCE_PROOF" target="SYS_MBR"><data key="edge_relationship_id">R62_REL029</data><data key="edge_source_entity_id">DATA_LAWFUL_PRESENCE_PROOF</data><data key="edge_relationship_type">stored_or_evidenced_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current lawful-presence policy allows qualifying MBR LAW PRS proof/status coding to establish prior proof under stated conditions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL030" source="DATA_LAWFUL_PRESENCE_PROOF" target="SYS_SSR"><data key="edge_relationship_id">R62_REL030</data><data key="edge_source_entity_id">DATA_LAWFUL_PRESENCE_PROOF</data><data key="edge_relationship_type">stored_or_evidenced_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current policy allows qualifying SSR alien-status coding, corroborated by archived SSI claims screens, to establish prior proof under stated conditions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL031" source="DATA_LAWFUL_PRESENCE_PROOF" target="APP_MCS"><data key="edge_relationship_id">R62_REL031</data><data key="edge_source_entity_id">DATA_LAWFUL_PRESENCE_PROOF</data><data key="edge_relationship_type">stored_or_evidenced_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Cleared/archived MCS CLLP/remarks information can establish lawful-presence evidence under stated conditions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL032" source="DATA_LAWFUL_PRESENCE_PROOF" target="APP_MSSICS"><data key="edge_relationship_id">R62_REL032</data><data key="edge_source_entity_id">DATA_LAWFUL_PRESENCE_PROOF</data><data key="edge_relationship_type">stored_or_evidenced_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Cleared/archived MSSICS Alien Status/remarks information can establish lawful-presence evidence under stated conditions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL033" source="SYS_NUMIDENT" target="DATA_LAWFUL_PRESENCE_PROOF"><data key="edge_relationship_id">R62_REL033</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">not_accepted_as_evidence_for</data><data key="edge_target_entity_id">DATA_LAWFUL_PRESENCE_PROOF</data><data key="edge_operational_context">Current POMS expressly says Numident coding is not acceptable evidence of U.S. lawful presence for this claim-proof purpose.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL034" source="DATA_PI_ARN" target="SVC_SAVE"><data key="edge_relationship_id">R62_REL034</data><data key="edge_source_entity_id">DATA_PI_ARN</data><data key="edge_relationship_type">used_to_query</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">Current policy uses an Alien Registration Number/A-Number to query online SAVE and separately says ARN from the document is entered in Person Information.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL035" source="DATA_DHS_ADMISSION_NUMBER" target="SVC_SAVE"><data key="edge_relationship_id">R62_REL035</data><data key="edge_source_entity_id">DATA_DHS_ADMISSION_NUMBER</data><data key="edge_relationship_type">used_to_query</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">An Admission Number can be used as the query identifier for online SAVE.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL036" source="SVC_SAVE" target="DATA_SAVE_ELIGIBILITY_STATEMENT"><data key="edge_relationship_id">R62_REL036</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_SAVE_ELIGIBILITY_STATEMENT</data><data key="edge_operational_context">The SAVE response propagated to SSA includes an Eligibility Statement along with person and immigration-status data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL037" source="DATA_SAVE_ELIGIBILITY_STATEMENT" target="APP_EP"><data key="edge_relationship_id">R62_REL037</data><data key="edge_source_entity_id">DATA_SAVE_ELIGIBILITY_STATEMENT</data><data key="edge_relationship_type">archived_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Policy requires copies of immigration documentation and the SAVE response to be scanned/uploaded into the electronic folder, including through Evidence Portal.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL038" source="DATA_SAVE_ELIGIBILITY_STATEMENT" target="APP_EVIEW"><data key="edge_relationship_id">R62_REL038</data><data key="edge_source_entity_id">DATA_SAVE_ELIGIBILITY_STATEMENT</data><data key="edge_relationship_type">viewed_or_archived_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Policy names eView as an electronic-folder route for the copied immigration document and SAVE response.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL039" source="APP_ISSNRC" target="SVC_DLDV"><data key="edge_relationship_id">R62_REL039</data><data key="edge_source_entity_id">APP_ISSNRC</data><data key="edge_relationship_type">verifies_state_identity_data_via</data><data key="edge_target_entity_id">SVC_DLDV</data><data key="edge_operational_context">iSSNRC policy lists participating jurisdictions for no-change replacement-card verification under AAMVA/DLDV.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL040" source="SVC_DLDV" target="ORG_AAMVA"><data key="edge_relationship_id">R62_REL040</data><data key="edge_source_entity_id">SVC_DLDV</data><data key="edge_relationship_type">facilitated_by</data><data key="edge_target_entity_id">ORG_AAMVA</data><data key="edge_operational_context">POMS explicitly labels the driver-license/state-ID verification participation column AAMVA/DLDV.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R62_REL041" source="APP_ISSNRC" target="ORG_NAPHSIS"><data key="edge_relationship_id">R62_REL041</data><data key="edge_source_entity_id">APP_ISSNRC</data><data key="edge_relationship_type">verifies_marriage_data_via</data><data key="edge_target_entity_id">ORG_NAPHSIS</data><data key="edge_operational_context">iSSNRC policy separately lists NAPHSIS participation for last-name changes due to marriage.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL042" source="APP_DHS_SELF_CHECK" target="EX_EVERIFY"><data key="edge_relationship_id">R62_REL042</data><data key="edge_source_entity_id">APP_DHS_SELF_CHECK</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">EX_EVERIFY</data><data key="edge_operational_context">POMS states Self Check is a subsystem of E-Verify.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL043" source="APP_DHS_SELF_CHECK" target="ORG_DHS"><data key="edge_relationship_id">R62_REL043</data><data key="edge_source_entity_id">APP_DHS_SELF_CHECK</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_DHS</data><data key="edge_operational_context">POMS states DHS owns and administers Self Check and E-Verify.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL044" source="APP_EV_STAR" target="EX_EVERIFY"><data key="edge_relationship_id">R62_REL044</data><data key="edge_source_entity_id">APP_EV_STAR</data><data key="edge_relationship_type">supports_case_resolution_for</data><data key="edge_target_entity_id">EX_EVERIFY</data><data key="edge_operational_context">SSA field offices/card centers must access EV-STAR to record E-Verify case resolution.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL045" source="APP_DHS_SELF_CHECK" target="APP_EV_STAR"><data key="edge_relationship_id">R62_REL045</data><data key="edge_source_entity_id">APP_DHS_SELF_CHECK</data><data key="edge_relationship_type">not_accessible_in</data><data key="edge_target_entity_id">APP_EV_STAR</data><data key="edge_operational_context">POMS explicitly says SSA staff do not access EV-STAR for Self Check cases.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL046" source="SVC_SELF_LOCK" target="EX_EVERIFY"><data key="edge_relationship_id">R62_REL046</data><data key="edge_source_entity_id">SVC_SELF_LOCK</data><data key="edge_relationship_type">controls_ssn_use_in</data><data key="edge_target_entity_id">EX_EVERIFY</data><data key="edge_operational_context">Self Lock can lock an SSN against use in E-Verify for the documented lock period.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL047" source="SVC_SELF_LOCK" target="APP_DHS_SELF_CHECK"><data key="edge_relationship_id">R62_REL047</data><data key="edge_source_entity_id">SVC_SELF_LOCK</data><data key="edge_relationship_type">controls_ssn_use_in</data><data key="edge_target_entity_id">APP_DHS_SELF_CHECK</data><data key="edge_operational_context">Self Lock also blocks the SSN from use in Self Check while active.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL048" source="SVC_SELF_LOCK" target="ORG_DHS"><data key="edge_relationship_id">R62_REL048</data><data key="edge_source_entity_id">SVC_SELF_LOCK</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_DHS</data><data key="edge_operational_context">Self Lock is a DHS myE-Verify feature.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL049" source="EX_DTA" target="FORM_SSA157"><data key="edge_relationship_id">R62_REL049</data><data key="edge_source_entity_id">EX_DTA</data><data key="edge_relationship_type">requested_via</data><data key="edge_target_entity_id">FORM_SSA157</data><data key="edge_operational_context">An agency requesting DTA must submit Form SSA-157 to ODXIA.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL050" source="EX_DTA" target="FORM_SSA120"><data key="edge_relationship_id">R62_REL050</data><data key="edge_source_entity_id">EX_DTA</data><data key="edge_relationship_type">requires_user_access_form</data><data key="edge_target_entity_id">FORM_SSA120</data><data key="edge_operational_context">Each designated employee who will use DTA requires an SSA-120 submitted to OIS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL051" source="EX_DTA" target="FORM_SSA222"><data key="edge_relationship_id">R62_REL051</data><data key="edge_source_entity_id">EX_DTA</data><data key="edge_relationship_type">conditionally_requires</data><data key="edge_target_entity_id">FORM_SSA222</data><data key="edge_operational_context">SSA-222 is required when the designated DTA user is an agency contractor.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL052" source="FORM_SSA120" target="DB_DTA_PIN_FILE"><data key="edge_relationship_id">R62_REL052</data><data key="edge_source_entity_id">FORM_SSA120</data><data key="edge_relationship_type">supports_pin_assignment_in</data><data key="edge_target_entity_id">DB_DTA_PIN_FILE</data><data key="edge_operational_context">After OIS approves required access forms, it assigns a PIN; user PII is attached to the PIN to capture transactions in the Privacy Act PIN File.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R62_REL053" source="DATA_DX_SOFTWARE_LICENSE_GRANT" target="TECH_FTMS"><data key="edge_relationship_id">R62_REL053</data><data key="edge_source_entity_id">DATA_DX_SOFTWARE_LICENSE_GRANT</data><data key="edge_relationship_type">enables_external_use_of</data><data key="edge_target_entity_id">TECH_FTMS</data><data key="edge_operational_context">External entities may receive test and production license grants for the sole purpose of communicating with SSA through the FTMS data-exchange environment.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL054" source="EX_CMA1038_BFS_SAVINGS" target="DB_BFS_SAVINGS_SECURITY_REG"><data key="edge_relationship_id">R62_REL054</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="edge_operational_context">Current SSI policy says the match compares qualifying SSI records against BFS savings security registration file.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL055" source="DB_BFS_SAVINGS_SECURITY_REG" target="ORG_BFS"><data key="edge_relationship_id">R62_REL055</data><data key="edge_source_entity_id">DB_BFS_SAVINGS_SECURITY_REG</data><data key="edge_relationship_type">maintained_by</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Current POMS identifies the matching source as BFS savings security registration file and separately describes BFS registration records.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL056" source="PROC_STP_CLAIMS" target="DOM_MEDICARE"><data key="edge_relationship_id">R62_REL056</data><data key="edge_source_entity_id">PROC_STP_CLAIMS</data><data key="edge_relationship_type">automates_processing_in</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">SSA says STP automates Medicare claims end-to-end from initial application through adjudication.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R62_REL057" source="UI_SSI_LRES" target="UI_SSI_APID"><data key="edge_relationship_id">R62_REL057</data><data key="edge_source_entity_id">UI_SSI_LRES</data><data key="edge_relationship_type">documents_residence_separately_from</data><data key="edge_target_entity_id">UI_SSI_APID</data><data key="edge_operational_context">Current redetermination policy directs residence address to LRES and mailing address to APID when they differ.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL001" source="ORG_SSA_OAG" target="PROC_ACQ360_SURVEY"><data key="edge_relationship_id">R63_REL001</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers</data><data key="edge_target_entity_id">PROC_ACQ360_SURVEY</data><data key="edge_operational_context">OAG current guidance requires/encourages use of FAR 52.201-1 Acquisition 360 in SSA solicitations under stated thresholds.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL002" source="PROC_ACQ360_SURVEY" target="SVC_SAM_GOV"><data key="edge_relationship_id">R63_REL002</data><data key="edge_source_entity_id">PROC_ACQ360_SURVEY</data><data key="edge_relationship_type">applies_to_solicitations_posted_via</data><data key="edge_target_entity_id">SVC_SAM_GOV</data><data key="edge_operational_context">The required Acquisition 360 provision is inserted into qualifying SSA solicitations posted to SAM.gov/Contract Opportunities.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL003" source="PROC_IRP_UPLOAD_DOCS" target="APP_MYSSA"><data key="edge_relationship_id">R63_REL003</data><data key="edge_source_entity_id">PROC_IRP_UPLOAD_DOCS</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Individual representative payees authenticate into my Social Security and select Representative Payee Services before entering Upload Documents.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL004" source="PROC_IRP_UPLOAD_DOCS" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R63_REL004</data><data key="edge_source_entity_id">PROC_IRP_UPLOAD_DOCS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">The workflow uses Upload Documents to submit eligible forms and evidence for a represented beneficiary.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL005" source="PROC_IRP_UPLOAD_DOCS" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">R63_REL005</data><data key="edge_source_entity_id">PROC_IRP_UPLOAD_DOCS</data><data key="edge_relationship_type">requires_authentication_via</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">Current IRP instructions explicitly allow Login.gov authentication for my Social Security access.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL006" source="PROC_IRP_UPLOAD_DOCS" target="SVC_IDME"><data key="edge_relationship_id">R63_REL006</data><data key="edge_source_entity_id">PROC_IRP_UPLOAD_DOCS</data><data key="edge_relationship_type">requires_authentication_via</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">Current IRP instructions explicitly allow ID.me authentication for my Social Security access.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL007" source="APP_IRPP" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R63_REL007</data><data key="edge_source_entity_id">APP_IRPP</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current instructions place Upload Documents on the Representative Payee Services and beneficiary overview surfaces for individual payees.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The source calls the customer surface Representative Payee Services rather than explicitly naming the iRPP acronym; relationship is mapped at reduced confidence to the existing iRPP entity.</data></edge><edge id="R63_REL008" source="FORM_SSA_2574" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R63_REL008</data><data key="edge_source_entity_id">FORM_SSA_2574</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current Forms and IRP guidance make SSA-2574 available for electronic completion/upload through Upload Documents.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL009" source="FORM_SSA_2574" target="CAP_UPLOAD_CONVERSATIONAL"><data key="edge_relationship_id">R63_REL009</data><data key="edge_source_entity_id">FORM_SSA_2574</data><data key="edge_relationship_type">available_as</data><data key="edge_target_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_operational_context">July 2026 Upload Documents guidance lists SSA-2574 among forms supported by the conversational forms capability.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL010" source="DATA_OASDI_PUF_2001" target="SYS_MBR"><data key="edge_relationship_id">R63_REL010</data><data key="edge_source_entity_id">DATA_OASDI_PUF_2001</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA states the OASDI public-use microdata file is an extract of fields from MBR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical December 2001 extract; not a live operational interface.</data></edge><edge id="R63_REL011" source="DATA_SSI_PUF_2001" target="SYS_SSR"><data key="edge_relationship_id">R63_REL011</data><data key="edge_source_entity_id">DATA_SSI_PUF_2001</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA states the SSI public-use microdata file is an extract of fields from SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical December 2001 extract; not a live operational interface.</data></edge><edge id="R63_REL012" source="REPORT_SSI_ANNUAL_2026" target="ORG_SSA_OCACT"><data key="edge_relationship_id">R63_REL012</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">published_by</data><data key="edge_target_entity_id">ORG_SSA_OCACT</data><data key="edge_operational_context">OACT publishes the 2026 SSI Annual Report as part of its actuarial/statistical program reporting.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL013" source="DATA_SSI_SINGLE_YEAR_2026" target="REPORT_SSI_ANNUAL_2026"><data key="edge_relationship_id">R63_REL013</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">supplements</data><data key="edge_target_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_operational_context">The single-year tables are explicitly published as supplemental detail consistent with the 2026 SSI Annual Report.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL014" source="ORG_SSA_OCACT" target="DATA_SSI_SINGLE_YEAR_2026"><data key="edge_relationship_id">R63_REL014</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_operational_context">OACT provides the supplemental single-year tables in HTML and Excel.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL015" source="APP_PER_TDR_MODELS" target="PROC_PER_DISABILITY_REVIEW"><data key="edge_relationship_id">R63_REL015</data><data key="edge_source_entity_id">APP_PER_TDR_MODELS</data><data key="edge_relationship_type">supports_case_selection_for</data><data key="edge_target_entity_id">PROC_PER_DISABILITY_REVIEW</data><data key="edge_operational_context">Current PER open-data documentation says PER uses a statistical model to identify favorable determinations with high probability of substantive error; this is aligned with the existing PER/TDR model entity.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Public page does not name the application/model inventory entry verbatim; relationship retained at confidence 4.</data></edge><edge id="R63_REL016" source="PROC_PER_DISABILITY_REVIEW" target="DATA_PER_REVIEW_2012_2016"><data key="edge_relationship_id">R63_REL016</data><data key="edge_source_entity_id">PROC_PER_DISABILITY_REVIEW</data><data key="edge_relationship_type">produces_public_results</data><data key="edge_target_entity_id">DATA_PER_REVIEW_2012_2016</data><data key="edge_operational_context">The public dataset contains annual national-level results of PER activity for FY2012-2016.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL017" source="PROC_DDS_ACCURACY_REVIEW" target="ORG_DDS"><data key="edge_relationship_id">R63_REL017</data><data key="edge_source_entity_id">PROC_DDS_ACCURACY_REVIEW</data><data key="edge_relationship_type">reviews_determinations_from</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">SSA samples favorable and unfavorable initial medical determinations from state DDSs to assess accuracy.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL018" source="PROC_DDS_ACCURACY_REVIEW" target="DATA_DDS_ACCURACY"><data key="edge_relationship_id">R63_REL018</data><data key="edge_source_entity_id">PROC_DDS_ACCURACY_REVIEW</data><data key="edge_relationship_type">produces_public_results</data><data key="edge_target_entity_id">DATA_DDS_ACCURACY</data><data key="edge_operational_context">The DDS Accuracy public dataset presents results from the sampled quality-assurance reviews.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL019" source="APP_PER_TDR_MODELS" target="PROC_DISABILITY_DENIAL_REVIEW"><data key="edge_relationship_id">R63_REL019</data><data key="edge_source_entity_id">APP_PER_TDR_MODELS</data><data key="edge_relationship_type">supports_case_selection_for</data><data key="edge_target_entity_id">PROC_DISABILITY_DENIAL_REVIEW</data><data key="edge_operational_context">Current denial-review documentation says SSA uses a statistical model to identify high-error-risk denied disability applications; mapped to the existing PER/TDR model family at reduced confidence.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The Open Data page does not explicitly name the application inventory object.</data></edge><edge id="R63_REL020" source="PROC_DISABILITY_DENIAL_REVIEW" target="ORG_DDS"><data key="edge_relationship_id">R63_REL020</data><data key="edge_source_entity_id">PROC_DISABILITY_DENIAL_REVIEW</data><data key="edge_relationship_type">reviews_determinations_from</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">The review examines denied disability cases adjudicated by DDSs for policy compliance and evidentiary support.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL021" source="PROC_DISABILITY_DENIAL_REVIEW" target="DATA_DISABILITY_DENIAL_REVIEWS"><data key="edge_relationship_id">R63_REL021</data><data key="edge_source_entity_id">PROC_DISABILITY_DENIAL_REVIEW</data><data key="edge_relationship_type">produces_public_results</data><data key="edge_target_entity_id">DATA_DISABILITY_DENIAL_REVIEWS</data><data key="edge_operational_context">The public data file summarizes review counts, returns, reversals, and rates.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL022" source="DATA_HEARING_REPRESENTATION_HIST" target="ORG_OHO"><data key="edge_relationship_id">R63_REL022</data><data key="edge_source_entity_id">DATA_HEARING_REPRESENTATION_HIST</data><data key="edge_relationship_type">covers_workload_of</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">The historical dataset measures attorney and non-attorney representation among OHO hearing claimants.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL023" source="DATA_HEARING_RECEIPTS_PENDING_HIST" target="ORG_OHO"><data key="edge_relationship_id">R63_REL023</data><data key="edge_source_entity_id">DATA_HEARING_RECEIPTS_PENDING_HIST</data><data key="edge_relationship_type">covers_workload_of</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">The historical dataset reports hearing receipts and pending workload; SSA points to OHO for data after FY2009.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R63_REL024" source="DATA_ALJ_CASE_REVIEW_HIST" target="ORG_OHO"><data key="edge_relationship_id">R63_REL024</data><data key="edge_source_entity_id">DATA_ALJ_CASE_REVIEW_HIST</data><data key="edge_relationship_type">covers_quality_review_of</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">The dataset reports post-effectuation quality-review agreement rates for ALJ disability hearing decisions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Review itself ended in 2019; this does not imply current ALJ post-effectuation review operation.</data></edge><edge id="R63_REL025" source="DATA_DISABILITY_RECON_APT" target="ORG_DDS"><data key="edge_relationship_id">R63_REL025</data><data key="edge_source_entity_id">DATA_DISABILITY_RECON_APT</data><data key="edge_relationship_type">measures_workload_processed_by</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Disability reconsideration processing-time data covers claims requiring medical determinations handled through the DDS process and SSA quality/payment/notice steps.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Elapsed-time metric spans end-to-end reconsideration processing; not all elapsed time belongs to DDS.</data></edge><edge id="R63_REL026" source="PROC_DUAL_MBR_SSR_COA" target="SYS_MBR"><data key="edge_relationship_id">R63_REL026</data><data key="edge_source_entity_id">PROC_DUAL_MBR_SSR_COA</data><data key="edge_relationship_type">updates_separately</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For dually entitled SSI/RSDI cases, current POMS requires a separate input to change the MBR address.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No single input changes both MBR and SSR.</data></edge><edge id="R63_REL027" source="PROC_DUAL_MBR_SSR_COA" target="SYS_SSR"><data key="edge_relationship_id">R63_REL027</data><data key="edge_source_entity_id">PROC_DUAL_MBR_SSR_COA</data><data key="edge_relationship_type">updates_separately</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">For dually entitled SSI/RSDI cases, current POMS requires a separate input to change the SSR address.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No single input changes both MBR and SSR.</data></edge><edge id="R64_REL001" source="APP_TITLEII_MAJOR" target="APP_T2_BATCH_SUBSYS"><data key="edge_relationship_id">R64_REL001</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_T2_BATCH_SUBSYS</data><data key="edge_operational_context">2017 Title II PIA identifies this subsystem within the Title II Major Application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Time-scoped to 2017 system boundary.</data></edge><edge id="R64_REL002" source="APP_TITLEII_MAJOR" target="APP_T2_INFRA_SUBSYS"><data key="edge_relationship_id">R64_REL002</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_T2_INFRA_SUBSYS</data><data key="edge_operational_context">2017 Title II PIA identifies this subsystem within the Title II Major Application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Time-scoped to 2017 system boundary.</data></edge><edge id="R64_REL003" source="APP_TITLEII_MAJOR" target="APP_T2_DATA_EXCHANGE_GROUP"><data key="edge_relationship_id">R64_REL003</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_T2_DATA_EXCHANGE_GROUP</data><data key="edge_operational_context">2017 Title II PIA identifies this subsystem within the Title II Major Application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Time-scoped to 2017 system boundary.</data></edge><edge id="R64_REL004" source="APP_TITLEII_MAJOR" target="APP_T2_PC_WORKLOADS"><data key="edge_relationship_id">R64_REL004</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_T2_PC_WORKLOADS</data><data key="edge_operational_context">2017 Title II PIA identifies this subsystem within the Title II Major Application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Time-scoped to 2017 system boundary.</data></edge><edge id="R64_REL005" source="APP_TITLEII_MAJOR" target="APP_MBR_SELECTIONS_GROUP"><data key="edge_relationship_id">R64_REL005</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_MBR_SELECTIONS_GROUP</data><data key="edge_operational_context">2017 Title II PIA identifies this subsystem within the Title II Major Application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Time-scoped to 2017 system boundary.</data></edge><edge id="R64_REL006" source="APP_TITLEII_MAJOR" target="APP_MBR_UPDATE_GROUP"><data key="edge_relationship_id">R64_REL006</data><data key="edge_source_entity_id">APP_TITLEII_MAJOR</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_MBR_UPDATE_GROUP</data><data key="edge_operational_context">2017 Title II PIA identifies this subsystem within the Title II Major Application.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Time-scoped to 2017 system boundary.</data></edge><edge id="R64_REL007" source="APP_T2_BATCH_SUBSYS" target="SYS_MBR"><data key="edge_relationship_id">R64_REL007</data><data key="edge_source_entity_id">APP_T2_BATCH_SUBSYS</data><data key="edge_relationship_type">annotates_or_updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2017 PIA says T2 Batch includes subprocesses that annotate MBR and compute benefit changes.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Field-level behavior not specified.</data></edge><edge id="R64_REL008" source="APP_T2_INFRA_SUBSYS" target="ORG_TREASURY"><data key="edge_relationship_id">R64_REL008</data><data key="edge_source_entity_id">APP_T2_INFRA_SUBSYS</data><data key="edge_relationship_type">coordinates_payment_transactions_with</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">2017 PIA says T2 Infrastructure calculates check debits, credits, payments and overpayments in coordination with Treasury.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Transport and Treasury endpoint not specified.</data></edge><edge id="R64_REL009" source="APP_MBR_SELECTIONS_GROUP" target="SYS_MBR"><data key="edge_relationship_id">R64_REL009</data><data key="edge_source_entity_id">APP_MBR_SELECTIONS_GROUP</data><data key="edge_relationship_type">updates_specific_data_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2017 PIA says MBR Selections Group applications update specific data for COLA, adjustments, and special-format runs.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Exact fields/jobs not identified.</data></edge><edge id="R64_REL010" source="APP_MBR_UPDATE_GROUP" target="SYS_MBR"><data key="edge_relationship_id">R64_REL010</data><data key="edge_source_entity_id">APP_MBR_UPDATE_GROUP</data><data key="edge_relationship_type">maintains_and_validates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2017 PIA describes MBR Update Group as maintaining payment-history/data and checking and validating claim/post-entitlement actions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The source names the group rather than a distinct physical MBR database tier.</data></edge><edge id="R64_REL011" source="APP_MBR_UPDATE_GROUP" target="ORG_TREASURY"><data key="edge_relationship_id">R64_REL011</data><data key="edge_source_entity_id">APP_MBR_UPDATE_GROUP</data><data key="edge_relationship_type">transmits_records_to</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">2017 PIA says MBR Update Group transmits Title II records to Treasury.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Exact payment file/interface not identified by this PIA.</data></edge><edge id="R64_REL012" source="APP_T2R" target="APP_T2_INFRA_SUBSYS"><data key="edge_relationship_id">R64_REL012</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">related_modern_processing_label_to</data><data key="edge_target_entity_id">APP_T2_INFRA_SUBSYS</data><data key="edge_operational_context">Current POMS continues to use T2R transaction-processing terminology, while 2017 PIA named a broader T2 Infrastructure subsystem; exact lineage/boundary equivalence is unresolved.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">3</data><data key="edge_notes">Cross-era relationship intentionally low confidence.</data></edge><edge id="R64_REL013" source="APP_QAS" target="APP_DICARS_LEGACY"><data key="edge_relationship_id">R64_REL013</data><data key="edge_source_entity_id">APP_QAS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_DICARS_LEGACY</data><data key="edge_operational_context">2018 QAS PIA identifies DICARS as a major QAS subsystem; later evidence shows DICARS was replaced by QRCPS by 2023.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical relationship.</data></edge><edge id="R64_REL014" source="APP_QAS" target="APP_DQR_LEGACY"><data key="edge_relationship_id">R64_REL014</data><data key="edge_source_entity_id">APP_QAS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_DQR_LEGACY</data><data key="edge_operational_context">2018 QAS PIA identifies DQR as a major QAS subsystem; later evidence shows legacy DQR was replaced by QRCPS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical relationship.</data></edge><edge id="R64_REL015" source="APP_QAS" target="APP_EQA"><data key="edge_relationship_id">R64_REL015</data><data key="edge_source_entity_id">APP_QAS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_EQA</data><data key="edge_operational_context">2018 QAS PIA identifies eQA as a major QAS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">eQA current production status not independently established.</data></edge><edge id="R64_REL016" source="APP_NDDSS" target="APP_DICARS_LEGACY"><data key="edge_relationship_id">R64_REL016</data><data key="edge_source_entity_id">APP_NDDSS</data><data key="edge_relationship_type">sends_sample_clearance_to</data><data key="edge_target_entity_id">APP_DICARS_LEGACY</data><data key="edge_operational_context">2018 PIA says NDDSS federally samples cleared disability cases and passes clearance information electronically to DICARS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Historical DICARS path.</data></edge><edge id="R64_REL017" source="APP_QAS" target="REPO_EF"><data key="edge_relationship_id">R64_REL017</data><data key="edge_source_entity_id">APP_QAS</data><data key="edge_relationship_type">integrates_claims_data_and_images_with</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">2018 PIA says QAS subsystems integrate with the Electronic Disability Folder and upload claims data and images to the Electronic Folder.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No transport mechanism inferred.</data></edge><edge id="R64_REL018" source="APP_EQA" target="APP_EFI"><data key="edge_relationship_id">R64_REL018</data><data key="edge_source_entity_id">APP_EQA</data><data key="edge_relationship_type">communicates_via</data><data key="edge_target_entity_id">APP_EFI</data><data key="edge_operational_context">2018 PIA explicitly lists Electronic Folder Interface communication among eQA functions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No protocol inferred.</data></edge><edge id="R64_REL019" source="APP_SSIRM" target="PROC_SSI_ABLE_REPORTING"><data key="edge_relationship_id">R64_REL019</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">PROC_SSI_ABLE_REPORTING</data><data key="edge_operational_context">2021 SSIRMS PIA identifies ABLE processing within SSIRMS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL020" source="PROC_SSI_ABLE_REPORTING" target="DATA_SSI_ABLE_ACCOUNT"><data key="edge_relationship_id">R64_REL020</data><data key="edge_source_entity_id">PROC_SSI_ABLE_REPORTING</data><data key="edge_relationship_type">receives_monthly_data_from</data><data key="edge_target_entity_id">DATA_SSI_ABLE_ACCOUNT</data><data key="edge_operational_context">State/designated-reporter monthly ABLE account information enters SSA through this process.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Mode/file format not specified.</data></edge><edge id="R64_REL021" source="DATA_SSI_ABLE_ACCOUNT" target="APP_MSSICS"><data key="edge_relationship_id">R64_REL021</data><data key="edge_source_entity_id">DATA_SSI_ABLE_ACCOUNT</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">2021 SSIRMS PIA states ABLE accounts are stored in the MSSICS database.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">APP_MSSICS represents the documented MSSICS application/database boundary; physical DBMS unspecified.</data></edge><edge id="R64_REL022" source="APP_SSIRM" target="APP_SSI_CMS_NH_INTERFACE"><data key="edge_relationship_id">R64_REL022</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_CMS_NH_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL023" source="APP_SSIRM" target="APP_SSI_DHS_ICE_INTERFACE"><data key="edge_relationship_id">R64_REL023</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_DHS_ICE_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL024" source="APP_SSIRM" target="APP_SSI_DOD_INTERFACE"><data key="edge_relationship_id">R64_REL024</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_DOD_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL025" source="APP_SSIRM" target="APP_SSI_DOL_BLB_INTERFACE"><data key="edge_relationship_id">R64_REL025</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_DOL_BLB_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL026" source="APP_SSIRM" target="APP_SSI_IRS_P1099_INTERFACE"><data key="edge_relationship_id">R64_REL026</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_IRS_P1099_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL027" source="APP_SSIRM" target="APP_SSI_MBR_INTERFACE"><data key="edge_relationship_id">R64_REL027</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_MBR_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL028" source="APP_SSIRM" target="APP_SSI_MEF_INTERFACE"><data key="edge_relationship_id">R64_REL028</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_MEF_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL029" source="APP_SSIRM" target="APP_SSI_OCSE_INTERFACE"><data key="edge_relationship_id">R64_REL029</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL030" source="APP_SSIRM" target="APP_SSI_OPM_INTERFACE"><data key="edge_relationship_id">R64_REL030</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_OPM_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL031" source="APP_SSIRM" target="APP_SSI_RRB_INTERFACE"><data key="edge_relationship_id">R64_REL031</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_RRB_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL032" source="APP_SSIRM" target="APP_SSI_VA_INTERFACE"><data key="edge_relationship_id">R64_REL032</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_VA_INTERFACE</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL033" source="APP_SSIRM" target="APP_SSI_SDX_SYSTEM"><data key="edge_relationship_id">R64_REL033</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_SDX_SYSTEM</data><data key="edge_operational_context">2021 SSIRMS PIA names this interface/system as an SSIRMS subsystem.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Component-level 2026 production status not assumed from 2021 PIA alone.</data></edge><edge id="R64_REL034" source="APP_SSI_CMS_NH_INTERFACE" target="ORG_CMS"><data key="edge_relationship_id">R64_REL034</data><data key="edge_source_entity_id">APP_SSI_CMS_NH_INTERFACE</data><data key="edge_relationship_type">receives_records_from</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">2021 PIA says the subsystem compares records received from CMS with SSI records for unreported nursing-home admissions.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL035" source="APP_SSI_CMS_NH_INTERFACE" target="EX_CMS_NURSING_1076"><data key="edge_relationship_id">R64_REL035</data><data key="edge_source_entity_id">APP_SSI_CMS_NH_INTERFACE</data><data key="edge_relationship_type">functionally_corresponds_to_current_exchange</data><data key="edge_target_entity_id">EX_CMS_NURSING_1076</data><data key="edge_operational_context">Current CMA 1076 covers CMS Title XIX facility admission/discharge matching; functional continuity is likely but exact application routing is not stated in the PIA.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Do not infer exact transport.</data></edge><edge id="R64_REL036" source="APP_SSI_DHS_ICE_INTERFACE" target="ORG_DHS"><data key="edge_relationship_id">R64_REL036</data><data key="edge_source_entity_id">APP_SSI_DHS_ICE_INTERFACE</data><data key="edge_relationship_type">receives_records_from</data><data key="edge_target_entity_id">ORG_DHS</data><data key="edge_operational_context">2021 PIA says the subsystem compares DHS records with SSI records for immigration-status eligibility.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL037" source="APP_SSI_DHS_ICE_INTERFACE" target="EX_CMA1010_DHS_NONCIT"><data key="edge_relationship_id">R64_REL037</data><data key="edge_source_entity_id">APP_SSI_DHS_ICE_INTERFACE</data><data key="edge_relationship_type">functionally_corresponds_to_current_exchange</data><data key="edge_target_entity_id">EX_CMA1010_DHS_NONCIT</data><data key="edge_operational_context">Current DHS noncitizen match serves related SSI eligibility/suspension functions; exact subsystem routing remains unproven.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R64_REL038" source="APP_SSI_DOD_INTERFACE" target="EX_CMA1004_DOD_RET"><data key="edge_relationship_id">R64_REL038</data><data key="edge_source_entity_id">APP_SSI_DOD_INTERFACE</data><data key="edge_relationship_type">functionally_corresponds_to_current_exchange</data><data key="edge_target_entity_id">EX_CMA1004_DOD_RET</data><data key="edge_operational_context">2021 PIA documents DOD finder/return military payment data; current DoD Military Retirement Match corroborates a continuing exchange function.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R64_REL039" source="APP_SSI_DOL_BLB_INTERFACE" target="EX_CMA1015_DOL_BLB"><data key="edge_relationship_id">R64_REL039</data><data key="edge_source_entity_id">APP_SSI_DOL_BLB_INTERFACE</data><data key="edge_relationship_type">functionally_corresponds_to_current_exchange</data><data key="edge_target_entity_id">EX_CMA1015_DOL_BLB</data><data key="edge_operational_context">2021 PIA documents Black Lung Part B income transactions; current CMA 1015 corroborates the continuing Part B data match.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R64_REL040" source="APP_SSI_IRS_P1099_INTERFACE" target="EX_SSI_IRS_1099"><data key="edge_relationship_id">R64_REL040</data><data key="edge_source_entity_id">APP_SSI_IRS_P1099_INTERFACE</data><data key="edge_relationship_type">functionally_corresponds_to</data><data key="edge_target_entity_id">EX_SSI_IRS_1099</data><data key="edge_operational_context">2021 PIA explicitly names the SSI/IRS Pension &amp; 1099 interface; Atlas already contains the current SSI/IRS 1099 exchange product.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Pension and 1099 subflows may have different match mechanics.</data></edge><edge id="R64_REL041" source="APP_SSI_IRS_P1099_INTERFACE" target="PROC_SSI_IRS_PENSION_MATCH"><data key="edge_relationship_id">R64_REL041</data><data key="edge_source_entity_id">APP_SSI_IRS_P1099_INTERFACE</data><data key="edge_relationship_type">supports_pension_match_process</data><data key="edge_target_entity_id">PROC_SSI_IRS_PENSION_MATCH</data><data key="edge_operational_context">2021 PIA interface receives pension data from IRS; current POMS separately validates the SSI IRS Pension Interface business process.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL042" source="APP_SSI_MBR_INTERFACE" target="SYS_MBR"><data key="edge_relationship_id">R64_REL042</data><data key="edge_source_entity_id">APP_SSI_MBR_INTERFACE</data><data key="edge_relationship_type">reads_income_and_entitlement_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2021 PIA says this interface inputs/edits/posts Title II income and Title XVIII entitlement into SSI processing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL043" source="APP_SSI_MBR_INTERFACE" target="SYS_SSR"><data key="edge_relationship_id">R64_REL043</data><data key="edge_source_entity_id">APP_SSI_MBR_INTERFACE</data><data key="edge_relationship_type">posts_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2021 PIA says the interface posts Title II income/Title XVIII entitlement to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL044" source="APP_SSI_MBR_INTERFACE" target="APP_MSSICS"><data key="edge_relationship_id">R64_REL044</data><data key="edge_source_entity_id">APP_SSI_MBR_INTERFACE</data><data key="edge_relationship_type">posts_to</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">2021 PIA says the interface posts Title II income/Title XVIII entitlement to MSSICS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL045" source="APP_SSI_MEF_INTERFACE" target="SYS_MEF"><data key="edge_relationship_id">R64_REL045</data><data key="edge_source_entity_id">APP_SSI_MEF_INTERFACE</data><data key="edge_relationship_type">reads_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">2021 PIA says the interface inputs Master Earnings data.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL046" source="APP_SSI_MEF_INTERFACE" target="SYS_SSR"><data key="edge_relationship_id">R64_REL046</data><data key="edge_source_entity_id">APP_SSI_MEF_INTERFACE</data><data key="edge_relationship_type">posts_alerts_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2021 PIA says the interface builds MEF transactions used to post alerts to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL047" source="APP_SSI_OCSE_INTERFACE" target="EX_OCSE_SSI_WAGE_ALERT"><data key="edge_relationship_id">R64_REL047</data><data key="edge_source_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="edge_relationship_type">receives_wage_and_unemployment_data_via</data><data key="edge_target_entity_id">EX_OCSE_SSI_WAGE_ALERT</data><data key="edge_operational_context">2021 PIA identifies OCSE wage/unemployment input; current Atlas exchange product represents OCSE state wage alerts.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">The PIA does not explicitly name the specific exchange-product implementation.</data></edge><edge id="R64_REL048" source="APP_SSI_OCSE_INTERFACE" target="SYS_SSR"><data key="edge_relationship_id">R64_REL048</data><data key="edge_source_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="edge_relationship_type">posts_alerts_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2021 PIA says wage and unemployment transactions are used to post alerts to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL049" source="APP_SSI_OPM_INTERFACE" target="EX_T16_OPM"><data key="edge_relationship_id">R64_REL049</data><data key="edge_source_entity_id">APP_SSI_OPM_INTERFACE</data><data key="edge_relationship_type">functionally_corresponds_to_current_exchange</data><data key="edge_target_entity_id">EX_T16_OPM</data><data key="edge_operational_context">2021 PIA says OPM interface posts civil-service income to SSI records; current Title XVI/OPM exchange corroborates this functional relationship.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R64_REL050" source="APP_SSI_OPM_INTERFACE" target="SYS_SSR"><data key="edge_relationship_id">R64_REL050</data><data key="edge_source_entity_id">APP_SSI_OPM_INTERFACE</data><data key="edge_relationship_type">posts_income_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2021 PIA says civil-service income transactions post to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL051" source="APP_SSI_OPM_INTERFACE" target="APP_MSSICS"><data key="edge_relationship_id">R64_REL051</data><data key="edge_source_entity_id">APP_SSI_OPM_INTERFACE</data><data key="edge_relationship_type">posts_income_to</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">2021 PIA says civil-service income transactions post to MSSICS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL052" source="APP_SSI_RRB_INTERFACE" target="ORG_RRB"><data key="edge_relationship_id">R64_REL052</data><data key="edge_source_entity_id">APP_SSI_RRB_INTERFACE</data><data key="edge_relationship_type">receives_data_from</data><data key="edge_target_entity_id">ORG_RRB</data><data key="edge_operational_context">2021 PIA says RRB data enters this interface.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL053" source="APP_SSI_RRB_INTERFACE" target="SYS_SSR"><data key="edge_relationship_id">R64_REL053</data><data key="edge_source_entity_id">APP_SSI_RRB_INTERFACE</data><data key="edge_relationship_type">posts_income_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2021 PIA says RRB income transactions post to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL054" source="APP_SSI_RRB_INTERFACE" target="APP_MSSICS"><data key="edge_relationship_id">R64_REL054</data><data key="edge_source_entity_id">APP_SSI_RRB_INTERFACE</data><data key="edge_relationship_type">posts_income_to</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">2021 PIA says RRB income transactions post to MSSICS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL055" source="APP_SSI_VA_INTERFACE" target="EX_VA_CMA1008"><data key="edge_relationship_id">R64_REL055</data><data key="edge_source_entity_id">APP_SSI_VA_INTERFACE</data><data key="edge_relationship_type">functionally_corresponds_to_current_exchange</data><data key="edge_target_entity_id">EX_VA_CMA1008</data><data key="edge_operational_context">2021 PIA documents veterans income input; current VA Compensation and Pension Payment Match corroborates a continuing income exchange.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R64_REL056" source="APP_SSI_VA_INTERFACE" target="SYS_SSR"><data key="edge_relationship_id">R64_REL056</data><data key="edge_source_entity_id">APP_SSI_VA_INTERFACE</data><data key="edge_relationship_type">posts_income_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2021 PIA says veteran income transactions post to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL057" source="APP_SSI_VA_INTERFACE" target="APP_MSSICS"><data key="edge_relationship_id">R64_REL057</data><data key="edge_source_entity_id">APP_SSI_VA_INTERFACE</data><data key="edge_relationship_type">posts_income_to</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">2021 PIA says veteran income transactions post to MSSICS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL058" source="APP_SSI_SDX_SYSTEM" target="EX_SDX"><data key="edge_relationship_id">R64_REL058</data><data key="edge_source_entity_id">APP_SSI_SDX_SYSTEM</data><data key="edge_relationship_type">provides_state_exchange_product</data><data key="edge_target_entity_id">EX_SDX</data><data key="edge_operational_context">2021 PIA identifies SSI SDX as the system providing States eligibility, payment, and demographic data; existing Atlas SDX entity represents the exchange product.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Separates internal subsystem from outward exchange product.</data></edge><edge id="R64_REL059" source="APP_SSOARS" target="APP_APINET"><data key="edge_relationship_id">R64_REL059</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_APINET</data><data key="edge_operational_context">2020 SSOARS PIA names this subsystem/component.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current component status varies; see entity status.</data></edge><edge id="R64_REL060" source="APP_SSOARS" target="APP_APRS_SSOARS"><data key="edge_relationship_id">R64_REL060</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_APRS_SSOARS</data><data key="edge_operational_context">2020 SSOARS PIA names this subsystem/component.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current component status varies; see entity status.</data></edge><edge id="R64_REL061" source="APP_SSOARS" target="APP_SSOARS_FIS"><data key="edge_relationship_id">R64_REL061</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSOARS_FIS</data><data key="edge_operational_context">2020 SSOARS PIA names this subsystem/component.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current component status varies; see entity status.</data></edge><edge id="R64_REL062" source="APP_SSOARS" target="APP_SSOARS_SOA"><data key="edge_relationship_id">R64_REL062</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSOARS_SOA</data><data key="edge_operational_context">2020 SSOARS PIA names this subsystem/component.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current component status varies; see entity status.</data></edge><edge id="R64_REL063" source="APP_SSOARS" target="TECH_ORACLE_FED_FIN"><data key="edge_relationship_id">R64_REL063</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">based_on</data><data key="edge_target_entity_id">TECH_ORACLE_FED_FIN</data><data key="edge_operational_context">2020 PIA and FY2025 AFR both state SSOARS is based on Oracle Federal Financials.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL064" source="APP_SSASY" target="TECH_UNISON_PRISM"><data key="edge_relationship_id">R64_REL064</data><data key="edge_source_entity_id">APP_SSASY</data><data key="edge_relationship_type">uses_cots_product</data><data key="edge_target_entity_id">TECH_UNISON_PRISM</data><data key="edge_operational_context">2020 SSOARS PIA says SSASy is the contract-writing system utilizing Unison PRISM COTS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Current product version not established.</data></edge><edge id="R64_REL065" source="APP_APINET" target="APP_SSOARS"><data key="edge_relationship_id">R64_REL065</data><data key="edge_source_entity_id">APP_APINET</data><data key="edge_relationship_type">provides_status_access_for</data><data key="edge_target_entity_id">APP_SSOARS</data><data key="edge_operational_context">APINET provides intranet access to the status of administrative payment information processed through SSOARS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL066" source="APP_SSOARS" target="TECH_SOLARIS"><data key="edge_relationship_id">R64_REL066</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">migrated_from_operating_system</data><data key="edge_target_entity_id">TECH_SOLARIS</data><data key="edge_operational_context">FY2025 AFR says SSOARS hardware migration entailed a change from Solaris to Linux.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Scoped to SSOARS.</data></edge><edge id="R64_REL067" source="APP_SSOARS" target="TECH_LINUX"><data key="edge_relationship_id">R64_REL067</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">runs_on_operating_system</data><data key="edge_target_entity_id">TECH_LINUX</data><data key="edge_operational_context">FY2025 AFR says SSOARS migrated to new hardware using Linux during FY2025.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">No distribution/version identified.</data></edge><edge id="R64_REL068" source="APP_SSOARS" target="SVC_GINVOICING"><data key="edge_relationship_id">R64_REL068</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">integrates_with</data><data key="edge_target_entity_id">SVC_GINVOICING</data><data key="edge_operational_context">FY2025 AFR says SSA continues G-Invoicing releases/patches and prior AFR material describes SSOARS as fully interfacing as a requestor.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL069" source="APP_SSOARS" target="SVC_GOGOV"><data key="edge_relationship_id">R64_REL069</data><data key="edge_source_entity_id">APP_SSOARS</data><data key="edge_relationship_type">planned_real_time_interfaces_with</data><data key="edge_target_entity_id">SVC_GOGOV</data><data key="edge_operational_context">FY2025 AFR planned multiple real-time SSOARS interfaces with GO.gov during FY2026.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">GSA confirms GO.gov is live governmentwide; SSA-specific interface completion not independently confirmed.</data></edge><edge id="R64_REL070" source="PROJ_SSOARS_FMQSMO" target="APP_SSOARS"><data key="edge_relationship_id">R64_REL070</data><data key="edge_source_entity_id">PROJ_SSOARS_FMQSMO</data><data key="edge_relationship_type">planned_to_replace_or_modernize</data><data key="edge_target_entity_id">APP_SSOARS</data><data key="edge_operational_context">FY2025 AFR describes planned procurement of an FM QSMO core financial system with tentative FY2029 cutover.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data><data key="edge_notes">Procurement/cutover status after report remains unconfirmed.</data></edge><edge id="R64_REL071" source="ORG_SSA_OAG" target="SVC_UNISON_MARKETPLACE"><data key="edge_relationship_id">R64_REL071</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">uses_procurement_channel</data><data key="edge_target_entity_id">SVC_UNISON_MARKETPLACE</data><data key="edge_operational_context">Current OAG/OSDBU guidance says SSA uses Unison Marketplace reverse auctions to post requirements and select bids.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL072" source="ORG_SSA_OAG" target="SVC_GSA_EBUY"><data key="edge_relationship_id">R64_REL072</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">uses_procurement_channel</data><data key="edge_target_entity_id">SVC_GSA_EBUY</data><data key="edge_operational_context">Current OAG/OSDBU guidance says SSA often uses GSA eBuy for products/services under GSA schedules and technology contracts.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R64_REL073" source="APP_PERSON_INFO" target="DOM_PERSON_CUSTOMER_RECORD"><data key="edge_relationship_id">R64_REL073</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">implements_physical_primary_person_storage_for</data><data key="edge_target_entity_id">DOM_PERSON_CUSTOMER_RECORD</data><data key="edge_operational_context">SSA 2022 instructions call PI/PERSON a web-based primary storage application for number-holder person-centric information; FY2025 CJ calls PI the Customer Record database.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">This establishes physical PI/PERSON storage. It does not establish that DB_PERSON_STORE is the exact physical backing store.</data></edge><edge id="R65_REL001" source="APP_SSI_OCSE_INTERFACE" target="WORK_SSI_S2_DIARY"><data key="edge_relationship_id">R65_REL001</data><data key="edge_source_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="edge_relationship_type">produces_work_control</data><data key="edge_target_entity_id">WORK_SSI_S2_DIARY</data><data key="edge_operational_context">Quarterly OCSE wage information compared with SSR can generate the S2 discrepancy diary.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL002" source="WORK_SSI_S2_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R65_REL002</data><data key="edge_source_entity_id">WORK_SSI_S2_DIARY</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">POMS says the S2 alert is controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL003" source="WORK_SSI_S2_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL003</data><data key="edge_source_entity_id">WORK_SSI_S2_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says the S2 diary posts to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL004" source="WORK_SSI_S2_DIARY" target="UI_DSWM"><data key="edge_relationship_id">R65_REL004</data><data key="edge_source_entity_id">WORK_SSI_S2_DIARY</data><data key="edge_relationship_type">resolved_using</data><data key="edge_target_entity_id">UI_DSWM</data><data key="edge_operational_context">SSI Claims users clear S2 through State Wage Match Development (DSWM).</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL005" source="UI_DSWM" target="SYS_SSR"><data key="edge_relationship_id">R65_REL005</data><data key="edge_source_entity_id">UI_DSWM</data><data key="edge_relationship_type">builds_transaction_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">S2 clearance instructions require DSWM and build transaction SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL006" source="WORK_SSI_S2_DIARY" target="QRY_DEQY"><data key="edge_relationship_id">R65_REL006</data><data key="edge_source_entity_id">WORK_SSI_S2_DIARY</data><data key="edge_relationship_type">may_require_query</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">During the specified March-September period staff obtain DEQY when working S2 alerts.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL007" source="APP_SSI_OCSE_INTERFACE" target="WORK_SSI_S7_DIARY"><data key="edge_relationship_id">R65_REL007</data><data key="edge_source_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="edge_relationship_type">produces_work_control</data><data key="edge_target_entity_id">WORK_SSI_S7_DIARY</data><data key="edge_operational_context">Quarterly OCSE wage information compared with SSR can generate S7 overreported-wage diaries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL008" source="WORK_SSI_S7_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R65_REL008</data><data key="edge_source_entity_id">WORK_SSI_S7_DIARY</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">POMS says S7 is controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL009" source="WORK_SSI_S7_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL009</data><data key="edge_source_entity_id">WORK_SSI_S7_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says the S7 diary posts to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL010" source="WORK_SSI_S7_DIARY" target="UI_SSI_DORW"><data key="edge_relationship_id">R65_REL010</data><data key="edge_source_entity_id">WORK_SSI_S7_DIARY</data><data key="edge_relationship_type">resolved_using</data><data key="edge_target_entity_id">UI_SSI_DORW</data><data key="edge_operational_context">SSI Claims users clear S7 through the Over Reported Wage Development page.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL011" source="UI_SSI_DORW" target="SYS_SSR"><data key="edge_relationship_id">R65_REL011</data><data key="edge_source_entity_id">UI_SSI_DORW</data><data key="edge_relationship_type">builds_transaction_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">S7 clearance instructions require DORW and build transaction SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL012" source="WORK_SSI_S7_DIARY" target="QRY_DEQY"><data key="edge_relationship_id">R65_REL012</data><data key="edge_source_entity_id">WORK_SSI_S7_DIARY</data><data key="edge_relationship_type">may_require_query</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">POMS requires DEQY in the specified March-September period when working S7 alerts.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL013" source="APP_SSI_OCSE_INTERFACE" target="WORK_SSI_U5_DIARY"><data key="edge_relationship_id">R65_REL013</data><data key="edge_source_entity_id">APP_SSI_OCSE_INTERFACE</data><data key="edge_relationship_type">produces_work_control</data><data key="edge_target_entity_id">WORK_SSI_U5_DIARY</data><data key="edge_operational_context">Quarterly OCSE unemployment-compensation information compared with SSR can generate U5 diaries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL014" source="WORK_SSI_U5_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R65_REL014</data><data key="edge_source_entity_id">WORK_SSI_U5_DIARY</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">POMS says U5 alerts are controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL015" source="WORK_SSI_U5_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL015</data><data key="edge_source_entity_id">WORK_SSI_U5_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">U5 is an SSR diary generated from the OCSE unemployment-compensation comparison.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL016" source="WORK_SSI_U5_DIARY" target="UI_MSSICS_DUEM"><data key="edge_relationship_id">R65_REL016</data><data key="edge_source_entity_id">WORK_SSI_U5_DIARY</data><data key="edge_relationship_type">resolved_using</data><data key="edge_target_entity_id">UI_MSSICS_DUEM</data><data key="edge_operational_context">MSSICS U5 clearance uses the DUEM screen.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL017" source="WORK_SSI_U5_DIARY" target="UI_SSI_UDIA"><data key="edge_relationship_id">R65_REL017</data><data key="edge_source_entity_id">WORK_SSI_U5_DIARY</data><data key="edge_relationship_type">alternate_clearance_using</data><data key="edge_target_entity_id">UI_SSI_UDIA</data><data key="edge_operational_context">Non-MSSICS U5 clearance deletes the diary through UDIA/Direct SSR Update.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL018" source="DATA_CMS_LTC_MDS" target="WORK_SSI_D8_DIARY"><data key="edge_relationship_id">R65_REL018</data><data key="edge_source_entity_id">DATA_CMS_LTC_MDS</data><data key="edge_relationship_type">feeds_work_control</data><data key="edge_target_entity_id">WORK_SSI_D8_DIARY</data><data key="edge_operational_context">Monthly CMS Title XIX/Minimum Data Set information supplies facility-admission data used for D8 matching.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL019" source="APP_MSSICS" target="WORK_SSI_D8_DIARY"><data key="edge_relationship_id">R65_REL019</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">generates_work_control</data><data key="edge_target_entity_id">WORK_SSI_D8_DIARY</data><data key="edge_operational_context">POMS states MSSICS produces D8 alerts/diaries when match conditions are met.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL020" source="WORK_SSI_D8_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL020</data><data key="edge_source_entity_id">WORK_SSI_D8_DIARY</data><data key="edge_relationship_type">compares_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">D8 match logic checks current-pay and living-arrangement/payment conditions on SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL021" source="WORK_SSI_D8_DIARY" target="UI_MSSICS_DXIX"><data key="edge_relationship_id">R65_REL021</data><data key="edge_source_entity_id">WORK_SSI_D8_DIARY</data><data key="edge_relationship_type">resolved_using</data><data key="edge_target_entity_id">UI_MSSICS_DXIX</data><data key="edge_operational_context">MSSICS D8 clearance uses the TXIX Facility Interface Development (DXIX) screen.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL022" source="UI_MSSICS_DXIX" target="SYS_SSR"><data key="edge_relationship_id">R65_REL022</data><data key="edge_source_entity_id">UI_MSSICS_DXIX</data><data key="edge_relationship_type">builds_transaction_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS requires DXIX clearance and build transaction to SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL023" source="WORK_SSI_D8_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL023</data><data key="edge_source_entity_id">WORK_SSI_D8_DIARY</data><data key="edge_relationship_type">may_result_in_verified_update_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">After contacting facilities and completing development, staff make necessary address/living-arrangement changes and build/update SSR; no automatic CMS address write is inferred.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL024" source="APP_SSI_DHS_ICE_INTERFACE" target="WORK_SSI_3D_DIARY"><data key="edge_relationship_id">R65_REL024</data><data key="edge_source_entity_id">APP_SSI_DHS_ICE_INTERFACE</data><data key="edge_relationship_type">supports_work_control</data><data key="edge_target_entity_id">WORK_SSI_3D_DIARY</data><data key="edge_operational_context">The cataloged SSI/DHS immigration/deportation interface is consistent with the documented DHS removal workload; exact internal routing is not public.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R65_REL025" source="WORK_SSI_3D_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R65_REL025</data><data key="edge_source_entity_id">WORK_SSI_3D_DIARY</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">POMS says the 3D diary is controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL026" source="WORK_SSI_3D_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL026</data><data key="edge_source_entity_id">WORK_SSI_3D_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says 3D posts to the diary field on SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL027" source="WORK_SSI_3D_DIARY" target="UI_SSI_UDIA"><data key="edge_relationship_id">R65_REL027</data><data key="edge_source_entity_id">WORK_SSI_3D_DIARY</data><data key="edge_relationship_type">resolved_using</data><data key="edge_target_entity_id">UI_SSI_UDIA</data><data key="edge_operational_context">Current policy clears the 3D diary on UDIA and builds transaction SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL028" source="ORG_DHS" target="WORK_SSI_I8_DIARY"><data key="edge_relationship_id">R65_REL028</data><data key="edge_source_entity_id">ORG_DHS</data><data key="edge_relationship_type">provides_reentry_permit_data_for</data><data key="edge_target_entity_id">WORK_SSI_I8_DIARY</data><data key="edge_operational_context">DHS transmits reentry-permit information that drives the monthly I8 planned-departure workload.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL029" source="WORK_SSI_I8_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R65_REL029</data><data key="edge_source_entity_id">WORK_SSI_I8_DIARY</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">POMS says I8 is controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL030" source="WORK_SSI_I8_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL030</data><data key="edge_source_entity_id">WORK_SSI_I8_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says I8 posts to the SSR diary field.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL031" source="WORK_SSI_I8_DIARY" target="DB_MISF"><data key="edge_relationship_id">R65_REL031</data><data key="edge_source_entity_id">WORK_SSI_I8_DIARY</data><data key="edge_relationship_type">duplicates_alerts_to</data><data key="edge_target_entity_id">DB_MISF</data><data key="edge_operational_context">POMS says duplicate I8 alert records are sent to the Management Information Storage Facility.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL032" source="WORK_SSI_I8_DIARY" target="UI_SSI_UDIA"><data key="edge_relationship_id">R65_REL032</data><data key="edge_source_entity_id">WORK_SSI_I8_DIARY</data><data key="edge_relationship_type">resolved_using</data><data key="edge_target_entity_id">UI_SSI_UDIA</data><data key="edge_operational_context">Current policy clears I8 via UDIA and Build Transaction SSR.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL033" source="SYS_MEF" target="WORK_SSI_K6K7_DIARY"><data key="edge_relationship_id">R65_REL033</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">feeds_work_control</data><data key="edge_target_entity_id">WORK_SSI_K6K7_DIARY</data><data key="edge_operational_context">MEF annual W-2/Schedule SE earnings compared with SSR can create K6/K7 diaries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL034" source="EX_MEF_SSR_MATCH" target="WORK_SSI_K6K7_DIARY"><data key="edge_relationship_id">R65_REL034</data><data key="edge_source_entity_id">EX_MEF_SSR_MATCH</data><data key="edge_relationship_type">generates_work_control</data><data key="edge_target_entity_id">WORK_SSI_K6K7_DIARY</data><data key="edge_operational_context">The MEF/SSR earned-income enforcement interface generates K6/K7 discrepancy work.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL035" source="WORK_SSI_K6K7_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R65_REL035</data><data key="edge_source_entity_id">WORK_SSI_K6K7_DIARY</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">POMS says K6/K7 are controlled on PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL036" source="WORK_SSI_K6K7_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL036</data><data key="edge_source_entity_id">WORK_SSI_K6K7_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">K6/K7 are SSR diary controls associated with MEF discrepancy resolution.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL037" source="WORK_SSI_K6K7_DIARY" target="QRY_DEQY"><data key="edge_relationship_id">R65_REL037</data><data key="edge_source_entity_id">WORK_SSI_K6K7_DIARY</data><data key="edge_relationship_type">developed_using</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">Staff obtain DEQY for specific MEF data including wage amount and employer name/address.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL038" source="WORK_SSI_J3J5_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R65_REL038</data><data key="edge_source_entity_id">WORK_SSI_J3J5_DIARY</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">POMS says J3/J5 are controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL039" source="SYS_MEF" target="WORK_SSI_J3J5_DIARY"><data key="edge_relationship_id">R65_REL039</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">feeds_work_control</data><data key="edge_target_entity_id">WORK_SSI_J3J5_DIARY</data><data key="edge_operational_context">MEF annual earnings compared with SSR can create J3/J5 overreported-earnings diaries.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL040" source="EX_MEF_SSR_MATCH" target="WORK_SSI_J3J5_DIARY"><data key="edge_relationship_id">R65_REL040</data><data key="edge_source_entity_id">EX_MEF_SSR_MATCH</data><data key="edge_relationship_type">generates_work_control</data><data key="edge_target_entity_id">WORK_SSI_J3J5_DIARY</data><data key="edge_operational_context">The MEF/SSR interface generates J3/J5 discrepancy work.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL041" source="WORK_SSI_J3J5_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R65_REL041</data><data key="edge_source_entity_id">WORK_SSI_J3J5_DIARY</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">J3/J5 are SSR diary controls associated with MEF discrepancy resolution.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL042" source="WORK_SSI_J3J5_DIARY" target="QRY_DEQY"><data key="edge_relationship_id">R65_REL042</data><data key="edge_source_entity_id">WORK_SSI_J3J5_DIARY</data><data key="edge_relationship_type">developed_using</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">Staff obtain DEQY for specific MEF data when resolving J3/J5.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL043" source="PROC_SSI_EARNINGS_ALERT_RESOLUTION" target="WORK_SSI_S2_DIARY"><data key="edge_relationship_id">R65_REL043</data><data key="edge_source_entity_id">PROC_SSI_EARNINGS_ALERT_RESOLUTION</data><data key="edge_relationship_type">includes_workload_type</data><data key="edge_target_entity_id">WORK_SSI_S2_DIARY</data><data key="edge_operational_context">This diary is an SSI earnings discrepancy workload resolved through the broader earnings-alert process.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R65_REL044" source="PROC_SSI_EARNINGS_ALERT_RESOLUTION" target="WORK_SSI_S7_DIARY"><data key="edge_relationship_id">R65_REL044</data><data key="edge_source_entity_id">PROC_SSI_EARNINGS_ALERT_RESOLUTION</data><data key="edge_relationship_type">includes_workload_type</data><data key="edge_target_entity_id">WORK_SSI_S7_DIARY</data><data key="edge_operational_context">This diary is an SSI earnings discrepancy workload resolved through the broader earnings-alert process.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R65_REL045" source="PROC_SSI_EARNINGS_ALERT_RESOLUTION" target="WORK_SSI_K6K7_DIARY"><data key="edge_relationship_id">R65_REL045</data><data key="edge_source_entity_id">PROC_SSI_EARNINGS_ALERT_RESOLUTION</data><data key="edge_relationship_type">includes_workload_type</data><data key="edge_target_entity_id">WORK_SSI_K6K7_DIARY</data><data key="edge_operational_context">This diary is an SSI earnings discrepancy workload resolved through the broader earnings-alert process.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R65_REL046" source="PROC_SSI_EARNINGS_ALERT_RESOLUTION" target="WORK_SSI_J3J5_DIARY"><data key="edge_relationship_id">R65_REL046</data><data key="edge_source_entity_id">PROC_SSI_EARNINGS_ALERT_RESOLUTION</data><data key="edge_relationship_type">includes_workload_type</data><data key="edge_target_entity_id">WORK_SSI_J3J5_DIARY</data><data key="edge_operational_context">This diary is an SSI earnings discrepancy workload resolved through the broader earnings-alert process.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R65_REL047" source="PROC_SSI_EARNINGS_ALERT_RESOLUTION" target="SYS_SSR"><data key="edge_relationship_id">R65_REL047</data><data key="edge_source_entity_id">PROC_SSI_EARNINGS_ALERT_RESOLUTION</data><data key="edge_relationship_type">updates_after_development</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Resolved earnings discrepancies can result in corrected SSR income/payment information after required verification and development.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL048" source="PROC_SSI_EARNINGS_ALERT_RESOLUTION" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R65_REL048</data><data key="edge_source_entity_id">PROC_SSI_EARNINGS_ALERT_RESOLUTION</data><data key="edge_relationship_type">uses_work_control_store</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">Multiple documented SSI earnings alert types are controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">4</data></edge><edge id="R65_REL049" source="ORG_DHS" target="PROC_DHS_ALIEN_DEPARTURE_ADDR_DEV"><data key="edge_relationship_id">R65_REL049</data><data key="edge_source_entity_id">ORG_DHS</data><data key="edge_relationship_type">provides_reentry_permit_data_for</data><data key="edge_target_entity_id">PROC_DHS_ALIEN_DEPARTURE_ADDR_DEV</data><data key="edge_operational_context">DHS I-131/reentry-permit information can trigger Title II development when departure was not reported.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL050" source="PROC_DHS_ALIEN_DEPARTURE_ADDR_DEV" target="SYS_MBR"><data key="edge_relationship_id">R65_REL050</data><data key="edge_source_entity_id">PROC_DHS_ALIEN_DEPARTURE_ADDR_DEV</data><data key="edge_relationship_type">reviews</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PSC reviews MBR before initiating address development.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL051" source="PROC_DHS_ALIEN_DEPARTURE_ADDR_DEV" target="UI_POS_PEAD"><data key="edge_relationship_id">R65_REL051</data><data key="edge_source_entity_id">PROC_DHS_ALIEN_DEPARTURE_ADDR_DEV</data><data key="edge_relationship_type">processes_address_change_via</data><data key="edge_target_entity_id">UI_POS_PEAD</data><data key="edge_operational_context">Qualifying domestic-to-foreign Title II COA is processed through POS PEAD after development.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL052" source="UI_POS_PEAD" target="SYS_MBR"><data key="edge_relationship_id">R65_REL052</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS ties POS PEAD to Title II domestic-to-foreign address change processing.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL053" source="FORM_SSA157" target="PROC_SSN_SEX_DISCLOSURE"><data key="edge_relationship_id">R65_REL053</data><data key="edge_source_entity_id">FORM_SSA157</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_SSN_SEX_DISCLOSURE</data><data key="edge_operational_context">New data-exchange requests use SSA-157/DXRF to submit justification for sex-field verification disclosure.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL054" source="ORG_PPDX" target="PROC_SSN_SEX_DISCLOSURE"><data key="edge_relationship_id">R65_REL054</data><data key="edge_source_entity_id">ORG_PPDX</data><data key="edge_relationship_type">coordinates</data><data key="edge_target_entity_id">PROC_SSN_SEX_DISCLOSURE</data><data key="edge_operational_context">PPDX leads/facilitates the approval process with legal, privacy/disclosure and business sponsor review.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL055" source="PROC_SSN_SEX_DISCLOSURE" target="DATA_SSN_SEX_VERIFY_IND"><data key="edge_relationship_id">R65_REL055</data><data key="edge_source_entity_id">PROC_SSN_SEX_DISCLOSURE</data><data key="edge_relationship_type">authorizes_data_element</data><data key="edge_target_entity_id">DATA_SSN_SEX_VERIFY_IND</data><data key="edge_operational_context">Approved requests may receive the sex field verification indicator as an SSN-verification response element.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL056" source="APP_SSNVS" target="DATA_SSN_SEX_VERIFY_IND"><data key="edge_relationship_id">R65_REL056</data><data key="edge_source_entity_id">APP_SSNVS</data><data key="edge_relationship_type">does_not_return_by_default</data><data key="edge_target_entity_id">DATA_SSN_SEX_VERIFY_IND</data><data key="edge_operational_context">SSA removed the sex-field indicator from employer SSNVS in September 2011; current data-exchange disclosure requires separate justification.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL057" source="PROJ_MYSSA_ALL_COMMS" target="APP_MYSSA"><data key="edge_relationship_id">R65_REL057</data><data key="edge_source_entity_id">PROJ_MYSSA_ALL_COMMS</data><data key="edge_relationship_type">modernizes</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">FY2027 initiative calls for agency written communications and notices to be accessible online through my Social Security.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL058" source="APP_ECC" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R65_REL058</data><data key="edge_source_entity_id">APP_ECC</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">FY2027 budget describes Enterprise Contact Center/IVR as the cloud-based contact-center solution for automated and agent support and call routing on N8NN.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R65_REL059" source="PROJ_ENTERPRISE_CRM" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R65_REL059</data><data key="edge_source_entity_id">PROJ_ENTERPRISE_CRM</data><data key="edge_relationship_type">planned_integration_with</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">FY2027 budget states N8NN is planned to integrate with a customer relationship management system.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data></edge><edge id="R66_REL001" source="APP_PCS" target="DOM_TITLE2"><data key="edge_relationship_id">R66_REL001</data><data key="edge_source_entity_id">APP_PCS</data><data key="edge_relationship_type">supports_preclaim_screening_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">PCS was designed to help employees identify potential Social Security retirement/disability entitlement during pre-claim interviews.</data><data key="edge_observed_as_of">2020-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL002" source="APP_PCS" target="DOM_TITLE16"><data key="edge_relationship_id">R66_REL002</data><data key="edge_source_entity_id">APP_PCS</data><data key="edge_relationship_type">supports_preclaim_screening_for</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">PCS was designed to help employees identify potential SSI eligibility during pre-claim interviews.</data><data key="edge_observed_as_of">2020-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL003" source="APP_PCS" target="DOM_MEDICARE"><data key="edge_relationship_id">R66_REL003</data><data key="edge_source_entity_id">APP_PCS</data><data key="edge_relationship_type">supports_preclaim_screening_for</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">PCS was designed to help employees identify potential Medicare eligibility during pre-claim interviews.</data><data key="edge_observed_as_of">2020-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL004" source="APP_PCS" target="APP_CCE"><data key="edge_relationship_id">R66_REL004</data><data key="edge_source_entity_id">APP_PCS</data><data key="edge_relationship_type">functionality_integrated_into</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">SSA stopped PCS development in September 2020 and began integrating PCS programming and functionality into Consolidated Claims Experience.</data><data key="edge_observed_as_of">2020-09</data><data key="edge_confidence">5</data><data key="edge_notes">This relationship is source-explicit and does not establish that PCS and CCE were otherwise the same application.</data></edge><edge id="R66_REL005" source="PROJ_CCS_2019" target="DOM_TITLE2"><data key="edge_relationship_id">R66_REL005</data><data key="edge_source_entity_id">PROJ_CCS_2019</data><data key="edge_relationship_type">planned_unified_claims_processing_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">FY2020 budget planned CCS as a single place to work RSDI claims.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL006" source="PROJ_CCS_2019" target="DOM_TITLE16"><data key="edge_relationship_id">R66_REL006</data><data key="edge_source_entity_id">PROJ_CCS_2019</data><data key="edge_relationship_type">planned_unified_claims_processing_for</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">FY2020 budget planned CCS as a single place to work SSI claims.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL007" source="PROJ_CCS_2019" target="DOM_MEDICARE"><data key="edge_relationship_id">R66_REL007</data><data key="edge_source_entity_id">PROJ_CCS_2019</data><data key="edge_relationship_type">planned_unified_claims_processing_for</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">FY2020 budget planned CCS as a single place to work Medicare claims.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL008" source="DB_CCS_PLANNED" target="PROJ_CCS_2019"><data key="edge_relationship_id">R66_REL008</data><data key="edge_source_entity_id">DB_CCS_PLANNED</data><data key="edge_relationship_type">planned_component_of</data><data key="edge_target_entity_id">PROJ_CCS_2019</data><data key="edge_operational_context">SSA planned to establish a new database for the Consolidated Claims System.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL009" source="APP_PCS" target="PROJ_CCS_2019"><data key="edge_relationship_id">R66_REL009</data><data key="edge_source_entity_id">APP_PCS</data><data key="edge_relationship_type">planned_information_source_for</data><data key="edge_target_entity_id">PROJ_CCS_2019</data><data key="edge_operational_context">SSA planned for CCS to use information collected in PCS to reduce redundant/manual data collection.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes">Historical planned relationship; PCS was later integrated into CCE.</data></edge><edge id="R66_REL010" source="PROJ_PE_MODERNIZATION" target="DB_MCS_PENDING"><data key="edge_relationship_id">R66_REL010</data><data key="edge_source_entity_id">PROJ_PE_MODERNIZATION</data><data key="edge_relationship_type">targeted_redundancy_reduction_across</data><data key="edge_target_entity_id">DB_MCS_PENDING</data><data key="edge_operational_context">PE modernization planned to eliminate redundancy involving the MCS Pending File.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL011" source="PROJ_PE_MODERNIZATION" target="DB_T2_SHARED_LEGACY"><data key="edge_relationship_id">R66_REL011</data><data key="edge_source_entity_id">PROJ_PE_MODERNIZATION</data><data key="edge_relationship_type">targeted_redundancy_reduction_across</data><data key="edge_target_entity_id">DB_T2_SHARED_LEGACY</data><data key="edge_operational_context">PE modernization planned to eliminate redundancy involving the Title II Shared Database.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL012" source="PROJ_PE_MODERNIZATION" target="SYS_MBR"><data key="edge_relationship_id">R66_REL012</data><data key="edge_source_entity_id">PROJ_PE_MODERNIZATION</data><data key="edge_relationship_type">targeted_redundancy_reduction_across</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PE modernization planned to eliminate redundancy involving MBR along with other Title II stores.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL013" source="DB_MCS_PENDING" target="TECH_IDMS_DBMS"><data key="edge_relationship_id">R66_REL013</data><data key="edge_source_entity_id">DB_MCS_PENDING</data><data key="edge_relationship_type">implemented_with</data><data key="edge_target_entity_id">TECH_IDMS_DBMS</data><data key="edge_operational_context">FY2020 budget explicitly describes the MCS Pending File as dependent on an Integrated Database Management System database structure.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes">IDMS here is database technology, not the Integrated Disability Management System application.</data></edge><edge id="R66_REL014" source="DB_MCS_PENDING" target="APP_MCS"><data key="edge_relationship_id">R66_REL014</data><data key="edge_source_entity_id">DB_MCS_PENDING</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">The legacy object is explicitly named the MCS Pending File and is discussed as part of MCS-related Title II post-entitlement modernization.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">4</data><data key="edge_notes">The source establishes association but does not expose record layout or interface mechanics.</data></edge><edge id="R66_REL015" source="PROJ_COMP_SERVICES" target="TECH_COBOL"><data key="edge_relationship_id">R66_REL015</data><data key="edge_source_entity_id">PROJ_COMP_SERVICES</data><data key="edge_relationship_type">modernizes_from</data><data key="edge_target_entity_id">TECH_COBOL</data><data key="edge_operational_context">SSA planned to convert decades-old Title II computational utilities from COBOL.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL016" source="PROJ_COMP_SERVICES" target="TECH_JAVA"><data key="edge_relationship_id">R66_REL016</data><data key="edge_source_entity_id">PROJ_COMP_SERVICES</data><data key="edge_relationship_type">targets_language</data><data key="edge_target_entity_id">TECH_JAVA</data><data key="edge_operational_context">SSA planned to implement modernized Title II computational services written in Java.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL017" source="PROJ_COMP_SERVICES" target="SVC_GEN_INSURED"><data key="edge_relationship_id">R66_REL017</data><data key="edge_source_entity_id">PROJ_COMP_SERVICES</data><data key="edge_relationship_type">modernizes</data><data key="edge_target_entity_id">SVC_GEN_INSURED</data><data key="edge_operational_context">General Insured Status Utility was a named Computational Services conversion target.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL018" source="PROJ_COMP_SERVICES" target="SVC_GRUMPI"><data key="edge_relationship_id">R66_REL018</data><data key="edge_source_entity_id">PROJ_COMP_SERVICES</data><data key="edge_relationship_type">modernizes</data><data key="edge_target_entity_id">SVC_GRUMPI</data><data key="edge_operational_context">GRUMPI was a named Computational Services conversion target.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL019" source="PROJ_COMP_SERVICES" target="SVC_GRATES"><data key="edge_relationship_id">R66_REL019</data><data key="edge_source_entity_id">PROJ_COMP_SERVICES</data><data key="edge_relationship_type">modernizes</data><data key="edge_target_entity_id">SVC_GRATES</data><data key="edge_operational_context">GRATES was a named Computational Services conversion target.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL020" source="PROJ_COMP_SERVICES" target="SVC_EE_UTILITY"><data key="edge_relationship_id">R66_REL020</data><data key="edge_source_entity_id">PROJ_COMP_SERVICES</data><data key="edge_relationship_type">modernizes</data><data key="edge_target_entity_id">SVC_EE_UTILITY</data><data key="edge_operational_context">Entitlement/Eligibility Utility was a named Computational Services conversion target.</data><data key="edge_observed_as_of">2020</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL021" source="SVC_GEN_INSURED" target="DOM_TITLE2"><data key="edge_relationship_id">R66_REL021</data><data key="edge_source_entity_id">SVC_GEN_INSURED</data><data key="edge_relationship_type">supports_title2_computation_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">SSA identifies the utility within the Title II computational-services modernization effort.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL022" source="SVC_GRUMPI" target="DOM_TITLE2"><data key="edge_relationship_id">R66_REL022</data><data key="edge_source_entity_id">SVC_GRUMPI</data><data key="edge_relationship_type">supports_title2_computation_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">SSA identifies GRUMPI within the Title II computational-services modernization effort.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL023" source="SVC_GRATES" target="DOM_TITLE2"><data key="edge_relationship_id">R66_REL023</data><data key="edge_source_entity_id">SVC_GRATES</data><data key="edge_relationship_type">supports_title2_computation_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">SSA identifies GRATES within the Title II computational-services modernization effort.</data><data key="edge_observed_as_of">2019</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL024" source="SVC_EE_UTILITY" target="DOM_TITLE2"><data key="edge_relationship_id">R66_REL024</data><data key="edge_source_entity_id">SVC_EE_UTILITY</data><data key="edge_relationship_type">supports_title2_computation_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">SSA identifies EE within the Title II computational-services modernization effort.</data><data key="edge_observed_as_of">2020</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL025" source="ORG_SSA_ORES" target="PROC_MGD"><data key="edge_relationship_id">R66_REL025</data><data key="edge_source_entity_id">ORG_SSA_ORES</data><data key="edge_relationship_type">develops</data><data key="edge_target_entity_id">PROC_MGD</data><data key="edge_operational_context">ORES is developing the MGD methodology for annual employment and earnings statistical production.</data><data key="edge_observed_as_of">2024-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL026" source="DATA_TAX_GEO_ADDR" target="PROC_MGD"><data key="edge_relationship_id">R66_REL026</data><data key="edge_source_entity_id">DATA_TAX_GEO_ADDR</data><data key="edge_relationship_type">provides_geographic_input_to</data><data key="edge_target_entity_id">PROC_MGD</data><data key="edge_operational_context">Address information is the only information extracted from worker tax records into the MGD geographic component for state/county assignment.</data><data key="edge_observed_as_of">2024-12</data><data key="edge_confidence">5</data><data key="edge_notes">Statistical input only; no program-master address update is established.</data></edge><edge id="R66_REL027" source="SYS_NUMIDENT" target="PROC_MGD"><data key="edge_relationship_id">R66_REL027</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">validates_ssns_for</data><data key="edge_target_entity_id">PROC_MGD</data><data key="edge_operational_context">MGD treats an SSN as valid when it is present in Numident; invalid-SSN records are omitted from analysis.</data><data key="edge_observed_as_of">2024-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL028" source="SYS_NUMIDENT" target="PROC_MGD"><data key="edge_relationship_id">R66_REL028</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">provides_demographic_attributes_to</data><data key="edge_target_entity_id">PROC_MGD</data><data key="edge_operational_context">Numident provides the identity/demographic basis needed for MGD year-of-birth and sex assignment.</data><data key="edge_observed_as_of">2024-12</data><data key="edge_confidence">5</data><data key="edge_notes">Source establishes Numident role; no writeback to Numident is implied.</data></edge><edge id="R66_REL029" source="PROC_MGD" target="DATA_MGD"><data key="edge_relationship_id">R66_REL029</data><data key="edge_source_entity_id">PROC_MGD</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_MGD</data><data key="edge_operational_context">ORES used the MGD process to assemble annual MGD files for tax years 2014 through 2021.</data><data key="edge_observed_as_of">2024-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL030" source="DATA_MGD" target="REPORT_EARN_EMP_SERIES"><data key="edge_relationship_id">R66_REL030</data><data key="edge_source_entity_id">DATA_MGD</data><data key="edge_relationship_type">developed_as_future_methodology_input_for</data><data key="edge_target_entity_id">REPORT_EARN_EMP_SERIES</data><data key="edge_operational_context">ORES is developing MGD to support estimates for the Earnings and Employment annual publication series.</data><data key="edge_observed_as_of">2024-12</data><data key="edge_confidence">5</data><data key="edge_notes">The December 2024 source says methodology development is ongoing; current edition methodology remains separately documented.</data></edge><edge id="R66_REL031" source="DATA_MGD" target="REPORT_STAT_SUPP_SERIES"><data key="edge_relationship_id">R66_REL031</data><data key="edge_source_entity_id">DATA_MGD</data><data key="edge_relationship_type">developed_as_future_methodology_input_for</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_SERIES</data><data key="edge_operational_context">ORES is developing MGD to support estimates for the Annual Statistical Supplement publication series.</data><data key="edge_observed_as_of">2024-12</data><data key="edge_confidence">5</data><data key="edge_notes">Does not assert that MGD produced the 2026 edition.</data></edge><edge id="R66_REL032" source="REPORT_EARN_EMP_2023" target="REPORT_EARN_EMP_SERIES"><data key="edge_relationship_id">R66_REL032</data><data key="edge_source_entity_id">REPORT_EARN_EMP_2023</data><data key="edge_relationship_type">part_of_series</data><data key="edge_target_entity_id">REPORT_EARN_EMP_SERIES</data><data key="edge_operational_context">The 2023 report is the current published edition of the recurring Earnings and Employment series.</data><data key="edge_observed_as_of">2026-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL033" source="REPORT_STAT_SUPP_2026" target="REPORT_STAT_SUPP_SERIES"><data key="edge_relationship_id">R66_REL033</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">part_of_series</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_SERIES</data><data key="edge_operational_context">The current 2026 Annual Statistical Supplement is an edition of the recurring publication series.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL034" source="DATA_CWHS" target="REPORT_EARN_EMP_2023"><data key="edge_relationship_id">R66_REL034</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">current_sample_source_for</data><data key="edge_target_entity_id">REPORT_EARN_EMP_2023</data><data key="edge_operational_context">Current published tables identify SSA Continuous Work History Sample, 1-percent sample, as their source.</data><data key="edge_observed_as_of">2026-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R66_REL035" source="DATA_TAX_GEO_ADDR" target="REPORT_EARN_EMP_2023"><data key="edge_relationship_id">R66_REL035</data><data key="edge_source_entity_id">DATA_TAX_GEO_ADDR</data><data key="edge_relationship_type">provides_geographic_assignment_to</data><data key="edge_target_entity_id">REPORT_EARN_EMP_2023</data><data key="edge_operational_context">Current methodology bases state/county designations on employee residence shown on W-2 wage reports and addresses matched to self-employment earnings reports.</data><data key="edge_observed_as_of">2026-01</data><data key="edge_confidence">5</data><data key="edge_notes">Statistical publication geography; not an SSA program address update.</data></edge><edge id="R66_REL036" source="ORG_SSA_ORES" target="REPORT_EARN_EMP_SERIES"><data key="edge_relationship_id">R66_REL036</data><data key="edge_source_entity_id">ORG_SSA_ORES</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">REPORT_EARN_EMP_SERIES</data><data key="edge_operational_context">ORES produces the recurring Earnings and Employment statistical publication series.</data><data key="edge_observed_as_of">2026-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL001" source="UI_CWP" target="APP_EDCS"><data key="edge_relationship_id">R67_REL001</data><data key="edge_source_entity_id">UI_CWP</data><data key="edge_relationship_type">page_within</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Current POMS directs technicians to the Consolidated Wage Page in EDCS.</data><data key="edge_observed_as_of">2026-09-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL002" source="APP_ITOPSS" target="UI_CWP"><data key="edge_relationship_id">R67_REL002</data><data key="edge_source_entity_id">APP_ITOPSS</data><data key="edge_relationship_type">provides_wage_data_to</data><data key="edge_target_entity_id">UI_CWP</data><data key="edge_operational_context">The 2021 CWP release included iTOPSS pay-stub wage data supplied through Ticket to Work operations.</data><data key="edge_observed_as_of">2021-12-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL003" source="UI_CWP" target="PROJ_WORK_CDR"><data key="edge_relationship_id">R67_REL003</data><data key="edge_source_entity_id">UI_CWP</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">PROJ_WORK_CDR</data><data key="edge_operational_context">SSA described the 2021 CWP release as part of the new Work CDR product.</data><data key="edge_observed_as_of">2021-12-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL004" source="UI_CWP" target="APP_EWORK"><data key="edge_relationship_id">R67_REL004</data><data key="edge_source_entity_id">UI_CWP</data><data key="edge_relationship_type">provides_wage_evidence_for</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">Work-CDR instructions use CWP/iTOPSS wage information as evidence and direct technicians to enter applicable earnings in eWork.</data><data key="edge_observed_as_of">2026-07-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL005" source="ORG_BLS" target="ORG_DOL"><data key="edge_relationship_id">R67_REL005</data><data key="edge_source_entity_id">ORG_BLS</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">ORG_DOL</data><data key="edge_operational_context">SSA identifies BLS as the Department of Labor bureau partnering on occupational-data collection.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL006" source="ORG_BLS" target="DATA_ORS"><data key="edge_relationship_id">R67_REL006</data><data key="edge_source_entity_id">ORG_BLS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_ORS</data><data key="edge_operational_context">BLS develops, collects and publishes Occupational Requirements Survey data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL007" source="DATA_ORS" target="SYS_OIS"><data key="edge_relationship_id">R67_REL007</data><data key="edge_source_entity_id">DATA_ORS</data><data key="edge_relationship_type">primary_data_source_for</data><data key="edge_target_entity_id">SYS_OIS</data><data key="edge_operational_context">SSA states ORS data will be the OIS primary source for work requirements.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL008" source="APP_VIT" target="SYS_OIS"><data key="edge_relationship_id">R67_REL008</data><data key="edge_source_entity_id">APP_VIT</data><data key="edge_relationship_type">houses</data><data key="edge_target_entity_id">SYS_OIS</data><data key="edge_operational_context">SSA states OIS will be housed through the Vocational Information Tool.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL009" source="APP_VIT" target="SYS_OIS"><data key="edge_relationship_id">R67_REL009</data><data key="edge_source_entity_id">APP_VIT</data><data key="edge_relationship_type">operationalizes</data><data key="edge_target_entity_id">SYS_OIS</data><data key="edge_operational_context">SSA states OIS will be accessed and operationalized through VIT.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL010" source="APP_VIT" target="DATA_ORS"><data key="edge_relationship_id">R67_REL010</data><data key="edge_source_entity_id">APP_VIT</data><data key="edge_relationship_type">combines_data_from</data><data key="edge_target_entity_id">DATA_ORS</data><data key="edge_operational_context">VIT is the web platform that will combine ORS with other reliable occupational-information sources.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL011" source="SYS_OIS" target="DATA_DOT"><data key="edge_relationship_id">R67_REL011</data><data key="edge_source_entity_id">SYS_OIS</data><data key="edge_relationship_type">planned_replacement_for</data><data key="edge_target_entity_id">DATA_DOT</data><data key="edge_operational_context">SSA is developing OIS to replace DOT as its primary occupational-information source for disability adjudication.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL012" source="ORG_DOL" target="DATA_DOT"><data key="edge_relationship_id">R67_REL012</data><data key="edge_source_entity_id">ORG_DOL</data><data key="edge_relationship_type">developed</data><data key="edge_target_entity_id">DATA_DOT</data><data key="edge_operational_context">SSA states DOL developed the Dictionary of Occupational Titles.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL013" source="DATA_ORS" target="STD_SOC"><data key="edge_relationship_id">R67_REL013</data><data key="edge_source_entity_id">DATA_ORS</data><data key="edge_relationship_type">classified_using</data><data key="edge_target_entity_id">STD_SOC</data><data key="edge_operational_context">SSA states BLS classifies ORS using the Standard Occupational Classification system; Wave 2 uses 2018 SOC.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL014" source="DATA_DOT" target="PROC_DISABILITY_OCC_EVAL"><data key="edge_relationship_id">R67_REL014</data><data key="edge_source_entity_id">DATA_DOT</data><data key="edge_relationship_type">legacy_primary_source_for</data><data key="edge_target_entity_id">PROC_DISABILITY_OCC_EVAL</data><data key="edge_operational_context">SSA identifies DOT as the main current occupational source while OIS is being developed.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL015" source="SYS_OIS" target="PROC_DISABILITY_OCC_EVAL"><data key="edge_relationship_id">R67_REL015</data><data key="edge_source_entity_id">SYS_OIS</data><data key="edge_relationship_type">planned_primary_source_for</data><data key="edge_target_entity_id">PROC_DISABILITY_OCC_EVAL</data><data key="edge_operational_context">OIS is intended to provide current occupational information for determining past-work and other-work capability.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL016" source="EX_SSI_IRS_1099" target="DATA_SSI_IRS_NONWAGE"><data key="edge_relationship_id">R67_REL016</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_SSI_IRS_NONWAGE</data><data key="edge_operational_context">SSI IRS match receives 1099 and similar non-wage financial-transaction information.</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL017" source="DATA_SSI_IRS_NONWAGE" target="DB_SSI_IRS_INTERFACE"><data key="edge_relationship_id">R67_REL017</data><data key="edge_source_entity_id">DATA_SSI_IRS_NONWAGE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_operational_context">POMS says IRS data are posted to a database used for SSI alerts; the database historically exposed the most recent two years.</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL018" source="DB_SSI_IRS_INTERFACE" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R67_REL018</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">retrieved_via</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">Technicians can retrieve IRS alert data overnight through MI Central.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL019" source="DB_SSI_IRS_INTERFACE" target="APP_SSTNG"><data key="edge_relationship_id">R67_REL019</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">retrieved_via</data><data key="edge_target_entity_id">APP_SSTNG</data><data key="edge_operational_context">POMS says the same IRS data may be retrieved immediately through SSTNG.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL020" source="DB_SSI_IRS_INTERFACE" target="UI_MSSICS_DIRS"><data key="edge_relationship_id">R67_REL020</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">supports_development_in</data><data key="edge_target_entity_id">UI_MSSICS_DIRS</data><data key="edge_operational_context">POMS cross-references MSSICS IRS Interface Development (DIRS) for development of SSI IRS information.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL021" source="DB_SSI_IRS_INTERFACE" target="WORK_SSI_IRS_5B_DIARY"><data key="edge_relationship_id">R67_REL021</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">supports_work_control</data><data key="edge_target_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_operational_context">Controlled IRS alerts correspond to a 5B diary posted to SSR and alert data in the IRS database.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL022" source="PROC_SSI_IRS_PENSION_MATCH" target="DB_SSI_IRS_INTERFACE"><data key="edge_relationship_id">R67_REL022</data><data key="edge_source_entity_id">PROC_SSI_IRS_PENSION_MATCH</data><data key="edge_relationship_type">uses_interface_database</data><data key="edge_target_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_operational_context">Current SSI workload policy describes IRS 5B and pension 5H alert data as available on an interface database.</data><data key="edge_observed_as_of">2026-07</data><data key="edge_confidence">5</data><data key="edge_notes">The public source establishes a shared interface-database presentation but does not disclose physical schema or whether 5B and 5H use identical storage tables.</data></edge><edge id="R67_REL023" source="ORG_IRS" target="FORM_IRS_3857"><data key="edge_relationship_id">R67_REL023</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">sends_request_via</data><data key="edge_target_entity_id">FORM_IRS_3857</data><data key="edge_operational_context">Form 3857 is the IRS formal request for SSA assistance locating and identifying taxpayer SSNs.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL024" source="FORM_IRS_3857" target="PROC_IRS_3857_RESOLUTION"><data key="edge_relationship_id">R67_REL024</data><data key="edge_source_entity_id">FORM_IRS_3857</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_operational_context">SSA uses the form as both a formal request and a scrambled-earnings alert requiring resolution.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL025" source="PROC_IRS_3857_RESOLUTION" target="SYS_NUMIDENT"><data key="edge_relationship_id">R67_REL025</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current Form 3857 instructions require a Numident query during identity development.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL026" source="PROC_IRS_3857_RESOLUTION" target="QRY_ALPHADENT"><data key="edge_relationship_id">R67_REL026</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">QRY_ALPHADENT</data><data key="edge_operational_context">Current Form 3857 instructions require the alphadent file among master-file queries.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL027" source="PROC_IRS_3857_RESOLUTION" target="QRY_DEQY"><data key="edge_relationship_id">R67_REL027</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">Current Form 3857 instructions require DEQY among master-file queries.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL028" source="PROC_IRS_3857_RESOLUTION" target="SVC_ERQY"><data key="edge_relationship_id">R67_REL028</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SVC_ERQY</data><data key="edge_operational_context">Current Form 3857 instructions use ERQY for employer/earnings development.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL029" source="PROC_IRS_3857_RESOLUTION" target="SYS_MBR"><data key="edge_relationship_id">R67_REL029</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current Form 3857 instructions require MBR among master-file queries.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL030" source="PROC_IRS_3857_RESOLUTION" target="APP_ICOR"><data key="edge_relationship_id">R67_REL030</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ICOR</data><data key="edge_operational_context">Current Form 3857 instructions require checking/annotating Item Correction during case development.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL031" source="PROC_IRS_3857_RESOLUTION" target="DB_ESF"><data key="edge_relationship_id">R67_REL031</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">Current Form 3857 instructions require checking the earnings suspense file and historical files.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL032" source="PROC_IRS_3857_RESOLUTION" target="FORM_SSA_L2001"><data key="edge_relationship_id">R67_REL032</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">uses_for_address_development</data><data key="edge_target_entity_id">FORM_SSA_L2001</data><data key="edge_operational_context">When current postal addresses are needed, technicians send SSA-L2001 to the Postal Service.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL033" source="PROC_IRS_3857_RESOLUTION" target="SYS_MEF"><data key="edge_relationship_id">R67_REL033</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">may_result_in_adjustment_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">When evidence resolves the case, SSA makes necessary adjustments to earnings records supported by taxpayer/employer evidence.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes">MEF is the Atlas master earnings record endpoint; exact transaction mechanism for each adjustment is not inferred here.</data></edge><edge id="R67_REL034" source="PROC_IRS_3857_RESOLUTION" target="SYS_NUMIDENT"><data key="edge_relationship_id">R67_REL034</data><data key="edge_source_entity_id">PROC_IRS_3857_RESOLUTION</data><data key="edge_relationship_type">may_remove_incorrect_cross_references_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS explicitly directs removal of incorrect Numident cross-references when supported by evidence.</data><data key="edge_observed_as_of">2025-06-13</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL035" source="PROJ_SSI_UNDERPAY_UI" target="DOM_TITLE16"><data key="edge_relationship_id">R67_REL035</data><data key="edge_source_entity_id">PROJ_SSI_UNDERPAY_UI</data><data key="edge_relationship_type">supports_controls_for</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">The planned interface is intended to implement systems controls for SSI underpayment processing and two-PIN review.</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL036" source="PROC_RETAP" target="ALERT_RETAP_STUDENT_AGE18"><data key="edge_relationship_id">R67_REL036</data><data key="edge_source_entity_id">PROC_RETAP</data><data key="edge_relationship_type">planned_to_produce</data><data key="edge_target_entity_id">ALERT_RETAP_STUDENT_AGE18</data><data key="edge_operational_context">SSA says the chosen solution is Regular Transcript Attainment and Selection Pass Alerts.</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL037" source="ALERT_RETAP_STUDENT_AGE18" target="APP_T2R"><data key="edge_relationship_id">R67_REL037</data><data key="edge_source_entity_id">ALERT_RETAP_STUDENT_AGE18</data><data key="edge_relationship_type">planned_in</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">The open recommendation calls for the Title II Redesign System to generate the age-18 student alert; SSA chose RETAP/selection-pass alerts as the solution.</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">4</data><data key="edge_notes">Atlas links the alert to the existing T2R processing entity; the public report does not disclose the internal component boundary.</data></edge><edge id="R67_REL038" source="PROJ_ENHANCED_MEDICAL_ACQ" target="APP_NCPS"><data key="edge_relationship_id">R67_REL038</data><data key="edge_source_entity_id">PROJ_ENHANCED_MEDICAL_ACQ</data><data key="edge_relationship_type">enhances</data><data key="edge_target_entity_id">APP_NCPS</data><data key="edge_operational_context">FY2027 budget says the initiative updates NCPS features used by State DDSs for forms, medical-evidence requests and case processing.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R67_REL039" source="PROJ_IMAGEN_EXPANSION" target="APP_IMAGEN"><data key="edge_relationship_id">R67_REL039</data><data key="edge_source_entity_id">PROJ_IMAGEN_EXPANSION</data><data key="edge_relationship_type">expands</data><data key="edge_target_entity_id">APP_IMAGEN</data><data key="edge_operational_context">FY2027 budget explicitly calls for increased IMAGEN adoption, expansion and integrations.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL001" source="DB_DIGITAL_IDENTITY_FILE" target="DATA_DIGID_POSTAL_ADDRESS"><data key="edge_relationship_id">R68_REL001</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_DIGID_POSTAL_ADDRESS</data><data key="edge_operational_context">Current SORN 60-0373 lists postal addresses among the Digital Identity File record categories.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes">Digital-identity storage does not establish a program-master address update.</data></edge><edge id="R68_REL002" source="DB_DIGITAL_IDENTITY_FILE" target="DATA_DIGID_W2SE_ADDRESS"><data key="edge_relationship_id">R68_REL002</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_DIGID_W2SE_ADDRESS</data><data key="edge_operational_context">Current SORN 60-0373 lists addresses from W-2 and Schedule-SE forms among maintained record categories.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes">Precise source provenance and downstream update behavior are not stated.</data></edge><edge id="R68_REL003" source="APP_AFES" target="DB_DIGITAL_IDENTITY_FILE"><data key="edge_relationship_id">R68_REL003</data><data key="edge_source_entity_id">APP_AFES</data><data key="edge_relationship_type">historically_ingested_or_used</data><data key="edge_target_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_operational_context">The 2018 AFES PIA identified SORN 60-0373, then titled Central Repository of Electronic Authentication Data Master File, as a primary record source.</data><data key="edge_observed_as_of">2018-04-18</data><data key="edge_confidence">4</data><data key="edge_notes">The record system was materially modified/retitled by 2025; this edge is time-scoped to the 2018 AFES architecture.</data></edge><edge id="R68_REL004" source="APP_AFES" target="DB_PINFILE"><data key="edge_relationship_id">R68_REL004</data><data key="edge_source_entity_id">APP_AFES</data><data key="edge_relationship_type">historically_ingested_or_used</data><data key="edge_target_entity_id">DB_PINFILE</data><data key="edge_operational_context">The 2018 AFES PIA identified Personal Identification Number File 60-0214 as a primary record source.</data><data key="edge_observed_as_of">2018-04-18</data><data key="edge_confidence">4</data><data key="edge_notes">Historical 2018 AFES dependency; current AFES/PINFile implementation not inferred.</data></edge><edge id="R68_REL005" source="APP_RCS" target="CTRL_ESERVICES_BLOCK"><data key="edge_relationship_id">R68_REL005</data><data key="edge_source_entity_id">APP_RCS</data><data key="edge_relationship_type">manages</data><data key="edge_target_entity_id">CTRL_ESERVICES_BLOCK</data><data key="edge_operational_context">2021 instructions direct standard non-elevated eServices block cases to existing RCS block/unblock policy.</data><data key="edge_observed_as_of">2021-05-05</data><data key="edge_confidence">4</data><data key="edge_notes">Current electronic blocking remains documented, but current RCS product identity is not independently revalidated.</data></edge><edge id="R68_REL006" source="CTRL_ESERVICES_BLOCK" target="APP_MYSSA"><data key="edge_relationship_id">R68_REL006</data><data key="edge_source_entity_id">CTRL_ESERVICES_BLOCK</data><data key="edge_relationship_type">blocks_electronic_access_to</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Current SSA electronic-services text states a customer can block all electronic access to personal information; my Social Security is a principal online personal-information channel.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Source describes the block generically rather than naming mySSA in the same sentence.</data></edge><edge id="R68_REL007" source="AUTH_SAP" target="APP_MYSSA"><data key="edge_relationship_id">R68_REL007</data><data key="edge_source_entity_id">AUTH_SAP</data><data key="edge_relationship_type">available_to_account_holders_of</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA introduced SAP for my Social Security accountholders beginning August 2025.</data><data key="edge_observed_as_of">2025-08-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL008" source="AUTH_SAP" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R68_REL008</data><data key="edge_source_entity_id">AUTH_SAP</data><data key="edge_relationship_type">authenticates_callers_to</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA says callers can use SAP to authenticate identity when calling the National 800 Number.</data><data key="edge_observed_as_of">2025-08-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL009" source="PROC_DD_BANK_VERIFICATION" target="SVC_AVS"><data key="edge_relationship_id">R68_REL009</data><data key="edge_source_entity_id">PROC_DD_BANK_VERIFICATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_AVS</data><data key="edge_operational_context">FY2027 budget states SSA implemented real-time bank-verification checks that include Treasury BFS Account Verification Service.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL010" source="ORG_BFS" target="SVC_AVS"><data key="edge_relationship_id">R68_REL010</data><data key="edge_source_entity_id">ORG_BFS</data><data key="edge_relationship_type">operates</data><data key="edge_target_entity_id">SVC_AVS</data><data key="edge_operational_context">Treasury identifies AVS as a Bureau of the Fiscal Service payment-integrity service.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL011" source="PROC_DD_BANK_VERIFICATION" target="APP_MYDD"><data key="edge_relationship_id">R68_REL011</data><data key="edge_source_entity_id">PROC_DD_BANK_VERIFICATION</data><data key="edge_relationship_type">protects_changes_submitted_through</data><data key="edge_target_entity_id">APP_MYDD</data><data key="edge_operational_context">SSA applies real-time bank verification to direct-deposit change requests; my Social Security Direct Deposit is an established online direct-deposit change channel.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">4</data><data key="edge_notes">Verification applies across direct-deposit change processing; source does not state that AVS is limited to or embedded inside myDD.</data></edge><edge id="R68_REL012" source="APP_EWORK" target="CTRL_DECEFFECT"><data key="edge_relationship_id">R68_REL012</data><data key="edge_source_entity_id">APP_EWORK</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">CTRL_DECEFFECT</data><data key="edge_operational_context">When eWork cannot automatically effectuate a decision, it creates a DECEFFECT issue on the Development Worksheet.</data><data key="edge_observed_as_of">2024-07-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL013" source="APP_EWORK" target="DOC_DIB_CESSATION_EXCLUSION"><data key="edge_relationship_id">R68_REL013</data><data key="edge_source_entity_id">APP_EWORK</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DOC_DIB_CESSATION_EXCLUSION</data><data key="edge_operational_context">EM-24037 states eWork generates a DIB Cessation Exclusion document when automatic MBR effectuation cannot occur.</data><data key="edge_observed_as_of">2024-07-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL014" source="DOC_DIB_CESSATION_EXCLUSION" target="APP_EP"><data key="edge_relationship_id">R68_REL014</data><data key="edge_source_entity_id">DOC_DIB_CESSATION_EXCLUSION</data><data key="edge_relationship_type">routed_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">EM-24037 directs the DIB Cessation Exclusion document to the Processing Center via Evidence Portal; current POMS also directs documentation to EP or eView.</data><data key="edge_observed_as_of">2026-09-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL015" source="DOC_DIB_CESSATION_EXCLUSION" target="APP_PCACS"><data key="edge_relationship_id">R68_REL015</data><data key="edge_source_entity_id">DOC_DIB_CESSATION_EXCLUSION</data><data key="edge_relationship_type">creates_action_control_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">Current POMS says the DECEFFECT barcode/fax creates an Action Control Record in PCACS for Processing Center resolution.</data><data key="edge_observed_as_of">2026-09-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL016" source="CTRL_DECEFFECT" target="SYS_MBR"><data key="edge_relationship_id">R68_REL016</data><data key="edge_source_entity_id">CTRL_DECEFFECT</data><data key="edge_relationship_type">requires_validation_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">DECEFFECT follow-up requires review of MBR to confirm the decision was completely and accurately processed.</data><data key="edge_observed_as_of">2024-07-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL017" source="CTRL_DECEFFECT" target="APP_POS"><data key="edge_relationship_id">R68_REL017</data><data key="edge_source_entity_id">CTRL_DECEFFECT</data><data key="edge_relationship_type">exception_to_automated_input_via</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">DECEFFECT is used when the normal eWork/POS effectuation path cannot complete the decision automatically.</data><data key="edge_observed_as_of">2026-09-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL018" source="ORG_WBDOC" target="DIARY_R8"><data key="edge_relationship_id">R68_REL018</data><data key="edge_source_entity_id">ORG_WBDOC</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">DIARY_R8</data><data key="edge_operational_context">Current SSI workload policy says R8 is set when WBDOC processes an annual representative-payee accounting report with conserved funds over the threshold.</data><data key="edge_observed_as_of">2026-07-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL019" source="ORG_WBDOC" target="SYS_SSR"><data key="edge_relationship_id">R68_REL019</data><data key="edge_source_entity_id">ORG_WBDOC</data><data key="edge_relationship_type">posts_conserved_funds_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Active POMS says WBDOC posts reported conserved funds to the CF field in the REPY segment of SSR for Title XVI/concurrent cases.</data><data key="edge_observed_as_of">2013-06-06</data><data key="edge_confidence">5</data><data key="edge_notes">Current 2026 workload policy continues to rely on this WBDOC/SSR R8 mechanism.</data></edge><edge id="R68_REL020" source="DIARY_R8" target="SYS_SSR"><data key="edge_relationship_id">R68_REL020</data><data key="edge_source_entity_id">DIARY_R8</data><data key="edge_relationship_type">recorded_or_driven_by</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current SSI workload policy ties R8 selection to the CF field in the SSR REPY segment and subsequent LI/RZ selection.</data><data key="edge_observed_as_of">2026-07-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL021" source="DIARY_R8" target="PROC_R8_CONSERVED_FUNDS_REVIEW"><data key="edge_relationship_id">R68_REL021</data><data key="edge_source_entity_id">DIARY_R8</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_R8_CONSERVED_FUNDS_REVIEW</data><data key="edge_operational_context">Field offices receive R8 to review SSI/concurrent cases with high conserved funds and develop continuing eligibility.</data><data key="edge_observed_as_of">2026-07-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R68_REL022" source="PROC_R8_CONSERVED_FUNDS_REVIEW" target="DOM_TITLE16"><data key="edge_relationship_id">R68_REL022</data><data key="edge_source_entity_id">PROC_R8_CONSERVED_FUNDS_REVIEW</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">R8 review addresses SSI resource eligibility when conserved funds approach or exceed program resource limits.</data><data key="edge_observed_as_of">2026-07-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R69_REL001" source="APP_ECO" target="SVC_AVC"><data key="edge_relationship_id">R69_REL001</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">requests_verified_address_from</data><data key="edge_target_entity_id">SVC_AVC</data><data key="edge_operational_context">Current TRO policy says ECO retrieves a verified debtor address from an Address Verification Contractor before mailing the pre-offset notice.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes">Vendor identity and lookup technology are not stated.</data></edge><edge id="R69_REL002" source="SVC_AVC" target="DATA_AVC_DEBTOR_ADDR"><data key="edge_relationship_id">R69_REL002</data><data key="edge_source_entity_id">SVC_AVC</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_AVC_DEBTOR_ADDR</data><data key="edge_operational_context">The AVC returns a good/verified address result used by ECO for debt-collection notice mailing.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes">Classification is external lookup/notice-address data.</data></edge><edge id="R69_REL003" source="DATA_AVC_DEBTOR_ADDR" target="APP_ECO"><data key="edge_relationship_id">R69_REL003</data><data key="edge_source_entity_id">DATA_AVC_DEBTOR_ADDR</data><data key="edge_relationship_type">supplies_notice_address_to</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">When the AVC returns a good address, ECO mails the pre-offset notice to that address.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes">No master-record overwrite is stated.</data></edge><edge id="R69_REL004" source="APP_ECO" target="SYS_MBR"><data key="edge_relationship_id">R69_REL004</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">uses_recent_address_fallback_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">If AVC does not return a good address and MBR was updated within the last year, ECO uses the MBR address for the pre-offset notice.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes">Fallback usage does not imply synchronization with AVC.</data></edge><edge id="R69_REL005" source="APP_ECO" target="SYS_SSR"><data key="edge_relationship_id">R69_REL005</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">uses_recent_address_fallback_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">If AVC does not return a good address and SSR was updated within the last year, ECO uses the SSR address for the pre-offset notice.</data><data key="edge_observed_as_of">2025-05-08</data><data key="edge_confidence">5</data><data key="edge_notes">Fallback usage does not imply synchronization with AVC.</data></edge><edge id="R69_REL006" source="FORM_SS5" target="DOM_ENUMERATION"><data key="edge_relationship_id">R69_REL006</data><data key="edge_source_entity_id">FORM_SS5</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">Current POMS identifies Form SS-5 as an application pathway for original, replacement, and corrected SSN-card actions and electronic-record changes.</data><data key="edge_observed_as_of">2024-06-14</data><data key="edge_confidence">5</data><data key="edge_notes">EAB/EAE/EBE and online routes are separate application pathways.</data></edge><edge id="R69_REL007" source="APP_SSNAP" target="FORM_SS5"><data key="edge_relationship_id">R69_REL007</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">normally_processes</data><data key="edge_target_entity_id">FORM_SS5</data><data key="edge_operational_context">Current enumeration policy says paper Form SS-5 applications are normally entered and processed in SSNAP, with specified manual-processing exceptions.</data><data key="edge_observed_as_of">2024-06-14</data><data key="edge_confidence">5</data><data key="edge_notes">Manual OCO processing exceptions remain.</data></edge><edge id="R69_REL008" source="APP_IRON" target="FORM_SS5"><data key="edge_relationship_id">R69_REL008</data><data key="edge_source_entity_id">APP_IRON</data><data key="edge_relationship_type">stores_or_retrieves_application_images_of</data><data key="edge_target_entity_id">FORM_SS5</data><data key="edge_operational_context">Current Numident correction policy says paper SS-5 and SS-5 microprints are available through IRON.</data><data key="edge_observed_as_of">2026-06-05</data><data key="edge_confidence">5</data><data key="edge_notes">Document retrieval role only.</data></edge><edge id="R69_REL009" source="APP_SS5_REPRINTS" target="FORM_SS5"><data key="edge_relationship_id">R69_REL009</data><data key="edge_source_entity_id">APP_SS5_REPRINTS</data><data key="edge_relationship_type">retrieves_application_records_of</data><data key="edge_target_entity_id">FORM_SS5</data><data key="edge_operational_context">Current Numident correction policy says prior SS-5 records are available through SS-5 Reprints.</data><data key="edge_observed_as_of">2026-06-05</data><data key="edge_confidence">5</data><data key="edge_notes">Document retrieval role only.</data></edge><edge id="R69_REL010" source="FORM_SS5" target="PROC_NCP"><data key="edge_relationship_id">R69_REL010</data><data key="edge_source_entity_id">FORM_SS5</data><data key="edge_relationship_type">provides_source_evidence_for</data><data key="edge_target_entity_id">PROC_NCP</data><data key="edge_operational_context">SSA compares a prior SS-5 or SS-5 microprint with Numident to establish documented keying errors before NCP correction.</data><data key="edge_observed_as_of">2026-06-05</data><data key="edge_confidence">5</data><data key="edge_notes">NCP is used only when the keying error can be documented.</data></edge><edge id="R69_REL011" source="DATA_REP_PAYEE_TYPE" target="APP_ERPS"><data key="edge_relationship_id">R69_REL011</data><data key="edge_source_entity_id">DATA_REP_PAYEE_TYPE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS says Rep Payee Type is recorded in eRPS.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data><data key="edge_notes">Attribute is Individual or Organization.</data></edge><edge id="R69_REL012" source="DATA_REP_PAYEE_TYPE" target="SYS_MBR"><data key="edge_relationship_id">R69_REL012</data><data key="edge_source_entity_id">DATA_REP_PAYEE_TYPE</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS says Rep Payee Type is recorded on MBR.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data><data key="edge_notes">Title II program-record attribute.</data></edge><edge id="R69_REL013" source="DATA_REP_PAYEE_TYPE" target="SYS_SSR"><data key="edge_relationship_id">R69_REL013</data><data key="edge_source_entity_id">DATA_REP_PAYEE_TYPE</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS says Rep Payee Type is recorded on SSR.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data><data key="edge_notes">Title XVI program-record attribute.</data></edge><edge id="R69_REL014" source="DATA_ERPS_ORG_PHYS_ZIP" target="APP_ERPS"><data key="edge_relationship_id">R69_REL014</data><data key="edge_source_entity_id">DATA_ERPS_ORG_PHYS_ZIP</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">eRPS uses the ZIP Code of the organization physical location when establishing an organizational payee identifier.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data><data key="edge_notes">Address-derived organization identity attribute.</data></edge><edge id="R69_REL015" source="DATA_ERPS_ORG_PHYS_ZIP" target="DATA_ERPS_ORG_ID"><data key="edge_relationship_id">R69_REL015</data><data key="edge_source_entity_id">DATA_ERPS_ORG_PHYS_ZIP</data><data key="edge_relationship_type">used_to_construct</data><data key="edge_target_entity_id">DATA_ERPS_ORG_ID</data><data key="edge_operational_context">Current POMS says eRPS establishes Organization ID using the ZIP Code of the organization physical location.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data><data key="edge_notes">Organization ID is not the EIN and EINs are not unique in the eRPS context.</data></edge><edge id="R69_REL016" source="MODEL_OACT_LABOR_FORCE" target="ORG_SSA_OCACT"><data key="edge_relationship_id">R69_REL016</data><data key="edge_source_entity_id">MODEL_OACT_LABOR_FORCE</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_OCACT</data><data key="edge_operational_context">The 2026 Trustees Report says Actuarial Services uses a model to project the civilian labor force.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes">Logical actuarial-model relationship; implementation technology not stated.</data></edge><edge id="R69_REL017" source="MODEL_OACT_LABOR_FORCE" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R69_REL017</data><data key="edge_source_entity_id">MODEL_OACT_LABOR_FORCE</data><data key="edge_relationship_type">supports_projection_in</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Civilian labor-force projections form part of the economic assumptions and methods supporting the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes">The model projects age/sex/marital-status/children dimensions.</data></edge><edge id="R69_REL018" source="MODEL_OACT_POPULATION" target="ORG_SSA_OCACT"><data key="edge_relationship_id">R69_REL018</data><data key="edge_source_entity_id">MODEL_OACT_POPULATION</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_OCACT</data><data key="edge_operational_context">The 2026 Trustees Report says Actuarial Services projects the Social Security area population by age, sex, and marital status.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes">Logical actuarial-model relationship.</data></edge><edge id="R69_REL019" source="MODEL_OACT_POPULATION" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R69_REL019</data><data key="edge_source_entity_id">MODEL_OACT_POPULATION</data><data key="edge_relationship_type">supports_projection_in</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Social Security area population projections support demographic assumptions and projections in the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes">Combines fertility, mortality, immigration, marriage, and divorce assumptions.</data></edge><edge id="R69_REL020" source="ORG_SSA_OCACT" target="DATA_OACT_BENEFICIARY"><data key="edge_relationship_id">R69_REL020</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_BENEFICIARY</data><data key="edge_operational_context">OCACT publishes the current Social Security Beneficiary Data service.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Public statistical publication layer.</data></edge><edge id="R69_REL021" source="DATA_MONTHLY_STAT_SNAPSHOT" target="DATA_OACT_BENEFICIARY"><data key="edge_relationship_id">R69_REL021</data><data key="edge_source_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_relationship_type">directs_detailed_oasdi_statistics_to</data><data key="edge_target_entity_id">DATA_OACT_BENEFICIARY</data><data key="edge_operational_context">Current Monthly Statistical Snapshot tells users to visit the Actuary’s Beneficiary Data site for more detailed monthly OASDI information.</data><data key="edge_observed_as_of">2026-03</data><data key="edge_confidence">5</data><data key="edge_notes">Publication-navigation relationship, not a physical data interface.</data></edge><edge id="R69_REL022" source="ORG_SSA_OCACT" target="REPORT_OACT_FACT_SHEET"><data key="edge_relationship_id">R69_REL022</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">REPORT_OACT_FACT_SHEET</data><data key="edge_operational_context">OCACT publishes the semiannual Social Security Program Fact Sheet.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Current observed edition June 30, 2026.</data></edge><edge id="R69_REL023" source="ORG_SSA_OCACT" target="DATA_POPULAR_BABY_NAMES"><data key="edge_relationship_id">R69_REL023</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_POPULAR_BABY_NAMES</data><data key="edge_operational_context">OCACT publishes SSA Popular Baby Names statistics and supporting data pages.</data><data key="edge_observed_as_of">2026-03</data><data key="edge_confidence">5</data><data key="edge_notes">Public statistical publication.</data></edge><edge id="R69_REL024" source="DATA_POPULAR_BABY_NAMES" target="DOM_ENUMERATION"><data key="edge_relationship_id">R69_REL024</data><data key="edge_source_entity_id">DATA_POPULAR_BABY_NAMES</data><data key="edge_relationship_type">derived_from_application_records_in</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">SSA states all popular-name data come from records on Social Security card applications.</data><data key="edge_observed_as_of">2026-03</data><data key="edge_confidence">5</data><data key="edge_notes">Do not infer a specific physical source store beyond the enumeration/application record domain.</data></edge><edge id="R69_REL025" source="PORTAL_SSA_OPEN_DATA" target="DATA_SSA_COMPREHENSIVE_LISTING"><data key="edge_relationship_id">R69_REL025</data><data key="edge_source_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_SSA_COMPREHENSIVE_LISTING</data><data key="edge_operational_context">SSA Open Data publishes the comprehensive listing/inventory of authoritative primary data assets and associated public endpoints.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Inventory is also downloadable in CSV/JSON.</data></edge><edge id="R69_REL026" source="DATA_SSA_COMPREHENSIVE_LISTING" target="EXT_FED_DATA_CATALOG"><data key="edge_relationship_id">R69_REL026</data><data key="edge_source_entity_id">DATA_SSA_COMPREHENSIVE_LISTING</data><data key="edge_relationship_type">available_via</data><data key="edge_target_entity_id">EXT_FED_DATA_CATALOG</data><data key="edge_operational_context">SSA directs users to browse, search, and filter its comprehensive data listing through the Federal Data Catalog at Data.gov.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Catalog layer only; operational source data remain with SSA.</data></edge><edge id="R69_REL027" source="PORTAL_SSA_OPEN_DATA" target="EXT_FED_DATA_CATALOG"><data key="edge_relationship_id">R69_REL027</data><data key="edge_source_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_relationship_type">links_to</data><data key="edge_target_entity_id">EXT_FED_DATA_CATALOG</data><data key="edge_operational_context">SSA Open Data directs users to the Federal Data Catalog for browsing the agency inventory.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Public catalog integration/linkage.</data></edge><edge id="R69_REL028" source="DATA_SSA_COMPREHENSIVE_LISTING" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R69_REL028</data><data key="edge_source_entity_id">DATA_SSA_COMPREHENSIVE_LISTING</data><data key="edge_relationship_type">catalogs</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">SSA Open Data lists US-GOV-SSA-3413 Monthly Statistical Snapshot among recently cataloged data assets.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Catalog relationship.</data></edge><edge id="R69_REL029" source="DATA_SSA_COMPREHENSIVE_LISTING" target="DATA_OASDI_STATE_COUNTY_2025"><data key="edge_relationship_id">R69_REL029</data><data key="edge_source_entity_id">DATA_SSA_COMPREHENSIVE_LISTING</data><data key="edge_relationship_type">catalogs</data><data key="edge_target_entity_id">DATA_OASDI_STATE_COUNTY_2025</data><data key="edge_operational_context">SSA Open Data lists US-GOV-SSA-3415 OASDI Beneficiaries by State and County, 2025.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Catalog relationship.</data></edge><edge id="R69_REL030" source="DATA_SSA_COMPREHENSIVE_LISTING" target="DATA_SSI_STATE_COUNTY_2025"><data key="edge_relationship_id">R69_REL030</data><data key="edge_source_entity_id">DATA_SSA_COMPREHENSIVE_LISTING</data><data key="edge_relationship_type">catalogs</data><data key="edge_target_entity_id">DATA_SSI_STATE_COUNTY_2025</data><data key="edge_operational_context">SSA Open Data lists US-GOV-SSA-3416 SSI Recipients by State and County, 2025.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Catalog relationship.</data></edge><edge id="R69_REL031" source="DATA_SSA_COMPREHENSIVE_LISTING" target="REPORT_SSI_ASR_2025"><data key="edge_relationship_id">R69_REL031</data><data key="edge_source_entity_id">DATA_SSA_COMPREHENSIVE_LISTING</data><data key="edge_relationship_type">catalogs</data><data key="edge_target_entity_id">REPORT_SSI_ASR_2025</data><data key="edge_operational_context">SSA Open Data lists US-GOV-SSA-3417 SSI Annual Statistical Report, 2025.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Catalog relationship.</data></edge><edge id="R69_REL032" source="REPORT_OASDI_MONTHLY_STATS" target="SYS_MBR"><data key="edge_relationship_id">R69_REL032</data><data key="edge_source_entity_id">REPORT_OASDI_MONTHLY_STATS</data><data key="edge_relationship_type">historically_derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The final OASDI Monthly Statistics edition identifies MBR 100-percent data as the source for current-payment OASDI statistics.</data><data key="edge_observed_as_of">2007-11</data><data key="edge_confidence">5</data><data key="edge_notes">Historical statistical-production relationship.</data></edge><edge id="R69_REL033" source="REPORT_OASDI_MONTHLY_STATS" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R69_REL033</data><data key="edge_source_entity_id">REPORT_OASDI_MONTHLY_STATS</data><data key="edge_relationship_type">succeeded_by_comparable_statistics_in</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">SSA states OASDI Monthly Statistics was discontinued after November 2007 and comparable statistics remain available in Monthly Statistical Snapshot.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Publication lineage; not a system migration claim.</data></edge><edge id="R69_REL034" source="REPORT_OASDI_MONTHLY_STATS" target="DATA_OACT_BENEFICIARY"><data key="edge_relationship_id">R69_REL034</data><data key="edge_source_entity_id">REPORT_OASDI_MONTHLY_STATS</data><data key="edge_relationship_type">succeeded_by_comparable_statistics_in</data><data key="edge_target_entity_id">DATA_OACT_BENEFICIARY</data><data key="edge_operational_context">SSA states comparable statistics also remain available through OACT Beneficiary Data.</data><data key="edge_observed_as_of">2026-08-24</data><data key="edge_confidence">5</data><data key="edge_notes">Publication lineage; not a direct database migration claim.</data></edge><edge id="R69_REL035" source="ORG_SSA_OIG" target="GOV_NAFC"><data key="edge_relationship_id">R69_REL035</data><data key="edge_source_entity_id">ORG_SSA_OIG</data><data key="edge_relationship_type">participates_in</data><data key="edge_target_entity_id">GOV_NAFC</data><data key="edge_operational_context">SSA OIG describes NAFC as a partnership between SSA and SSA OIG.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes">Quarterly meetings and annual summit documented.</data></edge><edge id="R69_REL036" source="GOV_NAFC" target="ORG_SSA_OIG"><data key="edge_relationship_id">R69_REL036</data><data key="edge_source_entity_id">GOV_NAFC</data><data key="edge_relationship_type">informs_oversight_by</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">OIG testimony says NAFC discussions help inform SSA OIG oversight and highlight fraud risks and best practices.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes">Governance/oversight relationship.</data></edge><edge id="R70_REL001" source="PROC_UPLOAD_TECH_INIT" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL001</data><data key="edge_source_entity_id">PROC_UPLOAD_TECH_INIT</data><data key="edge_relationship_type">implemented_by</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Technician-requested forms/evidence are completed through Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL002" source="APP_TED" target="PROC_UPLOAD_TECH_INIT"><data key="edge_relationship_id">R70_REL002</data><data key="edge_source_entity_id">APP_TED</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_UPLOAD_TECH_INIT</data><data key="edge_operational_context">Technician creates the document request task in TED before the customer receives the upload link.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL003" source="PROC_UPLOAD_CUSTOMER_INIT" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL003</data><data key="edge_source_entity_id">PROC_UPLOAD_CUSTOMER_INIT</data><data key="edge_relationship_type">implemented_by</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Customer self-service form/evidence submission runs through Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL004" source="PROC_UPLOAD_CUSTOMER_INIT" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">R70_REL004</data><data key="edge_source_entity_id">PROC_UPLOAD_CUSTOMER_INIT</data><data key="edge_relationship_type">authenticates_via</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">Customer-initiated access requires authentication through Login.gov or ID.me.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL005" source="PROC_UPLOAD_CUSTOMER_INIT" target="SVC_IDME"><data key="edge_relationship_id">R70_REL005</data><data key="edge_source_entity_id">PROC_UPLOAD_CUSTOMER_INIT</data><data key="edge_relationship_type">authenticates_via</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">Customer-initiated access requires authentication through ID.me or Login.gov.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL006" source="PROC_UPLOAD_CUSTOMER_INIT" target="APP_MYSSA"><data key="edge_relationship_id">R70_REL006</data><data key="edge_source_entity_id">PROC_UPLOAD_CUSTOMER_INIT</data><data key="edge_relationship_type">accessible_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Customers can launch Upload Documents from my Social Security.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL007" source="PROC_UPLOAD_CUSTOMER_INIT" target="DATA_UPLOAD_ROUTING_ZIP"><data key="edge_relationship_id">R70_REL007</data><data key="edge_source_entity_id">PROC_UPLOAD_CUSTOMER_INIT</data><data key="edge_relationship_type">uses_routing_attribute</data><data key="edge_target_entity_id">DATA_UPLOAD_ROUTING_ZIP</data><data key="edge_operational_context">The submission uses a mailing-address ZIP to route the document to a field office.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL008" source="APP_PERSON_INFO" target="DATA_UPLOAD_ROUTING_ZIP"><data key="edge_relationship_id">R70_REL008</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">provides_when_available</data><data key="edge_target_entity_id">DATA_UPLOAD_ROUTING_ZIP</data><data key="edge_operational_context">When a mailing address exists in Person Information, its ZIP is the routing value used for the customer submission.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL009" source="PROC_UPLOAD_CUSTOMER_INIT" target="DATA_UPLOAD_ROUTING_ZIP"><data key="edge_relationship_id">R70_REL009</data><data key="edge_source_entity_id">PROC_UPLOAD_CUSTOMER_INIT</data><data key="edge_relationship_type">collects_when_pi_missing</data><data key="edge_target_entity_id">DATA_UPLOAD_ROUTING_ZIP</data><data key="edge_operational_context">If PI has no mailing address, the customer is prompted to enter a mailing-address ZIP before submission.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL010" source="DATA_UPLOAD_ROUTING_ZIP" target="APP_PERSON_INFO"><data key="edge_relationship_id">R70_REL010</data><data key="edge_source_entity_id">DATA_UPLOAD_ROUTING_ZIP</data><data key="edge_relationship_type">does_not_have_documented_update_path_to</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">EM-25024 describes customer entry for routing when PI lacks a mailing address but does not say that entered ZIP updates PI/PERSON.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL011" source="PROC_UPLOAD_CUSTOMER_INIT" target="APP_WORKTRACK"><data key="edge_relationship_id">R70_REL011</data><data key="edge_source_entity_id">PROC_UPLOAD_CUSTOMER_INIT</data><data key="edge_relationship_type">routes_submission_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">All successfully submitted documents arrive at the field office through WorkTrack.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL012" source="FORM_SSA827" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL012</data><data key="edge_source_entity_id">FORM_SSA827</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA digital-service guidance supports electronic submission through Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL013" source="FORM_SSA820BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL013</data><data key="edge_source_entity_id">FORM_SSA820BK</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA digital-service guidance supports electronic submission through Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL014" source="FORM_SSA821BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL014</data><data key="edge_source_entity_id">FORM_SSA821BK</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA digital-service guidance supports electronic submission through Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL015" source="FORM_SSA632BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL015</data><data key="edge_source_entity_id">FORM_SSA632BK</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA digital-service guidance supports electronic submission through Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL016" source="FORM_SSA634" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL016</data><data key="edge_source_entity_id">FORM_SSA634</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA digital-service guidance supports electronic submission through Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL017" source="FORM_SSA454BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL017</data><data key="edge_source_entity_id">FORM_SSA454BK</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA digital-service guidance supports electronic submission through Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL018" source="FORM_SSA827" target="PROC_UPLOAD_CREDENTIAL_STEPUP"><data key="edge_relationship_id">R70_REL018</data><data key="edge_source_entity_id">FORM_SSA827</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">PROC_UPLOAD_CREDENTIAL_STEPUP</data><data key="edge_operational_context">Current SSA forms/EM guidance identifies SSA-827 as requiring advanced identity credential step-up for electronic submission.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL019" source="FORM_SSA454BK" target="PROC_UPLOAD_CREDENTIAL_STEPUP"><data key="edge_relationship_id">R70_REL019</data><data key="edge_source_entity_id">FORM_SSA454BK</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">PROC_UPLOAD_CREDENTIAL_STEPUP</data><data key="edge_operational_context">Current SSA Forms catalog lists SSA-454-BK among forms requiring additional identity verification for electronic submission.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL020" source="FORM_SSA454BK" target="APP_I454"><data key="edge_relationship_id">R70_REL020</data><data key="edge_source_entity_id">FORM_SSA454BK</data><data key="edge_relationship_type">implemented_online_by</data><data key="edge_target_entity_id">APP_I454</data><data key="edge_operational_context">Current CDR guidance provides online SSA-454 completion through the i454 application behind mySSA.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL021" source="APP_I454" target="APP_EDCS"><data key="edge_relationship_id">R70_REL021</data><data key="edge_source_entity_id">APP_I454</data><data key="edge_relationship_type">propagates_submission_into</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">POMS says keyed i454 and electronic SSA-827 propagate into EDCS before transfer to DDS.</data><data key="edge_observed_as_of">2026-04-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL022" source="FORM_SSA827" target="FORM_SSA454BK"><data key="edge_relationship_id">R70_REL022</data><data key="edge_source_entity_id">FORM_SSA827</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">FORM_SSA454BK</data><data key="edge_operational_context">Current CDR policy requires SSA-827 with SSA-454-BK for CDR development.</data><data key="edge_observed_as_of">2026-04-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL023" source="FORM_SSA820BK" target="FORM_SSA454BK"><data key="edge_relationship_id">R70_REL023</data><data key="edge_source_entity_id">FORM_SSA820BK</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">FORM_SSA454BK</data><data key="edge_operational_context">Current CDR procedures identify SSA-820-BK as supporting work-activity documentation with CDR packages when applicable.</data><data key="edge_observed_as_of">2026-04-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL024" source="FORM_SSA821BK" target="FORM_SSA454BK"><data key="edge_relationship_id">R70_REL024</data><data key="edge_source_entity_id">FORM_SSA821BK</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">FORM_SSA454BK</data><data key="edge_operational_context">Current CDR procedures identify SSA-821-BK as supporting work-activity documentation with CDR packages when applicable.</data><data key="edge_observed_as_of">2026-04-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL025" source="FORM_SSA766" target="CAP_UPLOAD_WEBFORM_MODE"><data key="edge_relationship_id">R70_REL025</data><data key="edge_source_entity_id">FORM_SSA766</data><data key="edge_relationship_type">available_as_mode</data><data key="edge_target_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="edge_operational_context">EM-25024 lists the form as a static webform in the March 2025 Upload Documents release.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL026" source="FORM_SSA769" target="CAP_UPLOAD_WEBFORM_MODE"><data key="edge_relationship_id">R70_REL026</data><data key="edge_source_entity_id">FORM_SSA769</data><data key="edge_relationship_type">available_as_mode</data><data key="edge_target_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="edge_operational_context">EM-25024 lists the form as a static webform in the March 2025 Upload Documents release.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL027" source="FORM_SSA783" target="CAP_UPLOAD_WEBFORM_MODE"><data key="edge_relationship_id">R70_REL027</data><data key="edge_source_entity_id">FORM_SSA783</data><data key="edge_relationship_type">available_as_mode</data><data key="edge_target_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="edge_operational_context">EM-25024 lists the form as a static webform in the March 2025 Upload Documents release.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL028" source="FORM_SSA4178" target="CAP_UPLOAD_WEBFORM_MODE"><data key="edge_relationship_id">R70_REL028</data><data key="edge_source_entity_id">FORM_SSA4178</data><data key="edge_relationship_type">available_as_mode</data><data key="edge_target_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="edge_operational_context">EM-25024 lists the form as a static webform in the March 2025 Upload Documents release.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL029" source="FORM_SSA7156" target="CAP_UPLOAD_WEBFORM_MODE"><data key="edge_relationship_id">R70_REL029</data><data key="edge_source_entity_id">FORM_SSA7156</data><data key="edge_relationship_type">available_as_mode</data><data key="edge_target_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="edge_operational_context">EM-25024 lists the form as a static webform in the March 2025 Upload Documents release.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL030" source="FORM_SSA766" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL030</data><data key="edge_source_entity_id">FORM_SSA766</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">EM-25024 lists the form for electronic customer submission in Upload Documents.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL031" source="FORM_SSA769" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL031</data><data key="edge_source_entity_id">FORM_SSA769</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">EM-25024 lists the form for electronic customer submission in Upload Documents.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL032" source="FORM_SSA783" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL032</data><data key="edge_source_entity_id">FORM_SSA783</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">EM-25024 lists the form for electronic customer submission in Upload Documents.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL033" source="FORM_SSA4178" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL033</data><data key="edge_source_entity_id">FORM_SSA4178</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">EM-25024 lists the form for electronic customer submission in Upload Documents.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL034" source="FORM_SSA7156" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R70_REL034</data><data key="edge_source_entity_id">FORM_SSA7156</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">EM-25024 lists the form for electronic customer submission in Upload Documents.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL035" source="DATA_SSA8240" target="CAP_UPLOAD_WEBFORM_MODE"><data key="edge_relationship_id">R70_REL035</data><data key="edge_source_entity_id">DATA_SSA8240</data><data key="edge_relationship_type">available_as_mode</data><data key="edge_target_entity_id">CAP_UPLOAD_WEBFORM_MODE</data><data key="edge_operational_context">EM-25024 lists SSA-8240 as the March 2025 fillable PDF addition in Upload Documents.</data><data key="edge_observed_as_of">2025-03-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL036" source="REPORT_OACT_DEMOGRAPHIC_2026" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R70_REL036</data><data key="edge_source_entity_id">REPORT_OACT_DEMOGRAPHIC_2026</data><data key="edge_relationship_type">supplies_assumptions_to</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">OCACT states the memorandum presents the demographic assumptions used in the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-06-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL037" source="REPORT_OACT_DEMOGRAPHIC_2026" target="MODEL_OASDI_SCENARIO"><data key="edge_relationship_id">R70_REL037</data><data key="edge_source_entity_id">REPORT_OACT_DEMOGRAPHIC_2026</data><data key="edge_relationship_type">documents_methodology_for</data><data key="edge_target_entity_id">MODEL_OASDI_SCENARIO</data><data key="edge_operational_context">The memo defines the three long-range demographic assumption sets used in Trustees projections; relationship is methodological, not a software interface.</data><data key="edge_observed_as_of">2026-06-09</data><data key="edge_confidence">4</data><data key="edge_notes">Existing scenario-model entity is broader than the demographic memo; no physical model implementation is inferred.</data></edge><edge id="R70_REL038" source="REPORT_SSAB_REPPAYEE_TRENDS_2026" target="DOM_REPPAYEE"><data key="edge_relationship_id">R70_REL038</data><data key="edge_source_entity_id">REPORT_SSAB_REPPAYEE_TRENDS_2026</data><data key="edge_relationship_type">analyzes</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">SSAB issue brief analyzes 2010-2025 trends among adult Title II and SSI populations with representative payees.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL039" source="PROC_PIR" target="REPO_PIR_SHARED_SITE"><data key="edge_relationship_id">R70_REL039</data><data key="edge_source_entity_id">PROC_PIR</data><data key="edge_relationship_type">stores_documents_in</data><data key="edge_target_entity_id">REPO_PIR_SHARED_SITE</data><data key="edge_operational_context">OIG says SSA relies on a shared internal website for PIR document storage.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL040" source="PROC_PIR" target="DASH_PIR_SUMMARY"><data key="edge_relationship_id">R70_REL040</data><data key="edge_source_entity_id">PROC_PIR</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">DASH_PIR_SUMMARY</data><data key="edge_operational_context">OIG reviewed PIR summary metrics from an Agency dashboard.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL041" source="DASH_PIR_SUMMARY" target="REPO_PIR_SHARED_SITE"><data key="edge_relationship_id">R70_REL041</data><data key="edge_source_entity_id">DASH_PIR_SUMMARY</data><data key="edge_relationship_type">not_control_linked_to</data><data key="edge_target_entity_id">REPO_PIR_SHARED_SITE</data><data key="edge_operational_context">OIG says the shared site lacked controls linking dashboard data to source PIR documents.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL042" source="APP_IAPPT" target="DATA_IAPPT_MAILING_ADDRESS"><data key="edge_relationship_id">R70_REL042</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">DATA_IAPPT_MAILING_ADDRESS</data><data key="edge_operational_context">Current iAppt policy requires the claimant to provide mailing address as appointment-intake information.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL043" source="DATA_IAPPT_MAILING_ADDRESS" target="APP_PERSON_INFO"><data key="edge_relationship_id">R70_REL043</data><data key="edge_source_entity_id">DATA_IAPPT_MAILING_ADDRESS</data><data key="edge_relationship_type">does_not_have_documented_update_path_to</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Current iAppt policy treats internet intake data as unverified and does not document automatic correction of Person Information.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL044" source="DATA_IAPPT_MAILING_ADDRESS" target="SYS_NUMIDENT"><data key="edge_relationship_id">R70_REL044</data><data key="edge_source_entity_id">DATA_IAPPT_MAILING_ADDRESS</data><data key="edge_relationship_type">does_not_have_documented_update_path_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current iAppt policy does not document automatic correction of Numident from claimant-entered appointment data.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R70_REL045" source="EX_HRS_LINKAGE" target="DATA_HRS_CYBF"><data key="edge_relationship_id">R70_REL045</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">refreshes_with_consent</data><data key="edge_target_entity_id">DATA_HRS_CYBF</data><data key="edge_operational_context">Current HRS documentation says new SSA record sets refresh the cross-year benefits product under valid permissions; benefits permissions can have a maximum prospective range of 12 years.</data><data key="edge_observed_as_of">2026-04-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL001" source="DB_MASTER_REP_PAYEE_FILE" target="APP_ERPS"><data key="edge_relationship_id">R71_REL001</data><data key="edge_source_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS states the Master Representative Payee File is a part of eRPS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL002" source="DB_MASTER_REP_PAYEE_FILE" target="DATA_MRPF_ADDRESS"><data key="edge_relationship_id">R71_REL002</data><data key="edge_source_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_MRPF_ADDRESS</data><data key="edge_operational_context">SORN 60-0222 lists addresses among categories of records maintained for payees, applicants, beneficiaries/recipients and organizations.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL003" source="SYS_NUMIDENT" target="DB_MASTER_REP_PAYEE_FILE"><data key="edge_relationship_id">R71_REL003</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">record_source_for</data><data key="edge_target_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="edge_operational_context">SORN 60-0222 identifies the Master Files of SSN Holders and SSN Applications as an existing SSA record source for MRPF.</data><data key="edge_observed_as_of">2018-11-02</data><data key="edge_confidence">5</data><data key="edge_notes">Current physical interface mechanism is not stated.</data></edge><edge id="R71_REL004" source="SYS_MBR" target="DB_MASTER_REP_PAYEE_FILE"><data key="edge_relationship_id">R71_REL004</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">record_source_for</data><data key="edge_target_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="edge_operational_context">SORN 60-0222 identifies MBR as an existing SSA record source for MRPF.</data><data key="edge_observed_as_of">2018-11-02</data><data key="edge_confidence">5</data><data key="edge_notes">No transport or automatic field synchronization is inferred.</data></edge><edge id="R71_REL005" source="SYS_SSR" target="DB_MASTER_REP_PAYEE_FILE"><data key="edge_relationship_id">R71_REL005</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">record_source_for</data><data key="edge_target_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="edge_operational_context">SORN 60-0222 identifies SSI Record and Special Veterans Benefits as an existing SSA record source for MRPF.</data><data key="edge_observed_as_of">2018-11-02</data><data key="edge_confidence">5</data><data key="edge_notes">No transport or automatic field synchronization is inferred.</data></edge><edge id="R71_REL006" source="DB_CLAIMS_FOLDERS_SYSTEM" target="DB_MASTER_REP_PAYEE_FILE"><data key="edge_relationship_id">R71_REL006</data><data key="edge_source_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="edge_relationship_type">record_source_for</data><data key="edge_target_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="edge_operational_context">SORN 60-0222 identifies Claims Folders System as an existing SSA record source for MRPF.</data><data key="edge_observed_as_of">2018-11-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL007" source="APP_DMS" target="DB_MASTER_REP_PAYEE_FILE"><data key="edge_relationship_id">R71_REL007</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">record_source_for</data><data key="edge_target_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="edge_operational_context">SORN 60-0222 identifies ROAR/DMS as an existing SSA record source for MRPF.</data><data key="edge_observed_as_of">2018-11-02</data><data key="edge_confidence">5</data><data key="edge_notes">No transport mechanism is stated.</data></edge><edge id="R71_REL008" source="APP_PUPS" target="DB_MASTER_REP_PAYEE_FILE"><data key="edge_relationship_id">R71_REL008</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">record_source_for</data><data key="edge_target_entity_id">DB_MASTER_REP_PAYEE_FILE</data><data key="edge_operational_context">SORN 60-0222 identifies PUPS as an existing SSA record source for MRPF.</data><data key="edge_observed_as_of">2018-11-02</data><data key="edge_confidence">5</data><data key="edge_notes">No transport mechanism is stated.</data></edge><edge id="R71_REL009" source="DATA_MRPF_ADDRESS" target="APP_ERPS"><data key="edge_relationship_id">R71_REL009</data><data key="edge_source_entity_id">DATA_MRPF_ADDRESS</data><data key="edge_relationship_type">supports_suitability_assessment_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">SSA policy permits use of residence stability and contact information in representative-payee suitability work; MRPF is part of eRPS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">The policy establishes use of address/residence information in payee suitability, but does not expose a discrete automated scoring mechanism.</data></edge><edge id="R71_REL010" source="APP_WMS" target="DOM_TITLE2"><data key="edge_relationship_id">R71_REL010</data><data key="edge_source_entity_id">APP_WMS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Current POMS defines WMS as providing information about Title II benefit claims currently in process.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL011" source="APP_WMS" target="APP_PEBES"><data key="edge_relationship_id">R71_REL011</data><data key="edge_source_entity_id">APP_WMS</data><data key="edge_relationship_type">provides_pending_claim_information_to</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">Current Statement policy includes WMS as the source of information about Title II claims currently in process used in Statement selection/processing.</data><data key="edge_observed_as_of">2023-12-12</data><data key="edge_confidence">5</data><data key="edge_notes">This is a functional data-use relationship; no physical interface mechanism is stated.</data></edge><edge id="R71_REL012" source="QRY_WMHH" target="APP_WMS"><data key="edge_relationship_id">R71_REL012</data><data key="edge_source_entity_id">QRY_WMHH</data><data key="edge_relationship_type">query_of</data><data key="edge_target_entity_id">APP_WMS</data><data key="edge_operational_context">The named WMS History Query is a workload-history query of WMS used to review case movement.</data><data key="edge_observed_as_of">2026-10-04</data><data key="edge_confidence">5</data><data key="edge_notes">Naming and current POMS context support the query-to-system relationship; hosting technology remains unknown.</data></edge><edge id="R71_REL013" source="UI_DMS_DMFS" target="APP_WMS"><data key="edge_relationship_id">R71_REL013</data><data key="edge_source_entity_id">UI_DMS_DMFS</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_WMS</data><data key="edge_operational_context">Current waiver policy explicitly calls DMFS the Workload Management System Debt Management Function Selection screen.</data><data key="edge_observed_as_of">2026-06-11</data><data key="edge_confidence">5</data><data key="edge_notes">This supplements the existing DMS workflow relationship; it does not imply WMS and DMS are one application.</data></edge><edge id="R71_REL014" source="APP_WMS" target="ORG_WSU"><data key="edge_relationship_id">R71_REL014</data><data key="edge_source_entity_id">APP_WMS</data><data key="edge_relationship_type">supports_diary_origin_routing_for</data><data key="edge_target_entity_id">ORG_WSU</data><data key="edge_operational_context">Processing Centers query WMS to identify whether a WSU originated a partial-award diary so follow-up routes back to the WSU.</data><data key="edge_observed_as_of">2025-09-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL015" source="DATA_DCR_LOCATION_V32" target="ORG_DCR"><data key="edge_relationship_id">R71_REL015</data><data key="edge_source_entity_id">DATA_DCR_LOCATION_V32</data><data key="edge_relationship_type">identifies</data><data key="edge_target_entity_id">ORG_DCR</data><data key="edge_operational_context">Current POMS identifies DCR as location code V32.</data><data key="edge_observed_as_of">2026-04-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL016" source="ORG_SSA_FIELD_OFFICES" target="ORG_DCR"><data key="edge_relationship_id">R71_REL016</data><data key="edge_source_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_relationship_type">transfers_railroad_claims_to</data><data key="edge_target_entity_id">ORG_DCR</data><data key="edge_operational_context">Field offices transfer specified railroad-related disability claims to DCR instead of the State DDS.</data><data key="edge_observed_as_of">2026-04-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL017" source="ORG_DCR" target="PROC_DCR_RR_DUAL"><data key="edge_relationship_id">R71_REL017</data><data key="edge_source_entity_id">ORG_DCR</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_DCR_RR_DUAL</data><data key="edge_operational_context">DCR has jurisdiction for qualifying railroad dual-eligibility claims and performs the disability adjudication.</data><data key="edge_observed_as_of">2026-04-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL018" source="PROC_DCR_RR_DUAL" target="APP_DCPS"><data key="edge_relationship_id">R71_REL018</data><data key="edge_source_entity_id">PROC_DCR_RR_DUAL</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DCR disability processing specialists receive CEF claims in DCPS and use DCPS to complete disability determination forms and notices.</data><data key="edge_observed_as_of">2026-04-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL019" source="PROC_DCR_RR_DUAL" target="REPO_CEF"><data key="edge_relationship_id">R71_REL019</data><data key="edge_source_entity_id">PROC_DCR_RR_DUAL</data><data key="edge_relationship_type">accesses</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Current POMS says DCR receives the certified electronic folder claim and uploads decisional notices and rationales to CEF.</data><data key="edge_observed_as_of">2026-04-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL020" source="ORG_DCR" target="ORG_RRB"><data key="edge_relationship_id">R71_REL020</data><data key="edge_source_entity_id">ORG_DCR</data><data key="edge_relationship_type">coordinates_with</data><data key="edge_target_entity_id">ORG_RRB</data><data key="edge_operational_context">DCR jurisdiction facilitates coordination of medical evidence and disability determinations with the Railroad Retirement Board.</data><data key="edge_observed_as_of">2026-04-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL021" source="PROC_DCR_RR_DUAL" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R71_REL021</data><data key="edge_source_entity_id">PROC_DCR_RR_DUAL</data><data key="edge_relationship_type">forwards_adjudicated_case_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">After DCR adjudicates the railroad-related case, it forwards the case to the field office for final processing.</data><data key="edge_observed_as_of">2026-04-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL022" source="ORG_DCR" target="PROC_DCR_MEDICAL_CDR"><data key="edge_relationship_id">R71_REL022</data><data key="edge_source_entity_id">ORG_DCR</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_DCR_MEDICAL_CDR</data><data key="edge_operational_context">SSA announced DCR will handle medical CDRs nationwide.</data><data key="edge_observed_as_of">2026-03-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL023" source="ORG_DCR" target="ORG_DDS"><data key="edge_relationship_id">R71_REL023</data><data key="edge_source_entity_id">ORG_DCR</data><data key="edge_relationship_type">assumes_medical_cdr_work_from</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">SSA announced transition of medical CDR processing from State DDSs to DCR.</data><data key="edge_observed_as_of">2026-03-12</data><data key="edge_confidence">5</data><data key="edge_notes">This is a workload transfer, not evidence of a data-store migration.</data></edge><edge id="R71_REL025" source="PROC_KEEP_WHAT_YOU_TAKE" target="APP_WLM"><data key="edge_relationship_id">R71_REL025</data><data key="edge_source_entity_id">PROC_KEEP_WHAT_YOU_TAKE</data><data key="edge_relationship_type">implemented_with</data><data key="edge_target_entity_id">APP_WLM</data><data key="edge_operational_context">The current limited-rollout business model is executed in the WLM/ASC initial-claim appointment workflow.</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL026" source="PROC_KEEP_WHAT_YOU_TAKE" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R71_REL026</data><data key="edge_source_entity_id">PROC_KEEP_WHAT_YOU_TAKE</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">Under the limited rollout, the office that takes the claim retains ownership through adjudication regardless of claimant local jurisdiction within participating locations.</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL027" source="WORK_WLM_APPT_QUEUE" target="APP_WLM"><data key="edge_relationship_id">R71_REL027</data><data key="edge_source_entity_id">WORK_WLM_APPT_QUEUE</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">APP_WLM</data><data key="edge_operational_context">WLM supports the appointment queue used to assign ASC domestic phone initial-claim appointments.</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes">Logical work-control component; no queue technology is inferred.</data></edge><edge id="R71_REL028" source="APP_ASC" target="WORK_WLM_APPT_QUEUE"><data key="edge_relationship_id">R71_REL028</data><data key="edge_source_entity_id">APP_ASC</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">WORK_WLM_APPT_QUEUE</data><data key="edge_operational_context">ASC establishes eligible appointments and sends them to WLM for distribution.</data><data key="edge_observed_as_of">2026-08-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R71_REL029" source="WORK_WLM_APPT_QUEUE" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R71_REL029</data><data key="edge_source_entity_id">WORK_WLM_APPT_QUEUE</data><data key="edge_relationship_type">routes_work_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">WLM assigns queued appointments to technicians based on skillsets and availability.</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship describes operational routing; no local-office ownership inference beyond the published rollout model.</data></edge><edge id="R71_REL030" source="WORK_WLM_APPT_QUEUE" target="APP_TED"><data key="edge_relationship_id">R71_REL030</data><data key="edge_source_entity_id">WORK_WLM_APPT_QUEUE</data><data key="edge_relationship_type">accessed_through</data><data key="edge_target_entity_id">APP_TED</data><data key="edge_operational_context">Technicians use WLM in TED and select Get Next Work to receive the next matched appointment.</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R72_REL001" source="WORK_SSI_IRS_5H_DIARY" target="UI_MSSICS_DPEN"><data key="edge_relationship_id">R72_REL001</data><data key="edge_source_entity_id">WORK_SSI_IRS_5H_DIARY</data><data key="edge_relationship_type">developed_via</data><data key="edge_target_entity_id">UI_MSSICS_DPEN</data><data key="edge_operational_context">POMS identifies DPEN as the MSSICS documentation screen for the 5H Pension Interface diary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Current policy reference; physical backend is not inferred.</data></edge><edge id="R72_REL002" source="DB_SSI_IRS_INTERFACE" target="UI_MSSICS_DPEN"><data key="edge_relationship_id">R72_REL002</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">supports_development_context_for</data><data key="edge_target_entity_id">UI_MSSICS_DPEN</data><data key="edge_operational_context">The SSI IRS/pension interface workflow produces 5H work that is documented in DPEN.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Logical workflow relationship only; no direct database-to-screen transport is asserted.</data></edge><edge id="R72_REL003" source="EXT_STATE_EBR" target="DATA_EAB_BCN"><data key="edge_relationship_id">R72_REL003</data><data key="edge_source_entity_id">EXT_STATE_EBR</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_EAB_BCN</data><data key="edge_operational_context">State BVS assigns the birth certificate number before transmitting EAB birth information to SSA.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL004" source="EX_EAB" target="DATA_EAB_BCN"><data key="edge_relationship_id">R72_REL004</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">transmits</data><data key="edge_target_entity_id">DATA_EAB_BCN</data><data key="edge_operational_context">EAB transmission to SSA includes the birth certificate number.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL005" source="DATA_EAB_BCN" target="SYS_NUMIDENT"><data key="edge_relationship_id">R72_REL005</data><data key="edge_source_entity_id">DATA_EAB_BCN</data><data key="edge_relationship_type">represented_on</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS describes the EAB Numident record and EAB processing includes the birth certificate number.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No separate table or field implementation beyond the documented Numident element is inferred.</data></edge><edge id="R72_REL006" source="EXT_STATE_EBR" target="DATA_EAB_MOTHER_ADDRESS"><data key="edge_relationship_id">R72_REL006</data><data key="edge_source_entity_id">EXT_STATE_EBR</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_EAB_MOTHER_ADDRESS</data><data key="edge_operational_context">State vital statistics transmits the mother address with the EAB request.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL007" source="EX_EAB" target="DATA_EAB_MOTHER_ADDRESS"><data key="edge_relationship_id">R72_REL007</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">transmits</data><data key="edge_target_entity_id">DATA_EAB_MOTHER_ADDRESS</data><data key="edge_operational_context">20 CFR 422.103(c)(2), quoted in current POMS, lists the address of the mother among EAB data sent to SSA.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No downstream address-master update is documented.</data></edge><edge id="R72_REL008" source="DATA_SSN_RETIREMENT_DESIG" target="SYS_NUMIDENT"><data key="edge_relationship_id">R72_REL008</data><data key="edge_source_entity_id">DATA_SSN_RETIREMENT_DESIG</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG states duplicate-SSN remediation may include designating additional SSNs as retired.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Physical storage field and implementation are not public.</data></edge><edge id="R72_REL009" source="APP_800_EMPVER" target="DATA_TNEV_TRANSIENT_INPUT"><data key="edge_relationship_id">R72_REL009</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">captures_transient</data><data key="edge_target_entity_id">DATA_TNEV_TRANSIENT_INPUT</data><data key="edge_operational_context">TNEV collects authentication, employer, and employee identity elements during the verification call.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL010" source="APP_800_EMPVER" target="DATA_TNEV_TRANSIENT_INPUT"><data key="edge_relationship_id">R72_REL010</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">discards_at_call_end</data><data key="edge_target_entity_id">DATA_TNEV_TRANSIENT_INPUT</data><data key="edge_operational_context">Current PIA states all information collected and transmitted for TNEV is dropped at the end of the call.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL011" source="APP_800_EMPVER" target="EXT_TNEV_GRAMMAR_DB"><data key="edge_relationship_id">R72_REL011</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">uses_speech_recognition_reference</data><data key="edge_target_entity_id">EXT_TNEV_GRAMMAR_DB</data><data key="edge_operational_context">SSA telecommunications vendor matches spoken user IDs against a standard 2.8 trillion alphanumeric grammar database.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Vendor/product identity is not public.</data></edge><edge id="R72_REL012" source="APP_800_EMPVER" target="SYS_NUMIDENT"><data key="edge_relationship_id">R72_REL012</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">verifies_employee_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">TNEV matches employee identity elements against Master Files of SSN Holders and SSN Applications.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL013" source="DATA_MONTHLY_STAT_SNAPSHOT" target="DATA_MONTHLY_SNAPSHOT_FLAT"><data key="edge_relationship_id">R72_REL013</data><data key="edge_source_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_relationship_type">provides_archive_for</data><data key="edge_target_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_operational_context">SSA regenerates the flattened time series monthly from the full archive of Monthly Statistical Snapshot HTML tables.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL014" source="DATA_MONTHLY_SNAPSHOT_FLAT" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">R72_REL014</data><data key="edge_source_entity_id">DATA_MONTHLY_SNAPSHOT_FLAT</data><data key="edge_relationship_type">published_as</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">Flattened files are a machine-readable derivative companion to the Monthly Statistical Snapshot series.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship describes publication lineage, not a physical application interface.</data></edge><edge id="R72_REL015" source="PROC_MSP_OUTREACH" target="NOTICE_MSP_L447"><data key="edge_relationship_id">R72_REL015</data><data key="edge_source_entity_id">PROC_MSP_OUTREACH</data><data key="edge_relationship_type">produces_notice</data><data key="edge_target_entity_id">NOTICE_MSP_L447</data><data key="edge_operational_context">SSA annually mails L447 as part of statutory low-income Medicare outreach.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL016" source="PROC_MSP_OUTREACH" target="NOTICE_MSP_L448"><data key="edge_relationship_id">R72_REL016</data><data key="edge_source_entity_id">PROC_MSP_OUTREACH</data><data key="edge_relationship_type">produces_notice</data><data key="edge_target_entity_id">NOTICE_MSP_L448</data><data key="edge_operational_context">SSA annually mails L448 as part of statutory low-income Medicare outreach.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL017" source="DATA_MSP_L447_MAILINGS" target="NOTICE_MSP_L447"><data key="edge_relationship_id">R72_REL017</data><data key="edge_source_entity_id">DATA_MSP_L447_MAILINGS</data><data key="edge_relationship_type">summarizes</data><data key="edge_target_entity_id">NOTICE_MSP_L447</data><data key="edge_operational_context">Open Data product reports annual counts of L447 notices mailed by ZIP code.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL018" source="DATA_MSP_L448_MAILINGS" target="NOTICE_MSP_L448"><data key="edge_relationship_id">R72_REL018</data><data key="edge_source_entity_id">DATA_MSP_L448_MAILINGS</data><data key="edge_relationship_type">summarizes</data><data key="edge_target_entity_id">NOTICE_MSP_L448</data><data key="edge_operational_context">Open Data product reports annual counts of L448 notices mailed by ZIP code.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL019" source="DATA_MSP_L447_MAILINGS" target="PROC_MSP_OUTREACH"><data key="edge_relationship_id">R72_REL019</data><data key="edge_source_entity_id">DATA_MSP_L447_MAILINGS</data><data key="edge_relationship_type">derived_from_process</data><data key="edge_target_entity_id">PROC_MSP_OUTREACH</data><data key="edge_operational_context">Dataset is produced from annual MSP/Extra Help outreach mailings.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL020" source="DATA_MSP_L448_MAILINGS" target="PROC_MSP_OUTREACH"><data key="edge_relationship_id">R72_REL020</data><data key="edge_source_entity_id">DATA_MSP_L448_MAILINGS</data><data key="edge_relationship_type">derived_from_process</data><data key="edge_target_entity_id">PROC_MSP_OUTREACH</data><data key="edge_operational_context">Dataset is produced from annual MSP/Extra Help outreach mailings.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL021" source="FORM_SSA3105" target="PROC_T2_OVERPAY_EXPL"><data key="edge_relationship_id">R72_REL021</data><data key="edge_source_entity_id">FORM_SSA3105</data><data key="edge_relationship_type">historically_supported_request_for</data><data key="edge_target_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_operational_context">Historical SSA-3105 allowed an overpaid person to request an explanation of the overpayment.</data><data key="edge_observed_as_of">2025-01</data><data key="edge_confidence">5</data><data key="edge_notes">Historical relationship only. Current 2026 notice policy and forms index do not establish continued SSA-3105 use.</data></edge><edge id="R72_REL022" source="PROC_T2_OVERPAY_EXPL" target="UI_DMS_RMKS"><data key="edge_relationship_id">R72_REL022</data><data key="edge_source_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_relationship_type">documents_in</data><data key="edge_target_entity_id">UI_DMS_RMKS</data><data key="edge_operational_context">Current POMS requires a detailed explanation, date, office code, employee identifier, and debtor decision in DMS Remarks.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL023" source="PROC_T2_OVERPAY_EXPL" target="IFACE_DRPR"><data key="edge_relationship_id">R72_REL023</data><data key="edge_source_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_relationship_type">stops_recovery_via</data><data key="edge_target_entity_id">IFACE_DRPR</data><data key="edge_operational_context">PSC uses DRPR with the explanation protest reason to stop recovery when applicable.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL024" source="PROC_T2_OVERPAY_EXPL" target="IFACE_DRPF"><data key="edge_relationship_id">R72_REL024</data><data key="edge_source_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_relationship_type">codes_fo_request_via</data><data key="edge_target_entity_id">IFACE_DRPF</data><data key="edge_operational_context">FO uses DRPF to suspend collection or code the requested protest when an explanation requires PSC action.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL025" source="PROC_T2_OVERPAY_EXPL" target="UI_DMS_DMFS"><data key="edge_relationship_id">R72_REL025</data><data key="edge_source_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_relationship_type">routes_to_psc_via</data><data key="edge_target_entity_id">UI_DMS_DMFS</data><data key="edge_operational_context">POMS directs FO to transfer WMS jurisdiction using the DMFS screen in DMS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL026" source="PROC_T2_OVERPAY_EXPL" target="APP_WMS"><data key="edge_relationship_id">R72_REL026</data><data key="edge_source_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_relationship_type">transfers_workload_in</data><data key="edge_target_entity_id">APP_WMS</data><data key="edge_operational_context">Current POMS requires transferring WMS jurisdiction for explanation protest requests to the servicing PSC.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">WMS remains separate from newer WLM because equivalence is not established.</data></edge><edge id="R72_REL027" source="APP_SSI_VA_INTERFACE" target="DATA_VA_SSI_ADDRESS"><data key="edge_relationship_id">R72_REL027</data><data key="edge_source_entity_id">APP_SSI_VA_INTERFACE</data><data key="edge_relationship_type">carries_address_attribute</data><data key="edge_target_entity_id">DATA_VA_SSI_ADDRESS</data><data key="edge_operational_context">Current POMS VA extract includes foreign-address indicator, address type, 500-byte address data, and ZIP code.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic SSA master-address write-back is documented.</data></edge><edge id="R72_REL028" source="APP_SSI_DOD_INTERFACE" target="DATA_DOD_SSI_ADDRESS"><data key="edge_relationship_id">R72_REL028</data><data key="edge_source_entity_id">APP_SSI_DOD_INTERFACE</data><data key="edge_relationship_type">carries_address_attribute</data><data key="edge_target_entity_id">DATA_DOD_SSI_ADDRESS</data><data key="edge_operational_context">Current POMS DOD extract includes beneficiary address and ZIP; legend identifies DOD as source.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic SSA master-address write-back is documented.</data></edge><edge id="R72_REL029" source="APP_SSI_RRB_INTERFACE" target="DATA_RRB_SSI_ADDRESS"><data key="edge_relationship_id">R72_REL029</data><data key="edge_source_entity_id">APP_SSI_RRB_INTERFACE</data><data key="edge_relationship_type">carries_address_attribute</data><data key="edge_target_entity_id">DATA_RRB_SSI_ADDRESS</data><data key="edge_operational_context">Current POMS RRB record format includes ZIP CODE and ADDR fields.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">No automatic SSA master-address write-back is documented.</data></edge><edge id="R72_REL030" source="DATA_MSP_L447_MAILINGS" target="PORTAL_SSA_OPEN_DATA"><data key="edge_relationship_id">R72_REL030</data><data key="edge_source_entity_id">DATA_MSP_L447_MAILINGS</data><data key="edge_relationship_type">published_via</data><data key="edge_target_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_operational_context">SSA publishes the L447 mailing dataset on its Open Data site.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R72_REL031" source="DATA_MSP_L448_MAILINGS" target="PORTAL_SSA_OPEN_DATA"><data key="edge_relationship_id">R72_REL031</data><data key="edge_source_entity_id">DATA_MSP_L448_MAILINGS</data><data key="edge_relationship_type">published_via</data><data key="edge_target_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_operational_context">SSA publishes the L448 mailing dataset on its Open Data site.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R73_REL001" source="PROC_SSI_TRUST_REVIEW" target="APP_SSITMS"><data key="edge_relationship_id">R73_REL001</data><data key="edge_source_entity_id">PROC_SSI_TRUST_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_SSITMS</data><data key="edge_operational_context">Claims Specialists submit trust determinations and RTRT decisions/feedback are communicated through SSITMS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL002" source="ORG_RTRT" target="PROC_SSI_TRUST_REVIEW"><data key="edge_relationship_id">R73_REL002</data><data key="edge_source_entity_id">ORG_RTRT</data><data key="edge_relationship_type">performs_review_for</data><data key="edge_target_entity_id">PROC_SSI_TRUST_REVIEW</data><data key="edge_operational_context">RTRT reviews SSI trust resource determinations submitted by field-office Claims Specialists.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL003" source="APP_SSITMS" target="ORG_RTRT"><data key="edge_relationship_id">R73_REL003</data><data key="edge_source_entity_id">APP_SSITMS</data><data key="edge_relationship_type">routes_trust_determinations_to</data><data key="edge_target_entity_id">ORG_RTRT</data><data key="edge_operational_context">SSITMS is the internal submission and response path for RTRT review.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL004" source="PROC_SSI_TRUST_REVIEW" target="APP_EP"><data key="edge_relationship_id">R73_REL004</data><data key="edge_source_entity_id">PROC_SSI_TRUST_REVIEW</data><data key="edge_relationship_type">uses_evidence_from</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Trust determinations and related documents are uploaded to and reviewed through the Evidence Portal.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL005" source="PROC_SSI_TRUST_REVIEW" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R73_REL005</data><data key="edge_source_entity_id">PROC_SSI_TRUST_REVIEW</data><data key="edge_relationship_type">uses_case_information_from</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current trust-review POMS directs reviewers to information documented in the SSI Claims System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL006" source="APP_SSITMS" target="DATA_SSITMS_TRUST_CASE"><data key="edge_relationship_id">R73_REL006</data><data key="edge_source_entity_id">APP_SSITMS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_SSITMS_TRUST_CASE</data><data key="edge_operational_context">POMS identifies claimant/recipient name, representative payee name when applicable, SSN, trust type, remarks, statuses, and results in the SSITMS case.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL007" source="ORG_RTRT" target="REPO_SSITMS_PRECEDENTS"><data key="edge_relationship_id">R73_REL007</data><data key="edge_source_entity_id">ORG_RTRT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">REPO_SSITMS_PRECEDENTS</data><data key="edge_operational_context">Regional Trust Leads add and update pooled/IGRA trust precedents in the SSITMS precedent repository.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL008" source="REPO_SSITMS_PRECEDENTS" target="PLAT_SHAREPOINT"><data key="edge_relationship_id">R73_REL008</data><data key="edge_source_entity_id">REPO_SSITMS_PRECEDENTS</data><data key="edge_relationship_type">implemented_on</data><data key="edge_target_entity_id">PLAT_SHAREPOINT</data><data key="edge_operational_context">POMS explicitly calls this the SSITMS SharePoint Repository/Site for Precedents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL009" source="APP_SSITMS" target="REPO_SSITMS_PRECEDENTS"><data key="edge_relationship_id">R73_REL009</data><data key="edge_source_entity_id">APP_SSITMS</data><data key="edge_relationship_type">links_to</data><data key="edge_target_entity_id">REPO_SSITMS_PRECEDENTS</data><data key="edge_operational_context">The SSITMS Help link provides access to the SharePoint precedent repository.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL010" source="ORG_OPLAW" target="REPO_SSITMS_PRECEDENTS"><data key="edge_relationship_id">R73_REL010</data><data key="edge_source_entity_id">ORG_OPLAW</data><data key="edge_relationship_type">provides_legal_evaluations_for</data><data key="edge_target_entity_id">REPO_SSITMS_PRECEDENTS</data><data key="edge_operational_context">Regional Trust Leads consult OPLaw before establishing/updating pooled-trust precedents; written evaluations are stored with precedent materials.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL011" source="APP_NAPR" target="DATA_NAPR_PRECEDENTS"><data key="edge_relationship_id">R73_REL011</data><data key="edge_source_entity_id">APP_NAPR</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NAPR_PRECEDENTS</data><data key="edge_operational_context">NAPR stores Tribal income/resource precedents, references, and decision-tree guidance.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL012" source="APP_NAPR" target="PLAT_SHAREPOINT"><data key="edge_relationship_id">R73_REL012</data><data key="edge_source_entity_id">APP_NAPR</data><data key="edge_relationship_type">implemented_as_internal_site_on</data><data key="edge_target_entity_id">PLAT_SHAREPOINT</data><data key="edge_operational_context">Current POMS links NAPR through the socialsecuritygov.sharepoint.com domain.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Platform observation is limited to the authoritative internal link target; no database technology is inferred.</data></edge><edge id="R73_REL013" source="APP_NAPA" target="APP_NAPR"><data key="edge_relationship_id">R73_REL013</data><data key="edge_source_entity_id">APP_NAPA</data><data key="edge_relationship_type">replaced_by</data><data key="edge_target_entity_id">APP_NAPR</data><data key="edge_operational_context">NAPR replaced NAPA as the repository for Tribal benefit precedents; NAPA was decommissioned in January 2023.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL014" source="APP_NAPA" target="DATA_NAPR_PRECEDENTS"><data key="edge_relationship_id">R73_REL014</data><data key="edge_source_entity_id">APP_NAPA</data><data key="edge_relationship_type">precedents_transferred_to</data><data key="edge_target_entity_id">DATA_NAPR_PRECEDENTS</data><data key="edge_operational_context">All precedents formerly stored in NAPA were transferred into NAPR.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship describes migration of precedent content, not continued NAPA operation.</data></edge><edge id="R73_REL015" source="APP_NAPR" target="APP_SSITMS"><data key="edge_relationship_id">R73_REL015</data><data key="edge_source_entity_id">APP_NAPR</data><data key="edge_relationship_type">routes_tribal_trust_precedents_to</data><data key="edge_target_entity_id">APP_SSITMS</data><data key="edge_operational_context">POMS directs Tribal trust precedent information to SSITMS rather than the general NAPR precedent workflow.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL016" source="APP_NAPR" target="APP_CCE"><data key="edge_relationship_id">R73_REL016</data><data key="edge_source_entity_id">APP_NAPR</data><data key="edge_relationship_type">provides_precedent_guidance_for_documentation_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Current POMS directs technicians to document Tribal income/resource treatment in a CCE Report of Contact based on NAPR precedent guidance.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL017" source="PROC_PERC" target="APP_MSSICS"><data key="edge_relationship_id">R73_REL017</data><data key="edge_source_entity_id">PROC_PERC</data><data key="edge_relationship_type">processed_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS provides MSSICS processing paths for PERCs.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL018" source="UI_MSSICS_PERC" target="APP_MSSICS"><data key="edge_relationship_id">R73_REL018</data><data key="edge_source_entity_id">UI_MSSICS_PERC</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Preeffectuation Review Contact page is a named MSSICS page.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL019" source="UI_MSSICS_DSSR" target="APP_MSSICS"><data key="edge_relationship_id">R73_REL019</data><data key="edge_source_entity_id">UI_MSSICS_DSSR</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">DSSR is a named MSSICS screen used during PERC processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL020" source="UI_MSSICS_DADJ" target="APP_MSSICS"><data key="edge_relationship_id">R73_REL020</data><data key="edge_source_entity_id">UI_MSSICS_DADJ</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">DADJ is a named MSSICS screen used during PERC processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL021" source="PROC_PERC" target="UI_MSSICS_PERC"><data key="edge_relationship_id">R73_REL021</data><data key="edge_source_entity_id">PROC_PERC</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MSSICS_PERC</data><data key="edge_operational_context">MSSICS PERC processing uses the Preeffectuation Review Contact page; limited cases select WITH EXCLUSION.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL022" source="PROC_PERC" target="UI_MSSICS_DSSR"><data key="edge_relationship_id">R73_REL022</data><data key="edge_source_entity_id">PROC_PERC</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MSSICS_DSSR</data><data key="edge_operational_context">POMS directs entry to close the open event on DSSR during PERC processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL023" source="PROC_PERC" target="UI_MSSICS_DADJ"><data key="edge_relationship_id">R73_REL023</data><data key="edge_source_entity_id">PROC_PERC</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MSSICS_DADJ</data><data key="edge_operational_context">POMS directs entry of the initial claim decision on DADJ during PERC processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL024" source="FORM_SSA8000BK" target="PROC_PERC"><data key="edge_relationship_id">R73_REL024</data><data key="edge_source_entity_id">FORM_SSA8000BK</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_PERC</data><data key="edge_operational_context">Current POMS uses SSA-8000-BK in full/deferred PERC development when required.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL025" source="FORM_SSA8010BK" target="PROC_PERC"><data key="edge_relationship_id">R73_REL025</data><data key="edge_source_entity_id">FORM_SSA8010BK</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_PERC</data><data key="edge_operational_context">Current POMS uses SSA-8010-BK for income/resource development in specified PERC workflows.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL026" source="PROC_PERC" target="SYS_SSR"><data key="edge_relationship_id">R73_REL026</data><data key="edge_source_entity_id">PROC_PERC</data><data key="edge_relationship_type">can_result_in_build_or_update_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">In the documented age-18 financial-permission workflow, PERC completion precedes SSA-450-SI input that builds the SSR with specified payment status.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Case-specific update path; not asserted for every PERC.</data></edge><edge id="R73_REL027" source="UI_MCS_DICL" target="APP_MCS"><data key="edge_relationship_id">R73_REL027</data><data key="edge_source_entity_id">UI_MCS_DICL</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">DICL is explicitly identified as the MCS Disability Allowance/Denial screen.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL028" source="ORG_DDS" target="UI_MCS_DICL"><data key="edge_relationship_id">R73_REL028</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">determination_data_propagates_to</data><data key="edge_target_entity_id">UI_MCS_DICL</data><data key="edge_operational_context">Current POMS says DDS statutory-blind determination data propagates to the MCS DICL screen.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL029" source="FORM_SSA2935" target="PROC_EFORM_EXTRA_IDV"><data key="edge_relationship_id">R73_REL029</data><data key="edge_source_entity_id">FORM_SSA2935</data><data key="edge_relationship_type">requires_for_electronic_submission</data><data key="edge_target_entity_id">PROC_EFORM_EXTRA_IDV</data><data key="edge_operational_context">SSA Forms identifies this form as requiring additional identity verification for electronic submission.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL030" source="FORM_SSA8510" target="PROC_EFORM_EXTRA_IDV"><data key="edge_relationship_id">R73_REL030</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">requires_for_electronic_submission</data><data key="edge_target_entity_id">PROC_EFORM_EXTRA_IDV</data><data key="edge_operational_context">SSA Forms identifies this form as requiring additional identity verification for electronic submission.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL031" source="FORM_SSA454BK" target="PROC_EFORM_EXTRA_IDV"><data key="edge_relationship_id">R73_REL031</data><data key="edge_source_entity_id">FORM_SSA454BK</data><data key="edge_relationship_type">requires_for_electronic_submission</data><data key="edge_target_entity_id">PROC_EFORM_EXTRA_IDV</data><data key="edge_operational_context">SSA Forms identifies this form as requiring additional identity verification for electronic submission.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL032" source="FORM_SSA827" target="PROC_EFORM_EXTRA_IDV"><data key="edge_relationship_id">R73_REL032</data><data key="edge_source_entity_id">FORM_SSA827</data><data key="edge_relationship_type">requires_for_electronic_submission</data><data key="edge_target_entity_id">PROC_EFORM_EXTRA_IDV</data><data key="edge_operational_context">SSA Forms identifies this form as requiring additional identity verification for electronic submission.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL033" source="FORM_SSA_2574" target="PROC_EFORM_EXTRA_IDV"><data key="edge_relationship_id">R73_REL033</data><data key="edge_source_entity_id">FORM_SSA_2574</data><data key="edge_relationship_type">requires_for_electronic_submission</data><data key="edge_target_entity_id">PROC_EFORM_EXTRA_IDV</data><data key="edge_operational_context">SSA Forms identifies this form as requiring additional identity verification for electronic submission.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL034" source="APP_OSSNAP" target="APP_RACEETH"><data key="edge_relationship_id">R73_REL034</data><data key="edge_source_entity_id">APP_OSSNAP</data><data key="edge_relationship_type">captures_voluntary_race_ethnicity_for</data><data key="edge_target_entity_id">APP_RACEETH</data><data key="edge_operational_context">Current SSN-card application policy requires provided race/ethnicity responses to be recorded in SSNAP; RECS is the dedicated race/ethnicity system of records.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">The public sources establish capture in SSNAP and storage in RECS but do not describe the physical interface mechanism.</data></edge><edge id="R73_REL035" source="APP_RACEETH" target="DATA_RECS_SOURCE_INDICATOR"><data key="edge_relationship_id">R73_REL035</data><data key="edge_source_entity_id">APP_RACEETH</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_RECS_SOURCE_INDICATOR</data><data key="edge_operational_context">The 2025 RECS SORN lists a source-indicator code as part of the record.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL036" source="DATA_RECS_SOURCE_INDICATOR" target="EX_EAB"><data key="edge_relationship_id">R73_REL036</data><data key="edge_source_entity_id">DATA_RECS_SOURCE_INDICATOR</data><data key="edge_relationship_type">can_identify_source_as</data><data key="edge_target_entity_id">EX_EAB</data><data key="edge_operational_context">The 2025 SORN gives Enumeration at Birth as an example value for the data-source indicator.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL037" source="SYS_NUMIDENT" target="APP_RACEETH"><data key="edge_relationship_id">R73_REL037</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">serves_as_record_source_for</data><data key="edge_target_entity_id">APP_RACEETH</data><data key="edge_operational_context">The 2025 SORN identifies the Master Files of SSN Holders and SSN Applications as a record source for RECS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Mapped to Numident as the Atlas identity/master record concept; the SORN names the system of records rather than a specific transport or physical table.</data></edge><edge id="R73_REL038" source="PROC_SYSTEM_INFO_AS_PROOF" target="APP_MCS"><data key="edge_relationship_id">R73_REL038</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">can_use_as_acceptable_proof_source</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Current POMS permits information in this system to serve as acceptable proof for specified entitlement factors when policy conditions are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL039" source="PROC_SYSTEM_INFO_AS_PROOF" target="APP_MSSICS"><data key="edge_relationship_id">R73_REL039</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">can_use_as_acceptable_proof_source</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS permits information in this system to serve as acceptable proof for specified entitlement factors when policy conditions are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL040" source="PROC_SYSTEM_INFO_AS_PROOF" target="SYS_MBR"><data key="edge_relationship_id">R73_REL040</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">can_use_as_acceptable_proof_source</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS permits information in this system to serve as acceptable proof for specified entitlement factors when policy conditions are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL041" source="PROC_SYSTEM_INFO_AS_PROOF" target="SYS_SSR"><data key="edge_relationship_id">R73_REL041</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">can_use_as_acceptable_proof_source</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS permits information in this system to serve as acceptable proof for specified entitlement factors when policy conditions are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL042" source="PROC_SYSTEM_INFO_AS_PROOF" target="SYS_NUMIDENT"><data key="edge_relationship_id">R73_REL042</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">can_use_as_acceptable_proof_source</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS permits information in this system to serve as acceptable proof for specified entitlement factors when policy conditions are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL043" source="PROC_SYSTEM_INFO_AS_PROOF" target="APP_DRAMS"><data key="edge_relationship_id">R73_REL043</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">can_use_as_acceptable_proof_source</data><data key="edge_target_entity_id">APP_DRAMS</data><data key="edge_operational_context">Current POMS permits information in this system to serve as acceptable proof for specified entitlement factors when policy conditions are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL044" source="PROC_SYSTEM_INFO_AS_PROOF" target="APP_EVID"><data key="edge_relationship_id">R73_REL044</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">can_use_as_acceptable_proof_source</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Current POMS permits information in this system to serve as acceptable proof for specified entitlement factors when policy conditions are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL045" source="PROC_SYSTEM_INFO_AS_PROOF" target="APP_EP"><data key="edge_relationship_id">R73_REL045</data><data key="edge_source_entity_id">PROC_SYSTEM_INFO_AS_PROOF</data><data key="edge_relationship_type">can_use_as_acceptable_proof_source</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Current POMS permits information in this system to serve as acceptable proof for specified entitlement factors when policy conditions are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL046" source="SYS_NUMIDENT" target="DATA_NUMIDENT_SPIN6"><data key="edge_relationship_id">R73_REL046</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_NUMIDENT_SPIN6</data><data key="edge_operational_context">Current POMS states HALE-issued SSNs carry special indicator 6 on the Numident record.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL047" source="PROC_HALE_NEW_SSN_DISABILITY" target="SYS_NUMIDENT"><data key="edge_relationship_id">R73_REL047</data><data key="edge_source_entity_id">PROC_HALE_NEW_SSN_DISABILITY</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">The new-SSN disability workflow reviews Numident SPIN/cross-reference information and the reason for the SSN change.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL048" source="PROC_HALE_NEW_SSN_DISABILITY" target="APP_EDCS"><data key="edge_relationship_id">R73_REL048</data><data key="edge_source_entity_id">PROC_HALE_NEW_SSN_DISABILITY</data><data key="edge_relationship_type">uses_with_exception_handling</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Current POMS describes EDCS processing for new-SSN disability claims and identifies cases that must become EDCS exclusions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL049" source="APP_EDCS" target="PROC_HALE_NEW_SSN_DISABILITY"><data key="edge_relationship_id">R73_REL049</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">cannot_associate_former_and_new_ssn_claims_in</data><data key="edge_target_entity_id">PROC_HALE_NEW_SSN_DISABILITY</data><data key="edge_operational_context">POMS states EDCS cannot associate a claim under the former SSN with a new claim/appeal under the newly issued SSN.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL050" source="PROC_HALE_NEW_SSN_DISABILITY" target="REPO_PAPER_DISABILITY_FOLDER"><data key="edge_relationship_id">R73_REL050</data><data key="edge_source_entity_id">PROC_HALE_NEW_SSN_DISABILITY</data><data key="edge_relationship_type">converts_case_to</data><data key="edge_target_entity_id">REPO_PAPER_DISABILITY_FOLDER</data><data key="edge_operational_context">When a prior filing exists under the former SSN in specified cases, POMS requires conversion to a paper folder and printing electronic documents into it.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL051" source="PROC_HALE_NEW_SSN_DISABILITY" target="DATA_HALE_SECURE_MAIL_ADDR"><data key="edge_relationship_id">R73_REL051</data><data key="edge_source_entity_id">PROC_HALE_NEW_SSN_DISABILITY</data><data key="edge_relationship_type">confirms</data><data key="edge_target_entity_id">DATA_HALE_SECURE_MAIL_ADDR</data><data key="edge_operational_context">For HALE cases, FO staff verify that the mailing address provided by the claimant is secure for notices.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R73_REL052" source="DATA_HALE_SECURE_MAIL_ADDR" target="PROC_FO_ADDRESS_AS_MAILING"><data key="edge_relationship_id">R73_REL052</data><data key="edge_source_entity_id">DATA_HALE_SECURE_MAIL_ADDR</data><data key="edge_relationship_type">can_fall_back_to</data><data key="edge_target_entity_id">PROC_FO_ADDRESS_AS_MAILING</data><data key="edge_operational_context">If the claimant lacks a secure address, current POMS directs staff to consider the existing field-office-address-as-mailing procedure.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">This is an operational fallback, not an automatic master-address update.</data></edge><edge id="R74_REL001" source="DB_CLAIMS_FOLDERS_SYSTEM" target="DB_HA_CASE_CONTROL_RECORDS"><data key="edge_relationship_id">R74_REL001</data><data key="edge_source_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_operational_context">SORN 60-0009 identifies Claims Folders System records among sources for case-control records.</data><data key="edge_observed_as_of">2026-01-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL002" source="DB_EDIB_CLAIM_FILE" target="DB_HA_CASE_CONTROL_RECORDS"><data key="edge_relationship_id">R74_REL002</data><data key="edge_source_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_operational_context">SORN 60-0009 identifies Electronic Disability Claim File records among sources for case-control records.</data><data key="edge_observed_as_of">2026-01-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL003" source="DB_APPOINTED_REP" target="DB_HA_CASE_CONTROL_RECORDS"><data key="edge_relationship_id">R74_REL003</data><data key="edge_source_entity_id">DB_APPOINTED_REP</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_operational_context">SORN 60-0009 identifies Appointed Representative File records among sources for case-control records.</data><data key="edge_observed_as_of">2026-01-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL004" source="SYS_HOTS_RECORDS" target="DB_HA_CASE_CONTROL_RECORDS"><data key="edge_relationship_id">R74_REL004</data><data key="edge_source_entity_id">SYS_HOTS_RECORDS</data><data key="edge_relationship_type">records_combined_into</data><data key="edge_target_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_operational_context">April 20, 2026 rescindment says 60-0010 records will be combined and managed through 60-0009.</data><data key="edge_observed_as_of">2026-04-20</data><data key="edge_confidence">5</data><data key="edge_notes">Records-governance consolidation; migration mechanism not stated.</data></edge><edge id="R74_REL005" source="DB_ALJ_WORKING_FILE" target="REPO_EVIEW_PRIVATE_SECTION"><data key="edge_relationship_id">R74_REL005</data><data key="edge_source_entity_id">DB_ALJ_WORKING_FILE</data><data key="edge_relationship_type">electronically_maintained_and_viewed_in</data><data key="edge_target_entity_id">REPO_EVIEW_PRIVATE_SECTION</data><data key="edge_operational_context">60-0005 states electronic ALJ working-file documents are gathered, maintained, and viewed in the Private Section of eView.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL006" source="REPO_EVIEW_PRIVATE_SECTION" target="APP_EVIEW"><data key="edge_relationship_id">R74_REL006</data><data key="edge_source_entity_id">REPO_EVIEW_PRIVATE_SECTION</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">The SORN describes the Private Section as a restricted section of eView.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL007" source="DB_ALJ_WORKING_FILE" target="DB_CLAIMS_FOLDERS_SYSTEM"><data key="edge_relationship_id">R74_REL007</data><data key="edge_source_entity_id">DB_ALJ_WORKING_FILE</data><data key="edge_relationship_type">official_copies_placed_in</data><data key="edge_target_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="edge_operational_context">60-0005 states official copies of working-file materials are placed in claim folders.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes">Logical claim-folder relationship; exact eFolder/paper routing varies by case.</data></edge><edge id="R74_REL008" source="DB_AC_WORKING_FILE" target="REPO_EVIEW_PRIVATE_SECTION"><data key="edge_relationship_id">R74_REL008</data><data key="edge_source_entity_id">DB_AC_WORKING_FILE</data><data key="edge_relationship_type">electronically_maintained_and_viewed_in</data><data key="edge_target_entity_id">REPO_EVIEW_PRIVATE_SECTION</data><data key="edge_operational_context">60-0004 states electronic Appeals Council working-file documents are gathered, maintained, and viewed in the Private Section of eView.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL009" source="DB_AC_WORKING_FILE" target="DATA_HEARING_TRANSCRIPT"><data key="edge_relationship_id">R74_REL009</data><data key="edge_source_entity_id">DB_AC_WORKING_FILE</data><data key="edge_relationship_type">may_contain_copy_of</data><data key="edge_target_entity_id">DATA_HEARING_TRANSCRIPT</data><data key="edge_operational_context">60-0004 says the Appeals Council working file may contain copies of transcripts when available.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL010" source="DATA_HEARING_RECORDING" target="DATA_HEARING_TRANSCRIPT"><data key="edge_relationship_id">R74_REL010</data><data key="edge_source_entity_id">DATA_HEARING_RECORDING</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_HEARING_TRANSCRIPT</data><data key="edge_operational_context">60-0006 says the hearing recording is the basic hearing record and the source from which the documentary transcript is prepared.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL011" source="DB_OHO_EXPERT_AVAIL" target="DATA_OHO_EXPERT_BUS_ADDRESS"><data key="edge_relationship_id">R74_REL011</data><data key="edge_source_entity_id">DB_OHO_EXPERT_AVAIL</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_OHO_EXPERT_BUS_ADDRESS</data><data key="edge_operational_context">60-0012 explicitly includes business address(es) for covered experts and reporters.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL012" source="DB_OHO_EXPERT_AVAIL" target="PROC_OHO_VE_BPA"><data key="edge_relationship_id">R74_REL012</data><data key="edge_source_entity_id">DB_OHO_EXPERT_AVAIL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_OHO_VE_BPA</data><data key="edge_operational_context">60-0012 is used for BPA administration, availability, scheduling, usage assessment, renewals, invoices and related expert/reporter management.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Current SSA VE page separately confirms VE services continue under BPAs.</data></edge><edge id="R74_REL013" source="DB_OHO_EXPERT_AVAIL" target="DB_OHO_EXPERT_USAGE"><data key="edge_relationship_id">R74_REL013</data><data key="edge_source_entity_id">DB_OHO_EXPERT_AVAIL</data><data key="edge_relationship_type">contains_usage_information_overlapping</data><data key="edge_target_entity_id">DB_OHO_EXPERT_USAGE</data><data key="edge_operational_context">60-0012 says it contains usage records while 60-0013 separately governs expert usage records.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Exact physical overlap, duplication, synchronization, or consolidation is not established.</data></edge><edge id="R74_REL014" source="DB_OHO_EXPERT_USAGE" target="PROC_OHO_VE_BPA"><data key="edge_relationship_id">R74_REL014</data><data key="edge_source_entity_id">DB_OHO_EXPERT_USAGE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_OHO_VE_BPA</data><data key="edge_operational_context">60-0013 uses expert usage information for contract/BPA renewal and statistical/summary reporting.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL015" source="APP_ERE_EXPERTS" target="DB_EDIB_CLAIM_FILE"><data key="edge_relationship_id">R74_REL015</data><data key="edge_source_entity_id">APP_ERE_EXPERTS</data><data key="edge_relationship_type">provides_assigned_case_access_to</data><data key="edge_target_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_operational_context">ERE for Experts gives authorized experts access to exhibited documents in assigned claimant eFolders.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Modeled at eFolder/eDIB logical data-store level; exact current service interface is not inferred.</data></edge><edge id="R74_REL016" source="APP_ERE_EXPERTS" target="DB_ERE_EXPERT_ADMIN"><data key="edge_relationship_id">R74_REL016</data><data key="edge_source_entity_id">APP_ERE_EXPERTS</data><data key="edge_relationship_type">uses_authorization_table</data><data key="edge_target_entity_id">DB_ERE_EXPERT_ADMIN</data><data key="edge_operational_context">Current ERE for Experts FAQ says the expert authorization SSN is housed only in the restricted Admin Table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL017" source="DB_ERE_EXPERT_ADMIN" target="DATA_ERE_EXPERT_AUTH_SSN"><data key="edge_relationship_id">R74_REL017</data><data key="edge_source_entity_id">DB_ERE_EXPERT_ADMIN</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_ERE_EXPERT_AUTH_SSN</data><data key="edge_operational_context">Current ERE for Experts FAQ says expert SSN is housed only in the Admin Table and used for authentication/authorization.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL018" source="APP_ERE_EXPERTS" target="APP_CPMS"><data key="edge_relationship_id">R74_REL018</data><data key="edge_source_entity_id">APP_ERE_EXPERTS</data><data key="edge_relationship_type">documentation_names_authorization_dependency_on</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Current live ERE page says access compares ERE account SSN to expert assignment SSN in CPMS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">3</data><data key="edge_notes">Conflict: CPMS is independently documented as retired September 26, 2025. Current post-retirement backing assignment mechanism is unresolved; do not treat this as proof CPMS remains active.</data></edge><edge id="R74_REL019" source="APP_ERE_EXPERTS" target="APP_HACPS"><data key="edge_relationship_id">R74_REL019</data><data key="edge_source_entity_id">APP_ERE_EXPERTS</data><data key="edge_relationship_type">status_reports_include_cases_from</data><data key="edge_target_entity_id">APP_HACPS</data><data key="edge_operational_context">March 27, 2021 ERE release added HACPS cases to expert status reports.</data><data key="edge_observed_as_of">2021-03-27</data><data key="edge_confidence">5</data><data key="edge_notes">Current persistence of the exact implementation is not separately confirmed.</data></edge><edge id="R74_REL020" source="APP_ERE_EXPERTS" target="DATA_ERE_EXPERT_RESUME"><data key="edge_relationship_id">R74_REL020</data><data key="edge_source_entity_id">APP_ERE_EXPERTS</data><data key="edge_relationship_type">accepts_upload</data><data key="edge_target_entity_id">DATA_ERE_EXPERT_RESUME</data><data key="edge_operational_context">December 9, 2016 release added expert resume/CV upload.</data><data key="edge_observed_as_of">2016-12-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL021" source="DATA_ERE_EXPERT_RESUME" target="DB_EDIB_CLAIM_FILE"><data key="edge_relationship_id">R74_REL021</data><data key="edge_source_entity_id">DATA_ERE_EXPERT_RESUME</data><data key="edge_relationship_type">uploaded_to</data><data key="edge_target_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_operational_context">2016 release says the CV/resume can be uploaded to an eFolder.</data><data key="edge_observed_as_of">2016-12-09</data><data key="edge_confidence">5</data><data key="edge_notes">Logical eFolder relationship; no inference to SORN 60-0014 physical storage.</data></edge><edge id="R74_REL022" source="APP_ERE_EXPERTS" target="DATA_ERE_EXPERT_STATUS_REPORT"><data key="edge_relationship_id">R74_REL022</data><data key="edge_source_entity_id">APP_ERE_EXPERTS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_ERE_EXPERT_STATUS_REPORT</data><data key="edge_operational_context">ERE for Experts offers downloadable/viewable assigned-case status reports.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL023" source="APP_ALJ_MISCONDUCT" target="DATA_ALJ_PAMC_ADDRESS"><data key="edge_relationship_id">R74_REL023</data><data key="edge_source_entity_id">APP_ALJ_MISCONDUCT</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_ALJ_PAMC_ADDRESS</data><data key="edge_operational_context">2025 PIA says ALJ/PAMC collects and maintains claimant address when provided and relevant to complaint.</data><data key="edge_observed_as_of">2025-02-11</data><data key="edge_confidence">5</data><data key="edge_notes">No master-address propagation established.</data></edge><edge id="R74_REL024" source="ORG_SSA_OCACT" target="REPORT_OACT_ECONOMIC_2026"><data key="edge_relationship_id">R74_REL024</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">REPORT_OACT_ECONOMIC_2026</data><data key="edge_operational_context">OCACT published the long-range economic assumptions memorandum supporting the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-06-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL025" source="REPORT_OACT_ECONOMIC_2026" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R74_REL025</data><data key="edge_source_entity_id">REPORT_OACT_ECONOMIC_2026</data><data key="edge_relationship_type">documents_assumptions_for</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Memorandum documents long-range economic assumptions used in the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-06-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL026" source="ORG_SSA_OCACT" target="DATA_OACT_PRINC_ECON_2026"><data key="edge_relationship_id">R74_REL026</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_PRINC_ECON_2026</data><data key="edge_operational_context">OCACT publishes Table V.B1 as a public 2026 Trustees Report data table.</data><data key="edge_observed_as_of">2026-06-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R74_REL027" source="DATA_OACT_PRINC_ECON_2026" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R74_REL027</data><data key="edge_source_entity_id">DATA_OACT_PRINC_ECON_2026</data><data key="edge_relationship_type">table_for</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Table V.B1 is part of the 2026 OASDI Trustees Report economic assumptions/data products.</data><data key="edge_observed_as_of">2026-06-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL001" source="SYS_NUMIDENT" target="DB_APPT_VISITOR_CUSTOMER_RECORD"><data key="edge_relationship_id">R75_REL001</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_operational_context">60-0350 identifies Master Files of SSN Holders and SSN Applications among source record systems.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL002" source="DB_CLAIMS_FOLDERS_SYSTEM" target="DB_APPT_VISITOR_CUSTOMER_RECORD"><data key="edge_relationship_id">R75_REL002</data><data key="edge_source_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_operational_context">60-0350 identifies Claims Folders System among source record systems.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL003" source="SYS_MBR" target="DB_APPT_VISITOR_CUSTOMER_RECORD"><data key="edge_relationship_id">R75_REL003</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_operational_context">60-0350 identifies MBR among source record systems.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL004" source="SYS_SSR" target="DB_APPT_VISITOR_CUSTOMER_RECORD"><data key="edge_relationship_id">R75_REL004</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_operational_context">60-0350 identifies SSI Record/SVB among source record systems.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL005" source="DB_EDIB_CLAIM_FILE" target="DB_APPT_VISITOR_CUSTOMER_RECORD"><data key="edge_relationship_id">R75_REL005</data><data key="edge_source_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_operational_context">60-0350 identifies the Electronic Disability Claim File among source record systems.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL006" source="DB_RAMP" target="DB_APPT_VISITOR_CUSTOMER_RECORD"><data key="edge_relationship_id">R75_REL006</data><data key="edge_source_entity_id">DB_RAMP</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_operational_context">60-0350 identifies RAMP among source record systems.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes">Reverse direction is also documented in the 2026 RAMP SORN: 60-0350 is a source for RAMP, so these record systems can each be source categories for the other in different operational contexts.</data></edge><edge id="R75_REL007" source="APP_AIRS" target="DB_APPT_VISITOR_CUSTOMER_RECORD"><data key="edge_relationship_id">R75_REL007</data><data key="edge_source_entity_id">APP_AIRS</data><data key="edge_relationship_type">supplies_high_risk_reports_to</data><data key="edge_target_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_operational_context">60-0350 explicitly lists source of the report from the Automated Incident Reporting System.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL008" source="DB_APPT_VISITOR_CUSTOMER_RECORD" target="DATA_CSR_VISITOR_MAILING_ADDRESS"><data key="edge_relationship_id">R75_REL008</data><data key="edge_source_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_CSR_VISITOR_MAILING_ADDRESS</data><data key="edge_operational_context">60-0350 visitor records include mailing address.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes">Mailing-address provenance is not assigned to a specific upstream system because the SORN source categories are broader than this field.</data></edge><edge id="R75_REL009" source="DB_APPT_VISITOR_CUSTOMER_RECORD" target="DATA_CSR_HIGH_RISK_ALERT"><data key="edge_relationship_id">R75_REL009</data><data key="edge_source_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_CSR_HIGH_RISK_ALERT</data><data key="edge_operational_context">60-0350 includes High Risk alert information among its record categories.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL010" source="APP_AIRS" target="DATA_CSR_HIGH_RISK_ALERT"><data key="edge_relationship_id">R75_REL010</data><data key="edge_source_entity_id">APP_AIRS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_CSR_HIGH_RISK_ALERT</data><data key="edge_operational_context">60-0350 identifies AIRS as source of the report underlying High Risk alert information.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL011" source="DB_APPT_VISITOR_CUSTOMER_RECORD" target="DOM_TITLE2"><data key="edge_relationship_id">R75_REL011</data><data key="edge_source_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_relationship_type">supports_transactions_in</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">60-0350 purpose includes assisting with Title II claims and post-entitlement actions.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL012" source="DB_APPT_VISITOR_CUSTOMER_RECORD" target="DOM_TITLE16"><data key="edge_relationship_id">R75_REL012</data><data key="edge_source_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_relationship_type">supports_transactions_in</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">60-0350 purpose includes assisting with Title XVI claims and post-entitlement actions.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL013" source="DB_APPT_VISITOR_CUSTOMER_RECORD" target="SYS_NUMIDENT"><data key="edge_relationship_id">R75_REL013</data><data key="edge_source_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_relationship_type">supports_ssn_actions_using</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">60-0350 purpose includes SSN applications/actions and identifies Numident records as a source.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">4</data><data key="edge_notes">This does not establish direct write access or a technical interface to Numident.</data></edge><edge id="R75_REL014" source="DB_CLAIMS_FOLDERS_SYSTEM" target="DB_RAMP"><data key="edge_relationship_id">R75_REL014</data><data key="edge_source_entity_id">DB_CLAIMS_FOLDERS_SYSTEM</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_RAMP</data><data key="edge_operational_context">2026 RAMP SORN identifies Claims Folder System as a source.</data><data key="edge_observed_as_of">2026-01-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL015" source="DB_EDIB_CLAIM_FILE" target="DB_RAMP"><data key="edge_relationship_id">R75_REL015</data><data key="edge_source_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_RAMP</data><data key="edge_operational_context">2026 RAMP SORN identifies Electronic Disability Claim File as a source.</data><data key="edge_observed_as_of">2026-01-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL016" source="DB_APPT_VISITOR_CUSTOMER_RECORD" target="DB_RAMP"><data key="edge_relationship_id">R75_REL016</data><data key="edge_source_entity_id">DB_APPT_VISITOR_CUSTOMER_RECORD</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DB_RAMP</data><data key="edge_operational_context">2026 RAMP SORN identifies 60-0350 as a source.</data><data key="edge_observed_as_of">2026-01-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL017" source="EXT_DHS_ADIS" target="DB_TRAVEL_BORDER_CROSSING"><data key="edge_relationship_id">R75_REL017</data><data key="edge_source_entity_id">EXT_DHS_ADIS</data><data key="edge_relationship_type">supplies_records_to</data><data key="edge_target_entity_id">DB_TRAVEL_BORDER_CROSSING</data><data key="edge_operational_context">60-0389 names DHS CBP Arrival and Departure Information System as a source under established data exchange agreements.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL018" source="DB_TRAVEL_BORDER_CROSSING" target="DOM_TITLE2"><data key="edge_relationship_id">R75_REL018</data><data key="edge_source_entity_id">DB_TRAVEL_BORDER_CROSSING</data><data key="edge_relationship_type">supports_entitlement_or_eligibility_for</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">60-0389 purpose is to identify U.S. absences to establish or verify Title II entitlement.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL019" source="DB_TRAVEL_BORDER_CROSSING" target="DOM_TITLE16"><data key="edge_relationship_id">R75_REL019</data><data key="edge_source_entity_id">DB_TRAVEL_BORDER_CROSSING</data><data key="edge_relationship_type">supports_entitlement_or_eligibility_for</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">60-0389 purpose is to identify U.S. absences to establish or verify Title XVI eligibility.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL020" source="DB_TRAVEL_BORDER_CROSSING" target="DOM_MEDICARE"><data key="edge_relationship_id">R75_REL020</data><data key="edge_source_entity_id">DB_TRAVEL_BORDER_CROSSING</data><data key="edge_relationship_type">supports_entitlement_or_eligibility_for</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">60-0389 purpose includes Title XVIII eligibility/entitlement.</data><data key="edge_observed_as_of">2025-08-20</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL021" source="PROC_UPLOAD_SIGNED_APP_INTAKE" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R75_REL021</data><data key="edge_source_entity_id">PROC_UPLOAD_SIGNED_APP_INTAKE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Signed benefit applications can be electronically submitted through Upload Documents after mySSA authentication.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL022" source="PROC_UPLOAD_SIGNED_APP_INTAKE" target="APP_MCS"><data key="edge_relationship_id">R75_REL022</data><data key="edge_source_entity_id">PROC_UPLOAD_SIGNED_APP_INTAKE</data><data key="edge_relationship_type">technician_loads_application_into</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS directs technicians to load the signed application into MCS or CCE.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes">Manual/technician processing; not modeled as an automatic electronic transfer.</data></edge><edge id="R75_REL023" source="PROC_UPLOAD_SIGNED_APP_INTAKE" target="APP_CCE"><data key="edge_relationship_id">R75_REL023</data><data key="edge_source_entity_id">PROC_UPLOAD_SIGNED_APP_INTAKE</data><data key="edge_relationship_type">technician_loads_application_into</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">POMS directs technicians to load the signed application into MCS or CCE.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes">Manual/technician processing; not modeled as an automatic electronic transfer.</data></edge><edge id="R75_REL024" source="PROC_UPLOAD_SIGNED_APP_INTAKE" target="WORK_MCS_ATTEST_ISSUE"><data key="edge_relationship_id">R75_REL024</data><data key="edge_source_entity_id">PROC_UPLOAD_SIGNED_APP_INTAKE</data><data key="edge_relationship_type">receipts</data><data key="edge_target_entity_id">WORK_MCS_ATTEST_ISSUE</data><data key="edge_operational_context">Technician receipts the ATTEST issue and adds a remark identifying Upload Documents as the actual signature method.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL025" source="WORK_MCS_ATTEST_ISSUE" target="UI_MCS_DW01"><data key="edge_relationship_id">R75_REL025</data><data key="edge_source_entity_id">WORK_MCS_ATTEST_ISSUE</data><data key="edge_relationship_type">automatically_propagates_to</data><data key="edge_target_entity_id">UI_MCS_DW01</data><data key="edge_operational_context">Current policy says MCS automatically propagates ATTEST to DW01 even when attestation is not the actual signature method.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes">Remarks must identify the true method such as upload docs, wet signature, or CPAS.</data></edge><edge id="R75_REL026" source="FORM_SSA721" target="APP_DIPS"><data key="edge_relationship_id">R75_REL026</data><data key="edge_source_entity_id">FORM_SSA721</data><data key="edge_relationship_type">provides_death_evidence_to</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">Current POMS directs SSA-721 death records to be added to Numident using DIPS.</data><data key="edge_observed_as_of">2026-05-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL027" source="FORM_SSA721" target="DATA_SSA721_SURVIVOR_ADDRESS"><data key="edge_relationship_id">R75_REL027</data><data key="edge_source_entity_id">FORM_SSA721</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSA721_SURVIVOR_ADDRESS</data><data key="edge_operational_context">Current SSA-721 provides fields for surviving spouse/child addresses when known.</data><data key="edge_observed_as_of">2024-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL028" source="DATA_SSA721_SURVIVOR_ADDRESS" target="APP_DPS"><data key="edge_relationship_id">R75_REL028</data><data key="edge_source_entity_id">DATA_SSA721_SURVIVOR_ADDRESS</data><data key="edge_relationship_type">used_to_address_notice_from</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">When SSA-721 contains survivor name/address, POMS directs sending a Survivor letter in the DPS General folder.</data><data key="edge_observed_as_of">2026-05-29</data><data key="edge_confidence">5</data><data key="edge_notes">No update to MBR, SSR, Numident, or PI/PERSON is stated.</data></edge><edge id="R75_REL029" source="APP_DPS" target="NOTICE_SURVIVOR_LETTER"><data key="edge_relationship_id">R75_REL029</data><data key="edge_source_entity_id">APP_DPS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">NOTICE_SURVIVOR_LETTER</data><data key="edge_operational_context">POMS directs staff to send the Survivor letter from the General folder in DPS.</data><data key="edge_observed_as_of">2026-05-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL030" source="FORM_SSA721" target="APP_EVID"><data key="edge_relationship_id">R75_REL030</data><data key="edge_source_entity_id">FORM_SSA721</data><data key="edge_relationship_type">coded_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">For a beneficiary who filed a claim, current POMS directs staff to annotate EVID with 721.</data><data key="edge_observed_as_of">2026-05-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL031" source="FORM_SSA8203BK" target="PROC_SSI_RZ_ADDRESS_DEVELOPMENT"><data key="edge_relationship_id">R75_REL031</data><data key="edge_source_entity_id">FORM_SSA8203BK</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="edge_operational_context">Current RZ policy uses SSA-8203-BK address/residence questions for paper redeterminations.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL032" source="PROC_SSI_RZ_ADDRESS_DEVELOPMENT" target="UI_SSI_LRES"><data key="edge_relationship_id">R75_REL032</data><data key="edge_source_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_SSI_LRES</data><data key="edge_operational_context">Current policy documents residence address on LRES.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL033" source="PROC_SSI_RZ_ADDRESS_DEVELOPMENT" target="UI_SSI_APID"><data key="edge_relationship_id">R75_REL033</data><data key="edge_source_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_SSI_APID</data><data key="edge_operational_context">Current policy documents mailing address on APID.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL034" source="PROC_SSI_RZ_ADDRESS_DEVELOPMENT" target="SYS_SSR"><data key="edge_relationship_id">R75_REL034</data><data key="edge_source_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="edge_relationship_type">compares_alleged_residence_with</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current policy says if the alleged address is on SSR no further COA development is required; otherwise staff determine whether an unreported COA occurred.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes">Comparison does not itself overwrite SSR.</data></edge><edge id="R75_REL035" source="FORM_SSA8006F4" target="PROC_SSI_RZ_ADDRESS_DEVELOPMENT"><data key="edge_relationship_id">R75_REL035</data><data key="edge_source_entity_id">FORM_SSA8006F4</data><data key="edge_relationship_type">documents_development_for</data><data key="edge_target_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="edge_operational_context">Current policy permits use of SSA-8006-F4 for residence/living-arrangement development when necessary.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R75_REL036" source="FORM_SSA8007" target="PROC_SSI_RZ_ADDRESS_DEVELOPMENT"><data key="edge_relationship_id">R75_REL036</data><data key="edge_source_entity_id">FORM_SSA8007</data><data key="edge_relationship_type">documents_development_for</data><data key="edge_target_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="edge_operational_context">Current policy permits use of SSA-8007 for residence/living-arrangement development when necessary.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R75_REL037" source="FORM_SSA8008" target="PROC_SSI_RZ_ADDRESS_DEVELOPMENT"><data key="edge_relationship_id">R75_REL037</data><data key="edge_source_entity_id">FORM_SSA8008</data><data key="edge_relationship_type">documents_development_for</data><data key="edge_target_entity_id">PROC_SSI_RZ_ADDRESS_DEVELOPMENT</data><data key="edge_operational_context">Current policy permits use of SSA-8008 for residence/living-arrangement development when necessary.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R75_REL038" source="REPORT_SSAB_SSI_REPORTING_2026" target="INIT_SSI_IMPROVEMENT"><data key="edge_relationship_id">R75_REL038</data><data key="edge_source_entity_id">REPORT_SSAB_SSI_REPORTING_2026</data><data key="edge_relationship_type">advises</data><data key="edge_target_entity_id">INIT_SSI_IMPROVEMENT</data><data key="edge_operational_context">SSAB frames its digital-reporting recommendations as opportunities for SSA and its SSI Improvement Team.</data><data key="edge_observed_as_of">2026-07-25</data><data key="edge_confidence">4</data><data key="edge_notes">Advisory recommendation, not deployment evidence.</data></edge><edge id="R75_REL039" source="REPORT_SSAB_SSI_REPORTING_2026" target="APP_SSIMWV"><data key="edge_relationship_id">R75_REL039</data><data key="edge_source_entity_id">REPORT_SSAB_SSI_REPORTING_2026</data><data key="edge_relationship_type">evaluates_reporting_limitations_of</data><data key="edge_target_entity_id">APP_SSIMWV</data><data key="edge_operational_context">SSAB says online SSI tools remain limited to monthly wage submissions and recommends considering broader reporting capabilities.</data><data key="edge_observed_as_of">2026-07-25</data><data key="edge_confidence">4</data><data key="edge_notes">Report does not state SSIMWV is the only wage tool; relationship represents the documented monthly-wage digital capability class.</data></edge><edge id="R75_REL040" source="ORG_SSA_OCACT" target="DATA_PAYMENT_CALC_BASES"><data key="edge_relationship_id">R75_REL040</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_PAYMENT_CALC_BASES</data><data key="edge_operational_context">OACT Actuarial Services determines and publishes annual Payment Calculation Bases.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL041" source="DATA_PAYMENT_CALC_BASES" target="DOM_TITLE2"><data key="edge_relationship_id">R75_REL041</data><data key="edge_source_entity_id">DATA_PAYMENT_CALC_BASES</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">OACT publishes a distinct Title II payment calculation base.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL042" source="DATA_PAYMENT_CALC_BASES" target="DOM_TITLE16"><data key="edge_relationship_id">R75_REL042</data><data key="edge_source_entity_id">DATA_PAYMENT_CALC_BASES</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">OACT publishes a distinct Title XVI payment calculation base.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R75_REL043" source="DATA_PAYMENT_CALC_BASES" target="PROC_VR_COST_REIMB"><data key="edge_relationship_id">R75_REL043</data><data key="edge_source_entity_id">DATA_PAYMENT_CALC_BASES</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_VR_COST_REIMB</data><data key="edge_operational_context">Payment Calculation Bases are used for payments to rehabilitation-service providers under applicable SSA program rules.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">4</data><data key="edge_notes">Public OACT source establishes provider-payment purpose; specific VR reimbursement system handoff is not described, so this is a business-rule support relationship, not a technical interface.</data></edge><edge id="R76_REL001" source="DATA_MBR_MAILING_ADDRESS" target="SYS_MBR"><data key="edge_relationship_id">R76_REL001</data><data key="edge_source_entity_id">DATA_MBR_MAILING_ADDRESS</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current Title II address policy and myCOA policy identify the beneficiary mailing address as maintained on the MBR.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL002" source="APP_MYCOA" target="DATA_MBR_MAILING_ADDRESS"><data key="edge_relationship_id">R76_REL002</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_MBR_MAILING_ADDRESS</data><data key="edge_operational_context">myCOA permits eligible Title II users to update mailing address; the change posts to the MBR overnight.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL003" source="PROC_NCOA_TITLEII" target="DATA_MBR_MAILING_ADDRESS"><data key="edge_relationship_id">R76_REL003</data><data key="edge_source_entity_id">PROC_NCOA_TITLEII</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_MBR_MAILING_ADDRESS</data><data key="edge_operational_context">Eligible USPS NCOA matches conditionally update the Title II mailing address maintained on MBR.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL004" source="DATA_MBR_RESIDENCE_SCC" target="SYS_MBR"><data key="edge_relationship_id">R76_REL004</data><data key="edge_source_entity_id">DATA_MBR_RESIDENCE_SCC</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS requires SCC coding on MBR when residence differs from mailing address.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL005" source="ORG_CMS" target="DATA_MBR_RESIDENCE_SCC"><data key="edge_relationship_id">R76_REL005</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_MBR_RESIDENCE_SCC</data><data key="edge_operational_context">CMS uses the MBR SCC to verify that a Medicare Advantage member resides in a certified service area.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL006" source="PROC_MA_SCC_ADDRESS_VERIFY" target="DATA_MBR_RESIDENCE_SCC"><data key="edge_relationship_id">R76_REL006</data><data key="edge_source_entity_id">PROC_MA_SCC_ADDRESS_VERIFY</data><data key="edge_relationship_type">reviews</data><data key="edge_target_entity_id">DATA_MBR_RESIDENCE_SCC</data><data key="edge_operational_context">The workflow compares beneficiary residence and county information with the MBR SCC and Medicare records.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL007" source="PROC_MA_SCC_ADDRESS_VERIFY" target="QRY_HIQR"><data key="edge_relationship_id">R76_REL007</data><data key="edge_source_entity_id">PROC_MA_SCC_ADDRESS_VERIFY</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">QRY_HIQR</data><data key="edge_operational_context">POMS directs staff to compare MBR and HIQR information after MBR address/SCC correction processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL008" source="PROC_MA_SCC_ADDRESS_VERIFY" target="DATA_MA_ADDRESS_VERIFY_FORM"><data key="edge_relationship_id">R76_REL008</data><data key="edge_source_entity_id">PROC_MA_SCC_ADDRESS_VERIFY</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_MA_ADDRESS_VERIFY_FORM</data><data key="edge_operational_context">The POMS exhibit captures mailing address, permanent residence address and county of residence for discrepancy resolution.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL009" source="PROC_MA_SCC_ADDRESS_VERIFY" target="SYS_MBR"><data key="edge_relationship_id">R76_REL009</data><data key="edge_source_entity_id">PROC_MA_SCC_ADDRESS_VERIFY</data><data key="edge_relationship_type">may_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Verified beneficiary information can require correction of MBR address/SCC data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL010" source="SYS_MBR" target="QRY_HIQR"><data key="edge_relationship_id">R76_REL010</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">address_correction_propagates_to</data><data key="edge_target_entity_id">QRY_HIQR</data><data key="edge_operational_context">POMS instructs staff to allow two days for an MBR address correction to pass to HIQR.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">The cited POMS does not describe transport or intermediate stores.</data></edge><edge id="R76_REL011" source="PROC_MA_SCC_ADDRESS_VERIFY" target="ORG_CMS"><data key="edge_relationship_id">R76_REL011</data><data key="edge_source_entity_id">PROC_MA_SCC_ADDRESS_VERIFY</data><data key="edge_relationship_type">may_trigger_partner_correction_by</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">Where HIQR/CMS records are wrong after SSA verification, the case may be referred to CMS for correction of CMS records.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL012" source="DATA_NUMIDENT_SSD" target="SYS_NUMIDENT"><data key="edge_relationship_id">R76_REL012</data><data key="edge_source_entity_id">DATA_NUMIDENT_SSD</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS describes this field as part of the Death Data Numident query response.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL013" source="DATA_NUMIDENT_EDR_FIELD" target="SYS_NUMIDENT"><data key="edge_relationship_id">R76_REL013</data><data key="edge_source_entity_id">DATA_NUMIDENT_EDR_FIELD</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS describes this field as part of the Death Data Numident query response.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL014" source="DATA_NUMIDENT_POD" target="SYS_NUMIDENT"><data key="edge_relationship_id">R76_REL014</data><data key="edge_source_entity_id">DATA_NUMIDENT_POD</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS describes this field as part of the Death Data Numident query response.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL015" source="DATA_NUMIDENT_DEATH_COMMENTS" target="SYS_NUMIDENT"><data key="edge_relationship_id">R76_REL015</data><data key="edge_source_entity_id">DATA_NUMIDENT_DEATH_COMMENTS</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS describes this field as part of the Death Data Numident query response.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL016" source="APP_PERSON_INFO" target="DATA_NUMIDENT_SSD"><data key="edge_relationship_id">R76_REL016</data><data key="edge_source_entity_id">APP_PERSON_INFO</data><data key="edge_relationship_type">provides_query_access_to</data><data key="edge_target_entity_id">DATA_NUMIDENT_SSD</data><data key="edge_operational_context">POMS directs staff to use Person Information via iMAIN to access Numident death information including source-of-death coding.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL017" source="DATA_NUMIDENT_SSD" target="DATA_DMF"><data key="edge_relationship_id">R76_REL017</data><data key="edge_source_entity_id">DATA_NUMIDENT_SSD</data><data key="edge_relationship_type">governs_disclosure_handling_for</data><data key="edge_target_entity_id">DATA_DMF</data><data key="edge_operational_context">State-source codes on Numident invoke section 205(r) restrictions on disclosure of state death information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship expresses policy handling, not a file-level data transfer.</data></edge><edge id="R76_REL018" source="DATA_NUMIDENT_SSD" target="DATA_NUMIDENT_POD"><data key="edge_relationship_id">R76_REL018</data><data key="edge_source_entity_id">DATA_NUMIDENT_SSD</data><data key="edge_relationship_type">combined_with</data><data key="edge_target_entity_id">DATA_NUMIDENT_POD</data><data key="edge_operational_context">Current proof-of-death policy interprets SSD and POD together to determine preferred/proven death evidence.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL019" source="DATA_NUMIDENT_EDR_FIELD" target="DATA_NUMIDENT_POD"><data key="edge_relationship_id">R76_REL019</data><data key="edge_source_entity_id">DATA_NUMIDENT_EDR_FIELD</data><data key="edge_relationship_type">combined_with</data><data key="edge_target_entity_id">DATA_NUMIDENT_POD</data><data key="edge_operational_context">Verified EDR proof requires the EDR indicator together with POD and other Numident death fields.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL020" source="DATA_NUMIDENT_EDR_FIELD" target="DATA_NUMIDENT_DEATH_COMMENTS"><data key="edge_relationship_id">R76_REL020</data><data key="edge_source_entity_id">DATA_NUMIDENT_EDR_FIELD</data><data key="edge_relationship_type">combined_with</data><data key="edge_target_entity_id">DATA_NUMIDENT_DEATH_COMMENTS</data><data key="edge_operational_context">Current POMS uses the EDR indicator and the EDR Death Report comment as part of the verified-EDR test.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL021" source="EX_IEDR" target="DATA_NUMIDENT_EDR_FIELD"><data key="edge_relationship_id">R76_REL021</data><data key="edge_source_entity_id">EX_IEDR</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">DATA_NUMIDENT_EDR_FIELD</data><data key="edge_operational_context">Current policy treats an EDR-marked Numident death as state-source death information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">The public policy establishes EDR provenance semantics but does not document the internal field-write interface; relationship is intentionally non-mechanistic.</data></edge><edge id="R76_REL022" source="APP_DIPS" target="DATA_NUMIDENT_SSD"><data key="edge_relationship_id">R76_REL022</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_SSD</data><data key="edge_operational_context">DIPS is the required application for adding, changing, or removing Numident death information; source coding is part of the resulting Death Data Numident record.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Field-specific write mechanics are not public.</data></edge><edge id="R76_REL023" source="APP_ISSNRC" target="DATA_ISSNRC_APP_VOLUMES"><data key="edge_relationship_id">R76_REL023</data><data key="edge_source_entity_id">APP_ISSNRC</data><data key="edge_relationship_type">generates_activity_for</data><data key="edge_target_entity_id">DATA_ISSNRC_APP_VOLUMES</data><data key="edge_operational_context">SSA Open Data says the public dataset uses front-end activity counts from the Online Social Security Replacement Card Application.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL024" source="APP_ISSNRC" target="DB_ISSNRC_ACTIVITY_DW"><data key="edge_relationship_id">R76_REL024</data><data key="edge_source_entity_id">APP_ISSNRC</data><data key="edge_relationship_type">transactions_stored_in</data><data key="edge_target_entity_id">DB_ISSNRC_ACTIVITY_DW</data><data key="edge_operational_context">SSA Open Data says captured internet replacement-card transactions are stored in a data warehouse.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL025" source="DB_ISSNRC_ACTIVITY_DW" target="DATA_ISSNRC_APP_VOLUMES"><data key="edge_relationship_id">R76_REL025</data><data key="edge_source_entity_id">DB_ISSNRC_ACTIVITY_DW</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_ISSNRC_APP_VOLUMES</data><data key="edge_operational_context">The documented warehouse stores the captured transactions used for the public usage dataset.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">SSA does not name the warehouse or explicitly describe the extract job, so only the publication-source role is recorded.</data></edge><edge id="R76_REL026" source="ORG_TREASURY" target="EX_TREASURY_OACT_MONTHLY_TRUST_DATA"><data key="edge_relationship_id">R76_REL026</data><data key="edge_source_entity_id">ORG_TREASURY</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">EX_TREASURY_OACT_MONTHLY_TRUST_DATA</data><data key="edge_operational_context">OACT states Treasury manages the Social Security trust funds and provides SSA monthly financial-operations and investment data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL027" source="EX_TREASURY_OACT_MONTHLY_TRUST_DATA" target="ORG_SSA_OCACT"><data key="edge_relationship_id">R76_REL027</data><data key="edge_source_entity_id">EX_TREASURY_OACT_MONTHLY_TRUST_DATA</data><data key="edge_relationship_type">received_by</data><data key="edge_target_entity_id">ORG_SSA_OCACT</data><data key="edge_operational_context">OCACT publishes trust-fund financial and investment products from Treasury-provided data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">SSA page says Treasury provides SSA data; OCACT recipient role is inferred only at organizational publication boundary, not internal routing.</data></edge><edge id="R76_REL028" source="ORG_BFS" target="DATA_OACT_TRUST_FUND_HOLDINGS"><data key="edge_relationship_id">R76_REL028</data><data key="edge_source_entity_id">ORG_BFS</data><data key="edge_relationship_type">provides_monthly_reports_for</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_HOLDINGS</data><data key="edge_operational_context">OACT says monthly Bureau of the Fiscal Service reports provide holdings by security type, interest rate and maturity date.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL029" source="ORG_BFS" target="DATA_OACT_TRUST_FUND_TRANSACTIONS"><data key="edge_relationship_id">R76_REL029</data><data key="edge_source_entity_id">ORG_BFS</data><data key="edge_relationship_type">provides_monthly_reports_for</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_TRANSACTIONS</data><data key="edge_operational_context">OACT says monthly Bureau of the Fiscal Service reports support trust-fund investment transaction reporting.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL030" source="EX_TREASURY_OACT_MONTHLY_TRUST_DATA" target="DATA_OACT_TRUST_FUND_FINANCIAL"><data key="edge_relationship_id">R76_REL030</data><data key="edge_source_entity_id">EX_TREASURY_OACT_MONTHLY_TRUST_DATA</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_operational_context">Treasury monthly financial-operations data are the documented upstream source family for OACT trust-fund financial data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL031" source="EX_TREASURY_OACT_MONTHLY_TRUST_DATA" target="DATA_OACT_TRUST_FUND_HOLDINGS"><data key="edge_relationship_id">R76_REL031</data><data key="edge_source_entity_id">EX_TREASURY_OACT_MONTHLY_TRUST_DATA</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_HOLDINGS</data><data key="edge_operational_context">Treasury/Fiscal Service monthly investment data support the OACT holdings product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL032" source="EX_TREASURY_OACT_MONTHLY_TRUST_DATA" target="DATA_OACT_TRUST_FUND_TRANSACTIONS"><data key="edge_relationship_id">R76_REL032</data><data key="edge_source_entity_id">EX_TREASURY_OACT_MONTHLY_TRUST_DATA</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_TRANSACTIONS</data><data key="edge_operational_context">Treasury/Fiscal Service monthly investment data support the OACT transaction product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL033" source="DATA_OACT_TRUST_FUND_FINANCIAL" target="DATA_OACT_TRUST_FUND_TIME_SERIES"><data key="edge_relationship_id">R76_REL033</data><data key="edge_source_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_relationship_type">includes_view</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_TIME_SERIES</data><data key="edge_operational_context">The OACT financial-data family exposes a selectable time-series view for trust-fund financial items.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL034" source="ORG_SSA_OCACT" target="DATA_OACT_TRUST_FUND_FINANCIAL"><data key="edge_relationship_id">R76_REL034</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_operational_context">OCACT publishes Social Security trust-fund financial operations data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL035" source="ORG_SSA_OCACT" target="DATA_OACT_TRUST_FUND_HOLDINGS"><data key="edge_relationship_id">R76_REL035</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_HOLDINGS</data><data key="edge_operational_context">OCACT publishes trust-fund investment-holdings reports.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL036" source="ORG_SSA_OCACT" target="DATA_OACT_TRUST_FUND_TRANSACTIONS"><data key="edge_relationship_id">R76_REL036</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_TRANSACTIONS</data><data key="edge_operational_context">OCACT publishes trust-fund investment-transaction reports.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL037" source="ORG_SSA_OCACT" target="DATA_OACT_TRUST_FUND_TIME_SERIES"><data key="edge_relationship_id">R76_REL037</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_TRUST_FUND_TIME_SERIES</data><data key="edge_operational_context">OCACT publishes selectable time-series trust-fund financial data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R76_REL038" source="DATA_OACT_TRUST_FUND_FINANCIAL" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R76_REL038</data><data key="edge_source_entity_id">DATA_OACT_TRUST_FUND_FINANCIAL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">The 2026 Trustees Report financial-operations section cross-references OACT trust-fund program data and presents consistent fund-operation and investment measures.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">This is a publication/data-support relationship, not a claim about the Trustees Report production software.</data></edge><edge id="R77_REL001" source="DATA_SSR_ACD" target="SYS_SSR"><data key="edge_relationship_id">R77_REL001</data><data key="edge_source_entity_id">DATA_SSR_ACD</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS identifies ACD on the SSR address query and uses it to assess SSI address recency.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL002" source="DATA_MBR_ADDR_UPDATED" target="SYS_MBR"><data key="edge_relationship_id">R77_REL002</data><data key="edge_source_entity_id">DATA_MBR_ADDR_UPDATED</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS identifies ADDR Updated on MBR as the Title II address recency value compared with SSR ACD.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL003" source="PROC_T2_SSI_ADDR_RECENCY" target="DATA_SSR_ACD"><data key="edge_relationship_id">R77_REL003</data><data key="edge_source_entity_id">PROC_T2_SSI_ADDR_RECENCY</data><data key="edge_relationship_type">compares</data><data key="edge_target_entity_id">DATA_SSR_ACD</data><data key="edge_operational_context">Undeliverable-mail workflow compares SSR ACD against MBR address update date.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL004" source="PROC_T2_SSI_ADDR_RECENCY" target="DATA_MBR_ADDR_UPDATED"><data key="edge_relationship_id">R77_REL004</data><data key="edge_source_entity_id">PROC_T2_SSI_ADDR_RECENCY</data><data key="edge_relationship_type">compares</data><data key="edge_target_entity_id">DATA_MBR_ADDR_UPDATED</data><data key="edge_operational_context">Workflow compares MBR ADDR Updated with SSR ACD.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL005" source="PROC_T2_SSI_ADDR_RECENCY" target="SYS_SSR"><data key="edge_relationship_id">R77_REL005</data><data key="edge_source_entity_id">PROC_T2_SSI_ADDR_RECENCY</data><data key="edge_relationship_type">uses_more_recent_address_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">If SSR ACD is later, staff accept SSI address as most current.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Technician action, not automatic replication.</data></edge><edge id="R77_REL006" source="PROC_T2_SSI_ADDR_RECENCY" target="APP_POS"><data key="edge_relationship_id">R77_REL006</data><data key="edge_source_entity_id">PROC_T2_SSI_ADDR_RECENCY</data><data key="edge_relationship_type">updates_via</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Newer SSI address is input to Title II through POS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL007" source="PROC_T2_SSI_ADDR_RECENCY" target="SYS_MBR"><data key="edge_relationship_id">R77_REL007</data><data key="edge_source_entity_id">PROC_T2_SSI_ADDR_RECENCY</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Selected more-current SSI address is entered to MBR through POS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No background synchronization inferred.</data></edge><edge id="R77_REL008" source="PROC_T2_UNDELIV_ADDRESS" target="PROC_T2_SSI_ADDR_RECENCY"><data key="edge_relationship_id">R77_REL008</data><data key="edge_source_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">PROC_T2_SSI_ADDR_RECENCY</data><data key="edge_operational_context">Address-date comparison is a step in Title II undeliverable-mail development.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL009" source="ORG_DDS" target="FORM_SSA408"><data key="edge_relationship_id">R77_REL009</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA408</data><data key="edge_operational_context">DDS prepares SSA-408 to route paper disability folders.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Electronic cases use electronic routing.</data></edge><edge id="R77_REL010" source="FORM_SSA7004" target="ORG_WBDOC"><data key="edge_relationship_id">R77_REL010</data><data key="edge_source_entity_id">FORM_SSA7004</data><data key="edge_relationship_type">mailed_to</data><data key="edge_target_entity_id">ORG_WBDOC</data><data key="edge_operational_context">SSA-7004 paper Statement requests enter the Wilkes-Barre Statement-request processing path.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Current help says use the form address; POMS supplies DOC/WBDOC processing context.</data></edge><edge id="R77_REL011" source="FORM_SSA7004" target="APP_PEBES"><data key="edge_relationship_id">R77_REL011</data><data key="edge_source_entity_id">FORM_SSA7004</data><data key="edge_relationship_type">requests_processing_by</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">SSA-7004 is the paper request artifact within the Social Security Statement/PEBES processing subchapter.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Not a direct system interface.</data></edge><edge id="R77_REL012" source="FORM_HA85" target="CAP_UPLOAD_CONVERSATIONAL"><data key="edge_relationship_id">R77_REL012</data><data key="edge_source_entity_id">FORM_HA85</data><data key="edge_relationship_type">available_as</data><data key="edge_target_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_operational_context">EM-26029 lists HA-85 in the July 25, 2026 conversational-form release.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL013" source="FORM_HA539" target="CAP_UPLOAD_CONVERSATIONAL"><data key="edge_relationship_id">R77_REL013</data><data key="edge_source_entity_id">FORM_HA539</data><data key="edge_relationship_type">available_as</data><data key="edge_target_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_operational_context">EM-26029 lists HA-539 in the July 25, 2026 conversational-form release.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL014" source="FORM_SSA263" target="CAP_UPLOAD_CONVERSATIONAL"><data key="edge_relationship_id">R77_REL014</data><data key="edge_source_entity_id">FORM_SSA263</data><data key="edge_relationship_type">available_as</data><data key="edge_target_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_operational_context">EM-26029 lists SSA-263 in the July 25, 2026 conversational-form release.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL015" source="FORM_SSA371" target="CAP_UPLOAD_CONVERSATIONAL"><data key="edge_relationship_id">R77_REL015</data><data key="edge_source_entity_id">FORM_SSA371</data><data key="edge_relationship_type">available_as</data><data key="edge_target_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_operational_context">EM-26029 lists SSA-371 in the July 25, 2026 conversational-form release.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL016" source="FORM_SSA789" target="CAP_UPLOAD_CONVERSATIONAL"><data key="edge_relationship_id">R77_REL016</data><data key="edge_source_entity_id">FORM_SSA789</data><data key="edge_relationship_type">available_as</data><data key="edge_target_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_operational_context">EM-26029 lists SSA-789 in the July 25, 2026 conversational-form release.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL017" source="FORM_SSA792" target="CAP_UPLOAD_CONVERSATIONAL"><data key="edge_relationship_id">R77_REL017</data><data key="edge_source_entity_id">FORM_SSA792</data><data key="edge_relationship_type">available_as</data><data key="edge_target_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_operational_context">EM-26029 lists SSA-792 in the July 25, 2026 conversational-form release.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL018" source="FORM_SSA1021" target="CAP_UPLOAD_CONVERSATIONAL"><data key="edge_relationship_id">R77_REL018</data><data key="edge_source_entity_id">FORM_SSA1021</data><data key="edge_relationship_type">available_as</data><data key="edge_target_entity_id">CAP_UPLOAD_CONVERSATIONAL</data><data key="edge_operational_context">EM-26029 lists SSA-1021 in the July 25, 2026 conversational-form release.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL019" source="FORM_SSA1021" target="APP_MAPS"><data key="edge_relationship_id">R77_REL019</data><data key="edge_source_entity_id">FORM_SSA1021</data><data key="edge_relationship_type">establishes_appeal_in</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">POMS says MAPS Appeal Application screens or SSA-1021 are used to establish Extra Help appeal.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL020" source="FORM_SSA1021" target="ORG_WBDOC"><data key="edge_relationship_id">R77_REL020</data><data key="edge_source_entity_id">FORM_SSA1021</data><data key="edge_relationship_type">mailed_to</data><data key="edge_target_entity_id">ORG_WBDOC</data><data key="edge_operational_context">POMS says the mailing address on SSA-1021 is WBDOC.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL021" source="PROC_EXTRA_HELP_APPEAL" target="APP_MAPS"><data key="edge_relationship_id">R77_REL021</data><data key="edge_source_entity_id">PROC_EXTRA_HELP_APPEAL</data><data key="edge_relationship_type">implemented_in</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">Extra Help appeals are established in MAPS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL022" source="PROC_EXTRA_HELP_APPEAL" target="FORM_SSA1021"><data key="edge_relationship_id">R77_REL022</data><data key="edge_source_entity_id">PROC_EXTRA_HELP_APPEAL</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA1021</data><data key="edge_operational_context">SSA-1021 is a request channel for Extra Help appeal.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL023" source="PROC_EXTRA_HELP_APPEAL" target="ORG_SAU"><data key="edge_relationship_id">R77_REL023</data><data key="edge_source_entity_id">PROC_EXTRA_HELP_APPEAL</data><data key="edge_relationship_type">decided_by</data><data key="edge_target_entity_id">ORG_SAU</data><data key="edge_operational_context">Established appeal is submitted to Subsidy Appeals Unit for decision.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL024" source="FORM_SSA8012" target="FORM_SSA8011F3"><data key="edge_relationship_id">R77_REL024</data><data key="edge_source_entity_id">FORM_SSA8012</data><data key="edge_relationship_type">succeeds_for_current_periods</data><data key="edge_target_entity_id">FORM_SSA8011F3</data><data key="edge_operational_context">SSA-8012 is used for periods effective 2024-09-30 or later; SSA-8011-F3 applies to earlier periods.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL025" source="FORM_SSA8011F3" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R77_REL025</data><data key="edge_source_entity_id">FORM_SSA8011F3</data><data key="edge_relationship_type">used_when_system_documentation_not_feasible_in</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">For applicable historical periods, POMS uses SSA-8011-F3 when file cannot be documented solely in SSI Claims System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL026" source="EX_EAE" target="DATA_EAE_DHS_DOS_MAILING_ADDRESS"><data key="edge_relationship_id">R77_REL026</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">carries</data><data key="edge_target_entity_id">DATA_EAE_DHS_DOS_MAILING_ADDRESS</data><data key="edge_operational_context">EAE carries immigration/admission data used to mail SSN card.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No program-master address update inferred.</data></edge><edge id="R77_REL027" source="DATA_EAE_DHS_DOS_MAILING_ADDRESS" target="ORG_DOS"><data key="edge_relationship_id">R77_REL027</data><data key="edge_source_entity_id">DATA_EAE_DHS_DOS_MAILING_ADDRESS</data><data key="edge_relationship_type">originates_from</data><data key="edge_target_entity_id">ORG_DOS</data><data key="edge_operational_context">DoS collects visa enumeration data; POMS identifies DHS or DoS address as card mailing source.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">CBP may update data at admission.</data></edge><edge id="R77_REL028" source="DATA_EAE_DHS_DOS_MAILING_ADDRESS" target="ORG_CBP"><data key="edge_relationship_id">R77_REL028</data><data key="edge_source_entity_id">DATA_EAE_DHS_DOS_MAILING_ADDRESS</data><data key="edge_relationship_type">may_be_updated_by</data><data key="edge_target_entity_id">ORG_CBP</data><data key="edge_operational_context">CBP updates enumeration data when immigrant is admitted before downstream DHS transfer.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Specific field changes vary.</data></edge><edge id="R77_REL029" source="ORG_DOS" target="ORG_CBP"><data key="edge_relationship_id">R77_REL029</data><data key="edge_source_entity_id">ORG_DOS</data><data key="edge_relationship_type">transmits_enumeration_data_to</data><data key="edge_target_entity_id">ORG_CBP</data><data key="edge_operational_context">DoS electronically sends immigrant visa enumeration information to CBP.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL030" source="ORG_CBP" target="ORG_USCIS"><data key="edge_relationship_id">R77_REL030</data><data key="edge_source_entity_id">ORG_CBP</data><data key="edge_relationship_type">transmits_updated_enumeration_data_to</data><data key="edge_target_entity_id">ORG_USCIS</data><data key="edge_operational_context">After admission, CBP updates enumeration data and electronically sends it to USCIS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL031" source="DATA_NUMIDENT_EAE_FMC_A" target="SYS_NUMIDENT"><data key="edge_relationship_id">R77_REL031</data><data key="edge_source_entity_id">DATA_NUMIDENT_EAE_FMC_A</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Form Code A appears on Numident to indicate EAE record creation.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R77_REL032" source="EX_EAE" target="DATA_NUMIDENT_EAE_FMC_A"><data key="edge_relationship_id">R77_REL032</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">results_in</data><data key="edge_target_entity_id">DATA_NUMIDENT_EAE_FMC_A</data><data key="edge_operational_context">Fully processed EAE record is marked on Numident with Form Code A.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No physical write interface inferred.</data></edge><edge id="R78_REL001" source="UI_MSSICS_ACID" target="APP_MSSICS"><data key="edge_relationship_id">R78_REL001</data><data key="edge_source_entity_id">UI_MSSICS_ACID</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS identifies ACID as the client-identification screen for applications taken in MSSICS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL002" source="UI_MSSICS_MULTI_SSN" target="APP_MSSICS"><data key="edge_relationship_id">R78_REL002</data><data key="edge_source_entity_id">UI_MSSICS_MULTI_SSN</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS identifies the Multiple SSNs page as the MSSICS page used to collect other names and SSNs.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL003" source="UI_MSSICS_MULTI_SSN" target="SYS_NUMIDENT"><data key="edge_relationship_id">R78_REL003</data><data key="edge_source_entity_id">UI_MSSICS_MULTI_SSN</data><data key="edge_relationship_type">supports_verification_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS says the collected other names and SSNs are needed for Numident verification.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL004" source="FORM_SSA377" target="ORG_DOS"><data key="edge_relationship_id">R78_REL004</data><data key="edge_source_entity_id">FORM_SSA377</data><data key="edge_relationship_type">requests_verification_from</data><data key="edge_target_entity_id">ORG_DOS</data><data key="edge_operational_context">SSA-377 requests Department of State verification of U.S. passport and specified citizenship records.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL005" source="DATA_DIFSLA_RESPONSE" target="COMP_DIFSLA_ALERT_PROFILER"><data key="edge_relationship_id">R78_REL005</data><data key="edge_source_entity_id">DATA_DIFSLA_RESPONSE</data><data key="edge_relationship_type">filtered_by</data><data key="edge_target_entity_id">COMP_DIFSLA_ALERT_PROFILER</data><data key="edge_operational_context">Current CMA attachment says returned IRS-matched records are screened by criteria/tolerances and then a profiling module reduces alerts released to field offices.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R78_REL006" source="ORG_SSA_OQI" target="COMP_DIFSLA_ALERT_PROFILER"><data key="edge_relationship_id">R78_REL006</data><data key="edge_source_entity_id">ORG_SSA_OQI</data><data key="edge_relationship_type">developed</data><data key="edge_target_entity_id">COMP_DIFSLA_ALERT_PROFILER</data><data key="edge_operational_context">Current CMA attachment identifies the Office of Quality Improvement as developer of the profiling module.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R78_REL007" source="COMP_DIFSLA_ALERT_PROFILER" target="DATA_DIFSLA_FO_ALERT"><data key="edge_relationship_id">R78_REL007</data><data key="edge_source_entity_id">COMP_DIFSLA_ALERT_PROFILER</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_DIFSLA_FO_ALERT</data><data key="edge_operational_context">The profiling module further reduces the number of IRS alerts released to field offices for development.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R78_REL008" source="DATA_DIFSLA_FO_ALERT" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">R78_REL008</data><data key="edge_source_entity_id">DATA_DIFSLA_FO_ALERT</data><data key="edge_relationship_type">routed_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">Current CMA attachment describes DIFSLA IRS alerts released to field offices for development.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R78_REL009" source="DATA_DIFSLA_RESPONSE" target="PROC_DIFSLA_INDEPENDENT_VERIFY"><data key="edge_relationship_id">R78_REL009</data><data key="edge_source_entity_id">DATA_DIFSLA_RESPONSE</data><data key="edge_relationship_type">requires_independent_verification_via</data><data key="edge_target_entity_id">PROC_DIFSLA_INDEPENDENT_VERIFY</data><data key="edge_operational_context">Current CMA requires SSA to independently verify IRS unearned-income match information before adverse benefit action.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL010" source="PROC_DIFSLA_INDEPENDENT_VERIFY" target="DOM_TITLE16"><data key="edge_relationship_id">R78_REL010</data><data key="edge_source_entity_id">PROC_DIFSLA_INDEPENDENT_VERIFY</data><data key="edge_relationship_type">precedes_adverse_action_in</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Verification and opportunity to contest are required before termination, denial, suspension, or reduction of SSI benefits.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL011" source="DATA_HAVV_TXN_STATE" target="EX_HAVV"><data key="edge_relationship_id">R78_REL011</data><data key="edge_source_entity_id">DATA_HAVV_TXN_STATE</data><data key="edge_relationship_type">summarizes</data><data key="edge_target_entity_id">EX_HAVV</data><data key="edge_operational_context">SSA Open Data says the public dataset represents combined results of state HAVV verification transactions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL012" source="ORG_SSA_OCACT" target="DATA_OACT_BEND_POINTS"><data key="edge_relationship_id">R78_REL012</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_BEND_POINTS</data><data key="edge_operational_context">OACT publishes the annual PIA and maximum-family-benefit bend-point series.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL013" source="DATA_OACT_BEND_POINTS" target="DOM_TITLE2"><data key="edge_relationship_id">R78_REL013</data><data key="edge_source_entity_id">DATA_OACT_BEND_POINTS</data><data key="edge_relationship_type">supports_benefit_formula_in</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">The OACT page identifies the values as dollar amounts in the Primary Insurance Amount and maximum-family-benefit formulas.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL014" source="PROC_BSO_NONSSN_IDME" target="SVC_IDME"><data key="edge_relationship_id">R78_REL014</data><data key="edge_source_entity_id">PROC_BSO_NONSSN_IDME</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">SSA 2026 employer guidance directs registrants without an SSN to ID.me using an ITIN or passport and requires MFA for BSO access.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL015" source="PROC_BSO_NONSSN_IDME" target="PLAT_BSO"><data key="edge_relationship_id">R78_REL015</data><data key="edge_source_entity_id">PROC_BSO_NONSSN_IDME</data><data key="edge_relationship_type">enables_access_to</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">The alternative ID.me registration path enables access to Business Services Online for registrants without an SSN.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL016" source="APP_DIPS" target="DB_ALPHIDENT"><data key="edge_relationship_id">R78_REL016</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">may_match_against</data><data key="edge_target_entity_id">DB_ALPHIDENT</data><data key="edge_operational_context">SSA OIG reported in January 2026 that DIPS performs an Alphident match when an incoming death report lacks an SSN or the SSN does not match Numident.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Oversight source describes SSA response; detailed matching criteria remain nonpublic.</data></edge><edge id="R78_REL017" source="FORM_HA86" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL017</data><data key="edge_source_entity_id">FORM_HA86</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL018" source="FORM_HA510" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL018</data><data key="edge_source_entity_id">FORM_HA510</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL019" source="FORM_HA4608" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL019</data><data key="edge_source_entity_id">FORM_HA4608</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL020" source="FORM_HA4631" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL020</data><data key="edge_source_entity_id">FORM_HA4631</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL021" source="FORM_HA4632" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL021</data><data key="edge_source_entity_id">FORM_HA4632</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL022" source="FORM_HA4633" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL022</data><data key="edge_source_entity_id">FORM_HA4633</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL023" source="FORM_SSA3" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL023</data><data key="edge_source_entity_id">FORM_SSA3</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL024" source="FORM_SSA8" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL024</data><data key="edge_source_entity_id">FORM_SSA8</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL025" source="FORM_SSA10" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL025</data><data key="edge_source_entity_id">FORM_SSA10</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL026" source="FORM_SSA25" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL026</data><data key="edge_source_entity_id">FORM_SSA25</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL027" source="FORM_SSA44" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL027</data><data key="edge_source_entity_id">FORM_SSA44</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL028" source="FORM_SSA150" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL028</data><data key="edge_source_entity_id">FORM_SSA150</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL029" source="FORM_SSA372" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL029</data><data key="edge_source_entity_id">FORM_SSA372</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL030" source="FORM_SSA521" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL030</data><data key="edge_source_entity_id">FORM_SSA521</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL031" source="FORM_SSA546" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL031</data><data key="edge_source_entity_id">FORM_SSA546</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSA Forms page lists Complete Online Form and Upload PDF routes; the page states select electronic form completion/upload uses the Upload Documents feature.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL032" source="DATA_FI_BANK_STATEMENT_EVIDENCE" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R78_REL032</data><data key="edge_source_entity_id">DATA_FI_BANK_STATEMENT_EVIDENCE</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current SSI resource policy expressly allows downloaded bank-statement files and images to be submitted electronically using Upload Documents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R78_REL033" source="DATA_FI_BANK_STATEMENT_EVIDENCE" target="DOM_TITLE16"><data key="edge_relationship_id">R78_REL033</data><data key="edge_source_entity_id">DATA_FI_BANK_STATEMENT_EVIDENCE</data><data key="edge_relationship_type">supports_resource_verification_in</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Current POMS accepts complete and unaltered bank statements or qualifying FI records as evidence for SSI account/resource development under specified conditions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Alternative evidence can coexist with required AFI negative searches; no claim of replacing AFI globally.</data></edge><edge id="R79_REL001" source="DB_EDIB_CLAIM_FILE" target="DATA_EDIB_ADDR_CHANGE_REPORT"><data key="edge_relationship_id">R79_REL001</data><data key="edge_source_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_EDIB_ADDR_CHANGE_REPORT</data><data key="edge_operational_context">Current SORN 60-0320 includes post-adjudicative reports of changes of address entered into computer processes.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL002" source="DB_EDIB_CLAIM_FILE" target="DATA_EDIB_EMSG_SELECTION"><data key="edge_relationship_id">R79_REL002</data><data key="edge_source_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_EDIB_EMSG_SELECTION</data><data key="edge_operational_context">Current SORN 60-0320 includes opt-in and opt-out selections for electronic messaging.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL003" source="DB_EDIB_CLAIM_FILE" target="DATA_EDIB_PROVIDER_CREDENTIAL"><data key="edge_relationship_id">R79_REL003</data><data key="edge_source_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_EDIB_PROVIDER_CREDENTIAL</data><data key="edge_operational_context">Current SORN includes provider address, TIN, medical license number and license expiration date.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL004" source="EXT_HHS_OIG_LEIE" target="DB_EDIB_CLAIM_FILE"><data key="edge_relationship_id">R79_REL004</data><data key="edge_source_entity_id">EXT_HHS_OIG_LEIE</data><data key="edge_relationship_type">provides_exclusion_status_to</data><data key="edge_target_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_operational_context">SORN 60-0320 identifies LEIE as a record source and stores an indicator when a medical examiner/provider is listed.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL005" source="DB_EDIB_CLAIM_FILE" target="ARCH_CLOUD"><data key="edge_relationship_id">R79_REL005</data><data key="edge_source_entity_id">DB_EDIB_CLAIM_FILE</data><data key="edge_relationship_type">has_records_in</data><data key="edge_target_entity_id">ARCH_CLOUD</data><data key="edge_operational_context">The 2026 SORN says information is also located in additional locations in connection with cloud-based services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Does not establish that the named PLAT_EDIB_CLOUD is the same hosting boundary.</data></edge><edge id="R79_REL006" source="DB_DDS_CE_PROVIDER_FILE" target="DATA_CE_PROVIDER_ADDR"><data key="edge_relationship_id">R79_REL006</data><data key="edge_source_entity_id">DB_DDS_CE_PROVIDER_FILE</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_CE_PROVIDER_ADDR</data><data key="edge_operational_context">Current 60-0046 includes provider address in CE Provider File.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL007" source="DB_DDS_CE_PROVIDER_FILE" target="DATA_CE_PROVIDER_CREDENTIAL"><data key="edge_relationship_id">R79_REL007</data><data key="edge_source_entity_id">DB_DDS_CE_PROVIDER_FILE</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_CE_PROVIDER_CREDENTIAL</data><data key="edge_operational_context">Current 60-0046 includes license and credential information including expiration date.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL008" source="DB_DDS_CE_PROVIDER_FILE" target="DATA_CE_PROVIDER_PHOTO_ID"><data key="edge_relationship_id">R79_REL008</data><data key="edge_source_entity_id">DB_DDS_CE_PROVIDER_FILE</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_CE_PROVIDER_PHOTO_ID</data><data key="edge_operational_context">Current 60-0046 includes images of CE provider photo identification cards.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL009" source="DB_DDS_CE_PROVIDER_FILE" target="DATA_CE_PROVIDER_OVERSIGHT"><data key="edge_relationship_id">R79_REL009</data><data key="edge_source_entity_id">DB_DDS_CE_PROVIDER_FILE</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_CE_PROVIDER_OVERSIGHT</data><data key="edge_operational_context">Current 60-0046 includes CE quality/timeliness, fees, site visits, oversight, exclusion information, preferences and investigations.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL010" source="DB_DDS_CE_PROVIDER_FILE" target="ARCH_CLOUD"><data key="edge_relationship_id">R79_REL010</data><data key="edge_source_entity_id">DB_DDS_CE_PROVIDER_FILE</data><data key="edge_relationship_type">has_records_in</data><data key="edge_target_entity_id">ARCH_CLOUD</data><data key="edge_operational_context">The 2026 SORN says CE Provider File information may also be in cloud-based service locations and backup locations.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Cloud provider/platform is not named.</data></edge><edge id="R79_REL011" source="SYS_NUMIDENT" target="DATA_NUMIDENT_FRAUD_APP_MAIL_ADDR"><data key="edge_relationship_id">R79_REL011</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_FRAUD_APP_MAIL_ADDR</data><data key="edge_operational_context">Current 60-0058 explicitly includes mailing addresses for persons filing SSN applications supported by suspected or fraudulent evidence.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL012" source="APP_EDCS" target="ORG_DHU"><data key="edge_relationship_id">R79_REL012</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">transfers_cdr_reconsideration_to</data><data key="edge_target_entity_id">ORG_DHU</data><data key="edge_operational_context">Current CDR reconsideration policy directs EDCS transfer to DDS or the Disability Hearing Unit.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL013" source="UTIL_EDCS_UAT" target="ORG_DHU"><data key="edge_relationship_id">R79_REL013</data><data key="edge_source_entity_id">UTIL_EDCS_UAT</data><data key="edge_relationship_type">sends_address_or_phone_update_to</data><data key="edge_target_entity_id">ORG_DHU</data><data key="edge_operational_context">After transfer, the FO sends a UAT with the individual new address or telephone number to DDS or DHU.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL014" source="FORM_SSA408" target="ORG_DHU"><data key="edge_relationship_id">R79_REL014</data><data key="edge_source_entity_id">FORM_SSA408</data><data key="edge_relationship_type">routes_paper_address_change_to</data><data key="edge_target_entity_id">ORG_DHU</data><data key="edge_operational_context">For paper official folders, current POMS directs SSA-408 to forward change-of-address information to DDS or DHU.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL016" source="ORG_OPM" target="EX_CMA1045_OPM_EARN"><data key="edge_relationship_id">R79_REL016</data><data key="edge_source_entity_id">ORG_OPM</data><data key="edge_relationship_type">submits_identifiers_to</data><data key="edge_target_entity_id">EX_CMA1045_OPM_EARN</data><data key="edge_operational_context">OPM submits full name, SSN, date of birth, and requested tax year(s) under CMA 1045.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL017" source="EX_CMA1045_OPM_EARN" target="SYS_NUMIDENT"><data key="edge_relationship_id">R79_REL017</data><data key="edge_source_entity_id">EX_CMA1045_OPM_EARN</data><data key="edge_relationship_type">verifies_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Notice says OPM identifiers are compared with SSA Enumeration System before earnings disclosure.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL018" source="EX_CMA1045_OPM_EARN" target="SYS_MEF"><data key="edge_relationship_id">R79_REL018</data><data key="edge_source_entity_id">EX_CMA1045_OPM_EARN</data><data key="edge_relationship_type">returns_earnings_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">CMA 1045 uses the Earnings Recording and Self-Employment Income System / MEF to return matched wage and self-employment information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL019" source="SYS_MEF" target="DATA_CMA1045_EMPLOYER_ADDR"><data key="edge_relationship_id">R79_REL019</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_CMA1045_EMPLOYER_ADDR</data><data key="edge_operational_context">CMA 1045 categories of records explicitly include employer address(es) in the SSA matched earnings return.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL020" source="DATA_CMA1045_EMPLOYER_ADDR" target="EX_CMA1045_OPM_EARN"><data key="edge_relationship_id">R79_REL020</data><data key="edge_source_entity_id">DATA_CMA1045_EMPLOYER_ADDR</data><data key="edge_relationship_type">transmitted_via</data><data key="edge_target_entity_id">EX_CMA1045_OPM_EARN</data><data key="edge_operational_context">Employer address is one of the wage/self-employment fields SSA discloses on a match.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL021" source="ORG_OPM" target="EX_CMA1071_OPM_BENEFIT"><data key="edge_relationship_id">R79_REL021</data><data key="edge_source_entity_id">ORG_OPM</data><data key="edge_relationship_type">submits_identifiers_to</data><data key="edge_target_entity_id">EX_CMA1071_OPM_BENEFIT</data><data key="edge_operational_context">OPM submits name, SSN, DOB and SVES indicator under CMA 1071.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL022" source="DATA_CMA1071_SVES_IND" target="EX_CMA1071_OPM_BENEFIT"><data key="edge_relationship_id">R79_REL022</data><data key="edge_source_entity_id">DATA_CMA1071_SVES_IND</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">EX_CMA1071_OPM_BENEFIT</data><data key="edge_operational_context">The SVES indicator is a named input field in the CMA 1071 request.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL023" source="EX_CMA1071_OPM_BENEFIT" target="SYS_NUMIDENT"><data key="edge_relationship_id">R79_REL023</data><data key="edge_source_entity_id">EX_CMA1071_OPM_BENEFIT</data><data key="edge_relationship_type">verifies_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">CMA 1071 notice says SSA verifies the SSN using its Enumeration System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL024" source="SYS_MBR" target="EX_CMA1071_OPM_BENEFIT"><data key="edge_relationship_id">R79_REL024</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_title_ii_benefit_data_to</data><data key="edge_target_entity_id">EX_CMA1071_OPM_BENEFIT</data><data key="edge_operational_context">When SSN verifies, SSA returns Title II beneficiary status and associated benefit information from MBR.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL025" source="EX_CMA1071_OPM_BENEFIT" target="EX_SVES"><data key="edge_relationship_id">R79_REL025</data><data key="edge_source_entity_id">EX_CMA1071_OPM_BENEFIT</data><data key="edge_relationship_type">delivered_through</data><data key="edge_target_entity_id">EX_SVES</data><data key="edge_operational_context">Federal Register notice explicitly says matched Title II MBR information is disclosed through SVES.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL026" source="ORG_SSA_OCACT" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL026</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">OACT publishes the consolidated Automatic Determinations in Recent Years table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL027" source="ORG_SSA_OCACT" target="DATA_OACT_CBB"><data key="edge_relationship_id">R79_REL027</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_CBB</data><data key="edge_operational_context">OACT publishes the contribution and benefit base determination and calculation details.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL028" source="ORG_SSA_OCACT" target="DATA_OACT_OLDLAW_CBB"><data key="edge_relationship_id">R79_REL028</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_OLDLAW_CBB</data><data key="edge_operational_context">OACT publishes the old-law contribution and benefit base determination.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL029" source="ORG_SSA_OCACT" target="DATA_OACT_COVERAGE_THRESH"><data key="edge_relationship_id">R79_REL029</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_COVERAGE_THRESH</data><data key="edge_operational_context">OACT publishes domestic-employee and election-worker coverage-threshold determinations.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL030" source="ORG_SSA_OCACT" target="DATA_OACT_RET_TEST_EXEMPT"><data key="edge_relationship_id">R79_REL030</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_RET_TEST_EXEMPT</data><data key="edge_operational_context">OACT publishes retirement earnings-test exempt amount determinations.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL031" source="ORG_SSA_OCACT" target="DATA_OACT_SGA"><data key="edge_relationship_id">R79_REL031</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_SGA</data><data key="edge_operational_context">OACT publishes SGA determination methodology and annual amounts.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL032" source="ORG_SSA_OCACT" target="DATA_OACT_TWP"><data key="edge_relationship_id">R79_REL032</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_TWP</data><data key="edge_operational_context">OACT publishes trial-work-period earnings trigger methodology and annual amounts.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL033" source="ORG_SSA_OCACT" target="DATA_OACT_QC_AMOUNT"><data key="edge_relationship_id">R79_REL033</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_QC_AMOUNT</data><data key="edge_operational_context">OACT publishes the quarter-of-coverage earnings amount in its automatic determinations table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL034" source="DATA_AWI_SERIES" target="DATA_OACT_CBB"><data key="edge_relationship_id">R79_REL034</data><data key="edge_source_entity_id">DATA_AWI_SERIES</data><data key="edge_relationship_type">indexes</data><data key="edge_target_entity_id">DATA_OACT_CBB</data><data key="edge_operational_context">2026 CBB formula uses 2024 national Average Wage Index relative to 1992.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL035" source="DATA_AWI_SERIES" target="DATA_OACT_OLDLAW_CBB"><data key="edge_relationship_id">R79_REL035</data><data key="edge_source_entity_id">DATA_AWI_SERIES</data><data key="edge_relationship_type">indexes</data><data key="edge_target_entity_id">DATA_OACT_OLDLAW_CBB</data><data key="edge_operational_context">2026 old-law base formula uses 2024 AWI relative to 1992.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL036" source="DATA_AWI_SERIES" target="DATA_OACT_COVERAGE_THRESH"><data key="edge_relationship_id">R79_REL036</data><data key="edge_source_entity_id">DATA_AWI_SERIES</data><data key="edge_relationship_type">indexes</data><data key="edge_target_entity_id">DATA_OACT_COVERAGE_THRESH</data><data key="edge_operational_context">2026 coverage thresholds use AWI ratios under statutory formulas.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL037" source="DATA_AWI_SERIES" target="DATA_OACT_RET_TEST_EXEMPT"><data key="edge_relationship_id">R79_REL037</data><data key="edge_source_entity_id">DATA_AWI_SERIES</data><data key="edge_relationship_type">indexes</data><data key="edge_target_entity_id">DATA_OACT_RET_TEST_EXEMPT</data><data key="edge_operational_context">2026 retirement earnings-test exempt amounts use AWI-based statutory formulas.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL038" source="DATA_AWI_SERIES" target="DATA_OACT_SGA"><data key="edge_relationship_id">R79_REL038</data><data key="edge_source_entity_id">DATA_AWI_SERIES</data><data key="edge_relationship_type">indexes</data><data key="edge_target_entity_id">DATA_OACT_SGA</data><data key="edge_operational_context">OACT determines annual SGA amounts using wage-indexed formulas.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL039" source="DATA_AWI_SERIES" target="DATA_OACT_TWP"><data key="edge_relationship_id">R79_REL039</data><data key="edge_source_entity_id">DATA_AWI_SERIES</data><data key="edge_relationship_type">indexes</data><data key="edge_target_entity_id">DATA_OACT_TWP</data><data key="edge_operational_context">OACT determines the annual TWP trigger with an AWI-based formula.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL040" source="ORG_BLS" target="DATA_BLS_CPIW"><data key="edge_relationship_id">R79_REL040</data><data key="edge_source_entity_id">ORG_BLS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_BLS_CPIW</data><data key="edge_operational_context">BLS calculates CPI-W monthly; OACT republishes the series for Social Security use.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL041" source="DATA_BLS_CPIW" target="PROC_OACT_COLA"><data key="edge_relationship_id">R79_REL041</data><data key="edge_source_entity_id">DATA_BLS_CPIW</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">PROC_OACT_COLA</data><data key="edge_operational_context">SSA COLA methodology uses third-quarter CPI-W averages as the statutory inflation input.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL042" source="PROC_OACT_COLA" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL042</data><data key="edge_source_entity_id">PROC_OACT_COLA</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">The consolidated automatic-determinations table includes annual COLA values produced under the CPI-W methodology.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL043" source="DATA_OACT_CBB" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL043</data><data key="edge_source_entity_id">DATA_OACT_CBB</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">The automatic-determinations table includes the annual contribution and benefit base.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL044" source="DATA_OACT_OLDLAW_CBB" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL044</data><data key="edge_source_entity_id">DATA_OACT_OLDLAW_CBB</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">The table includes the annual old-law contribution and benefit base.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL045" source="DATA_OACT_COVERAGE_THRESH" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL045</data><data key="edge_source_entity_id">DATA_OACT_COVERAGE_THRESH</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">The table includes domestic-employee and election-worker coverage thresholds.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL046" source="DATA_OACT_RET_TEST_EXEMPT" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL046</data><data key="edge_source_entity_id">DATA_OACT_RET_TEST_EXEMPT</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">The table includes lower and higher retirement earnings-test exempt amounts.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL047" source="DATA_OACT_SGA" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL047</data><data key="edge_source_entity_id">DATA_OACT_SGA</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">The table includes blind and non-blind monthly SGA amounts.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL048" source="DATA_OACT_TWP" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL048</data><data key="edge_source_entity_id">DATA_OACT_TWP</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">The table and related OACT pages include annual TWP earnings trigger amounts.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL049" source="DATA_OACT_QC_AMOUNT" target="DATA_OACT_AUTO_DETERMINATIONS"><data key="edge_relationship_id">R79_REL049</data><data key="edge_source_entity_id">DATA_OACT_QC_AMOUNT</data><data key="edge_relationship_type">summarized_in</data><data key="edge_target_entity_id">DATA_OACT_AUTO_DETERMINATIONS</data><data key="edge_operational_context">The table includes annual earnings needed for a quarter of coverage.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL050" source="ORG_SSA_OOC" target="ORG_SSA_OAG"><data key="edge_relationship_id">R79_REL050</data><data key="edge_source_entity_id">ORG_SSA_OOC</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">Current OAG page identifies Office of Operations Contracts as an OAG component responsible for facilities and non-IT acquisitions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL051" source="ORG_SSA_OAS" target="ORG_SSA_OAG"><data key="edge_relationship_id">R79_REL051</data><data key="edge_source_entity_id">ORG_SSA_OAS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">Current OAG page identifies Office of Acquisition Support as an OAG component.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL052" source="ORG_SSA_OAS" target="PROC_SSA_PURCHASE_CARD"><data key="edge_relationship_id">R79_REL052</data><data key="edge_source_entity_id">ORG_SSA_OAS</data><data key="edge_relationship_type">administers</data><data key="edge_target_entity_id">PROC_SSA_PURCHASE_CARD</data><data key="edge_operational_context">Current OAG page says Office of Acquisition Support administers the purchase card program.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL053" source="ORG_SSA_OAG" target="PROC_SSA_GRANT_APPLICATION"><data key="edge_relationship_id">R79_REL053</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers</data><data key="edge_target_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="edge_operational_context">OAG has agency-wide responsibility for grants and the documented application/award workflow.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL054" source="PROC_SSA_GRANT_APPLICATION" target="SVC_SAM_GOV"><data key="edge_relationship_id">R79_REL054</data><data key="edge_source_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="edge_relationship_type">requires_registration_in</data><data key="edge_target_entity_id">SVC_SAM_GOV</data><data key="edge_operational_context">SSA grant instructions require applicants to register or update registration in SAM.gov.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL055" source="PROC_SSA_GRANT_APPLICATION" target="SVC_GRANTS_GOV"><data key="edge_relationship_id">R79_REL055</data><data key="edge_source_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="edge_relationship_type">routes_competitive_applications_through</data><data key="edge_target_entity_id">SVC_GRANTS_GOV</data><data key="edge_operational_context">Competitive discretionary grant applications are submitted through Grants.gov.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL056" source="PROC_SSA_GRANT_APPLICATION" target="SVC_GRANTSOLUTIONS"><data key="edge_relationship_id">R79_REL056</data><data key="edge_source_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="edge_relationship_type">routes_continuation_applications_through</data><data key="edge_target_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_operational_context">Continuation grant applications are submitted through GrantSolutions when stipulated by the announcement.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R79_REL057" source="PROC_SSA_GRANT_APPLICATION" target="SVC_GRANTSOLUTIONS"><data key="edge_relationship_id">R79_REL057</data><data key="edge_source_entity_id">PROC_SSA_GRANT_APPLICATION</data><data key="edge_relationship_type">sends_successful_award_notification_through</data><data key="edge_target_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_operational_context">SSA says successful applicants receive electronic award notification from GrantSolutions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL001" source="SYS_NUMIDENT" target="DATA_NUMIDENT_ITERATION"><data key="edge_relationship_id">R80_REL001</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_ITERATION</data><data key="edge_operational_context">Current POMS describes Numident as containing record iterations for each number holder.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL002" source="APP_SSNAP" target="DATA_NUMIDENT_ITERATION"><data key="edge_relationship_id">R80_REL002</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">appends_new_iteration_to</data><data key="edge_target_entity_id">DATA_NUMIDENT_ITERATION</data><data key="edge_operational_context">When an update is not a documented keying error, SSNAP processing creates a new Numident iteration appended to the previous iteration.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL003" source="PROC_NCP" target="DATA_NUMIDENT_ITERATION"><data key="edge_relationship_id">R80_REL003</data><data key="edge_source_entity_id">PROC_NCP</data><data key="edge_relationship_type">corrects_without_adding_iteration</data><data key="edge_target_entity_id">DATA_NUMIDENT_ITERATION</data><data key="edge_operational_context">NCP corrects a verified keying error on the existing Numident iteration and does not increase the number of iterations.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL004" source="DATA_NUMIDENT_SEX_CODE" target="SYS_NUMIDENT"><data key="edge_relationship_id">R80_REL004</data><data key="edge_source_entity_id">DATA_NUMIDENT_SEX_CODE</data><data key="edge_relationship_type">is_field_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS identifies sex as a Numident field subject to correction/update.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL005" source="DATA_NUMIDENT_PARENT_NAME" target="SYS_NUMIDENT"><data key="edge_relationship_id">R80_REL005</data><data key="edge_source_entity_id">DATA_NUMIDENT_PARENT_NAME</data><data key="edge_relationship_type">is_field_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS identifies parent name as a Numident field subject to evidence-based update.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL006" source="DATA_NUMIDENT_SEX_CODE" target="PROC_NUMIDENT_ASSOC_RECON"><data key="edge_relationship_id">R80_REL006</data><data key="edge_source_entity_id">DATA_NUMIDENT_SEX_CODE</data><data key="edge_relationship_type">triggers_if_updated</data><data key="edge_target_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="edge_operational_context">After updating the Numident sex code, policy directs staff to update MBR, SSR, RPS, or other applicable SSA records.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL007" source="DATA_NUMIDENT_PARENT_NAME" target="PROC_NUMIDENT_ASSOC_RECON"><data key="edge_relationship_id">R80_REL007</data><data key="edge_source_entity_id">DATA_NUMIDENT_PARENT_NAME</data><data key="edge_relationship_type">triggers_if_updated</data><data key="edge_target_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="edge_operational_context">After updating a child Numident parent-name field, policy directs staff to identify whether the parent is a Title II beneficiary, SSI recipient, or payee and review related records.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL008" source="PROC_NUMIDENT_ASSOC_RECON" target="SYS_MBR"><data key="edge_relationship_id">R80_REL008</data><data key="edge_source_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="edge_relationship_type">updates_or_reviews</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Policy-directed associated-record action can include updating the MBR after selected Numident attribute changes.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Human/workflow-directed; no automatic propagation inferred.</data></edge><edge id="R80_REL009" source="PROC_NUMIDENT_ASSOC_RECON" target="SYS_SSR"><data key="edge_relationship_id">R80_REL009</data><data key="edge_source_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="edge_relationship_type">updates_or_reviews</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Policy-directed associated-record action can include correcting or otherwise updating the SSR after selected Numident attribute changes.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Human/workflow-directed; no automatic propagation inferred.</data></edge><edge id="R80_REL010" source="PROC_NUMIDENT_ASSOC_RECON" target="APP_RPS"><data key="edge_relationship_id">R80_REL010</data><data key="edge_source_entity_id">PROC_NUMIDENT_ASSOC_RECON</data><data key="edge_relationship_type">updates_or_reviews</data><data key="edge_target_entity_id">APP_RPS</data><data key="edge_operational_context">Policy-directed associated-record action can include RPS review/update after selected Numident attribute changes.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Human/workflow-directed; no automatic propagation inferred.</data></edge><edge id="R80_REL011" source="EX_STATE_ABLE_MONTHLY" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R80_REL011</data><data key="edge_source_entity_id">EX_STATE_ABLE_MONTHLY</data><data key="edge_relationship_type">transmits_monthly_account_data_to</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">State ABLE programs notify SSA through a monthly data exchange; the Pending ABLE page displays new account information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL012" source="APP_SSI_CLAIMS_LOGICAL" target="UI_SSI_ABLE_ACCOUNT"><data key="edge_relationship_id">R80_REL012</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">UI_SSI_ABLE_ACCOUNT</data><data key="edge_operational_context">Current POMS directs staff to record ABLE account and balance information on the web-based SSI Claims System ABLE Account page.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL013" source="APP_SSI_CLAIMS_LOGICAL" target="UI_SSI_ABLE_PENDING"><data key="edge_relationship_id">R80_REL013</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">UI_SSI_ABLE_PENDING</data><data key="edge_operational_context">The Pending ABLE page in SSI Claims displays new State-reported ABLE account information requiring resolution.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL014" source="UI_SSI_ABLE_ACCOUNT" target="DATA_SSI_ABLE_ACCOUNT"><data key="edge_relationship_id">R80_REL014</data><data key="edge_source_entity_id">UI_SSI_ABLE_ACCOUNT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_SSI_ABLE_ACCOUNT</data><data key="edge_operational_context">The ABLE Account page records State, account number, dates, signature authority, and balance information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL015" source="UI_SSI_ABLE_ACCOUNT" target="DATA_SSI_ABLE_BALANCE"><data key="edge_relationship_id">R80_REL015</data><data key="edge_source_entity_id">UI_SSI_ABLE_ACCOUNT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_SSI_ABLE_BALANCE</data><data key="edge_operational_context">The ABLE Account page includes balance month/year and value information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL016" source="UI_SSI_ABLE_PENDING" target="DATA_SSI_ABLE_ACCOUNT"><data key="edge_relationship_id">R80_REL016</data><data key="edge_source_entity_id">UI_SSI_ABLE_PENDING</data><data key="edge_relationship_type">displays_pending_match_for</data><data key="edge_target_entity_id">DATA_SSI_ABLE_ACCOUNT</data><data key="edge_operational_context">New State-reported ABLE account data are displayed for update/add/reject/decide-later resolution.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL017" source="EX_STATE_ABLE_MONTHLY" target="DATA_SSI_ABLE_BALANCE"><data key="edge_relationship_id">R80_REL017</data><data key="edge_source_entity_id">EX_STATE_ABLE_MONTHLY</data><data key="edge_relationship_type">conditionally_auto_updates</data><data key="edge_target_entity_id">DATA_SSI_ABLE_BALANCE</data><data key="edge_operational_context">After an ABLE account is documented, subsequent matching State reports automatically update the account balance information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Automatic behavior is limited to matching State reports and balance information as documented by POMS.</data></edge><edge id="R80_REL018" source="EX_STATE_ABLE_MONTHLY" target="DATA_SSI_ABLE_DISTRIBUTION"><data key="edge_relationship_id">R80_REL018</data><data key="edge_source_entity_id">EX_STATE_ABLE_MONTHLY</data><data key="edge_relationship_type">transmits</data><data key="edge_target_entity_id">DATA_SSI_ABLE_DISTRIBUTION</data><data key="edge_operational_context">State ABLE programs report prior-month distribution information; current POMS says this exchange-derived information is in SSI Claims.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL019" source="APP_SSI_CLAIMS_LOGICAL" target="DATA_SSI_ABLE_DISTRIBUTION"><data key="edge_relationship_id">R80_REL019</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">contains_but_currently_blocks_user_access_to</data><data key="edge_target_entity_id">DATA_SSI_ABLE_DISTRIBUTION</data><data key="edge_operational_context">Current POMS says State-exchange distribution information is in SSI Claims but cannot be accessed until additional system enhancements are completed.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL020" source="APP_SSI_CLAIMS_LOGICAL" target="UI_SSI_OTHER_RESOURCE"><data key="edge_relationship_id">R80_REL020</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">UI_SSI_OTHER_RESOURCE</data><data key="edge_operational_context">Current POMS directs staff to use the SSI Claims Other Resource page for ABLE prepaid debit cards.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL021" source="UI_SSI_OTHER_RESOURCE" target="DATA_SSI_ABLE_PREPAID_CARD"><data key="edge_relationship_id">R80_REL021</data><data key="edge_source_entity_id">UI_SSI_OTHER_RESOURCE</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">DATA_SSI_ABLE_PREPAID_CARD</data><data key="edge_operational_context">ABLE prepaid debit cards are recorded with program State, account number, intended use, alleged value, and excluded amount.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL022" source="PROC_SSI_ABLE_REPORTING" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R80_REL022</data><data key="edge_source_entity_id">PROC_SSI_ABLE_REPORTING</data><data key="edge_relationship_type">implemented_through_current</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Current 2026 POMS documents ABLE reporting and reconciliation in the web-based SSI Claims System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">This supplements the earlier 2021 MSSICS/SSIRMS architecture; no physical re-platforming is inferred.</data></edge><edge id="R80_REL023" source="PROC_MANUAL_RP_SELECTION" target="FORM_SSA11BK"><data key="edge_relationship_id">R80_REL023</data><data key="edge_source_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="edge_relationship_type">uses_exception_form</data><data key="edge_target_entity_id">FORM_SSA11BK</data><data key="edge_operational_context">SSA-11-BK is used when a representative-payee application cannot be processed through eRPS, including specified no-SSN cases.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL024" source="FORM_SSA11BK" target="APP_EVIEW"><data key="edge_relationship_id">R80_REL024</data><data key="edge_source_entity_id">FORM_SSA11BK</data><data key="edge_relationship_type">retained_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Current POMS directs SSA to retain a copy in eView using Evidence Portal or the eView application.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL025" source="FORM_SSA11BK" target="REPO_NDRED"><data key="edge_relationship_id">R80_REL025</data><data key="edge_source_entity_id">FORM_SSA11BK</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Current POMS permits retention of SSA-11-BK in NDRed using Evidence Portal.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL026" source="FORM_SSA11BK" target="APP_EP"><data key="edge_relationship_id">R80_REL026</data><data key="edge_source_entity_id">FORM_SSA11BK</data><data key="edge_relationship_type">ingested_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Evidence Portal is a documented route for retaining SSA-11-BK in eView or NDRed.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL027" source="NET_N8NN_CARE2020" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R80_REL027</data><data key="edge_source_entity_id">NET_N8NN_CARE2020</data><data key="edge_relationship_type">historically_supported</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA Open Data identifies CARE 2020 as the National 800 Number network and reports dual-network operation beginning 2020-03-31.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Current replacement/retirement date is not inferred from this source.</data></edge><edge id="R80_REL028" source="NET_N8NN_AVAYA" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R80_REL028</data><data key="edge_source_entity_id">NET_N8NN_AVAYA</data><data key="edge_relationship_type">historically_supported</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA Open Data says N8NN CSRs answered calls on both CARE2020 and Avaya effective 2020-03-31.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL029" source="PLAT_N8NN_CCAAS" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R80_REL029</data><data key="edge_source_entity_id">PLAT_N8NN_CCAAS</data><data key="edge_relationship_type">included_in_metrics_for</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA Open Data says N8NN performance metrics include CCaaS beginning 2023-03-23.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Provider identity is intentionally not inferred from this statement.</data></edge><edge id="R80_REL030" source="DATA_N8NN_CALL_VOLUME_BUSY" target="SVC_NATIONAL_800"><data key="edge_relationship_id">R80_REL030</data><data key="edge_source_entity_id">DATA_N8NN_CALL_VOLUME_BUSY</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">Monthly public dataset reports N8NN call volume and CSR busy rate.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL031" source="DATA_N8NN_CALL_VOLUME_BUSY" target="NET_N8NN_CARE2020"><data key="edge_relationship_id">R80_REL031</data><data key="edge_source_entity_id">DATA_N8NN_CALL_VOLUME_BUSY</data><data key="edge_relationship_type">includes_historical_metrics_from</data><data key="edge_target_entity_id">NET_N8NN_CARE2020</data><data key="edge_operational_context">Dataset documentation identifies CARE/CARE2020 as a source context for the N8NN metrics.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL032" source="DATA_N8NN_CALL_VOLUME_BUSY" target="NET_N8NN_AVAYA"><data key="edge_relationship_id">R80_REL032</data><data key="edge_source_entity_id">DATA_N8NN_CALL_VOLUME_BUSY</data><data key="edge_relationship_type">includes_dual_network_period_with</data><data key="edge_target_entity_id">NET_N8NN_AVAYA</data><data key="edge_operational_context">Dataset notes identify Avaya as the parallel network beginning 2020-03-31.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL033" source="DATA_N8NN_CALL_VOLUME_BUSY" target="PLAT_N8NN_CCAAS"><data key="edge_relationship_id">R80_REL033</data><data key="edge_source_entity_id">DATA_N8NN_CALL_VOLUME_BUSY</data><data key="edge_relationship_type">includes_ccaas_metrics_from_2023_03_23</data><data key="edge_target_entity_id">PLAT_N8NN_CCAAS</data><data key="edge_operational_context">The public dataset explicitly states that its N8NN metrics include CCaaS beginning 2023-03-23.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL034" source="APP_MCS" target="DATA_PC_INITIAL_DISABILITY_APT"><data key="edge_relationship_id">R80_REL034</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">records_case_dates_used_for</data><data key="edge_target_entity_id">DATA_PC_INITIAL_DISABILITY_APT</data><data key="edge_operational_context">The Open Data collection description says MCS records case information, processing actions, and associated dates used in this workload measurement.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL035" source="APP_MCS" target="DB_BI_REPOSITORY"><data key="edge_relationship_id">R80_REL035</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">feeds_elapsed_time_management_information_to</data><data key="edge_target_entity_id">DB_BI_REPOSITORY</data><data key="edge_operational_context">SSA says management information such as elapsed/processing time is collected and stored in a Business Intelligence Repository after case dates/actions are recorded in MCS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical publication/data-production relationship; transport and ETL mechanism are not public.</data></edge><edge id="R80_REL036" source="DB_BI_REPOSITORY" target="DATA_PC_INITIAL_DISABILITY_APT"><data key="edge_relationship_id">R80_REL036</data><data key="edge_source_entity_id">DB_BI_REPOSITORY</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_PC_INITIAL_DISABILITY_APT</data><data key="edge_operational_context">The public dataset states that elapsed-time management information is stored in the BI Repository.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL037" source="ORG_SSA_OCACT" target="PROC_OACT_ADMIN_EXPENSE_PROJ"><data key="edge_relationship_id">R80_REL037</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_OACT_ADMIN_EXPENSE_PROJ</data><data key="edge_operational_context">Actuarial Services projects OASDI administrative expenses for the Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL038" source="ORG_SSA_BUDGET_FUNCTION" target="PROC_OACT_ADMIN_EXPENSE_PROJ"><data key="edge_relationship_id">R80_REL038</data><data key="edge_source_entity_id">ORG_SSA_BUDGET_FUNCTION</data><data key="edge_relationship_type">provides_near_term_estimates_to</data><data key="edge_target_entity_id">PROC_OACT_ADMIN_EXPENSE_PROJ</data><data key="edge_operational_context">The 2026 Trustees Report says SSA’s Budget department provides estimates for the first several years of the administrative-expense projection.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL039" source="PROC_OACT_ADMIN_EXPENSE_PROJ" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R80_REL039</data><data key="edge_source_entity_id">PROC_OACT_ADMIN_EXPENSE_PROJ</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Administrative-expense projection methodology contributes to the 2026 OASDI Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL040" source="ORG_SSA_OCACT" target="PROC_OACT_RR_FIN_INTERCHANGE"><data key="edge_relationship_id">R80_REL040</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_OACT_RR_FIN_INTERCHANGE</data><data key="edge_operational_context">Actuarial Services projects future Railroad Retirement financial-interchange amounts.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL041" source="PROC_OACT_RR_FIN_INTERCHANGE" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R80_REL041</data><data key="edge_source_entity_id">PROC_OACT_RR_FIN_INTERCHANGE</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">The financial interchange is a separately described OASDI cost component in the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL042" source="ORG_SSA_OCACT" target="PROC_OACT_BENEFIT_TAX_PROJ"><data key="edge_relationship_id">R80_REL042</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_OACT_BENEFIT_TAX_PROJ</data><data key="edge_operational_context">Actuarial Services estimates OASI/DI trust-fund income from taxation of benefits.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL043" source="ORG_TREASURY_OTA" target="PROC_OACT_BENEFIT_TAX_PROJ"><data key="edge_relationship_id">R80_REL043</data><data key="edge_source_entity_id">ORG_TREASURY_OTA</data><data key="edge_relationship_type">provides_projection_factors_to</data><data key="edge_target_entity_id">PROC_OACT_BENEFIT_TAX_PROJ</data><data key="edge_operational_context">Treasury Office of Tax Analysis supplies short-range factors and long-range estimates used by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL044" source="PROC_OACT_BENEFIT_TAX_PROJ" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R80_REL044</data><data key="edge_source_entity_id">PROC_OACT_BENEFIT_TAX_PROJ</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Taxation-of-benefits income methodology contributes to the Trustees Report trust-fund income projections.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL045" source="ORG_SSA_OCACT" target="PROC_OACT_SCHEDULED_BENEFITS"><data key="edge_relationship_id">R80_REL045</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_OACT_SCHEDULED_BENEFITS</data><data key="edge_operational_context">Actuarial Services uses short-range and long-range models to calculate scheduled benefit amounts.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R80_REL046" source="PROC_OACT_SCHEDULED_BENEFITS" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R80_REL046</data><data key="edge_source_entity_id">PROC_OACT_SCHEDULED_BENEFITS</data><data key="edge_relationship_type">contributes_to</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">Scheduled benefit projections feed the program-specific cost methodology in the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R81_REL001" source="EX_BENDEX" target="DATA_BENDEX_RESPONSE"><data key="edge_relationship_id">R81_REL001</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_BENDEX_RESPONSE</data><data key="edge_operational_context">BENDEX provides a structured response record to participating State partners.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL002" source="DATA_BENDEX_RESPONSE" target="DATA_BENDEX_PAYEE_ADDR"><data key="edge_relationship_id">R81_REL002</data><data key="edge_source_entity_id">DATA_BENDEX_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_BENDEX_PAYEE_ADDR</data><data key="edge_operational_context">The BENDEX layout includes payee name and mailing-address fields.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL003" source="DATA_BENDEX_RESPONSE" target="DATA_BENDEX_RES_SCC"><data key="edge_relationship_id">R81_REL003</data><data key="edge_source_entity_id">DATA_BENDEX_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_BENDEX_RES_SCC</data><data key="edge_operational_context">The BENDEX layout includes the five-position State/county code of residence.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL004" source="DATA_BENDEX_RESPONSE" target="DATA_BENDEX_VERIFIED_BOAN"><data key="edge_relationship_id">R81_REL004</data><data key="edge_source_entity_id">DATA_BENDEX_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_BENDEX_VERIFIED_BOAN</data><data key="edge_operational_context">The BENDEX layout includes verified beneficiary own-account-number data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL005" source="DATA_BENDEX_RESPONSE" target="DATA_BENDEX_CITIZENSHIP"><data key="edge_relationship_id">R81_REL005</data><data key="edge_source_entity_id">DATA_BENDEX_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_BENDEX_CITIZENSHIP</data><data key="edge_operational_context">The BENDEX layout includes citizenship occurrence fields.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL006" source="EX_BENDEX" target="DATA_BENDEX_PAYEE_ADDR"><data key="edge_relationship_id">R81_REL006</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">transmits</data><data key="edge_target_entity_id">DATA_BENDEX_PAYEE_ADDR</data><data key="edge_operational_context">BENDEX transmits the documented payee mailing-address representation to State partners.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL007" source="EX_SDX" target="DATA_SDX_RESPONSE"><data key="edge_relationship_id">R81_REL007</data><data key="edge_source_entity_id">EX_SDX</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_SDX_RESPONSE</data><data key="edge_operational_context">SDX provides a structured SSI response record to State partners.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL008" source="DATA_SDX_RESPONSE" target="DATA_SSR_AD"><data key="edge_relationship_id">R81_REL008</data><data key="edge_source_entity_id">DATA_SDX_RESPONSE</data><data key="edge_relationship_type">exposes_exchange_representation_of</data><data key="edge_target_entity_id">DATA_SSR_AD</data><data key="edge_operational_context">SDX recipient mailing-address fields represent mailing-address information held for the SSI record; the record layout describes its uses for correspondence and payment mailing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL009" source="DATA_SDX_RESPONSE" target="DATA_SSR_RA"><data key="edge_relationship_id">R81_REL009</data><data key="edge_source_entity_id">DATA_SDX_RESPONSE</data><data key="edge_relationship_type">exposes_exchange_representation_of</data><data key="edge_target_entity_id">DATA_SSR_RA</data><data key="edge_operational_context">SDX carries a residence address when it differs from the mailing address and is present on the SSI master file.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL010" source="DATA_SDX_RESPONSE" target="DATA_SSI_RES_STATE_COUNTY"><data key="edge_relationship_id">R81_REL010</data><data key="edge_source_entity_id">DATA_SDX_RESPONSE</data><data key="edge_relationship_type">exposes_exchange_representation_of</data><data key="edge_target_entity_id">DATA_SSI_RES_STATE_COUNTY</data><data key="edge_operational_context">SDX carries State/county jurisdiction information generally reflecting residence.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL011" source="DATA_SDX_RESPONSE" target="DATA_SDX_CURRENT_REC_IND"><data key="edge_relationship_id">R81_REL011</data><data key="edge_source_entity_id">DATA_SDX_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SDX_CURRENT_REC_IND</data><data key="edge_operational_context">SDX uses a current-record indicator where multiple transactions create multiple SDX records.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL012" source="DATA_SDX_RESPONSE" target="DATA_SDX_RESIDENCY_BEGIN"><data key="edge_relationship_id">R81_REL012</data><data key="edge_source_entity_id">DATA_SDX_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SDX_RESIDENCY_BEGIN</data><data key="edge_operational_context">SDX includes the date residency began for the reported jurisdiction.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL013" source="DATA_SDX_RESPONSE" target="DATA_SDX_REP_PAYEE_ADDR"><data key="edge_relationship_id">R81_REL013</data><data key="edge_source_entity_id">DATA_SDX_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SDX_REP_PAYEE_ADDR</data><data key="edge_operational_context">SDX includes representative-payee address fields.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL014" source="DATA_SDX_REP_PAYEE_ADDR" target="DATA_SSR_AD"><data key="edge_relationship_id">R81_REL014</data><data key="edge_source_entity_id">DATA_SDX_REP_PAYEE_ADDR</data><data key="edge_relationship_type">exchange_representation_of</data><data key="edge_target_entity_id">DATA_SSR_AD</data><data key="edge_operational_context">The payee address is an SDX exchange representation associated with the SSI master record's mailing/payee address semantics; physical field identity is not established.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Semantic mapping only; do not infer field-level physical identity.</data></edge><edge id="R81_REL015" source="EX_SOLQ" target="DATA_SOLQ_T1_RESPONSE"><data key="edge_relationship_id">R81_REL015</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_SOLQ_T1_RESPONSE</data><data key="edge_operational_context">SOLQ/SOLQ-I can return the documented Type 1 identity-verification response.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL016" source="DATA_SOLQ_T1_RESPONSE" target="DATA_SOLQ_ID_DISCREP"><data key="edge_relationship_id">R81_REL016</data><data key="edge_source_entity_id">DATA_SOLQ_T1_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SOLQ_ID_DISCREP</data><data key="edge_operational_context">Type 1 includes an Identity Discrepancy Code.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL017" source="DATA_SOLQ_T1_RESPONSE" target="DATA_SOLQ_VERIFY_CODE"><data key="edge_relationship_id">R81_REL017</data><data key="edge_source_entity_id">DATA_SOLQ_T1_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SOLQ_VERIFY_CODE</data><data key="edge_operational_context">Type 1 includes a Verification Code and verification SSN data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL018" source="DATA_SOLQ_T1_RESPONSE" target="DATA_SOLQ_T2_RESPONSE"><data key="edge_relationship_id">R81_REL018</data><data key="edge_source_entity_id">DATA_SOLQ_T1_RESPONSE</data><data key="edge_relationship_type">accompanies</data><data key="edge_target_entity_id">DATA_SOLQ_T2_RESPONSE</data><data key="edge_operational_context">The SOLQ/SOLQ-I record layout defines Type 1 and Type 2 response structures within the same real-time query product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL019" source="DATA_SOLQ_T1_RESPONSE" target="DATA_SOLQ_T16_RESPONSE"><data key="edge_relationship_id">R81_REL019</data><data key="edge_source_entity_id">DATA_SOLQ_T1_RESPONSE</data><data key="edge_relationship_type">accompanies</data><data key="edge_target_entity_id">DATA_SOLQ_T16_RESPONSE</data><data key="edge_operational_context">The SOLQ/SOLQ-I record layout defines Type 1 and Title XVI response structures within the same real-time query product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL020" source="DATA_SOLQ_T16_RESPONSE" target="DATA_SOLQ_MULTI_SSN"><data key="edge_relationship_id">R81_REL020</data><data key="edge_source_entity_id">DATA_SOLQ_T16_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SOLQ_MULTI_SSN</data><data key="edge_operational_context">The Title XVI response layout includes a multiple-SSN indicator/list.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL021" source="DATA_SOLQ_T16_RESPONSE" target="DATA_SSR_AD"><data key="edge_relationship_id">R81_REL021</data><data key="edge_source_entity_id">DATA_SOLQ_T16_RESPONSE</data><data key="edge_relationship_type">exposes_exchange_representation_of</data><data key="edge_target_entity_id">DATA_SSR_AD</data><data key="edge_operational_context">SOLQ/SOLQ-I Title XVI response fields include payee/mailing address information from the SSI record.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL022" source="DATA_SOLQ_T16_RESPONSE" target="DATA_SSR_RA"><data key="edge_relationship_id">R81_REL022</data><data key="edge_source_entity_id">DATA_SOLQ_T16_RESPONSE</data><data key="edge_relationship_type">exposes_exchange_representation_of</data><data key="edge_target_entity_id">DATA_SSR_RA</data><data key="edge_operational_context">SOLQ/SOLQ-I Title XVI response fields include residence address and ZIP information from the SSI master.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL023" source="APP_PUPS" target="DATA_PUPS_RESPONSE"><data key="edge_relationship_id">R81_REL023</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">DATA_PUPS_RESPONSE</data><data key="edge_operational_context">SSA's current Data Exchange catalog links the abridged prisoner response record layout associated with PUPS/prisoner exchange processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data></edge><edge id="R81_REL024" source="DATA_PUPS_RESPONSE" target="DATA_PUPS_FACILITY_ADDR"><data key="edge_relationship_id">R81_REL024</data><data key="edge_source_entity_id">DATA_PUPS_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_PUPS_FACILITY_ADDR</data><data key="edge_operational_context">The prisoner response layout includes prison/facility address and contact fields.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data></edge><edge id="R81_REL025" source="REPORT_TRUSTEES_2026" target="DATA_OACT_TR2026_SINGLE_YEAR"><data key="edge_relationship_id">R81_REL025</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">publishes_supplemental_data_as</data><data key="edge_target_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_operational_context">OACT publishes single-year historical and projected tables consistent with the 2026 OASDI Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL026" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_WORKERS_BEN_TABLE"><data key="edge_relationship_id">R81_REL026</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_OACT_WORKERS_BEN_TABLE</data><data key="edge_operational_context">The single-year table set includes Table IV.B4, Covered Workers and Beneficiaries.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL027" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TRUST_RATIO_TABLE"><data key="edge_relationship_id">R81_REL027</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_OACT_TRUST_RATIO_TABLE</data><data key="edge_operational_context">The single-year table set includes Table IV.B5, Trust Fund Ratios.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL028" source="DATA_OACT_WORKERS_BEN_TABLE" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R81_REL028</data><data key="edge_source_entity_id">DATA_OACT_WORKERS_BEN_TABLE</data><data key="edge_relationship_type">consistent_with</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">OACT labels the table as consistent with the assumptions and results of the 2026 OASDI Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL029" source="DATA_OACT_TRUST_RATIO_TABLE" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R81_REL029</data><data key="edge_source_entity_id">DATA_OACT_TRUST_RATIO_TABLE</data><data key="edge_relationship_type">consistent_with</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">OACT labels the table as consistent with the assumptions and results of the 2026 OASDI Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL031" source="FORM_SSA671" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL031</data><data key="edge_source_entity_id">FORM_SSA671</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL032" source="FORM_SSA753" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL032</data><data key="edge_source_entity_id">FORM_SSA753</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL033" source="FORM_SSA754F5" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL033</data><data key="edge_source_entity_id">FORM_SSA754F5</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL034" source="FORM_SSA760" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL034</data><data key="edge_source_entity_id">FORM_SSA760</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL035" source="FORM_SSA765" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL035</data><data key="edge_source_entity_id">FORM_SSA765</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL036" source="FORM_SSA773" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL036</data><data key="edge_source_entity_id">FORM_SSA773</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL037" source="FORM_SSA1222" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL037</data><data key="edge_source_entity_id">FORM_SSA1222</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL038" source="FORM_SSA1224" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL038</data><data key="edge_source_entity_id">FORM_SSA1224</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL039" source="FORM_SSA1724F4" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R81_REL039</data><data key="edge_source_entity_id">FORM_SSA1724F4</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists an electronic Complete Online Form and/or Upload PDF route for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL040" source="FORM_SSA1235" target="DATA_DMF"><data key="edge_relationship_id">R81_REL040</data><data key="edge_source_entity_id">FORM_SSA1235</data><data key="edge_relationship_type">establishes_reimbursable_service_for</data><data key="edge_target_entity_id">DATA_DMF</data><data key="edge_operational_context">SSA's current death-information request guidance requires Form SSA-1235 for reimbursable full death-file services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R81_REL041" source="ORG_PPDX" target="DATA_DMF"><data key="edge_relationship_id">R81_REL041</data><data key="edge_source_entity_id">ORG_PPDX</data><data key="edge_relationship_type">coordinates_request_process_for</data><data key="edge_target_entity_id">DATA_DMF</data><data key="edge_operational_context">SSA's current death-information guidance routes full-file data-exchange requests through the agency data-exchange process coordinated by PPDX.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL001" source="DB_DIGITAL_IDENTITY_FILE" target="DATA_DIGID_TRANSACTION_RECORD"><data key="edge_relationship_id">R82_REL001</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_DIGID_TRANSACTION_RECORD</data><data key="edge_operational_context">Current SORN 60-0373 identifies this category of information as maintained in the Digital Identity File Record System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL002" source="DB_DIGITAL_IDENTITY_FILE" target="DATA_DIGID_PROOF_RESULT"><data key="edge_relationship_id">R82_REL002</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_DIGID_PROOF_RESULT</data><data key="edge_operational_context">Current SORN 60-0373 identifies this category of information as maintained in the Digital Identity File Record System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL003" source="DB_DIGITAL_IDENTITY_FILE" target="DATA_DIGID_RISK_CONFIDENCE"><data key="edge_relationship_id">R82_REL003</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_DIGID_RISK_CONFIDENCE</data><data key="edge_operational_context">Current SORN 60-0373 identifies this category of information as maintained in the Digital Identity File Record System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL004" source="DB_DIGITAL_IDENTITY_FILE" target="DATA_DIGID_DEVICE_FINGERPRINT"><data key="edge_relationship_id">R82_REL004</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_DIGID_DEVICE_FINGERPRINT</data><data key="edge_operational_context">Current SORN 60-0373 identifies this category of information as maintained in the Digital Identity File Record System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL005" source="DB_DIGITAL_IDENTITY_FILE" target="DATA_DIGID_ACCESS_LOG"><data key="edge_relationship_id">R82_REL005</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_DIGID_ACCESS_LOG</data><data key="edge_operational_context">Current SORN 60-0373 identifies this category of information as maintained in the Digital Identity File Record System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL006" source="DB_DIGITAL_IDENTITY_FILE" target="DATA_DIGID_EVIDENCE_IMAGE"><data key="edge_relationship_id">R82_REL006</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_DIGID_EVIDENCE_IMAGE</data><data key="edge_operational_context">Current SORN 60-0373 identifies this category of information as maintained in the Digital Identity File Record System.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL007" source="DB_DIGITAL_IDENTITY_FILE" target="ORG_IRS"><data key="edge_relationship_id">R82_REL007</data><data key="edge_source_entity_id">DB_DIGITAL_IDENTITY_FILE</data><data key="edge_relationship_type">may_disclose_wage_submission_digital_identity_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">SORN 60-0373 routine use permits disclosure to IRS of digital identity information associated with electronic wage submissions processed by SSA for investigation of fraud, abuse, or security risks.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Routine-use authority; does not imply every digital identity record is sent to IRS.</data></edge><edge id="R82_REL008" source="APP_EQA" target="DATA_EQA_DYNAMIC_REPORTING"><data key="edge_relationship_id">R82_REL008</data><data key="edge_source_entity_id">APP_EQA</data><data key="edge_relationship_type">uses_for_analytical_reporting</data><data key="edge_target_entity_id">DATA_EQA_DYNAMIC_REPORTING</data><data key="edge_operational_context">2018 QAS PIA explicitly lists analytical reporting from the dynamic reporting dataset as an eQA function.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Historical implementation evidence within 10-year horizon; current physical dataset status unconfirmed.</data></edge><edge id="R82_REL009" source="FORM_IRS4029" target="PROC_IRS4029_RETURN"><data key="edge_relationship_id">R82_REL009</data><data key="edge_source_entity_id">FORM_IRS4029</data><data key="edge_relationship_type">processed_through</data><data key="edge_target_entity_id">PROC_IRS4029_RETURN</data><data key="edge_operational_context">Current POMS defines the return-processing workflow for an original processed Form 4029 returned from IRS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL010" source="ORG_IRS" target="PROC_IRS4029_RETURN"><data key="edge_relationship_id">R82_REL010</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">returns_processed_form_to</data><data key="edge_target_entity_id">PROC_IRS4029_RETURN</data><data key="edge_operational_context">Current POMS describes the workflow when an original processed Form 4029 is returned to SSA Religious Exemption Unit from IRS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL011" source="PROC_IRS4029_RETURN" target="SYS_NUMIDENT"><data key="edge_relationship_id">R82_REL011</data><data key="edge_source_entity_id">PROC_IRS4029_RETURN</data><data key="edge_relationship_type">verifies_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Workflow requires verification of SSN and date of birth before remaining processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL012" source="PROC_IRS4029_RETURN" target="APP_PEBES"><data key="edge_relationship_id">R82_REL012</data><data key="edge_source_entity_id">PROC_IRS4029_RETURN</data><data key="edge_relationship_type">suppresses_social_security_statement_in</data><data key="edge_target_entity_id">APP_PEBES</data><data key="edge_operational_context">Current POMS directs staff to suppress the Social Security Statement as part of returned Form 4029 processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL013" source="PROC_IRS4029_RETURN" target="APP_ESCORR"><data key="edge_relationship_id">R82_REL013</data><data key="edge_source_entity_id">PROC_IRS4029_RETURN</data><data key="edge_relationship_type">keys_required_information_via</data><data key="edge_target_entity_id">APP_ESCORR</data><data key="edge_operational_context">Current POMS directs staff to key required information into Enumeration System Correspondence (ESCORR).</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL014" source="APP_ESCORR" target="SYS_NUMIDENT"><data key="edge_relationship_id">R82_REL014</data><data key="edge_source_entity_id">APP_ESCORR</data><data key="edge_relationship_type">supports_q_action_on</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS states ESCORR is used to key required information to “Q” the Numident; the public source does not define internal field mechanics.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">No internal Numident field or transport mechanism inferred.</data></edge><edge id="R82_REL015" source="PROC_IRS4029_RETURN" target="DB_GIR"><data key="edge_relationship_id">R82_REL015</data><data key="edge_source_entity_id">PROC_IRS4029_RETURN</data><data key="edge_relationship_type">scans_form_into</data><data key="edge_target_entity_id">DB_GIR</data><data key="edge_operational_context">Current POMS directs returned Form 4029 to be scanned into General Information Retrieval.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL016" source="DB_GIR" target="FORM_IRS4029"><data key="edge_relationship_id">R82_REL016</data><data key="edge_source_entity_id">DB_GIR</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">FORM_IRS4029</data><data key="edge_operational_context">POMS identifies GIR as a repository housing historical and new IRS Forms 4029 received from IRS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL017" source="DB_GIR" target="FORM_IRS4361"><data key="edge_relationship_id">R82_REL017</data><data key="edge_source_entity_id">DB_GIR</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">FORM_IRS4361</data><data key="edge_operational_context">POMS identifies GIR as a repository housing historical and new IRS Forms 4361 received from IRS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL018" source="FORM_SSA2855" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL018</data><data key="edge_source_entity_id">FORM_SSA2855</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL019" source="FORM_SSA3369BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL019</data><data key="edge_source_entity_id">FORM_SSA3369BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL020" source="FORM_SSA3371BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL020</data><data key="edge_source_entity_id">FORM_SSA3371BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL021" source="FORM_SSA3373BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL021</data><data key="edge_source_entity_id">FORM_SSA3373BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL022" source="FORM_SSA3375BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL022</data><data key="edge_source_entity_id">FORM_SSA3375BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL023" source="FORM_SSA3376BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL023</data><data key="edge_source_entity_id">FORM_SSA3376BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL024" source="FORM_SSA3377BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL024</data><data key="edge_source_entity_id">FORM_SSA3377BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL025" source="FORM_SSA3378BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL025</data><data key="edge_source_entity_id">FORM_SSA3378BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL026" source="FORM_SSA3379BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL026</data><data key="edge_source_entity_id">FORM_SSA3379BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL027" source="FORM_SSA3380BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL027</data><data key="edge_source_entity_id">FORM_SSA3380BK</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL028" source="FORM_SSA4111" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL028</data><data key="edge_source_entity_id">FORM_SSA4111</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL029" source="FORM_SSA5062" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL029</data><data key="edge_source_entity_id">FORM_SSA5062</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL030" source="FORM_SSA5064" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL030</data><data key="edge_source_entity_id">FORM_SSA5064</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL031" source="FORM_SSA7104" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL031</data><data key="edge_source_entity_id">FORM_SSA7104</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL032" source="FORM_SSA7157" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL032</data><data key="edge_source_entity_id">FORM_SSA7157</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL033" source="FORM_SSA8552" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R82_REL033</data><data key="edge_source_entity_id">FORM_SSA8552</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's current Forms page lists Complete Online Form and Upload PDF routes for this form through the Upload Documents experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL034" source="ORG_SSA_OCACT" target="DATA_OACT_INSURED_WORKERS_STATUS"><data key="edge_relationship_id">R82_REL034</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_INSURED_WORKERS_STATUS</data><data key="edge_operational_context">OACT publishes the current statistical table as a public actuarial/statistical data product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL035" source="REPORT_TRUSTEES_2026" target="DATA_OACT_INSURED_WORKERS_STATUS"><data key="edge_relationship_id">R82_REL035</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">provides_estimation_basis_for</data><data key="edge_target_entity_id">DATA_OACT_INSURED_WORKERS_STATUS</data><data key="edge_operational_context">The OACT table identifies its estimates as based on the 2026 Trustees Report or its intermediate assumptions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL036" source="ORG_SSA_OCACT" target="DATA_OACT_FULLY_INSURED_WORKERS"><data key="edge_relationship_id">R82_REL036</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_FULLY_INSURED_WORKERS</data><data key="edge_operational_context">OACT publishes the current statistical table as a public actuarial/statistical data product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL037" source="REPORT_TRUSTEES_2026" target="DATA_OACT_FULLY_INSURED_WORKERS"><data key="edge_relationship_id">R82_REL037</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">provides_estimation_basis_for</data><data key="edge_target_entity_id">DATA_OACT_FULLY_INSURED_WORKERS</data><data key="edge_operational_context">The OACT table identifies its estimates as based on the 2026 Trustees Report or its intermediate assumptions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL038" source="ORG_SSA_OCACT" target="DATA_OACT_DISABILITY_INSURED_WORKERS"><data key="edge_relationship_id">R82_REL038</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_DISABILITY_INSURED_WORKERS</data><data key="edge_operational_context">OACT publishes the current statistical table as a public actuarial/statistical data product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL039" source="REPORT_TRUSTEES_2026" target="DATA_OACT_DISABILITY_INSURED_WORKERS"><data key="edge_relationship_id">R82_REL039</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">provides_estimation_basis_for</data><data key="edge_target_entity_id">DATA_OACT_DISABILITY_INSURED_WORKERS</data><data key="edge_operational_context">The OACT table identifies its estimates as based on the 2026 Trustees Report or its intermediate assumptions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL040" source="ORG_SSA_OCACT" target="DATA_OACT_SOCSEC_AREA_INSURED"><data key="edge_relationship_id">R82_REL040</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_SOCSEC_AREA_INSURED</data><data key="edge_operational_context">OACT publishes the current statistical table as a public actuarial/statistical data product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL041" source="REPORT_TRUSTEES_2026" target="DATA_OACT_SOCSEC_AREA_INSURED"><data key="edge_relationship_id">R82_REL041</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">provides_estimation_basis_for</data><data key="edge_target_entity_id">DATA_OACT_SOCSEC_AREA_INSURED</data><data key="edge_operational_context">The OACT table identifies its estimates as based on the 2026 Trustees Report or its intermediate assumptions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL042" source="DATA_CWHS" target="DATA_OACT_INSURED_WORKERS_STATUS"><data key="edge_relationship_id">R82_REL042</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">supports_estimation_of</data><data key="edge_target_entity_id">DATA_OACT_INSURED_WORKERS_STATUS</data><data key="edge_operational_context">The OACT source note says the 2026 Trustees Report estimates are based in part on the Continuous Work History Sample, 1-percent sample.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL043" source="DATA_CWHS" target="DATA_OACT_FULLY_INSURED_WORKERS"><data key="edge_relationship_id">R82_REL043</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">supports_estimation_of</data><data key="edge_target_entity_id">DATA_OACT_FULLY_INSURED_WORKERS</data><data key="edge_operational_context">The OACT source note says the 2026 Trustees Report estimates are based in part on the Continuous Work History Sample, 1-percent sample.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL044" source="DATA_CWHS" target="DATA_OACT_DISABILITY_INSURED_WORKERS"><data key="edge_relationship_id">R82_REL044</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">supports_estimation_of</data><data key="edge_target_entity_id">DATA_OACT_DISABILITY_INSURED_WORKERS</data><data key="edge_operational_context">The OACT source note says the 2026 Trustees Report estimates are based in part on the Continuous Work History Sample, 1-percent sample.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL045" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_INSURED_WORKERS_STATUS"><data key="edge_relationship_id">R82_REL045</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">defers_section_4c_publication_to</data><data key="edge_target_entity_id">DATA_OACT_INSURED_WORKERS_STATUS</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement says section 4.C is discontinued because these insured-worker tables are already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL046" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_FULLY_INSURED_WORKERS"><data key="edge_relationship_id">R82_REL046</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">defers_section_4c_publication_to</data><data key="edge_target_entity_id">DATA_OACT_FULLY_INSURED_WORKERS</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement says section 4.C is discontinued because these insured-worker tables are already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL047" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_DISABILITY_INSURED_WORKERS"><data key="edge_relationship_id">R82_REL047</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">defers_section_4c_publication_to</data><data key="edge_target_entity_id">DATA_OACT_DISABILITY_INSURED_WORKERS</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement says section 4.C is discontinued because these insured-worker tables are already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL048" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_SOCSEC_AREA_INSURED"><data key="edge_relationship_id">R82_REL048</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">defers_section_4c_publication_to</data><data key="edge_target_entity_id">DATA_OACT_SOCSEC_AREA_INSURED</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement says section 4.C is discontinued because these insured-worker tables are already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data></edge><edge id="R82_REL049" source="ARCH_BI" target="DATA_COMBINED_DISABILITY_APT"><data key="edge_relationship_id">R82_REL049</data><data key="edge_source_entity_id">ARCH_BI</data><data key="edge_relationship_type">supports_publication_of</data><data key="edge_target_entity_id">DATA_COMBINED_DISABILITY_APT</data><data key="edge_operational_context">SSA Open Data states elapsed time is electronically collected for every processed disability case and business intelligence capabilities present the data in data stores.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Generic BI architecture relationship only; no specific repository, ETL, or database is inferred.</data></edge><edge id="R83_REL001" source="ORG_NCHS" target="PROC_OACT_MORTALITY_PROJ"><data key="edge_relationship_id">R83_REL001</data><data key="edge_source_entity_id">ORG_NCHS</data><data key="edge_relationship_type">provides_mortality_data_to</data><data key="edge_target_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_operational_context">2026 Trustees Report uses NCHS data for historical death rates under age 65, cause-specific death rates, and provisional 2025 estimates.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL002" source="ORG_CMS" target="PROC_OACT_MORTALITY_PROJ"><data key="edge_relationship_id">R83_REL002</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">provides_medicare_mortality_data_to</data><data key="edge_target_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_operational_context">2026 Trustees Report uses final and preliminary Medicare death data for ages 65 and over.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL003" source="REPORT_TRUSTEES_2026" target="PROC_OACT_MORTALITY_PROJ"><data key="edge_relationship_id">R83_REL003</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">documents_method</data><data key="edge_target_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_operational_context">The 2026 Trustees Report documents mortality assumptions, historical input data, regressions, and alternative projection paths.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL004" source="PROC_OACT_MORTALITY_PROJ" target="DATA_OACT_DEATH_PROB_2026"><data key="edge_relationship_id">R83_REL004</data><data key="edge_source_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_OACT_DEATH_PROB_2026</data><data key="edge_operational_context">Projected central death rates are used to calculate probabilities of death by single year of age and sex; public tables publish historical and projected probabilities.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL005" source="ORG_SSA_OCACT" target="DATA_OACT_DEATH_PROB_2026"><data key="edge_relationship_id">R83_REL005</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_DEATH_PROB_2026</data><data key="edge_operational_context">OACT publishes the downloadable 2026 Trustees Report mortality tables.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL006" source="ORG_SSA_OCACT" target="DATA_OACT_PERIOD_LIFE_2026"><data key="edge_relationship_id">R83_REL006</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_PERIOD_LIFE_2026</data><data key="edge_operational_context">OACT publishes the downloadable 2026 Trustees Report period life tables.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL007" source="ORG_SSA_OCACT" target="DATA_OACT_COHORT_LIFE_2026"><data key="edge_relationship_id">R83_REL007</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_COHORT_LIFE_2026</data><data key="edge_operational_context">OACT publishes the downloadable 2026 Trustees Report cohort life tables.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL008" source="ORG_SSA_OCACT" target="DATA_OACT_SOCSEC_POP_DOWNLOAD_2026"><data key="edge_relationship_id">R83_REL008</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_SOCSEC_POP_DOWNLOAD_2026</data><data key="edge_operational_context">OACT publishes downloadable Social Security area population tables associated with the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL009" source="ORG_SSA_OCACT" target="DATA_OACT_ACTUARIAL_LIFE_TABLE"><data key="edge_relationship_id">R83_REL009</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_ACTUARIAL_LIFE_TABLE</data><data key="edge_operational_context">OACT publishes a current actuarial period life table view, including the 2023 table used in the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL010" source="PROC_OACT_MORTALITY_PROJ" target="DATA_OACT_PERIOD_LIFE_2026"><data key="edge_relationship_id">R83_REL010</data><data key="edge_source_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_relationship_type">supports_life_table_inputs</data><data key="edge_target_entity_id">DATA_OACT_PERIOD_LIFE_2026</data><data key="edge_operational_context">Period life tables depend on age/sex mortality probabilities produced from the Trustees mortality method; exact internal publication tooling is not identified.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Analytical lineage, not a software-interface claim.</data></edge><edge id="R83_REL011" source="PROC_OACT_MORTALITY_PROJ" target="DATA_OACT_COHORT_LIFE_2026"><data key="edge_relationship_id">R83_REL011</data><data key="edge_source_entity_id">PROC_OACT_MORTALITY_PROJ</data><data key="edge_relationship_type">supports_life_table_inputs</data><data key="edge_target_entity_id">DATA_OACT_COHORT_LIFE_2026</data><data key="edge_operational_context">Cohort life tables rely on mortality experience/projections across ages and years; exact internal publication tooling is not identified.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Analytical lineage, not a software-interface claim.</data></edge><edge id="R83_REL012" source="DATA_OACT_ACTUARIAL_LIFE_TABLE" target="DATA_OACT_PERIOD_LIFE_2026"><data key="edge_relationship_id">R83_REL012</data><data key="edge_source_entity_id">DATA_OACT_ACTUARIAL_LIFE_TABLE</data><data key="edge_relationship_type">is_public_view_of</data><data key="edge_target_entity_id">DATA_OACT_PERIOD_LIFE_2026</data><data key="edge_operational_context">Current Actuarial Life Table page is a period life-table presentation aligned to Trustees Report mortality tables.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Public-presentation relationship; not a claim of shared physical storage.</data></edge><edge id="R83_REL013" source="MODEL_OACT_POPULATION" target="DATA_OACT_SOCSEC_POP_DOWNLOAD_2026"><data key="edge_relationship_id">R83_REL013</data><data key="edge_source_entity_id">MODEL_OACT_POPULATION</data><data key="edge_relationship_type">supports_publication_of</data><data key="edge_target_entity_id">DATA_OACT_SOCSEC_POP_DOWNLOAD_2026</data><data key="edge_operational_context">Atlas already validates the OCACT population projection model; Run 83 links it conservatively to the public population-table family.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Publication lineage is logical; internal execution and export tooling remain unknown.</data></edge><edge id="R83_REL014" source="PROG_HRS" target="DATA_HRS_IMPUTED_LIFETIME_EARNINGS"><data key="edge_relationship_id">R83_REL014</data><data key="edge_source_entity_id">PROG_HRS</data><data key="edge_relationship_type">publishes_restricted</data><data key="edge_target_entity_id">DATA_HRS_IMPUTED_LIFETIME_EARNINGS</data><data key="edge_operational_context">HRS lists the product as restricted SSA data, latest release April 2026.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL015" source="EX_HRS_LINKAGE" target="DATA_HRS_IMPUTED_LIFETIME_EARNINGS"><data key="edge_relationship_id">R83_REL015</data><data key="edge_source_entity_id">EX_HRS_LINKAGE</data><data key="edge_relationship_type">supplies_matched_ssa_earnings_for</data><data key="edge_target_entity_id">DATA_HRS_IMPUTED_LIFETIME_EARNINGS</data><data key="edge_operational_context">HRS states that matched SSA earnings records are used where available, with projection and imputation for other periods/respondents.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Exact HRS extraction file feeding this derived product is not stated on the product page.</data></edge><edge id="R83_REL016" source="PROG_HRS" target="DATA_HRS_SS_WEIGHTS"><data key="edge_relationship_id">R83_REL016</data><data key="edge_source_entity_id">PROG_HRS</data><data key="edge_relationship_type">publishes_restricted</data><data key="edge_target_entity_id">DATA_HRS_SS_WEIGHTS</data><data key="edge_operational_context">HRS lists Cross-Wave Social Security Weights as a restricted SSA data product.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL017" source="DATA_HRS_SS_WEIGHTS" target="DATA_HRS_CYBF"><data key="edge_relationship_id">R83_REL017</data><data key="edge_source_entity_id">DATA_HRS_SS_WEIGHTS</data><data key="edge_relationship_type">distributed_with</data><data key="edge_target_entity_id">DATA_HRS_CYBF</data><data key="edge_operational_context">HRS says the weights product is included with the Benefits respondent dataset.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL018" source="DATA_HRS_SS_WEIGHTS" target="DATA_HRS_SER"><data key="edge_relationship_id">R83_REL018</data><data key="edge_source_entity_id">DATA_HRS_SS_WEIGHTS</data><data key="edge_relationship_type">distributed_with</data><data key="edge_target_entity_id">DATA_HRS_SER</data><data key="edge_operational_context">HRS says the weights product is included with the Summary Earnings respondent dataset.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL019" source="DATA_HRS_SS_WEIGHTS" target="DATA_HRS_DER"><data key="edge_relationship_id">R83_REL019</data><data key="edge_source_entity_id">DATA_HRS_SS_WEIGHTS</data><data key="edge_relationship_type">distributed_with</data><data key="edge_target_entity_id">DATA_HRS_DER</data><data key="edge_operational_context">HRS says the weights product is included with the Detail Earnings respondent dataset.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL020" source="DB_SSI_IRS_INTERFACE" target="DATA_SSI_IRS_CONTROLLED_ALERT"><data key="edge_relationship_id">R83_REL020</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="edge_operational_context">POMS describes alerts as printouts from the IRS database for records exceeding tolerances.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL021" source="DATA_SSI_IRS_CONTROLLED_ALERT" target="WORK_SSI_IRS_5B_DIARY"><data key="edge_relationship_id">R83_REL021</data><data key="edge_source_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="edge_relationship_type">corresponds_to_work_control</data><data key="edge_target_entity_id">WORK_SSI_IRS_5B_DIARY</data><data key="edge_operational_context">Controlled-alert cases have a 5B diary posted to the SSR; the alert and diary are modeled separately.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL022" source="PORTAL_SUMS_MCAS_MI_CENTRAL" target="DATA_SSI_IRS_CONTROLLED_ALERT"><data key="edge_relationship_id">R83_REL022</data><data key="edge_source_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_relationship_type">retrieves</data><data key="edge_target_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="edge_operational_context">Technicians may retrieve controlled IRS data overnight through RZ/LI listings in MI Central.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL023" source="APP_SSTNG" target="DATA_SSI_IRS_CONTROLLED_ALERT"><data key="edge_relationship_id">R83_REL023</data><data key="edge_source_entity_id">APP_SSTNG</data><data key="edge_relationship_type">retrieves</data><data key="edge_target_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="edge_operational_context">POMS says the same controlled IRS data may be retrieved immediately through SSTNG.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL024" source="DB_SSI_IRS_INTERFACE" target="DATA_SSI_IRS_INFORMATIONAL_ALERT"><data key="edge_relationship_id">R83_REL024</data><data key="edge_source_entity_id">DB_SSI_IRS_INTERFACE</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_SSI_IRS_INFORMATIONAL_ALERT</data><data key="edge_operational_context">SSI/IRS interface identifies informational alerts for specified below-tolerance high-error-profile redeterminations.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL025" source="PORTAL_SUMS_MCAS_MI_CENTRAL" target="DATA_SSI_IRS_INFORMATIONAL_ALERT"><data key="edge_relationship_id">R83_REL025</data><data key="edge_source_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_relationship_type">retrieves</data><data key="edge_target_entity_id">DATA_SSI_IRS_INFORMATIONAL_ALERT</data><data key="edge_operational_context">Informational alerts are available through MI Central.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL026" source="APP_SSTNG" target="DATA_SSI_IRS_INFORMATIONAL_ALERT"><data key="edge_relationship_id">R83_REL026</data><data key="edge_source_entity_id">APP_SSTNG</data><data key="edge_relationship_type">conditionally_retrieves</data><data key="edge_target_entity_id">DATA_SSI_IRS_INFORMATIONAL_ALERT</data><data key="edge_operational_context">For a high-error-profile redetermination, POMS says the informational alert is available in SSTNG.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL027" source="ORG_BENEFICIARY_FI" target="DATA_FI_LOCATE_MAIL_ADDR"><data key="edge_relationship_id">R83_REL027</data><data key="edge_source_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_relationship_type">supplies</data><data key="edge_target_entity_id">DATA_FI_LOCATE_MAIL_ADDR</data><data key="edge_operational_context">Financial institution can provide SSA the current mailing address it has for a Title II beneficiary during locate development.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL028" source="FORM_E3759" target="DATA_FI_LOCATE_MAIL_ADDR"><data key="edge_relationship_id">R83_REL028</data><data key="edge_source_entity_id">FORM_E3759</data><data key="edge_relationship_type">requests</data><data key="edge_target_entity_id">DATA_FI_LOCATE_MAIL_ADDR</data><data key="edge_operational_context">E3759 explicitly asks the financial institution to provide the customer current mailing address.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL029" source="DATA_FI_LOCATE_MAIL_ADDR" target="PROC_T2_UNDELIV_ADDRESS"><data key="edge_relationship_id">R83_REL029</data><data key="edge_source_entity_id">DATA_FI_LOCATE_MAIL_ADDR</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_operational_context">Current policy uses financial-institution address information in Title II undeliverable-mail/whereabouts development.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL030" source="DATA_FI_LOCATE_MAIL_ADDR" target="APP_POS"><data key="edge_relationship_id">R83_REL030</data><data key="edge_source_entity_id">DATA_FI_LOCATE_MAIL_ADDR</data><data key="edge_relationship_type">may_be_entered_through</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">After development, policy directs staff to input a new Title II address through POS; this is not an automatic FI-to-MBR write.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Human/workflow-controlled update path.</data></edge><edge id="R83_REL031" source="ORG_USPS" target="DATA_USPS_LOCATE_MAIL_ADDR"><data key="edge_relationship_id">R83_REL031</data><data key="edge_source_entity_id">ORG_USPS</data><data key="edge_relationship_type">supplies</data><data key="edge_target_entity_id">DATA_USPS_LOCATE_MAIL_ADDR</data><data key="edge_operational_context">USPS may return current address information requested during beneficiary locate development.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL032" source="FORM_SSA_L2001" target="DATA_USPS_LOCATE_MAIL_ADDR"><data key="edge_relationship_id">R83_REL032</data><data key="edge_source_entity_id">FORM_SSA_L2001</data><data key="edge_relationship_type">requests</data><data key="edge_target_entity_id">DATA_USPS_LOCATE_MAIL_ADDR</data><data key="edge_operational_context">SSA-L2001 is sent to USPS servicing the address of record to obtain address information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL033" source="DATA_USPS_LOCATE_MAIL_ADDR" target="PROC_T2_UNDELIV_ADDRESS"><data key="edge_relationship_id">R83_REL033</data><data key="edge_source_entity_id">DATA_USPS_LOCATE_MAIL_ADDR</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">PROC_T2_UNDELIV_ADDRESS</data><data key="edge_operational_context">USPS locate response is used in undeliverable-mail address development.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL034" source="DATA_USPS_LOCATE_MAIL_ADDR" target="APP_POS"><data key="edge_relationship_id">R83_REL034</data><data key="edge_source_entity_id">DATA_USPS_LOCATE_MAIL_ADDR</data><data key="edge_relationship_type">may_be_entered_through</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">After development, a new Title II address may be input through POS; this locate-letter path is separate from NCOA automated processing.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Human/workflow-controlled update path.</data></edge><edge id="R83_REL035" source="PROC_VENDOR_REPO_SUBMISSION" target="DATA_VENDOR_CAPABILITY_STATEMENT"><data key="edge_relationship_id">R83_REL035</data><data key="edge_source_entity_id">PROC_VENDOR_REPO_SUBMISSION</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_VENDOR_CAPABILITY_STATEMENT</data><data key="edge_operational_context">Vendor email submission produces a capability-statement record and related metadata/attachments for repository inclusion.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL036" source="DATA_VENDOR_CAPABILITY_STATEMENT" target="DB_VENDOR_INFO_REPO"><data key="edge_relationship_id">R83_REL036</data><data key="edge_source_entity_id">DATA_VENDOR_CAPABILITY_STATEMENT</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">DB_VENDOR_INFO_REPO</data><data key="edge_operational_context">Current vendor-repository guidance states SSA adds submitted capability information to the repository for market research.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL037" source="ORG_SSA_OAG" target="DB_VENDOR_INFO_REPO"><data key="edge_relationship_id">R83_REL037</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers</data><data key="edge_target_entity_id">DB_VENDOR_INFO_REPO</data><data key="edge_operational_context">OAG publishes and manages the vendor-repository submission guidance for SSA market research.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL038" source="DB_VENDOR_INFO_REPO" target="PLAT_SHAREPOINT"><data key="edge_relationship_id">R83_REL038</data><data key="edge_source_entity_id">DB_VENDOR_INFO_REPO</data><data key="edge_relationship_type">historically_implemented_on</data><data key="edge_target_entity_id">PLAT_SHAREPOINT</data><data key="edge_operational_context">2018 SSA Industry Day Q&amp;A identifies the vendor repository as an internal agency SharePoint site.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Time-scoped 2018 implementation evidence; current 2026 physical implementation is not established.</data></edge><edge id="R83_REL039" source="PROC_REP_PAYEE_CAPABILITY_DEV" target="DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE"><data key="edge_relationship_id">R83_REL039</data><data key="edge_source_entity_id">PROC_REP_PAYEE_CAPABILITY_DEV</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE</data><data key="edge_operational_context">Current POMS requires evaluation of medical evidence when beneficiary capability is questionable.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL040" source="PROC_REP_PAYEE_CAPABILITY_DEV" target="DATA_REP_PAYEE_LAY_CAP_EVIDENCE"><data key="edge_relationship_id">R83_REL040</data><data key="edge_source_entity_id">PROC_REP_PAYEE_CAPABILITY_DEV</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_REP_PAYEE_LAY_CAP_EVIDENCE</data><data key="edge_operational_context">Current POMS requires development of third-party lay evidence in applicable capability cases.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL041" source="PROC_REP_PAYEE_CAPABILITY_DEV" target="DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE"><data key="edge_relationship_id">R83_REL041</data><data key="edge_source_entity_id">PROC_REP_PAYEE_CAPABILITY_DEV</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE</data><data key="edge_operational_context">Current POMS requires certified court-order development when legal incompetence is alleged.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL042" source="FORM_SSA787" target="DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE"><data key="edge_relationship_id">R83_REL042</data><data key="edge_source_entity_id">FORM_SSA787</data><data key="edge_relationship_type">preferred_vehicle_for</data><data key="edge_target_entity_id">DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE</data><data key="edge_operational_context">SSA-787 is the preferred vehicle for medical-source capability evidence.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL043" source="FORM_SSA788" target="DATA_REP_PAYEE_LAY_CAP_EVIDENCE"><data key="edge_relationship_id">R83_REL043</data><data key="edge_source_entity_id">FORM_SSA788</data><data key="edge_relationship_type">documents</data><data key="edge_target_entity_id">DATA_REP_PAYEE_LAY_CAP_EVIDENCE</data><data key="edge_operational_context">SSA-788 is required when contacting a custodian different from the payee applicant for lay evidence.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL044" source="DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE" target="REPO_NDRED"><data key="edge_relationship_id">R83_REL044</data><data key="edge_source_entity_id">DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">POMS directs storage of medical capability evidence in NDRed under the beneficiary claim number or in eView.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL045" source="DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE" target="APP_EVIEW"><data key="edge_relationship_id">R83_REL045</data><data key="edge_source_entity_id">DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE</data><data key="edge_relationship_type">may_be_stored_or_viewed_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">POMS permits medical capability evidence in eView under the beneficiary own account number.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL046" source="DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE" target="APP_EP"><data key="edge_relationship_id">R83_REL046</data><data key="edge_source_entity_id">DATA_REP_PAYEE_MEDICAL_CAP_EVIDENCE</data><data key="edge_relationship_type">submitted_or_stored_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Evidence Portal is specified as a route for storing capability evidence in NDRed/eView.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL047" source="DATA_REP_PAYEE_LAY_CAP_EVIDENCE" target="REPO_NDRED"><data key="edge_relationship_id">R83_REL047</data><data key="edge_source_entity_id">DATA_REP_PAYEE_LAY_CAP_EVIDENCE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Signed or paper lay evidence is retained in NDRed when system report-of-contact documentation is unavailable or paper evidence is used.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL048" source="DATA_REP_PAYEE_LAY_CAP_EVIDENCE" target="APP_EVIEW"><data key="edge_relationship_id">R83_REL048</data><data key="edge_source_entity_id">DATA_REP_PAYEE_LAY_CAP_EVIDENCE</data><data key="edge_relationship_type">may_be_stored_or_viewed_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">POMS provides eView as a retention path for capability evidence.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL049" source="DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE" target="REPO_NDRED"><data key="edge_relationship_id">R83_REL049</data><data key="edge_source_entity_id">DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Certified court orders used for capability decisions are stored in NDRed or eView.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL050" source="DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE" target="APP_EVIEW"><data key="edge_relationship_id">R83_REL050</data><data key="edge_source_entity_id">DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE</data><data key="edge_relationship_type">may_be_stored_or_viewed_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Certified court orders may be retained in eView under the BOAN.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R83_REL051" source="DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE" target="APP_ERPS"><data key="edge_relationship_id">R83_REL051</data><data key="edge_source_entity_id">DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS directs staff to document legal-incompetence details, source, certification date, and description in eRPS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R84_REL001" source="SYS_NUMIDENT" target="DATA_NUMIDENT_INTERNAL_PROC_REF"><data key="edge_relationship_id">R84_REL001</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_INTERNAL_PROC_REF</data><data key="edge_operational_context">Current SORN 60-0058 includes this element or indicator within the Numident/SSN application record environment.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical field relationship; physical schema not inferred.</data></edge><edge id="R84_REL002" source="SYS_NUMIDENT" target="DATA_NUMIDENT_ALIEN_REG_NUM"><data key="edge_relationship_id">R84_REL002</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_ALIEN_REG_NUM</data><data key="edge_operational_context">Current SORN 60-0058 includes this element or indicator within the Numident/SSN application record environment.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical field relationship; physical schema not inferred.</data></edge><edge id="R84_REL003" source="SYS_NUMIDENT" target="DATA_NUMIDENT_CITIZENSHIP_CODE"><data key="edge_relationship_id">R84_REL003</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_CITIZENSHIP_CODE</data><data key="edge_operational_context">Current SORN 60-0058 includes this element or indicator within the Numident/SSN application record environment.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical field relationship; physical schema not inferred.</data></edge><edge id="R84_REL004" source="SYS_NUMIDENT" target="DATA_NUMIDENT_SPECIAL_INDICATOR_CODE"><data key="edge_relationship_id">R84_REL004</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_SPECIAL_INDICATOR_CODE</data><data key="edge_operational_context">Current SORN 60-0058 includes this element or indicator within the Numident/SSN application record environment.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical field relationship; physical schema not inferred.</data></edge><edge id="R84_REL005" source="SYS_NUMIDENT" target="DATA_NUMIDENT_MULTI_SSN_XREF_ATTR"><data key="edge_relationship_id">R84_REL005</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_MULTI_SSN_XREF_ATTR</data><data key="edge_operational_context">Current SORN 60-0058 includes this element or indicator within the Numident/SSN application record environment.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical field relationship; physical schema not inferred.</data></edge><edge id="R84_REL006" source="SYS_NUMIDENT" target="DATA_NUMIDENT_BENEFIT_CLAIM_IND"><data key="edge_relationship_id">R84_REL006</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_BENEFIT_CLAIM_IND</data><data key="edge_operational_context">Current SORN 60-0058 includes this element or indicator within the Numident/SSN application record environment.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical field relationship; physical schema not inferred.</data></edge><edge id="R84_REL007" source="SYS_NUMIDENT" target="DATA_NUMIDENT_FORM_CODE"><data key="edge_relationship_id">R84_REL007</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NUMIDENT_FORM_CODE</data><data key="edge_operational_context">Current SORN 60-0058 includes this element or indicator within the Numident/SSN application record environment.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical field relationship; physical schema not inferred.</data></edge><edge id="R84_REL008" source="DATA_NUMIDENT_EAE_FMC_A" target="DATA_NUMIDENT_FORM_CODE"><data key="edge_relationship_id">R84_REL008</data><data key="edge_source_entity_id">DATA_NUMIDENT_EAE_FMC_A</data><data key="edge_relationship_type">is_specific_value_of</data><data key="edge_target_entity_id">DATA_NUMIDENT_FORM_CODE</data><data key="edge_operational_context">Current SORN describes a generic form code; existing policy separately documents Form Code A for Enumeration at Entry.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Semantic specialization only; no physical schema inference.</data></edge><edge id="R84_REL009" source="DATA_NUMIDENT_SPIN6" target="DATA_NUMIDENT_SPECIAL_INDICATOR_CODE"><data key="edge_relationship_id">R84_REL009</data><data key="edge_source_entity_id">DATA_NUMIDENT_SPIN6</data><data key="edge_relationship_type">is_specific_value_of</data><data key="edge_target_entity_id">DATA_NUMIDENT_SPECIAL_INDICATOR_CODE</data><data key="edge_operational_context">Current SORN establishes a generic special-indicator-code field; existing policy separately documents Special Indicator 6 for the HALE use case.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Semantic specialization only.</data></edge><edge id="R84_REL010" source="SYS_NUMIDENT" target="SVC_DNP"><data key="edge_relationship_id">R84_REL010</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">authorized_for_disclosure_to</data><data key="edge_target_entity_id">SVC_DNP</data><data key="edge_operational_context">The November 2025 modified SORN added a routine use permitting disclosure to Treasury for payment and award eligibility review through the Do Not Pay Working System when legal requirements are met.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Privacy Act authorization does not by itself establish that a production interface is deployed.</data></edge><edge id="R84_REL011" source="SYS_NUMIDENT" target="SVC_DNP"><data key="edge_relationship_id">R84_REL011</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">proposed_verification_source_for</data><data key="edge_target_entity_id">SVC_DNP</data><data key="edge_operational_context">Treasury proposed designating Numident to Do Not Pay for verification of name, SSN, and optional date of birth for health or income-maintenance payments or awards.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Proposal only. A later final Federal Register designation would be required.</data></edge><edge id="R84_REL012" source="SYS_NUMIDENT" target="DATA_NUMIDENT_DNP_MATCH_RESPONSE"><data key="edge_relationship_id">R84_REL012</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">proposed_to_produce</data><data key="edge_target_entity_id">DATA_NUMIDENT_DNP_MATCH_RESPONSE</data><data key="edge_operational_context">Under the proposed Do Not Pay design, SSA would match submitted identity attributes against Numident and produce numerical response codes indicating match or non-match.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Proposal only; no corrected PII would be returned under the described design.</data></edge><edge id="R84_REL013" source="DATA_NUMIDENT_DNP_MATCH_RESPONSE" target="SVC_DNP"><data key="edge_relationship_id">R84_REL013</data><data key="edge_source_entity_id">DATA_NUMIDENT_DNP_MATCH_RESPONSE</data><data key="edge_relationship_type">proposed_returned_to</data><data key="edge_target_entity_id">SVC_DNP</data><data key="edge_operational_context">The proposed exchange would return only numerical match/non-match response codes to Do Not Pay.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Proposal only; not evidence of a deployed interface.</data></edge><edge id="R84_REL014" source="PROC_NUMIDENT_2026_RECONCILIATION" target="SYS_NUMIDENT"><data key="edge_relationship_id">R84_REL014</data><data key="edge_source_entity_id">PROC_NUMIDENT_2026_RECONCILIATION</data><data key="edge_relationship_type">reconciles_or_updates</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA reports reconciling the SSN database to remove deceased people, update citizenship data, and verify status.</data><data key="edge_observed_as_of">2026-08-14</data><data key="edge_confidence">5</data><data key="edge_notes">Agency-reported initiative; implementation details not published.</data></edge><edge id="R84_REL015" source="PROC_NUMIDENT_2026_RECONCILIATION" target="DATA_NUMIDENT_CITIZENSHIP_CODE"><data key="edge_relationship_id">R84_REL015</data><data key="edge_source_entity_id">PROC_NUMIDENT_2026_RECONCILIATION</data><data key="edge_relationship_type">updates_or_reviews</data><data key="edge_target_entity_id">DATA_NUMIDENT_CITIZENSHIP_CODE</data><data key="edge_operational_context">SSA specifically reports updating citizenship data as part of the 2026 SSN-database reconciliation.</data><data key="edge_observed_as_of">2026-08-14</data><data key="edge_confidence">5</data><data key="edge_notes">The release does not identify the upstream evidence sources or write rules.</data></edge><edge id="R84_REL016" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_HEARING_REQUEST_RECEIPT"><data key="edge_relationship_id">R84_REL016</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_HEARING_REQUEST_RECEIPT</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL017" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_LAST_ACTION_DATE"><data key="edge_relationship_id">R84_REL017</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_LAST_ACTION_DATE</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL018" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_CASE_LOCATION_STAGE"><data key="edge_relationship_id">R84_REL018</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_CASE_LOCATION_STAGE</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL019" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_FILING_DATE"><data key="edge_relationship_id">R84_REL019</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_FILING_DATE</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL020" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_SCHEDULED_HEARING_DATE"><data key="edge_relationship_id">R84_REL020</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_SCHEDULED_HEARING_DATE</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL021" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_ASSIGNED_ALJ"><data key="edge_relationship_id">R84_REL021</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_ASSIGNED_ALJ</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL022" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_REQUEST_REVIEW_DATE"><data key="edge_relationship_id">R84_REL022</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_REQUEST_REVIEW_DATE</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL023" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_ASSIGNED_APPEALS_REVIEWER"><data key="edge_relationship_id">R84_REL023</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_ASSIGNED_APPEALS_REVIEWER</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL024" source="DB_HA_CASE_CONTROL_RECORDS" target="DATA_HA_APPEALS_ISSUE_TYPE"><data key="edge_relationship_id">R84_REL024</data><data key="edge_source_entity_id">DB_HA_CASE_CONTROL_RECORDS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_HA_APPEALS_ISSUE_TYPE</data><data key="edge_operational_context">Current SORN 60-0009 identifies this information within the Hearings and Appeals Case Control System record boundary.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record-system field relationship; physical application mapping remains unresolved.</data></edge><edge id="R84_REL025" source="SVC_EVVE" target="DATA_EVVE_VERIFICATION_RESULT"><data key="edge_relationship_id">R84_REL025</data><data key="edge_source_entity_id">SVC_EVVE</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_EVVE_VERIFICATION_RESULT</data><data key="edge_operational_context">EVVE returns match or no-match verification results for birth-record queries.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Verification result only; not certification.</data></edge><edge id="R84_REL026" source="SVC_EVVE" target="DATA_EVVE_STATE_FILE_NUMBER"><data key="edge_relationship_id">R84_REL026</data><data key="edge_source_entity_id">SVC_EVVE</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_EVVE_STATE_FILE_NUMBER</data><data key="edge_operational_context">For a verified claim, POMS directs staff to record the state file number returned by EVVE in MCS DW01 remarks.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No separate SSA persistence store is inferred beyond the documented entry.</data></edge><edge id="R84_REL027" source="SVC_EVVE" target="DATA_EVVE_DEATH_INDICATION"><data key="edge_relationship_id">R84_REL027</data><data key="edge_source_entity_id">SVC_EVVE</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_EVVE_DEATH_INDICATION</data><data key="edge_operational_context">EVVE output can indicate that the number holder may be deceased.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">The indication must be reconciled with allegations and SSA records.</data></edge><edge id="R84_REL028" source="DATA_EVVE_VERIFICATION_RESULT" target="APP_MCS"><data key="edge_relationship_id">R84_REL028</data><data key="edge_source_entity_id">DATA_EVVE_VERIFICATION_RESULT</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">For claims, current POMS directs staff to document an EVVE verification in MCS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Documentation path; does not imply EVVE writes directly to the target.</data></edge><edge id="R84_REL029" source="DATA_EVVE_VERIFICATION_RESULT" target="UI_MSSICS_ACID"><data key="edge_relationship_id">R84_REL029</data><data key="edge_source_entity_id">DATA_EVVE_VERIFICATION_RESULT</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">UI_MSSICS_ACID</data><data key="edge_operational_context">For SSI claims, current POMS directs staff to code the MSSICS Client Identification screen when EVVE verifies birth information.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Documentation path; does not imply EVVE writes directly to the target.</data></edge><edge id="R84_REL030" source="DATA_EVVE_VERIFICATION_RESULT" target="APP_EVID"><data key="edge_relationship_id">R84_REL030</data><data key="edge_source_entity_id">DATA_EVVE_VERIFICATION_RESULT</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Current POMS directs staff to code evidence not recorded in MCS or MSSICS to EVID.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Documentation path; does not imply EVVE writes directly to the target.</data></edge><edge id="R84_REL031" source="DATA_EVVE_VERIFICATION_RESULT" target="APP_SSNAP"><data key="edge_relationship_id">R84_REL031</data><data key="edge_source_entity_id">DATA_EVVE_VERIFICATION_RESULT</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">For enumeration, current POMS directs staff to select Verified and annotate the SSNAP summary when EVVE returns a match.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Documentation path; does not imply EVVE writes directly to the target.</data></edge><edge id="R84_REL032" source="DATA_EVVE_STATE_FILE_NUMBER" target="UI_MCS_DW01"><data key="edge_relationship_id">R84_REL032</data><data key="edge_source_entity_id">DATA_EVVE_STATE_FILE_NUMBER</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">UI_MCS_DW01</data><data key="edge_operational_context">POMS directs staff to enter EVVE VERIF and the returned state file number in the MCS DW01 remarks field.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Technician documentation path.</data></edge><edge id="R84_REL033" source="DATA_EVVE_DEATH_INDICATION" target="SYS_NUMIDENT"><data key="edge_relationship_id">R84_REL033</data><data key="edge_source_entity_id">DATA_EVVE_DEATH_INDICATION</data><data key="edge_relationship_type">may_prompt_reconciliation_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">When EVVE indicates the person is alive but SSA records show death, current POMS directs staff to resolve erroneous death data on Numident if fraud is not suspected or detected.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Human/policy-controlled reconciliation, not automatic state-to-Numident synchronization.</data></edge><edge id="R84_REL034" source="PROC_OACT_DI_INCIDENCE_PROJ" target="DATA_OACT_DI_INCIDENCE_2026"><data key="edge_relationship_id">R84_REL034</data><data key="edge_source_entity_id">PROC_OACT_DI_INCIDENCE_PROJ</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_OACT_DI_INCIDENCE_2026</data><data key="edge_operational_context">The 2026 public Figure V.C3 series presents historical and projected disabled-worker incidence rates associated with the Trustees Report incidence method.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication lineage; internal ETL not inferred.</data></edge><edge id="R84_REL035" source="PROC_OACT_DI_TERMINATION_PROJ" target="DATA_OACT_DI_TERMINATION_2026"><data key="edge_relationship_id">R84_REL035</data><data key="edge_source_entity_id">PROC_OACT_DI_TERMINATION_PROJ</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_OACT_DI_TERMINATION_2026</data><data key="edge_operational_context">The 2026 public Figure V.C4 series presents historical and projected disabled-worker termination rates associated with the Trustees Report termination method.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication lineage; internal ETL not inferred.</data></edge><edge id="R84_REL036" source="PROC_OACT_DI_BENEFICIARY_PROJ" target="PROC_OACT_DI_INCIDENCE_PROJ"><data key="edge_relationship_id">R84_REL036</data><data key="edge_source_entity_id">PROC_OACT_DI_BENEFICIARY_PROJ</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PROC_OACT_DI_INCIDENCE_PROJ</data><data key="edge_operational_context">The Trustees Report states that incidence is a foundation for projecting disabled-worker beneficiaries in current-payment status.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Method dependency, not a software interface.</data></edge><edge id="R84_REL037" source="PROC_OACT_DI_BENEFICIARY_PROJ" target="PROC_OACT_DI_TERMINATION_PROJ"><data key="edge_relationship_id">R84_REL037</data><data key="edge_source_entity_id">PROC_OACT_DI_BENEFICIARY_PROJ</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PROC_OACT_DI_TERMINATION_PROJ</data><data key="edge_operational_context">The Trustees Report states that termination rates are a foundation for projecting disabled-worker beneficiaries in current-payment status.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Method dependency, not a software interface.</data></edge><edge id="R84_REL038" source="PROC_OACT_FERTILITY_PROJ" target="MODEL_OACT_POPULATION"><data key="edge_relationship_id">R84_REL038</data><data key="edge_source_entity_id">PROC_OACT_FERTILITY_PROJ</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">MODEL_OACT_POPULATION</data><data key="edge_operational_context">The Social Security area population projection combines fertility assumptions with mortality, immigration, marriage, and divorce assumptions.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Method/model dependency only.</data></edge><edge id="R84_REL039" source="PROC_OACT_IMMIGRATION_PROJ" target="MODEL_OACT_POPULATION"><data key="edge_relationship_id">R84_REL039</data><data key="edge_source_entity_id">PROC_OACT_IMMIGRATION_PROJ</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">MODEL_OACT_POPULATION</data><data key="edge_operational_context">The Social Security area population projection incorporates assumptions for the four documented immigration flows.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Method/model dependency only.</data></edge><edge id="R84_REL040" source="PROC_OACT_COVERED_EARNINGS_PROJ" target="PROC_OACT_TAXABLE_EARNINGS_PROJ"><data key="edge_relationship_id">R84_REL040</data><data key="edge_source_entity_id">PROC_OACT_COVERED_EARNINGS_PROJ</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">PROC_OACT_TAXABLE_EARNINGS_PROJ</data><data key="edge_operational_context">Taxable earnings are projected as the portion of covered earnings subject to OASDI payroll tax.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Actuarial-method dependency.</data></edge><edge id="R84_REL041" source="PROC_OACT_TAXABLE_EARNINGS_PROJ" target="DATA_OACT_CBB"><data key="edge_relationship_id">R84_REL041</data><data key="edge_source_entity_id">PROC_OACT_TAXABLE_EARNINGS_PROJ</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_OACT_CBB</data><data key="edge_operational_context">The contribution and benefit base limits taxable wages and is used in the taxable-earnings methodology.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Statutory parameter dependency.</data></edge><edge id="R84_REL042" source="PROC_OACT_TAXABLE_EARNINGS_PROJ" target="PROC_OACT_PAYROLL_TAX_PROJ"><data key="edge_relationship_id">R84_REL042</data><data key="edge_source_entity_id">PROC_OACT_TAXABLE_EARNINGS_PROJ</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">PROC_OACT_PAYROLL_TAX_PROJ</data><data key="edge_operational_context">Payroll tax liabilities are projected from scheduled rates applied to taxable wages and self-employment net earnings.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Actuarial-method dependency.</data></edge><edge id="R84_REL043" source="FORM_SSA3288OP1" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R84_REL043</data><data key="edge_source_entity_id">FORM_SSA3288OP1</data><data key="edge_relationship_type">available_for_electronic_submission_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA current Forms catalog lists a Complete Online Form route for SSA-3288-OP1 within the agency electronic-submission experience.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No separate form-specific database or transport is inferred.</data></edge><edge id="R85_REL001" source="UI_NED_NEDA" target="APP_NED"><data key="edge_relationship_id">R85_REL001</data><data key="edge_source_entity_id">UI_NED_NEDA</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_NED</data><data key="edge_operational_context">POMS identifies NEDA as the NED screen used to directly change the debtor domestic address and phone number.</data><data key="edge_observed_as_of">2017-10-31</data><data key="edge_confidence">5</data><data key="edge_notes">No UI technology inferred.</data></edge><edge id="R85_REL002" source="UI_NED_NEDA" target="DATA_NED_DOMESTIC_ADDRESS"><data key="edge_relationship_id">R85_REL002</data><data key="edge_source_entity_id">UI_NED_NEDA</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_NED_DOMESTIC_ADDRESS</data><data key="edge_operational_context">NEDA directly changes the domestic address maintained in the NED database.</data><data key="edge_observed_as_of">2017-10-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL003" source="APP_NED" target="DATA_NED_DOMESTIC_ADDRESS"><data key="edge_relationship_id">R85_REL003</data><data key="edge_source_entity_id">APP_NED</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_NED_DOMESTIC_ADDRESS</data><data key="edge_operational_context">The NED database maintains the domestic address used for a non-entitled debtor.</data><data key="edge_observed_as_of">2017-10-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL004" source="APP_ECO" target="APP_NED"><data key="edge_relationship_id">R85_REL004</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">extracts_data_from</data><data key="edge_target_entity_id">APP_NED</data><data key="edge_operational_context">POMS says NED does not pass data to ECO; instead ECO extracts data from the NED database.</data><data key="edge_observed_as_of">2017-10-31</data><data key="edge_confidence">5</data><data key="edge_notes">Direction is explicitly constrained by policy.</data></edge><edge id="R85_REL005" source="DATA_NED_DOMESTIC_ADDRESS" target="APP_ECO"><data key="edge_relationship_id">R85_REL005</data><data key="edge_source_entity_id">DATA_NED_DOMESTIC_ADDRESS</data><data key="edge_relationship_type">available_to</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">The NED address changed through NEDA provides ECO with the current debtor address.</data><data key="edge_observed_as_of">2017-10-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL006" source="DATA_NED_DOMESTIC_ADDRESS" target="SYS_MBR"><data key="edge_relationship_id">R85_REL006</data><data key="edge_source_entity_id">DATA_NED_DOMESTIC_ADDRESS</data><data key="edge_relationship_type">does_not_update</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS expressly states that changing the NED address does not interface with or update the MBR.</data><data key="edge_observed_as_of">2017-10-31</data><data key="edge_confidence">5</data><data key="edge_notes">Explicit negative propagation rule.</data></edge><edge id="R85_REL007" source="SVC_ITS_GOV" target="DATA_ITS_BENEFICIARY_ADDRESS"><data key="edge_relationship_id">R85_REL007</data><data key="edge_source_entity_id">SVC_ITS_GOV</data><data key="edge_relationship_type">receives</data><data key="edge_target_entity_id">DATA_ITS_BENEFICIARY_ADDRESS</data><data key="edge_operational_context">Current IDD policy requires beneficiary address input in ITS.gov for the documented country workflow.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No claim that ITS.gov becomes the Title II master address.</data></edge><edge id="R85_REL008" source="SVC_ITS_GOV" target="DATA_ITS_BANK_ADDRESS"><data key="edge_relationship_id">R85_REL008</data><data key="edge_source_entity_id">SVC_ITS_GOV</data><data key="edge_relationship_type">receives</data><data key="edge_target_entity_id">DATA_ITS_BANK_ADDRESS</data><data key="edge_operational_context">Current IDD policy requires bank address input in the bank contact information field in ITS.gov.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Financial-institution address, not person residence.</data></edge><edge id="R85_REL009" source="PROC_IDD" target="DATA_ITS_BENEFICIARY_ADDRESS"><data key="edge_relationship_id">R85_REL009</data><data key="edge_source_entity_id">PROC_IDD</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_ITS_BENEFICIARY_ADDRESS</data><data key="edge_operational_context">International direct-deposit processing uses the ITS.gov beneficiary address as part of required enrollment/update data.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL010" source="PROC_IDD" target="DATA_ITS_BANK_ADDRESS"><data key="edge_relationship_id">R85_REL010</data><data key="edge_source_entity_id">PROC_IDD</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_ITS_BANK_ADDRESS</data><data key="edge_operational_context">International direct-deposit processing uses the ITS.gov financial-institution address where required.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL011" source="DATA_ITS_BENEFICIARY_ADDRESS" target="SYS_MBR"><data key="edge_relationship_id">R85_REL011</data><data key="edge_source_entity_id">DATA_ITS_BENEFICIARY_ADDRESS</data><data key="edge_relationship_type">does_not_establish_update_path_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Policy requires MBR foreign-country status for certain IDD updates but does not state that the beneficiary address entered in ITS.gov updates the MBR address.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Negative inference control, not a claim that systems can never be coordinated manually.</data></edge><edge id="R85_REL012" source="EX_NUMIDENT_DNP_VERIFY" target="SYS_NUMIDENT"><data key="edge_relationship_id">R85_REL012</data><data key="edge_source_entity_id">EX_NUMIDENT_DNP_VERIFY</data><data key="edge_relationship_type">sources_identity_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">The final designation makes Numident the authoritative SSA source used through Do Not Pay for name, SSN and DOB verification.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL013" source="EX_NUMIDENT_DNP_VERIFY" target="SVC_DNP"><data key="edge_relationship_id">R85_REL013</data><data key="edge_source_entity_id">EX_NUMIDENT_DNP_VERIFY</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">SVC_DNP</data><data key="edge_operational_context">Treasury designated Numident to the Do Not Pay Working System for the specified verification purpose.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL014" source="EX_NUMIDENT_DNP_VERIFY" target="DATA_NUMIDENT_DNP_MATCH_RESPONSE"><data key="edge_relationship_id">R85_REL014</data><data key="edge_source_entity_id">EX_NUMIDENT_DNP_VERIFY</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_NUMIDENT_DNP_MATCH_RESPONSE</data><data key="edge_operational_context">The proposed exchange design retained in the Atlas describes numerical match/non-match responses rather than corrected PII; final designation authorizes the verification use.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">Exact production response encoding is not separately confirmed by the final notice.</data></edge><edge id="R85_REL015" source="EX_NUMIDENT_DNP_VERIFY" target="SVC_TREASURY_PAYMENT_VERIFICATION"><data key="edge_relationship_id">R85_REL015</data><data key="edge_source_entity_id">EX_NUMIDENT_DNP_VERIFY</data><data key="edge_relationship_type">currently_available_via_select_programs</data><data key="edge_target_entity_id">SVC_TREASURY_PAYMENT_VERIFICATION</data><data key="edge_operational_context">Treasury September 2026 catalog lists Numident in Payment Verification for select programs.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Select programs are not identified publicly.</data></edge><edge id="R85_REL016" source="EX_NUMIDENT_DNP_VERIFY" target="SVC_DNP_CONNECT"><data key="edge_relationship_id">R85_REL016</data><data key="edge_source_entity_id">EX_NUMIDENT_DNP_VERIFY</data><data key="edge_relationship_type">planned_for_select_programs</data><data key="edge_target_entity_id">SVC_DNP_CONNECT</data><data key="edge_operational_context">Treasury September 2026 catalog lists Numident in Do Not Pay Connect as coming soon for select programs.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Future-state product availability, not a deployed API assertion.</data></edge><edge id="R85_REL017" source="EX_NUMIDENT_DNP_VERIFY" target="SVC_PARIS"><data key="edge_relationship_id">R85_REL017</data><data key="edge_source_entity_id">EX_NUMIDENT_DNP_VERIFY</data><data key="edge_relationship_type">planned_state_access_via</data><data key="edge_target_entity_id">SVC_PARIS</data><data key="edge_operational_context">Treasury lists state usage of Numident as coming soon through PARIS.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Future-state state-agency access only.</data></edge><edge id="R85_REL018" source="PROC_DNP_SOURCE_DATA_CORRECTION" target="SVC_DNP"><data key="edge_relationship_id">R85_REL018</data><data key="edge_source_entity_id">PROC_DNP_SOURCE_DATA_CORRECTION</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">SVC_DNP</data><data key="edge_operational_context">Treasury requires data providers to maintain correction procedures and updates validated corrections at both the source and Do Not Pay.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL019" source="PROC_DNP_SOURCE_DATA_CORRECTION" target="SYS_NUMIDENT"><data key="edge_relationship_id">R85_REL019</data><data key="edge_source_entity_id">PROC_DNP_SOURCE_DATA_CORRECTION</data><data key="edge_relationship_type">preserves_source_authority_for</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">For Numident discrepancies, the source agency remains responsible for correction; Do Not Pay is not a replacement identity master.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Derived directly from Treasury correction-governance model and SSA ownership of Numident.</data></edge><edge id="R85_REL020" source="PROC_NUMIDENT_MATCHING_GOV" target="SYS_NUMIDENT"><data key="edge_relationship_id">R85_REL020</data><data key="edge_source_entity_id">PROC_NUMIDENT_MATCHING_GOV</data><data key="edge_relationship_type">governs_verification_of</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">OIG recommended cross-component collaboration and periodic risk assessment around Numident matching criteria; SSA agreed.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Does not identify a physical criteria repository.</data></edge><edge id="R85_REL021" source="PROC_NUMIDENT_MATCHING_GOV" target="PROJ_NUMIDENT_VERIFY_CONSOLIDATION"><data key="edge_relationship_id">R85_REL021</data><data key="edge_source_entity_id">PROC_NUMIDENT_MATCHING_GOV</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROJ_NUMIDENT_VERIFY_CONSOLIDATION</data><data key="edge_operational_context">OIG warned that centralizing verification without improving matching criteria would leave matching-risk issues unresolved.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Governance relationship; not a software dependency.</data></edge><edge id="R85_REL022" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_IVB1_RATES"><data key="edge_relationship_id">R85_REL022</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_OACT_TR_IVB1_RATES</data><data key="edge_operational_context">OACT publishes this table within the supplemental single-year series consistent with the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL023" source="REPORT_TRUSTEES_2026" target="DATA_OACT_TR_IVB1_RATES"><data key="edge_relationship_id">R85_REL023</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_OACT_TR_IVB1_RATES</data><data key="edge_operational_context">OACT directs users to the 2026 Trustees Report for context and terminology for the supplemental single-year table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL024" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_IVB2_COMPONENTS"><data key="edge_relationship_id">R85_REL024</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_OACT_TR_IVB2_COMPONENTS</data><data key="edge_operational_context">OACT publishes this table within the supplemental single-year series consistent with the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL025" source="REPORT_TRUSTEES_2026" target="DATA_OACT_TR_IVB2_COMPONENTS"><data key="edge_relationship_id">R85_REL025</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_OACT_TR_IVB2_COMPONENTS</data><data key="edge_operational_context">OACT directs users to the 2026 Trustees Report for context and terminology for the supplemental single-year table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL026" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_IVB3_GDP"><data key="edge_relationship_id">R85_REL026</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_OACT_TR_IVB3_GDP</data><data key="edge_operational_context">OACT publishes this table within the supplemental single-year series consistent with the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL027" source="REPORT_TRUSTEES_2026" target="DATA_OACT_TR_IVB3_GDP"><data key="edge_relationship_id">R85_REL027</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_OACT_TR_IVB3_GDP</data><data key="edge_operational_context">OACT directs users to the 2026 Trustees Report for context and terminology for the supplemental single-year table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL028" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VA1_FERT_MORT"><data key="edge_relationship_id">R85_REL028</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_OACT_TR_VA1_FERT_MORT</data><data key="edge_operational_context">OACT publishes this table within the supplemental single-year series consistent with the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL029" source="REPORT_TRUSTEES_2026" target="DATA_OACT_TR_VA1_FERT_MORT"><data key="edge_relationship_id">R85_REL029</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_OACT_TR_VA1_FERT_MORT</data><data key="edge_operational_context">OACT directs users to the 2026 Trustees Report for context and terminology for the supplemental single-year table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL030" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB1_APPLICATIONS"><data key="edge_relationship_id">R85_REL030</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB1_APPLICATIONS</data><data key="edge_operational_context">OACT publishes this table within the 2026 SSI supplemental single-year series.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL031" source="REPORT_SSI_ANNUAL_2026" target="DATA_SSI_AR_IVB1_APPLICATIONS"><data key="edge_relationship_id">R85_REL031</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB1_APPLICATIONS</data><data key="edge_operational_context">The 2026 SSI Annual Report provides the definitions and context for the supplemental table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL032" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB2_NEW_RECIPIENTS"><data key="edge_relationship_id">R85_REL032</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB2_NEW_RECIPIENTS</data><data key="edge_operational_context">OACT publishes this table within the 2026 SSI supplemental single-year series.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL033" source="REPORT_SSI_ANNUAL_2026" target="DATA_SSI_AR_IVB2_NEW_RECIPIENTS"><data key="edge_relationship_id">R85_REL033</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB2_NEW_RECIPIENTS</data><data key="edge_operational_context">The 2026 SSI Annual Report provides the definitions and context for the supplemental table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL034" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB3_DEATH_TERMS"><data key="edge_relationship_id">R85_REL034</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB3_DEATH_TERMS</data><data key="edge_operational_context">OACT publishes this table within the 2026 SSI supplemental single-year series.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL035" source="REPORT_SSI_ANNUAL_2026" target="DATA_SSI_AR_IVB3_DEATH_TERMS"><data key="edge_relationship_id">R85_REL035</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB3_DEATH_TERMS</data><data key="edge_operational_context">The 2026 SSI Annual Report provides the definitions and context for the supplemental table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL036" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVC1_FED_PAYMENTS"><data key="edge_relationship_id">R85_REL036</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC1_FED_PAYMENTS</data><data key="edge_operational_context">OACT publishes this table within the 2026 SSI supplemental single-year series.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL037" source="REPORT_SSI_ANNUAL_2026" target="DATA_SSI_AR_IVC1_FED_PAYMENTS"><data key="edge_relationship_id">R85_REL037</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC1_FED_PAYMENTS</data><data key="edge_operational_context">The 2026 SSI Annual Report provides the definitions and context for the supplemental table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL038" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_VC1_ADULT_DISP"><data key="edge_relationship_id">R85_REL038</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_AR_VC1_ADULT_DISP</data><data key="edge_operational_context">OACT publishes this table within the 2026 SSI supplemental single-year series.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL039" source="REPORT_SSI_ANNUAL_2026" target="DATA_SSI_AR_VC1_ADULT_DISP"><data key="edge_relationship_id">R85_REL039</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_SSI_AR_VC1_ADULT_DISP</data><data key="edge_operational_context">The 2026 SSI Annual Report provides the definitions and context for the supplemental table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL040" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_VC2_CHILD_DISP"><data key="edge_relationship_id">R85_REL040</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_AR_VC2_CHILD_DISP</data><data key="edge_operational_context">OACT publishes this table within the 2026 SSI supplemental single-year series.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL041" source="REPORT_SSI_ANNUAL_2026" target="DATA_SSI_AR_VC2_CHILD_DISP"><data key="edge_relationship_id">R85_REL041</data><data key="edge_source_entity_id">REPORT_SSI_ANNUAL_2026</data><data key="edge_relationship_type">contextualizes</data><data key="edge_target_entity_id">DATA_SSI_AR_VC2_CHILD_DISP</data><data key="edge_operational_context">The 2026 SSI Annual Report provides the definitions and context for the supplemental table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL042" source="SVC_SSA_WEB_STATUS" target="APP_MYSSA"><data key="edge_relationship_id">R85_REL042</data><data key="edge_source_entity_id">SVC_SSA_WEB_STATUS</data><data key="edge_relationship_type">monitors_public_health_of</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA status page publishes current health for the my Social Security Webapp.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Public monitoring surface only.</data></edge><edge id="R85_REL043" source="SVC_SSA_WEB_STATUS" target="DATA_SSA_WEB_INCIDENT_HISTORY"><data key="edge_relationship_id">R85_REL043</data><data key="edge_source_entity_id">SVC_SSA_WEB_STATUS</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_SSA_WEB_INCIDENT_HISTORY</data><data key="edge_operational_context">SSA status service exposes historical outages and scheduled maintenance.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R85_REL044" source="DATA_SSA_WEB_INCIDENT_HISTORY" target="APP_MYSSA"><data key="edge_relationship_id">R85_REL044</data><data key="edge_source_entity_id">DATA_SSA_WEB_INCIDENT_HISTORY</data><data key="edge_relationship_type">records_availability_for</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Incident history includes network disruptions and scheduled maintenance affecting the my Social Security Webapp.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">No internal root-cause platform inferred.</data></edge><edge id="R86_REL001" source="PROC_US_MAILING_BENEF_ABROAD" target="DATA_BENEF_ABROAD_ACTUAL_RESIDENCE"><data key="edge_relationship_id">R86_REL001</data><data key="edge_source_entity_id">PROC_US_MAILING_BENEF_ABROAD</data><data key="edge_relationship_type">requires_actual_residence</data><data key="edge_target_entity_id">DATA_BENEF_ABROAD_ACTUAL_RESIDENCE</data><data key="edge_operational_context">A beneficiary abroad using a qualifying U.S. mailing address must keep SSA advised of the actual residence address.</data><data key="edge_observed_as_of">2024-02-07</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic program-record write is inferred.</data></edge><edge id="R86_REL002" source="PROC_US_MAILING_BENEF_ABROAD" target="DATA_US_MAILING_ABROAD_240_CODE"><data key="edge_relationship_id">R86_REL002</data><data key="edge_source_entity_id">PROC_US_MAILING_BENEF_ABROAD</data><data key="edge_relationship_type">requires_control_code</data><data key="edge_target_entity_id">DATA_US_MAILING_ABROAD_240_CODE</data><data key="edge_operational_context">SSA prepares a 240 listing code when a beneficiary resides abroad but maintains a U.S. mailing address, except APO/FPO cases.</data><data key="edge_observed_as_of">2024-02-07</data><data key="edge_confidence">5</data><data key="edge_notes">Storage location of the listing code is unresolved.</data></edge><edge id="R86_REL003" source="PROC_FOREIGN_CARE_OF_MAILING" target="DATA_FOREIGN_CARE_OF_MAILING_ADDR"><data key="edge_relationship_id">R86_REL003</data><data key="edge_source_entity_id">PROC_FOREIGN_CARE_OF_MAILING</data><data key="edge_relationship_type">uses_mailing_address</data><data key="edge_target_entity_id">DATA_FOREIGN_CARE_OF_MAILING_ADDR</data><data key="edge_operational_context">The foreign C/O process accepts the relative/friend address as the mailing address when policy conditions are met.</data><data key="edge_observed_as_of">2023-12</data><data key="edge_confidence">5</data><data key="edge_notes">Actual residence must also be documented.</data></edge><edge id="R86_REL004" source="PROC_FOREIGN_CARE_OF_MAILING" target="FORM_SSA795"><data key="edge_relationship_id">R86_REL004</data><data key="edge_source_entity_id">PROC_FOREIGN_CARE_OF_MAILING</data><data key="edge_relationship_type">documents_actual_residence_with</data><data key="edge_target_entity_id">FORM_SSA795</data><data key="edge_operational_context">SSA obtains Form SSA-795 showing the beneficiary actual residence address and explaining use of the foreign C/O address.</data><data key="edge_observed_as_of">2023-12</data><data key="edge_confidence">5</data><data key="edge_notes">Form SSA-795 already existed in the Atlas.</data></edge><edge id="R86_REL005" source="PROC_FOREIGN_CARE_OF_MAILING" target="PROC_FBU_FALLBACK_MAILING"><data key="edge_relationship_id">R86_REL005</data><data key="edge_source_entity_id">PROC_FOREIGN_CARE_OF_MAILING</data><data key="edge_relationship_type">may_fall_back_to</data><data key="edge_target_entity_id">PROC_FBU_FALLBACK_MAILING</data><data key="edge_operational_context">If other mailing-address options are exhausted, policy permits rare use of the FBU address as the beneficiary mailing address.</data><data key="edge_observed_as_of">2023-12</data><data key="edge_confidence">5</data><data key="edge_notes">Fallback only; not the normal foreign mailing-address path.</data></edge><edge id="R86_REL006" source="UI_POS_PEAD" target="UI_POS_CLCZ"><data key="edge_relationship_id">R86_REL006</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">may_route_to</data><data key="edge_target_entity_id">UI_POS_CLCZ</data><data key="edge_operational_context">Foreign-to-domestic COA processing through PEAD may bring CLCZ into the path when MBR citizenship information is missing or incomplete.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes">This establishes workflow routing, not an automatic MBR write.</data></edge><edge id="R86_REL007" source="UI_POS_PEAD" target="UI_POS_CLLP"><data key="edge_relationship_id">R86_REL007</data><data key="edge_source_entity_id">UI_POS_PEAD</data><data key="edge_relationship_type">may_route_to</data><data key="edge_target_entity_id">UI_POS_CLLP</data><data key="edge_operational_context">Foreign-to-domestic COA processing through PEAD may bring CLLP into the path when lawful-presence information is missing or incomplete.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes">This establishes workflow routing, not an automatic MBR write.</data></edge><edge id="R86_REL008" source="UI_POS_CLCZ" target="SYS_MBR"><data key="edge_relationship_id">R86_REL008</data><data key="edge_source_entity_id">UI_POS_CLCZ</data><data key="edge_relationship_type">supports_review_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS directs staff to review MBR citizenship information before initiating the foreign-to-domestic address change.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes">Field-level write semantics are not stated.</data></edge><edge id="R86_REL009" source="UI_POS_CLLP" target="SYS_MBR"><data key="edge_relationship_id">R86_REL009</data><data key="edge_source_entity_id">UI_POS_CLLP</data><data key="edge_relationship_type">supports_review_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS directs staff to verify lawful-presence information associated with the MBR before the foreign-to-domestic address change when applicable.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">4</data><data key="edge_notes">Exact field mapping is not public.</data></edge><edge id="R86_REL010" source="PROC_FO_ADDRESS_AS_MAILING" target="DATA_MMCR"><data key="edge_relationship_id">R86_REL010</data><data key="edge_source_entity_id">PROC_FO_ADDRESS_AS_MAILING</data><data key="edge_relationship_type">maintains_check_control_with</data><data key="edge_target_entity_id">DATA_MMCR</data><data key="edge_operational_context">Field offices establish a separate MMCR control for each check received when the FO address is used as the mailing address.</data><data key="edge_observed_as_of">2026-09-18</data><data key="edge_confidence">5</data><data key="edge_notes">The record contains claimant/check control information, not a new beneficiary master address.</data></edge><edge id="R86_REL011" source="DATA_MMCR" target="REPO_NDRED"><data key="edge_relationship_id">R86_REL011</data><data key="edge_source_entity_id">DATA_MMCR</data><data key="edge_relationship_type">retained_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Control records for checks mailed to the field office may be retained in NDRed for three years after distribution; secure local holding is an alternative.</data><data key="edge_observed_as_of">2026-09-18</data><data key="edge_confidence">5</data><data key="edge_notes">Paper may be destroyed after verified scanning.</data></edge><edge id="R86_REL012" source="PROC_SSI_INTERSTATE_COA_STAGING" target="APP_MSSICS"><data key="edge_relationship_id">R86_REL012</data><data key="edge_source_entity_id">PROC_SSI_INTERSTATE_COA_STAGING</data><data key="edge_relationship_type">may_input_through</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current policy permits the new mailing/residence information to be entered through MSSICS.</data><data key="edge_observed_as_of">2026-08-07</data><data key="edge_confidence">5</data><data key="edge_notes">MSSICS implementation details beyond policy references are not inferred.</data></edge><edge id="R86_REL013" source="PROC_SSI_INTERSTATE_COA_STAGING" target="FORM_SSA1719B"><data key="edge_relationship_id">R86_REL013</data><data key="edge_source_entity_id">PROC_SSI_INTERSTATE_COA_STAGING</data><data key="edge_relationship_type">may_input_through</data><data key="edge_target_entity_id">FORM_SSA1719B</data><data key="edge_operational_context">When MSSICS is not used, current policy permits SSA-1719B SSI post-eligibility input.</data><data key="edge_observed_as_of">2026-08-07</data><data key="edge_confidence">5</data><data key="edge_notes">This is an alternative input route.</data></edge><edge id="R86_REL014" source="PROC_SSI_INTERSTATE_COA_STAGING" target="UI_MSSICS_DWO1"><data key="edge_relationship_id">R86_REL014</data><data key="edge_source_entity_id">PROC_SSI_INTERSTATE_COA_STAGING</data><data key="edge_relationship_type">refers_outstanding_development_via</data><data key="edge_target_entity_id">UI_MSSICS_DWO1</data><data key="edge_operational_context">Cases moving to another service area may be referred to the new field office via the MSSICS DWO1/DWOI control.</data><data key="edge_observed_as_of">2026-08-07</data><data key="edge_confidence">4</data><data key="edge_notes">POMS has DWO1/DWOI spelling inconsistency.</data></edge><edge id="R86_REL015" source="PROC_SSI_INTERSTATE_COA_STAGING" target="APP_MDW_AI"><data key="edge_relationship_id">R86_REL015</data><data key="edge_source_entity_id">PROC_SSI_INTERSTATE_COA_STAGING</data><data key="edge_relationship_type">refers_non_mssics_development_via</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">If a case is not in MSSICS, current POMS directs referral through the Modernized Development Worksheet.</data><data key="edge_observed_as_of">2026-08-07</data><data key="edge_confidence">5</data><data key="edge_notes">Reuses the existing MDW entity; does not assert that its later AI features are required by this workflow.</data></edge><edge id="R86_REL016" source="SYS_SSR" target="DATA_SSR_CMPH_SEGMENT"><data key="edge_relationship_id">R86_REL016</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains_segment</data><data key="edge_target_entity_id">DATA_SSR_CMPH_SEGMENT</data><data key="edge_operational_context">Current POMS identifies CMPH as a segment of the SSR used for residence-related case characteristics.</data><data key="edge_observed_as_of">2026-08-07</data><data key="edge_confidence">5</data><data key="edge_notes">Logical record segmentation only.</data></edge><edge id="R86_REL017" source="PROC_SSI_INTERSTATE_COA_STAGING" target="DATA_SSR_CMPH_SEGMENT"><data key="edge_relationship_id">R86_REL017</data><data key="edge_source_entity_id">PROC_SSI_INTERSTATE_COA_STAGING</data><data key="edge_relationship_type">updates_after_residence_development</data><data key="edge_target_entity_id">DATA_SSR_CMPH_SEGMENT</data><data key="edge_operational_context">After the new residence and living arrangement are developed, staff update correct residence information to the SSR CMPH segment.</data><data key="edge_observed_as_of">2026-08-07</data><data key="edge_confidence">5</data><data key="edge_notes">Staff-directed update path, not automatic external synchronization.</data></edge><edge id="R86_REL018" source="PROC_IAPPEALS_NUMIDENT_ACCESS_CHECK" target="SYS_NUMIDENT"><data key="edge_relationship_id">R86_REL018</data><data key="edge_source_entity_id">PROC_IAPPEALS_NUMIDENT_ACCESS_CHECK</data><data key="edge_relationship_type">reads_access_controls_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">iAppeals checks blocked-access and special-indicator conditions on Numident before allowing Internet appeal use.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">Read/eligibility relationship only.</data></edge><edge id="R86_REL019" source="PROC_IAPPEALS_NUMIDENT_ACCESS_CHECK" target="APP_IAPPEALS"><data key="edge_relationship_id">R86_REL019</data><data key="edge_source_entity_id">PROC_IAPPEALS_NUMIDENT_ACCESS_CHECK</data><data key="edge_relationship_type">controls_access_to</data><data key="edge_target_entity_id">APP_IAPPEALS</data><data key="edge_operational_context">Claimants with blocked Internet access or disqualifying Numident indicators cannot use iAppeals.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">Alternative appeal channels remain available.</data></edge><edge id="R86_REL020" source="APP_IAPPEALS" target="DATA_IAPPEALS_REENTRY_NUMBER"><data key="edge_relationship_id">R86_REL020</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">issues</data><data key="edge_target_entity_id">DATA_IAPPEALS_REENTRY_NUMBER</data><data key="edge_operational_context">iAppeals issues a reentry number for resuming an unfinished appeal submission.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">The public source states a 65-day restart rule.</data></edge><edge id="R86_REL021" source="APP_IAPPEALS" target="DATA_IAPPEALS_RECEIPT_PAGE"><data key="edge_relationship_id">R86_REL021</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_IAPPEALS_RECEIPT_PAGE</data><data key="edge_operational_context">After submission, iAppeals provides a receipt page with date, time, and submission summary.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">User-facing artifact.</data></edge><edge id="R86_REL022" source="APP_IAPPEALS" target="DATA_IAPPEALS_COVERSHEET_PAGE"><data key="edge_relationship_id">R86_REL022</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_IAPPEALS_COVERSHEET_PAGE</data><data key="edge_operational_context">After submission, iAppeals provides a coversheet with BNC, contact information, and local FO address.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">User-facing artifact.</data></edge><edge id="R86_REL023" source="APP_IAPPEALS" target="DATA_IAPPEALS_CLAIMANT_MAILING_ZIP"><data key="edge_relationship_id">R86_REL023</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">uses_for_routing</data><data key="edge_target_entity_id">DATA_IAPPEALS_CLAIMANT_MAILING_ZIP</data><data key="edge_operational_context">For applicable Title II/Canadian appeals, iAppeals uses claimant mailing ZIP/postal code to route the request to the servicing FO Internet Disability WMI.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">Other foreign Title II appeals route to OIO; concurrent/Title XVI route by preferred office.</data></edge><edge id="R86_REL024" source="DATA_IAPPEALS_COVERSHEET_PAGE" target="DATA_IAPPEALS_CLAIMANT_MAILING_ZIP"><data key="edge_relationship_id">R86_REL024</data><data key="edge_source_entity_id">DATA_IAPPEALS_COVERSHEET_PAGE</data><data key="edge_relationship_type">derives_office_from</data><data key="edge_target_entity_id">DATA_IAPPEALS_CLAIMANT_MAILING_ZIP</data><data key="edge_operational_context">The coversheet local FO address is based on the ZIP code of the claimant mailing address.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">Routing derivation only.</data></edge><edge id="R86_REL025" source="APP_IAPPEALS" target="FEATURE_IAPPEALS_ATTACHMENT_UTILITY"><data key="edge_relationship_id">R86_REL025</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">accepts_evidence_through</data><data key="edge_target_entity_id">FEATURE_IAPPEALS_ATTACHMENT_UTILITY</data><data key="edge_operational_context">Internet users can attach evidence to iAppeals submissions using the attachment utility.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">Attachment review/retention occurs in EDCS.</data></edge><edge id="R86_REL026" source="FEATURE_IAPPEALS_ATTACHMENT_UTILITY" target="UI_EDCS_PREVIEW_INTERNET_DOCS"><data key="edge_relationship_id">R86_REL026</data><data key="edge_source_entity_id">FEATURE_IAPPEALS_ATTACHMENT_UTILITY</data><data key="edge_relationship_type">reviewed_before_case_creation_in</data><data key="edge_target_entity_id">UI_EDCS_PREVIEW_INTERNET_DOCS</data><data key="edge_operational_context">EDCS users can process submitted Internet documents on Preview Internet Documents before creating the EDCS case.</data><data key="edge_observed_as_of">2023-12-28</data><data key="edge_confidence">5</data><data key="edge_notes">Documents are searched by SSN.</data></edge><edge id="R86_REL027" source="FEATURE_IAPPEALS_ATTACHMENT_UTILITY" target="UI_EDCS_INTERNET_DOCS"><data key="edge_relationship_id">R86_REL027</data><data key="edge_source_entity_id">FEATURE_IAPPEALS_ATTACHMENT_UTILITY</data><data key="edge_relationship_type">associated_with_case_in</data><data key="edge_target_entity_id">UI_EDCS_INTERNET_DOCS</data><data key="edge_operational_context">After EDCS case creation, Internet-submitted documents appear on the Internet Documents page for case-level action.</data><data key="edge_observed_as_of">2023-12-28</data><data key="edge_confidence">5</data><data key="edge_notes">Association is case/SSN controlled.</data></edge><edge id="R86_REL028" source="UI_EDCS_INTERNET_DOCS" target="REPO_EF"><data key="edge_relationship_id">R86_REL028</data><data key="edge_source_entity_id">UI_EDCS_INTERNET_DOCS</data><data key="edge_relationship_type">commits_retained_documents_to</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">EDCS can send retained Internet documents to the Electronic Folder and copy document metadata to the case.</data><data key="edge_observed_as_of">2023-12-28</data><data key="edge_confidence">5</data><data key="edge_notes">DMA moves the image to the permanent location; physical storage technology not inferred.</data></edge><edge id="R86_REL029" source="UI_EDCS_INTERNET_DOCS" target="UI_EVIEW_INTERNET_DOC_HISTORY"><data key="edge_relationship_id">R86_REL029</data><data key="edge_source_entity_id">UI_EDCS_INTERNET_DOCS</data><data key="edge_relationship_type">records_history_in</data><data key="edge_target_entity_id">UI_EVIEW_INTERNET_DOC_HISTORY</data><data key="edge_operational_context">After processing, eView exposes Internet document status and retention actions on the Internet Documents History page.</data><data key="edge_observed_as_of">2023-12-28</data><data key="edge_confidence">5</data><data key="edge_notes">History availability depends on the discard reason for image visibility.</data></edge><edge id="R86_REL030" source="APP_MCS" target="DATA_MCS_IAPPEALS_CONTACT_ALERT"><data key="edge_relationship_id">R86_REL030</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_MCS_IAPPEALS_CONTACT_ALERT</data><data key="edge_operational_context">MCS alerts a technician when iAppeals contact information differs from MCS contact information.</data><data key="edge_observed_as_of">2025-12-02</data><data key="edge_confidence">5</data><data key="edge_notes">Technician review and claimant contact resolve discrepancies; no automatic overwrite is established.</data></edge><edge id="R86_REL031" source="PROC_IRS_TAX_INFO_REQUEST" target="ORG_IRS_DISCLOSURE_SCANNING_OP"><data key="edge_relationship_id">R86_REL031</data><data key="edge_source_entity_id">PROC_IRS_TAX_INFO_REQUEST</data><data key="edge_relationship_type">routes_to</data><data key="edge_target_entity_id">ORG_IRS_DISCLOSURE_SCANNING_OP</data><data key="edge_operational_context">Current POMS directs written SSA tax-information requests to the IRS Disclosure Scanning Operation in Atlanta.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Operational mailing destination; transport beyond written request is not inferred.</data></edge><edge id="R86_REL032" source="ORG_IRS_DISCLOSURE_SCANNING_OP" target="ORG_IRS"><data key="edge_relationship_id">R86_REL032</data><data key="edge_source_entity_id">ORG_IRS_DISCLOSURE_SCANNING_OP</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">The Disclosure Scanning Operation is an IRS destination for SSA written tax-information requests.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">No internal IRS platform asserted.</data></edge><edge id="R86_REL033" source="PROC_IRS_TAX_INFO_REQUEST" target="DATA_IRS_TAX_REQUEST_TEMPLATE"><data key="edge_relationship_id">R86_REL033</data><data key="edge_source_entity_id">PROC_IRS_TAX_INFO_REQUEST</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_IRS_TAX_REQUEST_TEMPLATE</data><data key="edge_operational_context">SSA uses the designated two-part IRS request form/template to ask for needed tax information.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Request includes tax types/schedules and taxpayer identifiers.</data></edge><edge id="R86_REL034" source="DATA_IRS_TAX_REQUEST_TEMPLATE" target="DATA_IRS_TAX_REQUEST_TP_ADDRESS"><data key="edge_relationship_id">R86_REL034</data><data key="edge_source_entity_id">DATA_IRS_TAX_REQUEST_TEMPLATE</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">DATA_IRS_TAX_REQUEST_TP_ADDRESS</data><data key="edge_operational_context">Current POMS instructs SSA to include taxpayer name/address on the request template.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Outbound SSA-provided address attribute.</data></edge><edge id="R86_REL035" source="PROC_IRS_TAX_INFO_REQUEST" target="DATA_IRS_ACCOUNT_TRANSCRIPT"><data key="edge_relationship_id">R86_REL035</data><data key="edge_source_entity_id">PROC_IRS_TAX_INFO_REQUEST</data><data key="edge_relationship_type">may_receive</data><data key="edge_target_entity_id">DATA_IRS_ACCOUNT_TRANSCRIPT</data><data key="edge_operational_context">IRS may answer the written SSA request with an Account Transcript when available.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">POMS says allow IRS 30 days when online SSA systems do not contain the needed tax information.</data></edge><edge id="R86_REL036" source="PROC_IRS_TAX_INFO_REQUEST" target="DATA_IRS_RETURN_TRANSCRIPT"><data key="edge_relationship_id">R86_REL036</data><data key="edge_source_entity_id">PROC_IRS_TAX_INFO_REQUEST</data><data key="edge_relationship_type">may_receive</data><data key="edge_target_entity_id">DATA_IRS_RETURN_TRANSCRIPT</data><data key="edge_operational_context">IRS may answer the written SSA request with a Return Transcript when available.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">This is evidence retrieval, not a master-record synchronization feed.</data></edge><edge id="R86_REL037" source="DATA_IRS_ACCOUNT_TRANSCRIPT" target="ORG_IRS"><data key="edge_relationship_id">R86_REL037</data><data key="edge_source_entity_id">DATA_IRS_ACCOUNT_TRANSCRIPT</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">IRS provides Account Transcripts in response to appropriate SSA requests.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Current/prior-three-year availability is documented for relevant SE schedules.</data></edge><edge id="R86_REL038" source="DATA_IRS_RETURN_TRANSCRIPT" target="ORG_IRS"><data key="edge_relationship_id">R86_REL038</data><data key="edge_source_entity_id">DATA_IRS_RETURN_TRANSCRIPT</data><data key="edge_relationship_type">provided_by</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">IRS provides Return Transcripts in response to appropriate SSA requests.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Current/prior-three-year transcript availability is documented for relevant schedules.</data></edge><edge id="R86_REL039" source="FMT_EFW2" target="DATA_EFW2_EMPLOYER_DELIVERY_ADDRESS"><data key="edge_relationship_id">R86_REL039</data><data key="edge_source_entity_id">FMT_EFW2</data><data key="edge_relationship_type">contains_required_field</data><data key="edge_target_entity_id">DATA_EFW2_EMPLOYER_DELIVERY_ADDRESS</data><data key="edge_operational_context">Starting with tax year 2025, the EFW2 RE Employer record requires Employer Delivery Address for electronic submissions.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes">Required-file-field relationship.</data></edge><edge id="R86_REL040" source="FORM_SSA308" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R86_REL040</data><data key="edge_source_entity_id">FORM_SSA308</data><data key="edge_relationship_type">submittable_online_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA current Forms catalog provides an online-submission route for SSA-308 within the agency electronic forms framework.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">The public catalog does not expose per-form backend routing.</data></edge><edge id="R86_REL041" source="FORM_SSA3885" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R86_REL041</data><data key="edge_source_entity_id">FORM_SSA3885</data><data key="edge_relationship_type">submittable_online_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA current Forms catalog provides an online-submission route for SSA-3885 within the agency electronic forms framework.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">4</data><data key="edge_notes">The public catalog does not expose per-form backend routing.</data></edge><edge id="R86_REL042" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VA2_IMMIGRATION"><data key="edge_relationship_id">R86_REL042</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VA2_IMMIGRATION</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes V.A2 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL043" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VA3_POP_DEP"><data key="edge_relationship_id">R86_REL043</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VA3_POP_DEP</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes V.A3 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL044" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VA4_PERIOD_LE"><data key="edge_relationship_id">R86_REL044</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VA4_PERIOD_LE</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes V.A4 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL045" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VA5_COHORT_LE"><data key="edge_relationship_id">R86_REL045</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VA5_COHORT_LE</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes V.A5 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL046" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VB2_ECON"><data key="edge_relationship_id">R86_REL046</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VB2_ECON</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes V.B2 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL047" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VC4_OASI_BEN"><data key="edge_relationship_id">R86_REL047</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VC4_OASI_BEN</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes V.C4 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL048" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VC5_DI_BEN"><data key="edge_relationship_id">R86_REL048</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VC5_DI_BEN</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes V.C5 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL049" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VC7_SCHED_BEN"><data key="edge_relationship_id">R86_REL049</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VC7_SCHED_BEN</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes V.C7 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL050" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VIG1_ECON_VARS"><data key="edge_relationship_id">R86_REL050</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VIG1_ECON_VARS</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes VI.G1 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL051" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VIG2_TRUST_OPS_CUR"><data key="edge_relationship_id">R86_REL051</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VIG2_TRUST_OPS_CUR</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes VI.G2 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL052" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VIG3_NONINT_CUR"><data key="edge_relationship_id">R86_REL052</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VIG3_NONINT_CUR</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes VI.G3 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL053" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VIG4_TRUST_OPS_CPI"><data key="edge_relationship_id">R86_REL053</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VIG4_TRUST_OPS_CPI</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes VI.G4 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL054" source="DATA_OACT_TR2026_SINGLE_YEAR" target="DATA_OACT_TR_VIG5_NONINT_CPI"><data key="edge_relationship_id">R86_REL054</data><data key="edge_source_entity_id">DATA_OACT_TR2026_SINGLE_YEAR</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_OACT_TR_VIG5_NONINT_CPI</data><data key="edge_operational_context">The 2026 OASDI Trustees supplemental single-year collection publishes VI.G5 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL055" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVA1_POP"><data key="edge_relationship_id">R86_REL055</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVA1_POP</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.A1 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL056" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVA2_FBR"><data key="edge_relationship_id">R86_REL056</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVA2_FBR</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.A2 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL057" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB4_NONDEATH_TERMS"><data key="edge_relationship_id">R86_REL057</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB4_NONDEATH_TERMS</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.B4 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL058" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB5_ALL_TERMS"><data key="edge_relationship_id">R86_REL058</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB5_ALL_TERMS</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.B5 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL059" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB6_FED_CP"><data key="edge_relationship_id">R86_REL059</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB6_FED_CP</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.B6 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL060" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB7_PREVALENCE"><data key="edge_relationship_id">R86_REL060</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB7_PREVALENCE</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.B7 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL061" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB8_STATE_ONLY_CP"><data key="edge_relationship_id">R86_REL061</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB8_STATE_ONLY_CP</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.B8 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL062" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVB9_ALL_ADMIN_CP"><data key="edge_relationship_id">R86_REL062</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVB9_ALL_ADMIN_CP</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.B9 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL063" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVC2_FY_FED_PAY"><data key="edge_relationship_id">R86_REL063</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC2_FY_FED_PAY</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.C2 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL064" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVC3_CPI_FED_PAY"><data key="edge_relationship_id">R86_REL064</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC3_CPI_FED_PAY</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.C3 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL065" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVC4_STATE_SUPP_PAY"><data key="edge_relationship_id">R86_REL065</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVC4_STATE_SUPP_PAY</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.C4 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL066" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVD1_GDP"><data key="edge_relationship_id">R86_REL066</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVD1_GDP</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.D1 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R86_REL067" source="DATA_SSI_SINGLE_YEAR_2026" target="DATA_SSI_AR_IVE1_COSTS"><data key="edge_relationship_id">R86_REL067</data><data key="edge_source_entity_id">DATA_SSI_SINGLE_YEAR_2026</data><data key="edge_relationship_type">contains_table</data><data key="edge_target_entity_id">DATA_SSI_AR_IVE1_COSTS</data><data key="edge_operational_context">The 2026 SSI Annual Report supplemental single-year collection publishes IV.E1 as a separate table.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes">Publication containment only.</data></edge><edge id="R87_REL001" source="APP_MCS" target="PROC_EDCS_MAINFRAME_PROPAGATION"><data key="edge_relationship_id">R87_REL001</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">supplies_data_to_process</data><data key="edge_target_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_operational_context">Current EDCS policy identifies this as a mainframe source for data propagation into EDCS.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes">Existing direct source-to-EDCS relationships are retained; this adds the explicit propagation-process node.</data></edge><edge id="R87_REL002" source="APP_MSSICS" target="PROC_EDCS_MAINFRAME_PROPAGATION"><data key="edge_relationship_id">R87_REL002</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">supplies_data_to_process</data><data key="edge_target_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_operational_context">Current EDCS policy identifies this as a mainframe source for data propagation into EDCS.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes">Existing direct source-to-EDCS relationships are retained; this adds the explicit propagation-process node.</data></edge><edge id="R87_REL003" source="SYS_ICDB" target="PROC_EDCS_MAINFRAME_PROPAGATION"><data key="edge_relationship_id">R87_REL003</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">supplies_data_to_process</data><data key="edge_target_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_operational_context">Current EDCS policy identifies this as a mainframe source for data propagation into EDCS.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes">Existing direct source-to-EDCS relationships are retained; this adds the explicit propagation-process node.</data></edge><edge id="R87_REL004" source="SYS_NUMIDENT" target="PROC_EDCS_MAINFRAME_PROPAGATION"><data key="edge_relationship_id">R87_REL004</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">supplies_data_to_process</data><data key="edge_target_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_operational_context">Current EDCS policy identifies this as a mainframe source for data propagation into EDCS.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes">Existing direct source-to-EDCS relationships are retained; this adds the explicit propagation-process node.</data></edge><edge id="R87_REL005" source="SYS_SSR" target="PROC_EDCS_MAINFRAME_PROPAGATION"><data key="edge_relationship_id">R87_REL005</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">supplies_data_to_process</data><data key="edge_target_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_operational_context">Current EDCS policy identifies this as a mainframe source for data propagation into EDCS.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes">Existing direct source-to-EDCS relationships are retained; this adds the explicit propagation-process node.</data></edge><edge id="R87_REL006" source="SYS_MBR" target="PROC_EDCS_MAINFRAME_PROPAGATION"><data key="edge_relationship_id">R87_REL006</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">supplies_data_to_process</data><data key="edge_target_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_operational_context">Current EDCS policy identifies this as a mainframe source for data propagation into EDCS.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes">Existing direct source-to-EDCS relationships are retained; this adds the explicit propagation-process node.</data></edge><edge id="R87_REL007" source="PROC_EDCS_MAINFRAME_PROPAGATION" target="APP_EDCS"><data key="edge_relationship_id">R87_REL007</data><data key="edge_source_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_relationship_type">populates</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Propagation process populates EDCS when a case is created.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL008" source="PROC_EDCS_MAINFRAME_PROPAGATION" target="APP_MCS"><data key="edge_relationship_id">R87_REL008</data><data key="edge_source_entity_id">PROC_EDCS_MAINFRAME_PROPAGATION</data><data key="edge_relationship_type">uses_source_precedence</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS propagates before other mainframe sources when a current MCS claim exists.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL009" source="SYS_NUMIDENT" target="UI_EDCS_MCS_EXCLUSION_INFO"><data key="edge_relationship_id">R87_REL009</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">supplies_exclusion_case_data_to</data><data key="edge_target_entity_id">UI_EDCS_MCS_EXCLUSION_INFO</data><data key="edge_operational_context">When no current MCS/MSSICS claim or appeal exists, available Numident data can populate the EDCS MCS Exclusion Information screen.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL010" source="SYS_MBR" target="UI_EDCS_MCS_EXCLUSION_INFO"><data key="edge_relationship_id">R87_REL010</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">supplies_exclusion_case_data_to</data><data key="edge_target_entity_id">UI_EDCS_MCS_EXCLUSION_INFO</data><data key="edge_operational_context">When no current MCS/MSSICS claim or appeal exists, MBR name/date-of-birth information populates the EDCS MCS Exclusion Information screen.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL011" source="UI_EDCS_MCS_EXCLUSION_INFO" target="APP_EDCS"><data key="edge_relationship_id">R87_REL011</data><data key="edge_source_entity_id">UI_EDCS_MCS_EXCLUSION_INFO</data><data key="edge_relationship_type">screen_within</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">The MCS Exclusion Information page is an EDCS screen and can populate subsequent EDCS screens.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL012" source="UTIL_EDCS_COPY_FROM_PRIOR" target="APP_EDCS"><data key="edge_relationship_id">R87_REL012</data><data key="edge_source_entity_id">UTIL_EDCS_COPY_FROM_PRIOR</data><data key="edge_relationship_type">feature_within</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Copy from Prior is activated on applicable EDCS disability-report screens for subsequent initial cases.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL013" source="UTIL_EDCS_COPY_FROM_PRIOR" target="APP_EVIEW"><data key="edge_relationship_id">R87_REL013</data><data key="edge_source_entity_id">UTIL_EDCS_COPY_FROM_PRIOR</data><data key="edge_relationship_type">copies_selected_data_from</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">The feature copies selected information from the most recent closed electronic folder surfaced through the electronic-folder environment.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">4</data><data key="edge_notes">eView is modeled as the current electronic-folder viewing application; the source describes the prior closed EF rather than naming a storage table.</data></edge><edge id="R87_REL014" source="APP_EDCS" target="DATA_EVIEW_CLIENT_DATES"><data key="edge_relationship_id">R87_REL014</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">records_internet_propagation_status_for</data><data key="edge_target_entity_id">DATA_EVIEW_CLIENT_DATES</data><data key="edge_operational_context">EDCS records whether an Internet disability report propagated and eView Client Dates exposes submission/propagation details.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL015" source="DATA_EVIEW_CLIENT_DATES" target="APP_EVIEW"><data key="edge_relationship_id">R87_REL015</data><data key="edge_source_entity_id">DATA_EVIEW_CLIENT_DATES</data><data key="edge_relationship_type">displayed_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">POMS says this information is available in eView on Case Information under Client Dates.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL016" source="PROC_ERPS_EIN_VERIFICATION" target="APP_ERPS"><data key="edge_relationship_id">R87_REL016</data><data key="edge_source_entity_id">PROC_ERPS_EIN_VERIFICATION</data><data key="edge_relationship_type">implemented_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Organizational EIN verification is performed in eRPS.</data><data key="edge_observed_as_of">2023-05-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL017" source="PROC_ERPS_EIN_VERIFICATION" target="DB_EIF"><data key="edge_relationship_id">R87_REL017</data><data key="edge_source_entity_id">PROC_ERPS_EIN_VERIFICATION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_EIF</data><data key="edge_operational_context">The Verify EIN action searches the Employer Identification File.</data><data key="edge_observed_as_of">2023-05-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL018" source="PROC_ERPS_EIN_VERIFICATION" target="UI_ERPS_EIN_INFO_FROM_EIF"><data key="edge_relationship_id">R87_REL018</data><data key="edge_source_entity_id">PROC_ERPS_EIN_VERIFICATION</data><data key="edge_relationship_type">displays_result_on</data><data key="edge_target_entity_id">UI_ERPS_EIN_INFO_FROM_EIF</data><data key="edge_operational_context">EIF result is displayed on the EIN Info from EIF screen.</data><data key="edge_observed_as_of">2023-05-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL019" source="UI_ERPS_EIN_INFO_FROM_EIF" target="APP_ERPS"><data key="edge_relationship_id">R87_REL019</data><data key="edge_source_entity_id">UI_ERPS_EIN_INFO_FROM_EIF</data><data key="edge_relationship_type">screen_within</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">EIN Info from EIF is an eRPS screen.</data><data key="edge_observed_as_of">2023-05-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL020" source="PROC_ERPS_EIN_VERIFICATION" target="DATA_ERPS_EINVER_ISSUE"><data key="edge_relationship_id">R87_REL020</data><data key="edge_source_entity_id">PROC_ERPS_EIN_VERIFICATION</data><data key="edge_relationship_type">creates_issue_when_unresolved</data><data key="edge_target_entity_id">DATA_ERPS_EINVER_ISSUE</data><data key="edge_operational_context">Rejected or unresolved EIN verification can create an EINVER issue, including a five-day tickle when a found EIN is rejected.</data><data key="edge_observed_as_of">2023-05-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL021" source="DATA_ERPS_EINVER_ISSUE" target="APP_ERPS"><data key="edge_relationship_id">R87_REL021</data><data key="edge_source_entity_id">DATA_ERPS_EINVER_ISSUE</data><data key="edge_relationship_type">work_control_within</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">EINVER is a system-created eRPS issue.</data><data key="edge_observed_as_of">2023-05-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL022" source="UI_ERPS_BENEFICIARY_ADDRESS_CHANGE" target="APP_ERPS"><data key="edge_relationship_id">R87_REL022</data><data key="edge_source_entity_id">UI_ERPS_BENEFICIARY_ADDRESS_CHANGE</data><data key="edge_relationship_type">screen_within</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current policy identifies the Beneficiary Address Change screen as an eRPS screen.</data><data key="edge_observed_as_of">2025-05-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL023" source="UI_ERPS_BENEFICIARY_ADDRESS_CHANGE" target="PROC_RP_COA"><data key="edge_relationship_id">R87_REL023</data><data key="edge_source_entity_id">UI_ERPS_BENEFICIARY_ADDRESS_CHANGE</data><data key="edge_relationship_type">updates_beneficiary_residence_for</data><data key="edge_target_entity_id">PROC_RP_COA</data><data key="edge_operational_context">Representative-payee workflows use the screen for beneficiary residence changes.</data><data key="edge_observed_as_of">2025-05-16</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL024" source="APP_ERPS" target="SYS_MBR"><data key="edge_relationship_id">R87_REL024</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">automatically_updates_individual_payee_title_ii_address_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For an individual representative payee Title II COA, eRPS sends the change automatically to the MBR the following night.</data><data key="edge_observed_as_of">2020-04-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL025" source="APP_ERPS" target="SYS_SSR"><data key="edge_relationship_id">R87_REL025</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">does_not_send_individual_payee_title_xvi_coa_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">For an individual payee Title XVI COA, policy explicitly says eRPS does not send the address change to the SSR.</data><data key="edge_observed_as_of">2020-04-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL026" source="APP_ERPS" target="APP_MSSICS"><data key="edge_relationship_id">R87_REL026</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">requires_parallel_title_xvi_address_input_via</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">For individual payee Title XVI COA, staff first update eRPS and then MSSICS to build/update the SSR.</data><data key="edge_observed_as_of">2020-04-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL027" source="APP_ERPS" target="SYS_MBR"><data key="edge_relationship_id">R87_REL027</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">automatically_updates_institutional_payee_title_ii_records_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">For institutional payees correctly established in eRPS, COA input automatically updates associated Title II records.</data><data key="edge_observed_as_of">2020-04-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL028" source="APP_ERPS" target="SYS_SSR"><data key="edge_relationship_id">R87_REL028</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">automatically_updates_institutional_payee_title_xvi_records_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">For institutional payees correctly established in eRPS, COA input automatically updates associated Title XVI records.</data><data key="edge_observed_as_of">2020-04-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL029" source="APP_MYCOA" target="DATA_MYCOA_PENDING_FUTURE_ADDRESS"><data key="edge_relationship_id">R87_REL029</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">DATA_MYCOA_PENDING_FUTURE_ADDRESS</data><data key="edge_operational_context">Title II users may choose a later effective date within 90 days; future-effective address changes remain pending until the appropriate month.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL030" source="DATA_MYCOA_PENDING_FUTURE_ADDRESS" target="APP_T2R"><data key="edge_relationship_id">R87_REL030</data><data key="edge_source_entity_id">DATA_MYCOA_PENDING_FUTURE_ADDRESS</data><data key="edge_relationship_type">processed_by</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">Title II Redesign processes myCOA address inputs.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL031" source="DATA_MYCOA_PENDING_FUTURE_ADDRESS" target="SYS_MBR"><data key="edge_relationship_id">R87_REL031</data><data key="edge_source_entity_id">DATA_MYCOA_PENDING_FUTURE_ADDRESS</data><data key="edge_relationship_type">posts_to_when_effective</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">myCOA Title II address changes are reflected in the MBR; future-effective changes remain pending until the appropriate month.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes">The source does not identify the physical pending store.</data></edge><edge id="R87_REL032" source="ORG_SSA_OCACT" target="DATA_OACT_AS_4A1_OASI_TF"><data key="edge_relationship_id">R87_REL032</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_AS_4A1_OASI_TF</data><data key="edge_operational_context">Current Actuarial Services statistical-table publication.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL033" source="ORG_SSA_OCACT" target="DATA_OACT_AS_4A2_DI_TF"><data key="edge_relationship_id">R87_REL033</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_AS_4A2_DI_TF</data><data key="edge_operational_context">Current Actuarial Services statistical-table publication.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL034" source="ORG_SSA_OCACT" target="DATA_OACT_AS_4A3_OASDI_TF"><data key="edge_relationship_id">R87_REL034</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_AS_4A3_OASDI_TF</data><data key="edge_operational_context">Current Actuarial Services statistical-table publication.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL035" source="ORG_SSA_OCACT" target="DATA_OACT_AS_4A4_TOTAL_BENEFITS"><data key="edge_relationship_id">R87_REL035</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_AS_4A4_TOTAL_BENEFITS</data><data key="edge_operational_context">Current Actuarial Services statistical-table publication.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL036" source="ORG_SSA_OCACT" target="DATA_OACT_AS_4A5_OASI_BENEFITS"><data key="edge_relationship_id">R87_REL036</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_AS_4A5_OASI_BENEFITS</data><data key="edge_operational_context">Current Actuarial Services statistical-table publication.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL037" source="ORG_SSA_OCACT" target="DATA_OACT_AS_4A6_DI_BENEFITS"><data key="edge_relationship_id">R87_REL037</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_AS_4A6_DI_BENEFITS</data><data key="edge_operational_context">Current Actuarial Services statistical-table publication.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL038" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_AS_4A1_OASI_TF"><data key="edge_relationship_id">R87_REL038</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">publication_defers_to</data><data key="edge_target_entity_id">DATA_OACT_AS_4A1_OASI_TF</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement discontinues section 4.A because the same table is already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL039" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_AS_4A2_DI_TF"><data key="edge_relationship_id">R87_REL039</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">publication_defers_to</data><data key="edge_target_entity_id">DATA_OACT_AS_4A2_DI_TF</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement discontinues section 4.A because the same table is already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL040" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_AS_4A3_OASDI_TF"><data key="edge_relationship_id">R87_REL040</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">publication_defers_to</data><data key="edge_target_entity_id">DATA_OACT_AS_4A3_OASDI_TF</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement discontinues section 4.A because the same table is already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL041" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_AS_4A4_TOTAL_BENEFITS"><data key="edge_relationship_id">R87_REL041</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">publication_defers_to</data><data key="edge_target_entity_id">DATA_OACT_AS_4A4_TOTAL_BENEFITS</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement discontinues section 4.A because the same table is already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL042" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_AS_4A5_OASI_BENEFITS"><data key="edge_relationship_id">R87_REL042</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">publication_defers_to</data><data key="edge_target_entity_id">DATA_OACT_AS_4A5_OASI_BENEFITS</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement discontinues section 4.A because the same table is already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL043" source="REPORT_STAT_SUPP_2026" target="DATA_OACT_AS_4A6_DI_BENEFITS"><data key="edge_relationship_id">R87_REL043</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">publication_defers_to</data><data key="edge_target_entity_id">DATA_OACT_AS_4A6_DI_BENEFITS</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement discontinues section 4.A because the same table is already published by Actuarial Services.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL044" source="PROC_T2_OVERPAY_NOTICE_GENERATION" target="DATA_T2_OVERPAYMENT_NOTICE"><data key="edge_relationship_id">R87_REL044</data><data key="edge_source_entity_id">PROC_T2_OVERPAY_NOTICE_GENERATION</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_T2_OVERPAYMENT_NOTICE</data><data key="edge_operational_context">Current policy requires written notice after discovery of a Title II overpayment.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL045" source="APP_MACADE" target="DATA_T2_OVERPAYMENT_NOTICE"><data key="edge_relationship_id">R87_REL045</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">can_generate</data><data key="edge_target_entity_id">DATA_T2_OVERPAYMENT_NOTICE</data><data key="edge_operational_context">Current POMS identifies MACADE as a written overpayment-notice channel.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL046" source="APP_AURORA" target="DATA_T2_OVERPAYMENT_NOTICE"><data key="edge_relationship_id">R87_REL046</data><data key="edge_source_entity_id">APP_AURORA</data><data key="edge_relationship_type">can_generate</data><data key="edge_target_entity_id">DATA_T2_OVERPAYMENT_NOTICE</data><data key="edge_operational_context">Current POMS identifies AURORA as a written overpayment-notice channel.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL047" source="APP_DPS" target="DATA_T2_OVERPAYMENT_NOTICE"><data key="edge_relationship_id">R87_REL047</data><data key="edge_source_entity_id">APP_DPS</data><data key="edge_relationship_type">can_generate</data><data key="edge_target_entity_id">DATA_T2_OVERPAYMENT_NOTICE</data><data key="edge_operational_context">Current POMS identifies DPS as a written overpayment-notice channel.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R87_REL048" source="PROC_T2_OVERPAY_NOTICE_GENERATION" target="UI_DMS_RMKS"><data key="edge_relationship_id">R87_REL048</data><data key="edge_source_entity_id">PROC_T2_OVERPAY_NOTICE_GENERATION</data><data key="edge_relationship_type">documents_oral_contact_in</data><data key="edge_target_entity_id">UI_DMS_RMKS</data><data key="edge_operational_context">When overpayment is discovered during oral communication, policy directs staff to document the conversation on DMS Remarks.</data><data key="edge_observed_as_of">2026-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL001" source="SVC_SAVE" target="DATA_SAVE_QUERY_RESPONSE"><data key="edge_relationship_id">R88_REL001</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_operational_context">Online SAVE returns a DHS-derived response for the A-Number or admission number submitted to the query.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes">Response is a verification result; benefit eligibility remains an SSA determination.</data></edge><edge id="R88_REL002" source="DATA_SAVE_QUERY_RESPONSE" target="UI_SAVE_RESPONSE"><data key="edge_relationship_id">R88_REL002</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">displayed_on</data><data key="edge_target_entity_id">UI_SAVE_RESPONSE</data><data key="edge_operational_context">Selected DHS record attributes from the SAVE response propagate to the SSA SAVE screen.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL003" source="DATA_SAVE_QUERY_RESPONSE" target="DATA_SAVE_DOB"><data key="edge_relationship_id">R88_REL003</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SAVE_DOB</data><data key="edge_operational_context">Current lawful-presence POMS enumerates this value among or within the online SAVE response used by SSA.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL004" source="DATA_SAVE_QUERY_RESPONSE" target="DATA_SAVE_COUNTRY_OF_BIRTH"><data key="edge_relationship_id">R88_REL004</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SAVE_COUNTRY_OF_BIRTH</data><data key="edge_operational_context">Current lawful-presence POMS enumerates this value among or within the online SAVE response used by SSA.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL005" source="DATA_SAVE_QUERY_RESPONSE" target="DATA_SAVE_DHS_SSN"><data key="edge_relationship_id">R88_REL005</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SAVE_DHS_SSN</data><data key="edge_operational_context">Current lawful-presence POMS enumerates this value among or within the online SAVE response used by SSA.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL006" source="DATA_SAVE_QUERY_RESPONSE" target="DATA_SAVE_DATE_OF_ENTRY"><data key="edge_relationship_id">R88_REL006</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SAVE_DATE_OF_ENTRY</data><data key="edge_operational_context">Current lawful-presence POMS enumerates this value among or within the online SAVE response used by SSA.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL007" source="DATA_SAVE_QUERY_RESPONSE" target="DATA_SAVE_VERIFICATION_NUMBER"><data key="edge_relationship_id">R88_REL007</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SAVE_VERIFICATION_NUMBER</data><data key="edge_operational_context">Current lawful-presence POMS enumerates this value among or within the online SAVE response used by SSA.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL008" source="DATA_SAVE_QUERY_RESPONSE" target="DATA_SAVE_CLASS_OF_ADMISSION"><data key="edge_relationship_id">R88_REL008</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SAVE_CLASS_OF_ADMISSION</data><data key="edge_operational_context">Current lawful-presence POMS enumerates this value among or within the online SAVE response used by SSA.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL009" source="DATA_SAVE_QUERY_RESPONSE" target="DATA_SAVE_DATE_ADMITTED_TO"><data key="edge_relationship_id">R88_REL009</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SAVE_DATE_ADMITTED_TO</data><data key="edge_operational_context">Current lawful-presence POMS enumerates this value among or within the online SAVE response used by SSA.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL010" source="DATA_SAVE_QUERY_RESPONSE" target="DATA_SAVE_ELIGIBILITY_STATEMENT"><data key="edge_relationship_id">R88_REL010</data><data key="edge_source_entity_id">DATA_SAVE_QUERY_RESPONSE</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SAVE_ELIGIBILITY_STATEMENT</data><data key="edge_operational_context">Current lawful-presence POMS enumerates this value among or within the online SAVE response used by SSA.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL011" source="DATA_SAVE_DHS_SSN" target="SYS_NUMIDENT"><data key="edge_relationship_id">R88_REL011</data><data key="edge_source_entity_id">DATA_SAVE_DHS_SSN</data><data key="edge_relationship_type">not_authoritative_for_ssa_identity_correction</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">POMS warns the SSN in the DHS record may be self-reported and inaccurate and instructs SSA not to verify it or request DHS correction when incorrect.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes">Negative provenance boundary: no Numident update path is inferred from this DHS-returned value.</data></edge><edge id="R88_REL012" source="PROC_LAWFUL_PRESENCE_VERIFICATION" target="SVC_SAVE"><data key="edge_relationship_id">R88_REL012</data><data key="edge_source_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">When policy conditions are met, SSA uses online SAVE with submitted immigration evidence to establish U.S. lawful presence for benefit payment.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL013" source="PROC_LAWFUL_PRESENCE_VERIFICATION" target="DATA_LAWFUL_PRESENCE_PROOF"><data key="edge_relationship_id">R88_REL013</data><data key="edge_source_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="edge_relationship_type">uses_claim_proof</data><data key="edge_target_entity_id">DATA_LAWFUL_PRESENCE_PROOF</data><data key="edge_operational_context">Current policy can accept qualifying prior SSA system evidence/proof coding subject to currency and consistency rules.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL014" source="PROC_LAWFUL_PRESENCE_VERIFICATION" target="FORM_G845"><data key="edge_relationship_id">R88_REL014</data><data key="edge_source_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="edge_relationship_type">falls_back_to</data><data key="edge_target_entity_id">FORM_G845</data><data key="edge_operational_context">When online SAVE cannot be used for specified cases, SSA requests manual DHS verification using Form G-845.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL015" source="FORM_G845" target="FORM_G845_SUPPLEMENT"><data key="edge_relationship_id">R88_REL015</data><data key="edge_source_entity_id">FORM_G845</data><data key="edge_relationship_type">may_include</data><data key="edge_target_entity_id">FORM_G845_SUPPLEMENT</data><data key="edge_operational_context">Specified lawful-presence categories require or allow the Supplement to Form G-845.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL016" source="FORM_G845" target="CTRL_G845_DW01"><data key="edge_relationship_id">R88_REL016</data><data key="edge_source_entity_id">FORM_G845</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">CTRL_G845_DW01</data><data key="edge_operational_context">SSA enters a G845 issue on MCS DW01 with a 20-federal-working-day follow-up period.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL017" source="CTRL_G845_DW01" target="UI_MCS_DW01"><data key="edge_relationship_id">R88_REL017</data><data key="edge_source_entity_id">CTRL_G845_DW01</data><data key="edge_relationship_type">implemented_on</data><data key="edge_target_entity_id">UI_MCS_DW01</data><data key="edge_operational_context">The G845 development issue is entered on the MCS Development Worksheet DW01.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL018" source="DATA_CEF_FLAG" target="REPO_CEF"><data key="edge_relationship_id">R88_REL018</data><data key="edge_source_entity_id">DATA_CEF_FLAG</data><data key="edge_relationship_type">persisted_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Current EDCS/eView policy treats DATA_CEF_FLAG as part of the Certified Electronic Folder case-handling environment.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">CEF is the documented logical/official folder boundary; physical database technology is not inferred.</data></edge><edge id="R88_REL019" source="APP_EDCS" target="DATA_CEF_FLAG"><data key="edge_relationship_id">R88_REL019</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">creates_or_manages</data><data key="edge_target_entity_id">DATA_CEF_FLAG</data><data key="edge_operational_context">FO users can create or manage this CEF case-handling artifact in EDCS.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL020" source="APP_EVIEW" target="DATA_CEF_FLAG"><data key="edge_relationship_id">R88_REL020</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">creates_or_manages</data><data key="edge_target_entity_id">DATA_CEF_FLAG</data><data key="edge_operational_context">Users can create or manage this CEF case-handling artifact in eView.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL021" source="DATA_CEF_FLAG" target="DATA_EDCS_UAT_ALERT"><data key="edge_relationship_id">R88_REL021</data><data key="edge_source_entity_id">DATA_CEF_FLAG</data><data key="edge_relationship_type">can_trigger</data><data key="edge_target_entity_id">DATA_EDCS_UAT_ALERT</data><data key="edge_operational_context">When added by an office without case jurisdiction, the jurisdiction office receives an alert/UAT notification.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">Trigger is conditional on office jurisdiction.</data></edge><edge id="R88_REL022" source="DATA_CEF_MESSAGE" target="REPO_CEF"><data key="edge_relationship_id">R88_REL022</data><data key="edge_source_entity_id">DATA_CEF_MESSAGE</data><data key="edge_relationship_type">persisted_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Current EDCS/eView policy treats DATA_CEF_MESSAGE as part of the Certified Electronic Folder case-handling environment.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">CEF is the documented logical/official folder boundary; physical database technology is not inferred.</data></edge><edge id="R88_REL023" source="APP_EDCS" target="DATA_CEF_MESSAGE"><data key="edge_relationship_id">R88_REL023</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">creates_or_manages</data><data key="edge_target_entity_id">DATA_CEF_MESSAGE</data><data key="edge_operational_context">FO users can create or manage this CEF case-handling artifact in EDCS.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL024" source="APP_EVIEW" target="DATA_CEF_MESSAGE"><data key="edge_relationship_id">R88_REL024</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">creates_or_manages</data><data key="edge_target_entity_id">DATA_CEF_MESSAGE</data><data key="edge_operational_context">Users can create or manage this CEF case-handling artifact in eView.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL025" source="DATA_CEF_MESSAGE" target="DATA_EDCS_UAT_ALERT"><data key="edge_relationship_id">R88_REL025</data><data key="edge_source_entity_id">DATA_CEF_MESSAGE</data><data key="edge_relationship_type">can_trigger</data><data key="edge_target_entity_id">DATA_EDCS_UAT_ALERT</data><data key="edge_operational_context">When added by an office without case jurisdiction, the jurisdiction office receives an alert/UAT notification.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">Trigger is conditional on office jurisdiction.</data></edge><edge id="R88_REL026" source="CTRL_CDRW" target="DB_DCF"><data key="edge_relationship_id">R88_REL026</data><data key="edge_source_entity_id">CTRL_CDRW</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">FO places a five-day CDRW tickle in DCF to control expected post-determination record updates.</data><data key="edge_observed_as_of">2026-08-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL027" source="CTRL_CDRW" target="SYS_MBR"><data key="edge_relationship_id">R88_REL027</data><data key="edge_source_entity_id">CTRL_CDRW</data><data key="edge_relationship_type">monitors_update_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II and concurrent CDR appeal workflows use the CDRW tickle to ensure the MBR update posts.</data><data key="edge_observed_as_of">2026-08-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL028" source="CTRL_CDRW" target="SYS_SSR"><data key="edge_relationship_id">R88_REL028</data><data key="edge_source_entity_id">CTRL_CDRW</data><data key="edge_relationship_type">monitors_update_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI and concurrent CDR appeal workflows use the CDRW tickle to ensure the SSR update posts.</data><data key="edge_observed_as_of">2026-08-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL029" source="CTRL_DIBCESS_PCACS" target="APP_PCACS"><data key="edge_relationship_id">R88_REL029</data><data key="edge_source_entity_id">CTRL_DIBCESS_PCACS</data><data key="edge_relationship_type">pending_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">If an expected Title II MBR update does not post within five days, FO verifies the DIBCESS issue is pending on PCACS.</data><data key="edge_observed_as_of">2026-08-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL030" source="CTRL_DIBCESS_PCACS" target="DATA_DCF_PROBLEM_REPORT"><data key="edge_relationship_id">R88_REL030</data><data key="edge_source_entity_id">CTRL_DIBCESS_PCACS</data><data key="edge_relationship_type">absence_can_trigger</data><data key="edge_target_entity_id">DATA_DCF_PROBLEM_REPORT</data><data key="edge_operational_context">POMS directs a DCF Problem Report when there is no DIBCESS issue on PCACS and no explanatory THIS-query exception.</data><data key="edge_observed_as_of">2026-08-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL031" source="QUERY_THIS" target="DATA_DCF_PROBLEM_REPORT"><data key="edge_relationship_id">R88_REL031</data><data key="edge_source_entity_id">QUERY_THIS</data><data key="edge_relationship_type">no_exception_can_trigger</data><data key="edge_target_entity_id">DATA_DCF_PROBLEM_REPORT</data><data key="edge_operational_context">A DCF Problem Report is appropriate when the expected update is missing and the THIS query shows no exception under the stated conditions.</data><data key="edge_observed_as_of">2026-08-12</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL032" source="DATA_DCF_PROBLEM_REPORT" target="DB_DCF"><data key="edge_relationship_id">R88_REL032</data><data key="edge_source_entity_id">DATA_DCF_PROBLEM_REPORT</data><data key="edge_relationship_type">reports_problem_with</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">The problem report is used for missing/unexplained CDR update-control conditions involving DCF processing.</data><data key="edge_observed_as_of">2026-08-12</data><data key="edge_confidence">4</data><data key="edge_notes">Public POMS does not identify the report submission platform; relationship is business-context only.</data></edge><edge id="R88_REL033" source="FORM_SSA437BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R88_REL033</data><data key="edge_source_entity_id">FORM_SSA437BK</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current Forms catalog Submit Online link resolves to the shared Upload Documents route with target 437.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL034" source="FORM_SSA561" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R88_REL034</data><data key="edge_source_entity_id">FORM_SSA561</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current Forms catalog Submit Online link resolves to the shared Upload Documents route with target 561.</data><data key="edge_observed_as_of">2026-10-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL035" source="SVC_ONLINE_RIB_APP" target="APP_MCS"><data key="edge_relationship_id">R88_REL035</data><data key="edge_source_entity_id">SVC_ONLINE_RIB_APP</data><data key="edge_relationship_type">retrieved_for_entry_into</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">SSA says a Claims Representative retrieves the online retirement application and enters the information into MCS.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes">Staff-mediated entry; do not infer a direct frontend-to-MCS write interface.</data></edge><edge id="R88_REL036" source="SVC_ONLINE_RIB_APP" target="DATA_RIB_INTERNET_APPS_2246"><data key="edge_relationship_id">R88_REL036</data><data key="edge_source_entity_id">SVC_ONLINE_RIB_APP</data><data key="edge_relationship_type">provides_front_end_activity_tallies_for</data><data key="edge_target_entity_id">DATA_RIB_INTERNET_APPS_2246</data><data key="edge_operational_context">The Online Retirement Benefit Application provides the Internet front-end activity tallies used in the public collection.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL037" source="SVC_ONLINE_DIB_APP" target="APP_MCS"><data key="edge_relationship_id">R88_REL037</data><data key="edge_source_entity_id">SVC_ONLINE_DIB_APP</data><data key="edge_relationship_type">retrieved_for_entry_into</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">SSA says a Claims Representative retrieves the online disability application and enters the information into MCS.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes">Staff-mediated entry; do not infer a direct frontend-to-MCS write interface.</data></edge><edge id="R88_REL038" source="SVC_ONLINE_DIB_APP" target="DATA_DIB_INTERNET_APPS_2247"><data key="edge_relationship_id">R88_REL038</data><data key="edge_source_entity_id">SVC_ONLINE_DIB_APP</data><data key="edge_relationship_type">provides_front_end_activity_counts_for</data><data key="edge_target_entity_id">DATA_DIB_INTERNET_APPS_2247</data><data key="edge_operational_context">The Online Disability Benefit Application provides Internet front-end activity counts used in the public collection.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL039" source="APP_MCS" target="PROC_RSI_OPEN_DATA_AGGREGATION"><data key="edge_relationship_id">R88_REL039</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">feeds_nightly</data><data key="edge_target_entity_id">PROC_RSI_OPEN_DATA_AGGREGATION</data><data key="edge_operational_context">Current SSA Open Data says MCS data are downloaded nightly to the Title II ODS before batch preparation and aggregation for national reporting.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes">Process node represents the documented publication flow, not a newly asserted direct MCS-to-batch interface.</data></edge><edge id="R88_REL040" source="DB_TITLE2_ODS" target="PROC_RSI_OPEN_DATA_AGGREGATION"><data key="edge_relationship_id">R88_REL040</data><data key="edge_source_entity_id">DB_TITLE2_ODS</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">PROC_RSI_OPEN_DATA_AGGREGATION</data><data key="edge_operational_context">Current SSA Open Data identifies the Title II Operational Data Store as the nightly management-information store used before batch aggregation.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL041" source="DATA_DOWR" target="PROC_RSI_OPEN_DATA_AGGREGATION"><data key="edge_relationship_id">R88_REL041</data><data key="edge_source_entity_id">DATA_DOWR</data><data key="edge_relationship_type">provides_reporting_dates_to</data><data key="edge_target_entity_id">PROC_RSI_OPEN_DATA_AGGREGATION</data><data key="edge_operational_context">DOWR receipt dates define reporting periods for the public claims-volume data.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL042" source="PROC_RSI_OPEN_DATA_AGGREGATION" target="DATA_RSI_APPLICATION_VOLUMES"><data key="edge_relationship_id">R88_REL042</data><data key="edge_source_entity_id">PROC_RSI_OPEN_DATA_AGGREGATION</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_RSI_APPLICATION_VOLUMES</data><data key="edge_operational_context">SSA says batch processes prepare and aggregate Title II ODS claims data into national application-volume outputs.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R88_REL043" source="DB_TITLE2_ODS" target="DATA_DIB_INTERNET_APPS_2247"><data key="edge_relationship_id">R88_REL043</data><data key="edge_source_entity_id">DB_TITLE2_ODS</data><data key="edge_relationship_type">provides_counts_for</data><data key="edge_target_entity_id">DATA_DIB_INTERNET_APPS_2247</data><data key="edge_operational_context">The DIB Internet collection states MCS data are downloaded nightly to the Title II ODS and receipt counts are summarized into total and Internet national counts.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL001" source="APP_ELAS" target="UI_ELAS_WKSH"><data key="edge_relationship_id">R89_REL001</data><data key="edge_source_entity_id">APP_ELAS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_ELAS_WKSH</data><data key="edge_operational_context">eLAS uses the WKSH screen for Leads/Protective Filing worksheet issues including UNVER.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL002" source="APP_IAPPT" target="WORK_ELAS_UNVER"><data key="edge_relationship_id">R89_REL002</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">creates_work_control</data><data key="edge_target_entity_id">WORK_ELAS_UNVER</data><data key="edge_operational_context">iAppointment data transmitted to eLAS is marked with the UNVER issue.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL003" source="UI_ELAS_WKSH" target="WORK_ELAS_UNVER"><data key="edge_relationship_id">R89_REL003</data><data key="edge_source_entity_id">UI_ELAS_WKSH</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">WORK_ELAS_UNVER</data><data key="edge_operational_context">The eLAS WKSH screen contains the UNVER issue for iAppointment-created appointments/protective filings.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL004" source="WORK_ELAS_UNVER" target="SYS_ICDB"><data key="edge_relationship_id">R89_REL004</data><data key="edge_source_entity_id">WORK_ELAS_UNVER</data><data key="edge_relationship_type">isolates_data_from</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">Until verified/corrected and receipted, UNVER data remains isolated from CLIENT/ICDB.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes">No physical staging store is inferred.</data></edge><edge id="R89_REL005" source="APP_ELAS" target="FUNC_ELAS_VERIFY_PI"><data key="edge_relationship_id">R89_REL005</data><data key="edge_source_entity_id">APP_ELAS</data><data key="edge_relationship_type">provides_action</data><data key="edge_target_entity_id">FUNC_ELAS_VERIFY_PI</data><data key="edge_operational_context">The eLAS summary page exposes the Verify PI action used after staff verification.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL006" source="FUNC_ELAS_VERIFY_PI" target="WORK_ELAS_UNVER"><data key="edge_relationship_id">R89_REL006</data><data key="edge_source_entity_id">FUNC_ELAS_VERIFY_PI</data><data key="edge_relationship_type">receipts</data><data key="edge_target_entity_id">WORK_ELAS_UNVER</data><data key="edge_operational_context">Selecting Verify PI receipts the UNVER issue after staff verifies the appointment identity information.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes">Human-triggered control.</data></edge><edge id="R89_REL007" source="FUNC_ELAS_VERIFY_PI" target="SYS_ICDB"><data key="edge_relationship_id">R89_REL007</data><data key="edge_source_entity_id">FUNC_ELAS_VERIFY_PI</data><data key="edge_relationship_type">releases_verified_data_to</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">After verification, selecting Verify PI allows previously isolated iAppointment data to become part of CLIENT/ICDB.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes">Does not establish direct correction of Numident or PI.</data></edge><edge id="R89_REL008" source="APP_ELAS" target="UI_ELAS_RMRK"><data key="edge_relationship_id">R89_REL008</data><data key="edge_source_entity_id">APP_ELAS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_ELAS_RMRK</data><data key="edge_operational_context">eLAS includes the RMRK remarks screen referenced in iAppointment language-preference processing.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL009" source="APP_IAPPT" target="UI_ELAS_RMRK"><data key="edge_relationship_id">R89_REL009</data><data key="edge_source_entity_id">APP_IAPPT</data><data key="edge_relationship_type">writes_language_assistance_remark_to</data><data key="edge_target_entity_id">UI_ELAS_RMRK</data><data key="edge_operational_context">Non-English or sign-language preference generates an interpreter-assistance remark on eLAS RMRK.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL010" source="UI_SSI_ALIEN_STATUS" target="APP_MSSICS"><data key="edge_relationship_id">R89_REL010</data><data key="edge_source_entity_id">UI_SSI_ALIEN_STATUS</data><data key="edge_relationship_type">used_in_mssics_application_entry_for</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current SSI application policy identifies an Alien Status page for applications taken in MSSICS.</data><data key="edge_observed_as_of">2026-06-15</data><data key="edge_confidence">5</data><data key="edge_notes">Logical workflow relationship; exact UI implementation is not inferred.</data></edge><edge id="R89_REL011" source="UI_SSI_ALIEN_STATUS" target="APP_CCE"><data key="edge_relationship_id">R89_REL011</data><data key="edge_source_entity_id">UI_SSI_ALIEN_STATUS</data><data key="edge_relationship_type">used_in_cce_ssi_documentation_for</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Current LPR policy directs CCE SSI claims to annotate Alien Status page file-documentation notes.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes">Current policy terminology does not prove separate physical page instances.</data></edge><edge id="R89_REL012" source="UI_SSI_ALIEN_STATUS" target="DATA_SSI_US_ADMISSION_DATE"><data key="edge_relationship_id">R89_REL012</data><data key="edge_source_entity_id">UI_SSI_ALIEN_STATUS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_US_ADMISSION_DATE</data><data key="edge_operational_context">Archived SSI Alien Status page includes U.S. admission date used in lawful-presence evidence review.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL013" source="UI_SSI_ALIEN_STATUS" target="DATA_SSI_ALIEN_STATUS_CODE"><data key="edge_relationship_id">R89_REL013</data><data key="edge_source_entity_id">UI_SSI_ALIEN_STATUS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_ALIEN_STATUS_CODE</data><data key="edge_operational_context">Archived SSI Alien Status page includes the alien-status code.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL014" source="UI_SSI_ALIEN_STATUS" target="DATA_SSI_ALIEN_STATUS_VERIFIED"><data key="edge_relationship_id">R89_REL014</data><data key="edge_source_entity_id">UI_SSI_ALIEN_STATUS</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_SSI_ALIEN_STATUS_VERIFIED</data><data key="edge_operational_context">Archived SSI Alien Status page includes an alien-status-verified field.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL015" source="APP_SSI_CLAIMS_LOGICAL" target="SVC_SAVE"><data key="edge_relationship_id">R89_REL015</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">requires_verification_via</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">Current Title XVI policy requires SAVE verification for noncitizen initial claims, redeterminations, and status changes.</data><data key="edge_observed_as_of">2026-09-15</data><data key="edge_confidence">5</data><data key="edge_notes">Policy workflow; not an inferred direct application API.</data></edge><edge id="R89_REL016" source="PROC_CAP" target="EX_SDX"><data key="edge_relationship_id">R89_REL016</data><data key="edge_source_entity_id">PROC_CAP</data><data key="edge_relationship_type">uses_ssi_information_via</data><data key="edge_target_entity_id">EX_SDX</data><data key="edge_operational_context">Both CAP models use information already sent to States through the automated SDX to identify and enroll SSI recipients.</data><data key="edge_observed_as_of">2026-08-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL017" source="ORG_USDA_FNS" target="PROC_CAP"><data key="edge_relationship_id">R89_REL017</data><data key="edge_source_entity_id">ORG_USDA_FNS</data><data key="edge_relationship_type">participates_in</data><data key="edge_target_entity_id">PROC_CAP</data><data key="edge_operational_context">FNS is one of the government partners in CAP.</data><data key="edge_observed_as_of">2026-08-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL018" source="ORG_STATES" target="PROC_CAP"><data key="edge_relationship_id">R89_REL018</data><data key="edge_source_entity_id">ORG_STATES</data><data key="edge_relationship_type">participates_in</data><data key="edge_target_entity_id">PROC_CAP</data><data key="edge_operational_context">States are partners in CAP.</data><data key="edge_observed_as_of">2026-08-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL019" source="PROC_CAP" target="PROG_SNAP"><data key="edge_relationship_id">R89_REL019</data><data key="edge_source_entity_id">PROC_CAP</data><data key="edge_relationship_type">supports_enrollment_in</data><data key="edge_target_entity_id">PROG_SNAP</data><data key="edge_operational_context">CAP streamlines SNAP benefits for certain one-person households eligible for SSI.</data><data key="edge_observed_as_of">2026-08-04</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL020" source="APP_PUPS" target="PROC_PUPS_IP_RECOUP"><data key="edge_relationship_id">R89_REL020</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_PUPS_IP_RECOUP</data><data key="edge_operational_context">PUPS records, alerts, prisoner-status queries, and incentive-payment processing are reviewed during recoupment.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL021" source="PROC_PUPS_IP_RECOUP" target="FORM_SSA_L4020"><data key="edge_relationship_id">R89_REL021</data><data key="edge_source_entity_id">PROC_PUPS_IP_RECOUP</data><data key="edge_relationship_type">uses_notice</data><data key="edge_target_entity_id">FORM_SSA_L4020</data><data key="edge_operational_context">SSA uses SSA-L4020 to request return of an incorrectly paid incentive payment.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL022" source="APP_INFORM" target="FORM_SSA_L4020"><data key="edge_relationship_id">R89_REL022</data><data key="edge_source_entity_id">APP_INFORM</data><data key="edge_relationship_type">provides_template_for</data><data key="edge_target_entity_id">FORM_SSA_L4020</data><data key="edge_operational_context">Current POMS directs technicians to obtain SSA-L4020 from the inForm system.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL023" source="UI_IRCS_QPID" target="APP_IRCS"><data key="edge_relationship_id">R89_REL023</data><data key="edge_source_entity_id">UI_IRCS_QPID</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_IRCS</data><data key="edge_operational_context">QPID is identified as the IRCS Incentive Payment Identification Query screen.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL024" source="UI_IRCS_QPID" target="DATA_PUPS_INCENTIVE_PAYEE_ADDRESS"><data key="edge_relationship_id">R89_REL024</data><data key="edge_source_entity_id">UI_IRCS_QPID</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">DATA_PUPS_INCENTIVE_PAYEE_ADDRESS</data><data key="edge_operational_context">QPID Incentive Payment Data provides the facility incentive-payee name and mailing address used on SSA-L4020.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes">Institution address.</data></edge><edge id="R89_REL025" source="UI_PUPS_IPID" target="APP_PUPS"><data key="edge_relationship_id">R89_REL025</data><data key="edge_source_entity_id">UI_PUPS_IPID</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Current policy calls the Incentive Payment Identification Data screen a PUPS screen.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL026" source="UI_PUPS_IPID" target="DATA_PUPS_INCENTIVE_PAYEE_ADDRESS"><data key="edge_relationship_id">R89_REL026</data><data key="edge_source_entity_id">UI_PUPS_IPID</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_PUPS_INCENTIVE_PAYEE_ADDRESS</data><data key="edge_operational_context">Field Operations prisoner coordination can update IPID with a facility’s current incentive-payment address and contact information.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes">Staff-mediated update path.</data></edge><edge id="R89_REL027" source="DATA_PUPS_INCENTIVE_PAYEE_ADDRESS" target="FORM_SSA_L4020"><data key="edge_relationship_id">R89_REL027</data><data key="edge_source_entity_id">DATA_PUPS_INCENTIVE_PAYEE_ADDRESS</data><data key="edge_relationship_type">copied_to</data><data key="edge_target_entity_id">FORM_SSA_L4020</data><data key="edge_operational_context">Technicians copy the institutional incentive-payee address from QPID to the recoupment notice.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL028" source="ORG_PRISONS" target="DATA_PUPS_INCENTIVE_PAYEE_ADDRESS"><data key="edge_relationship_id">R89_REL028</data><data key="edge_source_entity_id">ORG_PRISONS</data><data key="edge_relationship_type">originates_or_confirms</data><data key="edge_target_entity_id">DATA_PUPS_INCENTIVE_PAYEE_ADDRESS</data><data key="edge_operational_context">Correctional or mental health institution contacts provide or confirm address/contact information used for prisoner incentive payments.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL029" source="ORG_USPS" target="DATA_PUPS_INCENTIVE_PAYEE_ADDRESS"><data key="edge_relationship_id">R89_REL029</data><data key="edge_source_entity_id">ORG_USPS</data><data key="edge_relationship_type">provides_candidate_forwarding_address_for</data><data key="edge_target_entity_id">DATA_PUPS_INCENTIVE_PAYEE_ADDRESS</data><data key="edge_operational_context">For undeliverable SSA-L4020 mail, USPS forwarding information or an SSA-L2001 response can supply a candidate current facility address.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes">The update to IPID is staff-mediated; USPS does not directly write PUPS.</data></edge><edge id="R89_REL030" source="FORM_SSA_L4020" target="REPO_L4020_SHAREPOINT"><data key="edge_relationship_id">R89_REL030</data><data key="edge_source_entity_id">FORM_SSA_L4020</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_L4020_SHAREPOINT</data><data key="edge_operational_context">The PUPS Systems Manager places completed SSA-L4020 copies on the view-only IP Recoup Forms SharePoint site.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL031" source="UI_PUPS_P2QY" target="APP_PUPS"><data key="edge_relationship_id">R89_REL031</data><data key="edge_source_entity_id">UI_PUPS_P2QY</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">P2QY is the PUPS Title II Prisoner Status Query used in incentive-payment review.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL032" source="UI_PUPS_T16QY" target="APP_PUPS"><data key="edge_relationship_id">R89_REL032</data><data key="edge_source_entity_id">UI_PUPS_T16QY</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Current POMS identifies the Title XVI Prisoner Status Query as T6QY in one section and P6QY in another.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">4</data><data key="edge_notes">Source naming conflict retained.</data></edge><edge id="R89_REL033" source="UI_PUPS_P2QY" target="DATA_PUPS_FACILITY_ID"><data key="edge_relationship_id">R89_REL033</data><data key="edge_source_entity_id">UI_PUPS_P2QY</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">DATA_PUPS_FACILITY_ID</data><data key="edge_operational_context">The Title II prisoner status query supplies the facility ID used on SSA-L4020.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL034" source="UI_PUPS_T16QY" target="DATA_PUPS_FACILITY_ID"><data key="edge_relationship_id">R89_REL034</data><data key="edge_source_entity_id">UI_PUPS_T16QY</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">DATA_PUPS_FACILITY_ID</data><data key="edge_operational_context">The Title XVI prisoner status query supplies the facility ID used on SSA-L4020.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">4</data><data key="edge_notes">Source uses T6QY/P6QY inconsistently.</data></edge><edge id="R89_REL035" source="FORM_SSA_L4020" target="DATA_PUPS_FACILITY_ID"><data key="edge_relationship_id">R89_REL035</data><data key="edge_source_entity_id">FORM_SSA_L4020</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">DATA_PUPS_FACILITY_ID</data><data key="edge_operational_context">SSA-L4020 includes the six-position facility ID.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL036" source="PROC_PUPS_IP_RECOUP" target="UI_PUPS_QIPD"><data key="edge_relationship_id">R89_REL036</data><data key="edge_source_entity_id">PROC_PUPS_IP_RECOUP</data><data key="edge_relationship_type">uses_screen</data><data key="edge_target_entity_id">UI_PUPS_QIPD</data><data key="edge_operational_context">POMS says institutional incentive-payment records in QIPD support inquiries about completed SSA-L4020 notices.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R89_REL037" source="PROC_PUPS_IP_RECOUP" target="UI_PUPS_QIPA"><data key="edge_relationship_id">R89_REL037</data><data key="edge_source_entity_id">PROC_PUPS_IP_RECOUP</data><data key="edge_relationship_type">uses_screen</data><data key="edge_target_entity_id">UI_PUPS_QIPA</data><data key="edge_operational_context">POMS says institutional incentive-payment records in QIPA support inquiries about completed SSA-L4020 notices.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R89_REL038" source="PROC_PUPS_IP_RECOUP" target="APP_DMT_DM_TRACKING"><data key="edge_relationship_id">R89_REL038</data><data key="edge_source_entity_id">PROC_PUPS_IP_RECOUP</data><data key="edge_relationship_type">tracked_in</data><data key="edge_target_entity_id">APP_DMT_DM_TRACKING</data><data key="edge_operational_context">The Administrative Debt Management Team records the institution in its DM system and tracks 30/60/95-day recovery actions.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">4</data><data key="edge_notes">Do not equate this generic DM-system label with DMS absent evidence.</data></edge><edge id="R89_REL039" source="FORM_SSA_L4020" target="APP_ORS"><data key="edge_relationship_id">R89_REL039</data><data key="edge_source_entity_id">FORM_SSA_L4020</data><data key="edge_relationship_type">uses_payment_notice_from</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">POMS says the original institutional incentive-payment notice in ORS supplies recoupment fill-in information.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL040" source="ORG_SSA_OCACT" target="DATA_OACT_SOLVENCY_PROVISIONS"><data key="edge_relationship_id">R89_REL040</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_SOLVENCY_PROVISIONS</data><data key="edge_operational_context">OACT maintains the public Long Range Solvency Provisions collection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL041" source="DATA_OACT_SOLVENCY_PROVISIONS" target="REPORT_TRUSTEES_2026"><data key="edge_relationship_id">R89_REL041</data><data key="edge_source_entity_id">DATA_OACT_SOLVENCY_PROVISIONS</data><data key="edge_relationship_type">uses_assumption_basis_from</data><data key="edge_target_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_operational_context">OACT states it is working to update the provision collection to a 2026 Trustees Report basis.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Current summary listing remains on a 2025 Trustees Report basis; transition is incomplete.</data></edge><edge id="R89_REL042" source="FORM_SSA1199_FAMILY" target="PROC_IDD"><data key="edge_relationship_id">R89_REL042</data><data key="edge_source_entity_id">FORM_SSA1199_FAMILY</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">SSA-1199 country forms are used to enroll qualifying Title II beneficiaries in International Direct Deposit.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL043" source="FORM_SSA1199_FAMILY" target="ORG_SSA_FBU"><data key="edge_relationship_id">R89_REL043</data><data key="edge_source_entity_id">FORM_SSA1199_FAMILY</data><data key="edge_relationship_type">submitted_to</data><data key="edge_target_entity_id">ORG_SSA_FBU</data><data key="edge_operational_context">Completed SSA-1199 country forms are mailed to the appropriate Federal Benefits Unit identified on the form.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL044" source="APP_VAMS" target="DATA_VAMS_VAN"><data key="edge_relationship_id">R89_REL044</data><data key="edge_source_entity_id">APP_VAMS</data><data key="edge_relationship_type">assigns</data><data key="edge_target_entity_id">DATA_VAMS_VAN</data><data key="edge_operational_context">Current catalog metadata says every account in VAMS is issued a unique Verification Account Number.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL045" source="APP_EVS" target="DATA_VAMS_VAN"><data key="edge_relationship_id">R89_REL045</data><data key="edge_source_entity_id">APP_EVS</data><data key="edge_relationship_type">uses_account_identifier</data><data key="edge_target_entity_id">DATA_VAMS_VAN</data><data key="edge_operational_context">EVS requests use Verification Account Numbers as account identifiers under the VAMS account-control model.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL046" source="PROJ_YTED" target="UI_CCE_ROC"><data key="edge_relationship_id">R89_REL046</data><data key="edge_source_entity_id">PROJ_YTED</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">UI_CCE_ROC</data><data key="edge_operational_context">Field technicians document YTED participation and start date in a CCE DROC.</data><data key="edge_observed_as_of">2026-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL047" source="PROJ_YTED" target="DATA_SSI_YTED_CG"><data key="edge_relationship_id">R89_REL047</data><data key="edge_source_entity_id">PROJ_YTED</data><data key="edge_relationship_type">coded_on</data><data key="edge_target_entity_id">DATA_SSI_YTED_CG</data><data key="edge_operational_context">Every YTED participant requires a YTED MMYY Case Characteristics code.</data><data key="edge_observed_as_of">2026-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R89_REL048" source="DATA_SSI_YTED_CG" target="SYS_SSR"><data key="edge_relationship_id">R89_REL048</data><data key="edge_source_entity_id">DATA_SSI_YTED_CG</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS directs staff to update the YTED Case Characteristics code on the SSR Special Message page.</data><data key="edge_observed_as_of">2026-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL001" source="APP_ESPF" target="APP_ELAS"><data key="edge_relationship_id">R90_REL001</data><data key="edge_source_entity_id">APP_ESPF</data><data key="edge_relationship_type">sends_protective_filing_requests_to</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Upon submission, eSPF information was sent to eLAS to create a protective filing record for further action.</data><data key="edge_observed_as_of">2024-11-21</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL002" source="APP_ESPF" target="WORK_ESPF_ONLPFL"><data key="edge_relationship_id">R90_REL002</data><data key="edge_source_entity_id">APP_ESPF</data><data key="edge_relationship_type">creates_work_control</data><data key="edge_target_entity_id">WORK_ESPF_ONLPFL</data><data key="edge_operational_context">All eSPF requests in eLAS were identified by Employee Name and Unit Code ONLPFL.</data><data key="edge_observed_as_of">2024-11-21</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL003" source="WORK_ESPF_ONLPFL" target="APP_ELAS"><data key="edge_relationship_id">R90_REL003</data><data key="edge_source_entity_id">WORK_ESPF_ONLPFL</data><data key="edge_relationship_type">identified_in</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">ONLPFL identifies the historical eSPF request in the eLAS listing/unit-code context.</data><data key="edge_observed_as_of">2024-11-21</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL004" source="WORK_ESPF_ONLPFL" target="APP_WAC"><data key="edge_relationship_id">R90_REL004</data><data key="edge_source_entity_id">WORK_ESPF_ONLPFL</data><data key="edge_relationship_type">displayed_in</data><data key="edge_target_entity_id">APP_WAC</data><data key="edge_operational_context">WAC imported eLAS workloads and displayed eSPF requests under unit ONLPFL; from Dec. 2023 it also displayed first- and third-party eSPF submissions.</data><data key="edge_observed_as_of">2024-11-21</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL005" source="WORK_ESPF_ONLPFL" target="APP_VIPR"><data key="edge_relationship_id">R90_REL005</data><data key="edge_source_entity_id">WORK_ESPF_ONLPFL</data><data key="edge_relationship_type">displayed_on</data><data key="edge_target_entity_id">APP_VIPR</data><data key="edge_operational_context">An appointment originated from eSPF when ONLPFL appeared on the VIPr Appointment Board or eLAS unit code.</data><data key="edge_observed_as_of">2024-11-21</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL006" source="FUNC_ELAS_VERIFY_PI" target="APP_PERSON_INFO"><data key="edge_relationship_id">R90_REL006</data><data key="edge_source_entity_id">FUNC_ELAS_VERIFY_PI</data><data key="edge_relationship_type">stores_verified_espf_person_data_in</data><data key="edge_target_entity_id">APP_PERSON_INFO</data><data key="edge_operational_context">Historical eSPF workflow: after staff verified identity, Verify PI propagated eSPF information for review; Save stored the verified information to PI and receipted the UNVER issue.</data><data key="edge_observed_as_of">2024-11-21</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL007" source="APP_ELAS" target="APP_VIPR"><data key="edge_relationship_id">R90_REL007</data><data key="edge_source_entity_id">APP_ELAS</data><data key="edge_relationship_type">propagates_verified_espf_contact_data_to</data><data key="edge_target_entity_id">APP_VIPR</data><data key="edge_operational_context">Historical eSPF workflow: all verified eLAS address, telephone number and language-preference information propagated to VIPr.</data><data key="edge_observed_as_of">2024-11-21</data><data key="edge_confidence">5</data><data key="edge_notes">This does not establish automatic updating of MBR, SSR or Numident.</data></edge><edge id="R90_REL008" source="APP_ESS" target="APP_VIPR"><data key="edge_relationship_id">R90_REL008</data><data key="edge_source_entity_id">APP_ESS</data><data key="edge_relationship_type">appointments_viewable_in</data><data key="edge_target_entity_id">APP_VIPR</data><data key="edge_operational_context">2025 appointment-focused-service instructions say technicians and managers may find existing ESS appointments in VIPr, ESS or WAC.</data><data key="edge_observed_as_of">2025-08-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL009" source="APP_VIPR" target="DB_VIPR_MI"><data key="edge_relationship_id">R90_REL009</data><data key="edge_source_entity_id">APP_VIPR</data><data key="edge_relationship_type">has_management_information_asset</data><data key="edge_target_entity_id">DB_VIPR_MI</data><data key="edge_operational_context">SSA separately catalogs VIPr Management Information containing detailed visitor/customer-relationship information related to VIPR and CHIP.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL010" source="APP_VIPR" target="APP_ESS"><data key="edge_relationship_id">R90_REL010</data><data key="edge_source_entity_id">APP_VIPR</data><data key="edge_relationship_type">supports_manual_same_day_and_future_scheduling</data><data key="edge_target_entity_id">APP_ESS</data><data key="edge_operational_context">When no ESS appointments are available, field-office staff may use VIPr Add Appointment for same-day or future appointments in their own office.</data><data key="edge_observed_as_of">2025-08-05</data><data key="edge_confidence">5</data><data key="edge_notes">This relationship reflects scheduling fallback/coexistence, not proof that VIPr writes to the ESS data store.</data></edge><edge id="R90_REL011" source="APP_ECO" target="PROC_ECO_UNDELIVERABLE"><data key="edge_relationship_id">R90_REL011</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">has_process</data><data key="edge_target_entity_id">PROC_ECO_UNDELIVERABLE</data><data key="edge_operational_context">Current Title II and Title XVI policy documents a specialized returned-undeliverable External Collections notice process within ECO.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL012" source="PROC_ECO_UNDELIVERABLE" target="UI_ECO_TRUN"><data key="edge_relationship_id">R90_REL012</data><data key="edge_source_entity_id">PROC_ECO_UNDELIVERABLE</data><data key="edge_relationship_type">uses_primary_screen</data><data key="edge_target_entity_id">UI_ECO_TRUN</data><data key="edge_operational_context">PC7 ODO mailroom staff normally scan barcodes on undeliverable ECO notices using TRUN.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL013" source="PROC_ECO_UNDELIVERABLE" target="UI_ECO_TRRN"><data key="edge_relationship_id">R90_REL013</data><data key="edge_source_entity_id">PROC_ECO_UNDELIVERABLE</data><data key="edge_relationship_type">uses_fallback_screen</data><data key="edge_target_entity_id">UI_ECO_TRRN</data><data key="edge_operational_context">TRRN is used when barcode scanning is not possible or notices are returned to another location.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL014" source="UI_ECO_TRUN" target="DATA_ECO_MASTER_RECORD"><data key="edge_relationship_id">R90_REL014</data><data key="edge_source_entity_id">UI_ECO_TRUN</data><data key="edge_relationship_type">posts_returned_notice_to</data><data key="edge_target_entity_id">DATA_ECO_MASTER_RECORD</data><data key="edge_operational_context">Barcode-scanned undeliverable ECO pre-offset notices are recorded on the ECO Master.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL015" source="UI_ECO_TRRN" target="DATA_ECO_MASTER_RECORD"><data key="edge_relationship_id">R90_REL015</data><data key="edge_source_entity_id">UI_ECO_TRRN</data><data key="edge_relationship_type">posts_returned_notice_to</data><data key="edge_target_entity_id">DATA_ECO_MASTER_RECORD</data><data key="edge_operational_context">Manually input undeliverable ECO pre-offset notices are recorded on the ECO Master.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL016" source="APP_ECO" target="DATA_ECO_MASTER_RECORD"><data key="edge_relationship_id">R90_REL016</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">uses_record_structure</data><data key="edge_target_entity_id">DATA_ECO_MASTER_RECORD</data><data key="edge_operational_context">Current public POMS repeatedly describes ECO Master / ECO Master File information used to control external-collection status and returned-mail handling.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes">Exact physical identity with DB_ECO_DATA remains unresolved.</data></edge><edge id="R90_REL017" source="APP_ECO" target="QRY_ECO_MASTER"><data key="edge_relationship_id">R90_REL017</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">provides_query</data><data key="edge_target_entity_id">QRY_ECO_MASTER</data><data key="edge_operational_context">Current POMS directs staff to use the ECO Master Query from the External Collection Operation menu.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL018" source="QRY_ECO_MASTER" target="DATA_ECO_MASTER_RECORD"><data key="edge_relationship_id">R90_REL018</data><data key="edge_source_entity_id">QRY_ECO_MASTER</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DATA_ECO_MASTER_RECORD</data><data key="edge_operational_context">ECO Master Query is used to review AWG status, employer information and other ECO Master data.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL019" source="PROC_ECO_UNDELIVERABLE" target="SVC_AVC"><data key="edge_relationship_id">R90_REL019</data><data key="edge_source_entity_id">PROC_ECO_UNDELIVERABLE</data><data key="edge_relationship_type">triggers_address_reverification_from</data><data key="edge_target_entity_id">SVC_AVC</data><data key="edge_operational_context">After an undeliverable pre-offset notice is recorded, ECO requests another debtor address from the Address Verification Contractor.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL020" source="PROC_ECO_UNDELIVERABLE" target="SVC_TOP"><data key="edge_relationship_id">R90_REL020</data><data key="edge_source_entity_id">PROC_ECO_UNDELIVERABLE</data><data key="edge_relationship_type">can_remove_existing_referral_from</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">If a debt was already referred, undeliverable pre-offset processing sends an update to Treasury to remove the debt from TOP.</data><data key="edge_observed_as_of">2026-10-05</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL021" source="PROC_AWG" target="WORK_ECO_AWG_RETURN_TX"><data key="edge_relationship_id">R90_REL021</data><data key="edge_source_entity_id">PROC_AWG</data><data key="edge_relationship_type">uses_returned_mail_transactions</data><data key="edge_target_entity_id">WORK_ECO_AWG_RETURN_TX</data><data key="edge_operational_context">Central scanning of returned AWG employer mail posts transaction 7001 for the employer package and 7005 for specified garnishment notices.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL022" source="WORK_ECO_AWG_RETURN_TX" target="APP_ECO"><data key="edge_relationship_id">R90_REL022</data><data key="edge_source_entity_id">WORK_ECO_AWG_RETURN_TX</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">The 7001/7005 undeliverable-employer-mail transactions are posted to ECO for follow-up processing.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL023" source="APP_ECO" target="DATA_ECO_MASTER_RECORD"><data key="edge_relationship_id">R90_REL023</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">checks_employer_address_in</data><data key="edge_target_entity_id">DATA_ECO_MASTER_RECORD</data><data key="edge_operational_context">For returned AWG mail, ECO checks the ECO Master File for a more recent employer address.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL024" source="APP_ECO" target="DB_EIF"><data key="edge_relationship_id">R90_REL024</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">checks_employer_address_in</data><data key="edge_target_entity_id">DB_EIF</data><data key="edge_operational_context">For returned AWG mail, ECO also checks the Employer Identification File for a more recent employer address.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL025" source="APP_ECO" target="PROC_AWG"><data key="edge_relationship_id">R90_REL025</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">automatically_resends_awg_mail_for</data><data key="edge_target_entity_id">PROC_AWG</data><data key="edge_operational_context">When ECO finds a newer employer address in ECO Master or EIF, it automatically resends the applicable AWG mail to the updated address.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL026" source="APP_ECO" target="ALERT_ECO_AWG_UNDELIV"><data key="edge_relationship_id">R90_REL026</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">ALERT_ECO_AWG_UNDELIV</data><data key="edge_operational_context">If returned AWG mail cannot be resolved automatically, ECO generates documented undeliverable AWG alerts.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL027" source="ALERT_ECO_AWG_UNDELIV" target="APP_PCACS"><data key="edge_relationship_id">R90_REL027</data><data key="edge_source_entity_id">ALERT_ECO_AWG_UNDELIV</data><data key="edge_relationship_type">controlled_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">The documented ECO-AWG undeliverable alerts are sent to the Debt Management Section through PCACS.</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL028" source="PROC_DQR_QUALITY_REVIEW" target="FORM_SSA93"><data key="edge_relationship_id">R90_REL028</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">FORM_SSA93</data><data key="edge_operational_context">SSI quality review uses the SSA-93 Quality Review Feedback Report to convey findings and required field-office action.</data><data key="edge_observed_as_of">2025-08-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL029" source="PROC_DQR_QUALITY_REVIEW" target="APP_SSA93_QR_WEB"><data key="edge_relationship_id">R90_REL029</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">sends_case_data_to</data><data key="edge_target_entity_id">APP_SSA93_QR_WEB</data><data key="edge_operational_context">Quality Review sends interim/final SSA-93 case data to the SSA-93 Quality Review website for tracking and field-office response.</data><data key="edge_observed_as_of">2025-08-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL030" source="APP_SSA93_QR_WEB" target="FORM_SSA93"><data key="edge_relationship_id">R90_REL030</data><data key="edge_source_entity_id">APP_SSA93_QR_WEB</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">FORM_SSA93</data><data key="edge_operational_context">Current policy says a copy of the SSA-93 is available from the SSA-93 Quality Review website.</data><data key="edge_observed_as_of">2025-08-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL031" source="PROC_DQR_QUALITY_REVIEW" target="REPO_NDRED"><data key="edge_relationship_id">R90_REL031</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">stores_supporting_evidence_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Quality Review uses Evidence Portal to scan supporting evidence into NDRed.</data><data key="edge_observed_as_of">2025-08-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL032" source="DATA_QR_REVDOC93" target="REPO_NDRED"><data key="edge_relationship_id">R90_REL032</data><data key="edge_source_entity_id">DATA_QR_REVDOC93</data><data key="edge_relationship_type">labels_documents_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">QR names supporting documents scanned to NDRed REVDOC 93 to distinguish them from field-office documents.</data><data key="edge_observed_as_of">2025-08-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL033" source="APP_SSA93_QR_WEB" target="PROC_DQR_QUALITY_REVIEW"><data key="edge_relationship_id">R90_REL033</data><data key="edge_source_entity_id">APP_SSA93_QR_WEB</data><data key="edge_relationship_type">notifies_completion_to</data><data key="edge_target_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_operational_context">After the field office records completed action, the website sends an email notification to Quality Review and marks the case complete.</data><data key="edge_observed_as_of">2025-08-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL034" source="ORG_SSA_OAG" target="CONTRACT_KIOWARE_2026"><data key="edge_relationship_id">R90_REL034</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">awarded</data><data key="edge_target_entity_id">CONTRACT_KIOWARE_2026</data><data key="edge_operational_context">Federal-award mirror data identifies SSA Office of Acquisition and Grants as the awarding office for purchase order 28321326P00050062.</data><data key="edge_observed_as_of">2026-09-09</data><data key="edge_confidence">4</data><data key="edge_notes">Primary award records were not machine-resolved during this run; secondary federal-award mirrors were used and confidence reduced.</data></edge><edge id="R90_REL035" source="ORG_DYNATOUCH" target="CONTRACT_KIOWARE_2026"><data key="edge_relationship_id">R90_REL035</data><data key="edge_source_entity_id">ORG_DYNATOUCH</data><data key="edge_relationship_type">prime_recipient_of</data><data key="edge_target_entity_id">CONTRACT_KIOWARE_2026</data><data key="edge_operational_context">Dynatouch Corporation is identified as the recipient of the SSA KioWare maintenance purchase order.</data><data key="edge_observed_as_of">2026-09-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R90_REL036" source="CONTRACT_KIOWARE_2026" target="SW_KIOWARE"><data key="edge_relationship_id">R90_REL036</data><data key="edge_source_entity_id">CONTRACT_KIOWARE_2026</data><data key="edge_relationship_type">procures_maintenance_for</data><data key="edge_target_entity_id">SW_KIOWARE</data><data key="edge_operational_context">Purchase order 28321326P00050062 is for renewal/maintenance of KioWare.</data><data key="edge_observed_as_of">2026-09-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R90_REL037" source="CONTRACT_KIOWARE_2026" target="APP_VIPR"><data key="edge_relationship_id">R90_REL037</data><data key="edge_source_entity_id">CONTRACT_KIOWARE_2026</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_VIPR</data><data key="edge_operational_context">The procurement description states KioWare supports the Visitor Intake Process Rewrite kiosk project used by visitors at SSA field offices.</data><data key="edge_observed_as_of">2026-09-09</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R90_REL038" source="SW_KIOWARE" target="APP_VIPR"><data key="edge_relationship_id">R90_REL038</data><data key="edge_source_entity_id">SW_KIOWARE</data><data key="edge_relationship_type">supports_kiosk_environment_for</data><data key="edge_target_entity_id">APP_VIPR</data><data key="edge_operational_context">Procurement records describe KioWare as a secure kiosk shell with centralized management/monitoring supporting VIPr kiosks.</data><data key="edge_observed_as_of">2026-09-09</data><data key="edge_confidence">4</data><data key="edge_notes">Product role is established by procurement evidence, not vendor marketing.</data></edge><edge id="R90_REL039" source="REPORT_STAT_SUPP_2026" target="DATA_STAT_SUPP_5L_2026"><data key="edge_relationship_id">R90_REL039</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">contains_section</data><data key="edge_target_entity_id">DATA_STAT_SUPP_5L_2026</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement contains section 5.L on OASDI beneficiaries with representative payees.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL040" source="SYS_MBR" target="DATA_STAT_SUPP_5L_2026"><data key="edge_relationship_id">R90_REL040</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for_publication</data><data key="edge_target_entity_id">DATA_STAT_SUPP_5L_2026</data><data key="edge_operational_context">Section 5.L identifies the Master Beneficiary Record as its 100-percent data source.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL041" source="REPORT_STAT_SUPP_2026" target="DATA_STAT_SUPP_7E_2026"><data key="edge_relationship_id">R90_REL041</data><data key="edge_source_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_relationship_type">contains_section</data><data key="edge_target_entity_id">DATA_STAT_SUPP_7E_2026</data><data key="edge_operational_context">The 2026 Annual Statistical Supplement contains section 7.E on SSI recipient characteristics.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL042" source="SYS_SSR" target="DATA_STAT_SUPP_7E_2026"><data key="edge_relationship_id">R90_REL042</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for_publication</data><data key="edge_target_entity_id">DATA_STAT_SUPP_7E_2026</data><data key="edge_operational_context">Section 7.E identifies the Supplemental Security Record as its 100-percent data source.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL043" source="ORG_SSA_OCACT" target="DATA_OACT_PRIMARY_BEN_AGE_SEX_2026"><data key="edge_relationship_id">R90_REL043</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_PRIMARY_BEN_AGE_SEX_2026</data><data key="edge_operational_context">OACT publishes the June 30, 2026 primary-beneficiary age/sex product.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL044" source="ORG_SSA_OCACT" target="DATA_OACT_TR2026_COLA_AWI_EST"><data key="edge_relationship_id">R90_REL044</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_TR2026_COLA_AWI_EST</data><data key="edge_operational_context">OACT publishes the future COLA and AWI estimate table under the 2026 Trustees Report assumptions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R90_REL045" source="REPORT_TRUSTEES_2026" target="DATA_OACT_TR2026_COLA_AWI_EST"><data key="edge_relationship_id">R90_REL045</data><data key="edge_source_entity_id">REPORT_TRUSTEES_2026</data><data key="edge_relationship_type">provides_intermediate_assumption_basis_for</data><data key="edge_target_entity_id">DATA_OACT_TR2026_COLA_AWI_EST</data><data key="edge_operational_context">The COLA and AWI estimates are explicitly derived from the intermediate assumptions in the 2026 Trustees Report.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL001" source="FORM_SSA781" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R91_REL001</data><data key="edge_source_entity_id">FORM_SSA781</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current Forms catalog Submit Online link resolves to shared Upload Documents route target=781.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL002" source="FORM_SSA2490" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R91_REL002</data><data key="edge_source_entity_id">FORM_SSA2490</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">Current Forms catalog Submit Online link resolves to shared Upload Documents route target=2490.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL003" source="FORM_SSA711" target="FORM_SS5"><data key="edge_relationship_id">R91_REL003</data><data key="edge_source_entity_id">FORM_SSA711</data><data key="edge_relationship_type">requests_record_associated_with</data><data key="edge_target_entity_id">FORM_SS5</data><data key="edge_operational_context">SSA recommends SSA-711 to request a deceased person’s SS-5; form is not mandatory.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL004" source="FORM_SSA711" target="SYS_NUMIDENT"><data key="edge_relationship_id">R91_REL004</data><data key="edge_source_entity_id">FORM_SSA711</data><data key="edge_relationship_type">requests_record_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA FOIA page prices and supports deceased-person Numident record requests in the same SSA-711/PAL record-access workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL005" source="FORM_SSA711" target="APP_FOIAXPRESS_PAL"><data key="edge_relationship_id">R91_REL005</data><data key="edge_source_entity_id">FORM_SSA711</data><data key="edge_relationship_type">alternative_submission_channel_to</data><data key="edge_target_entity_id">APP_FOIAXPRESS_PAL</data><data key="edge_operational_context">SSA allows online PAL submission or mailed SSA-711 for deceased-person record requests.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL006" source="FORM_SSA714" target="FORM_SSA711"><data key="edge_relationship_id">R91_REL006</data><data key="edge_source_entity_id">FORM_SSA714</data><data key="edge_relationship_type">supports_payment_for</data><data key="edge_target_entity_id">FORM_SSA711</data><data key="edge_operational_context">SSA directs requesters paying by credit card with mailed record requests to use SSA-714.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL007" source="EX_VA_VAPT" target="ORG_VA"><data key="edge_relationship_id">R91_REL007</data><data key="edge_source_entity_id">EX_VA_VAPT</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_VA</data><data key="edge_operational_context">VA identifies VAPT compensation recipients and provides SSA weekly information via automated data exchange.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL008" source="EX_VA_VAPT" target="SYS_NUMIDENT"><data key="edge_relationship_id">R91_REL008</data><data key="edge_source_entity_id">EX_VA_VAPT</data><data key="edge_relationship_type">verifies_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA verifies VA-supplied SSN, name, date of birth, sex and related identity data against Numident.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL009" source="EX_VA_VAPT" target="DATA_PERSON_VAPT_SEGMENT"><data key="edge_relationship_id">R91_REL009</data><data key="edge_source_entity_id">EX_VA_VAPT</data><data key="edge_relationship_type">stores_verified_identifier_in</data><data key="edge_target_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_operational_context">SSA stores only the SSN of verified VAPT disability-compensation recipients in PERSON/ICDB.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL010" source="DATA_PERSON_VAPT_SEGMENT" target="SYS_ICDB"><data key="edge_relationship_id">R91_REL010</data><data key="edge_source_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_relationship_type">is_component_of</data><data key="edge_target_entity_id">SYS_ICDB</data><data key="edge_operational_context">POMS calls ICDB also known as PERSON and identifies a PERSON VAPT segment in the workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL011" source="DATA_PERSON_VAPT_SEGMENT" target="DB_PERSON_STORE"><data key="edge_relationship_id">R91_REL011</data><data key="edge_source_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_relationship_type">is_person_attribute_structure_in</data><data key="edge_target_entity_id">DB_PERSON_STORE</data><data key="edge_operational_context">Current VAPT POMS uses PERSON nomenclature for the person-centric store; exact physical equivalence of DB_PERSON_STORE, PI/PERSON and ICDB remains unresolved.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R91_REL012" source="DATA_PERSON_VAPT_SEGMENT" target="WORK_ELAS_VAPT_ALERT"><data key="edge_relationship_id">R91_REL012</data><data key="edge_source_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">WORK_ELAS_VAPT_ALERT</data><data key="edge_operational_context">A claimant match can cause the eLAS time-sensitive VAPT scheduling alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL013" source="WORK_ELAS_VAPT_ALERT" target="APP_ELAS"><data key="edge_relationship_id">R91_REL013</data><data key="edge_source_entity_id">WORK_ELAS_VAPT_ALERT</data><data key="edge_relationship_type">surfaced_in</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">eLAS generates the VAPT time-sensitive case alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL014" source="DATA_PERSON_VAPT_SEGMENT" target="DATA_CSRQ_VAPT_ALERT"><data key="edge_relationship_id">R91_REL014</data><data key="edge_source_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">DATA_CSRQ_VAPT_ALERT</data><data key="edge_operational_context">A matched VAPT claimant can receive the customer-service expedited-procedures alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL015" source="DATA_CSRQ_VAPT_ALERT" target="APP_CSRQ"><data key="edge_relationship_id">R91_REL015</data><data key="edge_source_entity_id">DATA_CSRQ_VAPT_ALERT</data><data key="edge_relationship_type">generated_by</data><data key="edge_target_entity_id">APP_CSRQ</data><data key="edge_operational_context">Current POMS names Customer Service Record Query as the source of the VAPT expedited-procedures alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL016" source="DATA_CSRQ_VAPT_ALERT" target="APP_VIPR"><data key="edge_relationship_id">R91_REL016</data><data key="edge_source_entity_id">DATA_CSRQ_VAPT_ALERT</data><data key="edge_relationship_type">surfaced_in</data><data key="edge_target_entity_id">APP_VIPR</data><data key="edge_operational_context">CSRQ/CSQR VAPT alert appears in VIPr.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL017" source="DATA_CSRQ_VAPT_ALERT" target="APP_CICS_CUSTOMER_INFO"><data key="edge_relationship_id">R91_REL017</data><data key="edge_source_entity_id">DATA_CSRQ_VAPT_ALERT</data><data key="edge_relationship_type">surfaced_in</data><data key="edge_target_entity_id">APP_CICS_CUSTOMER_INFO</data><data key="edge_operational_context">CSRQ/CSQR VAPT alert appears in the Customer Information Control System.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL018" source="DATA_PERSON_VAPT_SEGMENT" target="WORK_MCS_VAPT_ISSUE"><data key="edge_relationship_id">R91_REL018</data><data key="edge_source_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">WORK_MCS_VAPT_ISSUE</data><data key="edge_operational_context">Matched VAPT status causes MCS ISSUE 100% PT and a DW01 remark.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL019" source="WORK_MCS_VAPT_ISSUE" target="APP_MCS"><data key="edge_relationship_id">R91_REL019</data><data key="edge_source_entity_id">WORK_MCS_VAPT_ISSUE</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">MCS adds the VAPT issue and DW01 remark.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL020" source="DATA_PERSON_VAPT_SEGMENT" target="FLAG_EDCS_VAPT38"><data key="edge_relationship_id">R91_REL020</data><data key="edge_source_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">FLAG_EDCS_VAPT38</data><data key="edge_operational_context">During case creation, an SSN present in PERSON VAPT causes EDCS to automatically attach the VAPT flag.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL021" source="FLAG_EDCS_VAPT38" target="APP_EDCS"><data key="edge_relationship_id">R91_REL021</data><data key="edge_source_entity_id">FLAG_EDCS_VAPT38</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS Flag #38 marks VAPT disability cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL022" source="DATA_PERSON_VAPT_SEGMENT" target="DATA_CPMS_VPAT"><data key="edge_relationship_id">R91_REL022</data><data key="edge_source_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">DATA_CPMS_VPAT</data><data key="edge_operational_context">POMS describes a CPMS VPAT case characteristic; relationship is time-scoped because CPMS is retired.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Current POMS retains historical CPMS reference; do not treat as proof of current production CPMS.</data></edge><edge id="R91_REL023" source="DATA_CPMS_VPAT" target="APP_CPMS"><data key="edge_relationship_id">R91_REL023</data><data key="edge_source_entity_id">DATA_CPMS_VPAT</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">CPMS held the VPAT characteristic before its documented retirement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Historical parent application.</data></edge><edge id="R91_REL024" source="DATA_PERSON_VAPT_SEGMENT" target="DATA_ARPS_VPAT"><data key="edge_relationship_id">R91_REL024</data><data key="edge_source_entity_id">DATA_PERSON_VAPT_SEGMENT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">DATA_ARPS_VPAT</data><data key="edge_operational_context">Matched VAPT status causes ARPS to add VPAT case characteristic.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL025" source="DATA_ARPS_VPAT" target="APP_ARPS"><data key="edge_relationship_id">R91_REL025</data><data key="edge_source_entity_id">DATA_ARPS_VPAT</data><data key="edge_relationship_type">maintained_in</data><data key="edge_target_entity_id">APP_ARPS</data><data key="edge_operational_context">ARPS holds VAPT VPAT case characteristic.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL026" source="PROC_VAPT_PRIORITY" target="EX_VA_VAPT"><data key="edge_relationship_id">R91_REL026</data><data key="edge_source_entity_id">PROC_VAPT_PRIORITY</data><data key="edge_relationship_type">uses_verification_from</data><data key="edge_target_entity_id">EX_VA_VAPT</data><data key="edge_operational_context">DDS policy says the SSA/VA exchange is sufficient 100% VAPT verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL027" source="PROC_VAPT_PRIORITY" target="FLAG_EDCS_VAPT38"><data key="edge_relationship_id">R91_REL027</data><data key="edge_source_entity_id">PROC_VAPT_PRIORITY</data><data key="edge_relationship_type">uses_case_flag</data><data key="edge_target_entity_id">FLAG_EDCS_VAPT38</data><data key="edge_operational_context">VAPT cases are flagged and given priority through case development and adjudication.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL028" source="DATA_ENUM_ACCURACY" target="EX_EAB"><data key="edge_relationship_id">R91_REL028</data><data key="edge_source_entity_id">DATA_ENUM_ACCURACY</data><data key="edge_relationship_type">measures</data><data key="edge_target_entity_id">EX_EAB</data><data key="edge_operational_context">Open Data description says enumeration accuracy review covers Enumeration at Birth actions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL029" source="DATA_ENUM_ACCURACY" target="EX_EAE"><data key="edge_relationship_id">R91_REL029</data><data key="edge_source_entity_id">DATA_ENUM_ACCURACY</data><data key="edge_relationship_type">measures</data><data key="edge_target_entity_id">EX_EAE</data><data key="edge_operational_context">Open Data description says enumeration accuracy review covers Enumeration at Entry actions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL030" source="DATA_ENUM_ACCURACY" target="APP_SSNAP"><data key="edge_relationship_id">R91_REL030</data><data key="edge_source_entity_id">DATA_ENUM_ACCURACY</data><data key="edge_relationship_type">measures</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Open Data description includes in-person/local-office and card-center enumeration actions; mapped to the established SSNAP enumeration gateway without inferring historical backend details.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="R91_REL031" source="DATA_STAT_SUPP_6A_2026" target="SYS_MBR"><data key="edge_relationship_id">R91_REL031</data><data key="edge_source_entity_id">DATA_STAT_SUPP_6A_2026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Published section explicitly identifies Master Beneficiary Record as its source.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL032" source="DATA_STAT_SUPP_6A_2026" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R91_REL032</data><data key="edge_source_entity_id">DATA_STAT_SUPP_6A_2026</data><data key="edge_relationship_type">part_of_publication</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Section is part of the 2026 Annual Statistical Supplement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL033" source="DATA_STAT_SUPP_6B_2026" target="SYS_MBR"><data key="edge_relationship_id">R91_REL033</data><data key="edge_source_entity_id">DATA_STAT_SUPP_6B_2026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Published section explicitly identifies Master Beneficiary Record as its source.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL034" source="DATA_STAT_SUPP_6B_2026" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R91_REL034</data><data key="edge_source_entity_id">DATA_STAT_SUPP_6B_2026</data><data key="edge_relationship_type">part_of_publication</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Section is part of the 2026 Annual Statistical Supplement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL035" source="DATA_STAT_SUPP_6C_2026" target="SYS_MBR"><data key="edge_relationship_id">R91_REL035</data><data key="edge_source_entity_id">DATA_STAT_SUPP_6C_2026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Published section explicitly identifies Master Beneficiary Record as its source.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL036" source="DATA_STAT_SUPP_6C_2026" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R91_REL036</data><data key="edge_source_entity_id">DATA_STAT_SUPP_6C_2026</data><data key="edge_relationship_type">part_of_publication</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Section is part of the 2026 Annual Statistical Supplement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL037" source="DATA_STAT_SUPP_6D_2026" target="SYS_MBR"><data key="edge_relationship_id">R91_REL037</data><data key="edge_source_entity_id">DATA_STAT_SUPP_6D_2026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Published section explicitly identifies Master Beneficiary Record as its source.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL038" source="DATA_STAT_SUPP_6D_2026" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R91_REL038</data><data key="edge_source_entity_id">DATA_STAT_SUPP_6D_2026</data><data key="edge_relationship_type">part_of_publication</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Section is part of the 2026 Annual Statistical Supplement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL039" source="DATA_STAT_SUPP_7A_2026" target="SYS_SSR"><data key="edge_relationship_id">R91_REL039</data><data key="edge_source_entity_id">DATA_STAT_SUPP_7A_2026</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Published section explicitly identifies Supplemental Security Record as its source.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R91_REL040" source="DATA_STAT_SUPP_7A_2026" target="REPORT_STAT_SUPP_2026"><data key="edge_relationship_id">R91_REL040</data><data key="edge_source_entity_id">DATA_STAT_SUPP_7A_2026</data><data key="edge_relationship_type">part_of_publication</data><data key="edge_target_entity_id">REPORT_STAT_SUPP_2026</data><data key="edge_operational_context">Section is part of the 2026 Annual Statistical Supplement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL001" source="SVC_TREASURY_LOCKBOX" target="DB_TREASURY_CIR"><data key="edge_relationship_id">R92_REL001</data><data key="edge_source_entity_id">SVC_TREASURY_LOCKBOX</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DB_TREASURY_CIR</data><data key="edge_operational_context">SSA uses Treasury CIR to view/download settled transaction information for programmatic remittances processed through Treasury collection systems.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL002" source="ORG_US_BANK" target="DATA_LOCKBOX_IRN"><data key="edge_relationship_id">R92_REL002</data><data key="edge_source_entity_id">ORG_US_BANK</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_LOCKBOX_IRN</data><data key="edge_operational_context">U.S. Bank generates an Individual Reference Number for lockbox remittances in the daily file.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL003" source="DATA_LOCKBOX_IRN" target="DB_TREASURY_CIR"><data key="edge_relationship_id">R92_REL003</data><data key="edge_source_entity_id">DATA_LOCKBOX_IRN</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">DB_TREASURY_CIR</data><data key="edge_operational_context">The lockbox IRN is sent to Treasury CIR as the unique remittance reference.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL004" source="DATA_LOCKBOX_IRN" target="UI_DMS_REQD"><data key="edge_relationship_id">R92_REL004</data><data key="edge_source_entity_id">DATA_LOCKBOX_IRN</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">UI_DMS_REQD</data><data key="edge_operational_context">The LCK-prefixed final eight digits of the IRN appear in the Receipt Number field of the DMS REQD screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL005" source="UI_DMS_REQD" target="APP_DMS"><data key="edge_relationship_id">R92_REL005</data><data key="edge_source_entity_id">UI_DMS_REQD</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">REQD is a Debt Management System screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL006" source="DB_TSMI" target="APP_VOIP_STATION_MANAGER"><data key="edge_relationship_id">R92_REL006</data><data key="edge_source_entity_id">DB_TSMI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_VOIP_STATION_MANAGER</data><data key="edge_operational_context">TSMI provides configuration, management, maintenance procedures, management information, and voice-message reporting for VoIP Station Manager.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">4</data><data key="edge_notes">Evidence is a catalog record last updated in 2018; current production status is unresolved.</data></edge><edge id="R92_REL007" source="PROC_PDAS" target="ORG_USPS"><data key="edge_relationship_id">R92_REL007</data><data key="edge_source_entity_id">PROC_PDAS</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">PDAS coordinators exchange missing-check information with designated USPS representatives until checks are located or classified.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL008" source="PROC_CO_MASS_LOSS_REPLACEMENT" target="APP_SSALERTS"><data key="edge_relationship_id">R92_REL008</data><data key="edge_source_entity_id">PROC_CO_MASS_LOSS_REPLACEMENT</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">APP_SSALERTS</data><data key="edge_operational_context">Mass-loss information and central-office replacement instructions are posted on SSAlerts for operational offices.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL009" source="APP_SSALERTS" target="APP_COMMUNICATIONS_CENTRAL"><data key="edge_relationship_id">R92_REL009</data><data key="edge_source_entity_id">APP_SSALERTS</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_COMMUNICATIONS_CENTRAL</data><data key="edge_operational_context">Current POMS says specific mass-loss information is posted on SSAlerts via Communications Central.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship captures documented publication path without inferring hosting topology.</data></edge><edge id="R92_REL010" source="PROC_CO_MASS_LOSS_REPLACEMENT" target="DATA_MASS_LOSS_SPECIAL_NONRECEIPT_FILE"><data key="edge_relationship_id">R92_REL010</data><data key="edge_source_entity_id">PROC_CO_MASS_LOSS_REPLACEMENT</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_MASS_LOSS_SPECIAL_NONRECEIPT_FILE</data><data key="edge_operational_context">Central-office systems replacement uses a special nonreceipt payment file to handle mass-loss cases at scale.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL011" source="DATA_MASS_LOSS_SPECIAL_NONRECEIPT_FILE" target="ORG_TREASURY"><data key="edge_relationship_id">R92_REL011</data><data key="edge_source_entity_id">DATA_MASS_LOSS_SPECIAL_NONRECEIPT_FILE</data><data key="edge_relationship_type">provided_to</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Treasury uses the special mass-loss file to create and issue replacement checks without separate field input.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL012" source="UI_SSI_UPER" target="PROC_PDAS"><data key="edge_relationship_id">R92_REL012</data><data key="edge_source_entity_id">UI_SSI_UPER</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_PDAS</data><data key="edge_operational_context">UPER supports specified Title XVI operational mass-loss nonreceipt inputs when SSAlerts directs field/TSC action.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">UPER is not used for ordinary delay-in-delivery situations.</data></edge><edge id="R92_REL013" source="DOC_SSI_UNDELIVERABLE_COVER_LETTER" target="PROC_T16_UNDELIV_ADDRESS"><data key="edge_relationship_id">R92_REL013</data><data key="edge_source_entity_id">DOC_SSI_UNDELIVERABLE_COVER_LETTER</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">PROC_T16_UNDELIV_ADDRESS</data><data key="edge_operational_context">When locate efforts succeed, specified SSI notices with appeal rights are re-mailed under the Undeliverable Cover Letter.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL014" source="SYS_MBR" target="DATA_STAT_SUPP_5A_2026"><data key="edge_relationship_id">R92_REL014</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_records_for</data><data key="edge_target_entity_id">DATA_STAT_SUPP_5A_2026</data><data key="edge_operational_context">The 2026 Statistical Supplement 5.A tables identify the Master Beneficiary Record as their administrative source, generally using 100-percent data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL015" source="UI_ERPS_PAYMENT_LEGEND" target="APP_ERPS"><data key="edge_relationship_id">R92_REL015</data><data key="edge_source_entity_id">UI_ERPS_PAYMENT_LEGEND</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Payment Legend is an eRPS screen used in representative-payee setup and naming rules.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R92_REL016" source="UI_ERPS_ORG_BASIC_INFO" target="APP_ERPS"><data key="edge_relationship_id">R92_REL016</data><data key="edge_source_entity_id">UI_ERPS_ORG_BASIC_INFO</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Rep Payee Organization Basic Info is an eRPS screen for organizational payee information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R93_REL001" source="APP_SSNAP" target="UI_SSNAP_ADDITIONAL_INFO"><data key="edge_relationship_id">R93_REL001</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_SSNAP_ADDITIONAL_INFO</data><data key="edge_operational_context">Current POMS identifies Additional Info as an SSNAP screen used for replacement-card count and card-suppression functions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL002" source="UI_SSNAP_ADDITIONAL_INFO" target="DATA_SSNAP_REPLACEMENT_CARD_COUNT"><data key="edge_relationship_id">R93_REL002</data><data key="edge_source_entity_id">UI_SSNAP_ADDITIONAL_INFO</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">DATA_SSNAP_REPLACEMENT_CARD_COUNT</data><data key="edge_operational_context">The Replacement Card Count is displayed on the SSNAP Additional Info screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL003" source="APP_SSNAP" target="DATA_SSNAP_REPLACEMENT_CARD_COUNT"><data key="edge_relationship_id">R93_REL003</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">tracks_or_exposes</data><data key="edge_target_entity_id">DATA_SSNAP_REPLACEMENT_CARD_COUNT</data><data key="edge_operational_context">POMS states the enumeration system tracks replacement cards and SSNAP exposes the count used to adjudicate limits.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL004" source="APP_SSNAP" target="UI_SSNAP_SUMMARY"><data key="edge_relationship_id">R93_REL004</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_SSNAP_SUMMARY</data><data key="edge_operational_context">Current Numident-change policy directs staff to use the SSNAP Summary screen Remarks field.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL005" source="UI_SSNAP_SUMMARY" target="SYS_NUMIDENT"><data key="edge_relationship_id">R93_REL005</data><data key="edge_source_entity_id">UI_SSNAP_SUMMARY</data><data key="edge_relationship_type">documents_supporting_evidence_for</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSNAP Summary Remarks lists evidence documents supporting a Numident change if not otherwise captured in SSNAP.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL006" source="APP_SSNAP" target="FORM_SSA_L676"><data key="edge_relationship_id">R93_REL006</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">uses_notice</data><data key="edge_target_entity_id">FORM_SSA_L676</data><data key="edge_operational_context">Current SSN processing policy directs use of SSA-L676 when SSA cannot process specified SSN/card requests for lack of required work authorization or valid nonwork basis/evidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL007" source="APP_SSNAP" target="UI_SSNAP_PROOF_LEGAL_ALIEN"><data key="edge_relationship_id">R93_REL007</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_SSNAP_PROOF_LEGAL_ALIEN</data><data key="edge_operational_context">Current policy names the Proof of Legal Alien Status screen in SSNAP for documenting specified nonwork SSN requests.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL008" source="EX_EBE" target="WORK_EBE_INVESTIGATE"><data key="edge_relationship_id">R93_REL008</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">can_create_pending_status</data><data key="edge_target_entity_id">WORK_EBE_INVESTIGATE</data><data key="edge_operational_context">An EBE record that generates EM3 is not automatically completed and remains pending in SSNAP as Investigate.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL009" source="DATA_ENUM_FEEDBACK_EM3" target="WORK_EBE_INVESTIGATE"><data key="edge_relationship_id">R93_REL009</data><data key="edge_source_entity_id">DATA_ENUM_FEEDBACK_EM3</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">WORK_EBE_INVESTIGATE</data><data key="edge_operational_context">Current EBE POMS states an Investigate application generated Enumeration Feedback Message 3.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL010" source="WORK_EBE_INVESTIGATE" target="REPORT_ENUM_MI_LISTING"><data key="edge_relationship_id">R93_REL010</data><data key="edge_source_entity_id">WORK_EBE_INVESTIGATE</data><data key="edge_relationship_type">listed_on</data><data key="edge_target_entity_id">REPORT_ENUM_MI_LISTING</data><data key="edge_operational_context">Current EBE POMS states Investigate applications are listed on the Enumeration MI listing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL011" source="WORK_EBE_INVESTIGATE" target="APP_SSNAP"><data key="edge_relationship_id">R93_REL011</data><data key="edge_source_entity_id">WORK_EBE_INVESTIGATE</data><data key="edge_relationship_type">remains_pending_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Unprocessed EBE Investigate records remain pending in SSNAP for up to 365 days absent required applicant evidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL012" source="EX_EBE" target="WORK_EBE_NOT_COMPLETED"><data key="edge_relationship_id">R93_REL012</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">can_create_pending_status</data><data key="edge_target_entity_id">WORK_EBE_NOT_COMPLETED</data><data key="edge_operational_context">An EBE application with errors or missing required information is left pending as Not Completed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL013" source="WORK_EBE_NOT_COMPLETED" target="APP_SSNAP"><data key="edge_relationship_id">R93_REL013</data><data key="edge_source_entity_id">WORK_EBE_NOT_COMPLETED</data><data key="edge_relationship_type">remains_pending_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Unprocessed EBE Not Completed records remain pending in SSNAP for up to 365 days absent required applicant evidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL014" source="QRY_SSID" target="DATA_SSID_DIAR_SEGMENT"><data key="edge_relationship_id">R93_REL014</data><data key="edge_source_entity_id">QRY_SSID</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">DATA_SSID_DIAR_SEGMENT</data><data key="edge_operational_context">Current POMS describes the DIAR segment of the SSID as holding diary maturity data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL015" source="QRY_SSID" target="DATA_SSID_CRZD_SEGMENT"><data key="edge_relationship_id">R93_REL015</data><data key="edge_source_entity_id">QRY_SSID</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">DATA_SSID_CRZD_SEGMENT</data><data key="edge_operational_context">Current POMS identifies CRZD selection indicators in the SSID for multiple RZ/LI workload categories.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL016" source="QRY_SSID" target="DATA_SSID_REPY_SEGMENT"><data key="edge_relationship_id">R93_REL016</data><data key="edge_source_entity_id">QRY_SSID</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">DATA_SSID_REPY_SEGMENT</data><data key="edge_operational_context">Current POMS directs staff to review the REPY segment of the pre-RZ SSID for representative-payee suitability and accounting indicators.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL017" source="PORTAL_DEEMING_LISTINGS" target="DATA_MANUAL_DEEMING_LIST"><data key="edge_relationship_id">R93_REL017</data><data key="edge_source_entity_id">PORTAL_DEEMING_LISTINGS</data><data key="edge_relationship_type">hosts</data><data key="edge_target_entity_id">DATA_MANUAL_DEEMING_LIST</data><data key="edge_operational_context">The Deeming Listings Page provides online read-only access to the annual manual deeming list.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL018" source="DATA_MANUAL_DEEMING_LIST" target="PORTAL_SUMS_MCAS_MI_CENTRAL"><data key="edge_relationship_id">R93_REL018</data><data key="edge_source_entity_id">DATA_MANUAL_DEEMING_LIST</data><data key="edge_relationship_type">not_control_linked_to</data><data key="edge_target_entity_id">PORTAL_SUMS_MCAS_MI_CENTRAL</data><data key="edge_operational_context">Current POMS explicitly states manual-deeming-list cases are not controlled by SUMS/MCAS MI Central.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL019" source="DATA_MANUAL_DEEMING_LIST" target="SYS_SSR"><data key="edge_relationship_id">R93_REL019</data><data key="edge_source_entity_id">DATA_MANUAL_DEEMING_LIST</data><data key="edge_relationship_type">does_not_generate_diary_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS explicitly states there is no SSR diary identifying cases on the annual manual-deeming list.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL020" source="ORG_STATE_DMV" target="DATA_STATE_VEHICLE_TITLE_REG"><data key="edge_relationship_id">R93_REL020</data><data key="edge_source_entity_id">ORG_STATE_DMV</data><data key="edge_relationship_type">provides_or_originates</data><data key="edge_target_entity_id">DATA_STATE_VEHICLE_TITLE_REG</data><data key="edge_operational_context">State vehicle-title and registration sources are used for conditional verification of suspected unreported vehicle ownership.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL021" source="PROC_SSI_VEHICLE_RESOURCE_VERIFY" target="DATA_STATE_VEHICLE_TITLE_REG"><data key="edge_relationship_id">R93_REL021</data><data key="edge_source_entity_id">PROC_SSI_VEHICLE_RESOURCE_VERIFY</data><data key="edge_relationship_type">uses_for_conditional_verification</data><data key="edge_target_entity_id">DATA_STATE_VEHICLE_TITLE_REG</data><data key="edge_operational_context">If staff suspect an unreported vehicle, they may verify State vehicle title and registration information from third parties.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL022" source="PROC_SSI_VEHICLE_RESOURCE_VERIFY" target="SVC_JD_POWER_VALUES"><data key="edge_relationship_id">R93_REL022</data><data key="edge_source_entity_id">PROC_SSI_VEHICLE_RESOURCE_VERIFY</data><data key="edge_relationship_type">uses_for_fair_market_value</data><data key="edge_target_entity_id">SVC_JD_POWER_VALUES</data><data key="edge_operational_context">SSA policy requires fair-market-value verification for multiple vehicles; the existing Atlas records J.D. Power Values Online as the current subscription valuation service.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL023" source="WORK_WCPDB_RIB_ALERT" target="PROC_WCPDB_HIGHER_RIB_NOTICE"><data key="edge_relationship_id">R93_REL023</data><data key="edge_source_entity_id">WORK_WCPDB_RIB_ALERT</data><data key="edge_relationship_type">initiates_review_for</data><data key="edge_target_entity_id">PROC_WCPDB_HIGHER_RIB_NOTICE</data><data key="edge_operational_context">The one-time alert prompts employees to compare retirement and disability benefit amounts and determine whether notification is required.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R93_REL024" source="PROC_WCPDB_HIGHER_RIB_NOTICE" target="APP_EVID"><data key="edge_relationship_id">R93_REL024</data><data key="edge_source_entity_id">PROC_WCPDB_HIGHER_RIB_NOTICE</data><data key="edge_relationship_type">documents_decision_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Current policy requires employees to document the beneficiary discussion and reason for not filing on the Evidence screen in SSA shared processes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL001" source="ORG_ORSIS" target="PROC_MASS_COA_USPS"><data key="edge_relationship_id">R94_REL001</data><data key="edge_source_entity_id">ORG_ORSIS</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_MASS_COA_USPS</data><data key="edge_operational_context">Live POMS identifies ORSIS as the organization performing automated master-file updates for mass USPS address changes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Organization name/status should be revalidated because the underlying transmittal is legacy.</data></edge><edge id="R94_REL002" source="PROC_MASS_COA_USPS" target="APP_ZIP4_SOFTWARE"><data key="edge_relationship_id">R94_REL002</data><data key="edge_source_entity_id">PROC_MASS_COA_USPS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ZIP4_SOFTWARE</data><data key="edge_operational_context">Mass change processing runs affected MBR/SSR records through ZIP+4 software to determine corrected ZIP data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL003" source="PROC_MASS_COA_USPS" target="DATA_USPS_ZIP_TABLES"><data key="edge_relationship_id">R94_REL003</data><data key="edge_source_entity_id">PROC_MASS_COA_USPS</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_USPS_ZIP_TABLES</data><data key="edge_operational_context">Mass postal change processing updates ZIP tables used for front-end validation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data></edge><edge id="R94_REL004" source="PROC_MASS_COA_USPS" target="WORK_SSI_Z7_DIARY"><data key="edge_relationship_id">R94_REL004</data><data key="edge_source_entity_id">PROC_MASS_COA_USPS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">WORK_SSI_Z7_DIARY</data><data key="edge_operational_context">POMS says a Z7 alert/diary is generated for Title XVI when ZIP+4 cannot determine the correct ZIP or ZIP+4.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data></edge><edge id="R94_REL005" source="WORK_SSI_Z7_DIARY" target="SYS_SSR"><data key="edge_relationship_id">R94_REL005</data><data key="edge_source_entity_id">WORK_SSI_Z7_DIARY</data><data key="edge_relationship_type">flags_address_problem_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The Z7 work control is generated for affected Title XVI records during mass postal address correction.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Logical work-control relationship; no physical diary table inferred.</data></edge><edge id="R94_REL006" source="APP_EVIEW" target="UI_EVIEW_CASE_SELECTION"><data key="edge_relationship_id">R94_REL006</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_EVIEW_CASE_SELECTION</data><data key="edge_operational_context">Current eView POMS identifies the Case Selection screen used to search and select electronic disability cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL007" source="UI_EVIEW_CASE_SELECTION" target="DATA_EDCS_FOLDER_NUMBER"><data key="edge_relationship_id">R94_REL007</data><data key="edge_source_entity_id">UI_EVIEW_CASE_SELECTION</data><data key="edge_relationship_type">searches_by</data><data key="edge_target_entity_id">DATA_EDCS_FOLDER_NUMBER</data><data key="edge_operational_context">Users can search eView directly by the unique EDCS Folder Number.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL008" source="APP_EDCS" target="DATA_EDCS_FOLDER_NUMBER"><data key="edge_relationship_id">R94_REL008</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">assigns</data><data key="edge_target_entity_id">DATA_EDCS_FOLDER_NUMBER</data><data key="edge_operational_context">POMS states the Field Office creates the EDCS case and a unique folder number is assigned.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL009" source="UI_EVIEW_CASE_SELECTION" target="DATA_EVIEW_CEF_INDICATOR"><data key="edge_relationship_id">R94_REL009</data><data key="edge_source_entity_id">UI_EVIEW_CASE_SELECTION</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">DATA_EVIEW_CEF_INDICATOR</data><data key="edge_operational_context">The case-selection results show a Y/N certified electronic folder indicator.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL010" source="UI_EVIEW_CASE_SELECTION" target="DATA_EVIEW_CASE_STATUS"><data key="edge_relationship_id">R94_REL010</data><data key="edge_source_entity_id">UI_EVIEW_CASE_SELECTION</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">DATA_EVIEW_CASE_STATUS</data><data key="edge_operational_context">The case-selection results expose electronic-folder status including Closed, Pending, Transferred, and Manually Cleared.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL011" source="UI_EVIEW_CASE_SELECTION" target="APP_MCS"><data key="edge_relationship_id">R94_REL011</data><data key="edge_source_entity_id">UI_EVIEW_CASE_SELECTION</data><data key="edge_relationship_type">derives_title_ii_filing_date_from</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">For Title II, the displayed filing date is derived from MCS, including the protective filing date on FDDS for initial claims.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL012" source="UI_EVIEW_CASE_SELECTION" target="UI_EVIEW_ALERTS_MESSAGES"><data key="edge_relationship_id">R94_REL012</data><data key="edge_source_entity_id">UI_EVIEW_CASE_SELECTION</data><data key="edge_relationship_type">opens</data><data key="edge_target_entity_id">UI_EVIEW_ALERTS_MESSAGES</data><data key="edge_operational_context">Selecting a matching case normally displays the Alerts &amp; Messages tab.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL013" source="APP_EVIEW" target="UI_EVIEW_CASE_PROCESS_VIEW"><data key="edge_relationship_id">R94_REL013</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_EVIEW_CASE_PROCESS_VIEW</data><data key="edge_operational_context">Current eView overview names the Disability Case Process (View Mode) screen as the selected-case view.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL014" source="UI_EVIEW_CASE_PROCESS_VIEW" target="UI_EVIEW_ALERTS_MESSAGES"><data key="edge_relationship_id">R94_REL014</data><data key="edge_source_entity_id">UI_EVIEW_CASE_PROCESS_VIEW</data><data key="edge_relationship_type">contains_tab</data><data key="edge_target_entity_id">UI_EVIEW_ALERTS_MESSAGES</data><data key="edge_operational_context">eView overview identifies Alerts &amp; Messages as a tab on the case view.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL015" source="UI_EVIEW_CASE_PROCESS_VIEW" target="DATA_EVIEW_CASE_DATA"><data key="edge_relationship_id">R94_REL015</data><data key="edge_source_entity_id">UI_EVIEW_CASE_PROCESS_VIEW</data><data key="edge_relationship_type">contains_tab</data><data key="edge_target_entity_id">DATA_EVIEW_CASE_DATA</data><data key="edge_operational_context">eView overview identifies Case Data as a tab on the case view.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL016" source="UI_EVIEW_CASE_PROCESS_VIEW" target="UI_EVIEW_CASE_DOCUMENTS"><data key="edge_relationship_id">R94_REL016</data><data key="edge_source_entity_id">UI_EVIEW_CASE_PROCESS_VIEW</data><data key="edge_relationship_type">contains_tab</data><data key="edge_target_entity_id">UI_EVIEW_CASE_DOCUMENTS</data><data key="edge_operational_context">eView overview identifies Case Documents as a tab on the case view.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL017" source="UI_EVIEW_CASE_PROCESS_VIEW" target="UI_EVIEW_STATUS_HISTORY"><data key="edge_relationship_id">R94_REL017</data><data key="edge_source_entity_id">UI_EVIEW_CASE_PROCESS_VIEW</data><data key="edge_relationship_type">contains_tab</data><data key="edge_target_entity_id">UI_EVIEW_STATUS_HISTORY</data><data key="edge_operational_context">eView overview identifies Status/History as a tab on the case view.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL018" source="UI_EVIEW_CASE_PROCESS_VIEW" target="UI_EVIEW_EXHIBIT_LIST"><data key="edge_relationship_id">R94_REL018</data><data key="edge_source_entity_id">UI_EVIEW_CASE_PROCESS_VIEW</data><data key="edge_relationship_type">contains_tab</data><data key="edge_target_entity_id">UI_EVIEW_EXHIBIT_LIST</data><data key="edge_operational_context">eView overview identifies Exhibit List as a tab when one exists, with OHO/OAO functionality.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL019" source="WORK_SSI_SB_DIARY" target="DB_SSI_PE_ODS"><data key="edge_relationship_id">R94_REL019</data><data key="edge_source_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_SSI_PE_ODS</data><data key="edge_operational_context">Current POMS instructs staff to identify records with SB diaries by accessing PE ODS and says the SB alert is controlled by PE ODS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL020" source="WORK_SSI_SB_DIARY" target="ALERT_SSI_SAVINGS_SECURITY"><data key="edge_relationship_id">R94_REL020</data><data key="edge_source_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_relationship_type">associated_with</data><data key="edge_target_entity_id">ALERT_SSI_SAVINGS_SECURITY</data><data key="edge_operational_context">The SB diary is the work control associated with the savings-security interface alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL021" source="EX_CMA1038_BFS_SAVINGS" target="WORK_SSI_SB_DIARY"><data key="edge_relationship_id">R94_REL021</data><data key="edge_source_entity_id">EX_CMA1038_BFS_SAVINGS</data><data key="edge_relationship_type">creates_work_for</data><data key="edge_target_entity_id">WORK_SSI_SB_DIARY</data><data key="edge_operational_context">The twice-yearly savings-security match produces the SB work-control population handled through PE ODS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL022" source="FORM_SSA562U3" target="ORG_BFS"><data key="edge_relationship_id">R94_REL022</data><data key="edge_source_entity_id">FORM_SSA562U3</data><data key="edge_relationship_type">used_to_request_verification_from</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">POMS instructs staff to use SSA-562-U3 through the designated SSA office to request BFS savings-security ownership verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL023" source="APP_ERPS" target="DATA_ERPS_BENE_CAPABILITY_NOTE"><data key="edge_relationship_id">R94_REL023</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">stores_note_type</data><data key="edge_target_entity_id">DATA_ERPS_BENE_CAPABILITY_NOTE</data><data key="edge_operational_context">Current POMS requires the Bene Capability Determination note type to document capability decisions in eRPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL024" source="DATA_ERPS_BENE_CAPABILITY_NOTE" target="UI_ERPS_BENE_DETAILS"><data key="edge_relationship_id">R94_REL024</data><data key="edge_source_entity_id">DATA_ERPS_BENE_CAPABILITY_NOTE</data><data key="edge_relationship_type">displayed_on</data><data key="edge_target_entity_id">UI_ERPS_BENE_DETAILS</data><data key="edge_operational_context">Completed capability determinations are viewable in Beneficiary Details notes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL025" source="APP_ERPC" target="UI_ERPC_WORKLOAD_MGMT"><data key="edge_relationship_id">R94_REL025</data><data key="edge_source_entity_id">APP_ERPC</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_ERPC_WORKLOAD_MGMT</data><data key="edge_operational_context">POMS identifies a Workload Management screen in the RPC tool.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL026" source="APP_ERPC" target="UI_ERPC_WORKLOAD_SUMMARY"><data key="edge_relationship_id">R94_REL026</data><data key="edge_source_entity_id">APP_ERPC</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_ERPC_WORKLOAD_SUMMARY</data><data key="edge_operational_context">POMS identifies a Workload Summary screen in the RPC tool.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL027" source="UI_ERPC_WORKLOAD_SUMMARY" target="APP_EVIEW"><data key="edge_relationship_id">R94_REL027</data><data key="edge_source_entity_id">UI_ERPC_WORKLOAD_SUMMARY</data><data key="edge_relationship_type">supports_case_review_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Authorized managers use Workload Summary access to review pending RPC cases in eView.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL028" source="APP_ERPC" target="DASH_ERPC_MI"><data key="edge_relationship_id">R94_REL028</data><data key="edge_source_entity_id">APP_ERPC</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DASH_ERPC_MI</data><data key="edge_operational_context">POMS identifies Management Information Dashboards within the RPC tool.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL029" source="APP_ERPC" target="QRY_ERPC_SEARCH"><data key="edge_relationship_id">R94_REL029</data><data key="edge_source_entity_id">APP_ERPC</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">QRY_ERPC_SEARCH</data><data key="edge_operational_context">POMS identifies Search Data and Text Search capabilities for RPC case and narrative analysis.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL030" source="PROC_SSIDPP" target="DATA_SSI_PS_T20"><data key="edge_relationship_id">R94_REL030</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">uses_termination_status</data><data key="edge_target_entity_id">DATA_SSI_PS_T20</data><data key="edge_operational_context">Duplicate-payment cases with payment made are terminated using T20 on the incorrect record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL031" source="PROC_SSIDPP" target="DATA_SSI_PS_T50"><data key="edge_relationship_id">R94_REL031</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">uses_termination_status</data><data key="edge_target_entity_id">DATA_SSI_PS_T50</data><data key="edge_operational_context">Duplicate/no-payment cases use T50 to prevent duplicate payment issuance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL032" source="DATA_SSI_PS_T20" target="SYS_SSR"><data key="edge_relationship_id">R94_REL032</data><data key="edge_source_entity_id">DATA_SSI_PS_T20</data><data key="edge_relationship_type">status_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">T20 is a Title XVI payment-status code applied to the incorrect duplicate SSI record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL033" source="DATA_SSI_PS_T50" target="SYS_SSR"><data key="edge_relationship_id">R94_REL033</data><data key="edge_source_entity_id">DATA_SSI_PS_T50</data><data key="edge_relationship_type">status_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">T50 is a Title XVI payment-status code applied to the incorrect duplicate SSI record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL034" source="PROC_SSIDPP" target="PROC_MSSICS_MANCLR"><data key="edge_relationship_id">R94_REL034</data><data key="edge_source_entity_id">PROC_SSIDPP</data><data key="edge_relationship_type">may_require</data><data key="edge_target_entity_id">PROC_MSSICS_MANCLR</data><data key="edge_operational_context">If a duplicate no-payment record has an unarchived MSSICS pending file, staff clear it with MANCLR before T50.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL035" source="PROC_MSSICS_MANCLR" target="APP_MSSICS"><data key="edge_relationship_id">R94_REL035</data><data key="edge_source_entity_id">PROC_MSSICS_MANCLR</data><data key="edge_relationship_type">operates_on</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS explicitly names MANCLR MSSICS as the manual process used to clear the pending file.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL036" source="PROC_REP_TRAVEL_EFT" target="FORM_SF3881"><data key="edge_relationship_id">R94_REL036</data><data key="edge_source_entity_id">PROC_REP_TRAVEL_EFT</data><data key="edge_relationship_type">accepts_enrollment_form</data><data key="edge_target_entity_id">FORM_SF3881</data><data key="edge_operational_context">SSA permits representatives to submit SF 3881 to establish direct deposit for travel reimbursement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL037" source="PROC_REP_TRAVEL_EFT" target="DATA_UNIQUE_ENTITY_IDENTIFIER"><data key="edge_relationship_id">R94_REL037</data><data key="edge_source_entity_id">PROC_REP_TRAVEL_EFT</data><data key="edge_relationship_type">accepts_identifier</data><data key="edge_target_entity_id">DATA_UNIQUE_ENTITY_IDENTIFIER</data><data key="edge_operational_context">SSA permits representatives to include an assigned UEI when submitting a travel reimbursement request.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL038" source="DATA_UNIQUE_ENTITY_IDENTIFIER" target="SVC_SAM_GOV"><data key="edge_relationship_id">R94_REL038</data><data key="edge_source_entity_id">DATA_UNIQUE_ENTITY_IDENTIFIER</data><data key="edge_relationship_type">obtained_from</data><data key="edge_target_entity_id">SVC_SAM_GOV</data><data key="edge_operational_context">SSA guidance directs representatives to obtain the UEI through SAM.gov.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL039" source="APP_ERPS" target="UI_ERPS_LEGAL_GUARDIAN_DETAILS"><data key="edge_relationship_id">R94_REL039</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">UI_ERPS_LEGAL_GUARDIAN_DETAILS</data><data key="edge_operational_context">Current capability-development POMS references the eRPS Legal Guardian Details screen for guardian information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL040" source="APP_ERPS" target="WORK_ERPS_CRTOR"><data key="edge_relationship_id">R94_REL040</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">uses_work_control</data><data key="edge_target_entity_id">WORK_ERPS_CRTOR</data><data key="edge_operational_context">Current POMS directs staff to diary eRPS for 10 calendar days with CRTOR when awaiting a required court order.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R94_REL041" source="WORK_ERPS_CRTOR" target="DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE"><data key="edge_relationship_id">R94_REL041</data><data key="edge_source_entity_id">WORK_ERPS_CRTOR</data><data key="edge_relationship_type">tracks_receipt_of</data><data key="edge_target_entity_id">DATA_REP_PAYEE_LEGAL_INCOMP_EVIDENCE</data><data key="edge_operational_context">CRTOR follows up for the court order supporting legal incompetence/guardian evidence.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data></edge><edge id="R95_REL001" source="PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT" target="DATA_TRUMP_ACCOUNT_RESOURCE"><data key="edge_relationship_id">R95_REL001</data><data key="edge_source_entity_id">PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT</data><data key="edge_relationship_type">develops_resource</data><data key="edge_target_entity_id">DATA_TRUMP_ACCOUNT_RESOURCE</data><data key="edge_operational_context">Current POMS establishes the Trump Account as the resource being documented and redeveloped for SSI purposes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL002" source="PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT" target="UI_SSI_OTHER_RESOURCES"><data key="edge_relationship_id">R95_REL002</data><data key="edge_source_entity_id">PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT</data><data key="edge_relationship_type">documents_on</data><data key="edge_target_entity_id">UI_SSI_OTHER_RESOURCES</data><data key="edge_operational_context">Current POMS directs staff to record Trump Account information on the Other Resources page.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL003" source="PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT" target="WORK_SSI_RT_DIARY"><data key="edge_relationship_id">R95_REL003</data><data key="edge_source_entity_id">PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT</data><data key="edge_relationship_type">schedules_followup_with</data><data key="edge_target_entity_id">WORK_SSI_RT_DIARY</data><data key="edge_operational_context">Current POMS requires RT diaries for age-17 and age-18 Trump Account/ABLE development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL004" source="WORK_SSI_RT_DIARY" target="UI_SSI_UDIA"><data key="edge_relationship_id">R95_REL004</data><data key="edge_source_entity_id">WORK_SSI_RT_DIARY</data><data key="edge_relationship_type">maintained_via</data><data key="edge_target_entity_id">UI_SSI_UDIA</data><data key="edge_operational_context">Current POMS directs staff to manually post the RT diary on the UDIA screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL005" source="UI_SSI_UMEN" target="UI_SSI_UDIA"><data key="edge_relationship_id">R95_REL005</data><data key="edge_source_entity_id">UI_SSI_UMEN</data><data key="edge_relationship_type">navigates_to</data><data key="edge_target_entity_id">UI_SSI_UDIA</data><data key="edge_operational_context">Current POMS says select Diaries from UMEN and post the diary on UDIA.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL006" source="UI_SSI_UMEN" target="IFACE_SSI_DIRECT_SSR"><data key="edge_relationship_id">R95_REL006</data><data key="edge_source_entity_id">UI_SSI_UMEN</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_operational_context">UMEN is explicitly named the Direct SSR Update Menu in current POMS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL007" source="PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT" target="APP_EP"><data key="edge_relationship_id">R95_REL007</data><data key="edge_source_entity_id">PROC_SSI_TRUMP_ACCOUNT_DEVELOPMENT</data><data key="edge_relationship_type">stores_evidence_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">At ages 16/17 and post-growth development, account statements and related evidence are stored through Evidence Portal.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL008" source="DATA_TA_ABLE_ROLLOVER" target="DATA_TRUMP_ACCOUNT_RESOURCE"><data key="edge_relationship_id">R95_REL008</data><data key="edge_source_entity_id">DATA_TA_ABLE_ROLLOVER</data><data key="edge_relationship_type">converts_resource_from</data><data key="edge_target_entity_id">DATA_TRUMP_ACCOUNT_RESOURCE</data><data key="edge_operational_context">Current policy treats the trustee-to-trustee TA-to-ABLE rollover as a resource-form conversion during the permitted age-17 period.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL009" source="DATA_TA_ABLE_ROLLOVER" target="DATA_SSI_ABLE_ACCOUNT"><data key="edge_relationship_id">R95_REL009</data><data key="edge_source_entity_id">DATA_TA_ABLE_ROLLOVER</data><data key="edge_relationship_type">converts_resource_to</data><data key="edge_target_entity_id">DATA_SSI_ABLE_ACCOUNT</data><data key="edge_operational_context">Current POMS directs staff to update the ABLE account page/data after a completed rollover.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL010" source="PROC_EAB_TRUMP_ACCOUNT_ENROLLMENT" target="EX_EAB"><data key="edge_relationship_id">R95_REL010</data><data key="edge_source_entity_id">PROC_EAB_TRUMP_ACCOUNT_ENROLLMENT</data><data key="edge_relationship_type">uses_identity_lifecycle_gateway</data><data key="edge_target_entity_id">EX_EAB</data><data key="edge_operational_context">SSA announced use of the Enumeration at Birth process to assist parents with newborn Trump Account enrollment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL011" source="PROC_EAB_TRUMP_ACCOUNT_ENROLLMENT" target="SYS_NUMIDENT"><data key="edge_relationship_id">R95_REL011</data><data key="edge_source_entity_id">PROC_EAB_TRUMP_ACCOUNT_ENROLLMENT</data><data key="edge_relationship_type">requires_valid_ssn</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA states eligible children need a valid Social Security number; no Numident write beyond ordinary enumeration is inferred.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL012" source="NOTICE_EDCOR" target="PLAT_BSO"><data key="edge_relationship_id">R95_REL012</data><data key="edge_source_entity_id">NOTICE_EDCOR</data><data key="edge_relationship_type">directs_employer_to</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">EDCOR notices historically directed employers to BSO; current employer guidance now relies on BSO tools instead of mailed EDCOR notices.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL013" source="SVC_BSO_NAME_SSN_ERRORS" target="PLAT_BSO"><data key="edge_relationship_id">R95_REL013</data><data key="edge_source_entity_id">SVC_BSO_NAME_SSN_ERRORS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">Current SSA employer guidance lists View Wage Report Name/SSN Errors as a BSO service.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL014" source="PROC_DECOR_NO_MATCH_MAILING" target="FORM_SSA_L3365_C1"><data key="edge_relationship_id">R95_REL014</data><data key="edge_source_entity_id">PROC_DECOR_NO_MATCH_MAILING</data><data key="edge_relationship_type">historically_generated</data><data key="edge_target_entity_id">FORM_SSA_L3365_C1</data><data key="edge_operational_context">Current POMS identifies SSA-L3365-C1 as a suspended DECOR letter to employees.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL015" source="PROC_DECOR_NO_MATCH_MAILING" target="FORM_SSA_L2765_C1"><data key="edge_relationship_id">R95_REL015</data><data key="edge_source_entity_id">PROC_DECOR_NO_MATCH_MAILING</data><data key="edge_relationship_type">historically_generated</data><data key="edge_target_entity_id">FORM_SSA_L2765_C1</data><data key="edge_operational_context">Current POMS identifies SSA-L2765-C1 as a suspended DECOR letter to self-employed workers.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL016" source="PROC_DECOR_NO_MATCH_MAILING" target="FORM_SSA_L4002_C1"><data key="edge_relationship_id">R95_REL016</data><data key="edge_source_entity_id">PROC_DECOR_NO_MATCH_MAILING</data><data key="edge_relationship_type">historically_generated</data><data key="edge_target_entity_id">FORM_SSA_L4002_C1</data><data key="edge_operational_context">Current POMS identifies SSA-L4002-C1 as a suspended DECOR letter to employers.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL017" source="FORM_SSA_L3365_C1" target="DATA_DECOR_W2_EMPLOYEE_ADDRESS"><data key="edge_relationship_id">R95_REL017</data><data key="edge_source_entity_id">FORM_SSA_L3365_C1</data><data key="edge_relationship_type">historically_used_address</data><data key="edge_target_entity_id">DATA_DECOR_W2_EMPLOYEE_ADDRESS</data><data key="edge_operational_context">Current POMS says the employee address used for this DECOR letter was derived from Form W-2.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL018" source="FORM_SSA_L2765_C1" target="DATA_DECOR_IRS_SE_ADDRESS"><data key="edge_relationship_id">R95_REL018</data><data key="edge_source_entity_id">FORM_SSA_L2765_C1</data><data key="edge_relationship_type">historically_used_address</data><data key="edge_target_entity_id">DATA_DECOR_IRS_SE_ADDRESS</data><data key="edge_operational_context">Current POMS says this DECOR letter used a self-employed worker address derived from IRS-provided data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL019" source="DATA_DECOR_IRS_SE_ADDRESS" target="ORG_IRS"><data key="edge_relationship_id">R95_REL019</data><data key="edge_source_entity_id">DATA_DECOR_IRS_SE_ADDRESS</data><data key="edge_relationship_type">derived_from_partner_data</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Current POMS explicitly identifies Internal Revenue Service-provided data as the source of the self-employed worker mailing address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">No automatic update to any SSA master address is documented.</data></edge><edge id="R95_REL020" source="PROC_DECOR_NO_MATCH_MAILING" target="DB_ESF"><data key="edge_relationship_id">R95_REL020</data><data key="edge_source_entity_id">PROC_DECOR_NO_MATCH_MAILING</data><data key="edge_relationship_type">responded_to_mismatch_workload</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">POMS explains that unmatched wage reports are placed in ESF and no-match correspondence historically supported correction of those mismatches.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL021" source="SYS_MBR" target="DATA_MBR_LAW_PRS"><data key="edge_relationship_id">R95_REL021</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_MBR_LAW_PRS</data><data key="edge_operational_context">Current POMS identifies the LAW PRS data line on MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL022" source="DATA_MBR_LAW_PRS" target="PROC_LAWFUL_PRESENCE_VERIFICATION"><data key="edge_relationship_id">R95_REL022</data><data key="edge_source_entity_id">DATA_MBR_LAW_PRS</data><data key="edge_relationship_type">can_provide_prior_proof_for</data><data key="edge_target_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="edge_operational_context">When PROOF is YES and the status is an allowed permanent/no-reverification condition, current policy permits the MBR LAW PRS line to establish previously proven lawful presence subject to conflict checks.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL023" source="SYS_NUMIDENT" target="DATA_NUMIDENT_IDN_H"><data key="edge_relationship_id">R95_REL023</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_NUMIDENT_IDN_H</data><data key="edge_operational_context">Current lawful-presence policy refers to Numident IDN coding including IDN H.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL024" source="DATA_NUMIDENT_IDN_H" target="PROC_LAWFUL_PRESENCE_VERIFICATION"><data key="edge_relationship_id">R95_REL024</data><data key="edge_source_entity_id">DATA_NUMIDENT_IDN_H</data><data key="edge_relationship_type">not_acceptable_as_proof_for</data><data key="edge_target_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="edge_operational_context">Current POMS explicitly states Numident coding is not acceptable evidence of lawful presence for the current claim.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL025" source="PROC_SVES_IDENTITY_VERIFICATION" target="EX_SVES"><data key="edge_relationship_id">R95_REL025</data><data key="edge_source_entity_id">PROC_SVES_IDENTITY_VERIFICATION</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">EX_SVES</data><data key="edge_operational_context">SSA data-exchange manual documents this identity-verification process as native SVES processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL026" source="PROC_SVES_IDENTITY_VERIFICATION" target="APP_EVS"><data key="edge_relationship_id">R95_REL026</data><data key="edge_source_entity_id">PROC_SVES_IDENTITY_VERIFICATION</data><data key="edge_relationship_type">uses_functions_of</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">SVES manual says SVES utilizes EVS functions for verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL027" source="PROC_SVES_IDENTITY_VERIFICATION" target="SYS_NUMIDENT"><data key="edge_relationship_id">R95_REL027</data><data key="edge_source_entity_id">PROC_SVES_IDENTITY_VERIFICATION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SVES uses Numident as one of three core identity-verification databases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL028" source="PROC_SVES_IDENTITY_VERIFICATION" target="SYS_MBR"><data key="edge_relationship_id">R95_REL028</data><data key="edge_source_entity_id">PROC_SVES_IDENTITY_VERIFICATION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SVES uses MBR as one of three core identity-verification databases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL029" source="PROC_SVES_IDENTITY_VERIFICATION" target="SYS_SSR"><data key="edge_relationship_id">R95_REL029</data><data key="edge_source_entity_id">PROC_SVES_IDENTITY_VERIFICATION</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SVES uses SSR as one of three core identity-verification databases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL030" source="EX_SVES" target="SYS_NUMIDENT"><data key="edge_relationship_id">R95_REL030</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">gathers_data_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current SVES/SOLQ manual states SVES/SOLQ gathers target data from Numident, MBR, and SSR without changing the values returned.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL031" source="EX_SVES" target="SYS_MBR"><data key="edge_relationship_id">R95_REL031</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">gathers_data_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current SVES/SOLQ manual states SVES/SOLQ gathers target data from Numident, MBR, and SSR without changing the values returned.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R95_REL032" source="EX_SVES" target="SYS_SSR"><data key="edge_relationship_id">R95_REL032</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">gathers_data_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current SVES/SOLQ manual states SVES/SOLQ gathers target data from Numident, MBR, and SSR without changing the values returned.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_AC_EDITION_1" source="DATA_FDC_3469" target="DATA_AC_RR_PUBLIC"><data key="edge_relationship_id">R96REL_AC_EDITION_1</data><data key="edge_source_entity_id">DATA_FDC_3469</data><data key="edge_relationship_type">annual_edition_of</data><data key="edge_target_entity_id">DATA_AC_RR_PUBLIC</data><data key="edge_operational_context">The FY-specific catalog asset is an annual Appeals Council Requests for Review publication within the already-mapped public collection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is semantic/publication lineage; no internal storage identity is inferred.</data></edge><edge id="R96REL_AC_EDITION_2" source="DATA_FDC_3470" target="DATA_AC_RR_PUBLIC"><data key="edge_relationship_id">R96REL_AC_EDITION_2</data><data key="edge_source_entity_id">DATA_FDC_3470</data><data key="edge_relationship_type">annual_edition_of</data><data key="edge_target_entity_id">DATA_AC_RR_PUBLIC</data><data key="edge_operational_context">The FY-specific catalog asset is an annual Appeals Council Requests for Review publication within the already-mapped public collection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is semantic/publication lineage; no internal storage identity is inferred.</data></edge><edge id="R96REL_AFI_001" source="APP_E4641" target="PROC_AFI_GEOREQUEST"><data key="edge_relationship_id">R96REL_AFI_001</data><data key="edge_source_entity_id">APP_E4641</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_AFI_GEOREQUEST</data><data key="edge_operational_context">e4641 provides the GeoRequest search function when financial account information is needed for defeat-the-purpose waiver development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_AFI_002" source="PROC_AFI_GEOREQUEST" target="EX_AFI_FI"><data key="edge_relationship_id">R96REL_AFI_002</data><data key="edge_source_entity_id">PROC_AFI_GEOREQUEST</data><data key="edge_relationship_type">uses_exchange</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">GeoRequest searches are sent to participating financial institutions through the electronic AFI process; nonparticipating and foreign institutions require paper SSA-4641 development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_DEATH_001" source="APP_DATS" target="PROC_ERRONEOUS_DEATH_CORRECTION"><data key="edge_relationship_id">R96REL_DEATH_001</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_ERRONEOUS_DEATH_CORRECTION</data><data key="edge_operational_context">DATS displays and tracks death alerts and provides the erroneous-report-of-death disposition when the alleged decedent is verified alive.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_DEATH_002" source="APP_DIPS" target="PROC_ERRONEOUS_DEATH_CORRECTION"><data key="edge_relationship_id">R96REL_DEATH_002</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">participates_in</data><data key="edge_target_entity_id">PROC_ERRONEOUS_DEATH_CORRECTION</data><data key="edge_operational_context">DIPS alerts are among the death-alert types resolved through the current DATS workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_DEATH_003" source="PROC_ERRONEOUS_DEATH_CORRECTION" target="SYS_NUMIDENT"><data key="edge_relationship_id">R96REL_DEATH_003</data><data key="edge_source_entity_id">PROC_ERRONEOUS_DEATH_CORRECTION</data><data key="edge_relationship_type">corrects_when_inaccurate</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">If the individual is alive and the payment record is correct but death remains on Numident, SSA removes the death from Numident under the prescribed correction procedures.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_FORM_UPLOAD_01" source="FORM_R96_HA501U5" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R96REL_FORM_UPLOAD_01</data><data key="edge_source_entity_id">FORM_R96_HA501U5</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">The current forms catalog routes the Submit Online action for this form into Upload Documents target HA501.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_FORM_UPLOAD_02" source="FORM_R96_SSA4BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R96REL_FORM_UPLOAD_02</data><data key="edge_source_entity_id">FORM_R96_SSA4BK</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">The current forms catalog routes the Submit Online action for this form into Upload Documents target 4.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_FORM_UPLOAD_03" source="FORM_R96_SSA5BK" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R96REL_FORM_UPLOAD_03</data><data key="edge_source_entity_id">FORM_R96_SSA5BK</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">The current forms catalog routes the Submit Online action for this form into Upload Documents target 5.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_FORM_UPLOAD_04" source="FORM_R96_SSA7F6" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R96REL_FORM_UPLOAD_04</data><data key="edge_source_entity_id">FORM_R96_SSA7F6</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">The current forms catalog routes the Submit Online action for this form into Upload Documents target 7-F6.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_FORM_UPLOAD_05" source="FORM_R96_SSA21" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R96REL_FORM_UPLOAD_05</data><data key="edge_source_entity_id">FORM_R96_SSA21</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">The current forms catalog routes the Submit Online action for this form into Upload Documents target 21.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_FORM_UPLOAD_06" source="FORM_R96_SSA455OCRSM" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">R96REL_FORM_UPLOAD_06</data><data key="edge_source_entity_id">FORM_R96_SSA455OCRSM</data><data key="edge_relationship_type">submitted_via</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">The current forms catalog routes the Submit Online action for this form into Upload Documents target 455.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_KB_001" source="WORK_SSI_KB_DIARY" target="WORK_SSI_CRITICAL_BDAY"><data key="edge_relationship_id">R96REL_KB_001</data><data key="edge_source_entity_id">WORK_SSI_KB_DIARY</data><data key="edge_relationship_type">subtype_of</data><data key="edge_target_entity_id">WORK_SSI_CRITICAL_BDAY</data><data key="edge_operational_context">KB is one of the SSI critical birthday diaries and applies at age 18.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_KB_002" source="SYS_SSR" target="WORK_SSI_KB_DIARY"><data key="edge_relationship_id">R96REL_KB_002</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">holds_control</data><data key="edge_target_entity_id">WORK_SSI_KB_DIARY</data><data key="edge_operational_context">Current policy describes KB and priority-select diary states on the Supplemental Security Record.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_KB_003" source="DB_SSI_PE_ODS" target="WORK_SSI_KB_DIARY"><data key="edge_relationship_id">R96REL_KB_003</data><data key="edge_source_entity_id">DB_SSI_PE_ODS</data><data key="edge_relationship_type">selects_work_for</data><data key="edge_target_entity_id">WORK_SSI_KB_DIARY</data><data key="edge_operational_context">PE ODS selects records with a KB diary as profile-K scheduled redeterminations in the month of age 18.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_KB_004" source="WORK_SSI_KB_DIARY" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">R96REL_KB_004</data><data key="edge_source_entity_id">WORK_SSI_KB_DIARY</data><data key="edge_relationship_type">triggers_processing_in</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Cases in the SSI Claims system are redetermined there when the KB diary matures.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_QR_001" source="ORG_DIGITAL_SERVICES_ENGAGEMENT" target="DATA_NOTICE_QR_CODE"><data key="edge_relationship_id">R96REL_QR_001</data><data key="edge_source_entity_id">ORG_DIGITAL_SERVICES_ENGAGEMENT</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">DATA_NOTICE_QR_CODE</data><data key="edge_operational_context">SSA states all QR codes for agency notices are created by the Digital Services Engagement Team.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_QR_002" source="APP_DIGITAL_SERVICES_CONTROL" target="DATA_NOTICE_QR_CODE"><data key="edge_relationship_id">R96REL_QR_002</data><data key="edge_source_entity_id">APP_DIGITAL_SERVICES_CONTROL</data><data key="edge_relationship_type">captures_request_for</data><data key="edge_target_entity_id">DATA_NOTICE_QR_CODE</data><data key="edge_operational_context">Digital Services produces QR codes based on information submitted through the Digital Services Control System - Request QR code/link.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_QR_003" source="PROC_NOTICE_QR_REPLACE" target="DATA_NOTICE_QR_CODE"><data key="edge_relationship_id">R96REL_QR_003</data><data key="edge_source_entity_id">PROC_NOTICE_QR_REPLACE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_NOTICE_QR_CODE</data><data key="edge_operational_context">The notice modernization process replaces eligible paper enclosures with QR codes that connect users to online content.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_QR_004" source="APP_T2R" target="DATA_NOTICE_QR_CODE"><data key="edge_relationship_id">R96REL_QR_004</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">incorporates</data><data key="edge_target_entity_id">DATA_NOTICE_QR_CODE</data><data key="edge_operational_context">POMS lists Title II redesign notices and post-entitlement notices among existing agency uses of QR codes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_ROM_001" source="ORG_SSA_ISB" target="FORM_US_ROMANIA_COC_US"><data key="edge_relationship_id">R96REL_ROM_001</data><data key="edge_source_entity_id">ORG_SSA_ISB</data><data key="edge_relationship_type">receives_requests_for</data><data key="edge_target_entity_id">FORM_US_ROMANIA_COC_US</data><data key="edge_operational_context">SSA directs U.S. certificate-of-coverage requests to the International Support Branch.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_ROM_002" source="SVC_OPTS_COC" target="FORM_US_ROMANIA_COC_US"><data key="edge_relationship_id">R96REL_ROM_002</data><data key="edge_source_entity_id">SVC_OPTS_COC</data><data key="edge_relationship_type">accepts_requests_for</data><data key="edge_target_entity_id">FORM_US_ROMANIA_COC_US</data><data key="edge_operational_context">Employers and self-employed persons may submit U.S. certificate-of-coverage requests online at opts.ssa.gov.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_ROM_003" source="ORG_ROMANIA_NHPP" target="FORM_US_ROMANIA_COC_RO"><data key="edge_relationship_id">R96REL_ROM_003</data><data key="edge_source_entity_id">ORG_ROMANIA_NHPP</data><data key="edge_relationship_type">issues</data><data key="edge_target_entity_id">FORM_US_ROMANIA_COC_RO</data><data key="edge_operational_context">The Romanian National House of Public Pensions issues certificates of Romanian coverage.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_ROM_004" source="FORM_US_ROMANIA_COC_US" target="EX_US_ROMANIA_TOTALIZATION"><data key="edge_relationship_id">R96REL_ROM_004</data><data key="edge_source_entity_id">FORM_US_ROMANIA_COC_US</data><data key="edge_relationship_type">documents_coverage_under</data><data key="edge_target_entity_id">EX_US_ROMANIA_TOTALIZATION</data><data key="edge_operational_context">The U.S. certificate documents coverage and exemption under the bilateral agreement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_ROM_005" source="FORM_US_ROMANIA_COC_RO" target="EX_US_ROMANIA_TOTALIZATION"><data key="edge_relationship_id">R96REL_ROM_005</data><data key="edge_source_entity_id">FORM_US_ROMANIA_COC_RO</data><data key="edge_relationship_type">documents_coverage_under</data><data key="edge_target_entity_id">EX_US_ROMANIA_TOTALIZATION</data><data key="edge_operational_context">The Romanian certificate documents coverage and exemption under the bilateral agreement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_RR_001" source="APP_ICERS" target="PROC_DCR_RR_DUAL"><data key="edge_relationship_id">R96REL_RR_001</data><data key="edge_source_entity_id">APP_ICERS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_DCR_RR_DUAL</data><data key="edge_operational_context">Field-office staff review ICERS and/or MCS earnings information to determine whether RRB medical evidence is available in career railroad disability cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_RR_002" source="ORG_RRB" target="DATA_RRB_MEDICAL_EVIDENCE"><data key="edge_relationship_id">R96REL_RR_002</data><data key="edge_source_entity_id">ORG_RRB</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_RRB_MEDICAL_EVIDENCE</data><data key="edge_operational_context">RRB agrees to furnish its medical evidence to SSA on request to avoid duplicate development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_RR_003" source="DATA_RRB_MEDICAL_EVIDENCE" target="PROC_DCR_RR_DUAL"><data key="edge_relationship_id">R96REL_RR_003</data><data key="edge_source_entity_id">DATA_RRB_MEDICAL_EVIDENCE</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">PROC_DCR_RR_DUAL</data><data key="edge_operational_context">Railroad medical evidence obtained from RRB is used in the disability case routed to DCR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_RR_004" source="APP_MCS" target="WORK_DDSDEC"><data key="edge_relationship_id">R96REL_RR_004</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">carries_work_control</data><data key="edge_target_entity_id">WORK_DDSDEC</data><data key="edge_operational_context">Current policy requires a DDSDEC issue and 90-day tickle on the MCS Development Worksheet for railroad cases sent to DCR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_RR_005" source="APP_CCE" target="WORK_DDSDEC"><data key="edge_relationship_id">R96REL_RR_005</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">carries_work_control</data><data key="edge_target_entity_id">WORK_DDSDEC</data><data key="edge_operational_context">Current policy requires a DDSDEC issue and 90-day tickle on the CCE Development Worksheet for railroad cases sent to DCR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_RR_006" source="WORK_DDSDEC" target="PROC_DCR_RR_DUAL"><data key="edge_relationship_id">R96REL_RR_006</data><data key="edge_source_entity_id">WORK_DDSDEC</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">PROC_DCR_RR_DUAL</data><data key="edge_operational_context">DDSDEC is the development control used for the railroad-disability DCR routing workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_T2R_001" source="APP_MYCOA" target="NOTICE_T2R_COA_CONFIRM"><data key="edge_relationship_id">R96REL_T2R_001</data><data key="edge_source_entity_id">APP_MYCOA</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">NOTICE_T2R_COA_CONFIRM</data><data key="edge_operational_context">An internet change of address through my Social Security triggers the T2R confirmation notice.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_T2R_002" source="APP_T2R" target="DATA_T2R_COA_XML"><data key="edge_relationship_id">R96REL_T2R_002</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_T2R_COA_XML</data><data key="edge_operational_context">Since October 2022, T2R notice software generates a COA XML file for fully composed notices.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_T2R_003" source="DATA_T2R_COA_XML" target="APP_CCM"><data key="edge_relationship_id">R96REL_T2R_003</data><data key="edge_source_entity_id">DATA_T2R_COA_XML</data><data key="edge_relationship_type">consumed_by</data><data key="edge_target_entity_id">APP_CCM</data><data key="edge_operational_context">The T2R COA XML file is used by Customer Communications Management to generate fully composed change-of-address notices.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_T2R_004" source="APP_CCM" target="NOTICE_T2R_COA_CONFIRM"><data key="edge_relationship_id">R96REL_T2R_004</data><data key="edge_source_entity_id">APP_CCM</data><data key="edge_relationship_type">composes</data><data key="edge_target_entity_id">NOTICE_T2R_COA_CONFIRM</data><data key="edge_operational_context">CCM generates the fully composed T2R COA notice from the XML file.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_T2R_005" source="NOTICE_T2R_COA_CONFIRM" target="DATA_MBR_MAILING_ADDRESS"><data key="edge_relationship_id">R96REL_T2R_005</data><data key="edge_source_entity_id">NOTICE_T2R_COA_CONFIRM</data><data key="edge_relationship_type">uses_delivery_address_from</data><data key="edge_target_entity_id">DATA_MBR_MAILING_ADDRESS</data><data key="edge_operational_context">The notice is sent to the old mailing address on the MBR, which may belong to the beneficiary or representative payee.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_T2R_006" source="APP_T2R" target="DATA_T2R_COA_ERROR_LOG"><data key="edge_relationship_id">R96REL_T2R_006</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">logs_incomplete_notice_to</data><data key="edge_target_entity_id">DATA_T2R_COA_ERROR_LOG</data><data key="edge_operational_context">Incomplete T2R COA notices are removed from the notice file and written to an error log for systems investigation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_T2R_007" source="DATA_T2R_COA_SKELCOMP" target="DATA_T2R_COA_XML"><data key="edge_relationship_id">R96REL_T2R_007</data><data key="edge_source_entity_id">DATA_T2R_COA_SKELCOMP</data><data key="edge_relationship_type">replaced_by</data><data key="edge_target_entity_id">DATA_T2R_COA_XML</data><data key="edge_operational_context">T2R stopped generating legacy SKELCOMP records in October 2022 and began generating XML for CCM.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_TOTAL_001" source="APP_MCS" target="DATA_MBR_TOTALIZATION_CODES"><data key="edge_relationship_id">R96REL_TOTAL_001</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_MBR_TOTALIZATION_CODES</data><data key="edge_operational_context">For U.S. Totalization claims, MCS screen entries systems-generate Totalization coding.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R96REL_TOTAL_002" source="SYS_MBR" target="DATA_MBR_TOTALIZATION_CODES"><data key="edge_relationship_id">R96REL_TOTAL_002</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_MBR_TOTALIZATION_CODES</data><data key="edge_operational_context">Systems-generated Totalization coding is posted to and retained on the MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL001" source="DATA_IAA_PACKAGE" target="FORM_SSA429"><data key="edge_relationship_id">R97REL001</data><data key="edge_source_entity_id">DATA_IAA_PACKAGE</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">FORM_SSA429</data><data key="edge_operational_context">SSA Data Exchange glossary defines Form SSA-429 as a component of the IAA package.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL002" source="DATA_IAA_PACKAGE" target="DOC_IAA_ADMIN_AGREEMENT"><data key="edge_relationship_id">R97REL002</data><data key="edge_source_entity_id">DATA_IAA_PACKAGE</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">DOC_IAA_ADMIN_AGREEMENT</data><data key="edge_operational_context">SSA Data Exchange glossary defines an administrative agreement identifying agreement provisions as an IAA-package component.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL003" source="DATA_IAA_PACKAGE" target="DOC_IAA_OGC_CLEARANCE"><data key="edge_relationship_id">R97REL003</data><data key="edge_source_entity_id">DATA_IAA_PACKAGE</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">DOC_IAA_OGC_CLEARANCE</data><data key="edge_operational_context">SSA Data Exchange glossary defines an OGC clearance memorandum as an IAA-package component.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL004" source="ORG_SSA_OGC" target="DOC_IAA_OGC_CLEARANCE"><data key="edge_relationship_id">R97REL004</data><data key="edge_source_entity_id">ORG_SSA_OGC</data><data key="edge_relationship_type">provides_clearance_via</data><data key="edge_target_entity_id">DOC_IAA_OGC_CLEARANCE</data><data key="edge_operational_context">SSA glossary identifies Office of the General Counsel clearance memorandum in the IAA package.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL005" source="UI_ERPS_ADD_NEW_ISSUE" target="APP_ERPS"><data key="edge_relationship_id">R97REL005</data><data key="edge_source_entity_id">UI_ERPS_ADD_NEW_ISSUE</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies Add New Issue as an eRPS screen used for follow-up diary control.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL006" source="UI_ERPS_ROC_DETAILS" target="APP_ERPS"><data key="edge_relationship_id">R97REL006</data><data key="edge_source_entity_id">UI_ERPS_ROC_DETAILS</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current POMS identifies Report of Contact Details as an eRPS screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL007" source="PROC_ERPS_QUESTIONABLE_PAYEE_FOLLOWUP" target="UI_ERPS_ADD_NEW_ISSUE"><data key="edge_relationship_id">R97REL007</data><data key="edge_source_entity_id">PROC_ERPS_QUESTIONABLE_PAYEE_FOLLOWUP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_ERPS_ADD_NEW_ISSUE</data><data key="edge_operational_context">Current POMS directs staff to use Add New Issue or another reliable diary control to establish the follow-up diary.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL008" source="PROC_ERPS_QUESTIONABLE_PAYEE_FOLLOWUP" target="WORK_ERPS_QUESTIONABLE_PAYEE_DIARY"><data key="edge_relationship_id">R97REL008</data><data key="edge_source_entity_id">PROC_ERPS_QUESTIONABLE_PAYEE_FOLLOWUP</data><data key="edge_relationship_type">establishes</data><data key="edge_target_entity_id">WORK_ERPS_QUESTIONABLE_PAYEE_DIARY</data><data key="edge_operational_context">Current POMS requires a follow-up diary for questionable representative-payee cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL009" source="WORK_ERPS_QUESTIONABLE_PAYEE_DIARY" target="UI_ERPS_ADD_NEW_ISSUE"><data key="edge_relationship_id">R97REL009</data><data key="edge_source_entity_id">WORK_ERPS_QUESTIONABLE_PAYEE_DIARY</data><data key="edge_relationship_type">may_be_managed_through</data><data key="edge_target_entity_id">UI_ERPS_ADD_NEW_ISSUE</data><data key="edge_operational_context">eRPS Add New Issue is an authorized method for establishing the diary; policy also permits another reliable control.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL010" source="PROC_ERPS_QUESTIONABLE_PAYEE_FOLLOWUP" target="UI_ERPS_ROC_DETAILS"><data key="edge_relationship_id">R97REL010</data><data key="edge_source_entity_id">PROC_ERPS_QUESTIONABLE_PAYEE_FOLLOWUP</data><data key="edge_relationship_type">records_findings_in</data><data key="edge_target_entity_id">UI_ERPS_ROC_DETAILS</data><data key="edge_operational_context">Current POMS directs staff to record personal-contact findings on an RC or the eRPS Report of Contact Details screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL011" source="DATA_ERPS_REP_PAYEE_APPLICANT_NOTE" target="UI_ERPS_MAKE_NOTE"><data key="edge_relationship_id">R97REL011</data><data key="edge_source_entity_id">DATA_ERPS_REP_PAYEE_APPLICANT_NOTE</data><data key="edge_relationship_type">created_through</data><data key="edge_target_entity_id">UI_ERPS_MAKE_NOTE</data><data key="edge_operational_context">Current representative-payee interview policy uses the eRPS Make Note screen with the Rep Payee Applicant Note Type.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL012" source="DATA_ERPS_REP_PAYEE_APPLICANT_NOTE" target="APP_ERPS"><data key="edge_relationship_id">R97REL012</data><data key="edge_source_entity_id">DATA_ERPS_REP_PAYEE_APPLICANT_NOTE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current policy treats the Rep Payee Applicant note as eRPS case documentation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Physical table/repository is not disclosed.</data></edge><edge id="R97REL013" source="PROC_SSI_ORAL_INQUIRY_PF" target="APP_ELAS"><data key="edge_relationship_id">R97REL013</data><data key="edge_source_entity_id">PROC_SSI_ORAL_INQUIRY_PF</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Current SSI protective-filing examples explicitly document oral-inquiry protective filing dates in eLAS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL014" source="PROC_SSI_ORAL_INQUIRY_PF" target="DATA_SSI_PROTECTIVE_FILING_DATE"><data key="edge_relationship_id">R97REL014</data><data key="edge_source_entity_id">PROC_SSI_ORAL_INQUIRY_PF</data><data key="edge_relationship_type">establishes</data><data key="edge_target_entity_id">DATA_SSI_PROTECTIVE_FILING_DATE</data><data key="edge_operational_context">An oral inquiry may establish a protected SSI filing date when policy criteria are met.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL015" source="DATA_SSI_PROTECTIVE_FILING_DATE" target="APP_ELAS"><data key="edge_relationship_id">R97REL015</data><data key="edge_source_entity_id">DATA_SSI_PROTECTIVE_FILING_DATE</data><data key="edge_relationship_type">documented_in</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Current POMS examples explicitly show the protective filing date documented in eLAS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Logical provenance relationship; public policy does not disclose physical field/storage implementation.</data></edge><edge id="R97REL016" source="APP_DMS_REMITTANCE" target="DATA_DMS_AUTOMATED_RECEIPT"><data key="edge_relationship_id">R97REL016</data><data key="edge_source_entity_id">APP_DMS_REMITTANCE</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_DMS_AUTOMATED_RECEIPT</data><data key="edge_operational_context">Current POMS states the automated receipt is the remitter's record of payment and is produced in DMS remittance processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL017" source="FORM_SSA1395_BK" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">R97REL017</data><data key="edge_source_entity_id">FORM_SSA1395_BK</data><data key="edge_relationship_type">fallback_for</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">SSA-1395-BK is used only when DMS is non-functional or unavailable.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL018" source="APP_DATS" target="PROC_DATS_DEATH_DEVELOPMENT"><data key="edge_relationship_id">R97REL018</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_DATS_DEATH_DEVELOPMENT</data><data key="edge_operational_context">Current DATS policy uses the alert and alleged death information to control unresolved death development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL019" source="PROC_DATS_DEATH_DEVELOPMENT" target="FORM_SSA2708"><data key="edge_relationship_id">R97REL019</data><data key="edge_source_entity_id">PROC_DATS_DEATH_DEVELOPMENT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA2708</data><data key="edge_operational_context">When initial contact cannot verify the death/alive status under the stated conditions, SSA sends SSA-2708.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL020" source="PROC_DATS_DEATH_DEVELOPMENT" target="WORK_DATS_DEATH_DEV_45D"><data key="edge_relationship_id">R97REL020</data><data key="edge_source_entity_id">PROC_DATS_DEATH_DEVELOPMENT</data><data key="edge_relationship_type">establishes</data><data key="edge_target_entity_id">WORK_DATS_DEATH_DEV_45D</data><data key="edge_operational_context">Current POMS directs staff to set a 45-day diary after sending SSA-2708.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL021" source="PROC_DATS_DEATH_DEVELOPMENT" target="APP_DIPS"><data key="edge_relationship_id">R97REL021</data><data key="edge_source_entity_id">PROC_DATS_DEATH_DEVELOPMENT</data><data key="edge_relationship_type">may_result_in_input_to</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">After 45 days without response or proof, current POMS directs staff to input the alleged death through DIPS as a non-responder on death development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL022" source="ORG_SSA_OCACT" target="DATA_OACT_BEN_BY_AGE"><data key="edge_relationship_id">R97REL022</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_BEN_BY_AGE</data><data key="edge_operational_context">OACT publishes the beneficiaries-by-age public product.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL023" source="ORG_SSA_OCACT" target="DATA_OACT_RETIRED_AGE_SEX_202606"><data key="edge_relationship_id">R97REL023</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_RETIRED_AGE_SEX_202606</data><data key="edge_operational_context">OACT publishes the June 2026 retired-worker age/sex table.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R97REL024" source="ORG_SSA_OCACT" target="DATA_OACT_CURRENT_PAYMENT_QUARTERLY"><data key="edge_relationship_id">R97REL024</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_CURRENT_PAYMENT_QUARTERLY</data><data key="edge_operational_context">OACT publishes the quarterly current-payment-status series.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL001" source="APP_REACT" target="ALERT_PREPARE1184_REACT"><data key="edge_relationship_id">R98REL001</data><data key="edge_source_entity_id">APP_REACT</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">ALERT_PREPARE1184_REACT</data><data key="edge_operational_context">Current POMS says the PSC receives a PREPARE 1184 REACT alert when a manual F-stop is needed on a courtesy check.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Work-control relationship; physical queue transport is not inferred.</data></edge><edge id="R98REL002" source="ALERT_PREPARE1184_REACT" target="PROC_MANUAL_FSTOP"><data key="edge_relationship_id">R98REL002</data><data key="edge_source_entity_id">ALERT_PREPARE1184_REACT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">PROC_MANUAL_FSTOP</data><data key="edge_operational_context">The PREPARE 1184 REACT alert prompts PSC manual F-stop action.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL003" source="UI_PESP_STOP_PAYMENT" target="PROC_MANUAL_FSTOP"><data key="edge_relationship_id">R98REL003</data><data key="edge_source_entity_id">UI_PESP_STOP_PAYMENT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MANUAL_FSTOP</data><data key="edge_operational_context">POMS identifies PESP input screens as a Title II path for entering a manual F-stop.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">UI/workflow relationship; no database inference.</data></edge><edge id="R98REL004" source="APP_MAMPSC_SSA4510" target="PROC_MANUAL_FSTOP"><data key="edge_relationship_id">R98REL004</data><data key="edge_source_entity_id">APP_MAMPSC_SSA4510</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MANUAL_FSTOP</data><data key="edge_operational_context">POMS identifies the MAMPSC Data Input Web Application (SSA-4510) as a processing-center path for entering Title II F-stops.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">No transport to Treasury is inferred.</data></edge><edge id="R98REL005" source="PROC_MANUAL_FSTOP" target="SVC_TCIS"><data key="edge_relationship_id">R98REL005</data><data key="edge_source_entity_id">PROC_MANUAL_FSTOP</data><data key="edge_relationship_type">results_available_in</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">Treasury F-stop status and claims-package information are made available to SSA through TCIS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow result relationship; not a direct application interface claim.</data></edge><edge id="R98REL006" source="IFACE_SSI_DIRECT_SSR" target="PROC_MANUAL_FSTOP"><data key="edge_relationship_id">R98REL006</data><data key="edge_source_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MANUAL_FSTOP</data><data key="edge_operational_context">For specified Title XVI courtesy/one-time-payment nonreceipt cases, current POMS directs the FO to enter the manual F-stop through SSI Claims System Direct SSR Update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL007" source="PROC_MANUAL_FSTOP" target="PROC_AOTP"><data key="edge_relationship_id">R98REL007</data><data key="edge_source_entity_id">PROC_MANUAL_FSTOP</data><data key="edge_relationship_type">can_apply_to</data><data key="edge_target_entity_id">PROC_AOTP</data><data key="edge_operational_context">Current POMS documents a Title XVI manual F-stop against a replacement Automated One-Time Payment in the specified courtesy-payment scenario.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL008" source="ORG_BFS" target="DATA_CORE_DAILY_DEATH_FILE"><data key="edge_relationship_id">R98REL008</data><data key="edge_source_entity_id">ORG_BFS</data><data key="edge_relationship_type">sends</data><data key="edge_target_entity_id">DATA_CORE_DAILY_DEATH_FILE</data><data key="edge_operational_context">Current CORE policy says Fiscal Service sends the daily death-information file to the Federal Reserve Bank handling CORE after SSA reports the payee death.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">File transport and format are not disclosed.</data></edge><edge id="R98REL009" source="DATA_CORE_DAILY_DEATH_FILE" target="SVC_TCORE"><data key="edge_relationship_id">R98REL009</data><data key="edge_source_entity_id">DATA_CORE_DAILY_DEATH_FILE</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">SVC_TCORE</data><data key="edge_operational_context">CORE matches death information in the Fiscal Service daily file against checks presented for payment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL010" source="SVC_TCORE" target="ORG_FRBKC"><data key="edge_relationship_id">R98REL010</data><data key="edge_source_entity_id">SVC_TCORE</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_FRBKC</data><data key="edge_operational_context">Current 2026 POMS explicitly states CORE is now handled by the Kansas City Federal Reserve Bank.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Historical Richmond implementation remains preserved in notes/history.</data></edge><edge id="R98REL011" source="SVC_TCORE" target="DATA_PHUS_EVENT070"><data key="edge_relationship_id">R98REL011</data><data key="edge_source_entity_id">SVC_TCORE</data><data key="edge_relationship_type">produces_credit_recorded_as</data><data key="edge_target_entity_id">DATA_PHUS_EVENT070</data><data key="edge_operational_context">In a Title II erroneous-death scenario, current POMS directs staff to review PHUS Event Code 070 to ensure the CORE/Treasury credit has been returned.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Operational credit-record relationship; no direct technical interface beyond the documented record result is inferred.</data></edge><edge id="R98REL012" source="DATA_PHUS_EVENT070" target="DB_PHUS"><data key="edge_relationship_id">R98REL012</data><data key="edge_source_entity_id">DATA_PHUS_EVENT070</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">Event Code 070 is reviewed on PHUS in the documented CORE erroneous-death workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL013" source="DATA_MBR_SPA_LINE" target="SYS_MBR"><data key="edge_relationship_id">R98REL013</data><data key="edge_source_entity_id">DATA_MBR_SPA_LINE</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS expressly identifies the Special Payment Amount line as part of the MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL014" source="SVC_TCORE" target="DATA_MBR_SPA_LINE"><data key="edge_relationship_id">R98REL014</data><data key="edge_source_entity_id">SVC_TCORE</data><data key="edge_relationship_type">related_returned_check_amount_may_post_to</data><data key="edge_target_entity_id">DATA_MBR_SPA_LINE</data><data key="edge_operational_context">POMS says a returned check issued after death can be placed on the MBR SPA line when benefits are suspended in the documented post-death context.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Conditional business-rule relationship.</data></edge><edge id="R98REL015" source="DATA_SSR_PAYFLAG3" target="SYS_SSR"><data key="edge_relationship_id">R98REL015</data><data key="edge_source_entity_id">DATA_SSR_PAYFLAG3</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current CORE instructions direct staff to inspect pay flag 3 on the SSR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL016" source="DATA_SSI_PTAC" target="SYS_SSR"><data key="edge_relationship_id">R98REL016</data><data key="edge_source_entity_id">DATA_SSI_PTAC</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current CORE erroneous-death instructions say the P-TAC remains on the SSR to balance the credit.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL017" source="DATA_SSI_DTAC" target="SYS_SSR"><data key="edge_relationship_id">R98REL017</data><data key="edge_source_entity_id">DATA_SSI_DTAC</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current CORE erroneous-death instructions direct staff to post a D-TAC to prevent the underpayment from release.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL018" source="ORG_RECLAMATIONS_TEAM" target="DATA_SSR_PAYFLAG3"><data key="edge_relationship_id">R98REL018</data><data key="edge_source_entity_id">ORG_RECLAMATIONS_TEAM</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_SSR_PAYFLAG3</data><data key="edge_operational_context">Current POMS says Reclamations overlays pay flag 3 from S to U before issuing the required special-voucher reimbursement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Human/operational update; application mechanism is not disclosed.</data></edge><edge id="R98REL019" source="ORG_RECLAMATIONS_TEAM" target="PROC_SSI_SPECIAL_VOUCHER"><data key="edge_relationship_id">R98REL019</data><data key="edge_source_entity_id">ORG_RECLAMATIONS_TEAM</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_SSI_SPECIAL_VOUCHER</data><data key="edge_operational_context">Current POMS directs staff to contact Reclamations to issue a special voucher payment to the party owed money.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL020" source="PROC_SSI_SPECIAL_VOUCHER" target="SVC_TCORE"><data key="edge_relationship_id">R98REL020</data><data key="edge_source_entity_id">PROC_SSI_SPECIAL_VOUCHER</data><data key="edge_relationship_type">resolves_erroneous_death_credit_from</data><data key="edge_target_entity_id">SVC_TCORE</data><data key="edge_operational_context">Special voucher procedures reimburse the party owed money after a CORE erroneous-death credit prevents the presenting institution from being paid.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Business-process relationship; internal disbursement application is not identified.</data></edge><edge id="R98REL021" source="DATA_SSI_PTAC" target="PROC_SSI_SPECIAL_VOUCHER"><data key="edge_relationship_id">R98REL021</data><data key="edge_source_entity_id">DATA_SSI_PTAC</data><data key="edge_relationship_type">used_in</data><data key="edge_target_entity_id">PROC_SSI_SPECIAL_VOUCHER</data><data key="edge_operational_context">In the no-S-pay-flag scenario, P-TAC is posted before the special-voucher reimbursement path.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL022" source="DATA_SSI_DTAC" target="PROC_SSI_SPECIAL_VOUCHER"><data key="edge_relationship_id">R98REL022</data><data key="edge_source_entity_id">DATA_SSI_DTAC</data><data key="edge_relationship_type">used_in</data><data key="edge_target_entity_id">PROC_SSI_SPECIAL_VOUCHER</data><data key="edge_operational_context">In the no-S-pay-flag scenario, D-TAC is posted to prevent underpayment release while special-voucher reimbursement is pursued.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL023" source="SVC_TCORE" target="APP_CPS"><data key="edge_relationship_id">R98REL023</data><data key="edge_source_entity_id">SVC_TCORE</data><data key="edge_relationship_type">can_require_correction_via</data><data key="edge_target_entity_id">APP_CPS</data><data key="edge_operational_context">In one Title II erroneous-death scenario, current POMS directs use of CPS after the bank debits the beneficiary account.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Conditional corrective-payment workflow, not a direct CORE-to-CPS integration.</data></edge><edge id="R98REL024" source="SVC_TCORE" target="APP_SPS"><data key="edge_relationship_id">R98REL024</data><data key="edge_source_entity_id">SVC_TCORE</data><data key="edge_relationship_type">can_require_reimbursement_via</data><data key="edge_target_entity_id">APP_SPS</data><data key="edge_operational_context">In another Title II erroneous-death scenario, current POMS directs SPS reimbursement to the financial institution after CORE returns the check unpaid.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Conditional corrective-payment workflow, not a direct CORE-to-SPS integration.</data></edge><edge id="R98REL025" source="FORM_SSA4968" target="APP_SSI_RMA"><data key="edge_relationship_id">R98REL025</data><data key="edge_source_entity_id">FORM_SSA4968</data><data key="edge_relationship_type">manual_calculation_alternative_to</data><data key="edge_target_entity_id">APP_SSI_RMA</data><data key="edge_operational_context">Current EAP policy allows the payment amount to be computed using the SSI RMA program or Form SSA-4968.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Functional alternative; no system interface is inferred.</data></edge><edge id="R98REL026" source="FORM_SSA4346U2" target="APP_ECOMPS"><data key="edge_relationship_id">R98REL026</data><data key="edge_source_entity_id">FORM_SSA4346U2</data><data key="edge_relationship_type">manual_fallback_for</data><data key="edge_target_entity_id">APP_ECOMPS</data><data key="edge_operational_context">POMS directs staff to use SSA-4346-U2 when eComputations is unavailable or cannot complete the required windfall-offset computation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL027" source="FORM_SSA4968" target="APP_ECOMPS"><data key="edge_relationship_id">R98REL027</data><data key="edge_source_entity_id">FORM_SSA4968</data><data key="edge_relationship_type">manual_fallback_for</data><data key="edge_target_entity_id">APP_ECOMPS</data><data key="edge_operational_context">POMS requires SSA-4968 when required computations cannot be completed in eComputations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL028" source="APP_ECOMPS" target="FORM_SSA4346U2"><data key="edge_relationship_id">R98REL028</data><data key="edge_source_entity_id">APP_ECOMPS</data><data key="edge_relationship_type">provides_electronic_equivalent_of</data><data key="edge_target_entity_id">FORM_SSA4346U2</data><data key="edge_operational_context">POMS states SSA-4346-U2 is equivalent to the Windfall Results, Windfall Offset, and Windfall Offset Summary tabs in eComputations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL029" source="APP_ECOMPS" target="FORM_SSA4968"><data key="edge_relationship_id">R98REL029</data><data key="edge_source_entity_id">APP_ECOMPS</data><data key="edge_relationship_type">provides_electronic_equivalent_of</data><data key="edge_target_entity_id">FORM_SSA4968</data><data key="edge_operational_context">POMS states SSA-4968 is equivalent to the Computational Results tab in eComputations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R98REL030" source="SVC_NCOA_LICENSED_VENDOR" target="DB_USPS_NCOA"><data key="edge_relationship_id">R98REL030</data><data key="edge_source_entity_id">SVC_NCOA_LICENSED_VENDOR</data><data key="edge_relationship_type">accesses</data><data key="edge_target_entity_id">DB_USPS_NCOA</data><data key="edge_operational_context">POMS states SSA address records are matched against USPS NCOA data through a licensed vendor.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Vendor identity and technical access mechanism are not disclosed.</data></edge><edge id="R98REL031" source="SVC_NCOA_LICENSED_VENDOR" target="PROC_NCOA_TITLEII"><data key="edge_relationship_id">R98REL031</data><data key="edge_source_entity_id">SVC_NCOA_LICENSED_VENDOR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_NCOA_TITLEII</data><data key="edge_operational_context">The unidentified licensed vendor performs the matching step used in the documented Title II NCOA process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">No vendor/product identity inferred.</data></edge><edge id="R99_REL001" source="DATA_MBR_SID_LINE" target="SYS_MBR"><data key="edge_relationship_id">R99_REL001</data><data key="edge_source_entity_id">DATA_MBR_SID_LINE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS identifies the SID line on the Master Beneficiary Record for state buy-in status.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL002" source="DATA_MBR_THIRD_PARTY_LINE" target="SYS_MBR"><data key="edge_relationship_id">R99_REL002</data><data key="edge_source_entity_id">DATA_MBR_THIRD_PARTY_LINE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS identifies a Third-Party line on MBR used for Medicare state buy-in/premium status.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL003" source="TXN_TYPE_M_OFFLINE_QUERY" target="PROC_SSR_MBR_FORCE_FINDER"><data key="edge_relationship_id">R99_REL003</data><data key="edge_source_entity_id">TXN_TYPE_M_OFFLINE_QUERY</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="edge_operational_context">FO requests a Type M offline query to force an SSR finder when correcting an SSR-MBR interface problem.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL004" source="PROC_SSR_MBR_FORCE_FINDER" target="SYS_SSR"><data key="edge_relationship_id">R99_REL004</data><data key="edge_source_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="edge_relationship_type">uses_record</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Forced finder process starts from an SSI query/SSR state and requires identifying data consistency with MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL005" source="PROC_SSR_MBR_FORCE_FINDER" target="SYS_MBR"><data key="edge_relationship_id">R99_REL005</data><data key="edge_source_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="edge_relationship_type">uses_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Forced finder correction requires identifying data on MBR and SSR to be consistent.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL006" source="PROC_SSR_MBR_FORCE_FINDER" target="DATA_MBR_SID_LINE"><data key="edge_relationship_id">R99_REL006</data><data key="edge_source_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_MBR_SID_LINE</data><data key="edge_operational_context">A successful forced finder corrects the MBR SID line.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL007" source="APP_TPS_BUYIN" target="DATA_MBR_SID_LINE"><data key="edge_relationship_id">R99_REL007</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">receives_followup_update_after</data><data key="edge_target_entity_id">DATA_MBR_SID_LINE</data><data key="edge_operational_context">After the SID line correction, POMS says TPS is updated on the 25th of the month.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL008" source="APP_TPS_BUYIN" target="DATA_MBR_THIRD_PARTY_LINE"><data key="edge_relationship_id">R99_REL008</data><data key="edge_source_entity_id">APP_TPS_BUYIN</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_MBR_THIRD_PARTY_LINE</data><data key="edge_operational_context">POMS says TPS updates the Third-Party line of the MBR by the following month.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL009" source="DATA_CMS1957" target="PROC_SSR_MBR_FORCE_FINDER"><data key="edge_relationship_id">R99_REL009</data><data key="edge_source_entity_id">DATA_CMS1957</data><data key="edge_relationship_type">used_as_fallback_for</data><data key="edge_target_entity_id">PROC_SSR_MBR_FORCE_FINDER</data><data key="edge_operational_context">POMS directs use of CMS-1957 or a headquarters correction request when the forced finder does not resolve the state buy-in problem.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL010" source="UI_MCS_STUD" target="APP_MCS"><data key="edge_relationship_id">R99_REL010</data><data key="edge_source_entity_id">UI_MCS_STUD</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Student Entitlement (STUD) is the MCS processing screen referenced by current student-benefit POMS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL011" source="FORM_SSA1372" target="DATA_STUDENT_EXPECTED_GRAD_DATE"><data key="edge_relationship_id">R99_REL011</data><data key="edge_source_entity_id">FORM_SSA1372</data><data key="edge_relationship_type">supplies</data><data key="edge_target_entity_id">DATA_STUDENT_EXPECTED_GRAD_DATE</data><data key="edge_operational_context">SSA-1372 supplies the expected graduation date used to code STUD.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL012" source="FORM_SSA1372" target="DATA_STUDENT_SCHOOL_OPERATING_BASIS"><data key="edge_relationship_id">R99_REL012</data><data key="edge_source_entity_id">FORM_SSA1372</data><data key="edge_relationship_type">supplies</data><data key="edge_target_entity_id">DATA_STUDENT_SCHOOL_OPERATING_BASIS</data><data key="edge_operational_context">The school official certifies school operating basis on SSA-1372 for STUD coding and termination rules.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL013" source="UI_MCS_STUD" target="DATA_STUDENT_EXPECTED_GRAD_DATE"><data key="edge_relationship_id">R99_REL013</data><data key="edge_source_entity_id">UI_MCS_STUD</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">DATA_STUDENT_EXPECTED_GRAD_DATE</data><data key="edge_operational_context">POMS directs staff to code STUD based on the expected graduation date.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL014" source="UI_MCS_STUD" target="DATA_STUDENT_SCHOOL_OPERATING_BASIS"><data key="edge_relationship_id">R99_REL014</data><data key="edge_source_entity_id">UI_MCS_STUD</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">DATA_STUDENT_SCHOOL_OPERATING_BASIS</data><data key="edge_operational_context">POMS directs staff to enter the school operating basis on STUD as certified by the school official.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL015" source="UI_MCS_STUD" target="DATA_MBR_STUDENT_ENTITLEMENT"><data key="edge_relationship_id">R99_REL015</data><data key="edge_source_entity_id">UI_MCS_STUD</data><data key="edge_relationship_type">posts_student_data_to</data><data key="edge_target_entity_id">DATA_MBR_STUDENT_ENTITLEMENT</data><data key="edge_operational_context">Student entitlement processing posts student data used to prevent automatic age-18 termination.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL016" source="DATA_MBR_STUDENT_ENTITLEMENT" target="SYS_MBR"><data key="edge_relationship_id">R99_REL016</data><data key="edge_source_entity_id">DATA_MBR_STUDENT_ENTITLEMENT</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS states student data must be posted to the Master Beneficiary Record to continue benefits past age 18.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL017" source="FORM_SSA1372" target="REPO_NDRED"><data key="edge_relationship_id">R99_REL017</data><data key="edge_source_entity_id">FORM_SSA1372</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Current student-benefit POMS directs staff to fax SSA-1372 into NDRed using Evidence Portal or eView/eDIB and destroy the paper after verifying content.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL018" source="UI_DMS_DROA" target="APP_DMS"><data key="edge_relationship_id">R99_REL018</data><data key="edge_source_entity_id">UI_DMS_DROA</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Current POMS names DROA as a DMS screen used to resume recovery.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL019" source="PROC_T2_OVERPAY_EXPL" target="UI_DMS_DROA"><data key="edge_relationship_id">R99_REL019</data><data key="edge_source_entity_id">PROC_T2_OVERPAY_EXPL</data><data key="edge_relationship_type">resumes_collection_via</data><data key="edge_target_entity_id">UI_DMS_DROA</data><data key="edge_operational_context">After the explanation notice, staff use DMS DROA to resume collection in the current operating month plus three months when applicable.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL020" source="DATA_DMS_EXPLANATION_PROTEST_REASON" target="APP_DMS"><data key="edge_relationship_id">R99_REL020</data><data key="edge_source_entity_id">DATA_DMS_EXPLANATION_PROTEST_REASON</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">The explanation protest reason is coded in DMS to suspend recovery while a detailed explanation is developed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL021" source="IFACE_DRPF" target="DATA_DMS_EXPLANATION_PROTEST_REASON"><data key="edge_relationship_id">R99_REL021</data><data key="edge_source_entity_id">IFACE_DRPF</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">DATA_DMS_EXPLANATION_PROTEST_REASON</data><data key="edge_operational_context">FO uses DRPF with the explanation protest reason when PSC assistance is required.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL022" source="IFACE_DRPR" target="DATA_DMS_EXPLANATION_PROTEST_REASON"><data key="edge_relationship_id">R99_REL022</data><data key="edge_source_entity_id">IFACE_DRPR</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">DATA_DMS_EXPLANATION_PROTEST_REASON</data><data key="edge_operational_context">PSC uses DRPR with the explanation protest reason to stop recovery when applicable.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL023" source="DATA_SSR_GRC" target="SYS_SSR"><data key="edge_relationship_id">R99_REL023</data><data key="edge_source_entity_id">DATA_SSR_GRC</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says an FO or automated interface adds a pending grant reimbursement code to the SSR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL024" source="DATA_SSR_UPV_V" target="SYS_SSR"><data key="edge_relationship_id">R99_REL024</data><data key="edge_source_entity_id">DATA_SSR_UPV_V</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS describes UPV:V as an SSR underpayment verification code used in the IAR hold workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL025" source="DATA_SSR_GRC" target="PROC_SSI_IAR_UNDERPAYMENT_HOLD"><data key="edge_relationship_id">R99_REL025</data><data key="edge_source_entity_id">DATA_SSR_GRC</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">PROC_SSI_IAR_UNDERPAYMENT_HOLD</data><data key="edge_operational_context">Adding the pending GRC causes the system to hold the entire underpayment while IAR is processed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL026" source="PROC_SSI_IAR_UNDERPAYMENT_HOLD" target="DATA_SSR_UPV_V"><data key="edge_relationship_id">R99_REL026</data><data key="edge_source_entity_id">PROC_SSI_IAR_UNDERPAYMENT_HOLD</data><data key="edge_relationship_type">sets_hold_via</data><data key="edge_target_entity_id">DATA_SSR_UPV_V</data><data key="edge_operational_context">The system holds the underpayment with UPV:V during IAR processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL027" source="APP_EIAR" target="PROC_SSI_IAR_UNDERPAYMENT_HOLD"><data key="edge_relationship_id">R99_REL027</data><data key="edge_source_entity_id">APP_EIAR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_SSI_IAR_UNDERPAYMENT_HOLD</data><data key="edge_operational_context">States submit reimbursement requests through eIAR; reimbursement can occur automatically before remaining underpayment is released.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL028" source="UI_SSI_UOUP" target="IFACE_SSI_DIRECT_SSR"><data key="edge_relationship_id">R99_REL028</data><data key="edge_source_entity_id">UI_SSI_UOUP</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_operational_context">POMS identifies UOUP as an Underpayment Processing screen accessed through Direct SSR Update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL029" source="UI_SSI_UOUP" target="PROC_SSI_IAR_UNDERPAYMENT_HOLD"><data key="edge_relationship_id">R99_REL029</data><data key="edge_source_entity_id">UI_SSI_UOUP</data><data key="edge_relationship_type">supports_prepaid_review_for</data><data key="edge_target_entity_id">PROC_SSI_IAR_UNDERPAYMENT_HOLD</data><data key="edge_operational_context">For specified large underpayments, the FO completes prepayment review and release selection through UOUP.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL030" source="FORM_SSA872" target="ORG_DDS"><data key="edge_relationship_id">R99_REL030</data><data key="edge_source_entity_id">FORM_SSA872</data><data key="edge_relationship_type">authorizes_federal_obligations_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">SSA-872 authorizes State disability agencies to incur obligations against Federal funds for approved necessary expenses.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL031" source="PROC_DDS_STATE_FUNDING_AUTH" target="FORM_SSA872"><data key="edge_relationship_id">R99_REL031</data><data key="edge_source_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA872</data><data key="edge_operational_context">SSA provides State funding authorization through SSA-872 on a quarterly or six-to-eight-week basis.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL032" source="PROC_DDS_STATE_FUNDING_AUTH" target="ORG_DDS"><data key="edge_relationship_id">R99_REL032</data><data key="edge_source_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="edge_relationship_type">funds</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">The process provides pre-authorized Federal funds for State disability program operations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL033" source="SVC_ASAP" target="PROC_DDS_STATE_FUNDING_AUTH"><data key="edge_relationship_id">R99_REL033</data><data key="edge_source_entity_id">SVC_ASAP</data><data key="edge_relationship_type">executes_drawdown_for</data><data key="edge_target_entity_id">PROC_DDS_STATE_FUNDING_AUTH</data><data key="edge_operational_context">State agencies use Treasury ASAP to draw funds pre-authorized for payment.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL034" source="PROC_SDX_1619_MEDICAID_NOTIFY" target="EX_SDX"><data key="edge_relationship_id">R99_REL034</data><data key="edge_source_entity_id">PROC_SDX_1619_MEDICAID_NOTIFY</data><data key="edge_relationship_type">uses_exchange</data><data key="edge_target_entity_id">EX_SDX</data><data key="edge_operational_context">SSA notifies States about section 1619 continuation-group members through SDX.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL035" source="PROC_SDX_1619_MEDICAID_NOTIFY" target="ORG_STATES"><data key="edge_relationship_id">R99_REL035</data><data key="edge_source_entity_id">PROC_SDX_1619_MEDICAID_NOTIFY</data><data key="edge_relationship_type">notifies</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">The SDX notification informs State Medicaid administration about qualifying section 1619 continuation groups.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL036" source="PROC_VENDOR_REPO_SUBMISSION" target="REPO_SSA_VENDOR"><data key="edge_relationship_id">R99_REL036</data><data key="edge_source_entity_id">PROC_VENDOR_REPO_SUBMISSION</data><data key="edge_relationship_type">populates</data><data key="edge_target_entity_id">REPO_SSA_VENDOR</data><data key="edge_operational_context">SSA vendor-submission instructions say accepted vendor information is added to the repository for market research.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL037" source="REPO_SSA_VENDOR" target="DATA_VENDOR_CAPABILITY_STATEMENT"><data key="edge_relationship_id">R99_REL037</data><data key="edge_source_entity_id">REPO_SSA_VENDOR</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_VENDOR_CAPABILITY_STATEMENT</data><data key="edge_operational_context">Vendor information/capability submissions are retained in the SSA vendor repository for market research.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL038" source="REPO_SSA_VENDOR" target="ORG_SSA_OAG"><data key="edge_relationship_id">R99_REL038</data><data key="edge_source_entity_id">REPO_SSA_VENDOR</data><data key="edge_relationship_type">supports_market_research_by</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">SSA says the repository is available to SSA personnel for market research; OAG publishes and administers the vendor instructions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL039" source="FORM_SF270" target="SVC_ASAP"><data key="edge_relationship_id">R99_REL039</data><data key="edge_source_entity_id">FORM_SF270</data><data key="edge_relationship_type">interim_payment_request_when_setup_pending_for</data><data key="edge_target_entity_id">SVC_ASAP</data><data key="edge_operational_context">SSA requires grant recipients to establish ASAP payment accounts and permits emailed SF-270 requests in the interim.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL040" source="FORM_SF425" target="ORG_SSA_OAG"><data key="edge_relationship_id">R99_REL040</data><data key="edge_source_entity_id">FORM_SF425</data><data key="edge_relationship_type">reports_grant_finances_to</data><data key="edge_target_entity_id">ORG_SSA_OAG</data><data key="edge_operational_context">SSA OAG provides SF-425 guidance for award financial reporting, including recipient share/cost share.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL041" source="WORK_MCS_PROTFL" target="APP_MCS"><data key="edge_relationship_id">R99_REL041</data><data key="edge_source_entity_id">WORK_MCS_PROTFL</data><data key="edge_relationship_type">work_control_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">PROTFL is a Development Worksheet issue in the MCS Title II filing-date workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL042" source="WORK_MCS_PROTFL" target="DATA_TITLE2_APP_FILING_DATE"><data key="edge_relationship_id">R99_REL042</data><data key="edge_source_entity_id">WORK_MCS_PROTFL</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">DATA_TITLE2_APP_FILING_DATE</data><data key="edge_operational_context">The PROTFL request date must reflect the earliest possible protective filing date.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL043" source="APP_MCS" target="DATA_TITLE2_APP_FILING_DATE"><data key="edge_relationship_id">R99_REL043</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">can_set_protective_filing_as</data><data key="edge_target_entity_id">DATA_TITLE2_APP_FILING_DATE</data><data key="edge_operational_context">Current POMS says MCS allows a protective filing date to show as the filing date on MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL044" source="DATA_TITLE2_APP_FILING_DATE" target="SYS_MBR"><data key="edge_relationship_id">R99_REL044</data><data key="edge_source_entity_id">DATA_TITLE2_APP_FILING_DATE</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS explicitly says the protective filing date can show as the date of filing on the MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="R99_REL045" source="ORG_SSA_OCACT" target="DATA_OACT_FACT_SHEET_20260630"><data key="edge_relationship_id">R99_REL045</data><data key="edge_source_entity_id">ORG_SSA_OCACT</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">DATA_OACT_FACT_SHEET_20260630</data><data key="edge_operational_context">OACT publishes the June 30, 2026 Fact Sheet summarizing program coverage, benefits, and OASI/DI trust-fund operations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">No unpublished production pipeline inferred.</data></edge><edge id="REL001" source="APP_MCS" target="APP_EDCS"><data key="edge_relationship_id">REL001</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS mainframe data propagation</data><data key="edge_observed_as_of">2025-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL002" source="APP_MSSICS" target="APP_EDCS"><data key="edge_relationship_id">REL002</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS mainframe data propagation</data><data key="edge_observed_as_of">2025-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL003" source="SYS_ICDB" target="APP_EDCS"><data key="edge_relationship_id">REL003</data><data key="edge_source_entity_id">SYS_ICDB</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS mainframe data propagation</data><data key="edge_observed_as_of">2025-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL004" source="SYS_NUMIDENT" target="APP_EDCS"><data key="edge_relationship_id">REL004</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS mainframe data propagation</data><data key="edge_observed_as_of">2025-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL005" source="SYS_SSR" target="APP_EDCS"><data key="edge_relationship_id">REL005</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS mainframe data propagation</data><data key="edge_observed_as_of">2025-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL006" source="SYS_MBR" target="APP_EDCS"><data key="edge_relationship_id">REL006</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">EDCS mainframe data propagation</data><data key="edge_observed_as_of">2025-04</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL007" source="APP_EDCS" target="APP_EVIEW"><data key="edge_relationship_id">REL007</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">creates_or_establishes_case_for</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Field office creates/transfers/determines EDCS case, establishing case in eView</data><data key="edge_observed_as_of">2025-01-03</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL008" source="APP_EVIEW" target="REPO_EF"><data key="edge_relationship_id">REL008</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">views_and_acts_on</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Disability case processing</data><data key="edge_observed_as_of">2025-01-03</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL009" source="REPO_CEF" target="REPO_EF"><data key="edge_relationship_id">REL009</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">is_certified_form_of</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Official electronic disability folder</data><data key="edge_observed_as_of">2019-03-15</data><data key="edge_confidence">4</data><data key="edge_notes">Direct official definition; concept remains in current POMS.</data></edge><edge id="REL010" source="APP_EP" target="REPO_NDRED"><data key="edge_relationship_id">REL010</data><data key="edge_source_entity_id">APP_EP</data><data key="edge_relationship_type">stores_documents_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Non-disability evidence storage</data><data key="edge_observed_as_of">2026-06-08</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL011" source="APP_DCPS" target="APP_UNIFORMS"><data key="edge_relationship_id">REL011</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">accesses</data><data key="edge_target_entity_id">APP_UNIFORMS</data><data key="edge_operational_context">DDS forms workflow</data><data key="edge_observed_as_of">2025-04-17</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL012" source="APP_UNIFORMS" target="REPO_CEF"><data key="edge_relationship_id">REL012</data><data key="edge_source_entity_id">APP_UNIFORMS</data><data key="edge_relationship_type">uploads_completed_forms_to</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DDS electronic disability folder</data><data key="edge_observed_as_of">2025-04-17</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL013" source="APP_EWORK" target="DB_DCF"><data key="edge_relationship_id">REL013</data><data key="edge_source_entity_id">APP_EWORK</data><data key="edge_relationship_type">creates_control_record_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Title II work CDR</data><data key="edge_observed_as_of">2026-05-08</data><data key="edge_confidence">5</data><data key="edge_notes">eWork establishes simultaneous T2 work CDR in DCF.</data></edge><edge id="REL014" source="APP_EWORK" target="DB_DCF"><data key="edge_relationship_id">REL014</data><data key="edge_source_entity_id">APP_EWORK</data><data key="edge_relationship_type">moves_case_with</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">Work CDR jurisdiction transfer</data><data key="edge_observed_as_of">2026-05-08</data><data key="edge_confidence">5</data><data key="edge_notes">eWork transfer automatically transfers DCF control.</data></edge><edge id="REL015" source="APP_DMS" target="SYS_MBR"><data key="edge_relationship_id">REL015</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">posts_special_message_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Fraud-related overpayment handling</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">4</data><data key="edge_notes">Direct official POMS; fresher corroboration pending.</data></edge><edge id="REL016" source="APP_DMS" target="APP_ROAR"><data key="edge_relationship_id">REL016</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">supports_or_contains</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">Overpayment accounting/recovery workflow</data><data key="edge_observed_as_of">2022-08-22</data><data key="edge_confidence">4</data><data key="edge_notes">POMS wording: ROAR's Debt Management System; exact product boundary pending.</data></edge><edge id="REL017" source="APP_EP" target="REPO_EF"><data key="edge_relationship_id">REL017</data><data key="edge_source_entity_id">APP_EP</data><data key="edge_relationship_type">searches_or_accesses</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Electronic disability case search/access</data><data key="edge_observed_as_of">2025-01-03</data><data key="edge_confidence">5</data><data key="edge_notes">Case selection can open eDib case in eView or EP.</data></edge><edge id="REL018" source="APP_DCPS" target="APP_EVIEW"><data key="edge_relationship_id">REL018</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">closes_case_with</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">eCDR case closure/routing</data><data key="edge_observed_as_of">2025-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">POMS states case is closed in DCPS, DDS legacy system, eView and NDDSS.</data></edge><edge id="REL019" source="APP_DCPS" target="APP_NDDSS"><data key="edge_relationship_id">REL019</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">closes_case_with</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_operational_context">eCDR case closure/routing</data><data key="edge_observed_as_of">2025-08-28</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL020" source="COMP_DMA" target="REPO_CEF"><data key="edge_relationship_id">REL020</data><data key="edge_source_entity_id">COMP_DMA</data><data key="edge_relationship_type">indexes_documents_into</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">Scanned/faxed disability evidence</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">DMA barcode associates and indexes documents in CEF.</data></edge><edge id="REL021" source="APP_CCE" target="REPO_NDRED"><data key="edge_relationship_id">REL021</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">records_title_xvi_case_notes_for</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Capability determination documentation</data><data key="edge_observed_as_of">2026-06-08</data><data key="edge_confidence">5</data><data key="edge_notes">CCE records where supporting evidence has been stored in NDRed/eView.</data></edge><edge id="REL022" source="APP_MCS" target="REPO_NDRED"><data key="edge_relationship_id">REL022</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">records_title_ii_case_notes_for</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Capability determination documentation</data><data key="edge_observed_as_of">2026-06-08</data><data key="edge_confidence">5</data><data key="edge_notes">MCS records where supporting evidence has been stored.</data></edge><edge id="REL023" source="APP_ERPS" target="REPO_NDRED"><data key="edge_relationship_id">REL023</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">documents_contacts_used_with</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Representative-payee capability evidence</data><data key="edge_observed_as_of">2026-06-08</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS links eRPS documentation with evidence storage.</data></edge><edge id="REL024" source="DB_DCF" target="APP_EWORK"><data key="edge_relationship_id">REL024</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">integrates_with</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">Post-entitlement disability/work control</data><data key="edge_observed_as_of">2014-05-02</data><data key="edge_confidence">4</data><data key="edge_notes">Historical descriptive POMS plus current 2026 operational corroboration.</data></edge><edge id="REL025" source="APP_PUPS" target="SYS_MBR"><data key="edge_relationship_id">REL025</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">cross_references</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Prisoner suspension/payment processing</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes">Current POMS instructs comparison of PUPS record with MBR fields.</data></edge><edge id="REL026" source="APP_DCPS" target="REPO_CEF"><data key="edge_relationship_id">REL026</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">writes_case_notes_used_in</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">DDS adjudication documentation</data><data key="edge_observed_as_of">2026-04-17</data><data key="edge_confidence">5</data><data key="edge_notes">Current SSA-827 workflow documents attestation in DCPS for electronic disability cases.</data></edge><edge id="REL027" source="APP_ENM" target="REPO_EF"><data key="edge_relationship_id">REL027</data><data key="edge_source_entity_id">APP_ENM</data><data key="edge_relationship_type">stores_nonmedical_hearing_records_for</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">OHO/OAO non-medical workflow</data><data key="edge_observed_as_of">2026-04-17</data><data key="edge_confidence">4</data><data key="edge_notes">ENM is used instead of EDCS/eView in specified OHO/OAO workflows; exact repository boundary needs more sourcing.</data></edge><edge id="REL100" source="EX_BEER" target="DOM_EARNINGS"><data key="edge_relationship_id">REL100</data><data key="edge_source_entity_id">EX_BEER</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Batch exchange to states</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1000" source="ORG_NAPHSIS" target="SVC_EVVE"><data key="edge_relationship_id">REL1000</data><data key="edge_source_entity_id">ORG_NAPHSIS</data><data key="edge_relationship_type">collaborated_on</data><data key="edge_target_entity_id">SVC_EVVE</data><data key="edge_operational_context">SSA POMS states EVVE resulted from collaboration between SSA and NAPHSIS.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1001" source="SVC_EVVE" target="ORG_STATE_BVS"><data key="edge_relationship_id">REL1001</data><data key="edge_source_entity_id">SVC_EVVE</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">EVVE queries participating states’ vital-record systems for birth-record verification.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1002" source="SVC_EVVE" target="APP_MCS"><data key="edge_relationship_id">REL1002</data><data key="edge_source_entity_id">SVC_EVVE</data><data key="edge_relationship_type">verification_documented_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">For claims, EVVE match results are documented in MCS when applicable.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow evidence; no direct interface protocol inferred.</data></edge><edge id="REL1003" source="SVC_EVVE" target="APP_MSSICS"><data key="edge_relationship_id">REL1003</data><data key="edge_source_entity_id">SVC_EVVE</data><data key="edge_relationship_type">verification_documented_in</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">For claims, EVVE match results are documented in MSSICS when applicable.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow evidence; no direct interface protocol inferred.</data></edge><edge id="REL1004" source="SVC_EVVE" target="APP_EVID"><data key="edge_relationship_id">REL1004</data><data key="edge_source_entity_id">SVC_EVVE</data><data key="edge_relationship_type">verification_documented_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">EVVE evidence not recorded in MCS/MSSICS is coded in EVID.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1005" source="SVC_EVVE" target="APP_SSNAP"><data key="edge_relationship_id">REL1005</data><data key="edge_source_entity_id">SVC_EVVE</data><data key="edge_relationship_type">verification_documented_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Enumeration EVVE matches are documented on SSNAP Proof of Age/Summary screens.</data><data key="edge_observed_as_of">2026-06-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1006" source="SVC_SAVE" target="ORG_USCIS"><data key="edge_relationship_id">REL1006</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_USCIS</data><data key="edge_operational_context">POMS identifies SAVE as a USCIS inter-governmental program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1007" source="APP_IMAIN" target="SVC_SAVE"><data key="edge_relationship_id">REL1007</data><data key="edge_source_entity_id">APP_IMAIN</data><data key="edge_relationship_type">accesses</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">For claims purposes, POMS directs staff to access SAVE through I-Main.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1008" source="APP_SSNAP" target="SVC_SAVE"><data key="edge_relationship_id">REL1008</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">accesses</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">For enumeration, POMS states SSNAP is used to access SAVE.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1009" source="SVC_SAVE" target="APP_EP"><data key="edge_relationship_id">REL1009</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">response_documented_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">SSI POMS directs staff to store SAVE responses and supporting immigration documents in the electronic folder, including Evidence Portal.</data><data key="edge_observed_as_of">2026-09-15</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow/storage relationship; not asserted as a direct API.</data></edge><edge id="REL101" source="EX_BEER" target="ORG_STATES"><data key="edge_relationship_id">REL101</data><data key="edge_source_entity_id">EX_BEER</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Batch exchange to states</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1010" source="SVC_SAVE" target="APP_EVIEW"><data key="edge_relationship_id">REL1010</data><data key="edge_source_entity_id">SVC_SAVE</data><data key="edge_relationship_type">response_documented_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">SSI POMS directs staff to store SAVE responses and supporting immigration documents in the electronic folder, including eView.</data><data key="edge_observed_as_of">2026-09-15</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow/storage relationship; not asserted as a direct API.</data></edge><edge id="REL1011" source="APP_QRCPS" target="APP_DICARS_LEGACY"><data key="edge_relationship_id">REL1011</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">replaced</data><data key="edge_target_entity_id">APP_DICARS_LEGACY</data><data key="edge_operational_context">SSA FY2025 budget says QRCPS replaced legacy DICARS.</data><data key="edge_observed_as_of">2023-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1012" source="APP_QRCPS" target="APP_DQR_LEGACY"><data key="edge_relationship_id">REL1012</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">replaced</data><data key="edge_target_entity_id">APP_DQR_LEGACY</data><data key="edge_operational_context">SSA FY2025 budget says QRCPS replaced the legacy DQR system.</data><data key="edge_observed_as_of">2023-09</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1013" source="APP_QRCPS" target="PROC_DQR_QUALITY_REVIEW"><data key="edge_relationship_id">REL1013</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_operational_context">Current POMS places DQR quality-review tasks and coding in the case-processing environment and explicitly uses QRCPS for MAQR tasks/referrals.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1014" source="FUNC_MAQR" target="APP_QRCPS"><data key="edge_relationship_id">REL1014</data><data key="edge_source_entity_id">FUNC_MAQR</data><data key="edge_relationship_type">implemented_within</data><data key="edge_target_entity_id">APP_QRCPS</data><data key="edge_operational_context">Qualified FQRs receive MAQR tasks and all FQRs can create MAQR Review referrals within QRCPS.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1015" source="PROC_DQR_QUALITY_REVIEW" target="APP_NCPS"><data key="edge_relationship_id">REL1015</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_NCPS</data><data key="edge_operational_context">DQR uses NCPS SSN History/Query and NCPS case transfer during current quality review.</data><data key="edge_observed_as_of">2026-03-27</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1016" source="PROC_DQR_QUALITY_REVIEW" target="APP_EVIEW"><data key="edge_relationship_id">REL1016</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Current POMS directs DQR to use eView to review trailer material/UAT information.</data><data key="edge_observed_as_of">2026-03-27</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1017" source="APP_ERPC" target="PROC_RPC"><data key="edge_relationship_id">REL1017</data><data key="edge_source_entity_id">APP_ERPC</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_RPC</data><data key="edge_operational_context">eRPC manages RPC receipt, scheduling, notifications, workload, searches and dashboards.</data><data key="edge_observed_as_of">2026-08-18</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1018" source="PROC_RPC" target="REPO_CEF"><data key="edge_relationship_id">REL1018</data><data key="edge_source_entity_id">PROC_RPC</data><data key="edge_relationship_type">limited_to</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">POMS explicitly states RPC applies only to certified electronic folders.</data><data key="edge_observed_as_of">2026-08-18</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1019" source="APP_ERPC" target="APP_EVIEW"><data key="edge_relationship_id">REL1019</data><data key="edge_source_entity_id">APP_ERPC</data><data key="edge_relationship_type">supports_case_review_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">RPC Workload Summary access allows managers to review pending RPC cases in eView.</data><data key="edge_observed_as_of">2026-01-21</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow linkage; no system-to-system API inferred.</data></edge><edge id="REL102" source="EX_BENDEX" target="DOM_TITLE2"><data key="edge_relationship_id">REL102</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">State benefit-program exchange</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1020" source="APP_MEGAHIT" target="DATA_HIT_REQUEST"><data key="edge_relationship_id">REL1020</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_HIT_REQUEST</data><data key="edge_operational_context">MEGAHIT creates a HIT Request artifact when it sends an electronic HIE request.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1021" source="APP_MEGAHIT" target="DATA_HIT_MER"><data key="edge_relationship_id">REL1021</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_HIT_MER</data><data key="edge_operational_context">When medical-record data are received, MEGAHIT formats them into imaged HIT MER documents.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1022" source="APP_MEGAHIT" target="DATA_HIT_RESPONSE"><data key="edge_relationship_id">REL1022</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_HIT_RESPONSE</data><data key="edge_operational_context">When no response or no records are returned, MEGAHIT creates a HIT Response document.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1023" source="DATA_HIT_REQUEST" target="REPO_EF"><data key="edge_relationship_id">REL1023</data><data key="edge_source_entity_id">DATA_HIT_REQUEST</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">POMS places HIT Request in the yellow-back section of the electronic folder.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1024" source="DATA_HIT_MER" target="REPO_EF"><data key="edge_relationship_id">REL1024</data><data key="edge_source_entity_id">DATA_HIT_MER</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">POMS places HIT MER documents in the yellow-back section of the electronic folder.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1025" source="DATA_HIT_RESPONSE" target="REPO_EF"><data key="edge_relationship_id">REL1025</data><data key="edge_source_entity_id">DATA_HIT_RESPONSE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">POMS places HIT Response documents in the yellow-back section of the electronic folder.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1026" source="APP_MEGAHIT" target="APP_EDCS"><data key="edge_relationship_id">REL1026</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">uses_source_listing_from</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">MEGAHIT sends a health-IT request when participating source(s) are listed in EDCS and authorization is present.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes">Operational dependency; transport/protocol not inferred.</data></edge><edge id="REL1027" source="SVC_E1696" target="APP_WORKTRACK"><data key="edge_relationship_id">REL1027</data><data key="edge_source_entity_id">SVC_E1696</data><data key="edge_relationship_type">routes_submission_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">POMS states servicing-FO staff receive the SSA-1696-APP electronic image using WorkTrack.</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1028" source="APP_ESS" target="APP_OSSNAP"><data key="edge_relationship_id">REL1028</data><data key="edge_source_entity_id">APP_ESS</data><data key="edge_relationship_type">supports_enumeration_workflow_with</data><data key="edge_target_entity_id">APP_OSSNAP</data><data key="edge_operational_context">Current POMS pairs ESS enumeration scheduling with the Online SSN Application workflow.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">4</data><data key="edge_notes">Workflow association only; no direct technical interface is asserted.</data></edge><edge id="REL1029" source="APP_ESS" target="APP_ELAS"><data key="edge_relationship_id">REL1029</data><data key="edge_source_entity_id">APP_ESS</data><data key="edge_relationship_type">superseded_for_pe_scheduling</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">EM-25035 REV moved PE appointment scheduling from eLAS to ESS effective July 2025, with documented exceptions.</data><data key="edge_observed_as_of">2025-07-28</data><data key="edge_confidence">5</data><data key="edge_notes">Does not mean eLAS was decommissioned; current POMS retains eLAS for initial claims.</data></edge><edge id="REL103" source="EX_BENDEX" target="DOM_EARNINGS"><data key="edge_relationship_id">REL103</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">State benefit-program exchange</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1030" source="APP_ESS" target="APP_ELAS"><data key="edge_relationship_id">REL1030</data><data key="edge_source_entity_id">APP_ESS</data><data key="edge_relationship_type">coexists_with</data><data key="edge_target_entity_id">APP_ELAS</data><data key="edge_operational_context">Current POMS directs ESS for PE/enumeration appointments and eLAS for initial-claim appointments.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1031" source="SVC_APPT_QUESTIONNAIRE" target="APP_ESS"><data key="edge_relationship_id">REL1031</data><data key="edge_source_entity_id">SVC_APPT_QUESTIONNAIRE</data><data key="edge_relationship_type">guides_customers_to_scheduling_in</data><data key="edge_target_entity_id">APP_ESS</data><data key="edge_operational_context">EM-25035 REV says the public questionnaire guides customers on scheduling and accompanies ESS customer self-scheduling.</data><data key="edge_observed_as_of">2025-07-21</data><data key="edge_confidence">4</data><data key="edge_notes">User-flow relationship; no direct API asserted.</data></edge><edge id="REL1032" source="PROJ_EEA" target="APP_ERE"><data key="edge_relationship_id">REL1032</data><data key="edge_source_entity_id">PROJ_EEA</data><data key="edge_relationship_type">modernizes</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">FY2025 budget says FY2024 EEA work includes modernization of ERE for reliable secure electronic record submission.</data><data key="edge_observed_as_of">2024</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1033" source="PROJ_EEA" target="ORG_HIT_PARTNERS"><data key="edge_relationship_id">REL1033</data><data key="edge_source_entity_id">PROJ_EEA</data><data key="edge_relationship_type">improves_interoperability_with</data><data key="edge_target_entity_id">ORG_HIT_PARTNERS</data><data key="edge_operational_context">FY2025 budget says EEA work focuses on improving interoperability with HIT partners.</data><data key="edge_observed_as_of">2024</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1034" source="PROJ_NCPS_SCHED_FY26" target="APP_NCPS"><data key="edge_relationship_id">REL1034</data><data key="edge_source_entity_id">PROJ_NCPS_SCHED_FY26</data><data key="edge_relationship_type">builds_on</data><data key="edge_target_entity_id">APP_NCPS</data><data key="edge_operational_context">FY2026 budget describes NCPS Scheduling as integrating calendar availability into NCPS.</data><data key="edge_observed_as_of">2025-05-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1035" source="PROJ_HEARING_SCHED" target="APP_NCPS"><data key="edge_relationship_id">REL1035</data><data key="edge_source_entity_id">PROJ_HEARING_SCHED</data><data key="edge_relationship_type">integrates_with</data><data key="edge_target_entity_id">APP_NCPS</data><data key="edge_operational_context">FY2027 budget explicitly describes the Streamline Hearing Scheduling Product as integrated with NCPS.</data><data key="edge_observed_as_of">2026</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL1036" source="CON_FIRSTNET_BACKUP_2026" target="TECH_FIRSTNET"><data key="edge_relationship_id">REL1036</data><data key="edge_source_entity_id">CON_FIRSTNET_BACKUP_2026</data><data key="edge_relationship_type">procures_backup_for</data><data key="edge_target_entity_id">TECH_FIRSTNET</data><data key="edge_operational_context">SSA solicitation seeks emergency satellite-backup equipment to restore FirstNet communications during network outages.</data><data key="edge_observed_as_of">2026-09-21</data><data key="edge_confidence">5</data><data key="edge_notes">Pre-award procurement relationship.</data></edge><edge id="REL1037" source="TECH_FIRSTNET" target="TECH_LMR"><data key="edge_relationship_id">REL1037</data><data key="edge_source_entity_id">TECH_FIRSTNET</data><data key="edge_relationship_type">planned_replacement_for</data><data key="edge_target_entity_id">TECH_LMR</data><data key="edge_operational_context">SSA solicitation says Security and Resilience is moving away from handheld LMR and identifies FirstNet as the resilient solution.</data><data key="edge_observed_as_of">2026-09-21</data><data key="edge_confidence">5</data><data key="edge_notes">Procurement-stage replacement target, not proof every LMR asset is retired.</data></edge><edge id="REL1038" source="TECH_FIRSTNET" target="ORG_ATT"><data key="edge_relationship_id">REL1038</data><data key="edge_source_entity_id">TECH_FIRSTNET</data><data key="edge_relationship_type">depends_on</data><data key="edge_target_entity_id">ORG_ATT</data><data key="edge_operational_context">SSA solicitation states FirstNet devices operate where AT&amp;T signal exists and identifies AT&amp;T network failure as the outage risk.</data><data key="edge_observed_as_of">2026-09-21</data><data key="edge_confidence">5</data><data key="edge_notes">External network dependency, not award status.</data></edge><edge id="REL1039" source="APP_EWORK" target="APP_POS"><data key="edge_relationship_id">REL1039</data><data key="edge_source_entity_id">APP_EWORK</data><data key="edge_relationship_type">inputs_decision_to</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Current POMS states eWork inputs applicable work-CDR decisions to POS, which effectuates payment/non-payment months.</data><data key="edge_observed_as_of">2026-09-14</data><data key="edge_confidence">5</data><data key="edge_notes">Current-state evidence demonstrates eWork remains operational while modernization projects are planned.</data></edge><edge id="REL104" source="EX_BENDEX" target="ORG_STATES"><data key="edge_relationship_id">REL104</data><data key="edge_source_entity_id">EX_BENDEX</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">State benefit-program exchange</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL105" source="EX_EAB" target="ORG_STATES"><data key="edge_relationship_id">REL105</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Birth registration / SSN request</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL106" source="EX_EAB" target="DOM_SSNV"><data key="edge_relationship_id">REL106</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Enumeration-at-birth process</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL107" source="EX_IEDR" target="ORG_STATES"><data key="edge_relationship_id">REL107</data><data key="edge_source_entity_id">EX_IEDR</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Death registration</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL108" source="EX_IEDR" target="DOM_DEATH"><data key="edge_relationship_id">REL108</data><data key="edge_source_entity_id">EX_IEDR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_DEATH</data><data key="edge_operational_context">Death verification/notification</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL109" source="EX_LIS" target="DOM_MEDICARE"><data key="edge_relationship_id">REL109</data><data key="edge_source_entity_id">EX_LIS</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">LIS/MSP outreach data</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL110" source="EX_LIS" target="ORG_STATES"><data key="edge_relationship_id">REL110</data><data key="edge_source_entity_id">EX_LIS</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">LIS leads</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL111" source="APP_PUPS" target="DOM_PRISONER"><data key="edge_relationship_id">REL111</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">stores_or_supports</data><data key="edge_target_entity_id">DOM_PRISONER</data><data key="edge_operational_context">Prisoner data retained in PUPS</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL112" source="APP_PUPS" target="ORG_PRISONS"><data key="edge_relationship_id">REL112</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_PRISONS</data><data key="edge_operational_context">Prisoner reporting</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL113" source="EX_QQ" target="DOM_EARNINGS"><data key="edge_relationship_id">REL113</data><data key="edge_source_entity_id">EX_QQ</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Quarters-of-coverage information</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL114" source="EX_SDX" target="DOM_TITLE16"><data key="edge_relationship_id">REL114</data><data key="edge_source_entity_id">EX_SDX</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Title XVI state data exchange</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL115" source="EX_SDX" target="ORG_STATES"><data key="edge_relationship_id">REL115</data><data key="edge_source_entity_id">EX_SDX</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Title XVI state data exchange</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL116" source="EX_SCHIPI" target="DOM_CITIZENSHIP"><data key="edge_relationship_id">REL116</data><data key="edge_source_entity_id">EX_SCHIPI</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_CITIZENSHIP</data><data key="edge_operational_context">Real-time citizenship verification</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL117" source="EX_SCHIPI" target="ORG_STATES"><data key="edge_relationship_id">REL117</data><data key="edge_source_entity_id">EX_SCHIPI</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">State CHIP/benefit programs</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL118" source="EX_SOLQ" target="DOM_SSNV"><data key="edge_relationship_id">REL118</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Real-time SSN verification</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL119" source="EX_SOLQ" target="DOM_TITLE2"><data key="edge_relationship_id">REL119</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Real-time benefit retrieval</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL120" source="EX_SOLQ" target="DOM_TITLE16"><data key="edge_relationship_id">REL120</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Real-time benefit retrieval</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL121" source="EX_SOLQ" target="ORG_STATES"><data key="edge_relationship_id">REL121</data><data key="edge_source_entity_id">EX_SOLQ</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">State online query</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL122" source="EX_SVES" target="DOM_SSNV"><data key="edge_relationship_id">REL122</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Batch SSN verification</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL123" source="EX_SVES" target="DOM_TITLE2"><data key="edge_relationship_id">REL123</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Batch benefit query</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL124" source="EX_SVES" target="DOM_TITLE16"><data key="edge_relationship_id">REL124</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Batch benefit query</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL125" source="EX_SVES" target="EX_BENDEX"><data key="edge_relationship_id">REL125</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">can_request_from</data><data key="edge_target_entity_id">EX_BENDEX</data><data key="edge_operational_context">SVES request can obtain BENDEX information</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL126" source="EX_SVES" target="EX_SDX"><data key="edge_relationship_id">REL126</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">can_request_from</data><data key="edge_target_entity_id">EX_SDX</data><data key="edge_operational_context">SVES request can obtain SDX information</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL127" source="EX_SVES" target="ORG_STATES"><data key="edge_relationship_id">REL127</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">State/federal batch query</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL128" source="EX_UIQ" target="DOM_SSNV"><data key="edge_relationship_id">REL128</data><data key="edge_source_entity_id">EX_UIQ</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">UI agencies receive SSN verification</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL129" source="EX_UIQ" target="DOM_TITLE2"><data key="edge_relationship_id">REL129</data><data key="edge_source_entity_id">EX_UIQ</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">UI agencies receive Title II payment data</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL130" source="EX_UIQ" target="ORG_DOL"><data key="edge_relationship_id">REL130</data><data key="edge_source_entity_id">EX_UIQ</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">ORG_DOL</data><data key="edge_operational_context">Via DOL ICON Hub</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL131" source="EX_UIQ" target="ORG_STATES"><data key="edge_relationship_id">REL131</data><data key="edge_source_entity_id">EX_UIQ</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">State unemployment-insurance agencies</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL132" source="APP_CBSV" target="DOM_SSNV"><data key="edge_relationship_id">REL132</data><data key="edge_source_entity_id">APP_CBSV</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Consent-based SSN verification</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL133" source="APP_ECBSV" target="DOM_SSNV"><data key="edge_relationship_id">REL133</data><data key="edge_source_entity_id">APP_ECBSV</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Electronic consent-based SSN verification</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL134" source="APP_EVITAL" target="DOM_DEATH"><data key="edge_relationship_id">REL134</data><data key="edge_source_entity_id">APP_EVITAL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_DEATH</data><data key="edge_operational_context">Electronic death registration</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL135" source="APP_ERMS" target="DOM_EARNINGS"><data key="edge_relationship_id">REL135</data><data key="edge_source_entity_id">APP_ERMS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Earnings-record maintenance</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL136" source="APP_EWR" target="DOM_EARNINGS"><data key="edge_relationship_id">REL136</data><data key="edge_source_entity_id">APP_EWR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Electronic wage reporting</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL137" source="APP_APPOINTED_REP" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL137</data><data key="edge_source_entity_id">APP_APPOINTED_REP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">Representation-related data</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">3</data><data key="edge_notes">Domain grouping for navigation; appointed-representative and representative-payee functions are not the same business process.</data></edge><edge id="REL138" source="REPO_CEF" target="DOM_CLAIMFOLDER"><data key="edge_relationship_id">REL138</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DOM_CLAIMFOLDER</data><data key="edge_operational_context">Electronic disability claim folder</data><data key="edge_observed_as_of">2026-10-02</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL139" source="APP_PUPS" target="APP_T2R"><data key="edge_relationship_id">REL139</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">creates_transaction_for</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">PUPS suspension input creates a T2R transaction.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL140" source="APP_T2R" target="SYS_MBR"><data key="edge_relationship_id">REL140</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Successful T2R prisoner suspension changes MBR LAF to S7 and annotates benefit data.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL141" source="APP_T2R" target="APP_PCACS"><data key="edge_relationship_id">REL141</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">creates_exception_control_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">A T2R exception should create a PCACS Action Control Record.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL142" source="APP_MONET" target="SYS_MBR"><data key="edge_relationship_id">REL142</data><data key="edge_source_entity_id">APP_MONET</data><data key="edge_relationship_type">posts_special_message_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MONET SMS1 is used to add a Special Message to the MBR.</data><data key="edge_observed_as_of">2026-01-06</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL143" source="APP_T2R" target="APP_ICF_T2"><data key="edge_relationship_id">REL143</data><data key="edge_source_entity_id">APP_T2R</data><data key="edge_relationship_type">processes_action_from</data><data key="edge_target_entity_id">APP_ICF_T2</data><data key="edge_operational_context">Current POMS states T2R processes ICF #32 adjudication actions.</data><data key="edge_observed_as_of">2025-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL144" source="APP_ICF_T2" target="APP_MACADE"><data key="edge_relationship_id">REL144</data><data key="edge_source_entity_id">APP_ICF_T2</data><data key="edge_relationship_type">supplies_notice_information_to</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">Benefit authorizer/technical examiner includes ICF notice information in MACADE.</data><data key="edge_observed_as_of">2025-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL145" source="APP_MACADE" target="APP_MADCAP"><data key="edge_relationship_id">REL145</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">submitted_for_processing_by</data><data key="edge_target_entity_id">APP_MADCAP</data><data key="edge_operational_context">Current ICF POMS states MADCAP processes the MACADE action.</data><data key="edge_observed_as_of">2025-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL146" source="APP_AURORA" target="APP_ORS"><data key="edge_relationship_id">REL146</data><data key="edge_source_entity_id">APP_AURORA</data><data key="edge_relationship_type">posts_notices_to</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Current POMS states Aurora automatically posts notices to ORS for viewing.</data><data key="edge_observed_as_of">2025-03-25</data><data key="edge_confidence">5</data><data key="edge_notes">Direct POMS.</data></edge><edge id="REL147" source="APP_MCS" target="APP_SPS"><data key="edge_relationship_id">REL147</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">propagates_payment_data_to</data><data key="edge_target_entity_id">APP_SPS</data><data key="edge_operational_context">SPS APAY propagates most payment information from MCS (among other sources).</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">4</data><data key="edge_notes">Current-transmittal POMS page; original section date is older.</data></edge><edge id="REL148" source="APP_MADCAP" target="APP_SPS"><data key="edge_relationship_id">REL148</data><data key="edge_source_entity_id">APP_MADCAP</data><data key="edge_relationship_type">propagates_payment_data_to</data><data key="edge_target_entity_id">APP_SPS</data><data key="edge_operational_context">SPS APAY propagates most payment information from MADCAP (among other sources).</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">4</data><data key="edge_notes">Current-transmittal POMS page; original section date is older.</data></edge><edge id="REL149" source="APP_SPS" target="DB_PHUS"><data key="edge_relationship_id">REL149</data><data key="edge_source_entity_id">APP_SPS</data><data key="edge_relationship_type">records_payment_data_in</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">POMS states PHUS shows SPS fee-payment data and reflects the SPS assessment/user fee.</data><data key="edge_observed_as_of">2025-05-06</data><data key="edge_confidence">4</data><data key="edge_notes">Direct POMS; exact technical interface is not described.</data></edge><edge id="REL150" source="APP_CPS" target="APP_TPPS"><data key="edge_relationship_id">REL150</data><data key="edge_source_entity_id">APP_CPS</data><data key="edge_relationship_type">transmits_immediate_payment_to</data><data key="edge_target_entity_id">APP_TPPS</data><data key="edge_operational_context">After CPS establishment/approval, Title II immediate payment is transmitted to TPPS.</data><data key="edge_observed_as_of">2026-09-18</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL151" source="APP_CPS" target="DB_PHUS"><data key="edge_relationship_id">REL151</data><data key="edge_source_entity_id">APP_CPS</data><data key="edge_relationship_type">recommended_control_checks</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">OIG recommended CPS controls use the most current PHUS data to flag incorrect/mismatched payments.</data><data key="edge_observed_as_of">2026-03-31</data><data key="edge_confidence">5</data><data key="edge_notes">This is a recommended control gap, not evidence of an existing automated interface.</data></edge><edge id="REL152" source="APP_CPS" target="APP_ROAR"><data key="edge_relationship_id">REL152</data><data key="edge_source_entity_id">APP_CPS</data><data key="edge_relationship_type">recommended_control_checks</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">OIG recommended CPS controls ensure staff consider ROAR overpayments during critical-payment processing.</data><data key="edge_observed_as_of">2026-03-31</data><data key="edge_confidence">5</data><data key="edge_notes">This is a recommended control gap, not evidence of an existing automated interface.</data></edge><edge id="REL153" source="DB_T2_ODS" target="DB_WMDW"><data key="edge_relationship_id">REL153</data><data key="edge_source_entity_id">DB_T2_ODS</data><data key="edge_relationship_type">provides_processing_time_data_to</data><data key="edge_target_entity_id">DB_WMDW</data><data key="edge_operational_context">SSA Open Data explicitly states the Title 2 ODS provides processing-time data to WMDW.</data><data key="edge_observed_as_of">2026-06-26</data><data key="edge_confidence">5</data><data key="edge_notes">Direct SSA Open Data metadata.</data></edge><edge id="REL154" source="APP_MCS" target="EX_OCSE_PENDING"><data key="edge_relationship_id">REL154</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">supplies_pending_records_to</data><data key="edge_target_entity_id">EX_OCSE_PENDING</data><data key="edge_operational_context">The daily OCSE match uses SSA's MCS Title II pending file.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Direct SSA Open Data metadata.</data></edge><edge id="REL155" source="EX_OCSE_PENDING" target="ORG_OCSE"><data key="edge_relationship_id">REL155</data><data key="edge_source_entity_id">EX_OCSE_PENDING</data><data key="edge_relationship_type">releases_matched_information_to</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">Matched Title II information is released to OCSE after the daily match.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Direct SSA Open Data metadata.</data></edge><edge id="REL156" source="APP_PCACS" target="DB_PCACS_FLAT"><data key="edge_relationship_id">REL156</data><data key="edge_source_entity_id">APP_PCACS</data><data key="edge_relationship_type">has_data_asset</data><data key="edge_target_entity_id">DB_PCACS_FLAT</data><data key="edge_operational_context">SSA inventories PCACS Flat Files as a non-public data asset supporting PCACS workloads.</data><data key="edge_observed_as_of">2026-07-28</data><data key="edge_confidence">5</data><data key="edge_notes">Direct title/description match in SSA Open Data.</data></edge><edge id="REL157" source="APP_MADCAP" target="DB_MADCAP_NOTICES"><data key="edge_relationship_id">REL157</data><data key="edge_source_entity_id">APP_MADCAP</data><data key="edge_relationship_type">has_data_asset</data><data key="edge_target_entity_id">DB_MADCAP_NOTICES</data><data key="edge_operational_context">SSA inventories a MADCAP Notices data asset that produces manual MADCAP notices.</data><data key="edge_observed_as_of">2026-07-28</data><data key="edge_confidence">5</data><data key="edge_notes">Direct title/description match in SSA Open Data.</data></edge><edge id="REL158" source="APP_CFRMS" target="DOM_CLAIMFOLDER"><data key="edge_relationship_id">REL158</data><data key="edge_source_entity_id">APP_CFRMS</data><data key="edge_relationship_type">manages_records_for</data><data key="edge_target_entity_id">DOM_CLAIMFOLDER</data><data key="edge_operational_context">CFRMS supports access, disclosure, retention and destruction in the CFRMS claims folder.</data><data key="edge_observed_as_of">2026-08-06</data><data key="edge_confidence">5</data><data key="edge_notes">Modeled to the existing claims-folder data domain; no CEF-specific interface asserted.</data></edge><edge id="REL159" source="DB_T2_GARNISH" target="ORG_IRS"><data key="edge_relationship_id">REL159</data><data key="edge_source_entity_id">DB_T2_GARNISH</data><data key="edge_relationship_type">supports_treasury_disbursement_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Data supports payments to Treasury for disbursement to IRS.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Treasury is an intermediary; relationship label preserves that nuance.</data></edge><edge id="REL160" source="DB_TAXY" target="ORG_IRS"><data key="edge_relationship_id">REL160</data><data key="edge_source_entity_id">DB_TAXY</data><data key="edge_relationship_type">supports_treasury_disbursement_to</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Data supports automated tax-levy payments to Treasury for disbursement to IRS.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Treasury is an intermediary; no direct SSA-to-IRS payment interface asserted.</data></edge><edge id="REL161" source="APP_SPS" target="DB_SPS_MI"><data key="edge_relationship_id">REL161</data><data key="edge_source_entity_id">APP_SPS</data><data key="edge_relationship_type">has_management_information_asset</data><data key="edge_target_entity_id">DB_SPS_MI</data><data key="edge_operational_context">SSA inventories SPS Management Information as the data store supporting SPS payment workloads.</data><data key="edge_observed_as_of">2026-08-05</data><data key="edge_confidence">5</data><data key="edge_notes">Direct title/description match.</data></edge><edge id="REL162" source="APP_MCS" target="WF_A101"><data key="edge_relationship_id">REL162</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">has_transaction_method</data><data key="edge_target_entity_id">WF_A101</data><data key="edge_operational_context">Current POMS says prepare an MCS A101 for certain allowances that cannot process through EC.</data><data key="edge_observed_as_of">2026-04-20</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL163" source="APP_MCS" target="WF_EF101"><data key="edge_relationship_id">REL163</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">has_transaction_method</data><data key="edge_target_entity_id">WF_EF101</data><data key="edge_operational_context">Current POMS says prepare an MCS EF101 for certain allowances that cannot process through EC.</data><data key="edge_observed_as_of">2026-04-20</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL164" source="APP_MACADE" target="SYS_MBR"><data key="edge_relationship_id">REL164</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">When systems input such as MCS/POS is not possible, current POMS directs use of MACADE to update the MBR.</data><data key="edge_observed_as_of">2026-04-20</data><data key="edge_confidence">5</data><data key="edge_notes">Direct current POMS.</data></edge><edge id="REL165" source="APP_POS" target="SYS_MBR"><data key="edge_relationship_id">REL165</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">supports_conversion_posted_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS directs POS for specified CDB conversions and states the disability determination must be posted to the MBR.</data><data key="edge_observed_as_of">2026-04-20</data><data key="edge_confidence">4</data><data key="edge_notes">Workflow relationship is clear; exact technical interface is not described.</data></edge><edge id="REL166" source="APP_SSIRM" target="APP_EIAR"><data key="edge_relationship_id">REL166</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_EIAR</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL167" source="APP_SSIRM" target="APP_MOURS"><data key="edge_relationship_id">REL167</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_MOURS</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL168" source="APP_SSIRM" target="APP_NHRP"><data key="edge_relationship_id">REL168</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_NHRP</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL169" source="APP_SSIRM" target="APP_SSI_CODO"><data key="edge_relationship_id">REL169</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_CODO</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL170" source="APP_SSIRM" target="APP_SSI_COMPUTE"><data key="edge_relationship_id">REL170</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_COMPUTE</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL171" source="APP_SSIRM" target="APP_SSI_DAILY_EDITS"><data key="edge_relationship_id">REL171</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_DAILY_EDITS</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL172" source="APP_SSIRM" target="APP_DABA"><data key="edge_relationship_id">REL172</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_DABA</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL173" source="APP_SSIRM" target="APP_SSI_EPATH"><data key="edge_relationship_id">REL173</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_EPATH</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL174" source="APP_SSIRM" target="APP_SSI_EXCEPTION"><data key="edge_relationship_id">REL174</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_EXCEPTION</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL175" source="APP_SSIRM" target="APP_SSI_FINVERIFY"><data key="edge_relationship_id">REL175</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_FINVERIFY</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL176" source="APP_SSIRM" target="APP_SSI_FOLDERCTRL"><data key="edge_relationship_id">REL176</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_FOLDERCTRL</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL177" source="APP_SSIRM" target="APP_SSI_GROUPTOTALS"><data key="edge_relationship_id">REL177</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_GROUPTOTALS</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL178" source="APP_SSIRM" target="APP_SSI_HOME"><data key="edge_relationship_id">REL178</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_HOME</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL179" source="APP_SSIRM" target="APP_SSI_INDEX"><data key="edge_relationship_id">REL179</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_INDEX</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL180" source="APP_SSIRM" target="APP_SSI_IC_UPDATE"><data key="edge_relationship_id">REL180</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_IC_UPDATE</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL181" source="APP_SSIRM" target="APP_SSI_NOTICES"><data key="edge_relationship_id">REL181</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_NOTICES</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL182" source="APP_SSIRM" target="APP_SSI_PAYHIST_CORR"><data key="edge_relationship_id">REL182</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_PAYHIST_CORR</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL183" source="APP_SSIRM" target="APP_PAYMT"><data key="edge_relationship_id">REL183</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_PAYMT</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL184" source="APP_SSIRM" target="APP_SSI_PE_UPDATE"><data key="edge_relationship_id">REL184</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_PE_UPDATE</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL185" source="APP_SSIRM" target="APP_SSI_PREPOST"><data key="edge_relationship_id">REL185</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_PREPOST</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL186" source="APP_SSIRM" target="APP_SSI_REDET"><data key="edge_relationship_id">REL186</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_REDET</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL187" source="APP_SSIRM" target="APP_ACCSTATS"><data key="edge_relationship_id">REL187</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_ACCSTATS</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL188" source="APP_SSIRM" target="APP_SSI_TREASURY"><data key="edge_relationship_id">REL188</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSI_TREASURY</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL189" source="APP_SSIRM" target="APP_DAILY_FAX"><data key="edge_relationship_id">REL189</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_DAILY_FAX</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL190" source="APP_SSIRM" target="APP_SSIMWV"><data key="edge_relationship_id">REL190</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSIMWV</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL191" source="APP_SSIRM" target="APP_MYWR"><data key="edge_relationship_id">REL191</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_MYWR</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL192" source="APP_SSIRM" target="APP_SSITWR"><data key="edge_relationship_id">REL192</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSITWR</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL193" source="APP_SSIRM" target="APP_SSAMWR"><data key="edge_relationship_id">REL193</data><data key="edge_source_entity_id">APP_SSIRM</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_SSAMWR</data><data key="edge_operational_context">Component listed in the 2021 SSIRMS PIA that remains in SSA's current PIA catalog</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Relationship is architecture documentation, not proof the component is unchanged in 2026.</data></edge><edge id="REL194" source="APP_MSSICS" target="APP_SSIRM"><data key="edge_relationship_id">REL194</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">front_end_for</data><data key="edge_target_entity_id">APP_SSIRM</data><data key="edge_operational_context">Field offices establish and modify SSI claims through MSSICS</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL195" source="APP_SSI_DAILY_EDITS" target="SYS_SSR"><data key="edge_relationship_id">REL195</data><data key="edge_source_entity_id">APP_SSI_DAILY_EDITS</data><data key="edge_relationship_type">prepares_updates_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Formats internal/external data into SSR update transactions</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL196" source="APP_SSI_IC_UPDATE" target="SYS_SSR"><data key="edge_relationship_id">REL196</data><data key="edge_source_entity_id">APP_SSI_IC_UPDATE</data><data key="edge_relationship_type">establishes</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Initial-claim update establishes SSRs for new claims</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL197" source="APP_SSI_PE_UPDATE" target="SYS_SSR"><data key="edge_relationship_id">REL197</data><data key="edge_source_entity_id">APP_SSI_PE_UPDATE</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Post-eligibility transactions update and validate SSRs</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL198" source="APP_SSI_PREPOST" target="SYS_SSR"><data key="edge_relationship_id">REL198</data><data key="edge_source_entity_id">APP_SSI_PREPOST</data><data key="edge_relationship_type">creates_update_files_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Creates files used by IC/PE Update to update SSRs</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL199" source="APP_SSI_INDEX" target="SYS_SSR"><data key="edge_relationship_id">REL199</data><data key="edge_source_entity_id">APP_SSI_INDEX</data><data key="edge_relationship_type">indexes</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Creates index records for SSNs and Claim Account Numbers on SSR</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL200" source="APP_SSI_GROUPTOTALS" target="SYS_SSR"><data key="edge_relationship_id">REL200</data><data key="edge_source_entity_id">APP_SSI_GROUPTOTALS</data><data key="edge_relationship_type">tracks_accounting_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Tracks accounting/payment information posted to SSR</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20065" source="ORG_DDS" target="PROC_DDS_CE_OVERSIGHT"><data key="edge_relationship_id">REL20065</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_DDS_CE_OVERSIGHT</data><data key="edge_operational_context">DDS components conduct the annual CE oversight process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20066" source="ORG_DDS" target="DATA_DDS_CE_OVERSIGHT_REPORT"><data key="edge_relationship_id">REL20066</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_DDS_CE_OVERSIGHT_REPORT</data><data key="edge_operational_context">DDS submits the annual CE Oversight Report.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20067" source="ORG_DDS" target="DATA_DDS_CE_PROVIDER_LIST"><data key="edge_relationship_id">REL20067</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_DDS_CE_PROVIDER_LIST</data><data key="edge_operational_context">DDS uploads an annual list of CE providers.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20068" source="ORG_DDS" target="DATA_DDS_CE_MER_FEE_SCHEDULE"><data key="edge_relationship_id">REL20068</data><data key="edge_source_entity_id">ORG_DDS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_DDS_CE_MER_FEE_SCHEDULE</data><data key="edge_operational_context">DDS uploads current CE and MER fee schedules annually.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20069" source="DATA_DDS_CE_OVERSIGHT_REPORT" target="REPO_DA_MPRO_SHAREPOINT"><data key="edge_relationship_id">REL20069</data><data key="edge_source_entity_id">DATA_DDS_CE_OVERSIGHT_REPORT</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_DA_MPRO_SHAREPOINT</data><data key="edge_operational_context">The report is submitted through the DA MPRO SharePoint site.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20070" source="DATA_DDS_CE_PROVIDER_LIST" target="REPO_DA_MPRO_SHAREPOINT"><data key="edge_relationship_id">REL20070</data><data key="edge_source_entity_id">DATA_DDS_CE_PROVIDER_LIST</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_DA_MPRO_SHAREPOINT</data><data key="edge_operational_context">The provider list is uploaded to the DDS CE Provider List section of the DA MPRO SharePoint site.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20071" source="DATA_DDS_CE_MER_FEE_SCHEDULE" target="REPO_DA_MPRO_SHAREPOINT"><data key="edge_relationship_id">REL20071</data><data key="edge_source_entity_id">DATA_DDS_CE_MER_FEE_SCHEDULE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">REPO_DA_MPRO_SHAREPOINT</data><data key="edge_operational_context">Current fee schedules are uploaded to the DDS Fee Schedules section of the DA MPRO SharePoint site.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20072" source="REPO_DA_MPRO_SHAREPOINT" target="PLAT_SHAREPOINT"><data key="edge_relationship_id">REL20072</data><data key="edge_source_entity_id">REPO_DA_MPRO_SHAREPOINT</data><data key="edge_relationship_type">implemented_on</data><data key="edge_target_entity_id">PLAT_SHAREPOINT</data><data key="edge_operational_context">SSA explicitly identifies the repository as a SharePoint site.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20073" source="APP_ITOPSS" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL20073</data><data key="edge_source_entity_id">APP_ITOPSS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">Current SSA Ticket terms describe iTOPSS as the management information system facilitating and recording Ticket to Work business functions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20074" source="APP_TICKET_PORTAL" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL20074</data><data key="edge_source_entity_id">APP_TICKET_PORTAL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">The Ticket Portal supports real-time Ticket Program transactions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20075" source="APP_TICKET_PORTAL" target="ORG_EMPLOYMENT_NETWORKS"><data key="edge_relationship_id">REL20075</data><data key="edge_source_entity_id">APP_TICKET_PORTAL</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_EMPLOYMENT_NETWORKS</data><data key="edge_operational_context">Employment Networks use the Ticket Portal for Ticket transactions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20076" source="APP_TICKET_PORTAL" target="ORG_STATE_VR_AGENCIES"><data key="edge_relationship_id">REL20076</data><data key="edge_source_entity_id">APP_TICKET_PORTAL</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_STATE_VR_AGENCIES</data><data key="edge_operational_context">State VR agencies use the Ticket Portal for Ticket transactions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20077" source="APP_VRRMS" target="PROC_VR_COST_REIMB"><data key="edge_relationship_id">REL20077</data><data key="edge_source_entity_id">APP_VRRMS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_VR_COST_REIMB</data><data key="edge_operational_context">Current SSA Ticket terms describe VRRMS as the MIS used to facilitate State VR cost-reimbursement payments.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20078" source="ORG_STATE_VR_AGENCIES" target="PROC_VR_COST_REIMB"><data key="edge_relationship_id">REL20078</data><data key="edge_source_entity_id">ORG_STATE_VR_AGENCIES</data><data key="edge_relationship_type">participates_in</data><data key="edge_target_entity_id">PROC_VR_COST_REIMB</data><data key="edge_operational_context">Only State VR agencies participate as providers in the SSA VR Cost Reimbursement program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20079" source="ORG_STATE_VR_AGENCIES" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL20079</data><data key="edge_source_entity_id">ORG_STATE_VR_AGENCIES</data><data key="edge_relationship_type">participates_in</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">State VR agencies may participate in the Ticket Program, including as ENs.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20080" source="ORG_EMPLOYMENT_NETWORKS" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL20080</data><data key="edge_source_entity_id">ORG_EMPLOYMENT_NETWORKS</data><data key="edge_relationship_type">participates_in</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">Employment Networks are provider participants in the Ticket Program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20081" source="PROC_VR_COST_REIMB" target="DOM_TITLE2"><data key="edge_relationship_id">REL20081</data><data key="edge_source_entity_id">PROC_VR_COST_REIMB</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">VR Cost Reimbursement covers qualifying SSDI beneficiaries.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20082" source="PROC_VR_COST_REIMB" target="DOM_TITLE16"><data key="edge_relationship_id">REL20082</data><data key="edge_source_entity_id">PROC_VR_COST_REIMB</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">VR Cost Reimbursement covers qualifying SSI recipients.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20083" source="PROC_TICKET_TO_WORK" target="DOM_TITLE2"><data key="edge_relationship_id">REL20083</data><data key="edge_source_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Ticket to Work is available to qualifying SSDI beneficiaries.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20084" source="PROC_TICKET_TO_WORK" target="DOM_TITLE16"><data key="edge_relationship_id">REL20084</data><data key="edge_source_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Ticket to Work is available to qualifying SSI beneficiaries.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20085" source="APP_ITOPSS" target="PROC_TTW_EPAY"><data key="edge_relationship_id">REL20085</data><data key="edge_source_entity_id">APP_ITOPSS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_TTW_EPAY</data><data key="edge_operational_context">For the E-PAY process, iTOPSS identifies and generates reconciliation payments after the 12th outcome payment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20086" source="PROC_TTW_EPAY" target="APP_TICKET_PORTAL"><data key="edge_relationship_id">REL20086</data><data key="edge_source_entity_id">PROC_TTW_EPAY</data><data key="edge_relationship_type">status_visible_in</data><data key="edge_target_entity_id">APP_TICKET_PORTAL</data><data key="edge_operational_context">E-PAY-created claims appear in Ticket Portal payment tracking.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20087" source="APP_TICKET_PORTAL" target="ORG_TREASURY"><data key="edge_relationship_id">REL20087</data><data key="edge_source_entity_id">APP_TICKET_PORTAL</data><data key="edge_relationship_type">tracks_clearance_by</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Portal pending-payment views distinguish processed payments that have not yet cleared Treasury.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20088" source="ORG_STATE_VR_AGENCIES" target="APP_TICKET_PORTAL"><data key="edge_relationship_id">REL20088</data><data key="edge_source_entity_id">ORG_STATE_VR_AGENCIES</data><data key="edge_relationship_type">reports_case_status_via</data><data key="edge_target_entity_id">APP_TICKET_PORTAL</data><data key="edge_operational_context">Current SSA FAQ says State VR agencies send relevant case/payment-method data into the Ticket Portal.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20089" source="DB_VR_REIMB_CASE" target="PROC_VR_COST_REIMB"><data key="edge_relationship_id">REL20089</data><data key="edge_source_entity_id">DB_VR_REIMB_CASE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_VR_COST_REIMB</data><data key="edge_operational_context">SORN 60-0221 identifies a Vocational Rehabilitation Reimbursement Case Processing System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Record-system title supports the business association; exact interface to VRRMS is not asserted.</data></edge><edge id="REL20090" source="DB_TTW_PAYMENT" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL20090</data><data key="edge_source_entity_id">DB_TTW_PAYMENT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">SORN 60-0295 identifies a Ticket-to-Work and Self-Sufficiency Program Payment Database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Exact application interface is not published.</data></edge><edge id="REL20091" source="DB_TTW_PM_MI" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL20091</data><data key="edge_source_entity_id">DB_TTW_PM_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">SORN 60-0300 identifies a Ticket-to-Work Program Manager Management Information System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Exact application interface is not published.</data></edge><edge id="REL20092" source="PROC_ADMIN_SANCTIONS" target="DOM_TITLE2"><data key="edge_relationship_id">REL20092</data><data key="edge_source_entity_id">PROC_ADMIN_SANCTIONS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Administrative sanctions can suspend Title II benefits.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20093" source="PROC_ADMIN_SANCTIONS" target="DOM_TITLE16"><data key="edge_relationship_id">REL20093</data><data key="edge_source_entity_id">PROC_ADMIN_SANCTIONS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Administrative sanctions can suspend Title XVI benefits.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20094" source="APP_AS_TOOL" target="PROC_ADMIN_SANCTIONS"><data key="edge_relationship_id">REL20094</data><data key="edge_source_entity_id">APP_AS_TOOL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_ADMIN_SANCTIONS</data><data key="edge_operational_context">POMS says the sanction period appears in the Administrative Sanctions Tool.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20095" source="UI_SHARED_PROCESS_MENU" target="UI_SPAS"><data key="edge_relationship_id">REL20095</data><data key="edge_source_entity_id">UI_SHARED_PROCESS_MENU</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">UI_SPAS</data><data key="edge_operational_context">POMS directs staff to access the client database through Shared Process Menu and enter sanction information on SPAS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20096" source="UI_SPAS" target="DB_CLIENT_SANCTIONS_CONTEXT"><data key="edge_relationship_id">REL20096</data><data key="edge_source_entity_id">UI_SPAS</data><data key="edge_relationship_type">writes_to</data><data key="edge_target_entity_id">DB_CLIENT_SANCTIONS_CONTEXT</data><data key="edge_operational_context">SPAS collects imposed/deferred sanction data in the client database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">The source calls the target only the client database; no mapping to ICDB or SORN 60-0280 is asserted.</data></edge><edge id="REL20097" source="PROC_ADMIN_SANCTIONS" target="APP_POS"><data key="edge_relationship_id">REL20097</data><data key="edge_source_entity_id">PROC_ADMIN_SANCTIONS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">POS is used to suspend current and later Title II months in administrative-sanction cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20098" source="PROC_ADMIN_SANCTIONS" target="APP_MACADE"><data key="edge_relationship_id">REL20098</data><data key="edge_source_entity_id">PROC_ADMIN_SANCTIONS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">MACADE is used for other Title II months or higher-priority suspense reasons in administrative-sanction cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20099" source="PROC_ADMIN_SANCTIONS" target="SYS_MBR"><data key="edge_relationship_id">REL20099</data><data key="edge_source_entity_id">PROC_ADMIN_SANCTIONS</data><data key="edge_relationship_type">records_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS requires an administrative-sanction remark on the MBR for Title II.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL201" source="APP_DAILY_FAX" target="SYS_SSR"><data key="edge_relationship_id">REL201</data><data key="edge_source_entity_id">APP_DAILY_FAX</data><data key="edge_relationship_type">tracks_transactions_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Tracks payment/accounting transactions posted to SSR</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20100" source="PROC_ADMIN_SANCTIONS" target="SYS_SSR"><data key="edge_relationship_id">REL20100</data><data key="edge_source_entity_id">PROC_ADMIN_SANCTIONS</data><data key="edge_relationship_type">records_in</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS requires an administrative-sanction remark/payment status on the SSR for Title XVI.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20101" source="DB_ADMIN_SANCTIONS" target="PROC_ADMIN_SANCTIONS"><data key="edge_relationship_id">REL20101</data><data key="edge_source_entity_id">DB_ADMIN_SANCTIONS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_ADMIN_SANCTIONS</data><data key="edge_operational_context">Current SORN catalog identifies the SSA Administrative Sanctions Database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Exact technical relationship to AS Tool, SPAS, or the POMS client database is not established.</data></edge><edge id="REL20102" source="ORG_OHO" target="APP_FACTS"><data key="edge_relationship_id">REL20102</data><data key="edge_source_entity_id">ORG_OHO</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_FACTS</data><data key="edge_operational_context">OHO Regional Offices use FAcTS to track representative fee administrative reviews.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20103" source="ORG_OAO" target="APP_WEBAFS"><data key="edge_relationship_id">REL20103</data><data key="edge_source_entity_id">ORG_OAO</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_WEBAFS</data><data key="edge_operational_context">OAO uses webAFS to track representative fee administrative reviews.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20104" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_FACTS"><data key="edge_relationship_id">REL20104</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_FACTS</data><data key="edge_operational_context">FAcTS is used for OHO fee-agreement administrative-review tracking and notices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20105" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_WEBAFS"><data key="edge_relationship_id">REL20105</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_WEBAFS</data><data key="edge_operational_context">webAFS is used for OAO administrative-review tracking.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20106" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_HACPS"><data key="edge_relationship_id">REL20106</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_HACPS</data><data key="edge_operational_context">HACPS provides OHO notice templates for fee administrative review.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20107" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_OAOCPS"><data key="edge_relationship_id">REL20107</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_OAOCPS</data><data key="edge_operational_context">OAOCPS provides OAO notice templates for fee administrative review.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20108" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_EVIEW"><data key="edge_relationship_id">REL20108</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">stores_requests_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Administrative-review requests and notices are uploaded to eView when an electronic record exists.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20109" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_ENM"><data key="edge_relationship_id">REL20109</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">stores_requests_in</data><data key="edge_target_entity_id">APP_ENM</data><data key="edge_operational_context">HALLEX directs use of ENM when applicable for administrative-review request records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20110" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_FACTS"><data key="edge_relationship_id">REL20110</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">generates_notices_via</data><data key="edge_target_entity_id">APP_FACTS</data><data key="edge_operational_context">OHO staff use FAcTS templates for fee review notices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20111" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_HACPS"><data key="edge_relationship_id">REL20111</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">generates_notices_via</data><data key="edge_target_entity_id">APP_HACPS</data><data key="edge_operational_context">OHO staff may use HACPS templates for fee review notices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20112" source="PROC_FEE_AGREEMENT_ADMIN_REVIEW" target="APP_OAOCPS"><data key="edge_relationship_id">REL20112</data><data key="edge_source_entity_id">PROC_FEE_AGREEMENT_ADMIN_REVIEW</data><data key="edge_relationship_type">generates_notices_via</data><data key="edge_target_entity_id">APP_OAOCPS</data><data key="edge_operational_context">OAO staff use OAOCPS templates for fee review notices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20113" source="APP_EVIEW" target="APP_EDCS"><data key="edge_relationship_id">REL20113</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">triggers_alerts_via</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">HALLEX says eView upload of fee-review determinations automatically alerts downstream components through EDCS and Evidence Portal.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20114" source="APP_EVIEW" target="APP_EP"><data key="edge_relationship_id">REL20114</data><data key="edge_source_entity_id">APP_EVIEW</data><data key="edge_relationship_type">triggers_alerts_via</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">HALLEX says eView upload of fee-review determinations automatically alerts downstream components through EDCS and Evidence Portal.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20115" source="DB_MEDICARE_PARTB_BUYIN" target="PROC_STATE_BUYIN"><data key="edge_relationship_id">REL20115</data><data key="edge_source_entity_id">DB_MEDICARE_PARTB_BUYIN</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_STATE_BUYIN</data><data key="edge_operational_context">The current SORN identifies the Medicare Part B Buy-In Information System; current POMS independently confirms State buy-in remains an active process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Business association by named record system; physical interface is not asserted.</data></edge><edge id="REL20116" source="DB_MEDICARE_PARTB_BUYIN" target="DOM_MEDICARE"><data key="edge_relationship_id">REL20116</data><data key="edge_source_entity_id">DB_MEDICARE_PARTB_BUYIN</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">The record system contains Medicare Part B buy-in information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20117" source="DB_MSP_INFO" target="DOM_MEDICARE"><data key="edge_relationship_id">REL20117</data><data key="edge_source_entity_id">DB_MSP_INFO</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">The record system contains Medicare Savings Programs information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20118" source="DATA_DAF" target="DOM_TITLE2"><data key="edge_relationship_id">REL20118</data><data key="edge_source_entity_id">DATA_DAF</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">DAF covers disability beneficiaries receiving OASDI/DI benefits.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20119" source="DATA_DAF" target="DOM_TITLE16"><data key="edge_relationship_id">REL20119</data><data key="edge_source_entity_id">DATA_DAF</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">DAF covers SSI disability recipients.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20120" source="DATA_DAF" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL20120</data><data key="edge_source_entity_id">DATA_DAF</data><data key="edge_relationship_type">includes_data_from</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">FY2026 budget says the mostly-complete DAF 2023 included Ticket to Work files.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20121" source="DATA_DAF" target="SYS_MEF"><data key="edge_relationship_id">REL20121</data><data key="edge_source_entity_id">DATA_DAF</data><data key="edge_relationship_type">linked_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">SSA 2021 disability-employment chartbook uses DAF21 linked to the Master Earnings File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Observed for DAF21 research use; not asserted as a permanent ETL interface.</data></edge><edge id="REL20122" source="PROJ_DRS" target="DATA_NBS"><data key="edge_relationship_id">REL20122</data><data key="edge_source_entity_id">PROJ_DRS</data><data key="edge_relationship_type">produced</data><data key="edge_target_entity_id">DATA_NBS</data><data key="edge_operational_context">NBS was one of the three surveys under the Disability Research Surveys project.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20123" source="DATA_NBS" target="DOM_TITLE2"><data key="edge_relationship_id">REL20123</data><data key="edge_source_entity_id">DATA_NBS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">NBS includes OASDI/DI disability beneficiaries.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20124" source="DATA_NBS" target="DOM_TITLE16"><data key="edge_relationship_id">REL20124</data><data key="edge_source_entity_id">DATA_NBS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">NBS includes SSI disability recipients.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20125" source="DB_PASS_MI" target="DOM_TITLE16"><data key="edge_relationship_id">REL20125</data><data key="edge_source_entity_id">DB_PASS_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">PASS is an SSI work-incentive program and the current SORN catalog maintains a PASS Management Information System record system.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">No current runtime application/interface is inferred from the SORN alone.</data></edge><edge id="REL20126" source="DB_SVB_CLAIMS_MI" target="DOM_SVB"><data key="edge_relationship_id">REL20126</data><data key="edge_source_entity_id">DB_SVB_CLAIMS_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SVB</data><data key="edge_operational_context">The current SORN title explicitly covers Title VIII Special Veterans Benefits claims development and management information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20127" source="ORG_PASS_CADRE" target="APP_PASS_CIS"><data key="edge_relationship_id">REL20127</data><data key="edge_source_entity_id">ORG_PASS_CADRE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_PASS_CIS</data><data key="edge_operational_context">PASS Specialists/AWICs must use PASS CIS to initiate, develop, adjudicate, and monitor PASS applications.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20128" source="APP_PASS_CIS" target="PROC_PASS"><data key="edge_relationship_id">REL20128</data><data key="edge_source_entity_id">APP_PASS_CIS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_PASS</data><data key="edge_operational_context">POMS requires all PASS applications and decisions to be documented in PASS CIS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20129" source="PROC_PASS" target="DOM_TITLE16"><data key="edge_relationship_id">REL20129</data><data key="edge_source_entity_id">PROC_PASS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">PASS is an SSI work-incentive process affecting income/resource exclusions and SSI eligibility/payment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20130" source="DATA_SSA545" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">REL20130</data><data key="edge_source_entity_id">DATA_SSA545</data><data key="edge_relationship_type">received_by</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">Field offices receive completed SSA-545-BK PASS applications.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20131" source="DATA_SSA545" target="APP_WORKTRACK"><data key="edge_relationship_id">REL20131</data><data key="edge_source_entity_id">DATA_SSA545</data><data key="edge_relationship_type">ingested_into</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">Field offices scan SSA-545-BK and accompanying PASS material into WorkTrack.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20132" source="DATA_SSA545" target="APP_EVIEW"><data key="edge_relationship_id">REL20132</data><data key="edge_source_entity_id">DATA_SSA545</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">PASS documentation is stored in eView when the certified electronic folder applies.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20133" source="DATA_SSA545" target="APP_EP"><data key="edge_relationship_id">REL20133</data><data key="edge_source_entity_id">DATA_SSA545</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">PASS documentation may be stored in Evidence Portal.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20134" source="UI_MSSICS_ISEI" target="APP_MSSICS"><data key="edge_relationship_id">REL20134</data><data key="edge_source_entity_id">UI_MSSICS_ISEI</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies iSEI as an MSSICS screen used for approved PASS self-employment earnings.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20135" source="UI_MSSICS_RFIA" target="APP_MSSICS"><data key="edge_relationship_id">REL20135</data><data key="edge_source_entity_id">UI_MSSICS_RFIA</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS identifies RFIA as an MSSICS screen used to exclude a PASS/business account as a resource.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20136" source="PROC_PASS" target="UI_MSSICS_ISEI"><data key="edge_relationship_id">REL20136</data><data key="edge_source_entity_id">PROC_PASS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MSSICS_ISEI</data><data key="edge_operational_context">Approved self-employment PASS cases post net earnings on iSEI.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20137" source="PROC_PASS" target="UI_MSSICS_RFIA"><data key="edge_relationship_id">REL20137</data><data key="edge_source_entity_id">PROC_PASS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MSSICS_RFIA</data><data key="edge_operational_context">Approved self-employment PASS cases exclude PASS/business accounts on RFIA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20138" source="PROC_PASS" target="SYS_SSR"><data key="edge_relationship_id">REL20138</data><data key="edge_source_entity_id">PROC_PASS</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">PASS specialists add remarks/status information to the SSR as appropriate.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20139" source="APP_MAPS" target="PROC_EXTRA_HELP"><data key="edge_relationship_id">REL20139</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">processes</data><data key="edge_target_entity_id">PROC_EXTRA_HELP</data><data key="edge_operational_context">SSA employees use MAPS to take and process Extra Help applications.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20140" source="DATA_SSA1020_OCR" target="APP_MAPS"><data key="edge_relationship_id">REL20140</data><data key="edge_source_entity_id">DATA_SSA1020_OCR</data><data key="edge_relationship_type">input_to</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">Field offices enter SSA-1020-OCR application data into MAPS unless routed for WBDOC processing under stated conditions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20141" source="SVC_I1020" target="PROC_EXTRA_HELP"><data key="edge_relationship_id">REL20141</data><data key="edge_source_entity_id">SVC_I1020</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_EXTRA_HELP</data><data key="edge_operational_context">i1020 is the online Extra Help application channel.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20142" source="SVC_I1020" target="APP_MAPS"><data key="edge_relationship_id">REL20142</data><data key="edge_source_entity_id">SVC_I1020</data><data key="edge_relationship_type">application_data_later_managed_in</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">Once accepted, MAPS screens can query or change data from an i1020 application; POMS explicitly says i1020 does not use or interface with MAPS screens for initial input.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Do not interpret this as a direct screen-to-screen input interface.</data></edge><edge id="REL20143" source="APP_MAPS" target="APP_ORS"><data key="edge_relationship_id">REL20143</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">stores_application_copy_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">POMS requires printing the MAPS application so it is stored in the Online Retrieval System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20144" source="APP_MAPS" target="PROC_MAPS_VERIFICATION"><data key="edge_relationship_id">REL20144</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">executes</data><data key="edge_target_entity_id">PROC_MAPS_VERIFICATION</data><data key="edge_operational_context">MAPS compares application data with agency data and sends cases to verification when specified discrepancies affect eligibility.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20145" source="UI_MAPS_DEV_WORKSHEET" target="APP_MAPS"><data key="edge_relationship_id">REL20145</data><data key="edge_source_entity_id">UI_MAPS_DEV_WORKSHEET</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">MAPS creates verification issues on its Development Worksheet.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20146" source="ORG_WSU" target="PROC_MAPS_VERIFICATION"><data key="edge_relationship_id">REL20146</data><data key="edge_source_entity_id">ORG_WSU</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_MAPS_VERIFICATION</data><data key="edge_operational_context">MAPS can assign Extra Help verification work to a Workload Support Unit.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20147" source="ORG_SAU" target="APP_MAPS"><data key="edge_relationship_id">REL20147</data><data key="edge_source_entity_id">ORG_SAU</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">Subsidy Appeals Unit staff use MAPS in correction/appeals contexts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The source identifies SAU/MAPS operational use; exact organizational placement is not modeled.</data></edge><edge id="REL20148" source="APP_MAPS" target="DOM_MEDICARE"><data key="edge_relationship_id">REL20148</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">MAPS processes Medicare Part D Extra Help eligibility.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20149" source="DATA_MSP_OUTREACH_FILE" target="SYS_MBR"><data key="edge_relationship_id">REL20149</data><data key="edge_source_entity_id">DATA_MSP_OUTREACH_FILE</data><data key="edge_relationship_type">generated_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA uses MBR data to produce candidate outreach files.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20150" source="DATA_MSP_OUTREACH_FILE" target="SYS_SSR"><data key="edge_relationship_id">REL20150</data><data key="edge_source_entity_id">DATA_MSP_OUTREACH_FILE</data><data key="edge_relationship_type">generated_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA uses SSR data to produce candidate outreach files.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20151" source="DATA_MSP_OUTREACH_FILE" target="APP_MAPS"><data key="edge_relationship_id">REL20151</data><data key="edge_source_entity_id">DATA_MSP_OUTREACH_FILE</data><data key="edge_relationship_type">generated_from</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">SSA uses MAPS data to produce candidate outreach files.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20152" source="PROC_MSP_OUTREACH" target="DATA_MSP_OUTREACH_FILE"><data key="edge_relationship_id">REL20152</data><data key="edge_source_entity_id">PROC_MSP_OUTREACH</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_MSP_OUTREACH_FILE</data><data key="edge_operational_context">Outreach vendors use system-generated files to mail letters to potential eligibles.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20153" source="PROC_MSP_OUTREACH" target="DOM_MEDICARE"><data key="edge_relationship_id">REL20153</data><data key="edge_source_entity_id">PROC_MSP_OUTREACH</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">Outreach identifies potential MSP and Extra Help eligibles.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20154" source="PROC_EXTRA_HELP" target="EX_MSP_STATE_REFERRAL"><data key="edge_relationship_id">REL20154</data><data key="edge_source_entity_id">PROC_EXTRA_HELP</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">EX_MSP_STATE_REFERRAL</data><data key="edge_operational_context">An Extra Help application decision triggers transmission of referral data to the appropriate state unless the beneficiary objects.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20155" source="EX_MSP_STATE_REFERRAL" target="ORG_STATE_MEDICAID"><data key="edge_relationship_id">REL20155</data><data key="edge_source_entity_id">EX_MSP_STATE_REFERRAL</data><data key="edge_relationship_type">sends_to</data><data key="edge_target_entity_id">ORG_STATE_MEDICAID</data><data key="edge_operational_context">SSA sends Extra Help application decision data to the appropriate state Medicaid agency to begin MSP processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20156" source="EX_MSP_STATE_REFERRAL" target="ORG_STATE_MEDICAID"><data key="edge_relationship_id">REL20156</data><data key="edge_source_entity_id">EX_MSP_STATE_REFERRAL</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATE_MEDICAID</data><data key="edge_operational_context">State Medicaid agencies receive the referral and make MSP/Medicaid eligibility determinations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20157" source="ORG_CMS" target="APP_MAPS"><data key="edge_relationship_id">REL20157</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">provides_deemed_status_to</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">CMS notifies SSA of deemed Extra Help eligibility and the information is available in MAPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20158" source="PROC_PW_ACCRETION" target="PROC_STATE_BUYIN"><data key="edge_relationship_id">REL20158</data><data key="edge_source_entity_id">PROC_PW_ACCRETION</data><data key="edge_relationship_type">subprocess_of</data><data key="edge_target_entity_id">PROC_STATE_BUYIN</data><data key="edge_operational_context">Public Welfare accretion is a State Part B buy-in process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20159" source="PROC_PW_ACCRETION" target="IFACE_MCS_HI19"><data key="edge_relationship_id">REL20159</data><data key="edge_source_entity_id">PROC_PW_ACCRETION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">IFACE_MCS_HI19</data><data key="edge_operational_context">When using MCS, HI19 is used to initiate State buy-in.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20160" source="UI_CCE_HEALTH_INSURANCE" target="APP_CCE"><data key="edge_relationship_id">REL20160</data><data key="edge_source_entity_id">UI_CCE_HEALTH_INSURANCE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">CCE Health Insurance / Benefits Leads workflow includes the option to initiate State buy-in.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20161" source="PROC_PW_ACCRETION" target="UI_CCE_HEALTH_INSURANCE"><data key="edge_relationship_id">REL20161</data><data key="edge_source_entity_id">PROC_PW_ACCRETION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_CCE_HEALTH_INSURANCE</data><data key="edge_operational_context">When using CCE, staff choose Medicaid status and initiate State buy-in through the Health Insurance workflow.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20162" source="PROC_PW_ACCRETION" target="PROC_MALP"><data key="edge_relationship_id">REL20162</data><data key="edge_source_entity_id">PROC_PW_ACCRETION</data><data key="edge_relationship_type">may_invoke</data><data key="edge_target_entity_id">PROC_MALP</data><data key="edge_operational_context">For certain SSI recipients without a Title II application, MALP initiates Title II development or establishes the MBR for an uninsured individual.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20163" source="PROC_PW_ACCRETION" target="ORG_STATE_MEDICAID"><data key="edge_relationship_id">REL20163</data><data key="edge_source_entity_id">PROC_PW_ACCRETION</data><data key="edge_relationship_type">verifies_with</data><data key="edge_target_entity_id">ORG_STATE_MEDICAID</data><data key="edge_operational_context">In alert states and certain non-SSI cases, SSA verifies Medicaid eligibility with the state Medicaid agency before buy-in.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20164" source="PROC_PW_ACCRETION" target="APP_EP"><data key="edge_relationship_id">REL20164</data><data key="edge_source_entity_id">PROC_PW_ACCRETION</data><data key="edge_relationship_type">stores_verification_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">State Medicaid eligibility verification is documented on SSA-5002 and stored in Evidence Portal in specified cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20165" source="DATA_CMS1957" target="PROC_STATE_BUYIN"><data key="edge_relationship_id">REL20165</data><data key="edge_source_entity_id">DATA_CMS1957</data><data key="edge_relationship_type">formerly_supported</data><data key="edge_target_entity_id">PROC_STATE_BUYIN</data><data key="edge_operational_context">CMS-1957 historically facilitated escalation of State buy-in problems.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20166" source="PROC_SVB_CLAIM" target="DOM_SVB"><data key="edge_relationship_id">REL20166</data><data key="edge_source_entity_id">PROC_SVB_CLAIM</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SVB</data><data key="edge_operational_context">Process administers Title VIII Special Veterans Benefits claims.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20167" source="PROC_SVB_CLAIM" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">REL20167</data><data key="edge_source_entity_id">PROC_SVB_CLAIM</data><data key="edge_relationship_type">initially_handled_by</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">Servicing field offices process domestic SVB claims until foreign residency is established.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20168" source="PROC_SVB_CLAIM" target="ORG_SVB_CPS"><data key="edge_relationship_id">REL20168</data><data key="edge_source_entity_id">PROC_SVB_CLAIM</data><data key="edge_relationship_type">transfers_to</data><data key="edge_target_entity_id">ORG_SVB_CPS</data><data key="edge_operational_context">Central Processing Sites handle foreign-filed applications and actions after foreign residency is established.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20169" source="PROC_SVB_CLAIM" target="APP_MSSICS"><data key="edge_relationship_id">REL20169</data><data key="edge_source_entity_id">PROC_SVB_CLAIM</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS says SVB is paid through the SSI system and its update function is accessed through MSSICS/Direct SSR Update.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20170" source="FUNC_SVB_UPDATE" target="IFACE_SSI_DIRECT_SSR"><data key="edge_relationship_id">REL20170</data><data key="edge_source_entity_id">FUNC_SVB_UPDATE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_operational_context">The Special Veterans Benefit update function is selected from the Direct SSR Update menu.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20171" source="FUNC_SVB_UPDATE" target="SYS_SSR"><data key="edge_relationship_id">REL20171</data><data key="edge_source_entity_id">FUNC_SVB_UPDATE</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The SVB update function applies the Title VIII indicator and related record actions to the SSR.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20172" source="DATA_SVB_INDICATOR" target="SYS_SSR"><data key="edge_relationship_id">REL20172</data><data key="edge_source_entity_id">DATA_SVB_INDICATOR</data><data key="edge_relationship_type">stored_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">A permanent Title VIII/SVB indicator is posted to the record.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20173" source="UI_SSIRD" target="DATA_SVB_INDICATOR"><data key="edge_relationship_id">REL20173</data><data key="edge_source_entity_id">UI_SSIRD</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">DATA_SVB_INDICATOR</data><data key="edge_operational_context">The SVB indicator appears in the Case Header segment of SSIRD.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20174" source="APP_FONS" target="PROC_SVB_CLAIM"><data key="edge_relationship_id">REL20174</data><data key="edge_source_entity_id">APP_FONS</data><data key="edge_relationship_type">generates_manual_notices_for</data><data key="edge_target_entity_id">PROC_SVB_CLAIM</data><data key="edge_operational_context">SVB automated notices are suppressed and staff prepare manual notices in FONS.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20175" source="DB_SVB_CLAIMS_MI" target="PROC_SVB_CLAIM"><data key="edge_relationship_id">REL20175</data><data key="edge_source_entity_id">DB_SVB_CLAIMS_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_SVB_CLAIM</data><data key="edge_operational_context">The current SORN identifies a Title VIII SVB claims development and management information record system.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">SORN title establishes business support, not a direct technical interface.</data></edge><edge id="REL20176" source="PROC_BL_RESIDUAL_SUPPORT" target="DOM_BLACK_LUNG"><data key="edge_relationship_id">REL20176</data><data key="edge_source_entity_id">PROC_BL_RESIDUAL_SUPPORT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_BLACK_LUNG</data><data key="edge_operational_context">SSA continues designated post-entitlement actions after primary Part B administration transferred to DOL.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20177" source="PROC_BL_RESIDUAL_SUPPORT" target="ORG_DOL"><data key="edge_relationship_id">REL20177</data><data key="edge_source_entity_id">PROC_BL_RESIDUAL_SUPPORT</data><data key="edge_relationship_type">coordinates_with</data><data key="edge_target_entity_id">ORG_DOL</data><data key="edge_operational_context">SSA residual Part B work operates under a reimbursable agreement with DOL.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20178" source="EX_CMA1015_DOL_BLB" target="DOM_TITLE16"><data key="edge_relationship_id">REL20178</data><data key="edge_source_entity_id">EX_CMA1015_DOL_BLB</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">The DOL Part B match is used to verify that recipients receive the correct SSI payment amount.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20179" source="DATA_DOL_BLC_MONTHLY_FILE" target="ORG_DOL"><data key="edge_relationship_id">REL20179</data><data key="edge_source_entity_id">DATA_DOL_BLC_MONTHLY_FILE</data><data key="edge_relationship_type">sent_by</data><data key="edge_target_entity_id">ORG_DOL</data><data key="edge_operational_context">DOL provides SSA a monthly payment file of live miners entitled to Part C Black Lung benefits.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20180" source="DATA_DOL_BLC_MONTHLY_FILE" target="SYS_MBR"><data key="edge_relationship_id">REL20180</data><data key="edge_source_entity_id">DATA_DOL_BLC_MONTHLY_FILE</data><data key="edge_relationship_type">matched_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">DOL Part C records are matched against MBR records to generate alerts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20181" source="DATA_DOL_BLC_MONTHLY_FILE" target="EX_CMA1003_DOL_BLC"><data key="edge_relationship_id">REL20181</data><data key="edge_source_entity_id">DATA_DOL_BLC_MONTHLY_FILE</data><data key="edge_relationship_type">source_file_for</data><data key="edge_target_entity_id">EX_CMA1003_DOL_BLC</data><data key="edge_operational_context">The DOL monthly Part C payment information underlies the SSA Black Lung Part C matching/alert process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20182" source="PROC_BL_PARTC_OFFSET" target="APP_ICF_T2"><data key="edge_relationship_id">REL20182</data><data key="edge_source_entity_id">PROC_BL_PARTC_OFFSET</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ICF_T2</data><data key="edge_operational_context">POMS directs staff to update Black Lung Part C offset through ICF WC.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20183" source="PROC_BL_PARTC_OFFSET" target="DATA_DOL_BLC_MONTHLY_FILE"><data key="edge_relationship_id">REL20183</data><data key="edge_source_entity_id">PROC_BL_PARTC_OFFSET</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_DOL_BLC_MONTHLY_FILE</data><data key="edge_operational_context">The monthly DOL Part C payment file serves as a third-party report for offset processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL20184" source="DB_BLACK_LUNG_PAYMENT" target="DB_BL_PAYMENT_MASTER"><data key="edge_relationship_id">REL20184</data><data key="edge_source_entity_id">DB_BLACK_LUNG_PAYMENT</data><data key="edge_relationship_type">historically_contains</data><data key="edge_target_entity_id">DB_BL_PAYMENT_MASTER</data><data key="edge_operational_context">The detailed BLPS SORN describes a Payment Master Record as one of two internal files.</data><data key="edge_observed_as_of">1987-03-25</data><data key="edge_confidence">3</data><data key="edge_notes">Historical internal structure only; exact 2026 decomposition is unverified.</data></edge><edge id="REL20185" source="DB_BLACK_LUNG_PAYMENT" target="DB_BL_BENEFIT_MASTER"><data key="edge_relationship_id">REL20185</data><data key="edge_source_entity_id">DB_BLACK_LUNG_PAYMENT</data><data key="edge_relationship_type">historically_contains</data><data key="edge_target_entity_id">DB_BL_BENEFIT_MASTER</data><data key="edge_operational_context">The detailed BLPS SORN describes a Benefit Master Record as one of two internal files.</data><data key="edge_observed_as_of">1987-03-25</data><data key="edge_confidence">3</data><data key="edge_notes">Historical internal structure only; exact 2026 decomposition is unverified.</data></edge><edge id="REL20186" source="DB_BL_PAYMENT_MASTER" target="DB_BL_BENEFIT_MASTER"><data key="edge_relationship_id">REL20186</data><data key="edge_source_entity_id">DB_BL_PAYMENT_MASTER</data><data key="edge_relationship_type">historically_matched_monthly_with</data><data key="edge_target_entity_id">DB_BL_BENEFIT_MASTER</data><data key="edge_operational_context">The 1987 SORN states the two BLPS files were matched once a month.</data><data key="edge_observed_as_of">1987-03-25</data><data key="edge_confidence">3</data><data key="edge_notes">Historical architecture; current implementation not reverified.</data></edge><edge id="REL202" source="APP_SSI_PAYHIST_CORR" target="APP_SSI_FINVERIFY"><data key="edge_relationship_id">REL202</data><data key="edge_source_entity_id">APP_SSI_PAYHIST_CORR</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">APP_SSI_FINVERIFY</data><data key="edge_operational_context">Corrected Treasury items feed Financial Verification nightly</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL203" source="APP_SSI_FINVERIFY" target="ORG_TREASURY"><data key="edge_relationship_id">REL203</data><data key="edge_source_entity_id">APP_SSI_FINVERIFY</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Processes Treasury input files</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL204" source="APP_PAYMT" target="ORG_TREASURY"><data key="edge_relationship_id">REL204</data><data key="edge_source_entity_id">APP_PAYMT</data><data key="edge_relationship_type">sends_payment_files_to</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">Produces daily and monthly SSI payment files for Treasury</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL205" source="APP_SSI_TREASURY" target="SYS_SSR"><data key="edge_relationship_id">REL205</data><data key="edge_source_entity_id">APP_SSI_TREASURY</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Reads monthly SSR Master</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL206" source="APP_SSI_TREASURY" target="EX_SDX"><data key="edge_relationship_id">REL206</data><data key="edge_source_entity_id">APP_SSI_TREASURY</data><data key="edge_relationship_type">distributes_changes_to</data><data key="edge_target_entity_id">EX_SDX</data><data key="edge_operational_context">Distributes payment-related change records to SDX</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL207" source="APP_SSI_TREASURY" target="APP_DAILY_FAX"><data key="edge_relationship_id">REL207</data><data key="edge_source_entity_id">APP_SSI_TREASURY</data><data key="edge_relationship_type">distributes_changes_to</data><data key="edge_target_entity_id">APP_DAILY_FAX</data><data key="edge_operational_context">Distributes payment-related change records to Daily/Monthly FAX</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL208" source="APP_SSI_REDET" target="APP_MSSICS"><data key="edge_relationship_id">REL208</data><data key="edge_source_entity_id">APP_SSI_REDET</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS directs redeterminations into the SSI Claims System/MSSICS screens</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL209" source="APP_SSIMWV" target="SYS_SSR"><data key="edge_relationship_id">REL209</data><data key="edge_source_entity_id">APP_SSIMWV</data><data key="edge_relationship_type">posts_wages_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS uses SSIMWV for monthly wage reports and SSI record updates</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_001" source="APP_ICLAIM" target="APP_I3368"><data key="edge_relationship_id">REL20_001</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">launches</data><data key="edge_target_entity_id">APP_I3368</data><data key="edge_operational_context">Current POMS says the i3368 opens after an Internet user submits iClaim.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_002" source="APP_I3368" target="DB_INTERNET_REPORT"><data key="edge_relationship_id">REL20_002</data><data key="edge_source_entity_id">APP_I3368</data><data key="edge_relationship_type">stores_partial_in</data><data key="edge_target_entity_id">DB_INTERNET_REPORT</data><data key="edge_operational_context">Unsubmitted i3368 partials are retained, archived and later purged from the Internet Report Database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_003" source="APP_I3820" target="DB_INTERNET_REPORT"><data key="edge_relationship_id">REL20_003</data><data key="edge_source_entity_id">APP_I3820</data><data key="edge_relationship_type">stores_partial_in</data><data key="edge_target_entity_id">DB_INTERNET_REPORT</data><data key="edge_operational_context">Unsubmitted i3820 partials are retained, archived and later purged from the Internet Report Database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_004" source="APP_I3441" target="DB_INTERNET_REPORT"><data key="edge_relationship_id">REL20_004</data><data key="edge_source_entity_id">APP_I3441</data><data key="edge_relationship_type">stores_partial_in</data><data key="edge_target_entity_id">DB_INTERNET_REPORT</data><data key="edge_operational_context">Unsubmitted i3441 partials are retained, archived and later purged from the Internet Report Database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_005" source="APP_IAPPEALS" target="APP_I3441"><data key="edge_relationship_id">REL20_005</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">launches</data><data key="edge_target_entity_id">APP_I3441</data><data key="edge_operational_context">iAppeals screening and appeal submission gives users access to the i3441.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_006" source="APP_I3368" target="APP_EDCS"><data key="edge_relationship_id">REL20_006</data><data key="edge_source_entity_id">APP_I3368</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Submitted i3368 data can propagate to EDCS; partials cannot.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_007" source="APP_I3820" target="APP_EDCS"><data key="edge_relationship_id">REL20_007</data><data key="edge_source_entity_id">APP_I3820</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Current i3820 procedures direct propagation into EDCS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_008" source="APP_I3441" target="APP_EDCS"><data key="edge_relationship_id">REL20_008</data><data key="edge_source_entity_id">APP_I3441</data><data key="edge_relationship_type">propagates_data_to</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Appeal intake procedures create the appeal case in EDCS and propagate the i3441.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_009" source="APP_IQF" target="DB_INTERNET_REPORT"><data key="edge_relationship_id">REL20_009</data><data key="edge_source_entity_id">APP_IQF</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_INTERNET_REPORT</data><data key="edge_operational_context">IQF queries access Internet Report Database information and control Internet workloads.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_010" source="APP_IQF" target="TECH_PCOM"><data key="edge_relationship_id">REL20_010</data><data key="edge_source_entity_id">APP_IQF</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">TECH_PCOM</data><data key="edge_operational_context">POMS routes IQF access through SSA mainframe shared processes / PCOM workflows.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_011" source="APP_IWMI" target="TECH_PCOM"><data key="edge_relationship_id">REL20_011</data><data key="edge_source_entity_id">APP_IWMI</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">TECH_PCOM</data><data key="edge_operational_context">POMS instructs users to open PCOM and select WMS listings to request iWMI.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_012" source="APP_IWMI" target="DATA_SUBMITTED_IDR_LIST"><data key="edge_relationship_id">REL20_012</data><data key="edge_source_entity_id">APP_IWMI</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_SUBMITTED_IDR_LIST</data><data key="edge_operational_context">iWMI provides the Submitted Disability Reports Listing of received Internet transmissions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_013" source="APP_I3368" target="DATA_SUBMITTED_IDR_LIST"><data key="edge_relationship_id">REL20_013</data><data key="edge_source_entity_id">APP_I3368</data><data key="edge_relationship_type">appears_on</data><data key="edge_target_entity_id">DATA_SUBMITTED_IDR_LIST</data><data key="edge_operational_context">Submitted Internet Disability Reports are represented on the iWMI submitted-report workload listing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">POMS describes the listing generically for IDRs; this relationship does not imply identical fields for every report type.</data></edge><edge id="REL20_014" source="APP_I3820" target="DATA_SUBMITTED_IDR_LIST"><data key="edge_relationship_id">REL20_014</data><data key="edge_source_entity_id">APP_I3820</data><data key="edge_relationship_type">appears_on</data><data key="edge_target_entity_id">DATA_SUBMITTED_IDR_LIST</data><data key="edge_operational_context">Submitted Internet Disability Reports are represented on the iWMI submitted-report workload listing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">POMS describes the listing generically for IDRs; this relationship does not imply identical fields for every report type.</data></edge><edge id="REL20_015" source="APP_I3441" target="DATA_SUBMITTED_IDR_LIST"><data key="edge_relationship_id">REL20_015</data><data key="edge_source_entity_id">APP_I3441</data><data key="edge_relationship_type">appears_on</data><data key="edge_target_entity_id">DATA_SUBMITTED_IDR_LIST</data><data key="edge_operational_context">Submitted Internet Disability Reports are represented on the iWMI submitted-report workload listing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">POMS describes the listing generically for IDRs; this relationship does not imply identical fields for every report type.</data></edge><edge id="REL20_016" source="APP_I3368" target="APP_CAL_SELECTION"><data key="edge_relationship_id">REL20_016</data><data key="edge_source_entity_id">APP_I3368</data><data key="edge_relationship_type">calls</data><data key="edge_target_entity_id">APP_CAL_SELECTION</data><data key="edge_operational_context">After medical conditions are entered, i3368 calls CAL selection software.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_017" source="APP_CAL_SELECTION" target="APP_QDD_MODEL"><data key="edge_relationship_id">REL20_017</data><data key="edge_source_entity_id">APP_CAL_SELECTION</data><data key="edge_relationship_type">housed_within</data><data key="edge_target_entity_id">APP_QDD_MODEL</data><data key="edge_operational_context">POMS describes CAL selection software as housed within the Predictive Model; the Atlas maps that term to the QDD predictive-model entity.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_018" source="APP_CAL_SELECTION" target="APP_EDCS"><data key="edge_relationship_id">REL20_018</data><data key="edge_source_entity_id">APP_CAL_SELECTION</data><data key="edge_relationship_type">identifies_cases_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">CAL software identifies EDCS cases for fast-track processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_019" source="APP_QDD_MODEL" target="APP_EDCS"><data key="edge_relationship_id">REL20_019</data><data key="edge_source_entity_id">APP_QDD_MODEL</data><data key="edge_relationship_type">identifies_cases_in</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">The QDD predictive model identifies initial EDCS cases for QDD fast-track processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_020" source="PLAT_EDIB" target="APP_ARPS"><data key="edge_relationship_id">REL20_020</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_ARPS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_021" source="PLAT_EDIB" target="DB_ARPS_MI"><data key="edge_relationship_id">REL20_021</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_ARPS_MI</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_022" source="PLAT_EDIB" target="APP_CFRMS"><data key="edge_relationship_id">REL20_022</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_CFRMS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_023" source="PLAT_EDIB" target="APP_CPMS"><data key="edge_relationship_id">REL20_023</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_024" source="PLAT_EDIB" target="DB_CPMS_MI"><data key="edge_relationship_id">REL20_024</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_CPMS_MI</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_025" source="PLAT_EDIB" target="DB_CAL_QDD_DM"><data key="edge_relationship_id">REL20_025</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_CAL_QDD_DM</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_026" source="PLAT_EDIB" target="DB_DISABILITY_DATABASE_SYSTEM"><data key="edge_relationship_id">REL20_026</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_DISABILITY_DATABASE_SYSTEM</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_027" source="PLAT_EDIB" target="DB_DIODS"><data key="edge_relationship_id">REL20_027</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_DIODS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_028" source="PLAT_EDIB" target="APP_DGS"><data key="edge_relationship_id">REL20_028</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_DGS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_029" source="PLAT_EDIB" target="REPO_DMA_ECLIENT"><data key="edge_relationship_id">REL20_029</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">REPO_DMA_ECLIENT</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_030" source="PLAT_EDIB" target="DB_ECAT_MI"><data key="edge_relationship_id">REL20_030</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_ECAT_MI</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_031" source="PLAT_EDIB" target="DB_ERE_MI"><data key="edge_relationship_id">REL20_031</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_ERE_MI</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_032" source="PLAT_EDIB" target="DB_HIT_MI"><data key="edge_relationship_id">REL20_032</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_HIT_MI</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_033" source="PLAT_EDIB" target="APP_LAWS"><data key="edge_relationship_id">REL20_033</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_LAWS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_034" source="PLAT_EDIB" target="APP_MIDAS"><data key="edge_relationship_id">REL20_034</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_MIDAS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_035" source="PLAT_EDIB" target="APP_NDDSS"><data key="edge_relationship_id">REL20_035</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_036" source="PLAT_EDIB" target="APP_NVF_FEEDS"><data key="edge_relationship_id">REL20_036</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_NVF_FEEDS</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_037" source="PLAT_EDIB" target="APP_NVF_MGMT"><data key="edge_relationship_id">REL20_037</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_NVF_MGMT</data><data key="edge_operational_context">The 2018 eDIB PIA explicitly lists this system, repository, datamart, management-information subsystem or application inside the eDIB authorization boundary.</data><data key="edge_observed_as_of">2018-02-01</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture boundary only; current status must be established separately.</data></edge><edge id="REL20_038" source="APP_RZWIZ" target="SYS_SSR"><data key="edge_relationship_id">REL20_038</data><data key="edge_source_entity_id">APP_RZWIZ</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">RZwiz automatically retrieves or reviews this record/query as part of SSI redetermination interview support.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_039" source="APP_RZWIZ" target="QRY_SSID"><data key="edge_relationship_id">REL20_039</data><data key="edge_source_entity_id">APP_RZWIZ</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">QRY_SSID</data><data key="edge_operational_context">RZwiz automatically retrieves or reviews this record/query as part of SSI redetermination interview support.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_040" source="APP_RZWIZ" target="QRY_DEQY"><data key="edge_relationship_id">REL20_040</data><data key="edge_source_entity_id">APP_RZWIZ</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">RZwiz automatically retrieves or reviews this record/query as part of SSI redetermination interview support.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_041" source="APP_RZWIZ" target="QRY_SEQY"><data key="edge_relationship_id">REL20_041</data><data key="edge_source_entity_id">APP_RZWIZ</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">QRY_SEQY</data><data key="edge_operational_context">RZwiz automatically retrieves or reviews this record/query as part of SSI redetermination interview support.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_042" source="APP_RZWIZ" target="DB_NDNH"><data key="edge_relationship_id">REL20_042</data><data key="edge_source_entity_id">APP_RZWIZ</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">RZwiz automatically retrieves or reviews this record/query as part of SSI redetermination interview support.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_043" source="APP_RZWIZ" target="TECH_PCOM"><data key="edge_relationship_id">REL20_043</data><data key="edge_source_entity_id">APP_RZWIZ</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">TECH_PCOM</data><data key="edge_operational_context">RZwiz instructions require a PCOM session when requesting queries.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_044" source="QRY_SSID" target="SYS_SSR"><data key="edge_relationship_id">REL20_044</data><data key="edge_source_entity_id">QRY_SSID</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSID presents Supplemental Security Record information for review.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_045" source="QRY_FACT" target="SYS_MBR"><data key="edge_relationship_id">REL20_045</data><data key="edge_source_entity_id">QRY_FACT</data><data key="edge_relationship_type">displays</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">FACT is the full account / full MBR query used in Title II workflows.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_046" source="APP_CATS" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_046</data><data key="edge_source_entity_id">APP_CATS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_047" source="APP_DDSQ" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_047</data><data key="edge_source_entity_id">APP_DDSQ</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_048" source="QRY_FACT" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_048</data><data key="edge_source_entity_id">QRY_FACT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_049" source="APP_MCS" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_049</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_050" source="APP_MSSICS" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_050</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_051" source="APP_MDW_AI" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_051</data><data key="edge_source_entity_id">APP_MDW_AI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_052" source="QRY_OFFLINE_CCTL" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_052</data><data key="edge_source_entity_id">QRY_OFFLINE_CCTL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_053" source="QRY_OHAQ" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_053</data><data key="edge_source_entity_id">QRY_OHAQ</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_054" source="APP_PCACS" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_054</data><data key="edge_source_entity_id">APP_PCACS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_055" source="QRY_QRSL" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_055</data><data key="edge_source_entity_id">QRY_QRSL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_056" source="QRY_SSID" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_056</data><data key="edge_source_entity_id">QRY_SSID</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_057" source="APP_ROQS" target="PROC_MEDICAL_FOLDER_SEARCH"><data key="edge_relationship_id">REL20_057</data><data key="edge_source_entity_id">APP_ROQS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MEDICAL_FOLDER_SEARCH</data><data key="edge_operational_context">POMS DI 13015.080 directs field-office staff to query this source when attempting to locate a medical folder.</data><data key="edge_observed_as_of">2024-02-06</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_058" source="APP_CATS" target="SYS_MBR"><data key="edge_relationship_id">REL20_058</data><data key="edge_source_entity_id">APP_CATS</data><data key="edge_relationship_type">receives_claim_data_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">CATS records include beneficiary and claims-related information from the Master Beneficiary Record.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_059" source="APP_CATS" target="SYS_SSR"><data key="edge_relationship_id">REL20_059</data><data key="edge_source_entity_id">APP_CATS</data><data key="edge_relationship_type">receives_claim_data_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">CATS records include beneficiary and claims-related information from the Supplemental Security Income Record.</data><data key="edge_observed_as_of">2018-11-01</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_060" source="APP_800_CLAIMS" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL20_060</data><data key="edge_source_entity_id">APP_800_CLAIMS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">PIA describes claims status as an automated application within the National 800-Number.</data><data key="edge_observed_as_of">2008-02-15</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_061" source="APP_800_VOICE" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL20_061</data><data key="edge_source_entity_id">APP_800_VOICE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">PIA states TVDC enhances the N8NN automated telephone application system.</data><data key="edge_observed_as_of">2008-10-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_062" source="APP_800_EMPVER" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL20_062</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">Employer verification is an automated telephone application in the National 800 Number environment.</data><data key="edge_observed_as_of">2025-02-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_063" source="APP_800_EMPVER" target="APP_SSNVS"><data key="edge_relationship_id">REL20_063</data><data key="edge_source_entity_id">APP_800_EMPVER</data><data key="edge_relationship_type">uses_registration_for</data><data key="edge_target_entity_id">APP_SSNVS</data><data key="edge_operational_context">PIA states TNEV is limited to users registered for SSNVS and uses those service credentials for verification.</data><data key="edge_observed_as_of">2025-02-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL20_064" source="CON_HV_PRINTER_RFI_2026" target="ORG_DDS"><data key="edge_relationship_id">REL20_064</data><data key="edge_source_entity_id">CON_HV_PRINTER_RFI_2026</data><data key="edge_relationship_type">intended_to_support</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">SAM.gov says the RFI seeks high-volume printers for SSA offices nationwide to help DDS offices improve service.</data><data key="edge_observed_as_of">2026-07-09</data><data key="edge_confidence">5</data><data key="edge_notes">Procurement intent only; no award or deployment inferred.</data></edge><edge id="REL210" source="APP_SSIMWV" target="APP_ORS"><data key="edge_relationship_id">REL210</data><data key="edge_source_entity_id">APP_SSIMWV</data><data key="edge_relationship_type">archives_receipts_to</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Current POMS says SSIMWV receipts are archived to ORS</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL211" source="APP_MYWR" target="SYS_SSR"><data key="edge_relationship_id">REL211</data><data key="edge_source_entity_id">APP_MYWR</data><data key="edge_relationship_type">posts_wages_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS recognizes myWR-submitted wages as posted to SSI claims/SSR</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL212" source="APP_MYWR" target="APP_EWORK"><data key="edge_relationship_id">REL212</data><data key="edge_source_entity_id">APP_MYWR</data><data key="edge_relationship_type">passes_wage_data_to</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">Current wage instructions support cross-program wage use; exact implementation boundary remains application-dependent</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL213" source="APP_SSAMWR" target="SYS_SSR"><data key="edge_relationship_id">REL213</data><data key="edge_source_entity_id">APP_SSAMWR</data><data key="edge_relationship_type">posts_wages_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Mobile wage reports update SSI wage information</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL214" source="APP_SSITWR" target="SYS_SSR"><data key="edge_relationship_id">REL214</data><data key="edge_source_entity_id">APP_SSITWR</data><data key="edge_relationship_type">posts_wages_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Telephone wage reports update SSI wage information</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL215" source="APP_WEIA" target="EX_PIE"><data key="edge_relationship_id">REL215</data><data key="edge_source_entity_id">APP_WEIA</data><data key="edge_relationship_type">authorizes</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">WEIA records authorization needed for payroll-provider exchange</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL216" source="EX_PIE" target="APP_MSSICS"><data key="edge_relationship_id">REL216</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">PIE automatically updates wage/employment information to active SSI Claims System cases when system conditions are met</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL217" source="EX_PIE" target="DOM_EARNINGS"><data key="edge_relationship_id">REL217</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">PIE provides wage and employment information from payroll data providers</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL218" source="APP_MSSICS" target="DB_EAP"><data key="edge_relationship_id">REL218</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">DB_EAP</data><data key="edge_operational_context">MSSICS EAP process checks EAP database before allowing payment</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL219" source="APP_MSSICS" target="APP_TPPS"><data key="edge_relationship_id">REL219</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">sends_eap_to</data><data key="edge_target_entity_id">APP_TPPS</data><data key="edge_operational_context">EAP data propagate from MSSICS to TPPS after same-day establishment/approval/transmission</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL220" source="APP_MSSICS" target="SYS_SSR"><data key="edge_relationship_id">REL220</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">EAP data must be transmitted to SSR the same day and are sent in overnight processing</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL221" source="DB_SUMS_T16_PEODS" target="APP_SSTNG"><data key="edge_relationship_id">REL221</data><data key="edge_source_entity_id">DB_SUMS_T16_PEODS</data><data key="edge_relationship_type">contains_data_from</data><data key="edge_target_entity_id">APP_SSTNG</data><data key="edge_operational_context">PEODS explicitly includes Starz &amp; Stripes workload-control data</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL222" source="DB_T16_DW_STAGING" target="DB_WMDW"><data key="edge_relationship_id">REL222</data><data key="edge_source_entity_id">DB_T16_DW_STAGING</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DB_WMDW</data><data key="edge_operational_context">Current inventory says staging instance provides Title XVI processing-time data to WMDW</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL223" source="DB_SSRPT" target="SYS_SSR"><data key="edge_relationship_id">REL223</data><data key="edge_source_entity_id">DB_SSRPT</data><data key="edge_relationship_type">stages_updates_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Holds temporary SSR images before nightly update to actual SSR</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL224" source="STRUCT_DSPE" target="SYS_SSR"><data key="edge_relationship_id">REL224</data><data key="edge_source_entity_id">STRUCT_DSPE</data><data key="edge_relationship_type">is_subsection_of</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Data.gov defines DSPE as a post-eligibility subsection of SSR</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL225" source="DB_SSI_PE_REJECT_PROG" target="SYS_SSR"><data key="edge_relationship_id">REL225</data><data key="edge_source_entity_id">DB_SSI_PE_REJECT_PROG</data><data key="edge_relationship_type">reports_failed_updates_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Lists batch PE transactions that fail to update SSR</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL226" source="DB_SSI_PE_REJECT_MI" target="SYS_SSR"><data key="edge_relationship_id">REL226</data><data key="edge_source_entity_id">DB_SSI_PE_REJECT_MI</data><data key="edge_relationship_type">reports_failed_updates_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">MI lists batch PE transactions that fail to update SSR</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL227" source="DB_T16_FO_DIARY_PROG" target="DOM_TITLE16"><data key="edge_relationship_id">REL227</data><data key="edge_source_entity_id">DB_T16_FO_DIARY_PROG</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Weekly pending diaries used to control SSI workloads</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL228" source="DB_T16_FO_DIARY_MI" target="DOM_TITLE16"><data key="edge_relationship_id">REL228</data><data key="edge_source_entity_id">DB_T16_FO_DIARY_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Weekly pending diaries used to control SSI workloads</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL229" source="DB_BCAS_T16" target="DOM_TITLE16"><data key="edge_relationship_id">REL229</data><data key="edge_source_entity_id">DB_BCAS_T16</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Stores Title XVI payment-certification information</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL230" source="DB_AFI_MI" target="APP_AFII"><data key="edge_relationship_id">REL230</data><data key="edge_source_entity_id">DB_AFI_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_AFII</data><data key="edge_operational_context">Management information covers financial-institution requests/responses for Title XVI eligibility</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL231" source="EX_MEF_SSR_MATCH" target="SYS_MEF"><data key="edge_relationship_id">REL231</data><data key="edge_source_entity_id">EX_MEF_SSR_MATCH</data><data key="edge_relationship_type">matches</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Semiannual match uses Master Earnings File</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL232" source="EX_MEF_SSR_MATCH" target="SYS_SSR"><data key="edge_relationship_id">REL232</data><data key="edge_source_entity_id">EX_MEF_SSR_MATCH</data><data key="edge_relationship_type">matches</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Semiannual match uses Supplemental Security Record</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL233" source="EX_MEF_SSR_MATCH" target="DOM_TITLE16"><data key="edge_relationship_id">REL233</data><data key="edge_source_entity_id">EX_MEF_SSR_MATCH</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Identifies discrepant earnings for SSI-eligible persons</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL234" source="EX_SSI_IRS_1099" target="DOM_TITLE16"><data key="edge_relationship_id">REL234</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">sends_finder_data_from</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">SSA sends a Title XVI finder file to IRS</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL235" source="EX_SSI_IRS_1099" target="ORG_IRS"><data key="edge_relationship_id">REL235</data><data key="edge_source_entity_id">EX_SSI_IRS_1099</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">IRS returns 1099 information to SSA</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL236" source="EX_OCSE_SSI_WAGE_ALERT" target="ORG_OCSE"><data key="edge_relationship_id">REL236</data><data key="edge_source_entity_id">EX_OCSE_SSI_WAGE_ALERT</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">OCSE provides state/federal wage and unemployment data used in the quarterly SSI match</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL237" source="EX_OCSE_SSI_WAGE_ALERT" target="DOM_TITLE16"><data key="edge_relationship_id">REL237</data><data key="edge_source_entity_id">EX_OCSE_SSI_WAGE_ALERT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Detects possible SSI overpayments from unreported wage/unemployment data</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL238" source="EX_T16_OPM" target="ORG_OPM"><data key="edge_relationship_id">REL238</data><data key="edge_source_entity_id">EX_T16_OPM</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_OPM</data><data key="edge_operational_context">Monthly OPM Civil Service benefit/payment data</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL239" source="EX_T16_OPM" target="DOM_TITLE16"><data key="edge_relationship_id">REL239</data><data key="edge_source_entity_id">EX_T16_OPM</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Used to verify SSI eligibility factors</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL240" source="SYS_NUMIDENT" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL240</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">authoritative_store_for</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">SSA Open Data identifies Numident as the database system of record for enumeration data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL241" source="APP_SSNEC" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL241</data><data key="edge_source_entity_id">APP_SSNEC</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">SSNEC architecture assigns SSNs, issues cards and establishes the card print file.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Historical PIA architecture; does not establish the exact 2026 component boundary.</data></edge><edge id="REL242" source="APP_SSNAP" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL242</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">Current POMS uses SSNAP for electronic SSN card applications and record maintenance.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL243" source="APP_SSNAP" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL243</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS directs technicians to create new Numident iterations or use NCP in SSNAP for documented corrections.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL244" source="APP_IRON" target="APP_SSNAP"><data key="edge_relationship_id">REL244</data><data key="edge_source_entity_id">APP_IRON</data><data key="edge_relationship_type">provides_source_documents_to</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Paper SS-5 and microprint records used for correction review are available in IRON; links are available in SSNAP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL245" source="APP_SS5_REPRINTS" target="APP_SSNAP"><data key="edge_relationship_id">REL245</data><data key="edge_source_entity_id">APP_SS5_REPRINTS</data><data key="edge_relationship_type">provides_source_documents_to</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">SS-5 Reprints provides prior application records used for Numident correction review through SSNAP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL246" source="PROC_NCP" target="APP_SSNAP"><data key="edge_relationship_id">REL246</data><data key="edge_source_entity_id">PROC_NCP</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">POMS explicitly identifies Numident Correction Processing as a function in SSNAP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL247" source="PROC_NCP" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL247</data><data key="edge_source_entity_id">PROC_NCP</data><data key="edge_relationship_type">corrects</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">NCP corrects documented keying errors on an existing Numident iteration.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL248" source="DB_SSNAP_TX" target="APP_SSNAP"><data key="edge_relationship_id">REL248</data><data key="edge_source_entity_id">DB_SSNAP_TX</data><data key="edge_relationship_type">stores_transactions_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">SSA inventories a database storing data for all transactions in the enumeration process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL249" source="DB_SSNAP_AUDIT" target="APP_SSNAP"><data key="edge_relationship_id">REL249</data><data key="edge_source_entity_id">DB_SSNAP_AUDIT</data><data key="edge_relationship_type">logs_transactions_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">SSA inventories a database that logs enumeration transactions processed by SSNAP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL250" source="DB_SSNAP_MI" target="APP_SSNAP"><data key="edge_relationship_id">REL250</data><data key="edge_source_entity_id">DB_SSNAP_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">SSA inventories SSN Application Process MI as information about the enumeration process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL251" source="DB_SSNAP_MI_ODS" target="APP_SSNAP"><data key="edge_relationship_id">REL251</data><data key="edge_source_entity_id">DB_SSNAP_MI_ODS</data><data key="edge_relationship_type">provides_reporting_for</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Enumeration ODS supports ad hoc query and standard MI reports.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL252" source="DB_SSNAP_MI_ODS" target="TECH_DB2"><data key="edge_relationship_id">REL252</data><data key="edge_source_entity_id">DB_SSNAP_MI_ODS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">SSA explicitly describes the Enumeration ODS as being in DB2.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL253" source="DB_SSNAP_MI_ODS" target="ARCH_SUMS"><data key="edge_relationship_id">REL253</data><data key="edge_source_entity_id">DB_SSNAP_MI_ODS</data><data key="edge_relationship_type">uses_architecture</data><data key="edge_target_entity_id">ARCH_SUMS</data><data key="edge_operational_context">SSA explicitly says the ODS uses SUMS standards and architecture.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL254" source="DB_ENUM_WAREHOUSE" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL254</data><data key="edge_source_entity_id">DB_ENUM_WAREHOUSE</data><data key="edge_relationship_type">supports_workload_control_for</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">Enumeration Warehouse stores workload-control information for employees managing enumeration workloads.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL255" source="APP_OSSNAP" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL255</data><data key="edge_source_entity_id">APP_OSSNAP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">oSSNAP supports online original/replacement SSN card application processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL256" source="APP_ISSNRC" target="APP_OSSNAP"><data key="edge_relationship_id">REL256</data><data key="edge_source_entity_id">APP_ISSNRC</data><data key="edge_relationship_type">integrated_into</data><data key="edge_target_entity_id">APP_OSSNAP</data><data key="edge_operational_context">Effective January 31, 2026, iSSNRC functionality was integrated into oSSNAP as the authenticated self-service path.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL257" source="EX_EAB" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL257</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">EAB permits automated newborn SSN applications through state birth-registration processes.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL258" source="EX_EAB" target="ORG_STATE_BVS"><data key="edge_relationship_id">REL258</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">State vital records agencies electronically transmit EAB records to SSA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL259" source="EX_EAB" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL259</data><data key="edge_source_entity_id">EX_EAB</data><data key="edge_relationship_type">posts_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">POMS states EAB records post to the Numident; an existing SSN can receive the EAB record without a new card.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL260" source="EX_EAE" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL260</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">EAE allows automated SSN assignment or replacement-card issuance for admitted lawful permanent residents.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL261" source="EX_EAE" target="ORG_DOS"><data key="edge_relationship_id">REL261</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_DOS</data><data key="edge_operational_context">DoS collects enumeration data during the immigrant visa process and transmits it to DHS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL262" source="EX_EAE" target="ORG_USCIS"><data key="edge_relationship_id">REL262</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_USCIS</data><data key="edge_operational_context">USCIS electronically sends enumeration data to SSA via the EAE interface.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL263" source="EX_EAE" target="APP_SSNAP"><data key="edge_relationship_id">REL263</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">exception_work_routes_to</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">Unprocessed EAE records can remain on the enumeration pending file and are retrieved/resolved in SSNAP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL264" source="EX_EBE" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL264</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">EBE supports automated original/replacement SSN card processing for approved USCIS applications.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL265" source="EX_EBE" target="ORG_USCIS"><data key="edge_relationship_id">REL265</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_USCIS</data><data key="edge_operational_context">USCIS electronically transmits approved EBE enumeration data to SSA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL266" source="EX_EBE" target="APP_SSNAP"><data key="edge_relationship_id">REL266</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">exception_work_routes_to</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">EBE applications that cannot process automatically remain pending in SSNAP as Investigate or Not Completed.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL267" source="APP_NOVU" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL267</data><data key="edge_source_entity_id">APP_NOVU</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">NOVU is documented as a mainframe application that accesses Numident for real-time SSN verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL268" source="APP_NOVU" target="TECH_MAINFRAME"><data key="edge_relationship_id">REL268</data><data key="edge_source_entity_id">APP_NOVU</data><data key="edge_relationship_type">runs_on</data><data key="edge_target_entity_id">TECH_MAINFRAME</data><data key="edge_operational_context">NOVU is explicitly described as a mainframe application.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL269" source="APP_SVS" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL269</data><data key="edge_source_entity_id">APP_SVS</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SVS is a mainframe program that accesses Numident for SSN verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL270" source="APP_SVS" target="TECH_MAINFRAME"><data key="edge_relationship_id">REL270</data><data key="edge_source_entity_id">APP_SVS</data><data key="edge_relationship_type">runs_on</data><data key="edge_target_entity_id">TECH_MAINFRAME</data><data key="edge_operational_context">SVS is explicitly described as a mainframe program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL271" source="APP_SVS_LITE" target="APP_SVS"><data key="edge_relationship_id">REL271</data><data key="edge_source_entity_id">APP_SVS_LITE</data><data key="edge_relationship_type">uses_verification_process_of</data><data key="edge_target_entity_id">APP_SVS</data><data key="edge_operational_context">SVS Lite uses the same verification process as SVS while returning only data needed by OCSE.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL272" source="APP_SVS_LITE" target="ORG_OCSE"><data key="edge_relationship_id">REL272</data><data key="edge_source_entity_id">APP_SVS_LITE</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">SVS Lite is documented as used exclusively by OCSE for batch SSN verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL273" source="APP_SVS_LITE" target="TECH_MAINFRAME"><data key="edge_relationship_id">REL273</data><data key="edge_source_entity_id">APP_SVS_LITE</data><data key="edge_relationship_type">runs_on</data><data key="edge_target_entity_id">TECH_MAINFRAME</data><data key="edge_operational_context">SVS Lite is explicitly described as a mainframe program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL274" source="APP_EVS" target="DOM_SSNV"><data key="edge_relationship_id">REL274</data><data key="edge_source_entity_id">APP_EVS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">EVS performs batch SSN verification for external and internal requesters.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL275" source="APP_SSNVS" target="DOM_SSNV"><data key="edge_relationship_id">REL275</data><data key="edge_source_entity_id">APP_SSNVS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Current SSNVS verifies employee names and SSNs against SSA records for wage-reporting purposes.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL276" source="APP_SSNVS" target="PLAT_BSO"><data key="edge_relationship_id">REL276</data><data key="edge_source_entity_id">APP_SSNVS</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">SSNVS is a current service in Business Services Online.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL277" source="APP_SSNVS" target="APP_NOVU"><data key="edge_relationship_id">REL277</data><data key="edge_source_entity_id">APP_SSNVS</data><data key="edge_relationship_type">uses_online_backend</data><data key="edge_target_entity_id">APP_NOVU</data><data key="edge_operational_context">SSA's back-end architecture metadata states online SSNVS requests use NOVU.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Backend metadata is 2016; current SSNVS operation is independently corroborated, but the backend mapping has not been re-published recently.</data></edge><edge id="REL278" source="APP_SSNVS" target="APP_EVS"><data key="edge_relationship_id">REL278</data><data key="edge_source_entity_id">APP_SSNVS</data><data key="edge_relationship_type">uses_batch_backend</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">SSA's back-end architecture metadata states SSNVS batch requests use EVS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Backend metadata is 2016; current SSNVS and current EVS are independently corroborated.</data></edge><edge id="REL279" source="APP_VAMS" target="APP_EVS"><data key="edge_relationship_id">REL279</data><data key="edge_source_entity_id">APP_VAMS</data><data key="edge_relationship_type">checks_account_for</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">Current VAMS metadata says EVS requests are verified in VAMS before processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL280" source="APP_VAMS" target="APP_NOVU"><data key="edge_relationship_id">REL280</data><data key="edge_source_entity_id">APP_VAMS</data><data key="edge_relationship_type">checks_account_for</data><data key="edge_target_entity_id">APP_NOVU</data><data key="edge_operational_context">Current VAMS metadata says NOVU requests are verified in VAMS before processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL281" source="APP_VAMS" target="EX_SVES"><data key="edge_relationship_id">REL281</data><data key="edge_source_entity_id">APP_VAMS</data><data key="edge_relationship_type">checks_account_for</data><data key="edge_target_entity_id">EX_SVES</data><data key="edge_operational_context">Current VAMS metadata says SVES requests are verified in VAMS before processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL282" source="APP_VAMS" target="EX_SOLQ"><data key="edge_relationship_id">REL282</data><data key="edge_source_entity_id">APP_VAMS</data><data key="edge_relationship_type">checks_account_for</data><data key="edge_target_entity_id">EX_SOLQ</data><data key="edge_operational_context">Current VAMS metadata says SOLQ requests are verified in VAMS before processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL283" source="APP_DEVO" target="APP_VAMS"><data key="edge_relationship_id">REL283</data><data key="edge_source_entity_id">APP_DEVO</data><data key="edge_relationship_type">interfaces_with</data><data key="edge_target_entity_id">APP_VAMS</data><data key="edge_operational_context">DEVO uses VAMS for account status, processing parameters and transaction counts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL284" source="APP_DEVO" target="APP_EVS"><data key="edge_relationship_id">REL284</data><data key="edge_source_entity_id">APP_DEVO</data><data key="edge_relationship_type">modernization_target_for</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">SSA metadata describes EVS as being reengineered into DEVO; current EVS metadata says replacement is still future.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">This is a migration target, not a completed replacement.</data></edge><edge id="REL285" source="APP_DEVO" target="APP_NOVU"><data key="edge_relationship_id">REL285</data><data key="edge_source_entity_id">APP_DEVO</data><data key="edge_relationship_type">modernization_target_for</data><data key="edge_target_entity_id">APP_NOVU</data><data key="edge_operational_context">SSA DEVO metadata describes NOVU as a legacy verification application being reengineered into DEVO.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Not modeled as completed.</data></edge><edge id="REL286" source="APP_DEVO" target="EX_SVES"><data key="edge_relationship_id">REL286</data><data key="edge_source_entity_id">APP_DEVO</data><data key="edge_relationship_type">modernization_target_for</data><data key="edge_target_entity_id">EX_SVES</data><data key="edge_operational_context">SSA DEVO metadata describes SVES as a legacy exchange being reengineered into DEVO.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Not modeled as completed.</data></edge><edge id="REL287" source="APP_DEVO" target="EX_SOLQ"><data key="edge_relationship_id">REL287</data><data key="edge_source_entity_id">APP_DEVO</data><data key="edge_relationship_type">modernization_target_for</data><data key="edge_target_entity_id">EX_SOLQ</data><data key="edge_operational_context">SSA DEVO metadata describes SOLQ as a legacy exchange being reengineered into DEVO.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Not modeled as completed.</data></edge><edge id="REL288" source="DB_ONLINE_EVS_MI" target="DOM_SSNV"><data key="edge_relationship_id">REL288</data><data key="edge_source_entity_id">DB_ONLINE_EVS_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Current SSA inventory identifies this as MI for several SSN verification systems that verify against Numident.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL289" source="UTIL_GUNSCHIP" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL289</data><data key="edge_source_entity_id">UTIL_GUNSCHIP</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current SSA inventory says GUNSCHIP reads and retrieves selected Numident data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL290" source="UTIL_GUNPUC03" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL290</data><data key="edge_source_entity_id">UTIL_GUNPUC03</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current SSA inventory says GUNPUC03 reads and retrieves selected Numident data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL291" source="SVC_GUVERF02" target="UTIL_GUNSCHIP"><data key="edge_relationship_id">REL291</data><data key="edge_source_entity_id">SVC_GUVERF02</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UTIL_GUNSCHIP</data><data key="edge_operational_context">Legacy service metadata says GUVERF02 retrieves Numident records by calling GUNSCHIP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="REL292" source="SVC_GUVERF02" target="TECH_WEBSPHERE"><data key="edge_relationship_id">REL292</data><data key="edge_source_entity_id">SVC_GUVERF02</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_WEBSPHERE</data><data key="edge_operational_context">Legacy service metadata documents a WebSphere/CICS interface.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="REL293" source="SVC_GUVERF02" target="TECH_CICS"><data key="edge_relationship_id">REL293</data><data key="edge_source_entity_id">SVC_GUVERF02</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_CICS</data><data key="edge_operational_context">Legacy service metadata documents a WebSphere/CICS interface.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="REL294" source="SVC_GUVERF02" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL294</data><data key="edge_source_entity_id">SVC_GUVERF02</data><data key="edge_relationship_type">verifies_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Legacy service metadata says GUVERF02 compares input identity fields with corresponding Numident fields.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="REL295" source="EX_SSOLV" target="ORG_STATES"><data key="edge_relationship_id">REL295</data><data key="edge_source_entity_id">EX_SSOLV</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">POMS documents SSOLV as real-time SSN verification for state motor-vehicle administrations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL296" source="EX_SSOLV" target="ORG_AAMVA"><data key="edge_relationship_id">REL296</data><data key="edge_source_entity_id">EX_SSOLV</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">ORG_AAMVA</data><data key="edge_operational_context">AAMVAnet/AAMVA acts as the conduit between authorized state agencies and SSA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL297" source="EX_SSOLV" target="APP_NOVU"><data key="edge_relationship_id">REL297</data><data key="edge_source_entity_id">EX_SSOLV</data><data key="edge_relationship_type">uses_backend</data><data key="edge_target_entity_id">APP_NOVU</data><data key="edge_operational_context">SSA metadata identifies SSOLV as a system using NOVU for verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Backend description is legacy-dated.</data></edge><edge id="REL298" source="EX_HAVV" target="ORG_STATES"><data key="edge_relationship_id">REL298</data><data key="edge_source_entity_id">EX_HAVV</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">Current SSA HAVV documentation describes state voter-registration verification using four SSN digits.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL299" source="EX_HAVV" target="ORG_AAMVA"><data key="edge_relationship_id">REL299</data><data key="edge_source_entity_id">EX_HAVV</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">ORG_AAMVA</data><data key="edge_operational_context">SSA exchange metadata identifies AAMVA connectivity between SSA and state MVAs for HAVV.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL300" source="EX_HAVV" target="DOM_SSNV"><data key="edge_relationship_id">REL300</data><data key="edge_source_entity_id">EX_HAVV</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">HAVV verifies submitted SSN digits, name and date of birth.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL301" source="EX_HAVV" target="DOM_DEATH"><data key="edge_relationship_id">REL301</data><data key="edge_source_entity_id">EX_HAVV</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_DEATH</data><data key="edge_operational_context">HAVV response categories include alive/deceased status from SSA records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL302" source="DB_HAVV_ODS" target="EX_HAVV"><data key="edge_relationship_id">REL302</data><data key="edge_source_entity_id">DB_HAVV_ODS</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">EX_HAVV</data><data key="edge_operational_context">HAVV ODS records management information about voter-identification transactions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL303" source="EX_ISVER" target="ORG_DOS"><data key="edge_relationship_id">REL303</data><data key="edge_source_entity_id">EX_ISVER</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_DOS</data><data key="edge_operational_context">ISVER metadata describes a real-time reimbursable SSN verification service for passport applicants.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="REL304" source="EX_ISVER" target="DOM_SSNV"><data key="edge_relationship_id">REL304</data><data key="edge_source_entity_id">EX_ISVER</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">ISVER verifies SSNs and other identifying information for Department of State passport adjudication.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="REL305" source="EX_EVERIFY" target="ORG_DHS"><data key="edge_relationship_id">REL305</data><data key="edge_source_entity_id">EX_EVERIFY</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_DHS</data><data key="edge_operational_context">SSA E-Verify participates in the DHS/USCIS automated employment-eligibility confirmation process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="REL306" source="EX_EVERIFY" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL306</data><data key="edge_source_entity_id">EX_EVERIFY</data><data key="edge_relationship_type">verifies_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA E-Verify metadata says the SSA system derives a verification code from SSN/DOB/name data in Numident.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes" /></edge><edge id="REL307" source="APP_ECBSV" target="SVC_ECBSV_API"><data key="edge_relationship_id">REL307</data><data key="edge_source_entity_id">APP_ECBSV</data><data key="edge_relationship_type">exposes_interface</data><data key="edge_target_entity_id">SVC_ECBSV_API</data><data key="edge_operational_context">Current SSA technical documentation describes an SSA Verification API for eCBSV permitted entities.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL308" source="SVC_ECBSV_API" target="TECH_OIDC"><data key="edge_relationship_id">REL308</data><data key="edge_source_entity_id">SVC_ECBSV_API</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_OIDC</data><data key="edge_operational_context">Current eCBSV technical documentation identifies this technology as part of direct API access requirements.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL309" source="SVC_ECBSV_API" target="TECH_OAUTH2"><data key="edge_relationship_id">REL309</data><data key="edge_source_entity_id">SVC_ECBSV_API</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_OAUTH2</data><data key="edge_operational_context">Current eCBSV technical documentation identifies this technology as part of direct API access requirements.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL310" source="SVC_ECBSV_API" target="TECH_JWT"><data key="edge_relationship_id">REL310</data><data key="edge_source_entity_id">SVC_ECBSV_API</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_JWT</data><data key="edge_operational_context">Current eCBSV technical documentation identifies this technology as part of direct API access requirements.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL311" source="SVC_ECBSV_API" target="TECH_REST_JSON"><data key="edge_relationship_id">REL311</data><data key="edge_source_entity_id">SVC_ECBSV_API</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_REST_JSON</data><data key="edge_operational_context">Current eCBSV technical documentation identifies this technology as part of direct API access requirements.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL312" source="SVC_ECBSV_API" target="TECH_JWE"><data key="edge_relationship_id">REL312</data><data key="edge_source_entity_id">SVC_ECBSV_API</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_JWE</data><data key="edge_operational_context">Current eCBSV technical documentation identifies this technology as part of direct API access requirements.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL313" source="APP_DIPS" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL313</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current POMS requires DIPS to add, change or remove death information on Numident.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL314" source="APP_DIPS" target="DOM_TITLE2"><data key="edge_relationship_id">REL314</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">posts_death_to</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">DIPS delete removes death from the Title II payment system and DIPS entries generally post to payment records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL315" source="APP_DIPS" target="DOM_TITLE16"><data key="edge_relationship_id">REL315</data><data key="edge_source_entity_id">APP_DIPS</data><data key="edge_relationship_type">conditionally_posts_death_to</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">DIPS generally posts to payment records, but current POMS explicitly says a DIPS death deletion does not automatically remove death from the Title XVI record.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">The relationship is deliberately conditional because Title XVI delete/reinstatement requires corrective action.</data></edge><edge id="REL316" source="APP_DATS" target="APP_DIPS"><data key="edge_relationship_id">REL316</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">receives_alerts_from</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">Current DATS instructions identify DIPS-generated death-alert types.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL317" source="APP_DATS" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL317</data><data key="edge_source_entity_id">APP_DATS</data><data key="edge_relationship_type">reconciles_with</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current DATS alerts include cases where death is on Numident but not payment record(s).</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL318" source="DATA_DMF" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL318</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA says its death-information files are compiled from the Enumeration System/SSN-holder master records; OIG confirms Numident is the official death source.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL319" source="DATA_DMF" target="ORG_NTIS"><data key="edge_relationship_id">REL319</data><data key="edge_source_entity_id">DATA_DMF</data><data key="edge_relationship_type">distributed_by</data><data key="edge_target_entity_id">ORG_NTIS</data><data key="edge_operational_context">SSA provides NTIS a public death file excluding state death records; NTIS distributes the public/Limited Access DMF.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL320" source="DB_MULTI_SSN_XREF" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL320</data><data key="edge_source_entity_id">DB_MULTI_SSN_XREF</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">Cataloged data asset contains cross-reference SSN data used to associate multiple numbers.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes">Dataset description is legacy-dated; no assumption is made about its current physical implementation.</data></edge><edge id="REL321" source="APP_ERMS" target="SYS_MEF"><data key="edge_relationship_id">REL321</data><data key="edge_source_entity_id">APP_ERMS</data><data key="edge_relationship_type">processes_earnings_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">ERMS receives employer and self-employment earnings and processes the data to MEF.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">ERMS component architecture comes from a 2007 PIA still relevant as governance/architecture evidence.</data></edge><edge id="REL322" source="APP_EWR" target="PROC_AWR"><data key="edge_relationship_id">REL322</data><data key="edge_source_entity_id">APP_EWR</data><data key="edge_relationship_type">submits_to</data><data key="edge_target_entity_id">PROC_AWR</data><data key="edge_operational_context">EWR wage report submissions are transmitted to AWR for processing individual tax forms.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">EWR PIA is older; current employer services independently confirm the electronic submission channels.</data></edge><edge id="REL323" source="PROC_AWR" target="SYS_MEF"><data key="edge_relationship_id">REL323</data><data key="edge_source_entity_id">PROC_AWR</data><data key="edge_relationship_type">posts_valid_earnings_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">AWR maintains worker earnings; MEF is the current database storing wage and self-employment income.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL324" source="PROC_AWR" target="DB_ESF"><data key="edge_relationship_id">REL324</data><data key="edge_source_entity_id">PROC_AWR</data><data key="edge_relationship_type">routes_unmatched_earnings_to</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">Earnings whose name/SSN cannot be matched are held in the Earnings Suspense File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL325" source="DB_ESF" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL325</data><data key="edge_source_entity_id">DB_ESF</data><data key="edge_relationship_type">contains_items_failing_match_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">ESF holds earnings for which name/SSN validation does not permit posting to an individual earnings record.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL326" source="DB_ERHF" target="PROC_AWR"><data key="edge_relationship_id">REL326</data><data key="edge_source_entity_id">DB_ERHF</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_AWR</data><data key="edge_operational_context">ERHF stores employer-side report-level wage data by EIN and tax year for AWR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL327" source="DB_EMPLOYERS_SUBMITTERS" target="PROC_AWR"><data key="edge_relationship_id">REL327</data><data key="edge_source_entity_id">DB_EMPLOYERS_SUBMITTERS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_AWR</data><data key="edge_operational_context">Current inventory says this database supports processing wage files for AWR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL328" source="DB_EMODS" target="PROC_AWR"><data key="edge_relationship_id">REL328</data><data key="edge_source_entity_id">DB_EMODS</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">PROC_AWR</data><data key="edge_operational_context">Current ODS houses AWR management information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL329" source="DB_EARNINGS_DW" target="PROC_AWR"><data key="edge_relationship_id">REL329</data><data key="edge_source_entity_id">DB_EARNINGS_DW</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">PROC_AWR</data><data key="edge_operational_context">Current Earnings Data Warehouse contains AWR management information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL330" source="DB_OWR" target="APP_EWR"><data key="edge_relationship_id">REL330</data><data key="edge_source_entity_id">DB_OWR</data><data key="edge_relationship_type">supports_online_submissions_for</data><data key="edge_target_entity_id">APP_EWR</data><data key="edge_operational_context">Current OWR database supports W-2/W-2c submissions through SSA internet services.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL331" source="DB_OWR_MI" target="DB_OWR"><data key="edge_relationship_id">REL331</data><data key="edge_source_entity_id">DB_OWR_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">DB_OWR</data><data key="edge_operational_context">Current inventory describes MI for internet W-2/W-2c submissions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL332" source="DB_EIF" target="ORG_IRS"><data key="edge_relationship_id">REL332</data><data key="edge_source_entity_id">DB_EIF</data><data key="edge_relationship_type">receives_employer_identifiers_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Current inventory states EIN information in EIF is provided by IRS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL333" source="APP_ICOR" target="SYS_MEF"><data key="edge_relationship_id">REL333</data><data key="edge_source_entity_id">APP_ICOR</data><data key="edge_relationship_type">corrects</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">ICOR enables correction of an individual number holder MEF record.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL334" source="APP_ICOR" target="DB_ESF"><data key="edge_relationship_id">REL334</data><data key="edge_source_entity_id">APP_ICOR</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">Current 2025 POMS tells staff to check ICOR and the Earnings Suspense File during earnings discrepancy development.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL335" source="APP_RCOR" target="SYS_MEF"><data key="edge_relationship_id">REL335</data><data key="edge_source_entity_id">APP_RCOR</data><data key="edge_relationship_type">adjusts</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">RCOR processes employer adjustments to MEF for tax years 1978 and later.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL336" source="APP_RCOR" target="DB_ESF"><data key="edge_relationship_id">REL336</data><data key="edge_source_entity_id">APP_RCOR</data><data key="edge_relationship_type">adjusts</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">RCOR processes employer adjustments to the Suspense File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL337" source="APP_ECMS" target="PROC_REAP"><data key="edge_relationship_id">REL337</data><data key="edge_source_entity_id">APP_ECMS</data><data key="edge_relationship_type">hosts_process</data><data key="edge_target_entity_id">PROC_REAP</data><data key="edge_operational_context">Electronic REAP Form SSA-4130 is used within ECMS when ICOR/RCOR cannot perform an adjustment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL338" source="PROC_REAP" target="SYS_MEF"><data key="edge_relationship_id">REL338</data><data key="edge_source_entity_id">PROC_REAP</data><data key="edge_relationship_type">posts_adjustments_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">REAP adjustments can post to MEF.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL339" source="PROC_REAP" target="DB_ESF"><data key="edge_relationship_id">REL339</data><data key="edge_source_entity_id">PROC_REAP</data><data key="edge_relationship_type">posts_adjustments_to</data><data key="edge_target_entity_id">DB_ESF</data><data key="edge_operational_context">REAP adjustments can post to ESF.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL340" source="DB_EMPLOYER_CTRL" target="SVC_ERQY"><data key="edge_relationship_id">REL340</data><data key="edge_source_entity_id">DB_EMPLOYER_CTRL</data><data key="edge_relationship_type">exposed_through</data><data key="edge_target_entity_id">SVC_ERQY</data><data key="edge_operational_context">Employer Control Data Base/Employer Report Query provide employer wage-report filing/problem information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL341" source="SVC_ERQY" target="APP_ICOR"><data key="edge_relationship_id">REL341</data><data key="edge_source_entity_id">SVC_ERQY</data><data key="edge_relationship_type">used_for_earnings_development_with</data><data key="edge_target_entity_id">APP_ICOR</data><data key="edge_operational_context">Current 2025 discrepancy development instructs staff to inspect ERQY and ICOR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL342" source="APP_MICES" target="DOM_EARNINGS"><data key="edge_relationship_id">REL342</data><data key="edge_source_entity_id">APP_MICES</data><data key="edge_relationship_type">controls_work_for</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">MICES controls earnings correspondence; current inventory also identifies earnings inquiry and quality-review MI functions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL343" source="APP_ACCUWAGE" target="PLAT_BSO"><data key="edge_relationship_id">REL343</data><data key="edge_source_entity_id">APP_ACCUWAGE</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">AccuWage Online is part of BSO.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL344" source="APP_ACCUWAGE" target="FMT_EFW2"><data key="edge_relationship_id">REL344</data><data key="edge_source_entity_id">APP_ACCUWAGE</data><data key="edge_relationship_type">validates</data><data key="edge_target_entity_id">FMT_EFW2</data><data key="edge_operational_context">AccuWage tests EFW2 files before SSA submission.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL345" source="APP_ACCUWAGE" target="FMT_EFW2C"><data key="edge_relationship_id">REL345</data><data key="edge_source_entity_id">APP_ACCUWAGE</data><data key="edge_relationship_type">validates</data><data key="edge_target_entity_id">FMT_EFW2C</data><data key="edge_operational_context">AccuWage tests EFW2C files before SSA submission.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL346" source="APP_W2_ONLINE_2026" target="PLAT_BSO"><data key="edge_relationship_id">REL346</data><data key="edge_source_entity_id">APP_W2_ONLINE_2026</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">Current W-2/W-2C Online is part of SSA employer services accessed through BSO.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL347" source="APP_W2_ONLINE_PREV" target="APP_W2_ONLINE_2026"><data key="edge_relationship_id">REL347</data><data key="edge_source_entity_id">APP_W2_ONLINE_PREV</data><data key="edge_relationship_type">replaced_by</data><data key="edge_target_entity_id">APP_W2_ONLINE_2026</data><data key="edge_operational_context">SSA decommissioned the prior W-2/W-2c Online application September 19, 2026 after releasing the modernized application.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL348" source="SVC_WAGE_FILE_UPLOAD" target="PLAT_BSO"><data key="edge_relationship_id">REL348</data><data key="edge_source_entity_id">SVC_WAGE_FILE_UPLOAD</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">PLAT_BSO</data><data key="edge_operational_context">Wage File Upload is a current BSO electronic filing option.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL349" source="SVC_WAGE_FILE_UPLOAD" target="FMT_EFW2"><data key="edge_relationship_id">REL349</data><data key="edge_source_entity_id">SVC_WAGE_FILE_UPLOAD</data><data key="edge_relationship_type">accepts</data><data key="edge_target_entity_id">FMT_EFW2</data><data key="edge_operational_context">Current electronic wage submission uses SSA EFW2 formatted files.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL350" source="SVC_WAGE_FILE_UPLOAD" target="FMT_EFW2C"><data key="edge_relationship_id">REL350</data><data key="edge_source_entity_id">SVC_WAGE_FILE_UPLOAD</data><data key="edge_relationship_type">accepts</data><data key="edge_target_entity_id">FMT_EFW2C</data><data key="edge_operational_context">Current electronic correction submission uses SSA EFW2C formatted files.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL351" source="SVC_EWRWS" target="PROC_AWR"><data key="edge_relationship_id">REL351</data><data key="edge_source_entity_id">SVC_EWRWS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_AWR</data><data key="edge_operational_context">Current POMS describes EWRWS as a channel for electronically submitting formatted wage reports; current employer materials limit new onboarding.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL352" source="APP_EWR" target="SVC_WAGE_FILE_UPLOAD"><data key="edge_relationship_id">REL352</data><data key="edge_source_entity_id">APP_EWR</data><data key="edge_relationship_type">includes_service</data><data key="edge_target_entity_id">SVC_WAGE_FILE_UPLOAD</data><data key="edge_operational_context">EWR suite architecture includes Wage File Upload.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL353" source="APP_EWR" target="SVC_EWRWS"><data key="edge_relationship_id">REL353</data><data key="edge_source_entity_id">APP_EWR</data><data key="edge_relationship_type">includes_interface</data><data key="edge_target_entity_id">SVC_EWRWS</data><data key="edge_operational_context">EWR suite architecture includes the wage-reporting web service.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL354" source="PLAT_BSO" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">REL354</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">authenticates_via</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">SSA states BSO employer services now require Login.gov or ID.me rather than legacy BSO credentials.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL355" source="PLAT_BSO" target="SVC_IDME"><data key="edge_relationship_id">REL355</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">authenticates_via</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">SSA states BSO employer services now require Login.gov or ID.me rather than legacy BSO credentials.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL356" source="ORG_WBDOC" target="PROC_AWR"><data key="edge_relationship_id">REL356</data><data key="edge_source_entity_id">ORG_WBDOC</data><data key="edge_relationship_type">receives_paper_reports_for</data><data key="edge_target_entity_id">PROC_AWR</data><data key="edge_operational_context">EWR PIA and wage-reporting glossary document Wilkes-Barre as the paper wage-report intake/scan operation.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes">Current routing should be revalidated before treating WBDOC as the sole paper intake path.</data></edge><edge id="REL357" source="EX_CAWR" target="ORG_IRS"><data key="edge_relationship_id">REL357</data><data key="edge_source_entity_id">EX_CAWR</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">CAWR MOU governs SSA/IRS exchange and responsibilities for wage/tax reporting and reconciliation.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL358" source="EX_CAWR" target="DOM_EARNINGS"><data key="edge_relationship_id">REL358</data><data key="edge_source_entity_id">EX_CAWR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">CAWR shares and reconciles employer wage/tax information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL359" source="EX_CAWR" target="DB_RECON"><data key="edge_relationship_id">REL359</data><data key="edge_source_entity_id">EX_CAWR</data><data key="edge_relationship_type">reconciles_through</data><data key="edge_target_entity_id">DB_RECON</data><data key="edge_operational_context">Current RECON repository is associated with reconciling SSA-reported wages and IRS-reported taxes.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL360" source="DB_RECON" target="PROC_AWR"><data key="edge_relationship_id">REL360</data><data key="edge_source_entity_id">DB_RECON</data><data key="edge_relationship_type">compares_data_from</data><data key="edge_target_entity_id">PROC_AWR</data><data key="edge_operational_context">RECON compares SSA processed employer wage totals against tax reporting.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL361" source="DB_RECON_CTRL" target="EX_CAWR"><data key="edge_relationship_id">REL361</data><data key="edge_source_entity_id">DB_RECON_CTRL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">EX_CAWR</data><data key="edge_operational_context">Legacy catalog record documents reconciliation control-locator data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes">Legacy metadata only.</data></edge><edge id="REL362" source="DB_RECON_DEV" target="EX_CAWR"><data key="edge_relationship_id">REL362</data><data key="edge_source_entity_id">DB_RECON_DEV</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">EX_CAWR</data><data key="edge_operational_context">Legacy catalog record documents reconciliation development worksheet data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">3</data><data key="edge_notes">Legacy metadata only.</data></edge><edge id="REL363" source="DB_EMPLOYER_SHARED" target="APP_EWORK"><data key="edge_relationship_id">REL363</data><data key="edge_source_entity_id">DB_EMPLOYER_SHARED</data><data key="edge_relationship_type">shared_by</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">Current inventory explicitly says Employer Database tables are shared with eWork.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL364" source="DB_EMPLOYER_SHARED" target="APP_SSIMWV"><data key="edge_relationship_id">REL364</data><data key="edge_source_entity_id">DB_EMPLOYER_SHARED</data><data key="edge_relationship_type">shared_by</data><data key="edge_target_entity_id">APP_SSIMWV</data><data key="edge_operational_context">Current inventory explicitly says Employer Database tables are shared with SSI Monthly Wage Verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL365" source="EX_OPM_EARNINGS" target="ORG_OPM"><data key="edge_relationship_id">REL365</data><data key="edge_source_entity_id">EX_OPM_EARNINGS</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_OPM</data><data key="edge_operational_context">OPM sends SSA a file annually for earnings verification/matching.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL366" source="EX_OPM_EARNINGS" target="SYS_MEF"><data key="edge_relationship_id">REL366</data><data key="edge_source_entity_id">EX_OPM_EARNINGS</data><data key="edge_relationship_type">matches</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Current inventory explicitly says OPM file is matched against MEF.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL367" source="EX_OPM_EARNINGS" target="DB_EIF"><data key="edge_relationship_id">REL367</data><data key="edge_source_entity_id">EX_OPM_EARNINGS</data><data key="edge_relationship_type">matches</data><data key="edge_target_entity_id">DB_EIF</data><data key="edge_operational_context">Current inventory says OPM file is matched against an Employer Information File (EIF); linked to current SSA Employer Identification File with nomenclature caveat.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">SSA uses Employer Information File wording in the exchange metadata while the separate inventory asset is Employer Identification File; exact physical identity needs validation.</data></edge><edge id="REL368" source="EX_OPM_EARNINGS" target="ORG_OPM"><data key="edge_relationship_id">REL368</data><data key="edge_source_entity_id">EX_OPM_EARNINGS</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_OPM</data><data key="edge_operational_context">SSA data returned from the annual match are used by OPM for continued eligibility decisions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL369" source="EX_PIE" target="DB_WEI_REPO"><data key="edge_relationship_id">REL369</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">stores_in</data><data key="edge_target_entity_id">DB_WEI_REPO</data><data key="edge_operational_context">SSA says monthly PIE information is kept in the Wage and Employment Information Repository.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL370" source="DB_WEI_REPO" target="APP_EWORK"><data key="edge_relationship_id">REL370</data><data key="edge_source_entity_id">DB_WEI_REPO</data><data key="edge_relationship_type">provides_to</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">Current disability POMS says PDP wage information in WEI Repository propagates into eWork.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL371" source="DB_WEI_REPO" target="APP_MSSICS"><data key="edge_relationship_id">REL371</data><data key="edge_source_entity_id">DB_WEI_REPO</data><data key="edge_relationship_type">provides_to</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current SSI POMS documents PIE wage information updating SSI Claims System records and SSR under system conditions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL372" source="ORG_EQUIFAX_WS" target="EX_PIE"><data key="edge_relationship_id">REL372</data><data key="edge_source_entity_id">ORG_EQUIFAX_WS</data><data key="edge_relationship_type">serves_as_payroll_data_provider_for</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">SSA states Equifax is currently the PDP for PIE.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL373" source="CON_PIE_IDIQ_2024" target="ORG_EQUIFAX_WS"><data key="edge_relationship_id">REL373</data><data key="edge_source_entity_id">CON_PIE_IDIQ_2024</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_EQUIFAX_WS</data><data key="edge_operational_context">FPDS-derived public records identify Equifax Workforce Solutions as awardee for PIE contract 28321324D00060023.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Procurement value/award metadata should be reconciled to first-party FPDS/USAspending before financial publication.</data></edge><edge id="REL374" source="CON_PIE_IDIQ_2024" target="EX_PIE"><data key="edge_relationship_id">REL374</data><data key="edge_source_entity_id">CON_PIE_IDIQ_2024</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">The contract is identified as Electronic Payroll Information Exchange (PIE).</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL375" source="CON_PIE_TASK_2026" target="CON_PIE_IDIQ_2024"><data key="edge_relationship_id">REL375</data><data key="edge_source_entity_id">CON_PIE_TASK_2026</data><data key="edge_relationship_type">task_order_under</data><data key="edge_target_entity_id">CON_PIE_IDIQ_2024</data><data key="edge_operational_context">Public FPDS-derived record identifies 28321326FDS030081 as a delivery order under the PIE IDIQ.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL376" source="CON_PIE_TASK_2026" target="ORG_EQUIFAX_WS"><data key="edge_relationship_id">REL376</data><data key="edge_source_entity_id">CON_PIE_TASK_2026</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_EQUIFAX_WS</data><data key="edge_operational_context">Public award record identifies Equifax as task-order recipient.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL377" source="CON_PIE_TASK_2026" target="EX_PIE"><data key="edge_relationship_id">REL377</data><data key="edge_source_entity_id">CON_PIE_TASK_2026</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">Task order description is matched hits for PIE for June 2026-May 2027.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL378" source="PLAT_EDIB" target="APP_EDCS"><data key="edge_relationship_id">REL378</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">APP_EDCS is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL379" source="PLAT_EDIB" target="APP_EVIEW"><data key="edge_relationship_id">REL379</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">APP_EVIEW is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL380" source="PLAT_EDIB" target="APP_UNIFORMS"><data key="edge_relationship_id">REL380</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_UNIFORMS</data><data key="edge_operational_context">APP_UNIFORMS is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL381" source="PLAT_EDIB" target="APP_ECAT"><data key="edge_relationship_id">REL381</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_ECAT</data><data key="edge_operational_context">APP_ECAT is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL382" source="PLAT_EDIB" target="APP_ERE"><data key="edge_relationship_id">REL382</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">APP_ERE is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL383" source="PLAT_EDIB" target="APP_MEGAHIT"><data key="edge_relationship_id">REL383</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_MEGAHIT</data><data key="edge_operational_context">APP_MEGAHIT is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL384" source="PLAT_EDIB" target="APP_EFI"><data key="edge_relationship_id">REL384</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_EFI</data><data key="edge_operational_context">APP_EFI is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL385" source="PLAT_EDIB" target="APP_EAUTH827"><data key="edge_relationship_id">REL385</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">APP_EAUTH827</data><data key="edge_operational_context">APP_EAUTH827 is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL386" source="PLAT_EDIB" target="DB_NVF"><data key="edge_relationship_id">REL386</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DB_NVF</data><data key="edge_operational_context">DB_NVF is documented inside the eDIB electronic-disability architecture boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">For legacy PIA components, this expresses documented architecture; current status is separately corroborated where available.</data></edge><edge id="REL387" source="PLAT_EDIB" target="REPO_EF"><data key="edge_relationship_id">REL387</data><data key="edge_source_entity_id">PLAT_EDIB</data><data key="edge_relationship_type">governs_electronic_folder</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">eDIB provides the electronic-disability framework in which evidence and adjudicative records are maintained in the electronic folder.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL388" source="REPO_CEF" target="REPO_MDF"><data key="edge_relationship_id">REL388</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">electronic_alternative_to</data><data key="edge_target_entity_id">REPO_MDF</data><data key="edge_operational_context">CEF is the official electronic folder; when EDCS exclusions/limitations prevent full electronic processing, the MDF becomes the official paper folder.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL389" source="APP_EDCS" target="REPO_MDF"><data key="edge_relationship_id">REL389</data><data key="edge_source_entity_id">APP_EDCS</data><data key="edge_relationship_type">exclusion_routes_to</data><data key="edge_target_entity_id">REPO_MDF</data><data key="edge_operational_context">Current POMS requires a paper MDF when an EDCS exclusion or processing limitation is present.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL390" source="APP_ERE" target="REPO_EF"><data key="edge_relationship_id">REL390</data><data key="edge_source_entity_id">APP_ERE</data><data key="edge_relationship_type">submits_documents_to</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Current ERE permits secure submission of medical, vocational and other evidence to the claimant's electronic folder.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL391" source="APP_ERE" target="DOM_CLAIMFOLDER"><data key="edge_relationship_id">REL391</data><data key="edge_source_entity_id">APP_ERE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_CLAIMFOLDER</data><data key="edge_operational_context">ERE is an electronic evidence-ingestion channel into disability claim folders.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL392" source="DB_ERE_MI_VOLUME" target="APP_ERE"><data key="edge_relationship_id">REL392</data><data key="edge_source_entity_id">DB_ERE_MI_VOLUME</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">Current ERE MI stores volume information for electronic records processed through the ERE website.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL393" source="DB_ERE_MI_VOLUME" target="APP_FECS"><data key="edge_relationship_id">REL393</data><data key="edge_source_entity_id">DB_ERE_MI_VOLUME</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">APP_FECS</data><data key="edge_operational_context">Current ERE MI reports records processed at each Front End Capture System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL394" source="DB_ERE_OUTBOUND" target="APP_ERE"><data key="edge_relationship_id">REL394</data><data key="edge_source_entity_id">DB_ERE_OUTBOUND</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">Current SSA inventory ties this non-public asset to ERE evidence collected and prepared for eDIB.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL395" source="SVC_ERE_EOR" target="APP_ERE"><data key="edge_relationship_id">REL395</data><data key="edge_source_entity_id">SVC_ERE_EOR</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">Electronic Outbound Request is an ERE feature.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL396" source="SVC_ERE_EOR" target="ORG_HIT_PARTNERS"><data key="edge_relationship_id">REL396</data><data key="edge_source_entity_id">SVC_ERE_EOR</data><data key="edge_relationship_type">sends_evidence_requests_to</data><data key="edge_target_entity_id">ORG_HIT_PARTNERS</data><data key="edge_operational_context">ERE eOR can deliver consultative-examination and evidence request packages directly to providers.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">ORG_HIT_PARTNERS is a partner-class node; eOR also reaches providers that may not be HIT-integrated.</data></edge><edge id="REL397" source="SVC_ERE_EOR" target="REPO_EF"><data key="edge_relationship_id">REL397</data><data key="edge_source_entity_id">SVC_ERE_EOR</data><data key="edge_relationship_type">receives_provider_responses_for</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">Providers can attach responses to electronic requests without manually entering barcode index information for routing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL398" source="APP_ERE" target="ORG_DDS"><data key="edge_relationship_id">REL398</data><data key="edge_source_entity_id">APP_ERE</data><data key="edge_relationship_type">receives_ce_reports_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Current CE instructions say DDS may receive consultative-examination reports through ERE.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL399" source="APP_MEGAHIT" target="APP_EDCS"><data key="edge_relationship_id">REL399</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">receives_case_trigger_from</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">POMS says MEGAHIT sends an automated HIT request when the field office transfers an electronic case to DDS and participating sources are present.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL400" source="APP_MEGAHIT" target="ORG_HIT_PARTNERS"><data key="edge_relationship_id">REL400</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">requests_medical_evidence_from</data><data key="edge_target_entity_id">ORG_HIT_PARTNERS</data><data key="edge_operational_context">MEGAHIT automates electronic evidence requests to HIT partners/HIEs.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL401" source="APP_MEGAHIT" target="REPO_EF"><data key="edge_relationship_id">REL401</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">stores_received_evidence_in</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">POMS says MEGAHIT formats returned HIT data into evidence documents stored in the electronic folder.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL402" source="APP_MEGAHIT" target="DOM_CLAIMFOLDER"><data key="edge_relationship_id">REL402</data><data key="edge_source_entity_id">APP_MEGAHIT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_CLAIMFOLDER</data><data key="edge_operational_context">Current Open Data inventory identifies HIT Medical Evidence Gathering and Analysis as a disability-claim evidence asset.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL403" source="ORG_HIT_PARTNERS" target="ORG_EHEALTH_EXCHANGE"><data key="edge_relationship_id">REL403</data><data key="edge_source_entity_id">ORG_HIT_PARTNERS</data><data key="edge_relationship_type">includes_network</data><data key="edge_target_entity_id">ORG_EHEALTH_EXCHANGE</data><data key="edge_operational_context">SSA identifies eHealth Exchange as a longstanding national HIT interoperability partner.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL404" source="ORG_EHEALTH_EXCHANGE" target="NETWORK_CAREQUALITY"><data key="edge_relationship_id">REL404</data><data key="edge_source_entity_id">ORG_EHEALTH_EXCHANGE</data><data key="edge_relationship_type">connects_to</data><data key="edge_target_entity_id">NETWORK_CAREQUALITY</data><data key="edge_operational_context">SSA says its eHealth Exchange relationship connects it to healthcare organizations on eHealth Exchange and Carequality networks.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL405" source="ORG_EHEALTH_EXCHANGE" target="NETWORK_TEFCA"><data key="edge_relationship_id">REL405</data><data key="edge_source_entity_id">ORG_EHEALTH_EXCHANGE</data><data key="edge_relationship_type">selected_qhin_for</data><data key="edge_target_entity_id">NETWORK_TEFCA</data><data key="edge_operational_context">SSA selected eHealth Exchange as its QHIN for TEFCA Government Benefits Determination exchange.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL406" source="NETWORK_TEFCA" target="APP_MEGAHIT"><data key="edge_relationship_id">REL406</data><data key="edge_source_entity_id">NETWORK_TEFCA</data><data key="edge_relationship_type">planned_to_expand</data><data key="edge_target_entity_id">APP_MEGAHIT</data><data key="edge_operational_context">SSA announced TEFCA/QHIN connectivity to expand targeted electronic health-information access for disability decisions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">No later first-party source confirming production go-live was found in this run; relationship is recorded as planned/connection-testing rather than completed.</data></edge><edge id="REL407" source="DB_NVF" target="APP_DCPS"><data key="edge_relationship_id">REL407</data><data key="edge_source_entity_id">DB_NVF</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Current SSA inventory says the National Vendor File supports DCPS and other SSA disability activities.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL408" source="APP_NVF_MGMT" target="DB_NVF"><data key="edge_relationship_id">REL408</data><data key="edge_source_entity_id">APP_NVF_MGMT</data><data key="edge_relationship_type">manages</data><data key="edge_target_entity_id">DB_NVF</data><data key="edge_operational_context">The eDIB PIA describes an intranet NVF management application consolidating vendor repositories and provider search.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL409" source="APP_NVF_FEEDS" target="DB_NVF"><data key="edge_relationship_id">REL409</data><data key="edge_source_entity_id">APP_NVF_FEEDS</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DB_NVF</data><data key="edge_operational_context">The eDIB PIA says legacy DDS vendor data flow through EFI to NVF and are staged in the NVF database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Legacy-feed relevance may have changed after nationwide DCPS implementation.</data></edge><edge id="REL410" source="APP_NVF_FEEDS" target="APP_EFI"><data key="edge_relationship_id">REL410</data><data key="edge_source_entity_id">APP_NVF_FEEDS</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">APP_EFI</data><data key="edge_operational_context">The eDIB PIA documents NVF legacy data feeds passing through EFI.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL411" source="APP_NVF_FEEDS" target="TECH_ABINITIO"><data key="edge_relationship_id">REL411</data><data key="edge_source_entity_id">APP_NVF_FEEDS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_ABINITIO</data><data key="edge_operational_context">The eDIB PIA says staged NVF data migrate to operational tables using Ab Initio software.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL412" source="DB_DIODS" target="APP_NDDSS"><data key="edge_relationship_id">REL412</data><data key="edge_source_entity_id">DB_DIODS</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">APP_NDDSS</data><data key="edge_operational_context">Current inventory says DIODS stores detailed case information from NDDSS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL413" source="DB_DIODS" target="ORG_DDS"><data key="edge_relationship_id">REL413</data><data key="edge_source_entity_id">DB_DIODS</data><data key="edge_relationship_type">provides_management_information_to</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">DIODS creates subtotals and summaries used for DDS management reports.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL414" source="DB_DCPS_MI" target="APP_DCPS"><data key="edge_relationship_id">REL414</data><data key="edge_source_entity_id">DB_DCPS_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Current SSA inventory describes DCPS MI as supporting management information for DCPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL415" source="DW_DCPS" target="APP_DCPS"><data key="edge_relationship_id">REL415</data><data key="edge_source_entity_id">DW_DCPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Current Open Data inventory explicitly says this release supports the DCPS Data Warehouse.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL416" source="DB_DCPS_CORRESP" target="APP_DCPS"><data key="edge_relationship_id">REL416</data><data key="edge_source_entity_id">DB_DCPS_CORRESP</data><data key="edge_relationship_type">supports_correspondence_for</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Current SSA inventory says the asset supports correspondence information for DCPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL417" source="DB_DCPS_CORRESP" target="TECH_THUNDERHEAD"><data key="edge_relationship_id">REL417</data><data key="edge_source_entity_id">DB_DCPS_CORRESP</data><data key="edge_relationship_type">uses_or_is_tagged_with</data><data key="edge_target_entity_id">TECH_THUNDERHEAD</data><data key="edge_operational_context">Current DCPS Correspondence metadata includes Thunderhead and COTS as keywords.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">The metadata supports a technology association but does not establish product version or every correspondence component.</data></edge><edge id="REL418" source="APP_DCPS" target="STRUCT_DDE"><data key="edge_relationship_id">REL418</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">writes_case_notes_to</data><data key="edge_target_entity_id">STRUCT_DDE</data><data key="edge_operational_context">Current POMS says DCPS Case Notes can write to the Disability Determination Explanation.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL419" source="APP_DCPS" target="STRUCT_CDW"><data key="edge_relationship_id">REL419</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">writes_case_notes_to</data><data key="edge_target_entity_id">STRUCT_CDW</data><data key="edge_operational_context">Current consultative-examination instructions say a DCPS Case Note can write to the case development worksheet.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL420" source="STRUCT_DDE" target="APP_DCPS"><data key="edge_relationship_id">REL420</data><data key="edge_source_entity_id">STRUCT_DDE</data><data key="edge_relationship_type">documents_rationale_for</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Current POMS uses the DDE to document electronic disability determination/CDR rationale and DCPS assessments.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL421" source="APP_ECAT" target="APP_DCPS"><data key="edge_relationship_id">REL421</data><data key="edge_source_entity_id">APP_ECAT</data><data key="edge_relationship_type">coexists_with</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">Current 2026 POMS still identifies workflows that can be processed in eCAT or DCPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Coexistence is workload-specific; separate guidance removes eCAT from some workflows.</data></edge><edge id="REL422" source="APP_ECAT" target="APP_DCPS"><data key="edge_relationship_id">REL422</data><data key="edge_source_entity_id">APP_ECAT</data><data key="edge_relationship_type">being_replaced_by_for_some_workflows</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">SSA revised medical-evaluation instructions to complete SSA-416/MA-416 in DCPS and removed eCAT/legacy references for that workflow.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">This is not a claim that eCAT has been fully retired.</data></edge><edge id="REL423" source="DB_ECAT_MI" target="APP_ECAT"><data key="edge_relationship_id">REL423</data><data key="edge_source_entity_id">DB_ECAT_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">APP_ECAT</data><data key="edge_operational_context">The eDIB PIA documents eCAT MI charts/reports for monitoring eCAT usage.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL424" source="APP_EAUTH827" target="APP_MEGAHIT"><data key="edge_relationship_id">REL424</data><data key="edge_source_entity_id">APP_EAUTH827</data><data key="edge_relationship_type">creates_authorization_for</data><data key="edge_target_entity_id">APP_MEGAHIT</data><data key="edge_operational_context">eDIB documentation describes Electronic Authorization as creating signed SSA-827s used to retrieve medical evidence; HIT requests require claimant authorization.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Exact current integration boundary is not asserted.</data></edge><edge id="REL425" source="APP_DCPS" target="ORG_DDS"><data key="edge_relationship_id">REL425</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Current Open Data inventory says DCPS contains data necessary for DDS components to process and make disability determinations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL426" source="APP_DCPS" target="ARCH_CLOUD"><data key="edge_relationship_id">REL426</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">uses_architecture</data><data key="edge_target_entity_id">ARCH_CLOUD</data><data key="edge_operational_context">GAO describes DCPS2 as SSA's cloud-based national disability case processing system.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL427" source="APP_DCPS" target="ORG_DDS"><data key="edge_relationship_id">REL427</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">replaced_legacy_systems_for</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">SSA testified the national system replaced 52 independently operated DDS legacy systems and all DDSs used the uniform system.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL428" source="APP_IMAGEN" target="PLAT_ADDS"><data key="edge_relationship_id">REL428</data><data key="edge_source_entity_id">APP_IMAGEN</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">PLAT_ADDS</data><data key="edge_operational_context">GAO describes the investment as ADDS-IMAGEN.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL429" source="APP_IMAGEN" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL429</data><data key="edge_source_entity_id">APP_IMAGEN</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">GAO explicitly identifies advanced machine learning as part of ADDS-IMAGEN.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL430" source="APP_IMAGEN" target="TECH_PREDICTIVE_ANALYTICS"><data key="edge_relationship_id">REL430</data><data key="edge_source_entity_id">APP_IMAGEN</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_PREDICTIVE_ANALYTICS</data><data key="edge_operational_context">GAO explicitly identifies predictive analytics as part of ADDS-IMAGEN.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL431" source="APP_IMAGEN" target="REPO_EF"><data key="edge_relationship_id">REL431</data><data key="edge_source_entity_id">APP_IMAGEN</data><data key="edge_relationship_type">supports_review_of</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">GAO says ADDS-IMAGEN supports review of medical evidence against SSA disability policies.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship expresses evidence-review function; GAO does not specify the physical repository interface.</data></edge><edge id="REL432" source="APP_DCPS" target="APP_IMAGEN"><data key="edge_relationship_id">REL432</data><data key="edge_source_entity_id">APP_DCPS</data><data key="edge_relationship_type">integration_enhancement_with</data><data key="edge_target_entity_id">APP_IMAGEN</data><data key="edge_operational_context">GAO says DCPS2 Enhancements include improving system integration with ADDS-IMAGEN.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">GAO reported expected completion September 2026; this edge is an enhancement target, not proof every planned enhancement is complete.</data></edge><edge id="REL433" source="CON_DCPS_LEIDOS_2018" target="ORG_LEIDOS"><data key="edge_relationship_id">REL433</data><data key="edge_source_entity_id">CON_DCPS_LEIDOS_2018</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_LEIDOS</data><data key="edge_operational_context">USAspending identifies Leidos, Inc. as recipient of completed delivery order 28321318FDS030231.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL434" source="CON_DCPS_LEIDOS_2018" target="APP_DCPS"><data key="edge_relationship_id">REL434</data><data key="edge_source_entity_id">CON_DCPS_LEIDOS_2018</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">USAspending description says contractor provided expertise, technical knowledge, IT support personnel and related resources for the SSA DCPS program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL435" source="APP_HACPS" target="ORG_OHO"><data key="edge_relationship_id">REL435</data><data key="edge_source_entity_id">APP_HACPS</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">GAO and SSA identify HACPS as the national system used by hearing offices and national hearing centers to manage appeals cases and schedule hearings.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL436" source="APP_HACPS" target="DB_HACPS_DATA"><data key="edge_relationship_id">REL436</data><data key="edge_source_entity_id">APP_HACPS</data><data key="edge_relationship_type">uses_logical_data_store</data><data key="edge_target_entity_id">DB_HACPS_DATA</data><data key="edge_operational_context">SSA separately inventories a HACPS-named data store containing hearings and appeals information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Logical app/store relationship; physical database boundary is not published.</data></edge><edge id="REL437" source="DB_HA_MI_ODS" target="ORG_OHO"><data key="edge_relationship_id">REL437</data><data key="edge_source_entity_id">DB_HA_MI_ODS</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">SSA inventories the ODS for managing/reporting on hearing and appeals level cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL438" source="DB_HA_MI_ODS" target="ORG_OAO"><data key="edge_relationship_id">REL438</data><data key="edge_source_entity_id">DB_HA_MI_ODS</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">ORG_OAO</data><data key="edge_operational_context">The same ODS is described as covering all hearing and appeals level cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL439" source="DB_OHA_LEGACY_DB2" target="ORG_OHO"><data key="edge_relationship_id">REL439</data><data key="edge_source_entity_id">DB_OHA_LEGACY_DB2</data><data key="edge_relationship_type">stores_legacy_data_for</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">SSA says this legacy asset stores hearing, appeal and federal-court adjudicative data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL440" source="DB_OHA_LEGACY_DB2" target="ORG_OAO"><data key="edge_relationship_id">REL440</data><data key="edge_source_entity_id">DB_OHA_LEGACY_DB2</data><data key="edge_relationship_type">stores_legacy_data_for</data><data key="edge_target_entity_id">ORG_OAO</data><data key="edge_operational_context">SSA says this legacy asset stores hearing, appeal and federal-court adjudicative data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL441" source="DB_OHA_LEGACY_DB2" target="TECH_DB2"><data key="edge_relationship_id">REL441</data><data key="edge_source_entity_id">DB_OHA_LEGACY_DB2</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">SSA says the legacy adjudicative data were converted to DB2.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL442" source="DB_OHA_LEGACY_DB2" target="TECH_IDMS"><data key="edge_relationship_id">REL442</data><data key="edge_source_entity_id">DB_OHA_LEGACY_DB2</data><data key="edge_relationship_type">migrated_from</data><data key="edge_target_entity_id">TECH_IDMS</data><data key="edge_operational_context">SSA says the legacy adjudicative data were converted from IDMS to DB2.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL443" source="APP_CPMS" target="ORG_OHO"><data key="edge_relationship_id">REL443</data><data key="edge_source_entity_id">APP_CPMS</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">Current HALLEX still directs CPMS use when a case remains in CPMS-only processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL444" source="APP_HACPS" target="APP_CPMS"><data key="edge_relationship_id">REL444</data><data key="edge_source_entity_id">APP_HACPS</data><data key="edge_relationship_type">progressively_replaces</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">SSA modernization records show HACPS replacing CPMS functions and reducing dual processing, while current HALLEX confirms CPMS remains for some workloads.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Transition is not modeled as complete.</data></edge><edge id="REL445" source="APP_OAOCPS" target="ORG_OAO"><data key="edge_relationship_id">REL445</data><data key="edge_source_entity_id">APP_OAOCPS</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_OAO</data><data key="edge_operational_context">Current HALLEX uses OAOCPS for Appeals Council/OAO case processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL446" source="APP_ARPS" target="ORG_OAO"><data key="edge_relationship_id">REL446</data><data key="edge_source_entity_id">APP_ARPS</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_OAO</data><data key="edge_operational_context">Current HALLEX still identifies ARPS for Appeals Council-level processing as appropriate.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL447" source="APP_OAOCPS" target="APP_ARPS"><data key="edge_relationship_id">REL447</data><data key="edge_source_entity_id">APP_OAOCPS</data><data key="edge_relationship_type">progressively_replaces</data><data key="edge_target_entity_id">APP_ARPS</data><data key="edge_operational_context">Archived transition instructions identify OAOCPS as the replacement path for ARPS; current HALLEX shows both remain in use as appropriate.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Transition not complete for all workflows.</data></edge><edge id="REL448" source="APP_RASR" target="APP_HACPS"><data key="edge_relationship_id">REL448</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">propagates_representative_data_to</data><data key="edge_target_entity_id">APP_HACPS</data><data key="edge_operational_context">Current HALLEX says information added/updated in RASR automatically propagates to HACPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL449" source="APP_RASR" target="APP_OAOCPS"><data key="edge_relationship_id">REL449</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">propagates_representative_data_to</data><data key="edge_target_entity_id">APP_OAOCPS</data><data key="edge_operational_context">Current HALLEX says information added/updated in RASR automatically propagates to OAOCPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL450" source="APP_RASR" target="APP_CPMS"><data key="edge_relationship_id">REL450</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">requires_manual_or_separate_update_for</data><data key="edge_target_entity_id">APP_CPMS</data><data key="edge_operational_context">Current HALLEX still requires appropriate CPMS entries in some workflows; older transition instructions state RASR did not propagate to CPMS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Exact present automated integration boundary requires technical validation.</data></edge><edge id="REL451" source="APP_RASR" target="APP_ARPS"><data key="edge_relationship_id">REL451</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">requires_manual_or_separate_update_for</data><data key="edge_target_entity_id">APP_ARPS</data><data key="edge_operational_context">Current HALLEX still requires ARPS entries in some workflows; older transition instructions state ARPS did not interface with RASR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Exact present automated integration boundary requires technical validation.</data></edge><edge id="REL452" source="APP_HACPS" target="SVC_OHO_CENTRAL_PRINT"><data key="edge_relationship_id">REL452</data><data key="edge_source_entity_id">APP_HACPS</data><data key="edge_relationship_type">generates_documents_for</data><data key="edge_target_entity_id">SVC_OHO_CENTRAL_PRINT</data><data key="edge_operational_context">OHO staff generate documents electronically in HACPS and send completed documents to central print.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL453" source="APP_DGS" target="SVC_OHO_CENTRAL_PRINT"><data key="edge_relationship_id">REL453</data><data key="edge_source_entity_id">APP_DGS</data><data key="edge_relationship_type">generates_documents_for</data><data key="edge_target_entity_id">SVC_OHO_CENTRAL_PRINT</data><data key="edge_operational_context">OHO staff also generate documents in DGS and send completed documents to central print.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL454" source="SVC_OHO_CENTRAL_PRINT" target="APP_EVIEW"><data key="edge_relationship_id">REL454</data><data key="edge_source_entity_id">SVC_OHO_CENTRAL_PRINT</data><data key="edge_relationship_type">causes_automatic_upload_to</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">HALLEX says documents sent to central print are also automatically uploaded to the claimant electronic claims file in eView.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL455" source="APP_OAOCPS" target="ORG_OAO"><data key="edge_relationship_id">REL455</data><data key="edge_source_entity_id">APP_OAOCPS</data><data key="edge_relationship_type">contains_notice_templates_for</data><data key="edge_target_entity_id">ORG_OAO</data><data key="edge_operational_context">Current HALLEX says OAO staff can find representative-related notices/templates in OAOCPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL456" source="APP_HEART" target="DATA_HEARING_RECORDING"><data key="edge_relationship_id">REL456</data><data key="edge_source_entity_id">APP_HEART</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_HEARING_RECORDING</data><data key="edge_operational_context">SSA describes HeaRT as recording hearings; the official hearing record is verbatim audio.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL457" source="APP_HEART" target="DATA_HEARING_TRANSCRIPT"><data key="edge_relationship_id">REL457</data><data key="edge_source_entity_id">APP_HEART</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_HEARING_TRANSCRIPT</data><data key="edge_operational_context">SSA describes HeaRT as producing transcripts for hearings-level cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL458" source="APP_HEART" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL458</data><data key="edge_source_entity_id">APP_HEART</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">SSA says HeaRT uses generative AI to improve automated transcript accuracy.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL459" source="APP_HEART" target="SVC_ONLINE_VIDEO_HEARINGS"><data key="edge_relationship_id">REL459</data><data key="edge_source_entity_id">APP_HEART</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SVC_ONLINE_VIDEO_HEARINGS</data><data key="edge_operational_context">SSA says HeaRT supports in-person, telephone and video hearing formats.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL460" source="SVC_ONLINE_VIDEO_HEARINGS" target="PLAT_MS_TEAMS"><data key="edge_relationship_id">REL460</data><data key="edge_source_entity_id">SVC_ONLINE_VIDEO_HEARINGS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PLAT_MS_TEAMS</data><data key="edge_operational_context">SSA currently conducts online video hearings using Microsoft Teams.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL461" source="SVC_ONLINE_VIDEO_HEARINGS" target="DATA_HEARING_RECORDING"><data key="edge_relationship_id">REL461</data><data key="edge_source_entity_id">SVC_ONLINE_VIDEO_HEARINGS</data><data key="edge_relationship_type">creates_official_record_as</data><data key="edge_target_entity_id">DATA_HEARING_RECORDING</data><data key="edge_operational_context">Current HALLEX says online-video proceedings are officially recorded in audio, not video.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL462" source="DATA_HEARING_RECORDING" target="APP_EVIEW"><data key="edge_relationship_id">REL462</data><data key="edge_source_entity_id">DATA_HEARING_RECORDING</data><data key="edge_relationship_type">can_be_accessed_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Appeals Council staff are instructed to check eView for hearing recordings; hearing offices upload recordings into electronic claim files.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL463" source="APP_EBB" target="APP_EVIEW"><data key="edge_relationship_id">REL463</data><data key="edge_source_entity_id">APP_EBB</data><data key="edge_relationship_type">linked_from</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">POMS states the eView secondary title bar displays an eBB indicator/link for qualifying hearing-level or higher cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Current reference is corroborated by 2026 batch run; feature-level modernization needs further validation.</data></edge><edge id="REL464" source="APP_REP_AVAIL_PORTAL" target="PROC_ERAP"><data key="edge_relationship_id">REL464</data><data key="edge_source_entity_id">APP_REP_AVAIL_PORTAL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_ERAP</data><data key="edge_operational_context">The Representative Availability Portal is the web submission channel for ERAP representative availability.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL465" source="APP_REP_AVAIL_PORTAL" target="APP_MYSSA"><data key="edge_relationship_id">REL465</data><data key="edge_source_entity_id">APP_REP_AVAIL_PORTAL</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA says entering the portal first takes the user through my Social Security credentialing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL466" source="PROC_ERAP" target="ORG_OHO"><data key="edge_relationship_id">REL466</data><data key="edge_source_entity_id">PROC_ERAP</data><data key="edge_relationship_type">supports_scheduling_for</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">ERAP collects representative availability for SSA hearing scheduling.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL467" source="APP_HACPS_INVOICE" target="APP_HACPS"><data key="edge_relationship_id">REL467</data><data key="edge_source_entity_id">APP_HACPS_INVOICE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_HACPS</data><data key="edge_operational_context">SSA labels the service the HACPS Invoice Portal.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL468" source="APP_HACPS_INVOICE" target="ORG_OHO"><data key="edge_relationship_id">REL468</data><data key="edge_source_entity_id">APP_HACPS_INVOICE</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">Portal submits call-order invoices to hearing offices electronically and provides real-time status.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL469" source="APP_HACPS_INVOICE" target="APP_MYSSA"><data key="edge_relationship_id">REL469</data><data key="edge_source_entity_id">APP_HACPS_INVOICE</data><data key="edge_relationship_type">accessed_after_authentication_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA allows portal access after logging into a my Social Security account (or ERE for Experts).</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL470" source="APP_HACPS_INVOICE" target="APP_ERE"><data key="edge_relationship_id">REL470</data><data key="edge_source_entity_id">APP_HACPS_INVOICE</data><data key="edge_relationship_type">accessed_after_authentication_via</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">SSA allows portal access after logging into an ERE for Experts account (or my Social Security).</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">ERE for Experts is treated as part of the broader ERE service in this Atlas.</data></edge><edge id="REL471" source="APP_MYSSA" target="SVC_MYSSA_APPEALS_STATUS"><data key="edge_relationship_id">REL471</data><data key="edge_source_entity_id">APP_MYSSA</data><data key="edge_relationship_type">hosts</data><data key="edge_target_entity_id">SVC_MYSSA_APPEALS_STATUS</data><data key="edge_operational_context">SSA launched hearing- and appeals-level claim status tracking in my Social Security.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL472" source="APP_MYSSA" target="SVC_MYSSA_ADJ_FORMS"><data key="edge_relationship_id">REL472</data><data key="edge_source_entity_id">APP_MYSSA</data><data key="edge_relationship_type">hosts</data><data key="edge_target_entity_id">SVC_MYSSA_ADJ_FORMS</data><data key="edge_operational_context">SSA launched online submission of HA-4631, HA-4632 and HA-4633 in my Social Security.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL473" source="APP_MYSSA" target="SVC_MYSSA_HEARING_NOTICES"><data key="edge_relationship_id">REL473</data><data key="edge_source_entity_id">APP_MYSSA</data><data key="edge_relationship_type">hosts</data><data key="edge_target_entity_id">SVC_MYSSA_HEARING_NOTICES</data><data key="edge_operational_context">SSA launched secure proffer-letter access and additional hearing notices in the my Social Security Message Center.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL474" source="APP_IAPPEALS" target="ORG_OAO"><data key="edge_relationship_id">REL474</data><data key="edge_source_entity_id">APP_IAPPEALS</data><data key="edge_relationship_type">submits_request_for_review_to</data><data key="edge_target_entity_id">ORG_OAO</data><data key="edge_operational_context">SSA identifies iAppeals i520 as the preferred method for requesting Appeals Council review.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL475" source="DATA_OHO_WORKLOAD_PUBLIC" target="ORG_OHO"><data key="edge_relationship_id">REL475</data><data key="edge_source_entity_id">DATA_OHO_WORKLOAD_PUBLIC</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">ORG_OHO</data><data key="edge_operational_context">The FY2026 public dataset reports hearing-office receipts, dispositions, pending workload and average processing time.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL476" source="DATA_AC_RR_PUBLIC" target="ORG_OAO"><data key="edge_relationship_id">REL476</data><data key="edge_source_entity_id">DATA_AC_RR_PUBLIC</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">ORG_OAO</data><data key="edge_operational_context">The public dataset reports Appeals Council request-for-review receipts, dispositions and pending workload.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL477" source="APP_DMS" target="APP_ARS2"><data key="edge_relationship_id">REL477</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_ARS2</data><data key="edge_operational_context">2018 DMS PIA identifies this as a DMS subsystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Current operation is independently corroborated where more recent POMS exists; otherwise relationship is architecture documentation.</data></edge><edge id="REL478" source="APP_DMS" target="APP_ECO"><data key="edge_relationship_id">REL478</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">2018 DMS PIA identifies this as a DMS subsystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Current operation is independently corroborated where more recent POMS exists; otherwise relationship is architecture documentation.</data></edge><edge id="REL479" source="APP_DMS" target="APP_NED"><data key="edge_relationship_id">REL479</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_NED</data><data key="edge_operational_context">2018 DMS PIA identifies this as a DMS subsystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Current operation is independently corroborated where more recent POMS exists; otherwise relationship is architecture documentation.</data></edge><edge id="REL480" source="APP_DMS" target="APP_RECOOP"><data key="edge_relationship_id">REL480</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context">2018 DMS PIA identifies this as a DMS subsystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Current operation is independently corroborated where more recent POMS exists; otherwise relationship is architecture documentation.</data></edge><edge id="REL481" source="APP_DMS" target="APP_ROAR"><data key="edge_relationship_id">REL481</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">2018 DMS PIA identifies this as a DMS subsystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Current operation is independently corroborated where more recent POMS exists; otherwise relationship is architecture documentation.</data></edge><edge id="REL482" source="APP_DMS" target="APP_DM_CONVERSION"><data key="edge_relationship_id">REL482</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_DM_CONVERSION</data><data key="edge_operational_context">2018 DMS PIA identifies this as a DMS subsystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Current operation is independently corroborated where more recent POMS exists; otherwise relationship is architecture documentation.</data></edge><edge id="REL483" source="APP_DMS" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">REL483</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">has_documented_subsystem</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">2018 DMS PIA identifies this as a DMS subsystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Current operation is independently corroborated where more recent POMS exists; otherwise relationship is architecture documentation.</data></edge><edge id="REL484" source="APP_DMS" target="DOM_PROGRAM_DEBT"><data key="edge_relationship_id">REL484</data><data key="edge_source_entity_id">APP_DMS</data><data key="edge_relationship_type">manages</data><data key="edge_target_entity_id">DOM_PROGRAM_DEBT</data><data key="edge_operational_context">DMS records, classifies, summarizes and consolidates program debt and collection activity.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL485" source="APP_ROAR" target="DOM_PROGRAM_DEBT"><data key="edge_relationship_id">REL485</data><data key="edge_source_entity_id">APP_ROAR</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">DOM_PROGRAM_DEBT</data><data key="edge_operational_context">ROAR establishes, recovers and accounts for Title II overpayments.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL486" source="SYS_SSR" target="DOM_PROGRAM_DEBT"><data key="edge_relationship_id">REL486</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">stores_title_xvi_debt_within</data><data key="edge_target_entity_id">DOM_PROGRAM_DEBT</data><data key="edge_operational_context">Current ECO/RECOOP/CPR instructions use SSR as the Title XVI debt source/record.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL487" source="SYS_MBR" target="DOM_PROGRAM_DEBT"><data key="edge_relationship_id">REL487</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">stores_title_ii_debt_context_for</data><data key="edge_target_entity_id">DOM_PROGRAM_DEBT</data><data key="edge_operational_context">Current external-collection and remittance processes use MBR/ROAR for Title II debtor and payment context.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL488" source="APP_ECO" target="APP_ROAR"><data key="edge_relationship_id">REL488</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">selects_debts_from</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">ECO selects eligible Title II debtors from ROAR master data for external collection.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL489" source="APP_ECO" target="SYS_SSR"><data key="edge_relationship_id">REL489</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">selects_debts_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">ECO selects eligible Title XVI debtors from SSR for external collection.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL490" source="APP_ECO" target="PROC_TRO"><data key="edge_relationship_id">REL490</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">initiates_or_routes_to</data><data key="edge_target_entity_id">PROC_TRO</data><data key="edge_operational_context">ECO selects and notices eligible tax-refund-offset debts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL491" source="APP_ECO" target="PROC_ADMIN_OFFSET"><data key="edge_relationship_id">REL491</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">initiates_or_routes_to</data><data key="edge_target_entity_id">PROC_ADMIN_OFFSET</data><data key="edge_operational_context">ECO selects eligible debts for administrative offset.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL492" source="APP_ECO" target="PROC_AWG"><data key="edge_relationship_id">REL492</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">initiates_or_routes_to</data><data key="edge_target_entity_id">PROC_AWG</data><data key="edge_operational_context">ECO selects eligible debts for administrative wage garnishment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL493" source="APP_ECO" target="PROC_FSO"><data key="edge_relationship_id">REL493</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">initiates_or_routes_to</data><data key="edge_target_entity_id">PROC_FSO</data><data key="edge_operational_context">ECO selects eligible debts for Federal salary offset.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL494" source="APP_ECO" target="EX_CREDIT_BUREAU_REPORTING"><data key="edge_relationship_id">REL494</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">reports_to</data><data key="edge_target_entity_id">EX_CREDIT_BUREAU_REPORTING</data><data key="edge_operational_context">ECO selection/noticing supports debt reporting to credit repositories.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL495" source="APP_ECO" target="SVC_TOP"><data key="edge_relationship_id">REL495</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">certifies_debts_to</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">After due process, SSA certifies qualifying debts selected by ECO to Treasury TOP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL496" source="APP_ECO" target="APP_ORS"><data key="edge_relationship_id">REL496</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">stores_notices_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">ECO notices sent November 2015 or later are stored in ORS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL497" source="APP_ECO" target="SVC_TOP"><data key="edge_relationship_id">REL497</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">sends_weekly_updates_to</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">SSA sends automated weekly debt-status updates to Treasury after TOP certification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL498" source="APP_NED" target="APP_ROAR"><data key="edge_relationship_id">REL498</data><data key="edge_source_entity_id">APP_NED</data><data key="edge_relationship_type">selects_or_controls</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">NED selects qualifying legally defined overpayments established on ROAR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL499" source="APP_NED" target="APP_RECOOP"><data key="edge_relationship_id">REL499</data><data key="edge_source_entity_id">APP_NED</data><data key="edge_relationship_type">uses_billing</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context">NED uses RECOOP billing and follow-up for debts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL500" source="APP_NED" target="APP_ECO"><data key="edge_relationship_id">REL500</data><data key="edge_source_entity_id">APP_NED</data><data key="edge_relationship_type">uses_external_collection</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">NED uses TOP/ECO tools for eligible debts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL501" source="APP_NED" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL501</data><data key="edge_source_entity_id">APP_NED</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">Published NED scope includes qualifying debts owed by representative payees of deceased Title II beneficiaries.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL502" source="APP_RECOOP" target="APP_ROAR"><data key="edge_relationship_id">REL502</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">controls_nonpay_debt_from</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">RECOOP bills and follows up Title II debts when benefit offset is unavailable/non-current-pay.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL503" source="APP_RECOOP" target="SYS_SSR"><data key="edge_relationship_id">REL503</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">controls_nonpay_debt_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">RECOOP controls SSI overpayment refund/billing cases for nonpayment status.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL504" source="APP_RECOOP" target="PROC_CPR"><data key="edge_relationship_id">REL504</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">selects_for</data><data key="edge_target_entity_id">PROC_CPR</data><data key="edge_operational_context">Current POMS says automated mandatory CPR selection of SSI debts is made from RECOOP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL505" source="APP_RECOOP" target="SYS_MBR"><data key="edge_relationship_id">REL505</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">stops_billing_when_death_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">When death is recorded on MBR, RECOOP automatically stops billing and produces a death alert.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL506" source="APP_RECOOP" target="SYS_SSR"><data key="edge_relationship_id">REL506</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">deletes_debt_when_death_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">When death is recorded on SSR, RECOOP automatically deletes the debt.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL507" source="APP_DM_CONVERSION" target="APP_ROAR"><data key="edge_relationship_id">REL507</data><data key="edge_source_entity_id">APP_DM_CONVERSION</data><data key="edge_relationship_type">prepares_transactions_for</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">DMS PIA says DM Conversion prepares Title II debt-management data for ROAR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL508" source="APP_DM_CONVERSION" target="APP_RECOOP"><data key="edge_relationship_id">REL508</data><data key="edge_source_entity_id">APP_DM_CONVERSION</data><data key="edge_relationship_type">prepares_transactions_for</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context">DMS PIA says DM Conversion prepares debt-management transactions for RECOOP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL509" source="APP_DM_CONVERSION" target="APP_ECO"><data key="edge_relationship_id">REL509</data><data key="edge_source_entity_id">APP_DM_CONVERSION</data><data key="edge_relationship_type">prepares_transactions_for</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">DMS PIA says DM Conversion prepares debt-management transactions for ECO.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL510" source="APP_DM_CONVERSION" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">REL510</data><data key="edge_source_entity_id">APP_DM_CONVERSION</data><data key="edge_relationship_type">prepares_transactions_for</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">DMS PIA says DM Conversion prepares transaction data for Remittance Process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL511" source="IFACE_DRIN" target="APP_DMS"><data key="edge_relationship_id">REL511</data><data key="edge_source_entity_id">IFACE_DRIN</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Current POMS identifies DRIN as a DMS Record Installment Agreement screen.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL512" source="IFACE_DRIN" target="APP_ROAR"><data key="edge_relationship_id">REL512</data><data key="edge_source_entity_id">IFACE_DRIN</data><data key="edge_relationship_type">updates_overnight</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">Current POMS says DRIN installment input updates ROAR overnight.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL513" source="APP_SERS" target="STORE_SERS_PROGRAMMATIC"><data key="edge_relationship_id">REL513</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">contains_store</data><data key="edge_target_entity_id">STORE_SERS_PROGRAMMATIC</data><data key="edge_operational_context">Current POMS identifies SERS Programmatic store.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL514" source="APP_SERS" target="STORE_SERS_CONSERVED"><data key="edge_relationship_id">REL514</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">contains_store</data><data key="edge_target_entity_id">STORE_SERS_CONSERVED</data><data key="edge_operational_context">Current POMS identifies SERS Conserved Funds store.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL515" source="STORE_SERS_PROGRAMMATIC" target="SYS_MBR"><data key="edge_relationship_id">REL515</data><data key="edge_source_entity_id">STORE_SERS_PROGRAMMATIC</data><data key="edge_relationship_type">queries_or_displays_debt_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SERS Programmatic store retrieves established debt/overpayment information from current SSA debt records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL516" source="STORE_SERS_PROGRAMMATIC" target="SYS_SSR"><data key="edge_relationship_id">REL516</data><data key="edge_source_entity_id">STORE_SERS_PROGRAMMATIC</data><data key="edge_relationship_type">queries_or_displays_debt_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SERS Programmatic store retrieves established debt/overpayment information from current SSA debt records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL517" source="STORE_SERS_PROGRAMMATIC" target="APP_ROAR"><data key="edge_relationship_id">REL517</data><data key="edge_source_entity_id">STORE_SERS_PROGRAMMATIC</data><data key="edge_relationship_type">queries_or_displays_debt_from</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">SERS Programmatic store retrieves established debt/overpayment information from current SSA debt records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL518" source="STORE_SERS_PROGRAMMATIC" target="APP_ECO"><data key="edge_relationship_id">REL518</data><data key="edge_source_entity_id">STORE_SERS_PROGRAMMATIC</data><data key="edge_relationship_type">queries_or_displays_debt_from</data><data key="edge_target_entity_id">APP_ECO</data><data key="edge_operational_context">SERS Programmatic store retrieves established debt/overpayment information from current SSA debt records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL519" source="APP_SERS" target="APP_DMS"><data key="edge_relationship_id">REL519</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">sends_nightly_batch_to</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Every evening SERS creates a batch file for DMS to process and post remittances to the correct record.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL520" source="APP_SERS" target="APP_DMS_REMITTANCE"><data key="edge_relationship_id">REL520</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_DMS_REMITTANCE</data><data key="edge_operational_context">SERS modernizes field-office remittance processing while DMS posts the resulting remittance data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL521" source="STORE_SERS_CONSERVED" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL521</data><data key="edge_source_entity_id">STORE_SERS_CONSERVED</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">SERS Conserved Funds store processes conserved-fund remittances when no debt exists.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL522" source="APP_RECOOP" target="SVC_PAYGOV"><data key="edge_relationship_id">REL522</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">generates_billing_for</data><data key="edge_target_entity_id">SVC_PAYGOV</data><data key="edge_operational_context">RECOOP billing notices include electronic repayment options for eligible program debt.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL523" source="SVC_PAYGOV" target="APP_RECOOP"><data key="edge_relationship_id">REL523</data><data key="edge_source_entity_id">SVC_PAYGOV</data><data key="edge_relationship_type">processes_payments_for</data><data key="edge_target_entity_id">APP_RECOOP</data><data key="edge_operational_context">Treasury Pay.gov processes electronic payments for eligible Title II/Title XVI debt active in RECOOP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL524" source="SVC_PAYGOV" target="ORG_BFS"><data key="edge_relationship_id">REL524</data><data key="edge_source_entity_id">SVC_PAYGOV</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Pay.gov is a Department of the Treasury/Fiscal Service collection service used on SSA behalf.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL525" source="UTIL_REMITTANCE_ID" target="SVC_PAYGOV"><data key="edge_relationship_id">REL525</data><data key="edge_source_entity_id">UTIL_REMITTANCE_ID</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">SVC_PAYGOV</data><data key="edge_operational_context">Current SSA notice language uses generated Remittance ID for Pay.gov repayment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL526" source="UTIL_REMITTANCE_ID" target="SVC_ONLINE_BILL_PAY"><data key="edge_relationship_id">REL526</data><data key="edge_source_entity_id">UTIL_REMITTANCE_ID</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">SVC_ONLINE_BILL_PAY</data><data key="edge_operational_context">Current notice language directs users to enter the Remittance ID as the account number for Online Bill Pay.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL527" source="SVC_ONLINE_BILL_PAY" target="SYS_SSR"><data key="edge_relationship_id">REL527</data><data key="edge_source_entity_id">SVC_ONLINE_BILL_PAY</data><data key="edge_relationship_type">posts_payment_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS says Online Bill Pay transactions appear on SSR with an OLBP code.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Posting behavior source is older but current 2026 SSA repayment guidance still promotes Online Bill Pay.</data></edge><edge id="REL528" source="SVC_ONLINE_BILL_PAY" target="APP_ROAR"><data key="edge_relationship_id">REL528</data><data key="edge_source_entity_id">SVC_ONLINE_BILL_PAY</data><data key="edge_relationship_type">posts_payment_to</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">POMS says Online Bill Pay transactions appear on MBR/ROAR with an OLBP code.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL529" source="SVC_ONLINE_BILL_PAY" target="SYS_MBR"><data key="edge_relationship_id">REL529</data><data key="edge_source_entity_id">SVC_ONLINE_BILL_PAY</data><data key="edge_relationship_type">posts_payment_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS says Online Bill Pay transactions appear on MBR/ROAR with an OLBP code.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL530" source="SVC_TOP" target="ORG_BFS"><data key="edge_relationship_id">REL530</data><data key="edge_source_entity_id">SVC_TOP</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Fiscal Service operates TOP as a government-wide debt matching and payment offset process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL531" source="SVC_TOP" target="DB_NID3"><data key="edge_relationship_id">REL531</data><data key="edge_source_entity_id">SVC_TOP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DB_NID3</data><data key="edge_operational_context">BPO/TOP matches SSA payment records against Treasury NID3 delinquent-debtor data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL532" source="PROC_TRO" target="SVC_TOP"><data key="edge_relationship_id">REL532</data><data key="edge_source_entity_id">PROC_TRO</data><data key="edge_relationship_type">executed_through</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">Treasury conducts Tax Refund Offset through TOP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL533" source="PROC_ADMIN_OFFSET" target="SVC_TOP"><data key="edge_relationship_id">REL533</data><data key="edge_source_entity_id">PROC_ADMIN_OFFSET</data><data key="edge_relationship_type">executed_through</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">Administrative Offset uses TOP to reduce eligible Federal/State payments.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL534" source="PROC_FSO" target="SVC_TOP"><data key="edge_relationship_id">REL534</data><data key="edge_source_entity_id">PROC_FSO</data><data key="edge_relationship_type">executed_through</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">Federal Salary Offset is a TOP-based collection mechanism.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL535" source="EX_CREDIT_BUREAU_REPORTING" target="ORG_CREDIT_REPOSITORIES"><data key="edge_relationship_id">REL535</data><data key="edge_source_entity_id">EX_CREDIT_BUREAU_REPORTING</data><data key="edge_relationship_type">sends_to</data><data key="edge_target_entity_id">ORG_CREDIT_REPOSITORIES</data><data key="edge_operational_context">SSA sends eligible delinquent debt information to national credit repositories and updates it monthly.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL536" source="APP_ECO" target="EX_CREDIT_BUREAU_REPORTING"><data key="edge_relationship_id">REL536</data><data key="edge_source_entity_id">APP_ECO</data><data key="edge_relationship_type">controls_notice_for</data><data key="edge_target_entity_id">EX_CREDIT_BUREAU_REPORTING</data><data key="edge_operational_context">ECO generates common due-process notices for external collection tools including credit reporting.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL537" source="PROC_BPO" target="SVC_TOP"><data key="edge_relationship_id">REL537</data><data key="edge_source_entity_id">PROC_BPO</data><data key="edge_relationship_type">executed_through</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">Fiscal Service uses TOP to conduct Benefit Payment Offset of eligible Title II payments.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL538" source="PROC_BPO" target="DB_NID3"><data key="edge_relationship_id">REL538</data><data key="edge_source_entity_id">PROC_BPO</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">DB_NID3</data><data key="edge_operational_context">Fiscal Service matches SSA Title II payment records against NID3 for BPO.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL539" source="PROC_BPO" target="ORG_TREASURY"><data key="edge_relationship_id">REL539</data><data key="edge_source_entity_id">PROC_BPO</data><data key="edge_relationship_type">receives_payment_file_from</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">SSA sends payment files to Fiscal Service/Treasury for BPO processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL540" source="PROC_BPO" target="DB_PHUS"><data key="edge_relationship_id">REL540</data><data key="edge_source_entity_id">PROC_BPO</data><data key="edge_relationship_type">posts_offset_history_to</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">Weekly Fiscal Service BPO offset data are posted to PHUS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL541" source="PROC_BPO" target="APP_ORS"><data key="edge_relationship_id">REL541</data><data key="edge_source_entity_id">PROC_BPO</data><data key="edge_relationship_type">stores_notices_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Fiscal Service warning/offset notice files are available in ORS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL542" source="PROC_FPLP" target="DB_PHUS"><data key="edge_relationship_id">REL542</data><data key="edge_source_entity_id">PROC_FPLP</data><data key="edge_relationship_type">posts_offset_history_to</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">Weekly Fiscal Service FPLP offset data are posted to PHUS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL543" source="PROC_FPLP" target="ORG_IRS"><data key="edge_relationship_id">REL543</data><data key="edge_source_entity_id">PROC_FPLP</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Fiscal Service sends levy collections to IRS for Federal tax debt.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL544" source="PROC_CPR" target="DOM_TITLE2"><data key="edge_relationship_id">REL544</data><data key="edge_source_entity_id">PROC_CPR</data><data key="edge_relationship_type">recovers_between</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">CPR can collect overpayment from benefits payable under another SSA-administered program, including Title II.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL545" source="PROC_CPR" target="DOM_TITLE16"><data key="edge_relationship_id">REL545</data><data key="edge_source_entity_id">PROC_CPR</data><data key="edge_relationship_type">recovers_between</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">CPR can collect SSI/Title XVI debt through eligible cross-program benefit recovery.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL546" source="SYS_SSR" target="APP_ROAR"><data key="edge_relationship_id">REL546</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">creates_exchange_record_for</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">Automated K TAC posting creates an SSR exchange record to ROAR to establish SSI debt on MBR/ROAR for Title II withholding.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL547" source="SVC_TREASURY_LOCKBOX" target="ORG_BFS"><data key="edge_relationship_id">REL547</data><data key="edge_source_entity_id">SVC_TREASURY_LOCKBOX</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Fiscal Service provides the lockbox banking service used for SSA programmatic remittances.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL548" source="SVC_TREASURY_LOCKBOX" target="ORG_US_BANK"><data key="edge_relationship_id">REL548</data><data key="edge_source_entity_id">SVC_TREASURY_LOCKBOX</data><data key="edge_relationship_type">uses_financial_agent</data><data key="edge_target_entity_id">ORG_US_BANK</data><data key="edge_operational_context">SSA POMS identifies U.S. Bank as Treasury financial agent processing lockbox payments.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL549" source="APP_RECOOP" target="SVC_TREASURY_LOCKBOX"><data key="edge_relationship_id">REL549</data><data key="edge_source_entity_id">APP_RECOOP</data><data key="edge_relationship_type">historically_routes_mailed_remittances_to</data><data key="edge_target_entity_id">SVC_TREASURY_LOCKBOX</data><data key="edge_operational_context">RECOOP billing notices were changed in 2021 to route mailed programmatic remittances to the Treasury lockbox.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">July 2026 SSA guidance now emphasizes electronic repayment and no longer asks people to mail checks or credit-card forms.</data></edge><edge id="REL550" source="PROJ_DMP" target="APP_DMS"><data key="edge_relationship_id">REL550</data><data key="edge_source_entity_id">PROJ_DMP</data><data key="edge_relationship_type">intended_to_replace_or_consolidate</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">DMP was intended as a comprehensive modern debt-management replacement/consolidation product.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">DMP never reached full production and is no longer being pursued.</data></edge><edge id="REL551" source="PROJ_DMP" target="PROJ_DEBT_COLLECTION_MOD"><data key="edge_relationship_id">REL551</data><data key="edge_source_entity_id">PROJ_DMP</data><data key="edge_relationship_type">status_superseded_by</data><data key="edge_target_entity_id">PROJ_DEBT_COLLECTION_MOD</data><data key="edge_operational_context">FY2026 portfolio shows DMP at $0 and a new Debt Collection Modernization line at $22.9M.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Budget portfolio indicates investment shift; exact program lineage is not explicitly described as a formal replacement.</data></edge><edge id="REL552" source="PROJ_DEBT_COLLECTION_MOD" target="SVC_CRS"><data key="edge_relationship_id">REL552</data><data key="edge_source_entity_id">PROJ_DEBT_COLLECTION_MOD</data><data key="edge_relationship_type">uses_or_plans_shared_service</data><data key="edge_target_entity_id">SVC_CRS</data><data key="edge_operational_context">SSA describes current debt modernization as using government-wide shared services; FY2025 AFR says SSA is implementing CRS for non-pay debtors.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL553" source="SVC_CRS" target="ORG_BFS"><data key="edge_relationship_id">REL553</data><data key="edge_source_entity_id">SVC_CRS</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Fiscal Service operates CRS for federal agencies.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL554" source="SVC_CRS" target="SVC_PAYGOV"><data key="edge_relationship_id">REL554</data><data key="edge_source_entity_id">SVC_CRS</data><data key="edge_relationship_type">integrates_with</data><data key="edge_target_entity_id">SVC_PAYGOV</data><data key="edge_operational_context">Fiscal Service says CRS leverages Pay.gov for collection services.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL555" source="SVC_CRS" target="SVC_CROSS_SERVICING"><data key="edge_relationship_id">REL555</data><data key="edge_source_entity_id">SVC_CRS</data><data key="edge_relationship_type">transfers_eligible_delinquent_debt_to</data><data key="edge_target_entity_id">SVC_CROSS_SERVICING</data><data key="edge_operational_context">CRS transfers eligible delinquent debt to Treasury Cross-Servicing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL556" source="SVC_CROSS_SERVICING" target="ORG_BFS"><data key="edge_relationship_id">REL556</data><data key="edge_source_entity_id">SVC_CROSS_SERVICING</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">Fiscal Service operates Cross-Servicing for delinquent nontax debt.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL557" source="SVC_CROSS_SERVICING" target="SVC_TOP"><data key="edge_relationship_id">REL557</data><data key="edge_source_entity_id">SVC_CROSS_SERVICING</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">Treasury says Cross-Servicing can refer delinquent debt to TOP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL558" source="SVC_CROSS_SERVICING" target="PROC_AWG"><data key="edge_relationship_id">REL558</data><data key="edge_source_entity_id">SVC_CROSS_SERVICING</data><data key="edge_relationship_type">can_use</data><data key="edge_target_entity_id">PROC_AWG</data><data key="edge_operational_context">Treasury says Cross-Servicing can use administrative wage garnishment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL559" source="APP_ERPS" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL559</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">stores_data_for</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">Current SSA Open Data says eRPS contains data for payee application/selection and misuse processes.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL560" source="APP_ERPS" target="SYS_MBR"><data key="edge_relationship_id">REL560</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">records_payee_information_on_or_with</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Payee information/type is maintained across eRPS and the Title II payment record; some updates are automatic and others require manual action.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship deliberately avoids claiming all MBR updates are automatic.</data></edge><edge id="REL561" source="APP_ERPS" target="SYS_SSR"><data key="edge_relationship_id">REL561</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">records_payee_information_on_or_with</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Payee information/type is maintained across eRPS and the SSI payment record; OIG and POMS document manual-transfer cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship deliberately avoids claiming all SSR updates are automatic.</data></edge><edge id="REL562" source="APP_ERPS" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL562</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">verifies_applicant_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Current applicant-interview policy uses NUMIDENT/NUMI information to verify individual applicants.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL563" source="APP_ERPS" target="APP_PUPS"><data key="edge_relationship_id">REL563</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">checks_suitability_data_from</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Current applicant-interview policy requires review of PUPS for incarceration history.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL564" source="APP_ERPS" target="APP_ORS"><data key="edge_relationship_id">REL564</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">stores_application_documents_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Current POMS says representative-payee applications taken via eRPS are stored electronically in ORS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL565" source="APP_ERPS" target="APP_NED"><data key="edge_relationship_id">REL565</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">shares_death_overpayment_work_with</data><data key="edge_target_entity_id">APP_NED</data><data key="edge_operational_context">Current termination instructions state death-overpayment information is in eRPS and the DMS Non-Entitled Debtor database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL566" source="APP_ERPS" target="SYS_MBR"><data key="edge_relationship_id">REL566</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">requires_follow_up_payment_record_action_on_termination</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Terminating a payee in eRPS does not itself terminate the payee relationship on the MBR; FO must take follow-up action.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL567" source="APP_ERPS" target="SYS_SSR"><data key="edge_relationship_id">REL567</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">requires_follow_up_payment_record_action_on_termination</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Terminating a payee in eRPS does not itself terminate the payee relationship on the SSR; FO must take follow-up action.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL568" source="PROC_MANUAL_RP_SELECTION" target="APP_ERPS"><data key="edge_relationship_id">REL568</data><data key="edge_source_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="edge_relationship_type">bypasses</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Applicants without an SSN may be processed through the rare manual exception rather than eRPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL569" source="PROC_MANUAL_RP_SELECTION" target="APP_MACADE"><data key="edge_relationship_id">REL569</data><data key="edge_source_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="edge_relationship_type">routes_title_ii_through</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">For Title II no-SSN exception cases, processing-center staff may manually input the payee case through MACADE.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL570" source="PROC_MANUAL_RP_SELECTION" target="SYS_MBR"><data key="edge_relationship_id">REL570</data><data key="edge_source_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II manual payee selections update MBR outside the normal eRPS path.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL571" source="PROC_MANUAL_RP_SELECTION" target="SYS_SSR"><data key="edge_relationship_id">REL571</data><data key="edge_source_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Field offices manually update SSR for Title XVI no-SSN exception cases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL572" source="PROC_MANUAL_RP_SELECTION" target="REPO_NDRED"><data key="edge_relationship_id">REL572</data><data key="edge_source_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="edge_relationship_type">stores_evidence_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Paper SSA-11 applications in manual cases are retained in NDRED using the Evidence Portal or electronic disability folder process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL573" source="PROC_MANUAL_RP_SELECTION" target="APP_EP"><data key="edge_relationship_id">REL573</data><data key="edge_source_entity_id">PROC_MANUAL_RP_SELECTION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Current manual-selection instructions direct staff to scan paper SSA-11 evidence using the Evidence Portal.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL574" source="APP_ERPA" target="APP_ERPS"><data key="edge_relationship_id">REL574</data><data key="edge_source_entity_id">APP_ERPA</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">POMS identifies Electronic Representative Payee Accounting (eRPA) in eRPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed system-selection description is older, while the eRPA data asset is current in Open Data.</data></edge><edge id="REL575" source="APP_ERPA" target="SYS_MBR"><data key="edge_relationship_id">REL575</data><data key="edge_source_entity_id">APP_ERPA</data><data key="edge_relationship_type">uses_source_data_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Accounting selection compiles MBR data for representative-payee reports.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL576" source="APP_ERPA" target="SYS_SSR"><data key="edge_relationship_id">REL576</data><data key="edge_source_entity_id">APP_ERPA</data><data key="edge_relationship_type">uses_source_data_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Accounting selection compiles SSR data for representative-payee reports.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL577" source="APP_ERPA" target="DB_PHUS"><data key="edge_relationship_id">REL577</data><data key="edge_source_entity_id">APP_ERPA</data><data key="edge_relationship_type">uses_source_data_from</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">Title II accounting forms use payment data derived from PHUS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL578" source="DB_ERPA_MI" target="APP_ERPA"><data key="edge_relationship_id">REL578</data><data key="edge_source_entity_id">DB_ERPA_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">APP_ERPA</data><data key="edge_operational_context">Current Data.gov catalog identifies management information for the Representative Payee Accounting process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL579" source="DB_ERPS_MI" target="APP_ERPS"><data key="edge_relationship_id">REL579</data><data key="edge_source_entity_id">DB_ERPS_MI</data><data key="edge_relationship_type">provides_business_intelligence_for</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Current Data.gov catalog says the database contains representative-payee counts for BI reporting.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL580" source="APP_IRPA" target="APP_ERPA"><data key="edge_relationship_id">REL580</data><data key="edge_source_entity_id">APP_IRPA</data><data key="edge_relationship_type">submits_accounting_to</data><data key="edge_target_entity_id">APP_ERPA</data><data key="edge_operational_context">iRPA is an internet channel for completing a requested representative-payee accounting report.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL581" source="APP_IRPP" target="APP_MYSSA"><data key="edge_relationship_id">REL581</data><data key="edge_source_entity_id">APP_IRPP</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA says individual payees access the Representative Payee Portal through a personal my Social Security account.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL582" source="APP_IRPP" target="APP_ERPA"><data key="edge_relationship_id">REL582</data><data key="edge_source_entity_id">APP_IRPP</data><data key="edge_relationship_type">submits_accounting_to</data><data key="edge_target_entity_id">APP_ERPA</data><data key="edge_operational_context">Current iRPP annual-accounting table allows individual payees to submit annual accounting reports.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL583" source="APP_IRPP" target="DOM_EARNINGS"><data key="edge_relationship_id">REL583</data><data key="edge_source_entity_id">APP_IRPP</data><data key="edge_relationship_type">supports_wage_reporting_for</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Current Representative Payee Portal lets individual payees report wages for beneficiaries.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL584" source="SVC_RP_MESSAGE_CENTER" target="APP_IRPP"><data key="edge_relationship_id">REL584</data><data key="edge_source_entity_id">SVC_RP_MESSAGE_CENTER</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_IRPP</data><data key="edge_operational_context">SSA describes the Representative Payee Message Center as a portal feature for messages, alerts and notices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL585" source="SVC_RP_MESSAGE_CENTER" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL585</data><data key="edge_source_entity_id">SVC_RP_MESSAGE_CENTER</data><data key="edge_relationship_type">delivers_notices_for</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">The Message Center displays beneficiary-specific representative-payee messages, alerts and available online notices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL586" source="PLAT_BSO" target="APP_ERPA"><data key="edge_relationship_id">REL586</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">provides_organizational_accounting_channel_to</data><data key="edge_target_entity_id">APP_ERPA</data><data key="edge_operational_context">Current BSO allows organizational representative payees to file Representative Payee Reports electronically.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL587" source="ORG_WBDOC" target="APP_ERPA"><data key="edge_relationship_id">REL587</data><data key="edge_source_entity_id">ORG_WBDOC</data><data key="edge_relationship_type">processes_accounting_forms_for</data><data key="edge_target_entity_id">APP_ERPA</data><data key="edge_operational_context">Current POMS says most Representative Payee Report forms are automatically scanned and reviewed at WBDOC.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL588" source="ORG_WBDOC" target="APP_ERPS"><data key="edge_relationship_id">REL588</data><data key="edge_source_entity_id">ORG_WBDOC</data><data key="edge_relationship_type">validates_accounting_against</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">WBDOC review instructions compare report information with eRPS as needed.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL589" source="ORG_WBDOC" target="SYS_MBR"><data key="edge_relationship_id">REL589</data><data key="edge_source_entity_id">ORG_WBDOC</data><data key="edge_relationship_type">validates_accounting_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">WBDOC review instructions include checking payee coding on MBR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL590" source="ORG_WBDOC" target="SYS_SSR"><data key="edge_relationship_id">REL590</data><data key="edge_source_entity_id">ORG_WBDOC</data><data key="edge_relationship_type">validates_accounting_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">WBDOC review instructions include checking SSR/eRPS beneficiary and payee information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL591" source="APP_ERPA" target="APP_ERPS"><data key="edge_relationship_id">REL591</data><data key="edge_source_entity_id">APP_ERPA</data><data key="edge_relationship_type">validates_collective_account_status_with</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Collective-account instructions use eRPA/eRPS controls and exception processing when collective-account status does not align.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL592" source="APP_RPMT" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL592</data><data key="edge_source_entity_id">APP_RPMT</data><data key="edge_relationship_type">identifies_reviews_due_for</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">RPMT automatically lists fee-for-service payees due for their three-year review.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL593" source="ORG_PA_AGENCIES" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL593</data><data key="edge_source_entity_id">ORG_PA_AGENCIES</data><data key="edge_relationship_type">conduct_reviews_for</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">Current SSA program page says P&amp;A organizations conduct periodic onsite and other reviews of representative payees.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL594" source="APP_RPMT" target="ORG_PA_AGENCIES"><data key="edge_relationship_id">REL594</data><data key="edge_source_entity_id">APP_RPMT</data><data key="edge_relationship_type">supports_review_work_of</data><data key="edge_target_entity_id">ORG_PA_AGENCIES</data><data key="edge_operational_context">POMS links RPMT review-due listings to P&amp;A-conducted periodic reviews.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL595" source="APP_RPMA" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL595</data><data key="edge_source_entity_id">APP_RPMA</data><data key="edge_relationship_type">tracks_expanded_monitoring_for</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">Current termination instructions say to annotate RPMA when a payee is subject to expanded monitoring.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL596" source="ORG_DNB" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL596</data><data key="edge_source_entity_id">ORG_DNB</data><data key="edge_relationship_type">provides_credit_information_for</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">SSA contracts with D&amp;B for credit information on new non-governmental FFS organizational payee applicants.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL597" source="APP_ERPS" target="ORG_DNB"><data key="edge_relationship_id">REL597</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">records_suitability_determination_informed_by</data><data key="edge_target_entity_id">ORG_DNB</data><data key="edge_operational_context">After D&amp;B credit review, staff document the suitability determination in the eRPS RPST screen.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL598" source="APP_ADRP" target="APP_MYSSA"><data key="edge_relationship_id">REL598</data><data key="edge_source_entity_id">APP_ADRP</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">The public can provide or update advance designation through my Social Security.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL599" source="APP_ADRP" target="APP_MCS"><data key="edge_relationship_id">REL599</data><data key="edge_source_entity_id">APP_ADRP</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Technicians can access ADRP through the MCS Claims Systems path.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL600" source="APP_ADRP" target="APP_MSSICS"><data key="edge_relationship_id">REL600</data><data key="edge_source_entity_id">APP_ADRP</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Technicians can access ADRP through the SSI Claims System path.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL601" source="APP_ADRP" target="APP_ORS"><data key="edge_relationship_id">REL601</data><data key="edge_source_entity_id">APP_ADRP</data><data key="edge_relationship_type">stores_receipts_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Effective July 1, 2025, SSA stopped mailing printed ADRP transaction receipts; a copy is stored in ORS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL602" source="APP_ADRP" target="APP_ERPS"><data key="edge_relationship_id">REL602</data><data key="edge_source_entity_id">APP_ADRP</data><data key="edge_relationship_type">provides_payee_leads_to</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">When a payee is needed, SSA considers advance designees as the first potential leads, while actual payee selection is processed under eRPS procedures.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL603" source="PROC_STUCK_SWEEPER" target="APP_ERPS"><data key="edge_relationship_id">REL603</data><data key="edge_source_entity_id">PROC_STUCK_SWEEPER</data><data key="edge_relationship_type">checks_pending_cases_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">OIG documented Stuck Sweeper as a monthly function reviewing eRPS Ready to Process cases older than 14 days.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Audit-documented 2024 control; current 2026 status not independently verified.</data></edge><edge id="REL604" source="PROC_STUCK_SWEEPER" target="SYS_MBR"><data key="edge_relationship_id">REL604</data><data key="edge_source_entity_id">PROC_STUCK_SWEEPER</data><data key="edge_relationship_type">compares_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Stuck Sweeper compares eRPS data with payment records, including MBR for Title II.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL605" source="PROC_STUCK_SWEEPER" target="SYS_SSR"><data key="edge_relationship_id">REL605</data><data key="edge_source_entity_id">PROC_STUCK_SWEEPER</data><data key="edge_relationship_type">compares_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Stuck Sweeper compares eRPS data with payment records, including SSR for SSI.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL606" source="PROC_STUCK_SWEEPER" target="APP_WAC"><data key="edge_relationship_id">REL606</data><data key="edge_source_entity_id">PROC_STUCK_SWEEPER</data><data key="edge_relationship_type">generates_alerts_to</data><data key="edge_target_entity_id">APP_WAC</data><data key="edge_operational_context">OIG states Stuck Sweeper generates discrepancy alerts controlled in WAC.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL607" source="APP_WAC" target="APP_ERPS"><data key="edge_relationship_id">REL607</data><data key="edge_source_entity_id">APP_WAC</data><data key="edge_relationship_type">stores_and_controls_alerts_for</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">OIG documented WAC as storing/controlling Stuck Sweeper and eRPS development alerts and listing pending alerts for field offices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL608" source="EX_SSA_VA_PAYEE_MISUSE" target="ORG_VBA"><data key="edge_relationship_id">REL608</data><data key="edge_source_entity_id">EX_SSA_VA_PAYEE_MISUSE</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_VBA</data><data key="edge_operational_context">Current POMS directs SSA and VA fiduciary hubs to exchange information when a dual payee/fiduciary is suspected or found to misuse benefits.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL609" source="EX_SSA_VA_PAYEE_MISUSE" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL609</data><data key="edge_source_entity_id">EX_SSA_VA_PAYEE_MISUSE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">The exchange supports representative-payee misuse and improper-use investigations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL610" source="EX_SSA_VA_PAYEE_MISUSE" target="APP_ERPS"><data key="edge_relationship_id">REL610</data><data key="edge_source_entity_id">EX_SSA_VA_PAYEE_MISUSE</data><data key="edge_relationship_type">records_allegations_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">When VA reports misuse, the SSA field office records the allegation in eRPS Misuse.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL611" source="SYS_RPMRCS" target="DOM_REPPAYEE"><data key="edge_relationship_id">REL611</data><data key="edge_source_entity_id">SYS_RPMRCS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_REPPAYEE</data><data key="edge_operational_context">SSA maintains a current SORN for the Representative Payee-Misuse Restitution Control System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">SORN evidence supports a maintained record-system role, not a detailed current application topology.</data></edge><edge id="REL612" source="APP_AFES" target="TECH_ADVANCED_ANALYTICS"><data key="edge_relationship_id">REL612</data><data key="edge_source_entity_id">APP_AFES</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_ADVANCED_ANALYTICS</data><data key="edge_operational_context">AFES uses advanced data analytics to identify fraud patterns, improve data-driven fraud activity, and conduct real-time fraud-risk analysis.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL613" source="APP_AFES" target="SYS_MBR"><data key="edge_relationship_id">REL613</data><data key="edge_source_entity_id">APP_AFES</data><data key="edge_relationship_type">ingests_or_uses</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The AFES PIA identifies the Master Beneficiary Record as a primary source of records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL614" source="APP_AFES" target="SYS_SSR"><data key="edge_relationship_id">REL614</data><data key="edge_source_entity_id">APP_AFES</data><data key="edge_relationship_type">ingests_or_uses</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">The AFES PIA identifies Supplemental Security Income records as a primary source.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL615" source="APP_AFES" target="DOM_CLAIMFOLDER"><data key="edge_relationship_id">REL615</data><data key="edge_source_entity_id">APP_AFES</data><data key="edge_relationship_type">ingests_or_uses</data><data key="edge_target_entity_id">DOM_CLAIMFOLDER</data><data key="edge_operational_context">The AFES PIA identifies Claims Folders System records as a primary source.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL616" source="APP_AFES" target="EX_CMS_AFES_1094"><data key="edge_relationship_id">REL616</data><data key="edge_source_entity_id">APP_AFES</data><data key="edge_relationship_type">receives_match_response_from</data><data key="edge_target_entity_id">EX_CMS_AFES_1094</data><data key="edge_operational_context">CMA 1094 requires SSA to retain CMS response-file elements in AFES for fraud-related analytics or investigation leads.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL617" source="APP_AFES" target="ARCH_CLOUD"><data key="edge_relationship_id">REL617</data><data key="edge_source_entity_id">APP_AFES</data><data key="edge_relationship_type">uses_architecture</data><data key="edge_target_entity_id">ARCH_CLOUD</data><data key="edge_operational_context">The AFES PIA states AFES inherits technical controls from the Enterprise network and Agency Cloud Infrastructure system boundary.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Generic cloud architecture link; no provider is inferred.</data></edge><edge id="REL618" source="APP_CIRP" target="ORG_DDS"><data key="edge_relationship_id">REL618</data><data key="edge_source_entity_id">APP_CIRP</data><data key="edge_relationship_type">selects_cases_for_review_by</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">Current POMS assigns DDS management responsibility for reviewing cases selected by CIRP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL619" source="APP_CIRP" target="APP_MCS"><data key="edge_relationship_id">REL619</data><data key="edge_source_entity_id">APP_CIRP</data><data key="edge_relationship_type">reviews_transactions_from</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">CIRP PIA describes review of transactions from Title II claims processing systems.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The current inventory establishes CIRP operation; exact application-level source topology is based on the older PIA description.</data></edge><edge id="REL620" source="APP_CIRP" target="APP_MSSICS"><data key="edge_relationship_id">REL620</data><data key="edge_source_entity_id">APP_CIRP</data><data key="edge_relationship_type">reviews_transactions_from</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">CIRP PIA describes review of transactions from Title XVI claims processing systems.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The current inventory establishes CIRP operation; exact application-level source topology is based on the older PIA description.</data></edge><edge id="REL621" source="APP_CIRP" target="APP_ARIS"><data key="edge_relationship_id">REL621</data><data key="edge_source_entity_id">APP_CIRP</data><data key="edge_relationship_type">review_may_generate_referral_via</data><data key="edge_target_entity_id">APP_ARIS</data><data key="edge_operational_context">When CIRP review develops potential fraud or violations, current POMS directs employees to report through ARIS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Business workflow relation, not an asserted technical interface.</data></edge><edge id="REL622" source="APP_ARIS" target="ORG_SSA_OIG"><data key="edge_relationship_id">REL622</data><data key="edge_source_entity_id">APP_ARIS</data><data key="edge_relationship_type">submits_referrals_to</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">Current POMS requires suspected criminal/program violations to be referred to the Inspector General via ARIS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL623" source="APP_ARIS" target="APP_OIG_ICMS"><data key="edge_relationship_id">REL623</data><data key="edge_source_entity_id">APP_ARIS</data><data key="edge_relationship_type">modernization_integration_with</data><data key="edge_target_entity_id">APP_OIG_ICMS</data><data key="edge_operational_context">OIG budget testimony identifies SSA's ARIS and OIG's Case Management System as systems targeted for integration and data-sharing modernization.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">This is modernization scope, not proof of a fully automated production interface.</data></edge><edge id="REL624" source="ORG_SSA_OIG" target="APP_OIG_ICMS"><data key="edge_relationship_id">REL624</data><data key="edge_source_entity_id">ORG_SSA_OIG</data><data key="edge_relationship_type">operates</data><data key="edge_target_entity_id">APP_OIG_ICMS</data><data key="edge_operational_context">OIG testimony describes its Investigative Case Management System as a mission-critical investigative application.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL625" source="APP_OIG_ICMS" target="DB_NICMS"><data key="edge_relationship_id">REL625</data><data key="edge_source_entity_id">APP_OIG_ICMS</data><data key="edge_relationship_type">uses_or_corresponds_to_store</data><data key="edge_target_entity_id">DB_NICMS</data><data key="edge_operational_context">SSA inventory lists a National Investigative Case Management System database of fraud allegations/dispositions; OIG currently refers to its application as Investigative Case Management System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Exact product/name continuity between NICMS and current ICMS requires validation.</data></edge><edge id="REL626" source="APP_OIG_ICMS" target="EX_OIG_NIBRS"><data key="edge_relationship_id">REL626</data><data key="edge_source_entity_id">APP_OIG_ICMS</data><data key="edge_relationship_type">exports_via</data><data key="edge_target_entity_id">EX_OIG_NIBRS</data><data key="edge_operational_context">In FY2026 OIG began automated NIBRS submissions that pull data from the Investigative Case Management System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL627" source="EX_OIG_NIBRS" target="ORG_FBI"><data key="edge_relationship_id">REL627</data><data key="edge_source_entity_id">EX_OIG_NIBRS</data><data key="edge_relationship_type">sends_to</data><data key="edge_target_entity_id">ORG_FBI</data><data key="edge_operational_context">OIG testimony says the automated process submits NIBRS data using FBI protocols.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL628" source="APP_OIG_ICMS" target="ARCH_CLOUD"><data key="edge_relationship_id">REL628</data><data key="edge_source_entity_id">APP_OIG_ICMS</data><data key="edge_relationship_type">transitioning_to</data><data key="edge_target_entity_id">ARCH_CLOUD</data><data key="edge_operational_context">OIG states FY2026 architectural improvements are transitioning ICMS and support applications to a cloud-hosted environment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">No cloud provider is inferred.</data></edge><edge id="REL629" source="ORG_SSA_OIG" target="DB_NICMS"><data key="edge_relationship_id">REL629</data><data key="edge_source_entity_id">ORG_SSA_OIG</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DB_NICMS</data><data key="edge_operational_context">Current SSA inventory identifies NICMS as a database of fraud allegations and dispositions warranting further investigation.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL630" source="ORG_SSA_OIG" target="PROGRAM_CDI"><data key="edge_relationship_id">REL630</data><data key="edge_source_entity_id">ORG_SSA_OIG</data><data key="edge_relationship_type">operates</data><data key="edge_target_entity_id">PROGRAM_CDI</data><data key="edge_operational_context">SSA OIG describes CDI as a core anti-fraud initiative operated jointly with SSA and partners.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL631" source="PROGRAM_CDI" target="ORG_CDI_UNITS"><data key="edge_relationship_id">REL631</data><data key="edge_source_entity_id">PROGRAM_CDI</data><data key="edge_relationship_type">implemented_through</data><data key="edge_target_entity_id">ORG_CDI_UNITS</data><data key="edge_operational_context">CDI investigations are performed through nationwide CDI units.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL632" source="ORG_CDI_UNITS" target="ORG_SSA_OIG"><data key="edge_relationship_id">REL632</data><data key="edge_source_entity_id">ORG_CDI_UNITS</data><data key="edge_relationship_type">includes_participant</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">Each CDI unit includes an SSA OIG special agent serving as team leader.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL633" source="ORG_CDI_UNITS" target="ORG_DDS"><data key="edge_relationship_id">REL633</data><data key="edge_source_entity_id">ORG_CDI_UNITS</data><data key="edge_relationship_type">includes_participant</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">CDI units include state DDS personnel.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL634" source="PROGRAM_CDI" target="ORG_DDS"><data key="edge_relationship_id">REL634</data><data key="edge_source_entity_id">PROGRAM_CDI</data><data key="edge_relationship_type">returns_investigative_evidence_to</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">After investigation, CDI provides a detailed investigative report to DDS for use in disability determinations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL635" source="PROGRAM_CDI" target="DOM_TITLE2"><data key="edge_relationship_id">REL635</data><data key="edge_source_entity_id">PROGRAM_CDI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">CDI combats fraud in Title II disability programs.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL636" source="PROGRAM_CDI" target="DOM_TITLE16"><data key="edge_relationship_id">REL636</data><data key="edge_source_entity_id">PROGRAM_CDI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">CDI combats fraud in Title XVI disability programs.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL637" source="EX_CMS_AFES_1094" target="SYS_MBR"><data key="edge_relationship_id">REL637</data><data key="edge_source_entity_id">EX_CMS_AFES_1094</data><data key="edge_relationship_type">sends_finder_data_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA sends CMS a finder file for Title II beneficiaries age 90+ derived from the MBR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL638" source="EX_CMS_AFES_1094" target="ORG_CMS"><data key="edge_relationship_id">REL638</data><data key="edge_source_entity_id">EX_CMS_AFES_1094</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMA 1094 is an active SSA-CMS computer matching agreement.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL639" source="EX_CMS_AFES_1094" target="DATA_CMS_NCH"><data key="edge_relationship_id">REL639</data><data key="edge_source_entity_id">EX_CMS_AFES_1094</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">DATA_CMS_NCH</data><data key="edge_operational_context">CMS compares the SSA finder file against National Claims History.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL640" source="EX_CMS_AFES_1094" target="DATA_CMS_EDB"><data key="edge_relationship_id">REL640</data><data key="edge_source_entity_id">EX_CMS_AFES_1094</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">DATA_CMS_EDB</data><data key="edge_operational_context">CMS compares the SSA finder file against the Enrollment Database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL641" source="EX_CMS_AFES_1094" target="DATA_CMS_LTC_MDS"><data key="edge_relationship_id">REL641</data><data key="edge_source_entity_id">EX_CMS_AFES_1094</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">DATA_CMS_LTC_MDS</data><data key="edge_operational_context">CMS compares the SSA finder file against Long-Term Care Minimum Data Set.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL642" source="EX_CMS_AFES_1094" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">REL642</data><data key="edge_source_entity_id">EX_CMS_AFES_1094</data><data key="edge_relationship_type">routes_matched_cases_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">SSA forwards matched records to field offices for review and development before adverse action.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL643" source="EX_CMS_AFES_1094" target="ORG_SSA_OIG"><data key="edge_relationship_id">REL643</data><data key="edge_source_entity_id">EX_CMS_AFES_1094</data><data key="edge_relationship_type">suspected_fraud_referred_to</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">The agreement says SSA refers individual suspected fraud, waste, or abuse cases to OIG.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL644" source="EX_CMS_AFES_1094" target="DOM_TITLE2"><data key="edge_relationship_id">REL644</data><data key="edge_source_entity_id">EX_CMS_AFES_1094</data><data key="edge_relationship_type">supports_review_of</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">The match is used to determine continuing eligibility for Title II beneficiaries age 90 and above.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL645" source="DB_LONG_TERM_SSN_FRAUD" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL645</data><data key="edge_source_entity_id">DB_LONG_TERM_SSN_FRAUD</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">The current asset provides reporting on prevention of SSN cards issued to non-existent children.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL646" source="DB_LONG_TERM_SSN_FRAUD" target="DOM_SSNV"><data key="edge_relationship_id">REL646</data><data key="edge_source_entity_id">DB_LONG_TERM_SSN_FRAUD</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">The asset is an identity/program-integrity control focused on SSN issuance validity.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Modeled as supporting the verification/integrity domain rather than a direct verification service.</data></edge><edge id="REL647" source="APP_PUPS" target="APP_EVS"><data key="edge_relationship_id">REL647</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">uses_identity_verification_from</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">Current POMS says questionable EVS codes on PUPS alerts must be resolved before suspension/incentive-payment actions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL648" source="APP_ATS" target="ORG_SSA_OIG"><data key="edge_relationship_id">REL648</data><data key="edge_source_entity_id">APP_ATS</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_OIG</data><data key="edge_operational_context">ATS PIA identifies OIG audit/investigative staff among primary users of audit-trail data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL649" source="APP_ATS" target="TECH_ADVANCED_ANALYTICS"><data key="edge_relationship_id">REL649</data><data key="edge_source_entity_id">APP_ATS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">TECH_ADVANCED_ANALYTICS</data><data key="edge_operational_context">ATS is an automated integrated audit facility used to execute high-volume transaction review for fraud/abuse detection.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Technology relationship is functional rather than a claim that ATS uses a specific analytics product.</data></edge><edge id="REL650" source="APP_MCAS_COST" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL650</data><data key="edge_source_entity_id">APP_MCAS_COST</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current Data.gov asset is explicitly titled SUMS/MCAS - Managerial Cost Analysis System (MCAS).</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL651" source="APP_SUMS_TAS" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL651</data><data key="edge_source_entity_id">APP_SUMS_TAS</data><data key="edge_relationship_type">component_of</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current Data.gov asset is explicitly titled SUMS/MCAS Time Allocation System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL652" source="APP_MCAS_COST" target="ORG_SSA_OFPO"><data key="edge_relationship_id">REL652</data><data key="edge_source_entity_id">APP_MCAS_COST</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_OFPO</data><data key="edge_operational_context">Current metadata says MCAS/CAS is used by analysts in the Office of Financial Policy and Operations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL653" source="APP_SUMS_TAS" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL653</data><data key="edge_source_entity_id">APP_SUMS_TAS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Time Allocation System supports the SUMS/MCAS program by improving management-information quality, consistency and access.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL654" source="DATA_SUMS_TAS_CAS_HR_EXTRACT" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL654</data><data key="edge_source_entity_id">DATA_SUMS_TAS_CAS_HR_EXTRACT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current integration asset is explicitly tagged SUMS/MCAS/TAS and contains a human-resource extract.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL655" source="DATA_SUMS_TAS_CAS_HR_EXTRACT" target="DB_HR_ODS"><data key="edge_relationship_id">REL655</data><data key="edge_source_entity_id">DATA_SUMS_TAS_CAS_HR_EXTRACT</data><data key="edge_relationship_type">extracts_from</data><data key="edge_target_entity_id">DB_HR_ODS</data><data key="edge_operational_context">Current integration metadata describes the asset as a human-resource operational-data-store extract.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL656" source="APP_UMS_MCAS" target="DOM_TITLE2"><data key="edge_relationship_id">REL656</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">derives_management_information_from</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">The SUMS/MCAS PIA says the system derives information from major programmatic applications including Title II claims processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed source-system topology is historical; current SUMS/MCAS operation is independently corroborated.</data></edge><edge id="REL657" source="APP_UMS_MCAS" target="DOM_TITLE16"><data key="edge_relationship_id">REL657</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">derives_management_information_from</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">The SUMS/MCAS PIA says the system derives information from major programmatic applications including Title XVI claims processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed source-system topology is historical; current SUMS/MCAS operation is independently corroborated.</data></edge><edge id="REL658" source="APP_UMS_MCAS" target="DOM_EARNINGS"><data key="edge_relationship_id">REL658</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">derives_management_information_from</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">The SUMS/MCAS PIA says the system contains earnings information and derives data from major SSA applications.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL659" source="APP_UMS_MCAS" target="DB_HR_ODS"><data key="edge_relationship_id">REL659</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">derives_management_information_from</data><data key="edge_target_entity_id">DB_HR_ODS</data><data key="edge_operational_context">The SUMS/MCAS PIA identifies payroll and human-resource databases as sources; current HR ODS confirms a present HR operational data store.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The PIA does not specifically name the current HR ODS identifier; relationship is architectural, not a physical-interface assertion.</data></edge><edge id="REL660" source="APP_UMS_MCAS" target="ORG_DDS"><data key="edge_relationship_id">REL660</data><data key="edge_source_entity_id">APP_UMS_MCAS</data><data key="edge_relationship_type">serves</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">The SUMS/MCAS PIA says the GSS provides management information, workload control and performance-measure data for SSA and DDS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL661" source="DB_SUMS_EARNINGS_ODS" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL661</data><data key="edge_source_entity_id">DB_SUMS_EARNINGS_ODS</data><data key="edge_relationship_type">part_of_management_information_family</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current asset is explicitly named SUMS Earnings Operational Data Store.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL662" source="DB_SUMS_EARNINGS_ODS" target="DOM_EARNINGS"><data key="edge_relationship_id">REL662</data><data key="edge_source_entity_id">DB_SUMS_EARNINGS_ODS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Current asset supports information and statistical counts for SUMS earnings data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL663" source="DB_SUMS_APPEALS_ODS" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL663</data><data key="edge_source_entity_id">DB_SUMS_APPEALS_ODS</data><data key="edge_relationship_type">part_of_management_information_family</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current asset is explicitly named SSA Unified Measurement System (SUMS) Appeals ODS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL664" source="DB_SUMS_APPEALS_ODS" target="ARCH_BI"><data key="edge_relationship_id">REL664</data><data key="edge_source_entity_id">DB_SUMS_APPEALS_ODS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">ARCH_BI</data><data key="edge_operational_context">SSA says the SUMS Appeals ODS is a single source for agency appeals information used in Business Intelligence.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL665" source="DB_SUMS_T2_PE_ODS" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL665</data><data key="edge_source_entity_id">DB_SUMS_T2_PE_ODS</data><data key="edge_relationship_type">part_of_management_information_family</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current asset is explicitly a SUMS Title II post-entitlement ODS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL666" source="DB_SUMS_T16_IC_ODS" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL666</data><data key="edge_source_entity_id">DB_SUMS_T16_IC_ODS</data><data key="edge_relationship_type">part_of_management_information_family</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current asset is explicitly a SUMS Title XVI initial-claims ODS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL667" source="DB_SUMS_T16_PEODS" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL667</data><data key="edge_source_entity_id">DB_SUMS_T16_PEODS</data><data key="edge_relationship_type">part_of_management_information_family</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">Current asset is explicitly a SUMS Title XVI post-eligibility ODS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL668" source="DB_MSHARE" target="ARCH_BI"><data key="edge_relationship_id">REL668</data><data key="edge_source_entity_id">DB_MSHARE</data><data key="edge_relationship_type">provides_shared_structures_for</data><data key="edge_target_entity_id">ARCH_BI</data><data key="edge_operational_context">Current MSHARE metadata says it provides shared data structures and utilities for the BI Architecture.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL669" source="DB_BI_REPOSITORY" target="ARCH_BI"><data key="edge_relationship_id">REL669</data><data key="edge_source_entity_id">DB_BI_REPOSITORY</data><data key="edge_relationship_type">catalogs_projects_for</data><data key="edge_target_entity_id">ARCH_BI</data><data key="edge_operational_context">Current BI Repository provides information on Business Intelligence projects in SSA's Office of Systems.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL670" source="DB_SUMS_ES_DW_QUERY" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL670</data><data key="edge_source_entity_id">DB_SUMS_ES_DW_QUERY</data><data key="edge_relationship_type">provides_query_access_for</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">The current asset is explicitly the SUMS and Electronic Services Production Data Warehouse Query Instance and stores warehouse information for query access.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL671" source="DB_SUMS_ES_DW_QUERY" target="DB_ESERVICE_ODS"><data key="edge_relationship_id">REL671</data><data key="edge_source_entity_id">DB_SUMS_ES_DW_QUERY</data><data key="edge_relationship_type">provides_query_access_for</data><data key="edge_target_entity_id">DB_ESERVICE_ODS</data><data key="edge_operational_context">The query instance is explicitly named for SUMS and Electronic Services production data-warehouse query access.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The title supports a logical association; Data.gov does not publish the underlying physical database topology.</data></edge><edge id="REL672" source="DB_ESERVICE_ODS" target="DOM_E_SERVICES"><data key="edge_relationship_id">REL672</data><data key="edge_source_entity_id">DB_ESERVICE_ODS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_E_SERVICES</data><data key="edge_operational_context">Current Electronic Services ODS exists for management-information reporting on electronic-service usage.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL673" source="DB_TPPS_ODS" target="APP_TPPS"><data key="edge_relationship_id">REL673</data><data key="edge_source_entity_id">DB_TPPS_ODS</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">APP_TPPS</data><data key="edge_operational_context">Current TPPS ODS stores management information about third-party payment transactions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL674" source="DB_PEMI" target="APP_UMS_MCAS"><data key="edge_relationship_id">REL674</data><data key="edge_source_entity_id">DB_PEMI</data><data key="edge_relationship_type">aggregates_from_multiple_source_systems</data><data key="edge_target_entity_id">APP_UMS_MCAS</data><data key="edge_operational_context">PEMI contains detail data for more than 500 post-entitlement workload actions from 16 source systems and produces summarized counts; it is represented here as part of the broader enterprise MI ecosystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The source does not explicitly say PEMI is a SUMS/MCAS subsystem, so this is an ecosystem association rather than a component assertion.</data></edge><edge id="REL675" source="DB_PE_MI_DETAIL" target="DB_PEMI"><data key="edge_relationship_id">REL675</data><data key="edge_source_entity_id">DB_PE_MI_DETAIL</data><data key="edge_relationship_type">supports_same_post_entitlement_mi_domain_as</data><data key="edge_target_entity_id">DB_PEMI</data><data key="edge_operational_context">Current PE Detail Database contains detailed and aggregate receipt, pending and clearance data for Title II and XVI post-entitlement transactions; PEMI provides detail/summarized PE workload MI.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Logical-domain relationship only; no physical feed is asserted.</data></edge><edge id="REL676" source="DB_PE_MI_HISTORY" target="DB_PEMI"><data key="edge_relationship_id">REL676</data><data key="edge_source_entity_id">DB_PE_MI_HISTORY</data><data key="edge_relationship_type">supports_same_post_entitlement_mi_domain_as</data><data key="edge_target_entity_id">DB_PEMI</data><data key="edge_operational_context">The historical PE MI database preserves historical receipt, pending and clearance data for the same post-entitlement management-information domain.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Logical-domain relationship only; no physical feed is asserted.</data></edge><edge id="REL677" source="APP_SOLQI" target="EX_SOLQ"><data key="edge_relationship_id">REL677</data><data key="edge_source_entity_id">APP_SOLQI</data><data key="edge_relationship_type">internet_variant_of</data><data key="edge_target_entity_id">EX_SOLQ</data><data key="edge_operational_context">SSA describes SOLQ-I as the Internet application providing authorized states real-time SOLQ-style verification and benefit retrieval.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL678" source="EX_SVES" target="TECH_FTMS"><data key="edge_relationship_id">REL678</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">uses_transfer_mechanism</data><data key="edge_target_entity_id">TECH_FTMS</data><data key="edge_operational_context">The current-linked SVES/SOLQ manual states SVES uses SSA's File Transfer Management System to receive and transmit batch files.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL679" source="EX_SVES" target="EX_BENDEX"><data key="edge_relationship_id">REL679</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">routes_non_native_requests_to</data><data key="edge_target_entity_id">EX_BENDEX</data><data key="edge_operational_context">SVES can pass verified non-native requests to BENDEX to trigger output records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL680" source="EX_SVES" target="EX_BEER"><data key="edge_relationship_id">REL680</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">routes_non_native_requests_to</data><data key="edge_target_entity_id">EX_BEER</data><data key="edge_operational_context">SVES can trigger Beneficiary Earnings Exchange Record output as part of non-native processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL681" source="EX_SVES" target="EX_SDX"><data key="edge_relationship_id">REL681</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">routes_non_native_requests_to</data><data key="edge_target_entity_id">EX_SDX</data><data key="edge_operational_context">SVES can route non-native requests to State Data Exchange processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL682" source="EX_SVES" target="EX_QQ"><data key="edge_relationship_id">REL682</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">routes_non_native_requests_to</data><data key="edge_target_entity_id">EX_QQ</data><data key="edge_operational_context">SVES supports non-native 40 Qualifying Quarters requests.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL683" source="EX_SVES" target="APP_PUPS"><data key="edge_relationship_id">REL683</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">routes_non_native_requests_to</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">SVES supports prisoner-record queries as a non-native request path.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The manual documents prisoner-query routing; it does not publish every internal handoff detail.</data></edge><edge id="REL684" source="EX_SVES" target="DOM_CITIZENSHIP"><data key="edge_relationship_id">REL684</data><data key="edge_source_entity_id">EX_SVES</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_CITIZENSHIP</data><data key="edge_operational_context">SVES provides citizenship-related data as part of its standard Type I verification response.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL685" source="DATA_BENDATA" target="EX_BENDEX"><data key="edge_relationship_id">REL685</data><data key="edge_source_entity_id">DATA_BENDATA</data><data key="edge_relationship_type">input_file_for</data><data key="edge_target_entity_id">EX_BENDEX</data><data key="edge_operational_context">SSA defines BENDATA as the state file sent to SSA to request BENDEX data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL686" source="DATA_BENDATA" target="ORG_STATES"><data key="edge_relationship_id">REL686</data><data key="edge_source_entity_id">DATA_BENDATA</data><data key="edge_relationship_type">sent_by</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">SSA defines BENDATA as a file sent by a state to SSA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL687" source="COMP_STC" target="ORG_STATES"><data key="edge_relationship_id">REL687</data><data key="edge_source_entity_id">COMP_STC</data><data key="edge_relationship_type">transfers_data_for</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">State agencies unable to receive SSA data directly use an STC to receive requested data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL688" source="EX_IBIQ" target="PLAT_ICON_HUB"><data key="edge_relationship_id">REL688</data><data key="edge_source_entity_id">EX_IBIQ</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">PLAT_ICON_HUB</data><data key="edge_operational_context">SSA's state agreement model says IBIQ accesses online state wage and unemployment records through ICON.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL689" source="EX_IBIQ" target="ORG_STATES"><data key="edge_relationship_id">REL689</data><data key="edge_source_entity_id">EX_IBIQ</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">IBIQ provides SSA with state quarterly wage and weekly unemployment-insurance benefit data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL690" source="EX_IBIQ" target="DOM_EARNINGS"><data key="edge_relationship_id">REL690</data><data key="edge_source_entity_id">EX_IBIQ</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Current SSI policy treats IBIQ query results as wage evidence.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL691" source="EX_IBIQ" target="DOM_TITLE16"><data key="edge_relationship_id">REL691</data><data key="edge_source_entity_id">EX_IBIQ</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Current SSI policy uses IBIQ wage and unemployment-benefit information in SSI eligibility/payment development.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL692" source="EX_UIQ" target="PLAT_ICON_HUB"><data key="edge_relationship_id">REL692</data><data key="edge_source_entity_id">EX_UIQ</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">PLAT_ICON_HUB</data><data key="edge_operational_context">Current UIQ inventory says state UI agencies receive real-time SSA data via the Department of Labor ICON Hub.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL693" source="PLAT_ICON_HUB" target="ORG_DOL"><data key="edge_relationship_id">REL693</data><data key="edge_source_entity_id">PLAT_ICON_HUB</data><data key="edge_relationship_type">associated_with</data><data key="edge_target_entity_id">ORG_DOL</data><data key="edge_operational_context">SSA's current UIQ inventory identifies the platform as the Department of Labor ICON Hub.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL694" source="EX_SASRO" target="ORG_STATES"><data key="edge_relationship_id">REL694</data><data key="edge_source_entity_id">EX_SASRO</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_STATES</data><data key="edge_operational_context">SASRO provides SSA employees online access to state-agency records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL695" source="EX_SASRO" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL695</data><data key="edge_source_entity_id">EX_SASRO</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">SSA states SASRO facilitates assignment of Social Security numbers.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL696" source="EX_SASRO" target="DOM_TITLE2"><data key="edge_relationship_id">REL696</data><data key="edge_source_entity_id">EX_SASRO</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">SSA states SASRO helps verify eligibility and establish Title II payment amounts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL697" source="EX_SASRO" target="DOM_TITLE16"><data key="edge_relationship_id">REL697</data><data key="edge_source_entity_id">EX_SASRO</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">SSA states SASRO helps verify eligibility and establish Title XVI payment amounts.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL698" source="EX_SASRO" target="DOM_EARNINGS"><data key="edge_relationship_id">REL698</data><data key="edge_source_entity_id">EX_SASRO</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">Current SSI wage policy identifies SASRO as a third-party wage evidence source.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL699" source="EX_SCHIPI" target="EX_SVES"><data key="edge_relationship_id">REL699</data><data key="edge_source_entity_id">EX_SCHIPI</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">EX_SVES</data><data key="edge_operational_context">Current SCHIP inventory states records come into SSA through SVES.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL700" source="EX_SCHIPI" target="APP_EVS"><data key="edge_relationship_id">REL700</data><data key="edge_source_entity_id">EX_SCHIPI</data><data key="edge_relationship_type">uses_verification_backend</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">Current SCHIP inventory states SVES records use EVS processing code 322.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL701" source="EX_SCHIPI" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL701</data><data key="edge_source_entity_id">EX_SCHIPI</data><data key="edge_relationship_type">verifies_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">EVS matches SCHIP applicant names and SSNs against Numident and obtains citizenship data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL702" source="APP_GSO" target="ORG_STATE_BVS"><data key="edge_relationship_id">REL702</data><data key="edge_source_entity_id">APP_GSO</data><data key="edge_relationship_type">receives_reporting_from</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">Current GSO services include birth and death reporting for state bureaus of vital statistics.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL703" source="APP_GSO" target="APP_PUPS"><data key="edge_relationship_id">REL703</data><data key="edge_source_entity_id">APP_GSO</data><data key="edge_relationship_type">supports_reporting_for</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Current GSO includes prison reporting for state and local law enforcement; PUPS is SSA's prisoner-processing system.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Business-function relationship; SSA does not publish the exact GSO-to-PUPS technical interface on this page.</data></edge><edge id="REL704" source="APP_GSO" target="EX_TDEX"><data key="edge_relationship_id">REL704</data><data key="edge_source_entity_id">APP_GSO</data><data key="edge_relationship_type">supports_exchange</data><data key="edge_target_entity_id">EX_TDEX</data><data key="edge_operational_context">Current GSO provides foreign death data exchange for totalization partner countries; TDEX is the cataloged foreign-death exchange process.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL705" source="APP_GSO" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">REL705</data><data key="edge_source_entity_id">APP_GSO</data><data key="edge_relationship_type">planned_authentication_via</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">SSA says GSO will soon require Login.gov or ID.me sign-in.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Planned authentication change, not yet represented as completed cutover.</data></edge><edge id="REL706" source="APP_GSO" target="SVC_IDME"><data key="edge_relationship_id">REL706</data><data key="edge_source_entity_id">APP_GSO</data><data key="edge_relationship_type">planned_authentication_via</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">SSA says GSO will soon require Login.gov or ID.me sign-in.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Planned authentication change, not yet represented as completed cutover.</data></edge><edge id="REL707" source="EX_TDEX" target="ORG_TOTALIZATION_PARTNERS"><data key="edge_relationship_id">REL707</data><data key="edge_source_entity_id">EX_TDEX</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_TOTALIZATION_PARTNERS</data><data key="edge_operational_context">TDEX exchanges death information with foreign totalization partners.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL708" source="EX_TDEX" target="DOM_DEATH"><data key="edge_relationship_id">REL708</data><data key="edge_source_entity_id">EX_TDEX</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_DEATH</data><data key="edge_operational_context">TDEX finder/response processing identifies deaths of U.S. beneficiaries abroad.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL709" source="EX_TDEX" target="DOM_TITLE2"><data key="edge_relationship_id">REL709</data><data key="edge_source_entity_id">EX_TDEX</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">TDEX death information concerns Social Security beneficiaries residing abroad.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL710" source="EX_VA_CMA1008" target="ORG_VBA"><data key="edge_relationship_id">REL710</data><data key="edge_source_entity_id">EX_VA_CMA1008</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">ORG_VBA</data><data key="edge_operational_context">VBA provides electronic compensation and pension payment files to SSA.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL711" source="EX_VA_CMA1008" target="SYS_SSR"><data key="edge_relationship_id">REL711</data><data key="edge_source_entity_id">EX_VA_CMA1008</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">After identity matching, SSA updates the SSR to reflect VA compensation and pension payment data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL712" source="EX_VA_CMA1008" target="DB_MDB"><data key="edge_relationship_id">REL712</data><data key="edge_source_entity_id">EX_VA_CMA1008</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">DB_MDB</data><data key="edge_operational_context">SSA matches VA compensation and pension payment data against the Medicare Database File for Extra Help verification/outreach.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL713" source="EX_VA_CMA1008" target="DOM_TITLE16"><data key="edge_relationship_id">REL713</data><data key="edge_source_entity_id">EX_VA_CMA1008</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">SSA uses VA payment data to determine SSI eligibility or payment amount.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL714" source="EX_VA_CMA1008" target="DOM_SVB"><data key="edge_relationship_id">REL714</data><data key="edge_source_entity_id">EX_VA_CMA1008</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_SVB</data><data key="edge_operational_context">SSA uses VA payment data to determine Special Veterans Benefits eligibility or payment amount.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL715" source="EX_VA_CMA1008" target="DOM_MEDICARE"><data key="edge_relationship_id">REL715</data><data key="edge_source_entity_id">EX_VA_CMA1008</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">SSA uses the match for Medicare Savings Program and Extra Help outreach and verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL716" source="DB_MDB" target="DOM_MEDICARE"><data key="edge_relationship_id">REL716</data><data key="edge_source_entity_id">DB_MDB</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">CMA 1008 identifies MDB as SSA's Medicare database used for Extra Help eligibility verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL717" source="EX_CMS_ACA_1097" target="ORG_CMS"><data key="edge_relationship_id">REL717</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMA 1097 is an active SSA-CMS computer matching program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL718" source="EX_CMS_ACA_1097" target="DATA_CMS_HIX"><data key="edge_relationship_id">REL718</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">receives_requests_from</data><data key="edge_target_entity_id">DATA_CMS_HIX</data><data key="edge_operational_context">CMS HIX is the CMS system of records supporting the matching program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL719" source="EX_CMS_ACA_1097" target="PLAT_CMS_FDSH"><data key="edge_relationship_id">REL719</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">PLAT_CMS_FDSH</data><data key="edge_operational_context">The CMA cost-benefit analysis says trusted data source information is accessed through the CMS Hub platform.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL720" source="ORG_STATE_AE" target="PLAT_CMS_FDSH"><data key="edge_relationship_id">REL720</data><data key="edge_source_entity_id">ORG_STATE_AE</data><data key="edge_relationship_type">accesses_via</data><data key="edge_target_entity_id">PLAT_CMS_FDSH</data><data key="edge_operational_context">State Affordable Insurance Exchanges access trusted data-source information through the Hub rather than directly from source agencies.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL721" source="EX_CMS_ACA_1097" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL721</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">responds_from</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">SSA uses the Enumeration System/Numident to provide identity, SSN and citizenship-attestation confirmation.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL722" source="EX_CMS_ACA_1097" target="APP_PUPS"><data key="edge_relationship_id">REL722</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">responds_from</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">SSA uses PUPS to provide incarceration information relevant to CMS requests.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL723" source="EX_CMS_ACA_1097" target="SYS_MBR"><data key="edge_relationship_id">REL723</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">responds_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA uses MBR data for Title II income and disability-related verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL724" source="EX_CMS_ACA_1097" target="SYS_MEF"><data key="edge_relationship_id">REL724</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">responds_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">SSA uses MEF data in the ACA matching program, including work-quarter-related verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL725" source="EX_CMS_ACA_1097" target="DOM_SSNV"><data key="edge_relationship_id">REL725</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_SSNV</data><data key="edge_operational_context">Responses include SSN verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL726" source="EX_CMS_ACA_1097" target="DOM_CITIZENSHIP"><data key="edge_relationship_id">REL726</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_CITIZENSHIP</data><data key="edge_operational_context">Responses can include confirmation of citizenship attestations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL727" source="EX_CMS_ACA_1097" target="DOM_TITLE2"><data key="edge_relationship_id">REL727</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Responses can include annual and monthly Title II income information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL728" source="EX_CMS_ACA_1097" target="DOM_DEATH"><data key="edge_relationship_id">REL728</data><data key="edge_source_entity_id">EX_CMS_ACA_1097</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DOM_DEATH</data><data key="edge_operational_context">Responses can include a death indicator.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL729" source="EX_CMS_NURSING_1076" target="ORG_CMS"><data key="edge_relationship_id">REL729</data><data key="edge_source_entity_id">EX_CMS_NURSING_1076</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMA 1076 is an active SSA-CMS matching program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL730" source="EX_CMS_NURSING_1076" target="DATA_CMS_LTC_MDS"><data key="edge_relationship_id">REL730</data><data key="edge_source_entity_id">EX_CMS_NURSING_1076</data><data key="edge_relationship_type">receives_from</data><data key="edge_target_entity_id">DATA_CMS_LTC_MDS</data><data key="edge_operational_context">The Title XIX facility match uses CMS facility/MDS admission and discharge information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL731" source="EX_CMS_NURSING_1076" target="APP_MSSICS"><data key="edge_relationship_id">REL731</data><data key="edge_source_entity_id">EX_CMS_NURSING_1076</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">MSSICS generates a D8 alert and diary when CMS facility-match conditions are met.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL732" source="EX_CMS_NURSING_1076" target="DOM_TITLE16"><data key="edge_relationship_id">REL732</data><data key="edge_source_entity_id">EX_CMS_NURSING_1076</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">The match identifies institutionalization changes that can affect SSI eligibility and payment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL733" source="INIT_ITOM" target="ARCH_HYBRID_CLOUD"><data key="edge_relationship_id">REL733</data><data key="edge_source_entity_id">INIT_ITOM</data><data key="edge_relationship_type">manages_capabilities_in</data><data key="edge_target_entity_id">ARCH_HYBRID_CLOUD</data><data key="edge_operational_context">SSA says ITOM technologies and practices are being replaced to improve management of IT capabilities in a hybrid cloud ecosystem.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL734" source="ARCH_HYBRID_CLOUD" target="ARCH_CLOUD"><data key="edge_relationship_id">REL734</data><data key="edge_source_entity_id">ARCH_HYBRID_CLOUD</data><data key="edge_relationship_type">is_specific_form_of</data><data key="edge_target_entity_id">ARCH_CLOUD</data><data key="edge_operational_context">SSA's current hybrid-cloud ecosystem is a cloud-based architecture pattern within the broader Atlas cloud architecture category.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Taxonomic relationship; it does not assert a complete physical topology.</data></edge><edge id="REL735" source="INIT_MAINFRAME_RESILIENCE" target="TECH_MAINFRAME"><data key="edge_relationship_id">REL735</data><data key="edge_source_entity_id">INIT_MAINFRAME_RESILIENCE</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">TECH_MAINFRAME</data><data key="edge_operational_context">SSA's Mainframe Business Resilience initiative automates movement of mainframe workloads between data centers.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL736" source="PLAT_MDE" target="ORG_AWS"><data key="edge_relationship_id">REL736</data><data key="edge_source_entity_id">PLAT_MDE</data><data key="edge_relationship_type">historically_hosted_on</data><data key="edge_target_entity_id">ORG_AWS</data><data key="edge_operational_context">SSA testified in 2016 that it had established its Modern Development Environment in the Amazon Web Services cloud.</data><data key="edge_observed_as_of">2016-05-26</data><data key="edge_confidence">4</data><data key="edge_notes">Historical architecture relationship; no claim of unchanged 2026 hosting.</data></edge><edge id="REL737" source="ORG_AWS" target="SVC_AMAZON_CONNECT"><data key="edge_relationship_id">REL737</data><data key="edge_source_entity_id">ORG_AWS</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_operational_context">Amazon Connect is an AWS cloud contact-center service used in SSA's documented task order.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL738" source="SVC_AMAZON_CONNECT" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL738</data><data key="edge_source_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA's FY2024 AFR says the National 800 Number transitioned to AWS/Amazon Connect in August 2024; GAO documented continuing toll-free procurement through the service in 2025.</data><data key="edge_observed_as_of">2024-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL739" source="PLAT_NGTP" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL739</data><data key="edge_source_entity_id">PLAT_NGTP</data><data key="edge_relationship_type">historically_supported</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA transitioned the National 800 Number onto NGTP in November 2023 before moving it off NGTP in August 2024.</data><data key="edge_observed_as_of">2025-04-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL740" source="SVC_AMAZON_CONNECT" target="PLAT_NGTP"><data key="edge_relationship_id">REL740</data><data key="edge_source_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_relationship_type">replaced_for_n8nn</data><data key="edge_target_entity_id">PLAT_NGTP</data><data key="edge_operational_context">SSA transitioned the National 800 Number away from NGTP to AWS/Amazon Connect in August 2024.</data><data key="edge_observed_as_of">2024-09-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL741" source="CON_CLOUD_BPA_FOUR_POINTS" target="ORG_FOUR_POINTS"><data key="edge_relationship_id">REL741</data><data key="edge_source_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_FOUR_POINTS</data><data key="edge_operational_context">SSA established BPA 28321321A00040003 with Four Points on December 22, 2020.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL742" source="CON_CLOUD_BPA_FOUR_POINTS" target="ORG_AWS"><data key="edge_relationship_id">REL742</data><data key="edge_source_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">ORG_AWS</data><data key="edge_operational_context">GAO says the BPA provides SSA access to commercial cloud service providers including AWS.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL743" source="CON_AWS_CONNECT_2024" target="ORG_FOUR_POINTS"><data key="edge_relationship_id">REL743</data><data key="edge_source_entity_id">CON_AWS_CONNECT_2024</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_FOUR_POINTS</data><data key="edge_operational_context">SSA issued task order 28321324FA0010214 to Four Points on August 1, 2024.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL744" source="CON_AWS_CONNECT_2024" target="CON_CLOUD_BPA_FOUR_POINTS"><data key="edge_relationship_id">REL744</data><data key="edge_source_entity_id">CON_AWS_CONNECT_2024</data><data key="edge_relationship_type">under_bpa</data><data key="edge_target_entity_id">CON_CLOUD_BPA_FOUR_POINTS</data><data key="edge_operational_context">The Amazon Connect CCaaS task order was issued under SSA's Four Points cloud-services BPA.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL745" source="CON_AWS_CONNECT_2024" target="SVC_AMAZON_CONNECT"><data key="edge_relationship_id">REL745</data><data key="edge_source_entity_id">CON_AWS_CONNECT_2024</data><data key="edge_relationship_type">procures</data><data key="edge_target_entity_id">SVC_AMAZON_CONNECT</data><data key="edge_operational_context">The task order's requirement is Contact Center as a Service, Amazon Web Services Connect.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL746" source="CON_GRAND_SLLAM" target="ORG_METTEL"><data key="edge_relationship_id">REL746</data><data key="edge_source_entity_id">CON_GRAND_SLLAM</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_METTEL</data><data key="edge_operational_context">GAO identifies Manhattan Telecommunications Corporation/MetTel as the Grand SLLAM task-order contractor.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL747" source="CON_GRAND_SLLAM" target="VEH_GSA_EIS"><data key="edge_relationship_id">REL747</data><data key="edge_source_entity_id">CON_GRAND_SLLAM</data><data key="edge_relationship_type">uses_vehicle</data><data key="edge_target_entity_id">VEH_GSA_EIS</data><data key="edge_operational_context">Grand SLLAM was issued under GSA Enterprise Infrastructure Solutions.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL748" source="CON_GRAND_SLLAM" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL748</data><data key="edge_source_entity_id">CON_GRAND_SLLAM</data><data key="edge_relationship_type">provides_telecommunications_for</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">Grand SLLAM includes toll-free telecommunications used by SSA; the contract is nonexclusive.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL749" source="CON_GRAND_SLLAM" target="CON_AWS_CONNECT_2024"><data key="edge_relationship_id">REL749</data><data key="edge_source_entity_id">CON_GRAND_SLLAM</data><data key="edge_relationship_type">overlapped_service_scope_with</data><data key="edge_target_entity_id">CON_AWS_CONNECT_2024</data><data key="edge_operational_context">GAO documented that SSA could obtain toll-free capability through both MetTel's nonexclusive Grand SLLAM order and the Four Points Amazon Connect order during the 2025 period.</data><data key="edge_observed_as_of">2025-06-30</data><data key="edge_confidence">5</data><data key="edge_notes">Overlap is documented for the GAO protest period; no October 2026 continuation is inferred.</data></edge><edge id="REL750" source="CON_NGTP_VERIZON" target="ORG_VERIZON"><data key="edge_relationship_id">REL750</data><data key="edge_source_entity_id">CON_NGTP_VERIZON</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_VERIZON</data><data key="edge_operational_context">SSA OIG identifies Verizon Business Network Services as the NGTP contractor.</data><data key="edge_observed_as_of">2025-04-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL751" source="CON_NGTP_VERIZON" target="PLAT_NGTP"><data key="edge_relationship_id">REL751</data><data key="edge_source_entity_id">CON_NGTP_VERIZON</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PLAT_NGTP</data><data key="edge_operational_context">The Verizon contract supported design, implementation, testing, transition, training, operations and maintenance of NGTP.</data><data key="edge_observed_as_of">2025-04-23</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL752" source="FAC_NSC" target="FAC_NCC"><data key="edge_relationship_id">REL752</data><data key="edge_source_entity_id">FAC_NSC</data><data key="edge_relationship_type">was_built_to_replace</data><data key="edge_target_entity_id">FAC_NCC</data><data key="edge_operational_context">SSA/OIG describe the National Support Center as the replacement for the aging National Computer Center.</data><data key="edge_observed_as_of">2016-07-14</data><data key="edge_confidence">4</data><data key="edge_notes">Historical modernization relationship; precise NCC retirement date not asserted.</data></edge><edge id="REL753" source="FAC_SSC" target="FAC_NSC"><data key="edge_relationship_id">REL753</data><data key="edge_source_entity_id">FAC_SSC</data><data key="edge_relationship_type">historically_provided_redundancy_for</data><data key="edge_target_entity_id">FAC_NSC</data><data key="edge_operational_context">OIG stated in 2016 that the Second Support Center provided data-computing redundancy while SSA moved core systems to the National Support Center.</data><data key="edge_observed_as_of">2016-07-14</data><data key="edge_confidence">4</data><data key="edge_notes">Both facilities are independently corroborated as current/current-occupancy, but the 2016 redundancy topology is not assumed unchanged.</data></edge><edge id="REL754" source="FAC_NSC" target="DOM_EARNINGS"><data key="edge_relationship_id">REL754</data><data key="edge_source_entity_id">FAC_NSC</data><data key="edge_relationship_type">stores_or_supports</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">SSA says the NSC maintains wage information on almost every American.</data><data key="edge_observed_as_of">2014-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">High-level facility/data-domain relationship; not a claim that the NSC is the authoritative earnings database.</data></edge><edge id="REL755" source="APP_ASC" target="APP_WLM"><data key="edge_relationship_id">REL755</data><data key="edge_source_entity_id">APP_ASC</data><data key="edge_relationship_type">sends_appointments_to</data><data key="edge_target_entity_id">APP_WLM</data><data key="edge_operational_context">Current ASC rollout instructions state that ASC establishes initial-claim telephone appointments and sends them to WLM for distribution.</data><data key="edge_observed_as_of">2026-08-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL756" source="APP_WLM" target="APP_TED"><data key="edge_relationship_id">REL756</data><data key="edge_source_entity_id">APP_WLM</data><data key="edge_relationship_type">used_within</data><data key="edge_target_entity_id">APP_TED</data><data key="edge_operational_context">Current WLM rollout instructions say technicians use WLM in the Technician Experience Dashboard.</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL757" source="APP_TED" target="APP_ASC"><data key="edge_relationship_id">REL757</data><data key="edge_source_entity_id">APP_TED</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">APP_ASC</data><data key="edge_operational_context">Current ASC instructions direct technicians to access ASC from TED after customer verification or through TED external links.</data><data key="edge_observed_as_of">2026-08-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL758" source="APP_ASC" target="APP_TED"><data key="edge_relationship_id">REL758</data><data key="edge_source_entity_id">APP_ASC</data><data key="edge_relationship_type">appointment_history_visible_in</data><data key="edge_target_entity_id">APP_TED</data><data key="edge_operational_context">Past and future ASC appointments are displayed in TED Customer History.</data><data key="edge_observed_as_of">2026-08-31</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL759" source="APP_ASC" target="DOM_TITLE2"><data key="edge_relationship_id">REL759</data><data key="edge_source_entity_id">APP_ASC</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Current protective-filing and appointment procedures use ASC in initial-claim workflows that include Title II claims.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL760" source="APP_ASC" target="DOM_TITLE16"><data key="edge_relationship_id">REL760</data><data key="edge_source_entity_id">APP_ASC</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Current SSI protective-filing policy identifies ASC as part of oral-inquiry/claim scheduling workflows.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL761" source="APP_WLM" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">REL761</data><data key="edge_source_entity_id">APP_WLM</data><data key="edge_relationship_type">distributes_work_to</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">WLM rollout uses a national queue so eligible initial-claim telephone appointments can be taken by available technicians beyond the claimant's local jurisdiction.</data><data key="edge_observed_as_of">2026-08-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL762" source="APP_TED" target="APP_UPLOAD_DOCUMENTS"><data key="edge_relationship_id">REL762</data><data key="edge_source_entity_id">APP_TED</data><data key="edge_relationship_type">initiates_tasks_for</data><data key="edge_target_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_operational_context">SSA's Upload Documents rollout describes the original technician-initiated workflow as beginning with a TED task.</data><data key="edge_observed_as_of">2025-03-28</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL763" source="APP_UPLOAD_DOCUMENTS" target="APP_MYSSA"><data key="edge_relationship_id">REL763</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">accessible_via</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Eligible individual representative payees submit forms and evidence through Upload Documents in my Social Security.</data><data key="edge_observed_as_of">2025-12-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL764" source="APP_UPLOAD_DOCUMENTS" target="APP_WORKTRACK"><data key="edge_relationship_id">REL764</data><data key="edge_source_entity_id">APP_UPLOAD_DOCUMENTS</data><data key="edge_relationship_type">routes_documents_to</data><data key="edge_target_entity_id">APP_WORKTRACK</data><data key="edge_operational_context">SSA states documents submitted through Upload Documents route to the servicing field office in WorkTrack.</data><data key="edge_observed_as_of">2025-12-11</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL765" source="APP_WORKTRACK" target="APP_EVIEW"><data key="edge_relationship_id">REL765</data><data key="edge_source_entity_id">APP_WORKTRACK</data><data key="edge_relationship_type">manually_transfers_documents_to</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Current instructions require technicians/managers to review WorkTrack documents and manually transfer appropriate documents to eView.</data><data key="edge_observed_as_of">2026-02-25</data><data key="edge_confidence">5</data><data key="edge_notes">Explicitly modeled as manual workflow, not an automated system interface.</data></edge><edge id="REL766" source="APP_WORKTRACK" target="APP_EP"><data key="edge_relationship_id">REL766</data><data key="edge_source_entity_id">APP_WORKTRACK</data><data key="edge_relationship_type">used_with</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Current protective-filing policy directs technicians to review WorkTrack and Evidence Portal among systems used to locate protective-filing evidence.</data><data key="edge_observed_as_of">2026-04-27</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow co-use only; no technical interface is asserted.</data></edge><edge id="REL767" source="PLAT_MODERN_DATA_LAYER" target="TECH_MICROSERVICES"><data key="edge_relationship_id">REL767</data><data key="edge_source_entity_id">PLAT_MODERN_DATA_LAYER</data><data key="edge_relationship_type">uses_modernization_approach</data><data key="edge_target_entity_id">TECH_MICROSERVICES</data><data key="edge_operational_context">FY2026 modernization text cites microservices as a technology for centralized customer-oriented data products and replacement of outdated systems.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Design-intent relationship; production implementation is not independently verified.</data></edge><edge id="REL768" source="PLAT_MODERN_DATA_LAYER" target="TECH_API"><data key="edge_relationship_id">REL768</data><data key="edge_source_entity_id">PLAT_MODERN_DATA_LAYER</data><data key="edge_relationship_type">uses_modernization_approach</data><data key="edge_target_entity_id">TECH_API</data><data key="edge_operational_context">FY2026 modernization text cites APIs as a technology for centralized customer-oriented data products and simplified data integration.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Design-intent relationship; no API product or protocol is inferred.</data></edge><edge id="REL769" source="PLAT_MODERN_DATA_LAYER" target="ARCH_CLOUD"><data key="edge_relationship_id">REL769</data><data key="edge_source_entity_id">PLAT_MODERN_DATA_LAYER</data><data key="edge_relationship_type">supports_migration_toward</data><data key="edge_target_entity_id">ARCH_CLOUD</data><data key="edge_operational_context">SSA states the modernization approach is intended to help migrate data and applications to cloud environments.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Budgeted design intent, not evidence of a completed MDL cloud deployment.</data></edge><edge id="REL770" source="APP_ECC" target="ARCH_CLOUD"><data key="edge_relationship_id">REL770</data><data key="edge_source_entity_id">APP_ECC</data><data key="edge_relationship_type">uses_architecture</data><data key="edge_target_entity_id">ARCH_CLOUD</data><data key="edge_operational_context">FY2027 budget describes Enterprise Contact Center/IVR as SSA's cloud-based contact-center solution.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL771" source="PROJ_ENTERPRISE_CRM" target="APP_TED"><data key="edge_relationship_id">REL771</data><data key="edge_source_entity_id">PROJ_ENTERPRISE_CRM</data><data key="edge_relationship_type">planned_integration_with</data><data key="edge_target_entity_id">APP_TED</data><data key="edge_operational_context">FY2027 budget states the enterprise CRM is planned to integrate with the Technician Experience Dashboard.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL772" source="PROJ_ENTERPRISE_CRM" target="APP_ECC"><data key="edge_relationship_id">REL772</data><data key="edge_source_entity_id">PROJ_ENTERPRISE_CRM</data><data key="edge_relationship_type">planned_integration_with</data><data key="edge_target_entity_id">APP_ECC</data><data key="edge_operational_context">FY2027 budget states the enterprise CRM is planned to integrate with the Enterprise Contact Center.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL773" source="PROJ_ENTERPRISE_CRM" target="APP_WLM"><data key="edge_relationship_id">REL773</data><data key="edge_source_entity_id">PROJ_ENTERPRISE_CRM</data><data key="edge_relationship_type">planned_integration_with</data><data key="edge_target_entity_id">APP_WLM</data><data key="edge_operational_context">FY2027 budget states the enterprise CRM is planned to integrate with workload-management capabilities.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL774" source="PROJ_MYSSA_MOBILE" target="APP_MYSSA"><data key="edge_relationship_id">REL774</data><data key="edge_source_entity_id">PROJ_MYSSA_MOBILE</data><data key="edge_relationship_type">modernizes</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">FY2027 budget identifies my Social Security modernization and mobile-app capabilities as a funded initiative.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL775" source="PROJ_SSN_CARD_MODERNIZATION" target="DOM_ENUMERATION"><data key="edge_relationship_id">REL775</data><data key="edge_source_entity_id">PROJ_SSN_CARD_MODERNIZATION</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_ENUMERATION</data><data key="edge_operational_context">FY2027 SSN Card Services Modernization concerns digital SSN card-related services and therefore directly supports the enumeration/SSN service domain.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL776" source="PROJ_WORK_CDR" target="TECH_API"><data key="edge_relationship_id">REL776</data><data key="edge_source_entity_id">PROJ_WORK_CDR</data><data key="edge_relationship_type">uses_modernization_approach</data><data key="edge_target_entity_id">TECH_API</data><data key="edge_operational_context">FY2027 budget describes a modern Work CDR application integrated with downstream systems and management information using modern application approaches.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The budget does not publish a specific API inventory, gateway or protocol.</data></edge><edge id="REL777" source="APP_CCE" target="TECH_API"><data key="edge_relationship_id">REL777</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">uses_modernization_approach</data><data key="edge_target_entity_id">TECH_API</data><data key="edge_operational_context">FY2027 budget describes continuing CCE modernization using modern cloud-native applications and APIs as legacy COBOL components are replaced.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL778" source="CON_OPTS_ACCENTURE_BPA" target="ORG_ACCENTURE_FEDERAL"><data key="edge_relationship_id">REL778</data><data key="edge_source_entity_id">CON_OPTS_ACCENTURE_BPA</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_ACCENTURE_FEDERAL</data><data key="edge_operational_context">USAspending identifies Accenture Federal Services LLC as recipient of BPA 28321321A00040017.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL779" source="CON_OPTS_ACCENTURE_BPA" target="APP_OPTS"><data key="edge_relationship_id">REL779</data><data key="edge_source_entity_id">CON_OPTS_ACCENTURE_BPA</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_OPTS</data><data key="edge_operational_context">The BPA description states it provides software and support services for the Online Processing and Tracking System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL780" source="CON_OPTS_ACCENTURE_BPA" target="TECH_SALESFORCE"><data key="edge_relationship_id">REL780</data><data key="edge_source_entity_id">CON_OPTS_ACCENTURE_BPA</data><data key="edge_relationship_type">procures</data><data key="edge_target_entity_id">TECH_SALESFORCE</data><data key="edge_operational_context">USAspending identifies the major program as Salesforce OPTS license renewal and services.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL781" source="APP_OPTS" target="TECH_SALESFORCE"><data key="edge_relationship_id">REL781</data><data key="edge_source_entity_id">APP_OPTS</data><data key="edge_relationship_type">uses_platform</data><data key="edge_target_entity_id">TECH_SALESFORCE</data><data key="edge_operational_context">The active BPA's major-program description explicitly ties Salesforce license renewal and services to OPTS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL782" source="CON_PEGA_2026" target="ORG_IMMIXTECH"><data key="edge_relationship_id">REL782</data><data key="edge_source_entity_id">CON_PEGA_2026</data><data key="edge_relationship_type">awarded_to</data><data key="edge_target_entity_id">ORG_IMMIXTECH</data><data key="edge_operational_context">USAspending identifies immixTechnology, Inc. as recipient of the SSA Pega re-compete award.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL783" source="CON_PEGA_2026" target="TECH_PEGA_PLATFORM"><data key="edge_relationship_id">REL783</data><data key="edge_source_entity_id">CON_PEGA_2026</data><data key="edge_relationship_type">procures</data><data key="edge_target_entity_id">TECH_PEGA_PLATFORM</data><data key="edge_operational_context">Award description covers Pega software modules, software maintenance and SaaS platform.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL784" source="APP_EEO" target="SYS_MEF"><data key="edge_relationship_id">REL784</data><data key="edge_source_entity_id">APP_EEO</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">EEO begins with earnings activity on the Master Earnings File and uses MEF earnings as the primary source for earnings-test enforcement.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL785" source="APP_EEO" target="SYS_MBR"><data key="edge_relationship_id">REL785</data><data key="edge_source_entity_id">APP_EEO</data><data key="edge_relationship_type">compares_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">EEO compares MEF earnings with earnings estimates/reports and other information posted to the MBR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL786" source="APP_EEO" target="APP_T2R"><data key="edge_relationship_id">REL786</data><data key="edge_source_entity_id">APP_EEO</data><data key="edge_relationship_type">automated_processing_via</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">Current POMS states automated EEO cases are processed through Title II Redesign.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL787" source="APP_EEO" target="DOM_TITLE2"><data key="edge_relationship_id">REL787</data><data key="edge_source_entity_id">APP_EEO</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">EEO selects Title II beneficiaries subject to earnings-test withholding and identifies potential overpayment or underpayment situations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL788" source="APP_EEO" target="APP_PCACS"><data key="edge_relationship_id">REL788</data><data key="edge_source_entity_id">APP_EEO</data><data key="edge_relationship_type">may_create_manual_work_control_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">EEO cases that cannot be automated require manual review in processing-center workflows; PCACS is used for Title II processing-center workload control.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Cross-workflow relationship; EEO POMS establishes manual-review cases but does not name PCACS for every EEO case.</data></edge><edge id="REL789" source="PROC_AERO" target="SYS_MEF"><data key="edge_relationship_id">REL789</data><data key="edge_source_entity_id">PROC_AERO</data><data key="edge_relationship_type">uses_earnings_from</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Current earnings-test policy treats AERO recomputation as dependent on corrected/posted earnings information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Functional dependency, not a claim of a direct technical API.</data></edge><edge id="REL790" source="PROC_AERO" target="APP_T2R"><data key="edge_relationship_id">REL790</data><data key="edge_source_entity_id">PROC_AERO</data><data key="edge_relationship_type">executed_within_or_via</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">POMS states T2R incorporated the functionality of legacy AJS-1/AERO.</data><data key="edge_observed_as_of">2014-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL791" source="HIST_AJS1" target="APP_T2R"><data key="edge_relationship_id">REL791</data><data key="edge_source_entity_id">HIST_AJS1</data><data key="edge_relationship_type">modernized_into</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">T2R incorporated Automated Job Stream 1 functionality in August 2014.</data><data key="edge_observed_as_of">2014-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL792" source="HIST_AJS1" target="PROC_AERO"><data key="edge_relationship_id">REL792</data><data key="edge_source_entity_id">HIST_AJS1</data><data key="edge_relationship_type">implemented</data><data key="edge_target_entity_id">PROC_AERO</data><data key="edge_operational_context">AJS-1 was also known as the Automated Earnings Reappraisal Operation and primarily handled earnings-driven benefit-rate changes.</data><data key="edge_observed_as_of">2014-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL793" source="HIST_AJS3" target="APP_T2R"><data key="edge_relationship_id">REL793</data><data key="edge_source_entity_id">HIST_AJS3</data><data key="edge_relationship_type">modernized_into</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">AJS-3 software was retired and its functionality rolled into T2R in August 2012.</data><data key="edge_observed_as_of">2012-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL794" source="APP_SRDBAR" target="APP_ICOR"><data key="edge_relationship_id">REL794</data><data key="edge_source_entity_id">APP_SRDBAR</data><data key="edge_relationship_type">processes_adjustments_from</data><data key="edge_target_entity_id">APP_ICOR</data><data key="edge_operational_context">Current POMS states SRDBAR can reject an Item Correction (ICOR) adjustment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL795" source="APP_SRDBAR" target="APP_PCACS"><data key="edge_relationship_id">REL795</data><data key="edge_source_entity_id">APP_SRDBAR</data><data key="edge_relationship_type">rejects_controlled_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">When SRDBAR rejects an ICOR adjustment requiring correction, staff list/control the case in PCACS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL796" source="APP_SRDBAR" target="SYS_MBR"><data key="edge_relationship_id">REL796</data><data key="edge_source_entity_id">APP_SRDBAR</data><data key="edge_relationship_type">reject_context_documented_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS requires a special message on the MBR explaining the earnings discrepancy when SRDBAR rejects an adjustment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL797" source="PROC_AERO" target="DB_AERO_BYPASS"><data key="edge_relationship_id">REL797</data><data key="edge_source_entity_id">PROC_AERO</data><data key="edge_relationship_type">uses_exception_file</data><data key="edge_target_entity_id">DB_AERO_BYPASS</data><data key="edge_operational_context">Unresolved listing-code conditions cause the AERO BYPASS file to generate a manual-review alert and prevent automatic AERO increases.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL798" source="DB_AERO_BYPASS" target="APP_PCACS"><data key="edge_relationship_id">REL798</data><data key="edge_source_entity_id">DB_AERO_BYPASS</data><data key="edge_relationship_type">generates_manual_review_for</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">AERO bypass conditions are associated with PC manual review and PCACS listing-code controls.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">POMS explicitly describes the bypass alert and PCACS listing code; it does not state the bypass file writes directly into PCACS.</data></edge><edge id="REL799" source="APP_CDREO" target="ORG_IRS"><data key="edge_relationship_id">REL799</data><data key="edge_source_entity_id">APP_CDREO</data><data key="edge_relationship_type">uses_earnings_from</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">Current POMS states CDREO uses earnings from IRS to identify disability beneficiaries requiring possible work CDR review.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL800" source="APP_CDREO" target="DB_DCF"><data key="edge_relationship_id">REL800</data><data key="edge_source_entity_id">APP_CDREO</data><data key="edge_relationship_type">generates_alerts_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">CDREO alerts post to the Disability Control File as T2 Work CDR events.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL801" source="APP_CDREO" target="IFACE_QWID"><data key="edge_relationship_id">REL801</data><data key="edge_source_entity_id">APP_CDREO</data><data key="edge_relationship_type">displayed_through</data><data key="edge_target_entity_id">IFACE_QWID</data><data key="edge_operational_context">Current POMS directs technicians to access CDREO enforcement information through QWID.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL802" source="APP_CDREO" target="APP_EWORK"><data key="edge_relationship_id">REL802</data><data key="edge_source_entity_id">APP_CDREO</data><data key="edge_relationship_type">feeds_reviews_in</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">CDREO alerts are a starting point for work reviews that technicians develop and adjudicate in eWork.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL803" source="APP_CDREO" target="DOM_TITLE2"><data key="edge_relationship_id">REL803</data><data key="edge_source_entity_id">APP_CDREO</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">CDREO targets Title II and concurrent disability beneficiaries with potentially uninvestigated earnings.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL804" source="PROC_QEP" target="ORG_OCSE"><data key="edge_relationship_id">REL804</data><data key="edge_source_entity_id">PROC_QEP</data><data key="edge_relationship_type">receives_quarterly_earnings_from</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">Current POMS states QEP uses quarterly earnings received from HHS OCSE.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL805" source="PROC_QEP" target="DB_NDNH"><data key="edge_relationship_id">REL805</data><data key="edge_source_entity_id">PROC_QEP</data><data key="edge_relationship_type">uses_data_from</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">QEP selections are based on NDNH earnings in the identified quarter.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL806" source="PROC_QEP" target="DB_DCF"><data key="edge_relationship_id">REL806</data><data key="edge_source_entity_id">PROC_QEP</data><data key="edge_relationship_type">generates_alerts_in</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">QEP alerts post as T2 Work CDR events used to initiate or support work review.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL807" source="PROC_QEP" target="IFACE_QWID"><data key="edge_relationship_id">REL807</data><data key="edge_source_entity_id">PROC_QEP</data><data key="edge_relationship_type">displayed_through</data><data key="edge_target_entity_id">IFACE_QWID</data><data key="edge_operational_context">Current POMS states QEP-generated alerts appear on the QWID screen.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL808" source="PROC_QEP" target="APP_EWORK"><data key="edge_relationship_id">REL808</data><data key="edge_source_entity_id">PROC_QEP</data><data key="edge_relationship_type">feeds_reviews_in</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">QEP alerts are a starting point for work reviews; current instructions direct review/development in eWork.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL809" source="IFACE_QMID" target="DB_DCF"><data key="edge_relationship_id">REL809</data><data key="edge_source_entity_id">IFACE_QMID</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">QMID is the CDR medical-information query screen used to examine diary information during enforcement review.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL810" source="IFACE_QWID" target="DB_DCF"><data key="edge_relationship_id">REL810</data><data key="edge_source_entity_id">IFACE_QWID</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">QWID is the DCF work-information query screen used for enforcement and work-review information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL811" source="DB_NDNH" target="ORG_OCSE"><data key="edge_relationship_id">REL811</data><data key="edge_source_entity_id">DB_NDNH</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">SSA POMS identifies NDNH as an OCSE database containing state/federal new-hire, wage and unemployment information.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL812" source="DB_NDNH" target="DOM_EARNINGS"><data key="edge_relationship_id">REL812</data><data key="edge_source_entity_id">DB_NDNH</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DOM_EARNINGS</data><data key="edge_operational_context">NDNH contains quarterly wage information used by SSA for payment accuracy and earnings investigations.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL813" source="IFACE_NDNH_QUERY" target="DB_NDNH"><data key="edge_relationship_id">REL813</data><data key="edge_source_entity_id">IFACE_NDNH_QUERY</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">Authorized SSA users use the NDNH Query to investigate potential earnings.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Detailed interface instructions are older; current 2026 POMS still lists the NDNH Query and active matching programs confirm ongoing NDNH use.</data></edge><edge id="REL814" source="IFACE_NDNH_QUERY" target="APP_MCS"><data key="edge_relationship_id">REL814</data><data key="edge_source_entity_id">IFACE_NDNH_QUERY</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">For initial disability claimants, POMS states an MCS application establishes the business relationship that permits authorized NDNH query access.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">This is an access prerequisite relationship, not a direct MCS-to-NDNH interface.</data></edge><edge id="REL815" source="EX_OCSE_NDNH_1074" target="ORG_OCSE"><data key="edge_relationship_id">REL815</data><data key="edge_source_entity_id">EX_OCSE_NDNH_1074</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">CMA 1074 is an active SSA-OCSE computer matching program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL816" source="EX_OCSE_NDNH_1074" target="DB_NDNH"><data key="edge_relationship_id">REL816</data><data key="edge_source_entity_id">EX_OCSE_NDNH_1074</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">The active matching arrangement supports online access to NDNH information; POMS documents query-only access for authorized SSA users.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Operational query detail comes from POMS; active status comes from the current matching-program list.</data></edge><edge id="REL817" source="EX_OCSE_NDNH_1074" target="IFACE_NDNH_QUERY"><data key="edge_relationship_id">REL817</data><data key="edge_source_entity_id">EX_OCSE_NDNH_1074</data><data key="edge_relationship_type">used_via</data><data key="edge_target_entity_id">IFACE_NDNH_QUERY</data><data key="edge_operational_context">POMS documents the authorized NDNH online query used in disability work development.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL818" source="EX_OCSE_NDNH_1098" target="ORG_OCSE"><data key="edge_relationship_id">REL818</data><data key="edge_source_entity_id">EX_OCSE_NDNH_1098</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_OCSE</data><data key="edge_operational_context">CMA 1098 is an active SSA-OCSE computer matching program.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL819" source="EX_OCSE_NDNH_1098" target="DB_NDNH"><data key="edge_relationship_id">REL819</data><data key="edge_source_entity_id">EX_OCSE_NDNH_1098</data><data key="edge_relationship_type">uses_source</data><data key="edge_target_entity_id">DB_NDNH</data><data key="edge_operational_context">The Title II match uses OCSE NDNH quarterly wage/unemployment information for DI administration.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">The current SSA list identifies the agreement and partner; detailed data content is corroborated by SSA POMS and prior matching documentation.</data></edge><edge id="REL820" source="EX_OCSE_NDNH_1098" target="DOM_TITLE2"><data key="edge_relationship_id">REL820</data><data key="edge_source_entity_id">EX_OCSE_NDNH_1098</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">CMA 1098 supports Title II Disability Insurance eligibility, continuing entitlement and payment-accuracy functions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL821" source="APP_TPPS" target="PAY_USDC"><data key="edge_relationship_id">REL821</data><data key="edge_source_entity_id">APP_TPPS</data><data key="edge_relationship_type">issues_payments_via</data><data key="edge_target_entity_id">PAY_USDC</data><data key="edge_operational_context">Current POMS says field offices issue EAPs and Title XVI immediate payments through TPPS via a U.S. Debit Card effective 2026-02-09.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL822" source="APP_MSSICS" target="APP_TPPS"><data key="edge_relationship_id">REL822</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">transmits_title_xvi_immediate_payment_to</data><data key="edge_target_entity_id">APP_TPPS</data><data key="edge_operational_context">Current SI 02004.010 says staff establish, approve, and transmit a Title XVI immediate payment in MSSICS and then transmit payment information to TPPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL823" source="APP_MSSICS" target="SYS_SSR"><data key="edge_relationship_id">REL823</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">transmits_title_xvi_immediate_payment_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current SI 02004.010 requires same-day transmission of Title XVI immediate-payment data to the SSR; overnight processing also sends the information to the SSR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL824" source="APP_SSI_RMA" target="APP_MSSICS"><data key="edge_relationship_id">REL824</data><data key="edge_source_entity_id">APP_SSI_RMA</data><data key="edge_relationship_type">supports_eap_amount_calculation_before</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">POMS directs technicians to compute the EAP amount with the SSI RMA program or SSA-4968 before establishing/approving/transmitting the EAP in MSSICS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">This is a documented workflow sequence, not an asserted automated system-to-system interface.</data></edge><edge id="REL825" source="PROC_AOTP" target="SYS_SSR"><data key="edge_relationship_id">REL825</data><data key="edge_source_entity_id">PROC_AOTP</data><data key="edge_relationship_type">recorded_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS states a successful automated one-time payment is annotated on the SSR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL826" source="PROC_MOTP" target="SYS_SSR"><data key="edge_relationship_id">REL826</data><data key="edge_source_entity_id">PROC_MOTP</data><data key="edge_relationship_type">manually_posted_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS states a manual one-time payment must be manually posted to the SSR after issuance.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL827" source="PROC_MOTP" target="ORG_TREASURY"><data key="edge_relationship_id">REL827</data><data key="edge_source_entity_id">PROC_MOTP</data><data key="edge_relationship_type">certified_to</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">POMS states the Payment Certification Branch certifies an M-OTP to the U.S. Department of the Treasury.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL828" source="DB_FO_MANUAL_OTP_CONTROL" target="PROC_MOTP"><data key="edge_relationship_id">REL828</data><data key="edge_source_entity_id">DB_FO_MANUAL_OTP_CONTROL</data><data key="edge_relationship_type">tracks</data><data key="edge_target_entity_id">PROC_MOTP</data><data key="edge_operational_context">POMS directs field offices to check the manual OTP control file when an alleged M-OTP does not appear on the SSR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL829" source="APP_MSSICS" target="IFACE_SSI_DIRECT_SSR"><data key="edge_relationship_id">REL829</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">exposes_or_uses</data><data key="edge_target_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_operational_context">Current waiver and nonreceipt procedures explicitly refer to MSSICS/SSI Claims System Direct SSR Update screens.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Logical user/system interface; implementation technology is not public.</data></edge><edge id="REL830" source="IFACE_SSI_DIRECT_SSR" target="SYS_SSR"><data key="edge_relationship_id">REL830</data><data key="edge_source_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS uses Direct SSR Update screens for stop-payment, overpayment-decision, and waiver actions affecting the SSR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL831" source="APP_CCE" target="APP_EDCS"><data key="edge_relationship_id">REL831</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">establishes_claim_before</data><data key="edge_target_entity_id">APP_EDCS</data><data key="edge_operational_context">Current EDCS procedures say MSSICS/CCE should establish the initial claim, reconsideration request, or hearing request before EDCS case creation, subject to documented exclusions.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL832" source="APP_CCE" target="SYS_SSR"><data key="edge_relationship_id">REL832</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">builds</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">For specified QDD/CAL SSI cases, current instructions direct staff to use CCE to build the SSR in blank payment status; under stated conditions a favorable DDS decision can then automatically effectuate.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Scope is limited to the conditions in DI 11055 TN 97; this is not asserted as the universal CCE-to-SSR path for every SSI case.</data></edge><edge id="REL833" source="APP_CCE" target="IFACE_SSI_DIRECT_SSR"><data key="edge_relationship_id">REL833</data><data key="edge_source_entity_id">APP_CCE</data><data key="edge_relationship_type">used_in_title_xvi_waiver_workflow_with</data><data key="edge_target_entity_id">IFACE_SSI_DIRECT_SSR</data><data key="edge_operational_context">Current waiver procedures document the determination in CCE DROC and then require Direct SSR Update/UOWV processing to post the Title XVI waiver decision to the SSR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Workflow relationship only; no direct CCE-to-interface technical call is asserted.</data></edge><edge id="REL834" source="REPO_NDRED" target="REPO_NDR"><data key="edge_relationship_id">REL834</data><data key="edge_source_entity_id">REPO_NDRED</data><data key="edge_relationship_type">prepares_dma_barcode_for_ingest_to</data><data key="edge_target_entity_id">REPO_NDR</data><data key="edge_operational_context">POMS says the NDRed application in Evidence Portal obtains artifact metadata, associates the artifact with the claim filing, and prepares the DMA barcode before the artifact is faxed into NDR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Pre-existing Atlas entity REPO_NDRED is retained even though current POMS calls NDRed an application.</data></edge><edge id="REL835" source="REPO_NDR" target="COMP_DMA"><data key="edge_relationship_id">REL835</data><data key="edge_source_entity_id">REPO_NDR</data><data key="edge_relationship_type">is_section_of</data><data key="edge_target_entity_id">COMP_DMA</data><data key="edge_operational_context">POMS states the Non Disability Repository is contained in a section of Document Manager Architecture.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL836" source="APP_CFUI" target="REPO_NDR"><data key="edge_relationship_id">REL836</data><data key="edge_source_entity_id">APP_CFUI</data><data key="edge_relationship_type">views</data><data key="edge_target_entity_id">REPO_NDR</data><data key="edge_operational_context">POMS says CFUI is used to view an artifact after it has been stored in NDR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL837" source="APP_CFUI" target="APP_EP"><data key="edge_relationship_id">REL837</data><data key="edge_source_entity_id">APP_CFUI</data><data key="edge_relationship_type">used_within</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">POMS says CFUI is used in the Evidence Portal to view artifacts stored in NDR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL838" source="APP_EWORK" target="APP_DPS"><data key="edge_relationship_id">REL838</data><data key="edge_source_entity_id">APP_EWORK</data><data key="edge_relationship_type">uses_notice_generation_from</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Current eWork exclusion instructions require DPS to prepare due-process or final notices because eWork exclusion processing cannot produce the notices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL839" source="APP_RASR" target="APP_DPS"><data key="edge_relationship_id">REL839</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">falls_back_to</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">Current representative-appointment POMS says acknowledgment notices are available in DPS for manual processing when RASR fails to send them; DPS is also used for failed direct-payment-assignment notices.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL840" source="APP_RASR" target="APP_AURORA"><data key="edge_relationship_id">REL840</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">falls_back_to</data><data key="edge_target_entity_id">APP_AURORA</data><data key="edge_operational_context">Current representative-appointment POMS says the acknowledgment notice is available in Manage Text (AURORA) for manual processing when RASR fails to send it.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL841" source="APP_DPS" target="PROC_SNO"><data key="edge_relationship_id">REL841</data><data key="edge_source_entity_id">APP_DPS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_SNO</data><data key="edge_operational_context">Current POMS uses DPS to prepare SNO cover notices and automatically route alternate-format requests.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL842" source="APP_CHIP" target="PROC_SNO"><data key="edge_relationship_id">REL842</data><data key="edge_source_entity_id">APP_CHIP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_SNO</data><data key="edge_operational_context">Current POMS uses CHIP to prepare SNO cover notices and automatically route alternate-format requests.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL843" source="APP_HEART" target="APP_DRAP"><data key="edge_relationship_id">REL843</data><data key="edge_source_entity_id">APP_HEART</data><data key="edge_relationship_type">replaces</data><data key="edge_target_entity_id">APP_DRAP</data><data key="edge_operational_context">SSA FY2025 budget material explicitly says the agency is migrating from the legacy DRAP system to HeaRT via Microsoft Teams, a commercial cloud-based solution.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Replacement is established for the hearing recording/transcription workflow; complete physical retirement of every DRAP artifact is not asserted.</data></edge><edge id="REL844" source="APP_HEART" target="PLAT_MS_TEAMS"><data key="edge_relationship_id">REL844</data><data key="edge_source_entity_id">APP_HEART</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PLAT_MS_TEAMS</data><data key="edge_operational_context">SSA FY2025 Congressional Justification names the product as Hearing Recordings and Transcriptions (HeaRT) via Microsoft Teams.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL845" source="APP_DRAP" target="DATA_HEARING_RECORDING"><data key="edge_relationship_id">REL845</data><data key="edge_source_entity_id">APP_DRAP</data><data key="edge_relationship_type">produced</data><data key="edge_target_entity_id">DATA_HEARING_RECORDING</data><data key="edge_operational_context">SSA historical PIA says DRAP replaces analog recording with digital audio for ALJ hearings and that the recording becomes part of the official agency claim file.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Historical relationship retained for modernization lineage, not current operation.</data></edge><edge id="REL846" source="INIT_CYBER_MOD_COMPLIANCE" target="PROGRAM_IT_SECURITY"><data key="edge_relationship_id">REL846</data><data key="edge_source_entity_id">INIT_CYBER_MOD_COMPLIANCE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROGRAM_IT_SECURITY</data><data key="edge_operational_context">FY2027 LAE lists Cybersecurity Modernization and Compliance as a key IT Security initiative.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Budget-plan relationship.</data></edge><edge id="REL847" source="INIT_IDENTITY_ACCESS_RISK" target="PROGRAM_IT_SECURITY"><data key="edge_relationship_id">REL847</data><data key="edge_source_entity_id">INIT_IDENTITY_ACCESS_RISK</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROGRAM_IT_SECURITY</data><data key="edge_operational_context">FY2027 LAE lists Identity, Access, and Risk Management as a key IT Security initiative.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Budget-plan relationship.</data></edge><edge id="REL848" source="INIT_SECOPS_THREAT_RESPONSE" target="PROGRAM_IT_SECURITY"><data key="edge_relationship_id">REL848</data><data key="edge_source_entity_id">INIT_SECOPS_THREAT_RESPONSE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROGRAM_IT_SECURITY</data><data key="edge_operational_context">FY2027 LAE lists Security Operations and Threat Response as a key IT Security initiative.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Budget-plan relationship.</data></edge><edge id="REL849" source="INIT_ASSESSMENT_APPSEC" target="PROGRAM_IT_SECURITY"><data key="edge_relationship_id">REL849</data><data key="edge_source_entity_id">INIT_ASSESSMENT_APPSEC</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">PROGRAM_IT_SECURITY</data><data key="edge_operational_context">FY2027 LAE lists Assessment and Application Security as a key IT Security initiative.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Budget-plan relationship.</data></edge><edge id="REL850" source="APP_AI_DIP" target="ORG_HYPERSCIENCE"><data key="edge_relationship_id">REL850</data><data key="edge_source_entity_id">APP_AI_DIP</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_HYPERSCIENCE</data><data key="edge_operational_context">SSA inventory identifies Hyperscience as vendor for Duplicate Identification Process.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL851" source="APP_AI_DIP" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL851</data><data key="edge_source_entity_id">APP_AI_DIP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies the use case as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL852" source="APP_FORM_DATA_EXTRACTION" target="ORG_HYPERSCIENCE"><data key="edge_relationship_id">REL852</data><data key="edge_source_entity_id">APP_FORM_DATA_EXTRACTION</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_HYPERSCIENCE</data><data key="edge_operational_context">SSA inventory identifies Hyperscience as vendor for forms classification/data extraction.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL853" source="APP_FORM_DATA_EXTRACTION" target="TECH_COMPUTER_VISION"><data key="edge_relationship_id">REL853</data><data key="edge_source_entity_id">APP_FORM_DATA_EXTRACTION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_COMPUTER_VISION</data><data key="edge_operational_context">Inventory classifies forms classification/data extraction as Computer Vision.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL854" source="APP_POLICYNET_21C" target="TECH_APACHE_SOLR"><data key="edge_relationship_id">REL854</data><data key="edge_source_entity_id">APP_POLICYNET_21C</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_APACHE_SOLR</data><data key="edge_operational_context">SSA states intelligent search results are enabled by Apache Solr.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL855" source="APP_POLICYNET_21C" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL855</data><data key="edge_source_entity_id">APP_POLICYNET_21C</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies PolicyNet search as Classical ML and describes learning-to-rank.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL856" source="APP_AGENCY_SUPPORT_COMPANION" target="ORG_MICROSOFT"><data key="edge_relationship_id">REL856</data><data key="edge_source_entity_id">APP_AGENCY_SUPPORT_COMPANION</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_MICROSOFT</data><data key="edge_operational_context">SSA inventory lists Microsoft / OpenAI for ASC.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL857" source="APP_AGENCY_SUPPORT_COMPANION" target="ORG_OPENAI"><data key="edge_relationship_id">REL857</data><data key="edge_source_entity_id">APP_AGENCY_SUPPORT_COMPANION</data><data key="edge_relationship_type">uses_model_provider</data><data key="edge_target_entity_id">ORG_OPENAI</data><data key="edge_operational_context">SSA inventory lists Microsoft / OpenAI for ASC.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL858" source="APP_AGENCY_SUPPORT_COMPANION" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL858</data><data key="edge_source_entity_id">APP_AGENCY_SUPPORT_COMPANION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies ASC as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL859" source="APP_DGP" target="PLAT_INFORMATICA_EDC"><data key="edge_relationship_id">REL859</data><data key="edge_source_entity_id">APP_DGP</data><data key="edge_relationship_type">runs_on</data><data key="edge_target_entity_id">PLAT_INFORMATICA_EDC</data><data key="edge_operational_context">Inventory identifies Enterprise Data Catalog as the authorized system for DGP.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL860" source="APP_DGP" target="ORG_INFORMATICA"><data key="edge_relationship_id">REL860</data><data key="edge_source_entity_id">APP_DGP</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_INFORMATICA</data><data key="edge_operational_context">Inventory identifies Informatica as vendor for DGP.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL861" source="APP_DGP" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL861</data><data key="edge_source_entity_id">APP_DGP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies DGP as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL862" source="APP_DGP" target="TECH_NLP"><data key="edge_relationship_id">REL862</data><data key="edge_source_entity_id">APP_DGP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_NLP</data><data key="edge_operational_context">Inventory description explicitly states DGP uses NLP to support rule creation and plain-text conversion.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL863" source="APP_CODE_MOD_AI" target="PLAT_AVERISOURCE"><data key="edge_relationship_id">REL863</data><data key="edge_source_entity_id">APP_CODE_MOD_AI</data><data key="edge_relationship_type">runs_on</data><data key="edge_target_entity_id">PLAT_AVERISOURCE</data><data key="edge_operational_context">Inventory identifies AveriSource Platform as the authorized system.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL864" source="APP_CODE_MOD_AI" target="ORG_AVERISOURCE"><data key="edge_relationship_id">REL864</data><data key="edge_source_entity_id">APP_CODE_MOD_AI</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_AVERISOURCE</data><data key="edge_operational_context">Inventory identifies AveriSource as vendor.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL865" source="APP_CODE_MOD_AI" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL865</data><data key="edge_source_entity_id">APP_CODE_MOD_AI</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies modernized-code generation as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL866" source="APP_PAT" target="APP_POLICYNET_21C"><data key="edge_relationship_id">REL866</data><data key="edge_source_entity_id">APP_PAT</data><data key="edge_relationship_type">augments</data><data key="edge_target_entity_id">APP_POLICYNET_21C</data><data key="edge_operational_context">PAT inventory row identifies 21st Century PolicyNet as its authorized system and grounds answers in SSA policy data.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL867" source="APP_PAT" target="ORG_MICROSOFT"><data key="edge_relationship_id">REL867</data><data key="edge_source_entity_id">APP_PAT</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_MICROSOFT</data><data key="edge_operational_context">Inventory lists Microsoft / OpenAI for PAT.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL868" source="APP_PAT" target="ORG_OPENAI"><data key="edge_relationship_id">REL868</data><data key="edge_source_entity_id">APP_PAT</data><data key="edge_relationship_type">uses_model_provider</data><data key="edge_target_entity_id">ORG_OPENAI</data><data key="edge_operational_context">Inventory lists Microsoft / OpenAI for PAT.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL869" source="APP_PAT" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL869</data><data key="edge_source_entity_id">APP_PAT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies PAT as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL870" source="APP_CODING_ASSIST" target="ORG_WINDSURF"><data key="edge_relationship_id">REL870</data><data key="edge_source_entity_id">APP_CODING_ASSIST</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_WINDSURF</data><data key="edge_operational_context">Inventory identifies Windsurf for pre-deployment Coding Assistance.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL871" source="APP_CODING_ASSIST" target="TECH_AGENTIC_AI"><data key="edge_relationship_id">REL871</data><data key="edge_source_entity_id">APP_CODING_ASSIST</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_AGENTIC_AI</data><data key="edge_operational_context">Inventory classifies Coding Assistance as Agentic AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL872" source="APP_MAINFRAME_CODE_ASSIST" target="ORG_IBM"><data key="edge_relationship_id">REL872</data><data key="edge_source_entity_id">APP_MAINFRAME_CODE_ASSIST</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">Inventory lists IBM watsonx Code Assistant for mainframe code modernization assistant.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL873" source="APP_MAINFRAME_CODE_ASSIST" target="ORG_BROADCOM"><data key="edge_relationship_id">REL873</data><data key="edge_source_entity_id">APP_MAINFRAME_CODE_ASSIST</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_BROADCOM</data><data key="edge_operational_context">Inventory lists Broadcom Code for Z for mainframe code modernization assistant.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL874" source="APP_MAINFRAME_CODE_ASSIST" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL874</data><data key="edge_source_entity_id">APP_MAINFRAME_CODE_ASSIST</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies mainframe code modernization assistant as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL875" source="APP_ETS" target="ORG_SERVICENOW"><data key="edge_relationship_id">REL875</data><data key="edge_source_entity_id">APP_ETS</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_SERVICENOW</data><data key="edge_operational_context">Inventory lists ServiceNow and AWS; authorized system is ServiceNow.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL876" source="APP_ETS" target="ORG_AWS"><data key="edge_relationship_id">REL876</data><data key="edge_source_entity_id">APP_ETS</data><data key="edge_relationship_type">uses_cloud_provider</data><data key="edge_target_entity_id">ORG_AWS</data><data key="edge_operational_context">Inventory lists AWS alongside ServiceNow for ETS.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL877" source="APP_GENERAL_USE_CHATBOT" target="ORG_MICROSOFT"><data key="edge_relationship_id">REL877</data><data key="edge_source_entity_id">APP_GENERAL_USE_CHATBOT</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_MICROSOFT</data><data key="edge_operational_context">Inventory identifies Microsoft M365 Copilot Chat.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL878" source="APP_GENERAL_USE_CHATBOT" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL878</data><data key="edge_source_entity_id">APP_GENERAL_USE_CHATBOT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies General Use Chatbot as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL879" source="APP_AI_COMMENT_ANALYSIS" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL879</data><data key="edge_source_entity_id">APP_AI_COMMENT_ANALYSIS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies AI Comment Analysis as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL880" source="APP_MDW_AI" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL880</data><data key="edge_source_entity_id">APP_MDW_AI</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies MDW use case as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL881" source="APP_MDW_AI" target="TECH_NLP"><data key="edge_relationship_id">REL881</data><data key="edge_source_entity_id">APP_MDW_AI</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_NLP</data><data key="edge_operational_context">Inventory names MDW using Natural Language Processing as the system.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL882" source="APP_PER_TDR_MODELS" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL882</data><data key="edge_source_entity_id">APP_PER_TDR_MODELS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies PER/TDR as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL883" source="APP_PER_TDR_MODELS" target="DOM_TITLE2"><data key="edge_relationship_id">REL883</data><data key="edge_source_entity_id">APP_PER_TDR_MODELS</data><data key="edge_relationship_type">scores_data_from</data><data key="edge_target_entity_id">DOM_TITLE2</data><data key="edge_operational_context">Inventory states PER/TDR uses Title II administrative data including SSA-831.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL884" source="APP_PER_TDR_MODELS" target="DOM_TITLE16"><data key="edge_relationship_id">REL884</data><data key="edge_source_entity_id">APP_PER_TDR_MODELS</data><data key="edge_relationship_type">scores_data_from</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Inventory states PER/TDR uses Title XVI administrative data including SSA-831.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL885" source="APP_CDR_MODEL" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL885</data><data key="edge_source_entity_id">APP_CDR_MODEL</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies CDR model as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL886" source="APP_CDR_MODEL" target="SYS_MBR"><data key="edge_relationship_id">REL886</data><data key="edge_source_entity_id">APP_CDR_MODEL</data><data key="edge_relationship_type">ingests</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Inventory states CDR model uses MBR data.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL887" source="APP_CDR_MODEL" target="SYS_SSR"><data key="edge_relationship_id">REL887</data><data key="edge_source_entity_id">APP_CDR_MODEL</data><data key="edge_relationship_type">ingests</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Inventory states CDR model uses SSR data.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL888" source="APP_CDR_MODEL" target="DOM_MEDICARE"><data key="edge_relationship_id">REL888</data><data key="edge_source_entity_id">APP_CDR_MODEL</data><data key="edge_relationship_type">ingests</data><data key="edge_target_entity_id">DOM_MEDICARE</data><data key="edge_operational_context">Inventory states Title II CDR models use CMS health data.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL889" source="APP_SSI_RZ_MODEL" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL889</data><data key="edge_source_entity_id">APP_SSI_RZ_MODEL</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies SSI Redetermination Model as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL890" source="APP_SSI_RZ_MODEL" target="DOM_TITLE16"><data key="edge_relationship_id">REL890</data><data key="edge_source_entity_id">APP_SSI_RZ_MODEL</data><data key="edge_relationship_type">prioritizes_cases_in</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Model prioritizes SSI discretionary non-medical redeterminations for expected overpayment.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL891" source="APP_PATH" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL891</data><data key="edge_source_entity_id">APP_PATH</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies PATH as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL892" source="APP_GENAI_ANALYTICS" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL892</data><data key="edge_source_entity_id">APP_GENAI_ANALYTICS</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies analytic-insights use case as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL893" source="APP_GENAI_ANALYTICS" target="ORG_MICROSOFT"><data key="edge_relationship_id">REL893</data><data key="edge_source_entity_id">APP_GENAI_ANALYTICS</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_MICROSOFT</data><data key="edge_operational_context">Inventory lists Microsoft / OpenAI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL894" source="APP_GENAI_ANALYTICS" target="ORG_OPENAI"><data key="edge_relationship_id">REL894</data><data key="edge_source_entity_id">APP_GENAI_ANALYTICS</data><data key="edge_relationship_type">uses_model_provider</data><data key="edge_target_entity_id">ORG_OPENAI</data><data key="edge_operational_context">Inventory lists Microsoft / OpenAI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL895" source="APP_CXFT" target="ORG_MEDALLIA"><data key="edge_relationship_id">REL895</data><data key="edge_source_entity_id">APP_CXFT</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_MEDALLIA</data><data key="edge_operational_context">Inventory identifies Medallia for Customer Insight Tool/CXFT.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL896" source="APP_CXFT" target="TECH_NLP"><data key="edge_relationship_id">REL896</data><data key="edge_source_entity_id">APP_CXFT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_NLP</data><data key="edge_operational_context">Inventory classifies Customer Insight Tool as NLP.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL897" source="DATA_BE_PUF" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL897</data><data key="edge_source_entity_id">DATA_BE_PUF</data><data key="edge_relationship_type">generated_with</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies Benefit and Earnings Public Use File generation as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL898" source="APP_SSAMWR" target="TECH_COMPUTER_VISION"><data key="edge_relationship_id">REL898</data><data key="edge_source_entity_id">APP_SSAMWR</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_COMPUTER_VISION</data><data key="edge_operational_context">2025 inventory states Mobile Wage Reporting uses computer vision to extract gross pay and pay date from pay-stub images.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL899" source="APP_SSAMWR" target="ORG_AWS"><data key="edge_relationship_id">REL899</data><data key="edge_source_entity_id">APP_SSAMWR</data><data key="edge_relationship_type">uses_cloud_provider</data><data key="edge_target_entity_id">ORG_AWS</data><data key="edge_operational_context">2025 inventory identifies AWS for Mobile Wage Reporting.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL900" source="APP_800_QA_BOT" target="APP_ECC"><data key="edge_relationship_id">REL900</data><data key="edge_source_entity_id">APP_800_QA_BOT</data><data key="edge_relationship_type">operates_within</data><data key="edge_target_entity_id">APP_ECC</data><data key="edge_operational_context">Inventory identifies Enterprise Contact Center as the authorized system for the 800-number Q&amp;A/OIG intake use case.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL901" source="APP_800_QA_BOT" target="ORG_AWS"><data key="edge_relationship_id">REL901</data><data key="edge_source_entity_id">APP_800_QA_BOT</data><data key="edge_relationship_type">uses_cloud_provider</data><data key="edge_target_entity_id">ORG_AWS</data><data key="edge_operational_context">Inventory identifies AWS for the 800-number Q&amp;A/OIG intake use case.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL902" source="APP_800_QA_BOT" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL902</data><data key="edge_source_entity_id">APP_800_QA_BOT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies the use case as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL903" source="APP_DIGITAL_ID_AI" target="SVC_IDME"><data key="edge_relationship_id">REL903</data><data key="edge_source_entity_id">APP_DIGITAL_ID_AI</data><data key="edge_relationship_type">implemented_by_external_service</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">Inventory identifies ID.me as the vendor for Digital Identity Verification Services.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL904" source="APP_DIGITAL_ID_AI" target="TECH_COMPUTER_VISION"><data key="edge_relationship_id">REL904</data><data key="edge_source_entity_id">APP_DIGITAL_ID_AI</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_COMPUTER_VISION</data><data key="edge_operational_context">Inventory classifies Digital Identity Verification Services as Computer Vision.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL905" source="APP_INSIGHT" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL905</data><data key="edge_source_entity_id">APP_INSIGHT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies Insight as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL906" source="APP_IMAGEN" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL906</data><data key="edge_source_entity_id">APP_IMAGEN</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">2025 inventory classifies IMAGEN as Classical ML and describes annotations and candidate impairment/listing codes.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL907" source="APP_HEART" target="ORG_MICROSOFT"><data key="edge_relationship_id">REL907</data><data key="edge_source_entity_id">APP_HEART</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_MICROSOFT</data><data key="edge_operational_context">2025 inventory identifies Microsoft for speech-to-text hearing transcription and names Hearing Recording and Transcription as the authorized system.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL908" source="APP_HEART" target="TECH_NLP"><data key="edge_relationship_id">REL908</data><data key="edge_source_entity_id">APP_HEART</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_NLP</data><data key="edge_operational_context">2025 inventory classifies speech-to-text hearing transcription as NLP.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL909" source="APP_VAAT" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL909</data><data key="edge_source_entity_id">APP_VAAT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies VAAT as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL910" source="APP_VAAT" target="ORG_MICROSOFT"><data key="edge_relationship_id">REL910</data><data key="edge_source_entity_id">APP_VAAT</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_MICROSOFT</data><data key="edge_operational_context">Inventory lists Microsoft / OpenAI for VAAT.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL911" source="APP_VAAT" target="ORG_OPENAI"><data key="edge_relationship_id">REL911</data><data key="edge_source_entity_id">APP_VAAT</data><data key="edge_relationship_type">uses_model_provider</data><data key="edge_target_entity_id">ORG_OPENAI</data><data key="edge_operational_context">Inventory lists Microsoft / OpenAI for VAAT.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL912" source="APP_VAAT" target="PLAT_EDIB_CLOUD"><data key="edge_relationship_id">REL912</data><data key="edge_source_entity_id">APP_VAAT</data><data key="edge_relationship_type">runs_within</data><data key="edge_target_entity_id">PLAT_EDIB_CLOUD</data><data key="edge_operational_context">Inventory identifies eDIB Cloud as the authorized system for VAAT.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL913" source="APP_APP_OBSERVABILITY_AI" target="ORG_DYNATRACE"><data key="edge_relationship_id">REL913</data><data key="edge_source_entity_id">APP_APP_OBSERVABILITY_AI</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_DYNATRACE</data><data key="edge_operational_context">Inventory identifies Dynatrace for Application Observability Support.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL914" source="APP_APP_OBSERVABILITY_AI" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL914</data><data key="edge_source_entity_id">APP_APP_OBSERVABILITY_AI</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies observability support as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL915" source="APP_THERAPY_CHATBOT" target="ORG_ESPYR_ACENTRA"><data key="edge_relationship_id">REL915</data><data key="edge_source_entity_id">APP_THERAPY_CHATBOT</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_ESPYR_ACENTRA</data><data key="edge_operational_context">Inventory identifies Espyr/Acentra for the employee therapy chatbot.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL916" source="APP_THERAPY_CHATBOT" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL916</data><data key="edge_source_entity_id">APP_THERAPY_CHATBOT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies the therapy chatbot as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL917" source="APP_TRAINING_SIMULATOR" target="ORG_SKILLSOFT_PERCIPIO"><data key="edge_relationship_id">REL917</data><data key="edge_source_entity_id">APP_TRAINING_SIMULATOR</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_SKILLSOFT_PERCIPIO</data><data key="edge_operational_context">Inventory identifies Skillsoft/Percipio for Training Interaction Simulator.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL918" source="APP_TRAINING_SIMULATOR" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL918</data><data key="edge_source_entity_id">APP_TRAINING_SIMULATOR</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies Training Interaction Simulator as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL919" source="APP_HR_CHATBOT" target="ORG_MICROSOFT"><data key="edge_relationship_id">REL919</data><data key="edge_source_entity_id">APP_HR_CHATBOT</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_MICROSOFT</data><data key="edge_operational_context">Inventory identifies Microsoft / OpenAI for HR Chatbot.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL920" source="APP_HR_CHATBOT" target="ORG_OPENAI"><data key="edge_relationship_id">REL920</data><data key="edge_source_entity_id">APP_HR_CHATBOT</data><data key="edge_relationship_type">uses_model_provider</data><data key="edge_target_entity_id">ORG_OPENAI</data><data key="edge_operational_context">Inventory identifies Microsoft / OpenAI for HR Chatbot.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL921" source="APP_HR_CHATBOT" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL921</data><data key="edge_source_entity_id">APP_HR_CHATBOT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies HR Chatbot as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL922" source="APP_TRAINING_MEDIA_AI" target="ORG_ADOBE"><data key="edge_relationship_id">REL922</data><data key="edge_source_entity_id">APP_TRAINING_MEDIA_AI</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_ADOBE</data><data key="edge_operational_context">Inventory identifies Adobe for training audio/video generation.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL923" source="APP_TRAINING_MEDIA_AI" target="ORG_ARTICULATE"><data key="edge_relationship_id">REL923</data><data key="edge_source_entity_id">APP_TRAINING_MEDIA_AI</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_ARTICULATE</data><data key="edge_operational_context">Inventory identifies Articulate for training audio/video generation.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL924" source="APP_TRAINING_MEDIA_AI" target="ORG_VYOND"><data key="edge_relationship_id">REL924</data><data key="edge_source_entity_id">APP_TRAINING_MEDIA_AI</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_VYOND</data><data key="edge_operational_context">Inventory identifies Vyond for training audio/video generation.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL925" source="APP_TRAINING_MEDIA_AI" target="TECH_GENERATIVE_AI"><data key="edge_relationship_id">REL925</data><data key="edge_source_entity_id">APP_TRAINING_MEDIA_AI</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_GENERATIVE_AI</data><data key="edge_operational_context">Inventory classifies training audio/video generation as Generative AI.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL926" source="APP_QDD_MODEL" target="ORG_IBM"><data key="edge_relationship_id">REL926</data><data key="edge_source_entity_id">APP_QDD_MODEL</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">Inventory identifies IBM for QDD model.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL927" source="APP_QDD_MODEL" target="TECH_MACHINE_LEARNING"><data key="edge_relationship_id">REL927</data><data key="edge_source_entity_id">APP_QDD_MODEL</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_MACHINE_LEARNING</data><data key="edge_operational_context">Inventory classifies QDD model as Classical ML.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL928" source="APP_QDD_MODEL" target="PLAT_EDIB"><data key="edge_relationship_id">REL928</data><data key="edge_source_entity_id">APP_QDD_MODEL</data><data key="edge_relationship_type">runs_within</data><data key="edge_target_entity_id">PLAT_EDIB</data><data key="edge_operational_context">Inventory identifies eDIB (electronic disability) as the authorized system for QDD.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL929" source="APP_QDD_MODEL" target="ORG_DDS"><data key="edge_relationship_id">REL929</data><data key="edge_source_entity_id">APP_QDD_MODEL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">QDD scores initial disability claims to prioritize DDS processing.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">5</data></edge><edge id="REL930" source="APP_EAFI" target="APP_E4641"><data key="edge_relationship_id">REL930</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">works_with</data><data key="edge_target_entity_id">APP_E4641</data><data key="edge_operational_context">Current POMS identifies eAFI and e4641 as the two main components used in the AFI process.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data></edge><edge id="REL931" source="APP_EAFI" target="EX_AFI_FI"><data key="edge_relationship_id">REL931</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">sends_requests_via</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">eAFI electronically requests and views bank-account balance data from participating financial institutions.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data></edge><edge id="REL932" source="APP_E4641" target="EX_AFI_FI"><data key="edge_relationship_id">REL932</data><data key="edge_source_entity_id">APP_E4641</data><data key="edge_relationship_type">sends_requests_via</data><data key="edge_target_entity_id">EX_AFI_FI</data><data key="edge_operational_context">e4641 is an electronic AFI component used for financial-institution verification requests.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data></edge><edge id="REL933" source="EX_AFI_FI" target="DATA_FI_BALANCE_HISTORY"><data key="edge_relationship_id">REL933</data><data key="edge_source_entity_id">EX_AFI_FI</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">DATA_FI_BALANCE_HISTORY</data><data key="edge_operational_context">AFI responses provide historical bank-account balance data used for SSI resource verification.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data></edge><edge id="REL934" source="APP_EAFI" target="DATA_FI_BALANCE_HISTORY"><data key="edge_relationship_id">REL934</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">receives</data><data key="edge_target_entity_id">DATA_FI_BALANCE_HISTORY</data><data key="edge_operational_context">eAFI View Request supports viewing returned FI balance information.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data></edge><edge id="REL935" source="APP_E4641" target="DATA_FI_BALANCE_HISTORY"><data key="edge_relationship_id">REL935</data><data key="edge_source_entity_id">APP_E4641</data><data key="edge_relationship_type">receives</data><data key="edge_target_entity_id">DATA_FI_BALANCE_HISTORY</data><data key="edge_operational_context">e4641 responses provide FI balance information in the AFI process.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data></edge><edge id="REL936" source="APP_EAFI" target="DOM_TITLE16"><data key="edge_relationship_id">REL936</data><data key="edge_source_entity_id">APP_EAFI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">Mandatory AFI verification applies to specified SSI initial-eligibility actions and resource determinations.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data></edge><edge id="REL937" source="APP_E4641" target="DOM_TITLE16"><data key="edge_relationship_id">REL937</data><data key="edge_source_entity_id">APP_E4641</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DOM_TITLE16</data><data key="edge_operational_context">e4641 is a main AFI component for SSI financial verification.</data><data key="edge_observed_as_of">2026-09-10</data><data key="edge_confidence">5</data></edge><edge id="REL938" source="APP_ERPS" target="DATA_ERPS_ORG_ID"><data key="edge_relationship_id">REL938</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_ERPS_ORG_ID</data><data key="edge_operational_context">eRPS creates an Organization ID using the organization physical-location ZIP Code plus a sequence number.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data></edge><edge id="REL939" source="APP_ERPS" target="DB_EIF"><data key="edge_relationship_id">REL939</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">verifies_organization_ein_against</data><data key="edge_target_entity_id">DB_EIF</data><data key="edge_operational_context">Current POMS requires FO managers to verify organizational EIN information; EIF is referenced when validating the business/EIN record.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data></edge><edge id="REL940" source="APP_ERPS" target="APP_DIPS"><data key="edge_relationship_id">REL940</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">checks_death_alerts_from</data><data key="edge_target_entity_id">APP_DIPS</data><data key="edge_operational_context">eRPS produces an RP death alert when death data exist for an applicant in DIPS.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data><data key="edge_notes">GN 00502.132 source is dated 2022 but remains available POMS; relationship is modeled as an alert dependency, not a direct protocol.</data></edge><edge id="REL941" source="APP_ERPS" target="SYS_MBR"><data key="edge_relationship_id">REL941</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">records_payee_type_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current POMS states Rep Payee Type is recorded on MBR, SSR, and eRPS.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data></edge><edge id="REL942" source="APP_ERPS" target="SYS_SSR"><data key="edge_relationship_id">REL942</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">records_payee_type_on</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS states Rep Payee Type is recorded on MBR, SSR, and eRPS.</data><data key="edge_observed_as_of">2026-07-17</data><data key="edge_confidence">5</data></edge><edge id="REL943" source="ORG_PPDX" target="EX_DTA"><data key="edge_relationship_id">REL943</data><data key="edge_source_entity_id">ORG_PPDX</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">EX_DTA</data><data key="edge_operational_context">PPDX is SSA’s focal point for agency-wide data exchange; DTA is one documented real-time data-exchange method.</data><data key="edge_observed_as_of">2026-03-17</data><data key="edge_confidence">5</data></edge><edge id="REL944" source="APP_GSO" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">REL944</data><data key="edge_source_entity_id">APP_GSO</data><data key="edge_relationship_type">planned_sign_in_via</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">Current GSO page states GSO will soon require sign-in using Login.gov or ID.me.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Planned/upcoming relationship; not represented as completed cutover.</data></edge><edge id="REL945" source="APP_GSO" target="SVC_IDME"><data key="edge_relationship_id">REL945</data><data key="edge_source_entity_id">APP_GSO</data><data key="edge_relationship_type">planned_sign_in_via</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">Current GSO page states GSO will soon require sign-in using Login.gov or ID.me.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Planned/upcoming relationship; not represented as completed cutover.</data></edge><edge id="REL946" source="SVC_DIRECT_EXPRESS" target="ORG_FIFTH_THIRD"><data key="edge_relationship_id">REL946</data><data key="edge_source_entity_id">SVC_DIRECT_EXPRESS</data><data key="edge_relationship_type">financial_agent</data><data key="edge_target_entity_id">ORG_FIFTH_THIRD</data><data key="edge_operational_context">Beginning May 18, 2026 new Direct Express enrollment requests go to Fifth Third Bank; SSA says the program is now managed by Fifth Third.</data><data key="edge_observed_as_of">2026-05-19</data><data key="edge_confidence">5</data></edge><edge id="REL947" source="SVC_DIRECT_EXPRESS" target="ORG_COMERICA"><data key="edge_relationship_id">REL947</data><data key="edge_source_entity_id">SVC_DIRECT_EXPRESS</data><data key="edge_relationship_type">legacy_financial_agent_during_transition</data><data key="edge_target_entity_id">ORG_COMERICA</data><data key="edge_operational_context">Existing Comerica-issued cards remain in use during phased migration to Fifth Third.</data><data key="edge_observed_as_of">2026-05-19</data><data key="edge_confidence">5</data></edge><edge id="REL948" source="ORG_BFS" target="ORG_FIFTH_THIRD"><data key="edge_relationship_id">REL948</data><data key="edge_source_entity_id">ORG_BFS</data><data key="edge_relationship_type">selected_financial_agent</data><data key="edge_target_entity_id">ORG_FIFTH_THIRD</data><data key="edge_operational_context">Treasury Bureau of the Fiscal Service selected Fifth Third as the new Direct Express financial agent in September 2025.</data><data key="edge_observed_as_of">2026-05-19</data><data key="edge_confidence">5</data></edge><edge id="REL949" source="PROC_IDD" target="ORG_FRBKC"><data key="edge_relationship_id">REL949</data><data key="edge_source_entity_id">PROC_IDD</data><data key="edge_relationship_type">operated_with</data><data key="edge_target_entity_id">ORG_FRBKC</data><data key="edge_operational_context">Current POMS states IDD is a joint effort between SSA and the Federal Reserve Bank of Kansas City.</data><data key="edge_observed_as_of">2026-08-25</data><data key="edge_confidence">5</data></edge><edge id="REL950" source="PROC_IDD" target="SYS_MBR"><data key="edge_relationship_id">REL950</data><data key="edge_source_entity_id">PROC_IDD</data><data key="edge_relationship_type">stores_bank_data_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current country-specific POMS stores IDD bank data on the MBR in the same fields used for U.S. direct deposit.</data><data key="edge_observed_as_of">2026-08-25</data><data key="edge_confidence">5</data></edge><edge id="REL951" source="PROC_IDD" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL951</data><data key="edge_source_entity_id">PROC_IDD</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Current POMS requires ITS.gov updates for IDD processing and identifies ITS.gov as International Treasury Services.</data><data key="edge_observed_as_of">2026-08-25</data><data key="edge_confidence">5</data></edge><edge id="REL952" source="PROC_IDD" target="ORG_FRBKC"><data key="edge_relationship_id">REL952</data><data key="edge_source_entity_id">PROC_IDD</data><data key="edge_relationship_type">routes_payments_through</data><data key="edge_target_entity_id">ORG_FRBKC</data><data key="edge_operational_context">Special country coding routes IDD payments through FRBKC and a processor bank to the beneficiary financial institution.</data><data key="edge_observed_as_of">2026-08-25</data><data key="edge_confidence">5</data></edge><edge id="REL953" source="APP_POS" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL953</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Current POMS requires same-day ITS.gov updates when processing supported IDD bank-data changes through POS.</data><data key="edge_observed_as_of">2026-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Represents coordinated business processing, not an inferred system-to-system API.</data></edge><edge id="REL954" source="APP_MACADE" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL954</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Current POMS requires same-day ITS.gov updates when processing supported IDD bank-data changes through MACADE.</data><data key="edge_observed_as_of">2026-08-25</data><data key="edge_confidence">5</data><data key="edge_notes">Represents coordinated business processing, not an inferred system-to-system API.</data></edge><edge id="REL955" source="PROC_RETAP" target="SYS_MBR"><data key="edge_relationship_id">REL955</data><data key="edge_source_entity_id">PROC_RETAP</data><data key="edge_relationship_type">establishes_entitlement_on</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">RETAP establishes applicable HI and SMI entitlement on the MBR for beneficiaries approaching Medicare entitlement.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL956" source="PROC_RETAP" target="ORG_CMS"><data key="edge_relationship_id">REL956</data><data key="edge_source_entity_id">PROC_RETAP</data><data key="edge_relationship_type">sends_hi_entitlement_to</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">For beneficiaries residing in foreign countries, SSA sends RETAP-established HI entitlement information to CMS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL957" source="PROC_MALP" target="SYS_MBR"><data key="edge_relationship_id">REL957</data><data key="edge_source_entity_id">PROC_MALP</data><data key="edge_relationship_type">can_establish</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Current state-buy-in POMS states MALP can automatically establish the MBR for an uninsured individual in specified cases.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data></edge><edge id="REL958" source="IFACE_MCS_HI19" target="APP_MCS"><data key="edge_relationship_id">REL958</data><data key="edge_source_entity_id">IFACE_MCS_HI19</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">POMS instructs technicians using MCS to use HI19 to initiate State buy-in.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data></edge><edge id="REL959" source="IFACE_MCS_HI19" target="PROC_STATE_BUYIN"><data key="edge_relationship_id">REL959</data><data key="edge_source_entity_id">IFACE_MCS_HI19</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_STATE_BUYIN</data><data key="edge_operational_context">HI19 is used in MCS to initiate State buy-in for applicable cases.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data></edge><edge id="REL960" source="IFACE_CCE_HEALTH_INS" target="APP_CCE"><data key="edge_relationship_id">REL960</data><data key="edge_source_entity_id">IFACE_CCE_HEALTH_INS</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">POMS identifies the CCE Health Insurance screen for documenting Medicaid and initiating State buy-in.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data></edge><edge id="REL961" source="IFACE_CCE_HEALTH_INS" target="PROC_STATE_BUYIN"><data key="edge_relationship_id">REL961</data><data key="edge_source_entity_id">IFACE_CCE_HEALTH_INS</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_STATE_BUYIN</data><data key="edge_operational_context">CCE Health Insurance screen includes an Initiate State Buy-in action for applicable cases.</data><data key="edge_observed_as_of">2026-06-30</data><data key="edge_confidence">5</data></edge><edge id="REL962" source="EX_STATE_BUYIN" target="PROC_STATE_BUYIN"><data key="edge_relationship_id">REL962</data><data key="edge_source_entity_id">EX_STATE_BUYIN</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_STATE_BUYIN</data><data key="edge_operational_context">POMS states the State buy-in program operates daily through automated data exchanges among States, SSA, and CMS.</data><data key="edge_observed_as_of">2026-07-15</data><data key="edge_confidence">5</data></edge><edge id="REL963" source="EX_STATE_BUYIN" target="ORG_CMS"><data key="edge_relationship_id">REL963</data><data key="edge_source_entity_id">EX_STATE_BUYIN</data><data key="edge_relationship_type">exchanges_with</data><data key="edge_target_entity_id">ORG_CMS</data><data key="edge_operational_context">CMS participates in the daily automated State buy-in data exchanges.</data><data key="edge_observed_as_of">2026-07-15</data><data key="edge_confidence">5</data></edge><edge id="REL964" source="APP_GSO" target="APP_FFSCF"><data key="edge_relationship_id">REL964</data><data key="edge_source_entity_id">APP_GSO</data><data key="edge_relationship_type">feeds_warrant_reporting_to</data><data key="edge_target_entity_id">APP_FFSCF</data><data key="edge_operational_context">Current POMS states computer-generated warrant information received through GSO is processed through FFSCF.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL965" source="FAC_NCC" target="APP_FFSCF"><data key="edge_relationship_id">REL965</data><data key="edge_source_entity_id">FAC_NCC</data><data key="edge_relationship_type">receives_warrant_input_for</data><data key="edge_target_entity_id">APP_FFSCF</data><data key="edge_operational_context">Current POMS states third-party computer-generated warrant information may be received at NCC and processed through FFSCF.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL966" source="APP_FFSCF" target="APP_EVS"><data key="edge_relationship_id">REL966</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">uses_identity_verification_from</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">Incoming warrant files are run through EVS before FFSCF matching and control processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL967" source="APP_FFSCF" target="SYS_MBR"><data key="edge_relationship_id">REL967</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">FFSCF matches verified warrant data against MBR records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL968" source="APP_FFSCF" target="SYS_SSR"><data key="edge_relationship_id">REL968</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">FFSCF matches verified warrant data against SSR records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL969" source="APP_FFSCF" target="APP_RPS"><data key="edge_relationship_id">REL969</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">matches_against</data><data key="edge_target_entity_id">APP_RPS</data><data key="edge_operational_context">FFSCF matches felony warrant data against the Representative Payee System.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL970" source="APP_FFSCF" target="DB_NICMS"><data key="edge_relationship_id">REL970</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">sends_matched_warrants_to</data><data key="edge_target_entity_id">DB_NICMS</data><data key="edge_operational_context">POMS states matched MBR/SSR warrant records are created for OIG to load into NICMS for verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Modeled as a business-data handoff; transport protocol is not public.</data></edge><edge id="REL971" source="DB_NICMS" target="DATA_OIG_WARRANT_DISP"><data key="edge_relationship_id">REL971</data><data key="edge_source_entity_id">DB_NICMS</data><data key="edge_relationship_type">produces_for</data><data key="edge_target_entity_id">DATA_OIG_WARRANT_DISP</data><data key="edge_operational_context">After OIG validation and law-enforcement action, OIG creates a Warrant Disposition File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">NICMS is the documented OIG case system used in verification; the exact file-generation implementation is not disclosed.</data></edge><edge id="REL972" source="DATA_OIG_WARRANT_DISP" target="APP_FFSCF"><data key="edge_relationship_id">REL972</data><data key="edge_source_entity_id">DATA_OIG_WARRANT_DISP</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">APP_FFSCF</data><data key="edge_operational_context">The OIG Warrant Disposition File is returned to FFSCF so the warrant database can be updated.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL973" source="APP_FFSCF" target="APP_FFAP"><data key="edge_relationship_id">REL973</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">generates_actionable_warrants_for</data><data key="edge_target_entity_id">APP_FFAP</data><data key="edge_operational_context">FFSCF generates an actionable warrant file for Title XVI processing in FFAP.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL974" source="APP_FFSCF" target="APP_RPS"><data key="edge_relationship_id">REL974</data><data key="edge_source_entity_id">APP_FFSCF</data><data key="edge_relationship_type">generates_warrant_data_for</data><data key="edge_target_entity_id">APP_RPS</data><data key="edge_operational_context">FFSCF generates warrant data for representative-payee processing in RPS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL975" source="IFACE_FFEL" target="APP_MCS"><data key="edge_relationship_id">REL975</data><data key="edge_source_entity_id">IFACE_FFEL</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Manual Title II fugitive suspension/reinstatement input can be made through FFEL in MCS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL976" source="IFACE_FFEL" target="APP_POS"><data key="edge_relationship_id">REL976</data><data key="edge_source_entity_id">IFACE_FFEL</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Manual Title II fugitive suspension/reinstatement input can be made through FFEL in POS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL977" source="IFACE_FFEL" target="APP_MACADE"><data key="edge_relationship_id">REL977</data><data key="edge_source_entity_id">IFACE_FFEL</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">Manual Title II fugitive suspension/reinstatement input can be made through an FFEL look-alike screen in MACADE.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL978" source="IFACE_FFEL" target="SYS_MBR"><data key="edge_relationship_id">REL978</data><data key="edge_source_entity_id">IFACE_FFEL</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">FFEL processing establishes or updates fugitive-felon data on the MBR FUGITIVE line.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL979" source="APP_PTMI" target="APP_PUPS"><data key="edge_relationship_id">REL979</data><data key="edge_source_entity_id">APP_PTMI</data><data key="edge_relationship_type">monitors_pending_workload_in</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">PTMI manages and monitors PUPS pending workloads and generates listings for offices with pending PUPS records.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL980" source="PROC_PRISONER_MATCH" target="APP_EVS"><data key="edge_relationship_id">REL980</data><data key="edge_source_entity_id">PROC_PRISONER_MATCH</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">The automated inmate matching operation verifies reported inmate identities through EVS when criteria are met.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL981" source="PROC_PRISONER_MATCH" target="APP_UPS"><data key="edge_relationship_id">REL981</data><data key="edge_source_entity_id">PROC_PRISONER_MATCH</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_UPS</data><data key="edge_operational_context">When EVS cannot verify an inmate identity, UPS supports manual verification and reentry into the matching operation.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL982" source="PROC_PRISONER_MATCH" target="DB_ALPHIDENT"><data key="edge_relationship_id">REL982</data><data key="edge_source_entity_id">PROC_PRISONER_MATCH</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DB_ALPHIDENT</data><data key="edge_operational_context">The automated inmate matching operation screens records against ALPHIDENT when an SSN is missing or does not meet verification criteria.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL983" source="PROC_PRISONER_MATCH" target="APP_PUPS"><data key="edge_relationship_id">REL983</data><data key="edge_source_entity_id">PROC_PRISONER_MATCH</data><data key="edge_relationship_type">creates_records_in</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">Current POMS states the matching operation creates PUPS records for verified inmate matches.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL984" source="APP_UPS" target="APP_EVS"><data key="edge_relationship_id">REL984</data><data key="edge_source_entity_id">APP_UPS</data><data key="edge_relationship_type">feeds_corrected_identity_to</data><data key="edge_target_entity_id">APP_EVS</data><data key="edge_operational_context">UPS can retain a corrected SSN and later notify EVS of the correct name and SSN for matching.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL985" source="APP_PUPS" target="APP_IRCS"><data key="edge_relationship_id">REL985</data><data key="edge_source_entity_id">APP_PUPS</data><data key="edge_relationship_type">calculates_incentive_payments_for</data><data key="edge_target_entity_id">APP_IRCS</data><data key="edge_operational_context">PUPS calculates prisoner-report incentive payments; IRCS maintains reporter/facility agreement and incentive-payment information.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">4</data><data key="edge_notes">Both roles are explicitly documented, but the public POMS does not establish a direct technical interface between PUPS and IRCS. This relation denotes shared business process, not API connectivity.</data></edge><edge id="REL986" source="APP_BUCS" target="APP_PUPS"><data key="edge_relationship_id">REL986</data><data key="edge_source_entity_id">APP_BUCS</data><data key="edge_relationship_type">sweeps_unpaid_incentive_records_in</data><data key="edge_target_entity_id">APP_PUPS</data><data key="edge_operational_context">On the first business day of each month BUCS searches PUPS for records with unpaid incentive-payment amounts.</data><data key="edge_observed_as_of">2026-04-14</data><data key="edge_confidence">5</data></edge><edge id="REL987" source="PROC_APRYSE_RENEWAL_2026" target="APP_DCE"><data key="edge_relationship_id">REL987</data><data key="edge_source_entity_id">PROC_APRYSE_RENEWAL_2026</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_DCE</data><data key="edge_operational_context">The solicitation states the 12-month Apryse PDFTron PDFNet SDK renewal is to support the Document Conversion Engine.</data><data key="edge_observed_as_of">2026-04-29</data><data key="edge_confidence">5</data></edge><edge id="REL988" source="PROC_APRYSE_RENEWAL_2026" target="TECH_APRYSE_PDFNET"><data key="edge_relationship_id">REL988</data><data key="edge_source_entity_id">PROC_APRYSE_RENEWAL_2026</data><data key="edge_relationship_type">renews</data><data key="edge_target_entity_id">TECH_APRYSE_PDFNET</data><data key="edge_operational_context">The solicitation is specifically for annual renewal of Apryse PDFTron PDFNet SDK.</data><data key="edge_observed_as_of">2026-04-29</data><data key="edge_confidence">5</data></edge><edge id="REL989" source="TECH_APRYSE_PDFNET" target="APP_DCE"><data key="edge_relationship_id">REL989</data><data key="edge_source_entity_id">TECH_APRYSE_PDFNET</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_DCE</data><data key="edge_operational_context">SSA identifies PDFNet SDK as software used to support DCE.</data><data key="edge_observed_as_of">2026-04-29</data><data key="edge_confidence">5</data></edge><edge id="REL990" source="ORG_APRYSE" target="TECH_APRYSE_PDFNET"><data key="edge_relationship_id">REL990</data><data key="edge_source_entity_id">ORG_APRYSE</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">TECH_APRYSE_PDFNET</data><data key="edge_operational_context">The official solicitation names the product as Apryse PDFTron PDFNet SDK.</data><data key="edge_observed_as_of">2026-04-29</data><data key="edge_confidence">5</data><data key="edge_notes">Product ownership is taken from the official product name; no reseller or awardee is inferred.</data></edge><edge id="REL991" source="PROC_MAINFRAME_PRICING_2026" target="TECH_MAINFRAME"><data key="edge_relationship_id">REL991</data><data key="edge_source_entity_id">PROC_MAINFRAME_PRICING_2026</data><data key="edge_relationship_type">assesses_pricing_for</data><data key="edge_target_entity_id">TECH_MAINFRAME</data><data key="edge_operational_context">The notice describes IT mainframe software pricing model assessment support services.</data><data key="edge_observed_as_of">2026-09-23</data><data key="edge_confidence">5</data></edge><edge id="REL992" source="PROC_DATA_PIPELINE_RFI_2026" target="CAP_ENTERPRISE_LOGGING"><data key="edge_relationship_id">REL992</data><data key="edge_source_entity_id">PROC_DATA_PIPELINE_RFI_2026</data><data key="edge_relationship_type">seeks_solution_for</data><data key="edge_target_entity_id">CAP_ENTERPRISE_LOGGING</data><data key="edge_operational_context">SSA seeks log creation/retention, aggregation, and encrypted-access functionality in a Data Pipeline Solution RFI.</data><data key="edge_observed_as_of">2026-05-14</data><data key="edge_confidence">5</data><data key="edge_notes">RFI requirements are linked to the existing Atlas enterprise-logging capability; this does not assert a selected product or implementation.</data></edge><edge id="REL993" source="APP_MCS" target="DB_T2_ODS"><data key="edge_relationship_id">REL993</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">feeds_nightly</data><data key="edge_target_entity_id">DB_T2_ODS</data><data key="edge_operational_context">SSA Open Data documentation states data are downloaded from MCS nightly to the Title II Operational Data Store.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">5</data></edge><edge id="REL994" source="DATA_DOWR" target="DB_T2_ODS"><data key="edge_relationship_id">REL994</data><data key="edge_source_entity_id">DATA_DOWR</data><data key="edge_relationship_type">provides_work_measurement_dates_for</data><data key="edge_target_entity_id">DB_T2_ODS</data><data key="edge_operational_context">SSA public workload documentation uses DOWR receipt dates alongside T2 ODS claims data for workload reporting.</data><data key="edge_observed_as_of">2026-07-10</data><data key="edge_confidence">4</data><data key="edge_notes">This represents documented reporting semantics, not a claimed direct database interface.</data></edge><edge id="REL995" source="DATA_DDFP_BLOCK" target="EX_ENR"><data key="edge_relationship_id">REL995</data><data key="edge_source_entity_id">DATA_DDFP_BLOCK</data><data key="edge_relationship_type">restricts_direct_deposit_changes_via</data><data key="edge_target_entity_id">EX_ENR</data><data key="edge_operational_context">When a DDFP Block is present, current POMS can require direct-deposit changes to be made in person rather than through automated channels.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data><data key="edge_notes">Control effect is modeled at the business-rule level; storage location is not inferred.</data></edge><edge id="REL996" source="SVC_TCIS" target="DB_PHUS"><data key="edge_relationship_id">REL996</data><data key="edge_source_entity_id">SVC_TCIS</data><data key="edge_relationship_type">supports_payment_research_with</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">SSA staff use TCIS together with PHUS in check/nonreceipt research and payment-status resolution.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Workflow relationship; no direct TCIS-to-PHUS technical interface is asserted.</data></edge><edge id="REL997" source="SVC_TCIS" target="APP_EP"><data key="edge_relationship_id">REL997</data><data key="edge_source_entity_id">SVC_TCIS</data><data key="edge_relationship_type">claims_documents_stored_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Completed Treasury FMS-1133 claims packages handled by SSA are scanned into Evidence Portal.</data><data key="edge_observed_as_of">2026-04-13</data><data key="edge_confidence">4</data><data key="edge_notes">Human-mediated document workflow, not a direct system integration.</data></edge><edge id="REL998" source="APP_REACT" target="DB_PHUS"><data key="edge_relationship_id">REL998</data><data key="edge_source_entity_id">APP_REACT</data><data key="edge_relationship_type">creates_limited_payability_event_in</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">Current POMS states successful REACT limited-payability processing results in PHUS creating EVENT 169 UNNEG CK.</data><data key="edge_observed_as_of">2026-07-16</data><data key="edge_confidence">5</data></edge><edge id="REL999" source="APP_UPTQ" target="SYS_SSR"><data key="edge_relationship_id">REL999</data><data key="edge_source_entity_id">APP_UPTQ</data><data key="edge_relationship_type">supports_returned_payment_processing_for</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current POMS uses UPTQ in Title XVI returned-payment processing and notes returned funds are posted to SSR depending on Treasury processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data><data key="edge_notes">Business-workflow relationship; POMS explicitly warns UPTQ may not always reflect a return.</data></edge><edge id="REL_R102_001" source="UI_MCS_NOT2" target="APP_MCS"><data key="edge_relationship_id">REL_R102_001</data><data key="edge_source_entity_id">UI_MCS_NOT2</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Current POMS identifies NOT2 as an MCS screen technicians review when adjudicating represented claims.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_002" source="UI_MSSICS_UATH" target="APP_MSSICS"><data key="edge_relationship_id">REL_R102_002</data><data key="edge_source_entity_id">UI_MSSICS_UATH</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS identifies UATH as a MSSICS screen used in represented-claim adjudication.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_003" source="UI_MSSICS_UFEE" target="APP_MSSICS"><data key="edge_relationship_id">REL_R102_003</data><data key="edge_source_entity_id">UI_MSSICS_UFEE</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MSSICS</data><data key="edge_operational_context">Current POMS identifies UFEE as a MSSICS screen used in represented-claim adjudication.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_004" source="UI_MACADE_ATT" target="APP_MACADE"><data key="edge_relationship_id">REL_R102_004</data><data key="edge_source_entity_id">UI_MACADE_ATT</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">Current POMS identifies ATT as a MACADE screen used in represented-claim adjudication.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_005" source="APP_RASR" target="UI_MCS_NOT2"><data key="edge_relationship_id">REL_R102_005</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">UI_MCS_NOT2</data><data key="edge_operational_context">RASR-entered appointment information is followed by technician review of downstream MCS screens to ensure current representative data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_006" source="APP_RASR" target="UI_MSSICS_UATH"><data key="edge_relationship_id">REL_R102_006</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">UI_MSSICS_UATH</data><data key="edge_operational_context">RASR-entered appointment information is followed by technician review of applicable MSSICS screens.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_007" source="APP_RASR" target="UI_MSSICS_UFEE"><data key="edge_relationship_id">REL_R102_007</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">UI_MSSICS_UFEE</data><data key="edge_operational_context">RASR-entered appointment information is followed by technician review of applicable MSSICS screens.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_008" source="APP_RASR" target="UI_MACADE_ATT"><data key="edge_relationship_id">REL_R102_008</data><data key="edge_source_entity_id">APP_RASR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">UI_MACADE_ATT</data><data key="edge_operational_context">RASR-entered appointment information is followed by technician review of applicable MACADE screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_009" source="FORM_SSA1128" target="APP_RASR"><data key="edge_relationship_id">REL_R102_009</data><data key="edge_source_entity_id">FORM_SSA1128</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_RASR</data><data key="edge_operational_context">SSA-1128 flags representative involvement on paper claims while SSA-1696 appointment information is entered into RASR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_010" source="PROC_SSI_EARNED_RZ" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">REL_R102_010</data><data key="edge_source_entity_id">PROC_SSI_EARNED_RZ</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">Opening a REDETERMINATION event in SSI Claims creates the guided path for earned-income development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_011" source="PROC_SSI_EARNED_RZ" target="SYS_SSR"><data key="edge_relationship_id">REL_R102_011</data><data key="edge_source_entity_id">PROC_SSI_EARNED_RZ</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Earned-income development evaluates wage information on the SSR and prior estimates.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_012" source="PROC_SSI_EARNED_RZ" target="SYS_SSR"><data key="edge_relationship_id">REL_R102_012</data><data key="edge_source_entity_id">PROC_SSI_EARNED_RZ</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Current procedure directs staff to input future estimates and verified income during the RZ.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_013" source="APP_SSI_CLAIMS_LOGICAL" target="WORK_SSI_B3_DIARY"><data key="edge_relationship_id">REL_R102_013</data><data key="edge_source_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">WORK_SSI_B3_DIARY</data><data key="edge_operational_context">The system sets a B3 diary when automated netting and/or automated notice processing cannot complete.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_014" source="WORK_SSI_B3_DIARY" target="PROC_SSI_EARNED_RZ"><data key="edge_relationship_id">REL_R102_014</data><data key="edge_source_entity_id">WORK_SSI_B3_DIARY</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">PROC_SSI_EARNED_RZ</data><data key="edge_operational_context">A B3 diary identifies the RZ case for manual netting and/or manual notice action by the field office.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_015" source="PROC_SSI_EARNED_RZ" target="DATA_SSI_U_TAC"><data key="edge_relationship_id">REL_R102_015</data><data key="edge_source_entity_id">PROC_SSI_EARNED_RZ</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_SSI_U_TAC</data><data key="edge_operational_context">Cases requiring manual netting require staff to input a U TAC.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_016" source="APP_UMCCC" target="PROC_UMC_SPECIAL_CDR"><data key="edge_relationship_id">REL_R102_016</data><data key="edge_source_entity_id">APP_UMCCC</data><data key="edge_relationship_type">controls</data><data key="edge_target_entity_id">PROC_UMC_SPECIAL_CDR</data><data key="edge_operational_context">The identified pre-2006 UMC workload is tracked in UMCCC until all required actions are completed and effectuated.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_017" source="APP_UMCCC" target="ORG_SSA_FIELD_OFFICES"><data key="edge_relationship_id">REL_R102_017</data><data key="edge_source_entity_id">APP_UMCCC</data><data key="edge_relationship_type">used_by</data><data key="edge_target_entity_id">ORG_SSA_FIELD_OFFICES</data><data key="edge_operational_context">The field office taking action on the new CDR enters and clears UMC tracking information in UMCCC.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_018" source="PROC_UMC_SPECIAL_CDR" target="UI_DCF_IFOA"><data key="edge_relationship_id">REL_R102_018</data><data key="edge_source_entity_id">PROC_UMC_SPECIAL_CDR</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_DCF_IFOA</data><data key="edge_operational_context">When a prior CDR remains open, staff use IFOA to close it by annotating the prior cessation determination.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_019" source="PROC_UMC_SPECIAL_CDR" target="UI_DCF_IRMK"><data key="edge_relationship_id">REL_R102_019</data><data key="edge_source_entity_id">PROC_UMC_SPECIAL_CDR</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_DCF_IRMK</data><data key="edge_operational_context">Staff use IRMK to document that the UMC cessation determination was set aside.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_020" source="PROC_UMC_SPECIAL_CDR" target="UI_DCF_DRES"><data key="edge_relationship_id">REL_R102_020</data><data key="edge_source_entity_id">PROC_UMC_SPECIAL_CDR</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_DCF_DRES</data><data key="edge_operational_context">Staff use DRES to manually establish the new CDR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_021" source="UI_DCF_IFOA" target="DB_DCF"><data key="edge_relationship_id">REL_R102_021</data><data key="edge_source_entity_id">UI_DCF_IFOA</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">IFOA is a DCF input screen used to record the prior CDR/cessation action.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_022" source="UI_DCF_IRMK" target="DB_DCF"><data key="edge_relationship_id">REL_R102_022</data><data key="edge_source_entity_id">UI_DCF_IRMK</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">IRMK records UMC remarks on the DCF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_023" source="UI_DCF_DRES" target="DB_DCF"><data key="edge_relationship_id">REL_R102_023</data><data key="edge_source_entity_id">UI_DCF_DRES</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">DRES manually establishes the new CDR on the DCF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_024" source="PROC_UMC_SPECIAL_CDR" target="ORG_DDS"><data key="edge_relationship_id">REL_R102_024</data><data key="edge_source_entity_id">PROC_UMC_SPECIAL_CDR</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">ORG_DDS</data><data key="edge_operational_context">After field-office package completion, the new CDR is sent to DDS for adjudication.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_025" source="ORG_CMS" target="EX_MNUP_CMS_NONUTIL"><data key="edge_relationship_id">REL_R102_025</data><data key="edge_source_entity_id">ORG_CMS</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">EX_MNUP_CMS_NONUTIL</data><data key="edge_operational_context">CMS identifies Medicare enrollees with no Part A or Part B use for three or more years for the SSA MNUP process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_026" source="EX_MNUP_CMS_NONUTIL" target="PROC_MNUP"><data key="edge_relationship_id">REL_R102_026</data><data key="edge_source_entity_id">EX_MNUP_CMS_NONUTIL</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">PROC_MNUP</data><data key="edge_operational_context">SSA uses CMS non-utilization data as an indicator to select and prioritize Title II cases for review.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_027" source="PROC_MNUP" target="APP_MNUP_WEBSITE"><data key="edge_relationship_id">REL_R102_027</data><data key="edge_source_entity_id">PROC_MNUP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MNUP_WEBSITE</data><data key="edge_operational_context">Current MNUP procedures require staff to document appointments, interviews, remarks, and case status on the MNUP website.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_028" source="PROC_MNUP" target="SYS_MBR"><data key="edge_relationship_id">REL_R102_028</data><data key="edge_source_entity_id">PROC_MNUP</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Before interview SSA reviews the MBR and resolves discrepancies such as date of birth or address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_029" source="PROC_MNUP" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL_R102_029</data><data key="edge_source_entity_id">PROC_MNUP</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Before interview SSA reviews NUMI/Numident information and resolves discrepancies.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_030" source="PROC_MNUP" target="SYS_SSR"><data key="edge_relationship_id">REL_R102_030</data><data key="edge_source_entity_id">PROC_MNUP</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Before interview SSA may review the SSI record and resolve discrepancies.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_031" source="PROC_MNUP" target="APP_CSRQ"><data key="edge_relationship_id">REL_R102_031</data><data key="edge_source_entity_id">PROC_MNUP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_CSRQ</data><data key="edge_operational_context">Current interview policy directs identity/benefit review using CSRQ as part of MNUP interview work.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Current search result supports CSRQ use; source does not document CSRQ internals.</data></edge><edge id="REL_R102_032" source="FORM_SSA_L501" target="PROC_MNUP"><data key="edge_relationship_id">REL_R102_032</data><data key="edge_source_entity_id">FORM_SSA_L501</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">PROC_MNUP</data><data key="edge_operational_context">SSA-L501 schedules the home-visit interview used in MNUP development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_033" source="FORM_SSA_L502" target="PROC_MNUP"><data key="edge_relationship_id">REL_R102_033</data><data key="edge_source_entity_id">FORM_SSA_L502</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">PROC_MNUP</data><data key="edge_operational_context">SSA-L502 schedules the preferred telephone interview used in MNUP development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_034" source="FORM_SSA_L505" target="PROC_MNUP"><data key="edge_relationship_id">REL_R102_034</data><data key="edge_source_entity_id">FORM_SSA_L505</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">PROC_MNUP</data><data key="edge_operational_context">SSA-L505 requests residence-address information needed for MNUP when only mailing address is available.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_035" source="APP_DPS" target="FORM_SSA_L501"><data key="edge_relationship_id">REL_R102_035</data><data key="edge_source_entity_id">APP_DPS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">FORM_SSA_L501</data><data key="edge_operational_context">Current MNUP policy states interview notices are available in DPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_036" source="APP_DPS" target="FORM_SSA_L502"><data key="edge_relationship_id">REL_R102_036</data><data key="edge_source_entity_id">APP_DPS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">FORM_SSA_L502</data><data key="edge_operational_context">Current MNUP policy states interview notices are available in DPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_037" source="APP_DPS" target="FORM_SSA_L505"><data key="edge_relationship_id">REL_R102_037</data><data key="edge_source_entity_id">APP_DPS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">FORM_SSA_L505</data><data key="edge_operational_context">Current MNUP policy states interview notices are available in DPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_038" source="FORM_SSA_L505" target="DATA_MNUP_RESIDENCE_ADDRESS"><data key="edge_relationship_id">REL_R102_038</data><data key="edge_source_entity_id">FORM_SSA_L505</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">DATA_MNUP_RESIDENCE_ADDRESS</data><data key="edge_operational_context">SSA-L505 is sent specifically to obtain a residence address when only a mailing address is available in SSA records.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_039" source="DATA_MNUP_RESIDENCE_ADDRESS" target="DATA_MNUP_ONLINE_WORKSHEET"><data key="edge_relationship_id">REL_R102_039</data><data key="edge_source_entity_id">DATA_MNUP_RESIDENCE_ADDRESS</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">DATA_MNUP_ONLINE_WORKSHEET</data><data key="edge_operational_context">Current foreign-address procedure requires the FO to update the new address and phone number in the MNUP online worksheet; domestic residence development is also documented in the MNUP workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Do not infer an automatic MBR/SSR update from worksheet storage.</data></edge><edge id="REL_R102_040" source="DATA_MNUP_ONLINE_WORKSHEET" target="APP_MNUP_WEBSITE"><data key="edge_relationship_id">REL_R102_040</data><data key="edge_source_entity_id">DATA_MNUP_ONLINE_WORKSHEET</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_MNUP_WEBSITE</data><data key="edge_operational_context">Interview information is transcribed into the online worksheet on the MNUP website.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_041" source="APP_MNUP_WEBSITE" target="DATA_MNUP_HIST_SUMMARY"><data key="edge_relationship_id">REL_R102_041</data><data key="edge_source_entity_id">APP_MNUP_WEBSITE</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">DATA_MNUP_HIST_SUMMARY</data><data key="edge_operational_context">Older still-active website policy states the MNUP site maintains historical summary-level data after interview entry.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Retention duration and physical store are not stated.</data></edge><edge id="REL_R102_042" source="APP_MNUP_WEBSITE" target="UI_MNUP_TRANSFER"><data key="edge_relationship_id">REL_R102_042</data><data key="edge_source_entity_id">APP_MNUP_WEBSITE</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">UI_MNUP_TRANSFER</data><data key="edge_operational_context">Current policy names a TRANSFER facility on the MNUP website for moving cases to a new servicing FO.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_043" source="PROC_MNUP" target="WORK_MNUP_15_DAY_DIARY"><data key="edge_relationship_id">REL_R102_043</data><data key="edge_source_entity_id">PROC_MNUP</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">WORK_MNUP_15_DAY_DIARY</data><data key="edge_operational_context">After a third failed appointment, SSA establishes a 15-day due-process diary before suspension.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_044" source="PROC_MNUP" target="APP_ARIS"><data key="edge_relationship_id">REL_R102_044</data><data key="edge_source_entity_id">PROC_MNUP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ARIS</data><data key="edge_operational_context">When benefits are suspended for failure to keep MNUP appointments, staff immediately refer the case to OIG through ARIS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_045" source="PROC_MNUP" target="PROC_MNUP_FOREIGN_COA"><data key="edge_relationship_id">REL_R102_045</data><data key="edge_source_entity_id">PROC_MNUP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_MNUP_FOREIGN_COA</data><data key="edge_operational_context">If MNUP discovers the beneficiary resides abroad, staff shift into the foreign-address verification and change-of-address development flow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_046" source="PROC_MNUP_FOREIGN_COA" target="ORG_SSA_OEIO"><data key="edge_relationship_id">REL_R102_046</data><data key="edge_source_entity_id">PROC_MNUP_FOREIGN_COA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">ORG_SSA_OEIO</data><data key="edge_operational_context">For specified foreign residences, FO sends the case to OEIO, which confirms residence and inputs the applicable change of address.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_047" source="PROC_MNUP_FOREIGN_COA" target="FORM_R96_SSA21"><data key="edge_relationship_id">REL_R102_047</data><data key="edge_source_entity_id">PROC_MNUP_FOREIGN_COA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_R96_SSA21</data><data key="edge_operational_context">The estimated date of foreign-address change serves as an indicator for SSA-21 in the OEIO development.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_048" source="PROC_MNUP_FOREIGN_COA" target="DATA_MNUP_ONLINE_WORKSHEET"><data key="edge_relationship_id">REL_R102_048</data><data key="edge_source_entity_id">PROC_MNUP_FOREIGN_COA</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DATA_MNUP_ONLINE_WORKSHEET</data><data key="edge_operational_context">After OEIO response, the FO updates the foreign address, phone, LAF status, remarks, and completion status on the MNUP worksheet.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_049" source="PROC_MNUP_FOREIGN_COA" target="DATA_MBR_MNUP_SPECIAL_MESSAGE"><data key="edge_relationship_id">REL_R102_049</data><data key="edge_source_entity_id">PROC_MNUP_FOREIGN_COA</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_MBR_MNUP_SPECIAL_MESSAGE</data><data key="edge_operational_context">Current policy directs staff to post a specific MNUP foreign-COA Special Message to the MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_050" source="DATA_MBR_MNUP_SPECIAL_MESSAGE" target="SYS_MBR"><data key="edge_relationship_id">REL_R102_050</data><data key="edge_source_entity_id">DATA_MBR_MNUP_SPECIAL_MESSAGE</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The MNUP foreign change-of-address Special Message is explicitly posted to the MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R102_051" source="DATA_OACT_DISABLED_AGE_SEX_202606" target="DATA_OACT_PRIMARY_BEN_AGE_SEX_2026"><data key="edge_relationship_id">REL_R102_051</data><data key="edge_source_entity_id">DATA_OACT_DISABLED_AGE_SEX_202606</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">DATA_OACT_PRIMARY_BEN_AGE_SEX_2026</data><data key="edge_operational_context">The primary-beneficiary age/sex product links to detailed disabled-worker data for June 30, 2026.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R103_0001" source="FORM_SSA4547" target="APP_ADRP"><data key="edge_relationship_id">REL_R103_0001</data><data key="edge_source_entity_id">FORM_SSA4547</data><data key="edge_relationship_type">supplies_information_to</data><data key="edge_target_entity_id">APP_ADRP</data><data key="edge_operational_context">SSA-4547 is a form channel for entering or updating ADRP information.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-4547 is a form channel for entering or updating ADRP information.</data></edge><edge id="REL_R103_0002" source="APP_MYSSA" target="APP_ADRP"><data key="edge_relationship_id">REL_R103_0002</data><data key="edge_source_entity_id">APP_MYSSA</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">APP_ADRP</data><data key="edge_operational_context">APP_MYSSA is a documented channel or technician route for ADRP; exact technical integration is not disclosed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">APP_MYSSA is a documented channel or technician route for ADRP; exact technical integration is not disclosed.</data></edge><edge id="REL_R103_0003" source="APP_ICLAIM" target="APP_ADRP"><data key="edge_relationship_id">REL_R103_0003</data><data key="edge_source_entity_id">APP_ICLAIM</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">APP_ADRP</data><data key="edge_operational_context">APP_ICLAIM is a documented channel or technician route for ADRP; exact technical integration is not disclosed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">APP_ICLAIM is a documented channel or technician route for ADRP; exact technical integration is not disclosed.</data></edge><edge id="REL_R103_0004" source="APP_MCS" target="APP_ADRP"><data key="edge_relationship_id">REL_R103_0004</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">APP_ADRP</data><data key="edge_operational_context">APP_MCS is a documented channel or technician route for ADRP; exact technical integration is not disclosed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">APP_MCS is a documented channel or technician route for ADRP; exact technical integration is not disclosed.</data></edge><edge id="REL_R103_0005" source="APP_IMAIN" target="APP_ADRP"><data key="edge_relationship_id">REL_R103_0005</data><data key="edge_source_entity_id">APP_IMAIN</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">APP_ADRP</data><data key="edge_operational_context">APP_IMAIN is a documented channel or technician route for ADRP; exact technical integration is not disclosed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">APP_IMAIN is a documented channel or technician route for ADRP; exact technical integration is not disclosed.</data></edge><edge id="REL_R103_0006" source="APP_ADRP" target="DATA_ADRP_DESIGNEE_INFO"><data key="edge_relationship_id">REL_R103_0006</data><data key="edge_source_entity_id">APP_ADRP</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">DATA_ADRP_DESIGNEE_INFO</data><data key="edge_operational_context">ADRP records ordered advance designee attributes and update dates and does not collect designee SSNs.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">ADRP records ordered advance designee attributes and update dates and does not collect designee SSNs.</data></edge><edge id="REL_R103_0007" source="UI_ADRP_DOCUMENT_CONTACT" target="APP_ADRP"><data key="edge_relationship_id">REL_R103_0007</data><data key="edge_source_entity_id">UI_ADRP_DOCUMENT_CONTACT</data><data key="edge_relationship_type">interface_of</data><data key="edge_target_entity_id">APP_ADRP</data><data key="edge_operational_context">ADRP Document Contact is reached through iMain.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">ADRP Document Contact is reached through iMain.</data></edge><edge id="REL_R103_0008" source="APP_IMAIN" target="UI_ADRP_DOCUMENT_CONTACT"><data key="edge_relationship_id">REL_R103_0008</data><data key="edge_source_entity_id">APP_IMAIN</data><data key="edge_relationship_type">provides_access_to</data><data key="edge_target_entity_id">UI_ADRP_DOCUMENT_CONTACT</data><data key="edge_operational_context">iMain intranet access is required for Document Contact page.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">iMain intranet access is required for Document Contact page.</data></edge><edge id="REL_R103_0009" source="UI_ADRP_DOCUMENT_CONTACT" target="DATA_ADRP_CONTACT_HISTORY"><data key="edge_relationship_id">REL_R103_0009</data><data key="edge_source_entity_id">UI_ADRP_DOCUMENT_CONTACT</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">DATA_ADRP_CONTACT_HISTORY</data><data key="edge_operational_context">Contact documentation is automatically written to the ADRP Contact History table.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Contact documentation is automatically written to the ADRP Contact History table.</data></edge><edge id="REL_R103_0010" source="PROC_ADRP_CONTACT" target="UI_ADRP_DOCUMENT_CONTACT"><data key="edge_relationship_id">REL_R103_0010</data><data key="edge_source_entity_id">PROC_ADRP_CONTACT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_ADRP_DOCUMENT_CONTACT</data><data key="edge_operational_context">SSA technicians document contact attempts and selection information in the Document Contact page.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA technicians document contact attempts and selection information in the Document Contact page.</data></edge><edge id="REL_R103_0011" source="PROC_ADRP_CONTACT" target="DATA_ADRP_DESIGNEE_INFO"><data key="edge_relationship_id">REL_R103_0011</data><data key="edge_source_entity_id">PROC_ADRP_CONTACT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_ADRP_DESIGNEE_INFO</data><data key="edge_operational_context">Contacts are attempted in order of beneficiary priority; limited contact details are available.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Contacts are attempted in order of beneficiary priority; limited contact details are available.</data></edge><edge id="REL_R103_0012" source="APP_ADRP" target="NOTICE_ADRP_ANNUAL"><data key="edge_relationship_id">REL_R103_0012</data><data key="edge_source_entity_id">APP_ADRP</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">NOTICE_ADRP_ANNUAL</data><data key="edge_operational_context">ADRP supports automated annual notice to beneficiaries with advance designee(s) and no payee.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">ADRP supports automated annual notice to beneficiaries with advance designee(s) and no payee.</data></edge><edge id="REL_R103_0013" source="APP_ADRP" target="DATA_ADRP_OR_RECEIPT"><data key="edge_relationship_id">REL_R103_0013</data><data key="edge_source_entity_id">APP_ADRP</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_ADRP_OR_RECEIPT</data><data key="edge_operational_context">ADRP transaction receipts continue to be stored in ORS after July 2025 print-mail change.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">ADRP transaction receipts continue to be stored in ORS after July 2025 print-mail change.</data></edge><edge id="REL_R103_0014" source="DATA_ADRP_OR_RECEIPT" target="APP_ORS"><data key="edge_relationship_id">REL_R103_0014</data><data key="edge_source_entity_id">DATA_ADRP_OR_RECEIPT</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Advance designation receipt is stored in Online Retrieval System.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Advance designation receipt is stored in Online Retrieval System.</data></edge><edge id="REL_R103_0015" source="PROC_ADRP_CONTACT" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0015</data><data key="edge_source_entity_id">PROC_ADRP_CONTACT</data><data key="edge_relationship_type">informs_selection_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Payee selection documents consideration of advance designees in eRPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Payee selection documents consideration of advance designees in eRPS.</data></edge><edge id="REL_R103_0016" source="UI_ERPS_MERGE_ORGANIZATION" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0016</data><data key="edge_source_entity_id">UI_ERPS_MERGE_ORGANIZATION</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">UI_ERPS_MERGE_ORGANIZATION is explicitly named as an eRPS screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">UI_ERPS_MERGE_ORGANIZATION is explicitly named as an eRPS screen.</data></edge><edge id="REL_R103_0017" source="UI_ERPS_PENDING_APPLICATIONS" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0017</data><data key="edge_source_entity_id">UI_ERPS_PENDING_APPLICATIONS</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">UI_ERPS_PENDING_APPLICATIONS is explicitly named as an eRPS screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">UI_ERPS_PENDING_APPLICATIONS is explicitly named as an eRPS screen.</data></edge><edge id="REL_R103_0018" source="UI_ERPS_SELECTED_LIST" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0018</data><data key="edge_source_entity_id">UI_ERPS_SELECTED_LIST</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">UI_ERPS_SELECTED_LIST is explicitly named as an eRPS screen.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">UI_ERPS_SELECTED_LIST is explicitly named as an eRPS screen.</data></edge><edge id="REL_R103_0019" source="PROC_ERPS_ORG_MASS_CHANGE" target="UI_ERPS_PENDING_APPLICATIONS"><data key="edge_relationship_id">REL_R103_0019</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_ERPS_PENDING_APPLICATIONS</data><data key="edge_operational_context">Mass organizational payee transition uses UI_ERPS_PENDING_APPLICATIONS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mass organizational payee transition uses UI_ERPS_PENDING_APPLICATIONS.</data></edge><edge id="REL_R103_0020" source="PROC_ERPS_ORG_MASS_CHANGE" target="UI_ERPS_SELECTED_LIST"><data key="edge_relationship_id">REL_R103_0020</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_ERPS_SELECTED_LIST</data><data key="edge_operational_context">Mass organizational payee transition uses UI_ERPS_SELECTED_LIST.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mass organizational payee transition uses UI_ERPS_SELECTED_LIST.</data></edge><edge id="REL_R103_0021" source="PROC_ERPS_ORG_MASS_CHANGE" target="UI_ERPS_MERGE_ORGANIZATION"><data key="edge_relationship_id">REL_R103_0021</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_ERPS_MERGE_ORGANIZATION</data><data key="edge_operational_context">Mass organizational payee transition uses UI_ERPS_MERGE_ORGANIZATION.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mass organizational payee transition uses UI_ERPS_MERGE_ORGANIZATION.</data></edge><edge id="REL_R103_0022" source="PROC_ERPS_ORG_MASS_CHANGE" target="WORK_ERPS_MASS_15_DAY"><data key="edge_relationship_id">REL_R103_0022</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">WORK_ERPS_MASS_15_DAY</data><data key="edge_operational_context">Mass organizational payee transition uses WORK_ERPS_MASS_15_DAY.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mass organizational payee transition uses WORK_ERPS_MASS_15_DAY.</data></edge><edge id="REL_R103_0023" source="PROC_ERPS_ORG_MASS_CHANGE" target="FORM_SSA11BK"><data key="edge_relationship_id">REL_R103_0023</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA11BK</data><data key="edge_operational_context">Mass payee transition requires one SSA-11 application and beneficiary list.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mass payee transition requires one SSA-11 application and beneficiary list.</data></edge><edge id="REL_R103_0024" source="PROC_ERPS_ORG_MASS_CHANGE" target="UI_ERPS_BENEFICIARY_ADDRESS_CHANGE"><data key="edge_relationship_id">REL_R103_0024</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_ERPS_BENEFICIARY_ADDRESS_CHANGE</data><data key="edge_operational_context">When beneficiary residence address changed during organization transition staff use the eRPS Beneficiary Address Change screen; no automatic MBR/SSR write inferred.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">When beneficiary residence address changed during organization transition staff use the eRPS Beneficiary Address Change screen; no automatic MBR/SSR write inferred.</data></edge><edge id="REL_R103_0025" source="DATA_ERPS_PAYEE_ORG_ADDRESS" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0025</data><data key="edge_source_entity_id">DATA_ERPS_PAYEE_ORG_ADDRESS</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Organization-level address and payee-legend updates handled in eRPS without a payee-selection change when organization continues.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Organization-level address and payee-legend updates handled in eRPS without a payee-selection change when organization continues.</data></edge><edge id="REL_R103_0026" source="PROC_ERPS_ORG_MASS_CHANGE" target="REPO_NDRED"><data key="edge_relationship_id">REL_R103_0026</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">stores_evidence_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">SSA-11 mass change evidence can be stored in NDRed under SSN of first beneficiary on list.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-11 mass change evidence can be stored in NDRed under SSN of first beneficiary on list.</data></edge><edge id="REL_R103_0027" source="PROC_ERPS_ORG_MASS_CHANGE" target="APP_EVIEW"><data key="edge_relationship_id">REL_R103_0027</data><data key="edge_source_entity_id">PROC_ERPS_ORG_MASS_CHANGE</data><data key="edge_relationship_type">stores_evidence_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">SSA-11 may alternatively be stored in eView via Evidence Portal.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-11 may alternatively be stored in eView via Evidence Portal.</data></edge><edge id="REL_R103_0028" source="UI_ERPS_RELATIONSHIP_DETAILS" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0028</data><data key="edge_source_entity_id">UI_ERPS_RELATIONSHIP_DETAILS</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Relationship Details is an eRPS documentation tab.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Relationship Details is an eRPS documentation tab.</data></edge><edge id="REL_R103_0029" source="UI_ERPS_RELATIONSHIP_DETAILS" target="DATA_ERPS_ABLE_TITLE_NOTE"><data key="edge_relationship_id">REL_R103_0029</data><data key="edge_source_entity_id">UI_ERPS_RELATIONSHIP_DETAILS</data><data key="edge_relationship_type">stores</data><data key="edge_target_entity_id">DATA_ERPS_ABLE_TITLE_NOTE</data><data key="edge_operational_context">Document payee fiduciary ownership and titling of ABLE accounts in eRPS relationship notes.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Document payee fiduciary ownership and titling of ABLE accounts in eRPS relationship notes.</data></edge><edge id="REL_R103_0030" source="PROC_PAYEE_MEDICAL_CONFIRMATION" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0030</data><data key="edge_source_entity_id">PROC_PAYEE_MEDICAL_CONFIRMATION</data><data key="edge_relationship_type">documents_in</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Medical evidence confirmation documented in eRPS RPOC when case is established.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Medical evidence confirmation documented in eRPS RPOC when case is established.</data></edge><edge id="REL_R103_0031" source="PROC_PAYEE_MEDICAL_CONFIRMATION" target="APP_MCS"><data key="edge_relationship_id">REL_R103_0031</data><data key="edge_source_entity_id">PROC_PAYEE_MEDICAL_CONFIRMATION</data><data key="edge_relationship_type">documents_in</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Title II cases outside eRPS use MCS Report of Contact.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title II cases outside eRPS use MCS Report of Contact.</data></edge><edge id="REL_R103_0032" source="PROC_PAYEE_MEDICAL_CONFIRMATION" target="APP_CCE"><data key="edge_relationship_id">REL_R103_0032</data><data key="edge_source_entity_id">PROC_PAYEE_MEDICAL_CONFIRMATION</data><data key="edge_relationship_type">documents_in</data><data key="edge_target_entity_id">APP_CCE</data><data key="edge_operational_context">Title XVI cases outside eRPS use CCE Report of Contact.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title XVI cases outside eRPS use CCE Report of Contact.</data></edge><edge id="REL_R103_0033" source="PROC_PAYEE_MEDICAL_CONFIRMATION" target="REPO_NDRED"><data key="edge_relationship_id">REL_R103_0033</data><data key="edge_source_entity_id">PROC_PAYEE_MEDICAL_CONFIRMATION</data><data key="edge_relationship_type">retains_fallback_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Use SSA-5002 in NDRed or eView if no system RPOC possible.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Use SSA-5002 in NDRed or eView if no system RPOC possible.</data></edge><edge id="REL_R103_0034" source="PROC_PAYEE_MEDICAL_CONFIRMATION" target="APP_EVIEW"><data key="edge_relationship_id">REL_R103_0034</data><data key="edge_source_entity_id">PROC_PAYEE_MEDICAL_CONFIRMATION</data><data key="edge_relationship_type">retains_fallback_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Use SSA-5002 in eView if no system RPOC possible.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Use SSA-5002 in eView if no system RPOC possible.</data></edge><edge id="REL_R103_0035" source="PROC_T2_REINSTATE_PAYEE_T2R" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0035</data><data key="edge_source_entity_id">PROC_T2_REINSTATE_PAYEE_T2R</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">Representative payee selection is initiated in eRPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Representative payee selection is initiated in eRPS.</data></edge><edge id="REL_R103_0036" source="APP_ERPS" target="APP_T2R"><data key="edge_relationship_id">REL_R103_0036</data><data key="edge_source_entity_id">APP_ERPS</data><data key="edge_relationship_type">passes_selection_through</data><data key="edge_target_entity_id">APP_T2R</data><data key="edge_operational_context">SSA explicitly says selected payee passes through T2R to MBR for some S-6/S-8 reinstatements.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA explicitly says selected payee passes through T2R to MBR for some S-6/S-8 reinstatements.</data></edge><edge id="REL_R103_0037" source="PROC_T2_REINSTATE_PAYEE_T2R" target="APP_POS"><data key="edge_relationship_id">REL_R103_0037</data><data key="edge_source_entity_id">PROC_T2_REINSTATE_PAYEE_T2R</data><data key="edge_relationship_type">conditionally_requires</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">S-9 whereabouts unknown needs separate POS reinstatement after eRPS payee selection is posted to MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">S-9 whereabouts unknown needs separate POS reinstatement after eRPS payee selection is posted to MBR.</data></edge><edge id="REL_R103_0038" source="WORK_ERPS_TERMINATED_RELATIONSHIP" target="APP_ERPS"><data key="edge_relationship_id">REL_R103_0038</data><data key="edge_source_entity_id">WORK_ERPS_TERMINATED_RELATIONSHIP</data><data key="edge_relationship_type">generated_by</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">eRPS alert reflects terminated payee relationship following certain Title II processing-center reinstatements.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">eRPS alert reflects terminated payee relationship following certain Title II processing-center reinstatements.</data></edge><edge id="REL_R103_0039" source="APP_MACADE" target="WORK_ERPS_TERMINATED_RELATIONSHIP"><data key="edge_relationship_id">REL_R103_0039</data><data key="edge_source_entity_id">APP_MACADE</data><data key="edge_relationship_type">may_trigger</data><data key="edge_target_entity_id">WORK_ERPS_TERMINATED_RELATIONSHIP</data><data key="edge_operational_context">MACADE reinstatement from termination with same payee may cause eRPS alert for FO correction.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MACADE reinstatement from termination with same payee may cause eRPS alert for FO correction.</data></edge><edge id="REL_R103_0040" source="DATA_USPS_119TH_CONG_GEO" target="ORG_USPS"><data key="edge_relationship_id">REL_R103_0040</data><data key="edge_source_entity_id">DATA_USPS_119TH_CONG_GEO</data><data key="edge_relationship_type">supplied_by</data><data key="edge_target_entity_id">ORG_USPS</data><data key="edge_operational_context">SSA publication explicitly attributes geographic district input to USPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA publication explicitly attributes geographic district input to USPS.</data></edge><edge id="REL_R103_0041" source="DATA_CONG_OASDI_2025" target="SYS_MBR"><data key="edge_relationship_id">REL_R103_0041</data><data key="edge_source_entity_id">DATA_CONG_OASDI_2025</data><data key="edge_relationship_type">derives_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA 2025 congressional OASDI table cites MBR 100-percent administrative data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA 2025 congressional OASDI table cites MBR 100-percent administrative data.</data></edge><edge id="REL_R103_0042" source="DATA_CONG_SSI_2025" target="SYS_SSR"><data key="edge_relationship_id">REL_R103_0042</data><data key="edge_source_entity_id">DATA_CONG_SSI_2025</data><data key="edge_relationship_type">derives_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">SSA 2025 congressional SSI table cites SSR 100-percent administrative data.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA 2025 congressional SSI table cites SSR 100-percent administrative data.</data></edge><edge id="REL_R103_0043" source="DATA_CONG_OASDI_2025" target="DATA_USPS_119TH_CONG_GEO"><data key="edge_relationship_id">REL_R103_0043</data><data key="edge_source_entity_id">DATA_CONG_OASDI_2025</data><data key="edge_relationship_type">uses_geographic_data</data><data key="edge_target_entity_id">DATA_USPS_119TH_CONG_GEO</data><data key="edge_operational_context">SSA publication cites USPS geographic data based on 119th Congress district definitions; field-level joins unknown.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA publication cites USPS geographic data based on 119th Congress district definitions; field-level joins unknown.</data></edge><edge id="REL_R103_0044" source="DATA_CONGRESSIONAL_STATS_2025" target="DATA_CONG_OASDI_2025"><data key="edge_relationship_id">REL_R103_0044</data><data key="edge_source_entity_id">DATA_CONGRESSIONAL_STATS_2025</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_CONG_OASDI_2025</data><data key="edge_operational_context">2025 Congressional Statistics publication presents a program-specific district table.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">2025 Congressional Statistics publication presents a program-specific district table.</data></edge><edge id="REL_R103_0045" source="DATA_CONG_SSI_2025" target="DATA_USPS_119TH_CONG_GEO"><data key="edge_relationship_id">REL_R103_0045</data><data key="edge_source_entity_id">DATA_CONG_SSI_2025</data><data key="edge_relationship_type">uses_geographic_data</data><data key="edge_target_entity_id">DATA_USPS_119TH_CONG_GEO</data><data key="edge_operational_context">SSA publication cites USPS geographic data based on 119th Congress district definitions; field-level joins unknown.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA publication cites USPS geographic data based on 119th Congress district definitions; field-level joins unknown.</data></edge><edge id="REL_R103_0046" source="DATA_CONGRESSIONAL_STATS_2025" target="DATA_CONG_SSI_2025"><data key="edge_relationship_id">REL_R103_0046</data><data key="edge_source_entity_id">DATA_CONGRESSIONAL_STATS_2025</data><data key="edge_relationship_type">contains</data><data key="edge_target_entity_id">DATA_CONG_SSI_2025</data><data key="edge_operational_context">2025 Congressional Statistics publication presents a program-specific district table.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">2025 Congressional Statistics publication presents a program-specific district table.</data></edge><edge id="REL_R103_0047" source="APP_UIPATH_ASSISTANT_PC" target="TECH_UIPATH_RPA"><data key="edge_relationship_id">REL_R103_0047</data><data key="edge_source_entity_id">APP_UIPATH_ASSISTANT_PC</data><data key="edge_relationship_type">built_on</data><data key="edge_target_entity_id">TECH_UIPATH_RPA</data><data key="edge_operational_context">UiPath Assistant is a platform built on vendor-identified UiPath automation technology.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">UiPath Assistant is a platform built on vendor-identified UiPath automation technology.</data></edge><edge id="REL_R103_0048" source="PROC_PC_RPA" target="TECH_UIPATH_RPA"><data key="edge_relationship_id">REL_R103_0048</data><data key="edge_source_entity_id">PROC_PC_RPA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_UIPATH_RPA</data><data key="edge_operational_context">SSA expressly reports UiPath bots for processing-center workloads.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA expressly reports UiPath bots for processing-center workloads.</data></edge><edge id="REL_R103_0049" source="PROC_PC_RPA" target="APP_UIPATH_ASSISTANT_PC"><data key="edge_relationship_id">REL_R103_0049</data><data key="edge_source_entity_id">PROC_PC_RPA</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_UIPATH_ASSISTANT_PC</data><data key="edge_operational_context">UiPath Assistant was deployed to PC staff for RPA interaction in August 2025.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">UiPath Assistant was deployed to PC staff for RPA interaction in August 2025.</data></edge><edge id="REL_R103_0050" source="APP_WORKSMART" target="PROJ_WORK_CDR"><data key="edge_relationship_id">REL_R103_0050</data><data key="edge_source_entity_id">APP_WORKSMART</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROJ_WORK_CDR</data><data key="edge_operational_context">WorkSmart alerts potentially overpaid DI beneficiary cases for work CDRs.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">WorkSmart alerts potentially overpaid DI beneficiary cases for work CDRs.</data></edge><edge id="REL_R103_0051" source="APP_WORKSMART" target="EX_PIE"><data key="edge_relationship_id">REL_R103_0051</data><data key="edge_source_entity_id">APP_WORKSMART</data><data key="edge_relationship_type">may_use_authorized_data_from</data><data key="edge_target_entity_id">EX_PIE</data><data key="edge_operational_context">With appropriate authorization WorkSmart may utilize PIE data for CDR targeting; do not model unconditional completed integration.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">With appropriate authorization WorkSmart may utilize PIE data for CDR targeting; do not model unconditional completed integration.</data></edge><edge id="REL_R103_0052" source="PROC_TARGETED_WORK_REVIEW" target="PROJ_WORK_CDR"><data key="edge_relationship_id">REL_R103_0052</data><data key="edge_source_entity_id">PROC_TARGETED_WORK_REVIEW</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROJ_WORK_CDR</data><data key="edge_operational_context">TWRP is an operational alternative path within work CDR processing launched July 2025.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">TWRP is an operational alternative path within work CDR processing launched July 2025.</data></edge><edge id="REL_R103_0053" source="APP_CDREO" target="DB_DCF"><data key="edge_relationship_id">REL_R103_0053</data><data key="edge_source_entity_id">APP_CDREO</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">DB_DCF</data><data key="edge_operational_context">2017 PIA says DCF controls CDREO operation that alerts post-disability work earnings; current implementation requires validation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">2017 PIA says DCF controls CDREO operation that alerts post-disability work earnings; current implementation requires validation.</data></edge><edge id="REL_R103_0054" source="APP_IDMS_DIS" target="APP_DCFS"><data key="edge_relationship_id">REL_R103_0054</data><data key="edge_source_entity_id">APP_IDMS_DIS</data><data key="edge_relationship_type">comprises</data><data key="edge_target_entity_id">APP_DCFS</data><data key="edge_operational_context">2017 PIA identifies DCFS as subsystem of IDMS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">2017 PIA identifies DCFS as subsystem of IDMS.</data></edge><edge id="REL_R103_0055" source="APP_IDMS_DIS" target="APP_EWORK"><data key="edge_relationship_id">REL_R103_0055</data><data key="edge_source_entity_id">APP_IDMS_DIS</data><data key="edge_relationship_type">comprises</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">2017 PIA identifies eWork as subsystem of IDMS; historical architecture.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">2017 PIA identifies eWork as subsystem of IDMS; historical architecture.</data></edge><edge id="REL_R103_0056" source="APP_IDMS_DIS" target="APP_CDREO"><data key="edge_relationship_id">REL_R103_0056</data><data key="edge_source_entity_id">APP_IDMS_DIS</data><data key="edge_relationship_type">comprises</data><data key="edge_target_entity_id">APP_CDREO</data><data key="edge_operational_context">2017 PIA identifies CDREO among disability management subsystems.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">2017 PIA identifies CDREO among disability management subsystems.</data></edge><edge id="REL_R103_0057" source="DB_DCF" target="SYS_MBR"><data key="edge_relationship_id">REL_R103_0057</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">historically_reads_and_updates_according_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">2017 PIA says DCF reads and updates according to MBR, SSR and MEF; exact direction on individual fields is unspecified.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">2017 PIA says DCF reads and updates according to MBR, SSR and MEF; exact direction on individual fields is unspecified.</data></edge><edge id="REL_R103_0058" source="DB_DCF" target="SYS_SSR"><data key="edge_relationship_id">REL_R103_0058</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">historically_reads_and_updates_according_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">2017 PIA says DCF reads and updates according to MBR, SSR and MEF; exact direction on individual fields is unspecified.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">2017 PIA says DCF reads and updates according to MBR, SSR and MEF; exact direction on individual fields is unspecified.</data></edge><edge id="REL_R103_0059" source="DB_DCF" target="SYS_MEF"><data key="edge_relationship_id">REL_R103_0059</data><data key="edge_source_entity_id">DB_DCF</data><data key="edge_relationship_type">historically_reads_and_updates_according_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">2017 PIA says DCF reads and updates according to MBR, SSR and MEF; exact direction on individual fields is unspecified.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">2017 PIA says DCF reads and updates according to MBR, SSR and MEF; exact direction on individual fields is unspecified.</data></edge><edge id="REL_R103_0060" source="DATA_SDX_PAYMENT_STATUS" target="EX_SDX"><data key="edge_relationship_id">REL_R103_0060</data><data key="edge_source_entity_id">DATA_SDX_PAYMENT_STATUS</data><data key="edge_relationship_type">distributed_via</data><data key="edge_target_entity_id">EX_SDX</data><data key="edge_operational_context">SDX carries SSI payment/nonpayment status for State Medicaid eligibility action.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SDX carries SSI payment/nonpayment status for State Medicaid eligibility action.</data></edge><edge id="REL_R103_0061" source="DATA_SDX_PAYMENT_STATUS" target="SYS_SSR"><data key="edge_relationship_id">REL_R103_0061</data><data key="edge_source_entity_id">DATA_SDX_PAYMENT_STATUS</data><data key="edge_relationship_type">derives_from</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Payment status is an SSI administrative field shown to State through SDX; field extraction details are undisclosed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Payment status is an SSI administrative field shown to State through SDX; field extraction details are undisclosed.</data></edge><edge id="REL_R103_0062" source="PROC_CDB_MEDICAID_SDX" target="EX_SDX"><data key="edge_relationship_id">REL_R103_0062</data><data key="edge_source_entity_id">PROC_CDB_MEDICAID_SDX</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">EX_SDX</data><data key="edge_operational_context">SSA notifies 1634 States of continuing Medicaid eligibility group via SDX.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA notifies 1634 States of continuing Medicaid eligibility group via SDX.</data></edge><edge id="REL_R103_0063" source="DATA_NUMI_BIRTH_CERTIFICATE_NUMBER" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL_R103_0063</data><data key="edge_source_entity_id">DATA_NUMI_BIRTH_CERTIFICATE_NUMBER</data><data key="edge_relationship_type">stored_or_displayed_in</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Illinois POMS identifies BCN field of Numident; describes number formatting variants.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Illinois POMS identifies BCN field of Numident; describes number formatting variants.</data></edge><edge id="REL_R103_0064" source="PROC_IL_BIRTH_EVVE" target="DATA_NUMI_BIRTH_CERTIFICATE_NUMBER"><data key="edge_relationship_id">REL_R103_0064</data><data key="edge_source_entity_id">PROC_IL_BIRTH_EVVE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_NUMI_BIRTH_CERTIFICATE_NUMBER</data><data key="edge_operational_context">BCN formatting comparison helps prepare EVVE searches.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">BCN formatting comparison helps prepare EVVE searches.</data></edge><edge id="REL_R103_0065" source="PROC_IL_BIRTH_EVVE" target="SVC_EVVE"><data key="edge_relationship_id">REL_R103_0065</data><data key="edge_source_entity_id">PROC_IL_BIRTH_EVVE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_EVVE</data><data key="edge_operational_context">Illinois staff use EVVE to verify birth records; no birth identity record auto-update implied.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Illinois staff use EVVE to verify birth records; no birth identity record auto-update implied.</data></edge><edge id="REL_R103_0066" source="PROC_PA_EVVE_FALLBACK" target="SVC_EVVE"><data key="edge_relationship_id">REL_R103_0066</data><data key="edge_source_entity_id">PROC_PA_EVVE_FALLBACK</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_EVVE</data><data key="edge_operational_context">PA birth-verification workflow attempts EVVE before manual document request if unsuccessful.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">PA birth-verification workflow attempts EVVE before manual document request if unsuccessful.</data></edge><edge id="REL_R103_0067" source="UI_MCS_ADDB" target="APP_MCS"><data key="edge_relationship_id">REL_R103_0067</data><data key="edge_source_entity_id">UI_MCS_ADDB</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Legacy ADDB initial pension questions appear in MCS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Legacy ADDB initial pension questions appear in MCS.</data></edge><edge id="REL_R103_0068" source="UI_MCS_GPOD" target="APP_MCS"><data key="edge_relationship_id">REL_R103_0068</data><data key="edge_source_entity_id">UI_MCS_GPOD</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_MCS</data><data key="edge_operational_context">Legacy GPOD screen on MCS holds GPO determinations pre-2024 applicability.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Legacy GPOD screen on MCS holds GPO determinations pre-2024 applicability.</data></edge><edge id="REL_R103_0069" source="UI_MCS_GPOD" target="APP_MACADE"><data key="edge_relationship_id">REL_R103_0069</data><data key="edge_source_entity_id">UI_MCS_GPOD</data><data key="edge_relationship_type">historically_propagated_to</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">When the PC received A101, GPOD info propagated to MACADE under documented manual limitations; historical only.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">When the PC received A101, GPOD info propagated to MACADE under documented manual limitations; historical only.</data></edge><edge id="REL_R103_0070" source="DATA_MBR_FUT_PENSION_ENT" target="SYS_MBR"><data key="edge_relationship_id">REL_R103_0070</data><data key="edge_source_entity_id">DATA_MBR_FUT_PENSION_ENT</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Legacy MBR future pension entitlement date triggers later RETAP alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Legacy MBR future pension entitlement date triggers later RETAP alert.</data></edge><edge id="REL_R103_0071" source="PROC_RETAP" target="WORK_RETAP_FUT_PENSION"><data key="edge_relationship_id">REL_R103_0071</data><data key="edge_source_entity_id">PROC_RETAP</data><data key="edge_relationship_type">historically_produced</data><data key="edge_target_entity_id">WORK_RETAP_FUT_PENSION</data><data key="edge_operational_context">RETAP generated alert a month before recorded anticipated noncovered pension entitlement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">RETAP generated alert a month before recorded anticipated noncovered pension entitlement.</data></edge><edge id="REL_R103_0072" source="WORK_RETAP_FUT_PENSION" target="DATA_MBR_FUT_PENSION_ENT"><data key="edge_relationship_id">REL_R103_0072</data><data key="edge_source_entity_id">WORK_RETAP_FUT_PENSION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_MBR_FUT_PENSION_ENT</data><data key="edge_operational_context">Legacy RETAP pension alert derived from future pension entitlement date on MBR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Legacy RETAP pension alert derived from future pension entitlement date on MBR.</data></edge><edge id="REL_R104_0001" source="PROC_WAIVER_2PIN" target="DATA_WAIVER_2PIN_CONTROL"><data key="edge_relationship_id">REL_R104_0001</data><data key="edge_source_entity_id">PROC_WAIVER_2PIN</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">DATA_WAIVER_2PIN_CONTROL</data><data key="edge_operational_context">For over-$2,000 approvals a reviewer other than initial decision maker supplies second-PIN authorization.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">For over-$2,000 approvals a reviewer other than initial decision maker supplies second-PIN authorization.</data></edge><edge id="REL_R104_0002" source="PROC_OVERPAYMENT_WAIVER" target="PROC_WAIVER_2PIN"><data key="edge_relationship_id">REL_R104_0002</data><data key="edge_source_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">PROC_WAIVER_2PIN</data><data key="edge_operational_context">Waiver approval above tolerance invokes tiered independent reviewer approval; exceptions for administrative tolerance.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Waiver approval above tolerance invokes tiered independent reviewer approval; exceptions for administrative tolerance.</data></edge><edge id="REL_R104_0003" source="ORG_SSA_RQ_GAP" target="PROC_WAIVER_2PIN"><data key="edge_relationship_id">REL_R104_0003</data><data key="edge_source_entity_id">ORG_SSA_RQ_GAP</data><data key="edge_relationship_type">performs</data><data key="edge_target_entity_id">PROC_WAIVER_2PIN</data><data key="edge_operational_context">RQ/GAP supplies final second-PIN review for $20,000-or-greater approved waivers.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">RQ/GAP supplies final second-PIN review for $20,000-or-greater approved waivers.</data></edge><edge id="REL_R104_0004" source="PROC_WAIVER_2PIN" target="APP_DMS"><data key="edge_relationship_id">REL_R104_0004</data><data key="edge_source_entity_id">PROC_WAIVER_2PIN</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Title II reviewers finalize approvals in DMS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title II reviewers finalize approvals in DMS.</data></edge><edge id="REL_R104_0005" source="PROC_WAIVER_2PIN" target="SYS_SSR"><data key="edge_relationship_id">REL_R104_0005</data><data key="edge_source_entity_id">PROC_WAIVER_2PIN</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">Title XVI decision maker and second-PIN reviewer use direct SSR update inputs on same day.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title XVI decision maker and second-PIN reviewer use direct SSR update inputs on same day.</data></edge><edge id="REL_R104_0006" source="APP_HDOP_POWERAPP" target="ORG_SSA_RQ_GAP"><data key="edge_relationship_id">REL_R104_0006</data><data key="edge_source_entity_id">APP_HDOP_POWERAPP</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">ORG_SSA_RQ_GAP</data><data key="edge_operational_context">RQ/GAP uses HDOP to access uploaded signed SSA-635 for proposed waivers of at least $20,000.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">RQ/GAP uses HDOP to access uploaded signed SSA-635 for proposed waivers of at least $20,000.</data></edge><edge id="REL_R104_0007" source="FORM_SSA635" target="APP_HDOP_POWERAPP"><data key="edge_relationship_id">REL_R104_0007</data><data key="edge_source_entity_id">FORM_SSA635</data><data key="edge_relationship_type">uploaded_to_for_review</data><data key="edge_target_entity_id">APP_HDOP_POWERAPP</data><data key="edge_operational_context">At $20,000 or more proposed approvals, form goes to HDOP for RQ review before final determination.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">At $20,000 or more proposed approvals, form goes to HDOP for RQ review before final determination.</data></edge><edge id="REL_R104_0008" source="FORM_SSA635" target="PROC_OVERPAYMENT_WAIVER"><data key="edge_relationship_id">REL_R104_0008</data><data key="edge_source_entity_id">FORM_SSA635</data><data key="edge_relationship_type">documents</data><data key="edge_target_entity_id">PROC_OVERPAYMENT_WAIVER</data><data key="edge_operational_context">SSA-635 documents adjudicated waiver determinations above $2,000 and rationale.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-635 documents adjudicated waiver determinations above $2,000 and rationale.</data></edge><edge id="REL_R104_0009" source="FORM_SSA635" target="APP_EP"><data key="edge_relationship_id">REL_R104_0009</data><data key="edge_source_entity_id">FORM_SSA635</data><data key="edge_relationship_type">stored_in_after_final_decision</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Only after final waiver decision, fax or import signed form and documents into EP; do not treat prereview upload as final archive.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Only after final waiver decision, fax or import signed form and documents into EP; do not treat prereview upload as final archive.</data></edge><edge id="REL_R104_0010" source="PROC_WAIVER_2PIN" target="FORM_SSA635"><data key="edge_relationship_id">REL_R104_0010</data><data key="edge_source_entity_id">PROC_WAIVER_2PIN</data><data key="edge_relationship_type">documents_review_on</data><data key="edge_target_entity_id">FORM_SSA635</data><data key="edge_operational_context">Required independent reviewers sign and date SSA-635 in applicable approval cases before final EP storage; no retention period specified.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Required independent reviewers sign and date SSA-635 in applicable approval cases before final EP storage; no retention period specified.</data></edge><edge id="REL_R104_0011" source="UI_DMS_DRWR" target="APP_DMS"><data key="edge_relationship_id">REL_R104_0011</data><data key="edge_source_entity_id">UI_DMS_DRWR</data><data key="edge_relationship_type">interface_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS identifies UI_DMS_DRWR as an interaction in the Title II DMS waiver process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies UI_DMS_DRWR as an interaction in the Title II DMS waiver process.</data></edge><edge id="REL_R104_0012" source="UI_DMS_DRWD" target="APP_DMS"><data key="edge_relationship_id">REL_R104_0012</data><data key="edge_source_entity_id">UI_DMS_DRWD</data><data key="edge_relationship_type">interface_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS identifies UI_DMS_DRWD as an interaction in the Title II DMS waiver process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies UI_DMS_DRWD as an interaction in the Title II DMS waiver process.</data></edge><edge id="REL_R104_0013" source="UI_DMS_DRPC" target="APP_DMS"><data key="edge_relationship_id">REL_R104_0013</data><data key="edge_source_entity_id">UI_DMS_DRPC</data><data key="edge_relationship_type">interface_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS identifies UI_DMS_DRPC as an interaction in the Title II DMS waiver process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies UI_DMS_DRPC as an interaction in the Title II DMS waiver process.</data></edge><edge id="REL_R104_0014" source="UI_DMS_RMKI" target="APP_DMS"><data key="edge_relationship_id">REL_R104_0014</data><data key="edge_source_entity_id">UI_DMS_RMKI</data><data key="edge_relationship_type">interface_of</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">POMS identifies UI_DMS_RMKI as an interaction in the Title II DMS waiver process.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS identifies UI_DMS_RMKI as an interaction in the Title II DMS waiver process.</data></edge><edge id="REL_R104_0015" source="UI_DMS_DRWR" target="PROC_WAIVER_2PIN"><data key="edge_relationship_id">REL_R104_0015</data><data key="edge_source_entity_id">UI_DMS_DRWR</data><data key="edge_relationship_type">records_review_of</data><data key="edge_target_entity_id">PROC_WAIVER_2PIN</data><data key="edge_operational_context">Reviewer supplies second waiver approval input via DRWR in Title II cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Reviewer supplies second waiver approval input via DRWR in Title II cases.</data></edge><edge id="REL_R104_0016" source="UI_DMS_DRWD" target="APP_ROAR"><data key="edge_relationship_id">REL_R104_0016</data><data key="edge_source_entity_id">UI_DMS_DRWD</data><data key="edge_relationship_type">posts_decision_to</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">DMS DRWD records waiver disposition in ROAR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DMS DRWD records waiver disposition in ROAR.</data></edge><edge id="REL_R104_0017" source="UI_DMS_DRPC" target="APP_ROAR"><data key="edge_relationship_id">REL_R104_0017</data><data key="edge_source_entity_id">UI_DMS_DRPC</data><data key="edge_relationship_type">posts_decision_to</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">DMS DRPC posts personal conference waiver denial decision to ROAR.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DMS DRPC posts personal conference waiver denial decision to ROAR.</data></edge><edge id="REL_R104_0018" source="UI_DMS_RMKI" target="APP_DMS"><data key="edge_relationship_id">REL_R104_0018</data><data key="edge_source_entity_id">UI_DMS_RMKI</data><data key="edge_relationship_type">indexes_notes_in</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">Waiver initial-determination remarks entered under OTHER category.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Waiver initial-determination remarks entered under OTHER category.</data></edge><edge id="REL_R104_0019" source="SYS_SSR" target="DATA_SSR_OPSQ"><data key="edge_relationship_id">REL_R104_0019</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains_logically</data><data key="edge_target_entity_id">DATA_SSR_OPSQ</data><data key="edge_operational_context">POMS explicitly identifies OPSQ as an SSR segment associated with pending waiver.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS explicitly identifies OPSQ as an SSR segment associated with pending waiver.</data></edge><edge id="REL_R104_0020" source="DATA_SSR_OPSQ" target="DATA_SSR_SQD"><data key="edge_relationship_id">REL_R104_0020</data><data key="edge_source_entity_id">DATA_SSR_OPSQ</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">DATA_SSR_SQD</data><data key="edge_operational_context">The OPSQ includes sequence/date SQD reference required on SSA-635.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">The OPSQ includes sequence/date SQD reference required on SSA-635.</data></edge><edge id="REL_R104_0021" source="FORM_SSA635" target="DATA_SSR_OPSQ"><data key="edge_relationship_id">REL_R104_0021</data><data key="edge_source_entity_id">FORM_SSA635</data><data key="edge_relationship_type">records</data><data key="edge_target_entity_id">DATA_SSR_OPSQ</data><data key="edge_operational_context">Title XVI SSA-635 must reference appropriate SSR overpayment sequence and date.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title XVI SSA-635 must reference appropriate SSR overpayment sequence and date.</data></edge><edge id="REL_R104_0022" source="FORM_SSA635" target="APP_ROAR"><data key="edge_relationship_id">REL_R104_0022</data><data key="edge_source_entity_id">FORM_SSA635</data><data key="edge_relationship_type">references</data><data key="edge_target_entity_id">APP_ROAR</data><data key="edge_operational_context">Title II SSA-635 must reference corresponding ROAR event number.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title II SSA-635 must reference corresponding ROAR event number.</data></edge><edge id="REL_R104_0023" source="PROC_WAIVER_PERSONAL_CONFERENCE" target="FORM_SSA635"><data key="edge_relationship_id">REL_R104_0023</data><data key="edge_source_entity_id">PROC_WAIVER_PERSONAL_CONFERENCE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA635</data><data key="edge_operational_context">SSA-635 documents determination at personal-conference stage.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-635 documents determination at personal-conference stage.</data></edge><edge id="REL_R104_0024" source="PROC_WAIVER_PERSONAL_CONFERENCE" target="UI_DMS_DRPC"><data key="edge_relationship_id">REL_R104_0024</data><data key="edge_source_entity_id">PROC_WAIVER_PERSONAL_CONFERENCE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_DMS_DRPC</data><data key="edge_operational_context">Title II determination after personal conference input via DRPC.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title II determination after personal conference input via DRPC.</data></edge><edge id="REL_R104_0025" source="PROC_WAIVER_PERSONAL_CONFERENCE" target="UI_SSR_UOWV"><data key="edge_relationship_id">REL_R104_0025</data><data key="edge_source_entity_id">PROC_WAIVER_PERSONAL_CONFERENCE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_SSR_UOWV</data><data key="edge_operational_context">Title XVI waiver denial input via UOWV direct SSR update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title XVI waiver denial input via UOWV direct SSR update.</data></edge><edge id="REL_R104_0026" source="PROC_WAIVER_PERSONAL_CONFERENCE" target="APP_DPS"><data key="edge_relationship_id">REL_R104_0026</data><data key="edge_source_entity_id">PROC_WAIVER_PERSONAL_CONFERENCE</data><data key="edge_relationship_type">produces_notice_via</data><data key="edge_target_entity_id">APP_DPS</data><data key="edge_operational_context">DPS prepares individualized waiver determination notice.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DPS prepares individualized waiver determination notice.</data></edge><edge id="REL_R104_0027" source="PROC_WAIVER_PERSONAL_CONFERENCE" target="APP_ORS"><data key="edge_relationship_id">REL_R104_0027</data><data key="edge_source_entity_id">PROC_WAIVER_PERSONAL_CONFERENCE</data><data key="edge_relationship_type">stores_notice_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">Final waiver determination notices retained in ORS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Final waiver determination notices retained in ORS.</data></edge><edge id="REL_R104_0028" source="PROC_WAIVER_PERSONAL_CONFERENCE" target="REPO_NDRED"><data key="edge_relationship_id">REL_R104_0028</data><data key="edge_source_entity_id">PROC_WAIVER_PERSONAL_CONFERENCE</data><data key="edge_relationship_type">stores_evidence_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Title II/non-disability SSA-635 copies sent to NDRed via EP when relevant.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Title II/non-disability SSA-635 copies sent to NDRed via EP when relevant.</data></edge><edge id="REL_R104_0029" source="PROC_HIT_AUTOMATED_MEDICAL_REQUEST" target="APP_MEGAHIT"><data key="edge_relationship_id">REL_R104_0029</data><data key="edge_source_entity_id">PROC_HIT_AUTOMATED_MEDICAL_REQUEST</data><data key="edge_relationship_type">executed_by</data><data key="edge_target_entity_id">APP_MEGAHIT</data><data key="edge_operational_context">MEGAHIT creates and sends automated evidence requests to HIT partners after FO-to-DDS electronic case transfer.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MEGAHIT creates and sends automated evidence requests to HIT partners after FO-to-DDS electronic case transfer.</data></edge><edge id="REL_R104_0030" source="PROC_HIT_AUTOMATED_MEDICAL_REQUEST" target="DATA_HIT_REQUEST"><data key="edge_relationship_id">REL_R104_0030</data><data key="edge_source_entity_id">PROC_HIT_AUTOMATED_MEDICAL_REQUEST</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_HIT_REQUEST</data><data key="edge_operational_context">Automated HIT process creates request document for health information partners.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Automated HIT process creates request document for health information partners.</data></edge><edge id="REL_R104_0031" source="PROC_HIT_AUTOMATED_MEDICAL_REQUEST" target="DATA_HIT_ADJUDICATION_REQUEST_WINDOW"><data key="edge_relationship_id">REL_R104_0031</data><data key="edge_source_entity_id">PROC_HIT_AUTOMATED_MEDICAL_REQUEST</data><data key="edge_relationship_type">scoped_by</data><data key="edge_target_entity_id">DATA_HIT_ADJUDICATION_REQUEST_WINDOW</data><data key="edge_operational_context">Initial, reconsideration and CDR have documented date-bound requests; no general health-record pull is established.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Initial, reconsideration and CDR have documented date-bound requests; no general health-record pull is established.</data></edge><edge id="REL_R104_0032" source="PROC_HIT_USER_TRIGGERED_REQUEST" target="APP_DCPS"><data key="edge_relationship_id">REL_R104_0032</data><data key="edge_source_entity_id">PROC_HIT_USER_TRIGGERED_REQUEST</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DDS creates user-triggered HIT request in DCPS when appropriate.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DDS creates user-triggered HIT request in DCPS when appropriate.</data></edge><edge id="REL_R104_0033" source="PROC_HIT_USER_TRIGGERED_REQUEST" target="UI_MEGAHIT_WEBSITE"><data key="edge_relationship_id">REL_R104_0033</data><data key="edge_source_entity_id">PROC_HIT_USER_TRIGGERED_REQUEST</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">UI_MEGAHIT_WEBSITE</data><data key="edge_operational_context">DDS also may create request via MEGAHIT website.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DDS also may create request via MEGAHIT website.</data></edge><edge id="REL_R104_0034" source="UI_MEGAHIT_WEBSITE" target="APP_MEGAHIT"><data key="edge_relationship_id">REL_R104_0034</data><data key="edge_source_entity_id">UI_MEGAHIT_WEBSITE</data><data key="edge_relationship_type">interface_of</data><data key="edge_target_entity_id">APP_MEGAHIT</data><data key="edge_operational_context">MEGAHIT website is the named user-initiated request route.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MEGAHIT website is the named user-initiated request route.</data></edge><edge id="REL_R104_0035" source="PROC_HIT_USER_TRIGGERED_REQUEST" target="DATA_HIT_REQUEST"><data key="edge_relationship_id">REL_R104_0035</data><data key="edge_source_entity_id">PROC_HIT_USER_TRIGGERED_REQUEST</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">DATA_HIT_REQUEST</data><data key="edge_operational_context">Request is sent to documented health IT partner.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Request is sent to documented health IT partner.</data></edge><edge id="REL_R104_0036" source="PROC_HIT_USER_TRIGGERED_REQUEST" target="DATA_HIT_REQUEST_LIMIT"><data key="edge_relationship_id">REL_R104_0036</data><data key="edge_source_entity_id">PROC_HIT_USER_TRIGGERED_REQUEST</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">DATA_HIT_REQUEST_LIMIT</data><data key="edge_operational_context">Ten requests per HIT partner at each adjudication level; no storage inferred.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Ten requests per HIT partner at each adjudication level; no storage inferred.</data></edge><edge id="REL_R104_0037" source="PROC_HIT_TRADITIONAL_MEDICAL_REQUEST" target="APP_DCPS"><data key="edge_relationship_id">REL_R104_0037</data><data key="edge_source_entity_id">PROC_HIT_TRADITIONAL_MEDICAL_REQUEST</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_DCPS</data><data key="edge_operational_context">DDS creates traditional medical evidence requests through DCPS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DDS creates traditional medical evidence requests through DCPS.</data></edge><edge id="REL_R104_0038" source="PROC_HIT_TRADITIONAL_MEDICAL_REQUEST" target="APP_ERE"><data key="edge_relationship_id">REL_R104_0038</data><data key="edge_source_entity_id">PROC_HIT_TRADITIONAL_MEDICAL_REQUEST</data><data key="edge_relationship_type">may_use</data><data key="edge_target_entity_id">APP_ERE</data><data key="edge_operational_context">Some traditional record requests use Electronic Records Express route; mail/fax are alternatives.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Some traditional record requests use Electronic Records Express route; mail/fax are alternatives.</data></edge><edge id="REL_R104_0039" source="PROC_HIT_TRADITIONAL_MEDICAL_REQUEST" target="PROC_HIT_AUTOMATED_MEDICAL_REQUEST"><data key="edge_relationship_id">REL_R104_0039</data><data key="edge_source_entity_id">PROC_HIT_TRADITIONAL_MEDICAL_REQUEST</data><data key="edge_relationship_type">fallback_for</data><data key="edge_target_entity_id">PROC_HIT_AUTOMATED_MEDICAL_REQUEST</data><data key="edge_operational_context">DDS reviews HIT response first, then uses traditional route for evidence unavailable by HIT such as abnormal graphical tests.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DDS reviews HIT response first, then uses traditional route for evidence unavailable by HIT such as abnormal graphical tests.</data></edge><edge id="REL_R104_0040" source="EX_CAWR" target="PROC_IRS_SSA_WAGE_RECONCILIATION"><data key="edge_relationship_id">REL_R104_0040</data><data key="edge_source_entity_id">EX_CAWR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_IRS_SSA_WAGE_RECONCILIATION</data><data key="edge_operational_context">CAWR agreement allows automated agency wage/tax report reconciliation.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">CAWR agreement allows automated agency wage/tax report reconciliation.</data></edge><edge id="REL_R104_0041" source="PROC_IRS_SSA_WAGE_RECONCILIATION" target="DATA_CAWR_EIN_TAXYEAR_KEY"><data key="edge_relationship_id">REL_R104_0041</data><data key="edge_source_entity_id">PROC_IRS_SSA_WAGE_RECONCILIATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_CAWR_EIN_TAXYEAR_KEY</data><data key="edge_operational_context">Report comparison matches by employer EIN and tax year.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Report comparison matches by employer EIN and tax year.</data></edge><edge id="REL_R104_0042" source="PROC_IRS_SSA_WAGE_RECONCILIATION" target="DB_RECON"><data key="edge_relationship_id">REL_R104_0042</data><data key="edge_source_entity_id">PROC_IRS_SSA_WAGE_RECONCILIATION</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DB_RECON</data><data key="edge_operational_context">Existing IRS/SSA reconciliation repository is the documented functional domain; no new physical schema inferred.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Existing IRS/SSA reconciliation repository is the documented functional domain; no new physical schema inferred.</data></edge><edge id="REL_R104_0043" source="PROC_IRS_SSA_WAGE_RECONCILIATION" target="SYS_MEF"><data key="edge_relationship_id">REL_R104_0043</data><data key="edge_source_entity_id">PROC_IRS_SSA_WAGE_RECONCILIATION</data><data key="edge_relationship_type">supports_corrections_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Wage data reporting and employer corrections support accurate earnings posting; does not establish direct IRS write into MEF.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Wage data reporting and employer corrections support accurate earnings posting; does not establish direct IRS write into MEF.</data></edge><edge id="REL_R104_0044" source="PROC_FTI_LOSS_REPORTING" target="APP_LOSS_REPORTING_TOOL"><data key="edge_relationship_id">REL_R104_0044</data><data key="edge_source_entity_id">PROC_FTI_LOSS_REPORTING</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_LOSS_REPORTING_TOOL</data><data key="edge_operational_context">FTI access or disclosure loss goes through LRT under SSA breach plan.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FTI access or disclosure loss goes through LRT under SSA breach plan.</data></edge><edge id="REL_R104_0045" source="ORG_SSA_OPD" target="APP_LOSS_REPORTING_TOOL"><data key="edge_relationship_id">REL_R104_0045</data><data key="edge_source_entity_id">ORG_SSA_OPD</data><data key="edge_relationship_type">monitors</data><data key="edge_target_entity_id">APP_LOSS_REPORTING_TOOL</data><data key="edge_operational_context">OPD monitors reported tax return information loss events.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">OPD monitors reported tax return information loss events.</data></edge><edge id="REL_R104_0046" source="ORG_SSA_OPD" target="ORG_IRS"><data key="edge_relationship_id">REL_R104_0046</data><data key="edge_source_entity_id">ORG_SSA_OPD</data><data key="edge_relationship_type">coordinates_with</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">OPD oversees IRS disclosure notification as required by POMS and tax information safeguard obligations.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">OPD oversees IRS disclosure notification as required by POMS and tax information safeguard obligations.</data></edge><edge id="REL_R104_0047" source="EX_CAWR" target="PROC_FTI_LOSS_REPORTING"><data key="edge_relationship_id">REL_R104_0047</data><data key="edge_source_entity_id">EX_CAWR</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">PROC_FTI_LOSS_REPORTING</data><data key="edge_operational_context">Tax return information exchanged for CAWR is subject to IRC 6103/IRS Publication 1075 protections; incident reporting is conditional.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Tax return information exchanged for CAWR is subject to IRC 6103/IRS Publication 1075 protections; incident reporting is conditional.</data></edge><edge id="REL_R104_0048" source="ORG_IRS" target="DATA_IRS_TOP_WEEKLY_TAX_DEBT_FILE"><data key="edge_relationship_id">REL_R104_0048</data><data key="edge_source_entity_id">ORG_IRS</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">DATA_IRS_TOP_WEEKLY_TAX_DEBT_FILE</data><data key="edge_operational_context">IRS submits tax debt records to Fiscal Service weekly, including existing-debt updates.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">IRS submits tax debt records to Fiscal Service weekly, including existing-debt updates.</data></edge><edge id="REL_R104_0049" source="DATA_IRS_TOP_WEEKLY_TAX_DEBT_FILE" target="DB_NID3"><data key="edge_relationship_id">REL_R104_0049</data><data key="edge_source_entity_id">DATA_IRS_TOP_WEEKLY_TAX_DEBT_FILE</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DB_NID3</data><data key="edge_operational_context">Fiscal Service maintains National Interactive Delinquent Debtors Database with IRS weekly tax-debt changes; no direct SSA authority asserted.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Fiscal Service maintains National Interactive Delinquent Debtors Database with IRS weekly tax-debt changes; no direct SSA authority asserted.</data></edge><edge id="REL_R104_0050" source="SVC_TOP" target="DATA_FPLP_WEEKLY_OFFSET_FILE"><data key="edge_relationship_id">REL_R104_0050</data><data key="edge_source_entity_id">SVC_TOP</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">DATA_FPLP_WEEKLY_OFFSET_FILE</data><data key="edge_operational_context">Treasury TOP/FPLP offset process produces electronic offset records received by SSA central office.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Treasury TOP/FPLP offset process produces electronic offset records received by SSA central office.</data></edge><edge id="REL_R104_0051" source="DATA_FPLP_WEEKLY_OFFSET_FILE" target="DB_PHUS"><data key="edge_relationship_id">REL_R104_0051</data><data key="edge_source_entity_id">DATA_FPLP_WEEKLY_OFFSET_FILE</data><data key="edge_relationship_type">posted_to</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">SSA central office processes Treasury weekly offset data into PHUS for employee viewing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA central office processes Treasury weekly offset data into PHUS for employee viewing.</data></edge><edge id="REL_R104_0052" source="PROC_FPLP" target="SVC_TOP"><data key="edge_relationship_id">REL_R104_0052</data><data key="edge_source_entity_id">PROC_FPLP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">Fiscal Service uses Treasury Offset Program for FPLP levy, after SSA has certified payment; SSA does not itself reduce payment for FPLP.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Fiscal Service uses Treasury Offset Program for FPLP levy, after SSA has certified payment; SSA does not itself reduce payment for FPLP.</data></edge><edge id="REL_R104_0053" source="PROC_SERS_NONPROGRAMMATIC_FEE" target="APP_SERS"><data key="edge_relationship_id">REL_R104_0053</data><data key="edge_source_entity_id">PROC_SERS_NONPROGRAMMATIC_FEE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_SERS</data><data key="edge_operational_context">SERS handles standard FO service charges including copying, SSN verification, DEQY, certification and extracts.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SERS handles standard FO service charges including copying, SSN verification, DEQY, certification and extracts.</data></edge><edge id="REL_R104_0054" source="PROC_SERS_NONPROGRAMMATIC_FEE" target="TECH_SERS_CHECK_SCANNER"><data key="edge_relationship_id">REL_R104_0054</data><data key="edge_source_entity_id">PROC_SERS_NONPROGRAMMATIC_FEE</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">TECH_SERS_CHECK_SCANNER</data><data key="edge_operational_context">FO employee scans domestic check or money order and verifies legible image.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FO employee scans domestic check or money order and verifies legible image.</data></edge><edge id="REL_R104_0055" source="APP_SERS" target="DATA_SERS_FEE_RECEIPT"><data key="edge_relationship_id">REL_R104_0055</data><data key="edge_source_entity_id">APP_SERS</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_SERS_FEE_RECEIPT</data><data key="edge_operational_context">SERS transaction generates printable payment receipt.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SERS transaction generates printable payment receipt.</data></edge><edge id="REL_R104_0056" source="APP_FEEBAYNET" target="APP_SERS"><data key="edge_relationship_id">REL_R104_0056</data><data key="edge_source_entity_id">APP_FEEBAYNET</data><data key="edge_relationship_type">separate_from</data><data key="edge_target_entity_id">APP_SERS</data><data key="edge_operational_context">SSA explicitly reserves FeeBayNet for invoicing, not standard SERS payment processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA explicitly reserves FeeBayNet for invoicing, not standard SERS payment processing.</data></edge><edge id="REL_R104_0057" source="PROC_SERS_FEE_REFUND" target="DATA_SERS_REFUND_REQUEST"><data key="edge_relationship_id">REL_R104_0057</data><data key="edge_source_entity_id">PROC_SERS_FEE_REFUND</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_SERS_REFUND_REQUEST</data><data key="edge_operational_context">Refund routing requires order number, SSN or tax ID, mailing address and transaction details.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Refund routing requires order number, SSN or tax ID, mailing address and transaction details.</data></edge><edge id="REL_R104_0058" source="PROC_SERS_FEE_REFUND" target="ORG_SSA_FS"><data key="edge_relationship_id">REL_R104_0058</data><data key="edge_source_entity_id">PROC_SERS_FEE_REFUND</data><data key="edge_relationship_type">processed_by</data><data key="edge_target_entity_id">ORG_SSA_FS</data><data key="edge_operational_context">Field-office employees send refund requests to FS for processing.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Field-office employees send refund requests to FS for processing.</data></edge><edge id="REL_R104_0059" source="PROC_SERS_FEE_REFUND" target="ORG_TREASURY"><data key="edge_relationship_id">REL_R104_0059</data><data key="edge_source_entity_id">PROC_SERS_FEE_REFUND</data><data key="edge_relationship_type">may_result_in_payment_by</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">POMS specifies a Department of the Treasury check issued to the refund request address; no particular Fiscal Service application or integration is established.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS specifies a Department of the Treasury check issued to the refund request address; no particular Fiscal Service application or integration is established.</data></edge><edge id="REL_R104_0060" source="DATA_SERS_REFUND_REQUEST" target="PROC_SERS_FEE_REFUND"><data key="edge_relationship_id">REL_R104_0060</data><data key="edge_source_entity_id">DATA_SERS_REFUND_REQUEST</data><data key="edge_relationship_type">addresses_payment_to</data><data key="edge_target_entity_id">PROC_SERS_FEE_REFUND</data><data key="edge_operational_context">Customer-supplied refund mailing address scopes Treasury refund delivery; it is not authenticated residence or master SSA record update.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Customer-supplied refund mailing address scopes Treasury refund delivery; it is not authenticated residence or master SSA record update.</data></edge><edge id="REL_R104_0061" source="PROC_SERS_SCANNER_OUTAGE_FALLBACK" target="PROC_SERS_NONPROGRAMMATIC_FEE"><data key="edge_relationship_id">REL_R104_0061</data><data key="edge_source_entity_id">PROC_SERS_SCANNER_OUTAGE_FALLBACK</data><data key="edge_relationship_type">fallback_for</data><data key="edge_target_entity_id">PROC_SERS_NONPROGRAMMATIC_FEE</data><data key="edge_operational_context">SERS help desk trouble and SSA-414 tracking route is exception path for scanner failure.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SERS help desk trouble and SSA-414 tracking route is exception path for scanner failure.</data></edge><edge id="REL_R104_0062" source="PROC_SERS_SCANNER_OUTAGE_FALLBACK" target="TECH_SERS_CHECK_SCANNER"><data key="edge_relationship_id">REL_R104_0062</data><data key="edge_source_entity_id">PROC_SERS_SCANNER_OUTAGE_FALLBACK</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">TECH_SERS_CHECK_SCANNER</data><data key="edge_operational_context">Failure of SERS scanner initiates help desk process, not authorization to send untracked checks to FS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Failure of SERS scanner initiates help desk process, not authorization to send untracked checks to FS.</data></edge><edge id="REL_R104_0063" source="PROC_SERS_SCANNER_OUTAGE_FALLBACK" target="ORG_SSA_FS"><data key="edge_relationship_id">REL_R104_0063</data><data key="edge_source_entity_id">PROC_SERS_SCANNER_OUTAGE_FALLBACK</data><data key="edge_relationship_type">reports_to</data><data key="edge_target_entity_id">ORG_SSA_FS</data><data key="edge_operational_context">FS requires help desk incident/ticket number before paper handling in scanner outage.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">FS requires help desk incident/ticket number before paper handling in scanner outage.</data></edge><edge id="REL_R105_0001" source="APP_QRCPS" target="UI_R105_QRCPS_GENERAL"><data key="edge_relationship_id">REL_R105_0001</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">provides_ui</data><data key="edge_target_entity_id">UI_R105_QRCPS_GENERAL</data><data key="edge_operational_context">QRCPS contains a general referral section for MAQR Review.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">QRCPS contains a general referral section for MAQR Review.</data></edge><edge id="REL_R105_0002" source="APP_QRCPS" target="WORK_R105_MAQR_TASK"><data key="edge_relationship_id">REL_R105_0002</data><data key="edge_source_entity_id">APP_QRCPS</data><data key="edge_relationship_type">assigns</data><data key="edge_target_entity_id">WORK_R105_MAQR_TASK</data><data key="edge_operational_context">DQR management requests assignment of MAQR task in QRCPS to qualified reviewers.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">DQR management requests assignment of MAQR task in QRCPS to qualified reviewers.</data></edge><edge id="REL_R105_0003" source="FUNC_MAQR" target="WORK_R105_MAQR_TASK"><data key="edge_relationship_id">REL_R105_0003</data><data key="edge_source_entity_id">FUNC_MAQR</data><data key="edge_relationship_type">controlled_by</data><data key="edge_target_entity_id">WORK_R105_MAQR_TASK</data><data key="edge_operational_context">MAQR authorization is limited to reviewers approved under eligibility rules.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">MAQR authorization is limited to reviewers approved under eligibility rules.</data></edge><edge id="REL_R105_0004" source="UI_R105_QRCPS_GENERAL" target="FUNC_MAQR"><data key="edge_relationship_id">REL_R105_0004</data><data key="edge_source_entity_id">UI_R105_QRCPS_GENERAL</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">FUNC_MAQR</data><data key="edge_operational_context">General Referral supports medical assessment review when the initiating reviewer lacks MAQR task.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">General Referral supports medical assessment review when the initiating reviewer lacks MAQR task.</data></edge><edge id="REL_R105_0005" source="PROC_DQR_QUALITY_REVIEW" target="FORM_R105_SSA3023"><data key="edge_relationship_id">REL_R105_0005</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_R105_SSA3023</data><data key="edge_operational_context">Psychiatric review technique consultant disagreement or agreement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Psychiatric review technique consultant disagreement or agreement.</data></edge><edge id="REL_R105_0006" source="PROC_DQR_QUALITY_REVIEW" target="FORM_R105_SSA392"><data key="edge_relationship_id">REL_R105_0006</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_R105_SSA392</data><data key="edge_operational_context">Physical RFC assessment consultant review.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Physical RFC assessment consultant review.</data></edge><edge id="REL_R105_0007" source="PROC_DQR_QUALITY_REVIEW" target="FORM_R105_SSA392_SUP"><data key="edge_relationship_id">REL_R105_0007</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_R105_SSA392_SUP</data><data key="edge_operational_context">Mental RFC assessment consultant review.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mental RFC assessment consultant review.</data></edge><edge id="REL_R105_0008" source="PROC_DQR_QUALITY_REVIEW" target="FORM_R105_SSA416"><data key="edge_relationship_id">REL_R105_0008</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_R105_SSA416</data><data key="edge_operational_context">Medical case analysis and documentation deficiencies.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Medical case analysis and documentation deficiencies.</data></edge><edge id="REL_R105_0009" source="PROC_DQR_QUALITY_REVIEW" target="FORM_R105_SSA2506"><data key="edge_relationship_id">REL_R105_0009</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_R105_SSA2506</data><data key="edge_operational_context">Psychiatric consultant when federal quality review assumes jurisdiction.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Psychiatric consultant when federal quality review assumes jurisdiction.</data></edge><edge id="REL_R105_0010" source="FUNC_MAQR" target="FORM_R105_SSA416"><data key="edge_relationship_id">REL_R105_0010</data><data key="edge_source_entity_id">FUNC_MAQR</data><data key="edge_relationship_type">documents_review_using</data><data key="edge_target_entity_id">FORM_R105_SSA416</data><data key="edge_operational_context">Qualified FQRs may complete and sign their own SSA-416 for allowable documentation deficiencies, excluding CDR and child cases.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Qualified FQRs may complete and sign their own SSA-416 for allowable documentation deficiencies, excluding CDR and child cases.</data></edge><edge id="REL_R105_0011" source="PROC_DQR_QUALITY_REVIEW" target="APP_EVIEW"><data key="edge_relationship_id">REL_R105_0011</data><data key="edge_source_entity_id">PROC_DQR_QUALITY_REVIEW</data><data key="edge_relationship_type">retains_final_medical_forms_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Federal quality reviewers upload final MC/PC review forms to eView after reviewing findings.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Federal quality reviewers upload final MC/PC review forms to eView after reviewing findings.</data></edge><edge id="REL_R105_0012" source="APP_ISNO" target="UI_R105_ISNO_AUTH"><data key="edge_relationship_id">REL_R105_0012</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">presents</data><data key="edge_target_entity_id">UI_R105_ISNO_AUTH</data><data key="edge_operational_context">iSNO uses SSN, DOB and name for initial authentication when accessed through iMain rather than mini-path.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">iSNO uses SSN, DOB and name for initial authentication when accessed through iMain rather than mini-path.</data></edge><edge id="REL_R105_0013" source="APP_ISNO" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL_R105_0013</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">checks_identity_against</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">POMS expressly states iSNO authentication checks Numident, MBR and SSR; failure requires mismatch against all three.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS expressly states iSNO authentication checks Numident, MBR and SSR; failure requires mismatch against all three.</data></edge><edge id="REL_R105_0014" source="APP_ISNO" target="SYS_MBR"><data key="edge_relationship_id">REL_R105_0014</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">checks_identity_against</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS expressly states iSNO authentication checks Numident, MBR and SSR; failure requires mismatch against all three.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS expressly states iSNO authentication checks Numident, MBR and SSR; failure requires mismatch against all three.</data></edge><edge id="REL_R105_0015" source="APP_ISNO" target="SYS_SSR"><data key="edge_relationship_id">REL_R105_0015</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">checks_identity_against</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">POMS expressly states iSNO authentication checks Numident, MBR and SSR; failure requires mismatch against all three.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS expressly states iSNO authentication checks Numident, MBR and SSR; failure requires mismatch against all three.</data></edge><edge id="REL_R105_0016" source="APP_ISNO" target="UI_R105_ISNO_SELECT"><data key="edge_relationship_id">REL_R105_0016</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">presents</data><data key="edge_target_entity_id">UI_R105_ISNO_SELECT</data><data key="edge_operational_context">Select Option is the notice-format input surface.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Select Option is the notice-format input surface.</data></edge><edge id="REL_R105_0017" source="UI_R105_ISNO_SELECT" target="DATA_R105_ISNO_HISTORY"><data key="edge_relationship_id">REL_R105_0017</data><data key="edge_source_entity_id">UI_R105_ISNO_SELECT</data><data key="edge_relationship_type">shows</data><data key="edge_target_entity_id">DATA_R105_ISNO_HISTORY</data><data key="edge_operational_context">Client History displays ten most recent SNO selections and possible accommodation history/pending alert.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Client History displays ten most recent SNO selections and possible accommodation history/pending alert.</data></edge><edge id="REL_R105_0018" source="APP_ISNO" target="UI_R105_ISNO_ACCOM"><data key="edge_relationship_id">REL_R105_0018</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">presents</data><data key="edge_target_entity_id">UI_R105_ISNO_ACCOM</data><data key="edge_operational_context">Additional accommodation paths open when request goes beyond seven automatically approved formats.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Additional accommodation paths open when request goes beyond seven automatically approved formats.</data></edge><edge id="REL_R105_0019" source="UI_R105_ISNO_ACCOM" target="DATA_R105_ISNO_ACCOM_ADDR"><data key="edge_relationship_id">REL_R105_0019</data><data key="edge_source_entity_id">UI_R105_ISNO_ACCOM</data><data key="edge_relationship_type">collects</data><data key="edge_target_entity_id">DATA_R105_ISNO_ACCOM_ADDR</data><data key="edge_operational_context">Mailing address is mandatory for notice of accommodation decision.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mailing address is mandatory for notice of accommodation decision.</data></edge><edge id="REL_R105_0020" source="APP_ISNO" target="PROC_R105_ISNO_AUTH_FIX"><data key="edge_relationship_id">REL_R105_0020</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">routes_failed_auth_to</data><data key="edge_target_entity_id">PROC_R105_ISNO_AUTH_FIX</data><data key="edge_operational_context">Mismatch referral goes to servicing field office for correction and retry.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Mismatch referral goes to servicing field office for correction and retry.</data></edge><edge id="REL_R105_0021" source="PROC_R105_ISNO_AUTH_FIX" target="APP_MDW_AI"><data key="edge_relationship_id">REL_R105_0021</data><data key="edge_source_entity_id">PROC_R105_ISNO_AUTH_FIX</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_MDW_AI</data><data key="edge_operational_context">Applicable SSA component sends MDW message to servicing field office listing identifying information and failure edit.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Applicable SSA component sends MDW message to servicing field office listing identifying information and failure edit.</data></edge><edge id="REL_R105_0022" source="APP_ISNO" target="PROC_R105_ISNO_NON_CEF"><data key="edge_relationship_id">REL_R105_0022</data><data key="edge_source_entity_id">APP_ISNO</data><data key="edge_relationship_type">documents_non_electronic_cases_through</data><data key="edge_target_entity_id">PROC_R105_ISNO_NON_CEF</data><data key="edge_operational_context">Paper case exception requires documentation of special notice choice on SSA-5002.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Paper case exception requires documentation of special notice choice on SSA-5002.</data></edge><edge id="REL_R105_0023" source="PROC_R105_ISNO_NON_CEF" target="FORM_SSA5002"><data key="edge_relationship_id">REL_R105_0023</data><data key="edge_source_entity_id">PROC_R105_ISNO_NON_CEF</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">FORM_SSA5002</data><data key="edge_operational_context">SSA-5002 documents special notice in non-CEF case; NDRED accepts SSA component fax and MDF holds DDS copy.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-5002 documents special notice in non-CEF case; NDRED accepts SSA component fax and MDF holds DDS copy.</data></edge><edge id="REL_R105_0024" source="PROC_R105_ISNO_NON_CEF" target="REPO_NDRED"><data key="edge_relationship_id">REL_R105_0024</data><data key="edge_source_entity_id">PROC_R105_ISNO_NON_CEF</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">SSA-5002 documents special notice in non-CEF case; NDRED accepts SSA component fax and MDF holds DDS copy.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-5002 documents special notice in non-CEF case; NDRED accepts SSA component fax and MDF holds DDS copy.</data></edge><edge id="REL_R105_0025" source="PROC_R105_ISNO_NON_CEF" target="REPO_MDF"><data key="edge_relationship_id">REL_R105_0025</data><data key="edge_source_entity_id">PROC_R105_ISNO_NON_CEF</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">REPO_MDF</data><data key="edge_operational_context">SSA-5002 documents special notice in non-CEF case; NDRED accepts SSA component fax and MDF holds DDS copy.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA-5002 documents special notice in non-CEF case; NDRED accepts SSA component fax and MDF holds DDS copy.</data></edge><edge id="REL_R105_0026" source="APP_MCS" target="APP_ISNO"><data key="edge_relationship_id">REL_R105_0026</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">can_launch</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">POMS lists this application as an entry point or mini-path to special notice option application.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS lists this application as an entry point or mini-path to special notice option application.</data></edge><edge id="REL_R105_0027" source="APP_MSSICS" target="APP_ISNO"><data key="edge_relationship_id">REL_R105_0027</data><data key="edge_source_entity_id">APP_MSSICS</data><data key="edge_relationship_type">can_launch</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">POMS lists this application as an entry point or mini-path to special notice option application.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS lists this application as an entry point or mini-path to special notice option application.</data></edge><edge id="REL_R105_0028" source="APP_RPS" target="APP_ISNO"><data key="edge_relationship_id">REL_R105_0028</data><data key="edge_source_entity_id">APP_RPS</data><data key="edge_relationship_type">can_launch</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">POMS lists this application as an entry point or mini-path to special notice option application.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS lists this application as an entry point or mini-path to special notice option application.</data></edge><edge id="REL_R105_0029" source="APP_CPMS" target="APP_ISNO"><data key="edge_relationship_id">REL_R105_0029</data><data key="edge_source_entity_id">APP_CPMS</data><data key="edge_relationship_type">can_launch</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">POMS lists this application as an entry point or mini-path to special notice option application.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS lists this application as an entry point or mini-path to special notice option application.</data></edge><edge id="REL_R105_0030" source="APP_ARPS" target="APP_ISNO"><data key="edge_relationship_id">REL_R105_0030</data><data key="edge_source_entity_id">APP_ARPS</data><data key="edge_relationship_type">can_launch</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">POMS lists this application as an entry point or mini-path to special notice option application.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS lists this application as an entry point or mini-path to special notice option application.</data></edge><edge id="REL_R105_0031" source="APP_CHIP" target="APP_ISNO"><data key="edge_relationship_id">REL_R105_0031</data><data key="edge_source_entity_id">APP_CHIP</data><data key="edge_relationship_type">can_launch</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">POMS lists this application as an entry point or mini-path to special notice option application.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">POMS lists this application as an entry point or mini-path to special notice option application.</data></edge><edge id="REL_R105_0032" source="PROC_SNO" target="APP_ISNO"><data key="edge_relationship_id">REL_R105_0032</data><data key="edge_source_entity_id">PROC_SNO</data><data key="edge_relationship_type">records_preference_using</data><data key="edge_target_entity_id">APP_ISNO</data><data key="edge_operational_context">Alternate-format special notice choice is recorded and queried in iSNO.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Alternate-format special notice choice is recorded and queried in iSNO.</data></edge><edge id="REL_R105_0033" source="APP_ECBSV" target="DATA_R105_ECBSV_CONSENT"><data key="edge_relationship_id">REL_R105_0033</data><data key="edge_source_entity_id">APP_ECBSV</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">DATA_R105_ECBSV_CONSENT</data><data key="edge_operational_context">Number holder written consent required before permitted-entity verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Number holder written consent required before permitted-entity verification.</data></edge><edge id="REL_R105_0034" source="APP_ECBSV" target="DATA_R105_ECBSV_CERT"><data key="edge_relationship_id">REL_R105_0034</data><data key="edge_source_entity_id">APP_ECBSV</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">DATA_R105_ECBSV_CERT</data><data key="edge_operational_context">Permitted entities certify eligibility, safeguards, and sufficient records at least every two years.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Permitted entities certify eligibility, safeguards, and sufficient records at least every two years.</data></edge><edge id="REL_R105_0035" source="APP_ECBSV" target="FORM_R105_ECBSV_EINCONSENT"><data key="edge_relationship_id">REL_R105_0035</data><data key="edge_source_entity_id">APP_ECBSV</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">FORM_R105_ECBSV_EINCONSENT</data><data key="edge_operational_context">EIN consent permits agency verification of applicant business EIN with IRS.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">EIN consent permits agency verification of applicant business EIN with IRS.</data></edge><edge id="REL_R105_0036" source="FORM_R105_ECBSV_EINCONSENT" target="ORG_IRS"><data key="edge_relationship_id">REL_R105_0036</data><data key="edge_source_entity_id">FORM_R105_ECBSV_EINCONSENT</data><data key="edge_relationship_type">authorizes_verification_with</data><data key="edge_target_entity_id">ORG_IRS</data><data key="edge_operational_context">eCBSV permitted entity EIN is verified with IRS pursuant to executed EIN consent.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">eCBSV permitted entity EIN is verified with IRS pursuant to executed EIN consent.</data></edge><edge id="REL_R105_0037" source="DATA_R105_ECBSV_CONSENT" target="SVC_ECBSV_API"><data key="edge_relationship_id">REL_R105_0037</data><data key="edge_source_entity_id">DATA_R105_ECBSV_CONSENT</data><data key="edge_relationship_type">authorizes</data><data key="edge_target_entity_id">SVC_ECBSV_API</data><data key="edge_operational_context">Written number-holder consent is required for permitted entity API SSN/name/DOB verification.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Written number-holder consent is required for permitted entity API SSN/name/DOB verification.</data></edge><edge id="REL_R105_0038" source="PROC_R105_STC_ROUTING" target="COMP_STC"><data key="edge_relationship_id">REL_R105_0038</data><data key="edge_source_entity_id">PROC_R105_STC_ROUTING</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">COMP_STC</data><data key="edge_operational_context">STC is used only when an authorized agency cannot receive SSA data directly.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">STC is used only when an authorized agency cannot receive SSA data directly.</data></edge><edge id="REL_R105_0039" source="COMP_STC" target="PROC_R105_STC_ROUTING"><data key="edge_relationship_id">REL_R105_0039</data><data key="edge_source_entity_id">COMP_STC</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_R105_STC_ROUTING</data><data key="edge_operational_context">State Transmission/Transfer Component routes data to authorized receiving state agency subject to agreement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">State Transmission/Transfer Component routes data to authorized receiving state agency subject to agreement.</data></edge><edge id="REL_R105_0040" source="FORM_SSA157" target="PROC_R105_STC_ROUTING"><data key="edge_relationship_id">REL_R105_0040</data><data key="edge_source_entity_id">FORM_SSA157</data><data key="edge_relationship_type">initiates</data><data key="edge_target_entity_id">PROC_R105_STC_ROUTING</data><data key="edge_operational_context">New state exchange requests use SSA-157 intake; actual STC availability requires signed agreement and need.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Not all SSA-157 requests become STC transfers.</data></edge><edge id="REL_R105_0041" source="APP_R105_LONGEVITY_VISUALIZER" target="DATA_R105_OACT_COHORT_TABLE_FAMILY"><data key="edge_relationship_id">REL_R105_0041</data><data key="edge_source_entity_id">APP_R105_LONGEVITY_VISUALIZER</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_R105_OACT_COHORT_TABLE_FAMILY</data><data key="edge_operational_context">2016 Longevity Visualizer consumes OACT cohort mortality life tables as a product family, with no inference that the 2016 executable incorporates the 2026 version.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Historical product family; do not infer current 2026 version is ingested.</data></edge><edge id="REL_R105_0042" source="APP_R105_LONGEVITY_VISUALIZER" target="DATA_R105_LV_SURVIVAL"><data key="edge_relationship_id">REL_R105_0042</data><data key="edge_source_entity_id">APP_R105_LONGEVITY_VISUALIZER</data><data key="edge_relationship_type">computes</data><data key="edge_target_entity_id">DATA_R105_LV_SURVIVAL</data><data key="edge_operational_context">Annual cohort death probabilities are converted to monthly survival and age-at-death probability distributions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Annual cohort death probabilities are converted to monthly survival and age-at-death probability distributions.</data></edge><edge id="REL_R105_0043" source="APP_R105_LONGEVITY_VISUALIZER" target="DATA_R105_LV_JOINT"><data key="edge_relationship_id">REL_R105_0043</data><data key="edge_source_entity_id">APP_R105_LONGEVITY_VISUALIZER</data><data key="edge_relationship_type">computes</data><data key="edge_target_entity_id">DATA_R105_LV_JOINT</data><data key="edge_operational_context">Combines individual survival functions for probability of both alive/both dead/one alive.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Combines individual survival functions for probability of both alive/both dead/one alive.</data></edge><edge id="REL_R105_0044" source="DATA_R105_LV_JOINT" target="DATA_R105_LV_SURVIVAL"><data key="edge_relationship_id">REL_R105_0044</data><data key="edge_source_entity_id">DATA_R105_LV_JOINT</data><data key="edge_relationship_type">derived_from</data><data key="edge_target_entity_id">DATA_R105_LV_SURVIVAL</data><data key="edge_operational_context">Joint two-person survival calculations derive from individual survival functions.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Joint two-person survival calculations derive from individual survival functions.</data></edge><edge id="REL_R105_0045" source="PROC_R105_GRANT_NEW" target="SVC_GRANTS_GOV"><data key="edge_relationship_id">REL_R105_0045</data><data key="edge_source_entity_id">PROC_R105_GRANT_NEW</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_GRANTS_GOV</data><data key="edge_operational_context">Competitive discretionary grant application is submitted through Grants.gov.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Competitive discretionary grant application is submitted through Grants.gov.</data></edge><edge id="REL_R105_0046" source="PROC_R105_GRANT_NEW" target="SVC_SAM_GOV"><data key="edge_relationship_id">REL_R105_0046</data><data key="edge_source_entity_id">PROC_R105_GRANT_NEW</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">SVC_SAM_GOV</data><data key="edge_operational_context">Applicant must register/update SAM.gov registration before applying to SSA grants.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Applicant must register/update SAM.gov registration before applying to SSA grants.</data></edge><edge id="REL_R105_0047" source="PROC_R105_GRANT_NEW" target="SVC_GRANTSOLUTIONS"><data key="edge_relationship_id">REL_R105_0047</data><data key="edge_source_entity_id">PROC_R105_GRANT_NEW</data><data key="edge_relationship_type">notifications_from</data><data key="edge_target_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_operational_context">Successful applicants receive award notification from GrantSolutions no later than September 30 of grant application year (site states calendar year).</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">Successful applicants receive award notification from GrantSolutions no later than September 30 of grant application year (site states calendar year).</data></edge><edge id="REL_R105_0048" source="PROC_R105_GRANT_CONT" target="SVC_GRANTSOLUTIONS"><data key="edge_relationship_id">REL_R105_0048</data><data key="edge_source_entity_id">PROC_R105_GRANT_CONT</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">SVC_GRANTSOLUTIONS</data><data key="edge_operational_context">SSA directs continuation applications through GrantSolutions as stipulated in announcement.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA directs continuation applications through GrantSolutions as stipulated in announcement.</data></edge><edge id="REL_R105_0049" source="ORG_SSA_OAG" target="PROC_R105_GRANT_NEW"><data key="edge_relationship_id">REL_R105_0049</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers</data><data key="edge_target_entity_id">PROC_R105_GRANT_NEW</data><data key="edge_operational_context">SSA OAG grant application and award administration workflow.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA OAG grant application and award administration workflow.</data></edge><edge id="REL_R105_0050" source="PROC_R105_TEFCA_QHIN_TEST" target="ORG_EHEALTH_EXCHANGE"><data key="edge_relationship_id">REL_R105_0050</data><data key="edge_source_entity_id">PROC_R105_TEFCA_QHIN_TEST</data><data key="edge_relationship_type">tests_integration_with</data><data key="edge_target_entity_id">ORG_EHEALTH_EXCHANGE</data><data key="edge_operational_context">SSA selected eHealth Exchange as its QHIN and disclosed integration testing in February 2026.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA selected eHealth Exchange as its QHIN and disclosed integration testing in February 2026.</data></edge><edge id="REL_R105_0051" source="PROC_R105_TEFCA_QHIN_TEST" target="NETWORK_TEFCA"><data key="edge_relationship_id">REL_R105_0051</data><data key="edge_source_entity_id">PROC_R105_TEFCA_QHIN_TEST</data><data key="edge_relationship_type">targets</data><data key="edge_target_entity_id">NETWORK_TEFCA</data><data key="edge_operational_context">Planned TEFCA exchange for disability government benefits determination; current production state unconfirmed.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">4</data><data key="edge_notes">Planned TEFCA exchange for disability government benefits determination; current production state unconfirmed.</data></edge><edge id="REL_R105_0052" source="USECASE_TEFCA_GBD" target="PROC_R105_TEFCA_QHIN_TEST"><data key="edge_relationship_id">REL_R105_0052</data><data key="edge_source_entity_id">USECASE_TEFCA_GBD</data><data key="edge_relationship_type">intended_to_support</data><data key="edge_target_entity_id">PROC_R105_TEFCA_QHIN_TEST</data><data key="edge_operational_context">SSA announced targeted Government Benefits Determination use case through QHIN connection.</data><data key="edge_observed_as_of">2026-10-07</data><data key="edge_confidence">5</data><data key="edge_notes">SSA announced targeted Government Benefits Determination use case through QHIN connection.</data></edge><edge id="REL_R119_001" source="APP_DOORS" target="R119_E001"><data key="edge_relationship_id">REL_R119_001</data><data key="edge_source_entity_id">APP_DOORS</data><data key="edge_relationship_type">maintains</data><data key="edge_target_entity_id">R119_E001</data><data key="edge_operational_context">office metadata source</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_002" source="APP_DOORS" target="R119_E002"><data key="edge_relationship_id">REL_R119_002</data><data key="edge_source_entity_id">APP_DOORS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R119_E002</data><data key="edge_operational_context">quarterly office directory</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_003" source="R119_E002" target="SVC_OFFICE_LOCATOR"><data key="edge_relationship_id">REL_R119_003</data><data key="edge_source_entity_id">R119_E002</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">SVC_OFFICE_LOCATOR</data><data key="edge_operational_context">Office Locator office directory</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_004" source="R119_E002" target="R119_E003"><data key="edge_relationship_id">REL_R119_004</data><data key="edge_source_entity_id">R119_E002</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R119_E003</data><data key="edge_operational_context">field_office public CSV</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_005" source="R119_E002" target="R119_E004"><data key="edge_relationship_id">REL_R119_005</data><data key="edge_source_entity_id">R119_E002</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R119_E004</data><data key="edge_operational_context">resident_station public CSV</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_006" source="R119_E002" target="R119_E005"><data key="edge_relationship_id">REL_R119_006</data><data key="edge_source_entity_id">R119_E002</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">R119_E005</data><data key="edge_operational_context">vsd_site public CSV</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_007" source="APP_MYDD" target="R119_E006"><data key="edge_relationship_id">REL_R119_007</data><data key="edge_source_entity_id">APP_MYDD</data><data key="edge_relationship_type">submits_to</data><data key="edge_target_entity_id">R119_E006</data><data key="edge_operational_context">Title II beneficiary direct deposit</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_008" source="R119_E006" target="SYS_MBR"><data key="edge_relationship_id">REL_R119_008</data><data key="edge_source_entity_id">R119_E006</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Title II direct-deposit change</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_009" source="APP_MYDD" target="R119_E007"><data key="edge_relationship_id">REL_R119_009</data><data key="edge_source_entity_id">APP_MYDD</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R119_E007</data><data key="edge_operational_context">Internet DD usage events</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_010" source="R119_E007" target="DATA_DD_INET"><data key="edge_relationship_id">REL_R119_010</data><data key="edge_source_entity_id">R119_E007</data><data key="edge_relationship_type">produces</data><data key="edge_target_entity_id">DATA_DD_INET</data><data key="edge_operational_context">monthly Internet direct-deposit counts</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_011" source="APP_MYDD" target="R119_E008"><data key="edge_relationship_id">REL_R119_011</data><data key="edge_source_entity_id">APP_MYDD</data><data key="edge_relationship_type">has_documented_rule</data><data key="edge_target_entity_id">R119_E008</data><data key="edge_operational_context">Title XVI/U.S. address eligibility</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_012" source="DB_MEDICARE_ODS" target="R119_E010"><data key="edge_relationship_id">REL_R119_012</data><data key="edge_source_entity_id">DB_MEDICARE_ODS</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">R119_E010</data><data key="edge_operational_context">daily Medicare workload data</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_013" source="R119_E010" target="DB_SUMS_COUNTS_DW"><data key="edge_relationship_id">REL_R119_013</data><data key="edge_source_entity_id">R119_E010</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">DB_SUMS_COUNTS_DW</data><data key="edge_operational_context">daily Medicare-to-SUMS refresh</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_014" source="DB_SUMS_COUNTS_DW" target="R119_E009"><data key="edge_relationship_id">REL_R119_014</data><data key="edge_source_entity_id">DB_SUMS_COUNTS_DW</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R119_E009</data><data key="edge_operational_context">annual Part D Extra Help statistical product</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_015" source="PROC_EXTRA_HELP" target="R119_E009"><data key="edge_relationship_id">REL_R119_015</data><data key="edge_source_entity_id">PROC_EXTRA_HELP</data><data key="edge_relationship_type">provides_measurement_for</data><data key="edge_target_entity_id">R119_E009</data><data key="edge_operational_context">eligibility determination outcomes</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_016" source="R119_E011" target="R119_E009"><data key="edge_relationship_id">REL_R119_016</data><data key="edge_source_entity_id">R119_E011</data><data key="edge_relationship_type">categorizes</data><data key="edge_target_entity_id">R119_E009</data><data key="edge_operational_context">state-level aggregate grouping</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_017" source="PROC_EXTRA_HELP" target="R119_E011"><data key="edge_relationship_id">REL_R119_017</data><data key="edge_source_entity_id">PROC_EXTRA_HELP</data><data key="edge_relationship_type">supplies</data><data key="edge_target_entity_id">R119_E011</data><data key="edge_operational_context">Extra Help application provided address</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_018" source="R119_E013" target="R119_E012"><data key="edge_relationship_id">REL_R119_018</data><data key="edge_source_entity_id">R119_E013</data><data key="edge_relationship_type">submitted_to</data><data key="edge_target_entity_id">R119_E012</data><data key="edge_operational_context">state-initiated identity verification</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_019" source="R119_E012" target="R119_E014"><data key="edge_relationship_id">REL_R119_019</data><data key="edge_source_entity_id">R119_E012</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">R119_E014</data><data key="edge_operational_context">response categories</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_020" source="R119_E012" target="DATA_HAVV_TXN_STATE"><data key="edge_relationship_id">REL_R119_020</data><data key="edge_source_entity_id">R119_E012</data><data key="edge_relationship_type">produces_statistics_for</data><data key="edge_target_entity_id">DATA_HAVV_TXN_STATE</data><data key="edge_operational_context">HAVV transaction counts</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_021" source="R119_E012" target="R119_E015"><data key="edge_relationship_id">REL_R119_021</data><data key="edge_source_entity_id">R119_E012</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R119_E015</data><data key="edge_operational_context">authorized state use</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_022" source="R119_E014" target="R119_E015"><data key="edge_relationship_id">REL_R119_022</data><data key="edge_source_entity_id">R119_E014</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R119_E015</data><data key="edge_operational_context">confidential results</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_023" source="DATA_EMPLOYER_SIGNATURE_PIN" target="R119_E016"><data key="edge_relationship_id">REL_R119_023</data><data key="edge_source_entity_id">DATA_EMPLOYER_SIGNATURE_PIN</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R119_E016</data><data key="edge_operational_context">opt-in annual PIN use</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_024" source="PROC_BSO_AUTHORIZATION" target="R119_E016"><data key="edge_relationship_id">REL_R119_024</data><data key="edge_source_entity_id">PROC_BSO_AUTHORIZATION</data><data key="edge_relationship_type">planned_to_support</data><data key="edge_target_entity_id">R119_E016</data><data key="edge_operational_context">December 2026 BSO authorization plan</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_025" source="PLAT_BSO" target="DATA_EMPLOYER_SIGNATURE_PIN"><data key="edge_relationship_id">REL_R119_025</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">planned_to_issue</data><data key="edge_target_entity_id">DATA_EMPLOYER_SIGNATURE_PIN</data><data key="edge_operational_context">administrator-facing annual PIN</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_026" source="PLAT_BSO" target="SVC_LOGIN_GOV"><data key="edge_relationship_id">REL_R119_026</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">accepts_identity_credential_from</data><data key="edge_target_entity_id">SVC_LOGIN_GOV</data><data key="edge_operational_context">employer and representative payee access</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_027" source="PLAT_BSO" target="SVC_IDME"><data key="edge_relationship_id">REL_R119_027</data><data key="edge_source_entity_id">PLAT_BSO</data><data key="edge_relationship_type">accepts_identity_credential_from</data><data key="edge_target_entity_id">SVC_IDME</data><data key="edge_operational_context">employer and representative payee access</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_028" source="DATA_SSI_IRS_CONTROLLED_ALERT" target="R119_E017"><data key="edge_relationship_id">REL_R119_028</data><data key="edge_source_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R119_E017</data><data key="edge_operational_context">unknown payer identity in tax alert</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_029" source="R119_E017" target="QRY_DEQY"><data key="edge_relationship_id">REL_R119_029</data><data key="edge_source_entity_id">R119_E017</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">employer identification number lookup</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_030" source="DATA_SSI_IRS_INFORMATIONAL_ALERT" target="R119_E018"><data key="edge_relationship_id">REL_R119_030</data><data key="edge_source_entity_id">DATA_SSI_IRS_INFORMATIONAL_ALERT</data><data key="edge_relationship_type">requires_conditional_review</data><data key="edge_target_entity_id">R119_E018</data><data key="edge_operational_context">nonmatching payee identity</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_031" source="R119_E018" target="QRY_DEQY"><data key="edge_relationship_id">REL_R119_031</data><data key="edge_source_entity_id">R119_E018</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">QRY_DEQY</data><data key="edge_operational_context">EIN-versus-SSN check</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_032" source="DATA_SSI_IRS_CONTROLLED_ALERT" target="R119_E019"><data key="edge_relationship_id">REL_R119_032</data><data key="edge_source_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R119_E019</data><data key="edge_operational_context">duplicate payer and amount</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_033" source="R119_E019" target="PROC_SSI_LIQUID_RESOURCE_RZ"><data key="edge_relationship_id">REL_R119_033</data><data key="edge_source_entity_id">R119_E019</data><data key="edge_relationship_type">informs</data><data key="edge_target_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_operational_context">resource tolerance evaluation</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_034" source="R119_E020" target="APP_E4641"><data key="edge_relationship_id">REL_R119_034</data><data key="edge_source_entity_id">R119_E020</data><data key="edge_relationship_type">requires_authorization</data><data key="edge_target_entity_id">APP_E4641</data><data key="edge_operational_context">bank verification authorization</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_035" source="R119_E020" target="ORG_BENEFICIARY_FI"><data key="edge_relationship_id">REL_R119_035</data><data key="edge_source_entity_id">R119_E020</data><data key="edge_relationship_type">seeks_primary_records_from</data><data key="edge_target_entity_id">ORG_BENEFICIARY_FI</data><data key="edge_operational_context">bank interest-bearing products</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_036" source="DATA_SSI_IRS_CONTROLLED_ALERT" target="R119_E020"><data key="edge_relationship_id">REL_R119_036</data><data key="edge_source_entity_id">DATA_SSI_IRS_CONTROLLED_ALERT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R119_E020</data><data key="edge_operational_context">interest account denied by recipient</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_037" source="SYS_MBR" target="R119_E021"><data key="edge_relationship_id">REL_R119_037</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">provides_lead_to</data><data key="edge_target_entity_id">R119_E021</data><data key="edge_operational_context">direct-deposit indicator may indicate account</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_038" source="SYS_SSR" target="R119_E021"><data key="edge_relationship_id">REL_R119_038</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">provides_lead_to</data><data key="edge_target_entity_id">R119_E021</data><data key="edge_operational_context">SSI record direct-deposit indicator</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_039" source="R119_E021" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">REL_R119_039</data><data key="edge_source_entity_id">R119_E021</data><data key="edge_relationship_type">documented_on</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">financial-account resource evidence</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_040" source="PROC_SSI_LIQUID_RESOURCE_RZ" target="R119_E022"><data key="edge_relationship_id">REL_R119_040</data><data key="edge_source_entity_id">PROC_SSI_LIQUID_RESOURCE_RZ</data><data key="edge_relationship_type">includes</data><data key="edge_target_entity_id">R119_E022</data><data key="edge_operational_context">month-opening resource calculation</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_041" source="R119_E022" target="UI_CCE_FIN_ACCOUNTS"><data key="edge_relationship_id">REL_R119_041</data><data key="edge_source_entity_id">R119_E022</data><data key="edge_relationship_type">documented_on</data><data key="edge_target_entity_id">UI_CCE_FIN_ACCOUNTS</data><data key="edge_operational_context">resource fact recording</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_042" source="UI_SSI_FI_PERMISSION" target="APP_EAFI"><data key="edge_relationship_id">REL_R119_042</data><data key="edge_source_entity_id">UI_SSI_FI_PERMISSION</data><data key="edge_relationship_type">permits_access_for</data><data key="edge_target_entity_id">APP_EAFI</data><data key="edge_operational_context">authorization before electronic verification</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_043" source="APP_SSNAP" target="SVC_SAVE"><data key="edge_relationship_id">REL_R119_043</data><data key="edge_source_entity_id">APP_SSNAP</data><data key="edge_relationship_type">uses_for_enumeration</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">SSN application lawful-status check</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_044" source="R119_E023" target="SVC_SAVE"><data key="edge_relationship_id">REL_R119_044</data><data key="edge_source_entity_id">R119_E023</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SVC_SAVE</data><data key="edge_operational_context">claims status verification</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_045" source="PROC_LAWFUL_PRESENCE_VERIFICATION" target="R119_E023"><data key="edge_relationship_id">REL_R119_045</data><data key="edge_source_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">R119_E023</data><data key="edge_operational_context">claims evidence verification</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_046" source="DATA_SAVE_DHS_SSN" target="R119_E024"><data key="edge_relationship_id">REL_R119_046</data><data key="edge_source_entity_id">DATA_SAVE_DHS_SSN</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R119_E024</data><data key="edge_operational_context">DHS response claimant-reported SSN caution</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_047" source="SYS_NUMIDENT" target="R119_E025"><data key="edge_relationship_id">REL_R119_047</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">supplies_work_authorization_code_to</data><data key="edge_target_entity_id">R119_E025</data><data key="edge_operational_context">work authorization is not payment lawful presence</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_048" source="R119_E025" target="PROC_LAWFUL_PRESENCE_VERIFICATION"><data key="edge_relationship_id">REL_R119_048</data><data key="edge_source_entity_id">R119_E025</data><data key="edge_relationship_type">requires_additional_proof_for</data><data key="edge_target_entity_id">PROC_LAWFUL_PRESENCE_VERIFICATION</data><data key="edge_operational_context">current lawful presence verification</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_049" source="R119_E026" target="REPO_CEF"><data key="edge_relationship_id">REL_R119_049</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">writes_to</data><data key="edge_target_entity_id">REPO_CEF</data><data key="edge_operational_context">CEF messages, assistance results, history</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_050" source="R119_E026" target="R119_E027"><data key="edge_relationship_id">REL_R119_050</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">grants</data><data key="edge_target_entity_id">R119_E027</data><data key="edge_operational_context">receiving office limited access</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_051" source="R119_E028" target="APP_EVIEW"><data key="edge_relationship_id">REL_R119_051</data><data key="edge_source_entity_id">R119_E028</data><data key="edge_relationship_type">screen_of</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">Assistance Request History</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_052" source="REPO_CEF" target="R119_E028"><data key="edge_relationship_id">REL_R119_052</data><data key="edge_source_entity_id">REPO_CEF</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R119_E028</data><data key="edge_operational_context">life-of-case AR history</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_053" source="R119_E026" target="R119_E029"><data key="edge_relationship_id">REL_R119_053</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R119_E029</data><data key="edge_operational_context">SSA-883 assistance case communication</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_054" source="R119_E026" target="R119_E030"><data key="edge_relationship_id">REL_R119_054</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R119_E030</data><data key="edge_operational_context">HA-4488 assistance case communication</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_055" source="R119_E026" target="R119_E031"><data key="edge_relationship_id">REL_R119_055</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R119_E031</data><data key="edge_operational_context">HA-4489 assistance case communication</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_056" source="R119_E026" target="R119_E032"><data key="edge_relationship_id">REL_R119_056</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">R119_E032</data><data key="edge_operational_context">SSA-5526 assistance case communication</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_057" source="R119_E026" target="R119_E033"><data key="edge_relationship_id">REL_R119_057</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">governed_by</data><data key="edge_target_entity_id">R119_E033</data><data key="edge_operational_context">FO request initiation restriction</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_058" source="R119_E026" target="R119_E034"><data key="edge_relationship_id">REL_R119_058</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">has_documented_exception</data><data key="edge_target_entity_id">R119_E034</data><data key="edge_operational_context">legacy capability differences</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_059" source="R119_E026" target="R119_E035"><data key="edge_relationship_id">REL_R119_059</data><data key="edge_source_entity_id">R119_E026</data><data key="edge_relationship_type">requires_conditional_paper_processing</data><data key="edge_target_entity_id">R119_E035</data><data key="edge_operational_context">local image repo interstate response</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_060" source="DATA_BEPUF2020_BENEFITS" target="R119_E036"><data key="edge_relationship_id">REL_R119_060</data><data key="edge_source_entity_id">DATA_BEPUF2020_BENEFITS</data><data key="edge_relationship_type">linked_by</data><data key="edge_target_entity_id">R119_E036</data><data key="edge_operational_context">synthetic sample linkage</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_061" source="DATA_BEPUF2020_EARNINGS" target="R119_E036"><data key="edge_relationship_id">REL_R119_061</data><data key="edge_source_entity_id">DATA_BEPUF2020_EARNINGS</data><data key="edge_relationship_type">linked_by</data><data key="edge_target_entity_id">R119_E036</data><data key="edge_operational_context">synthetic earnings linkage</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_062" source="DATA_BEPUF2020_BENEFITS" target="R119_E037"><data key="edge_relationship_id">REL_R119_062</data><data key="edge_source_entity_id">DATA_BEPUF2020_BENEFITS</data><data key="edge_relationship_type">subject_to_published_errata</data><data key="edge_target_entity_id">R119_E037</data><data key="edge_operational_context">April 2026 correction</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_063" source="INIT_SSI_IMPROVEMENT" target="R119_E038"><data key="edge_relationship_id">REL_R119_063</data><data key="edge_source_entity_id">INIT_SSI_IMPROVEMENT</data><data key="edge_relationship_type">recommended_to_evaluate</data><data key="edge_target_entity_id">R119_E038</data><data key="edge_operational_context">proposed customer visibility</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_064" source="INIT_SSI_IMPROVEMENT" target="R119_E039"><data key="edge_relationship_id">REL_R119_064</data><data key="edge_source_entity_id">INIT_SSI_IMPROVEMENT</data><data key="edge_relationship_type">recommended_to_evaluate</data><data key="edge_target_entity_id">R119_E039</data><data key="edge_operational_context">proposed self-service reporting</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_065" source="INIT_SSI_IMPROVEMENT" target="R119_E040"><data key="edge_relationship_id">REL_R119_065</data><data key="edge_source_entity_id">INIT_SSI_IMPROVEMENT</data><data key="edge_relationship_type">recommended_to_evaluate</data><data key="edge_target_entity_id">R119_E040</data><data key="edge_operational_context">more than ten million annual changes</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_066" source="INIT_CSCRM" target="PROC_CSCRA"><data key="edge_relationship_id">REL_R119_066</data><data key="edge_source_entity_id">INIT_CSCRM</data><data key="edge_relationship_type">requires_preaward_assessment</data><data key="edge_target_entity_id">PROC_CSCRA</data><data key="edge_operational_context">third-party risk before award</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_067" source="INIT_CSCRM" target="APP_TP_RISK_MGMT"><data key="edge_relationship_id">REL_R119_067</data><data key="edge_source_entity_id">INIT_CSCRM</data><data key="edge_relationship_type">tracks_third_party_relationships_in</data><data key="edge_target_entity_id">APP_TP_RISK_MGMT</data><data key="edge_operational_context">post-award oversight</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_068" source="SYS_MBR" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">REL_R119_068</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">100-percent OASDI benefit records</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_069" source="SYS_SSR" target="DATA_MONTHLY_STAT_SNAPSHOT"><data key="edge_relationship_id">REL_R119_069</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_MONTHLY_STAT_SNAPSHOT</data><data key="edge_operational_context">100-percent SSI payment records</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_070" source="APP_MCS" target="DB_T2_ODS"><data key="edge_relationship_id">REL_R119_070</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">DB_T2_ODS</data><data key="edge_operational_context">MCS to Title II ODS nightly</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R119_071" source="APP_MCS" target="DATA_RSI_APPLICATION_VOLUMES"><data key="edge_relationship_id">REL_R119_071</data><data key="edge_source_entity_id">APP_MCS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_RSI_APPLICATION_VOLUMES</data><data key="edge_operational_context">RSI collection captures app completions</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_001" source="R120_E002" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">REL_R120_001</data><data key="edge_source_entity_id">R120_E002</data><data key="edge_relationship_type">routed_to</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">CMS-2178-U2 referrals to processing centers go via Paperless.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_002" source="R120_E002" target="REPO_NDRED"><data key="edge_relationship_id">REL_R120_002</data><data key="edge_source_entity_id">R120_E002</data><data key="edge_relationship_type">copy_retained_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">SSA maintains a copy of CMS-2178-U2 in NDRED for audit and follow-up.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_003" source="R120_E002" target="SYS_MBR"><data key="edge_relationship_id">REL_R120_003</data><data key="edge_source_entity_id">R120_E002</data><data key="edge_relationship_type">corrects_or_refers</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Used when Medicare and MBR entitlement information require correction beyond direct online input.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_004" source="R120_E002" target="R120_E001"><data key="edge_relationship_id">REL_R120_004</data><data key="edge_source_entity_id">R120_E002</data><data key="edge_relationship_type">corrects_or_refers</data><data key="edge_target_entity_id">R120_E001</data><data key="edge_operational_context">HI-only problems go to CMS; MBR or combined errors go to SSA processing center as applicable.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_005" source="APP_POS" target="R120_E004"><data key="edge_relationship_id">REL_R120_005</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">used_for</data><data key="edge_target_entity_id">R120_E004</data><data key="edge_operational_context">POS is first-line correction attempt when address is incorrect on both MBR and HI.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_006" source="SYS_MBR" target="R120_E001"><data key="edge_relationship_id">REL_R120_006</data><data key="edge_source_entity_id">SYS_MBR</data><data key="edge_relationship_type">reconciled_with</data><data key="edge_target_entity_id">R120_E001</data><data key="edge_operational_context">MBR and HI can be inaccurate independently and require different correction/referral paths.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_007" source="APP_POS" target="R120_E005"><data key="edge_relationship_id">REL_R120_007</data><data key="edge_source_entity_id">APP_POS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R120_E005</data><data key="edge_operational_context">POS can correct name or sex data when both MBR and HI are wrong.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_008" source="R120_E005" target="DATA_CMS_EDB"><data key="edge_relationship_id">REL_R120_008</data><data key="edge_source_entity_id">R120_E005</data><data key="edge_relationship_type">triggers_subsequent_update_of</data><data key="edge_target_entity_id">DATA_CMS_EDB</data><data key="edge_operational_context">Official POMS explicitly says POS correction subsequently updates the CMS Enrollment Database.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_009" source="R120_E004" target="R120_E002"><data key="edge_relationship_id">REL_R120_009</data><data key="edge_source_entity_id">R120_E004</data><data key="edge_relationship_type">uses_form</data><data key="edge_target_entity_id">R120_E002</data><data key="edge_operational_context">Referral form required if POS cannot resolve MBR/HI or HI-only address issue.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_010" source="R120_E006" target="R120_E002"><data key="edge_relationship_id">REL_R120_010</data><data key="edge_source_entity_id">R120_E006</data><data key="edge_relationship_type">uses_form</data><data key="edge_target_entity_id">R120_E002</data><data key="edge_operational_context">HI-only mismatch requires CMS referral rather than MBR update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_011" source="R120_E007" target="R120_E002"><data key="edge_relationship_id">REL_R120_011</data><data key="edge_source_entity_id">R120_E007</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R120_E002</data><data key="edge_operational_context">Unresolved referral follow-up at 30 working days and escalation at 90 calendar days.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_012" source="R120_E008" target="R120_E001"><data key="edge_relationship_id">REL_R120_012</data><data key="edge_source_entity_id">R120_E008</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">R120_E001</data><data key="edge_operational_context">HMQ responses verify subsequent health insurance record corrections.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_013" source="R120_E009" target="R120_E001"><data key="edge_relationship_id">REL_R120_013</data><data key="edge_source_entity_id">R120_E009</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">R120_E001</data><data key="edge_operational_context">ESQ queried to confirm HI-only correction.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_014" source="R120_E002" target="R120_E003"><data key="edge_relationship_id">REL_R120_014</data><data key="edge_source_entity_id">R120_E002</data><data key="edge_relationship_type">may_correct</data><data key="edge_target_entity_id">R120_E003</data><data key="edge_operational_context">CMS-2178-U2 supports corrections to CMS-1966 card name/sex and related entitlement details.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_015" source="R120_E010" target="APP_SSI_CLAIMS_LOGICAL"><data key="edge_relationship_id">REL_R120_015</data><data key="edge_source_entity_id">R120_E010</data><data key="edge_relationship_type">initiates_or_controls</data><data key="edge_target_entity_id">APP_SSI_CLAIMS_LOGICAL</data><data key="edge_operational_context">RZ wizard is required for the related SSI claims-system RZ/LI interviews.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_016" source="APP_SSTNG" target="APP_SSI_REDET"><data key="edge_relationship_id">REL_R120_016</data><data key="edge_source_entity_id">APP_SSTNG</data><data key="edge_relationship_type">supports_workload_selection_for</data><data key="edge_target_entity_id">APP_SSI_REDET</data><data key="edge_operational_context">SSTNG is documented as RZ/LI diary workload selection interface; no direct technical connection to wizard assumed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_017" source="R120_E010" target="FORM_SSA8203BK"><data key="edge_relationship_id">REL_R120_017</data><data key="edge_source_entity_id">R120_E010</data><data key="edge_relationship_type">supports_completion_on</data><data key="edge_target_entity_id">FORM_SSA8203BK</data><data key="edge_operational_context">SSA-8203-BK documents redeterminations that cannot be completed in SSI Claims System under the published workflow.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_018" source="SYS_SSR" target="R120_E011"><data key="edge_relationship_id">REL_R120_018</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains_diary</data><data key="edge_target_entity_id">R120_E011</data><data key="edge_operational_context">KZ diary originates in SSI eligibility data and requires development of potential Title II insured status.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_019" source="R120_E011" target="SYS_MEF"><data key="edge_relationship_id">REL_R120_019</data><data key="edge_source_entity_id">R120_E011</data><data key="edge_relationship_type">development_cross_checks</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">Insured-status development relies on earnings coverage information; precise automated source interface not established.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_020" source="SYS_SSR" target="R120_E012"><data key="edge_relationship_id">REL_R120_020</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">contains_diary</data><data key="edge_target_entity_id">R120_E012</data><data key="edge_operational_context">KC age-90 limited issue control for Title XVI recipients.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_021" source="R120_E013" target="APP_SSI_REDET"><data key="edge_relationship_id">REL_R120_021</data><data key="edge_source_entity_id">R120_E013</data><data key="edge_relationship_type">scheduled_in</data><data key="edge_target_entity_id">APP_SSI_REDET</data><data key="edge_operational_context">UC profile used for redetermination scheduling after stated qualifying conditions.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_022" source="R120_E014" target="APP_SSI_REDET"><data key="edge_relationship_id">REL_R120_022</data><data key="edge_source_entity_id">R120_E014</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_SSI_REDET</data><data key="edge_operational_context">HEP, MEP and LEP frequencies depend on workload profile and category.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_023" source="DATA_MANUAL_DEEMING_LIST" target="PORTAL_DEEMING_LISTINGS"><data key="edge_relationship_id">REL_R120_023</data><data key="edge_source_entity_id">DATA_MANUAL_DEEMING_LIST</data><data key="edge_relationship_type">published_on</data><data key="edge_target_entity_id">PORTAL_DEEMING_LISTINGS</data><data key="edge_operational_context">October manual deemed case list is updated annually; not controlled by MI Central and does not create SSR diary.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_024" source="APP_SSTNG" target="R120_E011"><data key="edge_relationship_id">REL_R120_024</data><data key="edge_source_entity_id">APP_SSTNG</data><data key="edge_relationship_type">assists_prioritization_of</data><data key="edge_target_entity_id">R120_E011</data><data key="edge_operational_context">SSTNG permits workload selection by diary/profile for KZ and other listed SSI diary types.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_025" source="SVC_TCIS" target="R120_E015"><data key="edge_relationship_id">REL_R120_025</data><data key="edge_source_entity_id">SVC_TCIS</data><data key="edge_relationship_type">provides_printable_copy_of</data><data key="edge_target_entity_id">R120_E015</data><data key="edge_operational_context">TCIS permits one-time printing of FMS-1133 for FO and processing center authorized staff.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_026" source="APP_UPTQ" target="R120_E015"><data key="edge_relationship_id">REL_R120_026</data><data key="edge_source_entity_id">APP_UPTQ</data><data key="edge_relationship_type">used_to_verify_stop_code_for</data><data key="edge_target_entity_id">R120_E015</data><data key="edge_operational_context">Title XVI technicians query Treasury Status Query for stop code before requesting package.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_027" source="DB_PHUS" target="R120_E015"><data key="edge_relationship_id">REL_R120_027</data><data key="edge_source_entity_id">DB_PHUS</data><data key="edge_relationship_type">used_to_verify_stop_code_for</data><data key="edge_target_entity_id">R120_E015</data><data key="edge_operational_context">Title II technicians use PHUS stop code to confirm nonreceipt action.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_028" source="R120_E016" target="R120_E015"><data key="edge_relationship_id">REL_R120_028</data><data key="edge_source_entity_id">R120_E016</data><data key="edge_relationship_type">separate_from</data><data key="edge_target_entity_id">R120_E015</data><data key="edge_operational_context">L-stop generates a check copy/FMS-3858, not an FMS-1133 claim package.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_029" source="R120_E017" target="R120_E015"><data key="edge_relationship_id">REL_R120_029</data><data key="edge_source_entity_id">R120_E017</data><data key="edge_relationship_type">restricts_retrieval_of</data><data key="edge_target_entity_id">R120_E015</data><data key="edge_operational_context">Only one-time printing by authorized FO/PC; TSC requests via MDW.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_030" source="R120_E017" target="SVC_TCIS"><data key="edge_relationship_id">REL_R120_030</data><data key="edge_source_entity_id">R120_E017</data><data key="edge_relationship_type">accesses</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">One-time forms are viewed in TCIS and cease to be printable once Treasury receives completed form.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_031" source="R120_E019" target="R120_E015"><data key="edge_relationship_id">REL_R120_031</data><data key="edge_source_entity_id">R120_E019</data><data key="edge_relationship_type">ingests</data><data key="edge_target_entity_id">R120_E015</data><data key="edge_operational_context">FO/TSC/PC scanning of all FMS-1133 pages before forwarding to Treasury.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_032" source="R120_E019" target="APP_EP"><data key="edge_relationship_id">REL_R120_032</data><data key="edge_source_entity_id">R120_E019</data><data key="edge_relationship_type">stores_evidence_in</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">FMS-1133 captured in SSA Evidence Portal; not a verified Treasury master record.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_033" source="R120_E018" target="R120_E015"><data key="edge_relationship_id">REL_R120_033</data><data key="edge_source_entity_id">R120_E018</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R120_E015</data><data key="edge_operational_context">Age and timeliness determine Treasury forgery versus handwriting review and recovery authority.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_034" source="R120_E020" target="SVC_TCIS"><data key="edge_relationship_id">REL_R120_034</data><data key="edge_source_entity_id">R120_E020</data><data key="edge_relationship_type">investigates_status_in</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">vHelp and PC operations staff use TCIS status and can contact Treasury for unresolved claims.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_035" source="R120_E015" target="SVC_TCIS"><data key="edge_relationship_id">REL_R120_035</data><data key="edge_source_entity_id">R120_E015</data><data key="edge_relationship_type">supporting_evidence_for</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">Treasury records claim status and repayment outcomes in TCIS.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_036" source="APP_REACT" target="R120_E021"><data key="edge_relationship_id">REL_R120_036</data><data key="edge_source_entity_id">APP_REACT</data><data key="edge_relationship_type">triggers</data><data key="edge_target_entity_id">R120_E021</data><data key="edge_operational_context">Successful Title II LP credit or correction triggers PHUS Event 169.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_037" source="R120_E021" target="DB_PHUS"><data key="edge_relationship_id">REL_R120_037</data><data key="edge_source_entity_id">R120_E021</data><data key="edge_relationship_type">recorded_in</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">PHUS Event 169 UNNEG CK records unnegotiated check state.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_038" source="APP_REACT" target="R120_E022"><data key="edge_relationship_id">REL_R120_038</data><data key="edge_source_entity_id">APP_REACT</data><data key="edge_relationship_type">sets</data><data key="edge_target_entity_id">R120_E022</data><data key="edge_operational_context">REACT generally sets RCLRN N and generates corresponding LP notice.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_039" source="R120_E022" target="R120_E023"><data key="edge_relationship_id">REL_R120_039</data><data key="edge_source_entity_id">R120_E022</data><data key="edge_relationship_type">controls_creation_of</data><data key="edge_target_entity_id">R120_E023</data><data key="edge_operational_context">LP notice file sent to beneficiary when check appears uncashed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_040" source="R120_E024" target="R120_E023"><data key="edge_relationship_id">REL_R120_040</data><data key="edge_source_entity_id">R120_E024</data><data key="edge_relationship_type">requires</data><data key="edge_target_entity_id">R120_E023</data><data key="edge_operational_context">Recipient signs and identifies checks on notice; unsigned notices returned or filed without repayment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_041" source="R120_E024" target="DB_PHUS"><data key="edge_relationship_id">REL_R120_041</data><data key="edge_source_entity_id">R120_E024</data><data key="edge_relationship_type">verifies</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">Processing center checks MBR and PHUS before agreeing money still due.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_042" source="R120_E024" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">REL_R120_042</data><data key="edge_source_entity_id">R120_E024</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">Completely unsigned unmarked notice may be filed in processing-center Paperless with no repayment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_043" source="SYS_SSR" target="R120_E023"><data key="edge_relationship_id">REL_R120_043</data><data key="edge_source_entity_id">SYS_SSR</data><data key="edge_relationship_type">excluded_from</data><data key="edge_target_entity_id">R120_E023</data><data key="edge_operational_context">Title XVI LP credits require direct recipient contact rather than automatic Title II LP notice.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_044" source="R120_E025" target="APP_REACT"><data key="edge_relationship_id">REL_R120_044</data><data key="edge_source_entity_id">R120_E025</data><data key="edge_relationship_type">investigates_using</data><data key="edge_target_entity_id">APP_REACT</data><data key="edge_operational_context">REACT output can prove outstanding returned payment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_045" source="R120_E025" target="DB_PHUS"><data key="edge_relationship_id">REL_R120_045</data><data key="edge_source_entity_id">R120_E025</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">DB_PHUS</data><data key="edge_operational_context">If REACT output absent check PHUS for return or nonreceipt.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_046" source="R120_E025" target="SVC_TCIS"><data key="edge_relationship_id">REL_R120_046</data><data key="edge_source_entity_id">R120_E025</data><data key="edge_relationship_type">queries</data><data key="edge_target_entity_id">SVC_TCIS</data><data key="edge_operational_context">TCIS alternative confirms Treasury check return or EFT nonreceipt.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_047" source="R120_E025" target="SYS_MBR"><data key="edge_relationship_id">REL_R120_047</data><data key="edge_source_entity_id">R120_E025</data><data key="edge_relationship_type">relates_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Authorizer develops right beneficiary and same-earnings-record survivor entitlement.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_048" source="R120_E026" target="R120_E025"><data key="edge_relationship_id">REL_R120_048</data><data key="edge_source_entity_id">R120_E026</data><data key="edge_relationship_type">used_as_evidence_for</data><data key="edge_target_entity_id">R120_E025</data><data key="edge_operational_context">Same-address check delivery may support spouse LISH under conditions and three-month MBP threshold.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_049" source="R120_E027" target="R120_E025"><data key="edge_relationship_id">REL_R120_049</data><data key="edge_source_entity_id">R120_E027</data><data key="edge_relationship_type">excluded_from</data><data key="edge_target_entity_id">R120_E025</data><data key="edge_operational_context">Conserved payee assets must go to estate and are not deceased beneficiary underpayment.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_050" source="R120_E026" target="SYS_MBR"><data key="edge_relationship_id">REL_R120_050</data><data key="edge_source_entity_id">R120_E026</data><data key="edge_relationship_type">not_a_master_update_of</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Same check-delivery address is evidentiary support, not a new MBR address update.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_051" source="EX_EAE" target="R120_E028"><data key="edge_relationship_id">REL_R120_051</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">may_create</data><data key="edge_target_entity_id">R120_E028</data><data key="edge_operational_context">DHS transmitted enumeration data may result in EAE Investigate or Not Completed rather than automatic card.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_052" source="R120_E028" target="APP_SSNAP"><data key="edge_relationship_id">REL_R120_052</data><data key="edge_source_entity_id">R120_E028</data><data key="edge_relationship_type">held_for_review_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">SSA can search pending EAE records in SSNAP by identity attributes or alien registration number.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_053" source="EX_EAE" target="R120_E029"><data key="edge_relationship_id">REL_R120_053</data><data key="edge_source_entity_id">EX_EAE</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R120_E029</data><data key="edge_operational_context">EAE non-receipt guidance uses cycle-date under/over 14 days.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_054" source="R120_E029" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL_R120_054</data><data key="edge_source_entity_id">R120_E029</data><data key="edge_relationship_type">checks</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Technicians inspect Numident cycle date before deciding replacement-card application.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_055" source="EX_EBE" target="R120_E030"><data key="edge_relationship_id">REL_R120_055</data><data key="edge_source_entity_id">EX_EBE</data><data key="edge_relationship_type">may_create</data><data key="edge_target_entity_id">R120_E030</data><data key="edge_operational_context">EBE exceptions Investigate or Not Completed remain pending awaiting evidence.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_056" source="R120_E030" target="APP_SSNAP"><data key="edge_relationship_id">REL_R120_056</data><data key="edge_source_entity_id">R120_E030</data><data key="edge_relationship_type">held_for_review_in</data><data key="edge_target_entity_id">APP_SSNAP</data><data key="edge_operational_context">POMS says unprocessed EBE cases remain pending in SSNAP 365 days.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_057" source="DB_ALPHIDENT" target="R120_E028"><data key="edge_relationship_id">REL_R120_057</data><data key="edge_source_entity_id">DB_ALPHIDENT</data><data key="edge_relationship_type">supports_identity_resolution_in</data><data key="edge_target_entity_id">R120_E028</data><data key="edge_operational_context">EAE pending-case search may use alien registration number and name/DOB.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_058" source="DB_ALPHIDENT" target="R120_E030"><data key="edge_relationship_id">REL_R120_058</data><data key="edge_source_entity_id">DB_ALPHIDENT</data><data key="edge_relationship_type">supports_identity_resolution_in</data><data key="edge_target_entity_id">R120_E030</data><data key="edge_operational_context">EBE pending-case search may use alien registration number and name/DOB.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_059" source="R120_E031" target="R120_E033"><data key="edge_relationship_id">REL_R120_059</data><data key="edge_source_entity_id">R120_E031</data><data key="edge_relationship_type">reported_in</data><data key="edge_target_entity_id">R120_E033</data><data key="edge_operational_context">FO telephony answer/busy metrics published monthly in FO open-data CSV.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_060" source="R120_E034" target="R120_E033"><data key="edge_relationship_id">REL_R120_060</data><data key="edge_source_entity_id">R120_E034</data><data key="edge_relationship_type">provides_measurements_for</data><data key="edge_target_entity_id">R120_E033</data><data key="edge_operational_context">SSA says unnamed software routing vendor supplies field office telephone rate data.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_061" source="R120_E033" target="R120_E035"><data key="edge_relationship_id">REL_R120_061</data><data key="edge_source_entity_id">R120_E033</data><data key="edge_relationship_type">subject_to</data><data key="edge_target_entity_id">R120_E035</data><data key="edge_operational_context">Abandoned and 15-minute overflow calls are omitted from published answer/busy rate.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_062" source="R120_E032" target="R120_E031"><data key="edge_relationship_id">REL_R120_062</data><data key="edge_source_entity_id">R120_E032</data><data key="edge_relationship_type">historical_network_for</data><data key="edge_target_entity_id">R120_E031</data><data key="edge_operational_context">SSA says routing transition completed in 2012; current platform cannot be assumed.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_063" source="R120_E033" target="PORTAL_SSA_OPEN_DATA"><data key="edge_relationship_id">REL_R120_063</data><data key="edge_source_entity_id">R120_E033</data><data key="edge_relationship_type">published_through</data><data key="edge_target_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_operational_context">SSA open-data FO answer/busy CSV downloadable via portal.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_064" source="DB_SCDD" target="R120_E036"><data key="edge_relationship_id">REL_R120_064</data><data key="edge_source_entity_id">DB_SCDD</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R120_E036</data><data key="edge_operational_context">SCDD supports SSDI initial-claim spoken language quarterly publication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_065" source="DB_SCDD" target="R120_E037"><data key="edge_relationship_id">REL_R120_065</data><data key="edge_source_entity_id">DB_SCDD</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R120_E037</data><data key="edge_operational_context">SCDD supports SSI blind/disabled initial-claim spoken language quarterly publication.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_066" source="R120_E036" target="PORTAL_SSA_OPEN_DATA"><data key="edge_relationship_id">REL_R120_066</data><data key="edge_source_entity_id">R120_E036</data><data key="edge_relationship_type">published_through</data><data key="edge_target_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_operational_context">CSV distributed via SSA data site; not a beneficiary-level operational language master.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_067" source="R120_E037" target="PORTAL_SSA_OPEN_DATA"><data key="edge_relationship_id">REL_R120_067</data><data key="edge_source_entity_id">R120_E037</data><data key="edge_relationship_type">published_through</data><data key="edge_target_entity_id">PORTAL_SSA_OPEN_DATA</data><data key="edge_operational_context">CSV distributed via SSA data site; not a beneficiary-level operational language master.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R120_068" source="R120_E039" target="R120_E038"><data key="edge_relationship_id">REL_R120_068</data><data key="edge_source_entity_id">R120_E039</data><data key="edge_relationship_type">co_listed_with</data><data key="edge_target_entity_id">R120_E038</data><data key="edge_operational_context">Strategy and public AI inventory are co-listed on SSA AI page; no technical dependency inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL_R120_069" source="R120_E040" target="R120_E038"><data key="edge_relationship_id">REL_R120_069</data><data key="edge_source_entity_id">R120_E040</data><data key="edge_relationship_type">co_listed_with</data><data key="edge_target_entity_id">R120_E038</data><data key="edge_operational_context">Compliance plan and public use-case listing appear on same SSA AI page; no deployment inferred.</data><data key="edge_observed_as_of">2026-10-08</data><data key="edge_confidence">4</data><data key="edge_notes" /></edge><edge id="REL_R194_0001" source="PROC_R194_SAMOA_IDD" target="FORM_R194_SAMOA_1199"><data key="edge_relationship_id">REL_R194_0001</data><data key="edge_source_entity_id">PROC_R194_SAMOA_IDD</data><data key="edge_relationship_type">uses_input_form</data><data key="edge_target_entity_id">FORM_R194_SAMOA_1199</data><data key="edge_operational_context">Samoa form SSA-1199-OP30 supports intake by mail, telephone, or fax.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0002" source="PROC_R194_SAMOA_IDD" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0002</data><data key="edge_source_entity_id">PROC_R194_SAMOA_IDD</data><data key="edge_relationship_type">uses_account_store</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">SSA uses MBR direct-deposit fields for Samoa-specific coding.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0003" source="PROC_R194_SAMOA_IDD" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL_R194_0003</data><data key="edge_source_entity_id">PROC_R194_SAMOA_IDD</data><data key="edge_relationship_type">requires_treasury_enrollment</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Samoa requires ITS.gov information before initial payment processing and same-day updates for later changes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0004" source="PROC_R194_SAMOA_IDD" target="ORG_FRBKC"><data key="edge_relationship_id">REL_R194_0004</data><data key="edge_source_entity_id">PROC_R194_SAMOA_IDD</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">ORG_FRBKC</data><data key="edge_operational_context">FRBKC routes payments to the Samoa processing financial institution and may reject incomplete transactions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0005" source="DATA_R194_SAMOA_BANK_ADDR" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL_R194_0005</data><data key="edge_source_entity_id">DATA_R194_SAMOA_BANK_ADDR</data><data key="edge_relationship_type">captured_in</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Samoa bank address is entered into ITS.gov in WS/Town/Name format.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0006" source="DATA_R194_SAMOA_BENE_ADDR" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL_R194_0006</data><data key="edge_source_entity_id">DATA_R194_SAMOA_BENE_ADDR</data><data key="edge_relationship_type">captured_in</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Samoa beneficiary address is separately entered into ITS.gov.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0007" source="R194_E001" target="PROC_R194_SAMOA_IDD"><data key="edge_relationship_id">REL_R194_0007</data><data key="edge_source_entity_id">R194_E001</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_R194_SAMOA_IDD</data><data key="edge_operational_context">Samoa country-specific routing and account coding.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0008" source="R194_E001" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0008</data><data key="edge_source_entity_id">R194_E001</data><data key="edge_relationship_type">constrains_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">MBR stores SSA-specific derived routing and depositor account values.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0009" source="R194_E002" target="PROC_R194_SAMOA_IDD"><data key="edge_relationship_id">REL_R194_0009</data><data key="edge_source_entity_id">R194_E002</data><data key="edge_relationship_type">conflict_affects</data><data key="edge_target_entity_id">PROC_R194_SAMOA_IDD</data><data key="edge_operational_context">Source conflict: Section E describes O+16 digits while F describes O+13; Section F step 3 wording inconsistent with its stated reason.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0010" source="R194_E002" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL_R194_0010</data><data key="edge_source_entity_id">R194_E002</data><data key="edge_relationship_type">requires_manual_validation</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Actual accepted ITS.gov and MBR values cannot be resolved from contradictory examples alone.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0011" source="PROC_R194_SANMARINO_IDD" target="FORM_R194_SM_1199"><data key="edge_relationship_id">REL_R194_0011</data><data key="edge_source_entity_id">PROC_R194_SANMARINO_IDD</data><data key="edge_relationship_type">uses_input_form</data><data key="edge_target_entity_id">FORM_R194_SM_1199</data><data key="edge_operational_context">San Marino SSA-1199-OP38 accepted for application and bank-account coding.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0012" source="PROC_R194_SANMARINO_IDD" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0012</data><data key="edge_source_entity_id">PROC_R194_SANMARINO_IDD</data><data key="edge_relationship_type">writes_banking_data_to</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">San Marino country-specific RTN and DAN stored in existing MBR direct deposit fields.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0013" source="PROC_R194_SANMARINO_IDD" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL_R194_0013</data><data key="edge_source_entity_id">PROC_R194_SANMARINO_IDD</data><data key="edge_relationship_type">requires_treasury_enrollment</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">Same-day dual entry to SSA claims/postentitlement system and ITS.gov required for San Marino bank-data changes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0014" source="PROC_R194_SANMARINO_IDD" target="ORG_FRBKC"><data key="edge_relationship_id">REL_R194_0014</data><data key="edge_source_entity_id">PROC_R194_SANMARINO_IDD</data><data key="edge_relationship_type">routes_through</data><data key="edge_target_entity_id">ORG_FRBKC</data><data key="edge_operational_context">FRBKC transfers via processor bank to local San Marino EUR-denominated FI.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0015" source="DATA_R194_SM_SWIFT" target="SVC_ITS_GOV"><data key="edge_relationship_id">REL_R194_0015</data><data key="edge_source_entity_id">DATA_R194_SM_SWIFT</data><data key="edge_relationship_type">captured_in</data><data key="edge_target_entity_id">SVC_ITS_GOV</data><data key="edge_operational_context">ITS.gov account request includes SWIFT-BIC and IBAN for San Marino.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0016" source="R194_E003" target="PROC_R194_SANMARINO_IDD"><data key="edge_relationship_id">REL_R194_0016</data><data key="edge_source_entity_id">R194_E003</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">PROC_R194_SANMARINO_IDD</data><data key="edge_operational_context">San Marino bank routing encoding rule.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0017" source="R194_E003" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0017</data><data key="edge_source_entity_id">R194_E003</data><data key="edge_relationship_type">constrains_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">POMS requires a foreign beneficiary address as a condition for San Marino IDD action.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0018" source="R194_E004" target="PROC_IDD"><data key="edge_relationship_id">REL_R194_0018</data><data key="edge_source_entity_id">R194_E004</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">Foreign-to-domestic COA ends IDD eligibility under GN 02605.260.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0019" source="R194_E004" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0019</data><data key="edge_source_entity_id">R194_E004</data><data key="edge_relationship_type">requires_record_review</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Verify title II deposit fields before PEAD changes.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0020" source="R194_E005" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0020</data><data key="edge_source_entity_id">R194_E005</data><data key="edge_relationship_type">uses_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Lawful presence and NRA tax values reviewed on MBR before address update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0021" source="R194_E005" target="APP_POS"><data key="edge_relationship_id">REL_R194_0021</data><data key="edge_source_entity_id">R194_E005</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Separate screens document address, lawful presence, and tax withholding as needed.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0022" source="R194_E006" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0022</data><data key="edge_source_entity_id">R194_E006</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Claim jurisdiction determined independently of simple mailing address update.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0023" source="R194_E006" target="APP_POS"><data key="edge_relationship_id">REL_R194_0023</data><data key="edge_source_entity_id">R194_E006</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">APP_POS</data><data key="edge_operational_context">Transfer jurisdiction follows completion of address transaction if qualifying criteria cease.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0024" source="R194_E007" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0024</data><data key="edge_source_entity_id">R194_E007</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">U.S. correspondence address may differ from actual overseas residence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0025" source="R194_E007" target="PROC_IDD"><data key="edge_relationship_id">REL_R194_0025</data><data key="edge_source_entity_id">R194_E007</data><data key="edge_relationship_type">constrains</data><data key="edge_target_entity_id">PROC_IDD</data><data key="edge_operational_context">Foreign residence and IDD eligibility cannot be inferred from U.S. mailing location alone.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0026" source="R194_E008" target="SYS_MBR"><data key="edge_relationship_id">REL_R194_0026</data><data key="edge_source_entity_id">R194_E008</data><data key="edge_relationship_type">updates_record</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">PC manual update after payee selection where eRPS cannot process applicant without SSN.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0027" source="R194_E008" target="APP_MACADE"><data key="edge_relationship_id">REL_R194_0027</data><data key="edge_source_entity_id">R194_E008</data><data key="edge_relationship_type">processed_using</data><data key="edge_target_entity_id">APP_MACADE</data><data key="edge_operational_context">PC executes Title II representative-payee action via MACADE.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0028" source="R194_E009" target="SYS_SSR"><data key="edge_relationship_id">REL_R194_0028</data><data key="edge_source_entity_id">R194_E009</data><data key="edge_relationship_type">updates_record</data><data key="edge_target_entity_id">SYS_SSR</data><data key="edge_operational_context">FO uses Title XVI manual payee selection path.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0029" source="R194_E009" target="APP_ERPS"><data key="edge_relationship_id">REL_R194_0029</data><data key="edge_source_entity_id">R194_E009</data><data key="edge_relationship_type">excludes_normal_processing</data><data key="edge_target_entity_id">APP_ERPS</data><data key="edge_operational_context">eRPS is default only if identifying requirements can be met.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0030" source="DATA_R194_EAB_ORIGINAL" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL_R194_0030</data><data key="edge_source_entity_id">DATA_R194_EAB_ORIGINAL</data><data key="edge_relationship_type">supports_identity_assignment</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">State-supplied EAB data supports automated infant SSN assignment and Numident application creation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0031" source="DATA_R194_EAB_ORIGINAL" target="ORG_STATE_BVS"><data key="edge_relationship_id">REL_R194_0031</data><data key="edge_source_entity_id">DATA_R194_EAB_ORIGINAL</data><data key="edge_relationship_type">originates_with</data><data key="edge_target_entity_id">ORG_STATE_BVS</data><data key="edge_operational_context">State vital records agencies transmit hospital-collected birth registration data to SSA.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0032" source="R194_E010" target="DATA_R194_EAB_ORIGINAL"><data key="edge_relationship_id">REL_R194_0032</data><data key="edge_source_entity_id">R194_E010</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">DATA_R194_EAB_ORIGINAL</data><data key="edge_operational_context">Special condition for previously assigned SSN.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0033" source="R194_E010" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL_R194_0033</data><data key="edge_source_entity_id">R194_E010</data><data key="edge_relationship_type">impacts</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">EAB information can post to Numident even without new SSN issuance.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0034" source="ORG_SSA_OAG" target="PROG_R194_RDRC"><data key="edge_relationship_id">REL_R194_0034</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers_grant_program</data><data key="edge_target_entity_id">PROG_R194_RDRC</data><data key="edge_operational_context">SSA OAG identifies RDRC as a research and demonstration grant example.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0035" source="ORG_SSA_OAG" target="PROG_R194_ARDRAW"><data key="edge_relationship_id">REL_R194_0035</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers_grant_program</data><data key="edge_target_entity_id">PROG_R194_ARDRAW</data><data key="edge_operational_context">SSA OAG identifies ARDRAW as a research and demonstration grant example.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0036" source="ORG_SSA_OAG" target="PROG_R194_WIPA"><data key="edge_relationship_id">REL_R194_0036</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers_grant_program</data><data key="edge_target_entity_id">PROG_R194_WIPA</data><data key="edge_operational_context">SSA OAG identifies WIPA as a service grant supporting beneficiaries returning to work.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0037" source="ORG_SSA_OAG" target="PROG_R194_PABSS"><data key="edge_relationship_id">REL_R194_0037</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers_grant_program</data><data key="edge_target_entity_id">PROG_R194_PABSS</data><data key="edge_operational_context">SSA OAG identifies PABSS among service grants.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0038" source="ORG_SSA_OAG" target="PROG_R194_SPSSB"><data key="edge_relationship_id">REL_R194_0038</data><data key="edge_source_entity_id">ORG_SSA_OAG</data><data key="edge_relationship_type">administers_grant_program</data><data key="edge_target_entity_id">PROG_R194_SPSSB</data><data key="edge_operational_context">SSA OAG identifies SPSSB representative-payee service grants covering onsite reviews.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0039" source="DATA_R194_STAT2020_T2A26_COR" target="REPORT_R194_SUPPLEMENT_2020"><data key="edge_relationship_id">REL_R194_0039</data><data key="edge_source_entity_id">DATA_R194_STAT2020_T2A26_COR</data><data key="edge_relationship_type">corrects_publication</data><data key="edge_target_entity_id">REPORT_R194_SUPPLEMENT_2020</data><data key="edge_operational_context">April 21 2026 correction to family amounts and survivor-family minimum-wage PIA.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0040" source="DATA_R194_STAT2020_T2A17_COR" target="REPORT_R194_SUPPLEMENT_2020"><data key="edge_relationship_id">REL_R194_0040</data><data key="edge_source_entity_id">DATA_R194_STAT2020_T2A17_COR</data><data key="edge_relationship_type">corrects_publication</data><data key="edge_target_entity_id">REPORT_R194_SUPPLEMENT_2020</data><data key="edge_operational_context">March 6 2026 corrections to minimum PIAs (2013-19) and family maximum formulas.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R194_0041" source="DATA_R194_STAT2020_T4A2_COR" target="REPORT_R194_SUPPLEMENT_2020"><data key="edge_relationship_id">REL_R194_0041</data><data key="edge_source_entity_id">DATA_R194_STAT2020_T4A2_COR</data><data key="edge_relationship_type">corrects_publication</data><data key="edge_target_entity_id">REPORT_R194_SUPPLEMENT_2020</data><data key="edge_operational_context">December 5 2025 correction to 1977 Railroad Retirement transfer amount representation.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Official evidence supports the stated and time-bound operation, not undocumented architecture.</data></edge><edge id="REL_R195_0001" source="R195_E_PBGC" target="R195_E_PBGC_PLAN_CHANGES"><data key="edge_relationship_id">REL_R195_0001</data><data key="edge_source_entity_id">R195_E_PBGC</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">R195_E_PBGC_PLAN_CHANGES</data><data key="edge_operational_context">PBGC plan termination and merger information is supplied to SSA Central Office for pension plan address records (2019).</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0002" source="R195_E_PBGC_PLAN_CHANGES" target="R195_E_ERISA_PLAN_ADDR"><data key="edge_relationship_id">REL_R195_0002</data><data key="edge_source_entity_id">R195_E_PBGC_PLAN_CHANGES</data><data key="edge_relationship_type">supplies_information_for</data><data key="edge_target_entity_id">R195_E_ERISA_PLAN_ADDR</data><data key="edge_operational_context">PBGC plan merger/termination data support SSA pension plan address files; no beneficiary residential address update is asserted.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0003" source="R195_E_IRS_ERISA_QTR" target="R146_E0002"><data key="edge_relationship_id">REL_R195_0003</data><data key="edge_source_entity_id">R195_E_IRS_ERISA_QTR</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R146_E0002</data><data key="edge_operational_context">IRS sends SSA quarterly plan-administration changes for ERISA pension processes; exact storage target is not documented.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0004" source="R138_E0009" target="SYS_NUMIDENT"><data key="edge_relationship_id">REL_R195_0004</data><data key="edge_source_entity_id">R138_E0009</data><data key="edge_relationship_type">identity_matched_to</data><data key="edge_target_entity_id">SYS_NUMIDENT</data><data key="edge_operational_context">Paper Form 8955-SSA participant name/SSN processed by WBDOC is checked against Numident before adding to Employee Master File.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0005" source="R146_E0001" target="R146_E0002"><data key="edge_relationship_id">REL_R195_0005</data><data key="edge_source_entity_id">R146_E0001</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">R146_E0002</data><data key="edge_operational_context">Electronic IRS FIRE Form 8955-SSA flow is a separate input channel from paper WBDOC processing.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0006" source="R146_E0002" target="R138_E0010"><data key="edge_relationship_id">REL_R195_0006</data><data key="edge_source_entity_id">R146_E0002</data><data key="edge_relationship_type">generates</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">SSA monthly identifies benefit applicants with deferred-vested ERISA data and mails SSA-L99-C1 notice.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0007" source="R195_E_ERISA_PLAN_ADDR" target="R138_E0010"><data key="edge_relationship_id">REL_R195_0007</data><data key="edge_source_entity_id">R195_E_ERISA_PLAN_ADDR</data><data key="edge_relationship_type">provides_contact_for</data><data key="edge_target_entity_id">R138_E0010</data><data key="edge_operational_context">Pension plan address files support ERISA pension notices; do not treat plan address as beneficiary current residence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">4</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0008" source="APP_MAPS" target="R195_E_MAPS_MEDQ"><data key="edge_relationship_id">REL_R195_0008</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">R195_E_MAPS_MEDQ</data><data key="edge_operational_context">MAPS MEDQ query displays current and detailed IRS and pension/annuity agency data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0009" source="R195_E_MAPS_MEDQ" target="R195_E_MAPS_EIN"><data key="edge_relationship_id">REL_R195_0009</data><data key="edge_source_entity_id">R195_E_MAPS_MEDQ</data><data key="edge_relationship_type">exposes</data><data key="edge_target_entity_id">R195_E_MAPS_EIN</data><data key="edge_operational_context">MEDQ Detailed Agency Data exposes payer EIN for follow-up.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0010" source="R195_E_MAPS_EIN" target="R195_E_MAPS_AEQY"><data key="edge_relationship_id">REL_R195_0010</data><data key="edge_source_entity_id">R195_E_MAPS_EIN</data><data key="edge_relationship_type">queried_via</data><data key="edge_target_entity_id">R195_E_MAPS_AEQY</data><data key="edge_operational_context">Staff manually enter EIN through PCOM MFQM &gt; MISM &gt; AEQY query.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0011" source="R195_E_MAPS_AEQY" target="R195_E_MAPS_PAYER_LOCATION"><data key="edge_relationship_id">REL_R195_0011</data><data key="edge_source_entity_id">R195_E_MAPS_AEQY</data><data key="edge_relationship_type">returns</data><data key="edge_target_entity_id">R195_E_MAPS_PAYER_LOCATION</data><data key="edge_operational_context">AEQY returns payer name and business address; cannot infer claimant location.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0012" source="APP_MAPS" target="R195_E_MAPS_DWRC"><data key="edge_relationship_id">REL_R195_0012</data><data key="edge_source_entity_id">APP_MAPS</data><data key="edge_relationship_type">has_screen</data><data key="edge_target_entity_id">R195_E_MAPS_DWRC</data><data key="edge_operational_context">MAPS DWRC records verifications and contacts.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0013" source="R195_E_MAPS_IRS_ANNUITY" target="R195_E_MAPS_MEDQ"><data key="edge_relationship_id">REL_R195_0013</data><data key="edge_source_entity_id">R195_E_MAPS_IRS_ANNUITY</data><data key="edge_relationship_type">displayed_in</data><data key="edge_target_entity_id">R195_E_MAPS_MEDQ</data><data key="edge_operational_context">IRS pension/annuity form type, tax year, EIN and monthly amount appear in MEDQ Detailed Agency Data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0014" source="R195_E_MAPS_RECENCY" target="R195_E_MAPS_DWRC"><data key="edge_relationship_id">REL_R195_0014</data><data key="edge_source_entity_id">R195_E_MAPS_RECENCY</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">R195_E_MAPS_DWRC</data><data key="edge_operational_context">Most recent relevant evidence and conclusion must be documented on DWRC before Extra Help determination.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0015" source="FORM_SSA8510" target="R195_E_MAPS_PAYER_LOCATION"><data key="edge_relationship_id">REL_R195_0015</data><data key="edge_source_entity_id">FORM_SSA8510</data><data key="edge_relationship_type">authorizes_contact_to</data><data key="edge_target_entity_id">R195_E_MAPS_PAYER_LOCATION</data><data key="edge_operational_context">If claimant cannot supply evidence and disputes IRS pension data, SSA-8510 signature is required before contacting payer.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0016" source="R195_E_MAPS_OPM_FIRST" target="APP_MAPS"><data key="edge_relationship_id">REL_R195_0016</data><data key="edge_source_entity_id">R195_E_MAPS_OPM_FIRST</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_MAPS</data><data key="edge_operational_context">OPM pension direct data, not contemporaneous IRS copy, used to verify OPM annuities after May 23 2009 release.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0017" source="R195_E_MAPS_OLD_IRS_OPM" target="DB_MAPS"><data key="edge_relationship_id">REL_R195_0017</data><data key="edge_source_entity_id">R195_E_MAPS_OLD_IRS_OPM</data><data key="edge_relationship_type">stored_in</data><data key="edge_target_entity_id">DB_MAPS</data><data key="edge_operational_context">Pre-2009 IRS OPM annuity data may remain visible on MEDQ despite discontinued current feed.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0018" source="ORG_OPM" target="R195_E_MAPS_OPM_FIRST"><data key="edge_relationship_id">REL_R195_0018</data><data key="edge_source_entity_id">ORG_OPM</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">R195_E_MAPS_OPM_FIRST</data><data key="edge_operational_context">Direct OPM annuity data is specified as verification source after 2009 source precedence change.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0019" source="R195_E_STAT_SUPP_2025_2F" target="R195_E_STAT_2024_T2F4"><data key="edge_relationship_id">REL_R195_0019</data><data key="edge_source_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F4</data><data key="edge_operational_context">2025 Supplement Section 2.F publishes or republishes the specified time-bounded workload product.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0020" source="R195_E_STAT_SUPP_2025_2F" target="R195_E_STAT_2024_T2F5"><data key="edge_relationship_id">REL_R195_0020</data><data key="edge_source_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F5</data><data key="edge_operational_context">2025 Supplement Section 2.F publishes or republishes the specified time-bounded workload product.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0021" source="R195_E_STAT_SUPP_2025_2F" target="R195_E_STAT_2024_T2F6"><data key="edge_relationship_id">REL_R195_0021</data><data key="edge_source_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F6</data><data key="edge_operational_context">2025 Supplement Section 2.F publishes or republishes the specified time-bounded workload product.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0022" source="R195_E_STAT_SUPP_2025_2F" target="R195_E_STAT_2024_T2F8"><data key="edge_relationship_id">REL_R195_0022</data><data key="edge_source_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F8</data><data key="edge_operational_context">2025 Supplement Section 2.F publishes or republishes the specified time-bounded workload product.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0023" source="R195_E_STAT_SUPP_2025_2F" target="R195_E_STAT_2024_T2F9"><data key="edge_relationship_id">REL_R195_0023</data><data key="edge_source_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F9</data><data key="edge_operational_context">2025 Supplement Section 2.F publishes or republishes the specified time-bounded workload product.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0024" source="R195_E_STAT_SUPP_2025_2F" target="R195_E_STAT_2024_T2F11"><data key="edge_relationship_id">REL_R195_0024</data><data key="edge_source_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F11</data><data key="edge_operational_context">2025 Supplement Section 2.F publishes or republishes the specified time-bounded workload product.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0025" source="R195_E_STAT_SUPP_2025_2F" target="R195_E_STAT_ENUM_2024"><data key="edge_relationship_id">REL_R195_0025</data><data key="edge_source_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="edge_relationship_type">publishes</data><data key="edge_target_entity_id">R195_E_STAT_ENUM_2024</data><data key="edge_operational_context">2025 Supplement Section 2.F publishes or republishes the specified time-bounded workload product.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0026" source="SYS_IWMS" target="R195_E_STAT_2024_T2F4"><data key="edge_relationship_id">REL_R195_0026</data><data key="edge_source_entity_id">SYS_IWMS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F4</data><data key="edge_operational_context">Integrated Work Measurement System listed as source in 2025 Supplement.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0027" source="SYS_IWMS" target="R195_E_STAT_2024_T2F5"><data key="edge_relationship_id">REL_R195_0027</data><data key="edge_source_entity_id">SYS_IWMS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F5</data><data key="edge_operational_context">Integrated Work Measurement System listed as source in 2025 Supplement.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0028" source="SYS_IWMS" target="R195_E_STAT_2024_T2F6"><data key="edge_relationship_id">REL_R195_0028</data><data key="edge_source_entity_id">SYS_IWMS</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F6</data><data key="edge_operational_context">Integrated Work Measurement System listed as source in 2025 Supplement.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0029" source="DB_CPMS_MI" target="R195_E_STAT_2024_T2F8"><data key="edge_relationship_id">REL_R195_0029</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F8</data><data key="edge_operational_context">CPMS Management Information listed as source; metric definitions differ by table.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0030" source="DB_CPMS_MI" target="R195_E_STAT_2024_T2F9"><data key="edge_relationship_id">REL_R195_0030</data><data key="edge_source_entity_id">DB_CPMS_MI</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F9</data><data key="edge_operational_context">CPMS Management Information listed as source; metric definitions differ by table.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0031" source="DB_ARPS_MI" target="R195_E_STAT_2024_T2F11"><data key="edge_relationship_id">REL_R195_0031</data><data key="edge_source_entity_id">DB_ARPS_MI</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F11</data><data key="edge_operational_context">ARPS Management Information listed as source of Appeals Council statistics.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0032" source="R195_E_STAT_ENUM_PERF" target="R195_E_STAT_ENUM_2024"><data key="edge_relationship_id">REL_R195_0032</data><data key="edge_source_entity_id">R195_E_STAT_ENUM_PERF</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_STAT_ENUM_2024</data><data key="edge_operational_context">Enumeration Performance Reports supply issuance counts and age distribution, not a person-unique count.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0033" source="R195_E_STAT_2022_WEEK" target="R195_E_STAT_2024_T2F9"><data key="edge_relationship_id">REL_R195_0033</data><data key="edge_source_entity_id">R195_E_STAT_2022_WEEK</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F9</data><data key="edge_operational_context">FY2022 2.F9 hearing data exclude extra fiscal 2022 week.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0034" source="R195_E_STAT_2022_WEEK" target="R195_E_STAT_2024_T2F11"><data key="edge_relationship_id">REL_R195_0034</data><data key="edge_source_entity_id">R195_E_STAT_2022_WEEK</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">R195_E_STAT_2024_T2F11</data><data key="edge_operational_context">FY2022 2.F11 Appeals Council data include extra-week receipts and dispositions.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0035" source="R195_E_STAT_2F_DISCONT" target="R195_E_STAT_SUPP_2025_2F"><data key="edge_relationship_id">REL_R195_0035</data><data key="edge_source_entity_id">R195_E_STAT_2F_DISCONT</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">R195_E_STAT_SUPP_2025_2F</data><data key="edge_operational_context">Discontinued sections refer to publication routing and do not establish loss of operational source data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0036" source="DATA_CWHS" target="R195_E_CWHS_ACTIVE_2006"><data key="edge_relationship_id">REL_R195_0036</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">has_component</data><data key="edge_target_entity_id">R195_E_CWHS_ACTIVE_2006</data><data key="edge_operational_context">2006 CWHS sampled active/inactive populations defined by observed earnings postings.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0037" source="DATA_CWHS" target="R195_E_CWHS_INACTIVE_2006"><data key="edge_relationship_id">REL_R195_0037</data><data key="edge_source_entity_id">DATA_CWHS</data><data key="edge_relationship_type">has_component</data><data key="edge_target_entity_id">R195_E_CWHS_INACTIVE_2006</data><data key="edge_operational_context">2006 CWHS sampled active/inactive populations defined by observed earnings postings.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0038" source="SYS_MEF" target="R195_E_CWHS_ACTIVE_2006"><data key="edge_relationship_id">REL_R195_0038</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_CWHS_ACTIVE_2006</data><data key="edge_operational_context">CWHS active SSNs determined from recorded earnings in MEF; historical one-percent sample.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0039" source="SYS_MEF" target="R195_E_CWHS_INACTIVE_2006"><data key="edge_relationship_id">REL_R195_0039</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_CWHS_INACTIVE_2006</data><data key="edge_operational_context">CWHS inactive sample SSNs have no earnings posted to MEF as of 2006 sample.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0040" source="R195_E_CWHS_TIMING_2009" target="DATA_CWHS"><data key="edge_relationship_id">REL_R195_0040</data><data key="edge_source_entity_id">R195_E_CWHS_TIMING_2009</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">DATA_CWHS</data><data key="edge_operational_context">2009 document: annual January extract and spring validation of CWHS, period-specific not a current SLA.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0041" source="SYS_MEF" target="R195_E_CWHS_SE_2009"><data key="edge_relationship_id">REL_R195_0041</data><data key="edge_source_entity_id">SYS_MEF</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">R195_E_CWHS_SE_2009</data><data key="edge_operational_context">Self-employment analytical file contains IRS-origin detail beyond fields stored in MEF, per 2009 article.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0042" source="R195_E_CWHS_INDUSTRY_2009" target="DATA_CWHS"><data key="edge_relationship_id">REL_R195_0042</data><data key="edge_source_entity_id">R195_E_CWHS_INDUSTRY_2009</data><data key="edge_relationship_type">enriches</data><data key="edge_target_entity_id">DATA_CWHS</data><data key="edge_operational_context">IRS and Census employer industry classification inputs enhance CWHS sample data.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0043" source="R195_E_MEF_W2W3" target="SYS_MEF"><data key="edge_relationship_id">REL_R195_0043</data><data key="edge_source_entity_id">R195_E_MEF_W2W3</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">2009 W-2 / W-3 reconciliation gate before individual earnings posting.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0044" source="R195_E_MEF_WEEKLY_2009" target="SYS_MEF"><data key="edge_relationship_id">REL_R195_0044</data><data key="edge_source_entity_id">R195_E_MEF_WEEKLY_2009</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">As observed in 2009 the MEF was updated weekly; current cadence not established.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0045" source="SYS_NUMIDENT" target="DATA_CWHS"><data key="edge_relationship_id">REL_R195_0045</data><data key="edge_source_entity_id">SYS_NUMIDENT</data><data key="edge_relationship_type">source_for</data><data key="edge_target_entity_id">DATA_CWHS</data><data key="edge_operational_context">2009: Numident supplied demographics; MEF earnings and MBR annual benefits contributed to research sample.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0046" source="R195_E_SSA1099_MFQUERY" target="R145_E0013"><data key="edge_relationship_id">REL_R195_0046</data><data key="edge_source_entity_id">R195_E_SSA1099_MFQUERY</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">R145_E0013</data><data key="edge_operational_context">FO on-demand SSA-1099 replacement query is an alternative to online self-service or Central Office print.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0047" source="R195_E_SSA1099_DECEASED_MBR" target="SYS_MBR"><data key="edge_relationship_id">REL_R195_0047</data><data key="edge_source_entity_id">R195_E_SSA1099_DECEASED_MBR</data><data key="edge_relationship_type">uses_address_from</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">Deceased claimant benefit-tax statement goes to last MBR recorded address; policy does not mean current residence.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0048" source="R195_E_SSA1099_DEAD_LOGIN" target="APP_MYSSA"><data key="edge_relationship_id">REL_R195_0048</data><data key="edge_source_entity_id">R195_E_SSA1099_DEAD_LOGIN</data><data key="edge_relationship_type">blocks</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Deceased identity flag blocks access through eAccess; historical authentication application ROME noted.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0049" source="R195_E_SSA1099_TAX_WINDOW" target="APP_MYSSA"><data key="edge_relationship_id">REL_R195_0049</data><data key="edge_source_entity_id">R195_E_SSA1099_TAX_WINDOW</data><data key="edge_relationship_type">governs</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">Annual tax-form replacement request calendar constraints; historical records continue online.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0050" source="R195_E_OACT_SSAREA_POP" target="DATA_OACT_SOCSEC_POP_DOWNLOAD_2026"><data key="edge_relationship_id">REL_R195_0050</data><data key="edge_source_entity_id">R195_E_OACT_SSAREA_POP</data><data key="edge_relationship_type">applies_to</data><data key="edge_target_entity_id">DATA_OACT_SOCSEC_POP_DOWNLOAD_2026</data><data key="edge_operational_context">The area population downloadable data include specified overseas and territorial populations, not simply domestic Census residents.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0051" source="R195_E_OACT_PERIOD_COHORT" target="DATA_OACT_PERIOD_LIFE_2026"><data key="edge_relationship_id">REL_R195_0051</data><data key="edge_source_entity_id">R195_E_OACT_PERIOD_COHORT</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">DATA_OACT_PERIOD_LIFE_2026</data><data key="edge_operational_context">Calendar-year period life table interpretation for 2026 Trustees downloadable series.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R195_0052" source="R195_E_OACT_PERIOD_COHORT" target="DATA_OACT_COHORT_LIFE_2026"><data key="edge_relationship_id">REL_R195_0052</data><data key="edge_source_entity_id">R195_E_OACT_PERIOD_COHORT</data><data key="edge_relationship_type">qualifies</data><data key="edge_target_entity_id">DATA_OACT_COHORT_LIFE_2026</data><data key="edge_operational_context">Birth-year cohort life table interpretation for 2026 Trustees downloadable series.</data><data key="edge_observed_as_of">2026-10-11</data><data key="edge_confidence">5</data><data key="edge_notes">Directly documented processing or data provenance at cited date; not a claim of automatic system-to-system synchronization or current physical implementation.</data></edge><edge id="REL_R19_001" source="APP_PPC" target="DATA_PPC_ACR"><data key="edge_relationship_id">REL_R19_001</data><data key="edge_source_entity_id">APP_PPC</data><data key="edge_relationship_type">has_documented_component</data><data key="edge_target_entity_id">DATA_PPC_ACR</data><data key="edge_operational_context">PPC imports/adds forms to Action Control Records; ACR history and user identity form the work audit trail.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_002" source="DATA_PPC_ACR" target="DATA_TOEL"><data key="edge_relationship_id">REL_R19_002</data><data key="edge_source_entity_id">DATA_PPC_ACR</data><data key="edge_relationship_type">classified_by</data><data key="edge_target_entity_id">DATA_TOEL</data><data key="edge_operational_context">ACRs show Type-of-Event-Level metadata describing the work involved.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_003" source="PROC_PPC_STUB" target="DATA_PPC_ACR"><data key="edge_relationship_id">REL_R19_003</data><data key="edge_source_entity_id">PROC_PPC_STUB</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">DATA_PPC_ACR</data><data key="edge_operational_context">The stub-record or tap-on-the-shoulder process automatically creates a Paperless ACR for fully electronic actionable work.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_004" source="PROC_PPC_STUB" target="APP_EVIEW"><data key="edge_relationship_id">REL_R19_004</data><data key="edge_source_entity_id">PROC_PPC_STUB</data><data key="edge_relationship_type">references_work_in</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">For examples such as ALJ reversals, the ACR tells the technician to access eView for the decision and process the action.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_005" source="APP_PCACS" target="DATA_PCACS_ECR"><data key="edge_relationship_id">REL_R19_005</data><data key="edge_source_entity_id">APP_PCACS</data><data key="edge_relationship_type">creates</data><data key="edge_target_entity_id">DATA_PCACS_ECR</data><data key="edge_operational_context">PCACS creates an Electronic Control Record when a listing arrives and no paper is associated with it.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_006" source="DATA_PCACS_ECR" target="APP_PCACS"><data key="edge_relationship_id">REL_R19_006</data><data key="edge_source_entity_id">DATA_PCACS_ECR</data><data key="edge_relationship_type">placeholder_in</data><data key="edge_target_entity_id">APP_PCACS</data><data key="edge_operational_context">POMS describes the ECR as a placeholder in PCACS that permits transactions for accounts without a paper folder.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_007" source="PROC_DOTEL" target="PROC_INTERCOMP_ASSIST"><data key="edge_relationship_id">REL_R19_007</data><data key="edge_source_entity_id">PROC_DOTEL</data><data key="edge_relationship_type">mode_of</data><data key="edge_target_entity_id">PROC_INTERCOMP_ASSIST</data><data key="edge_operational_context">POMS lists this as a mode for requesting assistance from another SSA office/component.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_008" source="APP_PCACS" target="PROC_INTERCOMP_ASSIST"><data key="edge_relationship_id">REL_R19_008</data><data key="edge_source_entity_id">APP_PCACS</data><data key="edge_relationship_type">mode_of</data><data key="edge_target_entity_id">PROC_INTERCOMP_ASSIST</data><data key="edge_operational_context">POMS lists this as a mode for requesting assistance from another SSA office/component.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_009" source="APP_MDW_AI" target="PROC_INTERCOMP_ASSIST"><data key="edge_relationship_id">REL_R19_009</data><data key="edge_source_entity_id">APP_MDW_AI</data><data key="edge_relationship_type">mode_of</data><data key="edge_target_entity_id">PROC_INTERCOMP_ASSIST</data><data key="edge_operational_context">POMS lists this as a mode for requesting assistance from another SSA office/component.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_010" source="APP_E562" target="PROC_INTERCOMP_ASSIST"><data key="edge_relationship_id">REL_R19_010</data><data key="edge_source_entity_id">APP_E562</data><data key="edge_relationship_type">mode_of</data><data key="edge_target_entity_id">PROC_INTERCOMP_ASSIST</data><data key="edge_operational_context">POMS lists this as a mode for requesting assistance from another SSA office/component.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_011" source="APP_M2M" target="PROC_INTERCOMP_ASSIST"><data key="edge_relationship_id">REL_R19_011</data><data key="edge_source_entity_id">APP_M2M</data><data key="edge_relationship_type">mode_of</data><data key="edge_target_entity_id">PROC_INTERCOMP_ASSIST</data><data key="edge_operational_context">POMS lists this as a mode for requesting assistance from another SSA office/component.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_012" source="APP_M2M" target="PROC_INTERCOMP_ASSIST"><data key="edge_relationship_id">REL_R19_012</data><data key="edge_source_entity_id">APP_M2M</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_INTERCOMP_ASSIST</data><data key="edge_operational_context">OIG describes M2M as a two-way communication tool for priority inquiries requiring action by another office.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_013" source="QRY_DEQY" target="SYS_MEF"><data key="edge_relationship_id">REL_R19_013</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">DEQY displays detailed earnings data extracted from the Master Earnings File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_014" source="QRY_DEQY" target="DB_EIF"><data key="edge_relationship_id">REL_R19_014</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">DB_EIF</data><data key="edge_operational_context">DEQY also displays employer-related data extracted from the Employer Identification File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_015" source="QRY_SEQY" target="SYS_MEF"><data key="edge_relationship_id">REL_R19_015</data><data key="edge_source_entity_id">QRY_SEQY</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_MEF</data><data key="edge_operational_context">SEQY displays yearly earnings totals from the Master Earnings File.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_016" source="QRY_DEQY" target="TECH_PCOM"><data key="edge_relationship_id">REL_R19_016</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">TECH_PCOM</data><data key="edge_operational_context">SSA policy documents obtaining DEQY through IBM Personal Communications.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_017" source="TECH_PCOM" target="APP_MFQM"><data key="edge_relationship_id">REL_R19_017</data><data key="edge_source_entity_id">TECH_PCOM</data><data key="edge_relationship_type">accesses</data><data key="edge_target_entity_id">APP_MFQM</data><data key="edge_operational_context">The PCOM DEQY procedure begins from the Master File Query Menu.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_018" source="QRY_DEQY" target="APP_EVIEW"><data key="edge_relationship_id">REL_R19_018</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">accessed_via</data><data key="edge_target_entity_id">APP_EVIEW</data><data key="edge_operational_context">SSA policy documents DEQY access from eView's Queries area.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_019" source="QRY_DEQY" target="REPO_EF"><data key="edge_relationship_id">REL_R19_019</data><data key="edge_source_entity_id">QRY_DEQY</data><data key="edge_relationship_type">can_be_saved_to</data><data key="edge_target_entity_id">REPO_EF</data><data key="edge_operational_context">The eView DEQY workflow includes a View &amp; Save to EF action.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_020" source="TECH_PCOM" target="ORG_IBM"><data key="edge_relationship_id">REL_R19_020</data><data key="edge_source_entity_id">TECH_PCOM</data><data key="edge_relationship_type">uses_vendor</data><data key="edge_target_entity_id">ORG_IBM</data><data key="edge_operational_context">POMS names IBM Personal Communications as the client technology used for the DEQY access path.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_021" source="EX_EMILRECS" target="ORG_NARA"><data key="edge_relationship_id">REL_R19_021</data><data key="edge_source_entity_id">EX_EMILRECS</data><data key="edge_relationship_type">serves_partner</data><data key="edge_target_entity_id">ORG_NARA</data><data key="edge_operational_context">NARA and SSA developed eMilrecs for electronic military-service verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_022" source="ORG_NARA" target="EX_EMILRECS"><data key="edge_relationship_id">REL_R19_022</data><data key="edge_source_entity_id">ORG_NARA</data><data key="edge_relationship_type">provides</data><data key="edge_target_entity_id">EX_EMILRECS</data><data key="edge_operational_context">NARA supplies military-service documentation as attachments through eMilrecs.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_023" source="EX_EMILRECS" target="APP_EVID"><data key="edge_relationship_id">REL_R19_023</data><data key="edge_source_entity_id">EX_EMILRECS</data><data key="edge_relationship_type">verification_documented_in</data><data key="edge_target_entity_id">APP_EVID</data><data key="edge_operational_context">Field-office procedure records acceptable military-service evidence on the EVID screen in Shared Processes.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_024" source="EX_EMILRECS" target="REPO_NDRED"><data key="edge_relationship_id">REL_R19_024</data><data key="edge_source_entity_id">EX_EMILRECS</data><data key="edge_relationship_type">stores_evidence_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">Field-office procedure scans NARA documents into NDRed through Evidence Portal.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_025" source="EX_EMILRECS" target="APP_EP"><data key="edge_relationship_id">REL_R19_025</data><data key="edge_source_entity_id">EX_EMILRECS</data><data key="edge_relationship_type">routes_documents_through</data><data key="edge_target_entity_id">APP_EP</data><data key="edge_operational_context">Evidence Portal is used to scan eMilrecs/NARA documents into NDRed.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_026" source="EX_EMILRECS" target="APP_PPC"><data key="edge_relationship_id">REL_R19_026</data><data key="edge_source_entity_id">EX_EMILRECS</data><data key="edge_relationship_type">imports_documents_to</data><data key="edge_target_entity_id">APP_PPC</data><data key="edge_operational_context">Processing-center procedure saves the NARA document and imports it into Paperless.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_027" source="EX_EIWO" target="APP_COGS"><data key="edge_relationship_id">REL_R19_027</data><data key="edge_source_entity_id">EX_EIWO</data><data key="edge_relationship_type">updates</data><data key="edge_target_entity_id">APP_COGS</data><data key="edge_operational_context">Accepted electronic income-withholding orders automatically update COGS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_028" source="APP_COGS" target="APP_ORS"><data key="edge_relationship_id">REL_R19_028</data><data key="edge_source_entity_id">APP_COGS</data><data key="edge_relationship_type">stores_order_copy_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">A copy of an accepted e-IWO is automatically stored in ORS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_029" source="EX_EIWO" target="APP_PPC"><data key="edge_relationship_id">REL_R19_029</data><data key="edge_source_entity_id">EX_EIWO</data><data key="edge_relationship_type">routes_rejections_to</data><data key="edge_target_entity_id">APP_PPC</data><data key="edge_operational_context">Specified COGS rejects are directed to Paperless for manual processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_030" source="EX_EIWO" target="DATA_PPC_ACR"><data key="edge_relationship_id">REL_R19_030</data><data key="edge_source_entity_id">EX_EIWO</data><data key="edge_relationship_type">rejection_creates</data><data key="edge_target_entity_id">DATA_PPC_ACR</data><data key="edge_operational_context">For specified reject reasons, Paperless creates a new ACR under garnishment/e-IWO reject TOELs.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_031" source="APP_GARNISH_NOTICE" target="DB_GARNISHMENT"><data key="edge_relationship_id">REL_R19_031</data><data key="edge_source_entity_id">APP_GARNISH_NOTICE</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">DB_GARNISHMENT</data><data key="edge_operational_context">The automated Garnishment Notice System uses information from the Garnishment DB2 database.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_032" source="APP_GARNISH_NOTICE" target="SYS_MBR"><data key="edge_relationship_id">REL_R19_032</data><data key="edge_source_entity_id">APP_GARNISH_NOTICE</data><data key="edge_relationship_type">reads</data><data key="edge_target_entity_id">SYS_MBR</data><data key="edge_operational_context">The Garnishment Notice System also uses MBR data.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_033" source="APP_GARNISH_NOTICE" target="APP_CCM"><data key="edge_relationship_id">REL_R19_033</data><data key="edge_source_entity_id">APP_GARNISH_NOTICE</data><data key="edge_relationship_type">feeds</data><data key="edge_target_entity_id">APP_CCM</data><data key="edge_operational_context">Beginning in summer 2020, the garnishment notice system passes information to CCM for notice creation.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_034" source="APP_GARNISH_NOTICE" target="TECH_DB2"><data key="edge_relationship_id">REL_R19_034</data><data key="edge_source_entity_id">APP_GARNISH_NOTICE</data><data key="edge_relationship_type">runs_on</data><data key="edge_target_entity_id">TECH_DB2</data><data key="edge_operational_context">The underlying garnishment database is explicitly identified as DB2.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_035" source="DB_TAXY" target="ORG_TREASURY"><data key="edge_relationship_id">REL_R19_035</data><data key="edge_source_entity_id">DB_TAXY</data><data key="edge_relationship_type">notifies</data><data key="edge_target_entity_id">ORG_TREASURY</data><data key="edge_operational_context">TAXY input of a paper levy automatically notifies Treasury to terminate an overlapping FPLP deduction.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_036" source="DB_TAXY" target="REPO_NDRED"><data key="edge_relationship_id">REL_R19_036</data><data key="edge_source_entity_id">DB_TAXY</data><data key="edge_relationship_type">generated_notice_stored_in</data><data key="edge_target_entity_id">REPO_NDRED</data><data key="edge_operational_context">POMS directs technicians to fax TAXY-generated exemption statement notices into NDRed.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_037" source="PROC_FPLP" target="SVC_TOP"><data key="edge_relationship_id">REL_R19_037</data><data key="edge_source_entity_id">PROC_FPLP</data><data key="edge_relationship_type">executed_through</data><data key="edge_target_entity_id">SVC_TOP</data><data key="edge_operational_context">POMS states Treasury Offset Program processes the automated tax levies that reduce SSA Title II benefits.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_038" source="PROC_FPLP" target="APP_ORS"><data key="edge_relationship_id">REL_R19_038</data><data key="edge_source_entity_id">PROC_FPLP</data><data key="edge_relationship_type">stores_notices_in</data><data key="edge_target_entity_id">APP_ORS</data><data key="edge_operational_context">IRS/Fiscal Service notices associated with FPLP are retrievable through ORS.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_039" source="PROC_FPLP" target="DATA_FPLP_PAYMENT_RECORD"><data key="edge_relationship_id">REL_R19_039</data><data key="edge_source_entity_id">PROC_FPLP</data><data key="edge_relationship_type">uses</data><data key="edge_target_entity_id">DATA_FPLP_PAYMENT_RECORD</data><data key="edge_operational_context">SSA sends a system-generated payment record to Fiscal Service for FPLP processing; POMS says it is not the MBR.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_040" source="DATA_FPLP_PAYMENT_RECORD" target="ORG_BFS"><data key="edge_relationship_id">REL_R19_040</data><data key="edge_source_entity_id">DATA_FPLP_PAYMENT_RECORD</data><data key="edge_relationship_type">sent_to</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">The payment record is sent automatically to Fiscal Service for disbursement/levy processing.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_041" source="DATA_FPLP_BYPASS_CODE" target="DATA_FPLP_PAYMENT_RECORD"><data key="edge_relationship_id">REL_R19_041</data><data key="edge_source_entity_id">DATA_FPLP_BYPASS_CODE</data><data key="edge_relationship_type">part_of</data><data key="edge_target_entity_id">DATA_FPLP_PAYMENT_RECORD</data><data key="edge_operational_context">SSA systems automatically place the bypass code on the payment record when exclusion conditions apply.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_042" source="DATA_FPLP_BYPASS_CODE" target="ORG_BFS"><data key="edge_relationship_id">REL_R19_042</data><data key="edge_source_entity_id">DATA_FPLP_BYPASS_CODE</data><data key="edge_relationship_type">signals_exclusion_to</data><data key="edge_target_entity_id">ORG_BFS</data><data key="edge_operational_context">The bypass code tells Fiscal Service not to levy an excluded Social Security payment.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_043" source="SVC_TWN" target="PROC_WAGE_VERIFY"><data key="edge_relationship_id">REL_R19_043</data><data key="edge_source_entity_id">SVC_TWN</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_WAGE_VERIFY</data><data key="edge_operational_context">SSA policy recognizes TWN as an approved primary wage-evidence source when higher-priority/automated evidence is unavailable and authorization exists.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_044" source="SVC_VERIFYADV" target="PROC_WAGE_VERIFY"><data key="edge_relationship_id">REL_R19_044</data><data key="edge_source_entity_id">SVC_VERIFYADV</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_WAGE_VERIFY</data><data key="edge_operational_context">SSA policy recognizes VerifyAdvantage as an approved primary wage-evidence source.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_045" source="EX_PIE" target="PROC_WAGE_VERIFY"><data key="edge_relationship_id">REL_R19_045</data><data key="edge_source_entity_id">EX_PIE</data><data key="edge_relationship_type">provides_primary_wage_evidence_to</data><data key="edge_target_entity_id">PROC_WAGE_VERIFY</data><data key="edge_operational_context">PIE/PDP wage and employment information is a primary automated evidence path in SSA wage verification.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_046" source="SVC_TWN" target="ORG_EQUIFAX_WS"><data key="edge_relationship_id">REL_R19_046</data><data key="edge_source_entity_id">SVC_TWN</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_EQUIFAX_WS</data><data key="edge_operational_context">CFPB identifies Equifax Workforce Solutions as the operator of The Work Number.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_047" source="SVC_VERIFYADV" target="ORG_FIRST_ADVANTAGE"><data key="edge_relationship_id">REL_R19_047</data><data key="edge_source_entity_id">SVC_VERIFYADV</data><data key="edge_relationship_type">operated_by</data><data key="edge_target_entity_id">ORG_FIRST_ADVANTAGE</data><data key="edge_operational_context">VerifyAdvantage's primary site identifies it as First Advantage's web-based employment and income verification service.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">4</data></edge><edge id="REL_R19_048" source="APP_WEIA" target="SVC_TWN"><data key="edge_relationship_id">REL_R19_048</data><data key="edge_source_entity_id">APP_WEIA</data><data key="edge_relationship_type">authorizes_access_to</data><data key="edge_target_entity_id">SVC_TWN</data><data key="edge_operational_context">SSA requires valid wage and employment information authorization before technicians obtain wage data from electronic wage verification companies.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_049" source="APP_WEIA" target="SVC_VERIFYADV"><data key="edge_relationship_id">REL_R19_049</data><data key="edge_source_entity_id">APP_WEIA</data><data key="edge_relationship_type">authorizes_access_to</data><data key="edge_target_entity_id">SVC_VERIFYADV</data><data key="edge_operational_context">SSA requires valid wage and employment information authorization before technicians obtain wage data from electronic wage verification companies.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R19_050" source="SVC_TWN" target="APP_EWORK"><data key="edge_relationship_id">REL_R19_050</data><data key="edge_source_entity_id">SVC_TWN</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">APP_EWORK</data><data key="edge_operational_context">Disability work policy directs technicians to verify earnings through approved third-party services such as TWN and code monthly earnings in eWork.</data><data key="edge_observed_as_of">2026-10-03</data><data key="edge_confidence">5</data></edge><edge id="REL_R26_001" source="DB_APPT_SYSTEM_MI" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL_R26_001</data><data key="edge_source_entity_id">DB_APPT_SYSTEM_MI</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA Open Data says this asset provides Appointment/Leads/800# management-information reports. This edge represents reporting scope only, not a physical interface.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">4</data><data key="edge_notes">No source-system feed is inferred.</data></edge><edge id="REL_R26_002" source="DB_APPT_SCHED_MI" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL_R26_002</data><data key="edge_source_entity_id">DB_APPT_SCHED_MI</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA Open Data says this asset provides Appointment/Leads/800 management-information reports. This edge represents reporting scope only, not a physical interface.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">4</data><data key="edge_notes">No source-system feed is inferred.</data></edge><edge id="REL_R26_003" source="DB_MYSSA_REG_MI" target="APP_MYSSA"><data key="edge_relationship_id">REL_R26_003</data><data key="edge_source_entity_id">DB_MYSSA_REG_MI</data><data key="edge_relationship_type">tracks_management_information_for</data><data key="edge_target_entity_id">APP_MYSSA</data><data key="edge_operational_context">SSA Open Data explicitly says the asset tracks management information for the MySSA suite of services.</data><data key="edge_observed_as_of">2026-07-28</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_004" source="APP_ESD_MI" target="DOM_E_SERVICES"><data key="edge_relationship_id">REL_R26_004</data><data key="edge_source_entity_id">APP_ESD_MI</data><data key="edge_relationship_type">produces_management_information_for</data><data key="edge_target_entity_id">DOM_E_SERVICES</data><data key="edge_operational_context">SSA Open Data describes the application as producing electronic-service-delivery management information.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">This is a functional/domain relationship; physical storage is not specified.</data></edge><edge id="REL_R26_005" source="DB_ESERVICES_MI_STAGE" target="DOM_E_SERVICES"><data key="edge_relationship_id">REL_R26_005</data><data key="edge_source_entity_id">DB_ESERVICES_MI_STAGE</data><data key="edge_relationship_type">contains_data_for</data><data key="edge_target_entity_id">DOM_E_SERVICES</data><data key="edge_operational_context">SSA Open Data describes this staging instance as containing Client-to-Government electronic-service transaction information.</data><data key="edge_observed_as_of">2026-09-08</data><data key="edge_confidence">5</data><data key="edge_notes">No stage-to-ODS transport is inferred.</data></edge><edge id="REL_R26_006" source="DB_EDIS_MI" target="PLAT_EDIB"><data key="edge_relationship_id">REL_R26_006</data><data key="edge_source_entity_id">DB_EDIS_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">PLAT_EDIB</data><data key="edge_operational_context">The catalog title is Electronic Disability Management Information and the record says it provides MI on disability cases; modeled as a logical association to the existing Electronic Disability System.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Physical feed/component boundaries are not published.</data></edge><edge id="REL_R26_007" source="DB_CIRP_MI" target="APP_CIRP"><data key="edge_relationship_id">REL_R26_007</data><data key="edge_source_entity_id">DB_CIRP_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">APP_CIRP</data><data key="edge_operational_context">The SSA catalog record is explicitly the management-information asset for Comprehensive Integrity Review Process.</data><data key="edge_observed_as_of">2026-07-07</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_008" source="DB_TTW_WORKLOAD_MI" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL_R26_008</data><data key="edge_source_entity_id">DB_TTW_WORKLOAD_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">SSA Open Data explicitly describes management information about disability beneficiaries participating in the Ticket to Work/back-to-work program.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_009" source="APP_CWOSS" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL_R26_009</data><data key="edge_source_entity_id">APP_CWOSS</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">SSA Open Data says CWOSS captures workload case-management, contract, and payment information to support the Ticket to Work program.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_010" source="DB_CWOSS_MI" target="APP_CWOSS"><data key="edge_relationship_id">REL_R26_010</data><data key="edge_source_entity_id">DB_CWOSS_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">APP_CWOSS</data><data key="edge_operational_context">The current catalog record is explicitly titled CWOSS Management Information and describes the same workload, contract, and payment information.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">4</data><data key="edge_notes">Logical association is direct by title/purpose; physical separation or integration is not published.</data></edge><edge id="REL_R26_011" source="DB_CWOSS_MI" target="PROC_TICKET_TO_WORK"><data key="edge_relationship_id">REL_R26_011</data><data key="edge_source_entity_id">DB_CWOSS_MI</data><data key="edge_relationship_type">supports</data><data key="edge_target_entity_id">PROC_TICKET_TO_WORK</data><data key="edge_operational_context">SSA Open Data says the CWOSS MI asset captures workload case-management, contract, and payment information to support Ticket to Work.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_012" source="DB_T16_FO_APPEALS_ODS" target="DB_SUMS_APPEALS_ODS"><data key="edge_relationship_id">REL_R26_012</data><data key="edge_source_entity_id">DB_T16_FO_APPEALS_ODS</data><data key="edge_relationship_type">replaced_by</data><data key="edge_target_entity_id">DB_SUMS_APPEALS_ODS</data><data key="edge_operational_context">SSA Open Data explicitly states that the legacy Title XVI Field Office Appeals ODS was replaced by SUMS Appeals.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">The actual cutover date is not published; 2026-09-29 is the observation date.</data></edge><edge id="REL_R26_013" source="DB_DMS_MI" target="APP_DMS"><data key="edge_relationship_id">REL_R26_013</data><data key="edge_source_entity_id">DB_DMS_MI</data><data key="edge_relationship_type">provides_management_information_for</data><data key="edge_target_entity_id">APP_DMS</data><data key="edge_operational_context">SSA Open Data says the asset stores management information for the debt-management process. The Atlas associates that process with the existing Debt Management System.</data><data key="edge_observed_as_of">2026-08-06</data><data key="edge_confidence">4</data><data key="edge_notes">The catalog does not publish a physical DMS-to-MI feed.</data></edge><edge id="REL_R26_014" source="DB_MEDICARE_MI" target="PROC_EXTRA_HELP"><data key="edge_relationship_id">REL_R26_014</data><data key="edge_source_entity_id">DB_MEDICARE_MI</data><data key="edge_relationship_type">contains_management_information_for</data><data key="edge_target_entity_id">PROC_EXTRA_HELP</data><data key="edge_operational_context">SSA Open Data says this store includes Medicare Part D prescription-drug-subsidy processing and workload management information.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">No direct MAPS interface is inferred.</data></edge><edge id="REL_R26_015" source="DB_T2_ODS" target="DB_WMDW"><data key="edge_relationship_id">REL_R26_015</data><data key="edge_source_entity_id">DB_T2_ODS</data><data key="edge_relationship_type">provides_processing_time_data_to</data><data key="edge_target_entity_id">DB_WMDW</data><data key="edge_operational_context">SSA Open Data explicitly says the Title 2 ODS provides processing-time data to the Work Measurement Data Warehouse.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_016" source="APP_TIME_REFERENCE_MI" target="TECH_MAINFRAME"><data key="edge_relationship_id">REL_R26_016</data><data key="edge_source_entity_id">APP_TIME_REFERENCE_MI</data><data key="edge_relationship_type">maintains_reference_tables_on</data><data key="edge_target_entity_id">TECH_MAINFRAME</data><data key="edge_operational_context">SSA Open Data says fiscal- and processing-year reference tables maintained by this application are located on mainframe and data-warehouse servers.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes">Only the mainframe technology node is linked; the source does not identify a specific warehouse server product.</data></edge><edge id="REL_R26_017" source="APP_SEXTANT" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL_R26_017</data><data key="edge_source_entity_id">APP_SEXTANT</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA Open Data identifies Sextant as a Care 2020 reporting system providing real-time and historical N8NN management information about customer/agent interactions.</data><data key="edge_observed_as_of">2026-09-22</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_018" source="APP_NAR" target="PLAT_NUANCE_IVR"><data key="edge_relationship_id">REL_R26_018</data><data key="edge_source_entity_id">APP_NAR</data><data key="edge_relationship_type">reports_on_customer_interactions_with</data><data key="edge_target_entity_id">PLAT_NUANCE_IVR</data><data key="edge_operational_context">SSA Open Data explicitly says Nuance Application Reporting provides Care 2020 MI on customer interactions with the Nuance IVR system.</data><data key="edge_observed_as_of">2026-09-17</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_019" source="DB_VIPR_MI" target="APP_CHIP"><data key="edge_relationship_id">REL_R26_019</data><data key="edge_source_entity_id">DB_VIPR_MI</data><data key="edge_relationship_type">contains_management_information_related_to</data><data key="edge_target_entity_id">APP_CHIP</data><data key="edge_operational_context">SSA Open Data explicitly says the VIPR MI data store contains visitor/call/customer-relationship information relating to VIPR and CHIP.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">5</data><data key="edge_notes" /></edge><edge id="REL_R26_020" source="DB_WMI_GARNISHMENT" target="DB_T2_GARNISH"><data key="edge_relationship_id">REL_R26_020</data><data key="edge_source_entity_id">DB_WMI_GARNISHMENT</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">DB_T2_GARNISH</data><data key="edge_operational_context">SSA Open Data describes Title II benefit-adjustment and Treasury-payment reporting for garnishment; modeled as a logical reporting relationship to the existing T2 Garnishment Process data store.</data><data key="edge_observed_as_of">2026-09-29</data><data key="edge_confidence">4</data><data key="edge_notes">Physical data movement is not published.</data></edge><edge id="REL_R26_021" source="DB_PSC_PAPERLESS_MI" target="APP_PAPERLESS_PSC"><data key="edge_relationship_id">REL_R26_021</data><data key="edge_source_entity_id">DB_PSC_PAPERLESS_MI</data><data key="edge_relationship_type">reports_on</data><data key="edge_target_entity_id">APP_PAPERLESS_PSC</data><data key="edge_operational_context">SSA Open Data identifies current Program Service Center Paperless management-information reporting. The edge is modeled to the existing Paperless PSC entity by title/purpose.</data><data key="edge_observed_as_of">2026-09-08</data><data key="edge_confidence">4</data><data key="edge_notes">This does not establish that the 2007 PIA application is technically identical to the current Paperless Processing Center system.</data></edge><edge id="REL_R26_022" source="DB_UNIFIED_ICM_CCE" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL_R26_022</data><data key="edge_source_entity_id">DB_UNIFIED_ICM_CCE</data><data key="edge_relationship_type">historically_routes_calls_for</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA's 2017 catalog record says Unified ICM/CCE used its central database to determine how to route N8NN calls.</data><data key="edge_observed_as_of">2017-12-22</data><data key="edge_confidence">3</data><data key="edge_notes">Historical official architecture only; current operation is unverified.</data></edge><edge id="REL_R26_023" source="APP_VERINT_IMPACT360" target="SVC_NATIONAL_800"><data key="edge_relationship_id">REL_R26_023</data><data key="edge_source_entity_id">APP_VERINT_IMPACT360</data><data key="edge_relationship_type">historically_supported_workforce_optimization_for</data><data key="edge_target_entity_id">SVC_NATIONAL_800</data><data key="edge_operational_context">SSA's 2017 catalog record describes CARE 2020 workforce optimization and tags the asset N8NN/workforce management.</data><data key="edge_observed_as_of">2017-12-20</data><data key="edge_confidence">3</data><data key="edge_notes">Historical official architecture only; current operation is unverified.</data></edge><edge id="REL_R26_024" source="PROC_PIV_CARDSTOCK_2026" target="APP_PIV"><data key="edge_relationship_id">REL_R26_024</data><data key="edge_source_entity_id">PROC_PIV_CARDSTOCK_2026</data><data key="edge_relationship_type">procures_support_for</data><data key="edge_target_entity_id">APP_PIV</data><data key="edge_operational_context">SSA's July 2026 notice is for HSPD-12 PIV Cardstock Replacement and Personalization Services.</data><data key="edge_observed_as_of">2026-07-22</data><data key="edge_confidence">5</data><data key="edge_notes">The public notice does not name the intended vendor.</data></edge></graph></graphml>